/srv/irclogs.ubuntu.com/2017/08/21/#ubuntu-devel.txt

=== cpaelzer_ is now known as cpaelzer
ginggsdoko: hi, can gsl be sync'd now? it might need another round of rebuilds08:00
lotuspsychjehey guys, im still having this bug on 17.10: https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/157638508:37
ubottuLaunchpad bug 1576385 in hexchat (Ubuntu) "Dialog window shows on a shot of gnome-screenshot only in hexchat" [Undecided,New]08:37
lotuspsychjejust letting you know, have a nice day08:37
dokoginggs: looks fine09:11
ginggsdoko: ok, thanks09:12
ginggsgsl sync'd now09:14
dokoxnox, jbicha (not here): gjs ftbfs on s390x, but built before10:17
xnoxdoko, i saw messages about dropping gjs binaries on s390x10:18
xnoxdoko, <jbicha> no objections to dropping gjs/s390x ? on #ubuntu-desktop10:18
xnoxdoko, i do not care about gjs, as that's not in the server stack. All the hip server things use nodejs / chromium js engine bits10:19
LocutusOfBorgtsimonq2, mitya57 ahasenack qtbase merge to fix qtwebkit?11:14
LocutusOfBorgI'm doing a qtwebkit-opensource-src 5.9.1+dfsg-4build1 with the fixes except for the qtbase bump, just to see how bad we go11:15
LocutusOfBorgmitya57, maybe you want to deal with it, since you seems to be the one who fixed qtbase :)11:16
mitya57LocutusOfBorg, let me look11:17
mitya57LocutusOfBorg, yes, it needs a dependency on qtbase downgraded. I did not think about Ubuntu when I bumped it in Debian :)11:18
mitya57And I would rather not merge qtbase at this point of time.11:19
LocutusOfBorgmitya57, so, upload as ubuntu1 or build1?11:19
mitya57As it changes debian/control, ubuntu1.11:19
mitya57Will you do it? I can too.11:19
LocutusOfBorgdoing that already :)11:19
LocutusOfBorgso I can do something useful there :D11:19
* mitya57 looks why previous version FTBFS on armhf11:20
LocutusOfBorgmitya57, symbols11:20
LocutusOfBorgsymbols sadness11:20
LocutusOfBorgbtw, queues are empty, so it might even be a good time for a qtbase merge11:21
LocutusOfBorgthis is actually the reason for me asking11:21
LocutusOfBorgI already have the dput ready to go BTW, I want the "build logs less than 20MB patch"11:21
mitya57LocutusOfBorg, please wait a couple of minutes before upload11:22
mitya57LocutusOfBorg, they won't be less than 20MB. They will be less than 500MB :)11:22
LocutusOfBorglol11:22
LocutusOfBorgI'm ready to go, on your ack11:23
mitya57LocutusOfBorg, can you please include also this? https://paste.ubuntu.com/25362023/ it should fix armhf build11:27
LocutusOfBorguploading!11:28
LocutusOfBorgis this something due to the change of linker?11:29
LocutusOfBorgadditional dup symbols?11:29
mitya57I don't know why that symbol exists only on some archs. It is not inline.11:30
mitya57The linker was changed only in Debian, in Ubuntu we are not using gold already.11:30
mitya57Thank you!11:30
mitya57And your upload LGTM :)11:32
LocutusOfBorgthanks!11:33
LocutusOfBorgmitya57, why it is not inline?11:35
LocutusOfBorg#if ENABLE(PARALLEL_GC)11:35
LocutusOfBorgvoid registerGCThread();11:35
LocutusOfBorgWTF_EXPORT_PRIVATE bool isMainThreadOrGCThread();11:35
LocutusOfBorg#elif PLATFORM(MAC)11:35
LocutusOfBorgWTF_EXPORT_PRIVATE bool isMainThreadOrGCThread();11:35
LocutusOfBorg#else11:35
LocutusOfBorginline bool isMainThreadOrGCThread() { return isMainThread(); }11:35
LocutusOfBorg#endif11:35
LocutusOfBorgnow, I don't know if it takes that else or not, but it might be11:35
LocutusOfBorgmaybe PARALLEL_GC is not defined on arm?11:38
LocutusOfBorganyhow, removing qtwebkit directory, my eyes are bleeding11:39
mitya57LocutusOfBorg, oh, I was looking at dev branch instead of 5.9.111:41
mitya57In any case it is not always inline, only when parallel GC is enabled.11:42
mitya57So it could be (optional=inline) in the symbols file, but really it is (optional=complicated) :)11:42
LocutusOfBorgI would say only when parallel GC is NOT enabled11:43
* mitya57 will add the optional tag to Git if the same diff is needed in Debian11:43
mitya57Right, sorry11:43
LocutusOfBorgwonderful, no problem, I just started looking at qt stuff, and I feel noob11:43
LocutusOfBorgbtw qtbase in Ubuntu is using ld linker, why aren't we hitting the duplicate symbol files issue?11:44
LocutusOfBorgI see in qtbase armhf log some --no-use-gold-linker or such11:44
* LocutusOfBorg is sorry if the answer is obvious, this is the first time he tried to understand all that stuff11:44
mitya57LocutusOfBorg, Ubuntu hit this bug earlier (some releases ago) and applied the fix earlier than Debian.11:45
mitya57The fix is *not* using gold (gold is default in upstream Qt, so needs to be disabled explicitly).11:46
mitya57Actually s/some releases ago/one release ago/: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/165643111:46
ubottuLaunchpad bug 1656431 in qtbase-opensource-src (Ubuntu) "Some KDE applications 16.10 FTbFS with Qt 5.7.1 on arm64 and ppc64el" [Undecided,Fix released]11:46
mitya57This bug is the same as Debian #85203511:47
ubottuDebian bug 852035 in binutils "binutils: bfd stumbles over duplicated symbols generated by gold" [Serious,Fixed] http://bugs.debian.org/85203511:47
LocutusOfBorgmitya57, mmm we fixed it in qt 5.7.1, but qt5.9 was syncd from debian, so the fix was lost, right?11:53
LocutusOfBorgwell now gold seems disabled everywhere11:53
LocutusOfBorg(in debian)11:54
mitya57LocutusOfBorg, qtbase 5.9 was merged, not synced. gold is disabled everywhere in ubuntu too.11:55
mitya57LocutusOfBorg, if you want I can adjust debian/rules in ubuntu+1 branch so that it does not differ from Debian?11:55
LocutusOfBorgit would be nice to make it syncable at the end11:56
LocutusOfBorgI mean all the qt stuff11:56
LocutusOfBorgtsimonq2, and I are working in that direction11:56
mitya57I am working in that direction too :) Currently we have only four packages with delta: qtbase, qtdeclarative, qtmultimedia (will be dropped with 5.9.2) and qtwebkit (temporary)11:59
mitya57In Debian we want to enable OpenGL ES on arm64 with Qt 5.9.2 packaging, which was a large part of Ubuntu delta.12:00
mitya57The only remaining delta in qtdeclarative is transitional packages, that can be dropped after 18.04.12:01
mitya57That is a big progress: in 5.7.1 times the qtdeclarative delta was huge12:02
mitya57Well, I was not quite right, there is also a patch to fix s390x weirdness.12:02
LocutusOfBorgs390x weirdness due to gcc different optimization levels?12:03
* LocutusOfBorg is not aware of that patch/package12:03
xnoxs390x does not have different optimization levels12:04
mitya57https://bugreports.qt.io/browse/QTBUG-61579, testcase_array_iteration.patch12:04
LocutusOfBorgwasn't it built with -O3?12:04
xnoxno, never12:05
xnoxppc64le only12:05
LocutusOfBorgack thanks12:05
LocutusOfBorgso, the Bl-symbolic foo applies as delta, right12:06
mitya57The reason for that weirdness is unknown to me, but we have a workaround12:06
LocutusOfBorgmitya57, did you try an ubuntu-built gcc compiler on a debian s390x porterbox? :)12:06
mitya57No12:06
xnoxdon't do that12:06
LocutusOfBorgwhy?12:06
xnoxs390x porterbox is lower minimal CPU arch than what Ubuntu targets12:07
LocutusOfBorgoh ok12:07
xnoxUbuntu requires zEC12+12:07
LocutusOfBorgso maybe the gcc uses more instructions on Ubuntu?12:07
LocutusOfBorgwe might do the other way around, keeping the gcc from Debian and try in Ubuntu12:08
LocutusOfBorgbut ppa don't have s390x, we need silo12:08
LocutusOfBorgor try to build a gcc without that bl stuff and no-change rebuild qt12:08
* LocutusOfBorg leaves for lunch, cheers12:09
mitya57xnox, how does Unity 7 need ubuntu-system-settings-online-accounts?12:11
xnoxmitya57, the expectation is that unity7 desktop "works" where "works" means is functionally equivalent. dropping unity-control-centre & online accounts would, imho, mean "not works". but this is out of scope for me to define what it means to "ship unity7 in 17.10". that is responsibility of the ubuntu desktop team.12:12
mitya57xnox, but ubuntu-system-settings-online-accounts is a Touch / Unity 8 package. It should not affect the desktop UI in any way.12:13
xnoxyes.12:14
xnoxlast time i looked it got entangled with unity7 stuff though12:15
xnoxmaybe i got it wrong12:15
xnoxbut there is work needed to be done to cut the touch bits out of things that are useful on both unity7 and unity812:15
seb128xnox, https://wiki.ubuntu.com/Unity/NotDefaultIssues12:15
seb128xnox, mitya57, not having online account was an accepted regression12:15
seb128we just can't maintain unity7 working as it was12:16
xnoxseb128, ah! is that authoritative wiki?12:16
seb128yes12:17
seb128well12:17
xnoxseb128, but the indicators must work, right? e.g. indicator-sound should drop dependency on url-launcher.12:17
seb128it's documented the known regression12:17
mitya57seb128, thanks for the pointer! Can you please comment on bug 1695928 and bug 1711204 that you (the desktop team) are fine with the proposed removals?12:17
ubottubug 1695928 in gnome-control-center-signon (Ubuntu) "Please remove obsolete UOA packages" [Undecided,Incomplete] https://launchpad.net/bugs/169592812:17
ubottubug 1711204 in ubuntu-system-settings-online-accounts (Ubuntu) "Remove ubuntu-ui-toolkit from the archive" [Undecided,Incomplete] https://launchpad.net/bugs/171120412:17
xnoxcause url-launcher is unity8/touch stuff - system-settings-app12:17
seb128we didn't make a call on what level of support we are still supposed to give to unity712:17
mitya57I think slangasek wants an input from Canonical desktop team, which you represent :)12:17
seb128mitya57, yes12:17
mitya57Thanks!12:17
seb128yeah, I already commented on that bug12:17
xnoxseb128, and if questions arise, are you the goto?12:17
seb128saying that the list is fine12:17
seb128xnox, willcooke or I yes12:18
xnoxseb128, tah. If i spot stuff whilst doing removals and have questions I will ping you two.12:18
mitya57xnox, url-dispatcher is easy to port away from ubuntu-ui-toolkit. I can take care of it.12:18
xnoxmitya57, that would make total amount of work to do go down. as we'd need not to patch every single indicator-* to drop the build-dep on url-dispatcher.12:19
xnoxand e.g. i'm not compentant to drop u-u-t from url-dispatcher12:20
mitya57Yes, my plan was to avoid patching all indicators.12:20
mitya57I also have no idea what it should do, but I can port the UI and test it :)12:20
seb128I doubt anything use that UI now12:20
seb128that was touch specific12:21
seb128so even if it's buggy/missing it shouldn't be an issue12:21
LocutusOfBorgwonderful! this makes qtbase candidate, right? :D12:22
LocutusOfBorgso we can look more carefully to what is missing12:22
mitya57https://code.launchpad.net/~mitya57/url-dispatcher/qtquickcontrols/+merge/32930213:05
xnoxmitya57, i like it! =)13:13
mitya57Actually I don’t know what is the point of what I have done, as nobody will use it on desktop. But it will allow url-dispatcher to die a bit later :)13:14
xnoxmitya57, >_< i feel you, and on the other hand feature freeze is on thursday hence YOLO13:20
FauxFreeze? Quick, time to sneak in openssl 1.1 while nobody is looking.13:21
xnoxFaux, haha, no.13:21
xnoxFaux, have you seen the state of openssl 1.1 in debian and the mega flame war thread13:21
xnox?13:21
FauxI haven't, since the one about having to do a release with two versions and e.g. curl being a nightmare.13:22
xnoxahhhh tl;dr there is more stuff "discussed" now13:22
FauxThere's not really much to discuss, except "when", and "I don't like it wah wah".13:23
xnoxFaux, literarly that's not what is discussed or causing contreversy now.13:25
FauxHaha. Maybe I should go look. -devel?13:26
FauxOh, I saw the TLS1.0/1.1 thing. Interesting experiment, but not a real problem or appropriate to release.13:27
xnoxi beg to differ13:33
xnoxi have no simpathy for using modern client to talk to old servers; or making my server insecure because of end of life client.13:33
xnoxthere is only one logical reason why people13:33
xnoxwould want to prevent stronger security.13:33
FauxIf TLS 1.1 had been widely supported even five years ago I might agree with you, but the ~3 years it's been relatively commonplace is just not enough for people to catch on.13:35
xnoxFaux, huh?! precise has TLSv1.2 support13:39
FauxI'm biased this dropping support for things like Android 4.3, the current release until Oct 2013 (less than four years ago), and openjdk-7, which was the most recent Java release until Xenial.13:41
xnoxFaux, i have no sympathy for obsolete clients, Android 4.3 is long dead and out of security support13:42
FauxI know! I'd love to see it fixed. But I still think the reality is that you have to give terrible people five years, which will be the case by buster's release, but not 17.10.13:43
dokotjaalton: plesae don't use llvm-5.0 for mesa yet. llvm-5.0 has a hard coded dependency on gcc-614:05
tjaaltondoko: ok, damn14:05
dokoapw, looking at https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1702056: do you build the linux package without having proposed enabled?14:15
ubottuLaunchpad bug 1702056 in linux (Ubuntu) "perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared libraries: libbfd-2.28-system.so: cannot open shared object file: No such file or directory" [High,Confirmed]14:15
ginggsdoko: gsl migrated on its own, no rebuilds required14:19
apwdoko, we do not, but that is an old pre transition kernel14:25
dokoapw: ta, so maybe close the issue14:25
apwwhen the new kernel and binutils migrated as a set they also orphaned the old kernel perf14:26
apwI am supprised that is installable though to get that erroe14:26
dokoLocutusOfBorg: do you intend to package the new lsvpd upstream version?14:59
naccslashd: ping18:06
slashdnacc, hi18:16
naccslashd: so i was reviewing the logrotate merge -- and i'm a bit confused why so much of the upstream bits were dropped from your fix to LP: #1709670 ? specifically, you dropped the bits that moved the allocateHash call and so they are incorrect now18:19
ubottuLaunchpad bug 1709670 in logrotate (Debian) "logrotate never recovers if the statefile is corrupted" [Unknown,New] https://launchpad.net/bugs/170967018:19
slashdnacc, looking18:23
naccslashd: thanks, i think i'll end up dropping your changes in the merge, and taking the strict upstream change, but it might be relevant for the SRUs18:23
slashdnacc, so you'll do artful and me the SRU does that sound good ?18:24
slashdnacc, thanks for catching this up18:25
naccslashd: right, but it looks like you already did both :) and i'm worried the SRUs might be wrong (and the one in artful looks a bit off too) -- so you might need to change the state there, to indicate it needs another update18:26
naccslashd: but yeah, i'll make sure the artful version is correct18:26
slashdnacc, yeah I'll look at the SRU again.18:26
naccslashd: thanks, let me know if you want help reviewing the changes -- sorry I didn't catch it earlier18:35
slashdnacc, glad you did, still don't understand why I miss that.18:37
naccslashd: i only caught it because the patch definitely doesn't apply (I didn't expect it to) to the latest from Debian (which isn't fully cuaght up to upstream), but contains a comment about don't return until we allocate the hash, which doesn't happen with the patch applied :)18:38
rosattighi guys, I'm trying to install artful and I got this message -> debootstrap warning: http://us.ports.ubuntu.com/ubuntu-ports/dists/artful/main/binary-ppc64el/Packages.gz was corrupt18:47
rosattigwhat does it mean?18:47
rosattigthanks in advance!18:47
naccrosattig: for #ubuntu, perhaps?18:47
rosattigok, I can post there thanks. But I thought as it was a development release, this channel would seem more appropriate18:48
naccrosattig: this is for development of ubuntu18:49
naccrosattig: sorry, #ubuntu+1 then, for artful18:49
rosattigok nacc, thanks!!18:49
naccrosattig: np18:50
LocutusOfBorgdoko, can you please ask the maintainer to update it in Debian too?20:41
slangasekmitya57: so bug #1695928 is not filed against the packages that you say should be removed. Do you want to correct that? or jbicha?21:06
ubottubug 1695928 in gnome-control-center-signon (Ubuntu) "Please remove obsolete UOA packages" [Undecided,New] https://launchpad.net/bugs/169592821:06
mwhudsonLaney: that's one special docker bug you have there21:21
mwhudsonwaait how the fuck are docker autopkgtests marked as always failing on ppc64el21:24
mwhudsonthey were definitely working at some point21:24
mwhudsonslangasek: why did you mark docker badtest?21:25
mwhudsonslangasek: without at least talking to me? :)21:25
mwhudsonbiab21:26
slangasekmwhudson: according to the comment in my hints file, the tests were failing when run against the release pocket alone, so the test had already regressed in release when I set the hint21:27
mwhudsonslangasek: :(21:27
mwhudsonat least it fails on amd64 too so i have some hope of debugging it21:31
mwhudsoni wonder if it's some change in how the lxd images are built21:32
jackpot51What does MIR mean in an issue title?22:31
naccMain Inclusion Request22:31
naccjackpot51: ---^22:31
Unit193Or a bug against the Mir display server, they named two different things by the same name.22:31
naccheh22:31
naccI assumed MIR referred to the former, and Mir to the latter in bugs, but I suppose that's not always going to be true :)22:31
FauxOr the Rust intermediate representation!22:32
seb128bah, I copied the new libreoffice from a ppa but to artful instead of artful-proposed :-/22:57
xnoxseb128, i thought new ubuntu-archive-tools did have a fail-safe net, to prevent archive admins from doing that.23:00
xnoxseb128, demote to proposed? and resurrect the old one?23:00
seb128xnox, seems not :-/23:00
seb128how do I do that?23:00
xnoxi'm not an AA, but it is possible.23:00
xnoxslangasek, doko, wgrant, can you help seb128 ?23:00
xnoxseb128, there should be a demotion script available in the ubuntu-archive-tools. and then it's a copy-package from artful to artful with a flag to allow copying deleted packages. make sure to use exact version number.23:01
xnoxsomething like that, but I do not know for sure.23:01
seb128xnox, k, tried to do that, I hope I did it right :-)23:08
xnoxseb128, ok, i see new libreoffice in proposed. that looks good.23:09
xnoxI do not see resurrected libreoffice, yet. there are double copy bugs, where if you do it twice it gets lost, thus if it's not there after 2 more publisher runs, you may need to do the ressurect again.23:10
* xnox ponders block-proposed bug until ressurection is done23:10
xnoxah, 5.3 is in artful-proposed, so it should migrate23:10
xnoxseb128, if you have powers - just hint to skip / ignore tests for old libreoffice to migrate http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libreoffice23:11
seb128I don't know how to do that23:12
xnoxhm or not, i am confused, i shall stop talking.23:12
seb128xnox, demotion failed with a "no binary to copy"23:12
xnox(it's entangled with poppler, etc)23:12
xnoxseb128, send an email to release, things look ok now, but i'm not sure if they could be improved and like have some libreoffice in artful-release23:13
seb128well copying back the old version seems to have failed23:13
seb128or at least I don't see it23:14
seb128score :-/23:14
xnoxdon't do it again, until a publisher run.23:14
* xnox somehow things that lp bug is not fixed yet.23:14
* xnox somehow thinks that lp bug is not fixed yet.23:14
seb128k23:15
seb128well, it looks like libreoffice-l10n failed or isn't showing in artful yet23:19
seb128libreoffice is pending23:19
seb128I guess I'm just going to call it a day and see how things look like in the morning/try to sort it out if nobody else fixed up for me in between23:19
xnoxyeah, it looks ok now.23:19
* xnox needs to sleep too23:20
Unit193No, sleep is bad.23:20
naccmwhudson: did you send the delta for src:python-pika-pool (from 1ubuntu2) to debian?23:55
mwhudsonnacc: i guess if you're asking you can't see a bug in debian bts and the answer is probably no?\23:55
nacccoreycb: --^ i guess you did the last upload to debian, presumably the same change as our last is needed there and we can then sync it?23:55
naccmwhudson: more to get the conversation rolling ;)23:56
naccmwhudson: and <cough>submittodebian<cough> you23:56
mwhudsonyeah looks like that one got missed23:56
naccnp, i'll send it up23:56
mwhudsonthanks :)23:56

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