/srv/irclogs.ubuntu.com/2017/02/19/#ubuntu-release.txt

-queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Zesty Beta 1] has been updated (20170219)02:23
-queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Zesty Beta 1] has been updated (20170219)02:23
-queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Zesty Beta 1] has been updated (20170219)05:52
-queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Zesty Beta 1] has been updated (20170219)05:52
-queuebot:#ubuntu-release- New binary: gocryptfs [amd64] (zesty-proposed/universe) [1.2-2ubuntu1] (no packageset)06:01
-queuebot:#ubuntu-release- New binary: gocryptfs [i386] (zesty-proposed/universe) [1.2-2ubuntu1] (no packageset)06:01
-queuebot:#ubuntu-release- New binary: gocryptfs [armhf] (zesty-proposed/universe) [1.2-2ubuntu1] (no packageset)06:02
-queuebot:#ubuntu-release- New binary: gocryptfs [s390x] (zesty-proposed/universe) [1.2-2ubuntu1] (no packageset)06:05
-queuebot:#ubuntu-release- New: rejected nut [amd64] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: rejected nut [armhf] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: rejected nut [powerpc] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: rejected nut [arm64] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: rejected nut [s390x] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: rejected nut [i386] (zesty-proposed) [2.7.4-5ubuntu1]11:34
-queuebot:#ubuntu-release- New: accepted nut [amd64] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [armhf] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [powerpc] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [s390x] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [arm64] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [ppc64el] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted nut [i386] (zesty-proposed) [2.7.4-5ubuntu2]11:36
-queuebot:#ubuntu-release- New: accepted gocryptfs [amd64] (zesty-proposed) [1.2-2ubuntu1]11:37
-queuebot:#ubuntu-release- New: accepted gocryptfs [i386] (zesty-proposed) [1.2-2ubuntu1]11:37
-queuebot:#ubuntu-release- New: accepted gocryptfs [armhf] (zesty-proposed) [1.2-2ubuntu1]11:37
-queuebot:#ubuntu-release- New: accepted gocryptfs [s390x] (zesty-proposed) [1.2-2ubuntu1]11:37
-queuebot:#ubuntu-release- New binary: x265 [i386] (zesty-proposed/universe) [2.3-1] (kubuntu)13:03
-queuebot:#ubuntu-release- New binary: x265 [s390x] (zesty-proposed/universe) [2.3-1] (kubuntu)13:03
-queuebot:#ubuntu-release- New binary: x265 [powerpc] (zesty-proposed/universe) [2.3-1] (kubuntu)13:03
-queuebot:#ubuntu-release- New binary: x265 [arm64] (zesty-proposed/universe) [2.3-1] (kubuntu)13:04
-queuebot:#ubuntu-release- New binary: x265 [ppc64el] (zesty-proposed/universe) [2.3-1] (kubuntu)13:04
-queuebot:#ubuntu-release- New binary: x265 [armhf] (zesty-proposed/universe) [2.3-1] (kubuntu)13:04
-queuebot:#ubuntu-release- New binary: x265 [amd64] (zesty-proposed/universe) [2.3-1] (kubuntu)13:08
-queuebot:#ubuntu-release- New: accepted x265 [amd64] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [armhf] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [powerpc] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [s390x] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [arm64] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [ppc64el] (zesty-proposed) [2.3-1]14:17
-queuebot:#ubuntu-release- New: accepted x265 [i386] (zesty-proposed) [2.3-1]14:17
santa_good afternoon release wizards14:51
santa_we have a problem right now with gpgme blocking the migration of most kubuntu's packaging out of -proposed14:52
santa_gpgme is making another package FTBFS with -proposed enabled14:53
santa_therefore that is making many autopkgtests fail14:53
santa_we proposed a fix for this here https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/comments/4414:54
ubot5Ubuntu bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [Undecided,Confirmed]14:54
santa_but we would need an upload of this fix (we don't have any active motu on the team unfortunately)14:54
santa_so if you could help us with this particular issue, that would be terrific. thanks in advance14:55
clivejoapw: would you be able to help on the above? ^14:57
maprerisanta_: gpgme1.0 is in main, so you'd need a core-dev, not a motu (so I can't help)14:59
santa_mapreri: oh, thanks for the clarification. I still need to get more familiar with ubuntu's "bureaucracy" :)15:01
clivejohttps://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/164720415:02
ubot5Ubuntu bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [Undecided,Confirmed]15:02
clivejoshould we sub the sponsor team again?15:02
mapreriit's already subscribed15:02
maprerilet me ask dkg if he'd upload that to debian15:03
apwis the whole change the reduction in the thread count from 100 to 10 in those two tests ?  that feels like a rather arbitrary fix without context.15:05
apwwhat is the symptoms when it is at 100 ?15:05
maprerilaunchpad-buildd hangs.15:06
santa_apw: it doesn't build, let me dig a bit, to see if I can find the specific failure...15:06
santa_apw: https://irclogs.ubuntu.com/2017/02/18/%23kubuntu-devel.html#t20:0215:07
apwsanta_, the patch implies but does not elucidate that you have confirmed that the failure it finds is not the intended failure mode tested but some other factor15:07
apwsanta_, ok that does tell me more what i wanted to know15:08
apwit would be good if the patch said that we run out of memory in a fork-storm15:08
jbichayes, I subscribed ~ubuntu-sponsors to that bug several hours ago15:08
clivejothanks jbicha15:08
jbichahave the Ubuntu Qt maintainers seen this bug? that QtCore error seemed odd15:11
maprerisanta_: from dkg (gpg* maintainer in Debian): https://paste.debian.net/plain/91555815:50
mapreri(guess it's a FYI)15:51
-queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Zesty Beta 1] has been updated (20170219)16:00
-queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Zesty Beta 1] has been updated (20170219)16:00
apwmapreri, santa_, that osunds liek the symlink makes no sense ...16:31
santa_we could try to patch the kde package which is failing to build instead16:33
clivejoapw: how should it be done?16:33
santa_in any case that is meant to be a temporary thing to be droped later16:33
apwsanta_, it sounds like that is essentially a transition for the consumers of that library, if that change is dev library is expected16:33
clivejoits a bit of a vicious circle16:35
clivejokf5-kdepim-apps-libs is the package that needs it16:37
apwclivejo, well that is only a build-time depedency and we are uploading this to free built-binaries16:37
apwclivejo, so why does it need that.  and if we are having to rebuild _that_ anyhow, it would be just as easy to fix it, in theory16:37
clivejoKDE PIM16:38
apw* libkf5gpgmepp-dev             (for libgpgme11-dev)16:38
apwthat is the only reverse-depends right?16:38
clivejohuge beast of a thing and not having a working gpgme has lead to us having to hold it back for now16:38
apwclivejo, will someone get round to fixing the reverse-depends if i let you bodge this, and remember to remove the bodge16:39
clivejoIf I recall kf5-kdepim-apps-libs is split out into new packages16:40
apwoh gawd16:41
apwsomeone on your side like to make your life hard16:41
clivejooh yes16:41
clivejoremember that list of new packages I told you about?16:41
clivejoapprox 20 new packages for PIM16:42
apwi guess now you have lots of FFEs to file too16:42
clivejobut its either an all or nothing16:43
clivejoso far we have held back the PIM packages to 16.04 and its deps16:45
apwok i'll look at this patch and perhaps mark that patch for not carrying forward in the next merge16:46
apwso you have to do something about it then :)16:46
clivejocan you hold back on it a sec16:46
* apw stops16:47
clivejowould you be willing to force kf5-kdepim-apps-libs tests?16:47
clivejowould the release team work with us to ensure the new packages are accepted and get in?16:49
apwi assume if they ahve been accepted for the release (as in FFE or whatever equivalent it needed)16:49
apwthen i assume we would work with you to get them in16:49
clivejowho would make that decision?16:50
apwwell at this stage i assume a big pile of updates would need an FFE, so that would be the place16:50
apwto ahve the discussion.  i am assuming that if KDE wants KDE to be specific thing, and are committing16:51
apwthe effort to get it done, then it would get approved.  but i don't think i should make that decision on my own16:51
clivejowell these are all the latest KDE Apps 16.1216:51
apwso right now we have half of KDE as 16.12 and half as 16.04, which sounds like a bad idea from a support16:52
clivejobut as we had problems with gpgme and 20+ new packages to get in, we have been holding off16:52
apwpoint of view... and i assume it is that you would be asking to correct16:52
clivejoour aim is to get everything to 16.1216:53
apwand that sounds like a laudible and sensible plan to me, so would likely get my vote16:53
clivejobut with PIM deps, one part of it not working, can bring the entire stack down16:54
apwpresumably that is an argument for it being in sync version wise16:54
santa_I think we could do it16:55
santa_but we need to get the NEW packages accepted16:55
santa_right now we have good resources to update all of this16:55
apwright the point of the FFE would be commiting both sides to it16:56
clivejowe have no MOTU's on our team at the moment, and found it very difficult to get previous NEW packages accpted16:56
apwclivejo, yep, someone would likely be voluntold to help with New reviews16:57
clivejoso for the FFE, we would open it against something high up in that stack, like Kontact?16:58
santa_apw: ok, I think the thing is doable in our side; what we can offer is 1. packages not ftbfsing, 2. most autopkgtests passing in amd64/i38617:00
santa_about the autopkgtests I would expect a little bit of mercy on some things17:00
clivejoesp on weird arch's!17:00
apwclivejo, nominally on all packages you want to update (obviously not on the ones which do not exist) so perhaps the one you are splitting or something17:00
clivejomost exist already, just split from source package17:03
clivejohttp://paste.ubuntu.com/24027977/17:03
clivejoapw: that would take forever, PIM has a lot of packages17:05
clivejoin the past we have selected one top tier package and opened an FFE for that to cover all the packages below17:05
apwclivejo, do what you did before indeed; get all that information in the FFE and do send me the bug number where you get that17:06
clivejothis is an example of Frameworks FFE - https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/162539217:06
ubot5Ubuntu bug 1625392 in plasma-desktop (Ubuntu) "[FFe] KDE Frameworks 5.26.0 into the Yakkety Archive" [Undecided,Fix released]17:06
apwclivejo, whatever worked last time, do that17:06
clivejoapw: is it possible to hold the entire packageset in proposed until we are happy everything is working as it should?17:08
apwclivejo, we can cirtainly block things in -proposed17:08
clivejobut like 50 odd packages?17:08
clivejoapw: could you force-bad-tests kf5-kdepim-apps-libs for the time being?17:13
clivejoits holding back 5 key frameworks from migrating17:16
apwclivejo, if you make me a list of what you want held, it can be held17:17
apwif there are some key libraries tha the remainder dep on we can hold those, and the rest get help as a result17:17
clivejook, its more a thought at the moment17:17
clivejowe know that KDE PIM 16.04 is working and is tested very well17:18
clivejo16.12 I know amd64 is working great, but we would need feedback for other arch17:19
santa_I would like to note that we still have some problems with some archs17:22
santa_http://gpul.grupos.udc.es/ka-iron-hand_reports/applications_staging/16.12.1_zesty_retry_builds.pdf17:22
santa_we will work on it17:23
santa_we also have a private wannabuild/buildd infrastructure to check the autopkgtests17:23
apwclivejo, ok that ADT failure is triggered by the fact the tests mandate a rebuild, which we know will fail17:24
apwclivejo, so i think we can badtest that reasonable.17:25
clivejothanks17:26
santa_apw: thank you very much, we are going to work on kde applications issues on our side17:35
valorieHi folks, I was just setting up torrents for seeding 16.04.2 and I see that Lubuntu i386 seems to be missing here: http://torrent.ubuntu.com:6969/23:48
valorieI checked and it is marked ready, and was reported as such here in the chan23:48
valorieinfinity: ^^^23:48

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