/srv/irclogs.ubuntu.com/2019/09/12/#ubuntu-devel.txt

DarkTrickGeneral question: Why is bugzilla necessary, if there is launchpad?02:07
DarkTrickAs my understanding, bug reports can be filed with both, but launchpad seems to also include a deploy mechanims.02:07
sarnoldlaunchpad was written because bugzilla wasn't the kindest thing to work with02:22
DarkTrickwhat would now be the difference between filing a bug in bugzilla vs filing one in launchpad?02:29
DarkTricke.g. thunar bugs can be filed in both systems02:29
Unit193thunar is part of Xfce, they use bugzilla as their tracker whereas Launchpad is Ubuntu's bugtracker for *distro* bugs.  If you're asking "Why don't they set up Launchpad?" well that's much easier said than done, I'm only aware of one instance ever.  It's basically open core, not made for others to set up a clone.02:35
Unit193(In time, Xfce may move to Gitlab and its "issue" system)02:36
DarkTrickUnit193, "distro bugs" are bugs related to the interaction between the software/package and the distro?02:43
DarkTrickFor example: thunar crashes on raspi .... ?02:44
Unit193DarkTrick: I'd try the latest one, if it's still an issue then I'd report on upstream's tracker.02:59
DarkTrickUnit193, that was just an example to check, if I understood it correctly03:34
DarkTrickbut if I understand you right, you would report a "thunar crash on raspi" to bugzilla of thunar (as it is their bug-tracker)03:35
Unit193After checking the latest released version*03:36
DarkTrickSo, what would be a "distro bug" then?03:41
DarkTrick(I don't see a dividing line)03:42
Unit193Sometimes it's a configuration or integration issue, or if you don't check the latest version.  (It doesn't help that I assist with maintaining thunar, soo.)03:47
Unit193Different people see that line differently.03:47
DarkTrickUnit193, thank you04:09
sarnoldUnit193: heh, you know I've actually seen another launchpad instance up somewhere in the wild..04:31
Unit193sarnold: I know which one, because there's only one! :P04:31
sarnoldUnit193: hah. of course you do :D I shoulda known.04:31
Unit193Granted, I have to *find* it every time...And to be fair, there's a chance you linked me the initial time.04:33
sarnoldbut if you can find it again, that's something. :)04:35
Unit193You mean, https://quickbuild.io/ ?04:42
Unit193I didn't think it was really updated, but https://quickbuild.io/~kb9vqf/+archive/ubuntu/mythtv-029 seems to indicate it is.04:45
sarnoldUnit193: there we go!! that's the one :)04:46
cpaelzerrbasak: the SRU template that I added already is correct05:45
cpaelzerrbasak: just ignore the exagerrated initial report05:46
cpaelzermruffell: I don't immediately see the issue05:56
cpaelzermruffell: is this reproducible, e.g. if you just retry the build?05:56
mruffellcpaelzer: yes, it is05:56
cpaelzerwhat is the config of that PPA that you use?05:56
cpaelzerany odd dependencies enabled?05:57
mruffellit is reproducible on each build05:57
mruffellthe only strange thing is a private ppa, let me check deps05:57
mruffellthere are no dependencies enabled05:58
cpaelzerI'm comparing it to the last good build now ...05:58
mruffellon the last good build, posix_openpt and openpty both PASS05:59
cpaelzermruffell: just to eliminate differences, can you on the ppa enable proposed in the dependencies05:59
cpaelzerbecause that is how the e.g. SRUs will build06:00
cpaelzerI'm not really expecting this to be the difference06:00
cpaelzerthat breaks it06:00
mruffellokay, I have resubmitted the build with -proposed enabled06:02
mruffellcpaelzer: if you are wondering, I'm making a test package for LP 1681839, which someone is now experiencing on xenial. We have a solid reproducer now.06:05
ubottuLaunchpad bug 1681839 in libvirt (Ubuntu Bionic) "libvirt - disk not ready for pivot yet" [Medium,Fix released] https://launchpad.net/bugs/168183906:05
cpaelzermruffell: I have prepped and kciked a local build and a PPA rebuild test of my own - just to be sure; continuing checking the logs now06:05
cpaelzeroh the solid reproducer surely was a great help06:05
cpaelzerbut I'd try to help you no matter what - no need to explain :-)06:06
mruffell=)06:06
cpaelzernext difference, the PPA is not building debug symbols - that aagin should make no difference - but I see DEB_BUILD_OPTIONS=noautodbgsym...06:07
cpaelzerthe next obvious diff are your 4 patches06:08
cpaelzerfor the sake of eliminating options, have you tried rebuilding without them?06:08
mruffellthe 4 patches are to the same file, and should have no effect on the openpt testcase06:08
mruffellbut I haven't yet06:08
mruffellit fails with -proposed added, on the same openpt tests06:09
cpaelzerIt sounds vaguely familiar, like failing these tests on container based builds on armhf in the past06:11
cpaelzerbut why should that hit these builds now ... ?06:11
mruffellgoogle brought me to LP 1641615 since it mentions the same failing testcase06:12
ubottuLaunchpad bug 1641615 in libvirt (Ubuntu) "gnutls api breakage in 3.5.6" [High,Fix released] https://launchpad.net/bugs/164161506:12
mruffellbut you resolved that years ago06:12
cpaelzerheh - I know that guy06:12
cpaelzermruffell: https://salsa.debian.org/libvirt-team/libvirt/commit/2be70b3 ?06:13
mruffellhmmm intriguing06:13
mruffellI'll add the patches and give it a go06:14
cpaelzersure, but you should know that my rebild test started to complete builds successful https://launchpad.net/~paelzer/+archive/ubuntu/xenial-test-rebuilds/+packages06:15
cpaelzerno amd64 yet, but ppc & s390x are good already06:15
mruffelleven more interesting06:16
cpaelzerstill - try that patch just so we know if it would help your case06:16
cpaelzerha and x86 fails06:17
cpaelzersame reason06:17
cpaelzersome of the bumps in Xenial to the libs might have made it an FTBFS there06:18
cpaelzeror changes in the build env, but I'd not have heard of any06:18
cpaelzermruffell: I can even recreate the same locally in sbuild06:19
cpaelzeras there the chroot has the same attributes06:19
mruffellinteresting, my xenial vm doesn't recreate it. Its not fully patched though06:19
cpaelzernono in a VM you'd have full pty06:19
cpaelzeronly triggers in chroots06:19
cpaelzerlike sbuild/pbiuld/...06:20
cpaelzermruffell: I'm already building with the fix I linked applied06:21
cpaelzerI should know in ~3-5 minutes if this is a fix to the FTBFS06:21
mruffellcpaelzer: same here. Just submitted a second ago06:21
cpaelzerif that turns out to be true we just open a bug and you can tag and close it with your upload06:21
mruffellsounds like a good plan06:22
cpaelzermruffell: fix doesn't apply cleanly to xenial06:30
cpaelzer../../../../gnulib/tests/test-openpty.c:47:24: error: 'ENENT' undeclared (first use in this function)06:30
mruffellfun times.06:31
cpaelzermruffell: I have filed https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1843674 for us06:31
ubottuLaunchpad bug 1843674 in libvirt (Ubuntu Xenial) "FTBFS of libvirt in Xenial" [Undecided,New]06:31
cpaelzerDiving into my sbuild env to check what we could do ...06:32
mruffellcpaelzer: thanks for filing the bug!06:33
cpaelzerok I have it in the build env down to the gcc call that breaks06:36
cpaelzerENENT sounds wrong right?06:36
cpaelzerENOENT ?06:36
mruffellyeah, ENENT is not defined in <errno.h>06:37
cpaelzeryep that gets it working06:37
cpaelzerthere surely was a fixup later06:37
cpaelzerlet me check git06:37
cpaelzermruffell: https://salsa.debian.org/libvirt-team/libvirt/commit/7baa0daf8b104fa9b8dafd70dd9ec4bdd9ccee5a06:41
cpaelzerand https://salsa.debian.org/libvirt-team/libvirt/commit/0ce5eb75bdeaa3ef306457a03ed74b6a6bd65cba06:41
cpaelzer"recent debootstrap" might be the reason here as well06:42
cpaelzerthrowing that into my build as well06:42
mruffellwould you look at that06:42
mruffellyep, let's give it a go06:42
cpaelzer'll eventually probably push you a branch somewhere to mcombine witho your work06:42
cpaelzermruffell: oh I frogot - the build works now07:02
cpaelzermruffell: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1843674/comments/207:02
ubottuLaunchpad bug 1843674 in libvirt (Ubuntu Xenial) "FTBFS of libvirt in Xenial" [Undecided,New]07:02
mruffellcpaelzer: excellent! Thanks again =)07:03
cpaelzerdoko do the issues I see with new binutils in bug 1843394 ring any bell ?07:24
ubottubug 1843394 in ipxe (Ubuntu) "FTBFS in Eoan - Error: operand type mismatch for `push' - gcc 9.2.1" [Undecided,New] https://launchpad.net/bugs/184339407:24
dokosforshee: replied to 1843458, empty linux-source package :-/12:06
dokocpaelzer: I'll have a look12:08
ahasenackgood morning12:08
=== ricab is now known as ricab|lunch
dokoLaney: why do you keep the pcre2 changes in vte2.91?13:26
=== ricab|lunch is now known as ricab
Laneydoko: if you're saying they can be dropped, I didn't know that, nobody told me14:28
dokoLaney: well, the desktop team pushed for pcre2 promotion ...14:41
Laneyok14:42
seb128doko, we didn't, jbicha did iirc14:43
Laneywant to know the cool thing?14:45
Laneyit's already dropped :D14:45
Laneythe changelog is a copy and paste mistake14:46
Laneyhappy doko is happy14:46
seb128:)14:46
cpaelzerdoko: dovecot-antispam in the eoan rebild seems to be a LP infra problem14:48
cpaelzerdoko: I'd love to just hit rebuild at https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17542928 but I can't14:48
seb128doko, those ftbfs you are opening, any idea why -Wno-error=deprecated-declarations isn't working?15:03
dokocpaelzer: given back, but that's the third time ...15:03
dokoseb128: any concrete example?15:03
seb128e.g https://bugs.launchpad.net/bugs/184374415:04
ubottuLaunchpad bug 1843744 in libdbusmenu (Ubuntu) "libdbusmenu ftbfs in eoan" [High,Confirmed]15:04
seb128hum, I guess the failure might not be the deprecated/first error but15:04
seb128../../../libdbusmenu-glib/defaults.c:77:13: error: G_ADD_PRIVATE [-Werror]15:04
seb128though that doesn't state what the error is15:05
rbasakvorlon: could you delete my mysql-8.0 upload from eoan-proposed please? It didn't achieve what it was supposed to achieve, I'll be a week or two before I can get back to it, and in the meantime I understand it's entangling with other things (PHP?)15:06
vorlonrbasak: I don't see it entangling anything else, what do you see?15:07
rbasakbryce: ^?15:07
vorlonI don't mind deleting it - but I was explicitly checking what else was entangled to know what needed no-change rebuilds if I deleted it15:07
rbasakThere are no API/ABI changes in mysql-8.0 between release and proposed, so I don't think no-change rebuilds would be needed?15:08
rbasakotp, I'll look deeper in abit15:08
dokoseb128: is that symbol dropped?  maybe a warning emitted by one of the included header files?15:09
seb128doko, I don't think the symbol is dropped, it's deprecated in the code just unsure why it hits a warning not a deprecated one ... I'm just going to fix the deprecation, easier, thx15:09
brycerbasak, vorlon php-horde-activesync and php-horde-db seem to have mysql ties15:10
dokoseb128: the deprecation warning is about g_type_class_add_private15:11
seb128doko, right, it's not unclear what it doesn't like about G_ADD_PRIVATE to me15:12
seb128 ../../../libdbusmenu-glib/defaults.c:77:13: error: G_ADD_PRIVATE [-Werror]15:12
seb128but it doesn't tell what the error is15:12
cjwatsoncpaelzer: LP infra> in what way?15:13
cpaelzercjwatson: build issue without any log in https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17542928 (before it was restarted)15:13
cpaelzercjwatson: and I keep saying "LP infra" when I mean builders - sorry for that15:14
dokoseb128: I asked you to look for a #warning statement in one of the header files ...15:14
vorlonbryce: but I don't see that either of these packages are blocked in -proposed as a result of mysql-8.0 being there15:14
cjwatsoncpaelzer: OK, that sometimes means a network problem between buildd-manager and the builder, and sometimes means that the build ran amok and crashed the builder VM15:14
seb128doko, ah ok, I didn't get that bit before, will do, thx for the hint15:14
brycevorlon, I don't know what is blocking them tbh15:15
vorlonbryce: I only see php-horde-mime with a failing autopkgtest, autopkgtests test against the release versions of all other packages by default, and I don't see that the failing autopkgtests pull in mysql-8.0 from -proposed15:15
cjwatsondoko: third time> I think you must be misremembering; there is only one previous record of that build failing in our logs15:16
cjwatsonThere are vaguely network-blip-like symptoms in the logs here but it's hard to be certain15:19
dokocjwatson: hmm, I gave back all failed builds twice for the test rebuild ppa, but maybe one of them didn't complete15:19
cjwatsonThat would be to be expected, I think, given that the queue is deep15:19
cjwatsonLots of builds will be getting exactly the same score, and in that case the tie-breaker is first-in-first-out15:20
dokojamespage: simplestreams dep-waits on python-swift. is this expected?15:20
powersjdoko, https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1841277 server will look at it next week15:23
ubottuLaunchpad bug 1841277 in simplestreams (Ubuntu) "please drop Py 2 OpenStack dependencies" [High,Triaged]15:23
dokopowersj: ta15:23
kyrofaHey folks, the robotics community is pinging me about https://bugs.launchpad.net/ubuntu/+source/urdfdom-headers/+bug/1817595 . A debdiff is attached there, can we get a pair of eyes on it? Does anything more need to happen?19:30
ubottuLaunchpad bug 1817595 in urdfdom-headers (Ubuntu Bionic) "[SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers" [Undecided,New]19:30
kyrofasil2100, I suppose you're the vanguard today, huh. That's probably a question for you ^19:38
juliankkyrofa: You're one step too far, the next step would be to request sponsorship19:44
juliankOr well, ubuntu-sponsors is subscribed19:44
juliankbut like that's sponsorship territory atm, not really SRU team stuff19:45
juliankIMHO This also needs a proper test case, not a Dockerfile that pulls patched versions from the PPA19:45
juliankFWIW, I have no intention of sponsoring this upload, it's too complex19:47
kyrofajuliank, that type of feedback would be useful in the bug, if you don't mind19:48
juliankAh, it's just my personal opinion19:49
juliankI'll add some notes, though19:49
kyrofajuliank, that would be excellent, thank you. Even just the feedback about proper tests would be useful19:50
kyrofaI just don't know enough about SRU's to help them on their journey, best I can do is find someone who does :)19:51
juliankkyrofa: basically same procedure as for normal upload, except that you test it after the upload, and that SRU team approves the uploaded package rather than release team / automatic19:55
juliankand yes, version numbers are different19:55
juliankkyrofa: I think the main blocker for me (when looking at sponsoring it) is that I'd want someone who commits to actually testing it and drive down any autopkgtest regressions19:58
juliankAs I'd be fine uploading it if you say you're committed to actually driving it, but I wouldn't want to drive that myself19:59
julianksame for somebody else20:00
julianklike I don't care who is committed to driving this20:00
kyrofajuliank, I think Jose would commit to that, they have a vested interest in this going through, and I can  help with autopkgtest failures. I'll ask for him to state it on the bug if you like20:03

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