dokoLocutusOfBorg, slangasek: a sync is not possible, Ubuntu has jpeg8 compatibility, Debian has jpeg6 compatibility. and libturbojpeg-dev's so was not provided becauses it's a legacy API. At least it was when turbo entered Ubuntu00:29
-queuebot:#ubuntu-release- New binary: golang-github-go-macaron-captcha [amd64] (artful-proposed/universe) [0.0~git20170330.0.cbfb9d9-1] (no packageset)00:38
dokoLocutusOfBorg: and not mentioning bug reports in this upload while you are aware of these and closing manually looks like you try to hide things. not amused00:49
dokoLocutusOfBorg, slangasek: the the README.md in the sources, "Using libjpeg-turbo". I don't see the value providing this, and fear desaster coming when more packages start depending on turbo-dev00:55
dokobut good night for now, 17.10 is not a LTS00:55
-queuebot:#ubuntu-release- New: accepted golang-github-go-macaron-captcha [amd64] (artful-proposed) [0.0~git20170330.0.cbfb9d9-1]00:56
-queuebot:#ubuntu-release- Unapproved: gnutls26 (trusty-proposed/main) [2.12.23-12ubuntu2.9 => 2.12.23-12ubuntu2.10] (core)06:13
LocutusOfBorgdoko, I saw them because jbicha pinged me *after* not before of course06:21
LocutusOfBorgI woudl have closed bugs in changelog, of course! and it is not my fault that Debian started using it :( do you want to help me patching dcm2niix=06:22
LocutusOfBorgI would  like to at least sync the packages with a minimal delta, same package names, ok for the jpeg6/jpeg8, but the current status quo is a mess, a double mess06:22
LocutusOfBorgI put it in queue 12h before noticing the bugs06:23
LocutusOfBorgbtw you can't avoid people doing bad symlinks on their systems to use it anyway, not providing a -dev package is not helping, but rather making people do nasty hacks :(06:24
LocutusOfBorgthe package uses functions such as tjDecompressHeader2, provided only by that library06:29
LocutusOfBorgnot really sure how can we avoid that06:29
-queuebot:#ubuntu-release- Unapproved: virt-manager (xenial-proposed/universe) [1:1.3.2-3ubuntu1.16.04.3 => 1:1.3.2-3ubuntu1.16.04.4] (no packageset)07:13
-queuebot:#ubuntu-release- Unapproved: virt-manager (zesty-proposed/universe) [1:1.3.2-3ubuntu4 => 1:1.3.2-3ubuntu6] (no packageset)08:34
cpaelzercould one please reject the shameful mistake of version number increase in zesty-unapproved being virt-manager 1:1.3.2-3ubuntu6?08:40
apwcpaelzer, looking08:50
-queuebot:#ubuntu-release- Unapproved: rejected virt-manager [source] (zesty-proposed) [1:1.3.2-3ubuntu6]08:51
LocutusOfBorghello, the following packages have been regressed in release casync/i386 pycurl/ppc64el r-cran-curl/ppc64el xandikos/amd64/i386 and are preventing curl migration08:52
LocutusOfBorgalso s390x might be sad, but it is not ran yet, maybe Laney knows an ETA for having it back online08:52
cpaelzerthanks apw08:53
LaneyIt's being investigated.08:54
-queuebot:#ubuntu-release- Unapproved: virt-manager (zesty-proposed/universe) [1:1.3.2-3ubuntu4 => 1:1.3.2-3ubuntu4.1] (no packageset)08:54
LocutusOfBorgplease accept the new llvm "lld" package, it is the linker, and has its new package since the default llvm in yakkety/zesty/artful08:59
LocutusOfBorgjust we were missing the metapackage from llvm-defaults08:59
apwLocutusOfBorg, where is that i don't see anything resembling that pending anywhere09:01
LocutusOfBorgit is just building09:01
LocutusOfBorgok finished now09:01
-queuebot:#ubuntu-release- New binary: llvm-defaults [amd64] (artful-proposed/universe) [0.37~exp3] (no packageset)09:02
LocutusOfBorghopefully having a new linker might help :)09:02
-queuebot:#ubuntu-release- New binary: llvm-defaults [arm64] (artful-proposed/universe) [0.37~exp3] (no packageset)09:03
-queuebot:#ubuntu-release- New binary: llvm-defaults [i386] (artful-proposed/universe) [0.37~exp3] (no packageset)09:03
-queuebot:#ubuntu-release- New binary: llvm-defaults [armhf] (artful-proposed/universe) [0.37~exp3] (no packageset)09:04
LocutusOfBorgsadly it still don't work on ppc64el and s390x... but meh, at least it is now in sync with debian experimental09:04
=== santa is now known as Guest88511
sil2100apw: hey, I have a new walinuxagent to be released, the package is not seeded and cloud-up-to-date essential - I guess I can push it to artful without a FFE, right?09:21
sil2100(by cloud-up-to-date essential I mean we always need to keep it up to date)09:21
apwsil2100, that one has an SRU exception for that reason doesn't it, so it seems reasonable it would something we can update yes09:36
sil2100apw: yeah, SRU exception it has, but I just wanted to make sure it also counts as a FF exception for the devel series09:37
apwsil2100, it seems reasonable to count it to me for all the reasons it is reasonable in stable09:37
LocutusOfBorgthanks Laney for having a look!09:47
LaneyLocutusOfBorg: Back up10:09
LocutusOfBorgthanks for the work!10:53
=== santa is now known as Guest19413
cpaelzerhi, does an FFE like https://bugs.launchpad.net/ubuntu/+source/slof/+bug/1706248 need any further pings/mails to be reviewed or is just a lot goging on atm delaying that?12:09
ubot5Ubuntu bug 1706248 in slof (Ubuntu) "[FFE] SLOF dhcp request doesn't include client architecture code 93" [Medium,Confirmed]12:09
flocculantcpaelzer: thanks for finding that virt-manager issue - I've been scratching my head for a couple of weeks :)12:24
cpaelzerflocculant: which one actually :-)12:28
cpaelzerflocculant: I happen to hack on a few the recent days12:28
flocculantbug 171463812:29
ubot5bug 1711358 in ubiquity (Ubuntu) "duplicate for #1714638 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver" [Undecided,Confirmed] https://launchpad.net/bugs/171135812:29
cpaelzerah yeah, well I only came from another bug report12:29
cpaelzerwas verifying what it is about and finally linked to the already existing issue report12:29
flocculantyup - but you did more than me - you found the dup :D12:29
=== santa is now known as Guest56020
-queuebot:#ubuntu-release- Unapproved: walinuxagent (trusty-proposed/main) [2.2.14-0ubuntu1~14.04.1 => 2.2.16-0ubuntu1~14.04.1] (ubuntu-cloud, ubuntu-server)13:12
-queuebot:#ubuntu-release- Unapproved: walinuxagent (zesty-proposed/main) [2.2.14-0ubuntu1~17.04.1 => 2.2.16-0ubuntu1~17.04.1] (ubuntu-cloud, ubuntu-server)13:12
-queuebot:#ubuntu-release- Unapproved: walinuxagent (xenial-proposed/main) [2.2.14-0ubuntu1~16.04.1 => 2.2.16-0ubuntu1~16.04.1] (ubuntu-cloud, ubuntu-server)13:12
=== Guest56020 is now known as santa_
rbalintLaney: could you please check if LP: #1714019 needs FFe and if it does tell what is missing? slangasek can't follow up on this soon13:16
ubot5Launchpad bug 1714019 in unattended-upgrades (Ubuntu) "Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/171401913:16
-queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (zesty-proposed) [2.2.16-0ubuntu1~17.04.1]13:22
-queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (xenial-proposed) [2.2.16-0ubuntu1~16.04.1]13:23
-queuebot:#ubuntu-release- Unapproved: accepted walinuxagent [source] (trusty-proposed) [2.2.16-0ubuntu1~14.04.1]13:24
apwrbalint, do you feel that unattended-upgrades has any new features ?13:27
apwrbalint, the changelog looks like all fixes perhap with the exclusion of the new --download-only13:27
rbalintapw: thanks for the review13:28
apwrbalint, oh and we have that fix in our ubunut8 as a backport, so ignore that13:28
rbalintapw: there are no features, but there are minimal changes which are not strictly bug fixes13:28
apwrbalint, there does not appear to be anything there which would be concerning from a "changing behaviour" point of view, it looks to be mostly fixes, some cleanup of formatting but meh13:29
rbalintapw: there is also default behavior change (longer timeout, minimal steps by default) but those are needed to fix real life issues IMO13:29
apwif theey are being changed to fix bugs without the change, then that is a bug-fix none the less13:30
rbalintapw: i'm perfectly fine with not needing FFe, i felt it was better to ask and have release team take a look at the changes13:30
apwrbalint, i don't see anything in there warrenting it .. so i'd say you are good13:31
rbalintapw: ok thanks!13:32
juliankI uploaded gnutls28 on saturday, but it seems the autopkgtest for lxc on amd64, i386, ppc64el are borked _since some time_ and blocking the migration out of -proposed.14:15
juliankwould be great to ignore those failures and allow it in14:15
juliank(BTW: there's also an SRU in the zesty unapproved queue with the same patches; bug 1707172 and bug 1714506 are being fixed)14:16
ubot5bug 1707172 in gnutls28 (Ubuntu Zesty) "AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration" [High,In progress] https://launchpad.net/bugs/170717214:16
ubot5bug 1714506 in gnutls28 (Ubuntu Zesty) "libgnutls30 OCSP verification bug" [High,In progress] https://launchpad.net/bugs/171450614:16
=== santa is now known as Guest46152
-queuebot:#ubuntu-release- New: accepted llvm-defaults [amd64] (artful-proposed) [0.37~exp3]14:18
-queuebot:#ubuntu-release- New: accepted llvm-defaults [armhf] (artful-proposed) [0.37~exp3]14:18
-queuebot:#ubuntu-release- New: accepted llvm-defaults [arm64] (artful-proposed) [0.37~exp3]14:18
-queuebot:#ubuntu-release- New: accepted llvm-defaults [i386] (artful-proposed) [0.37~exp3]14:18
apwjuliank, indeed those look unreleased to you for sure14:19
apwjuliank, ok hinted14:23
juliankapw: thanks14:24
LocutusOfBorgapw, the same happens on curl, all of them are regressed in release14:24
LaneyI hate this regressed in release thing14:25
LaneyIt means people spend time finding out whether not to fix something rather than fixing it14:25
Laneybecause we suck at catching failures at the right time14:25
apwa very valid sentiment ...14:26
LocutusOfBorgas said, such stuff shoudl run from time to time already against release14:26
LocutusOfBorgspecially when queues are emptu14:26
LocutusOfBorgtests for some packages are run once a yer14:26
Laneyso we can find out whether to ignore breakage in an automated way?14:26
LocutusOfBorgyear, so when you regress you have the world that changed in the meanwhile14:26
jbichaci.debian.net runs more frequently14:27
LocutusOfBorgI would prefer rather to know "which" package regressed it, not to find it with a complete different set of stuff14:27
apwLaney, i assume this is happening because we have either 1) ignored some other failure and released (say systemd with regressions) or 2) we have a missing dependency here14:28
apwLaney, perhap netplan given the networking nature14:29
Laneycould be - or something in the base system changed, or we only run for direct dependency changes so we miss anything transitive14:29
Laneyanyway, the main problem I have is accepting an ever worsening baseline14:30
LocutusOfBorg"so we can find out whether to ignore breakage in an automated way?" <-- I still don't get if this was a joke or not :) I admit, in my brain I had this thought, but I never said it out there14:31
Laneythat's what the proposal is14:31
LocutusOfBorgnot from my side I hope :)14:32
LocutusOfBorgit will make testsuite useless14:32
Laneywhat is 'run against release' meant to achieve then?14:32
LocutusOfBorgor at least useless when the breakage is something else14:32
LocutusOfBorgit is meant to have more logs, more runs14:32
Laneyyou want to run against nothing from proposed, find out if it is already broken there, and if it is then don't treat the failure as a regression14:32
LocutusOfBorgand less changed packages between them14:32
Laneythat is what requests like the curl one is14:32
LocutusOfBorgthis is what I did for curl14:33
LocutusOfBorgbut ok, I found release is broken, now, with some more test, I can diff the testbeds, and find "what" regressed it14:33
LaneyIn theory I wouldn't mind if someone were to schedule such tests if they were friendly to the infrastructure14:34
LocutusOfBorgof course, with less priority14:35
Laneyusing this to decide when to force-badtest, or changing the definition of REGRESSION, is where I start to have problems14:35
LocutusOfBorgalso, having somebody running tests (results ignored), with --all-proposed would be nice14:35
Laneybut if people on the release team want to do the former then I can't really stop them14:35
Laneythere's no way to ignore results like that14:36
LocutusOfBorgI sometimes run against all-proposed, but I don't like to have the green button as result in case14:36
LocutusOfBorgso, if it becomes green, I try to make migrate the fixex package from proposed too14:36
LocutusOfBorgbut again, choosing one architecture (e.g. arm64) to always run against proposed, will make us have a clear view of what regressed and where, and if a fix is already in place, just not migrated14:37
LocutusOfBorg(e.g. with k* qt* haskell* perl* this is normal)14:37
LaneyI don't think it's normal with perl14:37
Laneyor with haskell? they have correct dependencies14:37
LocutusOfBorgyes, perl testsuites should run against perl in proposed, if you rebuild14:38
LocutusOfBorgnope Laney14:38
Laneythey sure do14:38
LocutusOfBorgthey are just uninstallable in release, because all the rebuilds are in proposed14:38
LocutusOfBorgI think I remember haskell-hoogle having this issue14:38
Laneyyou're not trying to migrate the release thing14:38
LocutusOfBorgI don't know what to say, I remember with perl slangasek did the --all-proposed stuff, because of this issue14:39
LocutusOfBorg(maybe it was somebody else, but the problem was there)14:39
Laneywith haskell, I don't know what the specific problem with perl was14:39
LocutusOfBorgis that you rebuild 500 packages, and they are installable only with the correspective rebuilds14:40
LocutusOfBorgthere is no strict dependency I would assume, don't remember14:40
Laneythe haskell tooling makes you depend on the hash14:40
Laneyif you're saying that doesn't happen for Test-Depends, well, it should :)14:40
LocutusOfBorglook as example at the first failure14:41
apwLaney, i wonder if we should upload a no-change rebuild of things which fail in this way so they get wedged in -proposed and emails sent to the owners14:42
LocutusOfBorgindeed, or put the test in some "depwait" mode14:43
LocutusOfBorgso we can aware that the regression is just because the archive is not yet fully in place14:43
Laneythe first failure is an all-proposed run14:43
Laneyand 2, 3, 4, and I get bored now and stop looking14:43
Laneyhttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/h/haskell-hgettext/20170715_153508_199d7@/log.gz these ones that weren't all-proposed worked14:44
LocutusOfBorgthis one? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/h/haskell-hgettext/20170622_040119_7b95b@/log.gz14:46
LocutusOfBorgthe first failure14:46
LocutusOfBorg(the oldest)14:46
LocutusOfBorgso, maybe rebuilds were not complete then?14:47
Laneyautopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from proposed14:47
Laneyand it still didn't work14:47
Laneyso I don't blame pinning14:47
LocutusOfBorgbut having a "testbed unsatisfiable status" would have helped at least14:48
LocutusOfBorgI now agree with you14:48
LocutusOfBorg(I was just not aware of that pinning feature)14:48
LaneyI wouldn't look forward to implementing that particularly :(14:53
Laneyapw: Maybe, but the proposal I've heard is to make such things *not* get stuck because they wouldn't be regressions in proposed14:53
Laneyalso, things don't always have owners14:53
Laneydid anyone file a bug about the lxc regression so that its maintainers can look? :-)14:53
LocutusOfBorgit would be somewhat fixed if britney in Debian would have start to looking at ci too :D14:54
ubot5Ubuntu bug 1713726 in lxc (Ubuntu) "lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8" [Undecided,New]14:54
acheronukLocutusOfBorg: those kcrash tests should be ignored, as they pass here against the archive in a lxc adt containers. so something has gone a bit funky in the official ubuntu ones15:06
LocutusOfBorgs/should be ignored/ubuntu official adt containers should be fixed/ I would say :)15:09
LocutusOfBorgat least diverging makes local testing less effective15:09
apwLaney, yeah we tend to file bugs for everything we see in failure even if we ignore them, so they are not forgotten15:35
LocutusOfBorgfiling bugs for stuff in universe is... strange15:39
apwLocutusOfBorg, why so?  just becasue we don't want to support things doesn't mean they arn't broken16:00
LocutusOfBorgapw, yes, but not many looks at universe bugs, unfortunately16:09
LocutusOfBorg(I do, but I feel alone)16:09
=== tumbleweed_ is now known as tumbleweed
=== tdaitx_ is now known as tdaitx
LocutusOfBorgsorry, please remove lld/arm64, it was built but not available from llvm-toolchain-4.018:39
LocutusOfBorgold binaries left on arm64: lld (from 0.37~exp3) (NBS-proposed remove it)18:39
=== Kamilion|ZNC is now known as Kamilion
flexiondotorgdoko: I see caja-admin and caja-rename are in the Artful NEW.19:06
flexiondotorgThey took longer than expected to clear the Debian NEW queue, but we are hotly anticpating them for Ubuntu MATE.19:07
flexiondotorgCould you allow them through please.19:07
Laneyjbicha: http://autopkgtest.ubuntu.com/packages/e/evolution-data-server/artful/i386 http://autopkgtest.ubuntu.com/packages/e/evolution-data-server/artful/s390x were all of these you?20:17
jbichaLaney: yes, the probably is that e-d-s is now running the installed-tests, I expected them to be flaky so I'll probably disable them in my next upload20:18
jbicha*the problem20:18
Laney4 retries (5 attempts) is probably a bit much20:19
jbichaI now have data to show to upstream at least20:19
jbichaLaney: are you interested in ignoring the tests for this version to let e-d-s migrate?20:21
slangaseknacc: your sphinx-celery upload was binary rejected, but the source is still in -proposed; should we be expecting another upload, or should I just remove the corresponding source? https://launchpad.net/ubuntu/+source/sphinx-celery/1.3.1-1ubuntu121:02
tsimonq2Could an archive admin please look at ubuntu-mate-guide in NEW when they can?21:22
flexiondotorgCould an archive admin please look at caja-admin and caja-rename in NEW when they can?21:50

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