[00:33] <TheMuso> Thats weird. I used zsync to update isos on the weekend and had no problem.
[00:37] <arand> TheMuso: Yea, it worked for me, on the cdimage server at least, if it working for you atm, or care to confirm Bug #775192 ?
[01:35] <highvoltage> slangasek: howdy. any chance of a keysigning party again at UDS-O?
[01:49] <cjohnston> lifeless: I have a bug that's been tagged apport-crash and has apport retracing since 4/8/11
[01:51]  * RAOF could do with actually getting into the strong set.
[02:09] <serge_> should this have happened?  I 'update from 11.04 to 11.04' using desktop cd;  it preserved /opt, but it wiped out /var/mail!  (I had a backup, but that seems a horrible decision)
[04:04] <Bsims> stupid question lsmod shows pcspkr is available but when I try to modprobe it in it shows module not available
[04:37] <slangasek> highvoltage: there's certainly chance for a keysigning party, but I have no energy to organize one this year :)
[04:38] <slangasek> ScottK: bug #764096> hngh, cursed chroots
[04:39] <ScottK> Since it's our default configuration, it kind of ought to work ....
[04:39] <slangasek> yes, yes it should
[04:40] <slangasek> come to think of it, I'm using postfix and haven't seen this problem, I wonder why it works for me
[04:40] <slangasek> but yeah, I'll poke the package
[06:31] <pitti> Good morning
[06:32] <pitti> jcastro: seems cjwatson beat me to it
[07:05] <micahg> hi pitti, could you please copy chromium-browser from -proposed to -security/-updates for lucid-natty (bug 771935)
[07:18] <pitti> micahg: will do in a bit
[07:19] <micahg> pitti: thanks
[07:26] <speakman> mornin' folks!
[07:28] <speakman> How does Debian/Ubuntu handles packages using /var/lib/package - is the directory specified in debian/ directory, or how does the package know that it has to mkdir it? My package using GNU Autotools.
[07:31] <StevenK> Likely specified in debian/dirs, and therefore created by dh_installdirs during the package build process.
[07:40] <speakman> StevenK: Looks like a proper place. Just wondering how pure Autotools packages creates the dir at "make install" time.
[07:42] <StevenK> speakman: My knowledge of autotools is sadly spotty, but I'd think they'd have a mkdir call in the install target
[07:45] <speakman> ok
[07:49] <speakman> looks like a install-data-hook target is the way to create it at install time
[07:49] <speakman> http://osdir.com/ml/attachments/txtA8gAhtcp1W.txt
[07:50] <RAOF> Do you need the directory to exist, or for the directory to contain a file - if it contains a file, just add it to an autotools install target.  Otherwise, install-data-hook is good.
[08:08] <cjwatson> doko_: it looks like you did a sync of db_5.1.25-10 but didn't flush it
[08:08] <cjwatson> doko_: (I guess we're just going to hope that the Java bits will cross-build now?)
[08:18] <dholbach> good morning
[08:19] <mvo> hey dholbach, good morning
[08:19] <dholbach> hey mvo
[08:20] <speakman> RAOF: Just to create the dir. Files will be created by the program when running
[08:20] <speakman> Is there a debhelper tool to upgrade packages from upstream?
[08:21] <dholbach> speakman, check out uscan and uupdate
[08:21] <speakman> dholbach: thanks!
[08:21] <dholbach> (a devscripts tool)
[08:22] <speakman> it's here. But no upgrades available on mcelog unfortently :(
[08:23] <speakman> (having sporadious machine check exceptions, causing kernel panics. very annoying)
[08:24] <RAOF> speakman: Yeah, then you probably want to use install to create the directory in the -data-hook.
[08:26] <speakman> and OnTopic again; the mcelog daemon doesn't start at boot, even though it's symlinked in /etc/rc[2-5].d/. Running /etc/init.d/mcelog start manually works perfectly. No entries in log either. Is there a way to look at startup messages in retrospectively, or do I have to reboot to see if there's any error?
[08:27] <speakman> RAOF: thanks alot, mate!
[08:28] <cjwatson> speakman: /var/log/boot.log
[08:29] <cjwatson> if anything was printed at startup, it should be thre
[08:29] <cjwatson> *there
[08:29] <speakman> cjwatson: wow, thanks!
[08:37] <pitti> mvo: is bug 767776 fixed in oneiric as well?
[08:39] <mvo> pitti: yes, let me update that, fixed with the most recent apt upload
[08:39] <pitti> mvo: nice, thanks
[08:51] <cdbs> pitti: ping, when does the 'copy of all SRUs to dev release' happen?
[08:52] <pitti> cdbs: in the first days of opening a new release, when the versions are still the smae
[08:52] <cdbs> pitti: So I guess it means, now/
[08:52] <pitti> I'm doing that for the first round of 0-day SRUs, as when they got uploaded it wasn't possible to do an oneiric upload
[08:52] <cdbs> ?
[08:52] <pitti> cdbs: right
[08:53] <pitti> we'll stop doing so for future uploads, though, to have the updates be built against the oneiric toolchain
[08:55] <pitti> cjwatson, SpamapS: FYI, I committed an sru-release script (using launchpadlib) into ubuntu-archive-tools, and disabled the one on cocoplum; so Clint can now release SRUs without shell access
[09:04] <cjwatson> pitti: noted, thanks
[09:05] <cjwatson> cdbs: I have already been copying SRUs to oneiric when I notice them
[09:05] <cjwatson> periodically, in bulk
[09:06] <cjwatson> I have a script that looks for packages newer in natty-updates than oneiric
[09:06] <cdbs> cjwatson: okay, thanks
[09:06] <cdbs> cjwatson: We don't move -proposed packages?
[09:07] <cjwatson> cdbs: I don't
[09:07] <cdbs> I thought it was done, I sure was wrong
[09:07] <cjwatson> I never have
[09:08] <cjwatson> other people may have done, or it may have happened in certain cases
[09:08] <cjwatson> I don't consider it obviously safe to do in bulk
[09:10] <pitti> I usually copy them to -updates and devel at the same time, i. e. when they got verified
[09:10] <pitti> it's easiest from a workflow perspective and reasonably safe
[09:10] <cjwatson> right, I think that's sensible
[09:10] <cjwatson> the ones that I catch with my bulk runs are generally security updates
[09:52] <speakman> Are there any predefined paths for autotools parameters in debian/ubuntu? like --sysconfdir is probably defined somewhere?
[09:56] <cjwatson> speakman: that depends on what tools you're using.  If you're using dh_auto_configure (usually via dh), then it defines several default parameters, yes.  See /usr/share/perl5/Debian/Debhelper/Buildsystem/autoconf.pm
[09:57] <cjwatson> There are no universal defaults because debian/rules is entirely entitled to call ./configure directly if it likes.
[10:03] <talat> Hi i want to rebuild/repackage python2.6 package. is it possible ?
[10:04] <speakman> cjwatson: thanks alot! again! :D
[10:07] <tumbleweed> doko_: talat wants http://bugs.python.org/issue1813 fixed in python2.6 (apparently you applied a patch for it in python2.5)
[10:08] <talat> doko_: yes i want to apply isssue1813 patch in 2.6
[10:08] <talat> doko_: and other newer version :(
[10:09] <talat> doko_: is it possible ?
[10:10] <tumbleweed> talat: with most packages i'd say just post a patch and go through the sponsorship process, but for python you probably want to talk to doko (although he may not be around right now)
[10:11] <talat> tumbleweed: ok. Thnx. I will wait doko :)
[10:49] <seb128> is there anything that need to be run manually to get germinate datas on the ubuntu-archive people page for oneiric?
[10:49] <seb128> (just asking because the ubuntu-desktop version tracking use those to determine what to list in the desktop set)
[10:51] <cjwatson> seb128: oh, I forgot to update that script.  done now
[10:51] <cjwatson> you'll get output in a couple of hours or so
[10:52] <seb128> cjwatson, thanks
[10:52] <cjwatson> I'll create oneiric package sets tomorrow
[10:52] <cjwatson> (not actually at work today despite appearances)
[10:54] <lucidfox> seb128, have you seen that email about easytag?
[10:56] <seb128> lucidfox, hi, sort of, I read through it quickly, I've not been maintaining easytag for some years and I've no real opinion so whatever people thing is right just do it
[10:56] <lucidfox> ahh
[11:05] <drdozer> hi - I just upgraded to natty using the upgrader in maverick via kde
[11:06] <drdozer> now I can´t boot
[11:06] <drdozer> I
[11:06] <drdozer> I´ve not had any feedback in #ubuntu so thought I´d ask here
[11:06] <drdozer> error: symbol not found: `grub_env_export´.
[11:06] <drdozer> grub rescue>
[11:21] <lucidfox> seb128, my idea is to rebase easytag to stsquad's github fork as the new upstream, since the sourceforge version is basically dead. And if you have no time to maintain the package on your own, you could perhaps contribute it to the Debian Multimedia team
[11:22] <seb128> lucidfox, you are welcome to take over the package and put it under debian multimedia if you want
[11:22] <lucidfox> Okay, thanks
[11:27] <seb128> is there any known issue with qt softwares and systray?
[11:28] <seb128> we received some gnome-panel and unity bugs about systray icons being 1 pixel icons, seems specific to qt applications, I'm wondering if that could be a Qt issue
[11:32] <directhex> am i the only person using natty with a laptop plugged into an external monitor, with the internal laptop screen turned off? and by "using" i mean "failing to use"
[11:33] <RAOF> directhex: What's broken about that?
[11:34] <seb128> likely bug #737891
[11:34] <RAOF> directhex: If I were to guess that your external monitor stops updating when you turn off the internal monitor, would that be correct?
[11:35] <RAOF> Ahh, Intel.  Where would we be without your modesetting bugs.
[11:38] <directhex> RAOF, as soon as i log in, BOTH screens go blank? and if i badger it into letting me in by un-docking during login, as soon as i disable the internal screen, BOTH screens get disabled
[11:38] <directhex> seb128, similar, but i'm using displayport not vga. so my symptoms are different
[11:39] <RAOF> directhex: Then you're probably seeing…
[11:39]  * RAOF hunts for the Arrandale+DP black screen bug
[11:42] <RAOF> directhex: That might be bug #745112 but I recall another one that's DP specific.
[11:43] <directhex> RAOF, i'm reading that one, but i'm not exceeding the intel 4096x4096 limit
[11:43] <RAOF> directhex: The take home message?  drm-intel-next-proposed kernels from our friend the kernel team PPA are quite likely to fix the problem :/
[11:44] <directhex> 771344 ?
[11:44] <directhex> i'll try a newer kernel from that ppa
[11:55] <directhex> a desktop!
[11:55] <directhex> first time!
[11:55] <directhex> it didn't even apply my thinkpad ICC profile to my dell monitor this time!
[11:56] <RAOF> :)
[13:12] <dupondje> the Ubuntu MoM isn't updated anymore ?
[13:18] <pitti> it's supposed to update, but apparently got stuck
[13:19] <dupondje> give it a kick :)
[13:19] <pitti> -EPERM
[13:19] <pitti> (and -ECLUE too)
[13:22] <mvo> dupondje: just having a look, but it seems like its just very busy
[13:22] <mvo> dupondje: i.e. lots and lots to work on
[13:24] <dupondje> The html pages are updated 17-Apr-2011 23:02
[13:24] <dupondje> but dirs are indeed up-to-date it seems
[13:24] <Sweetshark> seb128, pitti: http://sweetshark.livejournal.com/857.html
[13:26] <pitti> \o/
[13:27] <diwic> Sweetshark, hmm, headline says "10.04"
[13:27] <Sweetshark> diwic: thanks.
[13:29]  * Sweetshark mumbles something about breaking things with last minute changes being never a good idea.
[13:29] <Sweetshark> diwic: fixed.
[13:29] <diwic> Sweetshark, it's all about fixing errors :-)
[13:58] <dupondje> Any idea when Gnome3 gets pushed into Oneiric ? :)
[14:03] <dholbach> dupondje, check out the oneiric-changes list - a lot of 3.0 gnome stuff got uploaded already
[14:37] <doko> janimo: could you make the rebuilt apt available somewhere?
[14:39] <janimo> doko, I will shortly
[14:47] <mvo> janimo: oh?
[14:47] <mvo> janimo: its just a rebuild that is needed?
[14:47] <janimo> mvo, ARM only. Relax :)
[14:47] <mvo> I was just looking into it on the porter machine but its *slow*
[14:48] <mvo> so did not get even close to diangosing it
[14:48] <mvo> janimo: what is the issue? gcc-4.6 incompatible changes?
[14:48] <janimo> mvo, I do not know yet, the only thing so far is that a rebuild with -O0 does not crash
[14:49] <mvo> janimo: cool, thanks!
[14:49] <janimo> it crashes in libapt-pkg in some printf-sytle function. If -fshrink-wrap was not disabled until fixed I would suspect that
[14:50] <doko> janimo: hmm, is shrink-wrap in Linaro 4.6 at all?
[14:51] <janimo> doko, no idea
[14:52] <doko> janimo: please wait with an upload until we know the reason
[14:55] <janimo> doko, I am not uploading anything
[14:56] <janimo> especially since I don't see how it will not FTBFS itself. Would it not?
[15:01] <doko> janimo: sure, but even a manual build would require an upload
[15:01] <janimo> doko, right
[15:48] <pitti> barry: hey Barry, how are you?
[15:48] <barry> pitti: hi, good, and you?
[15:49] <pitti> barry: quite well, thanks! successfully moved to Augsburg over the weekend
[15:49] <barry> congrats!
[15:49]  * barry looks up augsburg
[15:50] <pitti> barry: Tomeu just asked whether you would have an opinion about my patch in gnome bug 649165
[15:54] <Sweetshark> pitti: augsburg? try not to forget how to speak proper german then ...
[15:55] <pitti> Sweetshark: FSVO "proper" -- I'm from Saxony
[15:58] <barry> pitti: hi okay, i'll take a look
[16:01] <Sweetshark> pitti: hehe, that has not gone unnoticed when we had some phone calls.
[16:01] <pitti> Sweetshark: nu glar
[16:12] <stgraber> Laney: ping
[16:13] <stgraber> Laney: can you update https://blueprints.launchpad.net/ubuntu/+spec/other-o-dmb-meeting to be something else than "Complete" ? that might be why it doesn't appear on the schedule ...
[16:17] <barry> pitti: i have some comments
[16:17] <stgraber> jono: ping
[16:17] <jono> stgraber, hey
[16:18] <barry> pitti: let me know when you're ready :)
[16:18] <stgraber> jono: do you have a sec to look/approve two UDS specs in the community track ? https://blueprints.launchpad.net/edubuntu/+spec/community-o-debian-edu-edubuntu-collaboration and https://blueprints.launchpad.net/ubuntu/+spec/community-o-edubuntu
[16:18] <jono> one sec
[16:18] <stgraber> jono: they have special scheduling needs but I'll take care of that once they hit the summit website
[16:18] <jono> stgraber, done :-)
[16:20] <genis> hi
[16:20] <genis> apparently for python-qt4-sql there is no support for postgresql
[16:20] <genis> QSqlDatabase: QPSQL driver not loaded
[16:20] <genis> QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL
[16:21] <genis> from the defaul deb packages
[16:21] <genis> on 10.10
[16:21] <DoctorPepper> hi  guys!!!
[16:21] <genis> where can I find out if it will be supported
[16:21] <genis> in a future update?
[16:21] <pitti> barry: perhaps we should discuss that in the bug, so that the upstream guys can follow?
[16:22] <Laney> stgraber: do you mean 'informational'?
[16:22] <stgraber> jono: thanks!
[16:22] <jono> :-)
[16:23] <stgraber> Laney: I'd at least change the "Complete" status for something else as I doubt completed specs appear on summit.u.c, changing to something else than informational may also be a good idea
[16:23] <stgraber> I don't know the exact criteria, but the current spec is approved and wasn't imported on summit.u.c, so something is wrong :)
[16:23] <Laney> I can't edit the Status bit
[16:23] <barry> pitti: okay.  i'll go get an account :)
[16:24] <Laney> but I changed Implementation and it made Status go to 'Not started'
[16:24] <Laney> we'll see what that does
[16:24] <pitti> barry: oh, you don't have one? thanks
[16:24] <barry> pitti: actually, i do!
[16:25] <stgraber> jcastro: ^ can you change the status ?
[16:27] <jcastro> stgraber: on it
[16:28] <stgraber> jcastro: thanks
[16:40] <barry> pitti: comment posted
[16:40] <davidm> jcastro, we need to send map info to proximalabs folks or should we just skip map info?
[16:41] <jcastro> davidm:  wait I thought marianna sent you a map?
[16:41] <jcastro> let me reping
[16:43] <davidm> jcastro, I can't find an email with a map attached
[16:45] <hallyn> SpamapS: re bug 719448, when you say 'accepted to sru', does that mean you're pushing the package, or that you're waiting for me to push the fix to lucid-proposed and maverick-proposed and you'll allow it when I do?
[16:45] <jcastro> davidm: I have a PDF they sent me on april 1st that I forwarded to you that day, do you have that?
[16:55] <pitti> barry: ah, thanks!
[16:56] <pitti> barry: so you generally agree to the approach, just the implementation could be more robust?
[16:58] <SpamapS> hallyn: that means its accepted for the series as a valid SRU (as opposed to being too intrusive for instance)
[17:01] <hallyn> SpamapS: do i need to push the package to the -proposed archives?
[17:02] <SpamapS> I swear, UDD is just plain broken. :( 50/50 chance the package branch will be out of date
[17:02] <SpamapS> http://package-import.ubuntu.com/status/bash-completion.html#2011-03-15 20:29:05.392361
[17:03] <SpamapS> hallyn: yes thats the typical workflow (step 4 at https://wiki.ubuntu.com/StableReleaseUpdates :)
[17:03] <SpamapS> james_w`: is there anything someone in my position can do to improve UDD? Should I be manually importing/fixing branches?
[17:07] <hallyn> SpamapS: james_w`: yes, that's been killing me lately.  bzr checkout rarely gives me the actual current archive copy
[17:09] <hallyn> SpamapS: yeah, sorry, i'm to queezy about uploading things.  will push those then, thanks much.
[17:09] <SpamapS> hallyn: its good to be hesitant in this case. :)
[17:14] <jcastro> davidm: ok she sent one better than what I sent you before, in your inbox.
[17:14] <davidm> jcastro, thanks I'll forward now to proximalabs
[17:15] <jcastro> sorry about that I thought I had closed that loop
[17:23] <j1mc> pitti: i have marked you as an approver for my blueprint, but i'm not sure if you're the right person. i picked you because you were signed up as the approver for several desktop-* blueprints.
[17:23] <j1mc> pitti: here's the link: https://blueprints.launchpad.net/ubuntu-docs/+spec/desktop-o-ubuntu-docs-strategy
[17:23] <j1mc> if someone else should be assigned, please feel free to re-assign
[17:24] <jcastro> davidm: any idea when the app will suck in the schedule?
[17:27] <dupondje> thanks to the guy who fixed the MoM :)
[17:34] <stgraber> pitti: for bug 436936 should I upload the suggested fix to Oneiric for both gdm and kdebase-workspace and upload the same to natty-proposed for testing (bug will need extended testing with a range of graphic cards to make sure we don't get any regression)
[17:35] <dupondje> somebody should accept openssl into oneiric :) cant build half of packages because of it now :)
[17:36] <micahg> dupondje: it's in binary new
[17:38] <dupondje> micahg: I know. but pbuilder can't build alot now because ca-certs depends on it
[17:41] <micahg> jdstrand: do you have time to look at openssl in binary new?
[17:42] <jdstrand> micahg: not atm-- possibly later today (another aa who is on duty today may be able to)
[17:42] <jdstrand> micahg: that said armel is ftbfs
[17:42] <micahg> jdstrand: ugh, should that be fixed before going through binary new, it's blocking most of the archive?
[17:43] <jdstrand> micahg: meh
[17:43]  * jdstrand looks
[17:43] <jdstrand> it is a weird error in armel, I don't know how to fix it. might be a chroot problem
[17:43] <micahg> jdstrand: I only pinged you in case it needed some sort of security team review, was going to ping the AA on duty
[17:43] <jdstrand> lamont: ^
[17:44] <lamont> it's arm.
[17:44] <jdstrand> micahg: cjwatson did the upload, so I don't think it needs anything special
[17:44] <micahg> jdstrand: k, I'll ping another AA
[17:45] <jdstrand> micahg: I'm already doing it
[17:45] <micahg> jdstrand: oh, heh, sorry then, but thanks :)
[17:45]  * jdstrand was thinking the armel thing would need to be fixed, but since it is blocking everything, let's not
[17:47] <lamont> apparently apt needs a recompile to survive what 4.6 did to it
[17:48] <lamont> so don't expect oneiric arm builds until I get poked to do the bootstraporama
[17:49] <lamont> jdstrand: and it'll require me to deal with it
[17:49] <lamont> for some value of "me"
[17:49] <stgraber> Laney: ping
[17:50] <Laney> stgraber: hi
[17:50] <stgraber> Laney: hi, spec still didn't appear on the summit website ... can you try setting Definition to new maybe ?
[17:50] <Laney> haha
[17:50] <Laney> maybe someone can tell us how this was done in the past? ;-)
[17:50] <stgraber> Laney: scheduler should run in 10 minutes, if it still doesn't appear, I'll just add it manually in the DB :)
[17:52] <stgraber> Laney: comparing with other specs I registerd and that got approved, only the Definition is different, so if changing it doesn't work, I don't know what will :)
[17:53] <j1mc> stgraber: you might not be the right person for this, but i think i registered my blueprint under the wrong project. i can't change the project, should i just create a new one, and mark the old one as superceded?
[17:54] <j1mc> stgraber: here's the link: https://blueprints.launchpad.net/ubuntu-docs/+spec/desktop-o-ubuntu-docs-strategy  if you go to https://blueprints.launchpad.net/ubuntu-docs/ it says, "Launchpad does not know how Ubuntu Documentation tracks feature planning or documentation."  that the project
[17:54] <j1mc> which isn't good.  : )
[17:54] <stgraber> j1mc: don't you see a "re-target" button ?
[17:54] <jdstrand> lamont: heh, ok :)
[17:54] <stgraber> s/button/link/
[17:54] <j1mc> yep
[17:54] <j1mc> ah, got it... thanks.
[17:55] <stgraber> yeah, for whatever reason it's not in Edit details :)
[17:55] <j1mc> i thought that might be just for re-targeting to a new sprint or release milestone
[17:56] <stgraber> Laney: did you change the Definition to new ? scheduler is supposed to run in ~5 minutes
[17:57] <Laney> stgraber: rushing, lost network
[17:58] <Laney> done
[18:00] <jdstrand> micahg: done
[18:01] <micahg> jdstrand: thanks
[18:01] <jdstrand> sure
[18:01] <stgraber> Laney: thanks
[18:02] <micahg> dupondje: openssl should be done, there might be other issues though
[18:06] <Laney> stgraber: no good?
[18:06] <stgraber> Laney: just appeared on the schedule!
[18:06] <stgraber> I'm going to move it to the right slot now
[18:08] <stgraber> Laney: ok, scheduled at 16:15 in a 20 slots room. Now to solve the conflicts :)
[18:11] <Laney> :-)
[18:18] <stgraber> Laney: we still have multiple conflicts but next run of the scheduler should move some stuff around to fix that
[18:25] <ScottK> Did someone look into perl 5.12?
[18:25] <ScottK> I'm not volunteering to do it, but with the transition started in Debian, I think the sooner the better.
[18:27] <SpamapS> ScottK: nah, lets just hold off until 6.00 ;)
[18:27] <ScottK> Python3 will be default befor that happens.
[18:33] <stgraber> ScottK: I'm currently looking at bug 436936 and preparing the new upstart job for kdebase-workspace. Is that something you want uploaded to Oneiric as soon as it's ready or do you prefer to wait until someone has something else to upload ?
[18:34] <ScottK> stgraber: kdebase-workspace is a huge build.  It's probably better just to commit it to bzr.
[18:35] <stgraber> ScottK: what's the right place to commit that ? apt-get showsrc tells me lp:~kubuntu-members/kdebase-workspace/ubuntu but bzr tells me it doesn't exist ...
[18:35] <ScottK> stgraber: Should be ~/kubuntu-packagers.
[18:35] <ScottK> We just moved them and the packages aren't updated yet.
[18:35] <ScottK> You should have access there.
[18:36] <stgraber> ok, I'll also make sure debian/control has the rights Vcs field then :)
[18:57] <kees> jcastro: how do I mark a blueprint to _not_ be auto-scheduled for UDS? i.e. I want to keep it as a work-item tracker but not have discussion.
[18:58] <slangasek> kees: have it rejected for the sprint
[18:58] <slangasek> it can be targeted to oneiric without being accepted for uds-o
[18:58] <jcastro> kees: what he said ^
[18:58] <kees> slangasek: ah-ha! okay
[19:03] <stgraber> ScottK: ok, pushed to ~kubuntu-packagers/kdebase-workspace/ubuntu/. Was just wondering how you're dealing with SRUs though as I noticed a natty-proposed changelog entry in that branch (not sure you want to mix -proposed and oneiric changelog entries)
[19:04] <ScottK> stgraber: We normally just keep a 'trunk' so building you change on top of natty-proposed is good.
[19:30] <SpamapS> hmmm.. LP shows openssl 1.0 in oneiric, but my mirror does not..
[19:30] <Laney> it is/was in NEW
[19:31] <SpamapS> DOH
[19:32] <SpamapS> https://launchpad.net/ubuntu/oneiric/+queue?queue_state=0&queue_text=openssl
[19:32] <SpamapS> maybe just need to wait for a mirror update?
[19:32] <micahg> SpamapS: yeah, it was freed about 90 minutes ago
[19:32] <SpamapS> AH
[19:32] <SpamapS> where is that time? the package in LP says 17 hours
[19:33] <micahg> SpamapS: check scrollback here :)
[19:33] <SpamapS> doh
[19:37] <maco> pitti: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141 im lost. a 10.10 user says this still happens for them, yet it's marked fix released in karmic and discussion continues... any idea what the next step is?
[19:40] <SpamapS> maco: IIRC it was converted to an upstart job in 10.10 .. maybe the start on needs work?
[19:49] <maco> SpamapS: yes it was converted, and there's also a comment in there with pitti sru'ing something...and i dont know what the patch was that he sru'd
[19:59] <SpamapS> maco: I believe the fix was to send smbd a HUP whenever cups starts
[20:00] <stgraber> ScottK: ok, now for the SRU. I see that there's already a kdebase-workspace in proposed. Should I upload the upstart job SRU now or do you prefer to wait for the current one to hit -updates and then upload the upstart job fix in -proposed ?
[20:01] <SpamapS> maco: actually no, what happens is smbd starts cups in its pre-start
[20:02] <SpamapS> Oh wait, no.. ugh.. ok.. so confused .. thats not done either.
[20:04] <ScottK> stgraber: I'd prefer to let the current one get to -updates first.
[20:04] <ScottK> Entangled SRUs get complex.
[20:05] <bbigras> I made a branch and a debdiff to fix a little bug I got with pnopaste on Lucid (bug 771421). What should I do next?
[20:05] <SpamapS> ScottK: +1 .. one at a time please. :)
[20:06] <stgraber> ScottK: ok. I'll have the gdm uploaded in a few minutes, so we can probably do the testing with this one and if it works fine, the kdebase-workspace one should be easy (as the diff is identical)
[20:43] <spartan-11510> Hi!
[20:43] <spartan-11510> I've a little proplem
[20:43] <spartan-11510> I can't upload my pgp key on launchpad
[20:44] <micahg> spartan-11510: try #launchpad for support with that
[20:44] <spartan-11510> Ok thx
[21:04] <cjwatson> dupondje: I just finished fixing MoM this morning, so it was probably running when you asked about it.  the first successful run for ages completed at 13:58 UTC
[21:05] <geser> \o/
[21:06] <cjwatson> it required backporting patch 2.6 in order to successfully unpack banshee, and then running pack-archive to free up some disk space
[21:07] <geser> is there enough free space or do we get "disk full" during oneiric?
[21:07]  * micahg hugs cjwatson for fixing MoM
[21:07] <cjwatson> geser: I think it should be OK; the problems typically arise if it breaks for a while and nobody notices
[21:07] <cjwatson> because it uses temporary space proportional to the size of the packages it needs to operate on in a given run
[21:07] <cjwatson> (AIUI)
[21:08] <cjwatson> /dev/cciss/c0d0p1    557446636 472874300  78953604  86% /
[21:08] <cjwatson> also the more merges get done the fewer base revisions it has to keep
[21:11] <jcastro> ScottK: try to edit the schedule now
[21:11] <ScottK> Trying ...
[21:12] <ScottK> I have the edit button now.
[21:12] <ScottK> jcastro: Thanks.
[21:33] <dupondje> cjwatson: :) nice
[22:58] <soren> Yay. First server upgraded to oneiric.
[22:59] <ajmitch> as long as it's not a critical production server
[22:59]  * highvoltage will try for oneiric+1 then :(
[23:08] <Keybuk> I wish the Ubuntu dch would recognise "unstable" ...
[23:22] <soren> ajmitch: Hardly :)