=== mnepton is now known as mneptok
=== Guest77633 is now known as Cyrus
=== maclin1 is now known as maclin
=== g2 is now known as Iron_monkey
cpaelzernacc: you will likely not read this anytime soone so adding rbasak here as well06:48
cpaelzerrbasak: I did not add skip-applied, I had no  reason and didn't use any special option actually06:48
cpaelzerof the imlpicit whitelisting if importing I didn't know will take a look and add it right now via a MP06:49
cpaelzerrbasak: can review that and merge if ok06:49
cpaelzernacc: rbasak: I usually use stable, but IIRC last week for "client" side things you asked me to go back to edge - so it might have been edge - let me check06:50
cpaelzerrbasak: ok so I was on the egde due to the request a few days ago06:56
cpaelzerrbasak: did I interpret nacc correctly that imports up until the re-import-the-world should be done back on stable?06:57
cpaelzerrbasak: and if so should I kill the two packages that were imported and instead just add the three of them to the whitelist06:57
cpaelzerrbasak: I was able to see that they technically import without error - so just adding them to the whitelist would import them "the same way as all others"06:58
cpaelzerrbasak: https://code.launchpad.net/~paelzer/usd-importer/+git/usd-importer/+merge/33394907:07
pittiLaney: good morning! do the systemd-upstream tests loop again? http://autopkgtest.ubuntu.com/running#queue-upstream-xenial-amd64 hardly makes any progress, and neither does the artful-i386 queue07:20
cpaelzerrbasak: nacc: also added an MP to avoid accidential edge/git imports for your review07:46
fabbionedoko: btw, that valgrind bug is showing up again in Debian Experimental08:03
fabbionedoko: it doesn't show in debian Unstable08:03
fabbionedoko: not sure if you are involved with debian toolchain, but i thought you might want to know08:04
Laneyhey pitti09:16
Laneypitti: We made it so that only 10% of the workers would take upstream tests when the distro queue was huge --- I just reverted that, let's see how we get on09:17
* Laney will watch a log to see if it finishes09:18
pittiLaney: ah ok, that would explain it09:22
pittiLaney: that's fine, I was just worried about a test tmpfail-looping and eating resources09:22
pittiLaney: as the other queues are empty - would this patch also just have used 10% if the other 90% are idle?09:23
mwhudsonwhy would this be considered a regression? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/armhf/g/golang-dbus/20171120_075357_70f15@/log.gz09:24
mwhudsoni'm a bit confused as to why it thinks there are no tests though, they ran (via autodep8) on other arches09:25
pittimissing autodep on the runners?09:25
Laneypitti: it removed the context from 90% of the workers09:25
Laneyfairly brutal09:25
pittiLaney: ah, I see09:26
mwhudsonpitti: oh so autodep8 is not necessarily installed on all runners?09:26
Laneymwhudson: looking, one second09:26
pittimwhudson: right; it needs to be part of the runner setup charm or cloud-init userdata09:26
mwhudsonhmm it's not listed in testbed-packages in the artifacts, but it's not listed on the arch in ran in either...09:28
mwhudsoni guess that's captured to early or something?09:28
pittiautodep8 isn't part of the testbed, it needs to be installed on the "outside" runner (side by side with autopkgtest itself)09:29
mwhudsonthat makes sense when i actually think about it :)09:30
dokooSoMoN: libreooffice autopkg test failure on i386, segfaulting09:43
oSoMoNdoko, looking09:47
Laneymwhudson: fixed!10:04
Laneythanks for reporting10:04
LaneyI needed to upgrade autodep8 :(10:05
k1l_Hi, i got a question about the procedure of fixing a bug according to SRU: see bug https://bugs.launchpad.net/ubuntu/+source/corebird/+bug/1730927 The maintainer says he cant get a SRU since the final repos have different majorversions than bionic has got.10:07
ubottuLaunchpad bug 1730927 in corebird (Ubuntu) "Support the new 280 character limit." [Undecided,Fix released]10:07
k1l_but aiui this would make most packages unpatchable in final repos since the unstable version got a different major release most of the time?10:07
rbasakk1l_: I've tried to answer in https://bugs.launchpad.net/ubuntu/+source/corebird/+bug/1730927/comments/7 - hope that makes it clear.10:09
ubottuLaunchpad bug 1730927 in corebird (Ubuntu) "Support the new 280 character limit." [Undecided,Fix released]10:09
rbasakk1l_: sorry, I failed to say that I was going to answer _in_ the bug :)10:12
k1l_rbasak: alright. this sounds like i interpreted it correctly and it could be patched in the stable repos.10:14
rbasakk1l_: agreed. Thank you for chasing this up!10:14
rbasakcpaelzer: actually following discussions with nacc late last week we concluded that the importer should always be run from beta (which we'll create, but initially it'd start off the same as edge)10:23
rbasakcpaelzer: if you didn't run --skip-applied then something went wrong with your import I think.10:23
rbasakThe applied branches didn't get imported, and we don't know why.10:23
rbasaknacc tried it and he did get the applied branches updated, which is why he thought you'd probably run it with --skip-applied.10:24
rbasakSo if you didn't, I'm not sure we know what happened.10:24
cpaelzerrbasak: hmm :-/10:27
cpaelzerrbasak: ok so lets summarize the different things in flight here10:27
cpaelzer1. my import didn't work as it should, should I remove them for now?10:27
cpaelzerI didn't realize the applied branches were missing, but if so what is uploaded atm is incomplete10:28
cpaelzertoo bad, as I imported from edge and as I read that would have been correct after all10:30
cpaelzermy console log is gone so I can't check why it worked for me10:30
cpaelzerin the past being on xenial was a difference to you and nacc sometimes10:31
rbasakI don't think there's any need to remove them. It's better than nothing, and we haven't declared "hash stability" yet. I'm pretty sure didrocks would prefer to have them than nothing at all.10:31
cpaelzerI'm ok with that10:31
rbasakThe rest is accurate. I think Xenial shouldn't make a difference now that the snap embeds the necessary dependencies (and versions).10:32
cpaelzerso I could kick of the gtk+3.0 import as well then rbasak?10:32
cpaelzerthat was taking too long last week10:32
cpaelzeror would it be enough to accept the MP which whitelists it10:32
rbasakSo you stopped it?10:32
didrocksyes, I don't really care about git history and hashes for now, the community is just going to cp the content (just having access to latest easily for them will help once we get hash stability and can branch)10:32
cpaelzerI let it run, but it welcomed me with a timeout this morning10:32
rbasakI mean: that's fine, just want to understand current status.10:32
cpaelzerrbasak: actually I ahve the local tree10:33
cpaelzerrbasak: maybe there is some --re-import flag or so to not do it all over again10:33
rbasakcpaelzer: I wonder if you could try again locally and tee the output to a log?10:33
cpaelzerto just check on latest status and push then10:33
rbasakYou can use --no-fetch I think.10:33
rbasakBut that might imply --no-push. I don't recall.10:33
cpaelzerit does10:33
* rbasak doesn't know if there's a --no-no-push.10:33
cpaelzerlet me check on this gtk+3.0 first10:34
rbasakcpaelzer: if possible, I'd like you to try again to see if you can reproduce the previous problem but with log output (-v).10:34
cpaelzerthis issue was on gnome-shell10:34
cpaelzerso I'd run that again in another console10:34
rbasakcpaelzer: if that doesn't work or is difficult, then we can just add to the whitelist. Either way we can certainly add to the whitelist.10:34
cpaelzerbut with verbose and keeping the logs10:34
cpaelzerrbasak: the MP for the whitelist is up10:35
rbasakRight now, after adding to the whitelist, the central importer will only run after it sees an upload. Someone still has to manually do stuff (though I can do it from the bastion).10:35
cpaelzerrbasak: then we will do this10:35
cpaelzer1. you can review and merge the MP to whitelist10:35
cpaelzer2. I will create a local import of gnome-shell with logs to check what might have happened10:35
cpaelzer3. I check if I can re-use all the work done on gtk+3.0 by uploading it10:36
cpaelzerwell for 3. not just push but some sort of git ubuntu import --flags10:36
rbasakI can do that, but won't updating the whitelist potentially clash with our examination in case there is an upload for that package?10:37
cpaelzerrbasak: ok hold back the merge until I have a log provided10:37
cpaelzerrbasak: but even so a --no-fetch would then still be the same10:37
cpaelzergnome shell import with --no-push is running to create logs10:38
cpaelzernow looking at gtk+3.010:38
cpaelzereven with "--no-clean --no-push" it starts over again, but just pushing the repo is too unclean10:40
cpaelzerI start it again fresh10:40
cpaelzerwe can afford those few hours10:40
cpaelzerand I'll collect logs on that as well to be sure10:40
cpaelzermy problem with the last gtk+3.0 import was that a screen lock implies I need to unlock gpg again10:41
cpaelzerand since it was still running when I went EOD that was the case10:41
cpaelzerdue to that the timeout eventually10:41
cpaelzerboth now running fine and logging away rbasak10:41
cpaelzerI'll ping with logs once they completed10:41
LocutusOfBorgpitti, how do you feel about rfkill sync? the delta seems mostly upstart-only, but I prefer to not touch it10:48
pittiLocutusOfBorg: looking10:50
pittiLocutusOfBorg: confirmed, looks good; so you want me to sync? doing10:51
cpaelzerrbasak: gnome-shell is complete - what would I want to look for?11:18
cpaelzerbranches with --applied?11:19
cpaelzerrbasak: LGTM in the log11:20
cpaelzerit has applies and unapplied branches11:21
cpaelzereven the remote actually has them already from last week11:21
cpaelzerrbasak: but then I didn't follow your discussion back then, what was missing?11:21
rbasakcpaelzer: is importer/applied/ubuntu/devel recent?11:21
rbasakcpaelzer: it appeared that none of the applied branches had been updated11:21
rbasak(in the other repo the other day)11:22
cpaelzerhmm, no it seems old11:22
rbasakcpaelzer: so if the applied branches are current, then it's not the same problem.11:22
cpaelzer2.28.1~git20091020-1 of 200911:22
rbasakInteresting. So you can reproduce.11:22
cpaelzeryeah by doing "git ubuntu import --verbose --directory /tmp/import/gnome-shell --no-push gnome-shell"11:22
rbasakDoes the hash match the output of line 4773 in your pastebin?11:23
cpaelzermaybe that fetched the state as-is ?11:23
cpaelzerI can re-run with no-fetch if needed11:23
cpaelzerthe hash matches11:23
cpaelzerrbasak: can you see from the log if it just fetched what it imported last week?11:24
rbasakOK: but the hash is old?11:24
cpaelzerthe hash matches and it is old11:24
cpaelzerit seems all applied are the same11:24
cpaelzerlook at this11:24
cpaelzerit seems all applied are "on" this hash11:25
rbasakLet me see if I can reproduce here11:25
rbasakCan you confirm your snap version please?11:25
cpaelzerI also started one with --no-fetch as well to check on that11:25
cpaelzerwas 335 this morning11:25
cpaelzerjust a sec11:25
cpaelzeryes still on 33511:26
cpaelzerrbasak: you might need --no-fetch as well11:26
cpaelzerwhen you try to reproduce11:27
rbasakBut you didn't in that pastebin, right? I don't understand why you think I may need it.11:27
cpaelzerI didn't use in the pastebin and got to the same result11:28
cpaelzeras last week11:28
cpaelzerbut maybe I "now" got to the same result as it just fetched many things11:28
cpaelzerso as lon as gnome-shell is in usdi as a repo anything without --no-fetch might not be a valid reproduce of the actual issue11:28
rbasakI see11:29
dokooSoMoN: I see that this failure gets ignored by other packages: gcc-5 libreoffice/1:5.4.1-0ubuntu311:41
ginggsdoko: hint just needs updating? https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/265212:52
rbasakcpaelzer: reproduced12:55
dokoginggs: -> #ubuntu-release12:56
cpaelzerrbasak: ok, glad to hear it is not me13:01
cpaelzerOTOH it means "new bug"13:01
cpaelzerdidrocks: sorry for the delays, but well things are in development - better to catch those now13:02
didrockscpaelzer: no worry! better to catch that before we go all in ;)13:03
didrocksand thanks for keeping me posted!13:03
dokooSoMoN: is the i386 LO autopj13:12
dokooSoMoN: is the i386 LO autopkg test failure addressed with your recent upload?13:12
oSoMoNdoko, that upload is to make LO icu60-friendly, it's not related to i386 autopkgtests failures13:33
oSoMoNdoko, the i386 failures look related to bug #169977213:35
ubottubug 1699772 in linux (Ubuntu) "linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regression: many user-space apps crashing" [Critical,Confirmed] https://launchpad.net/bugs/169977213:35
ubottubdmurray, BenC, cyphermox, jbicha, micahg, rbasak, sil2100: DMB ping.15:01
dokoseb128, didrocks, Laney: there are a lot of autopkg test failures for gvfs triggered by various packages. afaics none yet blocking15:29
seb128doko, those seem to be "Error initializing camera" errors from gphoto so probably a problem in that stack15:43
rbasakoSoMoN: BTW, it's odd that https://launchpad.net/~osomon/+uploaded-packages lists only a tiny subset of your actual sponsored uploads.16:06
rbasakoSoMoN: is it that your changelog email address isn't registered in Launchpad perhaps?16:06
rbasakSee http://ubuntu-dev.alioth.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=*tilloy*&sponsoree_search=name for example.16:07
oSoMoNIĀ use my @canonical.com e-mail address16:07
oSoMoNand it's registered in LP16:07
* rbasak doesn't know then16:07
oSoMoNit's weird indeed16:09
seb128rbasak, could it be that this package only list the most recent upload of a package (by serie)?16:09
seb128like if you upload 15 times libreoffice to xenial you only get the most recent one16:10
rbasakI thought it listed all uploads.16:10
oSoMoNthat would make sense, as there's one chromium-browser entry for artful, and one for bionic16:10
rbasakBut also, oSoMoN has uploaded to previous series.16:10
seb128it seems to limit to 116:11
seb128like I looked for Till or robert-ancell16:11
seb128who often upload the same packages16:11
rbasakI suppose that could explain it then!16:11
seb128and they also only have 1 instance of package/serie16:11
seb128but that's just guessing16:11
* rbasak would prefer it not to limit for DMB application review purposes16:11
seb128could be a question for #launchpad16:11
LaneyI think it's more that many of the uploads are copies and those aren't recorded as sponsorships (e.g. https://launchpad.net/ubuntu/+source/chromium-browser/62.0.3202.89-0ubuntu0.14.04.1213)16:15
seb128Laney, well, if you look at https://launchpad.net/~robert-ancell/+uploaded-packages ... I'm pretty sure robert did more gnome-software uploads than that16:17
seb128there is 1 for artful on that page16:17
Laneywe're not talking about the sponsorship miner?16:17
seb128and he doesn't do copies afaik16:17
Laneylet's see one that's not listed?16:17
seb128Laney, dunno, I was replying to "it's odd that https://launchpad.net/~osomon/+uploaded-packages lists only a tiny subset of your actual sponsored uploads."16:18
seb128Laney, for robert you can take https://launchpad.net/ubuntu/+source/gnome-software/3.25.91-1ubuntu3 for example16:18
Laneyso it looks like it shows the currently published version16:20
seb128ah, could well be16:21
seb128unsure if that's by design or buggy though16:21
Laneyyeah don't remember16:22
LaneyI used to use the miner back in DMB days16:22
Laneyso might not have noticed16:22
clivejois gunzip broken in bionic?16:44
=== Iron_monkey is now known as g2`
dmj_s76sforshee: This bug just got brought to my attention: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/108919517:59
ubottuLaunchpad bug 1089195 in update-manager (Ubuntu) "linux-headers will eat your inodes on LTS." [Undecided,Confirmed]17:59
sarnoldclivejo: it might be, I saw someone else complain about it last week18:05
sarnoldclivejo: please file bug :)18:05
sarnolddmj_s76: wow, what a dumping ground of a bug. it's filed against update-manager but more than one person in ther comments that it happened on their server systems with unattended-upgrades installed, etc18:10
sforsheedmj_s76: that's the same for all kernel packages, 'apt-get autoremove' does remove them though18:18
dmj_s76sforshee: Yeah, this was commented to me as well.  It's described as "Not that difficult to recover from once you know what's going on and how to fix it, but really annoying the first time."18:32
dmj_s76Essentially, you get a broken system if you set unattended upgrades and expect that to work unattended.18:33
sforsheedmj_s76: it's been discussed before, though I wasn't much involved. There are definitely some issues with automatically removing kernel packages, not sure if they were insurmountable18:35
=== kmously is now known as kmously-afk1hr
=== kmously-afk1hr is now known as kmously
=== santa is now known as Guest73570
=== Guest73570 is now known as santa__
dokomdeslaur, cpaelzer: your postgresql-9.6 upload to bionic went wrong22:20
slangasekrbasak, nacc: so the lp:ubuntu remapping, did that happen?  and does the branch that was at bzr+ssh://bazaar.launchpad.net/+branch/ubuntu/shim-signed/ still exist somewhere?  My understanding was that only the mapping was going to be changed, but I don't seem to find that branch now23:18
rbasakslangasek: we haven't actually made any mapping changes yet23:26
slangasekhmm ok23:26
rbasakAIUI the bzr mappings are independent23:27
slangasekrbasak: then I'll chase up the question of the MP I thought I saw and can no longer find with cyphermox instead, thanks :)23:27
rbasakAnd separately there's the default VCS of the ubuntu project23:27

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