[00:27] <NCommander> doko, mind if I ask some glibc questions?
[00:28] <doko> just ask
[00:30] <NCommander> doko, to configure glibc to go into /lib32, vs /lib, it appears I need to set a few configure flags, but I'm kinda stumped on which ones those might be, and I was hoping you would know
[00:31] <doko> hmm, the current glibc package should work fine. afaicr we move things around after the build
[00:35] <NCommander> doko, I'm not building the package, sourceful build; I'm rebootstrapping the toolchain from scratch using a different set of CFLAGS (-fPIE/-fPIC enabled by default)
[00:36] <doko> sorry, don't know this by heart
[00:37]  * NCommander nods
[00:37] <NCommander> You work more with GCC itself vs. glibc if memory serves
[00:38] <doko> and it's 2am here, so maybe post to the list
[00:38] <doko> yep
[00:38] <NCommander> doko, you always ack my m68k toolchain patchs in Debian so thank you for that and your assistance ;-)
[02:35] <ScottK> doko: Still no luck on lpia.  I retried clamav and it failed with the same error and I don't see any successful lpia builds today.  I verified from the build log that gcc-4.3 4.3.2-1ubuntu4 was used.
[02:35] <ScottK> http://launchpadlibrarian.net/17354296/buildlog_ubuntu-intrepid-lpia.clamav_0.93.3.dfsg-1ubuntu1_FAILEDTOBUILD.txt.gz
[05:05] <NCommander> doko, is there a way I can place the -fPIE flag somewhere will it will only affect compilation and linking against 64-bit (-m64) targets, but not the 32-bit ones in a biarch compiler
[05:27] <ScottK> doko: Not just lpia either: http://launchpadlibrarian.net/17356138/buildlog_ubuntu-intrepid-ia64.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[07:38] <lukehasnoname> so is it known/acceptable that I can't put LVM on top of encryption?
[07:54] <cjwatson> lukehasnoname: known, bug 267048. I think it's also Debian bug 494910 which would make it an easy fix; I'll look at it when I'm more awake
[07:59] <lukehasnoname> mk, just wanted to make sure that was a predictable occurance.
[09:46] <geser> doko: should gcc-4.3 (4.3.2-1ubuntu4) be good again?
[14:23] <ScottK> geser: It's not.
[14:40] <doko> geser, ScottK: what does 'ls -l /usr/lib/gcc/*' say on your local machine?
[14:42] <geser> on my local machine the symlinks are there
[15:11] <doko> geser, ScottK: thanks, sent email to ubuntu-devel. but I suppose we'lll have to wait for infinity or cprov-afk to have a look at the buildds
[15:17] <ScottK> doko: I also see the problem on ia64 and hppa:
[15:17] <ScottK> http://launchpadlibrarian.net/17360353/buildlog_ubuntu-intrepid-ia64.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[15:17] <ScottK> http://launchpadlibrarian.net/17356476/buildlog_ubuntu-intrepid-hppa.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[15:19] <ScottK> Additionally, it looks like primero (hppa) is broken in it's own special way as Hardy builds are dying there due to CHROOT problems.
[16:53] <EagleSn> hi
[16:55] <EagleSn> i am making a patch for a package, i am using: diff original.source.folder edited.source.folder > patch.diff
[16:55] <EagleSn> i am using it well?
[16:59] <cjwatson> EagleSn: diff -ru
[16:59] <cjwatson> (never use diff without the -u option)
[17:00] <cjwatson> if you created new files, diff -ruN
[17:00] <EagleSn> -run == -Nur
[17:00] <cjwatson> incorrect, -n != -N
[17:01] <EagleSn> thanks you
[17:12] <EagleSn>  if i want to build a new binary debian package with my patch applied, i think i have to make debian/patched folder and copy my patch into, then debuild will apply my patch automatically, am i right?
[17:13] <ion_> pitti, tkamppeter: Rebased the CUPS patch again.
[17:13] <cjwatson> if there isn't a debian/patches directory already, you should just apply the patch rather than adding a patch system
[17:16] <EagleSn> cjwatson than my patch wont be in the sources
[17:30] <ion_> pitti: Btw, using ${vcs}-buildpackage or equivalent would entirely remove the possibility of local changes sneaking into diff.gz. :-)
[18:55] <fta> since 2.6.27, top and ps are acting strangely... http://www.sofaraway.org/ubuntu/tmp/top.gif
[18:55] <fta> (look at %cpu)
[19:00] <EagleSn> hi
[19:27] <cjwatson> EagleSn: what makes you say your patch won't be in the source if you just apply it directly?
[19:27] <cjwatson> EagleSn: (obviously if there already is a debian/patches/ directory then it's usually best to add the patch there.)
[19:31] <EagleSn> yeah
[19:32] <EagleSn> then i apply my patch directly to sources
[19:32] <EagleSn> patch -p1 routr/to/my/patch
[19:32] <EagleSn> i will submit my patch in Launchpad, then i want to make it correctly
[19:34] <cjwatson> EagleSn: you should follow https://wiki.ubuntu.com/PackagingGuide/Howtos/Debdiff, then
[19:35] <EagleSn> i already have read it
[19:36] <EagleSn> but the patches i usually see in surces are not debdiff, they are diff or patch extension
[19:36] <cjwatson> it's the same format
[19:37] <cjwatson> you can apply any of them with patch
[19:37] <cjwatson> the debdiff program just ensures some basic level of consistency in how the patch is created, and so is preferred for patches submitted as Ubuntu bug reports
[19:56] <EagleSn> gpg gives me error at singing, it is as my passphrase was incorrect
[19:57] <EagleSn> is any way to see my passphare for gpg? i dont use it since much time ago, may be i am typing it wrongly
[19:57] <jpds> No, when you lose a passphrase, the key is useless.
[19:58] <EagleSn> any quickly way to gpg ask me for password and can try multiple?
[19:59] <jpds> The option: "--passphrase-repeat N" might help.
[20:00] <EagleSn> debsign?
[20:00] <jpds> No, that's a gpg option.
[20:02] <EagleSn> --passphrase-repeat N must be typed in debuild command?
[20:02] <jpds> Forget it, I just remembered that option is used when creating keys.
[20:03] <EagleSn> i ma lamost sure that i am typing well the pasphrase
[20:03] <EagleSn> i have imported today my gpg key, may be i imported it bad
[20:05] <EagleSn> i have 4 files: my-private.key; my-public.key; mykey-ASCII.asc and revoke-mykey.asc
[20:06] <EagleSn> i also printed my key in ASCII in paper
[20:15] <EagleSn> i did gpg --import my-public.key
[20:15] <EagleSn> gpg --import my-private.key
[20:15] <EagleSn> was it enought for restoring my key?
[20:21] <EagleSn> is it possible that gpg is working bas in Intrepid?
[20:22] <EagleSn> working bad *
[20:22] <cjwatson> I've not heard any complaints from developers who use it all the time
[20:22] <cjwatson> check gpg --list-secret-keys output to make sure it imported your secret key to the right place
[20:23] <EagleSn> right place?
[20:23] <cjwatson> gpg maintains two different keyrings, one for public keys and one for secret keys
[20:23] <cjwatson> gpg --list-secret-keys will show the contents of the secret keyring
[20:24] <EagleSn> i ma sure that i am entering well my passphrase, i have done an experiment to know it, and gpg fails
[20:24] <cjwatson> why do you care about the signature anyway?
[20:25] <cjwatson> if you're just going to produce a debdiff, it doesn't matter if the signing step fails
[20:25] <EagleSn> i think it is important
[20:25] <cjwatson> that only matters if you have upload privileges and are going to upload it to an archive
[20:26] <EagleSn> okay, but i would like to discover what is happening with my sign
[20:26] <cjwatson> what is the error message from gpg?
[20:26] <EagleSn> it is in Spanish
[20:26] <cjwatson> 'LC_ALL=C debsign'
[20:27] <EagleSn> i think there is a coomand to all output in console to be in English
[20:27] <cjwatson> export LC_ALL=C
[20:28] <EagleSn> that only affects to this terminal session?
[20:28] <cjwatson> yes
[20:28] <cjwatson> (this is quite basic; you might want to go elsewhere for general Unix help)
[20:30] <EagleSn> when it ask me for pass, if i put it wrong intentionally, it warn me about it is incorrect, and ask for me again until 3 times
[20:30] <cjwatson> if gpg is literally saying that your passphrase is wrong, then there are two possibilities: (1) you have another secret key with that UID etc., and gpg is using that rather than the one you expected (you can force it with 'debsign -kKEYID'), or (2) your passphrase is wrong
[20:31] <EagleSn> yes, but if i put the pass correctly, it do not tell me that it is incorrect, directtly gives me an error
[20:31] <Mithrandir> you can set it permanently in ~/.devscripts by having DEBSIGN_KEYID=$yourkeyid there.
[20:32] <Mithrandir> you need to provide us with the error if we're going to help you debug it.
[20:32] <EagleSn> yes, now
[20:32] <EagleSn> now it is asking for pass, ok i am going to put it correctly
[20:34] <EagleSn> look http://paste.ubuntu.com/44299/
[20:37] <EagleSn> gpg: problem with the agent - disabling agent use
[20:37] <EagleSn> that appears before i type passphrase
[20:39] <cjwatson> comment out use-agent in ~/.gnupg/options; or else (if you're intending to use an agent) configure the agent to keep your key for some reasonable amount of time, and prime it in advance by signing some random bit of text
[20:39] <cjwatson> (I use http://people.ubuntu.com/~cjwatson/tmp/gpg-refresh-cache for the latter purpose)
[20:40] <EagleSn> i dont understand nothing lol
[20:40] <EagleSn> reading the link
[20:40] <cjwatson> if you have no idea what I'm talking about, then make sure use-agent is not set in ~/.gnupg/options
[20:41] <cjwatson> and if you have no idea what I'm talking about, then gpg-refresh-cache is unlikely to be of any use to you
[20:42] <EagleSn> ok, what is agent than, wehere can i read some ?
[20:42] <cjwatson> oh, meh, we use an agent by default now, that's a bit annoying
[20:43] <cjwatson> EagleSn: I suggest just putting 'no-use-agent' at the end of ~/.gnupg/options (create that file if it doesn't already exist)
[20:43] <EagleSn> there is not options file in ./gnupg
[20:43] <cjwatson> as I just said, "create that file if it doesn't already exist"
[20:43] <EagleSn> ok
[20:44] <EagleSn> options file does need any header?
[20:44] <cjwatson> no
[20:44] <EagleSn> i did it
[20:45] <EagleSn> try debuild again?
[20:46] <cjwatson> please, this is a developer channel and we expect people to try things for themselves :)
[20:46] <EagleSn> i am doing it..
[20:47] <EagleSn> exactly tha samep roblem is happening
[21:33] <EagleScreen> cjwatson it seems that ./gnupg file is being ignored, see the output: http://paste.ubuntu.com/44322/
[22:07] <cjwatson> EagleScreen: oh, I suppose it's ~/.gnupg/gpg.conf now
[22:09] <EagleScreen> yes, i already did it
[22:09] <EagleScreen> there are no problem now
[22:09] <EagleScreen> thansk for your atention
[22:10] <EagleScreen> i think in Debian Agent is not used by default, may be by that i hadn't problems with this before, this is the first time I use debuild in an Ubuntu system
[22:24] <EagleScreen> where can i leanr the utility of gpg Agent?
[22:24] <EagleScreen> *learn
[22:33] <doggymenz> look, i have good idea for ubuntu to make it better
[22:33] <doggymenz> http://img504.imageshack.us/img504/3081/pinkvolumewz2.png
[22:49] <EagleScreen> doggymenz are you serious?
[22:49] <doggymenz> yes
[22:49] <doggymenz> you can choose color of volume partition, so you can have pink for porno, or maybe other color for something
[22:50] <EagleScreen> i think your idea is to can custom icon of disk drives?
[22:50] <doggymenz> ya
[22:50] <EagleScreen> report it to Launchpad and also in bugzilla
[22:50] <doggymenz> oh
[23:07] <doggymenz> i request 10000 packages on launchpad, but nobody make them
[23:49] <Ampelbein> hi there. i just tried uploading a source-package to my ppa but the build failed with the error "configure: error: C compiler cannot create executables". Is there something broken with my package or with the buildsystem?