[08:03] <dholbach> good morning
[08:05] <ESphynx> oh it's that time again =) Good morning Dan :)
[08:05] <obounaim> Good morning dholbach.
[08:06] <Rcart> good morning o/
[08:29] <dholbach> hi ESphynx, Rcart :)
[15:18] <obounaim> Hello everybody
[15:39] <dholbach> Is anyone interested in the ubuntu development hangout (on air) at 16 UTC (in 20m) and talk a bit about what you're working on?
[15:57] <vibhav> dholbach: I can be there
[15:57] <dholbach> vibhav, cool
[17:03] <Laney> dholbach: I'll join you for the next one if you like
[17:05] <dholbach> Laney, I'll add you to https://wiki.ubuntu.com/UbuntuDevelopment/Hangouts - you mean the one next week or the one early on thursday?
[17:05] <Laney> well I'll be away next week
[17:05] <Laney> 9UTC might be a bit early ...
[17:05] <Laney> put me down for the 11th :P
[17:06] <dholbach> awesome
[17:07] <dholbach> Laney, any specific topic you'd like to talk about or shall we just wing it?
[17:07] <Laney> desktop stuff I've been doing (gstreamer 1.0 porting which has scope for people interested in coding to help with)
[17:07] <Laney> motu stuff
[17:07] <Laney> release team
[17:07] <Laney> all that jazz
[17:07] <Laney> backports
[17:08] <dholbach> perfect
[17:08] <dholbach> thanks a bunch Laney
[18:36] <jtaylor> does ony main stuff get added to the jenkins autopkgtest suite or can universe go in there too?
[18:42] <alo21> hi all
[18:43] <alo21> how can create a debdiff with two dsc which are linked to the same .orig.tar.gz?
[18:43] <jtaylor> debdiff *dsc
[18:45] <jtaylor> mh markdown is in adt and its universe, are the things added automatically?
[18:45] <alo21> jtaylor: I receive as error that debdiff expects a .orig.tar.gz 1547 MiB instead od 941 MiB
[18:45] <jtaylor> wtf
[18:45] <jtaylor> what has such a large orig.tar
[18:45] <alo21> jtaylor: let me explane...
[18:46] <alo21> I have two versions of a progarm
[18:46] <alo21> one for example is v 1.0 and the other is 1.1
[18:47] <alo21> 1.0's dsc is linked to a 1_orig.tar.gz which is for example 75 MiB...
[18:48] <alo21> 1.1's dsc is linked to another 1_orig.tar.gz which  is 80 MiB
[18:48] <alo21> so the name of the orig.tar.gz are the same, but che contents are different
[18:49] <jtaylor> how can they have the same name but different content
[18:50] <jtaylor> the orig tar name must include the version
[18:50] <alo21> jtaylor: I am talking especially about blueman in MoM
[18:50] <jtaylor> so the orig tar in debian and ubuntu diverge?
[18:51] <alo21> yes
[18:52] <jtaylor> hm
[18:55] <alo21> jtaylor: someone suggests me to merge it by my hand, but this does not resolve the conflict between .dsc files
[18:55] <jtaylor> I would merge the debian changes into ubuntu and create a debdiff to the old ubuntu package
[18:55] <jtaylor> it can be properly merged next upstream release
[18:56] <jtaylor> what is the difference in the orig tar? just compression or is the content differnt?
[18:57] <alo21> between the debian and ubuntu packages there are 53 conflicts... so I think the content is different
[18:57] <jtaylor> check why its different please
[18:57] <jtaylor> that should not happen
[18:58] <jtaylor> conflicts should only happen because someone compressed it differently but the content should stay the same
[18:58] <jtaylor> checksum conflicts that is
[18:59] <jtaylor> vcs conflicts can arise due to other reasons and are annoying but not necessarily a problem
[19:35] <alo21> jtaylor, strange.. I can't run merge-buildpackage because it says me 'Unmet build dependencies'. This is the first time I occurred this problem
[20:41] <gotwig> Hello, Masters
[20:42] <gotwig> I have problems with packaging my app for Ubuntu 12.04. It seems to work with packaging for 12.10 and 13.04. : https://launchpadlibrarian.net/124231249/buildlog.txt.gz  | https://code.launchpad.net/~gotwig/+archive/foto-fixedpackages/+recipebuild/353068/+files/buildlog.txt.gz https://code.launchpad.net/~gotwig/+archive/foto-fixedpackages/+recipebuild/353067/+files/buildlog.txt.gz
[20:43] <gotwig> can someone help pls?
[20:49] <gotwig> quadrispro, hey
[21:08] <alo21> jtaylor, I run merge-buildpackage, and I received 'dpkg-source: info: you can integrate the local changes with dpkg-source --commit'... and it created a file (http://pastebin.ubuntu.com/1392794/)
[21:10] <micahg> alo21: Debian has the wrong orig tarball for blueman, so, IMHO, not worth merging
[21:11] <alo21> micahg, do you think is a good idea to open a bug in debian?
[21:11] <micahg> debian 691655
[21:11] <micahg> are the bots still missing?
[21:12] <micahg> https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/4016896
[21:12] <micahg> oops
[21:12] <micahg> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691655
[21:13] <micahg> it would be a fake merge anyways (need to use the Ubuntu orig tarball)
[21:13] <alo21> what 'bots' mean?
[21:13] <micahg> so, I'd just suggest making the one change that Debian made for the added dependency if it makes sense and wait for a new upload there
[21:13] <micahg> alo21: ubottu and friends
[21:14] <alo21> micahg, If I will make that change on the ubuntu package, I will not able to create the debdiff
[21:15] <alo21> ..
[21:15] <alo21> between the old and the new ubuntu
[21:15] <micahg> alo21: you'd need to start with the old ubuntu package and just make that change
[21:15] <micahg> (not merge, just make the fix)
[21:16] <micahg> making a debdiff in this case isn't trivial anyways
[21:17] <alo21> micahg, mm... I think no worth it
[21:18] <micahg> right :)
[21:18] <alo21> thank you so much for your support and spending time on helping me
[21:19] <micahg> I think the reason I didn't make the dependency change manually is that it's seeded everywhere already
[21:20] <micahg> well, except for kubuntu...but I doubt that people are running a gtk bluetooth manager in KDE
[21:25] <jtaylor> meh I'm really wasting buildd cycles...
[21:25] <jtaylor> stupid arch/-indep splitting and my inability to test properly
[21:29] <alo21> micahg, do you think doc-debian can be dropped (LP: https://launchpad.net/ubuntu/+source/doc-debian) (PTS: http://packages.debian.org/changelogs/pool/main/d/doc-debian/current/changelog) ?
[21:30] <micahg> alo21: why drop?
[21:30] <alo21> because I think all the ubuntu's changes are in debian now
[21:31] <micahg> oh, that, maybe try in a PPA
[21:31] <micahg> backportpackage can help with that
[21:32] <alo21> micahg, what? I would first import that in raring
[21:32] <micahg> alo21: no, use backportpackage to test build the Debian package in your PPA
[21:33] <micahg> in raring
[21:34] <alo21> micahg, usaully I use my pc to test the packages.... but my doubt is about merge or sync
[21:34] <alo21> usually*
[21:34] <micahg> alo21: right, you won't know with this one most likely unless it's a PPA, it seems to be a soyuz specific failure from the changelog
[21:35] <micahg> alo21: so you can test build locally to watch for obvious failures, then if that works, throw it in a PPA
[21:36] <micahg> if that works, you can probably request a sync, but did you ask Bhavani if he's working on it since he touched it last?
[21:36] <alo21> micahg, thanks for your advice... I'm going to contact him (do not worry)
[21:36] <micahg> thanks
[21:39] <alo21> you are welcome.... but do you think (reading the changelog) that all bugs are fixed in debian too now
[21:39] <alo21> ?
[21:41] <micahg> alo21: maybe, it's not explicit, but hinted at
[22:00] <jtaylor> builds in the queue are not executed if they have been obsoleted right?
[22:12] <micahg> jtaylor: I'm sure you're aware of how to do an arch only build locally, right :)
[22:12] <micahg> jtaylor: and yes, obsoleted builds should be skipped
[22:12] <jtaylor> yes
[22:12] <jtaylor> I just screwed up the testing
[22:13] <jtaylor> had the fix in the chroot but not in the tree I did the  -S
[22:42] <xnox> jtaylor: all packages are added to the jenkins autopkgtest, universe included.
[22:42] <jtaylor> xnox: thx
[22:43] <jtaylor> when are they built?
[22:43] <jtaylor> s/build/executed/
[22:45] <xnox> jtaylor: currently on every upload, the plan is to execute on every package upload as well as re-executing all autopkgtest of the reverse dependencies.
[22:45] <xnox> such that we can catch if new packageA breaks packageC & packageD which depend on packageA.
[22:45] <jtaylor> neat, though that requires quite some resources :O
[22:46] <xnox> not really, as the tests are very simple and quick. We don't have nearly enough tests to start causing a load problem.
[22:47] <jtaylor> if its so I can add some tests that take days ;)
[22:57] <jtaylor> what does adt actually stand for?
[23:06] <jtaylor> what kind of machine is hosting that jenkins instance, its faster than my localhost jenkins at my work pc ._.