/srv/irclogs.ubuntu.com/2018/05/10/#ubuntu-release.txt

-queuebot:#ubuntu-release- New binary: openmpi [arm64] (cosmic-proposed/universe) [3.0.1.real-4] (kubuntu)00:08
-queuebot:#ubuntu-release- New binary: openmpi [armhf] (cosmic-proposed/universe) [3.0.1.real-4] (kubuntu)00:12
-queuebot:#ubuntu-release- New binary: openmpi [amd64] (cosmic-proposed/universe) [3.0.1.real-4] (kubuntu)00:29
-queuebot:#ubuntu-release- New: accepted openmpi [amd64] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New: accepted openmpi [armhf] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New: accepted openmpi [ppc64el] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New: accepted openmpi [arm64] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New: accepted openmpi [s390x] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New: accepted openmpi [i386] (cosmic-proposed) [3.0.1.real-4]01:08
-queuebot:#ubuntu-release- New binary: clipper [s390x] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:24
-queuebot:#ubuntu-release- New binary: clipper [ppc64el] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:25
-queuebot:#ubuntu-release- New binary: clipper [amd64] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:26
-queuebot:#ubuntu-release- New binary: clipper [i386] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:26
-queuebot:#ubuntu-release- New binary: clipper [arm64] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:29
-queuebot:#ubuntu-release- New binary: clipper [armhf] (cosmic-proposed/universe) [2.1.20160809-1] (no packageset)03:29
-queuebot:#ubuntu-release- New binary: weechat [s390x] (cosmic-proposed/universe) [2.1-2] (no packageset)03:39
-queuebot:#ubuntu-release- New binary: weechat [i386] (cosmic-proposed/universe) [2.1-2] (no packageset)03:40
-queuebot:#ubuntu-release- New binary: weechat [ppc64el] (cosmic-proposed/universe) [2.1-2] (no packageset)03:40
-queuebot:#ubuntu-release- New binary: weechat [amd64] (cosmic-proposed/universe) [2.1-2] (no packageset)03:41
-queuebot:#ubuntu-release- New binary: weechat [armhf] (cosmic-proposed/universe) [2.1-2] (no packageset)03:42
-queuebot:#ubuntu-release- New binary: weechat [arm64] (cosmic-proposed/universe) [2.1-2] (no packageset)03:43
=== tacobat` is now known as tacobat
-queuebot:#ubuntu-release- New: accepted clipper [amd64] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted clipper [armhf] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted clipper [ppc64el] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted weechat [amd64] (cosmic-proposed) [2.1-2]07:36
-queuebot:#ubuntu-release- New: accepted weechat [armhf] (cosmic-proposed) [2.1-2]07:36
-queuebot:#ubuntu-release- New: accepted weechat [ppc64el] (cosmic-proposed) [2.1-2]07:36
-queuebot:#ubuntu-release- New: accepted clipper [arm64] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted clipper [s390x] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted weechat [i386] (cosmic-proposed) [2.1-2]07:36
-queuebot:#ubuntu-release- New: accepted clipper [i386] (cosmic-proposed) [2.1.20160809-1]07:36
-queuebot:#ubuntu-release- New: accepted weechat [s390x] (cosmic-proposed) [2.1-2]07:36
-queuebot:#ubuntu-release- New: accepted weechat [arm64] (cosmic-proposed) [2.1-2]07:36
Laneyjuliank: nice08:05
LocutusOfBorgRelease Team, the Debian haskell transition should be mostly over, and I would like to drop llvm 3.7 from our world...08:11
LocutusOfBorgcan you please tell me when it is convenient to do my manual syncs? (please don't whitelist it right now, I prefer to sync in the right order to avoid useless rebuilds and infra time)08:12
Laneyjuliank: fixed the image script too08:40
juliankLaney: nice08:45
Laneycopied sil2100's email typo again :D09:26
-queuebot:#ubuntu-release- Unapproved: debhelper (bionic-proposed/main) [11.1.6ubuntu1 => 11.1.6ubuntu2] (core)09:34
sil2100E-mail typo?09:52
sil2100Which one ;p?09:52
* sil2100 does a lot of typos09:52
-queuebot:#ubuntu-release- Unapproved: accepted debhelper [source] (bionic-proposed) [11.1.6ubuntu2]09:54
Laneysil2100: I typoed your email address in a ticket the other day09:57
Laneyand then juliank copied and pasted that09:57
Laneyand today I just copied it again09:57
Laney/o\09:57
apwLaney, if that is the worst thing that happens today, you should grab it with both hands09:58
Laneyhaha09:59
Laneyapw feeling particularly upbeat today09:59
juliankapw: at least all those pesky germans have a holiday today, so no trouble from that country...09:59
apwjuliank, always on the day you need one of course ...10:00
Laneygetting good service on my SRUs10:01
Laneyhigh five to the team!10:01
* juliank doesn't really feel like holiday today10:01
apwLaney, that is because you make them small and easy to review :)10:01
LaneyNiels pinged me and said "take this commit plz"10:01
Laneyit was easy through and through10:01
apwLocutusOfBorg, in bionic we have a sync of virtualbox-ext-pack at 5.2.10-4 and an upload (after that) at 5.2.10-3ubuntu18.04.1 -- i assume you only want the latter ?10:03
Laneycan you do syncs as SRUs?10:05
Laneyif the dsc has LP-Bugs-Fixed maybe?10:05
Laneys/dsc/changes/ but then it won't have one...10:05
apwyou can technically, they tend to make people very sad; they would be a sync-from-ppa in that case often10:06
LocutusOfBorgapw, I would appreciate the sync, but if infra/policy disallows that, SRU versioning is fine10:32
LocutusOfBorgthey are technically the same10:32
apwLocutusOfBorg, oh that version hit cosmic already, so that makes the answer simple10:42
-queuebot:#ubuntu-release- Unapproved: rejected virtualbox-ext-pack [sync] (bionic-proposed) [5.2.10-4]10:49
ddstreetsil2100 i uploaded t/x/a for lp #1701023, if you have time to review/approve them, then we can let that sit in -proposed for enough time to get it widely tested11:22
ubot5Launchpad bug 1701023 in vlan (Ubuntu Artful) "(on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion" [High,In progress] https://launchpad.net/bugs/170102311:22
-queuebot:#ubuntu-release- New binary: faumachine [amd64] (cosmic-proposed/none) [20180503-1] (no packageset)11:34
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-148.197] (core, kernel)11:58
ahasenackhi, should we mark the dovecot dep8 armhf tests as flaky, https://autopkgtest.ubuntu.com/packages/dovecot/cosmic/armhf, or cam someone hand me an armhf box to further debug this?12:35
LocutusOfBorgapw, since this is a downloader, a copy-back of the binary from cosmic to bionic works too :)12:37
LocutusOfBorgit is binary identical I would say12:37
LocutusOfBorganyhow, let me know what is your best way12:37
LocutusOfBorgin the meanwhile the new vbox is out, so cosmic will have an higher version in 12h12:38
enycLocutusOfBorg: all virtualbox versions will be harmonized, resistance is futile????12:50
LocutusOfBorgenyc, you will be assimilated.12:51
* enyc thwarts LocutusOfBorg with a fatal memory protection violation12:51
enycLast I checked, virtualbox 5.1 was being a pain, audio/microphone nonsense, etc etc...12:52
* LocutusOfBorg borg have improved their NPE handling, after assimilating M$12:52
enycmaye thats' all fine now in -5.1, and its' now virtualbox-5.2 being a pain12:52
LocutusOfBorgwho knows? :)12:53
LocutusOfBorgseriously, it should be work correctly now12:53
slashdo/ sil2100, could you please approve the bionic upload of 'ubiquity' for LP: #1751252, if you have a moment ?12:58
ubot5Launchpad bug 1751252 in ubiquity (Ubuntu Bionic) "[regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''" [High,In progress] https://launchpad.net/bugs/175125212:58
sil2100slashd: hey! Sure13:27
slashdsil2100, thanks13:29
-queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.1]13:32
ddstreetsil2100 o/ if you have time could you review/approve the t/x/a uploads for lp #170102313:56
ubot5Launchpad bug 1701023 in vlan (Ubuntu Artful) "(on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion" [High,In progress] https://launchpad.net/bugs/170102313:56
sil2100ddstreet: on it! Will just finish this one pyvmomi13:58
ddstreetthnx!13:58
-queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (artful-proposed) [1.9-3.2ubuntu5.17.10.1]14:12
-queuebot:#ubuntu-release- Unapproved: accepted ifupdown [source] (artful-proposed) [0.8.16ubuntu2.1]14:17
-queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (xenial-proposed) [1.9-3.2ubuntu1.16.04.5]14:19
-queuebot:#ubuntu-release- Unapproved: accepted ifupdown [source] (xenial-proposed) [0.8.10ubuntu1.4]14:21
-queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (trusty-proposed) [1.9-3ubuntu10.6]14:23
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-148.197]14:24
-queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.13.0-42.47~16.04.1] (kernel)14:46
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (artful-proposed/main) [4.13.0-42.47] (core, kernel)14:47
-queuebot:#ubuntu-release- Unapproved: accepted ifupdown [source] (trusty-proposed) [0.7.47.2ubuntu4.5]15:04
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (artful-proposed) [4.13.0-42.47]15:19
-queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.13.0-42.47~16.04.1]15:20
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.15.0-1011.11] (kernel)16:44
-queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.13.0-1017.20] (no packageset)16:45
-queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-125.150] (core, kernel)16:49
bdmurraycyphermox: Do you think bug 1437353 has been verified?16:50
ubot5bug 1437353 in maas-images "UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+" [High,Triaged] https://launchpad.net/bugs/143735316:50
-queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-125.150~14.04.1] (kernel)16:51
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.13.0-1017.20]16:52
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-125.150]16:52
tsimonq2infinity: Hi. Want to do that seed conversion?16:53
-queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.15.0-1011.11]16:54
-queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-125.150~14.04.1]16:55
=== blackboxsw is now known as blackboxs
=== blackboxs is now known as blackboxsw
bdmurrayrbalint: Could you SRU verify bug 1758963?17:15
ubot5bug 1758963 in update-manager (Ubuntu Artful) "Please don't ship empty directories in the source package" [Undecided,Fix committed] https://launchpad.net/bugs/175896317:15
-queuebot:#ubuntu-release- New binary: kbackup [s390x] (cosmic-proposed/none) [18.04.0-1] (no packageset)17:15
-queuebot:#ubuntu-release- New binary: kbackup [ppc64el] (cosmic-proposed/none) [18.04.0-1] (no packageset)17:17
-queuebot:#ubuntu-release- New binary: pal2nal [amd64] (cosmic-proposed/none) [14.1-1] (no packageset)17:19
-queuebot:#ubuntu-release- New binary: kbackup [amd64] (cosmic-proposed/none) [18.04.0-1] (no packageset)17:20
-queuebot:#ubuntu-release- New binary: kbackup [i386] (cosmic-proposed/none) [18.04.0-1] (no packageset)17:20
bdrungtumbleweed, thanks for taking care of distro-info-data17:51
tumbleweedbdrung: np. infinity did the heavy lifting anyway17:52
tumbleweedhope you're ok with the debian relase date guessing bit...17:53
bdrungyes17:57
-queuebot:#ubuntu-release- New binary: kbackup [arm64] (cosmic-proposed/universe) [18.04.0-1] (no packageset)18:01
-queuebot:#ubuntu-release- New binary: kbackup [armhf] (cosmic-proposed/universe) [18.04.0-1] (no packageset)18:03
-queuebot:#ubuntu-release- New: accepted kbackup [amd64] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted kbackup [armhf] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted kbackup [ppc64el] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted kbackup [arm64] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted kbackup [s390x] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted kbackup [i386] (cosmic-proposed) [18.04.0-1]18:06
-queuebot:#ubuntu-release- New: accepted faumachine [amd64] (cosmic-proposed) [20180503-1]18:08
-queuebot:#ubuntu-release- New: accepted pal2nal [amd64] (cosmic-proposed) [14.1-1]18:08
cascardocan someone help get s390-tools from xenial-proposed to xenial-updates (and xenial-security)?18:22
infinitycascardo: Releasing.19:00
cascardoinfinity: thanks19:23
tsimonq2infinity: I finally got around to creating the CosmicCuttlefish wiki page. Do you have a draft release schedule somewhere, or should I copy over the one we were working on a few months ago?19:37
infinitytsimonq2: I'll put one up.19:38
tsimonq2infinity: OK.19:39
infinitytsimonq2: If we're doing ReleaseTaskSignup again, maybe we should replace A1/A2/B1 with lines asking for community volunteers to advocate testing weeks.19:39
infinitytsimonq2: Which should be much more lightweight.  Just sending mails to all the lists, making sure project leads are awake, that sort of thing.19:39
tsimonq2infinity: I agreed to do that for this cycle to get a process going.19:40
infinitytsimonq2: Then you can sign up for all of them! ;)19:40
tsimonq2infinity: But for next cycle though.19:40
tsimonq2infinity: OK. :D19:40
infinitytsimonq2: And sign me up for Beta and Final, obviously.19:40
tsimonq2infinity: Yep. It's now just "Beta", aye?19:40
infinityYeah.19:40
tsimonq2OK. On it.19:40
infinity"Final Beta" was a silly name anyway.19:40
flocculanttsimonq2: I#ll take a week later in the cycle19:40
infinityJust the only way to communicate that is was B2 for some and B1 for others.19:41
tsimonq2flocculant: Let's see how it plays out.19:41
infinityReally, B1 should have just been A3.  That would have been less dumb.19:41
tsimonq2Yeah.19:41
infinityBut it's in the past now, so yay.19:41
tsimonq2I agree.19:42
flocculantwell - we'll unlikely participate early in the cycle19:42
tsimonq2flocculant: So, you aren't alive at the beginning of the cycle?19:42
tsimonq2That's pretty much what's needed.19:42
infinity"Requirements to drive testing week: Breathing; access to email."?19:43
flocculanttsimonq2: actually it depends on how soon we land gtk3 xfce stuffs19:43
tsimonq2infinity: That. :P19:43
tsimonq2flocculant: Then tell us that.19:43
tsimonq2It'll be pretty lax, I think.19:44
flocculanttsimonq2: tell who? and why?19:44
tsimonq2flocculant: I'll put out an email to ubuntu-release at the end of May with details ahbout the testing week, buut it'd be good to check in  with flavors too.19:45
* tsimonq2 grrs at ConnectBot.19:45
flocculantmaybe we should try and set up some sort of frequent inter-flavour session/contact19:46
flocculantperhaps on https://community.ubuntu.com19:46
tsimonq2That's the idea here, ish.19:46
flocculantI'd say irc - but timezones ...19:46
flocculantnothing to onerous - but at least a talking shop19:47
tsimonq2Yeah.19:47
tsimonq2Of course.19:47
flocculantup to now - the only time we talk is at set times in the 6 months19:48
tsimonq2And that's not good, in my opinion.19:48
flocculantand that's ' you doing this milestone or not'19:48
flocculantyup - agree, I'm all for us talking to each other more19:49
tsimonq2Speaking of cross-flavor things...19:49
flocculantabout the only people I regularly talk to are you, wxl and random people from studio19:49
tsimonq2infinity: Where were we at irt seed things?19:49
flocculantoh - and valerie :)19:49
tsimonq2flocculant: Right. It's a mess, I agree.19:49
wxltsimonq2: p.s. congrats on the DMB election btw19:50
flocculanthi wxl19:50
tsimonq2wxl: Thanks.19:50
wxlhey-o flocculant :)19:50
flocculanttsimonq2: I'll mail -release about ^^ nowish19:51
tsimonq2flocculant: Go right ahead.19:51
flocculantI will ;)19:52
tsimonq2infinity: I'll put Beta at 09/27 and Release at 10/18 for now. Season to taste.19:53
tsimonq2(On the release task signup page, which is pretty much done, by the way.)19:54
tsimonq2flocculant: What are Xubuntu's thoughts on axing i386, by the way?19:55
flocculantno real thoughts currently - people take time away in the week(s) post-release19:56
tsimonq2OK.19:56
tewardtsimonq2: very real consideration: flavor-agnostic, Wine 64-bit sometimes *just doesn't work* for some Windows apps, and Wine i386 is needed for the 32-bit wineprefixes.19:57
tewardwhile that's not justification to totally destroy i386 globally, it's one consideration point19:57
teward(since it was brought up in the email chains)19:58
wxli think someone already brought that up on the maililng list, teward19:58
wxlsteam is apparently an issue, too19:59
tewardwxl: Wine was mentioned, but not specifically detailed19:59
* wxl nods19:59
tewardthe rest of the discussions spun off to flavors, download/install ratios, etc.19:59
tewardthe core part of *my* concern is, if we axe i386, we need to axe wine, since IIRC their 64bit version has an immediate dependency on the i386 version as well20:00
wxlgiven bug 1 that might be an issue :)20:00
ubot5bug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/120:00
tewardmmm20:00
tsimonq2Is there any hope for amd64 support upstream?20:00
wxlit's an issue with windows apps, tsimonq220:01
tewardtsimonq2: less an "upstream support" question more a "Windows Apps Are Cosmic Pains In The..."20:01
tewardi could finish that sentence but you know me well enough to complete the phrase your self.20:01
tsimonq2Pain in the Cuttlefish?20:01
tsimonq2:P20:01
Bashing-omi386 media attention: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-i386-Dropping-Discussion .20:04
tsimonq2Softpedia was first.20:04
tsimonq2And, technically, they're more accurate on this one.20:04
Bashing-omtsimonq2: Noted :)20:04
tsimonq2https://buff.ly/2KOVOzL20:05
tewardtsimonq2: wxl: I don't disagree with 32bit support being that much harder to maintain, but I disagree in theory about dropping i386 in the short/mid term20:06
tewardI haven't replied yet because my email is being screwy, but my opinion is if we *don't* cut i386 immediately, we cut it out sometime between now and next LTS20:06
flocculanttsimonq2: except for the blog title which include xubuntu ...20:06
tewardeven if the next 2 releases have i386, and the remaining ones don't, that'd at least give a year for some 32-bit-only things to be done.20:07
wxltbh i'm split about whether or not to remove it20:07
tsimonq2flocculant: Right, that's kinda clickbait. :P20:07
wxlthe meltdown issue is a big concern, imho20:07
flocculantteward: at the moment flavours are really only talking about stopping images building - nothing else20:08
infinityteward: Dropping 32-bit *installers* has no bearing on wine32, since you can (I certainly do) run wine64 and wine32 on a 64-bit install.20:08
tewardflocculant: infinity: one of you want to clarify on the chain about that?20:08
tewardI'm for dropping 32bit installer images.20:08
tewardi'm against droppping x86 as a repository arch20:08
tewardand i don't see the clear distinction in the thread20:09
tsimonq2teward: We either do it now or at the beginning of the 20.10 cycle.20:09
teward(which is a repeat problem of the prior discussion of 32bit support way back when in the Server team's discussions)20:09
infinityI haven't been following the thread, but yes, it should be about dropping installers first.  Then a second discussion about dropping the arch.20:09
tewardtsimonq2: clarify *your* intentions then: do you mean *total* x86 dropping, or just installer dropping, over the next cycle or two?20:09
infinityPersonally, I'd like to drop both armhf and i386 on the floor before 20.04, but I might not win that argument.20:09
tewardbecause this is something we need to clarify in the thread to focus the discussion20:10
tewardand as soon as I unscrew my email (your email might be screwed too I didn't check) i'll drop a note to the list for clarification20:10
tewardtsimonq2: i think you meant 20.04 cycle there, because 20.04 is (probably?) going to be an LTS, and it doesn't make sense to drop i386 *after* an LTS if it's going to be supported for 3-5 years anyways20:11
tewardI'm all in favor of a phaseout if we and upstreams can resolve the remaining dependency issues20:11
teward(again, in the thread, clarification required)20:12
tsimonq2infinity: I agree with i386. I disagree with armhf because I Like Pie. (Or Pi, whatever, but Pie is good too. :P)20:14
tsimonq2teward: No, after 20.04. I don't want to abandon users on unavailable upgrade paths.20:15
tewardinfinity: if you had a say, would you want to drop i386 *after* 20.04, or before?20:15
tewardon the premise that we'd have to support i386 for an additional 5 years if we kept it in 20.0420:15
infinitytsimonq2: The Pi1 can't run Ubuntu anyway and the Pi3 is arm64-capable, so armhf-versus-Pi only matters for the Pi2.20:15
Odd_BlokeIt would only be an additional 2 years; we're on the hook for 18.04 anyway.20:16
tsimonq2infinity: Ah.20:16
tewardOdd_Bloke: s/2 years/3 years/ ?20:16
teward(not sure your math works out as stated?)20:16
infinityteward: If it was entirely up to me, I'd drop all 32-bit before 20.04.  It's getting harder and harder to shoehorn modern bloaty software on 32-bit systems.  And i386 has other awful things going for it, most notably a lack of upstream kernel interest in actually fixing security bugs.20:16
infinityOdd_Bloke: You can make that same argument every 2 years. :P20:17
Odd_BlokeDoesn't make it any less valid. ;)20:17
Odd_Bloketeward: 18.04 will be supported until 2023, 20.04 would (presumably) be supported until 2025.  It's only an extra 2 years.20:18
tewardOdd_Bloke: I think we'd have to loop in the security team on this for their viewpoint, especially if it gets harder and harder to get viable security patches in.20:18
tewardoh, i have a question to ask you too infinity, but it's more to gauge opinion on something, and can be done after our discussion here.20:18
Odd_Bloke"only" is perhaps a little too diminutive. :p20:19
-queuebot:#ubuntu-release- Unapproved: horizon (bionic-proposed/main) [3:13.0.0-0ubuntu1 => 3:13.0.0-0ubuntu1.1] (openstack, ubuntu-server)20:19
tsimonq2sarnold: Hi. ;)20:19
tewardOdd_Bloke: i could make the same argument then, but at some point we have to kill it, and if come 2 years from now the same argument is used again to support not dropping it, you're in a cycle of "Yeah we'll just continually support this"20:19
tewardwhich is AFAICT what we're running into now?20:20
Odd_BlokeFrom a cloud images POV, we already don't produce images for i386.20:20
-queuebot:#ubuntu-release- Unapproved: horizon (artful-proposed/main) [3:12.0.2-0ubuntu1 => 3:12.0.2-0ubuntu1.1] (openstack, ubuntu-server)20:20
tsimonq2sarnold: You responded on the mailing list in 2016; what do you think about u32-bit from a security team POV?20:21
tsimonq2s/u3/3/20:21
Odd_Bloke(Well, we do for Openstack and LXD, but not for the clouds themselves.)20:21
tewardinfinity: do you have the power to unhold my message to -devel-discuss?  Apparently I forgot to select my @ubuntu.com address in my send aliases, so it sent as my bare email :/20:26
cjwatsonwxl: KPTI on i386 is being worked on, FWIW - it's true that it's been later than x86-64, but I don't expect that particular thing to be a long-term problem20:39
cjwatson(I don't have the links right now, but I saw them floating around in some thread on LWN)20:39
wxlcjwatson: that's good to know. that was the one thing that concerned me the most.20:40
wxltbh i don't really use i386 anymore (i do have some testing machines, but not for production), so i often just don't pay attention.20:40
cjwatsonOne of my other concerns is that nobody has ever put the effort into productising sidegrades, so it's something of a screw-you to continuous upgraders (on 64-bit-capable hardware, anyway).20:40
cjwatsonI mean, it *can* be done; I've done it I think three times.  But it's an expert manoeuvre right now, and it doesn't have to be.20:41
sarnoldat some point Very Important Pacakges like firefox and chromium just plain won't build on 32 bit systems21:13
sarnoldand we'll find out in the middle of two and a half LTS releases that we can't support e.g. firefox armhf or firefox i386 any more21:14
sarnoldI think the *politest* thing for the users is to stop i386 at an LTS boundary -- e.g., don't do 18.10 i386 or armhf, so that people can't accidentally step beyond the support curtain21:15
sarnoldof course people *love* their raspi and similar, and it'd be shame to say goodbye to those users, but it's getting hardr to fit in the address spaces available, and *far* harder to build on them21:16
UkikieMmmm, sidegrades.  I did one earlier this year on a headless system, the thought of doing it on my netbook (at the time of installation was unaware it did 64bit) with xorg/xfce and a whole lot more packages isn't very appealing.21:28
cjwatsonIt's certainly harder with a pile of desktop packages installed, yes22:02
-queuebot:#ubuntu-release- New binary: libpam-x2go [ppc64el] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:15
-queuebot:#ubuntu-release- New binary: libpam-x2go [s390x] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:15
-queuebot:#ubuntu-release- New binary: libpam-x2go [amd64] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:18
-queuebot:#ubuntu-release- New binary: mpl-scatter-density [amd64] (cosmic-proposed/universe) [0.3-2] (no packageset)23:18
-queuebot:#ubuntu-release- New binary: libpam-x2go [i386] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:19
-queuebot:#ubuntu-release- New binary: libpam-x2go [arm64] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:23
-queuebot:#ubuntu-release- New binary: libpam-x2go [armhf] (cosmic-proposed/universe) [0.0.2.0-2] (no packageset)23:23

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