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