[00:18] Getdeb Founder interviewed Topic => http://ubuntuforums.org/showthread.php?t=1038224 === Halph is now known as coppro [00:33] hi [00:33] someone know why if i type this [00:34] sudo debdiff slingshot_0.8.1p-1.dsc slingshot_0.8.1p-1ubuntu1.dsc > slingshot_0.8.1p-1ubuntu1.debdiff [00:34] it doesn't work [00:36] well, you don't need to sudo it, for a start [00:37] yes [00:37] but says [00:37] bash: slingshot_0.8.1-ubuntu1.debdiff: Permiso denegado [00:37] and i can't understand [00:37] must be my error, but i can't see i [00:37] it [00:37] then chown it to your user? [00:38] ops [00:38] hehe [00:38] dont worry :) [00:39] i do it like root [00:39] but it was chown error === _neversfelde is now known as neversfelde [00:50] So! Who wants to review nouveau-kernel-source! Simple, fun, and makes a very nice open-source nvidia driver installable in Jaunty! http://revu.ubuntuwire.com/details.py?package=nouveau-kernel-source [00:51] RAOF, is it dkms based? [00:51] Yes. [00:51] Which is mich easier than the wiki page suggests, it turns out. [00:52] directhex: If you haven't seen a dkms-using package before, I'd suggest checking it out. It's a good example, I think. [00:53] * Hobbsee clubs RAOF with a dead ferret [00:53] Hobbsee: Sadness. [00:53] Ferrets are awesome. They shouldn't be dead. [00:54] * RAOF tickles his ferret. [00:54] RAOF: gnome-do keeps flipping back to open for the ssh. Fix it, and I won't kill the ferrets and club you with them ;) [00:54] i didn't know you had a ferret. I'd like to see this! [00:54] * directhex feeds RAOF's ferret some cat food [00:54] Hobbsee: You mean my bug? [00:55] * RAOF doesn't _actually_ have a ferret. [00:55] StevenK: yeah. But now i'm actually being able to reproduce it [00:56] Woot [00:58] * RAOF files "SSH Hosts shouldn't be openable" against do-plugins, and does some bug gardening there, too. [00:59] Yay RAOF! [00:59] well, they should be openable. just, they should never be the default ;) [00:59] But nothing _happens_ on open, right? [00:59] * Hobbsee finds it useful to have a GUI for browsing remote machines, sometimes. [00:59] no, it opens / on the destination machine. [01:00] in nautilus. Works a charm when you actually want it to do that. [01:00] Oh, sweet. That's broken here, sadly. [01:00] or at least, did last time i tried it [01:00] Yeah, that's what it's _trying_ to do. [01:01] We may need to give it some gvfs love to make it work better, but that's what it's trying. [01:02] The relevance engine is next up on getting an overhaul. That should make this better. [01:16] * RAOF hopes he missed someone volunteer to review nouveau ;) [01:17] the qemu pkg dependencies is now ok with universe [01:17] now i run into a new issue: dpkg-source: error: unrecognized file for a v1.0 source package: qemu_0.9.2svn6277.orig.tar.bz2 [01:18] are .tar.bz2 not allowed anymore? [01:18] debian etch eats it! [01:20] Really? I thought that was reasonably recently introduced in dpkg. [01:23] debian etch works, but lenny not. [01:24] that is the strange thing [01:24] hmm, no. [01:24] bz2 is supported in dpkg, but not by the archive stuff [01:24] so you can create a local bz2 package, but not upload it [01:25] so i run into a new consistency check not present in etch? [01:28] quite possible [01:28] not upload it to the debian build system or the ubuntu build system? [01:29] so i should go back to .tar.gz then? [01:30] source files...? [01:32] Yeah; repack it to a tar.gz === hyperair1 is now known as hyperair [03:15] * ScottK does a cruft cleaning victory dance. 5 removal bugs done of his today. [03:15] Thanks slangasek [03:15] Congrats ScottK === hyperair1 is now known as hyperair === hyperair1 is now known as hyperair === hyperair1 is now known as hyperair [04:13] RAOF: how much time / skill would I need to review nouveau stuff? [04:14] pwnguin: Time? Dunno; depends on how fast you are at copyright sweeps. Probably a couple of hours. It's not very complicated packaging. [04:14] i guess the other thing is, im not motu [04:17] That is, of course, awkward. You're welcome to give it a once over; if you find anything I can fix it before someone who could advocate it needs to look at it. [04:17] RAOF: how much crack is it on? is it a new package, or waht? [04:18] persia: do you know where a schedule of the asia board meetings is? [04:18] persia: I keep misssing them cause announcements are sent after I finish work, and I don't read email in the evenings generally [04:18] lifeless, I only know of the one in my head, which goes 15:00 today, 9:00 on the 20th, 15:00 on the 27th, etc. [04:18] Hobbsee: It's a new package. It's not really on any crack at all. [04:19] UTC? [04:19] lifeless, I don't know how far in advance amachu has posted to the fridge. [04:19] Yes, UTC. [04:19] Hobbsee: Packaging-wise, at least. It's quite simple. [04:19] ok, well I won't be at todays [04:19] thats 2am [04:19] No, don't imagine anyone from the east will be there. [04:19] Hobbsee: It's also fairly safe; it shouldn't break anything for anyone. [04:19] I'd like a ical feed for these [04:19] hrm... [04:19] could you bring that up please [04:20] persia: ^ [04:20] An iCal feed? [04:20] * persia knows almost nothing about iCal [04:20] * nhandler still wishes the fridge would make their ical feed work with gcal [04:21] nhandler, It's an issue with the drupal plugin. Feel free to chase the bug :) [04:21] persia: I know it is. I don't have enough experience with drupal or ical to tackle this one. [04:23] RAOF: will there be gnome-do fixes if it gets reviewed? :P [04:23] nhandler: yeah, gcal is what I need [04:23] Hobbsee: There'll likely be a new gnome-do release if it gets reviewed, with plenty of shiny? [04:23] will it fix the ssh connect issues? [04:24] and how likely? :P [04:24] Probably not; that's related to something deep in the core. [04:24] awww [04:24] We can't really pin something to the top of the priority for a specific item at the moment. [04:25] ah [04:25] Improvements to the relevance, including per-element relevance (so the fact that you use "open" a lot on files doesn't affect your ssh hosts), are coming after the next release. [04:26] woot! [04:26] hand me a URL then, and i'll attack you with a rubber chicken if the copyrighting is wrong ;) [04:26] http://revu.ubuntuwire.com/details.py?package=nouveau-kernel-source [04:29] * Hobbsee blinks [04:30] That bad? [04:30] i just looked at the legal page [04:31] I think I've got them all covered, but yeah. [04:33] Damn. I should have just stolen the copyright from the kernel! That's where all those files normally end up! [04:34] * Hobbsee wonders why debian/install is needed [04:35] oh, you don't dump them all in the same place. [04:37] RAOF: presuambly one needs to update the debian/snapshot_hash when updating the package? [04:38] Hobbsee: I thought I set up a target to refresh that. [04:38] Let me check. It's been sitting there a while :) [04:38] Hobbsee: The get-new-snapshot target generates snapshot_hash [04:38] oh, so you do [04:39] Wow. That's quite a lot less trivial than I remember ;) [04:39] RAOF: I didn't check copyright, and I didn't try building it, but I can't find anything wrong with it. [04:40] I'm reasonably certain copyright is OK. Older versions of many of the files in there are in the kernel tree already, and the rest have clearcut copyright. [04:44] Want to upload or ack it, then? :) [04:44] RAOF: i'm assuming the answer is "no", but this doesn't require internet access while building the binaries, does it? [04:44] anyone know if dh_zope adds python to the dependencies itself? [04:44] No, it doesn't. [04:44] Hobbsee: ^ [04:45] oh good [04:45] does it need to ? as python is implied by zope.. [04:46] lifeless: Do packages which call dh_zope also call dh_python? [04:46] no [04:47] Should they? [04:48] I think it may 'depend' :P [04:49] Another query: where is dh_zope, exactly? [04:50] apt-file search dh_zope comes up empty. [04:50] Or are you writing a dh_zope yourself? [04:51] Hobbsee: BTW, it should be safe for you to build and install the package. [04:52] RAOF: that's what i'm tryingnow [04:53] Worst case: it kills your 3d :) [04:57] RAOF: found some interesting bits in the build log [04:57] Oh? Pastebin? [04:57] dpkg-source: info: building nouveau-kernel-source in nouveau-kernel-source_0.0.11+git20081220-0ubuntu1.dsc [04:57] debian/rules build [04:57] tail: cannot open `/usr/bin//changelog' for reading: No such file or directory [04:58] dpkg-parsechangelog: failure: tail of /usr/bin//changelog gave error exit status 1 [04:58] the last 2 lines repeated another 6 times [04:58] Ah, right. [04:59] It's trying to evaluate CURVER. I don't know why. [04:59] warning, `debian/nouveau-kernel-source/DEBIAN/control' contains user-defined field `Original-Maintainer' is a little odd too, as i can't see why [04:59] Hobbsee: Because it's got me as the original-maintainer? [05:00] I probably shouldn't be there. [05:00] RAOF: well, i'm not sure why it's cut off the XSBC- part [05:00] Because it's in the binary already? [05:00] ah, fair enough [05:01] W: nouveau-kernel-source: script-not-executable ./usr/src/nouveau-0.0.11+git20081220/scripts/create_bsd_pci_lists.sh [05:01] W: nouveau-kernel-source: script-not-executable ./usr/src/nouveau-0.0.11+git20081220/scripts/create_linux_pci_lists.sh [05:01] W: nouveau-kernel-source: old-fsf-address-in-copyright-file [05:01] fwiw [05:04] Hm. I wonder why those scripts don't come executable from git. [05:14] RAOF: it seems the other two in that directory did - just not those. [05:15] Yeah. I can fix that in get-orig-source if you think its worth it. [05:15] meh [05:16] RAOF: advocated. [05:18] Hobbsee: Sweet! I'll upload now. Nouveau can be installable for Alpha 3! [05:19] :) [05:19] that's if it gets thru the new queue [05:19] Well, yeah. I guess so. [05:29] Hobbsee: And uploaded. Thanks muchly! [05:29] RAOF: you're welcome [05:30] Hi. I'm upgrading a package to a new upstream version, and of the 2 patches that the package had is not used anymore. Should I remove the patch from the debian/patch or just delete from the series file? [05:31] "and ONE of the 2 patches" === hyperair1 is now known as hyperair [05:35] To push the bzr tree for that packaging I first need to create the launchpad project, don't I? Has that changed with packagebranches yet? === hyperair1 is now known as hyperair [05:48] RAOF, You might want to ask james_w that, in several hours :) [07:00] Hi room, I've just made my first debdiff to patch this bug: https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/211798 How do I go about getting it off my computer and into the stream? [07:00] Ubuntu bug 211798 in jack-rack "jack-rack open file hangs" [Undecided,Confirmed] [07:01] should I first post it to the bug as an attachment? or is there a review process? [07:02] stochastic: If you have tested it and it works well for you, post it to the bug as an attachment. [07:10] jmarsden, okay it's uploaded, is that all I need to do? [07:10] stochastic, Once the patch is uploaded, subscribe ubuntu-universe-sponsors to the bug. [07:11] okay, will do [07:45] morning o/ [07:54] james_w: ping, re: where to push bzr packaging to in these sourcepackage-branch laden days. [08:10] james_w: well, adding it in Debian will need NEW again, so I guess it will be easier to add small diff in Ubuntu === azeem_ is now known as azeem === ziroday` is now known as ziroday [08:36] james_w: added the additional info you needed to bug #316092, thx [08:36] Launchpad bug 316092 in ampache-themes "New Ampache themes" [Undecided,New] https://launchpad.net/bugs/316092 [09:17] <_ruben> is there a way to override the installation of packages listed in Recommends: ? [09:18] _ruben, yes, apt-get has an option to either disable it by default (if you put it in a config file) or per use (if you use the -o option); I forget what the option is called, though [09:19] _ruben: In aptitude? Certainly. List the package with a minus next to it (sudo aptitude full-upgrade idontwantyou-) [09:19] * _ruben reads the manual one more time [09:19] <_ruben> using apt-get [09:20] <_ruben> --no-install-recommends .. doh .. wonder how i could miss that :p [09:21] --without-recommends ? [09:25] good morning [09:28] asac: I have a question regarding tuxguitar merge. tuxguitar launcher script looks for libxpcom.so (needed for documentation browser) in /usr/lib/xulrunner-1.9. But the installation of xulrunner on ubuntu is done in /usr/lib/xulrunner-1.9.0.x. How do I solve the problem of libxpcom.so lookup? [09:28] dholbach: good morning. [09:28] hiya slytherin [09:29] hi room, I'm in the process of stepping through packaging tutorials in an attempt to build a .deb for the calf plugin pack here: http://calf.sourceforge.net/ and I'm wondering if someone can walk me through the depends and build-depends sections of the control file [09:31] stochastic, what you want to know about them? [09:32] I'm not sure on what the difference between build-depends and depends fileds [09:32] stochastic, erm... do you need gcc to run nano? [09:34] okay, should I just guess at the libraries required to run these plugins? [09:34] or are there systematic means of figuring it out? [09:34] stochastic, depends is for what the package needs when a user uses it; build-depends is what you need when you build it [09:34] stochastic, generally, you should use substitution variables and a sufficiently smart packaging helper tool for them to be calculated [09:35] stochastic, shared libraries are usually determined automatically (rare exceptions exist); other stuff you mostly have to figure out by reading the source code [09:35] directhex, sorry I'm BRAND new to this packaging thing [09:35] stochastic, or by experimenting [09:35] ${shlibs:Depends} is a good thing to depend on [09:36] it's populated by something, probably dh_makeshlibs in debian.rules [09:36] dh_shlibdeps [09:36] dh_makeshlibs is for libraries to *make* them [09:37] okay, so I only need to take the dependencies listed here: http://calf.sourceforge.net/?id=2 and find suitable packages in Ubuntu's repos and put those into build-deps [09:37] yeah, close enough [09:37] if your packaging helper is smart enough, you shouldn't even need to care about which dh_foo to run [09:37] stochastic: Just make sure you put the development libraries in the build-deps. [09:37] debhelper 7 for the win [09:38] StevenK, yes! [09:38] now when it says it requires Expat XML parser, should I include the dev libraries, or the expat executable? [09:38] it's even mono-friendly, and does ${cli:Depends} [09:39] stochastic: The development libraries, since things usually link against it [09:40] I'm learning off the youtube videos by dholbach, but they kinda gloss over this section [09:48] stochastic: when you are need a library for building your program, you usually need -dev package of that library since that is where all the header files lie. [10:15] hi again, I'm having further difficulties with build-depends in that same package when it comes to pbuilder [10:15] I get a whole bunch of is a virtual package errors and it fails to build [10:16] like ladspa-sdk and dssi-dev and libjack-dev [10:17] am I missing something obvious, or am I using the wrong packages? [10:18] stochastic: I believe you don't have universe enabled in your pbuilder [10:19] ok, that makes sense [10:19] how do I fix that? [10:20] RAOF: there's not a special place on launchpad yet, so either under the project, or under your +junk [10:20] james_w: OK. Which means creating the project, I guess. [10:21] stochastic: I believe the fix is to edit your ~/.pbuilderrc and then run "pbuilder update --override-config" [10:21] stochastic: I've never had to do it though, so that might be nonsense [10:21] RAOF: yeah, you could use your +junk, but creating the project can be useful for other things, such as bug watches [10:22] Yeah. [10:22] james_w, I don't have a ~/.pbuilderrc [10:25] stochastic: https://wiki.ubuntu.com/PbuilderHowto#Universe%20support [10:38] james_w: we shouldn't be doing sponsoring at the same time :) [10:38] mid-air collision on bug 316536 [10:38] Launchpad bug 316536 in nted "Please sync nted (1.4.17-1) from debian unstable" [Wishlist,Confirmed] https://launchpad.net/bugs/316536 [10:38] :-) [10:38] although you were quicker :) [10:38] at least we agreed :-) [10:38] yeah [10:39] I'm on gpsd and ampache-themes now [10:39] netkit-telnet [10:40] pff, main :-) [10:40] hehe, right [10:41] * dholbach does metacity next [10:45] you should set them to in progress when reviewing! [10:48] on goocanvasmm now [10:48] Laney: you can still have issues even then, but yeah it would help a bit [10:55] on azureus [10:59] hmm, still on with this package I'm trying to build, it didn't seem to generate any dependencies; my debian/control file had: dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}, ${misc:Depends} [11:01] stochastic, you're probably missing something earlier in your debian/rules file; can you post it to paste.ubuntu.com? [11:03] here it is: http://paste.ubuntu.com/104333/ [11:03] just what was automatically generated [11:06] stochastic, I think you want to uncomment the line that calls dh_makeshlibs [11:07] I'll try that, anything else? [11:07] not immediately [11:13] liw, I still get the same issue [11:13] stochastic, hmm [11:14] stochastic, can you put the entire source package up somewhere so that I can play with it to see what the problem is? [11:14] stochastic: turning on DH_VERBOSE may give some clues [11:15] what would you like, any of my packaging work, or just the source of the application? [11:15] stochastic: dh_shlibdeps is the call that should add ${shlibs:Depends} [11:17] james_w, should I just put the dh_verbose on line 75? [11:18] stochastic: nope, at the top of the file is a commented-out call to "export DH_VERBOSE=1" if you uncomment that the dh will tell you more about what it is doing [11:18] the trace may be informative about why that variable isn't getting set [11:26] here's the entire output of pbuilder with verbose on: http://paste.ubuntu.com/104339/ [11:26] I don't see anything obviously tracing that error [11:26] the error is way down at the bottom [11:27] stochastic: the issue is that the install rule doesn't actually install the program [11:28] it install the header files, and a few other things, but doesn't appear to install calfmakerdf etc. [11:28] oh [11:29] at least I assume that is what is supposed to happen [11:36] liw, I've tarred the whole kit and kaboodle up and it's here to download if anyone wants to fiddle: http://rapidshare.com/files/182751716/calf-packageAttempt.tar.gz.html [11:38] it does look like the calfmakerdf is moved at lines 1128, 1132, etc.. and besides these are audio plugins so they're not really designed as an executable standalone [11:40] stochastic, I'll have a look [11:42] well thank you all for the insights that have gotten it this far, unfortunately I do need sleep [11:43] liw, if you find something I'm missing, or any explanation please e-mail me (e-mail is in the packaging) as I'd love to know where I took a misstep [11:43] stochastic, sure [11:48] stochastic: dh_makeshlibs is not the command you should use, rather dh_shlibdeps [11:55] the usefulness of quilt suddenly becomes apparent, when looking at an rpm spec file with 54 patches in it [12:00] hmm, stochastic's package doesnt end up with a substvars file [12:09] which seems to be because he installs into debian/calf rather than debian/calf-plugins [12:10] fixing that, there's still a complaing about misc:Depends === nhandler_ is now known as nhandler [12:12] but that seesm to be fixed in newer debhelpers so that's ok === in[v]aleed is now known as invaleed [12:34] jpds: hi, FYI, I just added a tool to create credentials for the launchpad API to lp:~thekorn/ubuntu-dev-tools/use_launchpadlib === foursixnine is now known as santiago-ve [14:16] hm, looks like my new ikvm packaging did the trick - i can't imagine the old package would have been able to gobble a gig of ram on the armel buildd during compile [14:21] you da bomb [15:11] doko: ping [15:17] dholbach: ping [15:18] quadrispro: pong [15:20] mok0: contentless pong [15:20] doko: oh, just going through my bug list, and bumped into bug 308194 [15:20] Launchpad bug 308194 in lxml "[intrepid] Exception importing etree module" [Undecided,Confirmed] https://launchpad.net/bugs/308194 === ogra_ is now known as ogra [15:22] doko: I will make a patch for intrepid, ok? [15:23] mok0: sure [15:33] doko, did you remove cython building from lxml? [15:34] if universe sponsors hang about over here, where to main sponsors hang out? [15:34] apw: in -devel [15:35] mok0: yes [15:35] mok0, thanks :) [15:35] doko: OK. It was my impression that you didn't like that [15:35] apw: It depends a bit. You can also find people in #ubuntu-server, #ubuntu-desktop, and #kubuntu-devel depending on the package. [15:36] pm-utils and apport [15:36] so i'll try -devel [15:38] mok0: did I say that? hmm [15:38] apw: I doubt anyone other than pitti is going to touch apport unless it's an emergency. [15:39] doko: you said something like "if lxml can't be built from source it should leave Debian" [15:39] yeah, think he is away from keyboard this week [15:43] Someone who knows a bit of Python and is looking for a bug to fix, might want to look at Bug #316674 [15:43] Launchpad bug 316674 in catfish "catfish can't find on path containing whitespace" [Medium,Triaged] https://launchpad.net/bugs/316674 [15:45] ^^ I can check/sponsor this one thru PAPT [15:46] i.e. upload it as PAPT member [15:58] ScottK, why not subscribe the pythonistas team to the bug? [15:58] mok0: They are. [15:58] That's why I saw it. [15:58] ScottK, it's not on their bug page [15:59] mok0: If a team is subscribed to a package, that doesn't mean all package bugs show up on the team bug list. [15:59] ScottKnot they are [15:59] All members of the team got bugmail on it. [15:59] ScottK, sorry: now they are [15:59] Oh. [15:59] ScottK, the team was in the "Notified" column [16:00] ScottK, when I subscribed them, they moved to the "Subscribed" column [16:00] Ah. [16:01] * mok0 contemplates to join Ubuntu Pythonistas [16:02] ScottK, hey you are in it :-) [16:03] mok0: I can even approve your request to join. [16:03] ScottK, heh [16:09] mok0: no need to subscribe the team if they are notified, fwiw [16:10] pochu: notifcation is via mail, yes? [16:10] right [16:10] as subscribed is [16:10] I've sent a mail to contact at twotoasts punkt de about the catfish bug :) [16:10] pochu: I tend to forget about mails [16:10] pochu: but I often check the buglist [16:11] you can check the packages one team/person is subscribed to [16:11] pochu, go on... [16:12] e.g. https://bugs.edge.launchpad.net/~pythonistas/+packagebugs [16:12] if you go to the bugs tab in launchpad, then click on "Show package report", you will get that [16:12] hm.. there's a new upstream version, 0.3.2 for catfish [16:12] which are all the packages the team/person is in "also notified" [16:13] + fix search from folders with spaces breaking find [16:13] ScottK: http://www.twotoasts.de/media/catfish/ChangeLog - this is probably fixed in 0.3.1 [16:13] pochu: LP is a never-ending source of amazement... [16:13] hehe [16:14] pochu: ok, I wont subscribe anymore bugs to pythonistas [16:14] mok0: amazement/pain, but yes. [16:14] heh [16:14] savvas: Any interest in packaging the new version? [16:15] savvas: POX said he would sponsor it for Debian and we can sync it from there. [16:15] ScottK: I've joined the team, can you approve me? [16:15] ScottK: I'll try to package the new version :) [16:16] (well, or just do that once you check your mail and see the new member notification.. I've no hurry :)) [16:16] savvas: Great. You might also want to join #debian-python on IFTC. [16:16] RainCT: Sure thing. Will do. [16:17] I'm still learning, but I think it's easy for this package [16:18] savvas: OK. If you have questions, you can ask me here or on #debian-python [16:18] Any motu-sru around? [16:18] I am [16:19] cody-somerville: Would you please ack the ebox SRU? [16:19] bug #? [16:20] Bug 273486 [16:20] Launchpad bug 273486 in ebox "Current eBox packages in intrepid don't work at all" [Undecided,New] https://launchpad.net/bugs/273486 [16:20] bug 314606 [16:20] Launchpad bug 314606 in ebox "ebox and libebox don't support Intrepid gconf version" [Undecided,New] https://launchpad.net/bugs/314606 [16:20] Bug 255368 [16:20] Launchpad bug 255368 in ebox "ebox: Depends: libapache-authcookie-perl but it is not installable " [Undecided,Confirmed] https://launchpad.net/bugs/255368 [16:23] nixternal: yes, Brainstorm is finally being updated today (actually, it looks like it already has been), but it doesn't look like that thing in Jono's post :P === invaleed is now known as in[v]aleed [16:32] hello! could anybody help me to package a set of objects please? [16:34] thekorn: re: lplib - that's brilliant, I'll start merging it as soon as I can. [16:38] It's my firs time packaging, the objects are like plugins written in C, I need some help with rules file [16:39] nhandler: codelite's ready for reviewing again [16:41] hi [16:41] ScottK, sommer: https://bugs.edge.launchpad.net/ubuntu/+source/ebox/+bug/273486 [16:41] Ubuntu bug 273486 in ebox "Current eBox packages in intrepid don't work at all" [Undecided,New] [16:42] hi guys I know c/c++ and want to start developing some small softwares , but I dont know how to???Can anybody give me a starting point...please [16:44] cody-somerville: yep [16:44] sommer, I made some comments on your SRU application. [16:48] cody-somerville: thanks, I'll address those items [16:54] RainCT: argh, I was hoping I was correct ;) [16:55] nixternal: if you have some other theory, I'll listen ;P [16:58] vorian: I looked at the patches; only one is still relevant. I might as well make the last change and upload [16:58] vorian: (in stellarium) [16:59] sommer, Also commented on bug #255368 [16:59] Launchpad bug 255368 in ebox "ebox: Depends: libapache-authcookie-perl but it is not installable " [Undecided,Confirmed] https://launchpad.net/bugs/255368 [17:00] mok0: are you going to upload it then? [17:00] vorian: yeah why not. It is already in the archive [17:00] if so, the stellarium.desktop could use a patch as well [17:01] vorian: OK will take a look [17:01] awesomeness [17:01] vorian: It runs great on my intrepid amd 64!!! [17:01] sommer, I just commented on #314606 now too [17:01] coolio [17:01] vorian: Very nice work they did to the interface! [17:02] i'll have to play with it when the dust from kde updates settles down [17:02] vorian: uh-uh, I haven't dared take those on [17:03] :) [17:03] vorian: still at 4.1 [17:03] its a spiritual experience [17:03] mok0: 4.1.4 should be hitting any time now if you use -proposed [17:03] cody-somerville: thanks, should have updates to those sometime this afternoon or evening [17:03] vorian: tell me about it. I just had a spiritual experience when my sys disk crashed yesterday [17:03] ouch! [17:03] sommer, thanks [17:04] vorian: fortunately my home is on a separate disk ;-) [17:04] vorian: ... with backup [17:04] nice, not too big a deal then. other than hardware loss [17:04] :) [17:05] vorian: yes. This time, I bought a Server Edition disk [17:05] hello [17:05] any possibility of you fixing Bug #285417? or is this package on main? [17:05] Launchpad bug 285417 in ubuntulooks "[intrepid] gtk2-engines-ubuntulooks can't be installed" [Undecided,Confirmed] https://launchpad.net/bugs/285417 [17:06] hehe [17:07] Turl, if you click on the "ubuntulooks (Ubuntu)" link on the taskbar, and then select the "Overview" tab, you'll see that it's in main [17:08] oh, sorry then [17:08] is there any channel I can go to bug the main packagers? :p [17:09] Turl: is this a matter of changing a directory name? [17:09] Turl: core developers generally hang out in #ubuntu-devel [17:10] Turl, why didn't that elli222 fellow upload a patch? [17:10] mok0: it's changing the dependencies not to delete ubuntu-theme if I'm right, the bug has an explanation on how to repackage it to work correctly [17:11] mok0: no idea :p maybe he doesn't know how? [17:11] Turl: it's faster to make a patch than writing that long explanation :-) [17:12] I believe so :p [17:13] Turl, If you wanna fix it, we can guide you along here [17:13] really it's for a friend, I don't want to install that theme :p [17:14] Turl: you wanna fix it? :-) [17:14] will I need to install tons of packages? :p [17:15] Turl: I don't think so [17:15] Turl: perhaps some devel tools [17:15] Turl: but you'll need those the NEXT time you fix a bug lol [17:16] ok, guide me then := [17:16] :)* [17:16] Turl: first you need to go into a working dir and download the source package [17:16] any empty dir is ok, am I right? [17:16] Turl: yes [17:17] turl, what version do you want to make the fix. Intrepid? [17:18] yep [17:18] Turl: do you know how to get the source package? [17:18] apt-get source I guess? [17:19] Turl: yes, if you're on the same version of Ubuntu [17:19] yeah [17:19] I got a diff.gz, a .dsc, a tar.gz and a dir [17:20] Turl: now unpack using dpkg-source -x <.dsc file> [17:21] ok, done [17:23] now what mok0? [17:23] Turl: go down into the topdir [17:23] ok [17:23] Turl: what's that called, btw [17:23] ubuntulooks-0.9.12 [17:24] Turl: ok. Now go into debian/ [17:24] ok [17:24] Turl: as I understand the bug, you need to edit the dependencies? [17:25] Turl: then you need to edit "control" [17:25] with nano is ok? [17:25] or do I need to use some dpkg tool? [17:25] Turl: yes [17:25] Turl: not yet [17:27] Turl, remove the line containing "Replaces: ... " [17:29] ready [17:29] now what? [17:29] Turl: do you know anything about ubuntu artwork? Because I don't [17:30] I now there are pretty ones and ugly ones :p [17:30] Turl: now you need to edit "changelog" and write a new entry at the top [17:30] I copy one and edit it? [17:31] Turl: yes, you can make a copy of the first entry and change it [17:32] Turl, you need to use a new revision string [17:32] ubuntulooks (0.9.12-13) intrepid-proposed; urgency=low [17:33] yes [17:33] would that be ok? it said hardy-proposed on the other one [17:33] Turl: that will propose it as a fix for intrepid [17:34] ScottK: I think I've finished with catfish: http://revu.ubuntuwire.com/details.py?package=catfish https://launchpad.net/~medigeek/+archive/+build/836369 [17:34] Turl: if you want to fix for hardy, you need to do the same for the hardy version of the package [17:34] Turl: when you're done, cd .. [17:35] ScottK: I'm going to see if it actually works now with folders with spaces :) [17:35] Turl: then do "debuild -S -uc -us" [17:37] where can I get debuild? [17:37] Turl: sudo apt-get install devscripts [17:37] heh [17:38] savvas: Since we are going to get POX to upload this to Debian, you want the revision to be -1 and the distro to be unstable [17:39] ScottK, savvas: acually, new upstream release of catfish is already in PAPT svn, Kmos: why didn't I upload it yet? (/me is too lazy to dig in his mails) [17:39] Ah. [17:39] meh [17:39] savvas: Might be good of you to review what's in the svn and see if you have anything of significance that's different. [17:42] mok0: installing, might take some timeƧ [17:42] Turl: ok [17:42] it installed exim :/ [17:43] mok0: it threw a lot of errors :S [17:43] POX: the changelog in svn shows 0.3.1 - http://svn.debian.org/wsvn/python-apps/packages/catfish/trunk/debian/changelog?op=file&rev=1943&sc=1 [17:43] Turl: the debuild command? [17:44] a lot of "file or directory does not exist" [17:44] yeah [17:44] Turl: can you pastebin the output? [17:44] Something needs to be changed to depend/recommend postfix|mail-transport-agent instead of exim|mail-transport-agent [17:44] like /usr/share/cdbs/1/class/autotools.mk does not exist, /usr/share/cdbs/1/rules/debhelper.mk does not exist, .. [17:44] mok0: it's in spanish, idk if you want it all the same [17:44] cody-somerville: you're catfish maintainer, why it's not uploaded yet? [17:44] ScottK: it's been good for training hehe :) They've pretty much changed the same things I have, so that's good! [17:45] yes. [17:45] Turl: yikes. Try anyways [17:45] cody-somerville: http://people.debian.org/~piotr/sponsor Q9 (if that's the reason) [17:45] savvas: You can also request a sync after it's uploaded to Debian. [17:45] POX, I'm simply too busy atm [17:46] oh, ok [17:46] I'll upload it as PAPT member then [17:46] mok0: http://paste.pocoo.org/show/99473/ [17:46] (after some basic tests) [17:46] * mok0 looks [17:46] turl, sudo apt-get install cdbs [17:47] POX: I made one for 0.3.2, the one in Debian svn is for 0.3.1 [17:47] turl, sudo apt-get install debhelper === asac_ is now known as asac [17:47] savvas: did you have to change something besides version? [17:47] POX: I think it's the fix_makefile patch [17:47] * Turl installs what mok0 said [17:48] turl, after that try debuild again [17:48] POX, thanks [17:49] mok0: it seems to have worked [17:49] there's a little warning though, W: ubuntulooks source: ancient-standards-version 3.6.2 (current is 3.8.0) [17:49] Turl: yay [17:49] Turl: you should have a new source package in .. [17:50] savvas: send me `svn diff` output (or I'll prepare it myself) [17:50] mok0: I have some new files now, a .build and a .changes [17:50] is it OK? [17:51] Turl: sounds right. You should also have a new .dsc fie [17:51] file [17:51] mok0: I only have the old one :/ [17:52] I guess it's been replaced? [17:53] well, it seems to be the old one mok0. I cat'ted it and it has the old version number [17:53] Turl: what's in the changes file? (pastebin) [17:54] http://paste.pocoo.org/show/99474/ [17:54] Turl, hmm, I think something went wrong with your changelog entry [17:55] Turl: you didn't update the release to -13 [17:56] stupid me, I didn't :p [17:56] Turl: change it, and run the debuild command again [17:57] ready [17:57] I have now -12 and -13 files [17:57] POX: I'm still learning, can you grab it and compare it yourself? :) Here: http://savvas.radevic.com/packaging/catfish/10Fix_makefile.dpatch [17:57] turl, great. But you overwrote the original -12 files so you need to apt-get source again [17:57] ok [17:58] POX: It's mostly the same patch, but I've included the change to point to share/icons/hicolor/scalable/apps [17:58] mok0: do I need to do everything from scratch? [17:58] Turl: no, just don't delete the -13 files [17:58] ok [17:59] POX: do I have to open a new upstream package request in Debian for this? [17:59] Turl: we just need to re-establish the -12 files that were accidentally overwritten === bobbo_ is now known as bobbocanfly [17:59] now dpkg-source -x ? or what? [17:59] Turl: yes === bobbocanfly is now known as bobbo [18:00] ready mok0 [18:00] savvas: no, I will just upload it and let you know to file a sync request bug in Ubuntu (I'll close the LP bug in changelog) [18:00] Turl: now run debdiff old.dsc new.dsc [18:00] POX: ok, cheers! :) [18:01] Turl: replace "old" and "new" with the appropriate names [18:01] ok mok0 [18:01] ready [18:01] Turl: the output came to stdout, right? [18:01] I got a ubuntulooks_0.9.12-13.diff.gz if I'm right [18:02] yeah, some output came to stdout [18:02] Turl: ok, you need to pipe it to a file; I routinely would call it "ubuntulooks_0.9.12-13.debdiff" [18:03] ready [18:03] Turl: let's check the debdiff file. You need to: [18:04] Turl: apt-get install patchutils [18:04] btw, I noticed something in the dpatch file: "--- catfish-0.3~/Makefile.in2007-04-04 04:20:26.000000000 +0200" <- Does that ~ character stand for anything? [18:04] savvas: yes [18:04] savvas: patch needs it [18:05] mok0: it seems to be there already [18:05] turl, great. So do lsdiff ubuntulooks_....debdiff [18:06] Turl: it should tell you what files are modified by the diff [18:06] Turl: hopefully only 2 [18:07] mok0: I used catfish-0.3.2/Makefile.in instead of catfish-0.3~/Makefile.in and it built the package. Does that ~ mean something like .* in regex? :) [18:08] savvas: eerrr no [18:08] ok now I'm officially confused :p [18:08] savvas: it's actually only important what's in the +++ line [18:09] +++ catfish-0.3/Makefile.in2008-05-22 02:45:33.000000000 +0200 [18:09] mok0: there are more than 2 files, but it's because I moved a dir in purpouse for it not to conflict [18:09] ah I see, ok [18:09] savas, thats the one [18:09] thanks mok0! [18:09] Turl: ah, ok [18:09] now what mok0? [18:10] Turl: how did you move that dir? [18:10] mok0: with mv, why? [18:10] Turl: because that way it won't be reflected in the package [18:10] Turl: it's not the right way to do it [18:11] :/ [18:11] tell me how to move it and I'll do it from scratch then :p [18:11] Turl: but forgetting about that, you are in principle done. You could attach the debdiff to the bug and write a note that this fixes the ubuntulooks package [18:12] Turl: but the bug mentions making a fix in another package, too [18:12] yeah [18:12] and how can I upload it to a ppa? so it's available for my friend [18:12] Turl: so you should go through the same thing with that, build a new package with a new release number, make a debdiff to the old package and upload the debdiff to LP [18:13] ok mok0 [18:13] Turl: then the developers will look at your patches, and you will get a lot of karma ;-) [18:13] Turl: but we should look at that dir that you want to move [18:14] Turl: can you tell me what it is [18:15] Turl: yes you can upload to your ppa, [18:16] mok0: the dir is ubuntulooks-0.9.12/themes/Human/ [18:16] and I moved it to ubuntulooks-0.9.12/themes/Human-UbuntuLooks/ [18:16] and fixed the makefiles [18:16] Turl: ah [18:17] Turl: but when the package is built, it uses the orig.tar.gz which still has that dir in the same place [18:17] Turl: so the trick is not to move it locally, but install it somewhere else [18:19] hm, so what should I edit then? [18:20] Turl: err I need to figure out how it works first [18:21] Turl: during building, the package is constructed in a subdir to debian/ [18:22] Turl: so, it creates a directory: debian/gtk2-engines-ubuntulooks/usr/share/themes/Human [18:23] Turl: the trick is to move it after compilation but before package building [18:23] Turl: and you do that in debian/rules [18:24] Turl, are you there? [18:24] yeah mok0 [18:24] Turl: are you following? [18:24] the rules file has includes only [18:24] Turl: yes, but CDBS has some hooks you can use [18:25] I really don't know CDBS :p nor packaging, that's why you're explaining me [18:25] Turl: after the includes, make a new target called "install/gtk2-engines-ubuntulooks::" [18:25] turl, next line: [18:26] could someone review my package? http://revu.ubuntuwire.com/details.py?package=codelite [18:26] mok0: for the target I just type "install/gtk2-engines-ubuntulooks::" ? [18:27] mv -f ddebian/gtk2-engines-ubuntulooks/usr/share/themes/Human/ debian/gtk2-engines-ubuntulooks/usr/share/themes/Human_somethingelse [18:27] Turl: yers [18:27] is it ok the ddebian or is it a typo? [18:28] Turl: debian [18:28] Turl: it's just the mv command from topdir to move the Human directory to something else [18:28] ok :) [18:29] Turl: but the first character on that line is importatnt [18:30] turl, see here how it's done, about 1/5 down the document: https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml [18:31] Turl: my wife just called me the 2nd time to tell me to come home for dinner... I gotta go [18:32] Turl: don't forget to document moving the directory in changelog [18:35] RainCT: ping [18:54] w00t [18:54] :) [18:55] iulian: pong [19:08] RainCT: What do you think about the removal of the revu-uploaders team? [19:11] RainCT: I mean, do we still need it there? [19:15] iulian: nope [19:24] RainCT: OK then. Do you have the power to deactivate it or should we open a question in launchpad and ask for it to be removed? [19:24] iulian: I set it to restricted, that's all I can do [19:30] * iulian wonders who can deactivate it. [19:31] how can I sign a .changes file? [19:31] I already have my key [19:33] Turl: debsign -k ... [19:35] thanks iulian [19:42] my packages were rejected :/ PPA uploads must be for the RELEASE pocket. [19:42] what does that mean? [19:49] Turl: You should ask PPA questions in #launchpad. [19:49] ok [19:55] Turl, you used other version that normal release (hardy, jaunty, intrepid, ...) in your changelog [19:56] I used intrepid-proposed [19:56] you have to put intrepid [19:57] ok [20:09] Hi. Where can I ask something about sbuild (it seems to leave sometime a temporary build partition that I cannot delete) [20:20] fabrice_sp: Here's not bad. A number of people who hang out here use it (not me, however). [20:21] ok. I just wanted how to delete them, as I haven't found for the moment why it's happening [20:21] (and I have 6 of them) [20:27] I can't even umount them: Device is busy (and I rebooted several time my computer) [20:30] This is sbuild in lvm mode, I assume? [20:33] maxb, yes [20:33] I setup a lvm for that purpose [20:33] Try 'schroot --list --all-sessions' [20:34] here they are my 6 sessions [20:34] schroot --end-session --all-sessions (or do it individually) [20:35] It worked! You're the man, maxb ! Thanks :-) [20:36] And I've never even used LVM :-) [20:36] need to find some spare hd space to play at some point [20:37] I did that to have some software 'raid' for my home (already lost 2 times my home before) [20:37] and I decided to use it also for building thing, and separating the chroot in another 'partition'. Work great! :-) [20:39] but never access your lvm at the same time with gparted and system-config-lvm. You will lost everything [20:39] anyway, thanks for your help! :-) [20:47] can someone direct me to an example package to help me in writing get-orig-source: target ? [20:48] AnAnt: How about plasmoid-kbstate [20:49] what's the source package name ? [20:52] AnAnt: /me wrote recently this: http://svn.debian.org/viewsvn/*checkout*/python-modules/packages/sqlalchemy/trunk/debian/rules [20:53] AnAnt: plasmoid-kbstate. It's only in Jaunty though. [21:07] hrmph. Damn mysql build clogging up the build queue [21:11] jms@destiny:~$ firefox [21:11] Aborted [21:11] jms@destiny:~$ firefox [21:11] Aborted [21:11] go go free software [21:13] directhex, exactly how does "free software" relates to your problem ? [21:14] joaopinto, firefox crashes 30+ times a day. it gets annoying [21:15] I have no crashes with firefox, it most likely related to a plugin, or something specific to your configuration [21:15] nspluginwrapper/flash is certainly to blame for many of the crashes, but it seems not as many of them as i thought [21:16] relating a firefox crash with "free software" could be offending for free software developers [21:17] directhex: Firefox isn't particularly free, IMO. [21:18] ScottK, mmm, perhaps. i have a EULA here for you..... ;) [21:18] joaopinto: win [21:18] Firefox crashes sometimes for me yet Windows XP crashed more, how does it relate to the freeness of it? [21:18] directhex: Exactly. [21:19] firefox is one of the media's poster children for a successful free software app. it's high profile. when it cocks up, it's noticed more than if the chicken scheme compiler isn't up to scratch, fr'example [21:19] and as an app people use constantly, infuriating when it dies [21:20] Firefox is stable as a rock for me [21:20] mok0, i386? [21:20] directhex: perhaps you should direct your curses at the wireless producers that wont release their specs [21:21] directhex: amd64 [21:22] When a package gets removed for the reason "NBS" what does that mean? [21:25] Chris`: it's a binary package with no corresponding source package [21:26] * directhex gives webkit another spin [21:26] mok0: Thanks ;) [21:26] Chris`: for example if the source package has been renamed, the old binary packages will be "orphans" [21:27] directhex: are you looking at Chrome? [21:27] mok0, midori. does chrome's linux shell have advanced features like "pressing enter" yet? [21:28] directhex: I don't know [21:31] Hi everyone, I just finished my first package and uploaded it to my PPA: http://ppa.launchpad.net/stochastic/ubuntu it's of the Calf audio plugins. Please review and let me know how horrible my packaging skills are. [21:32] stochastic, cracked the variable substitution? [21:33] stochastic: you should probably put it on REVU (?) [21:33] directhex, yes, thanks to liw's advice it was a problem with it trying to make to debian/calf rather than debian/calf-plugins [21:34] laga, how do I do that - I'm new to all this [21:35] stochastic: i bet it's documented on the MOTU wiki page [21:35] ok, I'll do a search [21:36] !revu [21:36] REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [21:36] wee. [21:39] ok, it's in REVU now === khashayar is now known as khashayar_away [21:45] hmm, it looks like dput uploaded to REVU fine, but I don't see it there and my profile shows no uploads, am I just too quick for the system? === `Chris is now known as Chris` === khashayar_away is now known as khashayar === khashayar is now known as khashayar_away === albert24 is now known as albert23 [21:54] RainCT, james_w: We have lplib support in u-d-t \o/ [21:54] thanks jpds [21:54] and thekorn [21:54] Especially thekorn. [21:55] jpds: would you write a mail to the list about what that means please? [21:56] jpds: rock on! [21:56] * RainCT hugs jpds and thekorn [21:56] james_w: Sure, first shower and let brain cool down. [21:56] :-) === khashayar_away is now known as khashayar [22:19] stochastic: from my experience, it can take a while before the package shows up on the web interface ;-) [22:22] khashayar, I know you're good at backporting, and I'd like to upload a version of that package for intrepid to my PPA, is there anything special I need to do other than force the upload of the different version? [22:24] stochastic: The only thing you need to do, is to make sure it has a different version number (limitation of ppa). That is, if your jaunty package is calf-0.0.17-0ubuntu1~jaunty~ppa1, your intrepid pacakge should be something like calf-0.0.17-0ubuntu1~intrepid~ppa1. [22:26] But usually you wouldn't use ~jaunty at all since its the development release [22:26] oh, and you in your .dput.cf, you could have a section for intrepid with "incoming = ~stochastic/ubuntu/intrepid". This will upload to intrepid. [22:26] and the logical nesting is more ~ppa1~intrepid [22:26] maxb: That's right, no ~jaunty [22:26] Convention seems to be to do ~intrepid1, also [22:27] ok, so do I just rename the .changes file after I've debuild the package? or does that need to happen before debuild somewhere? [22:27] maxb: really? I thought convention was ~release~ppa1, and releaseX for backports. [22:27] nope [22:27] stochastic: In debian/changelog [22:27] Then debuild. [22:27] ok, perfect [22:28] maxb: I'd suggest the other way around. [22:28] because if you update the package in your ppa, you go to ~ppa2, and then you backport that [22:28] maxb: In Ubuntu Backports we use ~$RELEASEX [22:28] Quite [22:28] So ~ppaX will be a problem. [22:29] Should be ~releaseX~ppaY [22:29] Well, I'm basing my suggestion off https://help.launchpad.net/Packaging/PPA#Versioning [22:29] ScottK: What's the X for, in that model? [22:29] maxb: This is an Ubuntu channel. Nothing to do with us there. [22:29] Number starting with 1 [22:30] ScottK: I don't understand what you're saying. Given that Ubuntu is the only distribution with PPAs, how can documentation about PPA versioning not apply? [22:30] ScottK: Yes, but what does that number mean? Attempts at backporting? [22:31] Yes. Revisions. [22:31] maxb: It's written by Launchpad developers who are not Ubuntu developers. [22:32] If ~ppaX indicates releases of a package in a ppa, and ~intrepidX indicates attempts at backporting, then the order of versioning significance dictates ~ppaX before ~intrepidX [22:32] Because the first attempt at backporting the second release needs to be newer than the second attempt at backporting the first release [22:32] maxb: What happens if you upgrade from Hardy to Intrepid. You need to move to the intrepid version of the package. [22:33] How do you ensure that with that broken model [22:33] maxb: It's really OT here anyway. Go find someone on #launchpad that knows more about distro development than we do here. [22:33] * ScottK heads off. [22:34] Erm [22:36] I am unconvinced the model I'm suggesting is broken. Is there a better channel to discuss the interaction between Ubuntu PPAs and Ubuntu primary archive? [22:37] maxb: I pm:ed you. [22:39] indeed, I just wanted the conversation to unambiguously show that I don't accept the assertion that that model is broken === eights is now known as Guest5565 === Guest5565 is now known as eights [22:52] uhm.. how can I install the nvidia 180 driver? I tooke the .deb's from packages.ubuntu.com but the version doesn't show up in jockey [22:52] (as always I want to know something, no answers in #ubuntu :P) [22:52] RainCT: Install the -modaliases package, then jockey should know about it [22:52] funny, that's what I was doing right now :P [22:52] maxb: thanks :) [22:53] But, what do you mean you took the .deb's from packages.ubuntu.com? Why not let apt get them for you? [22:53] maxb: because (and I've no idea why) I can't get APT to see it.. [22:53] updates, backports, etc. are enabled and cache up2date [22:53] but I only see 180 packages in jaunty [22:53] That's because they're in intrepid-proposed [22:54] oh. packages.ubuntu.com shows them in intrepid-updates [22:54] great, jockey sees it now.. let's see if it works [22:56] maxb: failed to initialzie kernel module" [22:56] maxb: do I need to reboot' [22:56] * RainCT should learn to type :P [22:58] What's a major update binary nvidia driver doing in -proposed? [22:58] lmao [23:00] Oh, it's actually in -updates now, I hadn't noticed. [23:00] However, it's a new-to-intrepid package, so it's strictly opt-in [23:00] probably why it was considered SRU-able [23:00] does 180.22 support gtx295? [23:01] 180 does ameliorate some severe compiz rendering issues, so that's probably also a reason for the SRU [23:02] hm, no, 295 unsupported [23:02] (works now) [23:02] maxb: Does it fix nvidia leaking texture memory into the compiz process? [23:03] "Fixed a regression that could result in window decoration corruption when running Compiz using Geforce 6 and 7 series GPUs." [23:03] Don't know about that one. I know it stops my window decorations from corrupting themselves often, which they did with 177 [23:05] bluesmoke: That's a good question. I haven't tried that :) === bluesmoke is now known as Amaranth [23:35] Which section would a flight simulation program best fit? [23:41] maxb: I'll file a bug on help.launchpad.net when I get a moment. [23:41] Where would such a bug belong? It's not exactly part of launchpad-the-project per-se? [23:42] BTW, I don't accept that people managing to develop a really slow web tool gives them any particular expertise about Linux distro development. [23:42] maxb: Dunno. In Ubuntu we have a project for web site bugs, I'd assumed that Launchpad would have something similar. [23:43] Generally I file against the launchpad meta project and someone triages it into the right place. === khashayar is now known as khashayar_away [23:44] ok. By the way, are there any concrete examples of the number in ~releaseX being other than 1? [23:44] Sure. It takes me more than one try on a not infrequent basis. [23:45] for sourceful backports, then? [23:45] maxb: https://edge.launchpad.net/~ubuntu-clamav/+archive for a PPA. [23:46] That also shows you the multi-release model I suggest is appropriate. [23:48] In a quick read through I don't see anything other than ~release or ~release1, but I do see foo~dapper1~ppa4 but foo~hardy1~ppa1 which is enlightenting [23:49] My advocacy of ~ppaX~releaseX is founded on the assumption that any bump to the ppaX number is a crosscutting packaging change which *will* be backported to all release series [23:49] I agree that without that assumption, upgrading across releases is broken [23:50] maxb: https://launchpad.net/ubuntu/+source/clamav/+publishinghistory [23:50] Also ~ppa is a higher revision than anything you'll find in *-backports and that should be avoided too. === khashayar_away is now known as khashayar [23:52] Ah, thanks, didn't know about that view, so I tried to skim though all of the superseded package info, and evidently missed bits [23:54] Clamav is about as tortured a package history as you are likely to find as it's a highly used package with lots of security uploads and stuff. [23:55] Is ~dapper1ubuntu0.1 just someone driving dch in a non-optimal way? [23:56] ohh... I think I'm seeing the tortuous sense in it now [23:58] I agree ~ppaX is a bit of a nonsense all round, really. If you are doing further development of foo 1.0-1ubuntu1, then it makes more sense to go to 1.0-1ubuntu1ppa1 rather than 1.0-1ubuntu2~ppa1, I think [23:58] Whilst if you are doing a backport, it needs to be less than an official backport. [23:58] So ~ppa loses either way [23:59] Yay, catfish 0.3.2-1 published in debian: http://packages.debian.org/sid/catfish