[01:29] <ScottK> tumbleweed: No idea.  That was always a jdong_ tool.
[14:04] <Laney> I don't think prevu is needed any more
[14:04] <Laney> make sure no documentation mentions it
[14:05]  * Laney has just über synced haskell from sid
[14:05] <Laney> :-)
[14:35] <psusi> dear god, I had forgotten just how terrible cvs actually was... where's the real-life remove --purge command for cvs?
[15:20]  * tumbleweed watches his inbox fill up with Laney-uploads *again*
[15:22] <Laney> bad me?
[15:22] <tumbleweed> I guess you just got everything de-NEWed
[15:30] <Laney> 21 new emails: maybe
[16:04] <Laney> grr
[16:04] <Laney> university is being DoSed apparently
[16:10] <nigelb> By your emails?
[16:51] <Laney> erm
[17:31] <pmjdebruijn> hi all
[17:44] <pmjdebruijn> I am involved in a project (darktable), for which I maintained Ubuntu PPAs, we do packaging together with Debian (David Bremner), currently our last stable release 0.9.3 made it into Precise
[17:45] <pmjdebruijn> Our 0.9.3 release is fairly solid... and our future release schedule is unsure...
[17:45] <pmjdebruijn> however, is there a way to prevent 0.10 to be imported into Precise, if it has released and packaged by Debian
[17:47] <geser> you could try to get an archive admin to add a blacklist entry for this package (but it will also apply to new revisions of the current version)
[17:47] <pmjdebruijn> hmmm
[17:47] <pmjdebruijn> that's not entirely what I'd like
[17:48] <pmjdebruijn> since I'm "upstream" as well, I guess I should just monitor the situation
[17:48] <pmjdebruijn> when is the last automatic import from debian testing?
[17:49] <geser> Jan 12th (see https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule)
[17:49] <pmjdebruijn> ah
[17:49] <pmjdebruijn> thankyou
[18:06] <micahg> geser: pmjdebruijn: last Debian auto import is actually Jan 9, see parenthesis
[18:06] <pmjdebruijn> ah
[18:06] <pmjdebruijn> right
[18:07] <pmjdebruijn> tnx
[18:28] <psusi> how can you find out the process group that is currently controlling a tty?
[19:41] <blair> debian updated the package (rbtools in unstable) i was trying to get into ubuntu 12.04, now i just need to wait to see that the automatic sync happen?
[19:42] <broder> blair: it should get autosynced shortly after it hits testing
[20:02] <blair> broder, when does that happen?  i can always request a sync from unstable?
[20:02] <broder> blair: packages take 10 days to get migrated to testing - you can watch it at http://packages.qa.debian.org/r/rbtools.html
[20:03] <broder> you can request a sync from unstable if you think the fix is urgent - use requestsync from ubuntu-dev-tools
[20:03] <blair> no, it's not urgent, i just would like it in 12.04 since i'm trying to get our 500+ desktops on the OS
[20:04] <ScottK> blair: It should be fine.  Plenty of time before the deadline.
[20:04] <ScottK> blair: You wouldn't happen to know if that version of the package has the changes for bzr integration do you?
[23:01] <blair> ScottK, yes, it should.  The bzr branch I created has the effectively the same changes in it, but I may have redone the work inside of a Debian context instead of an Ubuntu one.  Also, the Debian maintainer put some additional changes into what's in Debian now, so it's a superset of my work
[23:02] <ScottK> blair: Thanks.
[23:03] <blair> ScottK, should I delete my branch
[23:03] <ScottK> I think so.
[23:03] <ScottK> Just double check the Debian package covers everything you were trying to do.