**** BEGIN LOGGING AT Sun Apr 01 02:59:57 2007 Apr 01 06:05:58 hi Apr 01 06:06:16 i got a new error during the do_rootfs Apr 01 06:07:28 Cannot find package ixp-eth. Apr 01 06:07:34 and a lot of packages Apr 01 08:52:03 03oleo * r5862 10optware/trunk/platforms/packages-ddwrt.mk: optware: promote dansguardian, iperf and ggrab for uclibc Apr 01 08:52:57 03oleo * r5863 10optware/trunk/platforms/packages-oleg.mk: optware: promote dansguardian, iperf and ggrab for uclibc Apr 01 08:57:04 eno. As it seems that there will not be unstable feed, I am planning to merge unstable branch back to trunk. Apr 01 08:58:49 rwhitby and eno : This upgrade from 0.9.28 to 0.9.28.3 affects many packages. The easiest way is to rebuild whole repository from scratch. Apr 01 08:59:05 When can we do this? Apr 01 08:59:56 how is it that a change in the *fourth* part of a version number (0.9.28 to 0.9.28.3) can affect many packages? Apr 01 09:00:26 * rwhitby doesn't see why people don't just stop after the first decimal point ... Apr 01 09:01:57 This means that for example /opt/bin/ls from coreutils gives strange output. Apr 01 09:02:32 what are the uclibc people *doing* if a change in the fourth part of a version number has that effect? Apr 01 09:03:22 People just give ipkg install -force-reinstall coreutils for example Apr 01 09:04:45 or simple oneliner for all packages as usr/bin/awk '/^Package:/{system("/opt/bin/ipkg install -force-reinstall -force-defaults " $2)}' /opt/lib/ipkg/status Apr 01 09:05:12 as it is written http://www.nslu2-linux.org/wiki/FAQ/Optware-uClibcBuild Apr 01 09:22:23 Why *fourth* part? Maybe because uClibc folks are heading to 0.9.29 and wanted to have some prerelease. Anyway it looks like changes worthwile. Note that uClibc does not guarantee binary compatibility between releases. See http://www.uclibc.org/downloads/Glibc_vs_uClibc_Differences.txt paragraph 3) Apr 01 09:30:59 well, if a change in the fourth part of a version number requires a feed rebuild, then we need to structure the uclibc feeds differently. Apr 01 09:32:47 our feeds are currently structured such that there is a stable feed that corresponds to each binary firmware release, and an unstable feed which tracks HEAD. We only ever deliver images which point to stable feeds. Optware has only had a single feed so far (unstable symlinked to stable) cause it was originally structured for nslu2 firmware (which has never changed library version) Apr 01 09:33:53 so before we rebuild this feed, I'd like to see a proposal of how to structure the optware uclibc feed that will work for many uclibc versions into the future (i.e. 0.9.29.3.58.23.45 ...) Apr 01 09:39:51 we could do similar as what OpenWrt is doing. They name package feeds with rc6 for example. We could do this like r12 for old and r13 subdirs for new Apr 01 09:40:26 eg. http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/r13 Apr 01 09:40:51 instead of dangling stable/unstable Apr 01 09:41:41 r13 meand ipkg feend number equal to toolchain feed. Apr 01 09:50:25 let's see what eno says to that, since he will be the one supporting it. Apr 01 09:51:38 OK. Thanks. I am in no hurry. But want to close unstable as I've put some effort in it. Apr 01 09:58:12 I will put this conversation into ticket. Apr 01 10:03:28 #8 Apr 01 10:27:55 oleo: don't worry - we will definitely add the new unstable - we just need to manage it so we don't need a rebuild in the future (i.e. use separate feeds) Apr 01 14:30:53 Suggested way to upgrade uClibc added to ticket #8 Apr 01 16:07:49 morning Apr 01 16:12:06 oleo: see if i understand your proposal correctly, you suggest Apr 01 16:12:54 create a tag corresponding to 0.9.28 as release Apr 01 16:13:49 merge your 0.9.28.3 changes back to trunk Apr 01 16:14:48 to have seperate feeds, one for release, one for HEAD Apr 01 16:17:50 i like the release vs trunk idea, but don't like the fact that stable==release and unstable==trunk Apr 01 16:23:22 in debian or freebsd, unstable packages usually can run on stable Apr 01 16:23:29 but this is not the case here Apr 01 16:34:56 03bzhou * r5864 10optware/trunk/make/varnish.mk: added varnish Apr 01 16:35:16 hi Apr 01 16:35:41 do you know how can I pipe the output of two scripts into one file? Apr 01 16:36:14 the scripts are startet with 'script1 && script2' Apr 01 16:37:14 Cheef-Daniel: use ">>" for the second script? Apr 01 16:37:19 script1 &> file.txt is working, but when they are joined together with && its not working any more ('script1 && script2 &> file.txt') Apr 01 16:37:39 morning, blaster8 Apr 01 16:37:47 hey there Apr 01 16:38:03 I use script1 && script2 &> file.txt, but I think theres something wrong with it Apr 01 16:38:57 Cheef-Daniel: try (script1 && script2) > file.txt Apr 01 16:41:48 thanks, that works Apr 01 16:45:24 this appends the ouput of all returned output to the file, right?: script1 &>> file.txt Apr 01 16:45:57 Cheef-Daniel: your question is more on topic at #bash Apr 01 16:46:37 Cheef-Daniel: script1 > file.txt && script2 >> file.txt Apr 01 16:46:38 yes, i'd think so, although i usually use '>> file.txt 2>&1' Apr 01 16:49:49 ok, thank you again ^^, I will switch the channel now, because I have no the right terms to look for Apr 01 18:12:22 03bzhou * r5865 10optware/trunk/ (Makefile make/haproxy.mk): added and promoted haproxy Apr 01 18:30:29 03bzhou * r5866 10optware/trunk/platforms/ (packages-ddwrt.mk packages-oleg.mk): demoted dansguardian on ddwrt and oleg Apr 01 19:05:41 03bzhou * r5867 10optware/trunk/ (4 files in 2 dirs): added and promoted: perl-bsd-resource, perl-danga-socket, perl-sys-syscall Apr 01 19:29:08 eno: we could drop stable/unstable and go just for release and trunk or head instead Apr 01 19:29:26 oleo: agreed Apr 01 19:30:30 * eno heading out, bbl Apr 01 19:30:48 OK. could sleep over too. Apr 01 20:44:27 03oleo * r5868 10optware/ (2 files in 2 dirs): libupnp: 1.4.1->1.4.3 - update to template Apr 01 20:46:38 03oleo * r5869 10optware/ (4 files in 4 dirs): ushare: 0.9.8->0.9.10 Apr 01 20:49:37 03oleo * r5870 10optware/ (2 files in 2 dirs): firmware-oleg: enamle ext2 filesystem Apr 01 21:26:47 hi Apr 01 22:06:07 03oleo * r5871 10optware/ (4 files in 4 dirs): davtools: Disk Allocation Viewer added Apr 01 22:52:51 03bzhou * r5872 10optware/trunk/ (Makefile make/perlbal.mk): added and promoted perlbal Apr 01 23:45:30 03bzhou * r5873 10optware/trunk/ (make/ushare.mk platforms/packages-ts101.mk): ushare: stage, link, & depend on libiconv if standalone libiconv; promoted for ts101 Apr 02 01:17:23 03bzhou * r5874 10optware/trunk/Makefile: varnish: ready for testing Apr 02 02:40:03 03bzhou * r5875 10optware/trunk/ (8 files in 2 dirs): varnish: promoted on ds101, ds101g, ddwrt, oleg & slugosbe **** ENDING LOGGING AT Mon Apr 02 02:59:56 2007