October 2008 - crux-devel

[CRUX][#364] mplayer port not working
by CRUX 15 Oct '08

15 Oct '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - miguel (sodamnmad) Attached to Project - CRUX Summary - mplayer port not working Task Type - New Port Version Category - ports - core/opt Status - New Assigned To - CRUX Developers Operating System - All Severity - Low Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - can't download the file: http://gentoo.chem.wisc.edu/gentoo/distfiles/mplayer-1.0_rc2_p27458.tar.bz2 maybe server is down? More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=364 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#363] tightvnc port not working
by CRUX 15 Oct '08

15 Oct '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. You have been assigned the following task: FS#363 - tightvnc port not working User who did this - miguel (sodamnmad) More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=363 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[CRUX][#363] tightvnc port not working
by CRUX 15 Oct '08

15 Oct '08

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - miguel (sodamnmad) Attached to Project - CRUX Summary - tightvnc port not working Task Type - New Port Version Category - ports - core/opt Status - New Assigned To - CRUX Developers Operating System - All Severity - Low Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - tight vnc port doesn't download file, times out More information can be found at the following URL: http://crux.nu/bugs/index.php?do=details&task_id=363 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

1 0

[RFC] new portdb
by Lucas Hazel 08 Oct '08

08 Oct '08

So it appears I've been handed the "portdb maintainer" hat. My first duty in this roll was to add a few repos to the portdb cacher. But alas the pdbcacher seems to have locked up and I don't have the privileges to kill the process. So rather than find out what's wrong with it, I've decided to write a new one (sans PHP) with a focus on me having to do as little data entry as possible. A few features I have in mind are, * Allow users to add repositories by themselves. * Allow users to create custom collections from other repositories. * Partial and full caching of repositories. * Make more information available, such as processing footprints, md5sums, meta data and verification results. * XML output, RSS feeds, email alerts, etc. * ??? * Profit Does anyone else have any nifty ideas for what could go into a new portdb? -- Lucas Hazel <lucas(a)amacdigital.com.au> AMAC Digital Products Technician 209 Beardy Street, Armidale NSW [phone: +61267711287]

4 5

Proposed git->rsync script updates
by Tilman Sauerbeck 07 Oct '08

07 Oct '08

Hi all, some months ago, I was frustrated with our git_to_httpup script. That script is run every 5 minutes and exports our ports repositories' contents to ~crux/git-to-rsync-working-copy directory structure. Which looks like this: git-to-rsync-working-copy |---crux-2.4 |---core |--- udev |--- rsync |--- ... |---opt |--- ... |---crux-2.5 |---core |--- ... |---opt |--- ... It annoys me that we're exporting *everything* every 5 minutes. I'd prefer if we exported only those repositories that changed, *when* they change, i.e. when some commit is pushed to the repository. This means we'd have to adjust the script that does the exporting. I suggest to make use of git's post-update hook there. That hook would run as the user who does the push, so the httpup area has to be writable by that user. Long story cut short, here's the new directory hierarchy: git-to-rsync-working-copy2 |---core (owned by core) |---2.4 |--- udev |--- rsync |--- ... |---2.5 |--- ... |---opt (owned by opt) |---2.4 |--- ... |---2.5 |--- ... Since we'd switch from "crux-2.4/core" style directories to "core/2.4" or something, we'd have to adjust our *.rsync files. Also we'd need to keep the old rsync area alive for users who are still running old CRUX systems. Advantages: o Updated ports are rsync-able after a very short time and not just after up to 5 minutes. o No more disk thrashing just because another 5 minutes went by even though there was no git activity. Disadvantages: o We'd have to adjust the *.rsync files. Would be doable with the CRUX release (2.5) o The branches that should be exported are currently set in each separate post-update hook, so once a new CRUX version is released, you need to touch {core,opt,contrib,xorg,xfce}.git/hooks/post-update. o More? Opinions? Should we do that switch? I've already written the necessary shell code, it just needs to be put in some separate function that can be sourced from the various hooks. Regards, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

2 1

IRC meeting tonight
by Johannes Winkelmann 07 Oct '08

07 Oct '08

Hi there, Here's a reminder for tonight's IRC meeting; main focus will be the upcoming 2.5 release progress. Looking forward to seeing you at 20 CEST in #crux-devel. Cheers, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch

1 0