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

=== BrAsS_mOnKeY is now known as g2
sarnoldWhat could cause this? https://gist.github.com/11619c37f334005d1681295aa940d8dd a guy in #ubuntu-server got "Processing triggers for systemd (229-4ubuntu19) ... dpkg: error: dpkg status database is locked by another process" from an apt-get install03:34
tsimonq2sarnold: first thought that comes to mind (just a theory) is unattended-upgrades being triggered and it steals the lock03:38
tsimonq2I would consider that a bug if unattended-upgrades actually did that, but you never know...03:38
julianktsimonq2: Yes, that can happen.03:48
julianksee https://lists.debian.org/debian-dpkg/2017/01/msg00044.html03:48
tsimonq2juliank: Oh ok, so I'm not far off ;)03:49
tsimonq2That's interesting03:49
tsimonq2Thanks for the link!03:49
sarnoldjuliank: thanks03:50
sarnoldI'm reminded of https://deadlockempire.github.io03:50
tsimonq2sarnold: hahahahahahaha03:52
=== JanC_ is now known as JanC
seb128hum, in artful when I use "debuild clean" I get08:32
seb128"dpkg-buildpackage: error: unknown option or argument clean"08:32
seb128is that me using tools wrong or a bug?08:33
saryreporting bugs in 17.10 concerns #ubuntu+1 , -devel , or both!08:54
mbieblI got an issue with ibus under 17.0408:55
seb128hum, python packaging question08:55
seb128if a package is shipping python files to a private dir, is it useful to byte compile those and if so is that something the tools can do for you or that you need a postinst/rm for?08:56
mbieblwhen I log out, I still have an ibus-daemon (+ ibus-dconf and ibus-engine-simple) process08:56
mbieblwhich don't want to exit08:56
mbieblso the logind session is not stopped08:56
seb128or asked differently is there a better way to do what https://github.com/fossfreedom/alternative-toolbar/blob/debian/debian/postinst is doing? (that was raised as weird in a review)08:56
mbieblunfortunately, ibus can't easily be uninstalled08:56
seb128mbiebl, is that https://bugzilla.gnome.org/show_bug.cgi?id=764029 ?08:56
ubottuGnome bug 764029 in general "goa-daemon (and most other D-Bus services) not stopped when the user session goes away" [Critical,New]08:56
mbieblseb128: those are systemd user services08:57
mbieblas long as a session scope is still active, those services are not stopped08:58
sarywell, this just happened , https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/170957208:58
ubottuLaunchpad bug 1709572 in system-config-printer (Ubuntu) "system-config-printer.py crashed with ValueError in require_version(): Namespace Secret not available" [Medium,New]08:58
seb128sary, launchpad is the right place to report bugs, no need to ping about them on IRC as well08:58
mbieblso the problem is, that a process from the session does not want to die on logout08:58
saryseb128: Noted. thank you!08:59
mbieblseb128: couldn't find a but about this ibus issue in the debian bts or launchpad08:59
mbiebla bug...08:59
seb128that's the first time I saw it mentioned I think09:02
mbieblseb128: it's an ibus bug i'd say09:08
seb128happyaron might know09:09
=== rumble is now known as grumble
rbasakjuliank: opinion on bug 1709603 please? This is in response to a few people in Canonical agreeing and asking what we can do to make it happen.11:32
ubottubug 1709603 in apt (Ubuntu) "apt {upgrade,install} require an update call first" [Wishlist,New] https://launchpad.net/bugs/170960311:32
rbasak(and I haven't yet heard any dissenting opinions apart from yours)11:32
Unit193There's already a freaking timer, why on earth would...OOh nevermind, as long as it's easy to disable it's not the end of the world anyway.  Just another thing to fix...11:34
Unit193rbasak: Thanks for the LE srus.11:34
rbasakUnit193: you're welcome. Are you suggest some improvement to adding the systemd timer in the SRU?11:36
rbasak*suggesting11:36
Unit193rbasak: No, unrelated topics.  Apt does pretty well now of keeping the indexes up to date, an 'automatic' call to 'update' is excessive.11:39
rbasakUnit193: how so?11:39
juliankrbasak: It's really one of the things that annoys me the most when using yum and friends. We update the indices automatically once per day any way; the only time this would really have any effect is after a new installation (or on systems not using unattended-upgrades).11:40
rbasakUnit193: my main issue is the call of "apt install ..." on a fresh instance, such as a container. It's a very common case (anyone doing "cloud" anything, really).11:40
rbasakjuliank: right, but that's a very common case.11:40
persiaPerhaps the sensible solution is to add an `apt update` call to the installer, after the archive mirrors are selected?11:41
Unit193rbasak: Ah, well if the recommendation is to ship an apt config snippet in one of the cloud packages, fine by me.11:41
rbasakjuliank: what if --is-necessary did not update if less than a day old? Then my proposal wouldn't introduce any functional change except in the failure case.11:41
rbasakpersia: that unnecessarily slows down the boot of cloud instances.11:41
rbasakpersia: or introduces a race in the system being ready to accept an "apt install", which is immediately necessary in this use case.11:42
rbasakUnit193: I think the config snippet would need to be Ubuntu-universal. We don't want a behaviour difference between Ubuntu on cloud and not-cloud by default. That's be infuriatingly confusing.11:42
persiarbasak: I thought the issue was that `apt install` didn't work on first install because the indecies were out of date.  I leave you to your previously planned work.11:42
juliankI don't really see how spawning a new cloud instance and then immediately having to run apt manually is a common thing to do. I'd expect people to script their cloud building, and then it's easy to add an update command first11:43
Unit193Better than the proposed option..11:43
rbasakpersia: I want 1) if I start a container for development, it starts straight away; 2) if I subsequently run "apt install", it does the necessary things. It's not possible to have both if cloud-init blocks on updating apt first.11:43
rbasakjuliank: it's a common thing to do when developing or debugging any automation.11:44
persiarbasak: So, automatically update the indices if they are too old or something?11:44
rbasakpersia: correct. Automatically on "apt install" or "apt upgrade".11:44
rbasakThat's what I want.11:44
mdeslaurI'd really hate for 4 apt installs in a row to download the indices each time11:44
persiaFor folk running production series, it oughtn't matter: the non-updated versions should be self-consistent for installation, even without a refresh of the updates.  Updates would become available at first time check.11:45
rbasakFolks running production expect the initial deployment to include all security updates.11:46
persiaPerhaps, for the short-lived use case, it would be appropriate to check for updated packages a few minutes after boot, or similar.11:46
rbasakThis requires a local index update.11:46
juliankI think that having an option like -u but disabled is a better choice. That's how paca11:46
juliank*pacman works11:46
persiarbasak: If the initial install is to have the security updates, the solution is to A) have the installer do the updates or B) if using image-based instantiation, update the image on every publisher run.11:47
juliankand automatically do the update if there are *no* lists11:47
persiaAnything else means that the deployed instance has a security problem most of the time.11:47
juliankSo apt install foo will run update on first apt use; and apt install -u foo will run update unconditionally11:48
rbasakjuliank: that may be sufficient for my failure cases.11:48
persiaThat implies the deployed image has a window of vulnerability (between deployment and update), which may not be very useful for short-lived images.11:48
rbasakThough it depends on unattended-upgrades not being configured away from the default, and that dependency is IMHO surprising to users.11:49
juliankI'm not sure how to make that no lists part work best with cdrom:// though11:49
rbasakjuliank: perhaps disable all of this if cdrom:// is present?11:49
persiaThat makes use of cdrom:// inherently less secure.11:50
rbasakSo deprecate it.11:50
juliankrbasak: Maybe this, or maybe we should just ignore cdrom:// URIs and check if "all (other) sources are missing"11:50
rbasakThat'd work fine for my case I think.11:50
rbasakjuliank, persia, Unit193, mdeslaur: thank you for the discussion. Some good ideas on adjustments.12:23
nacc@pilot in15:09
=== udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: nacc
slangaseknacc: were the build profile patches for php-directory-scanner sent upstream to Debian?15:37
naccslangasek: hrm, it looks like I didn't send it, but all of the infra for building the php* has been adjusted to be better capable of handling the upgrades (or building with two different versions). I expect it'd be ok to sync if you want -- or I can submit those to Debian15:42
slangaseknacc: your call15:43
naccslangasek: go ahead and sync it15:43
slangasekdone15:44
naccslangasek: if i'm reading the update_output.txt correctly, does php7.1 getting skipped mean that cacti-spine and php7.1-snmp become uninstallable with the binaries from src:php7.1 on s390x? but php7.1-snmp is from src:php7.1 itself15:48
slangaseknacc: on update_excuses, Depends: php7.1 net-snmp15:51
slangaseknacc: so php7.1 and net-snmp have to go in together; if there's a relevant 'Trying easy from autohinter' in the update_output, that will be more instructive15:52
slangaseknacc: and I see that net-snmp is in the big hint15:53
slangaseknacc: so doko's gcc-7 is blocking you ;)15:53
slangasekoSoMoN: hi, I see that libreoffice amd64 autopkgtest fails with gcc-7 because of new warnings (and stderr output considered a failure).  I will be overriding this test for the toolchain transition, which means libreoffice/amd64 autopkgtests will be failing in the meantime.  Would you be the person to fix this failure?16:39
bdmurrayslangasek: Any ideas about why test_is_child_of_process_name in update-manager would fail on !amd64 or !i386? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/u/update-manager/20170808_003647_cf6bd@/log.gz16:41
slangasekbdmurray: !amd64 !i386, or !s390x !armhf?16:46
slangasekbdmurray: it might be that pid1's name is different inside of a container16:46
bdmurrayslangasek: it fails on s390x too16:47
slangasekbdmurray: sorry, I meant "!amd64 !i386, or s390x armhf" - yes, I checked the ppc64el failure and it seems unrelated; so this test fails on the two container archs so I guess that's the difference16:48
slangasekbdmurray: http://paste.ubuntu.com/25277940/16:50
naccslangasek: got it, thanks, would that also cover cacti-spine?16:54
slangaseknacc: I imagine so16:54
naccslangasek: ok, i'll let that sit for a bit, then16:54
bdmurrayslangasek: hrm, these tests test function in update-manager's utils.py but update-manager doesn't use them ubuntu-release-upgrader does.16:55
slangasekbdmurray: should they be moved to python3-distupgrade, then?17:00
bdmurrayslangasek: I think they should be moved because I was thinking about removing the functions and the tests but I don't know if its a priority.17:02
slangasekbdmurray: at the very least, I don't think a test testing the name of pid1 is a good test17:04
bdmurrayslangasek: sorry, could you elaborate?17:05
slangasekbdmurray: sorry, now reading the test and code and need to re-collect my thoughts, because my pid1 on zesty host is also /sbin/init so why would it be have differently17:08
slangasekbdmurray: but generally, the point I'm trying to make is that the test is asserting things about the system, not about the correctness of the code under test17:08
slangasekbdmurray: a proper test of this code would mock /proc17:09
bdmurrayslangasek: okay17:11
oSoMoNslangasek, yes, that would be me17:22
oSoMoNputting that on my list17:22
slangasekoSoMoN: thanks17:28
slashdIs there any coredev who have some cycle atm to sponsor a patch for logrotate in devel release (artful) ? then I'll be able to proceed with the upload myself for stable release.18:32
naccslashd: yeah, do you have a bug open?18:33
naccslashd: i'm piloting right now anyways (see /topic)18:33
slashdnacc, https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/170967018:33
ubottuLaunchpad bug 1709670 in logrotate (Ubuntu Artful) "logrotate never recovers if the statefile is corrupted" [Medium,In progress]18:33
naccslashd: ok, i'll do that one next18:33
slashdnacc, thanks much appreciated18:33
slashdnacc, I'll take care of the SRU afterward18:33
naccslashd: sounds good18:34
naccslashd: iiuc, then, you don't need sponsorship to the sru series, right?18:59
slashdnacc, right I can sponsor myself on sru series18:59
naccslashd: ack, unsubbing sponsors thanks!19:02
slashdnacc, thanks19:03
=== Pharaoh_Atem is now known as Conan_Kudo
=== Conan_Kudo is now known as Pharaoh_Atem
naccslangasek: question re: src:numactl. I thnk we can technically sync it, except that debian dropped the arch-specication for the binary packages in favor of linux-any in 2.0.11-2.1. It specifically says 'armel and armhf are still not supported'. We don't currently build numactl on armhf anyways, but I assume for our purposes that will show up as  FTBFS?19:24
naccslangasek: and so we do need to keep delta that switches from linux-any to the explicit list of architectures we know it builds on?19:25
nacc@pilot out19:25
=== udevbot changed the topic of #ubuntu-devel to: Zesty Released | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-zesty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots:
slangaseknacc: it's fine for the package to be FTBFS on those archs; it wastes some builder time to try to build it and fail, but that's not usually worth carrying a delta19:26
Unit193nacc: Thanks!19:27
naccslangasek: ok, good to know, thanks!19:28
kyoderwhen I report a crash in ubuntu, is it better to turn that off after one report, or do the stats increase when I keep sending the same report?19:44
tyhicksbdmurray: hey! I'm curious about the answer to kyoder's question and I suspect that you may know it ^19:49
bdmurraykyoder: If you are using a stable release of Ubuntu (e.g. 16.04, 17.04) then the stats do increase, if you are using a development release of Ubuntu (Artful Aardvark) then the stats, in Launchpad, do not increase20:09
tyhicksthanks20:10
kyoderthanks bdmurray20:17
kyoderand tyhicks20:17
tsimonq2nacc_: yay patch pilot \o/20:26
nacc_tsimonq2: i might do some more later today, just stopping for lunch20:29
=== nacc_ is now known as nacc
tsimonq2:D20:31
bdmurrayjdstrand: what release did you discover bug 1707645 on?20:34
ubottubug 1707645 in util-linux (Ubuntu) "system with high numbered uids has huge sparse /var/log/lastlog" [Undecided,New] https://launchpad.net/bugs/170764520:34
slangasekhmm, if it's sparse, why is that a problem?20:50
slangasekoh, non-sparse rsync20:50
slangasekdoesn't seem like something we'd try to fix in util-linux; the format of /var/log/lastlog is fossilized20:51
Unit193cpaelzer: Oh, g'luck on core-dev!21:00
ahasenackjust checking, but a package in main cannot have a build-depends on something that is in universe, right?21:17
sarnoldahasenack: it was changed to be more nuanced; it's okay if it is strictly build-time, but if it results in binary package .. dependencies? changes? .. then the dep should be dropped or the universe package brought nito main21:19
Unit193IIRC, it can if it's only a *buildtime* depend, eg doesn't link to it.  I may be wrong.21:19
ahasenackhm21:19
ahasenackok, good21:19
ahasenackI'll check that21:20
ahasenackwhat about if it's for DEP8 tests?21:20
sarnoldahasenack: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2016-April/001179.html21:20
Unit193Of course, sarnold beats me and says it better. \o/21:21
ahasenacktry apt autoremove21:22
ahasenackit should do the right thing. But double check21:22
ahasenackI think it will even leave one kernel behind installed, in case you need to downgrade21:22
sarnoldahasenack: heh, I think you meant for those to go to #ubuntu-server instead? :)21:23
ahasenackoh, wow21:24
ahasenackit must be late :)21:24
valoriepersia: looooooooooooooooooong time, no see! o/21:24
ahasenackok, I think thid builddep that debian added (libcmocka-dev) is used only for tests21:25
ahasenackbut I have to check for real. grep shows it only being used in test files21:25
ahasenackbut I'll want to check the final build with ldd and the Depends header of the built package21:26
jdstrandbdmurray: artful21:49
=== Foxtrot is now known as foxtor
=== foxtor is now known as foxtrot

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