/srv/irclogs.ubuntu.com/2013/10/25/#ubuntu-release.txt

xnoxPlease demote boost1.53 src+binaries into universe =)00:04
infinityxnox: Done.00:25
xnox\o/00:26
doko_xnox, so gccxml should go too00:30
infinityByebye, libperl5.14.00:31
xnoxdoko_: libboost-python1.54-dev still "Recommends" gccxml. Is main done by build-depeds, depends & recommends?00:35
xnoxdoko_: or why is gccxml not in components-missmatches. I agree though gccxml should be in universe.00:36
infinityxnox: Recommends will keep it in main.00:37
xnoxdoko_: unless i package https://github.com/alexleach/gccxml_plugin which removes all gcc4.2 code.00:43
infinityI suppose it's too late to suggest we just drop boost entirely from Debian and Ubuntu?00:46
xnoxinfinity: to be honest, majority of packages should switch to C++11 & STL. Half of things only uses crap like unique_pointer & command-line-arg-parser from boost.00:47
wgrantxnox, doko_: That's why I initially demoted gccxml to Suggests, but someone disagreed.00:58
doko__xnox, wgrant: the objections for the suggests were for saucy. please do it for trusty01:21
doko__xnox, nice plugin, however should stay in universe01:21
xnoxdoko__: ok i'll do it for trusty, sometime with next / subsequent uploads.01:22
xnoxno rush to do it right now.01:22
ScottKdoko__: I'll see if I can find someone with interest, otherwise we can remove it.02:18
tseliotany admins around?09:06
tseliotdidrocks: ^09:07
didrockstseliot: in meetings09:12
tseliotdidrocks: ok, never mind, thanks09:12
didrockssorry ;)09:12
=== doko__ is now known as doko
tseliotRiddell: are you around?09:47
Riddellhi tseliot09:51
tseliotRiddell: hi, we filed a MIR in bug 1204820 but we didn't specify that we needed that for both saucy and precise09:53
ubot2Launchpad bug 1204820 in nvidia-prime (Ubuntu) "[MIR] nvidia-prime & fglrx-pxpress" [Undecided,Fix released] https://launchpad.net/bugs/120482009:53
cjwatsonRiddell: can I sync webcit and drop https://launchpadlibrarian.net/142321538/webcit_8.16-dfsg-1_8.16-dfsg-1ubuntu1.diff.gz ?  Same reason as citadel or citadel-client or whichever it was the other day09:54
tseliotRiddell: so now the two packages are in main only in Saucy. Would it be ok if I added the two packages to the seeds for precise and we moved them to main?09:54
xnoxtseliot: not really, why you need that?09:56
Riddellcjwatson: yeah go for it09:56
cjwatsonta, done09:56
Riddelltseliot: mm didn't we release precise last year?09:57
xnoxtseliot: sometimes security team picks up support for previous releases, if same package gets into main into latter release.09:57
tseliotxnox: because packages in main cannot depend on packages in universe09:57
tseliotRiddell: well, there are point releases09:57
xnoxtseliot: ok, but we don't change components post-release without a good reason. and if done the change would only be visible in -security and/or -updates only.09:58
tseliotand the two packages were included in 12.04.309:58
xnoxtseliot: what are the packages in question?09:58
tseliotxnox: nvidia-prime and fglrx-pxpress09:58
xnoxtseliot: neither of which have reverse dependencies in precise/main, or do you plan to introduce one?10:00
Riddellxnox: he wanted to add to seed10:00
RiddellI suppose it makes sense but I've not done it before so it makes me a little nervous I'm missing something10:00
xnoxtseliot: i'm not sure. Where did you want to seed them into? "supported" or on to desktop-cd?10:02
tseliotxnox: for now it's just that if I upload the package, it ends up in NEW10:02
tseliotas it happened to nvidia-prime10:02
tseliotxnox: supported, I guess10:03
tseliotor whatever else can prevent my packages from ending up in NEW10:04
xnoxtseliot: yeah, that's unfortunate bug in launchpad, but pretty much only affects you so far and poor AA who needs to de-new it constantly.10:04
Riddelltseliot: it needs a SRU request10:04
Riddellif you want new versions in precise10:04
tseliotRiddell: yes, I've done that10:04
xnoxtseliot: and i don't think seeding in main will help at all, cause i think launchpad still says "oh look precise-release didn't have it" => NEW, and it should learn to look at -updates pocket.10:04
Riddellit won't end up in new there's already packages in precise10:04
Riddelltseliot: bug no?10:05
cjwatsonRiddell: yeah it will10:05
xnoxRiddell: i think those two packages fall under "hardware enablement stacks" with respect to kernel & graphics packages.10:05
xnoxcjwatson: ^ wouldn't it?10:05
cjwatsonRiddell: there's an LP bug relating to post-release pockets and ancestry10:05
cjwatsonbut it's not a huge problem10:05
tseliotRiddell: bug 1224098 and bug 121965010:05
ubot2Launchpad bug 1224098 in nvidia-prime (Ubuntu Saucy) "xserver wont start after nvidia-prime installation" [High,In progress] https://launchpad.net/bugs/122409810:05
ubot2Launchpad bug 1219650 in nvidia-prime (Ubuntu Saucy) "Failed to install on 12.04.3 , /var/lib/dpkg/info/nvidia-prime.postinst: 36: printf: 08: not completely converted" [High,In progress] https://launchpad.net/bugs/121965010:05
xnoxouch.10:06
tseliotoh, so it's a bug10:06
Riddelltseliot: just get SRU team to approve it from New then10:07
cjwatsonno seed change will affect NEW handling10:07
tseliotcjwatson: ok, thanks10:08
tseliotRiddell: the SRU team is subscribed to the bugs10:08
Riddelltseliot: ok so upload package, add to seed, get SRU to approve it, if an archive admin needs to move to main that's the last step I think10:09
tseliotRiddell: but really it should be at least removed from NEW so that it ends up in the "pending approval" state10:09
cjwatsontseliot: dude it makes no difference10:09
cjwatsondon't obsess about the new vs. unapproved thing10:09
cjwatsonit requires manual action either way10:09
cjwatsonand we *can't* move it from new to unapproved anyway10:10
cjwatsonnot without fixing the lp bug10:10
tseliotcjwatson: can any member of the SRU team move it from NEW without being an admin?10:10
cjwatsonany member of the SRU team should be able to accept it if they think the changes are appropriate, yes10:10
cjwatsonwe don't have per-queue permissions10:10
tseliotok, good10:11
cjwatsonubuntu-sru has queue admin permissions for <all stable releases>-{proposed,updates}10:11
tseliotit's a rather serious issue, so I didn't want it to get stuck for any reason10:11
tseliotgood10:12
=== alex_abreu is now known as alex-abreu
xnoxI've uploaded sflphone rebuild against boost1.54, it's build-deps are not installable in trusty-proposed, but they are in trusty. Can that source package be somehow build with just "trusty" pocket enabled (a non-virt ppa?), binaries copied to trusted-proposed & migrated to trusty?13:57
xnox( i guess that can be last resort, if the build-deps uninstallability is not solved)13:57
cjwatsona non-virt PPA is possible, but fairly cumbersome; last resort as you say13:57
xnoxok.13:58
cjwatsonsflphone is part of the ucommon transition IIRC13:58
xnoxyeap, correct.13:58
xnoxi've bumped it to boost1.54, and it does build correctly in -release, so it shouldn't cause any additional entanglement in the ucommon transition.13:59
cjwatsonI don't especially object but I wonder if it would be better to just slap that transition through ASAP13:59
xnoxwell, i'm juggling slepc mini-transition and ogre-1.9 mini-transitions, to finally get off boost1.49.... having 3 boosts in the archive is too much.14:03
cjwatsonI can start on the obvious bits of it at least14:04
xnoxack. and I think boost1.54 will eventually be stuck on libav9 transition, unless e.g. old blender is rebuilt in trusty-release, bypassing new upstream release.14:05
jpdsAnyone from the SRU team know when https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719 will go into -updates ?14:05
ubot2Launchpad bug 995719 in puppet (Ubuntu Precise) "process_name.rb removed in 2.7.11 but still provided by puppet-common" [High,Fix committed]14:05
xnoxjpds: from http://people.canonical.com/~ubuntu-archive/pending-sru.html it looks like it's good to go, but SRUs are not usually released on Fridays.14:06
xnox(due to many developers missing typically over the weekend to handle a regression)14:07
cjwatsonWe don't normally.  That one looks harmless enough though?14:07
xnoxi think it is harmless enough.14:07
jpds"Mostly harmless."14:07
cjwatsonYeah, just removing a file14:07
cjwatsonjpds: released14:08
jpdscjwatson: Thank you!14:08
cjwatsonoh, I could've just retried libccaudio2, bah14:11
cjwatsonhm, the libucommon-dev -> libgnutls28-dev dep is going to be troublesome, and the ucommon changelog says it fails to build against libgnutls-dev14:15
xnoxI don't understand britney's excuse for not considering gnuradio. Can somebody help me, please? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html14:57
cjwatsonthat's probably NBS in -proposed, give me a minute14:58
cjwatson(proposed-migration needs some manual care in the case where one of the intermediate unmigrated versions has NBS binaries)14:59
xnoxok.15:03
cjwatsonxnox: removed, should work after the next publisher run15:06
cjwatsonright, let's see if the server image will build15:35
cjwatsonif this works I think I'll call it a week15:37
* cjwatson quickly fixes up ~cdimage/.isotracker.conf15:44
infinitycjwatson: FWIW, I concur that we should probably pull arm64 out of slow_arches nowish.  New uploads should take precedence, so the only reason it would lag is build failures, which we'll have to deal with one way or another.15:48
cjwatsonYeah, I was considering doing it before I finish for the day.15:48
infinityI'd certainly be more comfortable if our builders were more reliable, but I'm not holding my breath on that happening soon.15:48
cjwatsonhttp://people.canonical.com/~ubuntu-archive/proposed-migration/trusty_uninst_full.txt  if anyone fancies a project :-)15:49
cjwatsonthat's with considering arch: all on all architectures rather than just i38615:49
infinityThat's more depressing than the regular uninst.15:50
infinity(But actually, not all that bad)15:50
cjwatsonIt isn't quite as terrible as I'd expected.15:51
infinityppc and armhf are a bit worse than I suspected.  Lots of "do we actually care?" versus "arch:all packages that depend on :any should probably not be :all" decisions to take there.15:51
infinityOr, arguably, a Soyuz bug/misfeature to fix in some cases.15:52
cjwatsonI tried to persuade the nodejs people of the error of their ways a couple of weeks ago.  Not sure I've got the message across yet.15:52
cjwatson(I think all their packages should be Architecture: any Build-Depends: nodejs15:52
cjwatson)15:52
infinityAs in, if there's no build for a source in a DAS, perhaps we shouldn't publish the arch:all packages on that arch.15:52
infinityNot counting things that are all-only.15:53
infinitySo, it gets a bit messy to get the heuristic right.15:53
infinityBut I still suspect that's a correct heuristic to apply.15:53
cjwatsonI think most of these are all-only with arch-specific deps.15:53
infinityYeah, that's a harder problem that should be addressed at the package level.15:54
cjwatsonYou may have a point in some cases, yeah15:54
infinityI'm thinking of sources that are "i386 amd64 all", where the all seems to have a legit right to exist, but just shouldn't exist on !x86.15:54
cjwatsonThough I'd kinda like to persuade Debian of it first15:54
infinityAnd I'm not sure, but I think DAK might get that case right.15:54
cjwatsonJust in case there are weird exceptions ...15:54
cjwatsonNever heard of it does so.15:54
cjwatson*doing15:55
infinityI know they pull some tricks to not publish arch:all stuff when the :any build on an arch is lagging.15:55
cjwatsonI thought they just kept publishing the old one.15:55
infinityYes, but not the new one.15:55
cjwatsonOh, right, yeah15:55
cjwatsonI guess that might imply this15:55
infinityWhich works around the apt bug/misfeature we run into with our "publish them all" approach.15:56
* cjwatson checks15:57
cjwatsoninfinity: Nope - 7kaa is Architecture: amd64 i386 all, but 7kaa-data is published in unstable/powerpc15:59
infinityAhh, kay, so much for the hope that someone else got that more right than us. ;)15:59
infinityI guess it's hard to know for sure that you got it right.  One could construct a package that produces "foo-i386, foo-amd64, foo-sparc, foo-python-portable" and you'd actually want the last one on all arches.16:01
infinityOr whatever.16:01
cjwatsoninfinity: I think there really are such cases with Java.16:02
cjwatsonBuild foo-java on all architectures, foo-jni on some.16:02
infinitycjwatson: Right, so perhaps not worth trying to be clever at the archive level there.16:03
stgraberogra_, lool: I've turned off import-images for system-image as the last touch build is breaking the delta generation tool, I need to look into the specific problem20:39
ogra_stgraber, ok21:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!