[00:02] <Laney> VERSION:=${shell cat debian/changelog | head -1 | sed -e's/^maradns (//' | sed -e's/-[[:digit:]]\+) \w\+; .*//' }
[00:03] <Laney> the archive is a source of wonder
[00:03] <Laney> (resulted in make -f build/Makefile.linux all COMPILED=\""Linux system at Tue Jan 10 00:01:39 GMT 2012"\" VERSION=\"2.0.04-1ubuntu1) precise; urgency=low\"
[00:03] <Laney> /bin/sh: 1: Syntax error: ")" unexpected
[00:03] <Laney> )
[00:06] <Resistance> Laney:  who would process the sync request, if you know?
[00:07] <Laney> Resistance: a sponsor (did you subscribe ubuntu-sponsors?)
[00:08] <Resistance> Laney:  negative, point me to the links?
[00:08]  * Resistance is having issues with searching atm
[00:08] <Resistance> (FFox exploding)
[00:08] <Laney> SyncRequestProcess says
[00:08] <Laney> "To request a sync, file a bug in Launchpad with the above information (the requestsync tool discussed below makes this simple). Once the bug is complete and correct, if you are not an Ubuntu developer, subscribe (NOT assign) ubuntu-sponsors"
[00:09] <Resistance> ah
[00:09] <Resistance> done (i think)
[00:14] <Resistance> Laney:  which "email address" does it display when it refers to bug #523093?
[00:14] <Resistance> in that wiki for SyncRequestProcess (note my emails are public anyways)
[00:16] <Resistance> (i think)
[00:17] <Laney> your contact address
[00:17] <Resistance> i see...
[00:17] <Laney> the one that launchpad mails you on
[00:17] <Resistance> i take it i cant have my ubuntu.com email show up?
[00:17] <Laney> no you can't have that as your primary email sadly
[00:17] <Resistance> (since it autoforwards to the primary LP address, according to pleia2)
[00:17] <Resistance> thought not
[00:17]  * Resistance wishes you could :P
[03:59] <Resistance> anyone able to help me create a patch for a package?
[04:02] <Resistance> anyone?
[04:10] <kgoetz> hi all. are packages for this release being synced from unstable or testing? we just uploaded freeciv into debian and i'm wondering if i'll have to file a sync request
[04:12] <Resistance> if by "this release" you mean Precise
[04:12] <Resistance> its being synced from sid afaik
[04:12] <Resistance> (note i'm not a MOTU, but from what i've seen everything's coming from sid)
[04:13] <kgoetz> precise, yep :)
[04:13] <kgoetz> hopefully freeciv will scrape in then, thansk :)
[04:14] <Resistance> we hope :P
[04:14] <Resistance> s/we/you/
[04:15] <kgoetz> hehe
[04:34] <Resistance> if there's a package i uploaded a patch for, and the bug is triaged, should I change the status from "Triaged", or just leave it?
[04:46] <ScottK> kgoetz: Autosync was from Testing, but it's done for this cycle anyway, so a sync request will be needed.
[04:47] <kgoetz> ScottK: thanks. i'll have a dig around on the wiki and work out what needs to be done :)
[05:16] <Resistance> ScottK:  who checks the sync requests, and how often do those requests actually get checked/handled?
[05:17] <Resistance> ScottK:  i ask because the sync i asked to be done for ZNC from Debian Sid includes a vulnerability fix
[05:19] <Resistance> (if you're around)
[05:46] <ScottK> Resistance: You should subscribe the sync bug to ubuntu-sponsors and it'll get reviewed as part of the sponsorship queue.
[05:47] <Resistance> i did that
[05:47] <Resistance> ohhhhhhhhh
[05:47] <Resistance> wait a sec....
[05:47] <Resistance> would that explain why a soyuz icon shows up next to the Ubuntu project in my LP page?
[05:47]  * Resistance has been trying to figure out why that's there, because it wasnt there yesterday
[05:48] <ScottK> Dunno.  Link please?
[05:48] <Resistance> https://launchpad.net/~trekcaptainusa-tw
[05:49] <Resistance> see also: https://answers.launchpad.net/launchpad/+question/184233
[05:49] <Resistance> (me trying to figure out why the Ubuntu project has a soyuz icon next to it on his LP page)
[05:49] <ScottK> It's probably 2012-01-04 	PPA package upload accepted
[05:50] <Resistance> it *shouldnt*
[05:50] <Resistance> because that's within my own PPA
[05:50] <ScottK> Why not, I think it's not really a soyuz icon, but a uploaded stuff icon.
[05:50] <ScottK> I agree.  PPA shouldn't count for that.
[05:50]  * Resistance has never had any PPA uploads ever trigger a soyuz icon
[05:50] <ScottK> Dunno.
[05:50] <Resistance> the #launchpad people are stumped too
[05:50] <Resistance> hence the question
[05:51] <ScottK> Sync request wouldn't do it until it was processed and the sync done.
[05:51] <Resistance> i highly doubt that my submitting patches would do that...?
[05:51] <Resistance> indeed...
[05:51] <Resistance> which is why i'm thoroughly confuzled :/
[05:51] <ScottK> Once they are uploaded, it might.
[05:51] <Resistance> (tis also late, so i should be headed to sleep anyways)
[05:51] <ScottK> Sorry.  I'm not much help.
[05:51] <Resistance> no problem :P
[06:32] <siretart> dupondje: can you confirm that restarting lxdm is no longer necessary / work with the patch?
[13:53] <EvilResistance> any MOTU able to confirm something?
[13:53] <EvilResistance> it was my understanding 10.04 would EOL with 10.10... but https://wiki.ubuntu.com/Releases#Stable seems to suggest otherwise
[13:54] <EvilResistance> nevermind
[13:54]  * EvilResistance got the answer and misread something :P
[13:54] <Rhonda> Why do you expect an EOL half a year later?
[13:54] <Tm_T> EvilResistance: /;
[13:54] <Tm_T> (; even
[13:54] <EvilResistance> Rhonda:  misread something :P
[13:54]  * EvilResistance facedesks
[13:54] <EvilResistance> this is why i drink tons of coffee...
[13:54] <EvilResistance> keeps me alert >.>
[13:55] <Tm_T> EvilResistance: save the desk (and face)
[13:55] <EvilResistance> speaking of coffee, i think mine's finished brewing
[13:58] <EvilResistance> Tm_T:  if i ever make a fail statement like the one i just did, tell me to go get more coffee :P
[13:59] <EvilResistance> because something is wrong with me if i'm making fail statements like that
[13:59] <Tm_T> EvilResistance: nah, that was a tiny error that did no harm
[13:59] <EvilResistance> Tm_T:  it messed with my brain :P  and considering i only got 5 hours of sleep, i think coffee is a prerequisite to me being able to focus :P
[14:02] <Tm_T> my experience says you cannot replace sleep in the long run (:
[14:03] <micahg> while (sleep == NEEDED) { drink_caffeine(); }
[14:04] <EvilResistance> while (sleep == NEEDED && daysAwake <= 3) { drink_caffeine(); }
[14:04] <EvilResistance> if (daysAwake >=3) { pass_out(); }
[14:05] <EvilResistance> s/>=/>/
[14:06] <EvilResistance> i once had so much caffeine in a multiple-day sequence i was up for 6 straight days... the 7th day i passed out :P
[14:08] <jakewins_> Hey all! I'm putting together my first debian package (for the neo4j.org project) and have two cosmetic questions, hoping someone has the time to help out..
[14:08] <EvilResistance> jakewins_:  what generally do ya need?
[14:08]  * EvilResistance isnt an MOTU, but does packaging here and there
[14:09] <jakewins_> One, when I install my .deb via the Ubuntu software center, after install, the "install" button remains available, is that expected? (or should it turn into "uninstall" or "reinstall" or something?)
[14:09] <EvilResistance> *sips his coffee*  ahh... Tm_T give me 20 minutes, i'll be as awake as if i had slept 13 hours :P
[14:10] <jakewins_> Two, the ubuntu software center doesn't pick up that the package is open source, it shows the license as "unknown"
[14:10] <EvilResistance> jakewins_:  in my test installations of my binaries, i've seen that button thing as normal...  although Synaptic shows it as installed (yes, i still use synaptic)
[14:11] <EvilResistance> and i also have had that same issue as you've stated wtih LICENSE stuff
[14:11] <jakewins_> EvilResistance: Thanks!
[14:11] <EvilResistance> this is why i put my packages into my PPAs (or my archive for packages)
[14:11] <jakewins_> Does putting them in a PPA solve it?
[14:12] <EvilResistance> well considering I use synaptic instead of software center, idrk.  but the debian/copyright file contains all the licensing details, and all my stuff is released either under the GPL or the LGPL (depending on what the project uses)... (more often than not, I use the GPL)
[14:13] <EvilResistance> *checks something*
[14:14] <EvilResistance> read this: https://wiki.ubuntu.com/SoftwareCenter#Determining_software_item_information
[14:15] <EvilResistance> The license label for an item should be: “Open source”, if it is in Main or Universe; “Proprietary”, if it is in Restricted or archive.canonical.com; “Unknown”, if it is anywhere else (including Multiverse and standalone packages).
[14:15] <EvilResistance> since its a standalone, it shows up as "Unknown"
[14:15] <nabil> hi everyone
[14:15] <EvilResistance> jakewins_:  ^  (see above)
[14:16] <jakewins_> Ah, and the license label is set in PPA?
[14:16] <EvilResistance> jakewins_:  fwiw, i'd ignore what the "license" field of software center says, and focus on what you have in the debian/copyright file... if its GPL or LGPL or one of the open-source licenses i think you're fine
[14:16] <jakewins_> EvilResistance: Yeah, feel the same way
[14:16] <jakewins_> Thanks for your help!
[14:17] <EvilResistance> jakewins_: i havent had any *issues* with PPA things, but software center is just interfaces with apt... when i install things via PPAs, its usually via CLI (apt-get, aptitude, etc.)
[14:17] <EvilResistance> or god forbid synaptic :P
[14:17] <nabil> I think you must hear that really often, but I was wondering which is the easier way to start contributng for Ubuntu... I am kinda lost on the project...
[14:17] <jakewins_> lol
[14:18] <jakewins_> nabil: take a look at https://wiki.ubuntu.com/ContributeToUbuntu
[14:18] <nabil> I can add that I am a junior engineer in computer sciences, kinda good at C, but does not have a good grasp on system dev
[14:18] <EvilResistance> nabil:  there's multiple ways to contribute :)  depending on what you mean by contribute.  I contributed via support channels, #ubuntu, #ubuntu-server, ubuntuforums.org, etc.  if you want ot actually contribute to the coding and dev, start dealing with bugs and things
[14:18] <EvilResistance> there's bitesize bugs too
[14:18] <EvilResistance> (good for people starting out)
[14:19] <jakewins_> One more question: If I want to move towards making this package available in the public repos, I'm assuming setting it up in a personal PPA is initial step
[14:19] <EvilResistance> jakewins_:  define "available in the public repos"
[14:19] <EvilResistance> you mean like in the repos from Ubuntu?
[14:19] <EvilResistance> jakewins_:  i'd consider submitting your package to Debian for inclusion...
[14:19] <jakewins_> Preferrably general debian repos
[14:19] <jakewins_> Yeah
[14:19] <nabil> ok EvilResistance, but even bugs looks hard for me
[14:19] <nabil> very freakin specific
[14:19] <EvilResistance> jakewins_:  because submitting a package to Debian is far easier than submitting directly to Ubuntu
[14:19] <jakewins_> Makes sense
[14:20] <nabil> I am now changing nick because nabil is already reserved
[14:20] <jakewins_> So debian package maintainers is the people to talk to then I assume..
[14:20] <EvilResistance> jakewins_:  also, when its included in Debian sid, it'll be included later in Ubuntu (probably whatever q-series is)
[14:21] <EvilResistance> or perhaps even precise, but you have to go through the debian side
[14:21] <EvilResistance> jakewins_:  #debian-mentors @ irc.oftc.net is the home of their packaging helpers
[14:22] <EvilResistance> i've gotten more than enough help there building packages for both Debian and Ubuntu (although I come here to #ubuntu-motu or #ubuntu-packaging for Ubuntu-specific help)
[14:22] <EvilResistance> Ramz00z:  yeah, i found that to be the case as well, its why most of my launchpad karma comes from specification tracking for projects rather than bug fixing :P
[14:22] <jakewins_> EvilResistance: Great, thanks so much for your help!
[14:23] <EvilResistance> jakewins_:  yep, feel free to stop by and poke the MOTUs if you need more help.
[14:23] <EvilResistance> :)
[14:26] <EvilResistance> Ramz00z:  fwiw, i didnt start out dealing with bugs until i reported a few
[14:27] <EvilResistance> Ramz00z:  after that, i just kept helping out everywhere... in the IRC channels, on ubuntuforums.org, on askubuntu...
[14:27] <EvilResistance> didnt actually move into the technical aspects including packaging until after I had at least 6 months of command line experience working with server administration
[14:28] <EvilResistance> only branched out into bug fixing and patching yesterday :P
[14:28] <Ramz00z> yeah that's what I was thinking
[14:28] <EvilResistance> (otherwise, i report bugs like the back of my hand)
[14:28] <Ramz00z> isn't being "expert" in Ubuntu far more important than being good at prog ?
[14:28] <Ramz00z> because I am the latter but REALLY not the first...
[14:29] <Ramz00z> Ubuntu is just ocean wide... imoo
[14:30] <EvilResistance> being good at programming helps, but i'm by no means an expert
[14:30] <Ramz00z> I use it to dev but I don't really go deep... I must know like 20 command lines top
[14:30] <EvilResistance> i dont really need to know more than basic command line functions
[14:30] <Ramz00z> I guess only core dev are experts ^^
[14:30] <EvilResistance> and the functions of debuild, dpkg, aptitude, quilt (for patching packages), dget, backportpackage...
[14:31] <Ramz00z> and even them may not know every side of the project
[14:31] <EvilResistance> i may know a bunch about how Ubuntu works, and i may know some tricks to making things happen...
[14:31] <EvilResistance> but i dont know anything
[14:31] <EvilResistance> in comparison to me, the MOTUs are technically packaging gods
[14:31] <EvilResistance> and probably some of the most knowledgeable Ubuntu experts I know
[14:32] <Ramz00z> Becoming a MOTU is wayyyyyyyyyyyyyy down the road for me ^^
[14:32] <EvilResistance> (save Mark Shuttleworth, who probably knows everything there is to know, or where to get support for everything)
[14:32] <Ramz00z> I've been thinking about developping for Ubuntu for years now
[14:33] <Ramz00z> never found a project that I could effectively help
[14:33] <EvilResistance> well i've recently taken it upon myself to work directly with a few projects that have PPAs but no skilled packagers
[14:33] <EvilResistance> (thereby ending up with incomplete packages and they have no idea why)
[14:33] <EvilResistance> granted, i have a good number of PPAs of my own
[14:34] <Ramz00z> I'm about to get slapped I guess, but what's PPA ? :$
[14:34] <EvilResistance> (and most recently, i've gotten involved with NGINX and ZNC, but not via Launchpad
[14:34] <EvilResistance> !ppa
[14:34] <EvilResistance> Ramz00z:  ^
[14:35] <Ramz00z> thanks
[14:35] <Ramz00z> Didn't know they had a word to say "third party packages" ^^
[14:35] <EvilResistance> heh
[14:35] <EvilResistance> well the nginx project has its own PPA
[14:35] <EvilResistance> for up-to-date stables
[14:35]  * EvilResistance has helped once or twice with them
[14:36] <EvilResistance> been focusing on ZNC lately (backporting, and updating it)
[14:36] <EvilResistance> oh snap, its almost class time...
[14:36] <EvilResistance> *runs*
[14:37] <EvilResistance> (I'm a University student, but I still find time to contribute to ubuntu xD)
[14:39] <EvilResistance> oh dear, i misread the time... class doesnt start for an hour :p
[14:41] <Ramz00z> Evil I think you frightened every student out there ^^
[14:42] <EvilResistance> Ramz00z:  nah, i think its one of the freenode servers exploding
[14:42] <EvilResistance> i've seen this before :P
[14:43] <Ramz00z> nice exploding then !
[14:45] <Ramz00z> launchpad is not dedicated to Ubuntu, isn't it ?
[14:45] <Ramz00z> because I see an Android Project there... oO
[14:46] <tumbleweed> launchpad is run by canonical, primarily for Ubuntu, but there are many other projects on it too
[14:46] <Ramz00z> ok Ubuntu is just one of the projects
[14:46] <EvilResistance> and this is how i know it was an explodificated server that caused that mass death:  -RichiH/Wallops- Hi all. As you probably noticed, one of our servers just had a hiccup. It seems to be stable now, but we are investigating nonetheless.
[14:47] <EvilResistance> what tumbleweed said :P
[14:52] <Ramz00z> yeah they can investigate... Cause it won't disappear !
[14:52] <Ramz00z> always hated networking...
[16:55] <toabctl> what should i do to get a package from debian sid into precise (the package is currently not in precise, so it's a new package). i already filled a sync request with requestsync. is this enough?
[16:56] <Laney> yes
[16:56] <Laney> just watch your mail for followups from sponsors
[17:02] <toabctl> ok. thx
[17:38] <jtaylor> micahg: didn't you want to look at the numpy and svn merge requests?
[17:39] <micahg> jtaylor: yes, sorry. did I say I'd look at svn  also?
[17:41] <jtaylor> I don't think so, but it would be appreciated :)
[18:06] <philsf> hi, in natty I used dh-make-perl + dpkg-buildpackage to package a perl app I'm developing, but now in oneiric it's not working. dpkg-buildpackage says it can  parse the dependencies. Can anyone hint me on what's wrong and how can I fix this?  Paste at: http://paste.ubuntu.com/799639/
[18:07] <jtaylor> philsf: can you paste debian/control please
[18:11] <philsf> jtaylor, http://paste.ubuntu.com/799645/
[18:14] <jtaylor> philsf: remove the perl/ and science/ before all dependencies
[18:14] <philsf> jtaylor, is this a bug in recent dh-make-perl versions?
[18:15] <jtaylor> no idea, it may be a feature to get people to check the dependencies
[18:17] <philsf> lol
[18:17] <philsf> actually, this debian/control is from the lucid version. the oneiric d-m-p version doesn't work (see first paste). any ideas what it means?
[18:24] <jtaylor> hm you could try clearing your cache
[18:26] <jtaylor> ~/.cpan
[18:29] <philsf> I tried this, already
[18:30] <philsf> oh wait. I tried in another oneiric box. in this one I don't have a ~/.cpan. It shouldn't even work without a basic config, right?
[18:30] <jtaylor> don't know
[18:31] <jtaylor> I'm not familiar with perl
[18:31] <jtaylor> can this changelog weirdness cause any trouble when we sync? http://anonscm.debian.org/gitweb/?p=pkg-java/libhibernate-jbosscache-java.git;a=blob;f=debian/changelog;h=e208d0e4c525f0027eef470d515ddc09288cfb45;hb=HEAD
[18:31] <philsf> on any other box, if I remove .cpan and invoke the cpan shell, it promply autoconfigures cpan. in this one, this isn't happening
[18:31] <jtaylor> latest-debian-changelog-entry-without-new-version
[18:31] <philsf> jtaylor, oh, ok. thanks anyway
[18:44] <EvilResistance> by default, if i have a debian/patches/ folder, will the package building systems automatically apply those patches?
[18:44] <jtaylor> if its a 3.0 (quilt) package yes
[18:46] <EvilResistance> and where can i determine if its a quilt package?
[18:47] <jtaylor> debian/source/format
[19:29] <philsf> jtaylor, fwiw, I found out this is caused by a bug in dh-make-perl in the oneiric version. the version in debian testing 0.74-1 fixes it. btw, thanks for the pointers
[19:31] <EvilResistance> jtaylor:  i forgot to say thanks :P
[19:35] <l3on> cjwatson, around ? I'm looking at shogun that FTBFS ...
[19:35] <l3on> full log is here → http://debomatic.debian.net/precise/pool/shogun_1.1.0-1ubuntu1/shogun_1.1.0-1ubuntu1.buildlog (16 MB)
[19:36] <l3on> a snippet of build fail is here: http://paste.ubuntu.com/799742/
[19:36] <l3on> the problem is in configure...
[19:36] <jtaylor> didn't we already have this?
[19:36] <l3on> that generates these variables:
[19:36] <l3on> LINKFLAGS_STATIC_INTERFACES =  -L../../shogun -lshogun
[19:37] <l3on> LINKFLAGS_MODULAR_INTERFACES=  -L../../shogun -lshogun
[19:37] <l3on> LINKFLAGS_RUBY   = -lruby1.8 -fPIC -shared -ldl
[19:37] <l3on> LINKFLAGS_RUBY_MODULAR  = -lruby1.8 -fPIC -shared -ldl
[19:37] <l3on> ok, ruby1.8 is my test
[19:37] <jtaylor> cmake?
[19:37] <tumbleweed> there are .0 files after -lruby-1.9.1
[19:38] <tumbleweed> .o
[19:38] <l3on> tumbleweed, I see
[19:38] <tumbleweed> oh, that's clag, not g++. Don't know how strict that is
[19:38] <l3on> jtaylor, no cflag
[19:38] <l3on> that variables should be POSTFLAGS
[19:38] <jtaylor> what buildsystem?
[19:38] <jtaylor> linkflags looks like cmake
[19:38] <l3on> debomatic
[19:39] <tumbleweed> l3on: that's not what jtaylor meant :)
[19:39] <l3on> lol :D
[19:39] <l3on> I'm new here, so pay patience :D
[19:39] <l3on> anyway, I'm trying to patch configure, using that variables as POSTFLAGS
[19:39] <l3on> do you think is the right way ?
[19:40] <jtaylor> Makefile.template looks like the right place
[19:40] <jtaylor> tumbleweed: can this changelog cause problems when syncing? http://anonscm.debian.org/gitweb/?p=pkg-java/libhibernate-jbosscache-java.git;a=blob;f=debian/changelog;h=e208d0e4c525f0027eef470d515ddc09288cfb45;hb=HEAD
[19:41] <l3on> jtaylor, mmm but I didn't see the answer there
[19:41] <jtaylor> the versions are unordered
[19:42] <ScottK> jtaylor: Isn't the Debian version number lower than the Ubuntu one.
[19:42] <tumbleweed> yes, it is
[19:42] <tumbleweed> jtaylor: you'll need to bump the debian version number
[19:42] <tumbleweed> do a manual sync
[19:43] <jtaylor> ubuntu does not have that version in there
[19:43] <tumbleweed> oh, so it's just a b0rked changelog?
[19:43] <tumbleweed> then we're fine
[19:43] <jtaylor> yes
[19:43] <tumbleweed> still, file a WTF bug in debian :)
[19:44] <jtaylor> can you fix published changelogs?
[19:44]  * tumbleweed fixes bugs in old changelog entries
[19:44] <tumbleweed> but normally whitespace
[19:44] <tumbleweed> yeah you don't want to make big changes
[19:45] <tumbleweed> I suppose it has to be left as is
[19:46] <l3on> ah ok, I see maybe the problem in Makefile.template
[19:46] <l3on> see what's happen with last patch and, in case, patch Makefile.teplate
[19:47] <l3on> thanks for help :)
[19:47] <jtaylor> its a weird build system
[20:20] <l3on> guys is it correct:
[20:20] <l3on> X-Python-Version: >= 2.5
[20:20] <l3on> is I use dh_python2 ?
[20:20] <l3on> (and is it right for ubuntu ?)
[20:21] <jtaylor> yes
[20:21] <l3on> ah ok :)
[20:21] <l3on> thanks.
[20:22] <l3on> so jtaylor ... this change can be dropped:
[20:22] <l3on> -XS-Python-Version: 2.6
[20:22] <l3on> +XS-Python-Version: 2.7
[20:23] <l3on> if debian has set:
[20:23] <l3on> X-Python-Version: >= 2.5
[20:23] <jtaylor> debian converted to dh_python2 ?
[20:23] <jtaylor> which package?
[20:24] <EvilResistance> i take it that I can't get a PPA build bumped up in priority after its submitted?  I'm trying to release an updated version that patches out a vulnerability in the package, and its leaving me with a 20 hour wait time to build
[20:24] <l3on> always shogun, and yes, it use dh_python2 it's strange
[20:24] <l3on> s/it's strange//
[20:27] <jtaylor> you can drop the XS-Py-V
[20:27] <l3on> ok, thanks :)
[20:28] <jtaylor> did you see that package already has an as-needed patch in ubuntu?
[20:37] <l3on> jtaylor, yes I saw... but it does not work...
[20:37] <l3on> but it's the same way I patched configure
[21:41] <philsf> I just reported a bug in dh-make-perl (LP: #914479), that has a patch available in debian. can someone please review it and see if I need to provide anymore information?
[21:45] <Laney> philsf: Are you trying to get this fixed in Oneiric? If so, it would be good if you could make a debdiff that can be sponsored.
[21:46] <philsf> Laney, I don't have experience in packaging, so a debdiff is a little out of my league for now. Is there anything else I could do?
[21:47] <tumbleweed> whould you like to get some experience? :)
[21:47] <philsf> tumbleweed, I'm always always interested, but time is very short. is there a quick way for me to do this, or a for dummies tutorial I could read?
[21:49] <tumbleweed> I'll happily walk you through a first debdiff. There's lots of documentation, but nothing short adnd to the point for this
[21:50] <philsf> tumbleweed, if you think this bug applies for an SRU request, I'm game.
[21:52] <tumbleweed> the patch is pretty trivial, so it should be easy enough
[21:52] <tumbleweed> the apt-file issue is another bug and should be dealt with separately
[21:53] <philsf> ok
[21:54] <philsf> so, I never made a debdiff or prepared a patch, but I know how to get a source and compile a .deb.
[21:54] <tumbleweed> so, first, this bug is already fixed in precise (where 0.74 is published https://launchpad.net/ubuntu/+source/dh-make-perl ), so you can mark it fix released, and nominate the bug for oneiric
[21:56] <philsf> hmm, so this means it's also broken in precise, for the reason of the other bug (that should have been reported separately). is this correct?
[21:56] <EvilResistance> tumbleweed:  if i have a fork of a package, but its not hugely different from the package that exists in Debian or Ubuntu, is there an *easy* way to merge package version changes into the fork?
[21:56] <tumbleweed> philsf: it's broken for a different reason in precise, with different symptoms, right?
[21:56] <tumbleweed> I'd just edit those bits out of this bug
[21:57] <philsf> tumbleweed, right. should I then report another one, and link to the apt-file bug (later)?
[21:57] <tumbleweed> yeah
[21:58] <tumbleweed> EvilResistance: depends on how you forked it. VCS are handy for this kind of thing.
[21:59] <EvilResistance> tumbleweed:  just changed what the core install actually includes (i.e. the debian/<binary>.install for a single multi-binary source package, whereas the rest of the code and what not remains the same)
[21:59] <philsf> tumbleweed, how can I nominate for oneiric?
[21:59] <tumbleweed> philsf: do you get a "Nominate for series" button below the yellow bar? (I can't remember if everyone sees that these days)
[22:00] <philsf> tumbleweed, no. only "also affects project" and "... distribution"
[22:01] <tumbleweed> meh, ok, you have to ask for nominations on IRC then
[22:01] <Laney> I think it got taken away
[22:01]  * tumbleweed 'll do it now
[22:01] <tumbleweed> Laney: what does one have to do to be able to nominate then? join bugcontrol?
[22:02] <tumbleweed> philsf: right, so a debdiff is just a patch that'll apply to a source package
[22:02] <Laney> pretty sure you have to be a bug supervisor, yes
[22:02] <tumbleweed> start by grabbing the source: pull-debian-source dh-make-perl oneiric
[22:03] <tumbleweed> yeah, people used to abuse nominations a lot. I'm sure I did too, when I was a user who didn't know what it was for
[22:04]  * philsf may also be guilty of that
[22:06] <philsf> Error: Failed to download: dsc could not be found anywhere
[22:06] <Laney> pull-lp-source ;-)
[22:06] <tumbleweed> true, :)
[22:07] <philsf> lol, ok done
[22:08] <tumbleweed> right, now apply the patch you have, but throw away its changelog entry, and write your own (with dch -i)
[22:08] <philsf> should I edit the changelog out of the patch before applying?
[22:08] <tumbleweed> you could also do that
[22:09] <tumbleweed> it should target oneiric-proposed as the distribution
[22:09] <tumbleweed> and the version number should be smaller than the one in precise and bigger than the one in oneiric. We recommend 0.73-1ubuntu0.1
[22:10] <tumbleweed> (see https://wiki.ubuntu.com/StableReleaseUpdates  for all the details)
[22:10] <philsf> ok, changed version and target in changelog, nothing else so far. wil try patching now
[22:11] <tumbleweed> "dch -e" should let you edit it, and substitute your name and e-mail address in
[22:11] <philsf> oh, that's better
[22:12] <tumbleweed> the changelog entry should close the LP bug
[22:13] <tumbleweed> (the syntax is LP: #XXXX)
[22:18] <philsf> ok, not a very creative changelog, but I guess it works
[22:18] <philsf> patched, and changelog created for new version
[22:18] <philsf> what now?
[22:19] <tumbleweed> debuild -uc -us -S
[22:19] <tumbleweed> cd ..
[22:19] <tumbleweed> debdiff old.dsc new.dsc > debdiff
[22:19] <tumbleweed> review the diff, attach to the bug
[22:20] <tumbleweed> (oh, and building a deb and testing it is probably not a bad idea)
[22:21] <EvilResistance> that last statement there is definitely true
[22:21] <philsf> ok, will build
[22:21] <philsf> dpkg-buildpackage -b -uc -us?
[22:22] <tumbleweed> that'l lwork
[22:22] <tumbleweed> we tend to use clean environments (pbuilder / sbuild) for most building, but there's nothing wrong with a quick-and-dirty build for testing something like this
[22:22] <philsf> unmet deps. :(
[22:23] <tumbleweed> ah, that's another place where build systems help
[22:23] <philsf> so, how do I do this properly?
[22:23] <philsf> should I apt-get build-dep ?
[22:23] <tumbleweed> you want to set up a pbuilder?
[22:24] <jtaylor> I recommend mk-build-deps -r -i, easier to remove them all again
[22:24] <tumbleweed> +1 to mk-build-deps over apt-get source
[22:25] <philsf> do I run it inside the source dir, or where the .dsc is?
[22:25] <tumbleweed> in the source dir
[22:26] <philsf> ok, build deps installed, and package building (in test phase)
[22:30] <philsf> dh_auto_test: perl Build test returned exit code 255
[22:31] <tumbleweed> yay
[22:32] <philsf> did I patch it wrongly? I entered the source dir and patch -p1 < ../patch
[22:32] <philsf> but before I tried without -p1, wonder if it matters
[22:35] <tumbleweed> just busy replicating it here
[22:37] <philsf> ok, brb in 5min
[22:37] <tumbleweed> hrm, this test seems to be hammering the internet. Naughty test
[22:39] <tumbleweed> philsf: I see test failures at "t/dists.t line 82."
[22:43] <Laney> there are fixes to that file in git
[22:43] <tumbleweed> ah, thanks laney. I got sidetracked in another #
[22:44] <philsf> so, what should I do now? does this complicate the patch?
[22:44] <philsf> after that error, I'm retrying the build and t/cache.t is taking forever.
[22:44] <Laney> it seems like the test suite had bugs
[22:45] <Laney> you probably need the last change on http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/dh-make-perl.git;a=history;f=t/dists.t;h=f13e477a52ec0158b2f8bdcfb0cebd7a765beabc;hb=HEAD
[22:45] <Laney> and possibly other ones too
[22:45] <philsf> oh boy...
[22:46] <Laney> hey, at least the problem has (probably) already been fixed for you :P
[22:47] <philsf> lol. I thought it would be a simple patch-and-conquer. :/
[22:47] <tumbleweed> the simple-looking ones always turn out harder than they look :)
[22:48] <philsf> this last diff seems larger than the original patch
[22:48] <tumbleweed> well, the origional patch was 4 characters + a test :)
[22:50] <philsf> but AIUI the samller the patch, the better the chances it will be accepted for SRU
[22:51] <philsf> for my purposes, downgrading to the natty version works around the bug
[22:52] <tumbleweed> I don' tsee that being an issue here
[22:53] <philsf> but we also can't be sure this other diff will be enough, and it's already kind of late for me here
[22:53] <philsf> thanks for your time, but I think I'll get back to this tomorrow (maybe)
[22:53] <tumbleweed> philsf: sure, night
[22:54] <philsf> tumbleweed, thanks again. and sorry for your time
[22:54] <tumbleweed> np
[23:11] <l3on> finally shogun built fine !
[23:37] <cjwatson> jtaylor,Ampelbein: I'm afraid you read the d-i internals docs wrongly a few days back.  udebs must not depend on non-udebs, and vice versa.  Doing so will fail.
[23:41] <cjwatson> jtaylor,Ampelbein: udebs may Build-Depend on debs, though (in fact, they may *only* Build-Depend on debs)