[02:34] Does anyone know how to set the path that quilt uses to store patches? [02:36] export QUILT_PATCHES= [02:36] /usr/share/doc/quilt/README.source has a handy snippet that tends to do the right things for debian packaging [02:37] persia: Thanks [02:46] Am I missing the reason quilt doesn't want to add debian/ files to the patch? [02:46] It's not done that way. [02:46] If you're working on files in debian/ *don't* do it as a quilt patch (or with any other patch system). Just edit them. [02:47] Understood [02:47] The reasoning being something like "The packaging shouldn't be patched at build-time: just do it right, and let the archive track the revisions". [02:48] The other reasoning being "This stuff is patches to the upsteam code that upsteam may want to adopt, so we'll put it in a separate folder to ease management". [14:32] Hi I found a bug, but cannot figure out how to report it. [14:37] Anyone able to help? [14:37] jimbo2150: feel free to describe the situation around the bug (especially which program it occurs in) and someone will hopefully be able to help you. [14:37] Weekends tend to be very slow around here. [14:38] I turned off the computer incorrectly and when I booted it back up it started a disk check. It said press 'C' to cancel and I did but nothing happened. Pressing ESC does cancel it though. I am using lucid RC. === bencrisford is now known as bencrisford-edu [14:42] jimbo2150: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/561228 appears to describe it, but strangely the bug it is dup'ed against is listed as fixed [14:42] Launchpad bug 561228 in plymouth (Ubuntu) "Cannot cancel automatic fsck during boot (dup-of: 554737)" [Undecided,New] [14:42] Launchpad bug 554737 in plymouth (Ubuntu Lucid) (and 2 other projects) "ply_boot_client_flush() does not read replies (plymouth stuck during/after filesystem check or error) (affects: 114) (dups: 9) (heat: 614)" [High,Fix released] [14:44] is it allowed to discuss lucid bugs here? [14:44] jimbo2150: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/562811 is related as well. Looks like there might be more than one semi-interrelated problem here. Long story short, it looks like it is being looked into. [14:44] Launchpad bug 562811 in plymouth (Ubuntu Lucid) (and 3 other projects) "[Lucid] fsck cannot be cancelled in Plymouth (affects: 11) (dups: 1) (heat: 64)" [High,Fix committed] [14:45] That first one is pretty close, but I did not have to hit CTRL+C. ESC canceled it and Ubuntu continued booting. [14:46] The second one is somewhat close, but ESC did work for me. [14:47] jimbo2150: you might look around the other plymouth bugs and whichever one is closest, clicks "affects me too". Thanks for taking an interest in reporting! [14:47] Ok thanks mrand! [14:47] bramming9x: Kinda depends. We try to discuss bug _reporting_ (and triaging) here rather than the bugs themselves. Debugging is usually on #ubuntu+1 [14:49] mrand okay thanks :) will try that ;) === bulldog is now known as bulldog98 === radoe_ is now known as radoe [21:06] even|ng === bulldog is now known as bulldog98 [21:53] BUGabundo: evening ;) [21:54] hey ben === bulldog is now known as bulldog98