/srv/irclogs.ubuntu.com/2014/04/29/#ubuntu-release.txt

doko_pitti, jibel: https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-python3.4/7/ARCH=amd64,label=adt/  could you have a look?07:34
=== doko_ is now known as doko
dokoinfinity, could you have a look at https://launchpad.net/ubuntu/+source/ruby-patron/0.4.18-2 ? did you have to kill these two before as well?08:00
infinitydoko: That doesn't ring any bells, and the previous version built everywhere. :/08:05
infinitydoko: But, kill now, investigate later.  I need to go to bed.08:06
infinitydoko: This is the first time it's built on ruby2.0, so I assume we've just found a bug.08:07
jibeldoko, pitti restarted it and the testsuite is running08:08
Mirvthe new qtdeclarative-opensource-src binary packages in utopic should be promoted to main like the old packages they replaced, since it's preventing some builds for rsalveti08:13
Mirvafter that rsalveti would probably appreciate kicking rebuilds of https://launchpad.net/ubuntu/+source/qtpim-opensource-src/5.0~git20140203~e0c5eebe-0ubuntu3 and https://launchpad.net/ubuntu/+source/qtlocation-opensource-src/5.2.1-1ubuntu308:15
Laneyas a core-dev he's able to do that himself08:15
Mirvoh, ok (the rebuild part)08:21
Laneyyup08:24
Mirvthe list of new packages that are renames of the old ones that were made transitional: qml-model-qtqml-models2 qml-module-qt-labs-folderlistmodel qml-module-qt-labs-settings qml-module-qtquick-dialogs qml-module-qtquick-localstorage qml-module-qtquick-particles2 qml-module-qtquick-privatewidgets qml-module-qtquick-window2 qml-module-qtquick-xmllistmodel qml-module-qtquick2 qml-module-qttest08:24
dokodpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::Quilt08:26
dokogpgv: Signature made Mon Apr 28 13:12:05 2014 UTC using RSA key ID 311D765A08:26
dokogpgv: Can't check signature: public key not found08:26
dokodpkg-source: warning: failed to verify signature on ./rtkit_0.11-1.dsc08:26
dokodpkg-source: info: extracting rtkit in rtkit-0.1108:26
dokodpkg-source: info: unpacking rtkit_0.11.orig.tar.xz08:26
dokodpkg-source: info: unpacking rtkit_0.11-1.debian.tar.gz08:26
dokodpkg-source: info: applying 01-no_ptrace_cap.patch08:26
dokopatching file rtkit-daemon.c08:26
dokoHunk #1 FAILED at 1766.08:26
doko1 out of 1 hunk FAILED08:26
dokodpkg-source: info: fuzz is not allowed when applying patches08:26
dokodpkg-source: info: if patch '01-no_ptrace_cap.patch' is correctly applied by quilt, use 'quilt refresh' to update it08:26
dokodpkg-source: info: restoring quilt backup files for 01-no_ptrace_cap.patch08:26
dokodpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/01-no_ptrace_cap.patch/ --reject-file=- < rtkit-0.11/debian/patches/01-no_ptrace_cap.patch gave error exit status 108:26
dokoFAILED [dpkg-source died]08:26
dokohow can this happen when the debian upload did patch that correctly?08:26
Laneythat package has an ubuntu.series file08:30
dokoahh08:33
dokoomg, whole lot of ruby modules wants to migrate to main08:34
dokobanned09:08
ogra_infinity, so i talked to the heise author and he can obviously still reproduce the screensaver issue with his iso ... can that be ?09:26
seb128ogra_, what issue?09:27
ogra_seb128, hodling enter for 30sec09:27
ogra_seb128, http://www.heise.de/newsticker/meldung/Sperrbildschirm-bei-Ubuntu-14-04-einfach-zu-umgehen-2178733.html09:27
seb128did he download the iso before it was flagged official and got a wrong one?09:28
ogra_i'll ask him to check the md5 ... just want to be sure its supposed to be really gone09:28
ogra_(my system is obviously already up to date and i didnt use the iso anyway over here)09:28
michagogo|cloudogra_: ask him to update his system?09:29
michagogo|cloudsudo apt-get update && sudo apt-get dist-upgrade09:29
seb128ogra_, we didn't have any unity update since release (there is one SRU in proposed)09:29
ogra_michagogo|cloud, thats not the point, his article claimed the release iso has the issue09:29
seb128ogra_, you can also ask for the unity package version (dpkg -l | grep unity)09:29
ogra_will do09:29
seb128ogra_, we didn't have any unity update since release09:29
seb128so that doesn't make sense09:30
ogra_seb128, and the iso surely shouldnt have the issue, right ?09:30
seb128if it's fixed in the current version, it was fixed in release09:30
ogra_ok09:30
seb128no it shouldn't09:30
seb128and we tested the fix/verified it when it landed09:30
seb128there could be other issues though09:30
ogra_right09:32
ogra_seb128, seems he has the right iso and also unity 7.2.0+14.04.20140416-0ubuntu1 ... he uses nvidia drivers though09:49
pittidoko: run #8 finished, and failed due to su -c ... nobody; that's another fallout from last release's change that these accounts have a disabled shell09:51
seb128ogra_, can you ask what he does exactly and what happens?09:51
pittidoko: the usual fix is to call "su -s /bin/sh -c ..."09:51
ogra_will do09:51
seb128ogra_, ok, so I tested with the version which had the bug and with the fixed version09:52
seb128ogra_, sitting on enter for 45 seconds09:52
ogra_and you cant repro i guess09:53
ogra_(with the fixed)09:53
seb128ogra_, with the old version it would display "wrong password" and then the spinner would stop spinning and nothing would happen, then when you release the keypress unity would segfault09:53
seb128ogra_, with the new one, the spinner keeps spinning and it does a "wrong password" every few seconds09:53
seb128like if you kept trying to enter wrong passwords09:53
seb128no segfault09:53
ogra_seb128, hmm, with the iso he seems to see compiz crash and gets "respawn to fast" messages it seems10:04
seb128ogra_, can he submit the crash report/get a bt from apport?10:04
ogra_(which might not be the same segfault)10:04
ogra_i will ask10:05
ogra_not sure he is that technical :)10:05
dokopitti, you mean fallout caused by autopkgtest?10:26
pittidoko: no, by whichever package sets up the default user base (user-setup?), it caused massive pain10:27
cjwatsonpitti: base-passwd10:28
cjwatsonSorry for the pain but I think it was overdue10:28
pittino, not user-setpu10:29
pittiah, base-passwd10:29
pittiI think we fixed most fallout by now, but it seems python3.4's test still needs to be fixed10:29
cjwatsondoko: s/trusty/utopic/?11:09
dokoshit ... yeah11:09
ogra_cjwatson, oh, after you fixed the "touch i386 accidentially gets promoted all the time" issue on cdimage i assume i have to run mark-current for i386 too when manually promoting, right ?11:17
cjwatsonI believe so, yes11:17
ogra_thanks11:17
ogra_just wanted to make sure11:17
xnoxdoko: just install devscripts from utopic... it's fixed now.11:48
=== pete-woods1 is now known as pete-woods-lunch
dokopitti, jibel: please could you give back the rails-3.2 autopkg test. should have now all dependencies available for ruby2.114:18
cjwatsonwg 2514:18
cjwatsonsigh14:18
rbasak^^ I didn't realise this was new. Should this have happened, or should it just be on ddebs instead?14:23
rbasakI also appear to have forgotten to run update-maintainer :-/14:23
Laneyrbasak: If it's a -dbg package then it's the same as any other new binary as far as the archive is concerned14:25
cjwatsonIt's new, but it's also not a problem14:25
Laneyddebs.u.c should get a -dbgsym which is empty and Depends on the -dbg14:26
rbasakRight, but is -dbg the "right" way to do things?14:26
cjwatson*shrug*14:26
rbasakOK, I won't worry about it then :)14:26
cjwatsonIt's not worth diverging from Debian to remove it14:26
rbasakThanks!14:26
LaneyIt's the only way Debian has, and we don't bother removing them14:26
pittidoko: will do later; there's the d-jenkins migration to LP teams happening, so it's shutdown14:30
pittidoko: thanks!14:30
=== pete-woods-lunch is now known as pete-woods
sil2100Hi SRU team! In the UNAPPROVED queue there seems to be and qtorganizer5-eds SRU waiting since last week - is there anything wrong with it, should we take some action?15:44
bdmurraysil2100: for trusty? the queue is quite large so I'd be surprised if anyone has looked at it yet16:06
bdmurrayslangasek: is upgrading from P w/ -lts- packages to Q supported?16:06
sil2100bdmurray: ok, thanks :)16:10
sil2100Just been worried it got forgotten or (even worse) it had some problems that we didn't notice16:10
slangasekbdmurray: upgrading to Q now, or in the past given that it's now EOL?  anyway, I'm pretty sure we said we wouldn't support upgrades from P w/ lts-raring- to Q, but I don't remember if we said we would support P/ w lts-quantal- to Q16:42
bdmurrayslangasek: Q isn't EOL quite yet, infinity was talking about sending an announcement then waiting 4 weeks16:46
bdmurrayslangasek: but okay, not supported16:46
slangasekhas the announcement been sent?  It's supposed to be EOL now; has the security team agreed to supporting it an extra month?16:48
mdeslaurkill it kill it kill it16:53
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
infinitymdeslaur: I'll send the announce today (honest) and give it three weeks (which is what I gave raring), which will allow the last SRU kernel to land.17:25
mdeslaurinfinity: ok, sounds good17:25
slangasekinfinity, cjwatson, pitti: ddebs.u.c seems to be empty for trusty-proposed; is this a known issue?18:01
slangasekno ddebs for -updates seems problematic for errors retraceability18:01
infinityslangasek: s/proposed/updates/ you mean?18:02
slangasekinfinity: yes, that18:02
infinityslangasek: And not known by me until just now...18:02
infinityGiven how pitti does refcounting, some of them might be long gone by now, too. :/18:03
slangasekfwiw I only noticed because I had dpkg-dbgsym installed locally, and update-manager was throwing me to the 'partial upgrade' screen18:03
infinityslangasek: Oh, feh.  It's right there in the crontab.18:07
slangaseknext year, in the ho^W^W soyuz18:09
infinityslangasek: Should fix itself in a few minutes, though no idea how many will have been irrecoverably lost. :(18:09
infinityProbably a week or more of SRUs.18:09
slangasekwell, no worse crying over spilled ddebs18:10
infinityI guess the upshot is that most of what was SRUed in the first week or two are packages we tend to SRU a lot. :P18:10
slangasekjust one more reason to get ddebs into soyuz18:10
slangaseks/worse/use/ (?)18:10
infinityTotal brain/finger disconnect?18:11
infinityslangasek: Alright, ddebs should exist for -updates.18:52
slangasekhuzzah18:52
infinityslangasek: No idea how many were lost, but dpkg is there, at least. :P18:52
infinityLet's see if I can save a few more.18:54
apwinfinity, i thinik when the kernel started to go missing, he upped the retension a lot, to like 30 days or soemthing19:30
apw(for ddebs which are unclaimed)19:31
robrucjwatson, hiya, we have another unity8 release that needs to be version bumped to get through -proposed. thanks!20:27
infinityrobru: On it.20:38
robruinfinity, thanks!20:39
xnoxare daily _trusty_ images going to be build? useful to use those during sru verification20:53
=== jhodapp is now known as jhodapp|afk
infinityxnox: They will be, yes.21:08
cjwatsonpitti: Do autopkgtest jobs need a kick after the Jenkins migration?22:00
cjwatsonI notice that software-properties (at least) hasn't run22:01
cjwatsonMaybe that's what jibel just mentioned on some internal lists ...22:01
robruinfinity, cjwatson : I'm a little confused about unity8, excuses says the jenkins is running, but jenkins seems to indicate that the tests passed? is there some kind of hiccup there?23:41
infinityrobru: The jenkins instance was heavily mangled today, I suspect there's some fallout that jibel might need to look at.23:42
robruinfinity, ok, thanks23:43

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