--- Log opened Mon Sep 13 00:00:49 2010
01:01 -!- old_gaffer [~quassel@211.238.240.87] has joined #t2
07:16 -!- orici [~quassel@2001:470:9a41:107:20c:29ff:fea4:8189] has quit [Read error: Operation timed out]
08:09 -!- keinek [~leonel@host17.190-136-29.telecom.net.ar] has quit [Ping timeout: 240 seconds]
08:18 -!- keinek [~leonel@host16.190-136-29.telecom.net.ar] has joined #t2
08:55 <@rxr> re
09:35 < CIA-32> rene * r37606 /trunk/package/multimedia/lives/lives.desc: * updated lives (1.3.5 -> 1.3.6)
09:35 < CIA-32> rene * r37607 /trunk/package/network/wpa_supplicant/wpa_supplicant.desc: * updated wpa_supplicant (0.7.2 -> 0.7.3)
09:35 < CIA-32> rene * r37605 /trunk/package/network/bluez/bluez.desc: * updated bluez (4.70 -> 4.71)
09:35 < CIA-32> rene * r37608 /trunk/package/network/proftpd/proftpd.desc: * updated proftpd (1.3.3a -> 1.3.3b)
09:36 < CIA-32> rene * r37609 /trunk/package/graphic/poppler/poppler.desc: * updated poppler (0.14.2 -> 0.14.3)
09:36 < CIA-32> rene * r37610 /trunk/package/network/obexd/obexd.desc: * updated obexd (0.32 -> 0.33)
09:36 < CIA-32> rene * r37611 /trunk/package/xorg/xf86-video-glint/xf86-video-glint.desc: * updated xf86-video-glint (1.2.4 -> 1.2.5)
09:37 < CIA-32> rene * r37612 /trunk/package/perl/perl-devel-stacktrace/perl-devel-stacktrace.desc: * updated perl-devel-stacktrace (1.24 -> 1.25)
09:37 < CIA-32> rene * r37613 /trunk/package/archiver/alien/alien.desc: * updated alien (8.82 -> 8.83)
09:47 < CIA-32> rene * r37614 /trunk/package/network/hostapd/ (hostapd.desc prefix.patch): * updated hostapd (0.7.2 -> 0.7.3)
09:52 < CIA-32> rene * r37615 /trunk/package/network/bip/bip.desc: * updated bip (0.8.5 -> 0.8.6)
09:53 <@rxr> http://t2-project.org/packages/memtest86.html
11:21 -!- orici [~quassel@2001:470:9a41:107:20c:29ff:fea4:8189] has joined #t2
12:04 -!- mjungwirth2 [~mjungwirt@213.174.252.112] has joined #t2
12:04 -!- mjungwirth2 [~mjungwirt@213.174.252.112] has quit [Client Quit]
13:06 -!- mjungwirth [~mjungwirt@213.174.234.68] has quit [Quit: Nettalk6 - www.ntalk.de]
14:23 < rogermason> hello.
14:24 < rogermason> I want to create an ISO but I get the message: Chunk /root/t2-trunk/build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/pkgs/texlive-2009.tar.bz2 is too big!
14:25 <@rxr> guess it does not fit on your image size
14:25 <@rxr> the default is some 80m CD, you can specfiy the maximal size to Create-ISO
14:25 <@rxr> guess -size 1024 # whatever MB
14:31 < rogermason> Ah. The bz2 is 984 MB so I uses -size 984*1024 and that seems to work.
14:32 < rogermason> By the way, I created an account for myself on Wikipedia yesterday so I can contribute to a new T2 entry.
14:34 <@rxr> that would be much welcome
14:34 <@rxr> guess one has to speak with them in the talk page or so to ensure they do not just delete it again :-(((
14:44 < rogermason> I plan to write off-line initially. I'm trying to get haskell-platform installed so I can install pandoc. That will allow me to write in markdown syntax (or in LaTeX) and convert to MediaWiki.
15:34 -!- mqueiros_ [~mqueiros@a83-132-38-229.cpe.netcabo.pt] has joined #t2
15:35 -!- keinek [~leonel@host16.190-136-29.telecom.net.ar] has quit [Ping timeout: 245 seconds]
16:39 < rogermason> Hello again.
16:42 < rogermason> I have a problem with pam. I just made an iso from trunk. Before creating it I checked that the pam libraries present in build/.../lib. However, when i run stone on a new machine and select "(Re-) start sshd the file libpam.so cannot be found.
16:43 <@rxr> hm
16:43 <@rxr> does everything else work?
16:43 < rogermason> you meaneverything else in stone?
16:43 <@rxr> yes, and reboot, login etc.?
16:44 < rogermason> reboot works but I can't login because libpam_misc.so can't be found.
16:45 <@rxr> hm
16:45 <@rxr> I hope it is not a regression due the latest pam update :-(
16:45 <@rxr> I guess you did a full native build?
16:46 < rogermason> I've been building up this build over some time by using -job-5
16:50 <@rxr> that usually is fine
16:51 <@rxr> did you alter the package selection in the stone installer?
16:51 < rogermason> no
16:51 <@rxr> was pam installed?
16:51 <@rxr> can you check the flist of your pam package wether it includes the missing pam lib ?
16:53 < rogermason> various libpam*.so exist in build/.../lib/
16:53 <@rxr> if there was some issue with the flist tracker, the files might be there but not accounted in the flist
16:54 <@rxr> can you check build/.../var/adm/flists/pam?
16:54 < rogermason> yes, the files are in flists/pam
16:54 <@rxr> hm
16:55 <@rxr> can you check manually if they are also on your freshly isntalled HD in the installer environment, the HD is mounted to /mnt/target
16:55 < rogermason> is pam enabled by default in the minimal-with-x target?
16:55 < rogermason> no the files aren't on the new installs HD.
16:55 <@rxr> IIRC pam is even the default in the pure minimal target
16:56 <@rxr> hm, maybe they where not enabled in the installer package sleection?
16:56 <@rxr> maybe you did not choose the "install all packages", but install "minimal selection" ?
16:57 < rogermason> no I did install all
16:58 < rogermason> After an initial failure with this problem I built pam using -job-5. However, I wonder if I then forgot to re-create the iso.
16:59 < rogermason> checking...
17:01 < rogermason> well, the iso contains a package pam-0.99.9.0.tar.bz2 and a package pam-1.1.2.tar.bz2. The last is probably the version I built using -job-5
17:01 <@rxr> maybe the index file does not include it
17:01 <@rxr> IIRC the index file is only bulit at the end of Bulid-Target without a manual -job specification
17:02 < rogermason> the index only includes pam-0.99.9.0
17:03 <@rxr> then it is probably an old index I would guess
17:03 < rogermason> so I must run Build-Target?
17:10 <@rxr> when you manually build single jobs via Build-Target -job then yes, to let the post build generation, like the index being run
17:13 < rogermason> Running it now. Quite a lot of stuff is being (re)built. Guess they are updates.
17:16 <@rxr> Build-Target will not rebuild
17:16 <@rxr> it will only build what is selected in the config and was not yet built
17:18 < rogermason> hmm. How is "not yet built" determined? I'm sure I built fwbuilder, for example, but it got built just a few moments ago.
17:20 <@rxr> by the log files in build/var/adm/logs/
17:21 <@rxr> you did use the same -cfg config ?
17:23 < rogermason> yes
17:29 < rogermason> having stopped and re-started Buil-Target I see that fwbuilder is building. I thought it had stopped and that somethinge elese was building. My mistake. I'll be patient and see what happens.
17:39 < rogermason> OK. It finished and looks like only fwbuilder was built.
17:40 < rogermason> I see this after the build:
17:40 < rogermason> Searching for old lingering files ...
17:40 < rogermason> !> build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/pkgs/boost-jam-3.1.18.tar.bz2 should not be
17:40 < rogermason> present (now in src/invalid-files.lst)!
17:40 < rogermason> !> build/syslinux_minimal-9.0-trunk-generic-x86-i686-linux/TOOLCHAIN/pkgs/ccache-2.4.tar.bz2 should not be prese
17:40 < rogermason> nt (now in src/invalid-files.lst)!
17:40 < rogermason> Is this important?
17:41 <@rxr> I think they will only make the ISO bigger
17:41 < rogermason> how do I get rid of the messages?
17:41 <@rxr> only when you get "missing ..." warnings then you will certainly miss those binary packages on the ISO
17:41 <@rxr> you can rm all files in the invalid-files.lst
17:42 <@rxr> and re-run Build-Target to see if they are gone
17:42 < rogermason> OK. Thanks
17:46 < rogermason> Yes. Gone. The pam files are present in the build. Now to re-create the iso.
18:42 < rogermason> Everything is now working fine. many thanks for your help.
18:42 <@rxr> welcome
21:21 -!- keinek [~leonel@186.110.147.127] has joined #t2
21:21 < keinek> hi
21:38 < rogermason> hello.
21:43 -!- keinek [~leonel@186.110.147.127] has left #t2 []
21:43 -!- keinek [~leonel@186.110.147.127] has joined #t2
22:55 -!- keinek [~leonel@186.110.147.127] has quit [Quit: Leaving.]
--- Log closed Tue Sep 14 00:00:49 2010