[15:33] <flohack> sistpoty|work: THANKS! I'll give it a spin
[15:33] <flohack> sistpoty|work: I just assumed that everything which is not specially commented in the skeleton is optional
[15:35] <flohack> sistpoty|work: Ok that looks good, it complains about missing files in usr/include
[15:35] <sistpoty|work> flohack: was just coming to that
[15:35] <sistpoty|work> flohack: if my memory serves me, you'll need to list the full path relative to the source package dir in install files
[15:35] <sistpoty|work> flohack: which then would be debian/tmp/usr/include etc.
[15:35] <flohack> sistpoty|work: That would be debian/tmp/usr/include/* then
[15:36] <flohack> sistpoty|work: lol
[15:36] <sistpoty|work> flohack: unless you use --sourcedir=debian/tmp (or s.th. like that, just check the dh_install manpage)
[15:37] <flohack> sistpoty|work: Ok, I'll have a look!
[15:38] <RainCT> ScottK, jpds: send
[15:38] <jpds> s/d/t/
[15:38] <bigon> http://patch-tracking.debian.net/ new tools from debian \o/
[15:45] <ScottK> RainCT: Answered.
[15:48] <flohack> sistpoty|work: Works just fine now, thanks once again!
[15:48] <sistpoty|work> your welcome;)
[15:49] <ryanakca> Is it possible to use the GNU Free Documentation License for manpages that we submit to Ubuntu?
[15:49] <ScottK> ryanakca: Yes, but why?
[15:50] <ryanakca> ScottK: well, what license should I stick it under?
[15:50] <ScottK> ryanakca: It's much simpler to use the license used by the thing it's a man page for.
[15:50] <ryanakca> ScottK: ok, thanks
[15:51] <devfil_> jdstrand_: can you take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ? it is the package of a GUI for ufw
[15:51] <tacone> is there any reason that could provoke a patch being not applied to just 1 of the files or just on the first file ? (I have 2 files in total)
[15:52] <ScottK> Was it not applied or did it fail to apply?
[15:53] <tacone> half-ly applied. only to 1 of two files. also seems to work right when applying by hand in hardy.
[15:53] <ScottK> tacone: Also check and make sure you don't have a case where the same change for one file is inadvertently in the .diff.gz as a direct change and the patch isn't getting applied at all.
[15:54] <tacone> ScottK: one of the two files get patched.
[15:54] <tacone> I guessed I shuold get a warning otherwise? shuoldn't I '
[15:54] <tacone> ?
[15:54] <ScottK> RIght.  That or one of the files is patched via a direct change in .diff.gz and the actual patch isn't used.
[15:56] <tacone> ok, here's the big news. dpatch apply-all seems not to work the same way in hardy and intrepid.
[15:56] <directhex> is your 00list valid?
[15:57] <tacone> directhex: guess so. on my host computer I get everything ok. in intrepid dpatch apply-all gives no error messages but applies only half of the patch
[15:58] <tacone> if any of you has a hardy box or vm or chroot to download the source package of memaker-1.0.1, try to dpatch apply-all inside the working tree, then "grep class Memaker/ -Ri" and pastebin the result.
[16:03] <jdstrand_> devfil_: I can, but not today
[16:03] <devfil_> jdstrand_: tomorrow? the feature freeze will be tomorrow...
[16:05] <jdstrand_> devfil_: the feature freeze is 00:00 UTC tomorrow, or in 8 hours
[16:05] <jdstrand_> devfil_: I have too much to do for FF to get to it today
[16:06] <devfil_> jdstrand_: ok, np
[16:06] <jdstrand_> devfil_: I'd be happy to look at it another time though, otherwise try to get another revu person
[16:07] <devfil_> jdstrand_: yea, sure
[16:10] <bddebian> Heya folks
[16:12] <flohack> sistpoty|work: May I bug you once more? Now I have the problem, that the installed shared library does not work when being linked to with -lfb. I have to add the libfb dependencies too (-lnet -lpcap). I can remember that I had this problem a few years ago, but I can't remember how to resolve it. Google hasn't got an answer either.
[16:12] <sistpoty|work> hi bddebian
[16:12] <Iulian> Heya bddebian.
[16:12] <bddebian> Hi sistpoty|work, Iulian
[16:13] <directhex> so, anyone feel like giving mono-basic revu some love then?
[16:13] <sistpoty|work> flohack: it there a pkg-config file or similar? you could use that, to determine ldflags for the library
[16:14] <flohack> sistpoty|work: Ahh...ok so the pkg-config is responsible for pulling in required libs. But shouldn't the linker know that by itself?
[16:14] <sistpoty|work> flohack: yes, it is... the linker can't know this when you try to link statically (as I assume you're doing)
[16:15] <RainCT> devfil_: commented
[16:16] <flohack> sistpoty|work: Ok thanks...I'll dive into pkg-config. There isn't a dh_* command to create the necessary file automagically, is there?
[16:17] <sistpoty|work> flohack: no, you'll need to create such a file by hand
[16:17] <flohack> sistpoty|work: Cheers!
[16:17] <superm1> ScottK, I didn't.  RainCT had put together a gateway so that ubuntu developers could commit to the trees when sponsorship was needed and such
[16:17] <ScottK> superm1: Someone had to add that team to Mythbuntu
[16:18] <james_w> congratulations Laney
[16:18] <superm1> ScottK, the gateway was supposed to catch any mail?  Is it not?
[16:19] <ScottK> No.
[16:19] <RainCT> superm1: bugmail yes, but not other notifications (like the announcement of the new mythbuntu mailing lists) :(
[16:19] <devfil_> RainCT: mhh, I'm not sure about somethings
[16:19] <superm1> oh yikes
[16:19] <superm1> okay well for now i'll take it out then until this is sorted
[16:19] <RainCT> superm1: can you remove the team from mythbuntu until there's something decided on ubuntu-devel? (I can't find how to do it myself)
[16:19] <Iulian> Laney: Congratulations!
[16:20] <superm1> RainCT, okay should be done
[16:21] <ScottK> superm1: Thanks.
[16:23] <RainCT> devfil_: like?
[16:23] <sommer> ScottK: the perl spamassassin/clamav MIRs are done
[16:23] <devfil_> RainCT: - I’d call the binary package "ufw-gtk" instead of "gufw", to make it more discoverable and so that it’s more obvious what it is.
[16:24] <devfil_> then what about firestarter?
[16:24] <sommer> ScottK: you, or anyone else, wouldn't have a moment to look at bug #261462 ?
[16:25] <sommer> err would have a moment?
[16:25] <devfil_> RainCT: and the most other things seems me only aesthetics
[16:28] <RainCT> devfil_: does gufw do anything which you can't do with plain ufw?
[16:28] <RainCT> devfil_: and yes, I've only looked at the diff.. but aesthetics are important :)
[16:29] <RainCT> devfil_: err, not everything. the debian/copyright issue for instance would be a rejection
[16:29] <devfil_> RainCT: no, but this is no reason to call the package in a different way from upstream don't you think?
[16:30] <devfil_> s/this/there/
[16:30] <RainCT> devfil_: if so, why do you call the tarball gui-ufw instead of gufw?
[16:31] <devfil_> RainCT: because upstream calls the source dir gui-ufw
[16:31] <devfil_> and also it is the name of the project
[16:31] <RainCT> devfil_: ah, evil upstream :P
[16:31] <devfil_> but the apps is called gufw
[16:33] <RainCT> devfil_: anyway, I still think ufw-gtk is a better name (as you can do 'apt-get install ufw<tab>' and you find it), but n the other side, it could be confusing for users who directly search for 'gufw', so feel free to ignore this point :)
[16:33] <RainCT> devfil_: (generally, always when I say "I'd" or stuff like that on a review it's just a suggestion)
[16:35] <RainCT> Laney: congratulations :)
[16:35] <jdstrand_> RainCT: I think there may be a competing project called ufw-gtk, but I am not sure
[16:37] <RainCT> jdstrand_: uhm.. if so, they should do some decent SEO :P
[16:40] <jdstrand_> I'm not involved with either project, but I've tried to make them aware of each other
[16:50] <RainCT> persia: I'm not sure if I understand your last mail
[16:50] <flohack> sistpoty|work: Cheers!
[16:51] <sistpoty|work> cheers flohack
[16:51] <tacone> Laney: found it out. wrong patch.
[16:51] <persia> RainCT: Which part?
[16:51] <RainCT> persia: "As long as members of the team maintaining the package have an accurate tree ready for upload (or follow the more typical (and more widely documented) practice of attaching the debdiff to a bug), there ought be no issues sponsoring the update in the regular manner"
[16:51] <persia> RainCT: If someone prepared something that's ready to go into the archive, there's no need for write access to sponsor it.
[16:53] <RainCT> persia: so option 4 of those I listed on my first mail?
[16:54] <persia> RainCT: Well, some of that.  I'm against any upload which doesn't mirror the repo, as I discussed in my first mail.
[16:55] <persia> It's very much not ideal that the repo is out of date, and in my opinion, it's very much not ideal that someone upload something that can break a flavour without discussion with the flavour maintainers.
[16:55] <persia> I'm a *huge* fan of collaborative development, and think MOTU ought upload anything either not modified in Ubuntu or maintained by MOTU.
[16:56] <persia> That said, there are some pockets of packages related to flavours that can have a vast impact on the flavour, and with which an arbitrary MOTU may not have familiarity: the change in the Maintainer field accurately represents this, and ought be respected.
[16:57] <persia> If you'd asked me about non-flavour packages, I'd not be so opposed, and would think it only appropriate that ubuntu-dev have rights to modify the repo.
[16:57] <ScottK-laptop> Personally, I think the repo is a convenience.  The (pun intended) canonical source for the package, is the Ubuntu repository.
[16:58] <persia> ScottK-laptop: I can agree with that, but still think MOTU ought respect flavour-specific packages, especially core packages for a given flavour.
[16:58] <ScottK-laptop> Agreed.
[16:58] <RainCT> persia: So what you mean is that changes to mythbuntu packages (and in general packages which have a Maintainer different to the MOTU Team and have Vcs- fields set) should be done through branch merge requests instead of u-u-s?
[16:59] <persia> If a given MOTU happens to be interested in the flavour, they ought join the $(flavour)-dev group.
[16:59] <ScottK-laptop> Yes.
[16:59] <ScottK-laptop> RainCT: I don't think that's what he said.
[16:59] <persia> RainCT: No.  Whether it's branch merge or UUS or what have you doesn't matter.  It should be done in coordination with the developers for the flavour.
[17:00] <persia> When I find something in UUS for a flavour with which I'm not involved, I contact the flavour developers to confirm.  I've only had one case where I wasn't told "Go Ahead", and the flavour devs then fixed the issues and uploaded.
[17:00] <ScottK-laptop> And recognize that not all MOTU are interested manipulating $VCS as part of sponsoring, so a $VCS oriented sponsorship request will reduce your target audience.
[17:01] <persia> ScottK-laptop: Yes, but completely orthogonal to the point at hand: that I'm not a mythbuntu-dev.
[17:01] <RainCT> I that I agree with you
[17:02] <ScottK-laptop> persia: Yes, but there was also a comment about 'or pull from the branch for sponsorship' that I was responding to.
[17:02] <RainCT> persia: but that http://paste.ubuntu.com/40945/plain/ seems like a contradiction to me so I still don't understand your position in relation to sponsoring :/
[17:02] <persia> ScottK-laptop: That's not the documented procedure for UUS, but some people do it.  I'm not going to complain if it works for them, and I'm not going to tell anyone they must pull from a branch.
[17:03] <persia> I'm also not going to update the UUS documentation to indicate that one ought pull from a branch.
[17:03] <ScottK-laptop> RainCT: Another point (unrelated to what persia is trying to discuss now) is that if the Mtyhbuntu icon is on my LP profile, people will, reasonably assume I have something to do with Mythbuntu and that's wrong.
[17:03] <persia> RainCT: The repo should be up to date for an upload prior to it being sponsored.  Anything else is simply not correct.
[17:04] <sistpoty|work> ScottK-laptop: but it's another icon for the collection! :P
[17:04] <RainCT> ScottK-laptop: yes, that indeed a problem which I hadn't thought of until you first mentioned it
[17:04] <persia> Mind you, Mythbuntu is cool, and if I had an extra couple days each week, I'd like to be involved, but it's simply not the case now.
[17:04] <ScottK-laptop> sistpoty|work: I'm not an active collector.
[17:04] <sistpoty|work> heh
[17:05] <persia> sistpoty|work: I like emblems.  I want more emblems, but I want them for stuff I actually do.
[17:06] <RainCT> persia: Well, so if stuff can be uploaded going through u-u-s, but only if it is in the branch, we are back to the start.
[17:07] <RainCT> persia: where people should file branch merge requests for the mythbuntu team to handle them, and if the guy who handles the request isn't a MOTU either he or the original contributor ask u-u-s to upload it
[17:08] <persia> RainCT: Right.  We shouldn't be accepting random updates to flavour-specific packages that have not been approved by any members of the $(flavour)-dev team.
[17:09] <persia> That said, I don't know of any flavours (excepting possibly gobuntu) that don't have active enough development teams that this can be done in a timely manner.
[17:09] <ScottK-laptop> ... unless $(flavor)-dev team has a policy otherwise (not that the do/should, but the option is there).
[17:10] <RainCT> persia: (I though Gobuntu doesn't exist anymore?)
[17:10] <RainCT> persia: so that behaviour should be documented on the wiki (after proposing it on -devel)
[17:11] <persia> RainCT: gobuntu-meta was in the archives last I looked, but yes, I believe it's inactive.
[17:12] <persia> I also think it doesn't need special discussion: the Maintainer is not MOTU either explicitly or implicitly.  Why should MOTU be changing the package?
[17:12] <RainCT> (p.u.c doesn't show gobuntu-meta being in intrepid)
[17:13] <RainCT> persia: because it is in universe, and unless told otherwise new contributors only know that universe -> u-u-s, main -> u-m-s
[17:14] <ma10> New revision azureus_<IP_ADDRESS>-3ubuntu2 seeking sponsor. Bug 261879. lifeless, persia: it contains the fix we've been talking about on -java. Comments? jdong: ping :)
[17:14] <persia> RainCT: Sure.  I don't see why they need to be especially informed.  Like I said, I've only once had any response from a flavour development team other than "Go Ahead".  Generally, someone refreshes the branch from the upload, or so I presume.
[17:15] <jdong> ma10: looking
[17:15] <jdong> (packing today to go back to school)
[17:15] <jdong> lemme boot up my VMs
[17:16] <ma10> I'm packing too! My study abroad year is finished..  But this time i just have to empty the flat
[17:19] <jdong> ma10: that makes life easy. I stayed back at home for the summer so there's stuff *all around* here that I could've forgotten
[17:20] <jdong> ma10: have you tried submitting the multiuser workaround/fix upstream too?
[17:20] <ma10> jdong: just remember your pc and underwear, you'll be allright :)
[17:20] <jdong> I'd be curious what they have to say
[17:21] <ma10> oh i had quite a discussion with them
[17:21] <ma10> they fail to admit it's a real issue
[17:21] <jdong> ma10: lovely.
[17:22] <ma10> because there should be one user per machine with one instance running (good for network performance)
[17:22] <jdong> azureus upstream is fun at times. Plus they REALLY love Ubuntu (not)
[17:22] <ma10> i managed to dodge that point
[17:23] <ma10> anyway i think this fix is too much of a hack for them, they should reduce code duplication first, as lifeless was suggesting
[17:24] <jdong> ma10: indeed. At any rate, the fix is quite important for us as multiuser support and cross-user security are essential pieces of what Ubuntu is.
[17:24] <ma10> that's how i see it
[17:25] <RainCT> persia: so.. contributors subscribe u-u-s providing a debdiff (and perhaps also a branch) and the MOTU who looks at the debdiff pings a mythbuntu member for him to merge it into the branch, and after that mythbuntu guy says 'OK' upload it?
[17:25] <RainCT> *uploads
[17:26] <Laney> \o/
[17:27] <persia> RainCT: That might be one example of a workflow.  I suspect the majority of those who contribute to mythbuntu directly and propose things for upload will already be mythbuntu-dev, which makes some of that a no-op.
[17:27] <persia> At least my experience was that it was rare for someone not a member of the $(flavour)-dev team to be fiddling with a core flavour-specific package.
[17:32]  * RainCT doesn't see why we would want such stuff on u-u-s then as it makes more sense to ask a mythbuntu dev directly, but doesn't feel like continuing the discussion :P
[17:35] <Laney> thanks RainCT, Iulian and james_w (and jpds and dholbach)! Also thanks persia for the taste of power. It felt good
[17:36] <persia> Laney: Just a taste to get you excited :)
[17:36] <ma10> jdong: thanks!
[17:37] <dholbach> haha
[17:37]  * dholbach hugs laney
[17:38] <ScottK-laptop> RainCT: If the mythbuntu-dev is also MOTU, then it doesn't.
[17:39] <ScottK-laptop> I think a lot of this goes away after the archive reorg.
[17:39] <sebner> ScottK-laptop: in the evening I'll present you my first MIR try  ^^
[17:40] <ScottK-laptop> sebner: Best hurry as sommer is going wild.
[17:40] <sebner> ScottK-laptop: Sure, I'll try
[17:42] <Juli_> hi! can anybody help with second +1 for http://revu.ubuntuwire.com/details.py?package=libnb-platform-java please?
[17:43] <Juli_> huge thanks to dholbach for the first one
[17:43] <dholbach> it's probably worth mentioning that it's "an update" of the existing libnb-platform7-java
[17:44] <dholbach> which makes the review more straight-forward
[17:44] <dholbach> and it'S required for the new netbeans :)
[17:44] <Juli_> yes, exactly:)
[17:44] <jetsaredim> anyone know where I can find libstdc++-libc6.2-2.so.3
[17:48] <ScottK-laptop> dholbach: If it's an update, why can't you just upload it?
[17:49] <dholbach> ScottK-laptop: it's a new source package
[17:49] <ScottK-laptop> OK.
[17:50] <dholbach> or rather upstream rename... you know what I mean
[17:50] <dholbach> anyway... I call it a day now - see you guys tomorrow!
[17:51] <ScottK-laptop> dholbach: If it's a rename, I think one MOTU is enough.
[17:54] <Juli_> ScottK-laptop: won't there be any problems with archive admins
[17:54] <dholbach> better stick to the rules - in any case, I need to rush off now and my intrepid machine is already shutdown
[17:55] <ScottK-laptop> Juli_: No.  That's a MOTU rule, not a hard archive requirement.
[17:55] <dholbach> thanks in advance - see you tomorrow :)
[17:56]  * sistpoty|work also calls it a day and heads home... cya
[17:58]  * persia looks at libnb-platform-java
[17:59] <Juli_> persia: thanks! so only netbeans itself will be a headache after platform is uploaded
[17:59] <persia> Juli_: And that's in a bug, right?
[18:00] <TomaszD> hey, is it possible to create a debian driver package for the kernel so that it doesn't break between security updates to the kernel? I've manually modified the linux-image-2.6.24-19-generic_2.6.24-19.41_i386.deb package (added drivers, bumped minor version number), but this obviously will break after security updates
[18:00] <Juli_> persia: yes https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/253016
[18:01] <superm1> TomaszD, https://help.ubuntu.com/community/Kernel/DkmsDriverPackage
[18:01] <TomaszD> so is it possible to create a package that will just throw some .so files into the kernel tree, without it breaking?
[18:02] <superm1> TomaszD, DKMS will recompile them when you rev the kernel more or less
[18:03] <TomaszD> superm1, great, that was so obvious that I didn't think about dkms, wonder if it'll work
[18:03] <persia> Note that this ought only be used in cases where the driver is for a device that is typically installed in an environment suitable for compilation.
[18:03] <superm1> TomaszD, as long as you craft your dkms.conf properly, it should be able to to the trick for you
[18:03] <persia> Moving everything to DKMS would be bad.
[18:03] <superm1> the impression i got was this is a local solution for TomaszD
[18:04] <persia> Well, I'd argue there are cases where it's appropriate to use DKMS in the archives as well, just not for everything.
[18:04] <TomaszD> well, not local, it's for MSI Wind users in general, it will eventually be released into the wild
[18:04] <superm1> TomaszD, well the proper route to go is to try to get these into SRU's
[18:05] <superm1> so that future kernels will include them and then you won't need the DKMS built packages anymore
[18:05] <persia> TomaszD: MSI Wind is one of the examples where you might not want DKMS, as that's a fairly underpowered machine.
[18:05] <persia> Mind you, the new ones are nicer, but still.
[18:05] <superm1> and set a flag in the dkms.conf to stop using/building when you're on that newer kernel
[18:06] <TomaszD> SRU would be a good idea I guess
[18:06] <jpds> congrats Laney! Keep up the good work.
[18:06] <superm1> TomaszD, so if these are NEW drivers that don't conflict with anything that shouldn't be too troublesome.  if they are large changes to existing drivers then that can cause complications
[18:07] <TomaszD> no, these are compeltely separate drivers
[18:07] <TomaszD> Realtek 8187SE
[18:07] <TomaszD> WLAN
[18:07] <superm1> TomaszD, then i would try to factor them into the LUM packages and submit a patch to the kernel team's mailing list to add them
[18:08] <superm1> TomaszD, and until that package is released do a dkms package that includes binary and source of the modules
[18:08] <TomaszD> dang it I have to look up every SRU and LUM thing you throw at me
[18:08] <TomaszD> :]
[18:09] <superm1> TomaszD, lum == linux-ubuntu-modules.  it's the package that contains modules that are not upstream yet
[18:09] <TomaszD> ahh
[18:11] <devfil_> Someone can take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ?
[18:11] <jpds> devfil_: Wouldn't ufw-gtk be a better name?
[18:11] <ScottK-laptop> jpds: Read the scrollback.
[18:12] <jpds> Yay for evil upstreams.
[18:14] <lukehasnoname> scrollback?
[18:15] <jpds> lukehasnoname: irclogs.ubuntu.com
[18:15] <lukehasnoname> mm
[18:18] <TomaszD> jpds, a better name would be ubuntu-firewall, ufw-gtk is good for nerds only :]
[18:22] <directhex> TomaszD, ubuntu: linux for big fat nerds?
[18:22]  * directhex jumps up & down & pokes people over: mono-basic on revu; monodoc 1.9 main merge
[18:23] <TomaszD> didrocks, not quite the target audience Ubuntu is aiming at, they're all using gentoo ;]
[18:23] <TomaszD> I kid, I kid
[18:23] <directhex> TomaszD, cool kids dropped gentoo when it sold out & went mainstream. now they all run Arch
[18:24] <TomaszD> real men use LSB. Let's stop this now.
[18:24] <TomaszD> *LFS
[18:24] <directhex> LSD?
[18:24] <TomaszD> :]
[18:25] <didrocks> TomaszD: 3 times today someone hilight me here for directhex ^^
[18:25] <directhex> didrocks, sorry matey... http://www.googlefight.com/index.php?lang=en_GB&word1=directhex&word2=didrocks
[18:27] <persia> And for extra points, NM should stop disconnecting me today :)
[18:28] <directhex> for even more points, all my outstanding merge & sync requests should magically happen. and mono-basic gets the required approvals on revu
[18:28] <directhex> but sometimes, persia, life just isn't fair :(
[18:29] <laga> directhex: before feature freeze? ;)
[18:29] <directhex> laga, well, YES!
[18:29] <persia> directhex: If they are all in the queue, and they would otherwise violate feature freeze, chances are high they will be looked at in the next few hours.  No promises on them getting approved.
[18:30] <laga> time to prepare another mythtv upload..
[18:30] <persia> directhex: In the meantime, if you'd like to help with the 40 packages above, it may favorably incline various MOTU towards you, including those in some of the leadership positions :)
[18:30] <directhex> which 40? i only just got home
[18:31] <laga> i guess i could look at some, too, to prepare for my UUC application.
[18:32] <persia> directhex: Visit http://qa.ubuntuwire.com/bugs/rcbugs/ : everything with a new upstream ought get checked, as it will make the life of the SRU and SWAT teams easier if intrepid & lenny share the same version, and the current packages are likely to be RC buggy in intrepid.
[18:33] <persia> laga: That'd be great.  Thanks.
[18:33] <laga> dang, i need some caffeine...
[18:34] <laga> persia: what am i supposed to do? check the new upstream to see if the bugs are fixedß
[18:34] <persia> laga: That, and also whether introducing the new Debian changes (through a merge or sync) would cause significant disruption to intrepid development.
[18:35] <persia> If the package is an edge packages (no rdepends or reverse build-depends), it's exceedingly likely it is best updated.
[18:35] <persia> If there are reverse dependencies, it needs a little more investigation.
[18:35] <sebner> persia: what about extra points for uqm upload? :P
[18:36] <persia> Claim the package here, and ask any questions you have.  There are a few of us who tend to chase as much as possible pre-FF, and we'd be happy to help (as we need your help to get it done in time)
[18:36] <persia> sebner: No extra points for that: it's on my list of things to definitely do tonight though.
[18:36]  * persia has a shorter, targeted list today
[18:36] <sebner> persia: \o/
[18:37] <laga> i'll look at i810switch. looks like a fun package
[18:37] <persia> sebner: You like new stuff.  Want to check the 40 RCbug new-upstream packages?
[18:38] <persia> laga: Remember to check the LP bugs also: it may be that someone already requested the sync or merge, and it's just waiting for sponsoring.
[18:38] <sebner> persia: are they more important as the non-new grave bugs?
[18:38] <ScottK-laptop> sebner: You owe me a MIR before you do fun stuff.
[18:38] <sebner> ScottK-laptop: of course. Though I file sync requests besides :P
[18:39] <persia> sebner: Yes, because they need to get done in the next several hours.  The non-new upstream grave bugs can be fixed over the weekend.
[18:39] <persia> ScottK-laptop: Is FF also the deadline for MIRs ?
[18:39] <sebner> persia: Bah, you should have asked me ealier. I'm not harry potter to do loads of magic in few hours -.-
[18:40] <persia> sebner: It's been there for weeks.  I just got anxious now.  I know you know about RCbugs :p
[18:40] <persia> :)
[18:40] <ScottK-laptop> persia: It's not a hard, hard deadline, but yes.
[18:41] <sebner> persia: Sure but I focus on the grave ones and there a lot aren't new upstream ones
[18:41] <persia> ScottK-laptop: From a motu-release perspective, do you think it's more important to chase the MIRs, or the RCbugs with new upstreams?
[18:41] <leonel> how do I know what package system uses any package ??
[18:42] <persia> sebner: No, only 5.  You can have those, if you like?
[18:42] <persia> leonel: Generally reading debian/control and debian/rules will advise you.  Most of the time, debian/control ought be sufficient.  For many packages, even the .dsc alone is sufficient.
[18:42] <sebner> persia: We'll see. First I have to do some other stuff, then finish the MIR for ScottK-laptop and then when I don't fall asleep I grab some new upstream versions
[18:43] <leonel> thanks persia
[18:43] <persia> sebner: No sleep until midnight UTC.  That's the deadline.
[18:43] <sebner> persia: I would if I wouldn't have a (summer) job -.-
[18:44] <directhex> typical. the one package i've got experience with, sebner's already on
[18:44] <persia> Well, I suppose.  It's just the two days a year that this happens.
[18:44] <RainCT> superm1: btw, can mythtv be used for free?
[18:44] <laga> btw, what do i do if i think a package is suitable for merging/syncing? file a bug?
[18:44] <superm1> RainCT, define free...
[18:44] <persia> directhex: Be more agressive: fix the bugs before anyone else has a chance :)
[18:44] <RainCT> superm1: €
[18:44] <superm1> RainCT, yes it can depending on your locale and data availability
[18:45] <sebner> directhex: which one? midori?
[18:45] <directhex> sebner, nini
[18:45] <sebner> directhex: ah ^^
[18:45] <sebner> persia: lol, that's a good motivation xD
[18:45] <directhex> sebner, i had to patch around its funny behaviour in my tangerine mods in my repo
[18:46] <persia> laga: Yes, file a merge/sync bug, and subscribe the sponsors queue.  For a merge bug, be sure to attach the debdiff before subscribing the sponsors.
[18:46] <laga> ok
[18:46] <persia> slytherin!
[18:46] <slytherin> persia: hi
[18:46] <sebner> directhex: funny behaviour?
[18:47] <persia> slytherin: You feel like looking at merges/syncs to ensure we match Debian for the Java packages, right?
[18:47] <persia> (upstream versions)
[18:47] <sebner> persia: though I'm sure "sebner on it" is even more readable then "Sync requested" :P
[18:47] <persia> We've 493 minutes to review, and get everything requested
[18:47] <slytherin> yes, I will be able to this over weekend. is that fine?
[18:47] <directhex> sebner, .INI file comment character is ";", tangerine uses ";" as its separator for multiple paths
[18:48] <persia> sebner: I tend to put in bug numbers, for ease of reference by others, rather than just "persia on it"
[18:48] <sebner> persia: Nearly nobody uses them. and if you click on the package you'll see the bug report anyways so nvm
[18:49] <persia> sebner: Well, some people do, but yes, not that many people.  I still try to be helpful.
[18:49] <sebner> persia: I appreciate
[18:56] <sebner> ScottK-laptop: Launchpad to go Open Source by next OSCon  ;)
[18:56] <persia> sebner: You're reading the news, aren't you?
[18:56] <sebner> persia: yes, why?
[18:56] <ScottK-laptop> sebner: Get to work.
[18:56] <sebner> lol xD
[18:57] <persia> sebner: Aren't you supposed to be doing an MIR and some RCbugs?  If you're out of those, I can find you more stuff that needs doing: all new packages or new upstreams.
[18:57] <ScottK-laptop> sebner: If that helps reduce the parochialism of the developers, then I think I think it'll be a big win.  If not, not so much.
[18:58] <sebner> persia: ScottK-laptop: Don't worry. I'm already a slave of sebner. :P
[18:59] <laga> am i supposed to request syncs even if the RC bug doesnt affect ubuntu?
[19:00] <persia> laga: Your call.  For edge packages, I tend to do that anyway, especially where Ubuntu has a chance of matching a Debian stable release, but if there are a lot of rdepends, it's not the best thing, as it introduces instability into Ubuntu.
[19:00] <persia> If you want a real opinion, ask ScottK or another member of motu-release.
[19:01] <laga> okay. i810switch doesnt has rdepends and the diff is just a macbook fix.. who uses i810switch these days?
[19:01]  * laga goes to request a sync anywaysd
[19:02] <persia> laga: The three users will all thank you :)
[19:02] <slytherin> persia: will be back in 5-10 minutes
[19:03] <sebner> persia: so. here you have a new upstream sync bug #261939 --> but don't tell ScottK :P
[19:03] <sebner> ScottK-laptop: just a joke. now working on your MIR :)
[19:04] <persia> sebner: I'll be silent on the matter, but that solves 2 RC bugs with a single sync :)
[19:05] <sebner> persia: Die you bad bugs, die! :)
[19:05] <persia> sebner: That's the attitude :)
[19:05] <sebner> persia: does a MIR also kill RC bugs? ^^
[19:06] <persia> sebner: Sometimes.
[19:07] <sebner> :)
[19:07]  * sebner back to work
[19:07] <tuxmaniac> Harvest is cool! It makes it easy for people to identify bugs fixed upstream (Debian or the devel) and get a syn throu or closing issues after verifying and testing. Cool!
[19:07]  * tuxmaniac closed 2 bugs like that now :-)
[19:08] <persia> tuxmaniac: Indeed.  It's an excellent resource.  On the other hand, today we're focusing on bugfixes that need to be in place pre-FF, as we've only 472 minutes left, and harvest doesn't know any better.  Best to review quickly and see what's fixed in Debian or fixed Upstream that would require an FFe to be included, and concentrate on those.
[19:09] <laga> yay, my first sync bug evar
[19:10] <sebner> persia: I'm wonderin since new upstream versions won't get into the archive in 472 and they'll need a FF Exception. like it was in hardy cycle!?!
[19:10] <asomething> Anyone know why Bug #259300 was marked invalid? seems like it would fix a RC bug....
[19:11] <persia> sebner: If they aren't approved within 470 minutes, yes.  The archive-admins often pull the syncs post FF (by a few hours) without bothering about FF, as long as the syncs were approved in time.
[19:11] <ScottK-laptop> asomething: Looking
[19:12] <sebner> persia: Really? I thought it was different in hardy cycle
[19:12] <asomething> the RC bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487568
[19:12] <persia> sebner: Nope.  We've always done it that way.
[19:12] <ScottK-laptop> Iulian: See asomething's question about motion?
[19:13] <sebner> persia: kk, so my brain is playing a trick on me (as usual) :)
[19:13] <tuxmaniac> persia: yes. I am checking all Science packages for any such pending syncs
[19:14] <laga> haha.
[19:14] <laga>    * Save the world from masturbating monkeys (closes: #496409)
[19:15]  * persia grumbles about source pacakges that can only be built in intrepid
[19:15] <sebner> persia: Still don't have a intrepid chroot?
[19:16] <persia> sebner: I've currently 7 of them.  I just didn't happen to be in one when trying to build one of the sources.
[19:16] <sebner> ah ^^
[19:17] <sebner> persia: btw, you maybe should also focus on forcing u-u-s to process your forced sync/merge requests in time. :)
[19:18] <persia> sebner: Indeed.  The three areas I'm concentrating on right now are UUS, REVU, and multidistrotools for the Debian team to which I belong.
[19:18] <persia> I can only run a limited number of simultaneous builds, or I'd be pushing more.
[19:19] <persia> Speaking of REVU, we've 4 packages with one advocate.  Anyone want to be the second advocate?
[19:19] <sebner> persia: that is already pretty nice, just don't forget that many contributors aren't MOTUs and need sponsors(not only you) :)
[19:19] <persia> sebner: Indeed.  More sponsoring tonight would be a good thing.  Let's flood the buildds!
[19:20] <sebner> persia: I suppose u-u-s is already flooded? ^^
[19:20] <devfil> Someone can take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ?
[19:20] <geser> persia: find an archive admin to process the open syncs requests and the buildds get flooded
[19:20] <persia> sebner: Indeed, but keeping it flooded is the best means to get the buildds flooded.
[19:21] <persia> geser: I'm not so worried about that: I suspect we've enough merges and updates to do a fair bit of harm.
[19:21] <persia> archive-admin processing of NEW might help as well.
[19:21] <sebner> hopefully none of them is on holiday xD
[19:22] <persia> sebner: Doesn't matter.  archive-admins check the date of subscription, and will push stuff post-FF as long as it was forwarded to them (and valid) pre-FF.
[19:22] <sebner> ah cool
[19:22] <sebner> so FLOOOOOOOOOOOD
[19:22] <persia> Should all be caught up by Monday or Tuesday, but it might take that long.
[19:24]  * sebner is already looking forward at filing FFe bugs ^^ (though not that many. /me learned from hardy cycle)
[19:24] <slytherin> persia: What kind of setup do I need to do to use requestsync email interface?
[19:25] <sebner> slytherin: I never checked how this piece of software is working xD
[19:25] <persia> slytherin: No idea.  I used requestsync once, and decided that it was harder for me than doing it manually.
[19:25] <sebner> checked = understood
[19:25] <sebner> persia: +1
[19:26] <RainCT> devfil: advocated
[19:27] <devfil> RainCT: I've fixed the "allows" problem
[19:27] <persia> Five.  Five packages on REVU seeking a second advocate.  Who's up for some?
[19:27] <slytherin> Ok, can anyone tell me where can I find LP cookie in my firefox profile?
[19:28] <devfil> RainCT: can you readvocate it when I've upload the new version?
[19:28] <sebner> persia: I'm wondering that revu packages are still importatn
[19:28] <sebner> *important
[19:28] <RainCT> devfil: sure
[19:29] <emgent> hello
[19:29] <laga> sebner: anything containing the string "mythbuntu" (not kidding)
[19:29] <sebner> emgent: \o/
[19:29] <emgent> Laney: congrats :)
[19:29] <sebner> laga: I see
[19:29] <emgent> heya sebner :)
[19:29] <sebner> Laney: congratulations from me too
[19:29] <RainCT> slytherin: '~/.lpcookie.txt', '~/.mozilla/*/*/cookies.sqlite', '~/.mozilla/*/*/cookies.txt'
[19:29] <persia> sebner: No idea.  I've not reviewed them all.  People with important packages should be complaining about now.
[19:30] <sebner> emgent: want to help flood u-u-s or better the build machines?
[19:30] <emgent> lol no today sebner :)
[19:30] <jpds> LP COOKIES! \o/
[19:31] <sebner> emgent: surely today
[19:31] <emgent> jpds: oh you can remove my account in your server. thanks
[19:31] <sebner> persia: convert him!
[19:31] <persia> emgent: It's the day before FF.  We need your help to process everything that would otherwise be an FFe in the UUS queue.
[19:31] <jpds> emgent: OK; done.
[19:31] <sebner> ha!
[19:31] <emgent> sebner: i cant, i should go out
[19:31] <sebner> emgent: dito :P
[19:31] <emgent> persia: yeah i know :|
[19:31] <persia> emgent: Please?  There's only 449 minutes left until the deadline.
[19:32] <emgent> persia: tomorrow i will go out (Amsterdam)
[19:32] <persia> Why does installing devscripts install exim?  I thought that was fixed a while back.
[19:32] <persia> emgent: Yes, but it's FF!
[19:33] <emgent> persia: eh. I know, but i should go out! persia you can try to talk with my girlfriend, if you like..
[19:33] <stefanlsd> Im looking forward to dev week!
[19:33] <slytherin> RainCT: I was looking for instruction to copy it from firefox profile to ~/.lpcookie.txt. Anyway, I found that I have done it already at some point of time.
[19:34] <emgent> see you later people, good work.
[19:34] <RainCT> slytherin: have a look at prepareLaunchpadCookie() in ubuntu-dev-tool's common.py
[19:34] <persia> emgent: Just 5 sync requests?
[19:34] <slytherin> RainCT: ok
[19:34] <RainCT> devfil: still uploading?
[19:35] <devfil> RainCT: it will appear at 20:40
[19:35] <emgent> persia: uhm, i'm back in ~3hours i will try to give my little help
[19:35] <emgent> but now i have to go out :(
[19:35] <persia> emgent: Excellent.  See you then.  Thanks.
[19:35] <emgent> persia: see you later
[19:36] <RainCT> devfil: it isn't on REVU (on the server, I mean)
[19:36] <sebner> ScottK-laptop: I think I finished the MIR. do you check it now and I fix your complains or later and I can start killing bugs?
[19:36] <devfil> RainCT: I've uploaded it
[19:36] <RainCT> ah now
[19:37] <devfil> RainCT: http://revu.ubuntuwire.com/details.py?package=gui-ufw
[19:37] <RainCT> devfil: yep, advocated
[19:39] <ScottK-laptop> sebner: Sure.  What bug?
[19:39] <sebner> ScottK-laptop: bug #261946
[19:40] <ScottK-laptop> sebner: Looking
[19:41] <sebner> persia: debian changelogs page is pretty slow these day. our fault?
[19:41] <persia> sebner: Might well be.
[19:42] <slytherin> persia: Should I tell you bug number one by one or all at once?
[19:42]  * persia hopes so, as this would indicate that *lots* of people were looking at pre-FF stuff
[19:42] <tuxmaniac> bug 220268 is fixed upstream. But no patch is attached in the bug tracker for us to have a look. Is it worth digging such issues and bypassing upstream release cycle and getting it fixed in ubuntu?
[19:43] <tuxmaniac> I mean there are atleast 2 more such patches that upstream has "fix released" for gnumeric but not released an offocial version.
[19:43] <persia> slytherin: Subscribe the sponsors queue, and add the uus-fre-ff-810 tag
[19:43] <slytherin> persia: ok
[19:43] <persia> Err.  uus-pre-ff-810
[19:43] <slytherin> sebner: the page is indeed slow
[19:43] <tuxmaniac> if we port these patches we have the possiblity of clsoing couple of bugs
[19:43] <tuxmaniac> any suggestions?
[19:44] <sebner> slytherin: luckily not the news page :)
[19:44] <persia> tuxmaniac: Has upstream actually done a release that includes the fixes, or are the fixes just in VCS?
[19:45] <tuxmaniac> just in VCS
[19:45] <sebner> persia: you have the time in your head. how many minutes left?
[19:45] <persia> tuxmaniac: Feature changes, or just bugfixes?
[19:45] <persia> sebner: 375 or so.
[19:45] <tuxmaniac> persia: but they have closed the issue. one solves a crash and two minor bugfixes
[19:46] <persia> tuxmaniac: We'll want to backport the fixes later then.  Keep looking for stuff that needs to go pre-FF.
[19:46] <sebner> persia: k, thx
[19:46] <blueyed> Hi. Can somebody please review/advocate tvbrowser? should be fine by now: http://revu.ubuntuwire.com/details.py?package=tvbrowser
[19:46] <tuxmaniac> persia: aah ok
[19:46] <persia> sebner: Actually, rather 315 or so.  I can't do math right now.
[19:46] <RainCT> blueyed: I just started looking at it :)
[19:47] <blueyed> RainCT: awesome! :)
[19:47] <ScottK-laptop> sebner: Looks good.  Thanks.
[19:47] <sebner> ScottK-laptop: np. I'm just sad I didn't discover that ealier. I just did 1 and Asommer is working on it like hell :(
[19:48] <RainCT> blueyed: is it a KDE application?
[19:48] <blueyed> RainCT: java
[19:49] <RainCT> blueyed: right.. so for all desktop environments?
[19:49] <sebner> persia: And when I start complaining here that no one sponsors me? (1-2 hours before FF)? ^^
[19:49] <blueyed> RainCT: yes
[19:49] <persia> sebner: Don't.  You'll get sponsored.
[19:49] <RainCT> blueyed: I'd change the Name in the .desktop file then to be more descriptive
[19:49] <persia> (or if you don't, complaining won't help)
[19:50] <sebner> persia: I'm just answering for "worst case" :P
[19:50] <sebner> *asking xD
[19:51] <sebner> persia: bah, I always thought a u-u-c has VIP rights :P
[19:51] <persia> sebner: Regardless, the sponsors are likely agressively chasing the queue looking for FF stuff.  As long as you have the pre-FF tag, you'll get sponsored if the sponsors have the ability to sponsor it in time.
[19:51] <persia> No.  Why?
[19:51] <sebner> persia: *joke*
[19:51] <sebner> better we get back to work ^^
[19:52] <RainCT> blueyed: does it need some special hardware / subscription to some service / etc? if not, the priority should be optinal
[19:53] <RainCT> *"optional"
[19:53] <blueyed> RainCT: for example? IMHO it does not matter for the user which DE it is for really.
[19:53] <tuxmaniac> looks like maxima needs a merge badly. Debian bug 474909 lists a whole lot of bug fixes.
[19:53] <RainCT> blueyed: KDE displays the GenericName or something like that below the Name, that's why I asked if it if for KDE
[19:53] <blueyed> RainCT: it does not need some special HW/subscription
[19:54] <RainCT> blueyed: for GNOME/XFCE it is recommended (in the HIG, iirc) to have a descriptive name, like most applications preinstalled in Ubuntu  do ("Firefox Web Browser", and so on)
[19:54] <RainCT> blueyed: use the full URL in vcs-bzr
[19:56] <RainCT> blueyed: Overview.txt is uninteresting to the user
[19:57] <blueyed> RainCT: . I think it fits "extra", according to the desc: "This contains all packages that [...], or are only likely to be useful if you already know what they are or have specialized requirements."
[19:58] <RainCT> blueyed: because of what?
[19:59] <RainCT> blueyed: are all channels it knows about german or something like that? (if so I'm happy with extra)
[19:59] <blueyed> RainCT: I'm fine with "optional", too - if you still think it fits better.
[20:00] <RainCT> blueyed: no, just tell me the rationale :)
[20:00] <blueyed> ..not sure.. they are already "going international", so..
[20:00] <Iulian> ScottK-laptop: Commented
[20:00]  * RainCT is wondering wheter the priority has any real importance..
[20:00] <blueyed> RainCT: nothing more than above.. /me, too.
[20:00] <blueyed> RainCT: I will change it to optional.
[20:01] <ScottK-laptop> Iulian: Thanks.
[20:02] <RainCT> core dev ScottK-laptop :), is the priority used for anything useful?
[20:03] <jpds> RainCT: base packages?
[20:03] <RainCT> jpds: beside that
[20:04] <ScottK-laptop> RainCT: Not in Ubuntu.
[20:04] <ScottK-laptop> RainCT: But you may as well get it right.
[20:05] <RainCT> ScottK-laptop: and in Debian? higher priority = first to be build or something like that?
[20:05] <blueyed> RainCT: do you think GenericName in the desktop file should get improved?
[20:05] <RainCT> blueyed: no, it's fine :)
[20:07] <blueyed> RainCT: so a new upload is coming. changes at: http://bazaar.launchpad.net/aunchpad.net/~blueyed/tvbrowser/ubuntu
[20:07] <ScottK-laptop> No.  Not exactly.  More what the primary was to get something done.  As an example, their default MTA is Exim.  All other MTAs are priority Extra as a result.
[20:08] <ScottK-laptop> In theoty you can install all of optional and not get any confilcts.
[20:08] <RainCT> ScottK-laptop: Ah. Thanks for the info.
[20:09] <blueyed> RainCT: fixed url is: http://bazaar.launchpad.net/~blueyed/tvbrowser/ubuntu
[20:09] <RainCT> blueyed: OK. /me is test-building
[20:11] <sebner> how can I haXX0r debian/rules that gcc doesn't treat warnings as errors?
[20:12] <RainCT> blueyed: lintian is still unhappy.. output pasted on REVU
[20:12] <geser> sebner: look for -Werror in debian/rules or the Makefiles
[20:13] <sebner> geser: thanks :)
[20:17] <RainCT> blueyed: I'll advocate once everything I said is fixed
[20:17] <ScottK-laptop> So I find myself reverting to my pre-broadband browsing habit of clicking on something, moving on to another browswer window, and then coming back to it later on Launchpad.
[20:18] <ScottK-laptop> So I have a new motto for them:
[20:18] <ScottK-laptop> Launchpad:  For when you're nostalgic about dial-up.
[20:18] <persia> Yeah.  It could be a lot faster, especially today.
[20:19] <laga> i find some debian boxes slower.
[20:21] <sebner> geser: well I had to edit the configure script =) what was now the discussion about patch-systems? ^^
[20:26] <laga> gah, i cant remove comments on http://qa.ubuntuwire.com/bugs/rcbugs/
[20:26] <ScottK-laptop> laga: Known bug.  Harass ajmitch if you really want something done about it.
[20:27] <laga> ajmitch: consider yourself harassed - i can't delete comments on qa.ubuntuwire.com/bugs/
[20:28] <laga> alright, not gonna merge qemu now, i need to prepare a mythtv upload
[20:29] <persia> ScottK-laptop: How is UMS re: FF stuff?
[20:30] <ScottK-laptop> UMS is one acroynm too many for me for today?
[20:31] <RainCT> blueyed: woot. Just tried out TV-Browser, nice :)  (I prefer tvmovie.de, though)
[20:31] <persia> ScottK-laptop: Heh.  OK.  Not likely stuff that worries me much, but I thought there might be a heap of last-minute stuff.
[20:32] <ScottK-laptop> persia: What is UMS?
[20:34] <persia> Ubuntu-Main-Sponsors
[20:35] <persia> My apologies: I thought you were ignoring that acronym specifically, rather than having forgotten the definition.
[20:37] <ScottK-laptop> No problem.
[20:37] <ScottK-laptop> Dunno.  I haven't had much time to look.
[20:38] <persia> Anyone feel like doing a gnurobots merge?
[20:38] <sebner> ScottK-laptop: isn't that a *long-known* bug on ubuntuwire?
[20:39] <ScottK-laptop> Yes, but still unfixed.
[20:39] <persia> My memory is that the reason the bug is there is that a spider deleted all the comments one day.
[20:39] <persia> How about a tuxtype merge?
[20:39] <sebner> ^^
[20:40] <sebner> debian packages site isn't loading for me :( :( :(
[20:40] <sebner> R.I.P
[20:40] <laga> yeah, seemed borked here too
[20:40] <persia> Which site?  packages.qa.debian.org?
[20:41] <sebner> pretty everything ^^
[20:41] <persia> What data do you need?  There's probably another way to get it.
[20:41] <sebner> persia: debian changelog site xD  ... why merge gnurobots ... sync?
[20:42] <persia> sebner: apt-get source in a sid chroot, and I haven't investigated whether the Ubuntu changes may be dropped.
[20:42] <sebner> persia: there isn't an ubuntu change. just a rebuild. but before it was on autosync
[20:43] <persia> sebner: Great.  Now that you've investigated, would you like to file the bug?
[20:43] <sebner> persia: xD you are playing tricks :P Sure, I'll testbuild and file the bug then
[20:44] <persia> Don't forget tuxtype :)
[20:44] <sebner> haha
[20:44] <sebner> -.-
[20:44] <sebner> ok ok. I'm taking it as well
[20:44] <persia> Thank you.
[20:45] <sebner> persia: np, just wondering that gnurobots isn't on the RC list
[20:46] <persia> sebner: it's not RC.
[20:46] <sebner> persia: a app you like?  ^^
[20:47] <persia> Never used it.
[20:47] <persia> Just on one of my lists.
[20:48] <sebner> persia: and now I have to work on your list so you have time to upload uqm? ^^ ^^ ^^
[20:48] <persia> sebner: I just finished downloading the source, and will be reviewing the patch momentarily.
[20:49] <sebner> persia: I don't believe you until I see it uploaded :P
[20:49] <persia> sebner: You don't have to believe me if you don't like.
[20:49] <persia> Laney: Can you shed any light on the status of bug #229136?
[20:50] <persia> smarter: Maybe you have an idea?
[20:51] <smarter> persia: I'm still waiting for the Debian Maintainer to do something
[20:52] <smarter> I filled a bug with a patch to merge my changes to his package, but he never answered
[20:52] <persia> smarter: Well, if it doesn't happen in the next 249 minutes, it's not going to happen for intrepid.  Would you like to prepare a debdiff?
[20:52] <smarter> I may try
[20:52] <persia> smarter: Good luck, and thanks.
[20:53] <smarter> This stuff is a bit old, I may have forgotten how it worked (:
[20:53]  * smarter grabs his own patch and try to see what it does
[20:53] <persia> sebner: You could have told me someone else figured out the uqm packaging :)
[20:54] <sebner> persia: hmm? the git one?
[20:54] <RainCT> persia: do you have the u-u-s with tag link around?
[20:54] <persia> sebner: Indeed.  Anyway, it's not really an issue: less work for me :)
[20:54] <persia> RainCT: No, but I'll dig it out.
[20:54] <sebner> persia: ^^
[20:55] <RainCT> persia: don't worry, I'll search it myself then
[20:56] <persia> https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.searchtext=&orderby=-importance&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search
[20:56] <persia> 15 bugs currently on the list.
[20:56] <RainCT> thanks
[20:57] <stefanlsd_> That first one - Gpa I did.  Its been uploaded into intrepid and i've submitted the patches to debian.
[20:57] <persia> (and some of those are SRU or Debian, so I'm not sure exactly why they are there)
[20:58] <RainCT> stefanlsd_: ok, unsubscribed u-u-s
[20:58] <persia> Am I still here?
[20:58] <RainCT> persia: yep
[20:58] <persia> Excellent :)
[20:58] <sebner> persia: tuxtype = main?
[20:59] <persia> sebner: Apparently so.
[20:59] <stefanlsd_> ok. the next one with zaptel is also mine. heh.  https://bugs.launchpad.net/ubuntu/+source/zaptel/+bug/64059
[20:59] <sebner> persia: /me hides
[21:00] <persia> sebner: Don't let main scare you: it's probably a useful update, or it wouldn't have happened so close to the Debian freeze.
[21:01] <sebner> persia: ^^, kk
[21:01]  * RainCT is working on the sugar one
[21:01] <stefanlsd_> i think the problem with this is coming in that people are using asterisk with zaptel and asterisk is looking for /dev/zap/* with group asterisk, and its we have it as dialout.  I think thats correct and probably something we wont fix
[21:02] <RainCT> (although I'm tempted to reject it :P)
[21:03] <sebner> persia: I hope the contributors are doing a good job otherwise the reviewers will go wild xD
[21:04] <persia> sebner: Just to check, have you been adding the uus-pre-ff-810 tag on all the stuff that needs to get applied in the next 236 minutes?
[21:04] <stefanlsd_> Can we unsub u-u-s from 64059. i think its ok
[21:04] <RainCT> bug #64059
[21:05] <sebner> persia: ah. Didn't know that this exist xD but not needed for normal sync bugs I suppose!?
[21:05]  * nxvl dances
[21:06] <persia> sebner: Anything that includes a new upstream or a new feature needs that tag if you expect the sponsors to get to it before feature freeze (as announced by DktrKranz some days ago)
[21:06] <sebner> persia: as I said, "normal" sync bugs (no new upstream) don't need it right? That are most of mine :)
[21:07] <persia> nxvl!  Welcome to the last-minute rush against feature freeze.  We've 234 minutes to merge/sync/update/patch everything that might otherwise require a freeze exception.
[21:07] <persia> UUS needs you.  MoM needs you.  RCbugs needs you.  mdt needs you :)
[21:07] <sebner> persia: what about "We need you"
[21:07] <persia> sebner: No, a sync without a new upstream doesn't need it, unless that includes some significant feature additionl.
[21:08] <nxvl> persia: it smells like FF, things are going funnier and brains going to blow up!
[21:08] <persia> sebner: We always need nxvl, but today those four things need him especially.
[21:08] <persia> nxvl: Yep.  232 minutes left.  Get cracking!
[21:08] <slytherin> FF doesn't block FTBFS patches, right?
[21:08] <sebner> nxvl: We want you for the US Army .. ehm for FF bug hunting! ^^
[21:09] <persia> No, but good luck getting them sponsored right now :)
[21:09] <slytherin> :-)
[21:09] <nxvl> persia: i will find a table, i'm at the university right now and my class has been canceled
[21:10] <persia> nxvl: Excellent.
[21:10]  * persia is rubbing hands vigorously
[21:11]  * RainCT leaves the sugar sync for someone else :P
[21:11] <sebner> persia: tag is "uus-pre-ff-810" ?
[21:12] <persia> sebner: Yes.
[21:12] <sebner> kk
[21:13] <sebner> mok0: \o/
[21:13] <persia> hattory: Are you about?  Do you have time to discussion bug #250186 ?
[21:14] <persia> nhandler: Maybe you have insight?
[21:14] <persia> mok0: Join the team.  We're currently trying to crush https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.searchtext=&orderby=-importance&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=uus-pre-ff-810&field.tags_combinator=ANY&searc
[21:14] <persia> h=Search
[21:14] <persia> Except the URL works better if it's not hit by a buffer :)
[21:15]  * mok0 looks at the probably longest url ever seen
[21:15] <persia> mok0: Also, anything else you can find that needs to beat FeatureFreeze, needs to be pushed in the next 225 minutes.
[21:15]  * ScottK-laptop hands persia http://tinyurl.com/
[21:15] <mok0> persia: I am on the team
[21:15] <RainCT> http://tinyurl.com/ubuntu810
[21:16] <persia> Bah.  It's really just https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search
[21:16] <RainCT> that new custom alias thing is nice :)
[21:16] <mok0> persia: I was about to upload the linux-rt stuff at REVU
[21:16] <persia> mok0: Excellent choice :)
[21:16] <smarter> persia: debdiff here: http://ks33313.kimsufi.com/~smarter/pkg/extremetuxracer_0.4-1ubuntu1.debdiff :)
[21:16] <mok0> persia: I cannot test it though
[21:16] <persia> smarter: Stick it in the bug, and I'll pull, and run a test build.
[21:16] <persia> You'll fix it if it's broken?
[21:17] <nxvl> ready for blowing brain!
[21:17] <RainCT> ScottK-laptop: Launchpad may be slow, but packages.debian.org is way worse :P
[21:17] <smarter> okay
[21:17] <smarter> persia: I'll try
[21:17] <nxvl> party on!
[21:17] <smarter> persia: I also added a fix to bug #237830
[21:17] <nxvl> what are we working at?
[21:17] <nxvl> sponsoring queue?
[21:17] <persia> RainCT: Use packages.qa.debian.org : it gets fewer hits, and tends to contain more useful links.
[21:18] <persia> nxvl: There's 17 bugs in the sponsors queue that really need to be hit: https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search
[21:18] <persia> nxvl: It's also REVU day
[21:18] <mok0> ScottK:  I will probably need an FF exception for the eee-applet
[21:18] <sebner> persia: subscribing mighty u-m-s O_o ^^
[21:18] <RainCT> persia: Emmet Day, remember? ;)
[21:19] <persia> nxvl: http://qa.ubuntuwire.com/bugs/rcbugs/ lists some new upstreams, and we might want to push them.
[21:19] <smarter> persia: debdiff attached to bug 229136
[21:19] <nxvl> persia: i think sync are out
[21:19] <RainCT> packages.qa.debian.org works, thanks :)
[21:19] <smarter> bug #229136
[21:19] <persia> RainCT: Not "Emmet" Day.  No.
[21:19] <nxvl> persia: since we need an archive admin for that
[21:19] <persia> nxvl: Additionally, anything on MoM or mdt that would break FF but wants an update is fair game.
[21:19] <RainCT> persia: hehe
[21:20] <persia> nxvl: syncs aren't out.  We just need to get them approved and subscribed to the archive admins in the next 220 minutes.
[21:20]  * Adri2000 notes that DaD nicely shows new upstream releases with bold red :)
[21:20] <RainCT> what's mdt?
[21:20] <persia> Adri2000: Excellent point.
[21:20] <persia> Anything in RED on DaD ought get a look, especially as Debian is near frozen, so updates are only likely where required.
[21:21] <persia> mdt is http://qa.ubuntuwire.com/multidistrotools/ : http://qa.ubuntuwire.com/multidistrotools/universe.html is probably the link most interesting to us.
[21:21]  * smarter bbl
[21:21] <mok0> persia, what are those "changelog.intrepid" and "changelog.historical" in linux-rt?
[21:22] <sebner> persia: hey, you uploaded uqm. wuhu \o/
[21:22] <persia> mok0: From what I understand, changelog.historical is from the kernel when it was all together, and changelog.intrepid is for the new linux-rt kernel package.
[21:23] <persia> kernel packaging is rather frustratingly confusing, as it pulls in stuff from all over the place, and doesn't actually have any source.
[21:23] <persia> sebner: I did say I would, didn't I?
[21:23] <persia> sebner: Also, you got a special exception, as it didn't need to be uploaded today.
[21:27] <persia> Did my connection drop again?
[21:27] <persia> No.  Hurrah!
[21:29] <mok0> Only 1 package left in "advocated packages", if there's someone up to it, please have a look. I already advocated it.
[21:34] <emgent> back
[21:34] <persia> mok0: The other three may be archived?
[21:34] <sebner> emgent: norsetto \o/
[21:34] <emgent> heya norsetto
[21:34] <persia> emgent: Excellent :)
[21:34] <norsetto> hi gents and ladies
[21:34] <persia> norsetto: Welcome back :)
[21:35] <persia> norsetto: 205 minutes left until FeatureFreeze :)
[21:35] <sebner> norsetto: hide or persia is going crazy :P
[21:35] <emgent> persia: :)
[21:35] <sebner> too late xD
[21:35] <emgent> now, rock'n'roll
[21:36]  * norsetto gets his defrosters ready
[21:36] <sebner> persia: did you saw. uqm amd64 build has a chroot problem. *give back*
[21:36] <persia> norsetto: https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search is the key link to keep empty, although it keeps getting more.
[21:37] <persia> There's stuff on REVU, and DaD is highlighting any obvious FF-breaking merges in RED.
[21:38] <persia> sebner: What's the URL to the build?
[21:38] <sebner> persia: http://launchpadlibrarian.net/17122329/buildlog_ubuntu-intrepid-amd64.uqm_0.6.2.dfsg-8ubuntu1_CHROOTWAIT.txt.gz
[21:38] <norsetto> persia: I see there is some kind of very subtle hints you are trying to pass which is apparently lost on me
[21:39] <persia> sebner: No, the link to the page that has that link.
[21:39] <sebner> persia: hehe. true https://edge.launchpad.net/ubuntu/+source/uqm/0.6.2.dfsg-8ubuntu1/+build/702471
[21:40] <persia> norsetto: Essentially, we've 201 minutes to sponsor everything that would otherwise require an FFe, and to get any new packages we want from REVU, or updated sources from Debian.
[21:41] <norsetto> persia: oh, I apparently lost my ability to speack English
[21:42] <norsetto> persia: seriously though, I'm off to bed, was a long day today for me
[21:42] <persia> norsetto: Basta leggere
[21:42] <persia> Ah, too bad.  We could use your help.  Sleep well.
[21:44] <mok0> err looked at wxwidgets, but can't find <IP_ADDRESS>
[21:44] <sebner> norsetto: nighty
[21:44] <persia> devfil: Any ideas?
[21:44] <devfil> persia: let me read
[21:45] <RainCT> night norsetto
[21:45] <norsetto> night everybody
[21:45] <persia> sebner: uqm given back
[21:46] <devfil> persia: wxwidgets2.8 <IP_ADDRESS>?
[21:46] <persia> devfil: Yep.  mok0 can't find it.
[21:46] <devfil> https://bugs.edge.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/251260
[21:46] <sebner> persia: :) /me is now going back to work and filing sync bugs \o/
[21:47] <persia> Excellent.  Only 194 minutes left.
[21:47] <devfil> mok0: wxpython.org
[21:47] <devfil> you also can use get-orig-source provided with the package (best solution)
[21:47] <mok0> devfil: yes, I looked there
[21:47] <persia> mok0: I'm archiving the three packages fully advocated on REVU.  You've uploaded, right?
[21:48] <mok0> persia: yes
[21:48] <persia> mok0: Thanks for the confirmation.  Uploaded.
[21:49]  * persia gets distracted by real life and disappears for ~15 minutes
[21:49] <RainCT> is someone else already looking at rsplib?
[21:54] <mok0> RainCT: not to my knowledge
[21:55] <RainCT> mok0: uhm.. why do all descriptions in debian/control start by an empty line?
[21:55] <RainCT> and is there a needs-packaging bug for it?
[21:56] <devfil> mok0: have you found the tarball?
[21:57] <mok0> devfil: no
[21:57] <mok0> devfil: I am trying to get the source package
[21:58] <devfil> mok0: you can use the actual intrepid package to download the new tarball
[21:58] <RainCT> (found the needs-packaging bug)
[21:58] <devfil> just change the version on debian/rules and use get-orig-source
[22:01] <ScottK-laptop> RainCT: Not in my experience.
[22:01] <ScottK-laptop> Debian BTS is definitely faster.
[22:01] <ScottK-laptop> mok0: I think the packaging is fine.
[22:01] <ScottK-laptop> mok0: If you want me to advocate it and we can test later, that's fine.
[22:03] <mok0> ScottK: ok, I will advocate it then
[22:04] <ScottK-laptop> mok0: Since you uploaded it, it's automatically advocated by you.
[22:05] <ScottK-laptop> mok0: I added advocation, so you can upload it.
[22:05] <ScottK-laptop> mok0: Did you see I uploaded your other one?
[22:06] <mok0> ScottK: yes, I did, thanks a lot
[22:06] <RainCT> mok0: I'm pbuilding rsplib.. will upload it if it build fine :)
[22:07] <RainCT> *builds
[22:08] <mok0> ScottK: I uploaded the eee thingie.
[22:09] <mok0> ScottK: Thinking of getting the 901 when it appears in Denmark :-)
[22:10] <smarter> persia: have you testbuilt extremetuxracer yet?
[22:10] <smarter> 'cause it's already 11 PM here and I'll soon be off to bed
[22:12] <persia> smarter: Not yet.  I'll probably be another 30 minutes or so before I get to it.
[22:12] <smarter> 'kay
[22:13] <persia> Anyone else have a gap sooner to help smarter be able to go to bed earlier?
[22:13] <smarter> :)
[22:16] <emgent> persia: http://launchpadlibrarian.net/17124866/buildlog_ubuntu-intrepid-amd64.pgbouncer_1.1.2-1ubuntu1_CHROOTWAIT.txt.gz
[22:17] <persia> emgent: What's the page that links that?
[22:17] <emgent> https://launchpad.net/ubuntu/+source/pgbouncer/1.1.2-1ubuntu1
[22:17] <emgent> chroot problem in amd64 build box
[22:20] <stefanlsd> dev week is gonna be great
[22:23] <emgent> stefanlsd: :)
[22:24] <stefanlsd> So this is the end of new stuff in Intrepid?
[22:25] <james_w> ok, sorry to do this, but would someone be willing to sponsor a package update for me?
[22:25] <james_w> my usual sponsor is not here right now
[22:25] <james_w> http://people.ubuntu.com/~jamesw/packages/bzr-builddeb-2.0/bzr-builddeb_2.0~0ubuntu1.dsc
[22:26] <james_w> the packaging changes are trivial (debian/changelog, debian/NEWS, debian/copyright)
[22:26] <james_w> I've tested building, installing and using.
[22:26] <james_w> and I'm the upstream author.
[22:29] <mok0> RainCT: Did you take a look at rsplib?
[22:29] <james_w> mok0: thanks for uploading my two packages
[22:30] <mok0> james_w: they were important packages to get into ii
[22:33] <mok0> james_w: looking forward to play with them myself :-)
[22:34] <james_w> yeah, it could make our tools much more robust, and then some cool stuff may grow out of it.
[22:35] <devfil> mok0: thanks from me for gui-ufw
[22:36] <mok0> devfil: anything that makes ufw easier for users :-)
[22:37] <devfil> mok0: I have discovered it reading brainstorm, it is really requested
[22:38] <mok0> devfil: cool. I don't spend much time reading brainstorm myself
[22:39] <devfil> some ideas are really interesting
[22:40] <mok0> devfil: I agree
[22:41] <RainCT> mok0: yep, build fine.. uploading now
[22:41] <mok0> devfil: ubuntuforums and brainstorm make Ubuntu very special for users
[22:41] <mok0> RainCT: great, thx
[22:42] <devfil> mok0: I don't read much ubuntuforums, but I spend hours reading brainstorm
[22:42] <mok0> We have to make a big effort in the next cycle dedicated to REVU
[22:43] <smarter> persia: you're on it now? :)
[22:43] <persia> smarter: Apparently my estimate was a little off.  I'm waiting for a build to finish, but it's next in the queue.
[22:43] <mok0> I have the feeling that many REVU contributors are pretty frustrated
[22:44] <persia> I have the feeling that nearly all REVU contributors are frustrated.  We didn't really do much REVU this cycle, and it shows.
[22:44] <smarter> persia: ok, thanks
[22:44] <directhex> i prefer to work directly on debian versus revu. but the lenny freeze has bitten me
[22:45] <RainCT> persia: btw, nixternal said that I can take over the coordinator pos. I've to mail -motu somewhen but I'm not sure if makes sense now with the freeze
[22:45] <devfil> directhex: +1
[22:45] <wgrant> I cannot support any plan to increase REVU efforts.
[22:45] <wgrant> Why not just have people go to Debian?
[22:45] <directhex> hence mono-basic in revu. i'd rather it hit sid
[22:46] <persia> RainCT: Most of the coordinator work over the freeze period involves cleaning up the old "Needs Work" packages and setting expectations properly for the next release.
[22:46] <persia> I'd be happy if you want REVU Coordinator: I was afraid it would be me again next cycle :)
[22:47] <devfil> persia: if I want a package that I've uploaded in debian (but now in NEW) in ubuntu, do you suggest me to upload it now on REVU (is a really simple) or to request a freeze exception later?
[22:47] <RainCT> persia: alright, I'll write a mail within the next days then :)
[22:47] <persia> devfil: IF you think you can get two advocates in the next 133 minutes, upload to REVU.  Otherwise, it's better to seek a freeze exception.
[22:49] <devfil> persia: it is a simple gtk gui for virtualbox and doesn't have problems at all
[22:50] <ScottK-laptop> persia: Since it's been uploaded to Debian, I think one is enough.
[22:50] <devfil> maybe the best solution is to upload it now as it is not important to require a freeze exception
[22:50] <ScottK-laptop> devfil: Freeze exceptions for New packages are very hard to get.
[22:50] <mok0> Can someone please try clicking on "google-gadget" on REVU?
[22:50] <mok0> I get a strange error
[22:51] <devfil> ScottK-laptop: I know, this is why I'm uploading it
[22:51] <persia> ScottK-laptop: In that case, I would expect you to advocate based on it being in Debian NEW, to state your point :)  But yes, otherwise I agree.
[22:51] <mok0> http://revu.ubuntuwire.com/details.py?package=google-gadgets
[22:52] <persia> RainCT: ^^ Any ideas?
[22:52] <ScottK-laptop> persia: Sync's of new packages from Debian don't take two sponsors.  Only one.  The fact that the mechanics might have to be a little unorthodox doesn't change that IMO.
[22:52] <wgrant> I wonder if I add a custom error handler that tells people to upload to sid instead.
[22:52] <wgrant> ScottK-laptop: It's not a package in Debian.
[22:53] <ScottK-laptop> It's package that's been uploaded to Debian.  A very fine distinction.
[22:53] <persia> ScottK-laptop: I understand your point.  On the other hand, I think it's easy enough to reflect that without changing the system.
[22:53] <ScottK-laptop> Right.
[22:53] <persia> ScottK-laptop: So whoever reviews the package can probably ask here and say "It's also in NEW", and get someone to ACK with little fuss.
[22:54] <persia> (especially if the first person promises to upload)
[22:54] <ScottK-laptop> Yes.
[22:54] <ScottK-laptop> I'll be glad to if I'm around.
[22:55] <RainCT> mok0: does the package have a changelog? :P
[22:57] <mok0> RainCT: you mean the google one?
[22:57] <mok0> RainCT: I can't get to it
[22:58] <RainCT> yep. just fiex it
[22:58] <RainCT> *fixed
[22:58] <RainCT> mok0: the orig.tar.gz was missing for some reason and so dpkg-source -x wasn't executed
[23:02] <devfil> ScottK-laptop, persia: http://revu.ubuntuwire.com/details.py?package=vboxgtk
[23:02]  * ScottK-laptop looks
[23:03] <ScottK-laptop> devfil: You have a comment.
[23:04] <devfil> ScottK-laptop: I removed also all papt stuff and changed the manpage "for the Ubuntu project"
[23:04] <directhex> for the horde!
[23:04] <ScottK-laptop> devfil: Say that in a comment.
[23:04] <mok0> RainCT: thanks. Unfortunately the problems with that package are not yet fixed :-(
[23:05] <persia> smarter: Why change from CDBS to non-CDBS?
[23:05] <smarter> persia: to match Debian
[23:05] <persia> Oh.  Am I looking at a debdiff from Ubuntu to new Ubuntu?
[23:05] <persia> Can you attach a debdiff of your merge against Debian?
[23:05] <smarter> good idea, sorry ^^
[23:07] <devfil> ScottK-laptop: replied
[23:10] <smarter> persia: debdiff uploaded
[23:10] <persia> smarter: recollecting
[23:13] <devfil> ScottK-laptop: if you want a diff between Debian debian dir and Ubuntu debian dir let me know
[23:13]  * ScottK-laptop does svn up on his local copy of the papt repo.
[23:14] <devfil> ok
[23:17] <RainCT> good night
[23:18] <ScottK-laptop> devfil: debian/virtualbox-gtk is in Debian, but not your Ubuntu package.
[23:18] <directhex> mono-basic_1.9+dfsg-2_i386.changes uploaded successfully to localhost
[23:18] <directhex>         Your Debian queue daemon
[23:19] <devfil> ScottK-laptop: it shoudn't be there
[23:20] <ScottK-laptop> devfil: It's in the tagged copy of the debian/dir in the papt repo.
[23:21] <persia> 100 minutes to go.  Sponsors: not much left!
[23:22] <devfil> ScottK-laptop: uhm, maybe I forgot to remove it from svn, but as you can see in the install file it is not installed
[23:24] <devfil> ScottK-laptop: http://svn.debian.org/wsvn/python-apps/packages/vboxgtk/trunk/debian/install?op=diff&rev=1659&sc=1
[23:26] <devfil> ScottK-laptop: substituted by http://svn.debian.org/wsvn/python-apps/packages/vboxgtk/trunk/debian/links?op=diff&rev=1659&sc=1
[23:28] <persia> smarter: Looks clean.  Pushing.
[23:28] <smarter> persia: great
[23:28] <smarter> good night everybody
[23:28] <persia> smarter: Sleep well, and thanks for staying up to look at this.
[23:29] <jpds> bonsoir smarter
[23:29] <smarter> hasta luego jpds
[23:31]  * jpds closes some ubuntu-dev-tools bugs before heading off himself.
[23:31] <ScottK-laptop> devfil: Who sponsored it in Debian?
[23:31] <devfil> ScottK-laptop: POX
[23:31] <ScottK-laptop> OK.
[23:32] <ScottK-laptop> POX_ should apply for MOTU so he can advocate.
[23:32] <persia> https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search now has 18 bugs.  Let's get them done in the next 88 minutes :)
[23:32] <devfil> gh... my wxwidgets2.8!
[23:33] <persia> I know I don't have a build system capable of building that one :(
[23:33] <devfil> persia: the build logs are available on my ppa
[23:33] <ScottK-laptop> mok0 has done wxwidgets before.
[23:33] <devfil> only them
[23:34] <persia> devfil: Yes, but I only upload that which I can build (except when I make mistakes).  Maybe I'm too conservative, but that's how I do it.
[23:35] <devfil> persia: yes, however I think that wxwidgets2.8 can get the freeze exception, <IP_ADDRESS> is a bugfixonly release
[23:36] <ScottK-laptop> devfil: Advocated.
[23:36] <persia> devfil: Sure, but if we can get it in now, it's less work for the motu-release team later, as we know we want it.
[23:36] <persia> ScottK-laptop: Based on your previous assertion, if I ACK it also, will you upload?
[23:36] <RAOF> Gah!  Why does http://pastebin.com/f5b960558 run configure-stamp twice?
[23:37] <ScottK-laptop> persia: Sure.
[23:37] <devfil> persia: uhm... it needs 48 minutes on ppa if I remember right to build, what do you think?
[23:37] <azeem> RAOF: configure is PHONY
[23:37] <directhex> RAOF, configure is what azeem said
[23:37] <azeem> RAOF: build should probably depend on configure-stamp
[23:37] <persia> devfil: What's the REVU URL?
[23:37] <RAOF> azeem: but configure-stamp isn't.
[23:38] <devfil> persia: it is a bug https://bugs.edge.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/251260
[23:38] <azeem> RAOF: well, my gut feeling; I can't cite the make manual chapter now :-/
[23:38] <devfil> persia: or are you talking about vboxgtk?
[23:38] <azeem> or blame dh7
[23:38] <RAOF> I can't blame dh7; it never calls configure :)
[23:39] <directhex> phony has configure (which runs configure-stamp) and build (which runs configure which runs configure-stamp), no?
[23:40] <azeem> RAOF: hrm, could be a phony patch target imported from dpatch as well
[23:40] <azeem> or something like that
[23:40] <directhex> or maybe i'm just lost
[23:40] <RAOF> Yes.  So, build calls configure, which checks for configure-stamp; it doesn't exist, so configure-stamp is called.  Then install calls build which calls configure which checks for configure-stamp which now exists
[23:40] <azeem> RAOF: however, it's outdated, as configure is PHONY
[23:40] <azeem> AIUI
[23:41] <persia> devfil: vboxgtk
[23:41] <devfil> persia: http://revu.ubuntuwire.com/details.py?package=vboxgtk
[23:41] <persia> (or whatever package was in Debian NEW)
[23:41] <ScottK-laptop> That's the one.
[23:42] <persia> ScottK-laptop: It's all yours.
[23:43] <azeem> RAOF: also consider running make -d -f debian/rules build or something
[23:43] <devfil> persia, ScottK-laptop: thanks also for this
[23:43] <ScottK-laptop> devfil and persia: Uploaded.  I'll archive it too.
[23:46] <directhex> Subject: 	mono-basic_1.9+dfsg-2_i386.changes is NEW
[23:47] <persia> Only 74 minutes left, and still 18 bugs needing sponsoring.  Does anyone else have free build cycles?
[23:47] <RAOF> azeem: Aha. patch is phony, so always gets rebuild, triggering a rebuild of configure-stamp!
[23:48] <james_w> persia: I can test build if that is what you are after
[23:48] <devfil> persia: I'm uploading wxwidgets2.8 to my PPA
[23:48] <james_w> persia: I understand if that doesn't get you to where you want to be
[23:48] <persia> james_w: Well, yes, but really I want sponsors to build the source, test the result, sign, and upload.  I'm not sure how much you can help with that.
[23:48] <persia> devfil: Doesn't help me, but might help someone else.
[23:49] <james_w> persia: not really, I'd only be weeding things out.
[23:50] <persia> james_w: Well, if you've time and want to look at https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search and see if you can find anything that isn't realy to go, that could be helpful.  Even better if you can make sure it is ready to go before a sponsor gets to it.
[23:50] <james_w> persia: I'll do what I can
[23:50] <persia> james_w: 8 of them are sync requests, which are probably the easiest place to start.
[23:51] <jelmer> persia, does that mean whatever is not tagged uus-pre-ff-810 won't make it into intrepid?
[23:51]  * persia wants more processors and more memory and more minutes :)
[23:51]  * Laney screams
[23:51]  * ScottK-laptop considers that the only way to stop getting mail list invites for indirect subscriptions is to deactivate himself from ubuntu-dev.
[23:52] <persia> jelmer: No.  It means that the sponsors aren't reviewing things without that tag during the next 69 minutes, and anything that doesn't get uploaded in that time needs a Feature Freeze exception.
[23:52] <persia> Laney: Why?
[23:52]  * devfil thinks that persia want to stop the time
[23:52] <Laney> Oh no worries, just got to make a small change
[23:53] <Laney> FF paranoia
[23:53] <persia> Laney: Remember that you can still fix bugs post FF, just not introduce features.
[23:53] <Laney> persia: Yes, it's a package update
[23:53] <Laney> as in new version
[23:53] <Laney> althought the original sponsorship request was a couple of days ago, so I guess it'll be fine anyways
[23:53] <persia> Yeah, that needs to happen right this moment, and if it takes you a while to do, you'll be too late.
[23:54] <persia> Which bug?
[23:54] <Laney> bug #261158
[23:54] <jelmer> persia, ah, ok
[23:54] <Laney> (personally I'd leave the php4 alternatives in)
[23:55] <persia> php4 is dead, and we want it that way.
[23:55]  * jelmer looks forward to filing 7 ff exceptions
[23:55] <slangasek> php4 is dead, references to it ought to be dropped wherever feasible
[23:55] <Laney> Is it supported in any releases currently?
[23:56] <persia> It's in Dapper, but it's not supported upstream, and unlikely to be well maintained in Dapper as a result.
[23:56] <Laney> But php5 is also in dapper...
[23:56]  * Laney removes
[23:56] <ajmitch> security support for php4 has stopped
[23:56] <persia> Laney: Yeah, you need to update, push the new debdiff, and set the status to something better.
[23:56] <ajmitch> (from upstream)
[23:56] <Laney> I'll do it now, easy change
[23:56] <persia> ajmitch: Indeed.
[23:57] <persia> ajmitch: Want to help clear the queue?
[23:57] <persia> Oh, and Good Morning :)
[23:57] <ajmitch> persia: for what?
[23:57]  * ajmitch is at work, been organising hardware upgrades & annoying out-of-hours work
[23:58] <persia> ajmitch: FeatureFreeze is in 62 minutes, so we're trying to get everything listed at https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search sponsored beforehand.
[23:58] <persia> Oh, well, if you're busy at work, then maybe not so much :(
[23:58] <ajmitch> yeah
[23:58] <ajmitch> and I don't have an updated intrepid pbuilder
[23:59] <persia> And you live down the wrong end of narrow tubes


[00:24] <robru> yay
[01:04] <kenvandine> robru, btw... i kicked the tires a little on your new tool, sorry i didn't really have any feedback :)
[01:04] <kenvandine> i was just excited to see the end of the spreadsheet in sight i couldn't think straight :)
[01:04] <robru> kenvandine: i saw that, thanks. I've managed to find enough holes in my own so far ;-)
[01:05] <kenvandine> robru, i think the only thing i didn't understand was the status field
[01:05] <robru> It's down atm due to redeploying issues.
[01:05] <kenvandine> it's free form?
[01:05] <robru> kenvandine: yeah the status field will be set by Jenkins mostly.
[01:05] <kenvandine> ok, shouldn't let it be editable my me then :)
[01:05] <kenvandine> also there was no choice for dual landing
[01:05] <kenvandine> but i typed it in
[01:06] <robru> kenvandine: yeah all the fields are free form
[01:06] <kenvandine> s/my/by/
[01:06] <robru> I'll add dual as an option
[01:06] <kenvandine> i think those were the only issues i noticed
[01:06] <kenvandine> i expected status to be read-only
[01:06] <kenvandine> it's all VERY exciting though!
[01:08] <robru> kenvandine: thanks, yeah I'm hoping to have this ready in a week + however long it takes for #is to do the production rollout
[01:09] <kenvandine> awesome!
[07:38] <sil2100> jibel, davmor2, popey, ogra_: I suppose there's nothing to discuss today as well, right?
[08:05] <jibel> sil2100, works for me
[08:07]  * ogra_ has always something to discuss :P
[08:07] <davmor2> sil2100: probably not
[08:07] <ogra_> not particulary for this meeting though :)
[08:07] <sil2100> ;p
[08:10] <jibel> sil2100, I supposed your question implied that you'll cancel the meeting, hence my reply :)
[08:11] <ogra_> he did so, 15 min ago :)
[08:15] <mterry> rsalveti, hey btw, here's a little presentation I made.  I don't know how we are presenting stuff today, but you can use some of its slides maybe: https://docs.google.com/presentation/d/1fQ_1kSp6nacLa5970GMl3RxALQR0216_UpOtj4SR-ZQ/edit#slide=id.gb5009c440_0_141
[08:16] <ogra_> mterry, echan ? :)
[08:16] <mterry> ogra_, ineed
[08:27] <dbarth> hola
[08:27] <dbarth> hey trainguards, can you help me reconfig silo 001; i have added a branch that the tool doesn't like me to add myself
[08:28] <sil2100> dbarth: hey! On it
[08:28] <sil2100> dbarth: reconfiguring
[08:28] <sil2100> Should be good now
[08:29] <ogra_> sil2100, bug 1465214 .... i wouldnt actually call "Add debugging to figure out what's happening.." being "Fix Released" :)
[08:34] <jibel> ogra_, the commit message is wrong, it's more than just adding debug information.
[08:35] <ogra_> jibel, bah
[08:35]  * ogra_ did just set it back to "In Progess"
[08:35] <jibel> ogra_, the real fix is "Wait for SIM Manager interface to be fully initialised before we try and unlock any SIMs"
[08:36] <jibel> s/fix/message/
[08:37] <jibel> and it also fixes the case where you couldn't unlock your SIM if you boot with airplane mode on. 2 bugs with 1 fix :)
[08:37] <ogra_> i dont see that line anywhere in the changelog
[08:37] <jibel> https://code.launchpad.net/~pete-woods/indicator-network/sim-unlock-debugging-lp1465214/+merge/262108
[08:38] <jibel> this is what landed
[08:38] <pete-woods> jibel: yay :)
[08:38] <ogra_> jibel, right, but the package changelog (which is what counts) has some other message ...
[08:39] <pete-woods> dammit, forgot to rebuild after setting the commit message correctly
[08:39] <jibel> ogra_, yeah as I said the commit message was wrong
[08:39] <ogra_> pete-woods, you shouldnt have to ... changing it should auto-rebuild imho
[08:40] <ogra_> sil2100, ^^^ could the train check for that ?
[08:41] <ogra_> (so we dont end up with outdated changelogs)
[08:43] <sil2100> uh
[08:43] <sil2100> hm
[08:43] <sil2100> Need to look into the LP API
[08:43] <ogra_> pete-woods, hmm, that should be in todays image ... to which i just OTAed ... and on which i had to use the terminal to unlock :(
[08:43] <pete-woods> it wasn't landed when I eod'd last night
[08:44] <ogra_> phew
[08:44] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/vivid/20150626.changes has it listed
[08:44] <pete-woods> crap
[08:44] <ogra_> so why didnt it come to me with that OTA
[08:44] <ogra_> (i have the old one installed)
[08:44] <pete-woods> oh, that's a relief
[08:44] <ogra_> phablet@ubuntu-phablet:~$ dpkg -l |grep indicator-network
[08:44] <ogra_> ii  indicator-network                                    0.5.1+15.04.20150611-0ubuntu1                     armhf        Systems settings menu service - Network indicator
[08:45] <ogra_>  weird ... what did i just OTA to
[08:45] <ogra_> seems i'm on 38 ... now thats strange
[08:45]  * ogra_ checks for updates again
[08:46] <ogra_> ... and there is 39 waiting ... i wonder how thats possible
[08:46] <pete-woods> cosmic rays
[08:46] <ogra_> yeah, very weird
[08:47]  * ogra_ crosses fingers
[08:47] <ogra_> and there is a SIM dialog :D
[08:50] <jibel> ogra_, do you mean you received an update notification and you OTA-ed to 38 instead of 39 or you didn't receive a notification for 39 at all?
[08:51] <ogra_> jibel, yeah
[08:51] <ogra_> well, i had 38 waiting when i got up
[08:51] <ogra_> seems it didnt update the info and downloaded 39 even though it was available
[08:52] <ogra_> might be some network glitch though ... i'll keep an eye open if it happens again
[08:54] <jibel> sil2100, there are lot of package built in silo and nothing ready to land really?
[08:54] <jibel> packages* even
[08:55] <sil2100> ;)
[08:55] <sil2100> jibel: eh...
[08:56] <sil2100> I blame summer
[08:58] <jibel> sil2100, if nothing lands soon, we'll be strict and won't accept any silo after the gates are closed
[10:27] <bzoltan_> sil2100: robru: may I ask for a silo please?
[10:32] <sil2100> bzoltan_: sure thing!
[11:44] <jibel> pete-woods1, BTW, while running the indicator-network test plan I noticed that the test indicator-network/unlock-sim-connectivity-service-dbus-api fails. the query for ril_0 returns SIM2 and ril_1 returns SIM1
[11:44] <jibel> I'll file a bug
[11:45] <pete-woods1> jibel: will have a look at it
[11:46] <pete-woods> (after I've finished crying that is)
[11:46] <jibel> pete-woods, the issue was already there without the silo
[11:47] <davmor2> jibel: I think there is already a bug for that
[11:48] <jibel> davmor2, probably, you need something, there is always a bug for it :)
[11:48] <jibel> davmor2, do you have the bug #?
[11:49]  * sil2100 needs to jump out for lunch
[11:49] <sil2100> o/
[11:49] <ogra_> use the stairs !
[11:49] <davmor2> jibel: not off the top of my head but I'm sure I was going to file it ages ago and it was already filed
[11:53] <davmor2> joc_: ^ I think this was one of your bugs right?
[13:11] <bzoltan_> sil2100:  thanks
[13:19] <sil2100> yw!
[13:41] <joc_> davmor2: i did raise a bug about SIM unlock dialog from indicators yes
[13:43] <joc_> bug 1449925
[13:44] <davmor2> jibel: ^
[13:44] <davmor2> joc_: thanks
[13:47] <jibel> davmor2, it's different.
[13:47] <davmor2> jibel: ah fair enough just the description sounded similar
[13:49] <jibel> davmor2, yeah, in my case when you send the dbus call to unlock SIM1 it shows the prompt for SIM2 and not only the title is wrong. It really asks to unlock SIM2 (the pins are different on my 2 sims)
[13:50] <davmor2> jibel: ah right not just a title mis-match then
[13:54] <jgdx> is sjenkins down? I can't connect.
[14:23] <jibel> davmor2, actually I might be wrong. I'll double check but I locked my SIM and have to find the PUK now :/
[14:57] <pete-woods> jibel: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1449925 ?
[14:57] <pete-woods> davmor2 ^
[14:57] <pete-woods> I think it's that known one
[15:01] <jgdx> pete-woods, s-jenkins was down for me til now, so the new wpa-ep debs has just been kicked off. Will take 1.5 hours-ish.
[15:01] <jgdx> so you know what to do on your friday evening :p
[15:11] <davmor2> pete-woods: it's jibel that has hit it I think
[15:19] <dbarth> trainguards: o/ i have a new silo requests on line 58
[15:19] <sil2100> dbarth: woohoo, on it
[15:27] <rvr> karni: ping
[15:27] <karni> rvr: soon, in meeting
[15:31] <dbarth> ok thanks
[15:44] <karni> rvr: hi :)
[15:44] <karni> rvr: how can I help
[15:44] <rvr> karni: Hi
[15:44] <rvr> karni: I'm testing telegram
[15:44] <karni> :)
[15:45] <rvr> karni: I figured out where the click package was, the document links to the scope twice
[15:45] <karni> oooh, I'm sorry!
[15:45]  * karni fixes right now
[15:45] <rvr> karni: No problem
[15:45] <karni> oh, you found it
[15:45] <rvr> karni: I found an issue that must be solved before approving
[15:45] <karni> rvr: yes?
[15:45] <rvr> karni: In the scope, the Telegram message is not translated
[15:46] <karni> rvr: you mean there's an unranslated string like "Telegram message"?
[15:47] <rvr> karni:  "Could not retrieve your telegram data"
[15:48]  * karni looks
[15:49] <karni> rvr: we're talking about spanish specifically? (or there's requirement for more languages explicitly to pass QA)
[15:49] <rvr> karni: Spanish, German, French...
[15:50] <karni> interesting. I see no strings missing from translation for the scope on lp, and this in the source:
[15:50] <karni> scope/src/query.cpp:     res["title"] = _("Could not retrieve your telegram data");
[15:50] <karni> rvr: looking into it now
[15:57] <karni> rvr: seems like this string is marked for translation, but not included in the pot file. I'll consult Kyle
[15:58] <rvr> karni: Ack
[16:10] <rvr> karni: There is also a bunch of translated but non-approved strings in Launchpad for Spanish
[17:17] <sil2100> davmor2, jibel: is the emulator working already in rc-proposed?
[17:17] <sil2100> I can't find the bug
[17:22] <jdstrand> hmm
[17:23] <jdstrand> so, silo 011 was setup for ubuntu-system-settings-online-accounts (fine)
[17:23] <jdstrand> but there is an apparmor-easyprof-ubuntu change that should be tested with it
[17:23] <jdstrand> (also fine)
[17:23] <jdstrand> so in the spreadsheet I added apparmor-easyprof-ubuntu to column G of line 53
[17:23] <jdstrand> (also fine)
[17:24] <jdstrand> I uploaded apparmor-easyprof-ubuntu to the ppa directly (also fine)
[17:24] <jdstrand> and then realized that I probably need to reconfigure the silo
[17:25] <jdstrand> I then looked in the ppa and saw that ubuntu-system-settings-online-accounts is there for both vivid and wily
[17:25] <jdstrand> but I only uploaded apparmor-easyprof-ubuntu for vivid, since wily already has the fix
[17:27] <jdstrand> so now I don't know how to proceed
[17:27] <jdstrand> sil2100: ^
[17:33] <jibel> sil2100, it doesn't work, cf bug 1458689 and its duplicate
[17:48] <anpok> ping trainguards hmm where can I reconfigure my silo?
[17:49] <robru> anpok: the "Landing tools" menu at the top of the sheet has the reconfigure link
[17:50] <robru> jdstrand: delete the wily package and reconfigure the silo for vivid rather than dual
[17:50] <robru> jdstrand: actually wait, it's dbarth's silo, does he not want his thing built for both wily and vivid?
[17:52] <jdstrand> robru: honestly, I was surprised to see the wily package. we didn't discuss that
[17:53] <robru> jdstrand: I would confirm with him before tinkering with stuff.
[17:53] <jdstrand> robru: that said, this isn't a dependency thing-- it is just that things will still be quite noisy without the apparmor-easyprof-ubuntu change
[17:53] <jdstrand> robru: ok, he seems offline so I'll send him an email
[17:53] <robru> jdstrand: yeah, sorry. only dbarth knows why he chose the silo to be dual.
[17:55] <awe> robru, jhodapp, I want to grab row54 in the citrain, but you both are shown as hovering over its columns.  Just wanted to ensure I wasn't going to conflict with either of you...
[17:55] <jhodapp> awe: it's all good, no worries on my end
[17:55] <jhodapp> thanks
[17:55] <awe> np
[17:55] <robru> awe: yep go for it
[18:00] <robru> anpok: congrats on being the first person to use my brand new silo reconfigure job ;-)
[18:02] <anpok> robru: was confused by the request_id
[18:03] <anpok> and managed to do lots of copy and paste errors :)
[18:03] <robru> anpok: oh, what? request_id should be generated for you.. what were you copy&pasting?
[18:03] <anpok> robru: I thought I need to use the request id from the spread sheet..
[18:03] <anpok> i guess I used the wrong job?
[18:04]  * anpok used -> https://ci-train.ubuntu.com/job/prepare-silo/
[18:04] <robru> anpok: yeah but how did you get there?
[18:04] <anpok> from the dashboard 'reconfigure silo' .. couldnt finde the landing tools on the spreadsheet
[18:04] <anpok> aerm 'Prepare silo'
[18:05] <anpok> btw have to make another reconfiguration for gtk
[18:05] <anpok> robru: so where is the real thing?
[18:06] <robru> anpok: top of the spreadsheet, "Landing tools > Assign/Reconfigure" menu. it pops up a link, you click it, and it fills out the form for you. No copy & pasting is necessary.
[18:06] <robru> awe: silo 20
[18:06] <awe> robru, thanks!
[18:07] <robru> awe: you're welcome
[18:07] <anpok> ahh the google spreadsheet menu.. didnt expect to find anything there
[18:08] <robru> anpok: yeah there. don't worry, spreadsheet will be gone in a couple weeks and you'll have to relearn the new system all over ;-)
[18:09] <anpok> robru: interesting behavior..
[18:10] <anpok> i had the first or second row of the spreadsheet selected..
[18:10] <anpok> and it tried to reconfigure "Landing Documentation"
[18:11] <robru> anpok: yeah you have to select the correct row first, that's how it figures out what row to assign.
[18:11] <robru> anpok: the replacement smoothes out all that crap. each row will have an "assign" link that just does the right thing without surprises.
[18:14] <robru> I'm about to go for lunch, anybody need anything before I go?
[18:25]  * robru -> lunch
[18:35] <bzoltan_> robru: how is this failure possible? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+packages the non gles package builds well.. and the amd64 builds well.. also the 15.04 target builds well. magic... black one
[18:46] <robru> bzoltan_: in ci-train, anything is possible ;-)
[18:46] <robru> bzoltan_: checking
[18:48] <robru> bzoltan_: did you read the error log? https://launchpadlibrarian.net/210065299/buildlog_ubuntu-wily-i386.ubuntu-ui-toolkit-gles_1.3.1541%2B15.10.20150626-0ubuntu1_BUILDING.txt.gz looks like there's some kind of API difference there. could it arise from differences in underlying tooling between wily/vivid?
[18:48] <robru> bzoltan_: if you think it's a transient hiccup I'm happy to retry the job
[18:48] <robru> awe: oh, hmmmm
[18:49] <bzoltan_> robru:  the tool is indeed different, but should not be a diff between amd64 and i386
[18:49] <bzoltan_> robru:  thanks for pushing a retry
[18:53] <robru> awe: seems whitespace in column G screwed up the silo config, fixed, trying again: https://ci-train.ubuntu.com/view/1.%20Build/job/ubuntu-landing-020-1-build/162/console
[19:31] <robru> bzoltan_: no idea about that failure, sorry
[19:31] <bzoltan_> robru:  Ok, I try to dig out something from the logs
[23:45] <robru> bregma: you need to rebuild 21.
[23:50] <robru> bregma: i don't know what's happened but the revision numbers are way wrong. It looks like 10 commits disappeared. Build log references revision 3967 but mp has up to 3957. Definitely needs a rebuild to account for whatever changes are there.