[00:56] <jdong> hmm, BFS is actually noticeably more responsive...
[00:56] <jdong> heh of course I only have 1 and 2 core machines and gut feeling to back that up
[00:57] <ion> BFS?
[02:04] <matgeek> thumper:  notice you are doing miniconf at linuxconf.  I am seriously thinking of coming along.  Is there anything I can do to help you out?  How about an account of using launchpad as a Debian Developer?  I am moving to get one of my packages on it this week.
[03:39] <ScottK> Is there an archive admin in the house?
[03:41] <ScottK> odbcinst is a new binary (split out from odbcinst1debian1) that landed in Universe.
[03:41] <ScottK> So now the -dev package is uninstallable on the buildds
[03:43] <ScottK> (for main uploads)
[03:43]  * ScottK plays archive admin roulette and asks if StevenK might be around to help out?
[03:44]  * StevenK lunges for cocoplum
[03:45] <ScottK> StevenK: Thanks.
[03:52] <StevenK> ScottK: Done.
[03:52] <ScottK> StevenK: Thanks again.  Got it in before the publisher run even.
[03:55] <StevenK> ScottK: That was my plan
[03:55] <ScottK> Good plan that.
[04:26] <diwic> I'm trying to git pull, but it claims that my working tree is not up-to-date
[04:26] <diwic> It complains about files I haven't changed, at least not on purpose.
[04:26] <diwic> What is the easiest way to resolve that issue?
[04:26] <maco> diwic: try "git stash ; git pull ; git stash apply" ?
[04:27] <diwic> maco: stash, that was a new one :-)
[04:28] <maco> diwic: it stashes all your changes elsewhere so you can pull as if it were a clean tree
[04:28] <maco> did it work?
[04:28] <diwic> yes, thanks :-)
[04:28] <maco> yay!
[04:28] <maco> i had to learn that yesterday when i got too behind on pulling at work
[04:29] <diwic> I'm not going to do the apply part though
[04:29] <maco> ok
[04:30] <diwic> oh, next problem
[04:30] <diwic> pristine-tar: There's no local pristine-tar branch. Several remote pristine-tar branches exist.
[04:31] <diwic> Run "git branch --track pristine-tar <remote>" to create a local pristine-tar branch
[04:32] <diwic> maco: I remember you saying quilt was the most difficult part of becoming MOTU, but I must say git is three times harder
[04:34] <maco> diwic: most motu dont have to deal with git...
[04:34] <maco> diwic: just us weirdos who touch kernely thingies
[04:34] <diwic> maco: perhaps you're right. This is actually debian work
[04:34] <maco> ive never used pristine-tar thouhg
[04:34] <maco> *though
[04:36] <diwic> maco: perhaps it is Linus's way of keeping amateurs away from the kernel. ;-)
[04:36] <maco> diwic: my boss was watching me trying to use git yesterday and going "wish we could go back to ___" and named something older than CVS that is apparently found on mainframes
[04:37] <jdong> older than RCS?
[04:37] <jdong> SCCS?
[04:37] <jdong> the former doesn't follow from the latter.
[04:38] <diwic> maco: we use a serial VCS at work and it actually works pretty well.
[04:38] <StevenK> I thought they just paid to keep the programmers in cold storage along with the mainframes
[04:38] <spO> does changing my gcc version matter with regard to the kernel? IE, i can do it and it is not a big deal?
[04:38] <maco> jdong: possibly RCS
[04:39] <ebroder> maco: RCS isn't that old. The sipb.mit.edu AFS cell has way too much RCS in it. It's really sad
[04:39] <jdong> RCS is still cool in some ways :)
[04:39] <ebroder> Actually...that second sentence didn't follow from the first
[04:39] <maco> ebroder: i work for a company that does stuff on afs, so this makes sense coming from my boss
[04:39] <jdong> namely if you're trapped on a FreeBSD system...
[04:39] <jdong> that seems to be the scenario for all vintage tools :)
[04:40] <ebroder> Yeah, I'm told the sipb cell still have a copy of iexplore for Sun lying around somewhere. Ugh
[06:50] <mneptok> foxbuntu: ping
[06:53] <foxbuntu> mneptok, pong
[06:54] <mneptok> foxbuntu: could you join #ubuntu-ops for a moment, please?
[06:54] <foxbuntu> mneptok, sure.
[06:55] <mneptok> thanks!
[06:56] <lifeless> `/win 41
[09:16] <OC1> hi everybody
[09:17] <OC1> is there anyone who can read me :(
[09:18] <OC1> do u hear me :(
[09:18] <micahg> OC1: how can we help you?
[09:18] <OC1> hi micahg
[09:19] <OC1> I am new in ubuntu
[09:19] <OC1> I install ubuntu 9.1
[09:19] <OC1> but I can't update my system
[09:19] <micahg> OC1: #ubuntu is for support
[09:19] <OC1> thank you
[09:19] <micahg> OC1: good luck
[09:20] <OC1> see u
[12:56] <juliank> Is it normal that a NEW package (libslab in its own source package) available in Debian testing since Oct 22 is still not available in lucid?
[13:08] <slacker_nl> who should I notify if packages.u.c is down?
[13:15] <tsimpson> slacker_nl: try #canonical-sysadmin
[13:15] <slacker_nl> thnx
[13:23] <cjwatson> juliank: it's on the list, but it requires manual attention because it produces binaries that override binaries from a different source package that's modified in Ubuntu
[13:23] <cjwatson> E: libslab is trying to override libslab-dev_0.9.12+dfsg-0ubuntu4 without -f/--force.
[13:24] <juliank> cjwatson: Actually, gnome-main-menu (which previously contained libslab) should be synced as well.
[13:25] <cjwatson> juliank: that's fine, but we don't take these requests by IRC :) https://wiki.ubuntu.com/SyncRequestProcess
[13:25] <cjwatson> if you (or somebody) file a bug and subscribe ubuntu-archive to it, it'll be processed
[13:27] <juliank> cjwatson: I just said this because I wanted to wait for libslab before renaming https://bugs.edge.launchpad.net/ubuntu/+source/gnome-main-menu/+bug/428860 to a sync request. So it seems the gnome-main-menu sync must come first, and then libslab (gnome-main-menu depends on libslab, so this seems a bit strange)?
[13:27] <cjwatson> juliank: please file a bug about libslab, then
[13:27] <cjwatson> the gnome-main-menu sync doesn't have to come first; but the archive admins are not in a position to review every package in this state, so we rely on bugs
[13:28] <slacker_nl> hi all, got a problem with apt, debsums apt reports: missing file /usr/lib/libapt-pkg-libc6.10-6.so.4.8.1 (from apt package)
[13:28] <juliank> cjwatson: The libslab sync request was stopped by ubuntu-universe-sponsors because we are before import freeze (it is https://bugs.edge.launchpad.net/ubuntu/+bug/428968)
[13:29] <cjwatson> juliank: they were wrong. sorry about that.
[13:29] <cjwatson> please reopen it and feel free to quote me. the sync won't happen (semi-)automatically because it overrides binaries from another modified source package.
[13:30] <cjwatson> the required bit for sponsorship is an explicit check and statement that all changes in gnome-main-menu are no longer required.
[13:32] <cjwatson> there are a couple of dozen packages in this state. I should probably put the list somewhere ...
[13:33] <juliank> cjwatson: Why not allow the archive to contain two versions of a binary package from two different sources? This would make such syncs easier; but one would have to cleanup afterwards.
[13:35] <cjwatson> not going to happen, sorry :)
[13:35] <cjwatson> it would be pathological for users because apt will only ever use the latest one, so we don't really want to allow the archive into such a state
[13:36] <cjwatson> it's not a big enough problem in general for that sort of wide-ranging change to be worthwhile
[13:44] <juliank> cjwatson: Both bugs updated. And I guess after the sync, we should move libslab to main and rebuild gnome-control-center against it instead of its own copy.
[13:45] <juliank> Thanks for the information!
[13:54] <squirrelpimp> is packages.ubuntu.com down or deprecated?
[14:09] <juliank> squirrelpimp: It just seems to be down; at least there is still an IP for it.
[15:41] <craigbass1976> Is poppler something I can install, or it comes with cups?
[15:45] <craigbass1976> https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379/+activity  The last entry is something about  lp:ubuntu/jaunty-proposed/poppler   Does that mean I should see this by changing my software sources to include proposed updates?
[15:46] <craigbass1976> thanks ubottu, I knew that.
[15:46] <maxb> craigbass1976: poppler is a piece of software that cups may use, why do you ask?
[15:48] <craigbass1976> I can't print pdfs, and experience what's mentioned here:  https://bugs.launchpad.net/ubuntu/jaunty/+source/poppler/+bug/382379
[15:48] <craigbass1976> I've been trying to dork with this for a couple months, but today I grabbed the woman's computer and printer and have them at my house for the day
[15:49] <craigbass1976> maxb, I'm not sure how to implement the change, other than run an update
[15:52] <craigbass1976> maxb, no idea?
[15:52] <maxb> The bug is huge, I am reading
[15:52] <craigbass1976> thanks
[15:54] <maxb> There are no pending SRUs for cups or poppler.
[15:54] <maxb> -proposed is not relevant here
[15:55] <craigbass1976> I'm thick... is there a fix or not?
[15:55] <craigbass1976> And how do I implement it if there is.
[15:56] <maxb> bug 382379 is deemed fixed some time ago
[15:57] <maxb> poppler and cups have both been SRUed in jaunty multiple times since that, for other issues, apparently
[15:57] <craigbass1976> I thought it looked like that; I wonder why I still have such trouble then
[15:57] <maxb> I would suggest trying a Karmic livecd if that is an option for you
[15:57] <craigbass1976> Is there an L out yet?
[15:58] <maxb> pre-alpha
[16:00] <craigbass1976> maxb, well, karmic is an option, but I was hoping to avoid installing a new os.  Question for you...  I hear tell there is some trouble upgrading to Karmic.  Is there going to be the same kind of trouble upgrading out of Karmic?
[16:00] <craigbass1976> This woman has so much stuff on her box that wipe/reinstalls are a wicked pita
[16:04] <maxb> All upgrade paths out of jaunty lead through karmic anyway
[16:05] <FishEatFish> hello, can someone help me with the void * type ? i don't know how to deal with an array assignement
[16:06] <craigbass1976> maxb, I forget I can just throw this lappy drive in my desktop.  Dumping's quick.  I'll go karmic.
[16:06] <maxb> FishEatFish: Are you really in the right channel?
[16:08] <maxb> craigbass1976: Dumping? Please note that I am not unequivocally recommending karmic, I was just suggesting you try a livecd
[16:08] <FishEatFish> maxb : there is other channels dedicated to programming ?
[16:08] <maxb> FishEatFish: This isn't a channel dedicated to programming.
[16:09] <maxb> "Development of Ubuntu (not support, not app development on Ubuntu)"
[16:09] <FishEatFish> ok thank you maxb i apologize
[16:09] <maxb> ##c might help you
[16:10] <FishEatFish> :) i'll go there
[16:21] <aburch> Is there any historic data for popcon.ubuntu.com available?
[16:22] <aburch> I miss the nice graph that popcon.debian.org provides, so I build a small site to generate them, but only have data for the last 10 days.
[16:26] <aburch> FWIW the graphs are available from ubuntu-popcon.43-1.org for now.
[18:53] <yofel> hi, would bug 491483 qualify for an SRU?  if gdm and kdm are installed and kdm is used, kdm and failsave-x will race against each other to start X since failsave X thinks that gdm being disabled equals X not starting up.
[18:59] <craigbass1976> Is this channel logged somewhere?  I need to see what I said in here earlier
[19:00] <ebroder> !logs | craigbass1976
[19:00] <craigbass1976> ebroder, thanks
[19:00] <craigbass1976> maxb, you there?
[19:09] <maxb> craigbass1976: intermittently - ask and IO'll get back to you
[19:10] <craigbass1976> maxb, wanted to let you knwo that karmic prints pdf no better than jaunty.
[19:14] <craigbass1976> maxb, and I guess the netowrk doesn't matter; this thing suck via usb too.
[19:17] <maxb> craigbass1976: In that case, I think you should file a new bug
[19:23] <craigbass1976> maxb, lazyart's post here http://ubuntuforums.org/showthread.php?t=223819 has fixed my issue with the karmic livecd.  Now I'll see what happens on the jaunty install.  be back later..
[19:54] <craigbass1976> maxb, dude...  this is retarded.  use an HP laserjet foomatic driver to print to a networked brother mfc 7820N and all your troubles will go away.
[20:16] <craigbass1976> maxb, and I added to the bug thread you were reading earlier.  I don't know as this qualifies as part of the bug though.
[21:23] <maxb> I seek a main-sponsor for a subversion merge, is anyone interested?
[21:24] <maxb> bug 483953
[22:59] <fbond_> Where can I read about the relationship between -updates and -security?
[23:02] <kees> fbond: does this answer it for you? https://wiki.ubuntu.com/SecurityTeam/FAQ#Repositories
[23:05] <fbond> kees: Not really, I guess.  What I'm wondering is, if the updates pocket has a different version of a package than the release pocket, which version is the security update based on?
[23:11] <fbond> kees: And when do security updates also get published to the updates pocket?
[23:18] <fbond> kees: I think this will help me: https://wiki.ubuntu.com/ArchiveAdministration
[23:18] <fbond> Let me look that over for now.  Thanks for your help.
[23:22] <fbond> kees: Okay, I understand the policy.  Security updates would be based on packages in the updates pocket.  But wouldn't this lead to users that don't have the updates pocket enabled getting -updates changes via -security?
[23:26] <kees> fbond: yes.  that can happen and is accepted as the least bad of possible options.
[23:27] <fbond> kees: In other words, the cost of maintaining two separate security pockets would be too high?  Makes sense.
[23:29] <kees> fbond: yeah, correct.  I've updated the FAQ a bit to help clarify.
[23:54] <mun24> I have a requirement where I need to wait for 2 events, if event 1 occurs then do something and if event 2 occurs then do something else.  How can I achieve this.