/srv/irclogs.ubuntu.com/2018/08/22/#ubuntu-devel.txt

stgraberxnox: FYI bug 178831405:37
ubottubug 1788314 in zfs-linux (Ubuntu) "Conflict between zfs-linux and s390-tools" [High,Triaged] https://launchpad.net/bugs/178831405:37
=== acheronuk_ is now known as acheronuk
=== doko_ is now known as doko
seb128tsimonq2, hey, did you notice that your apport upload to cosmic is screwed? you removed some systemd units from the debian dir and the diff includes .bzrignore .bzr-builddeb  and .git noise09:02
sunweaverricotz: could you take a look at Debian bugs #836288 and #897694 and give some direction for a solution? (it is about plank upstream)10:04
ubottuDebian bug 836288 in src:plank "plank: please use dbus-run-session to run tests" [Normal,Open] http://bugs.debian.org/83628810:04
ubottuDebian bug 897694 in plank "plank: Shouldn't plank depends on dbus-x11 cause it's not working properly without it" [Normal,Open] http://bugs.debian.org/89769410:04
sunweavermy sense is that dbus-x11 is not the correct approach these days, but going the dbus-run-session route.10:05
sunweavercould you work on a patch?10:05
sunweaveroh well, maybe dbus-x11 is needed to solve #897694...10:05
sunweaverthanks for any feedback given...10:05
ricotzsunweaver, hi, yes, switching to dbus-run-session is reasonable, as the bug reports describes this should be pretty straightforward to do10:12
sunweaverricotz: what is the state of plank btw. any new upstream release coming before the end of the year? (Debian freeze)10:12
ricotzsunweaver, yes, I should do one soon10:13
sunweaverok. Can you add the dbus-run-session support then with it?10:14
ricotzyes10:14
sunweaverok, thanks. Removing that item from my list then.10:14
sunweaverThanks!10:14
xnoxstgraber, ouch!10:15
* sunweaver is currently doing bulk uploads to get the Vcs-*: fields correct for all my packages.10:15
ricotzsunweaver, this might be interesting too https://launchpad.net/%7Ericotz/+archive/ubuntu/cosmic-vala-42/+packages?start=0&memo=0&batch=20010:15
ricotzsunweaver, if it contains a package which you are working on10:16
sunweaverricotz: arctica-greeter -> ouch.10:18
ricotzthose failures are mostly easy to fix10:19
sunweaverricotz: libdbusmenu -> ouch10:19
sunweaverwhy is libdbusmenu related to vala 0.42?10:19
sunweaverit is C lib10:19
sunweaver(with a vapi file, possibly)10:19
ricotzit at least build-deps on valac10:19
sunweaverslick-greeter fails, too.10:20
sunweaverbut unity-greeter not.10:20
sunweaverinteresting...10:20
ricotza lot of vala-unrelated failure too10:20
ricotzif it is vala-related then they fail because of "error: Property `Background.current_background' with custom `get' accessor and/or `set' mutator cannot have `default' value"10:21
sunweaverah, arctica-greeter has been fixed upstream already.10:21
sunweaverI have some more changes in mind before I do a release.10:21
* sunweaver should hurry with that then.10:22
ricotz0.41.92-1 is still in NEW/exp10:22
sunweaverbackground.vala:447.5-447.37: error: Property `Background.current_background' with custom `get' accessor and/or `set' mutator cannot have `default' value10:22
sunweaveryeah, that one is new.10:22
sunweaverlet me see...10:23
ricotzthose default values can be dropped without further action if they e.g. null / 0 / 0.010:25
ricotzotherwise they should be moved into the constructor or made a field-initializer10:26
sunweaverlet me see...10:26
sunweaverricotz: how is this? http://paste.debian.net/1038857/10:26
ricotzdiff -U20 ?10:27
sunweaverhttp://paste.debian.net/1038860/10:28
sunweaverwhat about declarations/assignments like these...10:29
sunweaver"public double alpha { get; private set; default = 1.0; }" ?10:29
ricotzonly custom properties are affected10:30
sunweaverack.10:30
ricotzthe patch seems fine if you are familiar with the code base since this is a behaviour change10:31
eoli4nHi10:31
ricotzsunweaver, setting the default intends to have it set once at object creation10:32
sunweaverI guess my change is actual the wanted behaviour...10:33
ricotzwhich doesn't work as one expect for custom properties therefore the new error10:33
ricotzyeah, seems that way10:34
=== osx is now known as Toyo
=== pitti is now known as pittibot
=== pittibot is now known as pitti
GunnarHjrbasak, sil2100: What's the next step as regards the SRUs of bug #1778041? I have added to the bug report a link to an IRC conversion rbasak and I had last week, where the possibility to ship empty packages was mentioned. But the uploads also miss binary packages of certain archs, and such a measure wouldn't address that aspect. So is the latter considered a problem? Or put in another way: Considering that we don't seem to be13:30
GunnarHjable to consistently help certain users to keep their systems clean of dropped packages, is it motivated to do it for those libpdf and nacl packages which are said to be not functioning anyway?13:30
ubottubug 1778041 in freshplayerplugin (Ubuntu Xenial) "browser-plugin-freshplayer-pepperflash broken" [High,In progress] https://launchpad.net/bugs/177804113:30
rbasakGunnarHj: thank you for driving this bug. I won't be around for the next few weeks now, so I'm trying to avoid making any decisions that I won't be around to stand behind. I wanted to make sure we didn't go wrong on this point, but I'm happy for sil2100 to make the final decision.13:40
rbasaks/but//13:40
rbasak(or, if it had to be my decision, I'd ask infinity probably)13:41
GunnarHjrbasak: Ok, thanks for letting me know. Will talk with sil2100 about it, then.14:06
ahasenacktjaalton: heh, I was just about to ask you about sssd 1.16.3 :)14:39
ahasenackreleasing package sssd version 1.16.3-114:39
ahasenackTimo Aaltonen authored 1 hour ago14:39
roaksoaxdoko: howdy! is twisted broken on cosmic ? will the new update to 18.7 fix it ?14:44
roaksoaxdoko: i got a build failure with https://pastebin.ubuntu.com/p/P4pGG8RyFJ/14:45
jbichaacheronuk: so you have 2 copies of all the KDE autopkgtests running, 1 for the archive & 1 for a bileto ppa? 😢15:00
jbichacan we kill those bileto tests?15:00
acheronukjbicha: umm what? that wasn't intended!15:01
jbichaI'm looking at https://autopkgtest.ubuntu.com/running 😟15:01
acheronukjbicha: damn. usually I avoid that by lander sign off followed by publish immediately. I got called away from PC this morning at that time, so I guess was too slow15:03
seb128cyphermox, hey. modemmanager 1.8 is available, do you think you could update our package (and maybe Debian's)?15:03
acheronukjbicha: if they can be killed, please do!15:03
jbichajuliank: sil2100: slangasek: it would be appreciated if one of you could kill the #3374 ppa autopkgtests. Not sure if that's easy to do or not15:05
juliankjbicha: huh hmm15:06
juliankI can kill a running process, but I don't know how to remove it from the queue15:07
juliankso it would just go back in front of it15:07
slangasekjbicha: do I understand these packages are already published and the test results won't be used for the ppa?15:08
jbichayes15:08
slangasekok15:08
jbichahttps://bileto.ubuntu.com/#/ticket/337415:08
slangasekjuliank: from the cloud-worker, you can use autopkgtest-cloud/tools/filter-amqp to nuke things from the queue15:09
juliankslangasek: oh cool15:09
slangasekjuliank: example: for arch in amd64 armhf i386 pp864el s390x; do autopkgtest-cloud/tools/filter-amqp <amqp creds go here> debci-ppa-cosmic-${arch} -v ci-train-ppa-service/3375; done15:11
jbichaslangasek: 3374 please 😉15:14
slangasekdid I do the wrong one? shoot15:14
slangasekcpaelzer: ^^ sorry, I accidentally shot your autopkgtests out of the queue for https://bileto.ubuntu.com/#/ticket/337515:15
slangasekalso apparently I can't spell 'ppc64el' so let me fix that :P15:16
tjaaltonahasenack: ah, right. there's also 2.0.015:22
ahasenacktjaalton: yeah, but I was looking at the security fixes in 1.16.3 compared to 1.16.2, and ubuntu feature-freezes tomorrow15:23
cpaelzerslangasek: all of them or just one?15:25
slangasekcpaelzer: all of them that were in the queue... except I didn't kill them on ppc64el due to a typo15:25
cpaelzerhehe15:25
cpaelzerand I have one result on ppc being good :-)15:25
cpaelzerthanks for the notice15:25
cpaelzerwhat I have is barely enough to go on15:25
cpaelzergood that I don't wait for completion15:26
cjwatsonroaksoax: There's a fix for that in cosmic-proposed which hasn't made it to cosmic yet15:45
cjwatsonhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906215 is part of it but apparently twisted's own autopkgtests are failing too15:48
ubottuDebian bug 906215 in src:foolscap "foolscap autopkgtest needs update for new version of twisted" [Normal,Open]15:48
roaksoaxcjwatson: yes, I saw. thanks.15:52
roaksoaxcjwatson: i'm guessing this is a dependency that broke things? Becuase I built packages yesterday that depend on twisted and it didn't fail. Where as today it does with the same dependencies15:53
psusiok, what the heck?  I apt-get source qemu, dpkg-buildpackage, and qemu-system-* have extra deps that the one in the archive does not, including libcapstone315:53
cjwatsonroaksoax: Python 3.6 -> 3.7, presumably15:54
rbasakpsusi: are you using a clean chroot for the build? If not, configure scripts inside package builds can pick up extra dependencies and decide to build against them.15:54
cjwatsonroaksoax: Though I thought cosmic's default was still 3.615:55
psusiahh, I had previously tried building from the debian git repo and it had a few more deps it seems15:55
psusithat I guess are optional and we had them off15:56
psusihrm.. guess I should set up pbuilder again15:57
naccpsusi: i'd recommend build over pbuilder, fwiw16:11
psusithere's a new one?  I remember there being schroot and pbuilder16:15
naccpsusi: sorry, typo! sbuild :)16:16
psusiahh, forgot about that one16:28
tsimonq2seb128: I didn't O_O sorry.16:34
tsimonq2seb128: Want me to just revert it or is it handled already?16:34
ahasenackwhat does this do in debian/control, when there is no debian/tests? Testsuite: autopkgtest-pkg-python17:13
Unit193ahasenack: Basically, tries to import it.  See autodep8(1)17:15
seb128tsimonq2, it's not handled that I know of but I didn't follow up during the day, maybe best if you fix it17:19
=== ahasenack is now known as Guest22561
xnoxpsusi, on both debian & ubuntu -> $ mk-sbuild cosmic18:16
xnox$ sbuild -A -d cosmic *.dsc18:16
psusijbicha: say, what difference does it make whether gparted is in /usr/sbin or /usr/bin?18:47
=== slangasek changed the topic of #ubuntu-devel to: Archive: open (Cosmic Cuttlefish) | 18.04 released | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Bionic | If you can't send messages here, authenticate to nickserv first
jbichapsusi: ha, you're asking me about testing I did last year. I don't remember the details except that I guess it didn't run19:07
psusiodd... wonder why... I've merged your changes with a new upstream release I'm preparing for debian... was just wondering why it mattered either way19:09
jbichait should be pretty easy to check. You can drop the change if it works fine without it19:14
xnoxpsusi, policykit things hardcoding a path or something?19:16
psusiAFAIK, it should work fine either way19:16
xnoxis my best guess19:16
xnoxindeed19:16
psusiso I merged it and as long as it works in debian... it's fine I guess19:16
ahasenacktjaalton: hi, you seem to have included a patch file in the root directory of sssd 1.16.320:00
ahasenack--- sssd-1.16.3.orig/0001-common.dirs-common.postinst-Add-dir-for-secrets-with.patch20:00
ahasenack+++ sssd-1.16.3/0001-common.dirs-common.postinst-Add-dir-for-secrets-with.patch20:00
ahasenackin the debian .diff.gz file (source package)20:00
tjaaltonbah20:01
ahasenack1.16.2-1 is clean, doesn't have it20:04
tjaaltondoesn't matter20:05
ahasenackwas just checking if I hadn't overlooked it before20:05
tjaalton.2 was uploaded from another machine20:05
ahasenackthis 1.16.3 can be a sync with ubuntu20:06
ahasenackour delta was adopted upstream20:06
ahasenacker, sync with debian20:07
tjaaltonneed me to sync it?20:07
ahasenackno, I'll just make a formal mp to have a record20:07
tjaaltonk20:07
ahasenackshould be synced tomorrow my morning20:07
ahasenacktjaalton: fyi, the freeipa dep8 tests are failing but exiting 0, giving a false green status: http://autopkgtest.ubuntu.com/packages/freeipa/cosmic/amd6421:08
ahasenackscroll to the end21:08
ahasenackthey "all" end with a backtrace, but "PASS"21:08
ahasenackdebian is a few versions behind I think21:08
ahasenackI'll file a bug, and take a look when I cna21:09
ahasenackI'll add dep8 tests to sssd this cycle still21:09
tjaaltonit's in limbo atm21:13
tjaaltonnew dogtag is WIP, freeipa 4.7 too21:13
tjaaltonand I'm on paternity leave21:14
tjaaltonso most of it has to wait until next month21:14
ahasenackit's the only test than an sssd upload triggers, more reason for me to add a set of sssd specific tests21:16
ahasenackwhich I'll MP to debian, of course :)21:16
ahasenacktjaalton: congrats on the parenthood :)21:16
tjaaltonthx21:18
tjaaltonahasenack: btw, any plans to merge latest tomcat8? it finally adds a systemd unit21:52
tumbleweedwith the next tomcat8 upload, we should be able to sync again, going from the conversation in bugs.debian.org/89586621:59
tjaaltontumbleweed: check the ubuntu changelog..22:00
tjaaltonapparently what debian did wasn't enough22:01
tumbleweedtjaalton: I wrote that changelog entry22:12
naccheh22:14
tjaaltontumbleweed: so you're saying it's not needed?22:14
tjaaltonthe patch22:14
tumbleweedthey're taken another shot at the problem, upstream, and .33 hopefully won't need it any more22:17
tjaaltonah, .3322:18
tjaaltoncool22:18
tjaaltonI thought you meant .32-2 :P22:18

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