=== med_ is now known as Guest34220 === psivaa_ is now known as psivaa [07:31] jbicha, i think that is actually nbs in -proposed, will see if that sorts it out [08:48] jbicha, looks to have done the trick [09:52] infinity, bug #1652147 seems to indicate that if someone was on trusty and got the broke 1.21.4* shim and upgraded to xenial they would _then_ have an unbootable combination; dunno if we need a .is. upload there? [09:52] bug 1652147 in ubuntu-release-upgrader (Ubuntu) "UEFI secure boot fails after 14.04 to 16.04 upgrade" [High,New] https://launchpad.net/bugs/1652147 [09:54] btw, I updated the report now with explanation and work-around [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [amd64] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [armhf] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [powerpc] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [s390x] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [amd64] (zesty-proposed) [5.19.2-0ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [armhf] (zesty-proposed) [5.19.2-0ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [powerpc] (zesty-proposed) [5.19.2-0ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [s390x] (zesty-proposed) [5.19.2-0ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [arm64] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted gyoto [ppc64el] (zesty-proposed) [1.2.0-2ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [arm64] (zesty-proposed) [5.19.2-0ubuntu1] [11:41] -queuebot:#ubuntu-release- New: accepted yaz [ppc64el] (zesty-proposed) [5.19.2-0ubuntu1] [11:43] -queuebot:#ubuntu-release- New binary: olefile [amd64] (zesty-proposed/none) [0.43-1~ubuntu1] (no packageset) [11:45] -queuebot:#ubuntu-release- New: accepted olefile [amd64] (zesty-proposed) [0.43-1~ubuntu1] === henrix_ is now known as henrix [12:56] a/win 9 [13:04] hi, can you please ignore why autopkgtestsuite? [13:04] Laney, ^^ [13:04] that test was excluded in an Ubuntu specific diff, but now doko sync'd it [13:09] LocutusOfBorg: I guess so [13:25] Laney, do you prefer an ubuntu patch? I think ignoring it is the best solution [13:27] LocutusOfBorg: I don't really mind, probably not that important to have a delta over [13:28] would be good if people would follow through on their test-breaking syncs though :-) [13:28] thank you for pinging! [13:28] I guess so, a crippled autpkgtestsuite is not worth a delta [13:28] thanks for ignoring :) [13:28] hopefully ocaml will migrate [13:31] Laney: is there any way to get KDE KF 5.28 force-allowed ? [13:38] clivejo, can't you retry some of the failed test against -proposed? [13:39] e.g. akonadi/amd64 [13:40] LocutusOfBorg: not sure what you mean? [13:41] clivejo, stuff is failing its autopkgtestsuite, because it is run against -release, not against -proposed [13:41] look e.g. http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#kservice [13:41] autopkgtest for kscreenlocker/5.7.5-0ubuntu1: armhf: Pass, i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Pass [13:41] autopkgtest for kscreenlocker/5.8.5-0ubuntu1: amd64: Pass [13:41] retrying kscreenlocker i386 and ppc64el tests, against -proposed suite might make the testsuite pass [13:42] (append &all-proposed=1 at the end of the retry link) [13:43] at this point we are expecting the landing of Qt5.7.1 as per Mirv comments above [13:44] I'm retrying some of them, just to see if proposed pocket is self consistent [13:47] I retried probably all of them, lets see [13:47] LocutusOfBorg: in the past, we have requested a force-allow, do you know who can do that? [13:55] clivejo, you already pinged who can do that I guess :) [13:55] but some more green in the zesty updates excuses page is nice to have [13:56] it requires little effort to rerun against -proposed pocket, and avoids bad surprises [13:57] clivejo: Does the Kubuntu team work on the test failures that you get from autopkgtest? [13:57] Or just request to skip all failures? [13:58] we are trying to, however we are seriously underpowered and lacking the people with the necessary knowledge/skills [13:59] At this point, with Qt5.7.1 landing soon, we think its best to skip them [13:59] Fair enough --- I'm just wondering how much value they bring you/us [14:00] 5.28 will be superseded by release time [14:01] well we understand they are important and do intend to fix them before release, but at the moment they are causing a log jam in the entire KDE stack [14:02] For example every Qt upload triggers several hundred KDE tests, all of which rebuild the package (taking a long time), so if they aren't actually used by anyone ... [14:03] lol true story :) [14:03] clivejo: Anyway. Can you provide me with a list of packages that you want to skip? One per line: "force-badtest package/version" [14:03] Might want to wait a little bit for LocutusOfBorg's reruns to come in [14:04] if anyone can see the problems in why the tests are failing please let us know [14:04] we do need to learn :) [14:05] -queuebot:#ubuntu-release- Unapproved: barbican (xenial-proposed/universe) [1:2.0.0-0ubuntu1 => 1:2.0.0-0ubuntu1.1] (openstack) [14:05] Probably requires specific knowledge of the packages being tested [14:05] yes, that is a problem, the KDE stack is huge [14:22] Laney: taking as an example http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#knotifications [14:22] would that be 'force-badtest package/version knotifications' ? [14:23] force-badtest knotifications/5.28.0-0ubuntu1 I mean [14:25] acheronuk: force-badtest is for the actual packages being tested - gwenview, kleopatra, konsole, kparts in this case [14:25] Still, like I say, probably wait a bit for the re-runs [14:26] Laney: aha! thank you [14:28] acheronuk: You can use force-skiptest on the triggering package (knotifications) to skip all the tests under that one [14:28] Which one you want to use depends on why you're trying to skip a test [14:31] Laney: so which in these cases, where we are looking to get these through? [14:32] Can I ask for the diffoscope regression in armhf (against itself) to be ignored?? [14:42] mapreri, is there a reason behind that ? [14:47] apw: That we (diffoscope dev, which includes me, damn) lacks enough tuits to fix it properly, but the error is really harmless; diffoscope works just fine on armhf, only the testsuite is very brittle and and picky on other tools output. [14:50] also, the old version is deemed to block other packages soon, new version fixed compatibility with newer version of tools (for the comparison I said ↑) [14:58] mapreri, done (hopefully) [16:24] apw: Thank you! [16:24] (+ it worked, guess you can now drop the hint too) [16:28] mapreri: the hint is only for that version, see https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/2166 [16:29] ginggs: ack (+ thanks for linking that, I didn't know where they are [16:29] ) [16:33] -queuebot:#ubuntu-release- Unapproved: docker.io (yakkety-proposed/universe) [1.12.3-0ubuntu4~16.10.1 => 1.12.3-0ubuntu4~16.10.2] (no packageset) [16:36] -queuebot:#ubuntu-release- Unapproved: rejected docker.io [source] (yakkety-proposed) [1.12.3-0ubuntu4~16.10.2] [16:38] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (yakkety-proposed) [1.12.3-0ubuntu4~16.10.2] [17:14] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [ppc64el] (zesty-proposed/universe) [0.001-1] (no packageset) [17:15] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [armhf] (zesty-proposed/universe) [0.001-1] (no packageset) [17:16] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [arm64] (zesty-proposed/universe) [0.001-1] (no packageset) [17:18] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [i386] (zesty-proposed/universe) [0.001-1] (no packageset) [17:18] -queuebot:#ubuntu-release- New binary: pyparallel [amd64] (zesty-proposed/universe) [0.2.2-2] (no packageset) [17:18] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [s390x] (zesty-proposed/universe) [0.001-1] (no packageset) [17:18] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [powerpc] (zesty-proposed/universe) [0.001-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: libatteanx-endpoint-perl [amd64] (zesty-proposed/universe) [0.001-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: node-invariant [amd64] (zesty-proposed/universe) [2.2.2-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: libsub-quote-perl [amd64] (zesty-proposed/universe) [2.003001-1] (no packageset) [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [amd64] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [armhf] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [powerpc] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [s390x] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted node-invariant [amd64] (zesty-proposed) [2.2.2-1] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [arm64] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [ppc64el] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted pyparallel [amd64] (zesty-proposed) [0.2.2-2] [17:28] -queuebot:#ubuntu-release- New: accepted libatteanx-endpoint-perl [i386] (zesty-proposed) [0.001-1] [17:28] -queuebot:#ubuntu-release- New: accepted libsub-quote-perl [amd64] (zesty-proposed) [2.003001-1] [17:31] bdmurray, the docker.io SRU exception is not very clear to me, specifically i am assuming from the uploads that it is intended to imply an upstream minor release exception; is that correct ? [17:33] apw: "The aim is to backport the .1 release of a major version to the current LTS" - so yes [17:33] bdmurray, right, i can take that to imply that we can take .2 et al, good [20:31] can someone force-badtest baloo-widgets5/4:16.04.3-0ubuntu1 ? [20:32] as soon as we are able after new QT lands, this will be replaced by KDE applications 16.12 upload anyway [20:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (yakkety-proposed/universe) [0.12+16.10ubuntu1 => 0.13+16.10ubuntu1] (no packageset) [20:43] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (xenial-proposed/universe) [0.12+16.04ubuntu1 => 0.13+16.04ubuntu1] (no packageset) [21:00] acheronuk, done [21:54] Laney, why didn't you ignore why autopkgtestsuite? (affecting why, frama-c migration) /me pun intended [21:57] LocutusOfBorg: may I PM you? [21:59] clivejo, sure [21:59] I'm going to bed BTW [22:00] oh right, I won't bother you then! [22:00] no, feel free to PM [22:03] LocutusOfBorg: see https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/2164 [22:03] I don't know why that didn't work [22:05] interesting [22:12] -queuebot:#ubuntu-release- New binary: golang-1.8 [ppc64el] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:12] i think all/all is not valid syntax, i only see one other occurence of it: force-badtest pbsuite/all/all (p.itti) - and that doesn't work because i recently had to request pbsuite/15.8.24+dfsg-2/i386 (s.tefanor) [22:14] -queuebot:#ubuntu-release- New binary: golang-1.8 [amd64] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:16] -queuebot:#ubuntu-release- New binary: golang-1.8 [i386] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:17] -queuebot:#ubuntu-release- New binary: golang-1.8 [s390x] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:19] can someone force-badtest kio/5.28.0-0ubuntu1 please? [22:32] -queuebot:#ubuntu-release- New binary: golang-1.8 [arm64] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:32] -queuebot:#ubuntu-release- New binary: golang-1.8 [armhf] (zesty-proposed/universe) [1.8~beta2-1ubuntu1] (no packageset) [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [amd64] (zesty-proposed) [1.8~beta2-1ubuntu1] [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [armhf] (zesty-proposed) [1.8~beta2-1ubuntu1] [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [ppc64el] (zesty-proposed) [1.8~beta2-1ubuntu1] [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [arm64] (zesty-proposed) [1.8~beta2-1ubuntu1] [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [s390x] (zesty-proposed) [1.8~beta2-1ubuntu1] [22:35] -queuebot:#ubuntu-release- New: accepted golang-1.8 [i386] (zesty-proposed) [1.8~beta2-1ubuntu1] [23:21] -queuebot:#ubuntu-release- New binary: python-stopit [amd64] (zesty-proposed/universe) [1.1.1-1] (no packageset) [23:25] -queuebot:#ubuntu-release- New binary: pgrouting [amd64] (zesty-proposed/universe) [2.3.2+ds-1] (no packageset) [23:26] -queuebot:#ubuntu-release- New: accepted pgrouting [amd64] (zesty-proposed) [2.3.2+ds-1] [23:26] -queuebot:#ubuntu-release- New: accepted python-stopit [amd64] (zesty-proposed) [1.1.1-1]