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

naccxevious: thanks00:01
naccxevious: fyi, cacti just synced, it's running its tests now00:11
xeviousI found an issue with version parsing (see mediawiki), so I'm fixing that and rerunning.00:12
xeviousETA for that to hit bionic-proposed?00:12
naccxevious: it's there now, i'm retriggering php-defautls nnow00:12
xeviousOh great.00:12
naccxevious: monolog is also fixed (in b-p), and it should migrate with phpunit00:15
xeviousThat covers everything I looked at so far.00:16
naccxevious: thanks for all your help. I'll probably be EOD soon, but after some other work tmrw AM, I will pivot back to your script's output00:16
xeviousOnce I have the 'excuses...' parsing issue sorted out, I'll update the gist with the current output and copy of the script.00:17
naccxevious: thanks again00:17
xeviousGlad I can help. :)00:17
xeviousnacc: I updated the gist (https://gist.github.com/iammattcoleman/88013cb5f92105b15a66ee2ada442a16)00:34
xeviousnacc: I just noticed php-codesniffer updated to version 3.2.2 in my script's output. They just introduced a new way of annotating overrides for PHP_CodeSniffer and there have been a few regressions. At least some of them will be fixed in 3.2.3.00:36
xevious(3.2.3 should be out this week)00:37
naccxevious: ok, i can also backport it this week, if that ends up being the only thing blocking us :)00:46
lotuspsychjemorning to all04:43
lotuspsychjeim suffering this weird bug on 1 xenial machine, could you have a look? https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/174923704:44
ubottuLaunchpad bug 1749237 in linux-hwe (Ubuntu) "External usb 3.0 harddisk not detected by default on 16.04.3" [Undecided,New]04:44
cpaelzerpitti: I remember on the postgres MREs that we always had the armhf issues since the switch of lxc to lxd10:52
cpaelzerI wanted to mask the relaed tests now10:52
cpaelzerbug 174816110:53
ubottubug 1748161 in postgresql-9.5 (Ubuntu) "improve britney hints for postgres MREs" [Undecided,New] https://launchpad.net/bugs/174816110:53
cpaelzerrbasak: found that the actual fix would be very small actually https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=fc40fc34ce10:53
pitticpaelzer: for the old releases, you mean? AFAIK I fixed the namespace issues maybe a year or two ago10:53
cpaelzerpitti: was there a reason/blocker not to backport this or could I just group that with the next MRE?10:53
cpaelzerpitti: yeah trusty/xenial only10:53
pittihttp://autopkgtest.ubuntu.com/packages/p/postgresql-9.510:54
rbasakcpaelzer: are you responding to my MP comment? Or tell me that you also found that commit? :)10:54
pittiwow, since when do we have a *smiley* for errors?10:54
cpaelzerrbasak: I respond to your MP comment trying to clarify with pitti if there was a reason not to bring this back to T/X10:54
pitticpaelzer: not a blocker, there just has never been a postgresql-common SRU where I could have slipped this in10:54
rbasakOh, OK10:54
rbasakCarry on :)10:54
pittiI didn't want to SRU p-common just for this10:55
pittibut if you want to, please do of course10:55
rbasakOh, it needs an SRU to a different package?10:55
cpaelzeryes10:55
rbasakI hadn't realised that.10:55
pittithe integration tests are in postgresql-common10:55
rbasakI do have one observation though.10:55
rbasakATM, humans are still checking the armhf failure and verifying that it's just the stderr problem and nothing else. The test is still running.10:56
pittiso the arm64 error is infra-related, otherwise at least http://autopkgtest.ubuntu.com/packages/p/postgresql-9.4 loosk good10:56
rbasakIf we force-badtest it for future MREs, then we will stop looking at the armhf test run completely, which is objectively worse.10:56
pittiright10:56
rbasakI could be persuaded that on balance it's not worth the effort to look manually and force-badtest all future armhf though, as the MP requested.10:57
rbasakI didn't realise the SRU would need to be in a different source package. I agree it's not worth an SRU just for that.10:57
pitticpaelzer: at least precise fell off the radar by "natural cause" ☺10:57
pittithis looked quite poor10:57
rbasakThough if postgresql-common is tiny, perhaps it could be done at the same time as a postgres MRE and it wouldn't have any meaningful impact to users.10:58
pittione more year to go for trusty10:58
rbasak(if it's trivial source package)10:58
pittior 4 MREs10:58
pittirbasak: yes, it's a small arch:all package10:58
rbasakThen I'm in favour of "bundling" the fix at the same time as the next SRU10:58
cpaelzerok10:58
rbasak(to not-postgresql-common)10:58
cpaelzertaking a note for that10:58
cpaelzerrbasak: we still want to switch off mimeo thou10:59
rbasakUnless someone thinks otherwise10:59
rbasakcpaelzer: agreed10:59
cpaelzerrbasak: I'll update the MP comment and bump it to just affect mimeo10:59
cpaelzerback in a bit10:59
rbasakack10:59
pitticpaelzer: https://salsa.debian.org/postgresql/postgresql-common/commit/07ea2e63241c9806 FYI10:59
cpaelzerthanks11:00
cpaelzerrbasak: new MP is https://code.launchpad.net/~paelzer/britney/hints-ubuntu-xenial-postgresqlMREv2/+merge/33769611:12
cpaelzerjust mimeo as discussed11:12
rbasakack11:12
rbasakcpaelzer: one note: when you do the next postgresql MRE, get the SRU reviewer to accept postgresql-common and want for binaries to be published before accepting the others11:29
rbasakThen the dep8 test will definitely run against the new one.11:29
rbasak(I don't think a versioned dependency relationship is needed here)11:30
rbasaks/want/wait/11:30
pittithat's not true11:31
pittidependencies are satisfied from relelase/-updates as far as possible11:31
pittiyou either need a versioned test dependency, or explicitly trigger the test to run against p-common in -proposed11:32
rbasakOh.11:32
pitti(the latter appears better to me)11:32
rbasakOK we'll do an explicit trigger11:32
rbasakThanks11:32
pittii. e. see it fail, re-trigger armhf tests against p-common in -proposed, that should succeed and also validate the p-common SRU11:32
pittialthough bumping the test dep in postgresql's d/tests/comtrol isn't wrong11:33
cpaelzerjust as I did last week with some other migrations11:33
rbasakI generally shy away from bumping versioned deps to reflect bug fixes on the other side11:33
pitti(except the typoed file name, of course - tpying is hrad!)11:33
rbasakSeems like a recipe to madness11:34
pittiyeah, and breaks the clean backports, too11:34
pittiso I think manual trigger for that one round is just fine11:34
rbasakYep11:34
mvoxnox: hey, just wanted to ask for your opinion on 1749000 - I have a debdiff for systemd ready (trivial fix) that would help snapd to pass tests again in bionic14:53
julianktjaalton: I think I tried reproducing your autopkgtest-build-lxd problem 2 hours ago. I don't remember doing it exactly, but I do have a freshly generated image, so I say I did it and can't reproduce it.15:01
juliankWhat's better to use anyway, images:ubuntu/bionic or ubuntu-daily:bionic?15:01
tjaaltonjuliank: ah, well that's weird15:05
julianktjaalton: did you retry it?15:05
juliankmight be timing issues...15:05
tjaaltonI've tried many times on two machines15:06
juliankI know that other lxd stuff retries apt update a few times15:06
tjaaltonone bionic, the other xenial15:06
julianktjaalton: So I have the same first failure (from update), but the rest works15:07
juliankSo what happens is that it should do retries15:07
juliankas the container's network is not fully up when it tries to run update15:08
tjaaltondoes it try to install eatmydata on your end?15:11
juliankyeah, and that works, as network is up for me at that point15:11
juliank    chroot "$root" apt-get update || (sleep 15; chroot "$root" apt-get update)15:13
juliankum yeah, that's not going to work15:13
juliankIt exits with 0, saying "They have been ignored, or old ones used instead."15:13
cjwatsonat various points in the past that has exited non-zero in at least some interesting failure modes15:14
cjwatsonwe made the same change in LP (in fact autopkgtest probably got it from LP) and it basically eradicated most of the chroot-failure builds we were seeing at the time15:15
juliankWell, yeah, some times it might. But I think we cleaned up some of that15:16
juliankso more stuff is exit 0 now than it used to be or something15:16
juliankbecause some stuff was wrongly classified15:17
tjaaltonoh, a shell script.. I'll have a look15:17
juliankWe also have another solution15:17
juliankor not15:17
juliankI thought it should set Acquire::Retries, but I'm not sure we have a time out or something, and busy retrying seems bad15:18
willcookeCould someone with mailing list admin approve my subscription please?  I want to get an email out today if possible.  Cheers!15:19
willcookeoh, wait, it told me I am already subscribed, but when I just posted it told me I wasn't15:20
seb128willcooke, same email?15:20
willcookeseb128, yeah15:20
seb128no canonical vs ubuntu ?15:20
seb128weird15:20
willcookeI'll try and post again15:21
willcooke(I cancelled the previous one)15:22
willcookeAh, ok, it's because I'm not an Ubuntu developer.  I actually read the reply this time15:23
willcookecould a mod approve it please?15:23
cjwatsonwhat list?15:24
willcookecjwatson, ubuntu-devel15:25
cjwatsonwillcooke: done15:27
willcookethanks a lot cjwatson15:27
Odd_Blokejuliank: I think you were playing with ddebs, I'm seeing "E: Failed to fetch http://ddebs.ubuntu.com/dists/bionic-proposed/main/binary-amd64/Packages.xz  File has unexpected size (45916 != 38288). Mirror sync in progress? [IP: 91.189.90.217 80]"15:29
juliankOdd_Bloke: updates might take some time, and are not even close to atomic15:30
juliankI think I know how to fix that.15:30
Odd_Blokejuliank: "Release file created at: Wed, 14 Feb 2018 13:07:11 +0000" <-- that long?15:30
julianksays Date: Wed, 14 Feb 2018 15:17:46 UTC here15:32
juliankah no, wrong pocket15:32
juliankOdd_Bloke: The release file is updated last, though15:32
juliankOdd_Bloke: it seems to be indexing s390x now15:33
juliankah no, it's on ppc64el15:34
juliankIt takes about 2 minutes per architecture for main15:34
juliankI want to fix it by creating dists/bionic.new and then doing mv(bionic, bionic.old), mv(bionic.new, bionic)15:35
juliankbut, it's not a priority15:35
juliankat least that's what slangasek said :)15:36
juliankI think that is testable code, thouh15:37
juliankgh15:37
juliankso it should be easily possible15:37
julianklater maybe15:37
juliankcjwatson: Is ddeb-retriever back to normal runtimes again?15:38
juliankseems to be fine from what I can tell15:38
juliankAt least it did not update bionic-updates today :D15:39
cjwatsonjuliank: it hasn't been complaining at me in cronmail, so I assume so15:43
cjwatsonI only really notice when it whinges about being unable to take its lock15:43
juliankokay15:44
xnoxmvo, hey, that looks funky. I can include that in my next upload into bionic.15:46
xnoxmvo, also scary stuff =)15:46
juliankOdd_Bloke: proposed should be fine now15:47
Odd_Blokejuliank: It is, thanks!15:47
Odd_Blokejuliank: Was there actually a problem, or was I being impatient?15:47
Odd_Bloke(Or both? :p)15:47
juliankyou were being impatient :)15:47
xnoxmvo, also, will i need that in many other .service files as well?!15:49
mvoxnox: when do you plan your next upload? its blocking snapd right now (its one of the autopkgtest failures we see currently in 2.31)15:49
mvoxnox: probably, we only care about this one service in snapd15:49
xnoxmvo, today? =)15:49
mvoxnox: \o/15:49
GunnarHjHi wgrant! Do you have an idea why LP refuses to import the .po files here:15:50
GunnarHjhttps://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/comments/415:50
ubottuLaunchpad bug 1734545 in gnome-sudoku (Ubuntu) "Translations not updated from upstream" [High,Confirmed]15:50
mvoxnox: also I'm not sure what upstream dbus will do about this, its a bit of a mess IMO, so maybe the default will be "unconfined"15:50
mvoxnox: but jamie or tyler will know more15:50
mvoxnox: out of curiosity, how many dbus service files are there for systemd? i mean, dbus activatable ones?15:50
xnoxloads.15:52
xnoxhostanem1 locale1 login1 network1 resolve1 systemd1 timedate115:53
xnoxthe only odd one out, is systemd115:53
xnoxthe rest can be bus activated.15:53
GunnarHjwgrant: Please disregard my question for now. seb128 noticed that there was an obsolete upstream sharing link, so we have removed that link and will try a re-upload.16:15
=== caravena_ is now known as caravena
seb128GunnarHj, wgrant, well +sharing-details was still stating " Translations are not enabled on the upstream project. " and " Automatic synchronization of translations is not enabled. " so unsure if that's the issue, that part of lp translations is confusing so it would still be good to know if that is what stopped the .po to be listed for import16:17
Unit193juliank: Would it make sense to call automake with --forign?  Does it do anything else other than make it a little more lax in file checking?16:20
juliankidk16:21
Unit193If, say, 'ChangeLog' is missing, autoreconf fails because of gnu stupidity.16:21
juliankI think a lot of configure.ac seit foreign in AM_INIT or something?16:22
juliank*set16:23
Unit193Ooh, nice.16:23
juliankI think it also needs an option in Makefile.am16:27
juliankSOMETHING = foreign16:27
juliankbut details.......16:27
xeviousnacc: I updated the gist (https://gist.github.com/iammattcoleman/88013cb5f92105b15a66ee2ada442a16)16:28
Unit193I wondered why autoreconf failed but autogen.sh worked on some weird package, that was it.16:28
naccxevious: thanks, phpunit migrated overnight16:37
naccxevious: note also, i only care about those that are currently marked as regressions, if that makes sense?16:39
xeviousYou don't need to retest passed packages when there's a newer version available?16:40
naccxevious: not explicitly no (I mean, in theory, it's good), but it won't change the blocked state16:41
caravenajsalisbury: Hello, My name is Cristian Aravena Romero :-)16:50
caravenahttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/174847016:50
ubottuLaunchpad bug 1748470 in linux (Ubuntu) "Spectre V2 : System may be vulnerable to spectre v2" [High,Triaged]16:50
caravenaIs this report okay?16:50
=== alan_g_ is now known as alan_g
=== superm1_ is now known as superm1
tjaaltonmitya57: hi, do you have plans to upload the qt patch for bug 1749472 before FF?18:03
ubottubug 1749472 in qtbase-opensource-src (Ubuntu Bionic) "mesa 18.0.0 will cause rendering errors in Qt applications" [Undecided,New] https://launchpad.net/bugs/174947218:03
tsimonq2tjaalton: Hi, I will, yes.18:05
* tsimonq2 is working on the 5.9.4 transition in Bileto now18:05
tjaaltongreat, it will take some time to get this through anyway so next week is fine for me18:06
tsimonq2Worst case scenario, FF doesn't apply to things already uploaded iirc.18:06
tsimonq2Sure.18:06
infinityFF also doesn't apply to bugfixes.18:06
tjaaltonnvidia driver updates are still WIP and needed before it can land18:06
tsimonq2infinity: Does it apply to ABI bumps?18:07
tsimonq2i.e. I bumped ABI for qtbase for the sake of getting everything rebuilt.18:07
tsimonq2But, there's no real FF violation.18:08
tsimonq2tjaalton: Ah, OK.18:08
infinitytsimonq2: Err, you did what?18:08
tsimonq2infinity: the virtual package18:08
infinityOkay, you had me mildly terrified that you were picking package names or SONAMEs out of thin air.18:08
tsimonq2Hahahaha.18:08
tsimonq2No.18:08
xeviousnacc: Has phpunit fully pushed? I see both 5.4.6-3 and 6.5.5-1ubuntu2 listed under php7.2 on the 'excuses...' page. The 6.x test is marked as a regression, but it's only because php-defaults hasn't gone through and the test script pulled in a mix of 7.1 and 7.2 packages (including php7.1-xml instead of php7.2-xml)18:16
naccxevious: yes it has18:16
naccxevious: the logs you see are presumably old18:16
naccxevious: i've not retriggered much yet18:16
xeviousGotcha18:16
naccxevious: deubgging something in php-pear first (using count() on a return value from a function that can return a string or array)18:19
naccthat's part of the php-defaults failures18:19
xeviousYeah, that's the issue I was going to mention18:19
xeviousThat's affecting php-console-table, php-log, php-mail-mime, and php-net-smtp.18:20
naccyep18:20
nacci am just trying to figure out what they *wanted* to do :)18:20
xeviousphp-horde-activesync and php-horde-core are showing issues related to PHPUnit. Can you rerun those now that the new version of phpunit has pushed?18:21
xeviousphp-crypt-chap's log is vague about its error.18:23
naccxevious: let me look18:23
naccxevious: i think horde-activesync is actually tied to horde-test18:23
xeviousLikely. It seems like their test class just needed to be adapted to PHPUnit namespacing everything.18:24
naccxevious: yeah, i belileve i did that already18:24
xevious*needs18:24
naccit's what's in proposed, but the triggers nneed to be adjusted18:24
nacc(php-horde-test, that is)18:24
naccxevious: so let's hold off on php-horde as it relates to php-defaults18:24
naccfor now18:24
nacclet's get everything else green or understood, and then i'll work on unwedging horde itself18:25
naccsimilar to phpunit, it will be easier to get horde migrated, then just retrigger the new versions in bionic18:25
naccxevious: uploading a fixed php-pear18:25
xeviousAside from the Horde_Test_Case issue, the PEAR test count() thing, and the issue in php-crypt-chap, all the other regressions should be rerun using the new PHPUnit.18:26
naccok i'll retrigger amd64 (which tends to work fastest) and see if they go green, then trigger the rest18:27
naccok, retrigged something like 30 amd6418:29
nacci'll debug the crypt-chap one nonw18:30
naccand once php-pear publishes, i'll retrigger the dependent tests18:30
xeviousA few of the PHPUnit tests look like they'll have the same issue as the PEAR tests: `count(): Parameter must be an array or an object that implements Countable` We'll see after they rerun with PHPUnit 6.x18:34
naccyeah, it's a pain, because sometimes it's not in the code itself, but some dependent library18:34
xeviousnacc: How do you deal with php-defaults regressions that are failing because php-defaults hasn't been updated? For instance, phpunit is pulling in a mix of php7.1-* and php7.2-* packages.18:47
naccxevious: hrm, i saw the phpunit run was using an old phpunit18:53
naccxevious: so i retrigged it without anything18:53
naccxevious: as php-defaults (in that section) is already a trigger18:54
naccxevious: not sure if that answered your question18:54
xeviousnacc: This build failed due to php7.1-xml being pulled in instead of php7.2-xml. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/p/phpunit/20180214_163244_07123@/log.gz18:56
xeviouss/build/test/whatever18:56
xeviousI don't think that's one of the ones you just kicked off though, is it?18:57
naccxevious: which lilnk is that from? sorry, there's lots of moving pieces18:57
xnox-apt-pocket=proposed=src:php7.2 --apt-upgrade phpunit --env=ADT_TEST_TRIGGERS=php7.2/7.2.2-1ubuntu119:01
xnoxthat's run of phpunit, as triggered by php7.2 without the new php-defaults19:01
naccxnox: err, duh, thanks19:02
naccxevious: right, so i was just retriggering a lot of php7.2's tets, with php-defautls from proposed19:02
xnoxnacc, next one to migrate is php-defaults, right, or no?19:02
xnoxcause once that one migrates, everything else should become easier, no?19:02
naccxnox: yeah, the problem is php-defaults is probably wedged by php-horde*19:03
naccand i think i see why horde is wedged19:03
nacci'm not 100% on the why of the why, but it seems like there was a beahvior change in phpunit19:03
naccwrt the bootstrap fille19:04
naccxnox: so yeah, i'd *like* to unstick php-defaults, but i have a feeling it's going to actually be easier to unstick php-horde* and then retrigger php-defaults19:04
naccand php-horde-test looks to need a bunch of changes19:07
naccworking on that now19:07
naccxnox: that is to say, i don't think i *can* unstick php-defaults until i fix horde19:08
naccxevious: php-crypt-chap is failing because php7.2-mcrypt is gone19:17
nacchttp://php.net/manual/en/migration71.deprecated.php19:17
xeviousAh, that'll do it.19:17
naccso i think i need to pull in a new package19:17
xeviousIt's available in PECL now.19:18
xeviousWhat uses php-crypt-chap? Can it be retired?19:18
naccxevious: php-horde-passwd :)19:19
* xevious strongly dislikes Horde19:20
naccbut php-horde-passwd itself has no revdeps19:20
naccxevious: i'm pinging the debian folks to find out if they are going to package the pecl mcrypt19:21
naccxevious: ok, almost got horde-test working19:23
naccxevious: and some of the retriggers i ran are going throug now (php-imagick, php-memcache)19:49
naccxevious: horde-activesync needed a new horde-test and horde-stream-wrapper20:01
nacc(new as in either upstream or cahnges)20:01
naccxevious: and i just retriggered the php-pear dependent ones20:08
naccand the arches for those where amd64 passed20:11
naccxevious: i'm going to elt excuses settle for a bit, i'll get the php-pear fixes uploaded first21:03
xeviousnacc: Are these tests running on the Launchpad build farm that this channel's topic says has limited capacity?21:46
cjwatsonOh, that's out of date21:51
=== cjwatson changed the topic of #ubuntu-devel to: Artful Released + taken down LP#1734147 | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of trusty-artful | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots:
jbichacjwatson: should we drop the Artful bug from the topic now?21:56
cjwatsonjbicha: I dunno22:03
cjwatsonask somebody who was involved with that :)22:03
=== jbicha changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of trusty-artful | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots:
rharpernacc: I'm trying to do git ubuntu build or build-source  and I'm getting some errors when it attempts to lxc file push stuff into the ephemeral container ... is that a known issue ?22:36
naccrharper: which snap channel?22:39
naccrharper: and yes, possibly :)22:39
rharpernacc: looks like stable22:39
rharperon classic22:39
rharpershould I move to edge ?22:39
naccrharper: yeah22:40
naccrharper: it's fixed in edge and i've not done a release to stable in a while22:40
rharpersnap install git-ubuntu --classic --edge ?22:40
naccit's on my todo, but we're in heavy flux on edge and ENOTIME :)22:40
naccrharper: snap refresh --channel edge git-ubuntu22:40
nacciirc22:40
rharperk22:40
naccpossibly just snap refresh --edge git-ubuntu22:40
rharperyeah22:41
rharperor any order snap refresh git-ubuntu --edge22:41
naccrharper: right22:42
naccxevious: jmespath.php fixed (it just migrated, i'll wait til it shows up in rmadison then retrigger it)22:43
xeviousGood news. I was wondering about that one, since it wasn't showing up in APT at all.22:43
naccyeah i'm working on unwedging php-pear now (I need to craft the triggers properly)22:45
rharpernacc: well, it fails *differently*22:50
rharperE: Package 'equivs' has no installation candidate22:50
rharperand similar to the stable release, it seems to ahve trouble with the temporary tarball22:51
naccrharper: can you pastebin the command exact output/23:07
nacc*and exact output23:07
naccrharper: the equivs thing, presuming your lxd setup is good, should go away after a few attempts23:07
rharpersure23:07
nacc(we are just waiting on network in the lxd)23:07
rharperwhat container are you launching? and why not give it cloud config ?23:07
naccrharper: we just use lxc appropriately23:07
naccrharper: i don't know what you meann by a cloud config in this context23:08
naccrharper: we need the equivalent of an sbuild environment23:08
rharperif the lxc image you run inside has cloud-init , then whatever set of commands you want to run for like package install could do that23:08
naccrharper: because then we'd need to trust cloud-init :-P23:08
rharperwell, it waits for the network ...23:08
naccrharper: we *could* do that too23:08
naccrharper: feel free to file a bug23:09
rharpersure, I'm mostly interested in which image you're using the minimal, or the cloud based ones23:09
nacccloud-based23:09
naccwe just spawn ubuntu-daily:<whatever>23:09
naccbased uponn the changelog23:09
rharperif it's bionic, then you can do something like: lxc exec <name> -- cloud-init  status --wait which will block until cloud-init is done which ensures networking is up ; that way you're not spwaning apt commands when no network has come up23:10
naccrharper: and on trusty, xenial, artful?23:10
rharperthe networkd layer is somewhat sluggish due to ipv6 mantory waits23:11
rharpercloud-init wait is back to xenial23:11
rharpernot trusty23:11
naccrharper: which then we'd have to special case :)23:11
nacctbh, this is all experimental enough that it's not a big deal23:11
rharpery23:11
naccand we're not doing any work on that toolingn right nnow, focusing on the importer23:11
rharperfor sure23:11
nacci have a MP up that at least silences that output so it's not so scary23:11
rharperI'm looking at my add-a-patch workflow so I can do that via git-ubuntu instead23:11
naccack23:11
rharperhttps://paste.ubuntu.com/p/q235rHvvjv/23:12
rharperthere's the command and output23:12
naccrharper: ok, yeah the equivs is just noise while it waits for network (with a backoff)23:13
naccreading the failure bit23:13
nacccan you pass --keep-build-env and then go into the container and see what's there?23:13
rharperI do have an orig.tgz in the parent dir for the package23:13
rharperyeah23:14
nacci wonder if for some reason the tarball is root-owned23:14
naccbcause it's ap ermission issue, not a enofile23:14
rharperyeah23:14
rharperlet's look23:14
rharperno, owned by me23:15
naccrharper: in the container/23:15
nacc*?23:15
rharperoh23:15
rharperlet's wait23:15
rharperit's thinking about retrying23:15
naccrharper: ok :)23:15
rharperinteresting, it gets the uid of my user on the host23:16
rharper-rw-rw-r--  1 1001 1001 22039 Feb 14 23:16 bcache-tools_1.0.8.orig.tar.gz '23:16
rharper-rw-------  1 1001 1001 28516 Feb 14 23:16 tmp1k_sj6kn.tar.gz23:17
rharper 23:17
nacchrm, i guess that's probably because of `lxc file`23:17
naccand maybe local lxd config23:17
naccbut that would be why you get an issue, as we run as the ubuntu user in the lxd23:17
naccnow the question is why are the perms like that23:17
xeviousnacc: I updated the script to only flag regressions that have newer packages available. I also added a script to run it in a Docker container, in case that's convenient for you. https://gist.github.com/iammattcoleman/88013cb5f92105b15a66ee2ada442a1623:18
naccxevious: thanks23:18
rharpernacc: yeah, you su - to the ubuntu user23:21
naccrharper: is this a branch you have pushed to LP that i can test?23:21
rharpernacc: I think this is a local issue because on my system, my username is not uid=1000 like ubuntu is23:21
nacc(just to see if it's reproducible)23:21
naccah that would make sense23:21
naccand is probalby then an underlying bug23:21
nacc(we should be chown'ing the files to ubuntu:ubuntu as we copy them23:22
naccwe can use --uid, i think23:22
sarnoldpls no "chown as copy", but do the copy as the user in question..23:22
rharper https://code.launchpad.net/~raharper/ubuntu/+source/bcache-tools/+git/bcache-tools/+ref/add-bcache-export-patch23:22
naccsarnold: lxc file push --uid then?23:22
naccrharper: thanks, but based upon what you just said, that's the issue23:23
sarnoldnacc: yeah, that way if it's busted you can yell at serge and stephane :D23:23
naccsarnold: yeah23:23
rharpernacc: right, I think that's it as well23:23
naccrharper: do you mind fililng a bug?23:23
rharpersure, can I ubuntu-bug or what ?23:23
naccrharper: probably not? since it's not a package23:23
rharperboo23:23
nacchttps://bugs.launchpad.net/usd-importer/+filebug23:24
rharperso, what do ?23:24
rharperk23:24
naccthanks23:24
rharpernp23:24
naccsomething like 'lxc file operations should set the uid'23:24
rharpergit ubuntu build fails when user's uid doesn't match ubuntu user in container23:24
naccyeah23:24
naccthat works too :)23:24
xeviousnacc: I'm calling it a day.23:28
rharperhttps://bugs.launchpad.net/usd-importer/+bug/174960923:29
ubottuLaunchpad bug 1749609 in usd-importer "git ubuntu build fails when user's uid doesn't match ubuntu user in container" [Undecided,New]23:30
rharpernacc: ^23:30
naccrharper: thanks23:37
naccxevious: have a good evening23:37
xeviousnacc: If you want to give me one/several of the "update to namespaced PHPUnit 6 classes" tasks tomorrow, those are ones I could easily tackle between other things I'm working on and meetings and whatnot.23:39
naccxevious: sure, i'll let you know23:41

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