- crux-devel - lists.crux.nu

[clc-devel] [CRUX] #99: xine-lib update
by CRUX 25 Feb '06

25 Feb '06

#99: xine-lib update --------------------+------------------------------------------------------- Id: 99 | Status: new Component: ports | Modified: Fri Feb 24 17:19:33 2006 Severity: normal | Milestone: Priority: normal | Version: Owner: sten | Reporter: mark --------------------+------------------------------------------------------- The 1.1 series of xine-lib is the only one officially supporting GCC 4.x according to the 1.1.0 release notes (https://sourceforge.net/project/shownotes.php?release_id=344962&group_id=96…) I haven't had any success building 1.1.1 myself, but it appears to be a local problem caused by using a modular X tree. -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/99> CRUX <http://crux.nu/> CRUX

1 1

[clc-devel] [CRUX] #61: httpup timeout may be a conf option
by CRUX 25 Feb '06

25 Feb '06

#61: httpup timeout may be a conf option -------------------------+-------------------------------------------------- Id: 61 | Status: new Component: httpup | Modified: Sun Jan 22 12:17:45 2006 Severity: enhancement | Milestone: Priority: normal | Version: Owner: jw | Reporter: centericq(a)ukr.net -------------------------+-------------------------------------------------- I propose to make CURLOPT_TIMEOUT a configurable value. Patch below adds new option to httpup.conf: {{{ operation_timeout 300 # Timeout for operation - default is 30 }}} This makes the life of users with slow net connection - just like me - a lot easier :) -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/61> CRUX <http://crux.nu/> CRUX

1 6

[clc-devel] Re: Your message to clc-devel awaits moderator approval
by Nick Steeves 25 Feb '06

25 Feb '06

Sorry about forgetting to bzip2 those attachments--I've since compressed them, and resent the email. Cheers, Nick On Saturday 25 February 2006 3:20, clc-devel-admin(a)berlios.de wrote: > Your mail to 'clc-devel' with the subject > > Re: [clc-devel] CRUX-2.2-devtest2 stage1 error > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Message body is too big: 139515 bytes but there's a limit of 40 KB > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision.

1 0

[clc-devel] [CRUX] #97: new location of ukraine repo
by CRUX 24 Feb '06

24 Feb '06

#97: new location of ukraine repo --------------------+------------------------------------------------------- Id: 97 | Status: new Component: ports | Modified: Thu Feb 23 10:28:01 2006 Severity: normal | Milestone: Priority: normal | Version: Owner: per | Reporter: artur[at]idt.org.ua --------------------+------------------------------------------------------- == URL == * httpup http://crux.org.ua/repo/ukraine * rsync rsync://crux.org.ua::repo/ukraine == Maintainer == artur at idt dot org dot ua -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/97> CRUX <http://crux.nu/> CRUX

1 5

[clc-devel] [CRUX] #98: cyrus-sasl needs patching for gcc4
by CRUX 24 Feb '06

24 Feb '06

#98: cyrus-sasl needs patching for gcc4 --------------------+------------------------------------------------------- Id: 98 | Status: new Component: ports | Modified: Thu Feb 23 23:51:25 2006 Severity: normal | Milestone: Priority: normal | Version: Owner: per | Reporter: mark --------------------+------------------------------------------------------- Attached patch is needed to make cyrus-sasl compile with gcc4. (Side note: it would be nice with a 2.2 version for tickets.) -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/98> CRUX <http://crux.nu/> CRUX

1 1

[clc-devel] IRC meeting results
by Johannes Winkelmann 23 Feb '06

23 Feb '06

Hi there, [ "you" in this mail means "crux developers" :-) ] A short summary of yesterday's IRC meeting for those who missed it: http://crux.nu/newsite/wikka.php?wakka=WebSwitch This basically means the following (technical details omitted): - you'll get a more powerful wiki with a slightly different syntax - you'll get a more powerful bug tracking - you can continue to use subversion - you'll get a faster web interface to svn - you have to get an account for both the wiki and the bug tracking - it would be great if you could help populate the new wiki Furthermore, some other points of interest: - We'll start working on 2.2 in subversion ASAP (it's just a matter of importing the current work) - you can have a <username>@crux.nu mail address (forwarding only); this is mainly mean for crux related mail So much for now; detailed information to any of these items follow. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

1 0

[clc-devel] [CRUX] #92: hicolor-icon-theme 0.9
by CRUX 23 Feb '06

23 Feb '06

#92: hicolor-icon-theme 0.9 ---------------------+------------------------------------------------------ Id: 92 | Status: new Component: ports | Modified: Sat Feb 18 14:37:21 2006 Severity: trivial | Milestone: Priority: low | Version: Owner: jaeger | Reporter: mark ---------------------+------------------------------------------------------ hicolor-icon-theme 0.9 is out. The ChangeLog is pretty sparse: * index.theme: Sort values for Directories keys (fix gnome bug 315841) and add missing entries. Now all installed directories should have an entry in this file. A simple bump is all there is to it :) -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/92> CRUX <http://crux.nu/> CRUX

1 1

[clc-devel] [CRUX] #95: opt/pure-ftpd incorrect checksum
by CRUX 22 Feb '06

22 Feb '06

#95: opt/pure-ftpd incorrect checksum ----------------------+----------------------------------------------------- Id: 95 | Status: new Component: ports | Modified: Wed Feb 22 06:37:13 2006 Severity: critical | Milestone: Priority: normal | Version: 2.0 Owner: per | Reporter: anonymous ----------------------+----------------------------------------------------- =======> ERROR: Md5sum mismatch found: MISSING 2b9fc86e8090a746cf57b11a55e3c0a8 pure-ftpd-1.0.21.tar.bz2 NEW ca8a8dbec0cd9c8ea92fc4c37ea9c410 pure-ftpd-1.0.21.tar.bz2 =======> ERROR: Building '/usr/ports/opt/pure-ftpd/pure- ftpd#1.0.21-1.pkg.tar.gz' failed. -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/95> CRUX <http://crux.nu/> CRUX

1 1

[clc-devel] [CRUX] #96: contrib/fop source url not available
by CRUX 22 Feb '06

22 Feb '06

#96: contrib/fop source url not available --------------------+------------------------------------------------------- Id: 96 | Status: new Component: ports | Modified: Wed Feb 22 10:55:31 2006 Severity: normal | Milestone: Priority: normal | Version: Owner: per | Reporter: rugek(a)dirtyhack.net --------------------+------------------------------------------------------- the following url is not longer available. http://apache.filearena.net/xml/fop/fop-0.20.5-bin.tar.gz instead you can use http://ftp.plusline.de/ftp.apache.org/xml/fop/binaries/fop-0.20.5-bin.tar.gz -- Ticket URL: <http://crux.nu/cgi-bin/trac.cgi/ticket/96> CRUX <http://crux.nu/> CRUX

1 2

[clc-devel] road to 2.2; some change proposals
by Johannes Winkelmann 21 Feb '06

21 Feb '06

Hi, [ This is directed towards CRUX developers; this is not a wishlist thread, so if you're not a developer and like something to be changed, please DON'T post it as follow-up to this! Thank you ] 2.2 is getting more and more real, thanks to Simone's great work and your testing. Along with the work on 2.2 itself, I'd like to address a number of things which seems tedious now; this mail is a (non exclusive) list of things I'd like to see changed, in the hope that we could discuss them on IRC sometimes; I'd propose next wednesday, 22.2., 8pm CET as a first meeting; #crux-cruxcon is the place to be. If you can make it, that would be great; otherwise, feel free to comment here, in private mail (again, please CRUX devs only) or on IRC at any other point in time. ----------------------------------------------------------- I. Trac, Apache, Subversion 1. Trac There are a number of issues here: - the wiki is rather weak; it lacks features of other wikis, like category support which would be great for documentation - the bug tracking in 0.8 is horrible (free text "assign" field, no fine grained permission model etc, bad defaults for the "assign field" etc.). Also, there's no way to send notifications directly to the person who got the report assigned. - trac's templates (or the way we use it) are a bit unflexible, which made us avoid the conversions to 0.9 so far - the tight coupling of all the components (website/wiki, bug tracker) makes it harder to update in general 2. Subversion & Apache Subversion has been a great replacement for CVS so far, and I'm basically very happy; however, there are a couple of downsides: - Its dependencies and compile time - the "five minute export for rsync hack" - The way we use it, we're forced to use apache as webserver, since it's the only one supporting mod_dav_svn I've talked to Simone about this, and the (fairly radical) proposal from us would be: a. Switch to Wikka as Wiki http://varlock.com/tmp/wikka2/wikka01.png b. Switch to flyspray as bug tracking (Simone uses it at work, and seems very happy with it) http://varlock.com/tmp/wikka2/flyspray01.png c. Switch to git as revision control tool; alternatives have either more dependencies (hg, bzr, svk), or are awkward to use (GNU arch/tla, bazaar) d. use gitweb as VCS interface http://www.kernel.org/git/gitweb.cgi?p=git/git.git;a=summary This would mean the following: - we can update the wiki, bugtracking, version control, and web server without any interdependencies - we get a more powerful wiki - we get a more powerful bug tracking, which has proper access right control (i.e. only registered users can submit bugs) - we can send out direct mail notifications to tickets, making clc/crux-devel a much nicer list again; there's also jabber notification support :-) - git has no dependencies beyond patch and diff, and installs fairly quickly - the git repository could directly be served via rsyncd for ports -u (ignoring .git and therefore the history), which would allow us to get rid of the "five minute export" crontab - we can (actually have to) use system groups to control permissions for several git repositories, which I think it nice - we could drop apache and go with lighttpd if we wanted :-) Disadvantages are: - we'll have to get uses to a new revision control tool - some work to set up the initial repositories A final note regarding git: Tilman who uses it for xmms2 said he sees no reason why we couldn't use it for CRUX; Per uses it at work; I've been toying with it lately; conversion should be painless, IMO (except for the initial import, which could require some work) A final note regarding the setup: Simone volunteered to do a test setup for the wiki and flyspray; I'd suggest we do this ASAP. Matt suggested to do further planning for this switch in the test setup, which sounds good to me :-) ----------------------------------------------------------- II. Mailing list move We're ready to move the mailing lists to crux.nu; this will mean that they'll get a new address; the suggested names are: crux(a)lists.crux.nu crux-dev(a)lists.crux.nu crux-git-commits(a)lists.crux.nu :-) I'm not sure if we'd want to drop the prefix crux- for the later two; it's pretty obvious from the second level domain anyway... if we want to import the old mails into the archive, we'd need the relevant files from the old lists [<-- open task] ----------------------------------------------------------- III. Ports mirroring We have a ports.crux.nu subdomain, and 2.2's 'ports' utility should use that; we'd also like to allow admins to mirror the ports tree around the world (we've been asked a couple of times whether this is possible). Therefore we need a concept to allow users to select a ports mirror. Simplest solution: set it in rc.conf, source that one from ports. slightly more elegant: introduce a ports.conf; kinda overkill though Obviously, we can use ports.crux.nu as a default here ----------------------------------------------------------- IV. SF DNS RR fix So we've had fixes in our /etc/hosts for a while, which is fine. However, it doesn't look like SF is going to "fix" their DNS anytime soon, so I think a better solution would be to work around it in pkgutils. There are different ways around it: 1. using a variable in Pkgfiles: source=($SF_MIRROR/...) 2. sed'ing "s|dl.sf.net|$SF_MIRROR|" in pkgmk; advantage: requires no changes to the package files; could also be made more generic, to allow users to specify things like this: url_transform=(dl.sf.net:heanet.dl.sf.net someother.common.host:mirror.to.it) SF_MIRROR and url_transform would probably go into pkgmk.conf. Crucial here is that we have a stable mirror as default. I think #2 is quite a hack, but this is where we meet reality :-/ ----------------------------------------------------------- Okay, that was quite a bit of information. I hope it's making sense, and am looking forward to discuss some of those ideas with you soon. Thanks for reading, Best regards Johannes -- Johannes Winkelmann mailto:jw@tks6.net Zurich, Switzerland http://jw.tks6.net

2 1