/srv/irclogs.ubuntu.com/2008/03/17/#ubuntu-bugs.txt

greg-gIDEA: add an extra button/link on bug reports that members of the Bug Control team can see that does the search that LP does when submitting a new report, the list of similar bugs.  (only for Bug Control to curb the resources requirement)02:17
derelickedmoo02:44
techno_freak:)03:22
=== blue-frog__ is now known as blue-frog
=== blue-frog__ is now known as blue-frog
iwksehi all, I was searching for a duplicate of a bug i'm experiencing but i could not find. In few words, livecd can't boot and give the (initramfs) prompt when is used a usb-cdrom device. The problem seems to be due to initramfs which mount too fastly the new root before the cdrom is probed. It's a known bug?09:25
hggdhanyone noticed the number of g_slice_alloc SIGSEGV we have been having?09:28
techno_freakiwkse, feel free to report the bug, if you do not find a duplicate :)09:30
iwksetechno_freak: :) i'm saying so cause i told it to my friend and he said..ah it's a known bug....i wondered how much is known:)09:31
techno_freakiwkse, have you checked the forums?09:31
iwksetechno_freak: i surfed a on launchpad09:32
iwksetechno_freak: but forums, no..09:32
techno_freakiwkse, still feel free to report a bug, it will help us to know what went wrong :)09:33
iwksetechno_freak: oki :)09:33
=== blue-frog_ is now known as blue-frog
IulianHey12:43
pedro_hello12:43
IulianHiya pedro_12:44
thekornhey Iulian, pedro_12:45
pedro_hello thekorn12:48
IulianHi thekorn12:49
=== blue-frog__ is now known as blue-frog
bddebianBoo14:51
jpatrickbddebian: Moo.14:52
bddebianjpatrick: :-)14:58
bdmurrayhello bug hunters15:48
james_whi bdmurray15:50
bdmurrayjames_w: hey, you mentioned some samba upgrade bug / debconf question right?15:50
james_wbdmurray: yeah, slangasek looked at it and it is kind of intentional behaviour.15:51
james_wor rather unaviodable unwanted behaviour.15:51
bdmurrayokay, I personally saw it this weekend and saved some logs15:51
james_wit should only happen in hardy->hardy upgrades, not dapper-> or gutsy-> so it's fine for release15:51
james_wbdmurray: you didn't happen to look at the diff in the gtk window did you?15:52
bdmurrayYes, I believe I looked at it.15:53
james_wdid it look ok to you?15:53
james_wI wish I had had a proper look at it, rather than just deciding it was unreadable and carrying on15:53
bdmurrayIt seemed okay yes15:56
qensehello15:56
bdmurrayhello!15:56
james_wbdmurray: ok, thanks for looking, I'll keep my eye out in future15:57
james_wor maybe I could try and provoke it.15:57
* james_w finds my pointy stick15:57
bdmurrayjames_w: I captured the 2 config files during the process if you want them15:57
james_wbdmurray: I should just be able to do it by editing the file, thanks.15:58
=== thekorn_ is now known as thekorn
=== secretlondo is now known as secretlondon
=== Spec[x] is now known as Spec
=== noppe is now known as dudicus
james_wthekorn: another cool looking tool, thanks :)17:04
thekornjames_w, hehe17:05
bdmurraymvo: hello there17:07
mvohey bdmurray17:10
Iulianjames_w: Indeed :)17:11
bdmurraymvo: we are going to be looking at update-manager again for tomorrow's hug day. Is there anything new / special we should be aware of?17:16
mvonot that I know of right now17:16
mvolog files are still the most imporant bit required17:16
bdmurraymvo: I also ran across bug 182350 the other day and wasn't clear on the design decision there.17:19
ubotuLaunchpad bug 182350 in update-manager "no longer reports installed and available versions" [Medium,Triaged] https://launchpad.net/bugs/18235017:19
nxvlhi17:28
nxvlhow do i get privilegies to edit the bugs priority?17:28
bdmurraynxvl: you need to be a member of the ubuntu-bugcontrol team to edit bug priority17:28
nxvlbdmurray: so i just need to "join this team" and wait for one admin to accept it, or do i need to send some extra documentation?17:30
bdmurraynxvl: there is some more information at https://wiki.ubuntu.com/UbuntuBugControl17:31
nxvlbdmurray: ok, i have appied and i have al de requirements17:33
nxvli will now searh for 5 bug reports i have triage and i will send you by PM17:33
nxvlis that correct?17:34
bdmurraynxvl: yes, an e-mail to me with those bugs would be great17:35
nxvlok, looking for them now17:37
nxvlbdmurray: fixed bugs doesn't count, doesn't it?17:38
bdmurraynxvl: We are looking for bugs that you have triaged / worked with reporters on, so the bugs can absolutely be fixed.17:39
bdmurrayAdditionally, since as a member of the bug control team you will be able to assign importance it is good to know what importance you would give the bug reports.17:39
mvobdmurray: bug 182350 was a design desision17:51
ubotuLaunchpad bug 182350 in update-manager "no longer reports installed and available versions" [Medium,Triaged] https://launchpad.net/bugs/18235017:51
bdmurraymvo: Okay, I was wondering where it was duplicated.17:52
qenseare there hal developers on? I think they might find bug 203094 interesting18:42
ubotuLaunchpad bug 203094 in libsmbios "hal cannot set brighness on Dell notebook computers if a BIOS password is set" [Undecided,New] https://launchpad.net/bugs/20309418:42
qense(btw, maybe there should be a function added to this channel that you can poke a group)18:43
andrea-bsqense: please try on #ubuntu-dev ;)18:49
james_w#ubuntu-devel18:51
andrea-bsjames_w: #ubuntu-dev redirects to -devel ;)18:54
james_wah, thanks, never knew that, might save some characters.18:55
=== ogra_cmpc_ is now known as ogra_cmpc
andrea-bs:D18:56
Nightrosebdmurray: thx for approving me :)19:37
bdmurrayNightrose: no problem!19:37
bdmurraythekorn: Do you have an idea of how much work it would be to make another html bug listing page parsable?19:39
bdmurrayNightrose: I saw you were having an issue with the Gutsy version of python-launchpad-bugs is that right?19:40
Nightrosejep19:40
bdmurrayDid you look at the upstream version i.e. pull it from bzr?19:41
thekornbdmurray, it depends on how well structured the page is,19:42
Nightrosenope - I just tried the packaged one19:42
thekornbut parsing pages with  xpath is easy19:42
bdmurraythekorn: it's pages like https://launchpad.net/bugs/bugtrackers/gcc-bugzilla19:42
bdmurraythekorn: I forget did you make a gutsy ppa version of python-launchpad-bugs?19:44
thekornbdmurray, yes 0.2.28 for gutsy is in PPA19:46
thekornbdmurray, parsing of these bugtracker pages should be easy,19:47
thekornwhen we find a way to handle the different status/importance values of the different trackers19:48
bdmurrayI'm really just interested in getting the ubuntu bug numbers out of pages like than and then looking for upstream tasks19:49
bdmurrayThe url I posted is a list of ubuntu bugs with http://gcc.gnu.org/bugzilla/ showing up in the comments19:49
bdmurrayAs I understand it19:50
Nightrosethekorn: which ppa? and would you reccomend me to use it? the packaged version in gutsy doesn't work for me19:50
thekornNightrose, https://edge.launchpad.net/~bughelper-dev/+archive19:50
bdmurrayNightrose: we need to do release a new version of python-launchpad-bugs for Gutsy.  I'm sorry about that.19:50
Nightrosethekorn: thx :)19:51
thekornNightrose, I tested it for gutsy like two weeks ago19:51
Nightrosebdmurray: no prob19:51
Nightroseok19:51
bdmurrayIf you go from that list to bug 172326 you'll see that it doesn't have an upstream watch.19:51
ubotuLaunchpad bug 172326 in gcc-4.1 "Reproducable SIGSEGV (char ************* etc.)" [Undecided,New] https://launchpad.net/bugs/17232619:51
bdmurrayBut it should because in the last comment someone says they opened a bug but it just isn't linked to.19:52
thekornbdmurray, right19:52
thekornwill work on parsing this buglist soon19:53
thekornbdmurray, after finishing a first patch to fix bug 20045719:54
ubotuLaunchpad bug 200457 in python-launchpad-bugs "URLBugListFilter missing milestones" [Undecided,New] https://launchpad.net/bugs/20045719:54
Nightrosethekorn, bdmurray: still getting some warnings about API not being stable but it seems to work better now - will play around a little with it - thx20:07
bdmurrayNightrose: that is expected.  Please let us know if you have any questions.20:07
Nightrosewill do :)20:07
nxvlbdmurray: i have send you an e-mail one second ago20:30
bdmurraynxvl: I've received two of them20:33
nxvlmm20:33
nxvlstrange20:33
nxvl:S20:33
nxvlbut you received it, so it's fine20:33
bdmurrayIndeed!20:33
danagehi! my 0.6.6 network manager in hardy does not save my wpa2 key20:41
danagenetwork manager editor remains empty, key manager too20:42
danagegconf shows an entry for the network20:42
thekornbdmurray, added a patch to 20331221:09
thekornbug 20331221:09
ubotuLaunchpad bug 203312 in python-launchpad-bugs "add ability to parse bugtracker overviews" [Undecided,Fix committed] https://launchpad.net/bugs/20331221:09
thekornI hope this works...21:09
bdmurraythekorn: Awesome!  I'll test it today.21:14
=== Arby_ is now known as Arby
owhHiya, where do I find the buildd logs to see what the output was of a particular package being built?22:13
james_wowh: the launchpad overview page for the package links to it22:18
owhTah22:19
owhHiya, I'm following the recipe at https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff to create a debdiff. Thus far the way I've done this is to create a .orig directory, fix the bug, update the changelog appropriately and generate a diff -ruN between the .orig and the new directory. I'm doing this in a temporary alpha-6 hardy VM and setting it up as a build machine seems a lot of wasted effort. It needs a build environment, 22:48
pochuowh: you got cutted: "It needs a build  environment,22:51
pochu"22:51
owh...needs a build environment, gpg keys, dev scripts to name a few. Is there a better way?22:52
james_wto create a debdiff you don't need to be on hardy.22:53
owhjames_w: Well the package I'm fixing is in hardy.22:53
james_wyou do to test it properly, but for a lot of things a chroot suffices for that (pbuilder)22:53
james_wowh: you can download it to gutsy or wherever if you like.22:53
owhSo, I need to test it, make sure it builds, make sure that the debdiff I'm supplying will build, ultimately it's heading for a FFE.22:54
james_wif it's not a GUI app then you can do all of that in a chroot. If it is you only need to test it in a VM22:55
james_wyou don't need a GPG key either.22:55
owhIt's not a GUI. How do I stop debbuild failing with a GPG key error?22:56
james_wit should still have built the package.22:57
pochu"-us -uc"22:57
james_wbut as pochu says that will stop it from trying to sign.22:58
pochu(unsign source unsign changes)22:58
* owh has a go with those instructions.22:58
owhNow isn't that interesting. After all that, I get the same result :)23:03
owhExcellent :)23:03
owhShould I update the recipe to add pochu's comment about the GPG key error?23:04
pochufeel free to add a note or a comment23:05
owhHmm, just on the wording. I was thinking "If you're not signing this, then use...", but that's not really what's happening and I didn't think you'd want to encourage not signing stuff. Any suggestions on a better wording?23:09
pochu"If you don't have a GPG key, or if you aren't uploading the package by yourself to Ubuntu..."23:13
pochuperhaps note that only ubuntu devs can upload, so it's useless to sign it otherwise23:14
james_wpochu: I think the latter is probably true of most people reading the guide isn't it?23:14
pochuright23:14
james_wdoes REVU require signed uploads?23:14
pochuyes23:14
pochuand you need to be on ~ubuntu-universe-contributors23:14
james_wso it's more likely that someone less experienced will need to sign the package because of that.23:15
pochuwell since you're making a debdiff in that recipe, it doesn't matter whether you sign the package or not23:16
james_wpochu: that's true.23:16
james_wanyway I'm done for the day.23:17
pochuso perhaps directly adding "-us -uc" and explaining what they do and why we add them23:17
pochugood night james_w23:17
owhAt present here's what I have: https://wiki.ubuntu.com/PackagingGuide/Howtos/Debdiff23:17
james_wpochu: I think that's a good idea. With the note saying "If you want to upload the source package created at that stage use debsign to sign it"23:17
owhThe recipe doesn't create a package, it creates a debdiff.23:18
james_wowh: I think pochu's last suggestion is the best, would you like to do that?23:18
james_wowh: it creates a source package from which to make the debdiff, that's what that stage is doing.23:18
owhSo, then the opening statement of the recipe is wrong.23:18
owhIt says that you need a key.23:18
owhhttps://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff23:19
james_wowh: I don't see that.23:19
owhThe two URLs are different.23:19
owhThe last URL includes the first URL.23:20
james_wah, sorry23:20
owhThat is, the recipe includes the howto.23:20
james_wowh: yeah, you should change that too.23:20
james_wI must go, sorry.23:20
james_wnight all23:20
owhCheers james_w and thanks.23:20
owhI'm not sure that it's good policy to change the tone and nature of a document just like that. I mean the original author must have had a reason to put the GPG key information into the page.23:22
pochuhe could be wrong23:23
owhAt present I've put in the smallest change I can think of:  or if you're creating an unsigned package:   debuild -S -us -uc23:24
pochuwe can ask him tomorrow though, he's dholbach on irc23:24
pochubut I think changing it it's fine23:24
owhpochu: So, you're advocating changing two pages?23:27
pochuowh: yes23:34
pochuowh: why not? the change is correct, isn't it?23:35
seb128bdmurray: hi23:35
bdmurrayseb128: hello23:35
seb128bdmurray: do you have documentation advising users to copy their lsb informations to new bugs? could you change that to tell them to just copy the distribution information?23:35
bdmurrayseb128: where would you recommend them getting it from?23:36
seb128bdmurray: we get an increasing number of desktop bugs where people copy 6 lines at the start of every bug where we need 1 word23:36
seb128bdmurray: well, just change the information to tell them to copy the distribution name and not the whole thing?23:37
owhpochu: As I understand it yes, but that doesn't mean I'm correct.23:37
bdmurrayseb128: if you go to https://bugs.launchpad.net/ubuntu/+filebug-advanced you can see them below the description box23:38
owhpochu: I'd feel more comfortable discussing it with Daniel first.23:38
seb128bdmurray: right, they just run the command and copy the log to the bug23:38
pochuowh: as you want. he'll likely be around in ~7 or 8 hours23:39
pochuowh: it's a wiki anyway, so reverting a change is trivial ;)23:39
seb128bdmurray: that's a detail but it makes the bugs slightly harder to read23:39
owhpochu: I'll still be awake :)23:39
owhpochu: Just because you can, doesn't mean you should :)23:39
pochuseb128, bdmurray: perhaps the output of "lsb_release -rc" ?23:40
bdmurrayseb128: I understand your point but adding in a head or a grep might make it more error prone23:40
pochubdmurray: no need for that ^ :)23:40
seb128bdmurray: what pochu wrote23:40
bdmurrayDo you know if that works in all the releases we support?23:41
pochu(there's more options, but I think those are the more sensible ones)23:41
seb128that should23:41
seb128might be worth asking on #ubuntu-devel to be sure though23:41
bdmurrayI'll fire up a vm and check23:41
bdmurrayThat sounds like a great idea though, thanks!23:42
owhbdmurray: It works on 8.04 server and 7.10 workstation.23:42
* owh just checked.23:43

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!