[00:26] good night === nxvl_ is now known as nxvl_work === nxvl is now known as Guest68601 === nxvl_work is now known as nxvl [00:44] I’m sure spammers sincerely appreciate http://revu.tauware.de/uploaders.list :-) [00:54] Could someone please review ? Thanks. [03:24] QA target site(http://qa.ubuntuwire.com/) seems to be down [03:29] bliZZardz: Works for me. [03:35] ah! eternal damnation! [03:38] I could always add a firewall rule to block you if you really want it to be down. [03:39] :) ..and why would you do that [04:08] anyone available to review my pyrocket package? Comments from previous submission have been addressed. https://bugs.launchpad.net/ubuntu/+bug/242910 [04:08] Launchpad bug 242910 in ubuntu "[needs-packaging] pyrocket" [Wishlist,In progress] [04:44] kostmo: The link to the package on REVU is the one that potential reviewers are most likely to be interested in. [04:45] I wasn't sure which I should give, the REVU package link is present on the launchpad bug, tho [04:45] http://revu.ubuntuwire.com/details.py?upid=2707 [04:47] ScottK, the avscan package for hardy still needs updating for libclamav4 right? [04:48] or am I not seeing something [04:48] brandonperry: It does. There's a new upstream release that supports it that needs to be packaged. Unfortunately the new avscan also needs a new libendeavour2, which also needs packaging. [04:48] hrm [04:48] It's still broken in Intrepid too. [04:49] And the Debian Mainter just orphaned the package. [04:49] ok [04:49] So if you like avscan, you might want to look into packaging the update ... [04:50] well, I don't use it :-) [04:50] It'll probably get removed from Debian and I'll ask for removal in Ubuntu before Intrepid releases unless it gets fixed. [04:50] prefer regualr clamscan [04:50] Nah. Me neither. [04:51] I found some free time, so I will look into it tomorrow (looking at the debian packages for libendeavour2 now [04:51] kostmo: Think about making your potential reviewer's life easier. He's got to get the REVU link, so don't make him work harder. [04:51] brandonperry: Cool. If you need advice or sponsorship (in Ubuntu, I'm not a DD), let me know. [04:52] ok, thanks :-) [04:53] ScottK: gotcha [05:16] How does one clear out packages from the PPA? I deleted all packages from my PPA, but it still rejects my uploads saying that that version "is already accepted in ubuntu/hardy and you cannot upload the same version within the same distribution" === LucidFox is now known as WebstripFox === WebstripFox is now known as LucidFox [07:16] kostmo: That isn't how Debian archives work. [07:23] ? [07:23] if I upload a package w/ a specific version to my personal package archive, is it there forever? [07:24] You can't upload the same version again. [07:24] If you could, it would break upgrades for anybody using your PPA. [07:28] ah i c === Syntux_ is now known as Syntux [09:26] On https://wiki.ubuntu.com/PackagingGuide/Howtos/DesktopFiles it says 'Verify that the package is not listed below as not needing a .desktop file'. I can not find such a list. Would anyone (Riddell?) know where I can find it? [11:10] hi motu. could i set python-launchpad-bugs to build and install against 2.4.4 instead of 2.5 with success? [11:11] thekorn: ^ [11:13] kgoetz, sorry I'm not familiar with packaging, but python-launchpad-bugs is supposed to work with python2.4 [11:15] thekorn: i'll try changing the build+install deps to 2.4. thank you. [11:25] kgoetz: I'm not really familiar with the package, but changing the install deps should do [11:26] kgoetz: ... in the case you would want to install it on a system without python2.5 [11:27] kgoetz: if you just want to use it with python2.4 but have 2.5 installed this should already be possible, as it is currently being build for both versions (or at least the version in Intrepid) [11:27] RainCT: i dont have python2.5 (i'm running etch) [11:29] kgoetz: ah ok. yes, then just change them down [11:29] * kgoetz suspects it'll be faster to install an ubuntu chroot then it will to backport half the world to run 5-a-d [11:52] i'll be going with the chroot idea - i dont have a good enough grip on 5-a-day (and its depends) to know which dependancies can be changed and which cant === bdrung_ is now known as bdrung [13:43] slightly ot - how much ram does a pbuilder instance take? i'm sort of wondering how much more disk thrashing i'll get by building all packages in pbuilders rather then in a chroot (i'll be doign scripted rebuilds of a package set) [13:45] kgoetz: pbuilder uses chroots by default [13:46] geser: iirc "disposable" chroots though (as oposed to a shared chroot for all package builds, ala a buildd) [13:50] yes, pbuilder unpacks the base.tgz into a fresh dir and chroot there and removes it afterwards [13:51] if you have enough memory you can do it on a tmpfs [13:55] how much memory would be 'enough'? 500mb? 1gb? [13:57] my tmpfs for my pbuilder is 2 GB and the build takes 600MB-1GB of it (depending on the package) [13:57] I've 4 GB in total [13:58] an other idea is to use sbuild with LVM snapshots [13:58] might have to beef up my build system then. only got 512 in it [13:58] i dont have lvm [14:00] pbuilder isn't that bad, but the unpacking of the base.tgz to the disk and the removal afterwards takes some time [14:01] mmm. understandable [14:13] crimsun: im gonna be gone for most of today but can you please give your opinion on bug 235135 its about what to backport with flash 10 (PA or libflash...) [14:13] Launchpad bug 235135 in flashplugin-nonfree "[MASTER] Please backport flashplugin-nonfree version 10 beta and asound-plugins from Intrepid so we can drop libflashsupport and the crashes it causes" [Undecided,Invalid] https://launchpad.net/bugs/235135 [14:26] kgoetz: I can pbuild most packages on a system with 256MB RAM, but it's pretty slow. I wouldn't do more than one at a time though. [14:27] ScottK cheers. so more ram ==good, but not required. i'll think about finding more for it :) [14:28] Eclipse won't build in less than 2GB, but other than that, I think I've been able to build most any package. [14:33] Linux and OO.o will be the largest things i build (not that they are small) === evalles_ is now known as effie_jayx === asac_ is now known as asac [15:49] LucidFox: Hi, could you have another look at http://revu.tauware.de/details.py?package=tomboy-blogposter ? I hope it's really ready now ;) [15:53] hefe_bia> It's best to address all reviewers in general [15:53] One reviewer may catch something the other doesn't, and vice versa [15:56] LucidFox: Ok, I see. Then - is it at all ok to actively ask for a review? [16:03] hefe_bia: Nominally about once a day unless it's a REVU day. Then more often, but what you just posted will do for now. [16:08] ok, thanks. [16:12] hefe_bia: FTBFS for me [16:13] hefe_bia: see http://paste.ubuntu.com/25454/ for the error log [16:15] geser: thanks! I'll look into it. What system did you use to build? pbuilder? [16:15] intrepid pbuilder on AMD64 [16:20] anyone know why I would get this error? [16:20] make: *** No rule to make target `--prefix=/usr', needed by `build'. Stop. [16:20] that is after ./configure [16:21] brandonperry : well - something to do with the library path setting [16:22] brandonperry : some lib file is missing [16:22] hrm [16:22] this is my first package, would you mind looking at the rules file to make sure it isn't syntactical? [16:24] oh, wait [16:24] I think I found it [16:24] :) [16:35] Would somebody mind reviewing my package? http://revu.ubuntuwire.com/details.py?package=monkeystudio Thanks ;) [16:36] brandonperry : what was the problem? [16:38] well, I have another problem now, but I had the build commands in build: instead of build-stamp: === luisbg_ is now known as luisbg [16:50] i read from somewhere that debian follows a unique election policy for packet mgmt - is it still in use? [16:52] huh? [17:06] geser: Shame on me! I didn't test again after changing the manpage to lower case. I guess I have learned my lesson... Fixed version is in revu now. [17:52] ping [17:53] Anybody actually in here? [17:57] . === jcfp is now known as Guest68706 [18:28] ScottK: you around? [18:28] Vaguely. [18:28] I just finished packaging endeavour2 [18:28] OK. [18:29] How'd it go? [18:29] should I upload it to REVU? [18:29] once I got past the learning curve, not a problem [18:29] No. File an bug against the package tag it 'upgrade', attached the diff.gz to the bug and subscribe ubuntu-universe-sponsors. [18:29] REVU is just supposed to be for brand new packages now. [18:29] ok [18:29] thanks [18:30] I'll try and take a look at it in the next day or two if no one else gets it first. [18:30] You can also upload it to the ubuntu-clamav PPA since you're a member. [18:30] You did join that team, right? [18:30] uh, don't think so [18:32] If you do, you'll be able to upload stuff to it's PPA: https://launchpad.net/~ubuntu-clamav [18:32] * ScottK runs of for a bit. [18:38] done (attaching the diff) === Kopfgeldjaeger2 is now known as Kopfgeldjaeger === geser_ is now known as geser [20:05] I was trying to recompile gnucash in a pbuilder environment and it failed: http://oss.leggewie.org/wip/gnucash_2.2.4-1ubuntu1_i386.build Is the package faulty or my pbuilder installation? I don't really understand the errors I see and would appreciate some help [20:09] Laibsch: dpkg-deb: building package `gnucash' in `../gnucash_2.2.4-1ubuntu1_i386.deb'. [20:09] <-- It didn't fail ;) [20:09] Oh, really? [20:10] I was suspicious and looked for the package but did not find it [20:10] Laibsch: yes, it was successfull [20:10] all those "error messages" confused me [20:10] Good to know [20:10] check /var/cache/pbuilder/result [20:10] I'd rather not have a broken pbuilder ;-) [20:10] Thanks guys [20:10] Ah, right [20:11] I checked ../*.deb as I am used to with plain debuild [20:11] You can change that in /etc/pbuilderrc or ~/.pbuilderrc [20:12] well, it's empty! [20:12] But I have restarted the build [20:12] Maybe that deleted the old file [20:12] no [20:13] Laibsch: does your pbuilder use /usr/src/pbuilder? then check /usr/src/pbuilder/results [20:14] emgent: \o/ [20:16] hello there [20:20] geser: Looks like it: -> extracting base tarball [/usr/src/pbuilder/base.tgz] [20:20] Doesn't have to mean that, sure, but... [20:25] /usr/src/pbuilder/result it is === Amaranth_ is now known as Amaranth [21:40] Is there some command to find all packages which I installed from Intrepid? [21:41] (nautilus crashes each time I select an icon and I guess that's because I pulled some libs from there recently) [21:42] RainCT: try apt-show-versions [21:42] geser: thanks [21:48] RainCT: for individual packages, you can also use apt-cache policy [21:49] anyone in here with experience wrt php extension packaging? [22:08] RainCT: have you some time to review a package for me? [22:16] nxvl: hm.. yea, I could have a look. What's the URL? [22:17] RainCT: http://revu.ubuntuwire.com/details.py?package=augeas [22:18] * nxvl HUGS RainCT [22:29] hi [22:44] nxvl: ./missing and ./ylwrap aren't part of augeas itself, or? (they have different copyright holders) [22:46] Can Debian packaging be licensed under a license such as the BSD license? [22:47] * nxvl looks [22:48] Yes AFAIK, i’d suggest using the same (free) license as the upstream. [22:48] right [22:48] i didn't notice them [22:48] * nxvl changes [22:48] ion_: Cheers. [22:50] nxvl: egrep rules ;) /me always uses "egrep -ri copyright *" to find the authors and if the list is very long later adds "| grep -v known_author1 | grep -v known_author2 | etc.." to ensure that he hasn't missed anyone [22:50] RainCT: i was using a different script, thanks for the suggestion! [22:50] nxvl: also, you say where the LGPL is, but not where to find the GPL [22:51] (I mean the "On Debian systems,.." line) [22:51] right [22:53] * RainCT also notes that he uses to remove the "you should have received a copy..." part of the *GPL headers -- but that's just me :) [22:54] nxvl: you have't addressed norsetto's point about the package descriptions being messy [22:54] yes, i did [22:54] * nxvl rechecks [22:55] nxvl: augeas-tools and libaugeas-dev start with "this package" and later has "augeas is"; libaugeas0 and augeas-lenses have it in the inverted order (which is way more common) [22:58] RainCT: uploading new version with the suggestions [22:59] nxvl: and you can remove lines 3-7 from debian/rules [22:59] ah, nvm if you've already uploaded it [23:00] changed anyway in case i need to upload more versions of it [23:00] :D [23:05] ok.. building [23:07] Would like to add/maintain packages in http://sinhala.sourceforge.net/ubuntu/i386/hardy/ could anyone be a mentor? [23:07] RainCT: revu already got last version [23:07] - - Fix configuration file path for grub (Debian systems only). [23:07] + - Fix configuration file path. [23:08] RainCT: but is a debian systems change [23:08] RainCT: the original was a RedHat based sistems change [23:10] * RainCT ment why you have reverted the changelog entry.. the larger one was better [23:11] oh [23:11] yes [23:11] it should be larger one [23:11] * nxvl checks [23:11] oh, you are right [23:12] * nxvl reverts [23:13] reverted and uploading [23:20] RainCT: changes are already in revu [23:24] uhm.. shouldn't "editing" be "edition" in the description? [23:24] RainCT: on which of them? [23:24] jpds: "Augeas is a configuration editing tool" is this right? [23:25] RainCT: it's a c&p from upstream [23:25] RainCT: http://augeas.net/ [23:26] well, upstream doesn't need to be right.. although perhaps it is [23:28] nxvl: I haven't noticed it before but I guess the second paragraph in the libaugeas0 description should either be in all other descriptions or be removed from there. and in augeas-lenses paragraph 2 and 3 say basically the same :P [23:29] nxvl: it looks quite good otherwise, I just need to test-install the .deb's once aptitude finishes what it is doing right now [23:31] mmm i don't remember why i change the -lenses description that way [23:31] but you are right, they say the same in different works [23:31] and the libaugeas0, yes, it needs to be removed [23:31] that's explained on the 1st paragraph [23:47] argh.. there's a nice bug in gdebi :P [23:48] it says [y/N] when it asks for confirmation, but doesn't accept "y" (only the localized version, "s" for Sí) [23:50] that's why i use my system in english and not in spanish [23:50] :D [23:51] well, one of the reasons I do it the opposite is that this way I can find bugs :P [23:51] yes, but if you got an error, in english is easier to find a solution using google [23:51] :P [23:52] and I use ugly paths with spaces and special characters for the same reason.. so when I test a program or write one myself, if it doesn't properly support unicode paths I will notice it :P [23:52] (well, but only for my data, which I usually check with nautilus.. the development stuff has nice, one word paths, as else I'd get mad :P) [23:53] anyway.. how can I check if augtools is working? :P [23:53] yes, but it's a matter of "i want it to work for me" vs "i want to destroy it" [23:59] nxvl: anyway.. how can I check if augtools is working? :P