[07:09] <dholbach> good morning
[07:28] <gotwig> I want a feature freeze exception for this commit for gnome control center: http://git.gnome.org/browse/gnome-control-center/commit/?id=45ba8e89e86397df912e07df14d76373f1c7e7af.
[07:29] <gotwig> this fixes the error message from firewallid for finding network printers in Printers panel under GNOME Shell
[10:00] <Laney> https://launchpad.net/ubuntu/+source/balloontip/2008.11.14-0ubuntu2
[10:00] <Laney> should we be uploading for that?
[10:01] <Laney> It didn't actually add any new dependencies.
[10:15] <geser> is it perhaps related to the changes for -java packages? (and got matched by looking for source packages building -java packages)
[12:15] <marga> So, I have prepared a package that fixes some bugs for "myunity".  How do I go about getting sponsoring for it?
[12:28] <geser> !sponsorship
[12:29] <geser> in short: attach a debdiff to the bug and subscribe "ubuntu-sponsors" to it (or prepare a bzr branch if you prefer and file a merge-proposal)
[12:41] <marga> geser, ok, thanks.
[12:41] <marga> I had done the debdiff part but didn't know about subscribing sponsors to it.
[12:43] <geser> hmm, "myunity" doesn't seem to be in quantal anymore (see https://launchpad.net/ubuntu/quantal/+source/myunity/3.1.5-0ubuntu1)
[12:44] <marga> ugh
[12:44] <marga> Can it still be uploaded to precise?
[12:44] <geser> as a SRU? sure
[12:44] <geser> !SRU
[12:44] <marga> tnx
[12:45] <geser> the sponsoring is the same, just a little bit more paper work on the bug itself
[12:46] <marga> Yes, I get it.
[12:46] <marga> :-/
[12:49] <marga> Is it the same process if the current version is already in precise-backports?
[12:51] <geser> hmm, good question
[12:53] <geser> ScottK (or any other Ubuntu backporter): how to update a package in -backports when the package got deleted in the devel series?
[13:52] <shadeslayer> I'm trying to figure out how to make a portion of my postinst script run only when the package is installed the first time, so can I just check if $2 is zero and run my commands?
[13:53] <shadeslayer> or is there another/simpler way to do it
[13:54] <marga> shadeslayer, as far as I know, it's how you said.
[13:54] <shadeslayer> alright, I'll go with taht for now
[13:54] <Laney> $1 is configure and $2 is empty, yeah
[13:54] <shadeslayer> *that
[13:54] <Laney> make sure you don't break on remove/install though
[13:55] <shadeslayer> my script calls dpkg-divert, so I don't want to run that on upgrade
[13:55] <shadeslayer> Laney: oh?
[13:55] <Laney> you need to undo whatever it is you do on remove
[13:56] <shadeslayer> right ... I don't handle that atm
[13:56] <shadeslayer> had that on my todo for tomorrow
[13:59] <shadeslayer> alright, thanks :)
[14:00] <geser> Laney: as you also deal with backports, do you know how to update a package in precise-backports which got deleted from quantal?
[14:01] <Laney> not sure we have a precedent for that
[14:01] <marga> ouch
[14:01] <Laney> ScottK: ?
[14:02] <marga> The package is myunity.  It got deleted because it doesn't work with the unity version in quantal.  But it works with precise, oneiric and natty.
[14:02] <marga> I have prepared an upload with 3 patches for 3 bugs.
[14:05] <Laney> I think we could probably do it
[14:06] <Laney> do the bug fixes apply to all releases we backported to?
[14:10] <xnox> =( i want myunity =(
[14:53] <ScottK> geser: That's a really good question.  I don't recall it coming up before.  Are you talking about a new version or fixing a bug with the existing version in backports?
[15:41] <l3on> Hi all.. why if I use bzr lp-propose it files my propose to being merge into debian ?
[15:41] <l3on> example: https://code.launchpad.net/~l3on/ubuntu/quantal/smbldap-tools/merge/+merge/125754
[16:33] <mfisch> MOTUs, a process question: if Ubuntu and Debian are both out of date for a package (newer version upstream), is there any link between Ubuntu and Debian updating?  What I mean is if we update a package is it up to Debian to also do the update or would we (Ubuntu) send our debdiff and/or patches to debian?
[16:33] <micahg> mfisch: ideally, the update could be pushed through Debian (but the maintainer has to be willing to update)
[16:33] <micahg> mfisch: which package?
[16:33] <tumbleweed> syncing things from Debian is easy
[16:34] <tumbleweed> getting things from Ubuntu into debian tends to be a little bit harder
[16:34] <micahg> (not everyone wants to upload stuff to experimental during the freeze either)
[16:35] <Laney> weirdos, experimental is where all the fun happens
[16:36] <mfisch> micahg: just in general, I was looking at the list of outdated packages and wondering the process
[16:36] <micahg> mfisch: yeah, so best is to have an update in Debian (if you have team membership there or NMU if the package update qualifies)
[16:37] <mfisch> micahg: here's a simple one, "six", from this list: http://people.canonical.com/~platform/desktop/desktop.html
[16:37] <micahg> mfisch: that's cjwatson's package and he's usually on top of stuff...probably not updating for a reason at this point
[16:37] <mfisch> so ideally colin (the maintainer) or someone else would push to debian first
[16:38] <micahg> but speaking in general, yes
[16:38] <micahg> we've got upgrade requests here: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=upgrade-software-version
[16:39] <micahg> but since we're past feature freeze, most are unlikely to be addressed unless needed for quantal specifically
[16:39] <Laney> we can upload to backports now :-)
[16:39] <micahg> well, in general, most are unlikely to be addressed unless it happens in Debian first
[16:40] <Laney> (someone should make the q-backports project)
[16:40] <micahg> Laney: indeed, was waiting for midori to get uploaded to Debian to try it
[16:40] <micahg> I was going to create the project
[16:40] <mfisch> micahg: so for someone looking to get experience in this process (updating packages) is that bug list a good place to start?
[16:40]  * micahg isn't sure he has enough permissions to add it to ubp though
[16:41] <Laney> there is a list of ubuntu only packages which are outdated
[16:41] <micahg> mfisch: yeah, not a bad place to start, but most of those should probably be done in Debian
[16:42] <micahg> Laney is referring to http://qa.ubuntuwire.com/uehs/no_updated.html
[16:42] <micahg> that list isn't Ubuntu only though which is weird...
[16:42] <Laney> possibly is it pointing at testing
[16:42] <micahg> yeah
[16:42] <cjwatson> mfisch: Oh, I only missed that because apparently I didn't have a watch file
[16:42] <cjwatson> So it didn't show up on http://qa.debian.org/developer.php?login=cjwatson%40debian.org
[16:42] <mfisch> cjwatson: I just mailed you one ;)
[16:43] <cjwatson> Wait, I *do* have a watch file
[16:43] <cjwatson> What's going on
[16:43] <cjwatson> And it works with uscan --verbose --report
[16:43] <mfisch> cjwatson: six doesn't have a watch file, not one that I see
[16:43] <cjwatson> Oh well, I'll update the package
[16:43] <mfisch> cjwatson: I did write one
[16:43] <cjwatson> Heh
[16:43] <Laney> doesn't have one in the archive, anyhow
[16:43] <cjwatson> I committed it to bzr a while back
[16:43] <cjwatson> But I never uploaded it
[16:43] <cjwatson> timestamp: Sun 2012-01-22 15:14:03 +0000
[16:43] <mfisch> ah
[16:54] <cjwatson> So how did ~platform/desktop/desktop.html find the new upstream for six if not from a watch file, incidentaly?
[16:54] <cjwatson> *incidentally
[16:58] <mfisch> good question
[16:59] <dupondje> I know this isn't really the right place, but has anyone an idea about the following stacktrace: http://pastebin.com/raw.php?i=28BEEaS3 ?
[17:22] <jtaylor> someone familiar with php packaging?'
[17:25] <jtaylor> nevermind not php's fault
[17:26] <jtaylor> if a core-dev is bored I might need some rebuilds
[20:25] <geser> ScottK: marga wants has 3 patches for myunity ready, but myunity isn't in quantal anymore so asked instead if the version in precise-backports can still be fixed
[20:43] <micahg> quantal-backports registered
[20:45] <Laney> nice
[20:46] <mfisch> micahg: Here's my sync request: https://bugs.launchpad.net/ubuntu/+source/xfonts-mathml/+bug/1054324
[20:47] <mfisch> we have no Ubuntu specific changes and it builds fine
[20:47]  * mfisch fixes priority
[20:47] <micahg> mfisch: so, first, you want to use requestsync to request syncs
[20:47] <ScottK> geser: It seems reasonable to allow fixes like that.
[20:48] <mfisch> micahg: ok, it looked to be optional in the wiki, but I can redo with that, no problem
[20:48] <micahg> mfisch: second, we do have a diff with the package
[20:49] <mfisch> micahg: oh, I was looking for patches, but yes there is a diff in the control file
[20:49] <micahg> mfisch: you can cut/paste from requestsync for this one and use it in the future, it fills in the changelog from the differences automatically as well as warning you if there's an Ubuntu diff, use the -e option if you need a feature freeze exception
[20:49] <geser> ScottK: as direct upload to precise-backports? and can it that be backported from precise-backports to oneiric-backports if needed/wanted?
[20:50] <Laney> yeah
[20:50] <Laney> do the bugs affect the released version too?
[20:50] <Laney> (you know where this is going)
[20:50] <micahg> mfisch: PTS page is useful as well: http://packages.qa.debian.org/x/xfonts-mathml.html
[20:50] <micahg> mfisch: you'll also want to make sure that our font packages transitioned like the Debian ones did
[20:50] <geser> Laney: no idea, better ask marga about it/the patches
[20:51] <Laney> filling the backports bug is probably a good start
[20:51] <geser> marga: ^^
[20:51] <mfisch> micahg: what do you mean by "transitioned"?
[20:52] <micahg> mfisch: that we have the new binary packages that the control file (and the built binaries) will expect
[20:52] <ScottK> geser: Definitely.
[20:56] <micahg> mfisch: the package renames in version 6
[20:58] <mfisch> micahg: I don't see a renaming, where are you looking?
[20:59] <micahg>     - otf-stix -> fonts-stix and moved in Recommends because STIX fonts
[20:59] <micahg>       was now officially released (not beta version).
[20:59] <micahg>     - ttf-lyx -> fonts-lyx in Recommends. (Closes: #676489, #676492, #676497)
[21:00] <mfisch> ah, I was looking at the uupdate processed version, let me get a clean copy
[21:01] <micahg> mfisch: try grab-merge
[21:01] <mfisch> micahg: right, so Ubuntu still is using the old package names
[21:02] <micahg> mfisch: not in the current Ubuntu version, but what is in the Ubuntu archive (you can use rmadison to check that)
[21:02] <mfisch> micahg: grab-merge is very useful, thanks
[21:03] <micahg> *current Ubuntu xfonts-mathml version, but what font binaries are in the archive
[21:04] <mfisch> micahg: yep, there they are for quantal
[21:06] <micahg> mfisch: ok, then the next questions are is it just bug fixes or does it need a feature freeze exception? (build system changes usually need a feature freeze exception just to show that the binary still has the desired contents)
[21:07] <mfisch> micahg: it contains bug fixes
[21:07] <micahg>    * Introduced dh_installxfonts now.
[21:08] <mfisch> micahg: also pitti's patch for the 0.4 version still should apply since the lyx fonts are not in main
[21:08] <micahg> IANA release team member, so not sure if that qualifies
[21:08] <mfisch> micahg: so you meant "only bug fixes"
[21:08] <mfisch> micahg: the answer to that is "no"
[21:09] <mfisch> micahg: actually you did ask it that way
[21:09] <mfisch> micahg: I misread
[21:09] <micahg> packaging corrections == bug fixes
[21:11] <micahg> packaging changes ~= features
[21:11] <mfisch> right
[21:12] <mfisch> adding dh_installxfonts to the rules file is more of a correction isn't it?
[21:14] <micahg> well, the rules file was changed from using ~10 dh statements, to just one
[21:15] <micahg> as I said, IANA release team member, maybe one of them can comment (I'd probably just ask in IRC if they want an FFe for this)
[21:16] <mfisch> let me properly file the syncrequest
[21:21] <micahg> mfisch: also, so, this is a merge, not a sync, since we need to keep the diff, it's generally good practice to ask the person who touched it last if they plan on working on it
[21:22] <micahg> this prevents duplication of work
[21:22] <mfisch> sync is only valid then if we have absolutely no changes?
[21:22] <micahg> or if the changes aren't needed anymore
[21:22] <Laney> sync means 'copy this package from somewhere else'
[21:22] <mfisch> I believe we still need the control file change
[21:25] <mfisch> micahg: so can I file a merge request, then take the debian version, make the control file change and build the package, I can then attach the debdiff from 6ubuntu1 to 4ubuntu1
[21:26] <micahg> mfisch: that debdiff and the one from the new debian package to the merged package (which the sponsor will apply to the Debian package before uploading)
[21:26] <mfisch> micahg: got it
[21:26] <mfisch> micahg: is there a special tool for merge requests?
[21:26] <micahg> mfisch: but ideally, before you started, you'd want to ask pitti if he was working on it
[21:27] <mfisch> micahg: ok
[21:27] <mfisch> micahg: in this case I'll go ahead since I'm learning the process and I'll email pitti a note
[21:27] <micahg> mfisch: no, I've kicked around the idea for one for a while, you could just use requestsync and edit it to say merge
[21:27] <mfisch> if he's doing it already, he can toss my work, no big deal
[21:27] <micahg> then remove ubuntu-sponsors until the debdiffs are attached
[21:28] <mfisch> micahg: ok
[21:28] <micahg> mfisch: also good to check on merges.ubuntu.com to see if anyone is working on it
[21:29] <mfisch> micahg: there's some stuff there, does that mean it's being worked on?  https://merges.ubuntu.com/x/xfonts-mathml/
[21:30] <mfisch> looks like it was automated
[21:30] <mfisch> but failed
[21:30] <micahg> mfisch: no, I mean here: https://merges.ubuntu.com/main.html
[21:31] <mfisch> micahg: it's listed as outstanding
[21:33] <micahg> mfisch: right, which means it hasn't been merged this cycle yet, you'll want to look at the comments column to see if there's anything relevant there
[21:51] <mfisch> micahg: okay, I've got my bug and did my changes/debdiffs, I need to do some final testing, here's the bug: eowner's insurance, and health insurance are all taxes too?  T
[21:51] <mfisch> oops! paste fail
[21:52] <mfisch> micahg: https://bugs.launchpad.net/ubuntu/+source/xfonts-mathml/+bug/1054353
[21:53] <micahg> mfisch: well, you didn't ascertain if an FFe is needed, but if it would be, what they'd want to see is an sbuild log that includes a list of the contents of the built binaries
[21:54] <mfisch> micahg: I can remove that part from the bug, should I ask the release team on IRC?
[21:54] <micahg> mfisch: well, the release people dealing with universe usually lurk in here
[21:56] <micahg> mfisch: you'll also want to close the bug in your debdiff
[21:56] <mfisch> in the changelog you mean?
[21:56] <micahg> yep
[21:56] <mfisch> ok
[21:58] <cjwatson> mfisch: six 1.2.0-1 uploaded to Debian now.  But new upstreams really aren't a priority for quantal at this point so I probably won't bother syncing it
[21:58] <mfisch> cjwatson: no worries, I was looking for a package to experiment with the process on
[21:59] <cjwatson> mm.  this particular part of the process might be generally better at the start of the R cycle ...
[22:00] <cjwatson> unless you find things that are genuinely interesting bug fixes of course
[22:02] <mfisch> cjwatson: when does R open up?
[22:03] <mfisch> micahg: updated
[22:04] <micahg> well, we've still got over 200 packages that haven't been merged this cycle yet, but yeah, bug fixes, especially RC ones should probably come first at this point
[22:06] <cjwatson> mfisch: within a week (at the outside, usually earlier) after 12.10 releases
[22:09] <cjwatson> I like that part of the cycle so usually try to do it quickly :-)
[22:13] <Laney> woe is forgetting to start a long remote build in screen
[22:13] <Laney> (webkit)
[22:13] <micahg> Laney: it's painful :)
[22:14] <micahg> Laney: care to comment on the FFe necessity of https://bugs.launchpad.net/ubuntu/+source/xfonts-mathml/+bug/1054353/+attachment/3329883/+files/4ubuntu1_to_6ubuntu1.debdiff
[22:17] <Laney> micahg: probably doesn't need one
[22:17] <mfisch> Laney: thanks
[22:17] <Laney> are the maintainer scripts correct in light of using dh_installxfonts?
[22:18] <Laney> its man page mentions that it generates maintainer script snippers
[22:18] <Laney> ts
[22:18] <Laney> maybe best to check
[22:19] <mfisch> postinst is pretty much empty, but postrm has code in it
[22:19] <mfisch> looks like both of those will be regenerated by installxdonts
[22:19] <mfisch> fonts I mean