[00:51] <Resistance> anyone able to answer a question from #u-packaging, preferably a MOTU who understands the intricacies of the repos and stuff?
[00:54] <softcoder> anyhere know if the megaglest package will be pulled into 12.4 (as its data package has) even though arm and powerpc archs fail to build?
[00:55] <softcoder> if not could someone here tunr off arm and power archs so it will be fixed?
[00:55] <Resistance> softcoder: its in the 12.04 repos
[00:55] <Resistance> i'm not sure there's reasons for them to arbitrarily remove a package...
[00:55] <softcoder> why isn't it showing here: https://launchpad.net/ubuntu/precise/+search?text=megaglest
[00:55] <Resistance> esp. if i386 and amd64 build
[00:58] <ajmitch> softcoder: it's in precise, it was only uploaded 5 hours ago. it wouldn't surprise me if the search index is updated less often than that
[00:58] <Resistance> what ajmitch said
[00:58] <Resistance> fwiw...
[00:58] <Resistance> i recommend just trying to find teh source packages yourself
[00:58] <Resistance> i.e.
[00:58] <ajmitch> actually, it may be in the binary NEW queue, let me check
[00:59] <Resistance> https://launchpad.net/ubuntu/<release>/+source/<package>
[00:59] <Resistance> replacing <release> and <package> respectively
[00:59] <Resistance> ajmitch: the i386 and amd64 are marked as [NEW] on the source page
[00:59] <ajmitch> https://launchpad.net/ubuntu/precise/+queue - binary packages still have to be approved by archive admins
[01:02] <softcoder> ahh ok thc!
[01:02] <softcoder> thx guys!
[01:02] <softcoder> for checking
[02:50] <EvilResistance> ScottK:  around?
[02:50] <ScottK> Sort of.
[02:52] <EvilResistance> regarding that backport request... i dget'd znc 0.202-2, i can create a diff with the required change in debian/changelog, which i had to do because applying the debdiff of 0.202-1build1-to-0.202-2 failed because of the missing files or some other crap...
[02:52] <EvilResistance> is there any other required debdiff thing that i need to do, or would that manually-generated diff file work?
[03:26] <ScottK> I suspect that's OK, but I'd need to see it.
[03:28] <EvilResistance> i'll give you the pastebin version for review, note that to generate the debdiff i had to add a changelog entry and debuild -S it to make the .dsc, but you can omit that when it actually gets backported... http://pastebin.com/4RLkXPR8
[03:36] <EvilResistance> also, my main system is Natty, hence the 'natty' distribution entry
[03:49] <ScottK> that's fine, but for a backport with changes like this you do need to provide a changelog entry.
[03:49] <ScottK> target should be natty-backports and oneiric-backports (we need two)
[03:50] <ScottK> Versions should be 0.202-2~oneiric1 and 0.202-2~natty1
[03:52] <EvilResistance> i'll create two diffs shortly
[03:58] <EvilResistance> ScottK:  should I just attach them to the bug?
[03:58] <ScottK> Yes
[04:00] <EvilResistance> should i mark it as a patch?
[04:01] <EvilResistance> (LP's saying it looks like a patch)
[04:05] <EvilResistance> ScottK:  the two diffs are uploaded to bug 914996
[04:07] <ScottK> EvilResistance: Looks fine.  For future reference debian/changelog entries should be wrapped at 79 chars.
[04:07] <EvilResistance> ok
[04:07] <EvilResistance> my mistake :p
[04:08] <EvilResistance> now, since i havent had any food since lunch... i'm going to have some pizza :P
[06:23] <ISK> Hey
[06:27] <ISK> Hey, I packing GNU parallel, How to I do to register an ITP?
[07:10] <ISK> Hey, I packing GNU parallel, How to I do to register an ITP?
[11:31] <cjwatson> ISK: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518696
[13:54] <ScottK> EvilResistance: znc backports are done.  Thank you for your contribution to Ubuntu.  Please see how I edited debian/changelog for future reference.
[15:24] <Rhonda> Somehow my maverick uploads to my PPA get lost.
[15:26] <Rhonda> Successfully uploaded wesnoth-1.9_1.9.14-1~ppa1~maverick1_source.changes to ppa.launchpad.net for ppa-wesnoth-devel.
[15:26] <Rhonda> The other three uploads are there (oneiric, natty and lucid), but not maverick …
[15:41] <EvilResistance> ScottK:  yeah, i just did
[15:41] <EvilResistance> ScottK:  the only thing failing (which i expected) is the natty backports, but i noted that their building is blocked by a crit,triaged bug in LP
[15:42] <EvilResistance> Rhonda:  how long ago was that uploaded if I might ask?
[15:42] <EvilResistance> it takes PPA uploads about 5 - 10 minutes before they're usually pushed into the PPA and the builders
[16:01] <Rhonda> EvilResistance: Like, 4 hours?
[16:01] <Rhonda> EvilResistance: https://launchpad.net/~rhonda/+archive/wesnoth-devel/+packages for the other uploads and the delay so far
[16:02] <Rhonda> I didn't receive any mail, so no reject mail neither.
[16:19] <cjwatson> Rhonda: Silly question, but double-check that you signed it?
[17:05] <softcoder> can i ask for an artchive admin to approve (or examine and approve) megaglest
[17:05] <softcoder> its in the new queue and replaces glest
[17:06] <cjwatson> hm, I thought I'd processed that.  will do
[17:07] <cjwatson> I know I remember syncing it
[17:07] <softcoder> i checked 1 min ago and was still in the new queue
[17:08] <cjwatson> oh, it needed an Ubuntu modification, that's why it didn't happen semi-auto
[17:10] <cjwatson> softcoder: accepted
[17:10] <softcoder> yes because miniupnpc are different between debian and ubu currently
[17:10] <softcoder> thx
[17:15] <l3on> Hi all.... some one can help in adding SONAME to a package ?
[17:17] <tumbleweed> l3on: what are you trying to do?
[17:17] <tumbleweed> package a library?
[17:17] <l3on> tumbleweed, I'm trying to package a library
[17:18] <l3on> buildlog is here → http://debomatic64.debian.net/unstable/pool/oasys_1.5.0+hg2291-1/oasys_1.5.0+hg2291-1.buildlog
[17:20] <tumbleweed> l3on: what do you need help with?
[17:20] <l3on> tumbleweed, E: liboasys: sharedobject-in-library-directory-missing-soname usr/lib/liboasys-1.5.0.so
[17:21] <l3on> I'm looking at Makefile:
[17:21] <tumbleweed> it should be called liboasys1
[17:21] <tumbleweed> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[17:23] <l3on> tumbleweed, thanks I will look at that
[18:42] <EvilResistance> softcoder:  there's a queue... have patience
[18:42] <EvilResistance> oh cjwatson dealt with it :P
[18:43] <EvilResistance> Rhonda:  i see a maverick version there :/
[18:43] <EvilResistance> did you fix it?
[19:02] <softcoder> as in doctors patients :)
[19:08] <Rhonda> EvilResistance: But not 1.9.14, that is 1.9.13
[19:08] <Rhonda> cjwatson: dput doesn
[19:08] <Rhonda> cjwatson: dput doesn't allow upload of unsigned, so yes.
[19:32] <EvilResistance> whens the freeze on new packages for ubuntu occur?
[19:33] <jtaylor> 16 feb.
[20:14] <EvilResistance> jtaylor:  that's in 3 days?>
[20:14] <jtaylor> +31
[20:15] <EvilResistance> oh feb
[20:15] <EvilResistance> not jan :P
[20:15]  * EvilResistance facepalms
[20:15] <EvilResistance> good, i was worried because i have a package sitting in mentors.d.n waiting review/inclusion in Debian, if its included / approved sooner rather than later, i'd request it gets synced in :P
[20:16] <EvilResistance> (a *new* package)
[20:16] <jtaylor> hm no idea if really new packages still get in
[20:17] <EvilResistance> well considering its destined for whatever the non-main repos are, i'm assuming the MOTUs know the freeze dates for non-main repo stuffs
[20:17] <Laney> they do without any special effort until feature freeze
[20:17] <Laney> beyond a sync request
[20:17] <jtaylor> doesn't it need to go through some review?
[20:17] <jtaylor> or is that just during autosync?
[20:18] <jtaylor> and after muto sync acc is the same
[20:18] <Rhonda> EvilResistance: You wrote to the mentors mailinglist too, not just upload it to mentors.d.n, right?
[20:18] <EvilResistance> Rhonda:  the #debian-mentors @ oftc told me what to do
[20:18] <EvilResistance> so yes i did :P
[20:18]  * EvilResistance has been hanging out there almost as much as he hangs out on freenode
[20:19] <Laney> semi automatically pushed through the queue by a script, i believe
[20:19] <ScottK> EvilResistance: This is freenode.
[20:19] <EvilResistance> s/freenode/here/ then :P
[21:07] <softcoder> hmm getting timeout errors all days from launchpad
[21:07] <softcoder> all day not days
[23:44] <Q-FUNK1> https://bugs.launchpad.net/ubuntu/+bug/916303
[23:44] <Q-FUNK1> do I need anything else before I can upload to universe?
[23:46] <EvilResistance> um...
[23:46] <EvilResistance> whoops wrong chan
[23:46] <EvilResistance> sorry
[23:49] <tumbleweed> Q-FUNK1: getting it into Debian first is preferred
[23:50] <EvilResistance> ^
[23:50] <EvilResistance> tumbleweed:  i've got a package that i'm repairing in the Debian mentors.d.n list, if they support it and get it into Debian, will that new package autosync into Ubuntu?
[23:50] <EvilResistance> or do i have to request the sync myself?
[23:50] <Q-FUNK1> tumbleweed: true.  anything else?
[23:51] <tumbleweed> Q-FUNK: getting a review from another MOTU before uploading is recommended.
[23:51] <tumbleweed> EvilResistance: we are past Debian Import Freeze, so it'll need to be requested
[23:51] <Q-FUNK> tumbleweed: actually, according to the upload guide, it's a must.
[23:52] <tumbleweed> Q-FUNK: I thought so too, but https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages seems to say otherwise
[23:52] <tumbleweed> still, that doesn't look ubuntu-specific, getting it in Debian isn't a bad idea
[23:53] <EvilResistance> tumbleweed:  anything i should be concerned about if i want to have that package imported into Ubuntu?  i.e. should I have a MOTU review it?  or is the fact it got into Debian good enough?
[23:53] <Q-FUNK> tumbleweed: we intend to get it in debian at some point, but since I'm already a motu here but not a DM or DD, it's easier to start here.
[23:53] <tumbleweed> EvilResistance: if it builds on Ubuntu, that's good enough
[23:54] <EvilResistance> tumbleweed:  that is to say, builds in Precise?
[23:54] <EvilResistance> (it really doesnt have any builddeps afaict except for python)
[23:55] <tumbleweed> EvilResistance: yes
[23:55] <Q-FUNK> tumbleweed: another thing is, the window to get this into precise is getting shorter and yet we have a series of 6 packages that need to be uploaded and built in a precise order.
[23:56] <tumbleweed> yeah, I see the urgency :)
[23:57]  * tumbleweed would offer a review and debian sponsorship, but not for 6 packages that could be enormous :)
[23:57] <tumbleweed> anyway /me -> bed
[23:57] <ajmitch> night tumbleweed :)
[23:58] <tumbleweed> night
[23:59] <Q-FUNK> tumbleweed: I've been making debian packages since 2003, so I would think that my review of other people's packaging would be enough. :) of course, second opinions are always welcome.