T2 IRC Log: 2009-03-30

This is the log as captured by an IRC bot in the channel. The statements are those of the individual people and might not neccessarily reflect the policy and legal rules as set forth by the T2 SDE Project.

« prev | next »

--- Log opened Mon Mar 30 00:00:13 2009
01:56 -!- the_rainbow [i=ee@41.209.167.150] has quit [Read error: 110 (Connection timed out)]
02:04 -!- synchris_odium is now known as synchris
03:29 -!- fnordianslipeee [n=darren@78.33.82.89] has quit [Read error: 110 (Connection timed out)]
09:49 [Users #t2]
09:49 [@ChanServ] [ EnTeQuAk] [ mqueiros] [ Skaperen] [ tfl0pz]
09:49 [ CIA-41 ] [ koan ] [ mtr ] [ Stealth ] [ TobiX ]
09:49 [ dsoul ] [ LMJ ] [ rxr ] [ synchris] [ zod ]
09:49 -!- Irssi: #t2: Total of 15 nicks [1 ops, 0 halfops, 0 voices, 14 normal]
10:23 -!- tfl0pz [n=tfl0pz@mail.constalant.com] has quit ["Leaving"]
10:25 < CIA-41> rene * r32763 /trunk/package/network/iproute2/iproute2.desc: * updated iproute2 (2.6.28 -> 2.6.29-1)
10:25 < CIA-41> rene * r32764 /trunk/package/perl/perl-cairo/perl-cairo.desc: * updated perl-cairo (1.060 -> 1.061)
10:25 < CIA-41> rene * r32765 /trunk/package/perl/perl-anyevent/perl-anyevent.desc: * updated perl-anyevent (4.34 -> 4.35)
10:49 < CIA-41> rene * r32766 /trunk/package/network/wpa_supplicant/wpa_supplicant.desc: * updated wpa_supplicant (0.6.8 -> 0.6.9)
10:49 < CIA-41> rene * r32767 /trunk/package/network/iptables/iptables.desc: * updated iptables (1.4.3 -> 1.4.3.1)
10:49 < CIA-41> rene * r32768 /trunk/package/contrib/watchdog/watchdog.desc: * updated watchdog (5.4 -> 5.6)
10:50 < CIA-41> rene * r32769 /trunk/package/audio/liblo/liblo.desc: * updated liblo (0.24 -> 0.26)
10:50 < CIA-41> rene * r32770 /trunk/package/network/wireshark/wireshark.desc: * updated wireshark (1.0.6 -> 1.1.3)
10:50 < CIA-41> rene * r32771 /trunk/package/graphic/gnofract4d/gnofract4d.desc: * updated gnofract4d (3.10 -> 3.11)
10:51 < CIA-41> rene * r32772 /trunk/package/network/wput/wput.desc: * updated wput (0.6.1 -> 0.6.2)
10:51 < CIA-41> rene * r32773 /trunk/package/security/libfwbuilder/libfwbuilder.desc: * updated libfwbuilder (3.0.3 -> 3.0.4)
10:51 < CIA-41> rene * r32775 /trunk/package/emulators/wine/wine.desc: * updated wine (1.1.16 -> 1.1.18)
10:51 < CIA-41> rene * r32774 /trunk/package/network/phpldapadmin/phpldapadmin.desc: * updated phpldapadmin (1.1.0.6 -> 1.1.0.7)
11:27 -!- mpp [n=mpp@fulda025.server4you.de] has joined #t2
11:30 -!- fnordianslipeee [n=darren@78.33.82.89] has joined #t2
11:41 < mpp> moinsen
13:49 -!- the_rainbow [i=ee@41.209.167.147] has joined #t2
13:49 < the_rainbow> Hello everybody
13:50 < the_rainbow> I'm new in T2, I followord the t2-handbook instructions to create an ISO live CD, it created it, but when I boot, grub doesn't load the squash fs, it just prompts
13:50 < the_rainbow> Any hints would be appreciated ;)
14:04 < rxr> grub?
14:04 < rxr> did you use trunk or the stable 7.0 ?
14:12 < rxr> the_rainbow: sorry for any delay I'm pretty busy at work these days so replies can take some time
14:12 < rxr> the_rainbow: best always ask the mailing list for other to have a chance to reply, too
14:14 < the_rainbow> I'm using the 7.0 stable branch
14:14 < the_rainbow> and it seems I'm in trouble
14:15 < the_rainbow> I'm posting on the mailing list as well
14:16 < rxr> 7.0 should work quite good
14:16 < rxr> what is the grub error? grub should not load a squashfs
14:16 < rxr> maybe the kernel was already booted?
14:19 < the_rainbow> I just posted my problem in the mailing list: http://www.nabble.com/Problem-with-the-generated-livecd-td22781993.html
14:19 < the_rainbow> but, there's no vmlinuz nor initrd in the /boot directory
14:23 < rxr> did the target build without an error ?
14:25 < the_rainbow> when I run the Create-ISO script, it tells me
14:25 < the_rainbow> "unexpected joliet directory length 380 expected 384 ''
14:25 < the_rainbow> Done. Have fun !
14:25 < the_rainbow> but the iso is generated
14:25 < rxr> I mean the Built-Target
14:25 < the_rainbow> yes I think it was fine
14:25 < the_rainbow> I let it builiding for many hours
14:26 < the_rainbow> I didn't check what it was doing every minute
14:26 < the_rainbow> but at the end, it didn't report any error
14:26 < rxr> ./scripts/Create-ErrList
14:26 < rxr> add -cfg your-config if you used a config name
14:26 < the_rainbow> okay, I'm gonna check
14:28 < the_rainbow> 153 builds total, 245 completed fine, 208 with errors, 0 to go
14:28 < the_rainbow> 453 builds total*
14:28 < rxr> 208 with errors => thats' not good
14:29 < the_rainbow> hum
14:29 < the_rainbow> what am I supposed to do to get them build right?
14:29 < the_rainbow> I didn't touch anything
14:29 < the_rainbow> and I thought t2 builds packages without problems
14:29 < rxr> depends
14:30 < rxr> with an unstable system unstable internet connection etc. pp. there might be build errors
14:30 < koan> the_rainbow: this is probably some basis component which is failing, with the other packages failing as a result
14:31 -!- the_rainbow [i=ee@41.209.167.147] has quit [Read error: 104 (Connection reset by peer)]
14:32 -!- the_rainbow [i=ee@41.209.167.147] has joined #t2
14:32 < the_rainbow> ah okay, so I have to debug that myself
14:32 < the_rainbow> another thing, why there are some outdted packages like the linux kernel (2.6.19)
14:33 < the_rainbow> ?
14:33 < rxr> 7.0 should be newer
14:33 < rxr> was'nt it 2.6.21 ?
14:33 < rxr> maybe the header where at 2.6.19 but they are used to define a stable api
14:34 < rxr> major updates are on trunk
14:34 < rxr> if we would update the stable tree to every random new kernel it would break weekly on half of the systems
14:39 < the_rainbow> ahh okay I see
14:39 < the_rainbow> I'm gonna try to debug the failed builds, I hope it won't be very tough
14:40 < the_rainbow> actually, I'm building server distribution based on T2
14:41 < the_rainbow> T2 is a great work ! Nice work guys
14:43 < the_rainbow> but tell me, T2 autodetect dependencies based on what? I find this feature magical actually
14:48 < rxr> based on files (includes libs) read and the installed files of all packages
14:48 -!- T-One [n=T-One@62.218.122.66] has joined #t2
14:48 < rxr> but the deps are not yet used to magially builde the "designer" in the Config phase
15:06 < the_rainbow> thanks for the clarification man
15:49 < the_rainbow> By the way, is it easy for me to include the latest kernel version?
15:51 < rxr> other third party kernel modules will not build and might be major pain to update, too
15:52 < rxr> if you desperately want the latest greated kernel I suggest you use trunk
15:53 < the_rainbow> hum, it seems I'm going to use the trunk
15:53 < rxr> on trunk we updated to 2.6.29 some days ago
15:54 < rxr> though we're still wait'ng for the squashfs-tools and unionfs update etc.
15:54 < rxr> but the kernel as it builds ._9
15:54 < rxr> :-) even
15:56 < the_rainbow> but I don't understand, what's the relation between the kernel and the other packages?
15:57 -!- synchris_odium [n=synchris@athedsl-201369.home.otenet.gr] has joined #t2
15:57 < the_rainbow> the kernel can simply be compiled and run, I don't understand this stoy of stability and instability
15:57 < rxr> other packages like wifi driver, kqemu and unionfs (and squashfs in the past)
15:57 < rxr> they include kernel code that is sometims patches into the kernel and sometimes build as module
15:57 < rxr> due to no stable API in the ever changing Linux kernel busines they often break on every kernel update
15:58 < rxr> we even have some "not in mainstream" ethernet driver
15:58 < rxr> and in the past (7.0) the web-cam driver gspac etc. pp.
16:03 < the_rainbow> ah okay I see
16:03 < the_rainbow> I'm just building a minumal distro and I don't need madwifi or such driver packages, so I can use the trunk without problem right?
16:03 < rxr> hopefully
16:08 < the_rainbow> cool
16:12 -!- synchris [n=synchris@pdpc/supporter/professional/synchris] has quit [Read error: 110 (Connection timed out)]
17:55 -!- Stealth [i=stealth@sourcemage/guru/stealth] has quit [Remote closed the connection]
17:56 -!- Stealth [i=stealth@sourcemage/guru/stealth] has joined #t2
18:35 -!- mpp [n=mpp@fulda025.server4you.de] has quit ["ChatZilla 0.9.84 [Firefox 3.0.5/2008120121]"]
18:53 -!- the_rainbow [i=ee@41.209.167.147] has quit [Read error: 104 (Connection reset by peer)]
18:53 -!- the_rainbow [n=ee@41.209.167.147] has joined #t2
21:10 -!- the_rainbow [n=ee@41.209.167.147] has quit [Read error: 104 (Connection reset by peer)]
21:15 -!- Netsplit kornbluth.freenode.net <-> irc.freenode.net quits: koan, TobiX, Skaperen
21:16 -!- Netsplit over, joins: koan, Skaperen, TobiX
21:44 -!- whorrel [n=whorrel@122.173.27.235] has joined #t2
21:56 -!- digitaloktay [n=debian@dslb-084-057-236-239.pools.arcor-ip.net] has joined #t2
22:10 -!- whorrel [n=whorrel@122.173.27.235] has quit ["ircII EPIC4-2.0 Plan9 4 -- Are we there yet?"]
--- Log closed Tue Mar 31 00:00:13 2009