[00:09] Hi, question, I'm using a PPA and say if I want to distribute two types of the same program (e.g. a stable version and an alpha version) should I change the control file to have something like programname-alpha? [00:11] yes [00:11] and really you want a different name for the source package more than anything else, so it can coexist [00:11] on the ppa [00:13] directhex: alright, I'm trying some stuff out, let's see if it works [00:24] directhex: the packages should have seperate changelogs? [00:25] Brucevdk, assuming they have different source tarballs, that's mostly up to you [00:25] Brucevdk, but the names in the changelogs need to match the names in control [00:31] directhex: not sure how to best approach this. This is the current situation: http://tinyurl.com/aqwwqu (the build_package.sh in packages/ubuntu) creates a temporary directory for building in tmp. [00:36] james_w, you're a very odd individual [00:36] directhex: thanks [00:36] now, make me a sandwich [00:36] I was quite surprised I wasn't the only one to have thought of that [00:36] No! [00:40] wondering if I should just create three directories or so, one for each changelog and one for the common files then merge that using the build_package script at build-time. [00:40] but I must be doing this wrong, because that just seems stupid [00:42] I am trying to compile the amsn like https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/314805 but i recive this http://paste.ubuntu.com/121257/ what is wrong? [00:42] Error: Could not parse data returned by Ubuntu: The read operation timed out (https://launchpad.net/bugs/314805/+text) [00:43] Andre_Gondim, there's a problem? [00:43] Andre_Gondim: maybe it's just me, but that's just ./configure no? (launchpad is a little slow) [00:45] Hi, I'm having an issue with package name conflict here (with Eina music player and lib-eina with eina as src name in debian). Anyone familiar with this kind of issue? [00:45] Brucevdk, when i do make deb i recive http://paste.ubuntu.com/121259/ [00:48] Andre_Gondim: sorry, compile errors aren't my game [00:48] Brucevdk, ok [00:48] does anyone know how to solve this problem http://paste.ubuntu.com/121259/ [00:49] "Signer has no upload rights at all to this distribution." -- I'm an administrator... :-| [00:51] Andre_Gondim: this post shows on how to compile amsn 0.98b (http://ubuntuforums.org/showthread.php?t=712425) [00:51] Brucevdk, are you committing to your PPA? [00:52] directhex: yes, verifying my key right now [00:52] Brucevdk: you sure you're uploading to your PPA? [00:52] weboide, thanks [00:52] * directhex high-fives LaserJock [00:52] LaserJock: well assuming committing is the same as uploading, yes :-) [00:53] oh, you mean if I'm absolutely sure [00:53] Brucevdk: well, sometimes it's easy to miss the "where to upload to" part of dput [00:53] hold on [00:53] Brucevdk: which means you end up uploading to Ubuntu instead of the PPA [00:54] LaserJock: are you supposed to end incoming with /ubuntu/ ? [00:54] think I still managed to screw it up, it's missing ppa [00:54] fqdn = ppa.launchpad.net [00:54] Brucevdk: so you did put the location in your actual dput line though? [00:55] incoming = ~myusername/ubuntu [00:55] it was incoming = ~nautilussvn/ubuntu/ [00:55] changed to incoming = ~nautilussvn/ppa/ubuntu/ [00:57] also the documentation said a unique signing key should have been generated, but afaik it hasn't (it's been at least more than week now) [00:59] good grief, "i don't know" is not a very helpful bug description :( [00:59] lol [00:59] LaserJock: mark it as fix released :p [01:00] the one before that is filed against edubuntu-addon-meta with the title "my ubuntu don't know what is docx format" [01:00] just letting you know, it still got rejected with incoming set to ~nautilussvn/ppa/ubuntu/ [01:00] Is there anyone familiar with dealing with name conflict between a package already in repos and one that wish to enter? [01:01] Brucevdk: what was the command you ran? [01:01] LaserJock: dput nautilussvn_0.12-1ubuntu1_source.changes [01:01] weboide: what's the package names? [01:01] Brucevdk: I'm guessing that's your problem [01:02] LaserJock: I have eina (a music player) and in debian repos there is eina (from enlightenment) as src name, libeina as bin name. [01:02] Brucevdk: you run dput as: dput [01:02] Brucevdk: the default is to upload to the Ubuntu archives [01:03] weboide: so maybe eina-player [01:03] ? [01:03] LaserJock: yeah, I talked with enlightenment and they clear said "we won't change our name because of debian".. [01:04] LaserJock: oh I assumed that was what incoming in ~/.dput.conf meant, so wait, what is . The help page just says: my-ppa [01:04] LaserJock: but now I need to know how deep the changes need to be in eina-player. [01:04] weboide: I wouldn't expect them to. The general rule is that the first one to the archive gets to keep it [01:04] LaserJock: hm okay, well, we lost :( [01:05] Brucevdk: well, what's the name of the PPA in your .dput file? [01:05] Brucevdk, the [ppaname] in dput.cf [01:05] weboide: seems like eina-player or something similar may work [01:05] LaserJock: I'm not sure if I just need to change the packaging of the orig.tar.gz or does the configure.ac needs changing too? [01:06] LaserJock, directhex: so just nautilussvn? [01:06] weboide: are the files named the same? [01:06] right, looks like it [01:06] LaserJock: what files? [01:06] Brucevdk, if that's what the [heading] in dput.cf is called [01:07] weboide: the name of the actual programs? [01:07] LaserJock: well eina from enlightenment is a lib, so binary package is named libeina. [01:08] weboide: I'm not talking about packages [01:08] weboide: I mean the actual files that get shipped in the .deb [01:09] weboide: if there isn't a conflict you could just rename the package eina-player (in debian/changelog debian/control and rename the .orig.tar.gz) [01:09] directhex, LaserJock: ok thanks guys, looks like that was it, I'm feeling a little bit stupid (but the docs really weren't that obvious, really ;-) [01:09] Brucevdk: try "dput ppa:~nautilussvn/ppa nautilussvn_0.12-1ubuntu1_source.changes" [01:09] Brucevdk: yeah [01:10] LaserJock: well, it's a quite simple package, usr/share/doc/eina, usr/lib/eina, usr/bin/eina. except there is also eina-dev which is /usr/include/eina or something. [01:10] Brucevdk: "dput ppa:nautilussvn/ppa nautilussvn_0.12-1ubuntu1_source.changes" sorry [01:10] Brucevdk: just be glad your not a developer and accidently upload something to the wrong place. it doesn't get rejected ;-) [01:11] LaserJock: indeed :-) [01:11] weboide: your eina or enlightenment's eina? [01:11] LaserJock: mine [01:12] LaserJock: it does look like a real messy thing to check and make sure it's not confliction :( [01:12] really? [01:12] LaserJock: conflicting* [01:12] LaserJock: I mean the process [01:12] LaserJock: should I be worried that the general signing key hasn't shown up yet? [01:12] Brucevdk: I wouldn't think so [01:12] Brucevdk: I think it depends on when you uploaded last [01:13] LaserJock: you need to have one upload for it to start generating one? [01:13] weboide: all you should need to see is if the enlightenment package ships a /usr/bin/eina [01:13] Brucevdk: yep [01:13] LaserJock: okay [01:13] LaserJock: that explains it ;-) [01:13] Brucevdk: the signing is triggered off an upload [01:13] LaserJock: doesn't that mean I need to re-upload? Or is it going to be signed twice? [01:13] LaserJock: i've got a conflict with /usr/lib/eina/ [01:13] LaserJock: oh wait, I didn't upload a binary [01:14] weboide: you'll rename that [01:14] Brucevdk: it'll just get signed [01:14] LaserJock: so, you sign your source thingy with your own key, upload it, and then it signs the binary with the general key? [01:14] Brucevdk: you don't need to upload a binary [01:14] Brucevdk: right [01:14] Brucevdk, right [01:14] right, alright, makes sense [01:15] LaserJock: would /usr/include/eina get renamed too then? [01:15] weboide: yep [01:16] weboide: the packaging should take care of all that basically [01:16] LaserJock: okay, so this looks good to me, I'll try to package it with the name change and see the changes. [01:16] weboide: you just want to retain /usr/bin/eina so users can find it [01:17] weboide: okay, should I do any link with /usr/bin/eina-player or no? [01:17] weboide: no, just ship it as /usr/bin/eina [01:17] okay, thanks a *lot* for your help :) [01:28] LaserJock: I do have to also rename the directory in the orig.tar.gz to eina-player- right? (this will break any debian/watch updating though...) [01:30] It won't. uscan is smart enough to be able to mangle it appropriatelyl. [01:31] Hm, the annoying thing is to have to repackage the tar.gz from upstream everytime from now on, right? [01:32] hm [01:32] Nevermind that, if that works with uupdate [01:32] :p [01:33] weboide: it should mostly work ok without a lot of changes [01:35] okay, well thanks, I think I'm finally done with the questions now! [01:57] anybody about who uses git/bzr for packaging? [02:00] I'm wondering what a good strategy for using branches for patches [02:00] I guess if you create a branch off of an upstream branch it would work === freeflyi1g is now known as freeflying === jcfp is now known as Guest9965 [09:34] on the subject of bug 332722 [09:34] Launchpad bug 332722 in ubuntu "[needs-packaging] suvat" [Wishlist,New] https://launchpad.net/bugs/332722 [09:34] I was sent here to discuss it (as it's my project) [10:35] i was sent here to discuss bug 332722 as it's my package [10:35] Launchpad bug 332722 in ubuntu "[needs-packaging] suvat" [Wishlist,New] https://launchpad.net/bugs/332722 [10:44] madmartian: Have you prepared a source package? [10:44] it's in a ppa [10:44] https://launchpad.net/~suvat-dev/+archive/ppa [10:45] madmartian: OK, we usually review new package at revu.ubuntuwire.com, would you like me to import it there? [10:45] jpds: yes please [10:50] madmartian: OK; it appears that you have to login to revu to request to have a package imported, could you please do that? [10:52] ...although I could just dget your source package from the PPA and put it in the processing queue. [10:55] jpds: done, thanks for your help [11:11] how do I name the orig src tarball if I want to package a piece of software that is only available through svn?(concerning the version) [11:11] hey tdomhan [11:12] it's usually done as version+svn [11:12] hi james [11:12] if there are no releases at all that is a bit more difficult [11:12] 0.0.0+svn ? [11:12] there has been a release 1.27 [11:12] and you can use the date instead of the revno [11:12] I personally prefer: svnYYYYMMDD. [11:12] should I name it 1.28svn? [11:12] tdomhan, in that case, use 1.2.7+svn375218367853721 [11:13] tdomhan, no, for 2 reasons [11:14] tdomhan, if it's BASED on 1.27 (e.g. from a 1.27 branch) then use 1.27+svn; if it's BASED on 1.28 (e.g. from trunk leading towards a 1.28 release) then use 1.28~svn [11:14] tdomhan, using the ~ in the second example is very important [11:14] kk, it's the latter one, what are the meanings of +/~? [11:15] tdomhan, 1.28~svn100 is "older" than 1.28 [11:15] tdomhan, 1.27+svn100 is "newer" than 1.27 [11:20] kk thank you [11:24] "dpkg --compare-versions" can be used to check that two version numbers sort in the way that you think [11:25] ooi, is there a clear documentation of the algorithm anywhere? I resorted to the source to learn it [11:25] maxb: there was a discussion on d-d some time ago on exactly that question [11:26] I like 0~1 as a version. it's smaller than zero but positive :) [11:26] There's no such thing as a negative version [11:27] tdomhan, I use the naming system seen on the deng package here -> https://launchpad.net/~yagisan/+archive/ppa [11:28] That naming system is, IMO, inadvisable [11:29] It's overly verbose, and worse, it risks colliding with an official ubuntu package [11:29] maxb: but 0~1 < 0 [11:29] Yagisan's scheme is standard [11:29] mok0: for PPAs? [11:30] yep [11:30] maxb, consider my package is what will eventually be the offical ubuntu packe - I see no issues with it [11:30] It's not frowned upon to publish packages to PPAs that have versions which could be used in the primary archive? [11:31] No on the contrary [11:31] You should not use version numbers that might appear in the archive [11:32] -0ubuntu1~ppa1 is overwritten by -0ubuntu1 which gives the effect you want [11:32] the deng package in Yagisan's PPA ends -0ubuntu1, no ~ppa1, which is what I'm calling out as inadvisable [11:33] right [11:33] I've forgotten it too, occasionally [11:34] maxb, it's also been pending inclusion for what 2 years now ? It still can't get in, so the ppa can be skipped until I can actually get in [11:35] Yagisan: pending, where? [11:35] Yagisan: regardless, that doesn't mean you shouldn't practice good versioning hygiene [11:36] I agree [11:36] mok0, I've been sorting out license issues, and security issues ever since was it hoary or breezy - been such a long time now [11:36] Yagisan: what if it gets in with changes? Then your ppa version is not overwritten [11:36] I guarantee you'll never have an official ubuntu version that will conflict with it [11:37] Yagisan: you can't give such a guarantee [11:37] I sure can. as a former upstream, I can categorily state the is a remote eploitable security issue in it, and you can not include it under those grounds [11:38] thus [11:38] I can guarantee it [11:38] Well if that's the case, I'd say you should be deleting it from your PPA... [11:38] Yagisan: there are 330942 examples in Launchpad I can cite to disprove you :-) [11:38] (FYI - design issue - and getting that fixed has been more of a headache than the licensing issues were!) [11:39] Regardless of what you can say about any specific upstream version, that's no reason not to apply good versioning practices [11:40] I have. there will never be an official intrepid version, and when it finally can go in (assuming I haven't given up) any older versions will upgrade [11:42] Yagisan: where are you trying to get it in? [11:44] mok0, one day, far far far into the future it appears, I would like to see it in universe as it is/was a fun little game. Right now it fails a DFSG test over some issue with wording in an otherwise free license [11:45] Yagisan: If you are upstream, just fix the license then [11:45] mok0, and when I started, some 33% of the code base was GPL incompatible non-free code, so I'm doing well [11:46] mok0, **former** upstream, and that code didn't come from us. adocating it's removeal didn't go down well either ... [11:47] Yagisan: How sad [11:48] mok0, joys of politics mate - they no longer have a linux dev. That and I got canned over security fixes, and was vocal in my disapproval of windows only features being planned [11:49] Yagisan: perhaps you should move on and use your skills for a better cause [11:50] * Yagisan has. I have several other projects - but I do enjoy playing this one, and there is interest in an Ubuntu package, so I update it in my ppa [12:13] * RainCT wonders why Totem fails to play a song on a memory limited system with BadAlloc but Rhyhtmbox doesn't [12:18] Is there any channel where dbus experts hang out? Specifically I'm wondering "Is there any way to override session-bus service configuration on a per-user basis?" [13:09] Hi. I'd like to apply to U-C-D and already setup my wiki page? Should I send first the email to the mailing list or get the comments of the people that sponsored my uploads? [13:11] fabrice_sp_: get your sponsors comment on your application in your wiki page and when you have enough comments apply "formally" [13:15] thanks geser! [13:17] so, mok0, james_w and any MOTU whot sponsored my uploads recently: could you please put a comment on my wiki application page? Thanks! [13:17] james_w: btw, http://jameswestby.net/weblog/bzr/03-sandwich.html gives a blank page here [13:17] RainCT: how, odd, it worked yesterday [13:20] RainCT: should be fixed now, thanks [13:21] james_w: no problem. funny post :) [13:21] fabrice_sp_: sure [13:22] geser: did you see my reply to your question? [13:23] mok0: yes [13:23] mok0: so the PPA would only be used between FF and the next archive opening? [13:23] geser: Yes [13:24] geser: perhaps we come up with other uses, but that's the idea [13:25] mok0: who should be able to upload there? only ~ubuntu-dev? [13:25] geser: yes [13:26] geser: when the package passes review, and if the main archive is closed [13:27] geser: or.... perhaps if some rigorous testing is required??? [13:38] fabrice_sp_: do you have a list of uploads of yours that I sponsored? [13:39] oh, this is a U-C-D application, no need [13:53] mok0: I also like the idea of an 'official' PPA to build against for libs so New doesn't add to latency for doing a sequence of packages. [14:30] * RainCT pokes asac [14:37] ScottK: yes, it helps for packages that have a serial dependency [15:22] RainCT: ? [15:35] asac: Yesterday I asked whether we still want new extensions for Jaunty (now that FF has started, that is), like last cycle? [15:35] RainCT: depends on the extension. [15:36] i wont grant a general exception if thats what you ask [15:36] there are a few that missed FF because i was too overloaded to sponsor. those will certainly get in [15:36] on top i need to look at the specific extension [15:51] asac: Ah OK. I was thinking that if there was to be a general exception again I could take a look at packaging google gears [15:53] RainCT: is that free? [15:54] asac: Yes, New BSD [15:54] RainCT: go ahead and package it ... we can then look ;) [15:54] if its an important addition to the ubuntu-extension eco system it might be worth looking into an exception [15:55] Alright. The main advantage of having it packaged is that there's a patch to let it work with 64-bit systems, but Google hasn't accepted it so far. That's quite annoying as there are custom .xpi builds with it but when there comes a new version Firefox is all the time asking to update it (which it can't as it then tries with the 32 bit version) [16:00] RainCT: yes, amd64 support is an important use case [16:00] RainCT: is there a branch alreawdy [16:00] i just have kind of dejavu now that i think about it [16:00] like i already reviewed a package at some point [16:10] asac: Afaik no [16:12] can i create a watch file to look to a svn repo in which there are the release file and not a tar archive? [16:12] if yes can someone point me an example? [16:18] RainCT: then go for it ;) ... quick! [16:20] <__iron> hi [16:21] <__iron> what it is to do to get moto status ? [16:22] __iron: follow the links in the channel topic [16:22] <__iron> k [16:29] nevermind, solved in another way :) [16:30] goshawk: you can write a get-orig-source rule [16:32] RainCT: i solved using an http page in which there is a link to the tarbal [16:32] so in a complete different way [16:33] goshawk: ah, that's better :) [16:33] the problem right now is this one: Newest version on remote site is 0.99.7.0.99.7, local version is 0.99.7 [16:33] it gets the version two times [16:33] this is the watch [16:33] http://www.dsource.org/projects/tango/wiki/SourceDownloads http://downloads.dsource.org/projects/tango/([\d\.]+)/tango-([\d\.]+)-src.tar.gz [16:33] add ?: after the first ( [16:33] first one is the html page [16:33] http://downloads.dsource.org/projects/tango/(?:[\d\.]+)/tango-([\d\.]+)-src.tar.gz [16:35] perfect [16:35] it works [16:35] can you please tell me what that ?: [16:35] mean? [16:36] goshawk: parenthesis mark a group the content of which is selected; the ?: mean that you don't want that group [16:38] ok perfect, understood :) thx as everytime... [16:39] No problem. In case you have more difficulties with the watch file in the future, http://www.regular-expressions.info/ is a quite good resource. [16:39] Although the rules in debian/watch are usually quite simple [16:40] oki [16:42] i've uploaded libtango to REVU [16:42] nhandler: do you have some text for the FF warning? [16:42] if someone have spare time, please review :) thx all [16:43] RainCT: Not right now. I can write something up if you want [17:00] nhandler: There's a warning now. Does it look good to you? [17:01] nhandler: (it can be disabled once Koala is open changing "feature_freeze = 1" to 0 in /srv/revu-production/config/revu.cfg) [17:04] RainCT: http://paste.ubuntu.com/121479/. I made a few wording changes. I also removed the word "Jaunty" so that we don't need to update it for each release [17:04] nhandler: the distribution name is also taken from the config file ;) [17:04] Ok, I didn't know that. Then you can add Jaunty back in ;) [17:07] nhandler: I'm also pondering changing the header (the "A Review Tool for MOTUs" - it's not only for MOTU :)). What do you think about "Collaborative Ubuntu packages reviewing"? [17:12] (that's an open question to anyone who wants to answer :)) [17:13] RainCT: I have no objections. But we will also need to update a lot of the links that go to REVU [17:13] nhandler: Erm.. Why? [17:14] RainCT: Because a lot of links use the text "A Review Tool for MOTUs" [17:15] It is a tool for MOTUs. [17:15] ScottK: and for non-MOTUs who want to get a package into Ubuntu :) [17:16] It's a tool to help us do reviews. [17:16] and afaik MOTU is going away with archive reorg [17:16] Yes, so eventually it will have to be changed. [17:18] ScottK: So are you OK with changing the header? [17:19] I think you should ask a broader section of MOTU than "is on IRC right now". [17:19] nhandler: well, that REVU itself shows a different title doesn't mean that the links pointing to it must have the same name [17:19] I'd prefer not, but it's not a big deal. [17:19] So I don't object, other than please mail the MOTU ML first so others have a chance to object. [17:20] I'll leave it for later then. Don't feel like sending a mail just to change a string :P [17:21] nhandler: (the changes you've proposed will be up once LP processes my commit) [17:21] scottk: I also don't agree that the entire MOTU community needs a chance to decide. It isn't as if we are changing the name of REVU, just the description [17:21] Ok RainCT [17:22] nhandler: It's been call that for years. I do think people ought to at least get a chance to object. [17:24] * RainCT wonders why REVU is in Softpedia o_O [17:27] scottk: I still disagree. We do not ask for input when we change a package's description. We don't ask for input when we change a team's description on LP, and we don't ask for input when we change a wiki pages description. I really do not think changing REVU description is a huge deal. [17:29] nhandler: If you change the description of a team I'm a member of without getting input from the team, I would not appreciate that. It's not very Ubuntu. [17:31] ScottK: you didn't complain when the ~revu-uploaders description was updated [17:31] Did I know? [17:32] I don't see the harm in a quick mail to the ML saying, "I'm planning on doing X unless anyone objects". [17:32] i'm curious, how many people here like update-manager to spawn whenever there's an update as opposed to just having update-notifier show an icon in the notification area? [17:33] and how many don't notice the addition of a new icon in the notification area? [17:33] especially one so bright and orange as the update-notifier icon [17:33] I don't use Ubuntu, so I don't have the experience, but I can imagine from the descriptions I wouldn't like the change. [17:34] hyperair: I guess I won't like it neither, but haven't seen it yet. [17:34] I'd think a tooltip would be sufficient. [17:34] Although it may actually be better than the tooltip in some use cases [17:34] let's all tell that to ubuntu-devel! [17:34] That damn tooltip once popped up once while I was playing a game and took ages to go away -.- [17:34] i'm incredibly annoyed at this change [17:35] Although that may already be fixed with the new notification system [17:35] But yes, having to dismiss a dialogue asking to update each time there are updates is probably quite annoying, especially as I always upgrade from the terminal (but the icon remembers me to do it) [17:36] RainCT: the new notification system listens for screensaver inhibits and holds messages while they are active [17:36] RainCT: so as long as the game inhibits the screensaver it will work fine [17:37] james_w: Ah. So I guess the game doesn't :(. Is there some CLI command to add an inhibit? [17:37] gnome-screensaver-inhibit or something [17:38] gnome-screensaver-command -i [17:38] there's "xdg-screensaver suspend", but that's trickier to use [17:38] james_w: thanks [17:39] pass "-n" and "-r" to the gnome one as well [17:39] james_w: and how do I delete the inhibit afterwards? [17:40] RainCT: the inhibit is active for as long as the command runs [17:40] I would have thought it was possible to have a command that took another command as argument and inhibited the screensaver for as long as the child was active [17:41] anyone has a system that was installed before intrepid? [17:41] if so, please paste dpkg --query fontconfig-config | grep obsolete [17:41] asac: me [17:41] asac: I have 2 upgraded from Hardy [17:41] hyperair: ^^ ;) [17:41] RainCT: hardy would be good to see too [17:41] asac: hardy -> intrepid [17:42] hyperair: yes. please run the command and paste it [17:42] if there is any output at all ;) [17:42] james_w: yeah, something like that would rock [17:42] asac dpkg: unknown option --query [17:42] hyperair: RainCT: sorry ... its --status ;) [17:42] uhm.. how can I put on the network cable without having irssi reconnecting? :P [17:42] * asac dump ... made the same mistake twice in 2 minutes ;) === iulian is now known as Guest46483 [17:42] RainCT: i think a shell script could do that =\ [17:43] asac: /etc/fonts/conf.avail/README 296384642206e0c9952d5c73a5451eec obsolete [17:43] hyperair: ok. just that? [17:43] asac: yes just that [17:43] asac: http://paste.ubuntu.com/121504/ [17:43] <__iron> asac: ive got more [17:43] james_w: thanks. when installed? hardy? gutsy? [17:44] umm, feisty? [17:44] oh [17:44] ok [17:44] wow that's long [17:44] heh [17:44] james_w: thats less than i expected. i had a bunch more on my since-edgy system [17:44] i'll probably reinstall for jaunty =\ [17:44] i want to switch to amd64 [17:44] __iron: please paste [17:44] <__iron> http://paste.ubuntu.com/121506/ [17:45] james_w: can you run a md5sum on a few and see if they were changed? [17:46] or maybe you __iron ;) [17:46] <__iron> asac: ? [17:46] asac: all match dpkg's values [17:46] james_w: great. thanks a lot [17:47] am I still alive? [17:47] RainCT: it's not clear [17:47] __iron: nevermind. you can run md5sum on the file and see whether it matches the md5sum in the output [17:47] __iron: but james already answered [17:48] asac: http://paste.ubuntu.com/121510/plain/ (on one PC, the other one is offline right now) [17:49] RainCT: also feisty install? [17:49] <__iron> asac: one of them http://paste.ubuntu.com/121512/ [17:50] asac: nope, I use to make clean installs when I upgrade [17:50] __iron: right. that matches. [17:50] RainCT: so you installed when? intrepid? [17:50] or even jaunty? [17:50] asac: Ah. That one is an Intrepid upgraded from Hardy [17:50] RainCT: see ;) [17:51] so meaning the cruft is from hardy or intrepid [17:51] feisty had the same [17:51] my edgy had a bunch more ;) [17:52] what are menu-files for? to create a node under "applications" I have to provide a .desktop-file, haven't I? [17:52] tdomhan: menu files are for Debian's menu, .desktop for all others [17:53] tdomhan: although sometimes menu files are also used in Ubuntu (for example, the default menu in Openbox uses them) [17:53] they are not needed at all under ubuntu? [17:54] mh ok, just created one, then I will leave it [17:57] tdomhan: they are encouraged, and not that difficult to create after all [17:57] RainCT, kk thanks for the information, I will just create a .desktop file aditionally [17:58] tdomhan: Okay. Don't forget to run desktop-file-validate on it afterwards [18:08] RainCT: have you ever taken a look at storm? [18:09] mok0: nope [18:09] RainCT: Looks really cool [18:10] RainCT: I think it's used for LP [18:10] It is. [18:10] mok0: what can it do? [18:11] RainCT: it wraps a database in python objects [18:11] mok0: as in, removing the need for SQL? [18:11] RainCT: yes [18:12] RainCT: SQL is behind the scenes of course [18:12] I guess persia likes it then :P [18:12] ScottK, have you used it? [18:12] I have not. [18:12]