[01:54] <psusi> I've noticed a rash of bug reports lately where grub-efi fails to install because it depends on a version of grub-efi-amd64 that was superseded during raring development, and is newer than the version of grub2-efi that is present in the quantal, which is being installed.  anyone have a clue as to how the hell this could be?
[02:02] <Snow-Man> can't install postgresql 9.2 on raring?  really?
[02:06] <manchicken> Snow-Man: That would suck...
[02:06] <infinity> Hrm?
[02:06] <infinity> It's not in raring at all, is it?  How does that "suck"?
[02:07] <manchicken> I'm mistaken, I thought 9.2 came out earlier than it appears that it did.
[02:07] <Snow-Man> meh
[02:07] <Snow-Man> the issue is this postgresql-common foolishness.
[02:08] <infinity> Feel free to ask pitti when he intends to transition Ubuntu (and Debian) to 9.2, but 9.1 is what we're shipping right now.
[02:08] <Snow-Man> the problem is that the packages on apt.postgresql.org won't work because he added a 'Breaks' against logrotate >= 3.8
[02:09] <Snow-Man> presumably because the package doesn't do the right thing w/ it
[02:09]  * Snow-Man is not impressed
[02:09] <infinity> Snow-Man: I'm inclined to say that apt.postgresql.org is wildly out of scope for this channel.
[02:09] <Snow-Man> infinity: bah, #postgresql-apt was overly quiet. :)
[02:10] <Snow-Man> and pitti, who manages both (along w/ Myon) isn't in #postgresql-apt, so I tend to discuss such things w/ him here.
[02:10] <infinity> apt.psql.org doesn't mention pitti at all under contacts...
[02:11] <Snow-Man> eh, blame magnush
[02:11] <infinity> Anyhow, it also doesn't have builds for >> precise, so I suspect there's a bit of "get to keep both pieces" going on here.
[02:12] <infinity> Or, you can report the issues to them.  Not much help to discuss it here.
[02:12] <Snow-Man> yes, I shall discuss it with them and point out this is why we *should* having PG packages for all of the Ubuntu releases, not just LTS.
[02:13] <infinity> Well, it would be nice if experimental and a PPA were kept up-to-date, instead of some strange outside apt repo, but meh.
[02:14] <Snow-Man> they deprecated the PPA in favor of the "official" apt.p.o, actually
[02:15] <Snow-Man> which works for me, tbh, tho I could see how some might prefer it the other way.
[02:15] <infinity> I don't use either, I just wonder why people don't like to leverage existing resources.
[02:21] <ScottK> IIRC, pitti has a PPA that he generally keeps up to date.
[02:24] <Snow-Man> ... and that's the one which is supposed to be deprecated by apt.p.o existing.
[02:32] <ScottK> Right.
[02:33] <ScottK> In pitti's PPA he did provide packages for all releases.  Looks like they are just doing the LTS releases.
[02:33] <ScottK> That's definitely the place to complain.
[08:03] <Noskcaj> kirkland_, roaksoax: you guys can't ignore me forever
[13:06] <maxiaojun> https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1035136
[13:09] <maxiaojun> I find that "/usr/lib/lsb/initdutils.py" is a python 2 script ...
[13:09] <maxiaojun> binary package concerned is lsb-core
[13:27] <ogra_> maxiaojun, python2 was still the default in 12.10 so it shouldnt matter
[13:29] <maxiaojun> InterpreterPath: /usr/bin/python3.2mu
[13:29] <maxiaojun> ProcCmdline: /usr/bin/python3 /usr/lib/lsb/install_initd /etc/init.d/logmein-hamachi
[13:29] <maxiaojun> from the bug report
[13:31] <maxiaojun> head install_initd
[13:31] <maxiaojun> gives #! /usr/bin/python3 on raring at least
[13:32] <maxiaojun> and install_initd imports initdutils
[13:34] <ogra_> well, feel free to fix it then :)(
[13:38] <maxiaojun> i can run 2to3, but not savvy enough to verify whether the whole lsb stuff is working afterwards
[13:39] <maxiaojun> and i do not have quantal box
[13:40] <ogra_> use a cheoor ;)
[13:40] <ogra_> *chroot
[13:45] <maxiaojun> dummy question, is it considered better to link a branch rather than submit a patch ?
[13:53] <ogra_> infinity, i see some very weird behavior of copy_exec with the ubuntu-touch-generic-initrd package ....  comparing https://launchpadlibrarian.net/143820277/buildlog_ubuntu-saucy-armhf.ubuntu-touch-generic-initrd_0.5_UPLOADING.txt.gz with http://paste.ubuntu.com/5813896/ does not seem to take the linked adbd libs into account
[14:07] <maxiaojun> ok, all the files in /usr/lib/lsb is in python2 ...
[14:08] <maxiaojun> but install_initd  lsbinstall  remove_initd has #! /usr/bin/python3
[14:10] <maxiaojun> can Matthias Klose <doko@ubuntu.com> make a working change to python 3?
[14:28] <siretart> maxiaojun: so you want /usr/bin/python to point to python3?
[14:29] <maxiaojun> absolutely not
[14:29] <siretart> maybe you can clarify your question then
[14:29] <maxiaojun> i want lsb package be correctly ported to python 3
[14:30] <siretart> doesn't lsb mandate python2? (not sure here)
[14:30] <maxiaojun> if you don't mind, install "lsb" package and check /usr/lib/lsb
[14:31] <tumbleweed> the interface to lsb scripts is identical no matter whether it's python2 / 3
[14:31] <maxiaojun> you will find that all scripts under /usr/lib/lsb/ is in Python 2(contains print statement not print function, for example)
[14:31] <tumbleweed> the lsb python modules are considered private, aren't they?
[14:31] <tumbleweed> oh
[14:31] <maxiaojun> but install_initd  lsbinstall  remove_initd
[14:32] <maxiaojun> all have "#! /usr/bin/python3" at the beginning while initdutils.py doesn't specify
[14:32] <tumbleweed> initdutils.py sounds like a module, not a script
[14:32] <ogra_> maxiaojun, is that the quantal binary ?
[14:33]  * ogra_ is pretty sure slangasek only ported lsb to py3 in saucy
[14:33] <tumbleweed> IIRC we ported it earlier
[14:33] <maxiaojun> i'm on raring but i guess quantal is almost identical in this issue
[14:33] <tumbleweed> it was the thing we ported, to get python3 on the CD
[14:33] <ogra_> tumbleweed, well, the changelog disagrees
[14:33] <maxiaojun> http://changelogs.ubuntu.com/changelogs/pool/main/l/lsb/lsb_4.0-0ubuntu27/changelog
[14:33] <tumbleweed> it was ported and reverted at least once
[14:33] <ogra_> ah, reaverted
[14:34] <maxiaojun>   * Use python3 instead of python2 (again). at version ubuntu22
[14:34] <tumbleweed> 4.0-0ubuntu13 (oneiric)
[14:34] <maxiaojun> before quantal
[14:35] <maxiaojun> lsb (4.0-0ubuntu22) quantal; urgency=low
[14:38] <maxiaojun> the end result is that scripts in /usr/lib/lsb just won't at all, crash at startup
[14:38] <maxiaojun> just won't work
[14:39] <tumbleweed> right, so they may need to be ported to python3
[14:39] <tumbleweed> but clearly nobody else is using them
[14:40] <ogra_> not even us :)
[14:40] <maxiaojun> so i only noticed this through this bug: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1035136
[14:41] <maxiaojun> i do not use any lsb software, but i guess we shouldn't close the door
[14:42] <ogra_> yeah, definitely worth fixing (since lsb-core is in main) but given that nothing in ubuntu is using lsb-core by default thats not really high prio
[14:43] <maxiaojun> can we guarantee that /usr/bin/python points to python 2 in quantal and raring
[14:44] <ogra_> definitely in quantal
[14:44]  * ogra_ forgot about raring
[14:44] <tumbleweed> we're pretty sure that /usr/bin/python isn't going to point to python3 ever
[14:45] <tumbleweed> the thought seems to be that python4 will be around before 2 goes away, or something like that
[14:45] <nemo|omen> by default :-)
[14:45] <maxiaojun> yes, i actually wonder whether raring has python 2 pre-installed
[14:46] <maxiaojun> if we do have python 2, then let the scripts declare themselves as python 2 and problem solved
[14:49] <maxiaojun> "The Ubuntu 13.04 image continues this process, although we will not be able to convert everything to Python 3 for Ubuntu 13.04 final image."
[15:14] <maxiaojun> anyone have an idea whether python 2 is pre-installed on raring?
[15:24] <ScottK> For clarity: /usr/bin/python will point to python2.7 for the foreseeable future (not python2, although /usr/bin/python2 also exists).
[15:51] <maxiaojun> if it is there for raring, then just change the shebang may be sufficent for the bug. for saucy you seem to introduce lsb 4.1, then it is good chance to root fix this issue also
[17:53] <infinity> ogra_: Weird...
[20:56] <mwhudson> hm
[20:56] <mwhudson> i guess i'll google this myself
[20:56] <mwhudson> but how do i build -dbgsym packages myself?
[20:58] <jtaylor> a normal package built with DEB_BUILD_OPTIONS=nostrip will be the same
[20:58] <jtaylor> you may want to use "nostrip noopt" to disable optimization
[20:59] <mwhudson> no, i'm benchmarking, not debugging :)
[20:59] <mwhudson> ah i just install pkg-create-dbgsym and i get ddebs by magic?
[21:02] <mwhudson> although...
[21:03] <mwhudson> apache2 appears to be trying to build a -dbg package anyway
[21:03] <mwhudson> but for some reason it's not appearing
[21:08] <mwhudson> oh, rules stuff that prevents it from being built