/srv/irclogs.ubuntu.com/2017/07/28/#ubuntu-devel.txt

=== klebers__ is now known as klebers
=== bigon_ is now known as bigon
tsimonq2sil2100: Hey there! Do you mind if I attempt to merge isdnutils from Debian?08:03
sil2100tsimonq2: hey! Sure thing, thanks!08:04
rbasakCan anyone help with my review question at https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1698553/comments/6 please, in order to accept an SRU? SRU hat not required. It's a powerpc vs. autoconf question.08:13
ubottuLaunchpad bug 1698553 in gjs (Ubuntu Zesty) "Update gjs to 1.48.5" [High,In progress]08:13
xnoxrbasak, i'm not sure i can tell which way around the diff is =) where is the patch that is mentioned in that comment?08:19
xnoxI'm expecting the diff to look the other way around, like it does in e.g. http://launchpadlibrarian.net/318604762/gjs_1.48.2-0ubuntu0.1_1.48.3-0ubuntu0.1.diff.gz08:19
rbasakOne moment. I'll pastebin the exact patch08:20
xnoxinstead of removing ppc*, it should be added by most recent autoreconfery. A good check is to run up build target to make sure reconfery has both powerpc* and ppc*08:20
xnox(ppc* is the newer 64bit stuff, rather than the old powerpc* stuff)08:20
rbasakOh, I don't have it here.08:20
xnoxif it was $ diff new old -> then it's fine =)08:21
rbasakhttp://launchpadlibrarian.net/324981111/gjs_1.48.3-0ubuntu0.1_1.48.5-0ubuntu0.1.diff.gz08:21
rbasakdiff -Nru gjs-1.48.3/aclocal.m4 gjs-1.48.5/aclocal.m408:21
rbasakIt's old new08:21
rbasak-x86_64-*kfreebsd*-gnu|x86_64-*linux*|ppc*-*linux*|powerpc*-*linux*| \08:22
rbasak+x86_64-*kfreebsd*-gnu|x86_64-*linux*|powerpc*-*linux*| \08:22
rbasakThis is what bothered me.08:22
rbasakThough I appreciate that autoreconf might replace that.08:22
xnoxwhere can i download pull this new package to check that?08:23
rbasakThere are also various replacements of https with http, which does suggest it's going backwards somehow08:23
rbasakxnox: expand https://launchpad.net/ubuntu/zesty/+queue?queue_state=108:23
xnoxtah08:23
xnoxlooks like the tarball was generated with non-patched / out of date config.sub; rebuilding now with extra debug to see if autoreconf is actually done or not.08:26
xnox   dh_update_autotools_config08:28
xnox   dh_autoreconf are both run.08:28
xnoxcat config.sub, shows timestamp='2016-11-04' so all is good.08:29
xnoxstill a bit sad that a point release tarball is generated with very old configury.08:29
rbasakxnox: so it's all in config.sub, and I know what to look at to confirm this for next time. Thank you for your help!08:33
tsimonq2sil2100: bug 1707146 :)08:42
ubottubug 1707146 in isdnutils (Ubuntu) "Merge 1:3.25+dfsg1-8 from Debian Sid" [Undecided,In progress] https://launchpad.net/bugs/170714608:42
LocutusOfBorgjbicha, feeling dbus mergy?09:05
LocutusOfBorgyou have 15 merges in main with your name :)09:05
LocutusOfBorgprobably some of them can go syncd09:06
=== zyga-ubu1tu is now known as zyga-ubuntu
rbasakI've prepared documentation for an SRU exception for Certbot at: https://wiki.ubuntu.com/StableReleaseUpdates/Certbot10:31
rbasakReviews appreciated.10:31
apwrbasak, looks reasonable to me10:59
rbasakapw: thanks!11:23
=== dobey_ is now known as dobey
rbasakcyphermox: I still have bug 1624519 in my blocked list. Do you have a plan for that please?11:54
ubottubug 1624519 in tasksel (Ubuntu Artful) "Debian-defined tasks override Ubuntu-defined ones" [High,Triaged] https://launchpad.net/bugs/162451911:54
jbichaLocutusOfBorg: no, the main ones probably can't be synced, but yes I'm going to handle dbus12:08
jbichayou can take usb-modeswitch if you want, I don't feel like dealing with the rewrite-in-C patch again :|12:13
cyphermoxrbasak: should get to it today, are you saying this is critical to what you're doing?12:32
=== roaksoax_ is now known as roaksoax
rbasakcyphermox: no, to be clear, I'm not blocked. But I think we should get it done this cycle.12:38
rbasak(so before FF)12:38
rbasakI suppose I did say it's on my blocked list.12:38
cyphermoxdoesn't seem to me like this is to be before FF12:38
cyphermoxit's a bug12:38
rbasakFair enough.12:39
cyphermox(well, like I said though I'll probably get to it today)12:39
rbasakWhat I meant by blocked is that it's on my TODO and I'd prefer not to go further without your input, so I'm blocked from proceeding rather than it blocking something else.12:39
rbasakSorry I'm being confusing.12:40
cyphermoxit's already assigned to me and milestoned, I think you could remove it from your TODO :)12:40
cyphermoxit seems like a straightforward rm of the offending files, in any case12:40
LocutusOfBorgjbicha, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/8119633/+listing-archive-extra12:50
LocutusOfBorgthis was really trivial, I dropped an Ubuntu patch and didn't touch that rewrite-in-C stuff, it builds correctly12:50
LocutusOfBorgnot sure if it is enough to say it works12:50
LocutusOfBorgwas it a FTBFS fix? or a dependency avoidance in main-fix?12:51
ahasenackrbasak: hi, good morning. Procedure question12:56
ahasenackrbasak: slangasek uploaded ubuntu-advantage-tools to trusty-proposed yesterday, as part of bug #1686183 (see last comment)12:56
ubottubug 1686183 in ubuntu-meta (Ubuntu Artful) "Ship ubuntu-advantage in ubuntu-minimal" [Undecided,New] https://launchpad.net/bugs/168618312:56
ahasenackrbasak: it's showing up in https://launchpad.net/ubuntu/trusty/+queue as NEW, and in universe, not main12:56
ahasenackand I don't see it in trusty-proposed yet12:57
ahasenackso I'm guessing it has to be approved, even though it was slangasek who uploaded it?12:57
ahasenackin precise it's in main, I thought it would be in main for the other distros in this forward-copy12:57
jbichaLocutusOfBorg: dependency avoidance13:04
rbasakahasenack: packages always start off in universe. They have to be moved to main by an archive admin after they're in the archive, usually in response to the component mismatch report, whose results are based on the seeds to decide what should be in main.13:06
ahasenacktl;dr, ping slangasek when he gets online? :)13:07
rbasakI'm not sure what is intended in this case in relation to the seeds, but what you're observing makes sense to me.13:07
rbasakYes :)13:07
ahasenackok, got it wrt new packages13:07
rbasakSeparately, we don't usually have a sponsor (or the uploader) also wear an SRU hat, so I assume slangasek is awaiting SRU review from someone else as he did not upload with that hat.13:08
rbasakConvention is to not wear both hats, as that ensures a two person review for things going into the stable releases.13:08
rbasak(where one person is ~ubuntu-sru and a separate person is a DMB-approved uploader)13:09
infinityPackages don't always "start in universe", this is just a screw-up on the part of the person who accepted it originally.13:10
* infinity twiddles.13:10
rbasakI thought it hasn't been accepted yet, and ahasenack is reporting what the queue entry shows?13:10
infinityrbasak: The source was accepted, and should have been overriden to main before it was.  Then the binary currently in NEW would have also defaulted to main.13:11
ahasenackrbasak: the bug has the normal sru notification already13:11
infinityWhich I'm also fixing.13:11
ahasenackthx13:11
ahasenack"please test this package that should be in proposed in a few hours", blabla13:11
infinityAnd there.  Now it's in main in the queue.13:11
infinityAnd I guess I should review the binary and accept it too. :P13:12
rbasakOh, I see. I had assumed the source was in new.13:12
infinityahasenack: And copied forward to {xenial,zesty,artful}-proposed as well.13:23
ahasenackthanks13:23
* ahasenack checks trusty13:23
ahasenackhm, I should switch to the main archive instead of the country mirror13:24
infinityahasenack: It'll need verification on all of T, X, Z, despite it being the same binary.  Cause each one might behave differently with pam-motd, etc.13:24
ahasenackthat's ok13:24
infinityahasenack: Also, mirror patience.  When I say I copied it, I mean in LP, it's not on disk anywhere yet. :P13:24
ahasenackplenty to do until that happens :)13:24
ahasenackbetween the time I made an MP and now, the patch I forwarded upstream (via email) was merged13:36
ahasenackshould I update the DEP3 header? I used Author (myself), forwarder (yes, emailed foo), and bug links13:36
ahasenackhow should I record that it was merged upstream: origin http://<commiturl>, and/or replace forwarded with the commit url?13:37
ahasenackor something else?13:37
rbasakSo the MP has not been reviewed/uploaded yet?13:39
rbasakI'd update the dep3 header as that information is useful during a future merge.13:39
rbasakI think replacing the Forwarded URL makes sense. I wouldn't object to rewriting the Origin field though.13:40
rbasakOh13:41
rbasakEven better13:41
rbasakThere's an Applied-Upstream field13:41
rbasakSo you could leave everything else as-is and just add that with the upstream commit URL.13:41
ahasenackrbasak: correct, the mp hasn't been sponsored13:41
rbasakAlso there's a Last-Update field.13:41
ahasenackit was reviewed by cpaelzer13:41
* ahasenack checks applied-upstream13:41
ahasenacklast-update I updated13:41
ahasenackrbasak: this is the mp, btw: https://code.launchpad.net/~ahasenack/ubuntu/+source/libpam-ccreds/+git/libpam-ccreds/+merge/32782913:42
ahasenackI like applied-upstream13:43
ahasenackI think it conveys better the info that the patch was created, then forwarded, then accepted13:43
rbasakI agree13:43
ahasenackotherwise origin could mean that it was grabbed from upstream13:43
ahasenackok, thx, will add that and update Last-Update13:43
rbasakYeah and then there's an added complication if upstream changed it. So Applied-Upstream works best. Nice that it exists :)13:44
LocutusOfBorgjbicha, ok for dependency avoidance, but "it builds so it is fine"? or "it might break at runtime13:45
LocutusOfBorg"13:45
jbichaLocutusOfBorg: I just don't want to be responsible for it, I don't have the hardware, etc. :)13:55
jbichathanks14:18
slangasekrbasak, ahasenack: I accepted that source because I was sponsoring an upload that only differed from the previously-uploaded version by a fix that was identified in the previous queue review14:18
ahasenackslangasek: I think it's all good now, package is in trusty-proposed already and I'm testing14:19
ahasenackslangasek: this SRU is mostly for "book keeping" purposes, if I may use that term?14:19
=== santa is now known as Guest5096
ahasenackI know there are future plans for this tool (and I was in fact given a few tasks about it already), but right now it's just to have it available in all distros?14:20
slangasekahasenack: well, in part it's to make sure that on upgrade the precise package doesn't continue to tell users that they're EOL and should install ESM :)14:21
rbasakslangasek: that makes sense. I didn't mean to be accusing you, just explaining the general principle having assumed that ahasenack was asking about a source that hadn't been accepted. I should have looked.14:22
slangasekk :)14:23
ahasenackslangasek: hm, the motd14:23
ahasenackok, that's a good fix14:23
ahasenackI had forgotten about it,14:23
ahasenackbecause it's not mentioned in the test case14:23
ahasenackwhich I will update, of course14:25
=== grumble is now known as grumble2
=== rumble is now known as grumble
smoseri'm interested in thoughts on this bug16:24
smoser 16:24
smoserhttps://bugs.launchpad.net/ubuntu/+source/systemd/+bug/170722216:24
ubottuLaunchpad bug 1707222 in systemd (Ubuntu) "usage of /tmp during boot is not safe due to systemd-tmpfiles-clean" [Undecided,New]16:24
smoserxnox, ? rbalint ? it seems to me that there is basically no way to safely use /tmp. because there is no (easy) way to know that systemd-tmpfiles-clean is done running.16:28
smosercloud-init can choose to use tmp files in /run, but isn't possible for everything and has other questionable bits16:43
xnoxsmoser, correct, you should be using /run. What are you using /tmp for? is it too big for /run?17:00
* xnox goes to read the bug17:00
smoserxnox, size isn't really a concern.17:00
smoserbut if you're not running as root, ....17:00
smoserwhich i think is considered a good idea in many cases.17:01
smoserhow do you use /run ?17:01
=== alan_g is now known as alan_g|EOW
xnoxsmoser, in the bug, you say, you use it to mount things hence i assume priviledged. If you are not root, you have a few options:17:01
smoserand saying "use /run if it isn't too big" doesnt solve this problem if it *is* to big.17:01
xnox1) start a pam session, and thus use XDG_RUNTIME_DIR17:02
xnox2) specify runtime directory in the systemd unit17:02
smoseryeah... i can fix this for cloud-init by using /run17:02
smoserbut this seems a generic problem to me.17:02
xnoxsmoser, /tmp is not guaranteed to be large either, and can be smaller than /run. We actually do not gurantee sizes for either. As per file system hierarchy if /tmp is not large enough use /var/tmp17:03
xnoxor /var/cache17:03
smoserthere is no guarantee *ever* that if you amke a file in /tmp it wont just get cleaned up by systemd17:03
xnoxsmoser, and equivalent XDG_CACHE_DIR I think or soemthing for the user.17:03
xnoxsmoser, we can look at when the systemd-tmpiles-clean is run. it should be run before system is considered up.17:04
lotus|artfulboxhey guys, just letting you know this older bug still exist in 17.10 https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/156315517:04
ubottuLaunchpad bug 1563155 in gnome-software (Ubuntu) "No Application Data Found" [High,Confirmed]17:04
xnoxthus if you wait until systemctl is-system-running you are golden - which is when mere mortal users are allowed to login into the system and do things.17:04
lotus|artfulboxfixxed with installing language support #4617:04
xnoxi understand that cloud-init is very quazy here, as it integrates into the first boot, and thus it is not a normal mere mortal user that should be guranteed a non-evaporating /tmp.17:04
dreamcat4sometimes when i run the installer, it leaves /target mounted (and I cannot unmount it). other times its unmounted17:05
xnoxsmoser, is that fair, or not really?17:05
smoserxnox, why do you say " if you wait until systemctl is-system-running"17:05
smoserwhat guarantees that ?17:05
smoserall i see is 'Beforeo=shutdown.target'17:05
xnoxsmoser, also in systemd, you can set PrivateTmp on cloud-init untis, and then you will get your own /tmp just for you, which will be guaranteed to be there whilst you are running.17:05
xnoxsmoser, it's in a separate mountpoint, masquaraded for you onto /tmp, but is actually /tmp/systemd.tmpBLA17:06
xnoxsmoser, i think the easiest for you is to use PrivateTmp in the systemd unit, and not change any cloud-init code.17:06
xnoxhttps://www.freedesktop.org/software/systemd/man/systemd.exec.html#PrivateTmp=17:07
smoserthat seems possible for cloud-init.17:07
xnoxthat will give you persistent /tmp /var/tmp.17:07
smoserbut what guarantees " if you wait until systemctl is-system-running you are golden"17:07
xnoxi'm not sure how that works across multiple units. You may need extra if you want a.service to be able to access b.service privatetmp.17:07
smoserbecause i dont think that is true.17:07
smoserif i filled up /tmp with thousands and thousands of files17:08
smoserand rebooted17:08
smoserthat could take hours to clean17:08
xnoxsmoser, actually, it seems like it cleans things daily. thus no one is not guaranteed anything w.r.t. to /tmp.17:09
smoseryeah, i saw that too17:09
smoserthat is even worse17:09
xnoxPrivateTmp is the way to go, as PrivateTmp stays active for the duration of the unit.17:09
smoseri assumed i was just reading something wrong17:09
smoserand actually.. my experience is that it does not run daily17:09
smoser(which is good imo)17:09
xnoxhorum. i shall check if the timer unit is in fact activated by default on ubuntu, rather than just available.17:10
smoser(an ls on /tmp on my artful system shows files from July 17)17:10
xnoxit does it when thigs are quiet =) IOSchedulingClass=idle17:10
smoserstill seems probably broken17:10
smoserany definition of 'idle' would surely have included last saturday night at 3:00 am on my system.17:10
xnoxsomething is wrong.17:10
smoser(or right)17:11
smoserdepending on whether or not you want to allow people to use /tmp17:11
smoser:)17:11
xnoxsmoser, cause the unit is active on my system, my uptime 29 days, and i have loads of old crap in /tmp17:11
smoseri think that : if you use /tmp, your files might be deleted. is probably a bad policy17:11
smoserso i can use PrivateTmp for cloud-init, even though, annoyingly "the unit should be written in a way that does not solely rely on this setting"17:12
xnoxsmoser, eeeeh, that unit doesn't clean _all_ of /tmp17:12
xnoxsmoser, it only cleans things older than age, as specified in the tmpfiles.d config snippets.17:13
xnoxe.g.:17:13
smoserwell that is at least better policy.17:13
xnoxd /var/lib/systemd/coredump 0755 root root 3d17:13
xnoxso coredumps are gone, that are older than 3 days.17:14
xnoxthe '3d' is the setting.17:14
xnoxd /var/cache/man 2755 man root 1w17:15
smoserxnox, so ... if i'm understanding that right, then the problem i think i saw would in theory not be possible.17:15
xnoxseems odd, but not sure. i thought we should not clean man page cache.17:15
xnoxsmoser, yeah, we need logs.17:15
xnoxsmoser, and a dump of tmpfiles.d config from /run, /etc, /usr/lib to exclude tmpfiles.d culprit.17:15
smoseri saw this.. but then today someone sent me a email that seemed to smell very similar17:16
xnoxsoemthing can write 'd /tmp - - - 1s' to wipe things older than 1s in /tmp17:16
smoser"So, in our open-vm-tools.service file, we have added the dependency for it to run before cloud-init.17:16
smoserNow, if we do that (which is run open-vm-tools before cloud-init) we are not able to read files from /tmp folder"17:16
xnoxi want emails, details, logs, steps to reproduce. btw - i have just merged open-vm-tools in artful, no?17:17
smoseri dont know.17:17
xnoxso if this started recently, that maybe my bad merge.17:17
smoserwell i saw this on azure on zesty.17:18
smoserbut i didn't keep logs17:18
smoserbut the logs were just "no such file or directory". i dont htink i kept the systemd journal.17:18
xnoxazure had clock scew bugs =/17:20
xnoxnot sure if they mount /tmp on /tmpfs17:20
smoserindeed it does. and no they dont change /tmp mount (i'd hope)17:20
xnoxas then one will need to order oneself after tmpfs is setup, if one is without default dependencies.17:20
xnox(which is the case for cloud-init units - no default deps)17:21
ahasenackslangasek: hey, while verifying #168618317:56
ahasenackslangasek: I'm seeing that "sudo ubuntu-advantage enable-esm <token>" half works on non-precise and I'm wondering if that's a problem for this particular SRU17:56
ahasenackslangasek: the command creates that new sources.list.d/ file with the <token>, for the current ubuntu release, and then runs apt-get update17:57
ahasenacksince esm is not available for anything other than precise, apt-get update fails with a 404 when contacting the esm repository17:57
ahasenackand will keep failing until esm is disabled again on that non-precise machine17:57
=== JanC is now known as Guest48595
=== JanC_ is now known as JanC
slangasekahasenack: I think that's fine at this point18:51
slangasekahasenack: we haven't really defined what the experience should be for that on non-ESM releases18:52
ahasenackslangasek: cool18:53
juliankxnox: re bug 1686470: Did you actually check that libapt-pkg5.0 was upgraded in zesty? That's where the fix  - I thought I wrote this in the bug, but it seems to got lost or something (or did you see anything?)20:27
ubottubug 1686470 in unattended-upgrades (Ubuntu Artful) "Apt updates that are uniformly spread across all timezones, with predictable application windows" [High,Triaged] https://launchpad.net/bugs/168647020:27
juliankEhm, no, different bug20:27
juliankAh it was bug 169469720:28
ubottubug 1694697 in apt (Ubuntu Trusty) "build-depends keeps OR flag if end of or group is ignored" [Undecided,New] https://launchpad.net/bugs/169469720:28
juliankSorry, I see the message in LP now that I look in the right bug report :)20:28
xnoxjuliank, ah, maybe not. i can check.20:29
xnoxjuliank, verification done.20:31
xnoxjuliank, now i need to redo zesty again to check what's going on with not activating the timer units by default.20:32
=== ikonia_ is now known as ikonia
LocutusOfBorgjbicha, please, don't open another bug against xmonad21:00
LocutusOfBorgI'm uploading it in deferred/10 with the gnome-settings-daemon change21:00
LocutusOfBorgso you can have a smoother transition21:00
jbichaLocutusOfBorg: a bug may still be useful for tracking?21:11
jbichahttps://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintainers@lists.alioth.debian.org;tag=gsd32421:11
LocutusOfBorgjbicha, it is already uploaded in deferred21:15
jbichaok, whatever :)21:17
jbichamwhudson: why does python3-default still list python3.5 as supported?21:24
codepython777 just loaded ubuntu 16.04 on Intel nuc7i7bnh - no wifi detected. Any suggestions on how to fix this?22:55
sarnoldis there anything in dmesg?22:57
codepython777sarnold: the machine spec says it has a AC 8265 on board and the drivers here https://www.intel.com/content/www/us/en/support/network-and-i-o/wireless-networking/000005511.html list the driver for that card except not for my kernel  - I am running 4.4.023:00
sarnoldcodepython777: wow, what a fantastic table23:03
sarnoldthat's more than I expect from most vendors23:04
sarnoldcodepython777: try the HWE kernels https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack#hwe-16.0423:04
nacccodepython777: in the future, please avoid cross-posting, especially as your request is a support topic for #ubuntu not a development topic23:04
naccsarnold: fwiw, your suggestion was just made in #ubuntu as well :)23:05
sarnoldnacc: yay!23:05
naccsarnold: the system works :)23:05
codepython777Thanks for the help sarnold, nacc23:05
Unit193nacc: BTW, thanks for pushing parsedatetime on through, I got the update.23:09
naccUnit193: yw, but wasn't me :) I mean I got the sync in, but it was stuck due to c-m. Looks like it got resolved23:13

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