[01:14] <TheLordOfTime> whats the name for the metapackage that installs all the packaging related tools?
[09:01] <Laney> TheLordOfTime: I guess you mean packaging-dev
[14:12] <PriceChild> !ops
[14:13] <PriceChild> !ops
[14:15] <IdleOne> PriceChild: ?
[14:16] <PriceChild> what up my homey
[14:16] <IdleOne> why did you call for ops?
[14:16] <PriceChild> to be banned
[14:16] <PriceChild> !ops
[14:16] <PriceChild> kline me
[14:16]  * tumbleweed has no idea why anyone would want to be banned
[14:17] <PriceChild> i do! i get high easily
[14:17] <tumbleweed> I suppose we al have odd persuits...
[14:18] <IdleOne> Pricey: if you could remove your troll self :)
[14:18] <PriceChild> yay the real pricechild is here to kline me!
[14:18] <PriceChild> ban me
[14:18] <PriceChild> i want to get high!
[14:18] <PriceChild> ban me
[14:18] <IdleOne> impersonating a channel op and staff member to boot, good idea.
[14:18] <PriceChild> i am a mental retard by the way
[14:19] <tumbleweed> ah, normality
[14:39] <PaoloRotolo> Hi all!
[15:16] <scarneiro> PaoloRotolo: Hi
[15:18] <PaoloRotolo> scarneiro, hi!
[15:47] <TheLordOfTime> can i use Lintian on Ubuntu to check for lintian cleanliness for a Debian-destined package?
[15:52] <jbicha> TheLordOfTime: yes, lintian on Debian and lintian on Ubuntu is basically the same
[15:52] <TheLordOfTime> jbicha:  so i pretty much just need to run Lintian on the package to find whether its lintian clean, and fix any warnings and/or errors that arise?
[15:53] <jbicha> yes, being lintian clean is important :)
[15:54] <TheLordOfTime> definitely
[15:54] <TheLordOfTime> i once had a package that was lintian unclean by only one error, and that error was i forgot to change the standards number xD
[15:55] <TheLordOfTime> and they were like "You're x.x. 1 behind in the standards number, fix it"
[16:02] <tumbleweed> sponsoring is an opportunity to teach, so many of us tend to be pretty pedantic sponsors
[16:02] <TheLordOfTime> indeed
[16:03] <TheLordOfTime> although having said this, the debian people rejected a package even though it was lintian clean because they "Didn't agree with the way the source was run after installation"
[16:03] <TheLordOfTime> so.. i kinda gave up on trying to get packages into Debian (then again, i havent had any need to get anything into Debian lately, so... :P)
[16:04] <tumbleweed> was it totally crazy?
[16:05] <TheLordOfTime> source code without any compiled executable (because the entire thing was 100% python...)
[16:05] <TheLordOfTime> so...
[16:05] <TheLordOfTime> *shurgs*
[16:05] <TheLordOfTime> probably, although its irrelevant now
[16:06] <tumbleweed> did the sponsor have any experience with python?
[16:06] <tumbleweed> every DD has their own requirements and foibles
[16:07] <TheLordOfTime> i know right?
[16:07] <TheLordOfTime> don't know, but idc anymore :P
[16:08] <jbicha> Debian teams are awesome, if you can find a team that would be interested in your package
[16:09] <jbicha> it makes sponsorship easier and reduces the MIA Debian maintainer problem
[16:10] <tumbleweed> team-maintained packages++
[16:12] <TheLordOfTime> ^ that
[16:12] <TheLordOfTime> but i digress :P
[18:42] <AmberJ> Err... this is weird. Upstream compiles fine if I run: 'cmake .' and then 'make'. But if fails on PPA as well as locally (when using debuild).
[18:42] <AmberJ> Here's the PPA buildlog: http://paste.ubuntu.com/1055180/ (please scroll down to line 3883)
[18:42] <AmberJ> I don't understand why the build exits with error when using debuild. It builds fine when using 'make'.
[18:43] <AmberJ> (Timezone repost)
[18:59] <Yankees52> !ops
[18:59] <Yankees52> ban me
[18:59] <Yankees52> ban me
[18:59] <Yankees52> ban me
[18:59] <Yankees52> please!
[19:00] <Yankees52> !staff
[19:00] <Yankees52> !ops
[19:00] <Yankees52> please!
[19:00]  * iulian sighs.
[19:00] <Yankees52> lucas: ban me
[19:00] <Yankees52> yay ban coming!
[19:00] <bazhang> Yankees52, lets stop this
[19:02] <directhex> i'm confused.
[19:07] <james_w> AmberJ, could it be a gcc version difference?
[19:08] <james_w> looking at opencog-0.1/opencog/learning/moses/main/moses_exec.cc:828 might give some clues
[19:11] <AmberJ_> james_w, you mean the build breaking maybe because of using a different version of gcc/g++?
[19:11] <james_w> AmberJ, yeah, possibly
[19:11] <AmberJ_> Unfortunately, I'm unable to understand what is wrong with 828 of http://bazaar.launchpad.net/~opencog-dev/opencog/trunk/view/head:/opencog/learning/moses/main/moses_exec.cc
[19:13] <AmberJ_> james_w, I tried building in the same VM... The build breaks with debuild but works fine when manually using cmake/make. (I guess same VM/install cannot have two different versions of gcc)
[19:13] <james_w> AmberJ, it might be something in the environment then
[19:15] <AmberJ_> Not sure if this is the cause but I noticed something... The debuild build breaks when I manually copy orig.tar.gz and debian/ from another repo. The same debuild build works fine if I use 'bzr dh-make' for debianization..
[19:16] <AmberJ_> I thought that 'bzr dh-make' only creates orig.tar.gz and copies template debian/ files.... but it seems ot
[19:17] <AmberJ_> *but it seems that it (i.e. bzr dh-make) is doing something else as well... Maybe doing with build environment as you suggest)
[19:19]  * AmberJ_ is reading dh_make source
[19:25] <james_w> AmberJ_, might it be that MOSES_BZR_REVNO has no value when it breaks?
[19:25] <james_w> hmm, doesn't sound right though
[19:25] <james_w> but yeah, that error doesn't seem to have much to do with the file as you say
[20:27] <TheLordOfTime> http://paste.ubuntu.com/1056521/  <-- anyone able to tell me what's missing?  i told the system to use all the components
[20:28] <TheLordOfTime> COMPONENTS="main restricted universe multiverse"  <-- defined in ~/.pbuilderrc
[20:28] <TheLordOfTime> for all users
[20:29] <jtaylor> TheLordOfTime: try with PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-gdebi" in .pbuilderrc
[20:29] <jtaylor> it gives better error messages in my experience
[20:31] <TheLordOfTime> bleh, pbuilder base got purged
[20:31]  * TheLordOfTime is not pleased
[20:31] <TheLordOfTime> (the base.tgz)
[20:31] <TheLordOfTime> will that base be rebuilt when i specify distribution 'quantal' instead of precise or when i specify 'natty'?
[20:32] <jtaylor> yes
[20:32] <TheLordOfTime> good
[20:32] <jtaylor> use pbuilder-dist for easy multi distributions
[20:33] <jtaylor> or set BASETGZ/BASEPATH appropriately
[20:43] <TheLordOfTime> jtaylor:  This package is uninstallable
[20:43] <TheLordOfTime> Dependency is not satisfiable: debhelper (>= 7.0.50~)
[20:44] <TheLordOfTime> so...
[20:45] <TheLordOfTime> not sure what its on about...
[20:45] <TheLordOfTime> (since this is being caused by the 'juju' source package from quantal)
[20:46] <TheLordOfTime> and juju's in main, if this is triggered in Quantal, bad things'll happen
[20:49] <TheLordOfTime> jtaylor:  still around?
[20:49] <jtaylor> TheLordOfTime: debhelper 7 not available in quantal?
[20:49] <jtaylor> unlikely
[20:49] <TheLordOfTime> jtaylor:  <ubottu> debhelper (source: debhelper): helper programs for debian/rules. In component main, is optional. Version 9.20120419ubuntu2 (quantal), package size 594 kB, installed size 966 kB
[20:49] <TheLordOfTime> so...
[20:49] <TheLordOfTime> not sure wth's going on
[20:50] <jtaylor> just use pbuilder-dist
[20:50] <TheLordOfTime> and that's with a pbuilder-dist quantal create
[20:50] <TheLordOfTime> jtaylor:  i *did* i was just typing that
[20:50] <TheLordOfTime> so unless pbuilder's gone wonky and is bugged
[20:50] <TheLordOfTime> pbuilder-dist *
[20:50] <jtaylor> can you login and install the dependencies?
[20:53] <TheLordOfTime> pbuilder-dist quantal login --save-after-login right?
[20:54] <TheLordOfTime> ah there it is
[20:54] <TheLordOfTime> jtaylor:  i'm going to edit the debian/control
[20:55] <TheLordOfTime> i think the ~ is throwing it off (its yelling at python, ended with a ~ too)
[20:55] <TheLordOfTime> I: Installing the build-deps
[20:55] <TheLordOfTime> This package is uninstallable
[20:55] <TheLordOfTime> Dependency is not satisfiable: python (>= 2.6.6-3~)
[20:55] <TheLordOfTime> unless pbuilder-dist is literally broken
[20:56] <TheLordOfTime> unless you're willing to do me a favor and try to build juju in Quantal yourself
[20:56] <TheLordOfTime> (its directly synced from Debian, so i wonder if its breaking)
[20:57] <TheLordOfTime> even installing python myself doesnt fix it
[20:57] <TheLordOfTime> how much do you want to bet that pbuilder-dist is broken
[20:57] <TheLordOfTime> jtaylor:  ^
[20:58] <jtaylor> not sure what the problem
[20:58] <jtaylor> likely something with components
[20:58] <TheLordOfTime> well that's unlikely
[20:58] <TheLordOfTime> debhelper's main
[20:58] <TheLordOfTime> so's python
[20:59] <arand> pango-graphite needs SRUing somehow in lucid: Bug #893559 which I'll be marking a dupe of Bug #540035 shortly.
[20:59] <TheLordOfTime> yep, i think this is a bug in pbuilder
[20:59] <TheLordOfTime> because i even *installed* python
[21:00] <arand> This appears to fall into the "upstream microrelease" SRU category. Would it be appropriate here to simply request a sync from debian squeezy for the SRU?
[21:00] <jbicha> personally, I use sbuild instead of pbuilder http://wiki.debian.org/sbuild
[21:00] <TheLordOfTime> jbicha:  i dont have it installed
[21:07] <arand> TheLordOfTime: This is a qq pbuilder and qq juju source?
[21:08] <TheLordOfTime> arand:  precise pbuilder, quantal juju source
[21:08] <TheLordOfTime> although i have a tarball now built for quantal
[21:08] <TheLordOfTime> (for the pbuilder)
[21:08] <TheLordOfTime> i'm just testing a package build
[21:08] <TheLordOfTime> not actually *producing* the debs here
[21:08]  * TheLordOfTime tests any and all debian package builds prior to submitting debdiffs for bugs
[21:08] <TheLordOfTime> s/debian//
[21:11] <TheLordOfTime> arand:  and using pbuilder-dist also breaks
[21:11] <TheLordOfTime> it doesnt correctly identify that the debhelper and the python is valid
[21:12] <TheLordOfTime> unless quantal's bootstrapthingy is wrong
[21:15] <TheLordOfTime> oh hang on
[21:19] <arand> "pbuilder-dist quantal build juju_0.5+bzr542-1.dsc" seems to work for me from Debian
[21:20] <TheLordOfTime> meh might just be pbuilder
[21:20] <arand> precise doesn't have the python packages/versions that the quantal juju depends on.
[21:20] <TheLordOfTime> i'll reinstall everything for it later
[21:20] <TheLordOfTime> arand:  but it was a quantal pbuilder-dist
[21:20] <TheLordOfTime> i *confirmed* that
[21:20] <TheLordOfTime> it should have still built within the chroot
[21:20] <TheLordOfTime> no?
[21:20] <TheLordOfTime> i.e. pbuilder-dist quantal build ...
[21:21] <arand> Is it old and in need of an update?
[21:21] <arand> (the base tgz that is)
[21:21] <TheLordOfTime> i just recreated it
[21:21] <TheLordOfTime> so i doubt it
[21:22] <arand> Yeah.
[21:22]  * TheLordOfTime had to recreate it today after an unfortunate nuking of the cache
[21:31] <arand> Hmm, I'm seing your exact dependency errors on the precise base and not on the quantal one...
[21:31] <TheLordOfTime> arand:  then i'm going to file a bug against pbuilder at this rate
[21:31] <TheLordOfTime> pbuilder-dist quantal build did those errors
[21:31] <TheLordOfTime> it even said * distribution is quantal
[21:32]  * TheLordOfTime will purge pbuilder stuff and reinstall then test
[21:32] <TheLordOfTime> if it comes up i'll be filing a bug
[21:32] <TheLordOfTime> comes up after reinstall*
[21:33] <arand> Your first log from above is from precise though?
[21:33] <TheLordOfTime> in pbuilder
[21:33] <TheLordOfTime> but then i remembered i keep a build-tests ppa on lp
[21:33] <TheLordOfTime> so i just used that
[21:35] <arand> uh?
[21:36] <arand> So you tried it in a precise base.tgz then in a PPA on quantal, then in a quantal base.tgz?
[21:36] <arand> *PPA quantal pocket
[21:41]  * TheLordOfTime sighs
[21:42] <TheLordOfTime> arand:  i uploaded to a plain old PPA on Launchpad
[21:42] <TheLordOfTime> after i said "screw it" to pbuilder locally
[21:42]  * TheLordOfTime assumed that would have been understood immediately
[21:42] <TheLordOfTime> the package is targetted against Quantal, so it tried to build in a quantal chroot within the PPA builders
[21:42] <TheLordOfTime> so it got past the random crap i was seeing in pbuilder
[21:43] <TheLordOfTime> and stuff
[21:43] <TheLordOfTime> i'm on a different issue now
[21:43] <arand> Well, I FTBFS:ed as well, on a bunch of testcases...
[21:45] <arand> http://paste.debian.net/176022/ But the depends bit you were seing went ok.
[21:51] <TheLordOfTime> wait, so it FTBFS in Quantal?
[21:52] <TheLordOfTime> arand:  ^
[21:53] <arand> Looks like it, but later on in the build preocess than in your case... weird.
[21:55] <TheLordOfTime> arand:  https://launchpadlibrarian.net/108472904/buildlog_ubuntu-quantal-i386.juju_0.5%2Bbzr542-1.1_FAILEDTOBUILD.txt.gz  <-- that's what i'm getting when trying to help someone fix a bug (via an LP builder)
[21:55] <TheLordOfTime> (see -bugs if you're not there already)
[21:58] <TheLordOfTime> but if you're saying the original package isnt building from that source, then that's a bigger problem=
[21:58] <TheLordOfTime> whoops
[22:04] <arand> TheLordOfTime: From what I can tell that build log tells the exact same story as the one from pbuilder-precise-base... Just that it's using a different builder than pbuilder. But I've a hard time imagining that the QQ pocket in a PPA would confuse the series. I have no clue what's up there...
[22:04] <arand> I would say it's indicating that it's not a pbuilder bug though.
[22:10] <AmberJ_> ok thanks james_w ... I won't settle until I find the source of this bug.
[22:12] <arand> TheLordOfTime: I'm wondering if it's the latest python that's in flux, and being only half-published on some servers or so, hence everything that's depending on python suffers...
[22:18] <arand> Hmm, no I misread the publishing dates there, seems pretty unlikely to be python..
[22:22] <TheLordOfTime> agreed
[22:22] <TheLordOfTime> i'm thinking there's an error in the juju code
[22:22] <TheLordOfTime> especially if its FTBFS without any patches
[22:22] <TheLordOfTime> s/any/any additional/
[22:25] <arand> TheLordOfTime: Which package server were you using for your pbuilder by the way?
[22:26] <TheLordOfTime> iridium
[22:27] <arand> Oh, I meant http://archive.ubuntu.com/ubuntu or?
[22:27] <TheLordOfTime> oh, um...
[22:27]  * TheLordOfTime checks
[22:28] <TheLordOfTime> http://archive.ubuntu.com/ubuntu  <--
[22:28] <TheLordOfTime> (from the sources.list in the base tarball)
[22:29] <TheLordOfTime> i could try it off of the us archive though
[22:29] <TheLordOfTime> (the US mirrors)
[22:29] <arand> Well, we were using the same mirror, so that can't be the dependency mismatch either o_o
[22:29] <TheLordOfTime> but if the main archives have a major regression issue, then the mirrors wont be much better
[22:29] <TheLordOfTime> indeed
[22:29] <TheLordOfTime> hence why i'm going to uninstall and reinstall pbuilder
[22:30] <AmberJ_> Where is dh_make repo? I can see dh_make source on packages.debian.org but isn't there's supposed to be a version controlled repo as well?
[22:30] <TheLordOfTime> hmm
[22:30] <TheLordOfTime> arand:  is dh-make needed?
[22:30]  * TheLordOfTime isnt seeing dh-make installed on his system
[22:31] <arand> It's only for making packaging starter templates
[22:31] <TheLordOfTime> just making sure
[22:31] <TheLordOfTime> (although i do need that)
[22:32] <arand> It's time-saving, though doesn't help you in doing the actual work :)
[22:32] <TheLordOfTime> well...
[22:32] <TheLordOfTime> it prevents me from having to bzr branch my debian templates
[22:32] <TheLordOfTime> because i'll just recreate em
[22:32]  * TheLordOfTime keeps debian/ templates on a junk branch
[22:35] <AmberJ_> Found it http://anonscm.debian.org/viewvc/collab-maint/deb-maint/dh-make/ (dh-make svn repo on alioth)
[22:41] <arand> AmberJ_: It's http://git.debian.org/?p=collab-maint/dh-make.git;a=summary nowadays actually.
[22:42] <TheLordOfTime> ^ that
[22:51] <arand> TheLordOfTime: alo21's patch does cause a separate (earlier) FTBFS issue, it seems.
[22:51] <TheLordOfTime> ah, so then his patch is invalid
[22:51] <arand> Now we've got three of em' :D
[22:51] <TheLordOfTime> (good thing he didnt upload, i'd have been strict)
[22:51] <AmberJ_> Thanks arand!
[22:51] <TheLordOfTime> arand:  if you can narrow down the FTBFS issue, that'd be awesome.
[22:52] <arand> http://paste.debian.net/176033/ is the one with alo21's patch
[22:59] <arand> I'm doubting I'll have much luck with it, but I'll gather as much as possible for a bug report though.
[23:14] <AmberJ_> james_w, I think I now get what you meant by "[00:55] <james_w> AmberJ_, might it be that MOSES_BZR_REVNO has no value when it breaks?"
[23:15] <AmberJ_> In fact, I strongly suspect that MOSES_BZR_REVNO getting no value is the culprit :)
[23:15] <AmberJ_> I'm doing a build now to see if we are right..
[23:19] <arand> Though, now it's turning night here.
[23:28] <AmberJ_> It does NOT matters if I run debuild from package/debian or from package/ .... right?
[23:29] <TheLordOfTime> arand:  at the least, on the bug report, i'd recommend pointing out it FTBFS as well (although note he didnt upload his patch yet)
[23:29] <arand> AmberJ_: Should not.
[23:29] <AmberJ_> ok
[23:30] <arand> TheLordOfTime: Yeah, when I said Bug I meant a new one for the current-version ftbfs
[23:30] <TheLordOfTime> file it and subscribe me?
[23:30] <TheLordOfTime> (trekcaptainusa-tw is my LPID)
[23:53] <Yankees52> !ops
[23:53] <Yankees52> ban me =)
[23:53] <Yankees52> !staff