[02:17] IDEA: 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:44] moo [03:22] :) === blue-frog__ is now known as blue-frog === blue-frog__ is now known as blue-frog [09:25] hi 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:28] anyone noticed the number of g_slice_alloc SIGSEGV we have been having? [09:30] iwkse, feel free to report the bug, if you do not find a duplicate :) [09:31] techno_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] iwkse, have you checked the forums? [09:32] techno_freak: i surfed a on launchpad [09:32] techno_freak: but forums, no.. [09:33] iwkse, still feel free to report a bug, it will help us to know what went wrong :) [09:33] techno_freak: oki :) === blue-frog_ is now known as blue-frog [12:43] Hey [12:43] hello [12:44] Hiya pedro_ [12:45] hey Iulian, pedro_ [12:48] hello thekorn [12:49] Hi thekorn === blue-frog__ is now known as blue-frog [14:51] Boo [14:52] bddebian: Moo. [14:58] jpatrick: :-) [15:48] hello bug hunters [15:50] hi bdmurray [15:50] james_w: hey, you mentioned some samba upgrade bug / debconf question right? [15:51] bdmurray: yeah, slangasek looked at it and it is kind of intentional behaviour. [15:51] or rather unaviodable unwanted behaviour. [15:51] okay, I personally saw it this weekend and saved some logs [15:51] it should only happen in hardy->hardy upgrades, not dapper-> or gutsy-> so it's fine for release [15:52] bdmurray: you didn't happen to look at the diff in the gtk window did you? [15:53] Yes, I believe I looked at it. [15:53] did it look ok to you? [15:53] I wish I had had a proper look at it, rather than just deciding it was unreadable and carrying on [15:56] It seemed okay yes [15:56] hello [15:56] hello! [15:57] bdmurray: ok, thanks for looking, I'll keep my eye out in future [15:57] or maybe I could try and provoke it. [15:57] * james_w finds my pointy stick [15:57] james_w: I captured the 2 config files during the process if you want them [15:58] bdmurray: I should just be able to do it by editing the file, thanks. === 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 [17:04] thekorn: another cool looking tool, thanks :) [17:05] james_w, hehe [17:07] mvo: hello there [17:10] hey bdmurray [17:11] james_w: Indeed :) [17:16] mvo: 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] not that I know of right now [17:16] log files are still the most imporant bit required [17:19] mvo: I also ran across bug 182350 the other day and wasn't clear on the design decision there. [17:19] Launchpad bug 182350 in update-manager "no longer reports installed and available versions" [Medium,Triaged] https://launchpad.net/bugs/182350 [17:28] hi [17:28] how do i get privilegies to edit the bugs priority? [17:28] nxvl: you need to be a member of the ubuntu-bugcontrol team to edit bug priority [17:30] bdmurray: 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:31] nxvl: there is some more information at https://wiki.ubuntu.com/UbuntuBugControl [17:33] bdmurray: ok, i have appied and i have al de requirements [17:33] i will now searh for 5 bug reports i have triage and i will send you by PM [17:34] is that correct? [17:35] nxvl: yes, an e-mail to me with those bugs would be great [17:37] ok, looking for them now [17:38] bdmurray: fixed bugs doesn't count, doesn't it? [17:39] nxvl: We are looking for bugs that you have triaged / worked with reporters on, so the bugs can absolutely be fixed. [17:39] Additionally, 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:51] bdmurray: bug 182350 was a design desision [17:51] Launchpad bug 182350 in update-manager "no longer reports installed and available versions" [Medium,Triaged] https://launchpad.net/bugs/182350 [17:52] mvo: Okay, I was wondering where it was duplicated. [18:42] are there hal developers on? I think they might find bug 203094 interesting [18:42] Launchpad bug 203094 in libsmbios "hal cannot set brighness on Dell notebook computers if a BIOS password is set" [Undecided,New] https://launchpad.net/bugs/203094 [18:43] (btw, maybe there should be a function added to this channel that you can poke a group) [18:49] qense: please try on #ubuntu-dev ;) [18:51] #ubuntu-devel [18:54] james_w: #ubuntu-dev redirects to -devel ;) [18:55] ah, thanks, never knew that, might save some characters. === ogra_cmpc_ is now known as ogra_cmpc [18:56] :D [19:37] bdmurray: thx for approving me :) [19:37] Nightrose: no problem! [19:39] thekorn: Do you have an idea of how much work it would be to make another html bug listing page parsable? [19:40] Nightrose: I saw you were having an issue with the Gutsy version of python-launchpad-bugs is that right? [19:40] jep [19:41] Did you look at the upstream version i.e. pull it from bzr? [19:42] bdmurray, it depends on how well structured the page is, [19:42] nope - I just tried the packaged one [19:42] but parsing pages with xpath is easy [19:42] thekorn: it's pages like https://launchpad.net/bugs/bugtrackers/gcc-bugzilla [19:44] thekorn: I forget did you make a gutsy ppa version of python-launchpad-bugs? [19:46] bdmurray, yes 0.2.28 for gutsy is in PPA [19:47] bdmurray, parsing of these bugtracker pages should be easy, [19:48] when we find a way to handle the different status/importance values of the different trackers [19:49] I'm really just interested in getting the ubuntu bug numbers out of pages like than and then looking for upstream tasks [19:49] The url I posted is a list of ubuntu bugs with http://gcc.gnu.org/bugzilla/ showing up in the comments [19:50] As I understand it [19:50] thekorn: which ppa? and would you reccomend me to use it? the packaged version in gutsy doesn't work for me [19:50] Nightrose, https://edge.launchpad.net/~bughelper-dev/+archive [19:50] Nightrose: we need to do release a new version of python-launchpad-bugs for Gutsy. I'm sorry about that. [19:51] thekorn: thx :) [19:51] Nightrose, I tested it for gutsy like two weeks ago [19:51] bdmurray: no prob [19:51] ok [19:51] If you go from that list to bug 172326 you'll see that it doesn't have an upstream watch. [19:51] Launchpad bug 172326 in gcc-4.1 "Reproducable SIGSEGV (char ************* etc.)" [Undecided,New] https://launchpad.net/bugs/172326 [19:52] But it should because in the last comment someone says they opened a bug but it just isn't linked to. [19:52] bdmurray, right [19:53] will work on parsing this buglist soon [19:54] bdmurray, after finishing a first patch to fix bug 200457 [19:54] Launchpad bug 200457 in python-launchpad-bugs "URLBugListFilter missing milestones" [Undecided,New] https://launchpad.net/bugs/200457 [20:07] thekorn, bdmurray: still getting some warnings about API not being stable but it seems to work better now - will play around a little with it - thx [20:07] Nightrose: that is expected. Please let us know if you have any questions. [20:07] will do :) [20:30] bdmurray: i have send you an e-mail one second ago [20:33] nxvl: I've received two of them [20:33] mm [20:33] strange [20:33] :S [20:33] but you received it, so it's fine [20:33] Indeed! [20:41] hi! my 0.6.6 network manager in hardy does not save my wpa2 key [20:42] network manager editor remains empty, key manager too [20:42] gconf shows an entry for the network [21:09] bdmurray, added a patch to 203312 [21:09] bug 203312 [21:09] Launchpad bug 203312 in python-launchpad-bugs "add ability to parse bugtracker overviews" [Undecided,Fix committed] https://launchpad.net/bugs/203312 [21:09] I hope this works... [21:14] thekorn: Awesome! I'll test it today. === Arby_ is now known as Arby [22:13] Hiya, where do I find the buildd logs to see what the output was of a particular package being built? [22:18] owh: the launchpad overview page for the package links to it [22:19] Tah [22:48] Hiya, 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:51] owh: you got cutted: "It needs a build environment, [22:51] " [22:52] ...needs a build environment, gpg keys, dev scripts to name a few. Is there a better way? [22:53] to create a debdiff you don't need to be on hardy. [22:53] james_w: Well the package I'm fixing is in hardy. [22:53] you do to test it properly, but for a lot of things a chroot suffices for that (pbuilder) [22:53] owh: you can download it to gutsy or wherever if you like. [22:54] So, 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:55] if 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 VM [22:55] you don't need a GPG key either. [22:56] It's not a GUI. How do I stop debbuild failing with a GPG key error? [22:57] it should still have built the package. [22:57] "-us -uc" [22:58] but as pochu says that will stop it from trying to sign. [22:58] (unsign source unsign changes) [22:58] * owh has a go with those instructions. [23:03] Now isn't that interesting. After all that, I get the same result :) [23:03] Excellent :) [23:04] Should I update the recipe to add pochu's comment about the GPG key error? [23:05] feel free to add a note or a comment [23:09] Hmm, 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:13] "If you don't have a GPG key, or if you aren't uploading the package by yourself to Ubuntu..." [23:14] perhaps note that only ubuntu devs can upload, so it's useless to sign it otherwise [23:14] pochu: I think the latter is probably true of most people reading the guide isn't it? [23:14] right [23:14] does REVU require signed uploads? [23:14] yes [23:14] and you need to be on ~ubuntu-universe-contributors [23:15] so it's more likely that someone less experienced will need to sign the package because of that. [23:16] well since you're making a debdiff in that recipe, it doesn't matter whether you sign the package or not [23:16] pochu: that's true. [23:17] anyway I'm done for the day. [23:17] so perhaps directly adding "-us -uc" and explaining what they do and why we add them [23:17] good night james_w [23:17] At present here's what I have: https://wiki.ubuntu.com/PackagingGuide/Howtos/Debdiff [23:17] pochu: 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:18] The recipe doesn't create a package, it creates a debdiff. [23:18] owh: I think pochu's last suggestion is the best, would you like to do that? [23:18] owh: it creates a source package from which to make the debdiff, that's what that stage is doing. [23:18] So, then the opening statement of the recipe is wrong. [23:18] It says that you need a key. [23:19] https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff [23:19] owh: I don't see that. [23:19] The two URLs are different. [23:20] The last URL includes the first URL. [23:20] ah, sorry [23:20] That is, the recipe includes the howto. [23:20] owh: yeah, you should change that too. [23:20] I must go, sorry. [23:20] night all [23:20] Cheers james_w and thanks. [23:22] I'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:23] he could be wrong [23:24] At present I've put in the smallest change I can think of: or if you're creating an unsigned package: debuild -S -us -uc [23:24] we can ask him tomorrow though, he's dholbach on irc [23:24] but I think changing it it's fine [23:27] pochu: So, you're advocating changing two pages? [23:34] owh: yes [23:35] owh: why not? the change is correct, isn't it? [23:35] bdmurray: hi [23:35] seb128: hello [23:35] bdmurray: 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:36] seb128: where would you recommend them getting it from? [23:36] bdmurray: we get an increasing number of desktop bugs where people copy 6 lines at the start of every bug where we need 1 word [23:37] bdmurray: well, just change the information to tell them to copy the distribution name and not the whole thing? [23:37] pochu: As I understand it yes, but that doesn't mean I'm correct. [23:38] seb128: if you go to https://bugs.launchpad.net/ubuntu/+filebug-advanced you can see them below the description box [23:38] pochu: I'd feel more comfortable discussing it with Daniel first. [23:38] bdmurray: right, they just run the command and copy the log to the bug [23:39] owh: as you want. he'll likely be around in ~7 or 8 hours [23:39] owh: it's a wiki anyway, so reverting a change is trivial ;) [23:39] bdmurray: that's a detail but it makes the bugs slightly harder to read [23:39] pochu: I'll still be awake :) [23:39] pochu: Just because you can, doesn't mean you should :) [23:40] seb128, bdmurray: perhaps the output of "lsb_release -rc" ? [23:40] seb128: I understand your point but adding in a head or a grep might make it more error prone [23:40] bdmurray: no need for that ^ :) [23:40] bdmurray: what pochu wrote [23:41] Do you know if that works in all the releases we support? [23:41] (there's more options, but I think those are the more sensible ones) [23:41] that should [23:41] might be worth asking on #ubuntu-devel to be sure though [23:41] I'll fire up a vm and check [23:42] That sounds like a great idea though, thanks! [23:42] bdmurray: It works on 8.04 server and 7.10 workstation. [23:43] * owh just checked.