/srv/irclogs.ubuntu.com/2014/07/01/#ubuntu-release.txt

=== alexabreu is now known as alex-abreu|off
=== FourDollars_ is now known as FourDollars
jibelHi, could someone review and approve update-manager and update-notifier in precise-proposed unapproved queue? It's required for HWE EOL notifications07:15
jibelRAOF, arges ^07:16
* RAOF looks07:17
RAOFjibel: Hm. Won't be able to accept update-manager until the existing SRU is verified - bug07:22
RAOFbug #131139607:22
ubot93bug 1311396 in update-manager (Ubuntu Trusty) "broken translations results in traceback in new release notification" [Undecided,Confirmed] https://launchpad.net/bugs/131139607:22
RAOFFeel free to test that and mark it as verified :)07:23
jibelRAOF, thanks, I verify it.07:23
jibel+'ll07:23
RAOFjibel: Am I right in observing that the update-notifier update should be dependent on the update-manager update? It looks like the update-notifer script unconditionally calls hwe-support-status, which is added in the new update-manager, right?07:32
jibelRAOF, you're right. let me ask mvo to join this channel.07:36
RAOFJust upload with an appropriately versioned Depends and it should be fine.07:41
RAOFHey mvo!07:49
mvoRAOF: hi, thanks for your review of update-notifier07:49
mvoRAOF: I'm happy to add the dependency, but iirc (need to double check) it was done in a way that even without update-manager-core it would still work fine07:51
mvoi.e. it would just ignore this part07:51
RAOFIt looked to me like it didn't check whether the file existed and just called it; that would generate an error message somewhere, right?07:51
RAOFmvo: It calls “/usr/bin/hwe-support-status || true”; that's going to error if /usr/bin/hwe-support-status doesn't exist, right?07:53
mvoRAOF: yeah, there is || true that prevents damage and it won't be part of the user visible output, but I agree that for correctness it makes sense to add the dpenency07:53
RAOFIt'll certainly help in testing :)07:54
RAOFSince you can't usefully test without the dependency.07:54
mvo*cough* yes. sorry for that, I will re-upload07:55
ogra_could some archive admin NEW dbus-property-service ?10:05
seb128ogra_, done10:23
apwit looks like libgtop2 2.30.0-0ubuntu1 just migrated but this migrating seems to have ripped a versioned libgtop-2.0.so.7 out from under unity7 which no longer starts; i am wondering why britney didn't stop that10:26
apwplus could someone else confirm my diagnosis10:27
apwspecificially bamfdaemon seems to be linked to it and no longer starts, which seems to be fatal to unity710:27
apw(read, i have a blank desktop)10:27
Laneyapw: looks true from the package list10:31
seb128shrug10:31
Laneyfile list10:31
apwi suggest upgrading is a bad idea right now10:31
seb128can you mention it on -devel where the people who did the merge/upload are as well?10:32
seb128apw, how would have britney stopped that?10:33
seb128we don't have autopkgtests checking that unity runs10:34
LaneyIf there were any tests10:34
Laneylike testing bamf works or something10:34
seb128right10:35
apwseb128, hmmm well, i assume something else was done wrong which means it could not detect it, and i think you are suggesting that the binaries are -7 cause they contained abi 7 and should have changed to -10 and did not, if they had, britney would have had a chance10:36
seb128right, if they had renamed the binary we would have no issue10:36
seb128the old abi would still be around and britney would have stopped the migration until everything is ported to 1010:36
LaneyTransitions at the archive level are moving dependencies from one package (containing the old SONAME) to another (containing the NEW)10:37
LaneyBut if you forget to rename then you just have the new one and the archive seems to be all in order10:37
apwseb128, yep, i am not blaming britney that is for sure, i was wonderng how we got there, and user error is the answer10:37
LaneyBetter test coverage would have helped10:38
apwyes that is true indeed10:38
seb128well, what we need is autopilot tests integration in britney/autpkgtests10:39
seb128we have plenty of those for unity10:39
seb128they just don't run there10:39
apwso nearly enough :)  anyhow, sounds like it is getting sorted, thanks for your prompt help10:40
seb128yw, thanks for pointing it out!10:43
seb128revert uploaded10:44
apwit is probabally worth scoring up the lagging arm64 build for this revert given its effects: https://launchpad.net/ubuntu/+source/libgtop2/2.30.0.is.2.28.5-0ubuntu1/+build/614581011:12
cjwatsoncan't make it go faster without cancelling builds11:14
* cjwatson cancels the most recently started build, will retry it in a sec11:14
ogra_seb128, can i have a binary NEW for dbus-property-service too ?11:15
apwcjwatson, thanks, it seemed to keep moving out to 10m again every time i looked11:16
cjwatsonBuilding now11:16
seb128ogra_, done11:38
* ogra_ hugs seb128 11:38
ogra_thanks !!11:38
seb128yw! ;-)11:38
seb128that was an easy one11:38
mvojibel: I wonder if we simply should reject updatemanager in precise-proposed for #1311396 to unblock the SRU for the HWE stack11:42
jibelmvo, I agree, the SRU should be against the langpacks anyway since there is no other change in update-manager, isn't it?11:43
mvojibel: yes11:46
mvoso could a archive admin please remove update-manager  1:0.156.14.14 from precise-proposed ? so that we can upload a new .15 with a import HWE update?11:51
=== psivaa_ is now known as psivaa-lunch
=== psivaa-lunch is now known as psivaa
=== ogra_` is now known as ogra_
cjwatsonjibel,mvo: removed14:17
mlankhorstcjwatson: can you accept xorg-lts-transitional ?14:24
cjwatsonwhere?14:24
mlankhorsttrusty14:24
jibelcjwatson, thanks. Can you approve update-manager 1:0.156.14.15 in precise ?14:26
cjwatsonmlankhorst: done14:26
mlankhorstty14:26
cjwatsonjibel: doesn't it need to be rebased against .13?14:27
mlankhorstI'll make a backup and try to upgrade tomorrow :p14:27
jibelmvo, ^14:27
jibelcjwatson, .14 was a change in the translations which come from LP, but better wait for mvo's answer14:28
cjwatsonsure, but if I removed it that must be because it made things worse, right?14:29
cjwatsonotherwise it was unnecessary to remove it14:29
mvocjwatson: its like jibel said, the diff between 13->14 are only po files. I expected that translations.lp would import them from my upstream upload but apparently it didn't :/ it does not make anything worse, I just asked for removal to speed up the process14:38
cjwatsonoh, so there was no need to remove really then14:41
cjwatsonok, have to go to the bike shop, will have a look later14:41
mvothanks14:43
mlankhorstbdmurray: hm why is https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-raring/+bug/1246384 not a dpkg bug? seems to me that dpkg fails to remove all files for xserver-common-lts-raring before the postrm hook runs..14:43
ubot93Launchpad bug 1246384 in xorg-server-lts-raring (Ubuntu) "xserver-common-lts-raring does not always get correctly removed." [High,Confirmed]14:43
mvoand sorry for the confusion about the rmeoval14:44
barryinfinity: question: why is zope.interface in depwait when python3-zope.event is available in utopic?  https://launchpad.net/ubuntu/+source/zope.interface/4.1.1-2/+build/614434315:22
stgraberbarry: because python3-zope.event isn't in main15:23
barrystgraber: gah15:24
barrystgraber: okay, thanks, i missed that.  MIRing15:24
argesWhats the protocol with sru-releasing packages that I've uploaded or accepted? Do I need to get another person to do the final check?17:01
argesanyway, I would sru-release pacemaker/corosync for precise; but I'm not sure if I should get another person to do that since I sponsored both17:05
=== jsalisbury_ is now known as jsalisbury
slangasekarges: sponsor+accept+sru-release, ok.  prepare upload+accept+sru-release, not ok :)18:32
argesslangasek: so the diffrence is, is it a patch i wrote?18:33
slangasekarges: the difference is whether you can count yourself as a second set of eyeballs18:33
argesslangasek: yea that's what i want to avoid. I like having multiple sets of eyes on any change18:34
slangasekarges: I'm saying the rule of thumb should be that there are at least two sets of eyeballs on the package, the preparer and the SRU team member.  I think it's fine to sru accept a change that you sponsored, provided you're really just sponsoring and not extensively revising18:36
argesslangasek: gotcha.18:36
=== tgm4883__ is now known as tgm4883
popeyhello! is it possible to get marco, mate-session-manager, mate-desktop-environment synced from debian?22:01
popeyIf so, is there some paperwork I need to fill in?22:01
cjwatsonrequestsync(1)22:05
cjwatsonBut, err, we don't appear to have an Ubuntu delta to any of those?22:06
popeygrr22:06
cjwatsonThey're all in utopic at the same versions as in unstable22:06
cjwatsonSo nothing to sync22:06
popey1.8.0 vs 1.8.1?22:06
popey1.8.1-3 vs 1.8.1-4?22:07
cjwatson mate-session-manager     | 1.8.1-3               | sid              | source, amd64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc22:07
popeyI'm going by packages.d.o vs packages.u.c22:07
cjwatsonOh come on those were just uploaded today :)22:07
cjwatsonThey'll auto-sync22:07
popeyoh, i wasn't aware of that22:07
popeyi thought it was all manual, sorry.22:07
cjwatsonVery much automated22:07
popeyYay!22:08
popeythanks22:08
cjwatsonBefore Debian import freeze, anything that doesn't have an Ubuntu delta is auto-synced, basically22:08
cjwatson(There are a few exceptions)22:08
popeyah, got it.22:08
cjwatsonlp:ubuntu-archive-tools auto-sync has the full logic should you ever be unfortunate enough to need to investigate22:09

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