/srv/irclogs.ubuntu.com/2019/02/14/#ubuntu-devel.txt

sparrhttps://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc6/ has five patch files that are applied to the source before building the mainline kernel00:40
sparrhttps://help.ubuntu.com/community/Kernel/Compile and https://wiki.ubuntu.com/KernelTeam/GitKernelBuild don't mention those steps00:41
sparrif I am trying to build a kernel that is as close as possible to the ubuntu packaged kernels, should I be applying those or any other patches?00:42
sparraww, damnit, sorry, all that belongs in another channel. sorry00:42
=== cpaelzer__ is now known as cpaelzer
LocutusOfBorghello oSoMoN09:48
oSoMoNhi LocutusOfBorg09:48
LocutusOfBorgcan I upload a chromium fix for https://bugs.launchpad.net/ubuntu/+source/python-selenium/+bug/1667208 ?09:48
ubottuLaunchpad bug 1667208 in python-selenium (Ubuntu) "Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu" [Undecided,Confirmed]09:48
LocutusOfBorgmy wild guess is: let chromium-chromedriver provide chromium-driver09:48
LocutusOfBorgand add a symlink from /usr/lib/chromium-browser/chromedriver to /usr/bin/chromedriver09:48
LocutusOfBorgthis way chromium should expose the same binary packages as debian, and the binary would be in the same location, so applications can use it09:49
oSoMoNLocutusOfBorg, why not patch python-selenium to change the hardcoded path?09:50
LocutusOfBorgbecause we would need to patch all the reverse-dependencies if we do it that way...09:51
LocutusOfBorgdo you have a reason for exposing tools in a different location with debian?09:51
oSoMoNno specific reason, just trying to figure out the least invasive fix − I'm not sure I understand why reverse deps would need to be patched, if the path is already in python-selenium, do other packages hardcode it too?09:53
LocutusOfBorgmaybe ruby-selenium-webdriver?09:54
LocutusOfBorgnot sure how many else...09:54
LocutusOfBorg./lib/selenium/webdriver/chrome/service.rb:        @executable = 'chromedriver'.freeze09:55
LocutusOfBorg./lib/selenium/webdriver/chrome/service.rb:          Unable to find chromedriver. Please download the server from09:55
LocutusOfBorgif applications are supposed to find it in $PATH, I think we should patch chromium...09:55
oSoMoNthat makes sense09:56
LocutusOfBorgin the future more applications might start using it, this is why I think the binary package should be provided and the tool exposed in the system in a sane-way, otherwise we might not even have a way to find what in the archive breaks because of this09:56
oSoMoNLocutusOfBorg, please do not upload the fix right away though, as there's a new release in the stable channel for which I was preparing an upload when you pinged, if you make a patch and hand it to me I'll include it09:57
LocutusOfBorgoSoMoN, I think I'll reassing the bug to chromium, and I'm already looking at how debian did it, I'll provide a patch shortly09:57
LocutusOfBorgthanks for confirming my analysis, I'm of course not a chromium user/developer :)09:58
oSoMoNLocutusOfBorg, thanks, I'll put my upload on hold until I get your patch09:58
LocutusOfBorgmmm interesting, the debian package is 100MB, the Ubuntu one is 700MB09:58
oSoMoNI haven't checked in a while, they probably strip down the upstream source tarball09:59
LocutusOfBorgsince nobody is using the old location https://codesearch.debian.net/search?q=browser%2Fchromedriver10:05
LocutusOfBorgI think I will avoid the symlink10:05
LocutusOfBorghttps://paste.ubuntu.com/p/5TQn4kBMv6/10:18
LocutusOfBorgoSoMoN, ^^ it takes more time for the debdiff than for the patch itself...10:18
oSoMoNLocutusOfBorg, note that the description of bug #1667208 is incorrect, it says "/usr/lib/chromium/chromedriver" but it's "/usr/bin/chromedriver"11:31
ubottubug 1667208 in chromium-browser (Ubuntu) "Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu" [Undecided,Confirmed] https://launchpad.net/bugs/166720811:31
LocutusOfBorgtrue...11:40
oSoMoNLocutusOfBorg, here is an updated diff, would you mind giving it a sanity check? https://paste.ubuntu.com/p/mdzS9BGmVt/11:43
LocutusOfBorgyes, I like it!11:44
LocutusOfBorgof course if it builds :)11:44
oSoMoNwait, I forgot the provides line11:45
oSoMoNadding it11:45
LocutusOfBorgoops true11:45
=== ricab is now known as ricab|lunch
=== caribou_ is now known as caribou
rbasakIn backporting certbot from Bionic to Xenial, dh_installsystemd no longer exists which I think is causing the timer and service to no longer be installed.13:55
rbasakSuggestions?13:55
rbasakHow were systemd services installed back then?13:56
LocutusOfBorgrbasak, hold on13:57
LocutusOfBorg dh-systemd | 1.29ubuntu4                 | xenial-updates/universe   | all13:59
LocutusOfBorg dh-systemd | 10.2.2ubuntu1~ubuntu16.04.1 | xenial-backports/universe | all13:59
LocutusOfBorgusing dh-systemd from backports should work...13:59
LocutusOfBorgrbasak, is it ok?13:59
LocutusOfBorganyway, you should build-depend on dh-systemd (>= 1.5) on control file, it wasn't part of debhelper at that time14:00
rbasakI can do that. Thanks!14:03
LocutusOfBorgin virtualbox/xenial I simply do dh --with systemd14:03
LocutusOfBorgand it should take care of mostly of it...14:04
rbasakI'll give that a try.14:04
rbasakI had completely forgotten about dh-systemd!14:04
LocutusOfBorgman dh_systemd_enable should give you the best answer :)14:05
LocutusOfBorgit took me a while to that back in time :)14:05
rbasakOh. It's in backports?14:07
rbasakThis is for an SRU.14:07
rbasakWill 1.29 be enough?14:07
rbasakIt's >= 1.5 of course ;)14:07
LocutusOfBorgnot sure, vbox uses virtualbox.service IIRC and it works14:08
rbasakIt looks like certbot.service got installed but not the timer.14:09
rbasakAnd the override_dh_installsystemd didn't run.14:09
rbasakBut I can trawl through the docs now. Thanks again!14:09
LocutusOfBorgoverride_dh_systemd_enable:14:16
LocutusOfBorg        dh_systemd_enable -p$(sname) --name vboxweb --no-enable debian/vboxweb.service14:16
LocutusOfBorgthis is what I did in vbox for non-standard services names14:16
LocutusOfBorgif it is non-standard naming you should anyway tell it how to enable14:17
rbasakdh_systemd_enable: Could not find "certbot.timer" in the /lib/systemd/system directory of certbot. This could be a typo, or using Also= with a service file from another package. Please check carefully that this message is harmless.14:25
rbasakMaybe I can just installed that manually with dh_install14:25
rbasak(well, certbot.install)14:25
rbasakThe certbot.service is ending up in the deb though.14:26
=== ricab|lunch is now known as ricab
Ark74ricotz, hello!19:43
Ark74I've being studiying the libreoffice ppa compilation/build.19:44
Ark74Is this a good place to ask about it?19:44
hggdhkenvandine: ping re. a few gnome packages and snaps19:44
kenvandinehggdh: pong19:47
hggdhkenvandine: we compared the installed snaps from a Disco RC with an upgraded-to-Disco install. The RC install brings in gnome-(calculator|characters|logs|system-monitor), while on the already-existing system these are all (Disco) packages19:48
hggdhkenvandine: even more, at least gnome-calculator is at a different version package x snap19:48
kenvandinehggdh: upgraded from what?19:48
kenvandinedisco has the devel series of the debs19:49
kenvandinethe snaps are built from the upstream stable series19:49
kenvandinewhich is still 3.30.x19:49
kenvandineonce that hits 3.32 the snaps will as well19:49
hggdhkenvandine: the upgraded system was Bionic->Cossmic->Disco19:50
kenvandinebionic shipped with those 4 as snaps not debs19:50
kenvandineso it should have the snaps instead19:50
kenvandinehggdh: could it have been an upgrade from a bionic system that was originally installed before bionic release?19:51
kenvandinethe switch to the snaps was pretty late19:51
hggdhmy snap list only shows gnome-common-themes19:51
kenvandinethey were seeded pretty late, so if you installed around beta you wouldn't have gotten the snaps19:52
hggdhkenvandine: it *might*, yes. I got the laptop in... Feb 2018, so before release19:52
kenvandineah, yeah they weren't seeded yet19:52
hggdhyeah19:52
kenvandineso they would have been there as debs19:52
hggdhk. Still, then, we now have two different paths -- older systems still carry the package, new ones carry the snap19:54
hggdhbut they are at different versions. The gnome-calculator package on Disco is 1:3.31.90-1ubuntu1, the snap (stable) is 3.3019:55
hggdh(edge does have a 3.31.90)19:55
kenvandineyeah19:55
kenvandinethat's the intent19:56
zimmerianso this is probably a larger apt / dpkg thign but on remove my symlink gets removed20:54
zimmeriannothing in post pre scripts20:54
zimmerianis this a known bug?20:54
zimmerianor could it be the upgrading package at fault?20:55
cjwatsonnot very clear what you mean - how is this symlink created?20:55
infinity^20:55
infinityNeed more info here.  What symlink, what package is being removed, does the package believe it exclusively owns that path?20:56
infinitydpkg makes no real distinction between links and files20:56
cjwatson(except for some details around symlinks vs. directories on upgrade)20:57
zimmeriank - let me look a bit deeper I think I may know what's going on - sorry and thanks20:57
cjwatsonCertainly if a symlink is shipped in a .deb then it'll be removed when that package is removed.20:57
cjwatsonIntentionally20:57
infinityOr if you replace a file shipped by a deb with a symlink.20:57
infinitySame story.20:58
zimmerianokay nope - still confused … so more info time - let me write this to be more clear and concise :-)21:01
zimmerianalright - I hope this helps21:06
zimmerianhttps://pastebin.com/bw1MpGDU21:06
sarnoldmaybe start with ls -l and dpkg -L output with the old version and new version of your package21:08
cjwatsonIt's possible that dpkg feels itself entitled to clean up the top-level directory (actually a symlink) when there was previously exactly one package using it and then that package was removed.21:09
cjwatsonNot really specific to /opt except that packages generally don't install under /opt but apparently this one does.21:09
zimmeriancjwatson: that is true - it is the only package afaik21:09
zimmerianand yes - I fig'd that but this is the only package using /opt :-)21:09
cjwatsonNot sure if there's a good way to avoid that here.21:10
cjwatsonIt's just generic "remove cruft that appears to be no longer used" code21:10
zimmerianhmm well I can create a stupid package with /opt/dont_delete_me or something21:10
zimmerianmaybe that'd work21:10
zimmerianbut curious if I should file this as a bug w/ debian21:10
infinityIt's not a bug.21:11
zimmerianafter I do actually test your theory - which seems to apply21:11
cjwatsonI mean you could, but I'm not sure how it would be fixable even in theory21:11
infinitydpkg will always remove a directory when the last package owning it is removed.21:11
infinity(if it's also empty)21:11
zimmerianinfinity: it's a symlink and there's other stuff that the symlink has -21:11
zimmerianit's a bug IMO21:12
zimmerian /other/moar_stuff does exist21:12
infinityIt might be a bug if it's non-empty and dpkg has decided to treat it as a file instead of a directory.21:12
zimmerianand so this has a larger impact21:12
cjwatsonThe question is how it could possibly be fixed without breaking lots of other stuff21:12
cjwatsonBut it's certainly not Ubuntu-specific, so if you wanted to pursue it then the proper place would be a bug report on Debian dpkg, yes21:13
zimmeriancjwatson: true but I'm hoping somehow a test -L can be used - dunno21:13
zimmerianthank you all!21:13
infinityIt's not about testing if it's a link and then not removing it.21:13
infinityIt's about resolving it, treating it as a directory, and then applying the directory tests.21:14
zimmerianwell to see if it is indeed because no other packages are using there21:14
infinity(if not empty, don't remove)21:14
infinitySo it does indeed feel like a bug in this case, if the target isn't empty.21:14
zimmerianyeah - I agree infinity but I think that would actually make it a bigger quest perhaps?21:14
cjwatsondpkg just tries rmdir/unlink and ignores stuff like ENOTEMPTY; it doesn't look before it leaps21:15
zimmeriannot sure of the cost of delving into each / every item to see if there's something else if it's a symlink21:15
cjwatson(if it has no remaining references to the thing)21:15
zimmerianand it makes some sense from the apt / deb side21:16
cjwatsonnothing to do with apt21:16
cjwatsonpurely dpkg21:16
cjwatsonwhether it's a bug or not21:16
infinityI mean, the word "bug" is perhaps not the right one here.  Misfeature. :P21:17
zimmeriancool - well thanks all - I'll see what I can find21:17
zimmerianhehehe true21:17
infinityI think it's behaving as expected (by the people who wrote it), but those people could be seen to be wrong, based on what a user might expect in this case.21:17
cjwatsonIt is mildly surprising, looking at the code, because it should try rmdir first, get ENOTEMPTY, give up before getting as far as the unlink that must have removed the symlink.  But I haven't often needed to look at this code so might be misreading something.21:18
infinitycjwatson: Or, the misfeature was fixed, and you're reading a newer version than he's using.21:18
infinityGuillem does have a nasty habit of improving dpkg occasionally.21:19
cjwatsonoh, I'm misreading21:19
cjwatsonrmdir would get ENOTDIR in that case, and then it falls through21:19
infinityAhh.21:19
infinityBut that also highlights a maybe-not-computationally-insane path to fixing it.21:20
infinityIf ENOTDIR, check linkiness, check contents of target, bail if not-empty.  *hand-wavy*21:20
cjwatsonMaaaaybe.  If there aren't legit cases that would break21:20
* cjwatson is happy for somebody else to think through that maze21:20
zimmerianwell I'll be - seems like way back this was a thing and well … still is21:21
zimmerianhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18274721:21
ubottuDebian bug 182747 in dpkg "dpkg should not remove a symlink to a directory unless it's empty" [Wishlist,Open]21:21
cjwatsonProbably means it's hard :)21:21
zimmerian…. and in true fashion - also /opt :-D21:21
infinityYeah.21:21
infinityThe real answer here might be to admit that /opt is a thing and ship it in base-files. :P21:21
infinitygoogle packages have similar potential issues.21:22
infinityMy hot take is that as soon as something is in deb/rpm form, it should be installing to system locations, not /usr/local or /srv or /opt, but obviusly there are those who disagree, and plenty of packages in the wild to prove it.21:23

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