/srv/irclogs.ubuntu.com/2017/06/02/#ubuntu-devel.txt

=== tacocat` is now known as tacocat
=== JanC is now known as Guest29977
=== JanC_ is now known as JanC
=== CRogers_________ is now known as CRogers
jtaylorbigon: I got mozilla to change their firefox optimization default :D07:20
bigonyeah \o/07:21
bigonyou have a bug#?07:21
jtaylorhttps://hg.mozilla.org/integration/autoland/rev/8fdb9e30b6a707:24
abeatoinfinity, hey, I registered a bug in debian for klibc: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86376111:59
ubottuDebian bug 863761 in klibc-utils "klibc-utils: klibc does not support the reboot syscall argument" [Normal,Open]11:59
abeatoogra_, ^^11:59
ogra_wheee!12:03
Laneyslangasek: fixed12:41
=== CRogers_________ is now known as CRogers
slangasekLaney: cheers :)14:16
bigonjtaylor: "15:18
bigonWe however keep -Os as default for debug builds for now, because -O215:18
bigontriggers -Werror=strict-overflow failures somehow. "15:18
bigonshouldn't that be -Og for easier debugging?15:18
bigonor no -O option at all?15:18
jtaylorprobably compatibility with older gccs15:18
jtaylorand Og is not very good15:18
jtaylorthough probably not worse than Os15:19
bigondo you know in which version that patch will land?15:19
jtaylorversion 5515:20
bigonthx15:23
pdeeerbasak, bmw I've drafted an SRU justification for Certbot 0.14.0, and a template for future SRUs15:26
jamespageslangasek: hi!16:13
jamespageslangasek: so... what's the position on a package electing to not support 32bit architectures?  ceph as a project are not actively testing 32 on arm or i38616:14
nacccjwatson: perhaps you would have the context, is it appropriate to drop the same changes you did in LP: #1334916 for consolekit, in trusty?16:48
ubottuLaunchpad bug 1334916 in openssh (Ubuntu Trusty) "sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions" [Undecided,Confirmed] https://launchpad.net/bugs/133491616:48
slangasekjamespage: for future releases, it's ok to drop the package; for existing releases, we would want to continue providing the package if at all possible despite upstream not testing16:50
slangasekjamespage: do we have autopkgtests?16:50
cjwatsonnacc: I'm afraid I don't have the context for that any more - it would involve working out whether the desktop uses consolekit, and whether e.g. you can ssh to a trusty desktop without that patch and with X forwarding and run programs that do policykit checks that the user is an admin16:51
cjwatson(which IIRC was the original use case)16:51
nacccjwatson: ok, I'll put it on the backlog then :)16:51
naccmdeslaur: there might be a security regression in LP: #1690380 -- upstream adjusted the change they did (with the commits mentioned in my last comment)17:12
ubottuLaunchpad bug 1690380 in nagios3 (Ubuntu) ""Cannot open log file '/var/log/nagios3/nagios.log' for reading" error from nagios web UI when view alert history etc." [Undecided,Confirmed] https://launchpad.net/bugs/169038017:12
mdeslaurnacc: thanks, I'll look on mondayt17:15
naccmdeslaur: thanks!17:16
Unit193nacc: Did you get a chance to look at parsedatetime?17:54
naccUnit193: argh, sorry! doing it now17:55
Unit193Thanks.17:55
jamespageslangasek: limited - however it is possible to test i386 with the charms for ceph20:04
jamespageslangasek: we're ok for 10.2.x (current stable); next stable (12.0.3) is not so 32bit friendly - that said it is probably fixable20:05
jamespageslangasek: so this is >= artful only20:05
slangasekjamespage: right, it's perfectly fine to drop architecture support for a package between releases20:07
jamespageslangasek: ok I've raised on the upstream ML - lets see if users are actually using armhf or i386 :-)20:08
slangasekI mean, we want to support packages on every architecture we can, but you're not expected to make a herculean effort to support something that upstream doesn't20:08
infinityI think we're approaching the point where we need to have a large public discussion about possibly dropping armhf and i386 entirely (post-18.04, perhaps).20:15
infinityThough I might prefer pre-18.04, it's perhaps a bit late to suggest that.20:15
jbichaI don't think we have to provide installers for i386 and armhf for 18.04 LTS20:18
mardyMirv: hi! At ubports there's an ongoing discussion on whether to move to qt 5.9. Do you have any wise things to say? :-)20:19
jbichaa compromise idea: what about restricing support lifetime for i386 and armhf to 3 years to match 16.04 LTS?20:19
sarnoldi386 I think you're right, but arm still has a huge amount of enthusiasm from hobbyists20:19
sarnoldi386 feels like it only exists at this point to cause guitarpro6 users insane amounts of trouble with their sudo packages20:19
mardyMirv: like, do you know if Debian or KUbuntu will package it?20:19
Unit193sarnold: My netbook doesn't do amd64 either though. :/20:20
jbichamardy: part of Qt 5.9 is in Debian exp.20:22
mardyjbicha: mmm... good to know, thanks!20:23
jbichamardy: I thought ubports was only working on vivid and xenial?20:23
sarnoldUnit193: oh :(20:23
infinityjbicha, sarnold: We already don't provide any non-d-i images for armhf, turning off d-i images would be trivial, but probably also pointless.20:24
infinityjbicha: Agree with dropping i386 ISOs, though.20:24
sarnoldinfinity: the usual debian/ubuntu problem of you only see the installer once and just upgrade for the next twenty years? :)20:24
mardyjbicha: correct, but we are discussing which qt version to use. If debian has already packages for qt 5.9, building them on a PPA for xenial will be easier (than do the whole packaging ourselves)20:25
infinitysarnold: Right, while dropping an installer image will remove some new users, I'd argue that i386/armhf really aren't seeing a mess of new users anyway (ubuntu-core and rpi2 might be a sticky "but" there), it's old users we need to eventually convince to throw away their hardware or reinstall lm-compatible hardware with amd64.20:26
mardyjbicha: looks like qtbase and qtdeclarative are there at least! That's plenty to work with :-)20:26
jbichamardy: are you saying that ubports does not use the Ubuntu archive version of Qt?20:26
sarnoldinfinity: I swear I'm going to upgrade my pandaboard to trusty one of these days. honest.20:27
infinitysarnold: Pandaboards are pretty aerodynamic.20:28
infinitysarnold: Just sayin'.20:28
mardyjbicha: it does for now, but xenial has Qt 5.5, which is rather old20:28
sarnoldinfinity: hehehe20:28
mardyjbicha: in case you are interested: https://forums.ubports.com/topic/273/june-1-2017-app-developer-os-developer-meeting/620:28
infinitysarnold: I have a whole graveyard of ARM dev boards here that I have no idea what to do with.20:29
jbichamardy: I believe mitya57 would definitely appreciate some help in getting Qt 5.9 into Ubuntu, updating qt-creator, etc.20:30
jbichamardy: I don't want to speak for Mirv but maybe he's not currently working on Qt in Ubuntu?20:35
mardyjbicha: I'm afraid you are right; I just thought that he might know better. But I'm happy to bother mitya57 as well ;-)20:36
cjwatsoninfinity: or sidegrade, for the smart/adventurous/mad ones21:24
cjwatsoni386> I'll still campaign for keeping it in the archive, for the usual reason William and I quote (i.e. containers running a half-million lines of Python take noticeably less memory that way)21:25
sarnolddo they still run a useful load with only ~2.5 gigs address space per process?21:31
cjwatsonthey run the LP test suite just fine21:32
sarnoldaha :)21:32
=== ejat is now known as fenris
=== fenris is now known as ejat
=== stgraber_ is now known as stgraber
Unit193mwhudson: Right, so Debian 863998 was just filed (Linking to https://github.com/golang/go/issues/13191), which looks like Debian 849662 but yet I believe it still doesn't compile on arm?23:05
ubottuDebian bug 863998 in src:golang-defaults "golang-defaults: Getpagesize() always returns 65536 on arm64" [Normal,Open] http://bugs.debian.org/86399823:05
ubottuDebian bug 849662 in src:gocryptfs "gocryptfs: FTBFS on arm64: panic: page size incorrect: 65536" [Important,Open] http://bugs.debian.org/84966223:05

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