[00:47] <schakrava> bobbo: hi
[06:23] <dholbach> good morning
[06:47] <Iulian> Morning Daniel.
[06:50] <dholbach> hiya Iulian
[08:05] <\sh> moins
[08:09] <geser> good morning
[08:52] <siretart> yay. AAC decoding support merged into ffmpeg's mainline :)
[09:07] <Dreigroschenlies> +ncz
[09:34] <huats> morning everyone
[09:34] <huats> hello mister sylvaing
[09:34] <huats> :)
[09:36] <sylvaing> hi huats
[11:35] <Daviey> Are any revu admins around?
[11:35] <persia> Daviey: What do you need?
[11:35] <Daviey> persia: for some reason my dput's aren't showing
[11:35] <persia> Daviey: Which package?
[11:35] <Daviey> fsniper
[11:36] <jpds> Daviey: Please login at revu.ubuntuwire.com and try again.
[11:36] <jpds> Daviey: No, just log in and tell me when you've done.
[11:37] <persia> Daviey: Yep.  That got rejected.  jpds has the right advice :)
[11:37] <Daviey> hmm, didn't get a rejection mail :`(
[11:38] <jpds> Daviey: It does not mail on rejections.
[11:38] <Daviey> ahh
[11:38] <Daviey> jpds persia: Do the logs say why it was rejected?
[11:38] <jpds> Daviey: Your key is not in the keyring, log in and it shall be.
[11:38] <Daviey> jpds: is it now?
[11:39] <persia> Daviey: Maybe: I never check them.  Make sure you've logged in: I'm checking the signing key now.
[11:39] <Daviey> ta
[11:39] <jpds> Once you've done that, I can move it back in the upload queue.
[11:39] <persia> Daviey:  DSA key ID E30281B3 ?
[11:40]  * persia leaves the rest of it to jpds who is clearly on top of things :)
[11:40] <Daviey> no
[11:40] <Daviey>  0A0D5256
[11:40] <jpds> persia: I can see his (three) keys, I'll move the .changes file to the upload queue.
[11:40] <huats> hello persia
[11:40] <persia> Daviey: The package was signed with E30281B3 : you might want to check your DEBEMAIL configuration.
[11:41] <persia> huats: Hello.
[11:41] <jpds> Daviey: `/srv/uploads/rejected/fsniper_1.2-0ubuntu1_source.changes' -> `/srv/uploads/fsniper_1.2-0ubuntu1_source.changes' - it shall appear shortly.
[11:41] <Daviey> jpds persia : cool, thanks
[11:42] <jpds> Anytime.
[11:50] <jpds> Daviey: Nope, the package is still rejected; best check which key you signed it with.
[11:51] <Daviey> hmm
[11:52] <jpds> Daviey: Which key did you use with: debuild -S -sa -k$KEYID?
[11:52] <Daviey> my mistake, it was signed with E30281B3
[11:52] <Daviey> (intentionally)
[11:53] <jpds> Yep, that key does not appear to be in the keyring.
[11:59] <jpds> Daviey: Please reupload with a key you have registered on LP.
[12:01] <Daviey> jpds: that ey is on lp :S
[12:01] <Daviey> key*
[12:01] <Daviey> (or at least ubuntu's keyserver)
[12:02] <Daviey> http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0x9A20F055E30281B3
[12:02] <jpds> Daviey: 3
[12:02]  * jpds -> headdesk.
[12:03] <jpds> Daviey: You'll have to add it to your LP: https://edge.launchpad.net/~davewalker
[12:04] <Daviey> silly me!
[12:04] <jpds> At: /+editpgpkeys
[12:04] <jpds> And relogin to LP, and reupload.
[12:05] <jpds> s/LP/revu/
[14:09] <sistpoty|work> hi folks
[14:09] <KenBW2> apparently Pidgin 2.5 has been released. how long till its in the repos?
[14:10] <nxvl> good morning
[14:11] <\sh> hey sistpoty|work
[14:11] <sistpoty|work> hi \sh
[14:14] <Laney> KenBW2: It is.
[14:16] <KenBW2> Laney: oh, ok. on Windows atm, will check when at home :)
[14:34] <leleobhz> how can i use distcc to build packages?
[14:34] <leleobhz> im using make -j4 on debian/rules, but this is a WOP
[14:35] <soren> "WOP"? "Whopping Obese Puppy"?
[14:36] <soren> Wandering Overseeing Policeman?
[14:36] <leleobhz> workaround oriented programming :p
[14:36] <persia> Willful Oberonic Pretender
[14:36] <leleobhz> :p
[14:37] <nxvl> soren: lol
[14:37] <leleobhz> things like while 1=1 :p
[14:37] <leleobhz> well
[14:38]  * soren still doesn't know what "wop" is. :(
[14:38] <leleobhz> but how can i use distcc with dpkg-buildpackage or cowbuilder
[14:38] <nxvl> soren: < leleobhz> workaround oriented programming :p
[14:38] <leleobhz> :]
[14:39] <leleobhz> examples of WOP here: http://desciclo.pedia.ws/wiki/POG
[14:39] <soren> Oh, I thought that was another funny suggestion.
[14:39] <leleobhz> (see the examples)
[14:39] <soren> Gambiarras?
[14:39] <leleobhz> soren: portuguese link :]
[14:40] <leleobhz> search the code in this page to see WOPs :]
[14:42] <soren> I can see it's Portuguese. I just don't know what Gambiarras are.
[14:42] <persia> TheMuso: About the UUSA meeting: any times work for you?
[14:43] <leleobhz> soren: gambiarra = weird workarround
[14:43] <soren> I see.
[14:43] <leleobhz> soren: gambiarra = *VERY* weird workarround
[14:43] <leleobhz> :]
[15:57] <NCommander> DktrKranz, you floating around?
[15:58] <DktrKranz> NCommander: yes
[15:59] <NCommander> DktrKranz, any luck with gcl?
[15:59] <DktrKranz> not even tried... there's a new challenge here
[15:59] <NCommander> What is it?
[16:00] <NCommander> hrm?
[16:01] <DktrKranz> NCommander: bug 231307
[16:02] <bddebian> Heya gang
[16:02] <NCommander> DktrKranz, looks fixed
[16:04] <DktrKranz> NCommander: in intrepid yes, in Hardy a rebuild would be enough if asis would be fixed
[16:04] <NCommander> whats wrong with asis?
[16:05] <NCommander> ACK
[16:05] <NCommander> ADA
[16:06] <NCommander> so its just a FTBFS
[16:06] <NCommander> Or something more serious
[16:06]  * NCommander knows how to program in Ada :-/
[16:07] <NCommander> DktrKranz, ping?
[16:13] <NCommander> DktrKranz, oh nice, it FTBFS out of the box :-)
[16:13] <slayton> how long does it generally take for packages to get reviewed at REVU?
[16:14] <bobbo> slayton: quite a while normally
[16:14] <persia> slayton: Ideally, packages get reviewed within 3 months, but we're running a little behind this cycle.
[16:14] <bobbo> slayton: especially this cycle, things have been slow :/
[16:15] <slayton> ok... that gives me a better perspective on what to expect
[16:15] <NCommander> bobbo, even slower then that :-P
[16:15] <persia> Best plan is to advertise your package here (short quip about why it's cool, REVU status, and REVU URL) about once every 30 hours.
[16:15] <Laney> Moar REVU days!
[16:15] <bobbo> NCommander: yeah I have a package that has been waiting for sponsorship for about a month and a half
[16:15]  * Laney gets in quick: http://revu.ubuntuwire.com/details.py?package=goocanvasmm - l33t bindings for goocanvas, known to cure disease and end world hunger
[16:15] <bobbo> NCommander: bug filed this time last cycle :/
[16:16] <NCommander> ouch
[16:16] <slayton> persia, well then I'd like to advertise dbus-c++ and sourcery-vsipl++  I'm pretty sure they aren't ready to upload yet but I don't think I know enough yet on how to get them ready
[16:16] <slayton> on my own
[16:17] <ScottK-laptop> slayton: Links are generally a good thing.
[16:18] <NCommander> DktrKranz, I'm seeing if I can do anything about asis-2005
[16:18] <slayton> http://revu.ubuntuwire.com/details.py?package=sourceryvsipl%2B%2B
[16:18] <slayton> http://revu.ubuntuwire.com/details.py?package=dbus-c%2B%2B
[16:19] <DktrKranz> NCommander: asis can be fixed switching to gnat-4.2, but since it must be done on LTS, I'm worried about implications since debian completed transition with gnat-4.3
[16:19] <NCommander> hardy shipped with gnat-4.1, right?
[16:19] <NCommander> asis must match the gnat version installed
[16:19] <NCommander> asis must be downgraded then
[16:19] <DktrKranz> gcc-defaults ships 4.2
[16:20] <NCommander> gnat doesn't follow gcc-defaults
[16:20] <NCommander> Never has
[16:20] <DktrKranz> but most of the packages are compiled with/for 4.1
[16:20] <DktrKranz> are you sure?
[16:20] <NCommander> Quite
[16:20] <DktrKranz> I thought it did
[16:20]  * NCommander checks p.u.o
[16:20] <Laney> Someone done broked ubuntu-dev-tools
[16:20] <DktrKranz> http://packages.ubuntu.com/source/hardy-updates/gcc-defaults
[16:21] <NCommander> gnat doesn't build out of the gcc source package
[16:21] <NCommander> strange
[16:21] <NCommander> Ok
[16:21] <DktrKranz> sure, but gnat package is provided here
[16:22] <persia> Laney: Which patch caused the issue?  How is it broken?
[16:22] <DktrKranz> and we didn't catch it in time to move * to gnat-4.2
[16:22] <NCommander> Hardy shipped with gnat-4.2 according to packages.ubuntu.com
[16:22] <DktrKranz> yes
[16:22] <Laney> persia: Looking now. Error is: http://paste.ubuntu.com/39423/
[16:23] <NCommander> so what move has to be done? At best we need a binary rebuild of ada packages if I follow you
[16:23] <slayton> So here is a random question.... I assume that the MOTU are officially supported at some level by Canonical... but I'm guessing most MOTU's are just volunteers right/
[16:23] <slayton> ?
[16:23] <DktrKranz> but several packages were imported from edgy, feisty or gutsy with gnat-4.1
[16:23] <NCommander> Right
[16:23] <NCommander> The proper course of action would be the Ubuntu equivelent of a binNMU
[16:23] <NCommander> Something launchpad doesn't support -_-;
[16:23] <DktrKranz> for ~ 16 packages, IIRC
[16:24] <NCommander> when perl got updated in Debian, all non-arch all perl packages got rebuilt ;-)
[16:24] <DktrKranz> well... publishing rebuilds for packages in -proposed is not a problem, my problem is *how* to test things properly
[16:25] <DktrKranz> if someone has ADA/gnat knowledge, please speak :)
[16:25] <NCommander> Run the gnat test suite
[16:25]  * NCommander ported gnat to m68k
[16:25] <NCommander> I think I'm qualified ;-)
[16:25] <DktrKranz> cool!
[16:25] <persia> slayton: Most MOTU are volunteers, yes.  Generally, one's employer is not considered when one is involved with MOTU.
[16:26] <NCommander> There was a discussion on this issue years ago in debian
[16:26] <NCommander> I think they binNMUed all ada packages when gnat was upgraded
[16:27] <NCommander> DktrKranz, checking qa.ubuntuwire.com confirms that an archive rebuild caused asis to build properly
[16:28] <DktrKranz> yes... conflicting with gnat-4.2, as my previous test
[16:28] <NCommander> We need to cause a binary rebuild of every gnat package
[16:28] <NCommander> THe easiest way we can confirm this is simply to shove every package that needs to be rebuilt in a PPA
[16:29] <NCommander> and see if we get a working result
[16:29] <persia> We can't do binary rebuilds: we have to do sourceful uploads, but they can be changelog-only.
[16:29] <NCommander> That will work
[16:29] <NCommander> (ugly, but it will work)
[16:29] <NCommander> Now its just a matter of figuring out what needs to be SRUed
[16:29] <persia> There's a bug in Soyuz about making it less ugly, but yes, that's how it must be done.
[16:29] <NCommander> I don't have a (working) hardy chroot ATM, but how does the issue specificy manifest itself
[16:30] <DktrKranz> persia: complexity: this is in Hardy only, so a SRU campaign must be taken
[16:31] <DktrKranz> I guess binary rebuilds (or similar) must be taken the old way here
[16:31] <NCommander> DktrKranz, doing the actual patch work is relatively easy. its more of a trick of locating what we must rebuild in what order
[16:31] <DktrKranz> NCommander: exactly
[16:32] <DktrKranz> there are some core packages which needs to be processed first
[16:32] <NCommander> we have ada based packages in core?
[16:32] <DktrKranz> and, once landed in -upgrades, we can go with the remaining ones
[16:32] <NCommander> (gnat is universe ...)
[16:33] <DktrKranz> no... universe. I referred to "core" as infrastructure packages, not packages in main
[16:33] <persia> NCommander: "core" != "main"
[16:33] <NCommander> Oh
[16:33] <NCommander> d'oh
[16:35] <NCommander> DktrKranz, so what is your plan of attack, if you have one
[16:36] <DktrKranz> NCommander: what I'd do here is 1) identifying the whole set of packages involved 2) study dependency chain to see which packages are required to be available before other ones 3) publish them in a PPA in the given order 4) test them 5) go for a SRU campaign
[16:36] <NCommander> Hrm
[16:36] <NCommander> My intrepid installation has gnat-4.1 installed
[16:36] <DktrKranz> it has both 4.1 and 4.3 (default)
[16:36] <NCommander> Oh wait
[16:36] <NCommander> the man page is misleading :-P
[16:37] <NCommander> I thought 4.2 was the default
[16:37] <DktrKranz> 4.3 in intrepid
[16:37] <NCommander> oh
[16:37] <NCommander> d'oh
[16:37] <NCommander> I'd love to work on this
[16:37] <DktrKranz> I think intrepid has stuff in place, but better be sure of it before FF
[16:37] <NCommander> Mind if I create a team PPA so we can both upload?
[16:38] <cody-somerville> What bout the universe contributor PPA?
[16:38] <NCommander> I'm not a universe contributor :-/
[16:39] <DktrKranz> what about filing a spec for this, just to have things in place?
[16:40] <DktrKranz> it's not complex, but long to manage
[16:40] <cody-somerville> NCommander, Well frackin apply already if not for MOTU here soon :P
[16:40] <NCommander> SO you think I meet the critera for UUC?
[16:41] <cody-somerville> Is this a trick question? :P
[16:41] <NCommander> No
[16:41] <NCommander> I'm legitimentally asking
[16:43] <cody-somerville> NCommander, You've demonstrated skill, team focus, and commitment
[16:43] <cody-somerville> So yes
[16:43] <NCommander> sweet
[16:44] <NCommander> Care to sponsor me once I fire the conseul an email?
[16:44] <DktrKranz> NCommander: yes IMHO. You've been around for a while and give great help with REVU and with packages in the archives
[16:44] <NCommander> That's two <g>
[16:45] <laga> UUC is different from MOTU, right?
[16:45] <NCommander> UUC means I get an @ubuntu.com email address, and the IRC cloak pretty much
[16:45] <laga> UUC is basically just a "ubuntu member", or am i wrong?
[16:45] <laga> yeah.
[16:45] <NCommander> No upload rights
[16:45] <persia> laga: You are correct, indeed.
[16:45] <NCommander> (expect to the UUC PPA)
[16:45] <laga> so, nothing interesting for me ;)
[16:46] <Laney> The recognition of your development peers
[16:46] <cody-somerville> laga, That doesn't demonstrate a team focus :-(
[16:47] <laga> why would i focus on a team that doesn't give me any real benefits?
[16:47] <NCommander> I'd be very happy with UUC
[16:47] <NCommander> I can take maintainership of my pacakages in Ubuntu
[16:47] <laga> NCommander: can you also upload these packages then? that's technically possible with launchpad now
[16:47]  * cody-somerville nod nods.
[16:47]  * cody-somerville was nodding about NCommander being able to set himself as a maintainer
[16:47] <NCommander> Nope
[16:48] <NCommander> No DM in Ubuntu
[16:48] <laga> well, that's a different thing and something useful actually. although that doesn't demonstrate "team focus" ;)
[16:48] <NCommander> (and Debian Maintainers is a god-ugly hack in dak)
[16:48]  * DktrKranz is happy to be part of that god-ugly hack in dak
[16:49] <NCommander> You made my eyes bleed
[16:49] <NCommander> There is a wonderful trail of curses in dak's source about it
[16:49] <DktrKranz> heh
[16:50]  * NCommander updates his wiki page with current events
[16:50] <NCommander> My DD application moved
[16:50] <NCommander> I'm in shock
[16:50] <NCommander> My AM is alive
[16:50] <NCommander> ANd he's ready to help me get through that ASAP
[16:50] <NCommander> -_-;
[16:50] <NCommander> I'm going to be a DD before an MOTU
[16:51] <DktrKranz> :)
[16:51] <NCommander> DktrKranz & cody-somerville: https://wiki.ubuntu.com/MichaelCasadevall#preview - Do you mine looking this over briefly to see if its acceptable for the Ubuntu consul (I'm going to scratch the header that says MOTU application, and note I also headed the SRU policy)
[16:51] <geser> NCommander: you don't know for how long your AM is alive :)
[16:52] <NCommander> geser, bah
[16:52] <NCommander> Don't jinx it
[16:52] <NCommander> But if I get DD-ness
[16:52] <NCommander> I'll be sure to help the Utunbu team get things back into Debian, as well as anew one who is submitting Ubuntu packages
[16:52] <DktrKranz> NCommander: when you'll get DD-ness, remember me ok? :)
[16:52] <NCommander> I'm not leaving :-)
[16:53] <cody-somerville> NCommander, you headed the SRU policy?
[16:53] <NCommander> er
[16:53] <NCommander> SRU key policy
[16:53] <NCommander> ^team
[16:53] <cody-somerville> Ah.
[16:53] <NCommander> I was the shepard
[16:53] <NCommander> I should be more clear
[16:54] <DktrKranz> NCommander: gonna leave now, will you be here later?
[16:54] <NCommander> yeah
[16:54] <NCommander> DktrKranz, what's your email?
[16:54] <NCommander> (I need to CC you on this application)
[16:54] <NCommander> persia, ping?
[16:54] <DktrKranz> dktrkranz@ubuntu.com
[16:55] <DktrKranz> ok, let's catch this later and get it fixed in intrepid (if not already fixed), then move to Hardy
[16:56] <DktrKranz> c u
[17:01] <persia> NCommander: Best to give me content.  While I decided not to go to bed quite yet, the chance that I'd have an answer ready for you when you returned if I had would be much higher if I knew why you sought me.
[17:02] <NCommander> persia, heh, sorry, are you interested in sponsoring me for Ubuntu Universe Contributor?
[17:04] <persia> NCommander: As massively active as you are, the guideline for membership is at least two months of significant and sustained contributions.  I'm only seeing about 6 weeks right now, so I don't have a lot of confidence MC would approve your app.  I'd suggest keeping up your activities for another month or so, and applying then.
[17:05]  * NCommander sighs
[17:05] <NCommander> Ok
[17:05] <NCommander> (I only considered applying since it was suggested, not really a big issue in any case)
[17:06] <cody-somerville> NCommander, You can still apply but Persia does bring up a good point. It certainly wouldn't change any of the good things I have to say about you though :]
[17:06] <NCommander> persia, as an aside, I will have the KeyTeamPolicy finished and posted by tonight, I rolled the outstanding concerns into said policy, and as there are no other issues, I think its done and ready to roll
[17:07] <persia> NCommander: URL?
[17:07] <NCommander> I haven't commited it to the wiki yet
[17:07] <NCommander> (wiki doesn't work at work for some reason)
[17:07] <NCommander> or if it does
[17:07] <NCommander> It takes longer then usual to edit
[17:07]  * NCommander shrugs
[17:08] <NCommander> just watch your inbox :-)
[17:13] <NCommander> persia, https://wiki.ubuntu.com/MOTU/Teams/KeyTeamPolicy - seems the wiki decided to start working for me
[17:15] <NCommander> persia, it says that two months are recommended, not required. But I do also understand your point
[17:18] <bddebian> Hah, just wait until you get into the DD process. :)
[17:19] <ScottK-laptop> bddebian: He is.
[17:19] <bddebian> I know
[17:19] <ScottK-laptop> K.
[17:19] <bddebian> I'm just saying, if he thinks MOTU is long.. :)
[17:20] <NCommander> bddebian, I've got my AM, and I'm working on the questionares as he sends them to me :-)
[17:21] <bddebian> I've had my AM since March 7 and answered did P&P and T&S as soon as he sent them to me. :)
[17:25] <AktionJackson> hab doch letztens age of ampires 3 demo gezockt
[17:25] <AktionJackson> ups
[17:31] <persia> NCommander: The admins are not members of either of the teams, so the admin can never be the member that resigned.  Also, typically MC does the additions anyway.
[17:31] <NCommander> persia, you didn't catch that the last time around :-P
[17:31] <NCommander> (that was unchanged from before)
[17:31] <ScottK-laptop> persia: Isn't the fact that currently no admins are members just coincidence.  It is possible?
[17:33] <persia> ScottK: I don't think it's likely.  In the case of motu-sru, it's not possible, except that one of the members might happen to also have indirect administration.  In the case of motu-release, there is one person who could join the team and be both, but I'd be surprised, as that person is otherwise exceedingly busy.
[17:35] <ScottK-laptop> Right.  If we've gone to the trouble to write the policy for the case down, we may as well keep it since it could occur.
[17:35] <persia> I guess.  I'd rather fix the ownership of motu-release to not be one person.
[17:35] <NCommander> persia, I've got to run, if you edit it, just ping me on IRC, or tell me how to edit it
[17:36] <persia> NCommander: No worries.  ScottK raises a valid point that currently this is possible, but exceedingly unlikely, and it's not worth dropping it from policy while it remains possible.
[17:37] <NCommander> Got to love legal (or policy) technicalities
[17:37] <NCommander> persia, so it meets your seal of approval?
[17:38] <persia> NCommander: better to say that I don't have any specific objections.
[17:39] <persia> It's not what I would have written as policy, but it's something to which I can agree.
[17:41] <NCommander> persia, I'm sorry if I write policies like I was a lawyer :-P
[17:42] <persia> NCommander: No need to apologize.  While I wrote the previous draft, the original idea comes from LaserJock.  It's the result of collaboration and consensus, which is not a bad thing.
[17:43] <NCommander> I meant the written style of the policy which I thought you didn't quite like
[17:44] <persia> Oh, I'm not that fussed about the writing style.  It's that I wouldn't have written that policy, but I can agree to that policy.
[19:02] <emgent> evening
[19:02] <Laney> hi emgent
[19:02] <emgent> heya :)
[19:02] <sebner> emgent: \o/
[19:03] <emgent> sebner: launchpad bugs mass flooder!
[19:03] <firstman> hi
[19:03] <Laney> yo
[19:04] <sebner> emgent: why? ^^
[19:05] <emgent> i dont know why, i only saw your mass sync`s request. :)
[19:05] <firstman> i remember that there are a script that using a console let you create preinst, postinst, prerm or postrm easily, but i dont remember what is his name
[19:06] <sebner> emgent: 98% ACKed already ;)
[19:11] <sebner> DktrKranz: \o/
[19:11] <DktrKranz> hola sebner
[19:12] <NCommander> DktrKranz, working on determing the rdepends
[19:12] <DktrKranz> confess... you were watching football!
[19:12] <NCommander> It doesn't appear to be an issue in intrepid
[19:12] <NCommander> (in intrepid, everything appears to be properly linked to libgnat-4.3)
[19:12] <DktrKranz> NCommander, nice to know. It won't be much pain, though. Debian should have it fixed
[19:12] <NCommander> we don't sync binaries ;-)
[19:13] <DktrKranz> but can sync sources or rebuild them :)
[19:13] <NCommander> for hardy?
[19:13] <NCommander> I don't think we need to rebuild, just a changelog only upload to trigger a rebuild
[19:13] <NCommander> We just need to stage it all out
[19:14] <DktrKranz> well... rebuild == changelog only upload
[19:14] <NCommander> yeah
[19:14] <cody-somerville> DktrKranz, Well, a special changelog only upload :P
[19:16] <DktrKranz> NCommander, are you using apt-cache or grepping files from the archives?
[19:16] <NCommander> apt-rdepends :-)
[19:16] <DktrKranz> does it check for reverse b-d?
[19:17] <NCommander> E: Reverse build-dependencies are not supported
[19:17] <NCommander> So no ;-)
[19:17] <NCommander> I just looked for the rdepends recurively for the runtime library
[19:18] <DktrKranz> most of the packages are from a unique maintainer
[19:18] <DktrKranz> so, we can look at his QA page to check missing packages
[19:19] <NCommander> its amazing how few ada packages their are
[19:19] <DktrKranz> easier to accomplish :)
[19:19] <DktrKranz> how many so far?
[19:19] <NCommander> Daviey, 26 packages
[19:19] <NCommander> er
[19:20] <NCommander> DktrKranz,
[19:20] <firstman> there are an easy way for create patches? apart writing shellscript by hand
[19:20] <DktrKranz> well 26 SRUs are many, but not impossible
[19:20] <NCommander> s
[19:20] <ScottK-laptop> NCommander: For reverse build-depends, grep-dctrl is your friend.  IIRC there's an easy cheater script in ubuntu-dev-tools.
[19:21] <NCommander> what's it called?
[19:21] <jpds> reverse-build-depends
[19:21] <NCommander> rather obvious :-P
[19:21] <jpds> For (failed) rebuilds there's: "buildd".
[19:22] <NCommander> So 28
[19:22] <NCommander> actually, no 26
[19:22] <NCommander> Two can be removed from reverse-build-depends
[19:22] <DktrKranz> NCommander, I'd scan for gnat-dev and gnat-4.X-dev packages, so we can collect them all
[19:23] <NCommander> We don't need to rebuild ones the explicately state the compiler version
[19:23] <DktrKranz> assuming there's no other business involved
[19:23] <NCommander> gnat-dev finds no hits
[19:23] <NCommander> YOu just need build-dep on gnat, thats the actual compiler
[19:23] <DktrKranz> those for gnat-4.2-dev need love
[19:23] <DktrKranz> (if any)
[19:26] <NCommander> DktrKranz, there are none
[19:26] <NCommander> So the versioning would be XubuntuX.1
[19:26] <NCommander> Right?
[19:27] <NCommander> (and if there is no ubuntu version, add one as 0bubuntu0.1)
[19:27] <NCommander> er,
[19:27] <NCommander> Xubuntu0.1
[19:27] <afflux> Am I still able to request a sync for a package recently added to debian unstable? Do I need any special justification for it?
[19:27] <DktrKranz> for no-change rebuilds, Xbuild0.Y
[19:28] <NCommander> Is that if there is no Ubuntu version number, or in general?
[19:28] <Laney> afflux: Why do you want it if there's no reason?
[19:28] <afflux> Laney: I think it would be "good to have", just because it's python bindings for a software I'm writing ;)
[19:29] <Laney> afflux: Then write that, just a sentence on why it's nice to have
[19:30] <afflux> okay, will do. Thanks.
[19:32] <Laney> You don't need that much justification before FF
[19:33] <afflux> okay, I was just wondering because of DIF.
[19:34] <geser> it's not strictly needed, but I like it when sponsoring sync requests as it show that the requester has thought about it and doesn't want it sync just because Debian has a newer revision
[19:34] <ScottK-laptop> afflux: DIF just means autosync is turned off.  It would more precisely be name DAIF (adding Automatic).
[19:35] <NCommander> DktrKranz, was I right?
[19:35] <afflux> yeah, right.
[19:35]  * Laney is impressed with Wubi
[19:35] <DktrKranz> NCommander, yes
[19:36] <Laney> I wonder if $parents[] will be impressed with Ubuntu...
[19:36] <cody-somerville> I wouldn't recommend wubi personally
[19:36] <NCommander> DktrKranz, so should I start uploading things to a PPA :-)
[19:36] <Laney> cody-somerville: Why's that?
[19:37] <DktrKranz> NCommander, did you find which one?
[19:37] <cody-somerville> If you don't shutdown correctly, your wubi install of Ubuntu will not boot any longer until you run the ntfs (either Window's or Linux's) tools on it to mark the partition as clean.
[19:37] <NCommander> DktrKranz, what do you mean which one?
[19:37] <DktrKranz> will you upload to yours?
[19:37] <SolarWar> hi, i've lost my PGP key, but i have my revocation certificate, is it possible to revoke the key?
[19:37] <Laney> Does it offer to run it?
[19:37] <jpds> SolarWar: Yes, gpg --import the cert.
[19:38] <geser> SolarWar: yes, that's the only way to revoke a lost key
[19:38] <afflux> and don't forget to send it to the servers again: "gpg --send-key keyid".
[19:38] <SolarWar> jpds, gpg: key 7DC579EC: no public key - can't apply revocation certificate
[19:38] <geser> SolarWar: gpg --recv-key 0x7DC579EC and try again
[19:38] <NCommander> DktrKranz, I can simply make a team so we can both upload
[19:39] <DktrKranz> NCommander, eventually we can link our PPAs (or copy packages when ready), so there's no need to have a central PPA
[19:40]  * NCommander cleans out his PPA first
[19:40]  * DktrKranz too
[19:40] <NCommander> I can handle all the uploads if you want to write the spec and such?
[19:40] <DktrKranz> agreed
[19:41] <NCommander> I'm just going to go right down the list, I don't expect anything to fail
[19:41] <NCommander> (well, libs first, the the rest)
[19:43]  * NCommander installs hardy sources
[19:43] <NCommander> DktrKranz, do you have a standardized changelog message you'd like to use for this>
[19:43] <SolarWar> geser, jpds thanks :)
[19:44] <DktrKranz> NCommander, something similar to "No-change rebuild for gnat-4.2 transition (LP: #xxxxxx)" should go.
[19:45] <NCommander> Did you open an LP bug already?
[19:45] <NCommander> or should it be an individual bug for each package?
[19:45] <DktrKranz> how many packages are on hardy? ~ 26?
[19:46] <NCommander> 26
[19:46] <NCommander> (it will be a bitch to do it for each individual package)
[19:47] <DktrKranz> I think archive-admins will have troubles to discover which packages need to be pushed if we file a single bug, especially if SRUs need to be managed in several stages
[19:47] <NCommander> ok
[19:47] <NCommander> Individual bugs it is
[19:47] <NCommander> handy hint
[19:47] <DktrKranz> I'd rather discover which packages need to be pushed before and file a common bug report
[19:48] <DktrKranz> and then go for the second ones
[19:48] <DktrKranz> (if applicable)
[19:48] <NCommander> For ones that have no ubuntu minor, its build0.1, right appended?
[19:48] <persia> I'd recommend waiting until you know the structure that updates must follow before opening the bugs.
[19:48] <DktrKranz> Let's make some tests before announcing bugs on LP
[19:48] <NCommander> That means redoing each changelog twice :-/
[19:50] <DktrKranz> yes, but it will be easier to manage by every parties
[19:50] <NCommander> DktrKranz, ok, I'm going to test uploading asis
[19:50] <NCommander> THat's one of the major libraries that needs a rebuild
[19:50] <NCommander> (to my PPA)
[19:51] <DktrKranz> go go go!
[19:51] <NCommander> uploaded to PPA
[19:51] <DktrKranz> and I guess it's the main source of problems
[19:51] <DktrKranz> another problem is hardcoded binary packages dependencies
[19:52] <DktrKranz> I saw several packages have gnat-4.1 in it
[19:52] <NCommander> DktrKranz, if its hardcoded, its intentionly dependent on the old gnat-4.1
[19:52] <DktrKranz> so, gnat-dev should be replaced with gnat-4.1-dev
[19:52] <NCommander> (if we want to zap gnat-4.1 from the archive, then be my guest, crust busters would love you ;-))
[19:53] <NCommander> https://edge.launchpad.net/~sonicmctails/+archive - I'll keep track of the rebuild process in my whiteboard
[19:53] <DktrKranz> heh
[19:53]  * DktrKranz thinks about it a bit
[19:53] <Kilimanjaro> Has anybody here substantial experience with lazarus? I try to package some software with it. It compiled one month ago on Debian, but it does not now on either Debian or Ubuntu.
[19:53] <NCommander> At least once its all done, you just need to pull all the sources, and reupload to hardy-updates
[19:53] <DktrKranz> hardy-proposed, actually
[19:53] <NCommander> er, my mistake
[19:54] <NCommander> I thought hardy-updates was aliased to hardy-proposed, so a changelog with either one would go to the right place
[19:54] <DktrKranz> no, hardy-updates is (was?) a valid target for uploads
[19:54] <NCommander> man, things take awhile to show up in ones PPA
[19:55] <NCommander> (this is the first serious abuse of a PPA I've ever done ;-))
[19:56] <NCommander> There we go
[19:56] <NCommander> lpia doesn't have an ada compiler
[19:57] <DktrKranz> another layer of complexity: libgnatvsn-dev points to libgnatvsn-4.2-dev and there's no libgnatvsn-4.1-dev at all... packages which b-d on those must have hardcoded dependencies adjusted to new gnat
[19:58] <NCommander> Lets hold off moving packages that are hardcoded on gnat-4.1
[19:58] <NCommander> AFAIK, they aren't broken since they are all built consistantly with the same compiler
[19:58] <DktrKranz> asis has, IIRC
[19:58] <NCommander> asis is gnat, not gnat-4.1
[19:59] <NCommander> I mean to say the issue is code getting intermixed
[19:59] <DktrKranz> http://packages.ubuntu.com/hardy/asis-programs
[19:59] <NCommander> The build-dep in the control file is: Build-Depends: gnat (>= 4.1)
[20:00] <NCommander> But ...
[20:00] <NCommander> Oh
[20:00] <NCommander> damn it
[20:00] <DktrKranz> look at binary stanza
[20:00] <NCommander> Its got a depends on the compiler
[20:00] <NCommander> Ok
[20:00] <NCommander> That needs a fix
[20:00] <NCommander> But it at least it builds now it seems
[20:00] <DktrKranz> that's good
[20:00] <NCommander> Argh
[20:00] <NCommander> FTBFS
[20:01] <NCommander> http://launchpadlibrarian.net/16986932/buildlog_ubuntu-hardy-i386.asis_2005-5build0.1~ppa1_FAILEDTOBUILD.txt.gz
[20:01] <NCommander> That's ugly
[20:01] <NCommander> oh
[20:01] <NCommander> Shut
[20:01] <NCommander> asis is not compatible with gnat 4.1
[20:01] <NCommander> The actual source package will require an upgrade
[20:02] <NCommander> (er, asis-2005)
[20:02] <DktrKranz> *really* bad
[20:02] <NCommander> (2007 works fine with 4.3)
[20:02] <NCommander> I can find an asis that works with 4.2
[20:02] <NCommander> Then we just need to rebuild asis's rdepends
[20:03] <NCommander> Its your call on how we fix it
[20:03] <DktrKranz> a "minimal" patch would be welcome
[20:03] <DktrKranz> but I guess "minimal" won't be our case
[20:04] <NCommander> 2007-3 is 4.3
[20:04]  * DktrKranz starts to think debian didn't want to transition to 4-2 intentionally...
[20:05] <NCommander> Yeah
[20:05] <NCommander> THat's ugly
[20:05] <NCommander> (check out README.Debian)
[20:05] <DktrKranz> asis' ?
[20:05] <NCommander> Yeah
[20:05] <NCommander> That's the headache
[20:05] <NCommander> asis is compiler version dependent
[20:05] <NCommander> Since it hooks into GCC's internals
[20:06] <NCommander> I need to work out how the debian packaging works
[20:06] <NCommander> Then I can tell you how big of a headache we have
[20:07]  * DktrKranz prepares some Aul*n
[20:07] <NCommander> Aul*n?
[20:07] <DktrKranz> replace * with i
[20:08] <DktrKranz> it's a common remedy for headache, at least in Italy
[20:08] <NCommander> No idea what Aulin is
[20:09] <NCommander> Did any Debian release ever use gcc-4.2 as the default?
[20:09] <NCommander> (etch was 4.1, and lenny is 4.3 ...)
[20:09] <DktrKranz> just for a small period
[20:10] <DktrKranz> but they turned to 4.3 very soon and then started transitioning
[20:10] <DktrKranz> after that, 4.2 was removed
[20:10] <NCommander> yeah
[20:10] <NCommander> Dman
[20:10] <NCommander> That's a problem
[20:10] <DktrKranz> (and now I figured why)
[20:10] <NCommander> I'm looking for an asis that works with 4.2
[20:11] <NCommander> I say we do a clamav, and simply propose asis-2007 be used
[20:11] <DktrKranz> I'll do a quick diffstat
[20:12] <ScottK> NCommander: "Do a clamav" took about a year and lots of testing.  Enjoy.
[20:12] <NCommander> ATM, this doesn't work period
[20:12] <NCommander> But ...
[20:12] <NCommander> ugh
[20:12] <NCommander> asis has a hard coded build-depends on gcc-4.2
[20:13] <NCommander> r
[20:13] <NCommander> 4.3
[20:13] <DktrKranz> monstruos
[20:14] <DktrKranz> diff is > 3 Mb in size... archive-admin will blow us away
[20:14] <NCommander> I could see if I could port asis-2005 against gcc-4.3
[20:14] <NCommander> *43.2
[20:14]  * NCommander blows the dust off his ada coding skills
[20:15] <NCommander> at least its hard to shoot yourself in the foot with ada
[20:19] <NCommander> I see the issue
[20:19] <NCommander> This might be patchable
[20:23] <NCommander> DktrKranz, ok, I think I found a patch that might work
[20:27] <NCommander> DktrKranz, now what?
[20:27] <NCommander> (I'm seeing if I can patch this to build, not sure if I can)
[20:27] <DktrKranz> what is its weight?
[20:27] <NCommander> right now, six lines of code
[20:27] <NCommander> But I can't promise that if it builds it will actually work
[20:28] <NCommander> Right now, its just failing because of a casting issue, but there may be more issues that haven't cropped up yet
[20:29] <DktrKranz> if it's six lines, and it's safe enough, it's definitely worth having it in
[20:29] <NCommander> Right now, its just a forced cast
[20:29] <NCommander> ada is strongly typed, so any changes in objects will break things
[20:30] <DktrKranz> next question is if asis is compatible with 4.2
[20:30] <NCommander> We'll have to really test anything that depends on asis
[20:32] <DktrKranz> brb
[20:48] <NCommander> DktrKranz, ok, I think I got it working
[20:48] <DktrKranz> cool
[20:48] <NCommander> Had to remember my ada string manipulation ;-)
[20:49] <NCommander> We'll have to keep this all in a single ppa since asis needs patchs
[20:49] <NCommander> (I think there is a way though to specify to grab packages from another PPA)
[20:49] <NCommander> DktrKranz, under your PPA, add mine as a dependency so it can grab the modified asis from it
[20:51] <DktrKranz> NCommander, done
[20:52] <TomJaeger> is it possible to resume a build with dpkg-buildpackage?
[20:52] <NCommander> add -nc
[20:53] <TomJaeger> thanks
[20:54] <NCommander> Uh oh
[20:54] <NCommander> linker error
[21:00]  * jpds waves at rn114 
[21:00] <rn114> hi, i'm trying to create a new package, but having some trouble with pbuilder not satisfying dependencies
[21:00]  * rn114 waves back
[21:01] <rn114> The following packages have unmet dependencies:
[21:01] <rn114>   pbuilder-satisfydepends-dummy: Depends: libdts-dev which is a virtual package.
[21:01] <jpds> rn114: Could you paste bin the build log?
[21:01] <rn114> yeah one sec
[21:01] <geser> rn114: have you enabled universe in your pbuilder?
[21:02] <rn114> pastebin post here: http://pastebin.com/me808b1b
[21:02] <rn114> good question geser, this is my first use of pbuilder, i'll just check
[21:04] <rn114> geser, no i hadn't, retrying now
[21:04] <NCommander> DktrKranz, I think I got the linker error to clear
[21:05] <rn114> right, i tried uncommenting COMPONENTS="main restricted universe multiverse", but got the same result
[21:05] <rn114> i'm just rebuilding my pbuilder environment to see if that helps
[21:05] <jpds> rn114: Have you updated the base tgz?
[21:06] <rn114> with sudo pbuilder update?
[21:06] <rn114> i just did sudo pbuilder create again, although that was probably a mistake
[21:06] <jpds> It'll do it.
[21:07] <NCommander> DktrKranz, are you dead to the world?
[21:07] <DktrKranz> no
[21:07] <rn114> but overkill?
[21:07] <NCommander> /usr/bin/ld: a4g-a_elists.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
[21:08] <NCommander> Bah
[21:08] <DktrKranz> huh?
[21:08] <DktrKranz> wasn't it build with -fPIC already?
[21:08] <NCommander> Seems like it isn't
[21:08] <NCommander> well
[21:08] <NCommander> It's susposed to be
[21:12] <NCommander> Oh
[21:12] <NCommander> shoot, this looks like it might be an AMD64 issue
[21:12]  * NCommander tests
[21:14] <joaopinto> that is an AMD64 issue, you will need to add -fPIC on the object files building
[21:15] <rn114> jpds, geser its chuntering away now, seems good
[21:15] <rn114> thanks for the help
[21:15] <jpds> rn114: Glad to hear it works.
[21:15] <rn114> it'll probably be another hour or so before i find the first build error :-)
[21:15] <NCommander> joaopinto, I figured as much, I'm running down where I need to add it, gnat apps are kinda weird
[21:15] <rn114> i assume that the pbuilder environment will be quicker to set up on subsequent attempts?
[21:16] <NCommander> joaopinto, does the static library need to be -fPIC?
[21:16] <joaopinto> NCommander, no idea on that, I had that issue with a software which used no other libs :\
[21:17] <NCommander> joaopinto, I'm just rebuilding the source package first to check consistancy issues, I did so editng of the rules file
[21:17] <jpds> rn114: You'll just need to sudo pbuilder update.
[21:17] <geser> rn114: every pbuiler run needs to unpack the base.tgz and clean up afterwards
[21:17] <joaopinto> but I guess it does, because I have a vague idea of seeing that on  .a building some time ago
[21:18] <rn114> so geser, it unpacks base.tgz, selects all required packages and then goes on to try and build the package afresh each time?
[21:19] <geser> yes
[21:19] <rn114> k thanks
[21:19] <geser> this way you get every time a clean environment and only the packages which are needed to build the package are installed
[21:22] <rn114> yes, i realise what i said sounded a bit critical, but i understand the need for it
[21:35] <NCommander> DktrKranz, ok, got it :-)
[21:36] <NCommander> It's roughly a 10-15 line debdiff
[21:36] <DktrKranz> wooohooo!
[21:36] <NCommander> (bunch of rules file changes, control file change, changelog, and one new source patch)
[21:36] <NCommander> Uploading to ppa, with version of 5ubuntu0.1~ppa1
[21:44] <NCommander> DktrKranz, should I add lpia as an architecture?
[21:45] <DktrKranz> let me check p-a-s
[21:45] <DktrKranz> %asis:                alpha amd64 hppa i386 ia64 kfreebsd-i386 mips mipsel s390 sparc powerpc
[21:46] <DktrKranz> won't build
[21:48] <NCommander> Bah
[21:51] <NCommander> DktrKranz, ok, I think I got it fully fixed now (I had some issues with bad changes getting in the source package)
[21:54] <NCommander> DktrKranz, now that asis is properly ported and handled, we need to test it, got a good build-dep against asis we can test?
[21:54] <DktrKranz> NCommander, libaws, to fix  231307
[21:55] <NCommander> Where's the latest source of libaws?
[21:56] <DktrKranz> https://edge.launchpad.net/ubuntu/hardy/+source/libaws
[21:57] <DktrKranz> libaws should be released once asis is in -updates, though
[21:57] <NCommander> I don't see the debdiff
[21:57] <NCommander> Er
[21:57] <NCommander> I assume I need to grab the source out of proposed?
[21:58] <DktrKranz> I didn't upload anything, current version is the one from hardy-release
[21:58] <NCommander> Oh, that one just needs a rebuild?
[21:58] <DktrKranz> probably
[21:58] <DktrKranz> or just switching to gnat-4.1 to gnat
[21:59] <NCommander> The intrepid one is hard coded for 4.3
[21:59] <NCommander> gnat, gnat-4.2
[21:59] <NCommander> er, gnat, gnat-4.3
[21:59] <DktrKranz> hardy has gnat-4.1, IIRC
[21:59] <NCommander> ARGH
[22:00] <NCommander> *swears*
[22:00] <NCommander> no, hardy has 4.2
[22:00] <NCommander> By default
[22:00] <NCommander> Aren't we moving everything to 4.2?
[22:00] <DktrKranz> yes
[22:00] <DktrKranz> or trying to, at least
[22:00] <DktrKranz> if it has 4.2, a rebuild is enough
[22:01] <DktrKranz> if it won't FTBFS, of course
[22:02] <DktrKranz> I'm unsure if packages in -proposed are automatically propagated to others in -proposed too, if so, we could upload packages with shorter delats
[22:02] <DktrKranz> *delays
[22:09] <DktrKranz> ok, got an answer in -devel
[22:12] <NCommander> DktrKranz, uploaded the libaws package with gnat-4.1 depends removed
[22:12] <NCommander> I'm not sure if we should be hardcoding the depends to 4.2, or what
[22:12] <DktrKranz> no, gnat points to correct gnat
[22:12] <DktrKranz> *gnat-4.2
[22:12] <NCommander> what happens if gnat updates, and we have to binary rebuild AGAIN
[22:13] <NCommander> it worked out for intrepid because of the hardcoded gnat-4.3 I think
[22:13] <DktrKranz> I don't think someone will upgrade gnat :)
[22:13] <DktrKranz> and if he does, he should be prepared to a crisis!
[22:14] <NCommander> http://www.ada-france.org/debian/debian-ada-policy.html#The-Debian-Ada-compiler - there is nothing special here
[22:14] <DktrKranz> ppa3 failed too :(
[22:20] <NCommander> DktrKranz, bah, I'm just having issues
[22:20] <NCommander> I'm making sure it works in pbuilder this time around
[22:20] <NCommander> (I've been abusing the PPA, but it seems it ignores it if a patch fails to apply cleanly)
[22:21] <NCommander> Just not my night tonight :-/
[22:22] <NCommander> DktrKranz, libaws_2.2dfsg-1ubuntu0.1~ppa1.dsc: Section '-' is not valid
[22:22] <NCommander> (PPA reject)
[22:22] <DktrKranz> \o/
[22:22] <DktrKranz> no section in source stanza
[22:22] <NCommander> Yup
[22:22] <NCommander> *sighs*
[22:22] <DktrKranz> add a bogus one for now
[22:22] <NCommander> Who the hell packages these, and who checks incoming
[22:26] <slangasek> who checks what incoming?
[22:26] <NCommander> Debian incoming, source package lacking section
[22:26] <NCommander> dak should choke on that
[22:26]  * NCommander grumbles and stops being bitter
[22:27] <NCommander> slangasek, anyway, how goes your night?
[22:27]  * NCommander takes a chill/overreacting pill
[22:27] <slangasek> Sections are all done via override in dak, so the ones in the source package are just suggestions
[22:27] <slangasek> though I am a bit surprised that dak doesn't reject that
[22:27] <slangasek> NCommander: it's not night here...
[22:28] <NCommander> s/night/$SLANGSEK_LOCATION
[22:28] <NCommander> :-P!
[22:28] <azeem> ELANGASEK
[22:29] <NCommander> ack, typo
[22:29] <slangasek> NCommander: my Oregon is doing fine, thanks
[22:29] <NCommander> hrm
[22:29] <NCommander> ....
[22:29] <NCommander> I should not be allowed anywhere near regexs
[22:30] <NCommander> I may splice together non-sense, and insanity in something resembling a working mind like my own
[22:30] <TheMuso> persia: Preferably some time between 23UTC and 12UTC, during the week.
[22:33] <NCommander> wow, I didn't know you could rescore in a PPA
[22:37] <wgrant> NCommander: One cannot unless one is a buildd admin. But if one is, they're the same as primary archive builds.
[22:37] <NCommander> ah
[22:37] <NCommander> (one of the buildd admins said you could rescore in a PPA, but this is the first time I ever actually had something queued up in a ppa)
[22:38] <NCommander> DktrKranz, this time, it got past the section it kept FTBFS in the PPA
[22:39] <DktrKranz> be prepared to receive FTBFS in libawf
[22:39] <NCommander> yeah
[22:39] <NCommander> I'm simply going to retry it once asis finishs
[22:39] <DktrKranz> but a rebuild should be enought to fix them
[22:41] <NCommander> DktrKranz, WOOOOO, success on asis!
[22:41] <DktrKranz> \o/
[22:41] <NCommander> ugh, you have to reset individually each arch you want to build
[22:42] <wgrant> NCommander: buildd.py
[22:42] <NCommander> does it work on PPAs/
[22:42] <DktrKranz> wait until binaries are published, or you'll get another round of FTBFS
[22:42] <wgrant> Maybe not.
[22:43] <NCommander> oh er
[22:43] <NCommander> ...
[22:43] <wgrant> But I'm sure you could convince it to.
[22:43] <NCommander> damn
[22:43] <NCommander> How long does t take for binaries to get published
[22:43] <DktrKranz> 20 minutes?
[22:43] <wgrant> 16 minutes and 30  secondsfrom now.
[22:43] <NCommander> I see the binaries in the pool
[22:44] <wgrant> 4 minutes and 10 seconds ago, then.
[22:45] <NCommander> meh
[22:45] <NCommander> WHY DO I KNOW ADA
[22:45]  * NCommander hits his head on the wall
[22:49] <NCommander> I caught a mistake in the packaging
[22:50] <NCommander> Now
[22:50] <NCommander> Figures
[22:52] <nxvl> goof afternoon!
[22:53]  * DktrKranz is AFK for a while
[22:54] <james_w> hey nxvl
[22:56] <nxvl> james_w: ni!
[22:56] <nxvl> hi*
[22:59] <slangasek> the knights who say hi
[22:59] <NCommander> DktrKranz, ok ...
[22:59] <NCommander> bah
[22:59] <NCommander> slangasek, I thought we were the knights who said hi-how-are-you-how's-your-Oregon-going?
[22:59] <NCommander> (or the knights who formally said hi :-P)
[23:01] <slangasek> that may be!
[23:06]  * NCommander rebuilds libadaxml2 :-/
[23:06] <NCommander> Some people have lives
[23:06] <NCommander> I'm fixing gnat-4.2 issues
[23:06] <NCommander> *sigh*
[23:07] <azeem> when you're done not having a life fixing gnat-4.2, you could port it to the Hurd!
[23:07] <azeem> just kidding
[23:08] <NCommander> What porting
[23:08] <NCommander> It just needs a cross-bootstrap
[23:08] <NCommander> Now building GCC/Gnat on hurd might just be pure pain
[23:09] <azeem> I think there's some arch-dependant code
[23:09] <azeem> maybe I'm confusing it with another language
[23:10] <NCommander> http://launchpadlibrarian.net/16989115/buildlog_ubuntu-hardy-amd64.libaws_2.2dfsg-1ubuntu0.1~ppa1_FAILEDTOBUILD.txt.gz - does this build failure make sense to anyone?
[23:10] <NCommander> azeem, ada is implemented above the arch specifc parts of gcc
[23:11] <NCommander> YOu could target it to viengoos if you really liked pain
[23:11] <azeem> I don't
[23:12] <NCommander> azeem, I dunno, your a hurd porter. Some where deep inside is a pain loving masochist :-)
[23:12] <azeem> NCommander: probably easier to figure that out manually via apt-get in a hardy chroot
[23:12] <NCommander> Yeah
[23:12] <NCommander> Meh
[23:13] <NCommander> my hardy chroot currently updating itself so meh
[23:13] <azeem> NCommander: probably easier to figure that out manually via apt-get in a hardy chroot in a 5 minutes
[23:13] <azeem> -a
[23:19]  * NCommander returns from his smoke break
[23:20] <NCommander> DktrKranz, have you returned?
[23:21] <DktrKranz> sort of
[23:21] <NCommander> DktrKranz, sort of? It's kinda a binary question
[23:21] <DktrKranz> I'm retourned, but will be here for a little (quite late here9
[23:23] <NCommander> DO you want to handle the nitty gritty of writing the spec/SRUs, and I'll handle doing the transition part?
[23:23] <DktrKranz> sure, but I'll probably do it tomorrow
[23:24] <NCommander> With a little luck, I should be able to do all 26 rebuilds tonight
[23:24] <DktrKranz> with the hope there's no weird dependency chain to be followed
[23:25] <NCommander> Well, 26 sounds about right
[23:25] <NCommander> We can follow up by a removal of gnat-4.1
[23:25] <NCommander> (cruft busting at its best)
[23:26] <DktrKranz> in order to avoid this again :)
[23:27] <NCommander> it will happen with gnat-4.4 again -_-;
[23:27]  * DktrKranz thinks we should define a strategy to avoid cases like this
[23:27] <NCommander> Well, we need to binary rebuild everytime a new gnat hits the repo
[23:28] <NCommander> That can't be avoided
[23:28] <DktrKranz> we imported a bad transition we couldn't manage in time for hardy
[23:29] <DktrKranz> well, doing rebuilds is not a problem, real issues are when transitions are complex like this one (code change, API break, whatever) and Debian nor upstream is not of aid
[23:29] <NCommander> yeah well, at least its only 26 packages, and the changeset is managible
[23:32] <NCommander> libxmlada done