/srv/irclogs.ubuntu.com/2016/04/19/#ubuntu-devel.txt

Pharaoh_Atemnacc: I've verified that the extension works :)01:55
darkxstinfinity, oh the symlink was borked, can you take a look at this fix http://pastebin.com/ttxZLdxP02:07
infinityslangasek: ^-- Can you sponsor/review that for Tim?02:16
cyphermoxinfinity: slangasek: I will sponsor that ^ if you haven't already taken care of it02:50
sarnoldcyphermox: is the destination of that symlink correct? it's still /root/etc/..02:54
cyphermoxthe file needs to go in /root, but what it links to should be the path without /root02:54
cyphermoxthe diff looks correct to me02:54
sarnoldthanks02:55
cyphermoxthis is because casper runs outside the chroot where our live system is02:55
sarnoldI always think of /root as a user directory, for uid 0 .. not as a mount point. It kinda hurts my head. :)02:56
cyphermox;)02:57
darkxstcyphermox, thanks!04:09
cyphermoxnp04:10
tjaaltondoko: i don't have time to wait for it to get past debian NEW, there's no diff04:33
Mirvpitti: morning. if you want to look at one before I publish the silo, here's one stuck Test in progress: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-010/excuses.html04:50
cpaelzergood monring05:40
cpaelzermay be too early for a well typed morning :-)05:40
ginggs_morning pitti, thanks for htop!05:50
pittiGood morning05:51
pittiMirv: right, let me look into the logs in some 10 mins05:52
tjaaltonpitti: hi, you might remember working with mlankhorst 2y ago on xorg-lts-transitional? any idea why the packages were limited to just amd64 & i386?06:22
tjaaltonthis package was added to trusty to allow upgrades from lts-foo stacks06:22
tjaaltonand I had no idea about it until yesterday :P06:22
pittitjaalton: yes, I think we discussed the upgrade approach back then; but no idea why it's limited to these arches06:23
pittitjaalton: perhaps because we only did the enablement stacks on those?06:24
tjaaltonwell they are built on every arch but I guess there are no desktop images for other than these06:25
tjaaltonimages that use an lts stack06:26
=== athairus is now known as afkthairus
pittiMirv: I followed up to bug 157135306:51
ubottubug 1571353 in Auto Package Testing "test requests sometimes get lost and stay "in progress" forever" [Undecided,Incomplete] https://launchpad.net/bugs/157135306:51
pittiMirv: so the tests actually did run, but there's something between ci train and britney that doesn't pick them up06:51
pittiMirv: I asked robru about getting a debug log06:51
robrupitti: Hmmmmmmm?06:52
robrupitti: you want me to re enable -v on the britney runs?06:53
pitti(OTP, brb)06:53
pittirobru: yes, that would be nice; either in production, or an one-off run06:59
robrupitti: Mirv: ok I added the -v flag back, you should see the verbose logs in the next run, maybe ~1hr07:26
pittirobru: cool, thanks07:26
robruyw07:27
Mirvpitti: thank you for looking into it07:39
pittimwhudson: so, I started another run from your branch with -s, and will let you ssh into the testbed right after the failure happens07:46
pittimwhudson: then we can poke around07:46
mwhudsonpitti: yeah that would be very useful i think07:46
mwhudsonstep 1: wtf is actually listening on 10.0.8.1:844307:47
Odd_Blokeinfinity: Did you see we have powerpc images at http://cloud-images.ubuntu.com/xenial/current/? ^_^  If you have the time (you don't have much else going on this week, right?), a test would be appreciated. :)08:11
Odd_Bloke(Getting them in to streams is WIP; I'm poking this along when I have a minute between tamping down release-critical fires, and it doesn't matter too much if this lands post-GA :)08:12
cjwatsonnacc: lazr.restfulclient fix working its way into xenial-proposed now; thanks for the nudge09:40
jtaylorare there differences between debians ppc64el and ours?09:56
jtaylorseems like at least some compiler macros are defined in xenial that aren't in unstable09:57
jtaylorah no the compiler reports itself as ibm oO10:01
Mirvpitti: did you get better logs now?10:19
=== victorp_ is now known as victorp
jtaylordoes someone have access to a ppc64el box for a quick test?10:49
jtaylornot necessary as I can likely fix it without access but I am curious what the compiler doing10:49
=== xavigarcia is now known as xavigarcia_lunch
pittiMirv: yes, I did, and I just finished writing the followup to the bug11:02
pittirobru: you can disable verbosity again, thanks for your help11:02
=== hikiko is now known as hikiko|ln
pittiMirv: it's clear now what happened, I'll restart your lost test11:02
Mirvpitti: thanks a lot! the silo is already gone through QA so I was just holding off for getting this debugged which should help people in the future.11:05
Mirvpitti: interestingly the silo was already britney approved last week (which is why it went to QA queue), but at some point I noticed all of its tests, including passed ones, were restarted.11:05
pittiMirv: ah! well, nothing lost except for some additional universe heating then :)11:05
Mirv:)11:06
pittiMirv: hm, that's curious -- it should see the previously passed results then11:06
pittiunless the whole silo got cleared11:06
pittior did that involve a followup upload? (this would re-trigger all tests)11:06
Mirvpitti: nothing happened in the silo, I guessed it was some sort of global restart of things.11:06
Mirvthe silo has stood still since last Wednesday11:07
pittiMirv: ok, whatever then :) I understand what's going on, I'll think about how to solve this in the least possible ugly way11:07
Mirvyet something caused that. so I noticed it from the fact that suddenly bileto showed "Running" instead of "Approved"11:07
Mirvthank you again for looking into it11:07
sveinseWhat is the difference from Ubuntu core and a system which is debootstrapped?11:13
pittijtaylor: can test something for you if you want11:16
jtaylorpitti: if you have time great, I already fixed the problem but my curiousity remains :)11:16
pittimeh, no xenial schroot on the porter box; -- moving to a scalingstack instance11:17
pittijtaylor: so what do you want me to run?11:18
jtaylorpitti: http://paste.ubuntu.com/15928177/11:19
jtaylorshould be cat ftest.s, not cat test.s11:19
pittijtaylor: http://paste.ubuntu.com/15928232/11:23
pittijtaylor: that's actually the first piece of Fortran that I'm looking at, from the last 20 or so years :)11:23
jtaylorpitti: thx so there is an IBM in there which trips the package up11:23
jtaylorand also looks like its ubuntu specific which explains why debian is not affected11:24
jtaylorpitti: if only I could say the same ._.11:24
jtaylorstill ahve to occasionally deal with f77 code, written when f77 was actually new ...11:25
pitti+  * Update the ibm branch to 20160324.11:25
pittijtaylor: ^ in https://patches.ubuntu.com/g/gcc-5/gcc-5_5.3.1-14ubuntu2.patch11:25
pittijtaylor: can I delete that ppc instance again, or do you still need anythign?11:25
jtaylorpitti: no thats it thanks11:26
jtaylorthe ibm in the output in ubuntu is fine its just the package that does a pretty dumb check11:26
jtaylorit just does essentially grep IBM = ibm compiler11:26
Laneynice, I was eyeing that failure11:26
jtaylorLaney: the latest upload has fixed it11:26
LaneyI see that11:27
jtaylorI did check debian if all arches work first but this was ubuntu specific :/11:27
=== hikiko|ln is now known as hikiko
Laneybarry: sounds like https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/t/tox/20160419_041620@/log.gz is caused by the new virtualenv11:40
=== xavigarcia_lunch is now known as xavigarcia
barryLaney: see, i don't quite understand that because 15.0.1+ds-2 fixes it for me locally :(12:13
barryLaney: and the same versions work in an sid chroot12:15
barry*and* a xenial chroot12:15
* barry retries12:15
barryat least it will give me time to get some breakfast and caffeine first ;)12:16
Laney:(12:16
Laneybarry: adt-run --output-dir /tmp/virtualenv/out --timeout-copy=6000 --setup-commands 'if grep -q trusty /etc/lsb-release; then apt-get install -y build-essential; fi; apt-get purge --auto-remove -y ubuntu-snappy-cli || true' --apt-pocket=proposed=src:python-virtualenv --apt-upgrade tox --env=ADT_TEST_TRIGGERS=python-virtualenv/15.0.1+ds-2 --- qemu ~/temp/adt-xenial-amd64-cloud.img12:22
Laneythis makes it reproduce12:22
Laneywith an adt-buildvm-ubuntu-cloud thing12:22
=== _salem is now known as salem_
barryLaney: okay thanks.  let me see if i can figure out what's up12:50
=== davidcalle_ is now known as davidcalle
=== zyga_ is now known as zyga
barryLaney: so the problem with your reproducer is that it doesn't pick up python-pip-whl 8.1.1-2 which is where one half of the fix is.  if you add ,src:python-pip to the --apt-pocket option, then it does pick up 8.1.1-2 and all the tests pass.  notice in the excuses log file that it is picking up pip 8.1.1-2 but it's still picking up virtualenv 15.0.1+ds-1 but the other half of the fix is from 15.0.1+ds-2.13:08
barryhttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/p/python-virtualenv/20160418_153721@/log.gz13:08
barryLaney: so why isn't excuses picking up both pip 8.1.1-2 and virtualenv 15.0.1+ds-2?13:08
barrysimilarly, the tox failure is picking up python-pip-whl 8.1.1-1 and virtualenv 15.0.1+ds-213:09
Laneybarry: It's using the smallest amount of stuff possible from -proposed13:10
Laneydo you want a Breaks or something?13:10
barryLaney: i guess, if that'll make sure the right versions of both are picked up13:11
Laneybarry: We could retry with both, but it seems correct to add it if you need both pieces to have working stuff13:11
barryLaney: let me look13:11
barrydoesn't help that debian broke my sbuild ;)13:12
barrymaybe just add a Depends: python-pip-whl (>= 8.1.1-2) to virtualenv? (and similar to tox)13:13
barryLaney: ^^13:13
Laneybarry: Probably just virtualenv is enough?13:27
barryLaney: possibly.  let's try that first and see.  i'll upload to debian momentarily and syncpackage it over when lp picks it up.  if that's not good enough i'll add a version constraint to tox on virtualenv13:32
barryLaney: http://paste.ubuntu.com/15929623/13:32
Laneybarry: That'll force the new one to be installed, which I think is Good Enough13:32
barryLaney: +113:32
Laneyfeel free to syncpackage --no-lp imho13:33
barryLaney: ack13:33
=== maxb_ is now known as maxb
caribouExcuse the noob's question but I've been running Xenial since the beginning so why is the archive pushing me >500 packages two days from release ?14:11
gQuigscaribou: what packages?   I maybe got 30 in last two days14:12
caribougQuigs: well, 629 packages to be exact so most of everything including LibreOffice, vim, xorg,juju14:14
rbasakcaribou: are you using a mirror that has just been kicked into life perhaps or something?14:15
caribourbasak: archive.ubuntu.com14:15
rbasakThere have been many minor (bugfix) updates flowing through recently BTW.14:15
cjwatsonlibreoffice was last changed in xenial on 2016-04-0814:18
gQuigscaribou: I last updated libreoffice on 2016-04-1314:19
cjwatsonperhaps your apt-get update was failing for some reason14:19
cariboucjwatson: I was on training last week, I didn't do any upgrade during this time so the dates make sense14:20
gQuigscaribou: do you have IPv6 by any chance?14:20
gQuigsoh ok14:20
caribougQuigs: no still ipv4 but looks like it's normal, sorry for the noise14:20
cjwatsonthere you go, so not "two days before release" :)14:20
cariboucjwatson: indeed14:21
pittistgraber, apw, smoser: FYI, I filed bug 1572188 about the underlying bug for the weird lxc test failures14:56
ubottubug 1572188 in cloud-utils (Ubuntu) ""ubuntu-cloudimg-query xenial daily" fails with "confused by argument: xenial"" [Undecided,New] https://launchpad.net/bugs/157218814:56
nacccjwatson: thanks!14:57
naccPharaoh_Atem: awesome, thanks!14:57
smoserpitti, apt-get install distro-info14:57
pittismoser: ooh14:57
pittismoser: curious, why does it work for precise and trusty then?14:58
smoser$ grep KNOWN_RELEASES /usr/bin/ubuntu-cloudimg-query14:58
smoserKNOWN_RELEASES="hardy karmic lucid maverick natty oneiric precise quantal14:58
smoserlocal releases="${KNOWN_RELEASES}" r=""14:58
pittisome hardcoded fallback list? (I thought this queries the remote json for available releases, not distro-info)14:58
pittiaah14:58
smoserubutnu-cloud-image-query just needs *really needs* to be replaced by something reading the stream data.14:59
pittismoser: thanks for this15:02
stgraberI guess it recommends distro-info but doesn't depend on it or something?15:02
pittiyep15:02
stgraberand we somehow had some images that did have it for whatever reasons, explaining the random results15:02
pittistgraber: I think I know this15:03
stgraberpitti: is distro-info something we should have in the adt image or do you prefer a new test dep on lxc instead?15:03
pittistgraber: for a while now creating adt images on lcy01 has failed15:03
smoserit is a recommends.15:03
stgraberah, so old images have it, new ones do or something15:03
pittistgraber: so sometimes we run tests on full fat cloud images (on lcy01), and sometimes on adt images (on lgw01 or bos01)15:03
pittiand the latter are minimized and presumably don't have distro-info15:03
stgrabersmoser: yeah, won't do us much good since adt doesn't pull recommends15:03
pittistgraber: well, you can tell it to15:04
pittiEither add "Restrictions: needs-recommends" or add "distro-info" as a test dependency15:04
pitti(just wrote that to the bug)15:04
stgraberoh, then I guess I should do that everywhere because that's kinda what we expect with it being the distro default :)15:04
smoser"The Recommends field should list packages that would be found together with this one in all but unusual installations. "15:04
pittiwell, depends what you want to test15:04
stgraberI want to test the thing my users will get15:04
stgraberwhich means, having the recommends15:04
smoserunless you want to test unusual installations :)15:04
pittiif you want to verify that your recommends are really optional, then you don't want that15:04
hallynfor days now i've not been able to update my xenial laptop, alwyas get Hash Sum mismatches15:05
stgraberwell, someone installing lxc with --no-install-recommends wouldn't be getting the templates at all :)15:05
pittistgraber: anyway, let me know if I should upload lxc with that, or you want to do it from teh airpirt15:05
pittiairport too15:05
smoserhallyn, hm... those shoudl be gone the way of the dinosaur15:05
stgraberpitti: I can do it15:05
hallynsmoser: ...15:06
smoserhttps://bugs.launchpad.net/launchpad/+bug/143001115:06
ubottuLaunchpad bug 1430011 in Launchpad itself "support apt by-hash mirrors" [High,Fix released]15:06
smoserand http://www.chiark.greenend.org.uk/~cjwatson/blog/no-more-hash-sum-mismatch-errors.html15:06
pittihallyn: using apt-cacher-ng by any chance?15:06
smoserso that is interesting that you see it.15:06
hallynsmoser: then i call that a big fat fail :)15:06
hallynyeah15:06
hallyni was thinking i should turn it off for a bit, but...15:06
smoserThere will still be some people who won’t yet benefit from this. debmirror doesn’t support by-hash yet; apt-cacher-ng only supports it as of xenial, although there’s an easy configuration workaround15:06
pittihallyn: I had lots of troubles with that until cjwatson helpfully pointed out /etc/apt-cacher-ng/backends_ubuntu15:06
smoser(see the cjwatson link there, hallyn)15:06
pittihallyn: for me this was pointing to "de.archive.ubuntu.com",  i. e. it would divert all requests to *archive.ubuntu.com to that15:06
pittihallyn: which caused hash sum mismatches to no end15:07
smoserpitti, we can update cloud-utils if yiou want.15:07
hallynpitti: so you removed it?  pointed it to locahost?15:07
smoserto contain 'xenial'15:07
pittiI changed that to just a.u.c. and I've never gotten it ever since15:07
hallyna?15:07
cjwatsonI raised this in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819852; no response yet15:07
ubottuDebian bug 819852 in apt-cacher-ng "apt-cacher-ng: support by-hash index files" [Normal,Open]15:07
cjwatsona = archive15:07
pittihallyn: archive.ubuntu.com15:07
hallyncjwatson: oh, so i should turn it off?15:08
pittihallyn: well, full contents is: http://archive.ubuntu.com/ubuntu/15:08
hallynpitti: ok, thats where mine is pointing15:08
stgraberpitti: uploaded15:08
hallynno, us.archive...  ok lemme try dropping us.15:08
pittihallyn: hmm, so it's not that then; for me that was it15:08
cjwatsonhallyn: that's not what I said :)15:08
cjwatsonhallyn: dropping us.archive.ubuntu.com from /etc/apt-cacher-ng/backends_ubuntu will probably indeed deal with it for the moment15:08
pittistgraber: cheers15:08
hallyncjwatson: i'm having a hard time following15:08
stgraberpitti: didn't test to see if we may need more than that though, not enough bandwidth for that, but since all the other tests passed, that should really be it15:08
cjwatsonhallyn: just interleaved IRC conversations15:08
cjwatsonhallyn: my last-but-one statement is in agreement with pitti, so do that15:09
hallynneither emptying the file nor using http://archive.ubuntu.com/ubuntu/ seems to help15:09
pittistgraber: should be fine15:10
hallyndo i need to apt clean?15:10
cjwatsonhallyn: apt-get -oDebug::Acquire::http=1 -oDebug::Hashes=1 update15:10
cjwatsonhallyn: apt clean -> no, that's entirely useless here15:10
hallynhttp://paste.ubuntu.com/15931040/ and http://paste.ubuntu.com/15931043/15:12
pittithat doesn't look like a hash sum mismatch15:14
pittijust google's repo not being signed enough15:14
pittiI had that too, I just removed it15:14
cjwatsonindeed, I see no hash sum mismatches there.15:14
cjwatsonI'm happy to debug a hash sum mismatch, but only if you can show me update output with those debug options that actually exhibits a hash sum mismatch15:15
hallynd'oh, sorry, http://paste.ubuntu.com/15931102/15:15
hallyni pasted the same file twice15:15
cjwatsonthat's a mismatch on debs, rather than on indexes15:15
cjwatsonwhich suggests apt-cacher-ng has cached corrupt data15:15
hallyn<shrug>15:15
hallynok15:15
cjwatsonyou may shrug but it's important!15:15
cjwatsonI would probably rm -rf the relevant bit of apt-cacher-ng's cache and start again15:16
cjwatsonit's clearly got itself hopelessly lost15:16
rbasakThere was an apt bug causing deb download corruption.15:16
hallynok, lemme rm -rf its cache15:16
* rbasak looks15:16
cjwatsonthose files don't change content without changing URL and never have15:16
hallynso it seems to me this should be self-healing15:17
cjwatsonI've seen acng corrupting data in the past, but not for a while15:17
rbasakhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81079615:17
ubottuDebian bug 810796 in apt "HTTP pipelining is broken and causes download failures" [Normal,Fixed]15:17
hallyni'm on the road,  there's a good chance acng isn't entirely to blame,15:17
rbasakShould be fixed in the archive.15:17
cjwatsonit can probably only be self-healing with cooperation from acng15:17
rbasakBut if it's regressed or soemthing, then turning off HTTP pipelining may help.15:18
cjwatsonif it's cached lies and persistently continues to serve them, there's not a whole lot apt can do15:18
hallyncjwatson: as a naive user, seems like it should be able to tell acng "that doesn't seem right, try again"15:18
cjwatsonhallyn: that still requires cooperation from acng ...15:19
hallynof course15:19
hallynwhy is that bad?15:19
cjwatsonit's not, but it's what I said above and you appeared to be contradicting me?15:19
hallynhm, no, wasn't contradicting you15:20
cjwatsonAFAICS apt-cacher-ng does not implement the relevant cache-busting headers at all15:20
hallynthere are such headers?15:20
cjwatsonit just entirely ignores stuff like Pragma: no-cache and Cache-Control15:20
hallynmight be something i could look into this spring15:21
cjwatsonhttps://tools.ietf.org/html/rfc2616#section-14.915:22
cjwatsonthe thing that's needed would be for it to implement Cache-Control: max-age=<seconds>, I think15:24
hallynis apt sending that now?15:25
cjwatsonno, but it's the basic mechanism that would be necessary to recover from this sort of thing15:25
hallynseems like 'fetch url1;  hash some mismatch; fetch url1?refetch' would more directly fix it15:26
cjwatsonapt could at least conceivably send it as an attempt to recover from a hash mismatch on a package15:26
hallynbut i guess that doesn't fit into the spec15:26
cjwatsonhallyn: the "refetch" step in your pseudocode would need to be implemented by adding the Cache-Control: max-age=0 header15:26
hallynright15:26
hallynok, maybe i'll look into that, thx15:27
cjwatsonnp15:27
cjwatsonjust for clarity, this is unrelated to any of the stuff I changed recently15:27
hallyncjwatson: right,15:27
hallynand i think i know wha thappened - damned internet provider a few days ago redirected requests to their signin page and corrupted apt-cache-ng.  so yeah i want to code the automatic fix for that15:30
cjwatsonright, captive portals are the work of the devil15:31
cjwatsonapt itself is a lot better at dealing with those than it used to be15:31
cjwatsoni.e. it doesn't save stuff that doesn't validate15:31
cjwatsonbut I don't think acng is clever enough for that :-/15:31
cjwatsonso that's a separate fix, if acng understood the current state of the archive it's trying to fetch well enough, it could just not cache resources that can't possibly fit into it.  I don't know if that's feasible within acng's design15:32
hallynand then once google chrome gets redirected it caches that value, and send sme back to the portal every time until i go to settings to clear all cached pages :)15:32
hallynhm, yeah, that could be simpler15:32
hallynand good enough for me15:32
cjwatsonI suspect that right now it doesn't parse the archive's index files in enough detail to be able to do that15:33
cjwatsonprobably something to discuss with upstream before thinking about implementing it15:34
cyphermoxhallyn: NM can help you distinguish if you're behind a captive portal, if it helps15:36
hallyncyphermox: NM can't even find my mr3020 hotspot half the time15:36
cyphermoxo.O?15:37
hallyncyphermox: but the problem is captive portals which randomly and frequently recet15:37
hallyn(crappy-ass tengo internet in particular)15:37
hallynreset even15:37
cyphermoxyeah, but that's what I'm saying, it can poll some website of your choosing, look for a string, every $interval15:38
hallynso it's not at connect time - apt is going along fine, then it resends me to the portal15:38
hallynright but interval isn't actually regular.  sometimes it's every day, sometimes every 2 minutes (at the same location)15:38
cyphermoxand flip a key available in DBus that tells whether you have local or global connectivity (global meaning said website got the string)15:38
hallynthey really are broken...15:38
cyphermoxok15:38
hallyni had a script doing it by hand, every 5 minutes - still not good enough :)15:38
cyphermoxok15:39
cyphermoxthreaten them with less money?15:39
hallyncyphermox: now maybe i should be doing something like keeping a connection open and detecting when it's hung15:39
hallynhah, the curse of free15:39
cyphermoxoh ;)15:39
hallyni *should* get satelite internet.  but $$15:39
cyphermoxhallyn: what kind of internet right now?15:39
hallynnow meanwhile, yes, i shoudl file a bug on NM and my hotspot.  soemtimes it just doesn't find it15:40
cyphermoxmaybe you could do some keepalive magic.15:40
hallyncyphermox: at this very moemnt, it's tengo internet at an rv park in austin.15:40
cyphermoxright, but that's wifi?15:40
cyphermoxor dialup?15:40
hallynoh, yeah.15:40
hallynso a ubiquity m.2 rocket connected to tengo internet, with tp-link mr-3020 serving that to other devices15:41
hallynsometimes NM doesn't find th emr-3020, so i use scripts manually using wpa-supplicant :(15:41
hallyn'manually'15:41
hallynwhat kind of logs can i provide for a bug report?15:41
cyphermoxpretty much just syslog would have everything15:42
hallyn'sudo dmesg', or journalctl -u network-manager or something?15:42
cyphermoxNM just gets whatever wpasupplicant returns, but it has some issues in wily, and different issues in xenial15:42
cyphermoxnah, /var/log/syslog15:42
hallyni'm on xenial atm,15:42
hallynok, i'll switch back to n-m after a meeting and file a bug when it happens15:43
hallynthx15:43
hallyni should see if nmcli usage has changed recently too....15:43
naccslangasek: fyi, debian testing may just remove php-horde-mongo; not sure if we'd want to follow suit (it's one of our two remaining known-broken packages). Only has reverse-recommends in the archive, and will probably need to add a new package (https://github.com/mongodb/mongo-php-library) which Debian is not planning on adding15:59
slangaseknacc: yes, removal is fine/appropriate; file a bug?16:00
naccslangasek: ack, will do16:01
bdmurraypitti: Will you be testing the SRUs in bug 1560797? If not I can do it.16:03
ubottubug 1560797 in apt (Ubuntu Wily) "apt does not configure Pre-Depends: before depending package" [High,Fix committed] https://launchpad.net/bugs/156079716:04
AjithHi16:12
AjithHi my name is Ajith kumar, I am a newbie to the world of Linux environment. I started working with Ubuntu for the past few weeks and i am eager to contribute to the the vibrant community and i have absolutely no idea how to get started.Can some Guide me what to do?  P.S:I am a Computer science student and interested to work in coding part.16:20
Pici!contribute | Ajith there are some good links here16:23
ubottuAjith there are some good links here: To contribute and help out with Ubuntu, see http://community.ubuntu.com and https://wiki.ubuntu.com/ContributeToUbuntu16:23
AjithThank you for your help ubottu and Pici16:28
jtaylordoko: fyi a numpy delta and the fftw delta could now be dropped due to build depends on universe for main being allowed now16:54
jtaylornumpy is just for plots in the docs and fftw is an mpi library which can stay in universe16:55
slangaseknacc: archive removals, ~ubuntu-archive should be subscribed (done for bug #1564103)17:17
ubottubug 1564103 in php-horde-mongo (Ubuntu) "Please remove php-horde-mongo from the archive" [Undecided,New] https://launchpad.net/bugs/156410317:17
naccslangasek: ack, was just about to, sorry17:19
slangaseknacc: ok - figured that might be the case, but you subscribed me first so I interfered ;)17:24
naccslangasek: absolutely, appreciate it :)17:24
pittibdmurray: I'll do some tests, but if you have a setup ready for doing upgrade tests with that, that'd be appreicated of course17:32
bdmurraypitti: I did wily already17:33
pittibdmurray: oh wow, thanks17:33
tkamppeterinfinity, hi18:21
infinitytkamppeter: I'm getting there.18:25
infinitytkamppeter: You're in a queue.18:25
sarnold.. all alike18:26
tkamppeterOK18:27
infinitypitti: You still around?18:27
=== salem_ is now known as _salem
=== afkthairus is now known as athairus
=== _salem is now known as salem_
pittiinfinity: I am now (for another hour or so)19:00
Laneypitti: did you do anything to fix lxd before?19:00
pittiLaney: sorry, before what?19:00
infinitypitti:19:00
infinityApr 19 12:24:20 nosferatu systemd-fsck[574]: /dev/sda1: 7 files, 7094/489976 clusters19:00
infinitypitti: ^-- That line's hitting the console on boot.   lolwut.19:01
LaneyIt had some proxy / network problem, but then started passing19:01
LaneyThe latest upload is failing again19:01
LaneyWondering if you did some magic or if it's a real bug19:01
infinitypitti: Purely cosmetic, but between that and 1 line from the kernel, we're close to a completely quiet boot.19:01
pittiLaney: hm, no; my first reaction was that it might depend on whether it runs on lcy01 (standard cloud images) vs. lgw01 (minimized adt images), but we purge lxd on lcy01 too19:02
pittiinfinity: oh dear, I smell some plymouth ordering/race again19:02
pittiLaney: not sure what you mean, http://autopkgtest.ubuntu.com/packages/l/lxd/xenial/amd64/ looks pretty good?19:03
pittiLaney: or do you mean lxc?19:03
Laneypitti: oh, whoops, brain fart, I mean snapd19:03
Laneys/lxd/snapd/g19:03
=== pat_ is now known as pmcgowan
pittiLaney: don't do that :)19:04
pittiinfinity: oh, wait, yeah -- that's initramfs19:04
pittiinfinity: when we merged that from debian the last time, fsck and r/w mount of / moved into initramfs19:05
infinitypitti: Oh, right.19:05
infinitypitti: So, would be nice to figure out how to shut that up on !error.19:05
pittiback then I mentinoed that this will give us non-pretty fsck for root fs, but we didn't seem overly concerned19:05
pittiinfinity: well, fsck might take several minutes, you do want to see this19:05
infinityIf there's an actual fsck, that's a different case than the mount-time fake fsck.19:06
pittiinfinity: yeah, if it's quick it would be nice to hide indeed19:07
pittiinfinity: ah, the thing you quoted above is a "short" one?19:08
infinitypitti: Yeah, that wasn't a "real" fsck, that's the "you asked me to fsck a clean filesystem, so I didn nothing" fsck.19:08
infinitypitti: ie: I see it on every boot.19:08
infinityOh!19:09
infinityThat's not even my root.19:09
infinityThat's the EFI filesystem.19:09
infinityHence having "7 files". :P19:09
pittiah ok, so that should be under the control of the real root then19:11
infinityIndeed.19:12
infinityHence why it's systemd-fsck, and in the journal.19:12
pittiLaney: I interpreted http://autopkgtest.ubuntu.com/packages/s/snapd/xenial/amd64/ as "1.9.3 was broken", 1.9.4 fixed, and 2.0.2 introduced another failure19:12
infinityBut maybe the one we saw was from the initramfs.19:13
pittiLaney: and the first and second result both ran on lgw (i. e. on a minimized adt image), so not much infra difference there19:13
infinitypitti: We're going to have another look before blaming systemd.  I think your theory makes more sense.19:14
pittiLaney: did you already try running this locally?19:14
Laneypitti: I'm suspicious because the failures look the same (i.e. what we created a debug instance for mvo to mess around on the other day)19:14
pittiinfinity: I'm trying to reproduce with a fake fsck which takes very long19:14
LaneyDidn't run it myself, will do.19:14
pittiinfinity: it wouldn't surprise me at all if any of this regressed :/19:15
pittiLaney: the "error: no snaps found for "hello-world"19:15
pitti...thingy?19:15
Laneypitti: Yeah19:15
* Laney runs it19:16
mvopitti, Laney: I think its a store issue, I work on this with the store team as we speak19:17
Laneyhey mvo!19:17
Laneyyou mean a real bug?19:17
Laneyis that what you found out the other day?19:17
mvopitti, Laney: I am waiting for a new rollout, I think this will fix it19:19
mvopitti, Laney: however there might be yet another issue, but we fixed the http proxy thing so that should be ok19:19
mvothe store also moved to a cdn but that should be ok with the proxy fix we did19:19
pittiinfinity: just FAOD, this is with "splash", right?19:20
mvoLaney, pitti: so hopefulyl in ~1h we have a new store rollout and I will retrigger the tests (I hope I can actually do that)19:21
Laneyyeah, you can if you can upload it19:21
LaneyAh yeah, this fails locally19:22
pittimvo: you can test the retry button now on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#snapd (the machinery is mostly idle, so no harm)19:22
mvopitti: excellent, thanks. will do as soon as the store is updated19:23
infinitypitti: With splash, yes (though you only catch it for a brief flickery moment), shows without too, obviously.19:23
pittiinfinity: hmm, I created a partition for /mnt in fstab, and I get plymouth-y pretty fsck19:25
pitti(with a fake fsck that takes long)19:25
* pitti runs update-initramfs to get that into the initrd19:26
pittifor the root fs I seem to have the opposite problem: I *don't* get the fsck output in initramfs19:27
pittioh, I see -- it uses bash, and that's not in the initrd19:27
infinityAnd shouldn't be...19:29
pittiright, I just need to change the mock to use sh19:29
infinitypitti: What have we decided WRT snapd?19:35
pittiinfinity: AFAICT, wait for the store to get fixed (< 1 h) and retrigger the tests?19:35
pittithat's what mvo asked above, at least19:35
pittiotherwise I'm fine to hint it in if it blocks stuff19:36
infinitypitti: Well, it sort of blocks some world rebuilds slightly.19:37
mvogo and hint if it blocks stuff19:38
* pitti goes and hints19:38
pittiI went and I hinted :)19:39
cyphermox!regression-alert19:41
ubottubdmurray, cjwatson, Daviey, didrocks, doko, infinity, jdstrand, pitti, RAOF, Riddell, ScottK, seb128, skaet, slangasek, SpamapS, stgraber: reporting regression in a stable release update; investigate severity, start an incident report, perhaps have the package blacklisted from the archive19:41
cyphermoxhttps://launchpad.net/ubuntu/+source/samba/2:3.6.25-0ubuntu0.12.04.219:41
cyphermoxhttps://bugs.launchpad.net/ubuntu/+source/samba/+bug/157212219:41
ubottuLaunchpad bug 1572122 in samba (Ubuntu) "Samba upgrade break LDAP authentification only for my w7 clients" [Undecided,New]19:41
cyphermox^ someone pointed me to this19:41
cyphermoxmdeslaur: ^19:42
cyphermoxfwiw; I have two more links about the issue: http://serverfault.com/questions/771388/how-can-i-fix-samba-3-6-25-the-trust-relationship-between-this-workstation-and   http://askubuntu.com/questions/759123/samba-23-6-25-0ubuntu0-12-04-2-as-pdc-samba3-nt4-domain-windows-machines-lost19:42
tewardcyphermox: I should point out this sounds like a known issue in Microsoft's recent patches19:43
teward(not entirely related, but lots of domain auth issues on w7 after recent patches)19:43
mdeslaurcyphermox: yeah, it's broken19:43
teward^ thats what i guessed though19:43
cyphermoxteward: no idea, I don't know Samba well enough to know, and don't typically run any Windows machines here19:43
mdeslaurhave to wait for fixes from upstream/redhat19:43
cyphermoxmdeslaur: ok19:43
infinitycyphermox: stgraber and I already yelled at mdeslaur about it.19:44
infinity(After stgraber's mom yelled at him)19:44
mdeslaurinfinity: unrelated issue19:44
cyphermoxinfinity: sorry, I scrolled back and didn't see.19:44
infinitymdeslaur: Oh.  Two similar breakages?19:44
cyphermoxwhat's the other issue?19:45
slangasekcyphermox: can you remind me where that regression-alert is documented? because I'd really like to deprecate it :)  we ought to just use the regression-updates tag on bugs19:45
infinityForcing TLS unconditionally.19:45
mdeslaurinfinity: the other one isn't similar, it's that the whole point of the samba update was to disable plain text ldap19:45
infinitymdeslaur: Well, similar from the bug subject, I didn't click and read it. :P19:45
rbasakslangasek: https://wiki.ubuntu.com/StableReleaseUpdates#Regressions19:45
cyphermoxslangasek: https://wiki.ubuntu.com/StableReleaseUpdates#Regressions19:46
mdeslaurthere are currently 4 different regression from the samba badlock updates19:46
slangasekinfinity: ^^ can I rip !regression-alert out of there? :)19:46
infinityslangasek: Go nuts.19:46
Unit193slangasek: Want the trigger gone from ubottu?19:46
rbasakIt is useful to be able to be heard on occasion, as opposed to wondering if somebody's about for something one things is important.19:47
rbasak(and time-critical)19:47
rbasakI mean not for any old regression, but one that is actively breaking users and might be worth suspending.19:47
slangasekrbasak: well, the trigger in question also has a somewhat stale list of people to highlight19:49
rbasakThat's true.19:49
Unit193Could update it.19:49
rbasakI suggest updating it and updating the docs to suggest that it be used only in more restricted circumstances.19:50
mdeslaurfeel free to add me to that list19:50
cyphermoxI wouldn't mind seeing those pings either19:51
Odd_BlokeYeah, the one time I used it it was massive overkill.19:51
Odd_BlokeHad I realised what it would do, I would just have mentioned it in here and seen what happened.19:51
rbasak(by an Ubuntu dev perhaps, if not ask for an Ubuntu dev to check on the same channel, and only if suspending the update would be helpful)19:51
pittiinfinity: I finally have an initramfs compatible mock fsck, but when I  boot (the VM) with the default quiet splash $vt_handoff, I just keep the slightly purple plymouth screen and the initrd's fsck happens on VT719:53
pittimeh19:53
cyphermoxrbasak: I don't think it's used that often anyway19:53
cyphermoxand not for just any regression either19:53
pittiI see it being used once a month or less19:53
cyphermoxright19:53
cyphermoxI certainly wouldn't go nuts for a NM regression ;)19:54
cyphermoxshim/grub/boot stuff, maybe more.19:54
infinitypitti: S'ok.  I'll sort this one out with Andy, lay blame, and fix it in an SRU.  Perfectly pretty boot isn't RC, it's just nice to have. :P19:54
pittiinfinity: did we actually ever manage that?19:54
rbasakWell, an NM regression in an SRU I'd say is important. Depending on what it is. Since it could break users from updating to a regression fix.19:54
* pitti still remembers some lonesome kernel driver message in quiet mode19:55
cyphermoxrbasak: you can usually still get wired, and the big bad regressions we do catch ahead of time19:55
pittiinfinity: http://people.canonical.com/~pitti/scripts/fsck-mock-initrd is the mock I replaced /sbin/fsck with, FTR19:56
ogra_pitti, until u upgraded to xenial my XPS13 never showed me anything but plymouth til lightdm (now i have two  lines of fsck output since the upgrade)19:56
ogra_so yes, at least on preinstalled OEM hardware we achieved it :)19:56
pittiwe merged initramfs-tools like three months ago, this can hardly be a new thing?19:57
rbasakcyphermox: not everyone can get wired. This laptop I'm on cannot, and I don't have a dongle that'll work handy.19:57
pittiso seeing fsck output was actually known; the bit that's not known is *not* seeing it, i. e. hiding it behind plymouth if fsck happens in the initrd19:57
infinitypitti: Probabaly not new, I think I was blaming the kernel unti lnow.19:57
pittiactually, we did know that too19:57
infinitypitti: Don't worry about it.19:57
infinitypitti: I'll worry for both of us. :P19:57
rbasakAnyway, my point is that some regressions are bad, and I'd like to shout (and have a good chance of being heard) about time critical ones. That's all.19:58
pittiinfinity: okay :) I guess bedtime then19:58
cyphermoxrbasak: don't upgrade for my next upload then, we started dropping wifi, it was too broken ;P19:58
cyphermoxjust kidding, of course19:58
rbasak:)19:58
pitticyphermox: actually, NM 1.2 landed remarkably quietly, well done19:59
rbasak"wifi support removed due to unreliability issues"19:59
slangasekyeah, only joking, we've been dropping wifi forever19:59
cyphermoxpitti: so you say.19:59
cyphermoxslangasek: ah ah only serious19:59
rbasak"tinfoil DoS vulnerability" (cover the aerial)19:59
slangasekpitti: a little too quietly, right cyphermox?19:59
* slangasek looks at his empty logs20:00
cyphermoxit's not a murder, but it's not as pretty as it seems either20:00
pittiwell, it's not like I'm reading NM bugs, but I didn't hear any complaints20:00
cyphermoxslangasek: on that subject, would you mind bringing up logging in wpasupplicant to 11 and looking if the logging gets better?20:00
slangasekcyphermox: if you give me directions how20:00
Odd_Blokeslangasek: It's one louder.20:01
slangasekOdd_Bloke: look over there, it's a cloud shaped like a velociraptor20:01
pittixnox: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qemu seems to make nova unhappy (uninstallable), can you have a look?20:01
cyphermoxslangasek: add many -d 's to the Exec line in /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service20:02
cyphermox-dd or -ddd would be good20:02
cyphermoxit *will* log a lot more though20:03
pittimeh, what's up with s390x tests20:04
slangasekcyphermox: ok.  also the wireless hasn't dropped since yesterday so now it's teasing us20:04
Unit193cyphermox: So that'd be add you and md, drop Riddell, Scott, skaet, and SpamapS?20:04
cyphermoxwhy do I always get the heisenbugs?20:04
cyphermoxUnit193: I suppose yeah, unless slangasek really wants to drop it completely20:04
infinitypitti: I see no reason that should actually be true.20:04
slangasekcyphermox, Unit193: I honestly don't think it's useful; I think rbasak knows how to get ahold of SRU team members without it, and generally it renders for me as a contentless highlight well after I've read the bug in email (if the bug is tagged appropriately)20:05
slangasekif you want to omit me from the highlight list that is also ok ;)20:05
cyphermoxif it's not documented, why bother keeping it?20:06
* rbasak shrugs20:08
slangasekif someone who knows about it wants it there and wants to use it, I don't mind it being there and won't tell other people how to run their bot20:08
rbasakI don't particularly mind either way.20:08
rbasakSince I can always highlight people manually if I feel the need as you point out I suppose.20:08
infinityI don't read mid-line highlights anyway.20:09
rbasakAs long as it doesn't result in some additional delay for some serious could-have-acted regression.20:09
infinitySo lists don't work for me.20:09
rbasak(I only recall having found one or two since I started Ubuntu development in 2011)20:10
Unit193So I can talk about infinity all I want and he'd not see it?  Awesome. :D20:10
* Unit193 ducks.20:10
rbasakI don't particularly mind either way> I suppose that's different to what I said earlier. I'm weakening my objection.20:11
Unit193!forget regression-alert20:15
ubottuI'll forget that, Unit19320:15
Unit193cyphermox: There you go.20:15
rbasakDoes reverse-depends tell me about the release pocket or the proposed pocket?20:22
tumbleweedrelease20:22
rbasakOK, thanks20:22
pittiThe following packages have unmet dependencies:20:33
pitti qemu-system : Depends: qemu-system-s390x20:33
pittiinfinity: ^ my xenial-proposed schroot says there is a problem -- maybe just publisher delay from binNEW or so?20:33
pitti qemu-system-s390x | 1:2.5+dfsg-5ubuntu9 | xenial-proposed | s390x20:33
pittiit doesn't exist on any arch but s390x20:33
pittibut all arches depend on it20:33
pittixnox: ^20:34
infinitypitti: Oh.20:34
infinitypitti: Yeahp, that's a bug.20:34
slangasekinfinity, pitti: shall I fix?20:34
infinityslangasek: Go nuts, if you know how.20:34
LaneyThree uploads the charm20:34
infinityslangasek: The qemu packaging is whack, yo.20:34
pittiis it meant to exist on all arches, or is the dep only meant to exist on s390x?20:34
infinityNo, it's meant to only exist on s390x due to not having system emulation.20:34
* pitti guesses/hopes the former, would be nice :)20:34
slangasekit's a kvm implementation, should not exist on other archs20:34
infinityqemu-system shouldn't depend on it.20:34
pittiah, ok20:34
infinityNote qemu-system doesn't depend on qemu-system-aarch64 for the same reason, so there should be precedence in the packaging.20:35
Unit193Alright, I'm confused how seed blacklists are supposed to work then, it doesn't appear to as in the manpage.  If I blacklist !foo, and it's in an inherited seed, the manpage says it should still be blacklisted and I see in the output '* Blacklisting foo from bar' but it still ends up in the bar-recommends-arch.  What gives?20:38
pittiinfinity: would you prefer when I fakesync python-virtualenv -3 (to fix the regression in -proposed) now, or wait until tomorrow when it published in Debian and gets imported into LP?20:40
pitti(see barry's email)20:40
pittialthough, this change looks strange, just saw the diff20:40
infinitypitti: It's not seeded, don't care about timing.20:41
pittiack20:41
slangasekpitti, infinity: qemu uploaded to fix the bug introduced by that old engineer who refuses to recognize non-mainframes are real architectures20:43
pitti"old"? :-)20:43
pittiisn't he like the youngest of us all? :-)20:44
slangasekpitti: he aged 50 years instantaneously the first time he connected to z/VM20:44
pittioh, right -- time acceleration near super-fast machines20:44
pittiam I glad that this doesn't affect ssh connections20:45
cyphermoxssh going too fast?20:49
Unit193cjwatson: Perhaps you can tell me what I'm doing wrong, re: above?21:00
seb128slangasek, Laney, infinity, /etc/X11/Xsession.d/60x11-common_xdg_path do "XDG_DATA_DIRS=/usr/share/"$DESKTOP_SESSION":"$XDG_DATA_DIRS"", and worth case if that would be missing it would only means the override doesn't work so not break much, also the Name= translations are stripped by dh_translations in favor of using gettext so we can langpacks21:10
slangasekUnit193: blacklist doesn't cause the package to be un-seeded; instead it causes the seed as a whole to be considered buggy and invalid if a package is in the seed and matches the blacklist21:11
seb128slangasek, oh, and please tell me what is wrong with my sed use so I do the correct thing next time :-)21:12
slangasekseb128: two sed commands operating on the same file, so you're repeating the filename... you can pass multiple commands to sed, either as multiple '-e' arguments or just as commands separated by semicolons21:13
Unit193slangasek: Dang, I knew it didn't prevent installation, but from the manpage it seemed like it at least prevented from explicitly being selcted. :/21:13
seb128slangasek, oh, good point, I didn't think much when doing that :-/21:13
slangasekUnit193: it will cause an image build to fail, which is a bit late in the process21:13
slangasekseb128: and it wasn't a critical blocker ;)21:13
seb128slangasek, I'm going to change it with the next upload21:13
Unit193...Wow, that's near useless.21:13
Unit193slangasek: Thanks for the info.21:13
seb128right, was just curious why you meant by "non-DRY"21:14
slangasekseb128: DRY == Dont Repeat Yourself :-)21:14
seb128ooh, gotcha!21:15
roaksoaxwin 821:15
seb128slangasek, also I'm pondering doing another upload tomorrow (if we get a respin) to include some translations, we could strip the X-Gettext-Domain= for release and put Name[locale]=<translations> entries in the new desktop21:16
seb128then go back to langpacks in a SRU when we get a new langpack export which contains translations for the string21:16
slangasekinfinity: ^^21:17
=== salem_ is now known as _salem
dokocyphermox, console-setup ftbfs23:30
cyphermoxwat23:46

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