[01:58] <TheDrums> micahg: I had simply asked if it was going to be in backports, not pushing. :)   Reason I asked though, is because debian stable's one in backports supports additional ssh features such as keyfile and changing the port number which I can't find in the current Ubuntu one.  Found a devs PPA though.
[01:59] <micahg> TheDrums: if you want it there, request it, backports is based on user request mostly
[01:59] <micahg> TheDrums: it's easy enough to approve once the testing is done and I"m happy to prepare test packages if you like
[01:59] <micahg> the person who did the first round of backports has been busy of late
[02:00] <TheDrums> Well, I'm pretty new to the program, but I'd pretty much be up for it.
[02:00] <micahg> TheDrums: test == install/run, just run the requestbackport script from ubuntu-dev-tools, it'll help you file a request and tell you what needs testing
[02:01] <micahg> any questions along the way, I'm sure someone here can help
[02:02] <micahg> the great thing with backports is the testing is something almost anyone can do, and by helping something get there, you're making it available to all Ubuntu users
[02:04] <TheDrums> It's not a big deal to have for me, but I can do and I already have backports enabled. :)
[02:04] <micahg> TheDrums: it's on automatically in oneiric and later
[02:04] <micahg> you just have to select the new version the first time you want to jump to the backports version of something
[03:21] <ESphynx> Hey guys, would anyone have a clue on how to build for PPC on a Launchpad PPA so I could test the other platforms?
[03:25] <ESphynx> so the answer is I can't unless it's on an official Ubuntu archive :P
[03:28] <ESphynx> So should the source packages be de-built on Quantal, or it doesn't really matter?
[03:29] <ESphynx> downloading the image, though I guess I'll start by trying it out in Precise :P
[04:43] <ESphynx> What's up with this error guys native-package-with-dash-version ?
[05:09] <ESphynx> any ideas why debuild is giving me unmet dependencies , but the Launchpad PPA is working fine ? https://raw.github.com/ecere/sdk/ppa/precise/debian/control
[07:28] <dupondje> How can I let pbuilder include the source file when it generates a .changes file? I did build the .dsc with debuild -S -sa, but still not included :(
[07:57] <geser> dupondje: you mean a .changes file with the binary and the source "files"? (as needed for uploads to Debian)
[07:59] <Laney> I suppose it's --debbuildopts -sa
[08:01] <dupondje> geser: well i'm trying to make my own package, and upload it to my own repo with reprepro
[08:01] <dupondje> but the .changes doesn't include the orig.tar.gz
[08:01] <dupondje> so its not dputted
[08:17] <dupondje> Laney: dpkg-genchanges: including full source code in upload
[08:17] <dupondje> that worked :) thx
[09:42] <ESphynx> hey guys... so I've updated https://bugs.launchpad.net/ecere/+bug/394998
[09:43] <ESphynx> Do I need to re-subscribe sponsors? looks like it's not subscribed...
[09:51] <dholbach> ubuntu-sponsors seems to be subscribed as far as I can see
[09:53] <ESphynx> dholbach I just added it back ;P
[09:53] <dholbach> ok
[10:24] <tumbleweed> ESphynx: any reason that can't go through debian?
[10:27] <ESphynx> tumbleweed: well, I was hoping to make it into the feature freeze for Quantal :P
[10:28] <ESphynx> been trying to get this packaging settled for 3 years :|
[10:28] <tumbleweed> there's no rush. it can land after feature freeze
[10:28] <ESphynx> how so?
[10:37] <tumbleweed> there's an exception process, and brinding a new package through debian is a valid exceptoin reason for me
[10:39] <ESphynx> ah... well i'm tring to build on debian as well
[10:39] <ESphynx> different package standards though make it all a pain
[10:44] <landic> hi, is there someone around who can help me get this landed before feature freeze? https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1031035
[10:44] <tumbleweed> the standards are the same
[10:44] <tumbleweed> (well, almost)
[10:45] <tumbleweed> what differences are causing you trouble?
[10:45] <tumbleweed> landic: can you prepare a patch against the package?
[10:46] <ESphynx> dholbach: any chance you have the failed build log? :)
[10:47] <dholbach> ESphynx, just a sec
[10:47] <landic> tumbleweed: never done that, but it sounds like more work than just saving the file to the debian/ dir
[10:47] <dholbach> ESphynx, http://people.canonical.com/~dholbach/last_operation.log
[10:48] <tumbleweed> landic: that's what ubuntu developers expect, though
[10:49] <ESphynx> thanks dholbach
[10:50] <landic> tumbleweed: i'll see if I can find the time before my vacation
[10:50] <ESphynx> dholbach: that's very strange, because it said: The Ecere SDK is fully built. and The Ecere SDK has been installed.
[10:51] <landic> probably not though
[10:51] <Laney> landic: tumbleweed: While a patch is the most easy way to apply a change, I don't think it's necessary
[10:51] <Laney> as there is a proposed file there, I would expect most sponsors to be able to take it from here
[10:51] <dholbach> ESphynx, line 685
[10:52] <tumbleweed> Laney: no, it's not. But if there was a patch, the patch bot would have subscribed ubuntu-sponsors and that'd be all he had to do
[10:52] <ESphynx> don't wanna bug you too much though... guess I'll have to try it in Quantal...
[10:52] <Laney> landic: I'm saying that you can probably just subscribe ubuntu-sponsors now and someone could take a look
[10:52] <landic> Laney: I'll do that then, thanks
[10:53] <ESphynx> dholbach: I see the missing files, but I don't know who's saying that? https://code.launchpad.net/~ecere-team/+archive/ppa/+build/3722682/+files/ecere-sdk_201208132333-0~776~quantal1_i386.deb  --> the .so is in there, and if it said installed successfully, that's because install -D succeeded on that file....
[10:53] <Laney> if you want to ensure you get credit from the change in Launchpad then you should give a patch though.
[10:53] <dholbach> ESphynx, I built it in a i386 quantal pbuilder
[10:53] <dholbach> ESphynx, how did you build it?
[10:54] <landic> Laney: I don't really care about credit :)
[10:54] <ESphynx> or rather ln -sf $(LP)EDA$(SOV) $(LIBDIR)/$(LP)EDA$(SO)
[10:54] <Laney> fair enough
[10:54] <ESphynx> dholbach: on Quantal, only on Launchpad PPA (i386) so far...
[10:54] <landic> I just want to get this going so transmission will play nicer with ubuntu
[10:54] <ESphynx> there's another build pending in 15 min...
[10:55] <ESphynx> But last succeeded build was: https://launchpadlibrarian.net/112670033/buildlog_ubuntu-quantal-i386.ecere_201208132333-0~776~quantal1_BUILDING.txt.gz
[10:59] <dholbach> ESphynx, I'm happy to retry it locally and see if that changes anything
[11:00] <ESphynx> dholbach: well is there any way you could peek at the created files?
[11:01] <ESphynx> i.e. after the make install is done?
[11:03] <dholbach> ESphynx, I can try - give me a bit of time - I'm currently looking at something else as well
[11:04] <ESphynx> thanks a lot dholbach
[11:14] <dholbach> ESphynx, I'm in the i386 chroot now - which files do you want me to look at?
[11:15] <ESphynx> dholbach: well it's saying that it's missing a libEDA.so* ?
[11:15] <ESphynx> in /usr/lib/
[11:15] <ESphynx> (of the DESTDIR...)
[11:15] <dholbach> http://paste.ubuntu.com/1146636/
[11:16] <dholbach> ah, it's a i386 chroot on amd64, if that matters O:-)
[11:16] <ESphynx> and h_install: ecere-sdk missing files (usr/lib/libEDA.so*), aborting
[11:16] <dholbach> did the ppa build suceed?
[11:17] <ESphynx> dh_install*
[11:17] <ESphynx> dholbach: The earlier one did for sure
[11:17] <dholbach> let's wait for this one to run and see what it says
[11:17] <dholbach> if it succeeds, i386 chroot on amd64 might be a problem :)
[11:17] <ESphynx> it's currently building now...
[11:18] <dholbach> ok
[11:18] <ESphynx> https://code.launchpad.net/~jerstlouis/+recipe/ecere-daily-precise
[11:18] <ESphynx> I'm pretty sure it's gonna be the same thouhg...
[11:18] <ESphynx> it's the dh_install looking for it in /usr/lib/ while it's in /usr/lib32/ ...
[11:18] <ESphynx> but isn't that a symlink?
[11:19] <ESphynx> oh. but it's 'local' path
[11:19] <ESphynx> I know dholbach
[11:20] <ESphynx> what does DEB_HOST_ARCH say ?
[11:20] <ESphynx> ifeq ($(DEB_HOST_ARCH),i386)
[11:20] <ESphynx> 	cp debian/libecere.install.in32 debian/libecere.install
[11:20] <ESphynx> 	cp debian/ecere-sdk.install.in32 debian/ecere-sdk.install
[11:20] <ESphynx> endif
[11:20] <ESphynx> shell dpkg-architecture -qDEB_HOST_ARCH
[11:20] <ESphynx> I bet I could kill all this code on multiarch.
[11:21] <dholbach> i386
[11:22] <ESphynx> if it's i386, it tries to copy usr/lib/libEDA.so*
[11:22] <ESphynx> ah
[11:22] <ESphynx> HOSTTYPE := $(shell uname -m)
[11:22] <ESphynx> taht one probably conflicts :P
[11:22] <dholbach> uname -m is x86_64
[11:23] <ESphynx> they don't agree :P
[11:23] <dholbach> let me know how the PPA build goes :)
[11:23] <ESphynx> dholbach oh i'm sure the PPA will work.
[11:24] <ESphynx> it's really a cross-build issue
[11:24] <dholbach> yeah, I think so too - if I had set up a VM I'm sure it'd work in there as well
[11:24] <ESphynx> or rather, chroot issue...
[11:24] <ESphynx> i.e. if you build with make
[11:24] <dholbach> once the PPA build is done, I'll have a look at the resulting packages
[11:24] <ESphynx> it installs as is...
[11:24] <dholbach> let me know when it's done
[11:24] <ESphynx> without need for a chroot
[11:25] <ESphynx> I have it configured so one can just download the orig tarball and hit 'make' on a 64 bit system.
[11:25] <ESphynx> great, thanks!
[11:25] <dholbach> anytime
[11:31] <ESphynx> dholbach: hmm the binaries build are scheduled for in one hours :( do you want me to attach the .deb that my .dsc etc produced?
[11:32] <dholbach> ESphynx, maybe just link to the build page in the bug report
[11:32] <dholbach> attaching should not be necessary
[11:33] <ESphynx> dholbach: I was tols earlier that daily builds were not good enough :P
[11:34] <ESphynx> tumbleweed: my main problem with getting it in debian is they want me to do it with pbuilder :P which is a serious pain.
[11:34] <ESphynx> pbuilder for sid
[11:34] <dholbach> ESphynx, I'm too lazy to set up a i386 VM right now, so for reviewing it and establishing that a 'regular' i386 build works a daily build is good enough
[11:34] <dholbach> I assume that the daily build is pretty close to the source package you submitted in the bug report
[11:35] <xnox> ESphynx: $ apt-get install ubuntu-dev-tools; pbuilder-dist create sid ; pbuilder-dist sid build *.dsc
[11:35] <ESphynx> dholbach: it is.
[11:35]  * xnox There is a deb for that! =)
[11:35] <ESphynx> xnox: don't forget the i386 in there
[11:35] <ESphynx> and hten I get amd64 errors
[11:36] <xnox> ESphynx: pbuilder-dist crate sid i386
[11:36] <ESphynx> which I think is why i had the [i386] where the way I had them before
[11:36] <ESphynx> which you had me take out :P
[11:36] <xnox> will give you a i386 pbuilder chroot on amd64 host
[11:36] <ESphynx> I think they ahd to be like that to work on debian
[11:36] <xnox> and then you want
[11:36] <xnox> $ pbuilder-dist sid i386 build *.dsc
[11:36] <ESphynx> xnox: yse I did that, and I did it a second or 3rd time, and now my VDI is out of space.
[11:36] <ESphynx> let me try that
[11:37] <xnox> ESphynx: to recover space, $ pbuilder-dist sid i386 clean
[11:37] <ESphynx> E: amd64 not in arch list or does not match any arch wildcards: i386 armel armhf powerpc all
[11:37] <ESphynx> xnox: how to recover the non-i386 one I built by mistake?
[11:37] <xnox> ESphynx: can you pastebin the exact command you ran?
[11:37] <ESphynx> the exact one you just pasted
[11:38]  * xnox ESphynx note "sid i386" not just "sid"
[11:38] <xnox> and you need to create it first (the i386 variant)
[11:40] <ESphynx> xnox yes I copy pasted your command
[11:40] <ESphynx> I created it too
[11:40] <ESphynx> although i hope running the create command a 2nd time (did that by mistake) didn't delete the first one I had created
[11:41] <xnox> ESphynx: you create a chroot once (one time setup), then you simply use build each time (it creates a snapshots, does the build, and deletes the snapshot)
[11:42] <ESphynx> dholbach: if you have interest in reviewing the actual package capabilities, maybe you'd like to quickly look through http://ecere.com/SDKIntro.pdf which was published in the Software Developer's Journal :)
[11:42] <ESphynx> xnox: right I knwo
[11:42] <dholbach> ESphynx, I'm afraid I might be a bit too busy to do that right now :/
[11:42] <ESphynx> I ran it a 2nd time by mistake (wrong command going up, cuz they both started by pbuilder-dist!)
[11:43] <ESphynx> dholbach : hehe np
[11:54] <ESphynx> dholbach: allright I updated the maintainer and copyright thing and pushed to the packaging branch...
[11:54] <dholbach> ok
[11:54] <ESphynx> so the next build after that will pick it up I guess ;)
[11:57] <ESphynx> well all this sid creating and recreating is taking forever
[11:57] <ESphynx> I badly need sleep
[11:57] <ESphynx> thank you all, good day/night
[12:03] <ESphynx> xnox: still there?
[12:03] <ESphynx> xnox: same thing.
[12:03] <ESphynx> I: Logging to /home/jerome/pbuilder/sid-i386_result/last_operation.log
[12:03] <ESphynx> E: amd64 not in arch list or does not match any arch wildcards: i386 armel armhf powerpc all
[12:04] <xnox> strange.
[12:05] <StevenK> amd64 does not build all, and is not in i386 armel armhf powerpc
[12:05] <StevenK> So, maybe you should use 'any' rather than enumerating them
[12:05] <ESphynx> StevenK: exactly.
[12:05] <ESphynx> I remember going through the exacts steps 6 months ago or so.
[12:06] <ESphynx> someone had me change it back to all yesterday
[12:07] <ESphynx> any will cause problem
[12:07] <ESphynx> I had to list the same binary types
[12:07] <ESphynx> if I put any i'll get some amd64 errors
[12:08] <ESphynx> won't I?
[12:13] <ESphynx> well putting 'any' seems to work
[12:14] <ESphynx> guys in #debian-mentors says it might be fixed in pbuidler 0.202, which I don't have
[12:18] <xnox> hmm... let me check pbuilder
[12:18] <xnox> pbuilder 208 is in precise and quantal
[12:18] <xnox> what distro are you using?
[12:19] <ESphynx> well my pbuilder stuff was in oneiric
[12:19] <ESphynx> so I was doing that there
[12:19] <ESphynx> though i have a fresh quantal machine (That nicely froze on the reboot at the console!!!)
[12:20] <ESphynx> and a precise 32 VM up as well
[12:23] <ESphynx> dholbach: I hit that chroot bug with pbuilder... obviously
[12:39] <tumbleweed> ESphynx: do I remember right that this package doesn't actually support amd64?
[12:40] <ESphynx> tumbleweed: it will build if you just say 'make'
[12:40] <ESphynx> as 32 bit (-m32)
[12:40] <tumbleweed> right, so why bother?
[12:40] <tumbleweed> why not just only build it on i386?
[12:40] <ESphynx> tumbleweed: that is what I do.
[12:40] <ESphynx> however here I was in a 64bit oneiric machine trying to pbuilder it for those Debian guys
[12:40] <ESphynx> and I hit that chroot problem
[12:40] <tumbleweed> should work just fine. You need an i386 pbuilder chroot
[12:41] <ESphynx> tumbleweed oh I have one, but it hits a bug
[12:41] <ESphynx> disagreement between dpkg-architecture -qDEB_HOST_ARCH and uname -m
[12:41] <tumbleweed> right, don't trust uname
[12:41] <ESphynx> which is there to make 'make' just work if you do it
[12:41] <ESphynx> on the amd64...
[12:42] <ESphynx> tumbleweed: what else should I trust?
[12:57] <tumbleweed> ESphynx: I suppose you can trust uname -m. it should return i686 in a i386 chroot (thanks to linux32)
[12:58] <ESphynx> tumbleweed: it returns x86_64
[12:58] <ESphynx> [07:22] <dholbach> uname -m is x86_64
[12:59] <tumbleweed> it returns i686 in my chroots
[12:59] <ESphynx> weird.
[12:59] <ESphynx> but anyways, I insatlled pbuilder on my 32bit machine to build for Debian...
[13:01] <ESphynx> ok running it in a 32 bit now :P
[13:03] <directhex> use dpkg-architecture, never uname
[13:03] <directhex> uname returns x86_64 in an ARM chroot :)
[13:05] <ESphynx>  Failed to create /var/cache/pbuilder/ccache/2/6: Permission denie -- awesome
[13:05] <ESphynx> directhex: that is the command I use to build the source package... on any system, linux or not :)
[13:05] <ESphynx> I want it to be possible to build from 'make'
[13:06] <ESphynx> besides I hate chroot.
[13:09] <xnox> echo "unset CCACHEDIR" | sudo tee -a /etc/pbuilderrc
[13:09] <xnox> ESphynx: ^^^ should fix the ccache error
[13:09] <ESphynx> k thanks
[13:10] <xnox> or edit manually to add the unset into there....
[13:12] <ESphynx> ok... crashing
[14:05] <tumbleweed> directhex: works in mine
[14:06] <directhex> hmph. how about /proc/cpuinfo ?
[14:09] <tumbleweed> well, that always lies :)
[14:09] <tumbleweed> (I mean don't trust that at all, setarch doesn't fake it)
[14:14] <tumbleweed> directhex: back to the point,t hough. I think ESphynx is using uname in his upsrteam makefile. One can't depend on dpkg-architecture on non-debian
[18:08] <tbf> ricotz: hi. just advertised your grilo-0.2 packages. do you also plan packaging grilo-plugins-0.2 ?
[18:13] <green7> I keep getting this error after running debuild:
[18:13] <green7> dpkg-buildpackage: error: debian/rules build gave error exit status 2
[18:13] <green7> debuild: fatal error at line 1350:
[18:13] <green7> dpkg-buildpackage -rfakeroot -D -us -uc failed
[18:15] <Lasall> green7: please nopaste your build log
[18:16] <green7> all right
[18:16] <green7> can you help me?
[18:16] <Lasall> I don't know before viewing the log ;)
[18:16] <green7> well?
[18:17] <Lasall> green7: use pastebin.org or something similar
[18:18] <jtaylor> or the pastebinit command line tool
[18:19] <green7> here is the pastebin: http://pastebin.com/Jd966jPr
[18:19] <jtaylor> green7: did you install all build dependencies?
[18:19] <green7> yep
[18:20] <jtaylor> either apt-get build-dep package or mk-build-depends -ir
[18:20] <Lasall> green7: is libsigc++-2.0-dev installed?
[18:20] <jtaylor> this type of message can pretty much only mean missing build dependency
[18:21] <green7> Lasall: nope it's not :P
[18:23] <green7> Installed libsigc++-2.0-dev
[18:23] <green7> nothing!
[18:24] <Lasall> nothing what? please nopaste your login again.
[18:24] <Lasall> *log
[18:27] <green7> SFML/Graphics.hpp is missing
[18:28] <Lasall> install libsfml-dev
[18:28] <Lasall> but you really should install build-deps with one of the commands from jtay_lor
[18:29] <green7> Actually I'm packaging
[19:19] <green7> how do I submit my patch without using bzr?
[19:28] <micahg> green7: cross-posting in multiple channels is generally frowned upon, you should give people more than a few minutes to answer a question
[19:28] <green7> sorry
[19:29] <green7> can you help me out?
[19:43] <jtaylor> update the changelog with dch -i, build the package and the do a debdiff old.dsc new.dsc
[19:57] <hyperair> https://bugs.launchpad.net/bugs/1036725 is weird. is scintilla broken with regard to ubuntu mono's font hinting?
[19:57] <ESphynx> good morning guys
[21:23] <ESphynx> FYI I uploaded the Ecere package to mentors.debian.net as well: http://mentors.debian.net/package/ecere
[22:06] <dupondje> Somebody with experience on mozilla packages?
[22:06] <dupondje> would like to build new version of the lightning extension :)
[22:07] <dupondje> Building fails with "configure:17825:27: fatal error: sys/int_types.h: No such file or directory"
[22:07] <dupondje> but no idea where that file would be :)