[04:29] how do i request apport information on a bug? [04:31] i.e, there is a bug, on which additional info is needed. It is missing apport data. How do i instruct the bug reporter to add additional data (apport report) into existng bug? [04:31] sorry. got the answer. :) [04:35] which did you use phanimahesh [04:35] apport-collect xxxxxx ? [04:35] yup. [04:35] I need to suggest someone. [04:36] you saw the bug responses too [04:36] for apport collect? [04:36] there are no responses. very fresh bug with no info. [04:36] #1016363 [04:37] you can put bug 1016363 [04:37] :D [04:37] ubot is not working it seems [04:37] Launchpad bug 1016363 in command-not-found "not found problem" [Undecided,New] https://launchpad.net/bugs/1016363 [04:38] oh there it is [04:38] ok. so i put bug number and ubot2 sends a link? [04:38] good. :) [04:39] yes [04:39] put a nice response [04:39] can you look at it? I sent a short one. [04:40] you saw the page for that phanimahesh [04:40] bug page? [04:40] yup. [04:41] I've joined the bug squad long ago but couldn't contribute much. Ocassionally i drop by and look at something i can help with or contribute bug heat. :) [04:42] i meant this page https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information [04:42] thats all :D [04:43] oh! I'll remember to use those responses in future. I so very love canned responses. :P :) #lazy [04:44] lol, sometimes they help and some people think we sound like robots lol, so cant make everyone happy [04:45] yeah.. there was a meta post on Ask Ubuntu that complained that the site was full of robots. :P [04:45] coz we are lazy enough to use a user script to paste pro-forma comments. [04:48] lol the team has like 1000 members and the have 1000000 bugs so they need all the help they can get [04:48] yup. [05:45] I entered '~$ ubuntu-bug phpmyadmin'. The hard disk started heavy activity. To my surprise Launchpad did not open (as it did in the past). So I could not report verbally what error I observed. Is this the new intended way of ubuntu-bug's error reporting? [05:46] i dont think so. Heavy activity is kind of normal, as it tries to collect additional info. [05:46] did waiting help? === zyga-afk is now known as zyga [09:17] phanimahesh: Yes, very long waiting did help. Very long waiting actually. [09:18] lol. ok. [09:18] the data collection is heavily resource intensive. [09:28] In the past I have compiled more than 100 error reports. So I have acquired a feeling how long it usually takes until Launchpad appears after I issue a ubuntu-bug command. This time the period was unusually long. === zyga is now known as zyga-afk [10:38] bullgard6: thats.. unusual then. may be file a bug against apport. :P === zyga-afk is now known as zyga [12:30] hi ak [12:30] all* [12:30] I would like to fix easy bug and someo [12:31] ...someone suggest me to read how to work with patches [12:32] I found it a little bit tricky [12:32] alo21: This is a somewhat good page I often refer to: https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff [12:33] astraljava: it tells how to work with patches? [12:34] alo21: The only difference if you're making just general patches, is that you replace the 'debdiff' tool with 'diff -Nurp'. [12:34] alo21: It tells how you prepare them, and how you apply them. [12:35] alo21: Have you got a more precise problem or a question? [12:37] astraljava: let me find a specific page [12:40] astraljava: someone give me this guide (https://wiki.ubuntu.com/PackagingGuide/PatchSystems) [12:41] astraljava: and it does not seem very clear [12:43] alo21: Well, it presents all the various ways of using patching systems, and also the work flow of not using a patch system. [12:43] astraljava: are write there all needed informations on how create, apply and test a patch? [12:44] astraljava: so.. is it a comprehensive guide? [12:45] alo21: It _is_ quite comprehensive. Do you have a specific problem with any random steps? [12:52] astraljava: not now... but if I will, I ask you some questions [12:52] Sure, you're always welcome to do so. :) [12:52] astraljava: thanks spending your time helping me [12:52] No probs, happy to help. Thanks for showing interest in making ubuntu better. :) [12:54] it's my pleasure [13:10] hi [13:11] following this guide (https://wiki.ubuntu.com/PackagingGuide/PatchSystems) I edited a patch, my question is: How can I test this patch? [13:11] should I build all? === skaet is now known as skaet_afk === skaet_afk is now known as skaet_ === rsalveti` is now known as rsalveti [17:13] hi all How can i test a patch created by my hands? [17:13] try and manually build the package? [17:13] or have someone build and run for you [17:15] LoT: I am a beginner, how can I build a package? === skaet_ is now known as skaet === ashams_ is now known as ashams [19:19] Hi, I there are any method to resolve situation when bug with simple fix and patch is not fixed by maintainer for 5 years? [19:19] What to do in such cases? === Jikan is now known as Jikai === Jikai is now known as Jikan [19:28] which bug? [19:30] This for example https://bugs.launchpad.net/ubuntu/+source/readline6/+bug/103986 [19:30] Ubuntu bug 103986 in base-files "Update inputrc config and bash config" [Wishlist,Confirmed] [19:31] jtaylor: What to do in such cases? [19:33] this looks more like different opinion than a bug [19:35] if the maintainer disagrees, there is nothing you can do [19:35] jtaylor: Person says that feature of bash should be enabled. To enable it, maintainer must uncomment just two lines. And Gentoo linux have that lines uncommented realy [19:36] If maintainer disagrees with it he must to close bug as "wont fix"? or no? [19:38] yes [19:38] So, what can I do with it? [19:39] not much === s9iper1_ is now known as s9iper1 [19:40] its not really important enough for e.g. a mail to a list [19:42] if it so, than it is very bad :( This bug have patch included and still ignored [19:42] Can I commit some fix to the readline6 development brunch? [19:44] Ubuntu is titled as "Linux for human beings", but Gentoo have more human friendly bash configuration :( [19:45] It is obvious that https://launchpad.net/~doko is too busy. But having bad bash configuration is not an exit === ashams_ is now known as ashams === Jikan is now known as Jikai === Jikai is now known as Jikan === yofel_ is now known as yofel === Ursinha` is now known as Ursinha === Ursinha is now known as Guest72428 === Guest72428 is now known as Ursula === Ursula is now known as Ursinha === Jikan is now known as Jikai === Jikai is now known as Jikan