[00:01] <arand> The game redeclipse contains these items, but it's not available in "the preferred form for modification" (i.e. psd files, sequencer audio project files, etc.), which is why it was packaged in Debian "non-free".
[00:02] <RAOF> Multiverse is similar to non-free.
[00:03] <arand> Yes, I know, but I'm asking if Ubuntu has the same criteria for data that Debian has (lately)?
[00:03] <RAOF> Pretty much, yes.
[00:04] <arand> Ok
[01:25] <micahg> arand: the Ubuntu DFSG is slightly more lenient than the Debian version
[01:30] <arand> micahg: Hmm, does it affect what is considered "source" for an audio file for example?
[01:30] <micahg> arand: I'm not sure on specifics unfortunately
[01:31] <arand> Well, hmm, I guess the Ubuntu Font is in the same seat really, (source files in some unaccesible-ish proprietary format), and that's in main, right? :D
[01:35] <arand> Hence I figured Debian and Ubuntu's view on what 'source' entails differs slighly, and hence the requirements for Debian-Main and Universe...
[01:37] <arand> But I guess it's a wasps nest, at that... :)
[01:37] <micahg> arand: it's also license dependent which form is required
[01:38] <arand> Yeah, in this case it's CC-BY[-SA], so that doesn't give any hint.
[01:39] <arand> (or more permissive)
[04:59] <crimsun> these 180-min buildd timeouts are frustrating, particularly when I can't reproduce the build failures in schroots
[05:30] <John_____> This will take 10 minutes out of your life. I hope you have them:)) . We will be extremely grateful. We love Ubuntu. We hope Ubuntu developers are nice. I have never ever asked any Ubuntu dev. for any 'favour' since my adventure with Ubuntu started 5 years ago.  It looks like nobody has cared for 1.5 years (will be at the release time of 12.04). Over a year ago Ralink open sourced their drivers (links below), Fedora applied t
[05:31] <John_____> I've searched the issue on the net. Many (believe me) people are outraged and any solution is really bad. I tried to install manually, but failed due to failed initramfs update (perhaps it doesn't update on an USB flash drive...). Everyone hoped Ubuntu to pick it up- its on 11.10 bug report under 810111)
[05:31] <John_____> The solution to apply the patches from OpenSuse  (more likely they are NOT needed at all for the newer driver version below) and installing the drivers manually every time there's a kernel update is not nice. Talk about long FIVE YEARS. Dreadful. Hope you are a nice person and will help me (or more precise: us).
[05:31] <John_____> The solution to apply the patches from OpenSuse  (more likely they are NOT needed at all for the newer driver version below) and installing the drivers manually every time there's a kernel update is not nice. Talk about long FIVE YEARS. Dreadful. Hope you are a nice person and will help me (or more precise: us).
[05:32] <John_____> Please update patches for Ralink RT5390 to the (X)Ubuntu 12.04 LTS. Its critical not just for me (...). I hope you are nice person and will fix the bug as soon as possible and get back to me when its available in Xubuntu nightly build. Its getting close to LTS release and I have nobody to rely upon. I hope you folks in Ubuntu are nice. Otherwise I will be stuck with sloooooow yum (despite the fastestmirror-plugin), and other 
[05:32] <John_____> Please update patches for Ralink RT5390 to the (X)Ubuntu 12.04 LTS. Its critical not just for me (...). I hope you are nice person and will fix the bug as soon as possible and get back to me when its available in Xubuntu nightly build. Its getting close to LTS release and I have nobody to rely upon. I hope you folks in Ubuntu are nice. Otherwise I will be stuck with sloooooow yum (despite the fastestmirror-plugin), and other 
[05:32] <John_____> This driver is required for many, many, many HP laptops.   Thanks in advance, (X)Ubuntu Lover, John  Open Source RT539x: http://www.ralinktech.com/en/04_support/license.php?sn=5001  All Ralink Linux drivers: http://www.ralinktech.com/en/04_support/support.php?sn=501
[05:32] <John_____>  PS. I hope this time the AMD Northern Islands drivers will be ready and jockey in 12.04 will install them. No compiz tearing and no video tearing (sync to vblank).
[05:35] <crimsun> John_____: you're better off filing a bug against 'linux' and providing links to the Fedora and openSUSE bug reports.
[05:36] <crimsun> John_____: please be aware that we're past feature freeze, so it's highly unlikely those drivers will land in 12.04.
[05:39] <John_____> kernel freeze is in 5 weeks, its not a feature, its driver long overdue
[05:40] <John_____> bug is inder: 810111 in 11.10 its still stands
[05:41] <crimsun> John_____: it is a feature addition, since the current kernel does not ship a driver.
[05:42] <crimsun> John_____: regardless, this irc channel is not the best venue; please file a bug report against 'linux' as recommended earlier. You may also contact kernel-team at lists.ubuntu.com, and there is an irc channel: #ubuntu-kernel.
[05:42] <John_____> feature is a button, it will take less time than your denial, sorry you are rude I'm out
[05:42] <ajmitch> classic example of how not to motivate developers to jump to demands
[07:47] <dholbach> good morning
[07:47] <dholbach> happy fix it friday! :)
[07:57] <dholbach> is anyone here for Fix It Friday? :)
[07:59] <vibhav> I actually know a bit of packaging
[08:00] <vibhav> But cant fix bugs :(
[08:00] <vibhav> IS it important to be a developer to apply for MOTU ?
[08:02] <dholbach> welcome vibhav, no, you don't need to be member of a team to be able to fix bugs
[08:02] <vibhav> dholbach: What I meant was that *I dont know how to fix bugs* but wanted to apply for MOTU
[08:03] <dholbach> as long as you just attach patches to bug reports and subscribe 'ubuntu-sponsors', or bzr branch from ubuntu:<package>, push your changes to Launchpad and propose a merge, your suggested changes should turn up in review queue where somebody will take care of them
[08:03] <dholbach> ah ok
[08:03] <dholbach> you might want to have a look at http://developer.ubuntu.com/packaging/html/fixing-a-bug.html then
[08:03] <dholbach> (if you know some bits of packaging already)
[08:04] <vibhav> I know packgaing, but I dont know a programming language :(
[08:04] <dholbach> otherwise http://developer.ubuntu.com/packaging/html/introduction-to-ubuntu-development.html and http://developer.ubuntu.com/packaging/html/getting-set-up.html might be interesting too
[08:04] <dholbach> why don't you start with an easier bug then - today we wanted to have a look at bugs which have been fixed elsewhere
[08:04] <dholbach> https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream&orderby=-id is the bug list
[08:05] <dholbach> in an ideal case it would "just" be a matter of finding the fix either upstream or in Debian (or another distro) and applying it to the Ubuntu package
[08:05] <vibhav> thats interesting
[08:06] <dholbach> cool :)
[08:06] <vibhav> dholbach: thanks
[08:06] <dholbach> if there's anything else which is unclear, just ask :)
[08:07] <dholbach> I added links to docs, TODO lists and so on to http://pad.ubuntu.com/OsSL8mOs2o - it'd be great if everybody listed what they worked on on the pad as well - that'll make writing a summary of the event later on much much easier :)
[08:09] <vibhav> dholbach: I package through debuild, is that fine?
[08:09] <dholbach> yes
[08:16] <vibhav> dholbach: For example , I want to package Unity Fixing this bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/943223
[08:17] <vibhav> I downloaded the source, what do I need to do now?
[08:18] <dholbach> vibhav, unfortunately this might be a bad example - as far as I know this has been packaged in a PPA already and will soon be released to Ubuntu, but didrocks would know more about this
[08:18] <didrocks> there are still regressions in the release candidate
[08:18] <didrocks> so we are fixing them before releasing in ubuntu
[08:19] <vibhav> I see
[08:19] <didrocks> and this fix is even not confirmed
[08:19] <didrocks> so just need to be patient :)
[08:19] <dholbach> didrocks, so it might be better for vibhav to pick another "fixed elsewhere" bug?
[08:19] <didrocks> dholbach: I would mean, don't package unity right now ;)
[08:19] <dholbach> ok :)
[08:19] <didrocks> as we are in a release mode, everything will go in the current release
[08:28] <vibhav> Let me start again
[08:28] <vibhav> What I have to do is, find a random package with a bug fixed upstream
[08:29] <vibhav> Download the patch, apply the patch and package it, right?
[08:30] <dholbach> yes, that should be it
[08:30] <dholbach> ciao xdatap1
[08:33] <vibhav> From where do I find programs whose bugs are fixed upstream?
[08:33] <dholbach> https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=resolved_upstream&orderby=-id
[08:34] <xdatap1> dholbach, guten morgen!
[08:34] <dholbach> xdatap1, come stai? cosa fai?
[08:35] <xdatap1> dholbach, I'm taking care of my new baby: https://wiki.ubuntu.com/ItalianCD
[08:35] <xdatap1> dholbach, tonight I released the first image, based on beta1, for testing
[08:35] <dholbach> wow
[08:36] <dholbach> good work
[08:36] <xdatap1> dholbach, *last night, I meant
[08:36] <xdatap1> dholbach, thanks, we're all very excited about it
[08:37] <xdatap1> dholbach, If you're interested in the work in progress I created an english BP: https://blueprints.launchpad.net/ubuntu-defaults-it/+spec/precise-default-it
[08:38] <vibhav> dholbach: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/261595 IS fixed upstream, from where do I find its patch?
[08:41] <dholbach> vibhav, if you have a look at the top of that page, you see two lines one saying   "Mozilla Thunderbird"   and one saying  "thunderbird (Ubuntu)"
[08:41] <dholbach> both show the status of the same bug both Upstream and in Ubuntu
[08:41] <vibhav> dholbach: yes
[08:41] <dholbach> Upstream the bug was marked as "Invalid"
[08:41] <dholbach> so it's not necessarily fixed upstream
[08:41] <vibhav> ok
[08:45] <vibhav> dholbach: I found this bug https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/934433
[08:45] <vibhav> From where do I get its patch?
[08:46] <dholbach> in the line where it says "elfutils (Debian)", do you see the "debbugs #657139"?
[08:46] <dholbach> that's a reference to the upstream bug report
[08:46] <vibhav> yes
[08:46] <vibhav> I just went to that URL
[08:46] <dholbach> oh and in the bug report itself there's a patch too
[08:47] <dholbach> and the 'ubuntu-sponsors' team is subscribed to the bug already
[08:47] <dholbach> so that one is likely handled already
[08:47] <dholbach> you seem to be really good at picking the false positives :-/
[08:47] <vibhav> :(
[08:48] <dholbach> let me see if I can find one for you
[08:48] <vibhav> thanks
[08:48] <dholbach> but it is like that, sometimes you need to put a bit detective work into it
[08:48] <dholbach> don't give up yet :)
[08:48] <vibhav> This  is interesting though
[08:50] <dholbach> https://bugs.launchpad.net/ubuntu/+source/cssutils/+bug/931624 might work for example
[08:51] <dholbach> or https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916
[08:54] <vibhav> dholbach: The second bug, from Where do I get the patch now?
[08:58] <dholbach> vibhav, one option would be to download the source package from Ubuntu and Debian and diff the initscripts in there
[09:00] <tumbleweed> dholbach: the cssutils issue is fixed in Debian (where it's maintained by an ubuntu developer), and the tests are disabled in Ubuntu
[09:01] <dholbach> tumbleweed, ah, so we can close that one?
[09:01] <tumbleweed> I think porthose_spider wanted to sync it
[09:02] <tumbleweed> but yes, the temporary disabling of tests means it can be closed, I think
[09:02] <dholbach> great :)
[09:02] <broder> tumbleweed: ran into some friends of yours at the stripe ctf event today, though i don't remember their names at all
[09:02] <tumbleweed> broder: ah, so it was you, they remembered an "aron" :P
[09:03] <broder> heh
[09:04] <dholbach> broder, hey Aron - how are you doing? :)
[09:05] <dholbach> thanks for helping out with the d-a-t :)
[09:05] <broder> dholbach: hey :) np - things are good. looking forward to spending some time this weekend jamming. how're you?
[09:06] <dholbach> good good - reviewing a couple of things from the sponsoring list and trying to help out with Fix-It Friday
[09:06] <broder> yeah, i think i'm likely to spend most of my jam time working on the queue
[09:06] <dholbach> it's great - today is not only the start of Global Jam and Fix It Friday, but also an ARM Porting Jam from the ARM/Linaro folks
[09:06] <tumbleweed> dholbach: thanks for kicking of the doc-testing, sorry I'm tied up in moving house atm
[09:07] <tumbleweed> (which also means I'm not doing a global jam, but maybe I can get some people together next week...)
[09:07] <dholbach> tumbleweed, don't worry - sometimes it takes a bit to realise that it's better to bundle initiatives :)
[09:12] <vibhav> dholbach: I downloaded the packages, is the init script amavisd_init.sh ?
[09:14] <dholbach> vibhav, I would download both packages (from Ubuntu and Debian) and check the changes between the two for the files ./amavisd_init.sh and ./debian/amavisd-new.init
[09:17] <vibhav> dholbach: I found out the changes
[09:17] <dholbach> cool
[09:17] <vibhav> now?
[09:17] <dholbach> check out the fixing a bug in ubuntu article I mentioned earlier
[09:18] <dholbach> I need to step out for a bit now, so if you have any more questions or if anything's unclear, just ask in here and somebody else might be able to help
[09:47] <debfx> Rhonda: wesnoth-1.8 and wesnoth-1.10 have some overlapping binary packages. should I just drop them from wesnoth-1.8?
[09:52] <dholbach> who do we have here for Fix-It Friday? Are there any open questions? How are you all doing?
[09:53] <jokerdino> oh yeah, it is Fix-it Friday today. *must fix something*
[09:55] <dholbach> jokerdino, woohoo :)
[09:55] <dholbach> I added the Fix-It Friday page to the topic
[09:55] <dholbach> there's a TODO list if you can't think of anything :)
[09:57] <jokerdino> I have a bookmark of bugs that I can try to fix. :D
[09:57] <broder> dholbach: battery is dying and i should probably go to bed, but http://qa.ubuntuwire.com/bugs/rcbugs/ can be a good source of things to fix
[09:58] <dholbach> ah yes
[09:58] <dholbach> of course
[09:58] <dholbach> adding
[09:58] <jokerdino> i have been looking at the delta-with-unity tagged bugs. like this https://bugs.launchpad.net/unity-2d/+bug/910167
[09:59] <broder> dholbach: and there are still bugs marked bitesize
[09:59] <dholbach> jokerdino, wow - good luck with that one
[09:59] <broder> though that tends to be hit or miss
[10:00] <dholbach> maybe a number of us could get together to put a "real TODO list" together
[10:00] <dholbach> like a pre-filtered TODO list
[10:00] <dholbach> next Thursday :)
[10:00] <broder> it'd definitely be good to have
[10:00] <broder> i never feel like i have a good answer whne somebody asks me what they should work on
[10:01] <jokerdino> i think the bitesize tag on the bug report is not fair.
[10:01] <dholbach> and if it's 3-4 people working together, I'm sure you can easily get together 50 bugs/items in around 15 minutes
[10:01] <broder> (i personally don't like giving ftbfs or sync/merges to new people)
[10:01] <dholbach> I agree - some of them are quite hard - the best thing I can say about it is "it's a learning experience" :/
[10:02] <dholbach> you get to know how the bug tracker works, where to look for patches, etc
[10:02] <broder> heh
[10:02] <ajmitch> hi
[10:02] <dholbach> but it's by no means a "go through commands 1) to 5) and you're done"
[10:02] <jokerdino> dholbach: i think i can work with you to identify the easy bugs, i found quite a few when i was scourging the harvest.
[10:02]  * broder actually goes to bed now. 'night, folks
[10:02] <dholbach> broder, good night
[10:02] <dholbach> hey ajmitch
[10:03] <geser> Hi ajmitch and dholbach
[10:03] <dholbach> jokerdino, let's try to put something together for next Fix-It Friday then - maybe on Thursday
[10:03] <dholbach> hi geser
[10:04] <jokerdino> dholbach: sure
[10:04] <dholbach> awesome, thanks jokerdino
[10:10] <Laney> こんにちは
[10:11] <ajmitch> Laney: and hello to you too
[10:11]  * micahg wonders if anyone is working on ghc rebuilds/syncs
[10:11] <Laney> ajmitch in japanese speaker shocker
[10:12] <ajmitch> Laney: sadly not
[10:12] <ajmitch> micahg: are there still some to be done? :)
[10:13] <micahg> also, the tracker doesn't seem to show the uninstallablility on armhf
[10:14] <Laney> because it failed to build
[10:14] <micahg> hmmm, archive page shows it passed
[10:14] <micahg> oh, wait, I"m looking at the wrong one
[10:15] <micahg> that would explain why no one's started the rebuilds :-
[10:15] <Laney> yeah
[10:15] <ajmitch> amd64 & armel built in the end?
[10:15] <Laney> i wonder if you can give -mfloat-abi=hard to the build system
[10:16] <ajmitch> last I saw they'd both failed
[10:16]  * micahg kicks off a test build
[10:16] <Laney> i think armel was always fine, amd64 is ok too
[10:16] <Laney> you have hardware?
[10:16] <micahg> ajmitch: armel seems to have worked
[10:16] <micahg> Laney: porter box ;)
[10:16] <Laney> nice
[10:16] <Laney> bung an -optc in an armhf conditional then
[10:16]  * ajmitch was just watching the builds after it was uploaded & approved
[10:16]  * micahg has hardware, but the porter box is faster
[10:16] <ajmitch> maybe my memory is shot & I'm going senile
[10:16] <jokerdino> devs, is this one really a bitesize? https://bugs.launchpad.net/unity-2d/+bug/910167
[10:17] <jokerdino> ;(
[10:17] <Laney> no
[10:17] <Laney> you can just remove the tag from inappropriately tagged stuff
[10:18] <jokerdino> lol, i have been trying to find how to start fixing it.
[10:19] <dholbach> jokerdino, maybe one of the resolved_upstream bugs or the debian rcbugs might be better? (unless you want to get into unity hacking :-))
[10:19] <jokerdino> may be those are better
[10:20] <jokerdino> as long as i don't need to propose a branch, i will work with anything,
[10:21] <dholbach> you can also attach a patch to a bug report and subscribe ubuntu-sponsors if you like
[10:21] <jokerdino> i prefer the last one, attaching the patch works well.
[10:22] <dholbach> cool
[10:24] <jokerdino> how do i go about fixing rcbugs?
[10:25] <jokerdino> i am looking at hamster-applet
[10:27] <dholbach> jokerdino, you would have a look at the differences between the debian and ubuntu package and figure which change needs to be applied in Ubuntu
[10:28] <dholbach> it seems the Ubuntu package has changes not yet in Debian (2.91.3+git20110714.9aefd7-2ubuntu3 indicates there were 3 uploads to Ubuntu)
[10:29] <dholbach> so either we can identify how exactly this serious bug (http://bugs.debian.org/654474) was fixed, or we perform a merge between the debian and ubuntu package
[10:30] <dholbach> if we should find that the Ubuntu changes can be overwritten, we could sync the package
[10:31] <jokerdino> would bzr branch lp:hamster-applet get me the ubuntu package?
[10:32] <ajmitch> lp:ubuntu/hamster-applet
[10:33] <jokerdino> thanks ajmitch
[10:33] <jokerdino> Packaging branch version: 2.91.3+git20110714.9aefd7-2ubuntu1
[10:33] <jokerdino> Packaging branch status: OUT-OF-DATE
[10:33] <jokerdino> ?
[10:33] <ajmitch> that's a bit of a pain when that happens
[10:35] <micahg> jokerdino: grab-merge should work as it's in testing
[10:35] <jokerdino> i see
[10:36] <jokerdino> give me a while, it takes a while to get the branch
[10:37] <jokerdino> and how do i get the debian package?
[10:37] <micahg> jokerdino: grab-merge will get you the current Ubuntu and Debian packages (in non-bzr form)
[10:38] <rsajdok> dholbach: I am working on bug in loco-team-portal. Should I prepare css or only code of python and html?
[10:38] <rsajdok> https://bugs.launchpad.net/loco-team-portal/+bug/720824
[10:40] <Rhonda> debfx: Uhm, is there an update for wesnoth-1.8 needed in precise?  I thought uploading wesnoth-1.10 did already drop them from 1.8?
[10:40] <dholbach> rsajdok, I would suggest asking in #ubuntu-locoteams - people like daker, mhall119, cjohnston should be able to help you out (some of them might not be up yet)
[10:40] <dholbach> rsajdok, but feel free to change whatever is necessary
[10:40] <Rhonda> debfx: What update is needed for 1.8?  I am curious about that.
[10:41] <debfx> Rhonda: just a no-change rebuild
[10:42] <debfx> which failed to upload: https://launchpadlibrarian.net/94848743/upload_3454613_log.txt
[10:42] <micahg> Laney: well, passing that flag failed for me, but I probably did it wrong (janimo says it's the default for gcc anyways), he's having a look in a bit
[10:42] <Rhonda> This issue doesn't exist in Debian because binNMUs won't replace arch:all packages.
[10:42] <jokerdino> micahg: "It looks like this package is maintained in revision control:"
[10:42] <jokerdino> it says don't continue
[10:42] <Rhonda> debfx: Sure, because the versions are older indeed. :)  Yes, drop those four from debian/control{,.in}
[10:43] <Rhonda> Those are the meta packages that help people with the upgrade and noticing the new release.
[10:43] <jokerdino> now that i got both the packages, i should untar them right?
[10:44] <micahg> jokerdino: you can use the debdiff command along with filterdiff (I usually create a source package with the Ubuntu changes applied and then debdiff against the Debian upload to see if they're still relavent)
[10:45] <micahg> jokerdino: the script should create the new source dir for you with the previous patches applied (unless they failed, that'll show in the REPORT file)
[10:46] <debfx> Rhonda: ok, will do
[10:47] <jokerdino> micahg: it says conflicting changes have been made
[10:48] <micahg> jokerdino: so you have to resolve those manually, they should be visible in the filed
[10:48] <micahg> *files
[10:48] <Laney> micahg: oh ok, I really have no clue about this but it looks to me like some option is being passed incorrectly
[10:48] <Laney> i'm sure janimo can sort it
[10:49] <ajmitch> boo, syncpackage died on me
[10:49] <toabctl> what's the best way to show bugs for a source-package? ie i want to see all bugs from networkmanager i go to https://bugs.launchpad.net/ubuntu/+source/network-manager/ but the bug order is imho useless. the most important bug is from 2008..
[10:49] <jokerdino> micahg: no idea how i am supposed to do that. is it possible if you can go through them one by one? :S
[10:50] <dholbach> toabctl, you can sort by "number" - would that be helpful? what are you looking for?
[10:50] <toabctl> dholbach, i want to see only precise bugs ordered by date.
[10:51] <micahg> jokerdino: well, ask your questions, and I'm sure someone here can help (I might not be available)
[10:51] <toabctl> dholbach, i just don't understand why the default order seems to be useless
[10:51] <dholbach> toabctl, the default order is based on bug importance
[10:52] <jokerdino> well, after grab-merge, what should i be doing?
[10:52] <toabctl> dholbach, then imho bug importance is useless. why is a bug from 2008 most important?
[10:52] <dholbach> toabctl, I don't know - maybe the bug importance should be changed then :)
[10:52] <dholbach> jokerdino, you seem to have a knack for picking the hard ones :)
[10:52] <jokerdino> i am so lucky \o/
[10:52] <dholbach> jokerdino, the 'motion' package on the same list might be easier for example
[10:53] <dholbach> let me see if I can find anything else
[10:53] <toabctl> dholbach, is there a better interface to get the bugs? maybe command line tools?
[10:53] <jokerdino> ah, cool. dholbach i am now looking at motion.
[10:53]  * jokerdino is away for dinner now.
[10:54] <dholbach> toabctl, it depends on what you are after - do you want to triage new bugs that came in? does the 'heat' order help?
[10:54] <dholbach> there might be command line tools, but I don't know
[10:55] <toabctl> dholbach, i want to see the newest bugs but only for NM.
[10:55] <dholbach> sort by 'number'?
[10:55] <dholbach> on the page you mentioned above
[10:56] <toabctl> dholbach, ahh. the number is what i missed. thanks!
[10:56] <dholbach> :)
[10:57] <dholbach> jokerdino, pornview might also be easier
[10:58] <dholbach> and then generally: all the unmodified packages in Ubuntu - in their case it will be interesting to find out how much else was changed, so we don't end up bringing up huge changes just to fix a small bug
[10:58] <ajmitch> quite a few of those will have comments, too
[10:59]  * dholbach nods
[11:00]  * ajmitch is doing a few on the list at the moment
[11:03]  * ajmitch thought all kernel-patch-* packages were blacklisted from syncs
[11:03] <ajmitch> yet there's a https://launchpad.net/ubuntu/+source/kernel-patch-viewos which is horribly out of date :)
[11:04] <dholbach> might be a good idea to get rid of it :)
[11:05] <ajmitch> yeah, was just checking up on it before I asked for removal
[11:11] <ajmitch> ok, filed bug
[11:16] <dholbach> awesome
[11:17] <dholbach> I wonder who else came here for Fix-It Friday - maybe you could do a round of introductions? :)
[11:19]  * ajmitch should probably leave soon, it's no longer friday here
[11:20] <micahg> ajmitch: bug  944672 :P
[11:20] <ajmitch> micahg: sigh, sorry
[11:21] <ajmitch> I did ask you about this one a few days ago, too :)
[11:21] <micahg> ajmitch: more concerned that you didn't notice it needs an FFe ;)
[11:21] <ajmitch> I didn't think that it was needing an FFe for that change?
[11:22] <micahg> well, libdb5.1 dropped a feature and this required a specific source patch, I figured it was worth asking for one
[11:23]  * ajmitch will just stop now then
[11:24] <micahg> ajmitch: don't stop on my account ;)
[11:25] <ajmitch> no, I'll stop because I'm screwing up the archive :P
[11:29] <geser> ajmitch: a) it's Friday, so a good time to screw up the archive :) and b) you give dholbach tasks for his Fix-It-Friday :)
[11:29] <dholbach> geser, it's not *MY* Fix-It Friday :)
[11:29] <dholbach> seriously - we all want more contributors to development, no? :)
[11:31] <geser> yes, and hopefully they stay longer than one Friday
[11:31] <dholbach> :)
[11:32] <geser> and also contribute on the other days of the week
[11:44] <dholbach> so what are you all working on?
[11:49] <jokerdino> so dholbach now that i have the packages for motion, how do i proceed? i have no idea what i should be doing.
[11:50] <dholbach> jokerdino, so the line on the page says that between motion 3.2.12-3ubuntu2 in ubuntu and 3.2.12-3.1 in debian, debian bug 640562 was fixed
[11:50] <dholbach> now it's interesting to do some archaeology and figure out what the changes between the two packages are
[11:51] <dholbach> you might find one of the following things:
[11:51] <dholbach>  - there's an interesting change we should have, but there's too many other things in the change as well, so we "cherry-pick" the interesting change
[11:52] <dholbach>  - there's an interesting change we should have, and our changes were integrated in debian too, so we can sync from debian (basically overwrite our package)
[11:52] <dholbach>  - there's an interesting change we should have, but we can't overwrite all our changes, so we need to do a merge
[11:52] <dholbach>  - there's nothing interesting
[11:52] <dholbach> I think that's all :)
[11:53] <dholbach> so running a     debdiff motion_*.dsc | less     should give you a basis for archaeologic studies :)
[11:54] <jokerdino> Need exactly two deb files or changes files to compare
[11:54] <jokerdino> Weird thing is weird
[11:54] <dholbach> how many motion*.dsc  files do you have there? :)
[11:55] <jokerdino> three :/
[11:55] <dholbach> ok
[11:55] <dholbach> debdiff motion_3.2.12-3ubuntu2.dsc motion_3.2.12-3.1.dsc | less
[11:56] <dholbach> basically: diff the source packgae from ubuntu against the one from debian
[11:56] <jokerdino> so i ignore the base package i see
[11:56] <dholbach> what do you mean by "base package"?
[11:57] <jokerdino> the common ancestor from which the ubuntu and debian package came from?
[11:57] <jokerdino> that's what the report file says
[11:57] <dholbach> ah, yes
[11:58] <dholbach> sure, if a reviewing a diff gets too complicated, you can do that
[11:59] <dholbach> the good thing is: both the recent Ubuntu and Debian versions are based on the same version just one upload (in the case of Debian) and two uploads (in case of Ubuntu) before
[11:59] <dholbach> so it shouldn't be too crazy
[12:03] <jokerdino> so i found the part that fixes the relevant bug.
[12:05] <dholbach> as the Ubuntu changes fixed the build with a recent libav, it might worth doing a test-build of the current debian package, without any ubuntu modifications
[12:07] <jokerdino> how do i build a package locally?
[12:08] <dholbach> http://developer.ubuntu.com/packaging/html/getting-set-up.html#set-up-pbuilder
[12:08] <jokerdino> wow, this is so intense :S
[12:08] <dholbach> I'm glad you like it :)
[12:08] <jokerdino> i choose not to give up.
[12:08] <dholbach> good :)
[12:08] <dholbach> at the beginning it's important to understand a few concepts and workflow bits
[12:09] <dholbach> at some stage (I'd say quite soon), you'll know which tool to pick and a bunch of commands will go into muscle memory quickly :)
[12:10] <jokerdino> ah yeah. initially i found basic debian packaging quite hard, but now i can do a bit more stuff easily
[12:10] <dholbach> and you're doing much better than many others - lots of others gave up earlier :)
[12:14] <jokerdino> i will get back to you when the pbuilder finishes downloading the relevant parts :)
[12:14] <dholbach> it caches them, so you just have to go through this once :)
[12:14] <jokerdino> heh nice.
[12:14] <jokerdino> but i need to do this for the ubuntu version as well?
[12:15] <jokerdino> is this command right? pbuilder-dist sid create build motion_3.2.12-3.1.dsc
[12:16] <jokerdino> or is it wheezy instead of sid?
[12:18] <dholbach> no, unfortunately not
[12:19] <dholbach> try: pbuilder-dist precise build
[12:19] <dholbach> err, sorry
[12:19] <dholbach> try: pbuilder-dist precise create
[12:19] <dholbach>     pbuilder-dist precise build motion_3.2.12-3.1.dsc
[12:19] <dholbach> you don't want to test if it builds fine in Debian sid, but if it also builds in precise (without the Ubuntu modifications)
[12:19] <jokerdino> i should be building the unmodified debian package in precise, hmm
[12:21] <dholbach> yes
[12:21] <babai> afaik pbuilder caches the minimum deps for building packages, i have a slow internet connection, anyone knows the size of the 'minimum'?
[12:22] <sagaci> around 50-100mb
[12:22] <babai> k, thnx
[12:22] <dholbach> jokerdino, we want to check if the debian package would also build in ubuntu (without ubuntu modifications)
[12:23] <dholbach> babai, if you just want to do a quick build test, you can also build the package by running "debuild" in the source package tree
[12:23] <jokerdino> yes, i understand that :)
[12:23] <dholbach> ok :)
[12:23] <jokerdino> it makes no sense to test for debian
[12:23] <babai> dholbach: hmm, i want to build for stable releases also, so  i need pbuilder
[12:23] <dholbach> babai, the reason we recommend pbuilder ist that you can make sure that the package builds in a reproducible way (without relying on local changes you made to your system)
[12:24] <dholbach> babai, ok - that's fine :)
[12:33] <l3on> Hi all ... I need a sponsor for nmu ... somebody around? (debian bug 660044)
[12:34] <l3on> it also causes ftbfs in Precise
[12:36] <dholbach> ciao l3on, you could try to ask in #debian-ubuntu on irc.oftc.net
[12:36] <l3on> ok, thanks dholbach :)
[12:37] <geser> Laney: is http://people.canonical.com/~ubuntu-archive/transitions/ghc.html for the current ghc transition? (or an old one?)
[12:38] <Laney> current
[12:38] <Laney> i'm not sure if stuff will build against old ghc on armhf though
[12:38] <geser> should haskell-platform be also included in that list? see bug #944742
[12:39] <Laney> yeah probably
[12:40] <Laney> not fixed in debian though either
[13:01] <jokerdino> dholbach: the debian package builds well
[13:02] <dholbach> jokerdino, excellent - so it looks like we can completely replace the Ubuntu source with the one from Debian
[13:02] <dholbach> and as its only bug fixes, we can get it in without filing any freeze exceptions
[13:02] <dholbach> jokerdino, what's your launchpad id?
[13:02] <jokerdino> ~jokerdino
[13:02] <dholbach> great, I'll sync the package in your name
[13:02] <jokerdino> launchpad.net/~jokerdino
[13:02] <dholbach> well done
[13:03]  * jokerdino hugs dholbach.
[13:03]  * dholbach hugs jokerdino back :)
[13:04] <dholbach> done
[13:04] <jokerdino> heh awesome.
[13:07] <jokerdino> where do i verify if i actually haven't made a mistake and the package did build properly?
[13:08] <dholbach> jokerdino, if the build passed without any errors and you see the resulting .deb files in ~/pbuilder/*_result/ you should be fine
[13:10] <geser> jokerdino: you can also watch the build of the upload on https://launchpad.net/ubuntu/+source/motion/3.2.12-3.1 , the "Builds" section
[13:10] <jokerdino> awesome, motion is sitting right inside
[13:10] <jokerdino> thanks geser
[13:17]  * dholbach takes the dog for a walk - brb
[13:40] <Kiall> Heya - What is the recommended way to restart/reload a service from a postinst script - without caring if its a traditional or upstart script?
[13:40] <Kiall> something like if [ -e /etc/init/bla.conf] .. else ... or?
[13:48] <dupondje> https://launchpad.net/ubuntu/+source/cryptsetup -> is there a change a merge of this would still be accepted now ?
[13:48] <dupondje> chance*
[14:24] <Kapil> HI guys, so what are your expectations from 12.04?
[14:24] <valdur55> Hey! Good Fixit Friday!
[14:25] <dholbach> hey Kapil, hey valdur55 :)
[14:25] <dholbach> dupondje, are the changes mostly bug fixes?
[14:26] <vibhav> dholbach: I am a bit confused now, how do I apply the diff to to theamavisd-new.init
[14:26] <vibhav> the amavisd-new.init
[14:27] <dholbach> vibhav, if you want to merge all changes, you could just copy the file over
[14:27] <dholbach> if you just wish to merge select changes, you can do it manually by just editing the file
[14:29] <vibhav> dholbach: Copied the file, what do I need to put in the changelog?
[14:30] <dholbach> vibhav, http://developer.ubuntu.com/packaging/html/fixing-a-bug.html#documenting-the-fix
[14:30] <jokerdino> dholbach: pornview is a pain.
[14:31] <jokerdino> https://bugs.launchpad.net/ubuntu/+source/pornview/+bug/935370 ;(
[14:31] <dholbach> ok
[14:31] <dholbach> then pick another :)
[14:31] <jokerdino> snowballz?
[14:32] <dholbach> snowballz has a comment - on the very right of the page
[14:32] <dholbach> I don't know how much additional problems that's going to be
[14:32] <vibhav> dholbach: I am a bit confused now, how do I apply the diff to to theamavisd-new.init (LP: #930916)
[14:32] <vibhav> oops
[14:32] <jokerdino> ok then, i will look at something else. haha
[14:32] <vibhav> Sorry dholbach
[14:32] <dholbach> vibhav, no worries
[14:33] <jokerdino> i feel proud of myself. haha
[14:33] <vibhav> dholbach: I meant , shall I write "Update amavisd-new.init from upstream (Fixes LP: 930916)
[14:33] <vibhav> updated*
[14:33] <dholbach> "(LP: #930916)" is the syntax to get the bug automatically closed
[14:34] <dholbach> and I'd probably try to explain what exactly the fix from Debian fixed
[14:34] <dholbach> jokerdino, you could take a look at ldb - it is unmodified in Ubuntu, has received fixes in Debian - if you should find that it builds and works fine in Ubuntu and that there are only good bug fixes and not huge other modifications in the package, that might be a good fix for Ubuntu
[14:35] <dupondje> dholbach: nothing really special.
[14:35] <dholbach> dupondje, if it's bug-fixes, then yes - https://wiki.ubuntu.com/FreezeExceptionProcess explains how things work after Feature Freeze
[14:37] <vibhav> dholbach: Edited the changelog, what do I do now?
[14:37] <Rhonda> debfx: hmm, the changelog now only contains the dropping of the metapackages and no information why the rebuild was needed? :)
[14:37] <l3on> Ampelbein, hey... Are you sure about bug #931720 ? I can't reproduce it :/
[14:38] <debfx> Rhonda: I didn't change the changelog entry of the rebuild upload
[14:39] <dholbach> vibhav, you can ask the others in here as well - not just me :)
[14:39] <dholbach> vibhav, but yeah, try running   debuild -S
[14:39] <dholbach> so you generate a new source package from your changes
[14:39] <dholbach> and then try to build it with pbuilder
[14:40] <vibhav> Is pbuilder a must?
[14:40] <Ampelbein> l3on: I'll retry the the build when I get a chance. Could have been a temporary issue.
[14:40] <Ampelbein> vibhav: No, but it's highly recommended. With pbuilder/sbuild you build in a clean environment, making the build behave more like on the launchpad builders.
[14:41] <vibhav> Ampelbein: Cant I get it to build it somewhere else?
[14:42] <jokerdino> there is no ldb that i can grab :(
[14:42] <Ampelbein> vibhav: What is the first "it" referring to?
[14:42] <vibhav> Ampelbein: The fixed package
[14:42] <jokerdino> oh wait grab-merge won't work if there is no diff?
[14:42] <dholbach> vibhav, you could also upload it to PPA or build it locally by just running 'debuild' in the source tree
[14:43] <dholbach> jokerdino, you can run "apt-get source <...>" and "pull-debian-source <...>"
[14:43] <Ampelbein> vibhav: Like dholbach said, in a ppa or with debuild or dpkg-buildpackage.
[14:43] <vibhav> dhAfter running debuild, where do I need to submit the package?
[14:44] <dholbach> vibhav, do   debdiff <old>.dsc <new>.dsc > ~/<package>.debdiff
[14:44] <dholbach> and attach it to the bug report you're working on
[14:44] <dholbach> and subscribe the 'ubuntu-sponsors' team, so it ends up in the review queue :)
[14:47] <Rhonda> debfx: oh, right, it's partly visible in what mom did mail me, just not with a + at the start of the line. Sorry :)
[14:49] <jokerdino> ldb has no ubuntu source package, but i did download the debian package
[14:49] <debfx> mom sends mails?
[14:50] <dholbach> jokerdino, it does have a source package in ubuntu
[14:51] <dholbach> can you check in software-properties you have "Source code" enabled?
[14:51] <jokerdino> oh that one?
[14:51] <jokerdino> i don't have it on
[14:51] <dholbach> enable it and try again :)
[14:51] <vibhav> Ampelbein, dholbach : thanks
[14:52] <dholbach> if apt-get doesn't know where to get source packages from, it won't download anything :)
[14:52] <dholbach> vibhav, anytime :)
[14:52] <Rhonda> debfx: yes, To: wesnoth-1.8@packages.qa.debian.org  :)
[14:54] <vibhav> Also, how do I know which file do I need to edit while fixing bugs?
[14:54] <Rhonda> i.e., PTS keyword "derivatives".
[14:55] <dholbach> vibhav, sometimes you need to do some detective work to find out, but "grep -r ........" is often very helpful
[14:57] <vibhav> dholbach: I did not understand , what do I need to type after "grep -r "?
[14:58] <dholbach> type "man grep" - it will show you some information about the grep command
[14:58] <dholbach> but    grep -r <search> <path>    usually is a huge help to search for something in a source package
[14:59] <vibhav> i see
[15:10] <dholbach> there's a bunch of new people here - I hope you're all here for Fix-It Friday :)
[15:10] <dholbach> I'm wondering if some of you would be interested in chatting a bit in a Google+ Hangout
[15:11] <dholbach> and maybe be more comfortable asking questions there
[15:11] <dholbach> I still have 50 minutes until I have another call - I'll just set one up and we see how it goes :)
[15:11] <jokerdino> dholbach: the debian version of ldb builds well
[15:12] <dholbach> jokerdino, great - now you just need to make sure that it doesn't add huge amount of new features and just fixes bugs we're interested in seeing fixed
[15:12] <dholbach> in that case we should be able to sync it and get those bugs fixed
[15:12] <jokerdino>  * New upstream snapshot.
[15:12] <jokerdino>    + Extracts waf source code. Closes: #654482
[15:12] <jokerdino>    + Disable tdb2 support.
[15:12] <jokerdino> that's all you got
[15:13] <dholbach> it might be good to inspect the diff
[15:13] <dholbach> and see if there's another more detailed changelog in there
[15:13] <dholbach> https://plus.google.com/hangouts/d3e6d86b708ed0838b233de40dad8aab9ed4f246 for everyone's who interested in chatting a bit and asking all their questions about ubuntu development :)
[15:14] <randy_> hello i have a question
[15:15] <dholbach> hello randy_
[15:15] <dholbach> what's your question?
[15:16] <randy_> i use a tablet and when i use onboard (the default on screen keyboard) i often have to unselect then reselect the window i am using in order for ubuntu to not unfocus the window
[15:16] <randy_> is there a known bug concerning this and if so is this being worked on
[15:16] <dholbach> randy_, try asking the folks in #ubuntu-desktop
[15:16] <dholbach> they should have an overview over what's being worked on
[15:17] <randy_> ??
[15:17] <dholbach> just type this into the chat window: /join #ubuntu-desktop
[15:17] <jokerdino> the debdiff gives me a 26k line file :S
[15:17] <randy_> oic sorry i didnt realize this was not the correct IRC channel
[15:18] <dholbach> randy_, don't worry - that's fine
[15:18] <randy_> thank you
[15:18] <dholbach> it's just that you have the whole desktop team in the other channel and are more likely to get a quick answer there :)
[15:19] <randy_> O thanks i will direct my question there then.
[15:22] <Ampelbein> l3on: librsvg still fails with the same error for me. Are you on amd64, too?
[15:23] <l3on> Ampelbein, damn, no i386
[15:23] <l3on> let me check it on amd64
[15:24] <Ampelbein> I'll have more time to debug it later today
[15:25] <dholbach> toabctl, did you get anywhere with the network-manager bugs?
[15:30] <dholbach> jokerdino, I just briefly had a look over it - maybe it's not worth having - maybe some other package has more interesting bugs which were fixed - I don't know
[15:30] <jokerdino> yeah, i was thinking the same.
[15:30] <jokerdino> the diff is just too huge
[15:33] <jokerdino> perhaps the trivial logjam?
[15:33] <dholbach> yeah, check it out
[15:33] <tumbleweed> Laney, ScottK: busy moving flat, if one of you could stand in for me at the release meeting, that'd be awesome
[15:34] <ScottK> tumbleweed: OK.  Anything worth mentioning?
[15:34] <tumbleweed> I haven't been paying much attention, I'm afraid
[15:34] <ScottK> OK.
[15:34] <tumbleweed> you probably know more about approved FFes than me
[15:34] <ScottK> ghc6 I guess.
[15:34] <tumbleweed> yeah
[15:35] <dupondje> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/776264 could somebody review please ? :)
[15:37] <l3on> tumbleweed, can you sponsor me another nmu please? :)
[15:39] <dholbach> libsfml might be good too
[15:39] <dholbach> brb
[15:41] <jokerdino> logjam (4.6.2-1ubuntu1) UNRELEASED; urgency=low
[15:41] <jokerdino> heh it is done, i think
[15:41] <jokerdino> dholbach: logjam (4.6.2-1ubuntu1) UNRELEASED; urgency=low
[15:42] <jokerdino> it seems mom did the work
[15:42] <dholbach> jokerdino, in that case: can you make sure that the merge doesn't miss anything either having been done in Debian or Ubuntu and that it builds, etc?
[15:42] <jokerdino> i am not sure if you like people pinging you all the time
[15:43] <dholbach> jokerdino, just ask whatever your question is in here - there's lots of people who should be able to help you out
[15:43] <dholbach> most of them know much more about this stuff than I do ;-)
[15:44] <l3on> ok, someone can take a quick look at this → https://code.launchpad.net/~l3on/ubuntu/precise/lusca/fix-ftbfs/+merge/95594 ? :)
[15:45] <jokerdino> just clarifying. the dsc is still the older version
[15:45] <jokerdino> but the bzr inside the grab-merge has the latest version, without the dsc.
[15:45] <l3on> Amaranth, librsvg builds fine also in amd64 → http://debomatic64.debian.net/precise/pool/librsvg_2.35.1-0ubuntu2/
[15:45] <geser> l3on: we usually don't switch any packaging formats in Ubuntu delta
[15:46] <l3on> geser, dpatch is obsolete and bzr builddeb returns me error, I needed it to build the dsc
[15:46] <dholbach> jokerdino, if it's a patch file, you could get the old source package, then apply the diff in there, then rebuild the source package (debuild -S, etc.)
[15:47] <geser> hmm
[15:47] <l3on> Amaranth, sorry, was a ping for Ampelbein
[15:47] <geser> did the package had any dpatch patches?
[15:47] <l3on> Ampelbein, librsvg builds fine also in amd64 → http://debomatic64.debian.net/precise/pool/librsvg_2.35.1-0ubuntu2/
[15:47] <l3on> geser, no
[15:48] <jokerdino> well the control file of the modified logjam is in a mess
[15:52] <dholbach> jokerdino, do your best to fix the merge, generate a debdiff (first build the new source package, then do a debdiff <old>.dsc <new>.dsc > logjam.debdiff) and maybe put it up on paste.ubuntu.com if you need help from anyone in here
[15:52] <Ampelbein> l3on: Interesting. I'll investigate this. Feel free to close the bug.
[15:53] <l3on> Ampelbein, status Fix released ?
[15:53] <Ampelbein> l3on: Or Invalid, as you like.
[15:54] <l3on> Ampelbein, done, thanks :).
[15:58] <valdur55> lol :) i found funny bug on indicator-sound-gtk2 :P
[15:58] <valdur55> how can i record screen?
[16:00] <dholbach> if you work on something, can you add it to http://pad.ubuntu.com/OsSL8mOs2o please? :)
[16:00] <dholbach> I'll blog about the event later on then
[16:02] <dupondje> well dholbach  :)
[16:02] <dupondje> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/776264 uploaded a merge
[16:02] <dupondje> but gone now :)
[16:04] <dholbach> dupondje, in a call right now
[16:04] <dholbach> but maybe somebody else has a bit of time
[16:05] <l3on> dholbach, that pad is also for contributors like me (or only for motu?)?
[16:05] <dholbach> no, for everyone
[16:05] <dholbach> everyone who participates in Fix-It Friday :)
[16:05] <l3on> ah ok :)
[16:07] <ScottK> tumbleweed: No meeting today.
[16:22] <dholbach> coolbhavi, happy birthday! :)
[16:23] <coolbhavi> thanks a lot dholbach! :)
[16:23] <dholbach> :)
[16:51] <dholbach> how's Fix It Friday coming along? anyone stuck anywhere?
[17:10] <dholbach> hey crimsun
[17:10] <dholbach> happy fix-it friday :)
[17:11] <crimsun> hi dholbach :)
[17:11] <crimsun> I've been fighting with armhf, qemu, and sbuild
[17:12] <dholbach> crimsun, have you chatted with the guys currently doing the ARM Porting Jam?
[17:12] <crimsun> dholbach: no, but it isn't the armhf qemu that's causing problems. It's the i386 and amd64 buildds that time out after 180 minutes :/
[17:13] <dholbach> ugh :-(
[17:13] <dholbach> what's taking so long? is it some test suite which could be turned off?
[17:13] <crimsun> yeah, it's a test suite, though I'm loathe to just kludge a "FTBFS fix" just by turning off the single test suite
[17:14] <dholbach> yeah :-/
[17:20] <jokerdino> i can build logjam_4.6.2-1 here. needs someone to verify if sync is viable
[17:21] <crimsun> jokerdino: what arches does "here" cover in your statement?
[17:22] <jokerdino> here as in, in my system
[17:22] <crimsun> jokerdino: what arch is your system? i386? amd64?
[17:22] <jokerdino> amd64
[17:22] <crimsun> (`uname -m')
[17:22] <jokerdino> x86_64
[17:24] <dholbach> alright my friends - I'm going to call it a day as I'm supposed to be somewhere for dinner in a few minutes
[17:24] <crimsun> dholbach: see ya!
[17:24] <dholbach> but I'll make sure to check the review queue some times over the weekend :)
[17:25] <dholbach> and I'm looking forward to seeing your names there :)
[17:26] <jokerdino> good day dholbach !
[17:26] <crimsun> jokerdino: I'm test-building on armhf, sec.
[17:26] <jokerdino> I will give you a minute or more. no hurry
[17:28] <tumbleweed> ScottK: aah, right, beta week
[17:28] <jokerdino> crimsun: i am not doing a ftbfs, rather it is a rcbug thingie
[17:29] <dholbach> bye crimsun, jokerdino :)
[17:32] <crimsun> jokerdino: yep. I'm just avoiding a run if I know beforehand that the source will FTBFS :)
[17:32] <jokerdino> surely, it won't ;)
[17:33] <crimsun> at least we hope not. There are source packages that build fine locally but fall over on buildds.
[17:34] <jokerdino> hmm, yeah, it is safer to test
[17:38] <crimsun> hmph. 4.6.2-1 FTBFS on armhf.
[17:39] <jokerdino> heh, which package did you use?
[17:39] <jokerdino> the one i used was the debian package.
[17:39] <jokerdino> unmodified
[17:40] <crimsun> yep, I attempted using the source package from `pull-debian-source logjam'
[17:40] <jokerdino> i used from grab-merge logjam
[17:41] <crimsun> the error doesn't make any sense, though: failed to load "./logjam_ljuser.png": Couldn't recognize the image file format for file './logjam_ljuser.png'
[17:41] <jokerdino> o.O
[17:41] <crimsun> (invoked from gdk-pixbuf-csource)
[17:42] <jokerdino> have no idea what those things are supposed to mean
[17:52] <crimsun> jokerdino: synced, thanks
[17:53] <jokerdino> great.
[17:54] <crimsun> lfaraone: any plans for the Ubuntu Sugar Team to update the seeds for 12.04?
[17:58] <micahg> crimsun: in cases of FTBFS on arm*, I usually check if the previous Debian build built on the arch in question if it's not a failure specific to our libraries (Qt + GLES) and such
[18:11] <lfaraone> crimsun: "probably no"
[18:12] <lfaraone> crimsun: ISTR we have no users, and I was working on that as part of a contract two+ years ago.
[18:12] <lfaraone> crimsun: upstream's answer to "I want to use Sugar" is  "so then you also want to use Fedora, don't you."
[18:12] <crimsun> lfaraone: that's unfortunate, because it FTBFS
[18:13] <crimsun> it->ubuntu-sugar-remix-meta
[18:13] <lfaraone> crimsun: I noticed. I'm curious if we should have them dropped; nobody is looking at it and the company that was funding it has moved to fedora.
[18:15] <crimsun> sounds reasonable if there aren't any loud complaints
[18:16] <jokerdino> http://paste.ubuntu.com/865497/ any ideas? :S
[18:16] <crimsun> jokerdino: your debian/patches/series file wasn't properly merged
[18:17] <crimsun> jokerdino: i.e., it still has the diff(3) markers
[18:18] <jokerdino> not sure how i should handle it.
[18:19] <jokerdino> i did a grab-merge pornview and was packaging the unreleased version in it
[18:19] <Rhonda> debfx: speaking of, I really should finally upload wesnoth 1.10.1 and sync it  ;)
[18:20] <crimsun> jokerdino: compare change-libs-param-order-with-ld.patch and 615765-gold-no-add-needed
[18:20] <crimsun> jokerdino: chances are that we should drop our delta and take the 11.1 NMU
[18:23] <crimsun> jokerdino: actually for that source package, you should just drop the Ubuntu patch (change-libs-param-order-with-ld.patch) and take Debian's (615765-gold-no-add-needed), then finish the merge.
[18:23] <fabrice_sp> Rhonda, speaking of which: wesnoth-1.8 should be dropped from the archive, right? Because with the 1.10 upload, some packages are not installable anymore
[18:24] <Rhonda> fabrice_sp: debfx fixed that before :)
[18:24] <fabrice_sp> oh, ok :-)
[18:24]  * fabrice_sp should have checked before writting
[18:24] <Rhonda> I think it would be nice to keep 1.8 around for a release - on the other hand, this is a LTS release, so I'm uncertain …
[18:26] <Rhonda> I will get 1.8 removed eventually, but I haven't made up my mind when the best time is.  It definitely will be dropped before Q (is the name already decided?), but for now …
[18:26] <Rhonda> I was (and still am) on parental leave for almost 4 months now, and haven't followed stuff too closely.
[18:28] <fabrice_sp> tbh, I've been quite absent last 6 months because of real life (Work), so I can understand that perfectly :-)
[18:29] <Rhonda> Hope it's a nice job?
[18:29] <fabrice_sp> and about 1.8, it's up to you. I just noticed it when I was reviewing uninstallable packages
[18:30] <fabrice_sp> a lot of travels :-)
[18:31] <jokerdino> crimsun: i tried hard but i still don't know what i should be doing, can you guide me through?
[18:32] <Rhonda> sabdfl would still blog about the Q name, right?
[18:33] <debfx> I haven't fixed any installability issues in wesnoth, just an uploadability issue :)
[18:33] <Rhonda> I think that's what fabrice_sp meant.  installable to the archive :P
[18:38] <debfx> dupondje: have you tested that the new cryptsetup doesn't break root encryption?
[18:40] <crimsun> jokerdino: you need to carry forward only the necessary Ubuntu delta. Notice how the Debian patch that's in the 11.1 NMU is preferred to Ubuntu's. So take Debian's, remove Ubuntu's, and update the merge.
[18:41] <jokerdino> i mean, how is this process done? i have no experience of handling merges and packages.
[18:41] <crimsun> jokerdino: I may have glossed over it as obvious (sorry), but we want to reduce the Ubuntu delta to zero if possible so that syncs are possible.
[18:42] <crimsun> jokerdino: ah, there are some wiki pages on working through merging
[18:44] <crimsun> jokerdino: have you read https://wiki.ubuntu.com/UbuntuDevelopment/Merging ?
[18:46] <jokerdino> Just reading it
[19:23] <PaoloRotolo> Hi all!
[19:25] <valdur55> Hi
[20:03] <jokerdino> http://paste.ubuntu.com/865632/ anyone has any ideas / suggestions?
[20:08] <Ampelbein> jokerdino: You can use the -iI switch to get more information about tags
[20:08] <tumbleweed> or just look them up with lintian-info
[20:11] <jokerdino> well, they don't seem to help. :/
[20:12] <tumbleweed> jokerdino: pornview is in debian
[20:12] <tumbleweed> we don't try and make debian packages lintian clean
[20:13] <tumbleweed> we try and stay as close to debian as possible, preferably in sync with debian
[20:13] <jokerdino> they don't build.
[20:13]  * tumbleweed looks
[20:13] <jokerdino> https://bugs.launchpad.net/ubuntu/+source/pornview/+bug/935370
[20:14] <tumbleweed> is that the same issue as debian bug 527714
[20:14] <dupondje> pornview ... :D
[20:14] <dupondje> what could that be :P
[20:14] <dupondje> debfx: didn't test that no ...
[20:15] <tumbleweed> no
[20:16] <tumbleweed> anyway, I can't help with that right now
[20:16]  * tumbleweed tears himself from IRC
[20:16] <jokerdino> ;(
[20:16] <tumbleweed> but don't worry, the lintian errors don't look related to the build failure
[20:17] <jokerdino> i see.
[20:17] <JanC> dupondje: it's an image viewer with a somewhat controversial name  ;)
[20:17] <jokerdino> may be someone else can offer help later on.
[20:18] <jokerdino> i need some sleep.
[20:18] <jokerdino> zzzz
[20:18] <dupondje> JanC: boring, only images .. :)
[20:19] <JanC> dupondje: image/movie viewer apparently
[20:19] <JanC> in any case, many people seem to expect something else...
[20:20] <jokerdino> o.O
[20:21] <JanC> (there are several bug reports about removing porn from the repositories)
[20:21] <jokerdino> what porn?
[20:22] <dupondje> apt-get install porn
[20:22] <dupondje> some additional features ^^
[20:24] <asomething> jokerdino, people think pornview has something to do with porn, understandably
[20:31] <ajmitch> jokerdino: by the way, when working on things like the rc bugs page, please leave comments against packages you've looked at so that someone else doesn't end up looking at the same one
[20:32] <jokerdino> where should i be commenting?
[20:33] <Ampelbein> jokerdino: When I work on a bug, I set status "In Progress" and assign myself to prevent others from duplicating work.
[20:33] <ajmitch> in the right-hand column where there are comments already - there's a text input field on each line
[20:34] <ajmitch> jokerdino: also, the table at the bottom are for bugs that don't really need to be fixed in ubuntu :)
[20:34] <jokerdino> ajmitch: they are not necessary, but i was doing to learn the process
[20:44] <jokerdino> so far, i have synced motion and logjam.
[20:45] <jokerdino> i will look at others later tmrwo
[22:06] <mfisch> hey motu, a bug-fix day question.  I see the issue with aweather, but in the development branch it's been fixed and superseded, so I assume it's not worth fixing at this point?
[22:08] <micahg> mfisch: well, if it's easily fixable (by cherry-picking patches) in the stable releases, you could do that
[22:08] <mfisch> micahg: so what happened is that it was patched "fixes ftbfs" but they forgot to add quilt to the rules file.  In the dev branch the patch (and need for it) is gone
[22:09] <mfisch> micahg: so it would be immediately nuked once a new version comes out
[22:09] <micahg> mfisch: we don't add a patch system in general if Debian doesn't have one
[22:10] <mfisch> micahg: the attempted fix (patch) was done with quilt, but if you don't add it to the rules file, the patch is not very useful, at least thats my understanding
[22:10] <micahg> ah, ok, and this only affected the dev release?  yeah, nothing to do
[22:10] <mfisch> micahg: sorry, I'm not explaining myself well
[22:11] <mfisch> micahg: current ubuntu release ftbfs, despite an attempt last year to fix that (a patch was added, but quilt's not in the rules or control file)
[22:11] <mfisch> micahg: the development branch has changed to the point where this patch, working or not, is no longer needed
[22:11] <mfisch> micahg: so I assume it's a waste of time to fix the patch thats already superseded in the dev branch
[22:12] <jtaylor> dev branch of upstream?
[22:12] <mfisch> sorry again for not specifing, no the dev branch in launchpad
[22:12] <micahg> mfisch: FTBFS fixes are generally ok for SRUs
[22:14] <jtaylor> why was the patch dropped in the sync oO
[22:15] <mfisch> jtaylor: I think the rev 7 of the dev branch is new from upstream which precludes the need for said non-functional patch.
[22:16] <mfisch> I think doing nothing is the right thing here
[22:16] <jtaylor> no we definetly need to do something
[22:16] <mfisch> dputting the top of the dev branch would fix this
[22:16] <jtaylor> we don't want to put in dev releases without good reason
[22:16] <jtaylor> the old patch looks fine, can't we just use that?
[22:17] <mfisch> jtaylor: where would it get merged to?
[22:17] <jtaylor> the ubuntu package?
[22:17] <mfisch> the branches are precise/development and oneiric: https://code.launchpad.net/ubuntu/+source/aweather
[22:17] <micahg> mfisch: so, the patch needs to be carried fwd as the new upstream version still fails to build for the same reason, it might need to be rebased
[22:19] <mfisch> let me pull the rev from bzr and see if it builds
[22:19] <jtaylor> mfisch: don't bother about the branches, this case is quicker fixed by just doing it on the package directly
[22:20] <mfisch> jtaylor: just dputting a fix without checking in to bzr?
[22:20] <mfisch> I can certainly do that
[22:20] <jtaylor> yes, the importer will erge it into the branch after the dput
[22:20] <mfisch> got it
[22:20] <micahg> mfisch: well, you can propose a debdiff for someone else to dput :)
[22:20] <micahg> or a branch
[22:21] <mfisch> micahg: ah yes, I can't just dput this ;)
[22:23] <mfisch> while I do this, I'd also like to ask about the ftbfs for live-manual.  It failed to build in december, but from what I can see builds fine today.  if it's a transient error can it just be retried somehow?
[22:23] <jtaylor> yes
[22:24] <jtaylor> let me do one
[22:24] <mfisch> jtaylor: thanks
[22:24] <mfisch> jtaylor: worked for me on amd64 and i386
[22:24] <Amoz> pbuilder?
[22:25] <jtaylor> hm it also failed in oneiric
[22:25] <mfisch> Amoz: I used a vm, let me try a pbuilder
[22:25] <asomething> re: aweather 0.5.2-1ubuntu1 did build. The package is source version 3.0 (quilt) so you shouldn't need to touch debian/rules to make it apply. Someone synced it instead of merging.
[22:25] <Amoz> mfisch, I was just curious =)
[22:26] <asomething> Running "bzr merge . -r5..6" at the tip of lp:ubuntu/aweather will bring back those changes.
[22:27] <mfisch> asomething: so you don't need to add "dh --with quilt $@" to the rules file?
[22:27] <jtaylor> is bzr smart enough to refresh the patch?
[22:27] <jtaylor> I don't think so
[22:27] <micahg> mfisch: no, source format 3 has some built in source quilting
[22:28] <mfisch> micahg: awesome, I didn't know that
[22:28] <asomething> mfisch, not if it is source version "3.0 (quilt)" http://wiki.debian.org/Projects/DebSrc3.0
[22:29] <asomething> jtaylor, nope.
[22:31] <mfisch> asomething: that wiki wording could be misinterpreted: "Does a 3.0 (quilt) source package need to build-depend on quilt?    No because you're supposed to drop the quilt usage in debian/rules (patch/unpatch logic)."
[22:31] <mfisch> asomething: where drop could = "remove" or "drop .. in" = "add"
[22:32] <jtaylor> true
[22:32] <mfisch> English is fun
[22:32] <jtaylor> I'll fix it
[22:32] <asomething> mfisch, I could see that, but it definitely means "remove"
[22:32] <Amoz> I'd say "put" in that context
[22:32] <Amoz> not "drop"
[22:32] <Amoz> and I'm not even native english speaking
[22:33] <jtaylor> yes but drop is used that way, wy keep it ambigous
[22:33] <mfisch> Amoz: "drop the meat in the pan"
[22:33] <jtaylor> remove is clear
[22:33] <asomething> a drop in replacement
[22:33] <Amoz> jtaylor, yup, "remove" is more clear
[22:34] <Amoz> so, I've got this testcase in bzr-gtk failing, ftbfs
[22:34] <Amoz> it works if I run xvfb-run -a ./debian/testsuite.sh manually
[22:34] <Amoz> but in pbuilder it fails
[22:35] <asomething> Amoz, jelmer in #bzr would be the one to talk to. He's the debian maintainer and an upstream dev.
[22:36] <Amoz> asomething, thanks :(
[22:36] <Amoz> :)*
[22:37] <mfisch> well, live-manual will NOT build inside my chroot, so I'll go figure out what dep is missing
[22:37] <jtaylor> mfisch: libe-manual failed again
[22:37] <mfisch> jtaylor: jinx
[22:37] <jtaylor> I wonder why no bug was filed during the test rebuild
[22:38] <jtaylor> oh because it already had one
[22:38]  * jtaylor should not only look for "new" bugs
[22:42] <Amoz> hmm
[22:45] <mfisch> jtaylor: so it looks like we just need to pull a newer copy of live-manual from debian
[22:50] <jtaylor> quite a lot of changes :/
[22:55] <jtaylor> if you can identify the changes that would be great, but maybe its even worth requesting a freee exception