[01:20] <psusi> hallelujah, holy shit! I finally got it figured out and working... my god what a complex package, but I think I really understand what is going on now... it builds half a dozen packages with various interdependencies and two different sets of abi versions... damn!  it's milla time!
[02:07] <paissad> is there policy for creating Unity quicklinks ?
[02:08] <paissad> for the .deb packaging
[02:21] <psusi> there's no way to make a package a dependency only if a third package is also installed is there?
[07:00] <tumbleweed> paissad: #ayatana or #ubuntu-desktop
[08:29] <paissad> tumbleweed, ok
[14:04] <pcpratts> hi! I am trying to save off config files for an upgrade
[14:05] <pcpratts> in postrm upgrade I copy the config files to a temp folder
[14:05] <pcpratts> and in postint configure I am trying to overwrite the files from the newly installed .deb package
[14:06] <pcpratts> but .dkpg-temp files are being created
[14:06] <pcpratts> and those are finally used by the installer in some way
[14:18] <Ampelbein> pcpratts: What do you want to do? dpkg by default prompts the user to overwrite/keep/examine changed configfiles.
[14:27] <pcpratts> well, my conf files are not marked it seems
[14:27] <pcpratts> Ampelbein: do you know how to tell dpkg what my config files are?
[14:28] <Ampelbein> pcpratts: see http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
[14:29] <pcpratts> okay, thanks!
[16:52] <lfaraone> I'm attempting to mirror the Ubuntu archive with ubumirror; is there a way to exclude certain releases from the mirroring?
[16:53] <tumbleweed> never used ubumirror...
[16:53] <lfaraone> (as in, I tried to exclude maverick, natty, and precise; it didn't work and I ran out of disk space <_<;
[16:54] <lfaraone> tumbleweed: well, I need to do a two-stage sync, right?
[16:54] <lfaraone> jpds: ping ^^
[16:54] <tumbleweed> lfaraone: right, that looks like an ftpsync type thing
[16:54] <tumbleweed> you can't exclude releases, because it doesn't parse the Packages files
[16:55] <lfaraone> tumbleweed: should I use apt-mirror in the interim until I get a less sucky disk?
[16:55] <tumbleweed> yeah, or debmirror
[18:57] <Ampelbein> hyperair: Hi! Regarding bugs like 885505, it might be useful to include a short message with the status change to "Fix Released". Like "Fixed in the latest ubuntu version 0.21-1". That way, people know what happened.
[19:05] <hyperair> right, good idea.
[19:05] <hyperair> Ampelbein: thanks. i actually meant to close the bug in debian/changelog, but failed miserably when i missed out the #
[19:06] <Ampelbein> I thought so. I was a bit confused by the status change myself but checked the upload log to find out.
[19:06] <hyperair> heh
[19:07] <hyperair> sorry, i get a bit slipshod when changing a large number of bugs to fix released
[19:07] <Ampelbein> No worries ;-)
[19:07] <hyperair> i should probably make better use of the email interface for those
[21:48] <tumbleweed> ScottK, Laney, broder: do people use prevu? (Why is it still in the archive?) (re http://lists.debian.org/4EE4D536.7060909@grendelman.net )
[21:48] <broder> i've never heard of people using it
[21:49]  * tumbleweed is following up to that thread
[21:51] <broder> but i know its intent was to be easier to use/setup than sbuild/pbuilder. i don't know if it actually is
[21:52] <broder> or if that's still relevant in the era of ppas
[21:59]  * ajmitch thought it was just a wrapper around pbuilder
[21:59] <ajmitch> but I haven't really used it
[21:59] <tumbleweed> question is, is it a useful one. I see very few uploads and few bug reports
[22:00] <tumbleweed> yeah, the code is tiny
[22:00] <ajmitch> it did what backportpackage is meant for
[22:02] <broder> i tihnk it can be replaced by backportpackage + pbuilder-dist with little documentation and not a whole lot of difficulty
[23:01] <ScottL> i have a bzr branch (ubuntustudio-default-settings) that i want to completely replace with another bzr branch (xubuntu-default-settings with modifications i will make)
[23:02] <ScottL> is the command i use to remove my current branch from bzr:  'bzr remove-tree'
[23:02] <ScottL> ?
[23:02] <tumbleweed> no remove-tree removes your working directory
[23:03] <tumbleweed> just rm -r
[23:03] <tumbleweed> (if I'm understanding your question correctly)
[23:03] <ScottL> tumbleweed, i'm not sure i am asking clearly
[23:04] <tumbleweed> you have a local branch that you don't want any more?
[23:04] <EvilResistance> ScottL:  you basically want to purge your ubuntusudio-default-settings branch, and have xubuntu-default-settings take its place?
[23:04] <EvilResistance> remotely/
[23:04] <EvilResistance> *
[23:04] <ScottL> EvilResistance, aye
[23:04] <EvilResistance> tumbleweed:  read my interp.
[23:04] <ScottL> sorry, was helping wife with cooking dinner
[23:04] <EvilResistance> ScottL:  remotely, or locally?
[23:04] <EvilResistance> (remotely such as on LP)
[23:04] <EvilResistance> (and locally meaning at your machine)
[23:06] <ScottL> sorry, helping with dinner again
[23:06] <ScottL> okay
[23:06] <ScottL> the bzr branch is hosted in launchpad
[23:06] <ScottL> i was checking out a version that i wanted to replace
[23:06] <ScottL> so it would be locally
[23:06] <ScottL> and then i would push back to lp
[23:07] <ScottL> EvilResistance, ^^^
[23:07] <tumbleweed> if you are replacing it remotely, it really doesn't matter what you are doing locally
[23:07] <tumbleweed> you can push anything over anything else with push --overwrite
[23:07] <tumbleweed> (use with care, of course)
[23:10] <ScottL> tumbleweed, so i could not even use 'bzr branch' for the ubuntustudio-default-settings package?
[23:11] <tumbleweed> yes
[23:11] <ScottL> just 'apt-get source xubuntu-default-settings' ?
[23:11] <ScottL> bzr add
[23:11] <ScottL> commit and then push
[23:11] <ScottL> ?
[23:11] <ScottL> push meaning pushing to ubuntustudio-default-settings with --overwrite
[23:11] <tumbleweed> assuming you want to remove the entire history for the branch
[23:12] <ScottL> oh, not sure i want to do that actually
[23:12] <ScottL> i would feel more comfortable if i had something to fall back to
[23:12] <tumbleweed> so by "completly replace" you just mean "commit a new revision"?
[23:13]  * tumbleweed thinks he understands the question now
[23:13] <tumbleweed> branch the existing branch, delete every file in it (but leave .bzr), add the stuff you want to replace it with, bzr add, commit
[23:14] <ScottL> yes, i would like to "commit a new revision" which would not include any of the old code, yes
[23:14] <ScottL> can i use 'bzr add' to add everything?
[23:14] <ScottL> or does it require a qualifier?
[23:15] <tumbleweed> no qualifier required
[23:15] <ScottL> very cool, thanks tumbleweed
[23:16] <ScottL> it was more or less like i thought it would be, but it makes me feel very, very much more comfortable to have it confirmed :)
[23:16] <tumbleweed> np
[23:17] <ScottL> although i thought that i would need to 'bzr remove' at least _something_ :?
[23:18] <tumbleweed> bzr assumes that files you've deleted should be deleted
[23:28] <ScottL> even better, wasn't sure about that
[23:28] <ScottL> thanks again tumbleweed and EvilResistance
[23:33] <psusi> what's the environment variable you set to get debian/rules to use make -j?
[23:33] <tumbleweed> DEB_BUILD_OPTIONS. But the debian/rules needs to support it
[23:34] <tumbleweed> (dh has a --parallel option)
[23:34] <psusi> what do you set it to?
[23:35] <psusi> just DEB_BUILD_OPTIONS=-j4 debian/rules binary?
[23:35] <tumbleweed> no
[23:35] <tumbleweed> http://www.debian.org/doc/debian-policy/ch-source.html
[23:36] <psusi> ahh
[23:36] <psusi> pfft... silly kernel rules file told me to make mrproper before building... which then deleted the debian directory