[00:05] <lamont> doko: any thoughts on bug 873515?
[01:41]  * hyperair groans. irssi is so hard to use now that my alt+` key has been hijacked by unity.
[01:54] <TheMuso> hyperair: Working here for me in unity-2d.
[01:55] <hyperair> TheMuso: alt-grave is getting in my way =\
[01:55] <hyperair> TheMuso: alt-grave is my keybinding for active-window
[01:55] <hyperair> active_window i mean
[01:56] <hyperair> and typical unity style, it's beautifully hardcoded inside the code so i can't disable it
[01:59] <TheMuso> Ah ok.
[05:18] <pitti> SpamapS: for important ones I think we can be a little more lenient, because a lot more devs are running -proposed as well now and report problems; but in general the standard rules apply
[05:37] <didrocks> good morning
[06:30] <dholbach> good morning
[06:32] <pitti> cjwatson: is someone already merging dpkg? if not, want me to?
[06:47] <slangasek> pitti: cjwatson has said he's taking care of it
[06:47] <pitti> slangasek: ok, thanks
[06:47] <slangasek> as there are bits that need reverting and he knows what they are, I'd wait for him
[07:12] <cousin_luigi> hello
[07:15] <siretart> err, do we officially support natty->oneiric upgrades? I was under the impressen not, but bug #859373 seems to imply so.
[07:16] <geser> siretart: how else should an upgrade from natty to oneiric be done?
[07:18] <cousin_luigi> bbl
[07:21] <RAOF> siretart: We don't support maverick?oneiric upgrades (without going through natty), but how else would natty users be able to update? :)
[07:21] <siretart> geser: err, sorry. not enough coffee yet, today.
[07:21] <siretart> I mixed the order of natty and maverick
[07:25] <geser> :)
[07:30] <pitti> OdyX: cups should already recognize PPDs in /usr/share/ppd/; dh_pyppd putting PPDs into /usr/lib/cups/driver/ sounds seriously wrong, as PPDs are not drivers
[07:30] <OdyX> pitti: please amend the wikipage, I can't focus on that today (sorry).
[07:30] <pitti> OdyX: ah, sure
[07:31] <doko_> lamont, hmm, no, doesn't tell me much
[07:31] <OdyX> pitti: http://wiki.debian.org/Teams/Printing/RethinkingTheStack fwiw
[07:31] <pitti> OdyX: right, that's what I'm reading ATM
[07:32] <OdyX> great; thanks for your proofreading !
[07:37] <pitti> OdyX: done, left some remarks there; the stuff that I don't commented on looks good to me; thanks!
[07:45] <doko_> barry, ^^^ bug bug 873515 ?
[07:53] <doko_> lamont, hmm, can't see it on osageorange anymore
[08:33] <OdyX> pitti: now that I got drawned into looking into this; will Cups look in /usr/share/ppd/compressed/* or only under /usr/share/ppd/ ?
[08:46] <pitti> OdyX: all subdirs; there are already a few
[08:46] <OdyX> pitti: hmm. Does it look for "compressed" PPDs ?
[08:46] <OdyX> pitti: it doesn't seem to, at least here.
[08:47] <pitti> OdyX: perhaps it additionally needs the /usr/lib/cups/driver/foomatic-db-compressed-ppds driver?
[08:47] <pitti> OdyX: I had assumed that foomatic-db-compressed-ppds actually shipped somethign like *.ppd.gz
[08:47] <pitti> but it doesn't seem to
[08:48] <pitti> so perhaps I misunderstood this package entirely then
[08:48] <OdyX> pitti: foomatic-db-compressed-ppds is a pyppd-compressed archive of PPDs
[08:48] <OdyX> pyppd creates a python script with an embedded base64'ed xz-archive
[08:48] <OdyX> then you can "execute" it to either get the list or extract a specific PPD
[08:51] <OdyX> that's probably why tkamppeter put the compressed PPDs as "Cups drivers" at the first place.
[09:05] <tkamppeter> pitti, OdyX, CUPS searches /usr/share/ppd recursively for ready-made PPDs, uncompressed or single PPD file gzipped, it searches /usr/lib/cups/driver/ for executables which are PPD generators ("<excutable> list" has to list all PPDs the generator is capable to generate, <executable cat <PPD UIRI>" generates the requested PPD on stdout), and it searches /usr/share/cups/drv/ for .drv files, which are source files for CUPS' PPD compiler, pp
[09:05] <tkamppeter> dc. All this CUPS reports as available PPDs (via "lpinfo -m" or equivalent IPP requests from printer setup tools).
[09:06] <OdyX> tkamppeter: okay, is there a reason "PPD generators" are cups-specific ?
[09:10] <tkamppeter> OdyX, no. If they do not link against libcups they work perfectly well with no piece of CUPS installed. A non-CUPS printer setup tool (does such a thing exist as an upstream-maintained free software?) has only to find all the PPD generators, and run them with 'list' and 'cat' as described. PPDs itself can be used with non-CUPS spoolers using foomatic-rip.
[09:10] <OdyX> tkamppeter: couldn't they be shipped under /usr/share/ppd/generators/ and have cups look there then ?
[09:12] <OdyX> .oO(Especially when the content is not architecture-specific (/usr/lib/). )
[09:12] <tkamppeter> OdyX, this would require CUPS to be patched, then better symlink to /usr/lib/cups/driver. Another problem is that CUPS produces error messages when anything which is not .ppd or .ppd.gz is in the /usr/share/ppd/ tree.
[09:13] <tkamppeter> OdyX, how are non-CUPS Debian users setting up printers? Are there special tools which they use?
[09:14] <tkamppeter> OsyX, and which non-CUPS spoolers are actively maintained and supported under Debian?
[09:14] <OdyX> tkamppeter: honestly, I don't really know (nor care), but I just feel that putting non-cups-specific PPDs under /usr/lib/ … cups/ is wrong and should be fixed.
[09:14] <OdyX> tkamppeter: I guess lpr is the only one, but don't know really.
[09:14] <directhex> hmph. what's the process for debugging audio issues?
[09:18] <tkamppeter> OdyX, which flavor of lpr, LPRng or some old LPD thingy?
[09:22] <OdyX> "lpr" was last uploaded as NMU and hasn't evolved since oldstable; "lprng" was maintainer-updated since stable but is "RFA", "gnuspool" is new to wheezy
[09:23] <OdyX> tkamppeter: that's not important I'd say; what stays is that Debian hasn't taken a decision to go Cups-only (and will probably not), so I'm very fine to drop PPDs in favor of pre-processed drivers, those should just be available (too) under a known place
[09:24] <tkamppeter> pitti, as you have passed cups and s-c-p to -updates, can you approve the next -proposed packages of cups and s-c-p today? Thanks.
[09:25] <tkamppeter> OdyX, what is "RFA"?
[09:25] <pitti> tkamppeter: cups yes; s-c-p is still in proposed; it's not a critical bug and had large changes, so we should wait the full 7 days
[09:26] <OdyX> tkamppeter: "request for adoption", it's the step before "Orphaned"
[09:30] <tkamppeter> OdyX, so it means that it is unmaintained and Debian is searching for a maintainer?
[09:31] <OdyX> tkamppeter: RFA means it's maintained but the maintainer is looking out for someone to take over maintainership (There's no such thing as "Debian is searching" :->)
[09:34] <tkamppeter> OdyX, looking at downloadable gnuspool releases upstream, it seems that this is the most recent attempt to introduce a new printing system but the upstream authors have already given up again, as there is now one year without new releases.
[09:36] <OdyX> tkamppeter: yes, and ? My opinion is: if we can do non-cups-specifics, we should.
[10:01] <tkamppeter> OdyX, OK, so let us move the compressed PPDs into a CUPS-neutral place and symlink them to /usr/lib/cups/driver/
[10:11] <OdyX> tkamppeter: what about /usr/share/ppd/compressed/ + patching cups to avoid warnings there ?
[10:12] <tkamppeter> OdyX, would be a solution, pitti, WDYT?
[10:13] <tkamppeter> OdyX, did you say anything else in the last few minutes? I rebooted after my upgrade to Oneiric.
[10:14] <OdyX> tkamppeter: no
[10:25] <jkbys> pitti, could you take a look at bug 873401?
[10:26] <pitti> jkbys: I saw it, will have a look at some point
[10:26] <jkbys> pitti, thank you
[10:27] <Daviey> Has merges.ubuntu.com been updated for P-Series?
[10:28] <FourDollars> How to push this patch into SRU of 11.10 ? https://bugs.launchpad.net/ubuntu/+source/ibus-chewing/+bug/874028
[10:49] <tkamppeter> pitti, can accept the proposed SRU for bug 872527? Thanks.
[10:50] <pitti> yes, yes -- I don't run SRUs every hour, sorry
[10:51] <pitti> tkamppeter: done
[10:53] <tkamppeter> pitti, thanks.
[11:16] <OdyX> tkamppeter, pitti: we need to discuss this more in-depth; I'll send a mail to debian-printing@l.d.o CC'ing the maintainers of the various print spoolers we mentionned to gather more opinions.
[11:26] <lamont> doko_: you may need to reinstall one of the packages inside that chroot again
[11:26] <lamont> doko_: I don't remember if I left it broken or not
[11:30] <cjwatson> pitti: I'm a fairly substantial amount of the way through the dpkg merge now
[12:03]  * doko_ curses the libnih1 use of private glibc symbols
[12:05] <htorque> hello all! stuff uploaded to oneiric-proposed won't show up in precise, right?
[12:06] <infinity> htorque: Not by default, but you can request it to be copied over.
[12:06] <infinity> htorque: Though, usually, you want newer upstream versions in precise anyway.
[12:06] <htorque> infinity: thanks for the info :-)
[12:14] <pitti> htorque: in the first days, we'll copy oneiric-proposed to both -updates and precise (as long as the versions are equal and we are still frozen)
[12:14] <pitti> to ensure we don't drop patches
[12:15] <infinity> pitti: Yeah, but that "first few days" bit isn't exactly well-documented. ;)
[12:15] <infinity> It just sort of happens until it stops happening.
[12:16] <htorque> pitti: i just asked because i wanted to test the -proposed fix for bug 858056 and i'm already on precise on one system (don't ask why :P).
[12:16] <htorque> but the question is answered here: https://launchpad.net/ubuntu/+source/unity-lens-applications/+publishinghistory
[12:16] <pitti> htorque: ah, I copy stuff to -proposed after verification
[12:16] <pitti> i. e. at the same time as to -updates
[12:45]  * apw just tried to upgrade a natty box to oneiric using the popup box from update-manager, and it said that it couldn't do it cause i likely had unresolable package problems, any idea how to find out what the underlying packages even are
[12:48] <mvo> apw: could you pastebin your /var/log/dist-uprade/apt.log please?
[12:53] <apw> mvo, http://paste.ubuntu.com/707977/ ... note i am doing a dist-upgrade now to the latest natty packages to ensure its not related to that, just in case that has changed the log
[12:55] <sd_ubuntu__> Hi! I'm new at ubuntu community. Could I start a work with you?
[12:57] <OdyX> sd_ubuntu__: as in all free software communities: find an itch to scratch, then scratch it.
[12:59] <sd_ubuntu__> OdyX: but I read the code of conduct and it should collaborate. I just wanna help in something free that I received
[12:59] <sd_ubuntu__> OdyX: but I'd like to know where it nedds more help
[12:59] <sd_ubuntu__> (sorry if my english is not good)
[13:00] <sd_ubuntu__> *we should collaborate
[13:01] <apw> sd_ubuntu__, there really is everything available, and all of it needs help, so it really is about what interests you as you won't stay doing something for nothing that you don't like doing
[13:03] <sd_ubuntu__> apw: ok. I'd like to packaging ...
[13:03] <mvo> apw: so it seems its rather unhappy about the flashplugin, if you provie the /var/log/dist-upgrade/*apt-clone* file I will try to reproduce and see if I can find a global solution
[13:03] <sd_ubuntu__> apw: but I think is a work to do together...
[13:04] <apw> mvo, on it
[13:06] <apw> mvo, in pm
[13:08] <mvo> thx
[13:20] <Daviey> slangasek: We are getting a flurry of bugs regarding the samba issue.
[13:28] <jdstrand> @pilot in
[13:59] <Daviey> slangasek / infinity: 28 dupes, bug 862129
[14:15] <bdrung> how long will precise be frozen?
[14:16] <cjwatson> bdrung: shouldn't be too much longer, but dpkg does need to build
[14:17] <bdrung> cjwatson: ETA? hours or days?
[14:17] <cjwatson> dunno
[14:17] <cjwatson> not really in the mood for a mad rush and time estimates and all that at the moment, after the release sprint
[14:19] <cjwatson> apw: are you folks expecting to upload a new linux-libc-dev before precise opens for general uploads?
[14:21] <apw> cjwatson, i was expecting a kernel upload shortly, but i am currently unsure if the current kernel is tested
[14:22] <apw> i assume that the tool chain as it is now, wasx built with the old one too
[14:22] <cjwatson> yes
[14:22] <cjwatson> well, um
[14:22] <cjwatson> thinking about it I don't know what was in the PPA it was built in
[14:22] <cjwatson> https://launchpad.net/~ubuntu-toolchain-r/+archive/ppa doesn't have a kernel
[14:23] <cjwatson> and no extra dependencies there, so yeah, it would have built against oneiric's kernel
[14:23] <apw> cjwatson, in theory at least linux-libc-dev is backwards compatible so i don't think it matters ...
[14:24] <cjwatson> I don't mind leaving it for later
[14:25] <apw> cjwatson, yeah i don't think there is sufficient difference to worry about, and we'll have cycles round compiler and kernel in the next weeks
[14:26] <apw> we should have a get together at UDS with doko to work out what the best order is and how we can achieve that in combination with the toolchain pre-preparation
[14:29] <cjwatson> bdrung: ... also I plan to knock off early today and vanish for the weekend, so if we're opening, somebody else is going to do it :-)
[14:31] <pitti> bdrung: note that you can already upload, if you want to get stuff off your hard disk
[14:31] <bdrung> pitti: will that end up in the new queue?
[14:31] <pitti> bdrung: no, in unapproved
[14:32] <pitti> bdrung: https://launchpad.net/ubuntu/precise/+queue?queue_state=1
[14:32] <bdrung> ah, ok
[14:32] <pitti> bdrung: we'll flush that once precise opens
[14:32] <pitti> bdrung: unless it's actually NEW, of course (state=0)
[14:42] <ntr0py> Is there a way to get Gnome3 to use BGR instead of RGB subpixel rendering?
[14:48] <debfx> pitti: would you approve bug #873396 for a SRU?
[15:04] <lamont> is there some way under compiz to convince it that just because I launched a terminal window, does not mean that I want it to have focus?
[15:04] <doko> kees, I don't understand yet https://launchpadlibrarian.net/82793515/buildlog_ubuntu-precise-armel.eglibc_2.15~pre1-0ubuntu1_FAILEDTOBUILD.txt.gz
[15:05] <doko> from https://launchpad.net/~ubuntu-toolchain-r/+archive/test/+packages
[15:20] <kees> doko: hunh. looks like a static build? the _guard is the value that the stack protector looks for when checking for overflow, which means it wasn't included in the linkage...
[15:20] <kees> doko: I wonder what changed
[15:22] <doko> kees, yes, but anything is built with -fno-stack-protector -U_FORTIFY_SOURCE
[15:23] <kees> doko: yeah, that's really odd
[15:23] <kees>  /build/buildd/eglibc-2.15~pre1/resolv/gethnamaddr.c:974: undefined reference to `__stack_chk_guard'
[15:24] <kees> what's actually on that line of the code?
[15:24] <kees> I wonder if they started using the _guard for non-stack purposes
[15:24] <doko> and apparently it's ARM only
[15:40] <davmor2> any audio guru's about?  I have a huge issue on oneiric fresh install,  skype/mumble/voip I sound like a chipmunk worked perfectly in natty :(
[15:55] <directhex> dholbach, off the top of your head, do you know what software is used for the irc bot during UDW? the one that collects questions in one channel, which the session leader can then page through & have show up in the moderated channel?
[15:56] <dholbach> jussi, ^ do you know?
[15:59] <cjwatson> have fun
[16:01] <cjwatson> oh dear, sync-source is busted
[16:01] <pitti> yay precise
[16:11] <Daviey> erm, is -changes mailing list working properly?
[16:12] <Daviey> Ah, i'm being a bit unfair, it was only shown 9 mins ago.
[16:12] <Daviey> Accepted
[16:21] <jussi> directhex: I dont know, but nhandler did a lot of work with it. I suspect it was rbot, but I could be totally off with that. Im pretty sure its not supybot though.
[16:35] <frewsxcv> is there any reason why ubuntu hasn't updated their releases in their rsync mirror?
[16:37] <cjwatson> frewsxcv: could you be more specific?
[16:39] <dobey> should We bug someone to get a couple SRUs that were supposedly going to be 0-day, copied over to oneiric-updates? :)
[16:39] <cjwatson> frewsxcv: I'm not seeing anything obviously out of date ...
[16:39] <frewsxcv> http://mirrors.kernel.org/ubuntu-releases/oneiric/ pulls from rsync://<country-code>.archive.ubuntu.com/releases
[16:39] <frewsxcv> as does my mirror http://mirrors.calpoly.edu/ubuntu-releases
[16:40] <cjwatson> ubuntu-releases should be pulling from rsync.releases.ubuntu.com, not rsync.archive.ubuntu.com
[16:40] <cjwatson> I have no idea what <countrycode>.archive.ubuntu.com/releases might happen to point to :-)
[16:42] <cjwatson> the primary rsync mirror of releases definitely has 11.10 on it
[16:42] <frewsxcv> cjwatson: what is the rsync module for rsync.releases.ubuntu.com
[16:42] <cjwatson> releases, I believe
[16:42] <cjwatson> #ubuntu-mirrors might be able to help more with mirroring specifics
[16:43] <cjwatson> (since there may be something better than you pulling directly across the Atlantic; I can't see what us.releases.ubuntu.com::releases/ currently has since it's hit its client limit
[16:43] <cjwatson> )
[16:45] <frewsxcv> thanks cjwatson
[16:57] <smoser> @pilot in
[17:48] <smoser> TheMuso, mdeslaur i think that merge request at https://code.launchpad.net/~psusi/ubuntu/natty/gnome-power-manager/fix-duplicate-battery/+merge/67466 should be moved to 'merged', right?
[17:49] <smoser> as it seemed to be only relevant for natty and is fixed there.
[17:52] <mdeslaur> smoser: yep
[17:52] <mdeslaur> smoser: I don't have the required magic wand to change that
[17:52] <smoser> nor do i
[17:53] <mdeslaur> :(
[17:53] <smoser> i guess maybe that is bug 728012
[17:59] <mdeslaur> smoser: ah, yes, thanks for the bug link
[18:05] <jdstrand> @pilot out
[18:05] <jdstr> @pilot out
[18:11] <Quintasan> pitti: Can I have you accept two uploads for bug #872506 ?
[18:12] <jdstrand> Quintasan, pitti: hold on on that one
[18:13] <jdstrand> this needs patches for a security update
[18:13] <Quintasan> jdstrand: Which one exactly?
[18:13]  * jdstrand is getting them
[18:14] <Quintasan> jdstrand: Which package needs patches? https://wiki.kubuntu.org/Kubuntu/Ninjas/Packaging <- we have this many :)
[18:14] <jdstrand> kde4libs
[18:14] <Quintasan> I see
[18:15] <debfx> jdstrand: which security update? bug #857437?
[18:16] <jdstrand> debfx: yes
[18:16] <jdstrand> I attached the debdiff I am using for 4.7.1 to the bug
[18:16] <debfx> jdstrand: I'm pretty sure the fix is included in 4.7.2
[18:16] <jdstrand> I checked the debdiff in LP. let me recheck
[18:17] <Quintasan> quick google shows that 4.7.2 has it
[18:17] <jdstrand> hmm, http://launchpadlibrarian.net/82652015/kde4libs_4%3A4.7.2-0ubuntu1_4%3A4.7.2-0ubuntu2.diff.gz is less than complete
[18:18] <jdstrand> Quintasan, debfx: ah, well if it has them, please respond to my comment in the bug and ignore me :)
[18:18]  * Quintasan researches futher
[18:19] <debfx> jdstrand: that's just a follow-up upload, http://launchpadlibrarian.net/82564105/kde4libs_4%3A4.7.1-0ubuntu3_4%3A4.7.2-0ubuntu1.diff.gz is the 4.7.1->4.7.2 diff
[18:19] <jdstrand> oh, I missed that
[18:19] <jdstrand> let me look
[18:21] <jdstrand> ok, yes, it has it
[18:21] <jdstrand> pitti, debfx, Quintasan: ignore me. 4.7.2 is fine
[18:32] <broder> slangasek: oh geez. i think i figured out what vmware is doing that's breaking everything
[18:32] <broder> http://paste.ubuntu.com/708153/
[18:38] <slangasek> broder: right, yes, that was actually clear to me; sorry for not communicating it
[18:39] <broder> slangasek: ok; i didn't know if you had seen the actual code in question or not. unfortunately, i don't see any good way to trick the installer into doing something reasonable
[18:39] <slangasek> (the nature of the damage to rc6.d was apparent on first glance)
[18:39] <slangasek> no, there's no good way to trick it
[18:39] <slangasek> it needs to be stabbed in the face
[18:40] <slangasek> calling insserv is not an acceptable thing for any package to do
[18:40] <broder> will my system still function if i move the insserv binary out of the way?
[18:41] <slangasek> AFAIK yes
[18:41] <slangasek> since insserv is only meant to be called by update-rc.d, and only if the .legacy-bootordering flag is *not* set
[18:48] <SpamapS> hmm... since ScottK is taking a break, who will take charge over backports?
[18:53] <Laney> the rest of the team
[18:53] <Laney> but it would be good to have another administrator
[18:53] <Laney> someone needs to make oneiric-backports ...
[18:53]  * Laney does
[18:57] <Laney> there we go
[20:11] <smoser> pitti, wonder if you're ok with me uploading https://code.launchpad.net/~evfool/jockey/stringfixes/+merge/73737 just to finish it off ?
[20:14] <smoser> actually, never mind. ill let you handle that.