From crux at crux.nu Sun Jun 1 08:31:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 01 Jun 2008 10:31:33 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48425e65.1J54zRrzlhedUZZx%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Sun Jun 1 08:37:10 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 01 Jun 2008 10:37:10 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <48425fb6.eXM479//uWwuvbq4%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/bash-completion Url: http://www.caliban.org/files/bash/bash-completion-20060301.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libxml2 Url: ftp://xmlsoft.org/libxml2/libxml2-2.6.32.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libxml2-python Url: ftp://xmlsoft.org/libxml2/libxml2-2.6.32.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libxslt Url: ftp://xmlsoft.org/libxml2/libxslt-1.1.24.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/rar Url: http://www.rarlab.com/rar/rarlinux-3.6.0.tar.gz Reason: curl: (6) Couldn't resolve host 'www.rarlab.com' State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/unrar Url: http://www.rarlab.com/rar/unrarsrc-3.7.8.tar.gz Reason: curl: (6) Couldn't resolve host 'www.rarlab.com' State: New Full report: http://crux.nu/files/check_urls.html From jue at jue.li Sun Jun 1 17:56:31 2008 From: jue at jue.li (Juergen Daubert) Date: Sun, 1 Jun 2008 19:56:31 +0200 Subject: [crux-devel] Vacation Message-ID: <20080601175631.GA27877@jue.netz> Hello, FYI, I'm offline for the next 2-3 weeks. Please have a look at my ports, if there are very important updates or fixes. thanks and best regrards Juergen -- Juergen Daubert | mailto:jue at jue.li Korb, Germany | http://jue.li/crux From crux at crux.nu Mon Jun 2 08:31:30 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 02 Jun 2008 10:31:30 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4843afe2.5jkavTR3MzyoXyw8%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Mon Jun 2 09:01:39 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 02 Jun 2008 11:01:39 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4843b6f3.XuezAqqBkeSlmoML%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/emacs Url: http://ftp.gnu.org/gnu/emacs/emacs-22.2.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/xorg-font-msttcorefonts Url: http://www.cabextract.org.uk/cabextract-1.2.tar.gz Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Tue Jun 3 08:31:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Tue, 03 Jun 2008 10:31:33 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48450165.ZfRa4TKszlZpDVsL%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From jw at smts.ch Tue Jun 3 08:40:30 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Tue, 3 Jun 2008 10:40:30 +0200 Subject: [crux-devel] Casual developer IRC meeting In-Reply-To: <20080523085402.GA17427@titanium.smts.lan> References: <20080523085402.GA17427@titanium.smts.lan> Message-ID: <20080603084030.GA6180@titanium.smts.lan> Hi again, On Fri, May 23, 2008 at 10:54:02 +0200, Johannes Winkelmann wrote: > Hi there, > > I'd like to suggest casual IRC meeting of us developers, with no fixed > agenda and no need to give notice whether you can attend or not. It looks like tuesday and wednesday are the favorites so far; for Lucas and Richard the time isn't optimal, so the CEST time slot is more like 18:00-23:00. Let's just try and see how this works out, I for one won't be able to make it at 18:00 either day. I'd suggest we wait a couple more days to give those that didn't comment so far a chance to do so. Cheers, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Wed Jun 4 08:31:37 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 04 Jun 2008 10:31:37 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484652e9.kqGQomOIG+/Re9Lq%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From sepen at users.sourceforge.net Wed Jun 4 08:55:48 2008 From: sepen at users.sourceforge.net (Jose V Beneyto) Date: Wed, 4 Jun 2008 10:55:48 +0200 Subject: [crux-devel] prtverify daily results In-Reply-To: <484652e9.kqGQomOIG+/Re9Lq%crux@crux.nu> References: <484652e9.kqGQomOIG+/Re9Lq%crux@crux.nu> Message-ID: <48465894.80505@users.sourceforge.net> crux at crux.nu wrote: > Differences since last check: > > > (no differences) > > > Full report: http://crux.nu/files/prtverify.log > _______________________________________________ > crux-devel mailing list > crux-devel at lists.crux.nu > http://lists.crux.nu/mailman/listinfo/crux-devel > Please avoid this message, this is only a test. From sepen at users.sourceforge.net Wed Jun 4 10:00:27 2008 From: sepen at users.sourceforge.net (Jose V Beneyto) Date: Wed, 04 Jun 2008 12:00:27 +0200 Subject: [crux-devel] sorted threads In-Reply-To: <483E6890.6010806@users.sourceforge.net> References: <483E6890.6010806@users.sourceforge.net> Message-ID: <484667BB.7090406@users.sourceforge.net> Jose V Beneyto wrote: > Hi, > > Sometimes I use the 'web page' for reading the crux-devel ML, I would > like to filter @daily messages from crux.nu (broken sources, and > prtverify report), I try to sort them by subject, but the tree view > doesn't appear. > > I suggest a little modification if could be made, is it possible or > reasonable? or maybe am I wrong? > > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > * [crux-devel] prtverify daily results crux at crux.nu > Heyo, can someone give me a response? Imho, every month should appear a new thread, and after that messages replies this one. I made a test previously and seems that could be possible with the correct email headers, i.e: X-Original-To: crux-devel at lists.crux.nu Delivered-To: crux-devel at lists.crux.nu [...] To: crux-devel at lists.crux.nu References: <484652e9.kqGQomOIG+/Re9Lq%crux at crux.nu> In-Reply-To: <484652e9.kqGQomOIG+/Re9Lq%crux at crux.nu> Subject: Re: [crux-devel] prtverify daily results Maybe I need more headers, someone has more ideas? Thanks and regards, Jose V Beneyto From tilman at crux.nu Wed Jun 4 10:46:33 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Wed, 4 Jun 2008 12:46:33 +0200 Subject: [crux-devel] sorted threads In-Reply-To: <483E6890.6010806@users.sourceforge.net> References: <483E6890.6010806@users.sourceforge.net> Message-ID: <20080604104632.GA1319@code-monkey.de> Jose V Beneyto [2008-05-29 10:25]: > Hi, > > Sometimes I use the 'web page' for reading the crux-devel ML, I would > like to filter @daily messages from crux.nu (broken sources, and > prtverify report), I try to sort them by subject, but the tree view > doesn't appear. > > I suggest a little modification if could be made, is it possible or > reasonable? or maybe am I wrong? I think you should talk to the mailman guys... we hardly have the ressources to maintain our own mailman fork. ... or use gmane, maybe their archive is more usable for you. 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Wed Jun 4 10:57:51 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Wed, 4 Jun 2008 12:57:51 +0200 Subject: [crux-devel] sorted threads In-Reply-To: <483E6890.6010806@users.sourceforge.net> References: <483E6890.6010806@users.sourceforge.net> Message-ID: <20080604105751.GA21988@titanium.smts.lan> Hi, On Thu, May 29, 2008 at 10:25:52 +0200, Jose V Beneyto wrote: > Hi, > > Sometimes I use the 'web page' for reading the crux-devel ML, I would > like to filter @daily messages from crux.nu (broken sources, and > prtverify report), I try to sort them by subject, but the tree view > doesn't appear. > > I suggest a little modification if could be made, is it possible or > reasonable? or maybe am I wrong? > > * [crux-devel] Potentially broken source downloads crux at crux.nu > * [crux-devel] Potentially broken source downloads crux at crux.nu I wouldn't like this kind of setup, since I sort by thread and date the last posted message in the thread, so this would mean that I'd always see the whole thread (quite big in the end of the month) on top, hiding the rest. The same would also happen on gmane.org. Maybe we should create a separate list for it, since the messages are somewhat annoying when you search for something in the mail archive. I know we've discussed this before and decided not to to avoid subscribing to multiple lists, but I think for the sake of having a clean archive I'd be willing to do that :-). Opinions? Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From sepen at users.sourceforge.net Wed Jun 4 14:32:19 2008 From: sepen at users.sourceforge.net (Jose V Beneyto) Date: Wed, 04 Jun 2008 16:32:19 +0200 Subject: [crux-devel] sorted threads In-Reply-To: <20080604104632.GA1319@code-monkey.de> References: <483E6890.6010806@users.sourceforge.net> <20080604104632.GA1319@code-monkey.de> Message-ID: <4846A773.4020500@users.sourceforge.net> Tilman Sauerbeck wrote: > Jose V Beneyto [2008-05-29 10:25]: >> Hi, >> >> Sometimes I use the 'web page' for reading the crux-devel ML, I would >> like to filter @daily messages from crux.nu (broken sources, and >> prtverify report), I try to sort them by subject, but the tree view >> doesn't appear. >> >> I suggest a little modification if could be made, is it possible or >> reasonable? or maybe am I wrong? > > I think you should talk to the mailman guys... we hardly have the > ressources to maintain our own mailman fork. Heyo Tilman, Well my idea was around nightly scripts (not mailman sources), which are running on crux.nu (on crontab I suppose), I think that could be easily modified for sending the mail with those headers However, after read the Johannes post and the reasons he gave me (http://lists.crux.nu/pipermail/crux-devel/2008-June/003548.html), I'm according that it's not a good idea, and would be better to have a separate ML for this. In this case, maybe in the future, could be added more nightly scripts which will give us other complementary info. Best regards, Jose V Beneyto From crux at crux.nu Thu Jun 5 08:26:37 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 05 Jun 2008 10:26:37 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4847a33d.ZzYDBpXWApZ0u9Xx%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/chrony Url: http://chrony.sunsite.dk/download/chrony-1.23.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libjpeg Url: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.80.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/psutils Url: ftp://ftp.enst.fr/pub/unix/a2ps/psutils-1.17.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Thu Jun 5 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 05 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4847a467.qUyGdOKPeSn8Sxpl%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Fri Jun 6 08:27:58 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 06 Jun 2008 10:27:58 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4848f50e.OXvY0JvKEFALZ2KE%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/samhain Url: http://la-samhna.de/archive/samhain_signed-2.4.4.tar.gz Reason: curl: (7) couldn't connect to host State: Reminder Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Fri Jun 6 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 06 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4848f5e6.GpgL8EMAqr3pxEjm%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From sepen at users.sourceforge.net Sat Jun 7 00:37:55 2008 From: sepen at users.sourceforge.net (Jose V Beneyto) Date: Sat, 07 Jun 2008 02:37:55 +0200 Subject: [crux-devel] pkgmk source verification is not always needed Message-ID: <4849D863.9050509@users.sourceforge.net> Hi, I keep my old laptop by installing packages manually instead of building it, I ear about pkg-get but in the practice I can do whatever it does by using prt-get and configuring PKGMK_PACKAGE_DIR variable in pkgmk.conf. However after playing a bit, see that pkgmk does something odd: bash-3.2# cd /usr/ports/core/autoconf bash-3.2# grep PKGMK_PACKAGE_DIR /etc/pkgmk.conf PKGMK_PACKAGE_DIR="/usr/pkg" bash-3.2# pkgmk -utd -cf /etc/pkgmk.conf =======> Package '/usr/pkg/autoconf#2.62-1.pkg.tar.gz' is not up to date. bash-3.2# file /usr/pkg/pkg-get#0.4.5-2.pkg.tar.gz /usr/pkg/pkg-get#0.4.5-2.pkg.tar.gz: gzip compressed data, from Unix, last modified: Sat Jun 7 00:46:33 2008 bash-3.2# bash -x /usr/bin/pkgmk -utd -cf /etc/pkgmk.conf 2>&1 | tail -10 ++ '[' '!' -e Pkgfile ']' ++ '[' '!' /usr/pkg/autoconf#2.62-1.pkg.tar.gz -nt Pkgfile ']' ++ RESULT=yes ++ break ++ echo yes + '[' yes = yes ']' + info 'Package '\''/usr/pkg/autoconf#2.62-1.pkg.tar.gz'\'' is not up to date.' + echo '=======> Package '\''/usr/pkg/autoconf#2.62-1.pkg.tar.gz'\'' is not up to date.' =======> Package '/usr/pkg/autoconf#2.62-1.pkg.tar.gz' is not up to date. + exit 0 It tries to check if the package is newer than the Pkgfile (test FILE1 -nt FILE2), so it breaks and returns yes as result for `build_needed`. Here is a piece of `build_needed` function: [...] RESULT="no" for FILE in $PKGMK_PKGFILE ${source[@]}; do FILE=`get_filename $FILE` if [ ! -e $FILE ] || [ ! $TARGET -nt $FILE ]; then RESULT="yes" break [...] After 'touch' the package it should do the trick, but also the problem appears and seems that I need all sources for checking if package is up to date. IMO it shouldn't be the default action to take, and maybe by would be better a switch option. I attached a patch with my idea. I prefer to comment this improvement before reporting it in FS, what are your opinions? Best regards, Jose V Beneyto -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: pkgutils.patch-check_sources URL: From tilman at crux.nu Sat Jun 7 06:52:42 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Sat, 7 Jun 2008 08:52:42 +0200 Subject: [crux-devel] pkgmk source verification is not always needed In-Reply-To: <4849D863.9050509@users.sourceforge.net> References: <4849D863.9050509@users.sourceforge.net> Message-ID: <20080607065241.GA1218@code-monkey.de> Jose V Beneyto [2008-06-07 02:37]: > I keep my old laptop by installing packages manually instead of building > it, I ear about pkg-get but in the practice I can do whatever it does by > using prt-get and configuring PKGMK_PACKAGE_DIR variable in pkgmk.conf. > However after playing a bit, see that pkgmk does something odd: Teaching pkgmk not try to making anything seems a bit odd. I think I'd rather patch prt-get to call pkgadd directly instead of whatever it does atm :] 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Sat Jun 7 08:01:41 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Sat, 7 Jun 2008 10:01:41 +0200 Subject: [crux-devel] pkgmk source verification is not always needed In-Reply-To: <4849D863.9050509@users.sourceforge.net> References: <4849D863.9050509@users.sourceforge.net> Message-ID: <20080607080141.GA9004@titanium.smts.lan> Hi, On Sat, Jun 07, 2008 at 02:37:55 +0200, Jose V Beneyto wrote: [...] > After 'touch' the package it should do the trick, but also the problem > appears and seems that I need all sources for checking if package is up to > date. IMO it shouldn't be the default action to take, and maybe by would be > better a switch option. I attached a patch with my idea. That doesn't really make sense to me. If you change a patch and run pkgmk, it should really rebuild the package without any special arguments. Another thing that this would break is when we get reports that the md5sum changed of an existing tarball. If I redownload the source, it should really also rebuild the source IMO. This is probably a corner case though. pkgmk is a tool to build packages from source. Adding additional code to handle cases where no source is available doesn't make sense to me. Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Sat Jun 7 08:25:57 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 07 Jun 2008 10:25:57 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <484a4615.N8Mfp1OO0yUookzx%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/imagemagick Url: ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.3.9-0.tar.bz2 Reason: curl: (19) Given file does not exist State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/tetex Url: ftp://dante.ctan.org/pub/tex/systems/unix/teTeX/current/distrib/tetex-src-3.0.tar.gz Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/tetex Url: ftp://dante.ctan.org/pub/tex/systems/unix/teTeX/current/distrib/tetex-texmf-3.0.tar.gz Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/tetex Url: ftp://dante.ctan.org/pub/tex/systems/unix/teTeX/current/distrib/tetex-texmfsrc-3.0.tar.gz Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sat Jun 7 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 07 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484a4766.GM66/NE85lETQDsV%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From tillbiedermann at yahoo.de Sat Jun 7 11:05:15 2008 From: tillbiedermann at yahoo.de (Till Biedermann) Date: Sat, 07 Jun 2008 13:05:15 +0200 Subject: [crux-devel] Casual developer IRC meeting In-Reply-To: <20080523085402.GA17427@titanium.smts.lan> References: <20080523085402.GA17427@titanium.smts.lan> Message-ID: <484A6B6B.6080404@yahoo.de> Hi Johannes, > I'd like to suggest casual IRC meeting of us developers, with no fixed > agenda and no need to give notice whether you can attend or not. > [....] > It's by no means a replacement for the existing meetings, but could help > to make us more efficient at getting things done, and could hopefully > allow those that aren't frequently on IRC join for the important bits. > I like this idea. Regards, Till From tillbiedermann at yahoo.de Sat Jun 7 11:22:26 2008 From: tillbiedermann at yahoo.de (Till Biedermann) Date: Sat, 07 Jun 2008 13:22:26 +0200 Subject: [crux-devel] Wiki vs public wiki [WAS: Quick Install Reference] In-Reply-To: <20080518111426.GA4552@titanium.smts.lan> References: <482EF39E.2010208@yahoo.de> <20080518111426.GA4552@titanium.smts.lan> Message-ID: <484A6F72.9070907@yahoo.de> Johannes Winkelmann wrote: > Hi there, > > I'd like to take Till's mail as a reason to bring up something quite > related regarding our website: I'd like to suggest that we rename the > "public wiki" to just wiki, and stop calling the regular website "wiki". > This may be somewhat silly since it is a wiki anyway, but it seems that > users don't understand the idea, or dislike the idea of the "privileged" > main wiki. > [....] > Finally, we might play with CSS's to make the wiki look different, so > that it's more obvious in which section you are. > ok for me. +1 Regards, Till From crux at crux.nu Sun Jun 8 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 08 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484b98e6.9p1AGiXxmbSVCIPn%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From lucas at die.net.au Mon Jun 9 01:14:55 2008 From: lucas at die.net.au (Lucas Hazel) Date: Mon, 9 Jun 2008 11:14:55 +1000 Subject: [crux-devel] pkgmk source verification is not always needed In-Reply-To: <4849D863.9050509@users.sourceforge.net> References: <4849D863.9050509@users.sourceforge.net> Message-ID: <20080609111455.4e6e3d42@akira.digitilocal> On Sat, 07 Jun 2008 02:37:55 +0200 Jose V Beneyto wrote: > Hi, > > I keep my old laptop by installing packages manually instead of > building it, I ear about pkg-get but in the practice I can do > whatever it does by using prt-get and configuring PKGMK_PACKAGE_DIR > variable in pkgmk.conf. However after playing a bit, see that pkgmk > does something odd: If all you want to do is gracefully prevent packages from being built, this is what I do on my underpowered laptop using and NFS shared PKGMK_PACKAGE_DIR, prt-get sysup --config-append="addcommand true" -- Lucas Hazel From crux at crux.nu Mon Jun 9 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 09 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484cea66.hLhzclce0iwr+THb%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Tue Jun 10 08:31:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Tue, 10 Jun 2008 10:31:33 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484e3be5.oxrMuK23TPa+bSvH%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Wed Jun 11 08:31:16 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 11 Jun 2008 10:31:16 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <484f8d54.jY9ib7S80ccDmiUl%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libtiff Url: ftp://ftp.remotesensing.org/libtiff/tiff-3.8.2.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/xemacs Url: http://ftp.xemacs.org/pub/xemacs/xemacs-21.4/xemacs-21.4.21.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/xlockmore Url: http://www.tux.org/pub/tux/xlockmore/xlockmore-5.23.tar.bz2 Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Wed Jun 11 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 11 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <484f8d67.jidOJN0T+StCDFMR%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Thu Jun 12 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 12 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4850dee6.Pej36nZpjIv+5ZeH%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Thu Jun 12 08:34:20 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 12 Jun 2008 10:34:20 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4850df8c.7331qY2GfaTy2IMZ%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libjpeg Url: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/netpbm Url: http://aon.iki.fi/files/netpbm/netpbm-10.35.44.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/psutils Url: ftp://ftp.enst.fr/pub/unix/a2ps/psutils-1.17.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Fri Jun 13 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 13 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48523067.GpWeGzffvhmK5DwE%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Fri Jun 13 08:45:49 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 13 Jun 2008 10:45:49 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <485233bd.QjzjgYWLnjdVxblk%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/samhain Url: http://la-samhna.de/archive/samhain_signed-2.4.4.tar.gz Reason: curl: (7) couldn't connect to host State: Reminder Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sat Jun 14 08:21:27 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 14 Jun 2008 10:21:27 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <48537f87.GYrj/wzxXDEhuEi9%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.80.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sat Jun 14 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 14 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485381e7.Rz/0SZmjXxqNKMFc%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Sun Jun 15 08:23:48 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 15 Jun 2008 10:23:48 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4854d194.+3ptRG3XRREiro/3%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/imagemagick Url: ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.3.9-0.tar.bz2 Reason: curl: (19) Given file does not exist State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/ocaml Url: http://caml.inria.fr/pub/distrib/ocaml-3.10/ocaml-3.10.2.tar.bz2 Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sun Jun 15 08:31:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 15 Jun 2008 10:31:33 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4854d365.rftZonDGyqp70Xw7%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From jw at smts.ch Mon Jun 16 06:35:26 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Mon, 16 Jun 2008 08:35:26 +0200 Subject: [crux-devel] 64-bit test run Message-ID: <20080616063526.GA15292@titanium.smts.lan> Hi there, As recently pointed out by Fredrik [1] the demand for 64-bit OSes is only getting bigger, and as more and more of us have access to 64-bit hardware it would be nice to work towards an official crux 64-bit port. To prepare for this, we've discussed about the possible ways to manage ports, and came up with the following suggestion: - we'll keep separate core-x86_64.git and opt-x86_64.git - we'll add post commit hooks to all repositories, allowing to track changes to a port easily - ports will appear in opt-x86_64.git because they have a maintainer on this platform, not because they're in opt.git In other words, there won't be an automatic way to merge changes, however in most situations updates should be straight forward anyway, and for the rest I'd suggest to write a script which fetches the primary port, and runs some merge tool. I also suggest that we use the term "primary maintainer" (tracks upstream & makes the call whether a release should be used in CRUX, equivalent to the current maintainer) and "arch maintainer" (tracks the primary port). Being an arch maintainer should be a lot less work, and might in the future also be a good way to get into CRUX. In order to get things going, it would be nice to hear how many of you would be willing to help on this project. We can probably start with one of the existing 64-bit versions, so the initial release should be ready fairly quickly. More interesting would be to get a feeling what the costs of maintaining ports on two platforms are. Looking forward to hearing from you. Thanks, Johannes [1] http://crux.nu/bugs/index.php?do=details&task_id=280 -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From jw at smts.ch Mon Jun 16 07:44:22 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Mon, 16 Jun 2008 09:44:22 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080616063526.GA15292@titanium.smts.lan> References: <20080616063526.GA15292@titanium.smts.lan> Message-ID: <20080616074422.GA7552@titanium.smts.lan> On Mon, Jun 16, 2008 at 08:35:26 +0200, Johannes Winkelmann wrote: [...] > In other words, there won't be an automatic way to merge changes, > however in most situations updates should be straight forward anyway, > and for the rest I'd suggest to write a script which fetches the primary > port, and runs some merge tool. I've quickly put together a script that fetches a port from another arch, and runs diff: http://jw.smts.ch/files/crux/get_port Adding hooks similar to rejmerge (merge/keep/overwrite) would be fairly easy. Will of course not work for 'x86_64' for now, since there's git repo (and thus no rsyncable directory) available. Regards, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Mon Jun 16 08:31:39 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 16 Jun 2008 10:31:39 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485624eb.+r8LKnQh80ErV0+N%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Mon Jun 16 08:56:08 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 16 Jun 2008 10:56:08 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <48562aa8.pvnVusD/L6FkwGQP%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/xaw3d Url: ftp://ftp.x.org/contrib/widgets/Xaw3d/R6.3/Xaw3d-1.5.tar.gz Reason: curl: (56) FTP response reading failed State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Tue Jun 17 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Tue, 17 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48577667.R6INxjbj3er/7UV7%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From mike at openbunker.org Tue Jun 17 09:48:23 2008 From: mike at openbunker.org (Mikhail Kolesnik) Date: Tue, 17 Jun 2008 12:48:23 +0300 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080616063526.GA15292@titanium.smts.lan> References: <20080616063526.GA15292@titanium.smts.lan> Message-ID: <20080617124823.27d002c1@amilo.home> Hello, Johannes. On Mon, 16 Jun 2008 08:35:26 +0200 Johannes Winkelmann wrote: > In order to get things going, it would be nice to hear how many of you > would be willing to help on this project. > > We can probably start with one of the existing 64-bit versions, so the > initial release should be ready fairly quickly. More interesting would > be to get a feeling what the costs of maintaining ports on two platforms > are. It would be great to see CRUX being actively maintained on amd64. It's good time to join efforts and produce a well-supported version. I can offer my help (at least) in testing server-side software ports (still don't have a spare amd64 workstation with X server nearby). I am not a developer, but it is a kind of topic some users might be interested in. Should we involve others not subscribed to crux-devel at some point? By the way, is there any job/task list planned? -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta From kontakt at ecarux.de Tue Jun 17 14:20:55 2008 From: kontakt at ecarux.de (Hannes Mayer) Date: Tue, 17 Jun 2008 16:20:55 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080616063526.GA15292@titanium.smts.lan> References: <20080616063526.GA15292@titanium.smts.lan> (sfid-20080616_202355_994535_4E8669F5) Message-ID: <200806171620.55249.kontakt@ecarux.de> A pure 64Bit version or 32 and 64 multilib? The first will be very easy. I working with my crux 64bit Version since over one year. I have only 30 new / different ports. Just get them if you like. http://ecarux.de/crux86_64/ From tilman at crux.nu Tue Jun 17 16:27:37 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Tue, 17 Jun 2008 18:27:37 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <200806171620.55249.kontakt@ecarux.de> References: <20080616063526.GA15292@titanium.smts.lan> <200806171620.55249.kontakt@ecarux.de> Message-ID: <20080617162736.GA4157@code-monkey.de> Hannes Mayer [2008-06-17 16:20]: Hi Hannes, > A pure 64Bit version or 32 and 64 multilib? > The first will be very easy. I working with my crux 64bit Version since over > one year. I have only 30 new / different ports. > Just get them if you like. http://ecarux.de/crux86_64/ At the moment it looks like we'll be getting started with an updated version of your ISO, i.e. a pure 64 bit system. I don't know yet whether a multilib system would be better[tm]; we'll have to make up our minds later on this one :) 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From predatorfreak at dcaf-security.org Tue Jun 17 20:14:48 2008 From: predatorfreak at dcaf-security.org (Brett Goulder) Date: Tue, 17 Jun 2008 16:14:48 -0400 Subject: [crux-devel] Resigning from opt/contrib Message-ID: <20080617161448.6f2f8c7d@predatorbox> I'm done with contributing to CRUX in a formal way, I'm fed up with the bickering. I'm resigning from opt and contrib, so all of my ports in opt or contrib are up for grabs. Ports I maintain in opt: bchunk dbus dbus-glib dbus-python firefox firefox-flash-plugin gl-select grub hal hal-info libxvid mplayer nvidia openntpd rar win32-essential-codecs xulrunner yasm Ports I maintain in contrib: mkvtoolnix md5deep libebml libmatroska hplip -- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From pitillo at ono.com Tue Jun 17 21:57:44 2008 From: pitillo at ono.com (Victor Martinez) Date: Tue, 17 Jun 2008 23:57:44 +0200 Subject: [crux-devel] Resigning from opt/contrib In-Reply-To: <20080617161448.6f2f8c7d@predatorbox> References: <20080617161448.6f2f8c7d@predatorbox> Message-ID: <20080617235744.9962595b.pitillo@ono.com> On Tue, 17 Jun 2008 16:14:48 -0400 Brett Goulder wrote: Hello Brett, > I'm done with contributing to CRUX in a formal way, I'm fed up with the > bickering. I'm resigning from opt and contrib, so all of my ports in > opt or contrib are up for grabs. > > [...] > Sure you will be missed, I repeat my opinion here too. It's quite sad to lose good people (good people in all senses) in a little comunity. Thank you very much for your work, help and time. -- Learning bit by bit. -pitillo- From lucas at die.net.au Wed Jun 18 02:35:35 2008 From: lucas at die.net.au (Lucas Hazel) Date: Wed, 18 Jun 2008 12:35:35 +1000 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080617162736.GA4157@code-monkey.de> References: <20080616063526.GA15292@titanium.smts.lan> <200806171620.55249.kontakt@ecarux.de> <20080617162736.GA4157@code-monkey.de> Message-ID: <20080618123535.1c95ae21@akira.digitilocal> On Tue, 17 Jun 2008 18:27:37 +0200 Tilman Sauerbeck wrote: > Hannes Mayer [2008-06-17 16:20]: > > Hi Hannes, > > > A pure 64Bit version or 32 and 64 multilib? > > The first will be very easy. I working with my crux 64bit Version > > since over one year. I have only 30 new / different ports. > > Just get them if you like. http://ecarux.de/crux86_64/ > > At the moment it looks like we'll be getting started with an updated > version of your ISO, i.e. a pure 64 bit system. > > I don't know yet whether a multilib system would be better[tm]; we'll > have to make up our minds later on this one :) > Sure pure64 has it's advantages in that it's a single library set, but there are a number of sacrifices you have to be willing to make in terms of applications that are 32 bit only. Of course flash and acroread come to mind. But there's also proprietary media codecs, you can also say goodbye to wine, and any games out there you might like to play. Until recently there was no java plugin for 64 bit browsers as well. However I just discovered that RedHat is developing one in OpenJDK. Personally I feel rather than targeting a specific alternative platform, we should be coming up with a solution for any number of systems. We have had people targeting other systems other than amd64 such as a port to openbsd and even versions for the PPC and ARM processor. While I'll be the first to agree that my multiarch solution is probably not the best, however, it has allowed me to keep in sync with the official crux repos with relative ease as it makes changes required of me to make minimal, git merges are always conflict free aswell. I have a set of 110 ports that require compat32 and or x86_64 changes across core/opt/xorg/contrib. Most of time I will only need to edit these is when there is a change to the build script otherwise it's just a matter of fetch/merge/push. Again, I think a more holistic approach should be taken if CRUX officially decided to adopt another platform such as amd64. -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Wed Jun 18 08:25:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 18 Jun 2008 10:25:33 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4858c67d.Oo4OVVJbzATzlMrP%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/netpbm Url: http://aon.iki.fi/files/netpbm/netpbm-10.35.45.tar.gz Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Wed Jun 18 08:31:31 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 18 Jun 2008 10:31:31 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4858c7e3.K5MM8SFyBa2GLbjC%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From lucas at die.net.au Wed Jun 18 13:42:32 2008 From: lucas at die.net.au (Lucas Hazel) Date: Wed, 18 Jun 2008 23:42:32 +1000 Subject: [crux-devel] Resigning from opt/contrib In-Reply-To: <20080617161448.6f2f8c7d@predatorbox> References: <20080617161448.6f2f8c7d@predatorbox> Message-ID: <20080618234232.12b30a02@akira.digitilocal> On Tue, 17 Jun 2008 16:14:48 -0400 Brett Goulder wrote: > I'm done with contributing to CRUX in a formal way, I'm fed up with > the bickering. I'm resigning from opt and contrib, so all of my ports > in opt or contrib are up for grabs. Sad to see you go, I hope that day where I gave you hell over hal wasn't a contributing factor ;) Apparently it was rude of me to start adopting ports without first saying please and thank you. I have already adopted libebml, libmatroska, and mkvtoolnix. If there are any objections, let me know. IIRC I asked Brett to move these into contrib in the first place. I won't be touching the firefox port as it's quite clear that it is cursed. Opt ports I'd be willing to take on are dbus*, gl-select, grub, hal*, libxvid, mplayer, nvidia and rar But if anyone else wants them instead I don't mind. > Ports I maintain in opt: > > bchunk > dbus > dbus-glib > dbus-python > firefox > firefox-flash-plugin > gl-select > grub > hal > hal-info > libxvid > mplayer > nvidia > openntpd > rar > win32-essential-codecs > xulrunner > yasm > > Ports I maintain in contrib: > mkvtoolnix > md5deep > libebml > libmatroska > hplip > -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From tilman at crux.nu Wed Jun 18 15:06:42 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Wed, 18 Jun 2008 17:06:42 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080618123535.1c95ae21@akira.digitilocal> References: <20080616063526.GA15292@titanium.smts.lan> <200806171620.55249.kontakt@ecarux.de> <20080617162736.GA4157@code-monkey.de> <20080618123535.1c95ae21@akira.digitilocal> Message-ID: <20080618150641.GA1149@code-monkey.de> Lucas Hazel [2008-06-18 12:35]: > On Tue, 17 Jun 2008 18:27:37 +0200 > Tilman Sauerbeck wrote: > > > Hannes Mayer [2008-06-17 16:20]: > > > > Hi Hannes, > > > > > A pure 64Bit version or 32 and 64 multilib? > > > The first will be very easy. I working with my crux 64bit Version > > > since over one year. I have only 30 new / different ports. > > > Just get them if you like. http://ecarux.de/crux86_64/ > > > > At the moment it looks like we'll be getting started with an updated > > version of your ISO, i.e. a pure 64 bit system. > > > > I don't know yet whether a multilib system would be better[tm]; we'll > > have to make up our minds later on this one :) > > > > Sure pure64 has it's advantages in that it's a single library set, but > there are a number of sacrifices you have to be willing to make in > terms of applications that are 32 bit only. Of course flash and > acroread come to mind. But there's also proprietary media codecs, you > can also say goodbye to wine, and any games out there you might like to > play. Until recently there was no java plugin for 64 bit browsers > as well. However I just discovered that RedHat is developing one in > OpenJDK. True... I still need to finish Doom3, and I probably don't want to wait until it's GPLd :| > Personally I feel rather than targeting a specific alternative > platform, we should be coming up with a solution for any number of > systems. We have had people targeting other systems other than amd64 > such as a port to openbsd and even versions for the PPC and ARM > processor. > > While I'll be the first to agree that my multiarch solution is probably > not the best, however, it has allowed me to keep in sync with the > official crux repos with relative ease as it makes changes required of > me to make minimal, git merges are always conflict free aswell. > > I have a set of 110 ports that require compat32 and or x86_64 changes > across core/opt/xorg/contrib. Most of time I will only need to edit > these is when there is a change to the build script otherwise it's just > a matter of fetch/merge/push. > > Again, I think a more holistic approach should be taken if CRUX > officially decided to adopt another platform such as amd64. We'd like to achieve omg-awesome portability (I care much more about other architectures than operating systems though). Hopefully the scheme we have in mind will allow for the needed flexibility. We have of course looked at your multiarch solution, but found it to be kind of ugly. 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From lucas at die.net.au Wed Jun 18 15:42:53 2008 From: lucas at die.net.au (Lucas Hazel) Date: Thu, 19 Jun 2008 01:42:53 +1000 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080618150641.GA1149@code-monkey.de> References: <20080616063526.GA15292@titanium.smts.lan> <200806171620.55249.kontakt@ecarux.de> <20080617162736.GA4157@code-monkey.de> <20080618123535.1c95ae21@akira.digitilocal> <20080618150641.GA1149@code-monkey.de> Message-ID: <20080619014253.274584ed@akira.digitilocal> On Wed, 18 Jun 2008 17:06:42 +0200 Tilman Sauerbeck wrote: > We'd like to achieve omg-awesome portability (I care much more about > other architectures than operating systems though). Hopefully the > scheme we have in mind will allow for the needed flexibility. Is it just me or does there appear to be a "CRUX SECRET UNDERGROUND", it seems there's a lot of discussion that doesn't even make it to -devel... > We have of course looked at your multiarch solution, but found it to > be kind of ugly. Well yeah, it is kinda ugly I guess. But it did make life easy for me by allowing automatic merging with the official repos, and being perhaps the only 64bit multilib CRUX user I'm sure the reasons for such a feature are apparent. I initially looked at using the repo-per-architecture setup, but there was too much hand editing involved, I had to essentially edit 2 ports every time there was a version change. This also made writing compat32 ports rather tedious. But it seems this is the way we are going, so I guess I'll start splitting up my multiarch repos. Perhaps git-rebase -i can make merging a bit less hassle. -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Thu Jun 19 05:51:32 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Thu, 19 Jun 2008 07:51:32 +0200 Subject: [crux-devel] Precompiled headers and distributed compilation In-Reply-To: <20080518103209.GA12538@titanium.smts.lan> References: <20080518103209.GA12538@titanium.smts.lan> Message-ID: <20080619055132.GA24869@titanium.smts.lan> On Sun, May 18, 2008 at 12:32:09 +0200, Johannes Winkelmann wrote: > Hi there, > > My qt4 port triggered an error [1] when using distcc to build it. After > some investigation, I realized that Qt4 by default uses precompiled > headers [2], which break when the compilation is done on a different > machine since the precompiled headers are not transfered automatically. > > Currently, this means that any package using PCH will break when > trying to compile it with distcc. As a heads up, there's a new maintainer for distcc, and apparently one of the features to come soonish is support for precompiled headers. More info here: http://sourcefrog.net/weblog/2008/06/19/#passing-baton Good news for the distcc crowd :-). Regards, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From jw at smts.ch Thu Jun 19 06:51:57 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Thu, 19 Jun 2008 08:51:57 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080617124823.27d002c1@amilo.home> References: <20080616063526.GA15292@titanium.smts.lan> <20080617124823.27d002c1@amilo.home> Message-ID: <20080619065157.GA28827@titanium.smts.lan> Hi Mikhail, On Tue, Jun 17, 2008 at 12:48:23 +0300, Mikhail Kolesnik wrote: > Hello, Johannes. [...] > It would be great to see CRUX being actively maintained on amd64. It's > good time to join efforts and produce a well-supported version. > > I can offer my help (at least) in testing server-side software ports > (still don't have a spare amd64 workstation with X server nearby). Cool, that's good to hear. > I am not a developer, but it is a kind of topic some users might be > interested in. Should we involve others not subscribed to crux-devel at > some point? Since we want to get a feeling whether the approach works out, we'll definitely need some testers once we're familiar (and happy!) with the setup. That said, at this point in time this is a purely technical experiment, and there's a lot of open, non-technical questions which have to be answered > By the way, is there any job/task list planned? Not so far, but maybe we can start it here: - decide which CRUX64 version we want to start with (pure vs multilib) - set up the git repositories - set up the git commit hooks to allow arch maintainers tracking other arch's ports - get a feeling of maintaining arch ports Once that's done and if we're happy with it, we should announce the test run to crux@ and ask for testers. At the same time, we can start discussion about the structure of the project, i.e. how archs should be coordinated etc. Once that's clear (and assuming all goes well), we can hopefully put out a 2.5 release supporting both 32 and 64 bit x86 :-). That's just my personal view BTW :-). Cheers, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From jw at smts.ch Thu Jun 19 06:56:53 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Thu, 19 Jun 2008 08:56:53 +0200 Subject: [crux-devel] Casual developer IRC meeting In-Reply-To: <20080603084030.GA6180@titanium.smts.lan> References: <20080523085402.GA17427@titanium.smts.lan> <20080603084030.GA6180@titanium.smts.lan> Message-ID: <20080619065653.GB28827@titanium.smts.lan> On Tue, Jun 03, 2008 at 10:40:30 +0200, Johannes Winkelmann wrote: > Hi again, > > On Fri, May 23, 2008 at 10:54:02 +0200, Johannes Winkelmann wrote: > > Hi there, > > > > I'd like to suggest casual IRC meeting of us developers, with no fixed > > agenda and no need to give notice whether you can attend or not. > It looks like tuesday and wednesday are the favorites so far; for Lucas > and Richard the time isn't optimal, so the CEST time slot is more like > 18:00-23:00. Let's just try and see how this works out, I for one won't > be able to make it at 18:00 either day. I think most have commented and/or voted, and judging from the doodle result tuesday is the day that works for most. Let's start next week, and see how it works out. I'll try and send a reminder mail tuesday afternoon :-). Best wishes, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Thu Jun 19 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 19 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485a1966.fZy2iGx8eq8D1kN2%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From tilman at crux.nu Thu Jun 19 19:33:49 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Thu, 19 Jun 2008 21:33:49 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080619014253.274584ed@akira.digitilocal> References: <20080616063526.GA15292@titanium.smts.lan> <200806171620.55249.kontakt@ecarux.de> <20080617162736.GA4157@code-monkey.de> <20080618123535.1c95ae21@akira.digitilocal> <20080618150641.GA1149@code-monkey.de> <20080619014253.274584ed@akira.digitilocal> Message-ID: <20080619193136.GA12844@code-monkey.de> Lucas Hazel [2008-06-19 01:42]: > On Wed, 18 Jun 2008 17:06:42 +0200 > Tilman Sauerbeck wrote: > > > We'd like to achieve omg-awesome portability (I care much more about > > other architectures than operating systems though). Hopefully the > > scheme we have in mind will allow for the needed flexibility. > > Is it just me or does there appear to be a "CRUX SECRET UNDERGROUND", > it seems there's a lot of discussion that doesn't even make it to > -devel... Johannes and me had a private chat about this crux64 test thingie a couple of days ago. It was a little bit undergroundish, but since the topic made it to the list I don't feel very bad ;o 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? From sepen at users.sourceforge.net Thu Jun 19 19:59:23 2008 From: sepen at users.sourceforge.net (Jose V Beneyto) Date: Thu, 19 Jun 2008 21:59:23 +0200 Subject: [crux-devel] crux64 Message-ID: <485ABA9B.2060504@users.sourceforge.net> Hi, I don't have 64 boxes, but maybe in the near future or at office, and surely I'll be really interested on knowledge about it and reading these last messages. ATM CRUX is targeted for 686 systems, so I would propose you to move all 64 related mails to his mailing list [1]. What are your opinions? Best regards, Jose V Beneyto References: [1] http://lists.crux.nu/mailman/listinfo/crux64 From crux at crux.nu Fri Jun 20 08:23:03 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 20 Jun 2008 10:23:03 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <485b68e7.jlgSx5lEzIA1mNeZ%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libjpeg Url: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.80.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/psutils Url: ftp://ftp.enst.fr/pub/unix/a2ps/psutils-1.17.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Fri Jun 20 08:31:32 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 20 Jun 2008 10:31:32 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485b6ae4.LxZRmJezdVPkGuoo%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From tilman at crux.nu Fri Jun 20 22:32:28 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Sat, 21 Jun 2008 00:32:28 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080616074422.GA7552@titanium.smts.lan> References: <20080616063526.GA15292@titanium.smts.lan> <20080616074422.GA7552@titanium.smts.lan> Message-ID: <20080620223228.GA28997@code-monkey.de> Johannes Winkelmann [2008-06-16 09:44]: > On Mon, Jun 16, 2008 at 08:35:26 +0200, Johannes Winkelmann wrote: > [...] > > In other words, there won't be an automatic way to merge changes, > > however in most situations updates should be straight forward anyway, > > and for the rest I'd suggest to write a script which fetches the primary > > port, and runs some merge tool. > I've quickly put together a script that fetches a port from another > arch, and runs diff: > http://jw.smts.ch/files/crux/get_port > Adding hooks similar to rejmerge (merge/keep/overwrite) would be fairly > easy. > > Will of course not work for 'x86_64' for now, since there's git repo > (and thus no rsyncable directory) available. I've set up {core,opt,xorg}-x86_64.git today. So opt.rsync looks like this eg: host=crux.nu collection=ports/crux-2.4/opt-x86_64/ destination=/usr/ports/opt ... so just append "-x86_64" to the URLs ;) The repos are still pretty empty, but will probably be populated soonish :D 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From wszystkie.fajne.loginy.zajete at gmail.com Sat Jun 21 00:04:35 2008 From: wszystkie.fajne.loginy.zajete at gmail.com (Bartek Palmowski) Date: Sat, 21 Jun 2008 02:04:35 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: References: Message-ID: <485C4593.7040906@gmail.com> Hi crux64 looks promissing, and I'd me more than happy if I could help with project. I already have done some initial testing and must say crux for 64 bit processors is in demand. If I may suggest an idea to add variable to pkgmk.conf like ie. ARCH_HOST=64, which would make easier "architecture type" extraction. regards Bartlomiej Palmowski From lucas at die.net.au Sat Jun 21 04:43:42 2008 From: lucas at die.net.au (Lucas Hazel) Date: Sat, 21 Jun 2008 14:43:42 +1000 Subject: [crux-devel] 64-bit test run In-Reply-To: <485C4593.7040906@gmail.com> References: <485C4593.7040906@gmail.com> Message-ID: <20080621144342.77bf277c@akira.digitilocal> On Sat, 21 Jun 2008 02:04:35 +0200 Bartek Palmowski wrote: > Hi > > crux64 looks promissing, and I'd me more than happy if I could > help with project. I already have done some initial testing and must > say crux for 64 bit processors is in demand. If I may suggest an idea > to add variable to pkgmk.conf like ie. ARCH_HOST=64, which would make > easier "architecture type" extraction. > Why would that be a good idea? -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Sat Jun 21 08:29:02 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 21 Jun 2008 10:29:02 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <485cbbce.vQ5RXA//HXpdaESQ%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/core/net-tools Url: http://www.tazenda.demon.co.uk/phil/net-tools/net-tools-1.60.tar.bz2 Reason: curl: (28) connect() timed out! State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sat Jun 21 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 21 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485cbc66.KLWucbs85VcQFXXO%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From tilman at crux.nu Sat Jun 21 09:43:06 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Sat, 21 Jun 2008 11:43:06 +0200 Subject: [crux-devel] crux64 In-Reply-To: <485ABA9B.2060504@users.sourceforge.net> References: <485ABA9B.2060504@users.sourceforge.net> Message-ID: <20080621094306.GA1269@code-monkey.de> Jose V Beneyto [2008-06-19 21:59]: > Hi, > > I don't have 64 boxes, but maybe in the near future or at office, and > surely I'll be really interested on knowledge about it and reading these > last messages. ATM CRUX is targeted for 686 systems, so I would propose > you to move all 64 related mails to his mailing list [1]. > > What are your opinions? I agree, let's move x86_64 related discussions over there. 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From tilman at crux.nu Sat Jun 21 09:47:29 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Sat, 21 Jun 2008 11:47:29 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <485C4593.7040906@gmail.com> References: <485C4593.7040906@gmail.com> Message-ID: <20080621094728.GB1269@code-monkey.de> Bartek Palmowski [2008-06-21 02:04]: > crux64 looks promissing, and I'd me more than happy if I could help > with project. I already have done some initial testing and must say crux > for 64 bit processors is in demand. If I may suggest an idea to add > variable to pkgmk.conf like ie. ARCH_HOST=64, which would make easier > "architecture type" extraction. What were playing with atm are separate ports trees for x86_64. So opt-x84_64/foo/Pkgfile will only be used on x86_64 and so there's no need to check the current architecture etc. I guess I should document the layout I have in mind in the wiki? 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Sun Jun 22 08:27:30 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 22 Jun 2008 10:27:30 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <485e0cf2.IR/0WC2V8UQ7Pi4m%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/avahi Url: http://avahi.org/download/avahi-0.6.22.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/imagemagick Url: ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.3.9-0.tar.bz2 Reason: curl: (19) Given file does not exist State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libdaemon Url: http://0pointer.de/lennart/projects/libdaemon/libdaemon-0.12.tar.gz Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sun Jun 22 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 22 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485e0de6.JIL34NzQ4Eu1jnAh%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From predatorfreak at dcaf-security.org Sun Jun 22 09:31:15 2008 From: predatorfreak at dcaf-security.org (Brett Goulder) Date: Sun, 22 Jun 2008 05:31:15 -0400 Subject: [crux-devel] Resigning from opt/contrib In-Reply-To: <20080617161448.6f2f8c7d@predatorbox> References: <20080617161448.6f2f8c7d@predatorbox> Message-ID: <20080622053115.44a23bdf@predatorbox> On Tue, 17 Jun 2008 16:14:48 -0400 Brett Goulder wrote: > I'm done with contributing to CRUX in a formal way, I'm fed up with > the bickering. I'm resigning from opt and contrib, so all of my ports > in opt or contrib are up for grabs. > > Ports I maintain in opt: > > bchunk > dbus > dbus-glib > dbus-python > firefox > firefox-flash-plugin > gl-select > grub > hal > hal-info > libxvid > mplayer > nvidia > openntpd > rar > win32-essential-codecs > xulrunner > yasm > I forgot a port here, nss. > Ports I maintain in contrib: > mkvtoolnix > md5deep > libebml > libmatroska > hplip > -- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From jw at smts.ch Sun Jun 22 11:00:10 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Sun, 22 Jun 2008 13:00:10 +0200 Subject: [crux-devel] Resigning from opt/contrib In-Reply-To: <20080617161448.6f2f8c7d@predatorbox> References: <20080617161448.6f2f8c7d@predatorbox> Message-ID: <20080622110010.GE9492@selenium.smts.lan> Hi Brett, On Tue, Jun 17, 2008 at 16:14:48 -0400, Brett Goulder wrote: > I'm done with contributing to CRUX in a formal way, I'm fed up with the > bickering. I'm resigning from opt and contrib, so all of my ports in > opt or contrib are up for grabs. Thanks for your contributions, and sorry for the bickering :-). Here's an updated list of orphaned ports (thanks for those who picked up the others): > bchunk > firefox-flash-plugin > nss > win32-essential-codecs > yasm yasm currently has no dependent packages in opt, bchunk is a standalone app. I could imagine that people would yell at us if we dropped firefox-flash-plugin and win32-essential-codecs, so if there are volunteers please feel free to speak up :-). Best wishes, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From lucas at die.net.au Sun Jun 22 13:49:47 2008 From: lucas at die.net.au (Lucas Hazel) Date: Sun, 22 Jun 2008 23:49:47 +1000 Subject: [crux-devel] Specifying architecture in port Message-ID: <20080622234947.00f6b10e@akira.digitilocal> I'm putting together some multilib ports in the style that has been suggested for the upcoming 64 bit test run. An issue unique to multilib, compared to pure 64 bit, is that two different sets of libraries exist on the same system. This also means that there are a different set of options required for each one to be used by pkgmk. http://git.die.net.au/cgit/crux/ports/core/tree/pkgutils/x86_64/pkgmk.conf?h=multiarch This is the solution Daniel came up with when he first released the original CRUX64 several years ago. While not ideal, it's a necessary evil when dealing with multilib. The issue is that pkgutils requires the port to identify itself as a compat32 port. The method I'm using currently is to use a .arch file in the port. http://git.die.net.au/cgit/crux/tools/pkgutils/commit/?id=e31dab6d68b26811e92ae5c4646b9958cf76f22a This differs from Daniels original implementation which was to put it into the Pkgfile using arch=compat32. However, I believe that keeping it out of the Pkgfile is a much better solution. Using such a method also has it's advantages in cross compiling for people who want to build ports for alternative architectures that don't have the resources to build natively, such as embedded platforms. I'm just wondering if anyone else had anything to contribute to the idea, or alternative solutions before I go too far and have another set of ports that isn't going to be incompatible with CRUX. -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Mon Jun 23 08:21:54 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 23 Jun 2008 10:21:54 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <485f5d22.gIo3j6Kg7RIivIWy%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libpcap Url: http://www.tcpdump.org/release/libpcap-0.9.8.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.80.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/tcpdump Url: http://www.tcpdump.org/release/tcpdump-3.9.8.tar.gz Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Mon Jun 23 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 23 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <485f5f66.ZiUcZJzgbPKC//4U%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From predatorfreak at dcaf-security.org Tue Jun 24 01:05:02 2008 From: predatorfreak at dcaf-security.org (Brett Goulder) Date: Mon, 23 Jun 2008 21:05:02 -0400 Subject: [crux-devel] Resigning from opt/contrib In-Reply-To: <20080622110010.GE9492@selenium.smts.lan> References: <20080617161448.6f2f8c7d@predatorbox> <20080622110010.GE9492@selenium.smts.lan> Message-ID: <20080623210502.216b9b31@predatorbox> On Sun, 22 Jun 2008 13:00:10 +0200 Johannes Winkelmann wrote: > Hi Brett, > > On Tue, Jun 17, 2008 at 16:14:48 -0400, Brett Goulder wrote: > > I'm done with contributing to CRUX in a formal way, I'm fed up with > > the bickering. I'm resigning from opt and contrib, so all of my > > ports in opt or contrib are up for grabs. > > Thanks for your contributions, and sorry for the bickering :-). > > Here's an updated list of orphaned ports (thanks for those who picked > up the others): > > bchunk > > firefox-flash-plugin > > nss > > win32-essential-codecs > > yasm > > yasm currently has no dependent packages in opt, bchunk is a > standalone app. I could imagine that people would yell at us if we > dropped firefox-flash-plugin and win32-essential-codecs, so if there > are volunteers please feel free to speak up :-). yasm is preferred by both the xvid and x264 developers, potentially other apps. That's why I added it to opt. > > Best wishes, > Johannes -- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lucas at die.net.au Tue Jun 24 01:15:24 2008 From: lucas at die.net.au (Lucas Hazel) Date: Tue, 24 Jun 2008 11:15:24 +1000 Subject: [crux-devel] nvidia port Message-ID: <20080624111524.1f92d75f@akira.digitilocal> I just realised I don't actually have a i686 machine with an nvidia card in it, so I won't be able to properly test it. Someone else will need to pick this one up. I'm happy to be an arch maintainer for 64bit though. -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Tue Jun 24 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Tue, 24 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4860b0e6.AusM3wqKCS+w38pO%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From lucas at die.net.au Tue Jun 24 11:05:14 2008 From: lucas at die.net.au (Lucas Hazel) Date: Tue, 24 Jun 2008 21:05:14 +1000 Subject: [crux-devel] More orphans Message-ID: <20080624210514.67ad0584@akira.digitilocal> Just found these orphaned ports in opt: $ grep "#.*Maintainer.*Matt Housh" */Pkgfile | cut -d/ -f1 avahi * desktop-file-utils * gnutls gob libdaemon mingetty * opencdk vpnc The ones with a * are ones I use, so I can adopt these. I also noticed that Tilman recently made a commit for avahi. Yet Matt is still marked at the maintainer... -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From lucas at die.net.au Tue Jun 24 12:07:38 2008 From: lucas at die.net.au (Lucas Hazel) Date: Tue, 24 Jun 2008 22:07:38 +1000 Subject: [crux-devel] More orphans In-Reply-To: <20080624210514.67ad0584@akira.digitilocal> References: <20080624210514.67ad0584@akira.digitilocal> Message-ID: <20080624220738.6af56e9d@akira.digitilocal> On Tue, 24 Jun 2008 21:05:14 +1000 Lucas Hazel wrote: > > Just found these orphaned ports in opt: > > $ grep "#.*Maintainer.*Matt Housh" */Pkgfile | cut -d/ -f1 > > avahi > * desktop-file-utils > * gnutls > gob > libdaemon > mingetty > * opencdk > vpnc > > The ones with a * are ones I use, so I can adopt these. > gnutls which had opencdk as a requirement no longer uses it as an external dependency, instead using internal sources only. gnutls was also the only port I could find that is dependent on opencdk. So, unless there are any objections, I'll delete the port from opt. -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Tue Jun 24 15:56:03 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Tue, 24 Jun 2008 17:56:03 +0200 Subject: [crux-devel] Reminder: casual IRC meeting Message-ID: <20080624155603.GA1336@selenium.smts.lan> Hi there, Just a quick reminder that we'll meet tonight for the casual IRC meeting. It'll start in a couple of minutes already, and I hope most of you who attend can stay for a while to allow for some overlap with our friends from other timezones. Time: 18:00 - 23:00 CEST (or as it fits you) Place: #crux-devel on freenode As mentioned in an earlier mail, this is a not a regular IRC meeting but more of a fixed time to meet and discuss random ideas which affect CRUX developers, so if you can't make it it's not a problem. As always, there's a chat log available on http://crux.morpheus.net/irc. Looking forward to seeing you guys tonight! Best wishes, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From jw at smts.ch Tue Jun 24 16:03:10 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Tue, 24 Jun 2008 18:03:10 +0200 Subject: [crux-devel] More orphans In-Reply-To: <20080624220738.6af56e9d@akira.digitilocal> References: <20080624210514.67ad0584@akira.digitilocal> <20080624220738.6af56e9d@akira.digitilocal> Message-ID: <20080624160310.GA2747@selenium.smts.lan> Hi Lucas, On Tue, Jun 24, 2008 at 22:07:38 +1000, Lucas Hazel wrote: > On Tue, 24 Jun 2008 21:05:14 +1000 > Lucas Hazel wrote: > > > > > Just found these orphaned ports in opt: [...] > > The ones with a * are ones I use, so I can adopt these. > > > > gnutls which had opencdk as a requirement no longer uses it as an > external dependency, instead using internal sources only. gnutls was > also the only port I could find that is dependent on opencdk. So, unless > there are any objections, I'll delete the port from opt. Thanks a lot for the investigation. Of course, if you can pick those up, it would be great. I agree with the deletions, unless someone speaks up and maintains them. Cheers, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From tilman at crux.nu Tue Jun 24 16:04:49 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Tue, 24 Jun 2008 18:04:49 +0200 Subject: [crux-devel] More orphans In-Reply-To: <20080624210514.67ad0584@akira.digitilocal> References: <20080624210514.67ad0584@akira.digitilocal> Message-ID: <20080624160449.GB1207@code-monkey.de> Lucas Hazel [2008-06-24 21:05]: Hi, > Just found these orphaned ports in opt: > > $ grep "#.*Maintainer.*Matt Housh" */Pkgfile | cut -d/ -f1 Thanks for bringing this up. We failed epically at handling this :( > avahi > * desktop-file-utils > * gnutls > gob > libdaemon > mingetty > * opencdk > vpnc > > The ones with a * are ones I use, so I can adopt these. Please go ahead. Since nobody did anything to these, it's safe to assume that noone will complain if they go away or whatever :D > I also noticed that Tilman recently made a commit for avahi. Yet Matt > is still marked at the maintainer... I just talked to Matt and asked whether he could maintain libdaemon and avahi in the Gnome repository. He agreed -- I think we can drop libdaemon and avahi from opt soon. I just removed mingetty as well. 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Wed Jun 25 07:43:40 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Wed, 25 Jun 2008 09:43:40 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 Message-ID: <20080625074340.GA22427@selenium.smts.lan> Hi there, Just a quick summary of yesterday's meeting: Tilman suggested to do a 2.5 release soonish, pushing new versions of glibc and gcc (and also perl IIRC); the gcc 4.3 update will introduce a couple of compile failures, many of them can easily be solved (we should probably prepare some notes with the typical errors). There are a couple of open tasks in Flyspray due to 2.5, we can probably talk about these some other time. We agreed that we want to move the daily source and ports checks to a dedicated mailing list; I'll look into that and follow up on this once it's done The "Public Wiki" was renamed to "Wiki". Next time, we can probably go through the content and move more stuff from the current homepage to the wiki area; for example we thought about only having "Handbook" and "Faq" in the navigation, and move the rest from "Documentation" Also, we've quickly talked about handling standard situations (new maintainer, maintainer leaving etc.), and to document the workflow better; as a short hand task, we want to introduce a script to change the maintainer field of a list of ports to a magic label, which can then be used to identify such ports easily, and to optinally remove them automatically if they've been unmaintained for a certain period of time. The script to do that should be fairly simple, if someone wants to look into that please let us know, otherwise we can revive our TaskList. We also went through the list of open bugs, talking mainly about some pkgutils bugs/requests. I had the feeling that the meeting was quite effective, especially since we also got some actual work done. I think that if we can do this on a regular base, we can avoid a backlog of changes and/or bug reports to answer, which is probably in the interest of everyone :-). That said, next meeting is tuesday next week. Hope to see you there. Regards, Johannes P.S. Sorry for the later reminder -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Wed Jun 25 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Wed, 25 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48620266.MHwy5Wlt7zuU/w2O%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From pitillo at ono.com Wed Jun 25 08:38:00 2008 From: pitillo at ono.com (Victor Martinez) Date: Wed, 25 Jun 2008 10:38:00 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 In-Reply-To: <20080625074340.GA22427@selenium.smts.lan> References: <20080625074340.GA22427@selenium.smts.lan> Message-ID: <20080625103800.55eba775.pitillo@ono.com> On Wed, 25 Jun 2008 09:43:40 +0200 Johannes Winkelmann wrote: > Hi there, > Hello Johannes, [...] > > That said, next meeting is tuesday next week. Hope to see you there. > Is there a way to put some points that will be talked in the next meeting? I think it can be a good idea to plan ourself to assist or not to the meeting. I mean for example the point about DE which was talked and can be very interesting to have some points before start the meeting (some kind of little organization). I think it can be usefull for example to DE maintainers and users. Another thing about points to be talked in the meeting can be a public area in the website to let maintainers/users to put there what they can find interesting to be talked (for example if someone is interested in 1 bug, he can put there a note to the bug, to let core members read about it and think before the meeting and use the meeting to share opinions, answers, problems, fixes, ...) Really, yesterday meeting was long and very usefull from my point of view. I hope I can follow next meetings from my other home (next week I start half work day and may be it will be hard to follow the next meeting on afternoons, but I will try to connect from some wifi point). Thank you all who were there and talked in the meeting, and of course, for your great work done and effort to be in the meeting and co-ordinate it. > Regards, Johannes > Regards, pitillo. -- Learning bit by bit. -pitillo- From jw at smts.ch Wed Jun 25 14:54:43 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Wed, 25 Jun 2008 16:54:43 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 In-Reply-To: <20080625103800.55eba775.pitillo@ono.com> References: <20080625074340.GA22427@selenium.smts.lan> <20080625103800.55eba775.pitillo@ono.com> Message-ID: <20080625145443.GA32019@selenium.smts.lan> Hi Victor, On Wed, Jun 25, 2008 at 10:38:00 +0200, Victor Martinez wrote: > On Wed, 25 Jun 2008 09:43:40 +0200 > Johannes Winkelmann wrote: > > > Hi there, > > > Hello Johannes, > > [...] > > > > That said, next meeting is tuesday next week. Hope to see you there. > > > Is there a way to put some points that will be talked in the next > meeting? I guess we'll always go through the active bug reports and discussions from the mailing lists, so whatever comes up there which is relevant to developers can come up in the IRC meeting. > I think it can be a good idea to plan ourself to assist or not > to the meeting. I mean for example the point about DE which was talked > and can be very interesting to have some points before start the > meeting (some kind of little organization). I agree. I'd even go further and say that such big things like the DE discussion (for those wondering: contrib ports depending on gnome/kde/xfce) should be discussed before, to avoid losing too much time during the meeting with single issues. For that, I guess it could make sense to have an agenda with two groups of items: 1. needs discussion 2. needs decision or implementation At the casual meetings, we would typically address items from group #2. Items of group #1 should typically be discussed on the mailing list. Once we have a clear picture about an issue, we can move it to group two. We could in addition have one meeting per month as a regular IRC meeting, where we discuss about group #1 stuff. Does that sounds right, or is it too complicated? Best wishes, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From tilman at crux.nu Wed Jun 25 15:30:36 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Wed, 25 Jun 2008 17:30:36 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 In-Reply-To: <20080625074340.GA22427@selenium.smts.lan> References: <20080625074340.GA22427@selenium.smts.lan> Message-ID: <20080625153036.GA1247@code-monkey.de> Johannes Winkelmann [2008-06-25 09:43]: > Tilman suggested to do a 2.5 release soonish, pushing new versions of > glibc and gcc (and also perl IIRC); the gcc 4.3 update will introduce a > couple of compile failures, many of them can easily be solved (we should > probably prepare some notes with the typical errors). There are a couple btw, while I havent hit this bug yet, we probably should wait for gcc 4.3.2 :) https://bugzilla.redhat.com/show_bug.cgi?id=451068 resp http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36533 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From pitillo at ono.com Wed Jun 25 15:34:16 2008 From: pitillo at ono.com (Victor Martinez) Date: Wed, 25 Jun 2008 17:34:16 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 In-Reply-To: <20080625145443.GA32019@selenium.smts.lan> References: <20080625074340.GA22427@selenium.smts.lan> <20080625103800.55eba775.pitillo@ono.com> <20080625145443.GA32019@selenium.smts.lan> Message-ID: <20080625173416.8e77dc69.pitillo@ono.com> On Wed, 25 Jun 2008 16:54:43 +0200 Johannes Winkelmann wrote: > Hi Victor, > > I guess we'll always go through the active bug reports and discussions > from the mailing lists, so whatever comes up there which is relevant to > developers can come up in the IRC meeting. > Well, yesterday you traveled over bug reports, but without a planning. I mean, you see an error and you talk about it (I don't mean this is a bad way to go trought them, because the meeting for me was productive, but may be can be interesting to fill the agenda of a meeting with interesting bugs that can affect directly to one person, in this way, someone can put one item in the agenda making a reference to a bug, which can be found interesting by him, and more if he will be in the meeting, of course it can be told in the meeting, but may be people didn't thought about it, and can be a bit fast). > I agree. I'd even go further and say that such big things like the DE > discussion (for those wondering: contrib ports depending on > gnome/kde/xfce) should be discussed before, to avoid losing too much > time during the meeting with single issues. > The DE discussion was only an example, but you took the point (discussed before the meeting to don't lose too much time, or at least, to prepare points of view about the big items). > For that, I guess it could make sense to have an agenda with two > groups of items: > 1. needs discussion > 2. needs decision or implementation > > At the casual meetings, we would typically address items from group #2. > Items of group #1 should typically be discussed on the mailing list. > Once we have a clear picture about an issue, we can move it to group > two. > This sounds great for me. This is some kind of organization to make meetings. Btw, I tried to explain here my thoughts to see if you found them interesting and helpfully to organize the meetings. May be, making this kind of meeting groups can make them harder. > We could in addition have one meeting per month as a regular IRC > meeting, where we discuss about group #1 stuff. > If you feel confortable with the aproach you have now, I mean, looking for items which have been discussed (or it will be) and implement them, I think it's enought. I like the idea of meetings to make a bridge between maintainers/core members/users and to take decisions which will affect all people using CRUX. But in fact, making too much meetings in a month, can be hard to people to follow them, this was my point about items to be talked, to let people organize theirselves. > Does that sounds right, or is it too complicated? I understood the point, but not sure if it can be good for all people to follow this pattern, may be sounds hard to follow instead of hard to understand. Thank you very much for reading these posts and sharing your opinion. > Best wishes, Johannes > Same from here, pitillo. -- Learning bit by bit. -pitillo- From fredrik at obra.se Wed Jun 25 17:28:50 2008 From: fredrik at obra.se (Fredrik Rinnestam) Date: Wed, 25 Jun 2008 19:28:50 +0200 Subject: [crux-devel] 64-bit test run In-Reply-To: <20080625172316.GA1525@code-monkey.de> References: <20080625172316.GA1525@code-monkey.de> Message-ID: <20080625172850.GA22803@zoidberg.obra.se> I could probably help out a bit with arch maintenance. All i need is an account :> /Fredrik ------ This email was spied upon by FRA - Sweden's own STASI. Enjoy! From crux at crux.nu Thu Jun 26 08:31:33 2008 From: crux at crux.nu (crux at crux.nu) Date: Thu, 26 Jun 2008 10:31:33 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <486353e5.UsoHBCLHi1MtOm3o%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From jue at jue.li Thu Jun 26 12:30:47 2008 From: jue at jue.li (Juergen Daubert) Date: Thu, 26 Jun 2008 14:30:47 +0200 Subject: [crux-devel] Specifying architecture in port In-Reply-To: <20080622234947.00f6b10e@akira.digitilocal> References: <20080622234947.00f6b10e@akira.digitilocal> Message-ID: <20080626123047.GA6186@jue.netz> On Sun, Jun 22, 2008 at 11:49:47PM +1000, Lucas Hazel wrote: > > I'm putting together some multilib ports in the style that has been > suggested for the upcoming 64 bit test run. An issue unique to > multilib, compared to pure 64 bit, is that two different sets of > libraries exist on the same system. This also means that there are a > different set of options required for each one to be used by pkgmk. > > http://git.die.net.au/cgit/crux/ports/core/tree/pkgutils/x86_64/pkgmk.conf?h=multiarch > > This is the solution Daniel came up with when he first released the > original CRUX64 several years ago. While not ideal, it's a necessary > evil when dealing with multilib. > > The issue is that pkgutils requires the port to identify itself as a > compat32 port. The method I'm using currently is to use a .arch file in > the port. Hmm, I don't understand that. The item 'port' is normaly used for the directory in which Pkgfile/.md5sum etc. are laying around. In both cases you need the port IMO, or do I miss something? > http://git.die.net.au/cgit/crux/tools/pkgutils/commit/?id=e31dab6d68b26811e92ae5c4646b9958cf76f22a > > This differs from Daniels original implementation which was to put it > into the Pkgfile using arch=compat32. However, I believe that keeping > it out of the Pkgfile is a much better solution. I'd not call the file .arch but find a better name that reflects more what it really does, pulling in different settings to build the port. It should be read after pkgmk.conf so it would be possible to alter other variables like MAKEFLAGS for example. One drawback of the .xxxx file approach is that a modification of pkgmk is required, but I tend to favor that solution. > Using such a method also has it's advantages in cross compiling for > people who want to build ports for alternative architectures that don't > have the resources to build natively, such as embedded platforms. > > I'm just wondering if anyone else had anything to contribute to the > idea, or alternative solutions before I go too far and have another set > of ports that isn't going to be incompatible with CRUX. Greetings Juergen -- Juergen Daubert | mailto:jue at jue.li Korb, Germany | http://jue.li/crux From tilman at crux.nu Thu Jun 26 15:24:19 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Thu, 26 Jun 2008 17:24:19 +0200 Subject: [crux-devel] More orphans In-Reply-To: <20080624210514.67ad0584@akira.digitilocal> References: <20080624210514.67ad0584@akira.digitilocal> Message-ID: <20080626152419.GB1206@code-monkey.de> Lucas Hazel [2008-06-24 21:05]: > > Just found these orphaned ports in opt: > > $ grep "#.*Maintainer.*Matt Housh" */Pkgfile | cut -d/ -f1 Updated: $ grep "#.*Maintainer.*Matt Housh" */Pkgfile | cut -d/ -f1 $ Hurray! So I think we just need to find a poor soul to take nvidia, right? Any volunteers? Please? 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From lucas at die.net.au Thu Jun 26 23:40:34 2008 From: lucas at die.net.au (Lucas Hazel) Date: Fri, 27 Jun 2008 09:40:34 +1000 Subject: [crux-devel] Specifying architecture in port In-Reply-To: <20080626123047.GA6186@jue.netz> References: <20080622234947.00f6b10e@akira.digitilocal> <20080626123047.GA6186@jue.netz> Message-ID: <20080627094034.1b577a49@akira.digitilocal> On Thu, 26 Jun 2008 14:30:47 +0200 Juergen Daubert wrote: > On Sun, Jun 22, 2008 at 11:49:47PM +1000, Lucas Hazel wrote: > > > > I'm putting together some multilib ports in the style that has been > > suggested for the upcoming 64 bit test run. An issue unique to > > multilib, compared to pure 64 bit, is that two different sets of > > libraries exist on the same system. This also means that there are a > > different set of options required for each one to be used by pkgmk. > > > > http://git.die.net.au/cgit/crux/ports/core/tree/pkgutils/x86_64/pkgmk.conf?h=multiarch > > > > This is the solution Daniel came up with when he first released the > > original CRUX64 several years ago. While not ideal, it's a necessary > > evil when dealing with multilib. > > > > The issue is that pkgutils requires the port to identify itself as a > > compat32 port. The method I'm using currently is to use a .arch > > file in the port. > > Hmm, I don't understand that. The item 'port' is normaly used for the > directory in which Pkgfile/.md5sum etc. are laying around. In both > cases you need the port IMO, or do I miss something? Possibly, in this implementation the .arch file is placed in the port structure along with .md5sum, .footprint, etc. The file simply contains a value for PKGMK_ARCH, which can be used by /etc/pkgmk.conf to change the environment for building that arch. > > http://git.die.net.au/cgit/crux/tools/pkgutils/commit/?id=e31dab6d68b26811e92ae5c4646b9958cf76f22a > > > > This differs from Daniels original implementation which was to put > > it into the Pkgfile using arch=compat32. However, I believe that > > keeping it out of the Pkgfile is a much better solution. > > I'd not call the file .arch but find a better name that reflects more > what it really does, pulling in different settings to build the port. > It should be read after pkgmk.conf so it would be possible to alter > other variables like MAKEFLAGS for example. > > One drawback of the .xxxx file approach is that a modification of > pkgmk is required, but I tend to favor that solution. Perhaps an alternative solution would be to have a .pkgmk.conf to allow the port to make extra changes that may be required, such as extra CFLAGS, MAKEFLAGS, and so on. For example, with compat32 stuff .pkgmk.conf could contain, . /etc/pkgmk-compat32.conf This would remove the need for PKGMK_ARCH and the case structure in my version of pkgmk.conf. This could also allow a number of x86_64 ports that for example, have to have -fPIC set in their CFLAGS to have the same build script as the offificial ones as in those ports as the extra CFLAGS could be set in .pkgmk.conf rather than in build(). -- Lucas Hazel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From crux at crux.nu Fri Jun 27 08:24:21 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 27 Jun 2008 10:24:21 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4864a3b5.2nFB9NW2zTFOjOW+%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/libjpeg Url: ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/psutils Url: ftp://ftp.enst.fr/pub/unix/a2ps/psutils-1.17.tar.gz Reason: curl: (67) Access denied: 530 State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/spamprobe Url: http://dl.sourceforge.net/sourceforge/spamprobe/spamprobe-1.4d.tar.gz Reason: curl: (52) Empty reply from server State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Fri Jun 27 08:31:36 2008 From: crux at crux.nu (crux at crux.nu) Date: Fri, 27 Jun 2008 10:31:36 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4864a568.KLVOrBLyQl7UJFrc%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Sat Jun 28 08:26:44 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 28 Jun 2008 10:26:44 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <4865f5c4.0VVoxkk4XVwEWtDd%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/core/zlib Url: http://www.zlib.net/zlib-1.2.3.tar.bz2 Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/a2ps Url: http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/distfiles/a2ps-4.13c.tar.gz Reason: curl: (7) couldn't connect to host State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/ant Url: http://mirrors.publicshout.org/apache/ant/binaries/apache-ant-1.7.0-bin.tar.bz2 Reason: curl: (7) couldn't connect to host State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Sat Jun 28 08:31:34 2008 From: crux at crux.nu (crux at crux.nu) Date: Sat, 28 Jun 2008 10:31:34 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <4865f6e6.fyFmc0MlDTjfPhix%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From crux at crux.nu Sun Jun 29 08:31:35 2008 From: crux at crux.nu (crux at crux.nu) Date: Sun, 29 Jun 2008 10:31:35 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <48674867.F13IgNHRR0BwneaH%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From tilman at crux.nu Sun Jun 29 15:37:21 2008 From: tilman at crux.nu (Tilman Sauerbeck) Date: Sun, 29 Jun 2008 17:37:21 +0200 Subject: [crux-devel] Specifying architecture in port In-Reply-To: <20080627094034.1b577a49@akira.digitilocal> References: <20080622234947.00f6b10e@akira.digitilocal> <20080626123047.GA6186@jue.netz> <20080627094034.1b577a49@akira.digitilocal> Message-ID: <20080629153706.GA19189@code-monkey.de> Lucas Hazel [2008-06-27 09:40]: > On Thu, 26 Jun 2008 14:30:47 +0200 > Juergen Daubert wrote: > > [...] > > I'd not call the file .arch but find a better name that reflects more > > what it really does, pulling in different settings to build the port. > > It should be read after pkgmk.conf so it would be possible to alter > > other variables like MAKEFLAGS for example. > > > > One drawback of the .xxxx file approach is that a modification of > > pkgmk is required, but I tend to favor that solution. > > Perhaps an alternative solution would be to have a .pkgmk.conf to allow > the port to make extra changes that may be required, such as extra > CFLAGS, MAKEFLAGS, and so on. For example, with compat32 > stuff .pkgmk.conf could contain, > > . /etc/pkgmk-compat32.conf > > This would remove the need for PKGMK_ARCH and the case structure in my > version of pkgmk.conf. > > This could also allow a number of x86_64 ports that for example, have to > have -fPIC set in their CFLAGS to have the same build script as the > offificial ones as in those ports as the extra CFLAGS could be set > in .pkgmk.conf rather than in build(). I prefer .arch. Looks like the least intrusive approach to me. So, I'm ACKing the patches you linked to in your original mail. 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? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From jw at smts.ch Mon Jun 30 08:20:17 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Mon, 30 Jun 2008 10:20:17 +0200 Subject: [crux-devel] Specifying architecture in port In-Reply-To: <20080629153706.GA19189@code-monkey.de> References: <20080622234947.00f6b10e@akira.digitilocal> <20080626123047.GA6186@jue.netz> <20080627094034.1b577a49@akira.digitilocal> <20080629153706.GA19189@code-monkey.de> Message-ID: <20080630082017.GA21152@selenium.smts.lan> Hi there, On Sun, Jun 29, 2008 at 17:37:21 +0200, Tilman Sauerbeck wrote: > Lucas Hazel [2008-06-27 09:40]: > > On Thu, 26 Jun 2008 14:30:47 +0200 > > Juergen Daubert wrote: > > > > [...] > > > I'd not call the file .arch but find a better name that reflects more > > > what it really does, pulling in different settings to build the port. > > > It should be read after pkgmk.conf so it would be possible to alter > > > other variables like MAKEFLAGS for example. > > > > > > One drawback of the .xxxx file approach is that a modification of > > > pkgmk is required, but I tend to favor that solution. > > > > Perhaps an alternative solution would be to have a .pkgmk.conf to allow > > the port to make extra changes that may be required, such as extra > > CFLAGS, MAKEFLAGS, and so on. For example, with compat32 > > stuff .pkgmk.conf could contain, > > > > . /etc/pkgmk-compat32.conf > > > > This would remove the need for PKGMK_ARCH and the case structure in my > > version of pkgmk.conf. > > > > This could also allow a number of x86_64 ports that for example, have to > > have -fPIC set in their CFLAGS to have the same build script as the > > offificial ones as in those ports as the extra CFLAGS could be set > > in .pkgmk.conf rather than in build(). > > I prefer .arch. Looks like the least intrusive approach to me. > So, I'm ACKing the patches you linked to in your original mail. Somehow, .arch seems somewhat easy to overlook, and since some code within build() might actually be arch specific I wouldn't mind having an arch= variable inside Pkgfile. However, since Pkgfiles are potentially the same for all platforms, .arch sounds like a good way to simplify merging. The only thing I was wondering was whether PKGMK_ARCHFILE should be sourced, and look something like this: # Maintainer: PKGMK_ARCH=x86_64 This way, we'd also have the arch maintainer listed. Maybe we can discuss the .arch format tommorrow at the meeting, but in either case I have no objections against merging it. Cheers, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From crux at crux.nu Mon Jun 30 08:24:25 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 30 Jun 2008 10:24:25 +0200 Subject: [crux-devel] Potentially broken source downloads Message-ID: <48689839.eKl4/VHCpdPp9IiF%crux@crux.nu> Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/cryptsetup Url: http://luks.endorphin.org/source/cryptsetup-1.0.6.tar.bz2 Reason: curl: (6) Couldn't resolve host 'luks.endorphin.org' State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/imagemagick Url: ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick-6.3.9-0.tar.bz2 Reason: curl: (19) Given file does not exist State: Reminder Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/lsof Url: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.80.tar.bz2 Reason: curl: (8) This doesn't seem like a nice ftp-server response State: New Port: /home/crux/git-to-rsync-working-copy/crux-2.4/opt/splint Url: http://www.splint.org/downloads/splint-3.1.2.src.tgz Reason: curl: (6) Couldn't resolve host 'www.splint.org' State: New Full report: http://crux.nu/files/check_urls.html From crux at crux.nu Mon Jun 30 08:31:37 2008 From: crux at crux.nu (crux at crux.nu) Date: Mon, 30 Jun 2008 10:31:37 +0200 Subject: [crux-devel] prtverify daily results Message-ID: <486899e9.SIja6hCSGULNqorc%crux@crux.nu> Differences since last check: (no differences) Full report: http://crux.nu/files/prtverify.log From jw at smts.ch Mon Jun 30 08:38:18 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Mon, 30 Jun 2008 10:38:18 +0200 Subject: [crux-devel] Meeting notes 2008-06-24 In-Reply-To: <20080625145443.GA32019@selenium.smts.lan> References: <20080625074340.GA22427@selenium.smts.lan> <20080625103800.55eba775.pitillo@ono.com> <20080625145443.GA32019@selenium.smts.lan> Message-ID: <20080630083818.GB21152@selenium.smts.lan> On Wed, Jun 25, 2008 at 16:54:43 +0200, Johannes Winkelmann wrote: [...] > I agree. I'd even go further and say that such big things like the DE > discussion (for those wondering: contrib ports depending on > gnome/kde/xfce) should be discussed before, to avoid losing too much > time during the meeting with single issues. > > For that, I guess it could make sense to have an agenda with two > groups of items: > 1. needs discussion > 2. needs decision or implementation Tilman has created a wiki page for this: http://crux.nu/Wiki/MeetingAgenda Feel free to add items which you think are ready to discussed at IRC meetings. As a rule of thumb, I think any topic which is sufficiently explained with a single link ( mailing list thread or bug report) or a single sentence could make it there. Regards, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch From jw at smts.ch Mon Jun 30 10:15:47 2008 From: jw at smts.ch (Johannes Winkelmann) Date: Mon, 30 Jun 2008 12:15:47 +0200 Subject: [crux-devel] Maintainer line replacement script / Port removal policy Message-ID: <20080630101547.GA9651@selenium.smts.lan> Hi there, I've started a script to replace maintainer lines with "unmaintained". This is mainly meant to mark ports as unmaintained when a maintainer leaves, however we could also automate the port removal and use it for regular port removal as well, such that a developer never manually removes a port, but just marks it as unmaintained, and some script which runs once per day picks them up, sends out a reminder after ~20 days (optionally with a special warning to maintainers of dependent ports), and removes it after 30 days (number of days chosen randomly). This would give other maintainers and users some time to pick a port up. The questions remains who should do security updates to these packages in the days before it's unmaintained. The script is here: http://jw.smts.ch/files/crux/set_unmaint Currently, it does not replace the maintainer but just prints an updated version (add -i to sed line to change this), and it's meant to be run like this: $ set_unmaint ~/crux/ports/core prt-get httpup ... Opinions, patches? Cheers, Johannes -- Johannes Winkelmann mailto:jw at smts.ch Zurich, Switzerland http://jw.smts.ch