[09:34] <zyga> hi
[09:35] <zyga> do I need to assign my 'foo package needed' bug to any particular project or package?
[09:35] <zyga> https://bugs.launchpad.net/ubuntu/+bug/1254831
[09:41] <Laney> zyga: no, subscribe ubuntu-sponsors
[09:42] <Laney> also it'd be nice to submit it to debian mentors / DPMT
[09:46] <zyga> Laney: actually that situation is changed now
[09:46] <zyga> Laney: I got write access to the shared SVN repo on DPMT
[09:46] <zyga> Laney: and my sid package got a few review iterations now
[09:46] <zyga> Laney: so I guess we want to not go through motu but instead sync it from debian, correct?
[09:47] <Laney> zyga: yes, definitely
[09:47] <Laney> or upload from SVN if you want it in urgently
[09:48] <zyga> Laney: upload from SVN?
[09:49] <zyga> Laney: I'm doing one more modification to include the man page and I'll upload it to svn
[09:50] <Laney> yes, like take a snapshot
[09:50] <Laney> but I think they're quite fast at sponsoring / reviewing over in DPMT usually so that probably won't be necessary
[09:51] <zyga> Laney: I didn't understand what you mean by 'upload *from* svn'? upload to where? ubuntu?
[09:51] <Laney> yes
[09:51] <zyga> ah
[09:51] <zyga> I didn't know that is possible, I'm still quite new to this process
[09:52] <Laney> well, you just build a source package out of the VCS and give it the right version number to upload to Ubuntu
[09:52] <zyga> Laney: assuming it gets into the debian svn today, how long will it take it for the package to migrate to ubuntu?
[09:52] <zyga> Laney: (I also prepared 14.04 specific package with ubuntu1 suffix and different standards-version
[09:52] <Laney> <time in NEW> + 1 day-ish
[09:53] <zyga> Laney: new is 2 weeks?
[09:53] <zyga> Laney: and subsequent releases after that? we're likely to release the package and update it in debian bi-weekly
[09:53] <Laney> not sure what they're looking at atm
[09:53] <zyga> ah
[09:53] <Laney> yeah, a few hours to a day - not long
[09:53] <zyga> Laney: ok, this sounds great
[09:53] <Laney> after debian import freeze you need to request the syncs yourself though
[09:54] <zyga> Laney: what about standards version mismatch? will we sync to get 3.9.5 in trusty?
[09:54] <Laney> zyga: we usually don't bother changing that over Debian
[09:55] <zyga> Laney: ah, so lintian will complain but nothing breaks?
[09:56] <Laney> it's just for information really
[11:50] <vood> Hello, I have next question - what steps should I do, if I want to add my package in ubuntu repo ?
[14:06] <nobuto> I need some love to my backport request here: https://launchpad.net/bugs/1252729 It would be appreciated if someone takes a look.
[15:15] <ockham> hi, i'm currently trying to create a cowbuilder environment (under 13.10, ~/.pbuilderrc here: http://pastebin.com/7qmH3td1) -- which fails with:
[15:15] <ockham> W: Failed to fetch file:/var/cache/archive/saucy/Packages  File not found
[15:15] <ockham> E: Some index files failed to download. They have been ignored, or old ones used instead.
[15:15] <ockham> (the latter referring to an earlier line:)
[15:16] <ockham> Err file: saucy/ Packages
[15:16] <ockham>   File not found
[15:16] <ockham> any clue what's going on here?
[23:05] <quidnunc> Backporting packages is always a nightmare: Why am I getting "Dependency is not satisfiable: gyp (>= 0.1~svn1654)" when trying to backport nodejs to precise?
[23:05] <quidnunc> backportpackage -Urbw $PWD nodejs
[23:05] <cjwatson> Because precise doesn't have that version of gyp
[23:05] <cjwatson> $ rmadison -s precise gyp
[23:05] <cjwatson>  gyp | 0.1~svn1031-1 | precise/universe | source, all
[23:06] <quidnunc> cjwatson: Ah, I didn't notice subversion
[23:06] <quidnunc> cjwatson: thanks
[23:06] <quidnunc> and also f*ck
[23:06] <cjwatson> So I guess you'd need to backport gyp as well
[23:06] <quidnunc> sub-version number*
[23:07] <cjwatson> Or figure out how to weaken the dependency, although that's more intrusive for a backport
[23:07] <ari-tczew> quidnunc: you can try to minimize that version in B-D
[23:07] <quidnunc> cjwatson: Always fun going down that rabbit hole
[23:07] <quidnunc> what is B-D
[23:07] <quidnunc> ?
[23:07] <ari-tczew> Build-Depends
[23:07] <cjwatson> And sourceful changes require significantly more review than simple backports
[23:07] <ari-tczew> (see debian/control file)
[23:07] <quidnunc> non-official
[23:08] <quidnunc> ari-tczew: Right, I've never seen that abbreviation
[23:08] <ari-tczew> s/gyp (>= 0.1~svn1654)/gyp
[23:08] <cjwatson> But first check why it's there ...
[23:08] <cjwatson> Versioned relationships generally aren't introduced just for fun
[23:09] <ari-tczew> of course
[23:09] <ari-tczew> then see debian/changelog
[23:10] <ari-tczew> also, I look often for changes in certain files through Bazaar. Might be easier for you, as well.
[23:11] <quidnunc> When running pdebuild I get --> dpkg-checkbuilddeps: Unmet build dependencies. Are those build dependencies on my host or the pbuilder image?
[23:11] <cjwatson> In the chroot
[23:12] <quidnunc> dpkg-checkbuilddeps: Unmet build dependencies: cdbs dh-buildinfo libv8-3.14-dev (>= 3.7) libc-ares-dev (>= 1.7.5)
[23:13] <quidnunc> Why is it complaining about cdbs?
[23:13] <quidnunc> (Also I said precise but I'm building for raring)
[23:13] <cjwatson> You may not get accurate results as soon as one of your build-deps is uninstallable
[23:13] <cjwatson> In this case, libv8-3.14-dev is only available from saucy on - perhaps try libv8-dev instead?
[23:13] <quidnunc> cjwatson: But at least one of those is the problem right?
[23:13] <cjwatson> (assuming that's sufficient)
[23:14] <cjwatson> Yes, libv8-3.14-dev is the problem
[23:14] <cjwatson> At least that's how it looks from a quick examination of the archive
[23:16] <quidnunc> dpkg-checkbuilddeps: Unmet build dependencies: cdbs dh-buildinfo libv8-dev libc-ares-dev
[23:16] <quidnunc> alright I give up
[23:16] <quidnunc> I'll just install from source
[23:17] <cjwatson> Of course it could also be the pbuilder base image being broken or pbuilder just generally being terrible; I don't know, I don't use pbuilder :-)
[23:19] <quidnunc> Dependency hell has made a comeback: Developers can't use system packages for any dev platform (python, ruby, node, haskell) as they have effectively shunned distro packaging in lieu of their own packaging managers and it is very difficult to build system packages.
[23:20] <cjwatson> I've no interest in a philosophical debate on the subject I'm afraid
[23:21] <cjwatson> At least not without beer
[23:23] <quidnunc> just ranting. Worse is better these days