[00:06] <psusi> what's the tool that generates packages.gz etc so you can make a cdrom containing packages to install?
[00:28] <MTecknology> so.. how do you go about requesting a sync for something that's not a stable release yet?
[00:28] <MTecknology> I want to request a sync for a package because of a CVE
[01:18] <arand> MTecknology: What do you meant by not a "stable release"
[01:22] <MTecknology> arand: oneiric, not released yet, but very close to it
[01:23] <MTecknology> arand: the update will be in debian stable-security pretty soon
[01:32] <arand> MTecknology: https://wiki.ubuntu.com/SecurityTeam/ForDebianDevelopers#Getting_updates_into_Ubuntu seems to be one reference for how it goes.
[01:37] <arand> MTecknology: Only in the case of a D-U version match is there syncing (security fake sync), in all other cases it seems you'll go via standard patching if I've read that correctly
[04:46] <plipp> I'm still having the same problem with libglib2.0-data after upgrade. :(
[04:47] <plipp> trying to build a package of my checked out 'foobillard', and get:
[04:48] <plipp> 0 packages upgraded, 101 newly installed, 0 to remove and 0 not upgraded.
[04:48] <plipp> Need to get 86.3 kB/21.6 MB of archives. After unpacking 81.3 MB will be used.
[04:48] <plipp> Writing extended state information...
[04:48] <plipp> Err http://archive.ubuntu.com/ubuntu/ precise/main libglib2.0-data all 2.31.20-0ubuntu2
[04:48] <plipp>   404  Not Found [IP: 91.189.92.181 80]
[04:48] <plipp> E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/g/glib2.0/libglib2.0-data_2.31.20-0ubuntu2_all.deb: 404  Not Found [IP: 91.189.92.181 80]
[04:48] <plipp> E: Unable to correct for unavailable packages
[04:48] <plipp> installed version is 2.31.20-0ubuntu3
[04:49] <plipp> The error was interpreted to me earlier as me not having done an upgrade.  But to me, something's requiring an older package here.
[04:50] <ScottK> apt doesn't work that way.
[04:51] <ScottK> It would have given you a dependency error, not tried to get an older package.
[04:51] <ScottK> plipp: Can you pastebin your /etc/apt/sources.list somewhere?
[04:52] <plipp> ScottK: Absolutely
[04:53] <plipp> http://pastebin.com/L3E8iFji
[04:55] <ScottK> plipp: Could you pastebin the full upgrade log, from sudo apt-get upgrade to the ends.
[04:57] <plipp> ScottK: Yes, if the upgrade log is available somewhere?  (The error is during the local package build)
[04:58] <plipp> apt/history.log?
[04:58] <ScottK> /var/log/dist-upgrade
[04:58] <ScottK> Actually, nevermind.
[04:59] <ScottK> Are you using pbuilder?
[04:59] <plipp> pbuilder-dist <release> build ../<package>_<version>.dsc
[05:00] <plipp> pbuilder-dist precise build ../foobillard_<version>.dsc
[05:03] <plipp> 3.0a-5 being version, to be exact
[05:16] <plipp> ScottK:  full result of `pbuilder-dist precise build ../foobillard_3.0a-5`  http://pastebin.com/jH1zrk5p
[05:17] <ScottK> I understand now.
[05:17] <ScottK> The installed version in your system is ubuntu3.
[05:18] <ScottK> pbuilder has it's own cache (so you can run pbuilder for different releases than the one you're on)
[05:18] <ScottK> That's the pbuilder cache that's out of date (sorry, I missed it was part of a build before)
[05:18] <ScottK> plipp: do pbuilder-dist precise update and then try again.
[05:20] <plipp> Ok
[05:20] <plipp> Does 'dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested:' got to do anything with it, perhaps?
[05:22] <ScottK> That's normal.
[05:23] <ScottK> You just need to periodically run pbuilder update to keep it's internal packages file and cache up to date.
[05:26] <plipp> Aha. Is there any particular reason why pbuilder update is not run with apt update?
[05:26] <plipp> or upgrade, rather
[05:36] <ScottK> Two separate things.
[05:36] <ScottK> You may have good reason not to update one or the other.
[05:36] <ScottK> I have pbuilder chroots for every supported Ubuntu release.  Running update on them every time I did apt-get update would take a LONG time.
[05:41] <plipp> ScottK: Okay, I'll buy that. :)     Thing seemed to go much better now..  but something awkward..:
[05:42] <plipp> ....
[05:42] <plipp> dh_builddeb
[05:42] <plipp> dpkg-deb: building package `foobillard' in `../foobillard_3.0a-5_amd64.deb'.
[05:42] <plipp> ....
[05:42] <plipp> I: pbuilder-time-stamp: 1331962790
[05:43] <plipp> The ./foobillard_3.0a-5_amd64.deb is no where in my working directory..   does it end up somewhere completely different..?
[05:44] <plipp> ah, updatedb & locate did it..
[05:44] <plipp> under pbuilder, it seems
[05:46] <plipp> You live, you learn.
[05:51] <plipp> ScottK: I highly appreciate your patience. Thanks a lot
[05:53] <ScottK> plipp: You're welcome.  We were all new at this once.
[05:57] <plipp> ScottK: Seems like foobillards has been dead since 2007. I was thinking of c++:ify it, fix some bugs and turn it more into a snooker-specific game.  So a fork really...
[05:57] <ScottK> Dunno.  Not my sort of thing.  If it scratches your itch though, go for it.
[06:03] <plipp> ScottK: Just felt like informing you what I'm playing with here, given all the help.  I don't know if this kind of stuff is anything that are usually added to the ubuntu repositories (should be enough with one version of the same software).  It's more of an exercise for myself.
[06:04] <ScottK> Usually we get new packages like this through Debian.
[06:38] <plipp> ScottK: Yep, that's what I felt
[08:44] <bullgard4> Where are there on my Ubuntu computer  Source package control files -- debian/control? http://www.debian.org/doc/debian-policy/ch-controlfields.html '~$ find / -name '*debian/control*' 2>/dev/null does not provide any output.
[08:56] <tbf_> how can i restart a cancelled build?
[15:09] <valdur55> Hey. Where i should place application app indicator icons?
[15:12] <valdur55> Oh damn... google knows answer :)
[18:42] <dsfsd> There's a serious problem with Ubuntu... UNITY is pushing real users that have real work to do away from the distribution! There's a serious problem with Ubuntu... UNITY is pushing real users that have real work to do away from the distribution! There's a serious problem with Ubuntu... UNITY is pushing real users that have real work to do away from the distribution!
[18:43] <jtaylor> to bad one more repetition would have convinced me
[18:59]  * ajmitch wonders why people come into -motu to rant about non-universe stuff
[19:01] <ajmitch> with that, I wish compiz weren't using ~2G of RAM that it wants to swap in when trying to use my computer in the morning ;)
[19:01] <jtaylor> I wish X wouldn't crash when I try to watch a video :/
[19:02] <jtaylor> I'm still stuck on oneiric due to that, last cycle I was on oneiric permanent after a3 :/
[19:02] <ajmitch> heh, I'm just watching iotop as this laptop thrashes swap for a minute or so
[19:02] <ajmitch> peaked at ~275MB/sec disk read :)
[19:03] <jtaylor> :O
[19:08] <ScottK> ajmitch: Was that meant to be self-referential wonderment?
[19:10] <ajmitch> ScottK: I just had to complain, you know? :)
[19:10] <ScottK> Right, but I was wondering about the complaint followed by kvetching about compiz.
[19:11] <JontheEchidna> personally, I'd just use a sane compositing manager like kwin :P
[19:11] <ajmitch> I was just commenting on people that complain in a place where the appropriate people to fix stuff aren't listening
[19:12]  * ajmitch at least follows up with LP bugs 
[19:12] <ajmitch> anyway, I have to run :)
[19:12] <jalcine> JontheEchidna: lol, me too.
[19:48] <tbf_> hi, is there any way to restart a manually cancelled ppa build?
[19:48] <tbf_> or do i have to dput a fake release to trigger an entirely new build?
[19:52] <imbrandon> ajmitch: its where most the other bitching happens so seems natural ? heh