| === freeflying_away is now known as freeflying | ||
| === freeflying is now known as freeflying_away | ||
| === freeflying_away is now known as freeflying | ||
| ESphynx | hey guys... I'm running on up to date Saucy right now, and I keep making the gtk-window-decorator crash | 13:32 |
|---|---|---|
| ESphynx | Gdk-CRITICAL **: IA__gdk_drawable_get_depth: assertion 'GDK_IS_DRAWABLE (drawable)' failed | 13:32 |
| ESphynx | I would like to figure out whether my Ecere toolkit is doing anything bad, or it's just a bad unfixed bug in GTK? | 13:32 |
| ESphynx | https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1266572 -- Well :) | 13:37 |
| ubottu | Launchpad bug 1266572 in compiz (Ubuntu) "gtk-window-decorator crashes randomly" [Undecided,New] | 13:37 |
| ESphynx | I don't even get an option to file a bug though when that happens? | 13:37 |
| ESphynx | Woah... this is pretty bad. I just go 'gdb gtk-window-decorator' , run, and I get the crash right away | 13:39 |
| === freeflying is now known as freeflying_away | ||
| === freeflying_away is now known as freeflying | ||
| fully_human | Hello. I'm applying my first bug fix for Ubuntu Bug Week. In the changelog should I add (LP: ...) or (Closes: ...)? | 16:55 |
| cjwatson | (LP: #nnnnnn) is the syntax to close an Ubuntu bug | 16:55 |
| cjwatson | (closes: #nnnnnn) is the syntax to close a Debian bug (when uploading to Debian) | 16:56 |
| fully_human | Ah, thanks. | 16:56 |
| cjwatson | The latter already existed and we didn't want to introduce ambiguity by reusing it with a different bug number namespace | 16:56 |
| fully_human | Yeah, I saw the note in the docs that Closes is for debian, but I didn't know if that meant debian-ish (the docs sometimes do). | 16:56 |
| fully_human | What does "bzr bd -- -S" mean when it complains "dpkg-source: error: aborting due to unexpected upstream changes"? It refers me to a file that complains about my changelog message. | 17:08 |
| fully_human | I'll pastebin the changelog in a bit. | 17:09 |
| cjwatson | That suggests you've put your changelog message in the wrong place. It should be in debian/changelog, and dpkg-source won't consider things under debian/ to be "upstream". | 17:09 |
| cjwatson | Unless I'm misunderstanding. | 17:09 |
| fully_human | It is in debian/changelog. | 17:10 |
| cjwatson | Then I doubt it's actually *complaining* about your changelog message as such; that is, that isn't the error. | 17:10 |
| cjwatson | The majority of packages require that patches to upstream source be kept in debian/patches/ | 17:11 |
| fully_human | The build failed, though. | 17:11 |
| cjwatson | If debian/source/format says "3.0 (quilt)" (which is the most common case nowadays), then you need to use quilt when editing upstream source | 17:11 |
| cjwatson | And dpkg-source is probably complaining that you edited it directly instead | 17:11 |
| cjwatson | This is so that patches are separated and easily forwardable to the upstream maintainer | 17:12 |
| fully_human | Ah, okay, yeah, it says quilt. | 17:12 |
| fully_human | Thanks. | 17:12 |
| fully_human | Hm...so do I cat the output of 'quilt diff' into a file and then 'quilt add' that file? I'm sorry...the doc I'm reading (http://packaging.ubuntu.com/html/fixing-a-bug-example.html) doesn't have anything on quilt. | 17:19 |
| cjwatson | No - /usr/share/doc/quilt/README.source has basic instructions | 17:20 |
| cjwatson | You can also abbreviate the steps of running "quilt add FILE" then editing the file, as "quilt edit FILE" | 17:20 |
| fully_human | So after I run quilt refresh then I run 'bzr bd -- -S'? | 17:59 |
| cjwatson | Sounds plausible | 18:00 |
| fully_human | Hm, I went through all the steps for quilting but when I run 'bzr bd -- -S' this is the error I get: "dpkg-source: error: cannot read inkscape-0.48.4.orig.lzzAHP/debian/patches/bug-807861-typo-in-src_widgets_toolbox_cpp: No such file or directory" | 18:15 |
| fully_human | The bug-80.... is a new patch that I created with 'quilt new'. | 18:16 |
| cjwatson | You might have forgotten to "bzr add" it | 18:17 |
| cjwatson | (I tend to just use "debuild -S" personally, but "bzr bd -S" will I suppose provide a better check of whether your bzr working tree is right) | 18:18 |
| === TheLordOfTime is now known as teward | ||
| fully_human | So I'm now trying to run pbuilder-dist on the dsc file. It's trying to install a bunch of packages but doesn't ask me for the admin password so the install fails. Any work-around? thanks. | 22:54 |
| fully_human | This two minute bug fix is turning into a day-long project. :( | 22:54 |
| Ampelbein | fully_human: use "sudo pbuilder-dist ...."? | 22:56 |
| jtaylor | no pbuilder calls sudo for you | 22:56 |
| jtaylor | can you paste a log? | 22:56 |
| fully_human | It won't even run as root. :-\ | 22:56 |
| fully_human | pbuilder-dist: Error: You don't own $HOME | 22:56 |
| fully_human | That's if I run it with sudo. | 22:56 |
| fully_human | I'll run it without root now and paste the results... | 22:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!