[00:15] <quidnunc> How do I sanity check which disto and components pdebuild is using?
[00:16] <jtaylor> I have added a echo to my rc
[00:16] <quidnunc> .pbuilderrc?
[00:17] <quidnunc> okay that works, thanks
[00:18] <quidnunc> Why is haskell-devscripts reported as not installable when running pdebuild?
[00:19] <quidnunc> COMPONENTS="main restricted universe multiverse"; DIST=oneiric
[00:20] <jtaylor> is universe in the sources.list?
[00:20] <quidnunc> jtaylor: Doesn't COMPONENTS take care of that?
[00:20] <jtaylor> COMPONENTS only has effect on create and update
[00:21] <quidnunc> jtaylor: "sudo -E DIST=oneiric pbuilder login" shows it. But how do I ensure that is the same env that pdebuild is using?
[00:21] <jtaylor> can you install it when logged in?
[00:23] <quidnunc> it seems to be installing...
[00:26] <jtaylor> gotta go, bye
[00:26] <quidnunc> jtaylor: Okay installed haskell-devscripts when logged-in but pdebuild still fails with "dependency not satisfiable"
[00:31] <quidnunc> The installation should persist right?
[00:57] <quidnunc> Is there no debugging options in pdebuild?
[00:57] <quidnunc> s/Is/Are
[00:58] <ajmitch> quidnunc: what do you mean by debugging options? you can use hook scripts to perform actions at certain times, like when a build fails
[00:59] <quidnunc> ajmitch: I have a dependency that is not satisfiable and I can't determine why. Is there anyway those hooks could help me?
[01:01] <ajmitch> you cna get a shell inside the chroot when the build fails
[01:01] <ajmitch> that may be helpful, perhaps
[01:01] <ajmitch> https://wiki.ubuntu.com/PbuilderHowto#Running_a_Shell_When_Build_Fails_.28Intro_to_Hook_Scripts.29 has info on that
[01:02] <quidnunc> ajmitch: Thanks
[01:22] <quidnunc> ajmitch: Okay, doesn't seem to be working :(
[01:22] <quidnunc> Does it get invoked from pdebuild?
[01:22] <ajmitch> should do, make sure the hook is executable though
[01:24] <quidnunc> ajmitch: Yeah, it's +x
[01:24] <quidnunc> a+x
[01:25] <ajmitch> hook is in the right place referenced by the pbuilderrc file?
[01:25] <ajmitch> and is named properly?
[01:25] <quidnunc>  /var/cache/pbuilder/hook.d/C10shell
[01:25] <quidnunc> HOOKDIR="/var/cache/pbuilder/hook.d"
[01:25] <quidnunc> ajmitch: I remember reading something about re-reading .pbuilderrc
[01:25] <quidnunc> ...
[01:26] <quidnunc> Is it cached?
[01:26]  * ajmitch wonders if build fail scripts aren't called when the build depends aren't men
[01:26] <ajmitch> s/men/met/
[01:26] <ajmitch> shouldn't be cached
[01:29] <ajmitch> quidnunc: ok, rename C10shell to D10shell
[01:30] <ajmitch> D hooks are called just before unpacking the source, A hooks are called after trying to install build depends
[01:30] <quidnunc> ajmitch: that works
[01:31] <ajmitch> ok
[01:34] <quidnunc> ajmitch: apt-cache policy is showing a version from hardy.
[01:34] <quidnunc> (and no other options)
[01:35] <quidnunc> How do I determine which dist I am in?
[01:35] <ajmitch> pastebin /etc/apt/sources.list from there
[01:35] <quidnunc> ajmitch: Okay, it lists hardy but why?
[01:36] <quidnunc> I have DIST=oneiric in my .pbuilderrc
[01:36] <ajmitch> & did you create a new base tarball?
[01:36] <quidnunc> ajmitch: I believe so. I guess I will try again
[01:37] <quidnunc> ajmitch: Is this correct? "pbuilder-dist oneiric create"
[01:37]  * ajmitch has a slightly non-standard pbuilder setup & doesn't use pbuilder-dist
[01:37] <ajmitch> but I believe that'll work
[01:37] <quidnunc> Okay, but should that work?
[01:38] <ajmitch> try it & see?
[01:38] <quidnunc> Or what is another command that will do the equivalent?
[01:38] <quidnunc> ajmitch: Long process :)
[01:38] <ajmitch> I do things the old-fashioned way, separate pbuilderrc file per release, and separate named tarball
[01:40]  * ajmitch doesn't know for sure how pdebuild interacts with pbuilder-dist
[01:41] <quidnunc> "pbuilder create" it is
[01:42] <quidnunc> ajmitch: Do the D<name> scripts always run?
[01:45] <ajmitch> yes
[01:47] <pabelanger> Evening!  I know it's late in the game however I just created a feature freeze exception sync request (bug 947646).  Does anybody mind commenting on it, confirming all the required information is there?
[02:02] <ScottK> pabelanger: Easy enough.  Approved.
[02:05] <ScottK> pabelanger: Done.
[02:09] <pabelanger> ScottK: Great!  Thanks
[02:13] <ScottK> pabelanger: binary built and accepted too.
[02:13] <pabelanger> Nice, thanks again for the turn around on it
[02:14] <ScottK> No problem.  Your timing was good that there was someone that could approve it hanging around.
[02:16] <pabelanger> indeed
[03:49] <Corey> For those of you using Jenkins to build debs (for staging, then eventually to prod), how do you get the deb that Jenkins spits out into a dpkg repository?
[03:58] <RAOF> You mean an apt repository?
[03:59] <Corey> Er, yes. :-)
[03:59] <RAOF> apt-ftparchive is what I use for my build-against-local-packages sbuilder.
[03:59] <Corey> I get the idea of "rsync it to the repository server," but I'm still a bit hazy on "add it to the repository."
[03:59] <RAOF> Specifcally: “apt-ftparchive packages . > Packages” to create a Packages file from all the .debs in the current directory.
[04:00] <Corey> Ahhh.
[04:00] <Corey> RAOF: That makes sense. Thanks!
[04:08] <ESphynx> hey guys... things are not working :| i'm trying to install my 32 bit package on Precise 64, and I get: ecere-sdk:i386 : Depends: ecere-doc:i386 but it is not installable
[04:08] <ESphynx> and 2 others... these 3 packages have 'any'
[04:13] <ESphynx> sorry, they have Architecture: all
[04:13] <ESphynx> should it be 'any' ?
[06:10] <vibhav> Hello MOTUs, I have uploaded indicator-sensors at  http://revu.ubuntuwire.com/p/indicator-sensors can somebody review it?
[06:23] <sladen> vibhav: ooh, indicators
[06:24] <vibhav> heh
[06:27] <sladen> eww CDBS
[06:27] <sladen> vibhav: Source: <url://example.com>
[06:27] <sladen> vibhav: in debian/copyright
[06:29] <vibhav> oh no
[06:29] <vibhav> thanks sladen
[06:29] <sladen> vibhav: CDBS could be dropped by replacing '/debian/rules' with   %:
[06:29] <sladen>         dh $@
[06:33] <vibhav> sladen: Is it important to replace cdbs
[06:34] <sladen> vibhav: it's not a fail, but pretty much deprecated
[06:37] <vibhav> sladen: I recieved the rules from the package developer
[06:37] <vibhav> I wonder removing it might do some harm
[06:37] <EvilResistance> o.O CDBS IS EVIL!
[06:37] <EvilResistance> sorry, but i agree with sladen on that xD
[06:39] <vibhav> EvilResistance: wonder removing it might do some harm
[06:40] <vibhav> ?
[06:40] <EvilResistance> dunno, i'm just agreeeing with sladen is all :P
[06:41]  * EvilResistance is off
[06:42] <sladen> vibhav: I've commented on Revu.  Off to Millbank; I'll have another look when I arrive
[06:44] <vibhav> thanks sladen
[06:44] <sladen> vibhav: harm?  Oh, no no.  You've be helping save the planet :)
[06:44] <vibhav> Then Illl replace CDBS
[07:48] <vibhav> Can anybody tell me how do I package a program without a "./configure" ?
[07:50] <RAOF> That depends on the program; how do you build it?  How do you install it?  How do you tell it where to install, etc.
[07:53] <vibhav> The program has an "autogen.sh"
[07:54] <dholbach> good morning
[07:54] <RAOF> Oh.  Then you just run that to generate the configure script, and proceed as normal.
[07:54] <RAOF> dh_autoreconf will do that for you, too.
[08:02] <vibhav> dholbach: Good Morning
[08:02] <dholbach> hi vibhav
[08:04] <vibhav> Anybody knows why my .orig.tar.gz is not getting included in the source.changes file?
[08:04] <vibhav> I uploaded it to REVU
[08:04] <vibhav> And the orig.tar.gz was missing
[08:04] <broder> vibhav: it won't get included by default if it doesn't look like this is the first package for that upstream
[08:04] <broder> based on the version numer
[08:04] <broder> so if your version is -2 or -2ubuntu3 or something
[08:05] <broder> but you can override it by passing -sa to debuild
[08:05] <broder> or -- -sa to bzr bd
[08:06] <vibhav> broder: -sa did the trick, thanks :)
[08:07] <broder> np
[08:10] <vibhav> http://revu.ubuntuwire.com/p/indicator-sensors, can somebody review it?
[08:11] <vibhav> I have replaced cdbs
[08:33] <sladen> vibhav: strange, I'm not seeing your latest uploads.  Though I can sort-of-see a reversed(?) diff as the debdiff
[08:33] <sladen> vibhav: I wonder if revu has simply bitrotted in the meantime
[08:35] <vibhav> sladen: I can see my latest uploads
[08:36] <vibhav> sladen: try http://revu.ubuntuwire.com/details.py?upid=9402
[08:37] <sladen> ah, something changed.  I can see the .debian.tar.gz
[08:37] <sladen> instead of the .diff
[08:37] <sladen> will look in a few minutes again
[08:38] <vibhav> sladen: I uploaded the .orig.tar.gz too
[08:38] <sladen> woo
[08:38] <sladen> guess it was just revu catching up
[08:39] <vibhav> sladen: Can you see the latest uploads
[08:39] <vibhav> REVU processes uploads in 5 minutes
[08:58] <sladen> vibhav: does indicator-sensor actually have numbered releases.  Or is it just a pull of the bzr branch at a particular time/date?
[09:00] <sladen> vibhav: drop the cdbs dependency now it's not being used
[09:01] <sladen> vibhav: stick the closing ')' on the previous line
[09:02] <sladen> vibhav: drop the cdbs dependency now it's not being used
[09:02] <sladen> vibhav: stick the closing ')' on the previous line
[09:03] <sladen> vibhav: out-of-date-standards-version 3.9.1 (current is 3.9.3)
[09:06] <sladen> vibhav: two build-time generated files included in the diff:  config.log  po/POTFILES  which shouldn't be there
[09:06] <sladen> vibhav: clean them out before running   'debian -S'
[09:12] <vibhav> sladen: Anything more?
[09:13] <sladen> vibhav: not that I've spotted so far
[09:13] <vibhav> sladen: lintian returns W: indicator-sensors source: newer-standards-version 3.9.3 (current is 3.9.2)
[09:13] <vibhav> and indicator-sensors source: unused-build-dependency-on-cdbs
[09:14] <sladen> vibhav: debian/control    remove 'cdbs' from the Build Depends line
[09:15] <jalcine> Isn't cdbs phasing out?
[09:22] <sladen> jalcine: yes!  vibhav has already nuked it from the packaging, but it's still listed in the depends
[09:23] <jalcine> Hmm.
[09:32] <jokerdino> didrocks: you made a little mistake, dear friend. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/938748
[09:33] <didrocks> jokerdino: what mistake?
[09:33] <didrocks> hey :)
[09:33] <jokerdino> you sure you didn't make a mistake? ;)
[09:34] <didrocks> jokerdino: can you please explain? I don't really have the time to play a game now :)
[09:34] <jokerdino> heh, i see. it was me who submitted the patch.
[09:34] <jokerdino> not that i am angry or something, i probably made a mistake myself
[09:35] <didrocks> jokerdino: oh you're totally right
[09:35] <didrocks> jokerdino: sorry for that, wasn't intended :)
[09:35] <jokerdino> nah, i don't mind much.
[09:35] <didrocks> was king of sketchy because you aren't the one submitting upstream rigth?
[09:35] <didrocks> right*
[09:35] <jokerdino> nope not me. someone else took over the upstream part.
[09:36] <didrocks> 3 people on a bug report was a little bit etoomuch for my brain :)
[09:36] <jokerdino> I think it was Nathan.
[09:36] <didrocks> right
[09:36] <didrocks> jokerdino: thanks again for your work here and sorry for the wrong attribution ;)
[09:36] <didrocks> (I had to retake the upstream patch in fact and separate it in two commits
[09:36] <jokerdino> like i said, i made a mistake as well.
[09:37] <jokerdino> anyway, thanks for accepting the patch!
[09:37] <jokerdino> i am just glad i contributed :D
[09:38] <didrocks> jokerdino: thanks for doing it! :-)
[09:38] <didrocks> jokerdino: there are as well a lot of othe quicklist for defaults apps or keyword to be added! :)
[09:38] <didrocks> jokerdino: btw, you can as well propose a branch (most of the time against lp:~ubuntu-desktop/<projet>/ubuntu
[09:38] <jokerdino> true that, but my main focus is translating. \.
[09:38] <didrocks> and add a changelog (see the packaging guide) to ensure to have your name in it :)
[09:39] <didrocks> jokerdino: as well, submitting translations for those quicklists/keywords is a nice way as well :)
[09:39] <didrocks> thanks again for your contribution and again, sorry for the attribution mistake!
[09:40] <jokerdino> well, i think we should move on. you apologised way too many times.
[09:41] <jokerdino> oh and will surely add an entry in the changelog next time
[09:41] <didrocks> yeah, that will avoid it :)
[09:42] <jokerdino> and regarding proposing a branch, my network blocks ssh.
[09:42] <jokerdino> so, i can only attach a patch.
[09:43] <jokerdino> anyway, that is irrelevant.
[09:44] <didrocks> ah ok :/
[09:44] <didrocks> yeah, patch is fine
[09:44] <vibhav> sladen: Should I remove POTFILES.in too?
[09:46] <jokerdino> great, let's carry on with our stuff
[09:49] <sladen> vibhav: no
[09:49] <sladen> vibhav: that's the input file that gets converted to 'POTFILES' during the build
[10:03] <sladen> vibhav: poke
[10:03] <sladen> vibhav: (I'll keep checking back, in between gaps)
[10:29] <jalcine> Do you need SSL access to upload packages to a PPA?
[10:29] <jalcine> My connection blocks that, but I have my system ready to dput stuff.
[11:53] <geser> jalcine: no, dput uses ftp by default
[11:53] <jalcine> Also, when is the pocketsphinx source package going to be updated?
[11:54] <jalcine> It has a released version of 0.6.1 but the repositories show that the latest is 0.5.1+dfsg1-0ubuntu2
[11:54] <jalcine> thanks geser
[11:55] <jalcine> If that's updated, then sphinxbase ought to be updated as well.
[11:55]  * jalcine wonders who exactly maintains those packages.
[11:57] <geser> jalcine: as pocketsphinx got never touched again after the initial upload (ignoring a rebuild), probably nobody will update it (unless someone from the community steps up)
[11:58]  * jalcine sees an opporunity.
[11:58] <geser> packages in the universe component are "maintained" by the community (or directly taken from Debian)
[12:00] <geser> community = everyone can update it (but it usually respected if persons have a interest in specific packages so work gets coordinated with them)
[12:01] <geser> so feel free to update it (but I'm not sure if it will get into precise due to Feature Freeze)
[12:01] <jalcine> I use those packages heavily in an application I'm working on.
[12:01] <jalcine> And I'm in touch with upstream.
[12:01] <jalcine> I'll see if I can begin such an update.
[12:03] <jalcine> Thanks for your help geser
[12:18]  * jalcine enters back.
[12:40]  * Rhonda . o O ( updated the patches in bug #932011 for the latest upload )
[12:48] <vibhav> Can somebody review my package at http://revu.ubuntuwire.com/p/indicator-sensors ?
[13:14] <jalcine> Let's say you've download source packages and made updates to them.
[13:14] <jalcine> How do you get them uploaded back to the repositories?
[13:14] <jalcine> As a patch?
[13:16] <dholbach> jalcine, updates as in "update to a new upstream version"?
[13:17] <jalcine> That, for one, and the other kind of updates, like updates to packaging info.
[13:18] <dholbach> you could upload it to a PPA and then link to it in bug report where you subscribe the 'ubuntu-sponsors' team
[13:18] <jalcine> The package itself or the entire PPA?
[13:19] <dholbach> the package itself
[13:19] <jalcine> Alrighty, thanks.
[13:19] <jalcine> Lol, this stuff's more fun than I though.
[13:19] <jalcine> *thought
[13:20] <vibhav> Can somebody review my package at http://revu.ubuntuwire.com/p/indicator-sensors ?
[13:22] <jalcine> Is that process of linking and merging PPAs repeated each time there's an update to the software?
[13:39] <Laney> Rhonda: if you say you've tested it builds/installs/runs then I can approve
[13:48] <geser> JackyAlcine_: what you mean with "linking and merging PPAs"?
[13:54] <jalcine> geser: Opening a bug and making a link to the PPA.
[13:55] <tumbleweed> jalcine_: we don't usually use PPAs for sponsorship. debdiffs / bzr branches are preferred
[13:55] <tumbleweed> !sponsorship
[13:55] <jalcine_> ah, no problem.
[13:56] <dholbach> tumbleweed, jalcine_ asked because of an update to a new upstream version + fixes - I thought it'd be an easy solution to just give a link to a package in a ppa
[13:56] <dholbach> but sure, a branch also works
[13:57] <tumbleweed> yeah, PPAs work better for that than debdiffs
[13:58] <tumbleweed> the downside with PPAs for sponsorship is that a second round of review requires a bumped version, so the sponsor ends up with some changelog editing
[13:59] <jalcine_> Hmm.
[14:00] <tumbleweed> jalcine_: you just need a way to share the source package with the sponsor. Anything that works for you is fine
[14:00] <jalcine_> Alrighty.
[14:00] <jalcine_> Thanks all.
[14:00] <jalcine_> and dholbach, Silverlion says hello :)
[14:45] <tumbleweed> l3on: you were asknig for an NMU the other day. Did you find a sponsor?
[14:45] <l3on> tumbleweed, I'm not sure.. package is flowscan
[14:46] <l3on> I'm a little bit busy in these days with the ubuntu-it community, so I don't have enough time to follow devel as well...
[14:46] <l3on> :/
[14:48] <tumbleweed> l3on: debian bug 660044, I assume
[14:48] <l3on> tumbleweed, yes! :)
[14:49] <tumbleweed> seems reasonable
[17:10] <vibhav> Is any MOTU available here?
[17:23] <broder> EvilResistance: why did you file bug #948117 as a backport and not an sru?
[17:33] <Rhonda> Laney: right, I asked about testers: http://identi.ca/notice/91596187 http://twitter.com/lalobee/status/177012344239570944  :)
[17:42] <broder> micahg: wait, is fix committed the new in progress for backports?
[17:43] <broder> did anybody fix backport-helper to pick that up?
[17:43] <micahg> broder: oops, you're right, E_NOTENOUGHCAFFEINE :)
[17:43] <broder> heh. really, i wouldn't mind seeing us switch to triaged since we have a little more control over who uses that
[17:44] <broder> but meh. don't care enough to push on it
[17:51] <Laney> Rhonda: ack (you can confirm builds, installs though, even with a chroot)
[17:53] <Rhonda> Theoretically yes, but that would require disk space and setting up the chroots. :)
[17:53] <Rhonda> Not that I don't have that on some remote servers.
[18:13] <EvilResistance> broder, i was unaware of SRUs
[18:14] <EvilResistance> broder, see response on the bug, there's no one patch i can create to isolate the thing, short of an upgrade to the package itself with the latest debian-packaged version (3.2.1, as in Precise)
[18:15] <jtaylor> n
[18:15] <EvilResistance> the fix was done at the source code level, and there was a bunch of other source-level diffs that went along with the upstream revision
[18:15] <EvilResistance> s/revision/release/
[18:18] <EvilResistance> or short of having the Debian maintainer publish the latest upstream source for Debian, and then have that synced into Precise and Oneiric (which is extraordinarily irregular)
[18:20] <broder> EvilResistance: when we can, we want to be surgical with our patches post-release so that we can avoid regressing things. normally i would advocate looking through the diff between the releases and finding the relevant portions of the patch. in this case, though, i think all of the changes are important, so we can sru the entire release into oneiric
[18:21] <broder> it's basically like a backport, but it's actually an sru
[18:22] <broder> EvilResistance: actually, i should have done this earlier, but i'm going to completely close bug #948117 and instead we can track the sru in bug #884619
[18:23] <EvilResistance> broder, then in this case i'll have to rework the package in Oneiric now, apply the upstream code release that's in Oneiric, and then upload that package to <unidentifiedDestinationAddress>
[18:24] <broder> did you mean to use oneiric twice?
[18:24] <EvilResistance> nope, the second was supposed to be "Precise"
[18:25]  * EvilResistance has been staring at assembly code the past few hours dissecting why his router exploded
[18:25] <broder> ok, right
[18:25] <broder> you could do that, but if i was preparing this, i would start with the precise package, and just add a new changelog entry targeting oneiric-proposed
[18:25] <EvilResistance> i could do that
[18:25] <broder> something like 3.2.1-1~oneiric0.1
[18:26] <EvilResistance> ok, i've got to head out for a meeting, i'll be back  later, where do i then upload that package to?
[18:26] <EvilResistance> revu?
[18:26] <broder> EvilResistance: create a debdiff between 3.2.1-1 and 3.2.1-1~oneiric0.1 and attach that to bug #884619
[18:27] <broder> but i may just do it and upload, since there aren't any changes required other than the changelog
[18:27] <broder> EvilResistance: however, it will still be your responsibility to writeup those 5 points on the bug
[18:33] <broder> somebody really needs to tell these guys about asprintf or something, though
[18:33] <broder> their fix for the log name bug is pretty terrible
[18:35] <nigelb> x/ws 64
[18:35] <nigelb> grar
[18:45] <jtaylor> can I uplaod to -security?
[18:45] <jtaylor> or do I need sponsor for that?
[18:45] <jtaylor> (universe package)
[18:47] <Ampelbein> jtaylor: for -security you'd need a sponsor from the security team.
[18:47] <jdstrand> jtaylor: it needs to be sponsored. see https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures#Preparing_an_update
[18:47] <jtaylor> thx
[20:08] <EvilResistance> broder: does this work?  https://bugs.launchpad.net/ubuntu/+source/egenix-mx-base/+bug/884619/comments/3
[20:08] <EvilResistance> (it should it addresses all 5 points as outlined in the SRU procedure)
[20:09] <broder> EvilResistance: (a) we're not updating to 3.2.1 because finding the patch is time consuming; we're updating because all of the changes fix bugs in the code, (b) in the future put the writeup in the bug description, not a comment
[20:09] <broder> i'll post a followup comment to address (a)
[20:10] <EvilResistance> broder: the edit for the description didnt show up for me :/
[20:10] <EvilResistance> i couldnt post in the description, because the edit button didnt show up
[20:10] <EvilResistance> therefore, the comment was the only way to post the information (per the edit button not appearing)
[20:10] <broder> ok
[21:55] <aboudreault> why after a dpatch-edit-patch... my patches in 00list are not applied?
[21:56] <aboudreault> I want to create a new patch that need to be applied after other patches.
[21:57] <ScottK> aboudreault: Do dpatch-edit-patch new-patch last-patch-in-00list
[21:57] <ScottK> You have to tell it that.
[21:57] <aboudreault> ha... there is a -a option
[21:57] <aboudreault> sorry, had completly forgotten this. I normally use quilt. thanks
[22:00] <aboudreault> ScottK, well... do I have to do anything else or exit 0 should work?
[22:01] <aboudreault> the created patch is huge and contains all other patches
[22:01] <ScottK> exit 0 should work.
[22:01] <ScottK> It's been awhile since I had to use it.
[22:04] <aboudreault> will fix it manually...