[00:03] matthijs_: OK, did you set the tag to needs-packaging, and put it in the bug report subject line? If so, then it's just a waiting game, someone will sort it out :) [00:04] yes, I added [needs-packaging] to the start and end of both summary and description [00:05] matthijs_: OK, what bug # is it? [00:06] #187894, [00:06] the id is #187894 [00:07] bug #187894 [00:07] What's wrong with the bot? [00:08] it's not there? [00:08] bug #187894 [00:08] Launchpad bug 187894 in ubuntu "[needs-packaging] veejay-1.0 - http://veejayhq.net [needs-packaging]" [Undecided,New] https://launchpad.net/bugs/187894 [00:08] weird [00:09] it was doing *something* in it's corner. [00:09] matthijs_: Yeah that's fine, I edited the tags to needs-packaging so contributors can have a look, but yeah that's fine for now :) [00:09] it wasn't doing anything, it wasn't in the channel [00:09] lol how did it suddenly come back then? [00:09] by rejoining the channel [00:10] It hasn't been here for about an hour lol [00:10] ubotwo was. [00:10] and, networks sometimes have problems. [00:10] It didn't answer me an hour ago stupid bot lol [00:10] Oh well it's working now :) [00:11] I'm telling ya, he's been at it again, visiting those other channels, talkin' dirty [00:11] oh well, enough for this night. I should go to sleep now, long day ahead tomorrow [00:12] Thank you guys for the help, I wouldn't have figured this out using google I think. [00:12] bye! [00:25] can someone please answer the questions I placed in reply to the comment on http://revu.tauware.de/details.py?package=basic256 ? [00:30] ryanakca: the Debian menu has changed a bit [00:30] ryanakca: you'd need a new enough lintian/linda to check [00:30] LaserJock: ah, ok. [00:31] * ryanakca tries upgrading hardy [00:31] Apps has been replaced by Applications, that's why you get the particular warning [00:31] aha, okies. [00:31] but some categories were also moved around [00:31] so it's good to check [00:32] * ryanakca wonders if the Debian people should be prodded to update http://www.debian.org/doc/maint-guide/ch-dother.en.html#s-menu [00:32] LaserJock: feeling any better tonight? [00:32] nixternal: no way [00:33] LaserJock: and, about the man page? [00:34] ryanakca: I would say do it [00:34] even if it's not that informative [00:34] eh, ok... I guess it wouldn't matter too much if its 90% copy-paste from control/copyright? [00:35] Hi, does anybody here know if there is a gtkglext-1.2 deb file? the ubuntu repo only has version 1.1 [00:41] who was the one with wxformbuilder? [00:41] i was just revu'ing it but had a question for the packager [00:45] superm1: rjmyst3 [00:46] ah yeah he's not online [00:46] okay i'll just leave a comment on the revu then for him to take a look [00:47] Hi, does anybody here know if there is a gtkglext-1.2 deb file? the ubuntu repo only has version 1.1 [00:50] neurostumit: Version: 1.2.0-0ubuntu1 [00:50] neurostumit: in hardy, apt-cache show libgtkglext1 [00:56] Hey guys, I'm trying to build an upgraded upstream, but pbuilder keeps coming up saying that its depends: libgettext-ruby1.8, libgtk2-ruby1.8 and libxul-dev are virtual packages. [00:56] will that work in gutsy? [00:57] ryanakca: will a simple apt-get install libgtkglext1 work then? [01:00] neurostumit: no [01:00] neurostumit: you need to be running hardy [01:00] neurostumit: unless gutsy also has 1.2.0 [01:00] no gutsy's repos doesn't [01:02] Is there a way round this virtual package issue? Any help at all would be appreciated! [01:02] well they didn't a couple of weeks ago [01:04] ryanakca: does apt-cache show libgtglext1 show if gtkglext is available? [01:05] neurostumit: dunno, look on packages.ubuntu.com [01:06] Please help someone this pbuilder is doing my head in!! lol it keeps whinging about virtual packages, dependencies unmet, any ideas anyone please? [01:07] ok [01:07] also is there a way to download a deb file with apt and not install it? [01:09] persia: congrats! Can you add me to u-u-s, please? [01:21] can someone please review http://revu.tauware.de/details.py?package=basic256 [01:24] sorry for the duplicate mail on revu, I received a ProgrammingError and thought the comment wasn't posted... [01:31] pochu: I've had that before. === Elly is now known as hvincent_______ === hvincent_______ is now known as Elly [02:02] ping RAOF [02:05] TheMuso: Would you please add me back as a member of UUS? [02:05] TheMuso: My LP id is kitterman. [02:13] Heya bddebian. [02:14] Heya gang [02:14] Hi ScottK2 [02:15] ScottK2: Hey, you never answered my /query window :-) [02:16] bddebian: I don't think I got it. [02:16] bddebian: /msg me again. [02:16] It was a day or two ago :-) === Ibalon is now known as zakame [02:21] hi all [02:21] Hello freakabcd [02:21] ok, i've got pbuilder setup. and a source package from hardy [02:21] i want to build this in gutsy [02:21] i can make the necessary changes in the control/etc. files [02:22] i just want to know how to build it now [02:22] ScottK2: Just a sec. [02:22] TheMuso: Thanks. [02:23] ScottK2: have you applied? [02:23] hello there, in #ubuntu-hardened is avaiable a bot (nick ubuSecurity) that paste in realtime CVE advisory, bugtraq advisory and milw0rm POC. if someone is interested please join. :) [02:23] TheMuso: Do I need to? [02:24] ScottK2: No [02:24] TheMuso: No. I haven't. [02:24] ok [02:24] Done. You should receive an email about it shortly. [02:25] Thanks. [02:25] np [02:32] TheMuso: can you add me, too? (blueyed on LP) [02:32] you cannot apply there, btw. [02:33] Hey guys, I'm getting an error during pbuilder from my rules file: install -o0 -g0 -m 0644 LWP.pm debian/tmp/usr/share/perl5/LWP.pm [02:33] install: cannot stat `LWP.pm': No such file or directory [02:33] any ideas? [02:33] blueyed: People have done so, but I'll add you directly [02:33] oops sorry scrolling [02:34] blueyed: done [02:34] mcisbackuk: Whatever package provides that file you need to build-dep on. [02:34] TheMuso: thanks [02:34] TheMuso: Thanks. [02:34] np [02:34] * Hobbsee waves [02:34] Heya Hobbsee. [02:34] heya Hobbsee [02:35] ScottK2: How do I find that out? Google it? [02:36] mcisbackuk: apt-file find LWP.pm [02:37] That'll narrow it down. [02:38] ScottK2: Brilliant thanks :) === Aloha__ is now known as Aloha === asac_ is now known as asac [03:07] can someone please review http://revu.tauware.de/details.py?package=basic256 ? [03:25] ryanakca, i left you a comment on revu [03:27] * jdong wonders if we can adapt REVU into a dating service [04:00] jdong: lol [04:00] superm1: thanks [04:01] superm1: if I upload, can you check & advocate please? [04:07] hmm... revu only scans every 10 minutes by the looks of it... [04:08] * ryanakca wants time to move faster so he can go to bet [04:08] s/bet/bed [04:08] persia: You on? [04:10] can someone please review http://revu.tauware.de/details.py?package=basic256 ? [04:10] * ryanakca => bed :) === Hobbsee_ is now known as Hobbsee === Hobbsee` is now known as Hobbsee [05:05] If anyone is looking for a security upload to do, Bug #174615 needs fixing in Dapper/Edgy/Feisty/Gutsy. [05:05] Launchpad bug 174615 in heimdal "[heimdal] [CVE-2007-5939] possible remote vulnerability of unknown impact via an invalid username" [Undecided,Fix released] https://launchpad.net/bugs/174615 [05:09] superm1: Thanks for the review! I just uploaded a wxformbuilder package with the versions fixed. [05:09] rjmyst3, great! [05:09] i'll take a look in a moment [05:09] thank you [05:10] rjmyst3, so this is like an advance release upload :)? [05:10] yes [05:11] superm1: i am an upstream dev [05:11] cool. okay i'll upload it to the archive then. thanks a bunch :) [05:11] thank you [05:12] superm1: does this mean that it will be in hardy? - sorry, this is my first package, and I don't know if there are more steps or not [05:12] rjmyst3, this is it for steps on your end [05:13] archive admins need to look it over still [05:13] and if there are any issues they will contact both you and me [05:13] me since i'm sponsoring the upload [05:13] and you for the issues [05:13] but it should be in hardy yes. [05:13] ok [05:13] i'll keep my fingers crossed [05:13] thank you for your help [05:14] when will I know for sure? [05:14] (or how?) [05:15] rjmyst3, you'll get some email if there are any concerns [05:15] otherwise you can keep an eye on the NEW queue [05:16] to see once it gets accepted [05:16] there are two stages to it getting accepted, first the source package [05:16] then it will build [05:16] and then they accept the binary packages that are generated [05:16] https://launchpad.net/ubuntu/hardy/+queue [05:16] you can see its now at the top of the list on the queue [05:18] yes [05:18] i see that [05:18] those queues are processed on a regular basis, but they are only one of the tasks of archive admins, so it might be there for a week or so [05:18] ok [05:19] then it will move to accepted or rejected? [05:19] once it's accepted, it will automatically go into build mode [05:19] and the binaries will show up in there [05:19] ok, i understand now [05:20] thank you very much, i'm off to bed now [05:20] thanks for your contribution :) [05:20] night [05:20] your welcome - good night [05:45] :) [05:53] persia: I think we ought to add debmake to our list of packages to get removed from Hardy. [05:53] It looks like an easy enough one to knock off. [05:54] haha apparently laserjock, persia and you ScottK2 talk the most in here :D [05:54] :P [05:55] was there a scientific way you determined that? [05:55] http://core.joejaxx.net/~joejaxx/ircstats/freenode/ubuntu-motu/ [05:56] * superm1 wonders how persia is the in the top 10 for activity for all hours of the day [05:56] Lol [05:57] apparently his nick is the in the top 5 for said phrases [07:00] please review http://revu.tauware.de/details.py?package=sadms :) === nenolod_ is now known as nenolod [07:11] Good morning [07:11] warp10, morning! [07:12] Hey Aloha [07:12] hi, i have a bug with a fix from upstream & needs someone to bring it into ubuntu [07:13] 184505 [07:14] geser: Heya, I was taking a look at a package you uploaded, OnScripter , and I was interested in possibly updating it. I am not familiar with packaging yet, but I thought this might be a good way to learn about it. [07:15] malone 184505 [07:15] Launchpad bug 184505 in jppy "jppy fails to launch" [Undecided,New] https://launchpad.net/bugs/184505 [07:17] There is a June2007 version out now, compared to the existing Oct2005 version in the Ubuntu universe repository. [07:27] Wowz, there is even the original Japanese version that was updated just today. It's still a very active project. [07:28] Heh - and the Japanese version is already in Debian repositories. [07:29] Aloha, i left you some comments [07:29] superm1, thank you [07:33] superm1, how do i prevent stuff from being installed into /usr/local? [07:33] Aloha, typically you have to pass --prefix=/usr [07:33] to your configure script [07:35] superm1, isn't that upstream? [07:35] Aloha, you can override lots of things with parameters [07:35] it is done at a packager level though [07:35] superm1, how so? [07:37] well this package of yours is a bit interesting [07:37] it doesnt have a configure script [07:37] well then what you will need to do is patch the Makefile [07:38] so your package will need to adopt a type of patching system to do that [07:38] superm1, i don't know how to do that. can you point me to the right place? :) [07:39] this will get you started here: https://wiki.ubuntu.com/PackagingGuide/PatchSystems [07:42] superm1, thnx [07:45] superm1> Is a configure script required, though? [07:45] LucidFox, no its not [07:45] and in this case there isn't one [07:46] i was just generalizing that one normally is around for passing parameters [07:46] or is the Makefile hardcoded to use /usr/local as a prefix? [07:46] the Makefile is hardcoded [07:46] Eep. [07:53] so i should send the patch upstream to help them out yeah? [07:53] superm1, so in my patch i'm changing /usr/local to /usr in the Makefile correct? [07:54] Aloha, your patch will remain local to the package [07:54] because upstream distributes it like that so that people can install without disturbing /usr === soren_ is now known as soren [07:54] gotcha [07:54] it is bad that they dont offer a configuration facility [07:55] so if you wanted to provide them with a patch that did that, that would be of use to them [07:55] but probably more effort than its worth after looking at their build system [07:55] superm1, heh [07:55] Aloha, but yeah you need to change any instance of /usr/local to /usr [07:55] and it looked like you might need to define prefix = [07:55] you'll have to experiment and see what works out [08:03] superm1, how do i debhelper the changelog? [08:03] Aloha> dh_installchangelogs changelog_file_name [08:03] good morning [08:03] dholbach, morning! [08:03] LucidFox, thnx [08:03] heya dholbach [08:04] good [insert time of day here] :) [08:04] hey Aloha, emgent [08:11] superm1, my debianrules file has a debhelper for the changelog [08:11] s/debianrules/debian\/rules [08:12] hm [08:12] interesting [08:12] well dont worry about that right now then [08:12] superm1, ok [08:12] superm1, i created the patch for the Makefile [08:13] superm1, i don't know how to fix pam_parse.awk failing syntax checks. i don't know what that means [08:13] Aloha, you will probably have to make patches for the other things i've listed too [08:13] either that or modify that behavior in debian/rules [08:13] i got several of those things i listed from running linda or lintian on the resultant deb [08:13] superm1, that other stuff was in the Makefile also [08:14] after you build it [08:14] which tells you a lot about what is wrong with the build and needs to be improved upon [08:14] and in some cases points you at how to work on those types of things [08:15] superm1, cool. what arguments do you give them? [08:16] Jan 25 04:56:08 superm1: I use lintian -iIv and linda -v -f long -t E,I,W,X, but those are only a subset of my review checks. [08:16] those are quoted from persia [08:16] superm1, thnx [08:17] its times like these i love the xfce notes plugin ;) [08:18] superm1, how do you build the packge to run lintian and linda on it? dpkg-buildpackage -rfakeroot? [08:18] Aloha, i build my packages in a pbuilder [08:18] and then i run linda /lintian on the .changes file [08:18] that is created [08:19] that runs it on all of the debs that are produced from the pbuilder run [08:19] superm1, oh i didn't know builder creates .changes file. whats the syntax for that? sudo pbuilder build .dsc? [08:19] s/builder/pbuilder/ [08:20] Aloha, yeah it does create .changes files [08:20] cool [08:20] depending on how you configure your pbuilder that would be a possible command to run [09:01] hi there [09:02] can any REVU admin re-sync the REVU uploaders keyring? :) [09:02] foolano: yo [09:02] isaac: doing [09:02] Hobbsee: thanks [09:02] er, attempting to do [09:06] hm, would help if i ran the right script, i'll bet... [09:06] hi isaac [09:06] Hobbsee: I reckon it might help ;) [09:06] this output looks more promising :) [09:06] brill [09:07] its helps to debuild before you run pbuilder hehe..... /me smacks forehead [09:07] no wonder why it didn't update [09:08] hehe [09:08] this si why i used to like pdebuild [09:09] i don't want to repartion my disk just to build packages. especially when i don't know what i'm doing ;) [09:09] TLE, hi :) [09:09] ivoks, hihi :) [09:09] buahahaha to you too :) [09:10] buahahaha? [09:10] hallo [09:10] Hi, TLE :) [09:12] soren: virt-manager in hardy got special attention from phoronix :) [09:12] "phoronix"? [09:12] soren: http://www.phoronix.com/scan.php?page=article&item=983&num=1 [09:12] Hobbsee: so I should be able to upload to REVU already, right? [09:13] isaac, welcome to REVU :) [09:13] :) [09:13] Aloha: thanks [09:13] ivoks: Oh, nice. [09:13] isaac: it's still not finished [09:13] Hobbsee: I still have some work to do in the package [09:13] so it's ok :) [09:14] Aloha: I am hoping for a "quick" welcome to MOTU ;) [09:14] isaac, are you an experienced packager? [09:14] Aloha: I have been a debian developer for three years IIRC [09:14] Aloha: but I have switched to ubuntu now [09:14] isaac, cool glad to have you on the right side ;) [09:14] soren: thinking about dovecto/postfix, i think we should give up on modifing main.cf trough init script [09:15] Aloha: haha [09:15] Aloha: both sides are right ;) [09:15] soren: no one likes that :/ [09:15] isaac, thats what i said ;) [09:17] ivoks: I think it's kind of sexy. [09:18] soren: ...and wrong :D === txwikinger2 is now known as txwikinger [09:50] if upstream has a debian based tarball do we do -0ubuntu1? i couldn't find the actual upstream in debian repos [09:53] Aloha> Debian-based tarball? [09:53] LucidFox, yeah its a tarball of the source with a debian directory in it [09:54] Aloha> Then repackage the tarball and remove the debian/ directory from it [09:54] note it in debian/copyright, and add a get-orig-source rule to automate this [09:54] LucidFox, ok i'm thinking i shoulda started with that since the main tarball tries to build based on distribution [09:55] its getting really complicated heh [10:03] That's one really borked upstream build system [10:06] yeah [10:06] it tries to build a package of itself and then install the package [10:06] wtf? [10:06] heh [10:15] what if upstream doesn't include man pages for their binaries? how do i solve that? [10:19] write one :) [10:19] yay ;) [10:19] all the docs are html files... blah [10:20] * Aloha looks for html2man [10:27] hi jono [10:27] heya Hobbsee [10:28] moring everuyone [10:28] jono: taken over the world yet? [10:28] Hobbsee: nearly there :P [10:28] heh, nice work [10:29] * Hobbsee should do something useful, like cook dinner and write email. [10:29] Hobbsee, or chat ;) [10:29] no, tha'ts nto really useful :) [10:30] Hobbsee, it stimulates your need for artificial interaction ;) [10:31] thats kinda useful [10:31] heh [10:31] yeah well, there is that [10:31] * Hobbsee has always been somewaht of a hermit anyway [10:32] * Hobbsee used to only say around 20 words a day, at all. [10:34] * jono starts on the packaging guide again [10:35] jono, rewriting it? [10:35] Aloha: nope, learning it :) [10:35] jono, oh. :) its fun :) [10:35] :) [10:35] jono, i learned how to patch today. woohoo [10:36] wicked :) [10:37] i still can't get over this build system [10:38] its like a self replicating robot. it finds what system you're running and it packages itself to that spec and then installs the package [10:38] nuts [10:40] * persia rings the bddebian gong [10:41] superm1: The trick is being absent for spans across sampling periods. [10:41] blah [10:41] ScottK: I completely agree. There's actually a few packages that lintian recommends we purge that I think are achievable. [10:41] ehm people.. [10:41] http://blog.emanuele-gentili.com/images/google_love_kubuntu.png [10:41] see this. [10:42] the only problem with this build is that the resulting package totally violates debian policy in like every way possible [10:51] quick question [10:51] jono: Just ask (and I doubt I will provide a short answer) [10:52] can someone be a packager and not have programming experience? as in...could I look at bugs with patches attached and apply the patch and do an upload without having to hack on code? [10:52] or do MOTUs need programming experience? [10:52] Yes, very much so. [10:52] good stuff :) [10:52] There are several classes of bugs. Some just require a little investigation as to what happened, and a set of rebuilds in the right order. [10:53] jono, note that experience with diff and patch is rare without programming (at least scripting) experience [10:53] Some require small adjustments to packaging: perhaps the build-dependencies, the description, patches to correct spelling, file installation locations, etc. [10:53] gotcha [10:53] I am thinking of new MOTUs who have never coded [10:53] sorry, new "potential" MOTUs [10:53] Having experience with make or shell scripting is a big advantage, as it allows one to start working on bugs with maintainer scripts, debian/rules, etc. [10:54] right [10:54] From there, it gets more complicated, either code integration issues (local coding) or bugfix patches (which likely should be pushed upstream). [10:54] thanks :) [10:54] is it clear with the bug what kind of fix it needs? [10:54] In many cases, upstream already has a fix, and some discussion with upstream, and the application of the patch, and some testing is enough to resolve the bug. [10:54] or do I need to check the patch? [10:55] It's not always clear. Bugsquad processes about 1000 bugs a week, but those don't always reach a state of sufficient triage to be obvious. [10:56] You should always check the patch to see if it makes some sense. Even if you don't know the programming language, there should be some relation between the patch and the bug (and if there isn't, ask the patch author for some explanation). [10:56] is there a triage label or tag that indicates the complexity of the fix? [10:56] right [10:56] good stuff [10:56] This is more because you want to know what you signed: kind of like reading contracts before you sign them. [10:56] wise [10:56] :) [10:56] thanks persia [10:57] you read contracts? ;) [10:57] There's not really such a tag. Bugs that appear obviously easy get the "bitesize" tag, but there's lots of easy bugs that aren't tagged. Well understood bugs are usually status: triaged, but that doesn't mean they are easy to solve. [10:57] Aloha: Are you free next wednesday? I have a business proposition. [10:57] persia, heh [10:58] persia, i'd almost be tempted to take up your offer just to see where i end up ;) [10:58] Anyway, about bugs, my recommedation is that people interested in helping with development get involved with bugsquad (in #ubuntu-bugs: there are people there despite the bot) to get a better handle on how the bugs are organised, etc. [10:59] Also, this often gives a first chance to grab the easy ones, and get a good list of fixes in the archive, which can be satisfying. [11:00] Aloha: Please send me private email with details of a hotel reservation near you, and information regarding with whom I should arrange for transportation. I'll present the opportunity, and bring along some paperwork. [11:01] persia, which hotel do you want? Theres like 1000 here [11:02] * persia puts away the bait & tackle [11:15] so, apparently slicing your fingers open is a bad idea. [11:18] soren: I have uploaded a package called unblock-signals to REVU, which is needed to fix a problem in ebox related to apache2 blocking some signals , I am not sure if foolano has told you about it [11:18] Hobbsee: Generally. Lots of nerves and stuff. If you're just curious about the contents, someone else's fingers are recommended. [11:18] isaac: He hasn't. [11:18] soren: thing is that apache2 blocks some signals [11:19] soren: and then sometimes gconfd2 is spawned from inside apache2 by libgconf [11:19] erk.. [11:19] Ok. [11:19] soren: and it doesn't unblock these signals so it's impossible to terminate it gracefully [11:19] i filed a bug in gnome's bugzilla [11:19] this is the only workaround we have managed to think of that doesn't involve modifying any other package [11:20] Modifying other packages is not out of the question. [11:20] At all :) [11:20] soren: the thing is the package we would need to modify is gconf [11:20]