[00:16] <lfaraone> porthose: hey, would you mind reacking on bug 555948 (if it is needed). I mistakenly requested a sync from unstable when I meant to perform one from sid. (that was what I had tested)
[00:17] <crimsun> lfaraone: err...
[00:18] <crimsun> unstable <-> sid. Did you mean testing for one of them?
[00:19] <lfaraone> crimsun: squeeze/testing, sorry.
[00:19] <lfaraone> porthose: s/unstable/testing/g
[00:21] <crimsun> lfaraone: doesn't need a re-Ack, but I updated the description
[00:47] <crimsun> bdrung: WRT #555891, please use linux-alsa-driver-modules-$(uname -r) from ppa:ubuntu-audio-dev
[01:30] <bdrung> crimsun: ok, i will try that tomorrow
[04:14] <Semitones> hello guys! I was trying to install planetpenguin racer, and I found something curious
[04:14] <persia> What?
[04:15] <Semitones> Does it seem strange that planetpenguin-racer-extras is included in lucid and karmic
[04:15] <Semitones> but planetpenguin-racer is not? http://packages.ubuntu.com/search?keywords=planetpenguin-racer
[04:15] <Semitones> it seems like you'd need the game for the -extras to be useful
[04:15] <persia> Indeed.
[04:16] <Semitones> so... any guesses to why the game isn't there?
[04:16] <persia> You want to install extremetuxracer
[04:16] <Semitones> oh, I didn't realize it was a continuation of tux racer, but I did see it
[04:16] <Semitones> thanks persia
[08:17] <dholbach> good morning
[08:17] <geser> good morning
[08:17] <stefanlsd> morning!
[08:18] <dholbach> hey geser, hey stefanlsd
[08:44] <\sh> moins
[09:38] <jetienne> q. is there a way to know the dependancy of a .deb ? i got only the .deb fiel
[09:39] <Rhonda> jetienne: dpkg --info foo.deb
[09:39] <jetienne> Rhonda: thanks
[10:50] <m4rtin> hi all; I've written a bugfix patch for bash-completion, as requested by a member the sponsor team, but am struggling to get a debdiff up. I've got the lucid source package and it uses quilt. There is also a diff file listed. Should I apply this before running any quilt commands?
[10:54] <Rhonda> m4rtin: I'd do a "quilt push -a" before starting to patch, and "quilt new my-bash-completion-fix" (or some more suiting name) before you start "quilt edit"ing the files.
[10:58] <m4rtin> Rhonda: thanks; so: 1. untar apt source; 2. quilt push -a; 3. quilt new; 4. apply lucid source diff; 5. do my edits?
[10:59] <m4rtin> hmm, seems not
[10:59] <m4rtin> the lucid patch places the series patches in the dir
[11:03] <persia> m4rtin: When you get the .dsc file, use dpkg-source -x to extract it.  This will apply the diff.gz.  Inside that, export QUILT_PATCHES=debian/patches and run quilt push -a
[11:03] <persia> !patch
[11:04] <persia> Check the second link for more details
[11:05] <m4rtin> persia: thank you -- that's what I needed :) one further q if I may: does my changelog have to be inside the quilt edits, or is the packaging process outside of quilt?
[11:06] <persia> Please *don't* put the stuff in debian/ inside quilt patches: this just confuses the next person.
[11:06] <m4rtin> persia: excellent. So I've done my edit. quilt refresh; quilt pop -a; do the packaging
[11:33] <jetienne> q. i would like to create a user in the .deb, how can i do that ? "sudo adduser slotaaa" keeps asking for interactive question. i dont want interactive stuff
[11:41] <joaopinto> jetienne, check on how it's done on other packages, eg. postfix
[11:43] <persia> Or check debian policy 9.2: http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2
[11:44] <Rhonda> jetienne: … and sudo isn't needed, the maintainer scripts run as root. :)
[11:46] <jetienne> ok trying to get postfix example
[11:47] <m4rtin> could someone take a look at a patch I've attached and tell me if it looks ok please? It's at https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/435055 ; last comment
[11:49] <persia> m4rtin: It looks sane, but you may want to advertise in #ubuntu-devel, as there's a better chance someone there will be able to upload.  Also, did you submit the bare patch (not debdiff) to Debian?
[11:49] <hyperair> bash completion? i remember it failed for spaces for everything sometime back.
[11:50] <m4rtin> hyperair: no, I didn't... should I have?
[11:50] <m4rtin> hyperair: it still fails that for scp; that's my next task
[11:50] <hyperair> m4rtin: didn't what?
[11:50] <hyperair> m4rtin: oh i mean cat blah<tab> didn't work, for example.
[11:50] <m4rtin> sorry that was to persia
[11:50] <hyperair> i mean it'd complete up to the first space and stall
[11:51]  * hyperair goes back into lurk mode
[11:51] <m4rtin> persia: I didn't submit to debian... should I (and how?)
[11:52] <hyperair> mentors.debian.net
[11:53] <persia> m4rtin: http://www.debian.org/Bugs/Reporting and https://wiki.ubuntu.com/Debian/Bugs and https://wiki.ubuntu.com/Debian/Usertagging : short form "use submittodebian"
[11:54] <persia> hyperair: Not best for a well-maintained package, usually, unless one has a prior relationship with the maintainers.
[11:54] <hyperair> persia: oh whoops. sorry i wasn't thinking (my mind was thinking new package)
[11:54] <hyperair> m4rtin: regarding bash-completion perhaps it's best to poke some people in #bash-completion on irc.oftc.net
[11:55] <persia> Indeed.
[11:55] <persia> Getting the patch there helps *everyone*.
[11:55] <m4rtin> the problem is that they have fixed most of these bugs with a massive rewrite in their version control
[11:56] <m4rtin> however, they don't release frequently
[11:56] <m4rtin> it seems better to fix these bugs for lucid/debian and then when bash-completion team decide to release their next stable it will be solved anyway
[16:17] <NCommander> ScottK: ping, do you think a FFE for openttd would possibly fly? I'd like to see if we can sync it from sid
[16:17] <ScottK> Depends on why and what the differences are.
[16:19] <NCommander> ScottK: loads of bug fixes, and its now possible to put it in universe versus multiverse
[16:19] <ScottK> Any new features?
[16:19] <ScottK> Sounds promising.
[16:20] <NCommander> ScottK: better AI I think, haven't compiled it yet
[16:20] <NCommander> ScottK: the version in Ubuntu is fairly old compared to the version in sid
[16:20] <NCommander> 0.7.5 to 1.0
[16:20] <ScottK> It sounds worth looking into.
[16:21] <NCommander> ScottK: that's what I thought, hence why I wanted to ask if a FFE was out of the world of possibility
[16:21] <ScottK> It's not.
[16:27] <slytherin> Any archive admins present here?
[16:31] <persia> slytherin: Usually, but except in special cases, it's best to ask archive-admin questions in #ubuntu-devel
[16:32] <slytherin> Ok. Will ask there.
[17:00] <slytherin> ScottK: Hi. Can you please explain what was the reason behind adding explicit libtalloc-dev build-dep to evolution-mapi?
[17:06] <ScottK> slytherin: It uses the talloc headers (as evidenced by the shlibs generated runtime depends)
[17:12] <slytherin> ScottK: A simple grep -r talloc.h in source yields nothing. Also check this text from build log - warning: dependency on libtalloc.so.2 could be avoided if **** were not uselessly linked against it (they use none of its symbols).
[17:12] <ScottK> slytherin: The fact is that it is linked.
[17:13] <ScottK> slytherin: It's possible it's not needed.
[17:13] <persia> That would involve a buildsystem patch.  Adding another build-dependency is the easy (and safe) way out at this point in the release cycle.
[17:13] <persia> File a bug and fix it right for maverick.
[17:14] <slytherin> ScottK: Right. That is what I meant. It may be unnecessarily linked.
[17:15] <slytherin> ScottK: I was actually planning to file a sync request for version in Debian (2.28.3) which a bug-fix update. Hence I was checking with you if Ubuntu changes are important to keep.
[17:15]  * ScottK isn't saying that's the best solution, just made sense as part of doing the NBS rebuilds for libtalloc0
[17:15] <ScottK> slytherin: I'll leave it for you to decide.
[17:15] <slytherin> In any case libtalloc-dev gets pulled in because of other build-deps.
[17:18] <ScottK> Yes, but one shouldn't rely on that
[17:22] <ari-tczew> jdong: did you talk with SRU team about my objections?
[17:22] <slytherin> ScottK: In this case the (build)dependency seems unnecessary, so I suggest we drop this and make it a sync.
[17:52] <ScottK> slytherin: Your call.
[17:55] <lfaraone> ScottK: would you be willing to review bug 556483? james_w said you felt that it might need a FFE.
[17:56] <lfaraone> ScottK: (it already has the debian changelog attached, there were no upstream changes)
[17:58] <lfaraone> jdstrand: bug 552720 in squeak-vm needs a FFE, right?
[18:01] <jdstrand> lfaraone: squeak-vm is in universe, so based on https://wiki.ubuntu.com/FreezeExceptionProcess I'd say 'no'
[18:02] <jdstrand> lfaraone: plus, as it stands, it is totally unuseable
[18:05] <james_w> lfaraone: please make the request. Unusable as it is will probably make it very likely to get it, but we shouldn't circumvent the process.
[18:06] <lfaraone> james_w, okay.
[18:15]  * jdstrand (re)rereads FreezeExceptionProcess and sees it would need it
[18:18] <lfaraone> jdstrand: I can't seem to find the upstream changelog for that revision, the best I could find was http://squeakvm.org/unix/platforms/unix/doc/RELEASE_NOTES_3.11.3.2135
[18:20] <jdstrand> lfaraone: I see platforms/unix/ChangeLog in the source
[18:24] <jdong> ari-tczew: I was under the understanding you were going to write something up to us
[18:27] <ari-tczew> jdong: [Sunday 28 March 2010] [19:51:51] <jdong> ari-tczew: I'd start with mailing the ubuntu-devel-discuss mailing list, cc'ing the SRU team members, about your concern that the related bugs display in launchpad isn't a satisfactory radar map for what SRU tasks remain needing attention.
[18:28] <jdong> ari-tczew: poor wording, I meant if I were you, I'd start with..
[18:28] <persia> That looks like a request to receive mail to me
[18:28] <jdong> sorry
[18:29] <jdong> language barrier, lost in translation :)
[18:31] <ari-tczew> jdong: so what's the final decision?
[18:32] <jdong> ari-tczew: you start mail, please :)
[18:32] <jdong> it is your concern, so I think you'd be the best to voice it
[18:33] <ari-tczew> jdong: okay, but currect I don't have time, maybe in the second half of april
[18:33] <ari-tczew> s/currect/current
[18:35] <jdong> I am similarly scheduled :)
[18:36] <ari-tczew> hehe
[21:13] <kklimonda> how to request a removal of the unbuildable package?
[21:16] <geser> file a removal bug
[21:16] <geser> why is the package unbuildable?
[21:19] <mhall119> jdstrand: can you check the copyright files in the qimo-* packages in revu please?
[21:23] <kklimonda> geser: it depends on evo 2.30
[21:24] <kklimonda> I
[21:24] <kklimonda> I'm trying to find out if any previous package builds on lucid
[21:28] <geser> kklimonda: what about the last build debs which are still published? do they still work?
[21:29] <kklimonda> geser: they don't install
[21:29] <kklimonda> geser: it's anjal
[21:29] <geser> I assumed it's anjal as there aren't that many packages in depwait on evo 2.30
[21:31] <kklimonda> geser: the ubuntu3 package that is build doesn't install, it has to be rebuilt - I should (1) request package removal and then.. ask to upload no-change ubuntu4 to rebuild it?
[21:33] <kklimonda> (there is another option - to remove anjal from lucid completely as the 0.0.1 release we have is old one)
[21:33] <geser> kklimonda: I'm not sure if LP would allow that and the next question is if the archive admins are OK with this solution as they have to NEW the source again
[21:35] <kklimonda> mhm
[21:35] <kklimonda> I'll ask on #-devel then
[21:36] <kklimonda> ah, you are already on it ;)
[21:37] <geser> it's only related to this
[21:38] <geser> as I've noticed that the old debs are still published but only the new source version
[21:39] <kklimonda> right, that's also a problem - well, there is 0.0.1...ubuntu3 source downloadable but you have to dig -changes list for the link
[21:39] <kklimonda> probably not easy enough
[21:41] <geser> yeah, LP has still the old source but it's not on archive.u.c anymore
[22:07] <jdstrand> mhall119: done
[23:17] <lfaraone> Hm. Does http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548551 look severe enough to justify a sync?
[23:29] <bobbo> evening MOTUs!