[01:23] <hzsp> hi.  I've reported a bug but I've filed it against the wrong package.  can I fix this or do I have to find someone with sufficient privileges?
[01:25] <hggdh> hzsp: you can fix it, just change the package
[01:25] <hzsp> hggdh: I can't see a button to do it :)
[01:25] <hggdh> hzsp: bug #?
[01:26] <hzsp> 858310
[01:26] <hggdh> bug 858310
[01:26] <ubot4`> Launchpad bug 858310 in gnome-settings-daemon (Ubuntu) "Two sounds are played when choosing new alert sound (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/858310
[01:26] <hzsp> should be gnome-control-center, not gnome-settings-daemon
[01:26] <hggdh> done
[01:27] <hzsp> thanks!
[01:27] <hzsp> the folks at #ubuntu-devel have helped me get this thing building from source.  I might even have a go at fixing it later today :-)
[08:28] <grizzlysmit> hi trying to report a bug against synaptic in Precise Pangolin but cannot get to the page :(
[09:13] <grmls> hi
[11:49] <veger> I could use some help/advice with bug #609106, I think it should be closed as wontfix
[11:49] <ubot4`> Launchpad bug 609106 in pbuilder (Ubuntu) "pbuilderrc manpage doesn't mention that quotes are needed around multiple components (affects: 1)" [Low,Triaged] https://launchpad.net/bugs/609106
[11:49] <veger> anyone around to hear me out?
[11:54] <yofel> I don't see why it should be closed. Mutliple values need quotes, and you can misunderstand the manpage if you don't have enough shell experience
[11:54] <yofel> and pbuilderrc essentially has sh syntax
[11:55] <veger> The manpage says the pbuilderrc is sourced as a shell script
[11:55] <veger> so the COMPONENTS=main part is basically a variable and thus it should automatically include quotes when a space is required
[11:56] <yofel> yeah, but if you look at the options, they're a random mix of single values, mutliple values with quotes and multiple values without quotes (wrong)
[11:56] <yofel> for example: DEBEMAIL=Maintainer Name <Mail@Address> simply won't work like that
[11:57] <yofel> so the manpage needs fixing in any case
[11:57] <veger> true, so I should pass the report to debian
[11:57] <veger> and make it more general?
[11:57] <yofel> yeah, this should go to debian as they're the maintainers of pbuilder
[11:58] <veger> ok, will do that
[11:58] <yofel> post the issue that was reported and note that there are other misleading options too
[11:58] <veger> another (quick) thing, could you set thestatus of pbuilder in bug #770529 to Triaged?
[11:58] <ubot4`> Launchpad bug 770529 in ubuntu-dev-tools (Ubuntu) (and 2 other projects) "[pbuilder-dist] doesn't autocomplete directory path (affects: 2) (dups: 1) (heat: 20)" [Low,Triaged] https://launchpad.net/bugs/770529
[12:01] <veger> thanks
[12:01] <yofel> veger: done
[13:02] <veger> I have another question if any around is willing to answer (or direct me to the correct group)?
[13:03] <penguin42> ask the question
[13:03] <veger> I have updated the jsch package, as the my generated SSH keys were not accepted by the version distributed to ubuntu
[13:03] <veger> what s hould I do to get it accepted?
[13:03] <veger> to Ubuntu and/or debian
[13:04] <veger> see bug #803492 for the upgrade request
[13:04] <ubot4`> Launchpad bug 803492 in jsch (Ubuntu) "New upstream version 0.1.44 (affects: 1) (heat: 7)" [Undecided,In progress] https://launchpad.net/bugs/803492
[13:04]  * penguin42 looks
[13:05] <veger> I believe my own problem was fixed in 0.1.43: feature: support for private keys ciphered with aes192-cbc and aes128-cbc.
[13:07] <penguin42> hmm I've done simple fixes - but not got an update to a new version pushed through
[13:07] <veger> me neither... ;)
[13:08] <veger> should I ask in another channel?
[13:08] <Ampelbein> veger: Please follow http://wiki.ubuntu.com/SponsorshipProcess, attach a debdiff, subscribe the sponsors
[13:08] <Ampelbein> veger: #ubuntu-motu or #ubuntu-packaging are better for those kinds of questions.
[13:08] <veger> ok, thanks I'll read that page to get further instructions
[13:09] <veger> and 'bother' those guys :)
[17:40] <RedSingularity> jibel: Any reason bug 874220 was not marked triaged?  It is still effecting many users.
[17:40] <ubot4`> Launchpad bug 874220 in kdevplatform (Ubuntu Oneiric) (and 1 other project) "[MASTER] Failed to calculate the upgrade to Ubuntu 11.10: libsublime2 breaks on libsublime1 (affects: 29) (dups: 25) (heat: 104)" [Medium,Confirmed] https://launchpad.net/bugs/874220
[23:10] <mainerror> Hello.
[23:16] <mainerror> I've reported a bug #930745 but it was closed as a duplicate of #764700 which is closed because it expired.
[23:16] <ubot4`> Launchpad bug 930745 in xorg-server (Ubuntu) "Xorg crashed with SIGABRT in raise() (dup-of: 764700)" [Undecided,New] https://launchpad.net/bugs/930745
[23:16] <ubot4`> Launchpad bug 764700 in xorg-server (Ubuntu) "Xorg crashed with SIGABRT in utouch_frame_sync() (affects: 2) (dups: 1) (heat: 3)" [High,Expired] https://launchpad.net/bugs/764700
[23:17] <mainerror> I doesn't really make sense.