[06:57] <dholbach> good morning
[07:05] <ajmitch> morning dholbach
[07:05] <dholbach> hi ajmitch
[07:15] <dholbach> huats, warp10, broder: any comments on the report?
[07:16] <huats> morning !
[07:16] <dholbach> salut huats
[07:16] <huats> dholbach: honnestly I found it great
[07:17] <huats> and I am really impressed by the work done
[07:17] <dholbach> huats, you had some comments about the 'conclusions' section - if you could look over it again and suggest something that is missing, that'd be nice
[07:17] <huats> dholbach: sure
[07:36] <Zhenech> mh, how are my chances to upload a new upstream minor(bugsfix) release to debian tomorrow and get it synced in time for precise?
[07:38] <dholbach> zhenech: which package is it?
[07:38] <Zhenech> dholbach, pokerth (a poker game/client), so pretty leaf-package
[07:39] <dholbach> it certainly sounds doable
[07:40] <Zhenech> cool, thanks
[09:40] <Whoopie> broder: Hi, have you found some time to look at bug 898003? Or could another dev have a look? The new package is to avoid a regression in precise.
[09:43] <Whoopie> dholbach: ^ do you have perhaps some time?
[09:44] <dholbach> Whoopie, can you maybe ask in #ubuntu-devel - it looks like there are currently two patch pilots available
[09:44] <dholbach> I'm a bit busy with something else right now
[09:45] <Whoopie> dholbach: sure, thanks for the hint.
[09:45] <dholbach> de nada
[09:46] <dholbach> (just check the topic)
[11:27] <broder> dholbach: sorry, i've basically not been reading any ubuntu-related emails since starting my new job last week. i think i'm likely to be pretty useless until uds
[13:29] <ScottK> tumbleweed: Thanks for taking care of my u-d-t bug so quickly.
[13:39] <dholbach> broder, no, that's fine :)
[13:46] <vibhav> Is ubuntuwire down?
[13:50] <tumbleweed> ScottK: np
[13:51] <ScottK> vibhav: It seems so.
[13:53] <vibhav> ah
[16:34] <jtaylor> is it possible to add an rc to precise and possible update it to final also after release?
[16:35] <jtaylor> concerns matplotlib
[16:37] <tumbleweed> that's a question for the SRU team. But I don't know of this ever happening
[16:39] <gotwig> I think I found a broken package
[16:40] <gotwig> npm and/or nodejs(-dev) seems to be broken
[16:40] <gotwig> people on the web said the npm version is too old
[16:41] <gotwig> Radium: hey
[16:41] <gotwig> Do you want a paste ?
[16:41] <gotwig> tough its very easy to install npm without a package
[16:42] <gotwig> ok, here is the paste....
[16:42] <gotwig> http://paste.ubuntu.com/928180/
[16:47] <jtaylor> gotwig: does the version in debian work?
[16:48] <gotwig> jtaylor: yes
[16:48] <gotwig> jtaylor: I think so
[16:48] <gotwig> they have a newer version
[16:48] <gotwig> its an old bug
[16:48] <gotwig> but its a shame
[16:48] <gotwig> that a broken packages comes into precise
[16:48] <jtaylor> it has no rdepends and ts broken, I guess its feasable to update it
[16:48] <gotwig> https://bugs.launchpad.net/ubuntu/+source/npm/+bug/863094
[16:49] <gotwig> critical but triaged :/
[16:49] <gotwig> jtaylor: do you think there is a way? couse of feature freeze
[16:49] <jtaylor> can you need a feature freeze exception
[16:50] <gotwig> becouse if there is no way; you are not able to use node.js with packages
[16:50] <gotwig> if that affects ubuntu server
[16:50] <gotwig> its very very
[16:50] <gotwig> bad
[16:50] <gotwig> and I think; it does!
[16:50] <gotwig> jtaylor: please help
[16:50] <gotwig> philipballew: hey
[16:52] <gotwig> may anyone else help???
[16:52] <jtaylor> hm it needs a whole tail of other packages ...
[16:52] <gotwig> becouse this is critical
[16:52] <gotwig> jtaylor: example?
[16:52] <jtaylor> some of them are RC in debian
[16:53] <gotwig> jtaylor: hm, so what can we do...?
[16:54] <jtaylor> gotwig: let me check what is all needed
[16:56] <SpamapS> gotwig: hi!
[16:56] <tumbleweed> SpamapS: there's been a fair bit of discussion of that here too
[16:56] <SpamapS> Ok
[16:57] <gotwig> SpamapS: hey
[16:57] <jtaylor> gotwig: we'd ahve to pull a huge node stack for it which has never reached debian testing
[16:57] <gotwig> !logs
[16:57] <jtaylor> + the main executable has 2 RC bugs one of them might cause a name change in future
[16:57] <tumbleweed> SpamapS: http://paste.ubuntu.com/928200/
[16:57] <jtaylor> I think its better to remove it from precise
[16:57] <SpamapS> If we ship npm, we're shipping it alone
[16:57] <tumbleweed> gotwig: logs only update hourly
[16:57] <SpamapS> the debian version is pretty much dead
[16:58] <SpamapS> unless something changed in the last 2 weeks
[16:58] <jtaylor> its been updated
[16:58] <jtaylor> 5 days ago
[16:58] <SpamapS> oh thats good to hear
[16:58] <SpamapS> so what else are we missing?
[16:58] <jtaylor> ~ 10 packages
[16:58] <jtaylor> lots of node-+ stuff
[16:59] <gotwig> that also affects ubuntu server, right?
[17:00] <jtaylor> I don't like debian bug 611698
[17:00] <tumbleweed> gotwig: ubuntu server is ubuntu. Just some different packages installed by default
[17:01] <tumbleweed> jtaylor: that bug isn't particularly new, thuogh
[17:01] <jtaylor> yes have it in oneiric already
[17:01] <jtaylor> so its probably not so bud
[17:01] <jtaylor> though it will cause problem when the debian maintainer gives in and renames it
[17:01] <tumbleweed> it sounds like ax25 node is being renamed
[17:01] <SpamapS> not having /usr/bin/node as nodejs binary path will without any
[17:01] <SpamapS> doubt render nodejs package unuseful for a vast majority of users.
[17:01] <SpamapS> I have to agree with that
[17:02] <tumbleweed> IIRC ax25 node doesn't need to be on PATH, and really, *who* uses it...
[17:02] <SpamapS> The fact that node.js, a widly popular program, uses the same namespace as node, an almost completely unknown program, should not mean that node.js has to call itself something else. That is *insanity*
[17:03] <tumbleweed> OTOH, the debian policy around that is sane
[17:03] <tumbleweed> things just take time to shake out
[17:04] <SpamapS> So, I'd rather ship with a Conflicts to node, than not ship at all
[17:04] <tumbleweed> +1
[17:04] <SpamapS> inappropriate? yes, likely to cause problems? no.
[17:04] <jtaylor> ok then who files the FFE for all the node- packages? :)
[17:05] <gotwig> +t
[17:05] <jtaylor> doing it on so short notice risks that we ship with a new but broken node stack :/
[17:05] <gotwig> +1 :/
[17:06] <tumbleweed> jtaylor: none of the node stack is seeded, so we have some time still
[17:07] <jtaylor> gotwig, SpamapS: if you get an FFe I can help with syncing etc but I'm not using node myself, so you need to do some testing
[17:08] <SpamapS> We have some node.js apps in the juju charm store. Testing is as easy as 'juju bootstrap && juju deploy subway' :)
[17:08] <SpamapS> In fact subway uses npm too
[17:08] <SpamapS> (it points at the PPA right now.. so we'd have to tinker a bit, but yeah, I can test easily enough)
[17:09] <SpamapS> So is this an FFE just for syncs from debian?
[17:09] <jtaylor> and the new version of npm
[17:10] <gotwig> jtaylor: I am not a packager, or what ever :(
[17:10] <jtaylor> gotwig: but you can test?
[17:10] <gotwig> jtaylor: yes, but I also dont have *much* time
[17:10] <gotwig> only a few hours :X
[17:11] <SpamapS> I can put an hour into testing.
[17:11] <gotwig> hm, so *what* exactly
[17:12] <gotwig> is there a stable package somewhere?
[17:12] <gotwig> there are few ubuntu ppa's with packages, right... ?
[17:12] <gotwig> but they are not actual, I think
[17:16] <gotwig> so whats with all these dependencies?
[17:18] <onli> hi. can someone direct me to what i should do if i have a new version of a program, which is in universe but not developed anymore, and would like the ubuntu-package to use the new version (which is on github instead of sourceforge, where the original version was?)?
[17:19] <tumbleweed> onli: contact the debian maintainer of the package (possibly by filing a bug)
[17:20] <onli> tumbleweed: i tried that. he is not active anymore (he lead me here ;) )
[17:20] <tumbleweed> onli: which package?
[17:20] <onli> tumbleweed, simdock
[17:20] <SpamapS> gotwig: So what we should probably do is pull the desired packages into a clean precise PPA and test them, then if we're satisfied that this is what we want for precise, file the FFE.
[17:22] <gotwig> SpamapS: ok. It looks that there not a few packages that are dependencies and right now not part of universe
[17:22] <gotwig> 're
[17:22] <SpamapS> gotwig: if you can note all of them, I can put them into a precise PPA.
[17:23] <gotwig> SpamapS: hm, I try to...
[17:25] <SpamapS> part of me wants to say meh.. and just drop node and npm.. they move pretty fast.. and in a year, nobody will want the version in precise anyway
[17:25] <gotwig> SpamapS: but than the whole infrastructure cra*hes
[17:25] <gotwig> :X
[17:26] <gotwig> SpamapS: http://packages.qa.debian.org/n/npm.html that does not look good, the thing in ()
[17:26] <gotwig> all unconsidered
[17:26] <jtaylor> it all goes down to nodejs
[17:26] <gotwig> SpamapS: Are you able import these packages for testing into a ppa ?
[17:26] <jtaylor> is it likely that there is a "whole infrastructure" ?
[17:26] <jtaylor> npm only exists in oneiric
[17:27] <gotwig> jtaylor: not exactly npm
[17:27] <gotwig> jtaylor: but the whole charms thing... etc.
[17:27] <gotwig> npm is needed to install dependencies, etc...
[17:28] <SpamapS> npm is node's cpan
[17:28] <jtaylor> then they are already broken
[17:28] <gotwig> jtaylor: seems so
[17:28] <gotwig> SpamapS: ^
[17:28] <SpamapS> gotwig: ?
[17:28] <gotwig> SpamapS: are you able to import these packages, directly?
[17:29] <SpamapS> which packages?
[17:29] <gotwig> SpamapS: the dependencies for the "new" npm on http://packages.qa.debian.org/n/npm.html
[17:29] <gotwig> SpamapS: and npm
[17:29] <jtaylor> they should all be syncable
[17:30] <SpamapS> ahh
[17:30] <SpamapS> yeah thats easy enough
[17:30] <SpamapS> how do we handle NEW on syncs?
[17:30] <SpamapS> like do we just let it go through since it already passed debian's NEW?
[17:31] <gotwig> NEW?
[17:31] <gotwig> what do you mean
[17:31] <jtaylor> someone from -release needs to check them
[17:31] <SpamapS> packages that don't exist in ubuntu hit the "NEW" queue
[17:32] <gotwig> oh 1.1.16 ?
[17:32] <Laney> technically it is the same, practically it is just approved
[17:32] <gotwig> ohh ok
[17:32] <Laney> but it is still manual
[17:32] <gotwig> SpamapS: why dont package the very new version...?
[17:32] <gotwig> SpamapS: or is that not stable? :X
[17:32] <SpamapS> why don't we package everything from trunk?
[17:33] <SpamapS> at some point..
[17:33]  * EvilResistance chuckles
[17:33] <SpamapS> pick a version.. and test it
[17:33] <gotwig> SpamapS: what xD?
[17:33] <gotwig> SpamapS: :/ but that testing may take very long
[17:33]  * SpamapS is so tired of working on the bleeding edge all the time.. :-P
[17:33] <EvilResistance> anyways, can someone point me to the formatting for package update/sync requests for post-release versions of Ubuntu?
[17:33] <EvilResistance> SpamapS:  you and me both :p
[17:34]  * gotwig likes to dance, but he is unable
[17:34]  * gotwig has dreams of a better npm for Ubuntu and the World
[17:34] <SpamapS> gotwig: it will be better.. until the next NPM shift where they break their repo's again..
[17:35] <jtaylor> fast moving large stacks are not things that work well in ubuntu :/
[17:35] <SpamapS> Yeah, universe is meant to be a convenience for tools and things that will be useful for a while. node developers are going to hate the version from precise.
[17:36] <SpamapS> Its already 0.6.12 and 0.6.14 is out.. quick call the flying monkies and get me that new version!
[17:36] <tumbleweed> even if it wsa brand new today, they'll hate it in6 months, never mind 5 years
[17:38]  * gotwig_ 's internet is broken
[17:38] <gotwig_> do you got my last message?
[17:38] <gotwig_> SpamapS: so are you going to use 1.1.16?
[17:39] <SpamapS> gotwig_: no, I'm going to at best sync what is in Debian
[17:40] <SpamapS> if it all builds fine
[17:40] <gotwig_> SpamapS: ok, I hope that version is fine
[17:40] <SpamapS> ok I'm uploading all of those packages to this PPA https://launchpad.net/~clint-fewbar/+archive/latesyncs
[17:41] <SpamapS> I'll try the subway nodejs app with it once it all builds. If that succeeds, I'll file the FFE to sync all those packages in and do the sync myself.
[17:42] <jtaylor> you need someone to ack a whole bunch of packages, maybe its better to file the FFe first to see if someone is willing to do that?
[17:42] <gotwig_> SpamapS: and please dont forget the viruses lol
[17:43] <gotwig_> SpamapS: how have you synced them so fast :O ?
[17:43] <tumbleweed> I'm happy to review the FFe, if nobody gets there earlier
[17:43] <gotwig_> tumbleweed: oh yes, please ^^
[17:43] <gotwig_> tumbleweed: what do you mean :X
[17:44] <SpamapS> gotwig_: backportpackage .. amazing tool
[17:44] <jtaylor> :( seeded-in-ubuntu times out
[17:44] <SpamapS> $ for i in npm node-abbrev node-fstream node-graceful-fs node-ini node-minimatch node-mkdirp node-nopt node-request node-rimraf node-semver node-tar node-which ; do backportpackage -u ppa:clint-fewbar/latesyncs -s unstable -d precise -y -w . $i ; done
[17:44] <SpamapS> specifically
[17:44] <jtaylor> just for me or everyone?
[17:44] <tumbleweed> jtaylor: ubuntuwire is down
[17:44] <jtaylor> k
[17:44] <tumbleweed> I'll set up another source for that data
[17:44] <gotwig_> tumbleweed: can you make a FFe?
[17:45] <tumbleweed> gotwig_: can't review it until you've done the testing :)
[17:46] <gotwig_> tumbleweed: oh thats what you want ;)
[17:46] <SpamapS> gotwig_: take a deep breath. :)
[17:46] <gotwig_> alright, but I have to note, I only noted the error when I wanted to install npm to install dependencies xD
[17:47] <gotwig_> so I can try node.js I am a total noob...
[17:47] <SpamapS> gotwig_: looks like the PPA builders are about 20 minutes behind, so it will be about an hour before we can test those
[17:47] <gotwig_> SpamapS: you can count on me ;)
[17:48] <SpamapS> gotwig_: use this time wisely. Get yourself a clean precise VM setup (to the cloud!) and then be ready to add the PPA and test.
[17:50] <gotwig_> SpamapS: what
[17:50] <gotwig_> SpamapS: to the cloud?
[17:50] <SpamapS> gotwig_: just suggesting that the cloud would be useful here. :)
[17:50] <gotwig_> I am a total noob
[17:51] <gotwig_> I have to drink my big boy milk first :O
[17:51] <gotwig_> SpamapS: or with chroot
[17:51] <SpamapS> gotwig_: yeah that should work fine too
[17:52] <tumbleweed> jtaylor: http://corelli.tumbleweed.org.za/ubuntu-qa/ubuntu-seeded-packages/seeded.json.gz
[17:54] <gotwig_> SpamapS: are there ubuntu cloud * images out there?
[17:54] <gotwig_> SpamapS: got a link for me ?
[17:54] <SpamapS> gotwig_: https://cloud-images.ubuntu.com/
[17:54] <gotwig_> oh that was easy thanks
[17:55] <gotwig_> SpamapS: server?
[17:55] <gotwig_> SpamapS: or precise/ ?
[17:56] <SpamapS> gotwig_: you'll want precise I think
[17:57] <gotwig_> SpamapS: but that are no isos
[17:57] <SpamapS> gotwig_: images != isos
[17:58] <gotwig_> SpamapS: I know
[17:58] <SpamapS> gotwig_: those are installed images. You can boot them up as a VM.
[17:58] <gotwig_> SpamapS: but now I download a tar gz
[17:58] <gotwig_> I just pressed 64 bit
[17:58] <gotwig_> is that wrong :/ ?
[17:59] <gotwig_> SpamapS: btw can I use that with virtualbox, too ?
[17:59] <SpamapS> gotwig_: in theory yes
[18:00] <SpamapS> gotwig_: though I don't know how to make that work
[18:00] <gotwig_> SpamapS: I am going to take a look for that..
[18:06] <gotwig_> SpamapS: why cant I choose my normal notebook for the tests?
[18:08] <SpamapS> gotwig_: you can, but its more meaningful if you test without any extra packages installed.
[18:08] <SpamapS> gotwig_: test with both!
[18:08] <gotwig_> SpamapS: of course, Sir
[18:08] <tumbleweed> most of use use minimal schroots for testing things
[18:08] <gotwig_> SpamapS: Do you have no test environmen ? Germany has slow Internet.
[18:09] <SpamapS> yeah chroot should be fine for this case
[18:14] <gotwig_> SpamapS: I am downloading ubuntu core right now, too
[18:14] <EvilResistance> are Universe repositories still being updated for precise?
[18:14] <gotwig_> SpamapS: do you think that works?
[18:14] <EvilResistance> i.e. not completely frozen
[18:14] <SpamapS> EvilResistance: yeah, they need release team ACK, but can be uploaded to right up to release day.
[18:14] <Laney> erm
[18:14] <Laney> you shouldn't rely on being able to upload your crack
[18:14] <SpamapS> EvilResistance: should only be bug fixes at this point.
[18:15] <Laney> but bug fixes are welcome
[18:15] <SpamapS> Laney: if node.js isn't crack.. I don't know what is. :)
[18:15] <Laney> hoho
[18:15] <Laney> if it's that fast moving then some kind of SRU thing should be worked out
[18:15] <EvilResistance> i think i know of a few bugs in ZNC that were released with the recent 0.206-1 in Debian, i'm digging up the changelogs now (which are semi vague), and am checking against the devs
[18:15] <gotwig_> SpamapS: I love node.js... So you should )
[18:16] <gotwig_> *should you - hard english
[18:18] <EvilResistance> SpamapS:  what do i need to submit to get a sync from sid to precise for a specific package?
[18:18] <EvilResistance> (its got a few bugfixes)
[18:20] <SpamapS> EvilResistance: file a bug. You can even use the 'requestsync' tool to do it from the CLI
[18:21] <SpamapS> EvilResistance: then you probably want to mention it in here so somebody can help get it done foryou.
[18:21] <EvilResistance> mmkay, gimme a few minutes, my internet is laggy as [CENSORED]
[18:26] <EvilResistance> SpamapS: as the debian changelogs dont outline the changes between 0.204-1 (Precise) and 0.206-1 (Debian Unstable), should i add to the sync request the changelogs from ZNC's main site to detail the specific changes?
[18:28] <SpamapS> EvilResistance: if it helps support the case for the sync, yes.
[18:28] <SpamapS> EvilResistance: or if it has anything that might be a concern.. so.. actually, no if.. just include it :)
[18:28] <EvilResistance> :P
[18:30] <Laney> yes, you should definitely include that
[18:31] <Laney> as well as evidence you have build, installed, upgraded and tested it
[18:31] <gotwig_> SpamapS: got my chroot
[18:33] <EvilResistance> Laney:  getting to that, the download/build is *slow* on this network
[18:33]  * EvilResistance blames the massive number of ARP packets floating around on said network
[18:35] <gotwig_> SpamapS: in which package is "add-apt-repository" ?
[18:36] <gotwig_> SpamapS: so what tests I have to run? I test every package , ok?
[18:37] <gotwig_> SpamapS: do you know a test command or something like that?
[18:37] <EvilResistance> isnt it in some dev tools thing?
[18:37]  * EvilResistance forgets the specific package name
[18:37] <tumbleweed> gotwig_: python-software-properties
[18:38] <gotwig_> tumbleweed: yeah, I already knew it thanks
[18:38] <gotwig_> tumbleweed: btw the ubuntu core image is a very good thing
[18:38] <tumbleweed> gotwig_: for chroots, I use mk-sbuild (in ubuntu-dev-tools)
[18:39] <gotwig_> I use chroots directly
[18:39] <tumbleweed> if you're doing a lot of this, you'll find some automation handy :)
[18:39] <gotwig_> tumbleweed: I know what you mean, I did it always on my own
[18:39] <gotwig_> becouse of virtual filesystems and such stuff
[18:39] <gotwig_> in this case not important, I think...
[18:40] <tumbleweed> indeed
[18:41] <SpamapS> gotwig_: for npm, you should install some of the libraries
[18:42] <gotwig_> SpamapS: eh yeah
[18:42] <gotwig_> SpamapS: I have a problem somehow
[18:42] <gotwig_> SpamapS: PM would be better, kay?
[18:57] <gotwig_> SpamapS: ^
[19:12] <tumbleweed> onli: sorry, forgot to reply
[19:13] <tumbleweed> so, simbock has never been in Debian, only Ubuntu
[19:13] <tumbleweed> *simdock
[19:13] <tumbleweed> and it hasn't been touched since the initial upload to hardy :/
[19:13] <tumbleweed> https://launchpad.net/ubuntu/+source/simdock/1.2-0ubuntu1
[19:15] <tumbleweed> onli: so, there's still time to update it before precise releases, but you need to go through the feature freeze exception process
[19:16] <tumbleweed> !ffe
[19:16] <tumbleweed> alternatively, if it's totally broken, we should remove it
[20:07] <onli> tumbleweed: i dont know if it's broken, its just really old
[20:08] <tumbleweed> if there are good upsides to updating it, and not too much risk, we can do it
[20:09] <onli> ok. think their should be (and the risks are low, it's a not much known desktop-app, nothing depends on it)
[20:10] <onli> "Please note that we expect requesters to have an updated package already prepared and tested!"
[20:10] <onli> think that will be the issue. i dont have that - that was kind of the reason why i reached out to the original maintainer
[20:11] <tumbleweed> onli: yes, it does need someone to do the work
[20:11] <tumbleweed> but that could be you
[20:11] <onli> ok. i never done that cleanly, only with debinstall or plainly with dpkg -b, without the schroot-environment for dependency-checking
[20:12] <tumbleweed> mk-sbuild can get you going pretty quickly
[20:12] <onli> ok
[20:12] <tumbleweed> or you could use pbuilder / pbuilder-dist
[20:12] <onli> pbuilder sounded great
[20:12] <tumbleweed> or test-build in a PPA, but the turnaround there is slower
[20:13] <onli> that was my original plan, especially if universe wouldn't work ;)
[20:13] <onli> ok, now i know the general proceedings
[20:13] <onli> thank you
[20:13] <tumbleweed> np
[20:14] <onli> (if you have an motu-apprentice on hand who wants to learn how to package, i would have a testproject for him now^^)
[20:24] <gotwig_> why is packaging so hard :O ?
[20:26] <tumbleweed> there's a lot to learn, but it's not that hard
[20:45] <fo0bar_> time permitting, could I get a review on #946067 please?  it affects cricket and mrtg, throwing warnings during cron runs.  thanks.
[20:46] <gotwig_> hm
[20:49] <SpamapS> Ok, testing is successful for a sync of npm+deps from Debian
[20:49] <SpamapS> I marked bug 863094 as a FFE and subscribed ubuntu-release
[20:56] <gotwig_> what version should we pick ? debian  http://packages.qa.debian.org/n/npm.html     OR newer PPA ppa:chris-lea/node.js
[20:58] <SpamapS> gotwig_: *debian*
[20:58] <SpamapS> new is great, but I'm not really going to put in the time to resolve the diff
[21:12] <SpamapS> FACEFOX: can you perhaps fix your IRC client?
[21:12] <SpamapS> FACEFOX: btw, howdy from a neighbor also in Los Angeles ;)
[21:12] <EvilResistance> he's doing this across the network i think
[21:14] <ScottK> SpamapS: Approved npm
[21:14] <SpamapS> ScottK: thanks!
[21:21] <gotwig_> ScottK: huh=
[21:22] <gotwig_> so what's now about npm?
[21:22] <gotwig_> I sent the maintainer of the PPA a mail
[21:22] <gotwig_> maybe he helps...
[21:24] <ScottK> SpamapS: Accepted.
[21:25] <SpamapS> gotwig_: the PPA is something to look at next cycle. Its over. Syncing > trying to figure out if that PPA is worth using
[21:25] <SpamapS> ScottK: I hope I didn't misunderstand, I submitted syncs for all the deps too
[21:25] <SpamapS> which was rather tedious because syncpackage has no -y
[21:25] <gotwig_> ehhh
[21:25] <gotwig_> ok
[21:25] <ScottK> SpamapS: That's the only one I saw in the queue.
[21:26] <gotwig_> just becouse the different packages
[21:26] <ScottK> It's also the only one I saw in the FFe.
[21:26] <SpamapS> ScottK: ahh, the FFE asked for all the deps
[21:26] <SpamapS> but maybe only in the comments, and not clearly enough
[21:26] <gotwig_> but how do we later remove all these packages, if there is no need for them?
[21:26]  * ScottK looks again
[21:26] <SpamapS> gotwig_: there *is* need for them
[21:27] <gotwig_> why does the PPA not have all these packages
[21:27] <SpamapS> gotwig_: people will want to use those libraries without npm.. hence them being split out.
[21:27] <gotwig_> incomplete?
[21:27] <SpamapS> gotwig_: thats exactly the kind of question I don't have time to answer ;)
[21:27] <gotwig_> oh I understand
[21:27] <ScottK> SpamapS: Are they all unseeded/universe?
[21:27] <SpamapS> ScottK: they're all NEW
[21:27] <gotwig_> that is better than I tought...
[21:28] <ScottK> Ah.  Different screen.
[21:28] <gotwig_> SpamapS: thank you for syncing
[21:28] <ScottK> Got it.
[21:28]  * ScottK will take care of.
[21:28] <SpamapS> ScottK: you're my hero.
[21:29] <gotwig_> SpamapS: and you are my one ^^
[21:30] <gotwig_> I am happy that you react so fast
[21:30] <SpamapS> gotwig_: you happened to catch me at a unique moment of clarity + interest :)
[21:30] <gotwig_> I have to go to sleep... too late for a 17 years old boy ^^
[21:31] <gotwig_> thank you all. So that is going to come into the release, right?
[21:31] <gotwig_> got any link :X ?
[21:31] <SpamapS> yes
[21:34] <gotwig_> no link, good night :(
[21:43] <ScottK> SpamapS: I think that's the lot of them.
[21:44] <SpamapS> ScottK: indeed I counted 14+npm
[21:46] <EvilResistance> thanks SpamapS for helping me get the sync request created quickly with requestsync.
[21:46] <EvilResistance> for MOTUs: LP Bug #981044
[21:47] <EvilResistance> or anyone who can process that sync request
[21:49] <jtaylor> EvilResistance: does it have a granted FFe?
[21:49] <EvilResistance> jtaylor:  FFe = ?
[21:49] <EvilResistance> i only just filed the sync request, who else do i need to poke
[21:49] <jtaylor> or does itneed one
[21:49]  * EvilResistance points out ZNC is already in Precise, this is just an update from Debian sid to that version in precise
[21:51] <EvilResistance> that'd be a question for you guys, as ZNC is already in, 0.206-1 from Debian fixes several bugs, as to whether it needs a FFe, i'd have to look into it
[21:51] <jtaylor> it does have a couple of changes
[21:52] <EvilResistance> who do i need to poke then regarding whether it needs an FFe or not?
[21:52] <EvilResistance> because one of the bugs addressed is a crash bug when ZNC is told to shutdown or restart
[21:52] <tumbleweed> EvilResistance: you make that decision yourself
[21:53] <EvilResistance> ah, see i forgot about feature freeze >.>
[21:54] <EvilResistance> shows you what happens when someone gets too busy to monitor release schedules >.>
[21:54] <tumbleweed> EvilResistance: that's why you subscribe to ubuntu-devel-announce
[21:55] <Laney> it's basically the same every cycle ...
[21:55] <EvilResistance> i'm already subscribed to enough mailing lists, any more and my emails will be flooded :/
[21:55] <tumbleweed> announce lists are low traffic
[21:55] <EvilResistance> true, but i'm on multiple non-announce lists, so they can be pretty high-traffic
[21:56] <EvilResistance> it might just be prudent to wait until precise is released as stable, then SRU it *shrugs*
[21:57] <EvilResistance> s/to/for me to wait/
[21:57] <jtaylor> the changes look quite small
[21:57] <tumbleweed> if it's SRU worthy, do it now
[21:57] <jtaylor> if it fixes a bug it should be synced now
[21:58] <EvilResistance> it fixes a couple of bugs including RFC compliance bugs, but they werent filed on LP
[21:58] <EvilResistance> as for whether it needs an FFe, i'm unsure, so...
[21:58] <gotwig_> hey
[21:58] <EvilResistance> because it not only is a newer upstream release, but also contains bugfixes
[21:59] <gotwig_> SpamapS: I want to report an dependency
[21:59] <Laney> yes, it does
[21:59] <gotwig_> for npm
[21:59] <gotwig_> SpamapS: that is not included in the debian package
[21:59] <Laney> ideally you would test an upgrade from oneiric and lucid
[21:59] <gotwig_> SpamapS: buildutils becouse of make
[21:59] <gotwig_> SpamapS: very often people complain about the error that make is not found; so there have to be the dependency for make; for npm install
[22:00] <EvilResistance> Laney:  which is why i might have to wait until after release, this system here is extremely close to death (hard drive death), so i dont have the luxury of test-upgrading
[22:00] <Laney> do you have chroots?
[22:00] <gotwig_> like just now in my case when I did npm install express ; than entered that directory and than ran npm install; I got error becouse make isnt installed
[22:00] <EvilResistance> Laney: crupted by bad sectors
[22:00] <EvilResistance> as i said this system is *VERY* close to death, almost half the drive is riddled with bad sectors
[22:01] <EvilResistance> (unfortunately its the only system i have at the moment)
[22:03]  * EvilResistance likely won't get a replacement drive until after release occurs, hence why this sync request may become an SRU
[22:03] <EvilResistance> so unless you're volunteering to test, Laney, this'll remain pretty much stagnant
[22:03] <jtaylor> an sru is a lot more work
[22:04] <jtaylor> you need to extract the bugfixes from the changes
[22:04] <EvilResistance> tell that to the Debian packager for ZNC, they refuse to use patches
[22:04]  * EvilResistance has said this to them time and time again
[22:05] <EvilResistance> oh, and what's more, their trunk on github doesnt have logs for when a stable release occurs, making finding bugfixes exceptionally harder
[22:05] <jtaylor> why should they use patches?
[22:05] <kklimonda> EvilResistance: the diff for znc 0.206-1 looks simple enough, and I don't see us maintaining znc ourselves anyway so I'd be for syncing it now
[22:06] <kklimonda> the actual code diff is small: "10 files changed, 55 insertions(+), 14 deletions(-)"
[22:06] <gotwig_> SpamapS: sorry, just the packages 'make' and 'g++' are missing .
[22:07] <gotwig_> SpamapS: make sure you add them both to dependency list. Seems that these packages also are missing in the dependency list of the version of that PPA packager.
[22:07] <SpamapS> gotwig_: Thats certainly a bug, but its not critical. Should probably be in the Recommends, since many of the npm packages will work w/o make.
[22:07] <EvilResistance> ugh, system finally froze up and died, now i'm IRC-ing via my ZNC with my phone (EVIL way of IRCing... >.>)
[22:07] <gotwig_> SpamapS: ok.. I find it critical :X I mean very many noobs wrote about that (on mac) in forums
[22:07] <SpamapS> things that affect noobs are important, but they're not critical.
[22:08] <EvilResistance> kklimonda:  this'd need an FFe according to Laney, and since my system is dead, i cant file an FFe (given that my phone is limited in capabilities)
[22:08] <gotwig_> SpamapS: so are you adding the both somehow?
[22:08] <SpamapS> gotwig_: when make is not installed, you can work around it, by.. installing make :)
[22:08] <gotwig_> SpamapS: :O you're so smart ^^
[22:08] <SpamapS> gotwig_: no, but it should be opened as a bug against the Debian package.
[22:08] <gotwig_> SpamapS: hm, so why not
[22:09] <SpamapS> gotwig_: its a legitimate issue. Please file a bug.
[22:10] <gotwig_> SpamapS: yes... I have to look...
[22:12] <gotwig_> SpamapS: does Ubuntu sync Debian packages one to one?
[22:13] <SpamapS> gotwig_: yes
[22:13] <SpamapS> gotwig_: for the first half of the release cycle, they're automatically synced
[22:14] <SpamapS> gotwig_: unless the Ubuntu package has changed
[22:14] <gotwig_> SpamapS: ok, I am unfamiliar with reporting debian bugs :(
[22:14] <SpamapS> gotwig_: report it in Ubuntu then, and it will get forwarded
[22:15] <gotwig_> SpamapS: for that package? but its not included in ubuntu yet
[22:15] <SpamapS> gotwig_: npm or something else?
[22:15] <SpamapS> https://launchpad.net/ubuntu/+source/npm
[22:15] <SpamapS> very much included in Ubuntu :)
[22:16] <gotwig_> that was * fast
[22:16] <SpamapS> gotwig_: well it was included long before we started
[22:16] <SpamapS> just at an older version
[22:16] <gotwig_> yes
[22:17] <gotwig_> SpamapS: and does oneiric get an update, too?
[22:18] <kklimonda> EvilResistance: I can test upgrade from znc lucid version to precise, if someone else can test upgrade from oneiric I don't see why would that even need a FFe - there aren't really any new "features" and FinalFreeze doesn't affect unseeded packages afair (although this one could be better documented).
[22:18] <kklimonda> (in other news, sbuild is a terrible tool for building packages - any idea if pbuilder supports lvm snapshots? ;))
[22:22] <gotwig_> SpamapS: https://bugs.launchpad.net/iranpm/+bug/981213 , correct?
[22:23] <gotwig_> SpamapS: could you please change the "affects debian" or something like that, part?
[22:27] <SpamapS> gotwig_: it will get picked up during normal triage
[22:28] <EvilResistance> kklimonda:  if you upgrade in that fashion, you may need to change the debian requirements, remove 'swig' as a build-dep, not sure about Lucid's ability to upgrade easily (given that there've been significant changes since lucid's version)
[22:28] <gotwig_> SpamapS: do you have found any other bugs?
[22:28] <SpamapS> gotwig_: no
[22:28] <gotwig_> SpamapS: so does it work for you :) ?
[22:28] <kklimonda> EvilResistance: that will affect upgrades to 0.204-1 anyway, right?
[22:29] <EvilResistance> kklimonda: there'll also be build dep errors on lucid, because swig2.0 isnt available in lucid (last i checked) and won't backport
[22:29] <kklimonda> EvilResistance: I don't have to build it on lucid though
[22:29] <EvilResistance> (same applies to maverick, and natty), but when upgrading from lucid to precise, it should work (as swig2.0 exists on precise)
[22:30] <EvilResistance> ah, right, upgrading direct from lucid -> precise, that'd fix the builddeps issues