[00:01] <bdrung> arand: ping
[04:41] <imbrandon> hrm, i want to get a computer "fingerprint" , sugestions ?
[04:42] <ajmitch> in what sense?
[04:42] <ajmitch> some form of hardware identifier?
[04:43] <imbrandon> yea
[04:43]  * ajmitch guesses maybe info from dmidecode, or other tools like that
[04:44] <imbrandon> i was thinking something like a proc serial num and some identifying number from the /boot hdd and hash it
[04:44] <imbrandon> or something
[04:44] <imbrandon> dunno
[04:45] <imbrandon> hrm dmidecode lookes intresting
[04:45] <imbrandon> what about systems with efi and no bios
[04:48] <ajmitch> no idea
[05:00] <lfaraone> I see some Debian packages with Ubuntu changes in Launchpad with revision schemes like "-1build3" yet there are non-rebuild-only changes. Should I break the scheme when appling a patch and change it to "-1ubuntu1'?
[05:02] <ajmitch> lfaraone: yes
[05:02] <imbrandon> lfaraone: sounds sane
[05:12] <lfaraone> Likewise, bug 578717 seems like something that can only effect Lucid. Does it need to be "fixed" in Maverick before being SRU'd?
[05:16] <lfaraone> Nevermind, silly question.
[06:11] <kobrien> hey guys, I've tried a yesterday in #ubuntu-java but got no answer. I'm packaging a java app with cdbs. I get the following error: java.lang.ClassNotFoundException: org.apache.tools.ant.util.regexp.Jdk14RegexpRegexp. Any ideas?
[06:12] <kobrien> also as part of the same error is a note about not being able to find a regexp matcher. Now, I have installed ant-optional, and that doesn't fix it. JAVA_HOME is also set correctly.
[07:32] <\sh> moins
[08:17] <dholbach> good morning
[08:28] <ripps> Hmm... In Maverick, why is libwildmidi only 'i386', and not 'all' like in previous releases?
[08:29] <ripps> err libwildmidi-dev, that is.
[10:40] <DeeJay1> hello! I have a small question - how can I get deb package descriptions translated?
[10:41] <Rhonda> DeeJay1: If I'm not mistaken it uses the http://ddtp.debian.net/ service.
[10:42] <Rhonda> … and I still wonder when djpig will wake up to get my patches for the ubuntu-master branch of packages.git applied.  %-/
[10:45] <DeeJay1> "Real names consist of alphanumeric characters, spaces and quotes and are at least 6 letter long, thanks" - well, real names consist of UTF-8 characters LOL@ddtp
[10:53] <Rhonda> DeeJay1: utf-8 characters for names are a subset of alphanumeric
[10:53] <DeeJay1> well, not for ddtp
[10:53] <Rhonda> But I'm sure that Wookey begs to differ big time here, too.
[10:53] <Rhonda> Hmm, but then, wookey is 6 characters.
[10:54] <Rhonda> DeeJay1: I am having big issues with that interface myself too, but then it's the only thing we've got.
[11:04] <DeeJay1> eh, well it could be worse
[11:09] <Rhonda> Not much. The "review" of it isn't worth the term, it's a click-through thing that happens within the minutes without much possibility to leave the "translator" any hints or message.
[11:55] <ScottK> lfaraone: WRT packages with buildX suffixes and actual changes in them, it's not rare for people to upload that way if the change is already in Debian.
[11:56] <ScottK> lfaraone: So please be careful about undoing that.
[12:38] <iefremov> Hi All! Can anyone help me with the following issue: my package (ugene) fails to start in Lucid with symbol lookup error. I suspect that this issue can be fixed in stable release by simple rebuilding of the package. But SRU process requires some fixes/patches etc. Is there a way to request a rebuild without patching anything ? For details, see https://bugs.launchpad.net/ubuntu/+source/ugene/+bug/566146
[12:38] <Laney> you should just be able to ask for a rebuild in an SRU
[12:39] <iefremov> Laney, should I create a separate bug, or request the rebuild in an existing one (https://bugs.launchpad.net/ubuntu/+source/ugene/+bug/566146) ?
[12:39] <Laney> just do it in that one
[12:40] <iefremov> Ok, thanks! I will try this.
[13:38] <lfaraone> james_w: Oliver Tilloy reverted the @PACKAGENAME@ change per your request in lp:~osomon/ubuntu/maverick/epiphany-browser/user_agent. Do you think the branch is now ready to be merged?
[13:38] <james_w> lfaraone: I do
[13:39] <lfaraone> james_w: okay, I've got it.
[13:39] <james_w> thanks
[13:59] <effie_jayx> hello all
[14:00] <effie_jayx> does one need to enable backports ion order for pbuilder to know about Maverick as a release?
[14:01] <Rhonda> effie_jayx: You can always work around by creating a lucid chroot, --login --safe-after-login and change sources.list to maverick and then do an --update
[14:02] <effie_jayx> Rhonda: that is a neat trick
[14:02] <effie_jayx> I am curious since I tried creating the maverick chroot and I enabled the backports and pbuilder was not updated
[14:02] <effie_jayx> will keep that in mind thanks Rhonda
[14:03] <Rhonda> That's the one that usually works when bootstrapping a new devel version isn't working because of toolchain b0rkage. :)
[14:06] <effie_jayx> btw the multiple pbuilders section in https://wiki.ubuntu.com/PbuilderHowto needs a maverick there
[14:06] <effie_jayx> Rhonda: thanks again :)
[14:09] <Rhonda> effie_jayx: As that is a wiki I figure you can fix it on yourself too? :)
[14:11] <effie_jayx> Rhonda: well just though I needed clearace
[14:11] <effie_jayx> :P
[14:13] <effie_jayx> done
[14:19] <Quintasan> hiho
[14:47] <ScottK> effie_jayx: The changes for a maverick chroot were done before release, so no backports needed.
[15:18] <\sh> RainCT, pingeling
[15:18] <\sh> hey ScottK
[15:18] <ScottK> \sh: Hello.
[15:19] <\sh> ScottK, couldn't say "good buy" on saturday morning...hope you arrived home safely without any ashcloud madness
[15:19] <\sh> good bye I mean...still not recovered
[15:19] <ScottK> \sh: Yes.  No troubles at all.
[15:19] <ScottK> \sh: Yeah, me too.
[15:20]  * ScottK is currently staring at the cat man page trying to remember how to use it ...
[15:20] <\sh> hehe
[15:25] <RainCT> Heya \sh
[15:26] <\sh> RainCT, check your query
[15:26] <micahg> hi \sh
[15:27] <\sh> hey micahg
[15:27] <arand> If in QUILT I've got debian/patches/debian in quilt, and imported my patch to debian/patches/1.patch would "quilt rename 1.diff debian/1.diff" be the best thing to do as far as organisation?
[15:29] <arand> Also does it matter if it's -p0? (The original imported is.)
[15:35] <arand> And.. How would I reference a Fedora bug (source of fix) in the changlog?
[15:37] <ScottK> arand: How about "Fedora Bug #nnnnnn"?  There isn't a standard rule for that.
[15:38] <AnAnt> if it is a patch, there is a header for this
[15:38] <arand> Okay.
[15:39] <ScottK> True.  That's the place for details like a link to the exact place you got the patch from.
[15:40] <arand> Yea, I've written a header, but I thought I'd put it down in the changelog as well..
[15:40] <AnAnt> Bug-Fedora
[15:40] <AnAnt> ah, ok
[16:00] <arand> Should a quilt patch be refreshed to apply with -p1, or kept true to original with -p0  (lintian warns on -p0)
[16:02] <AnAnt> p1 I recall
[17:37] <_Andrew> I'm building a package for hardy under compat 6. In my install file I have "usr/bin" however dh_install fails to find /usr/bin/xyz
[17:37] <_Andrew> Any ideas?
[17:38] <_Andrew> I've tried "usr/bin/*" and "debian/tmp/usr/bin", etc
[17:40] <_Andrew> I'm using "dh_install --sourcedir=debian/tmp --fail-missing"
[20:26]  * abogani waves
[20:34] <abogani> imbrandon: Are you around?
[20:38] <abogani> imbrandon: Sorry for delay in reply. I have placed the updated version of linux-rt package for Lucid in my PPA at: https://launchpad.net/~abogani/+archive/broken/+packages
[21:13] <imbrandon> kk
[23:29] <arand> If a patched package in -proposed fails, is it enough to simply comment on the original bug?
[23:32] <crimsun> arand: do you mean that the -proposed packages "fails" to resolve the symptom of the bug? Yes, comment.
[23:33] <crimsun> "fails" there is ambiguous, namely "fails to install", "fails to upgrade", etc. are all valid interpretations ;-)
[23:33] <arand> Yes, it's Bug #526849, the hardy fix is incomplete.
[23:33] <crimsun> (nonetheless they're all cause for validation-failed)
[23:34] <ajmitch> "causes irreparable data loss" is also another fail, though unlikely in this case
[23:34] <arand> Yea, I've marked that as well, I was just thinking if there werer any more things to be done.
[23:34] <arand> It's simply that the pastebinit link output is garbled
[23:39] <arand> Where can I see the -proposed queue by the way?
[23:42] <ajmitch> https://edge.launchpad.net/ubuntu/hardy/+queue?queue_state=1&queue_text=
[23:42] <ajmitch> I think that's what you were looking for?
[23:43] <arand> ajmitch: cheers :) The queues are always a bugger to find...
[23:43] <ajmitch> you've checked that you have the right version of pastebinit installed before testing?
[23:45]  * ajmitch had an SRU for boost1.38 where the person testing have a self-compiled python-visual, which was linked against an old, unpatched boost version
[23:45] <ajmitch> thankfully we got that sorted
[23:47] <arand> ajmitch: Yea, well, the patch is exactly the same as I tested earlier and confirmed as not working on hardy...
[23:48] <arand> Seems like someone didn't read my comments :D
[23:48] <ajmitch> right, the bit about the patch being unfinished :)
[23:49] <ajmitch> problem is that the tags apply across all releases, so while it may be fixed on jaunty, you can only tag it as failed for all
[23:49] <ajmitch> how annoying
[23:50] <arand> Yea, well I'm marking as committed for k&j and confimed for hh, so there's at least som distinction there