/srv/irclogs.ubuntu.com/2017/02/21/#ubuntu-devel.txt

=== NCommander is now known as Guest61042
cpaelzergood morning06:33
=== jamesh_ is now known as jamesh
cult-xnox: when it's going to be released just out of curiosity?08:41
cpaelzerhmm, when I upgrade from A to a newer A' which now has a recommends to B will be auto-installed on the upgrade09:00
cpaelzerI know it would on install09:01
* cpaelzer heads raeading docs (but would be happy if one just knows)09:01
LocutusOfBorgyofel, please merge/sync libqapt and baloo? I have not enough knowledge for doing it by myself sorry09:10
=== jamespag` is now known as jamespage
pittiLaney: the two UPSTREAM_PULL_REQUEST=4670 ones in http://autopkgtest.ubuntu.com/running#pkg-systemd-upstream seem to loop; are there any errors in the logs?10:26
pittiLaney: yesterday they still ran and failed; then https://launchpad.net/ubuntu/+source/ifupdown/0.8.16ubuntu1 landed, maybe that changed/broke something10:27
Laneyhey pitti10:28
Laneylet me see10:28
Laneyall arches?10:28
pittiLaney: both i386 and amd64, yes10:29
pitti(I didn't trigger s390x, no point)10:29
Laneypitti: don't those upstream ones run on xenial?10:32
Laneywhy would an ifupdown in zesty break that?10:32
pittiLaney: I  manually triggered test runs on zesty, as this is useful for that PR10:32
Laneyoh right10:32
pittiLaney: that uses the new unified cgroup hierarchy on kernels that support enough of it, which isn't the case yet on xenial10:32
Laneyok, let me look for that then10:32
pittiso xenial is for "this doesn't break stuff on older kernels and continues to use cgroupsv1", and zesty is "this doesn't break on unified hierarchy"10:33
Laneythere's one running, /me tail -fs that10:33
pittiLaney: I have a feeling that it already has ran several times since yesterday evening; they usually take 1:30 hours or so10:33
pittiLaney: so I was wondering if there's any nova console log (or similar) in the journal already10:34
LaneyI just see the testbed failure10:35
Laneyah wait, there's an aborted worker10:35
LaneyFeb 21 08:03:28 juju-prod-ues-proposed-migration-machine-3 sh[5696]: Selecting previously unselected package libio-html-perl.10:36
Laneyit just ends on a package installation10:36
LaneyFeb 21 06:57:03 juju-prod-ues-proposed-migration-machine-3 sh[5839]: Selecting previously unselected package autoconf.10:37
LaneyFeb 21 06:21:49 juju-prod-ues-proposed-migration-machine-3 sh[5669]: Get:71 http://ftpmaster.internal/ubuntu zesty/main i386 libip4tc-dev i386 1.6.0-3ubuntu2 [6,534 B]10:38
Laneyhmm10:53
Laneypitti: is this helpful?10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: [    2.128242] Unable to open file: /etc/ima/ima-policy (-2)[    2.129043] IMA: policy update failed10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: [    2.129613] audit: type=1802 audit(1487638604.548:2): pid=1 uid=0 auid=4294967295 ses=4294967295 op="policy_update" cause="fa10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: [    2.141903] ip_tables: (C) 2000-2006 Netfilter Core Team10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: [    2.146335] systemd[1]: Failed to create symlink /sys/fs/cgroup/net_cls: Operation not permitted10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: [    2.147550] systemd[1]: Freezing execution.10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: ---------------------------------------------------10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: <VirtSubproc>: failure: Timed out on waiting for ssh connection10:54
LaneyFeb 21 01:01:46 juju-prod-ues-proposed-migration-machine-3 sh[26926]: autopkgtest [01:01:42]: ERROR: testbed failure: unexpected eof from the testbed10:54
xnoxpitti, we landed 4.10 kernel too11:12
* ogra_ hopes 4.10 passes quickly ... always makes me think "oh the warty kernel"11:13
=== _salem is now known as salem_
pittiLaney: sorry, long phone call11:16
pittiLaney: it looks related, yes; /sys/fs/cgroup/net_cls wouldn't exist any more with the unified hierarchy, just not sure why this would cut the ssh connectino11:17
pittixnox: oh right, only 10 hours ago, that could be relevant11:20
Laneypitti: Someone posted "Freezing execution" on the PR too11:22
Laneyseems that was with 4.9 though11:23
pittiLaney: any chance you could put the /tmp/autopkgtest.*/binaries/*.deb somewhere? I'd like to see if I can reproduce this locally with today's cloud image11:25
pittiworked fine yesterday still11:25
pittiLaney: I could also rebuild it myself, but the binaries should already be there in the running tests, so convenience..11:25
Laneyone second11:26
Laneygot to pull this string11:27
pittiLaney: ah bummer, current retry is still at package building stage11:27
Laneyno I've got binaries11:28
pittioh, cool11:28
Laneyno version in the filename11:28
Laneyis that normal?11:28
Laneypitti: http://people.canonical.com/~laney/weird-things/systemd.tar.xz11:34
pittiLaney: yes, that's normal11:34
pittiLaney: many thanks!11:36
Laneypitti: just got them out in time ;-)11:36
Laney(died now)11:36
LaneyI'll filter these out now if you don't mind11:36
pittiLaney: yes, please11:37
pitti[    2.080076] systemd[1]: Failed to create symlink /sys/fs/cgroup/net_cls: Operation not permitted11:38
pittigotcha11:38
pittitrivial to repro locally11:38
Laneyit killed the VM too?11:38
LaneyI should throttle debmirror somehow, kills SSH latency when it's running11:39
pittiLaney: yep, same "freezing execution", I followed up to the PR11:40
pittiLaney: so presumably it's a regression from the followup pushes yesterday  evening11:40
pittiunfortuantely ridiculously hard to detect by heuristics11:41
pittiunless we add "Freezing execution" to the list of strings it watches out for; we now have strings for kernel crashes, don't we ?11:41
pittisimilar to f9b3ee01e911:42
Laneypitti: could do, if that always indicates a failure11:43
Laneybit of whack a mole, but what can you do?11:43
dokoapw, infinity: what's the estimate for linux 4.10 and glibc 2.25 in z? asking for the test rebuild11:55
pittidoko: linux 4.10 landed yesterday (there's some fixes in -proposed, but hopefully shouldn't affect the headers much?)11:58
dokoahh, I see11:59
mdeslaur@pilot in12:37
=== udevbot changed the topic of #ubuntu-devel to: Yakkety Yak (16.10) Released | Archive: feature freeze, DIF | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-yakkety | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots: mdeslaur
Laneypitti: https://paste.ubuntu.com/24040277/ ?13:43
pittiLaney: nice! thanks13:47
Laneypitti: ok, deployed, could you trigger the test again to test it please?13:52
Laneyjust pick one arch13:52
pittiLaney: triggered amd6413:53
Laneymerci13:53
pittiLaney: merci à toi ! I'll trigger i386 after amd64 failed "properly"13:53
pitti(although, that doesn't really tell us anything, nevermind)13:54
LaneyYou'll get a nice 'x' on the PR :P13:54
pittiI already get that with one failure13:54
BluefoxicyI wish apt and update-manager had an integrated system to pull all process ids, identify all loaded binaries, and list everything using a binary which has been replaced14:14
Bluefoxicythat way when you update e.g. openssl, you can list everything running that's still using the previous version, and restart services or browsers14:14
Snow-Manuh14:16
Snow-Mancheck_libs14:16
Snow-ManDoes basically exactly that...14:16
Bluefoxicyoh cool14:16
Snow-ManI agree that it'd be nice if apt would tell you too.14:16
Bluefoxicycommand not found14:16
Snow-Mannagios-plugins-contrib: /usr/lib/nagios/plugins/check_libs14:17
Snow-Manheh14:17
Bluefoxicyoh lol14:17
Snow-Manlsof works too tho14:17
Snow-Manand is what check_libs runs14:17
Saviqwgrant, hey, looks like builders got a kernel upgrade again? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2457/+build/1203974014:20
=== barry` is now known as barry_
=== barry_ is now known as barry
ilmaisinhi14:56
ilmaisinhow do i report a disruptive user in launchpad?14:56
ilmaisinblacksheep001 keeps spamming some internet connection questions to cups bug reports14:57
ilmaisinwon't believe when i ask him to stop14:57
seb128ilmaisin, you can try asking on #launchpad but I think the recommended way is to use https://answers.launchpad.net/launchpad/+addquestion15:05
ilmaisinseb128: thanks15:05
seb128ilmaisin, yw!15:05
=== dgadomski_ is now known as dgadomski
tinococpaelzer: are u also taking care of qemu for trusty ?16:02
tinocoqemu/libvirt16:02
cpaelzertinoco: as much as possible :-)16:02
tinococpaelzer: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/131749116:02
ubottuLaunchpad bug 1317491 in libvirt (Ubuntu Trusty) "virsh blockcommit hangs at 100%" [Medium,In progress]16:02
tinocoi'll probably block the "block-commit" feature in libvirt for Trusty16:02
tinoco(just for active block devices)16:02
tinocoits broken anyway16:02
tinococpaelzer: could u review it for me so I can prepare the SRU ?16:03
cpaelzertinoco: yes, but not today16:03
tinococpaelzer: cool, i'll prepare the debdiffs and wait for you16:03
cpaelzertinoco: drop me a mail and I'll look at it then16:03
tinococpaelzer: ill attach them to the case and email you16:03
tinococpaelzer: tks buddy16:03
smoserxnox, around ?16:25
xnoxsmoser, sure! what's up?16:25
smoseri saw you re-ran some tests or open-iscsi once16:25
smoseri filed https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/166657316:25
ubottuLaunchpad bug 1666573 in open-iscsi (Ubuntu) "transient systemd ordering cycle in boot with overlayroot ver read-only open-iscsi root" [Medium,Confirmed]16:25
smoserwith some diagnosis comparing the pass and fail, and wanted to know if anything jumped out as you asa the reason for the transient results.16:25
* xnox learns a new word "posterity"16:26
smoserthe top 4 runs at http://autopkgtest.ubuntu.com/packages/o/open-iscsi/zesty/amd64 show pass and fail of identical runs16:26
xnoxsmoser, what updates the /etc/fstab? is it done in the initramfs before systemd is started?16:27
* nacc has noticed for a few packages in excuses that the oldest success has no logs -- is that something that can be avoided (i'm assuming maybe it got pushed off the bottom of the list, but still shows up on the web UI, e.g.: http://autopkgtest.ubuntu.com/packages/p/puppet/zesty/amd64)16:27
smoseroverlayrooto before intiramfs16:27
smoserer...16:27
smoserin initramfs16:27
smoserby overlayroot16:27
xnoxsmoser, there is possibly a race between fstab-generator and /etc/fstab being updated; if the update is not done in the initramfs.16:27
xnoxah, good.16:27
smoserthe attached .tar.xz has "short" logs (just the tgt-boot-test output)16:29
smoserand they actually compare side by side reasonably well with vimdiff16:29
smosercpaelzer, ^ i think that could be part of your issue with open-iscsi tests16:30
* cpaelzer reads backlog16:30
zuldoko: ping can you review os-faults wen you get a chance its a new dependency for rally16:31
dokozul: yes, will do it tomorrow morning16:33
zuldoko: thank you16:34
mdeslaur@pilot out16:35
=== udevbot changed the topic of #ubuntu-devel to: Yakkety Yak (16.10) Released | Archive: feature freeze, DIF | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-yakkety | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | Patch Pilots:
naccis there a convenient way for me to test the exact environment the autopkgtests run in? That is, http/https proxies and all. I think the puppet failure is due to https_proxy being set, but I'm not 100%16:47
jgrimmnacc, i'm interested in that too16:56
naccjgrimm: will keep you posted16:56
jgrimmtx16:57
naccLaney: --^ you may know16:57
Laneyafraid not16:57
naccLaney: np, thanks!16:59
naccLaney: you've just educated me on several other autopkgtest nuances :)16:59
naccjgrimm: ah, i think i see the puppet failure a bit clearer now (and why my initial 'fix' does workaround it, but is incorrect). I think the tests assume a host-naming pattern of 'puppet'.17:02
naccjgrimm: so when it attemps to use https://puppet... it will alias to localhost when Debian tests17:02
jgrimmnacc, aha.  tho, i was more interested in the part of your question that asked how to create the exact autopkgtest environment. :)17:05
naccjgrimm: understood, just fyi :)17:06
naccstgraber: `lxc --sudo --name puppet-1487554013 adt-sid-amd64` -- would that set the container's 'hostname' to puppet-1487554013 ?17:07
naccstgraber: ah nm, that's an autopkgtest-virt-lxc option17:10
Laneynacc: yes, it's passed to lxc-start --name17:12
naccLaney: yep, i see that now, thanks!17:13
Laneynacc: One way to do your thing might be to make the lxc/d runner apply a profile, and construct one of those which blocks network access other than to a proxy17:14
LaneyAssuming you can make such profiles (I don't actually know that)17:14
naccLaney: yeah, that's a thought. I think a much simpler one (looking at the test case ruby now), would be to just have puppet use the actual hostname at run-time, rather than assuming it's 'puppet' (and accessible at that hostname). There's nothing in the tests that asserts that's true.17:15
Laneynacc: That helps for this one problem, but not in general :P17:19
naccLaney: yeah :)17:19
LaneyWell done potentially finding the issue though17:19
Laneyyou can invoke autopkgtests against a PPA FYI17:19
naccLaney: only because in this case, I don't think the proxy is actually the problem17:19
Laneyso no need to upload to the archive to verify your fix if it's environment dependent17:19
naccLaney: ah that would be great -- documentation for it?17:20
Laney...17:20
LaneyI knew you'd ask that17:20
naccheh17:20
jgrimmnacc, or bileto!17:20
naccLP: #1550280 implies it's not present17:20
ubottuLaunchpad bug 1550280 in Launchpad itself "autopkgtest: allow testing against private PPAs with private results" [High,Triaged] https://launchpad.net/bugs/155028017:20
naccjgrimm: good point17:21
Laneyprivate no, but public ones sure17:21
naccLaney: err, right!17:21
Laneymeh, got to get this from the source17:23
Laneynacc: ok, I think it's &ppa=user/ppa (https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=puppet&ppa=nacc/myppa)17:25
Laneyif that works, would appreciate a sentence on https://wiki.ubuntu.com/ProposedMigration :-)17:26
naccLaney: ack, will test that!17:26
naccLaney: https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=puppet&ppa=nacc/lp1570472&trigger=puppet/4.8.2-3ubuntu2~ppa1, FYI17:41
naccLaney: will update the docs17:41
Laneynacc: it got published already?17:41
naccLaney: my upload to my PPA did yeah17:41
Laneywowzers17:41
Laneythings are fast these days17:41
naccLaney: yeah, faster than I expected :)17:41
Laneynext challenge is finding the results :P17:42
nacc:) was just going to ask17:42
Laneyhttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-nacc-lp1570472/?format=plain17:42
nacchrm, I get Unauthorized17:43
Laneythe container is made when the first result is uploaded17:43
Laneyoops, and I've just clicked on a huge text file which has killed firefox for the next X months17:45
naccLaney: so... once it's done, should i be able to access the above log?17:52
Saviqwgrant, hey, did you see my message before about arm64 builders crashing in QML again? (bug #1630906)17:52
ubottubug 1630906 in linux (Ubuntu) "QML segfault on arm64 due to builder kernel change" [Undecided,Confirmed] https://launchpad.net/bugs/163090617:52
Laneynacc: yup17:53
Laneywell, it'll be an index, and then you construct the path from that17:53
Laneyyou can see that the UX here has had a lot of thought :/17:53
Laneyto be fair it was mostly designed to be driven by machines17:54
Laneybut I'm sure we could make it more user friendly somehow17:54
naccLaney: totally understood17:54
smoserxnox, i did manage to catch a failure that i have emergency console access to if you were looking at bug 1666573 and needed anything17:57
ubottubug 1666573 in open-iscsi (Ubuntu) "transient systemd ordering cycle in boot with overlayroot ver read-only open-iscsi root" [Medium,Confirmed] https://launchpad.net/bugs/166657317:57
naccLaney: and i'll update the wiki to indicate you can see it running on the main autopkgtest page17:59
=== mwsb is now known as chu
xnoxsmoser, a dump of journal would be nice17:59
Laneynacc: Aye - you can see the formula for getting the index from that URL I gave18:00
xnoxif you can save / extract / copy if somwhere18:00
Laneyautopkgtest-release-username-ppaname18:00
Laneyin fact that's documented at https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Container_Names18:01
Laneybut that tells you more than you need to know18:01
* Laney imagines a CLI tool for all this18:01
Laneyok, those rocks aren't going to climb themselves18:03
Laneyo/18:03
naccLaney: thanks and enjoy!18:04
=== mardy_ is now known as mardy
naccjgrimm: in case you didn't see it: "Testing against a PPA" at https://wiki.ubuntu.com/ProposedMigration18:05
jgrimmnacc, tx18:06
naccLaney: just fyi, my autopkgtest seems wedged18:58
naccif anyone else has access: http://autopkgtest.ubuntu.com/running#pkg-puppet ran that aginst my PPA18:58
naccit looks like it's done and passed, but i've not seen any log change in a while now18:59
naccand I can't access the underlying logs until the jobs is done, afaict18:59
naccLaney (and anyone else): nevermind, it worked, it was just taking a while to extract the logs, i think19:34
robruanybody around that can help with an autopkgtest issue? sqlparse update is held back because failing autopkgtest with python-django-debug-toolbar 1.5, the issue is fixed by 1.6, which is in -proposed, but it's invalidated by sqlparse, which is invalidated by the autopkgtest run from 1.5. Not sure how to kick that autopkgtest with 1.6 which should work (I19:44
robruchecked the source and the traceback is resolved in 1.6)19:44
naccrobru: have you tried rerunning the test?19:45
naccrobru: i think it should use the new version if it's in z-p now19:45
robrunacc: yeah, gives very strange output where it claims to be installing 1.6 deb but traceback references 1.5 source tree (and same traceback): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/p/python-django-debug-toolbar/20170221_180502_a55de@/log.gz19:46
naccrobru: ah it's using the z-p to satisfy the debends, but the test it is running is from the 1.5 src19:48
nacc*depends19:48
robrunacc: any thoughts how to fix that?19:48
naccrobru: thinking -- there is a proposed flag we can pass to the test to use proposed for everything, but i'm not sure if that's what we need here or not19:49
robrunacc: I have no idea. I mean the log already shows it's installing the correct version of the deb, so I'm not sure where it's even getting the 1.5 source tree from19:49
naccrobru: because that's the version the test is running (earlier you can see it downloads the 1.5 src)19:50
naccrobru: the way it works is that only sqlparse will come from z-p by default19:50
naccrobru: for this specific run19:50
nacc--apt-pocket=proposed=src:sqlparse19:50
robrunacc: oh well, can you rerun with --all-proposed then? should fix it19:51
naccrobru: let me try it19:51
robruthanks19:51
naccrobru: trying amd64 first, let's see if it passes19:51
=== salem_ is now known as _salem
robrunacc: I just double checked, v 1.6 absolutely fixes this traceback, no doubt.19:52
robrumaybe some other problem will arise, not sure, but this specific traceback is for sure fixed by 1.6 ;-)19:52
naccrobru: ack19:52
pittiLaney: nice, that worked! proper failure with useful log now; thanks!19:57
robrunacc_: oooh I see the pass, thanks!20:02
robrunacc_: try the other arches please ;-)20:03
jbichabarry: hi, systemd-resolved hasn't been working smoothly here, bug 166602120:06
ubottubug 1666021 in systemd (Ubuntu) "zesty systemd-resolve timeout" [Undecided,Confirmed] https://launchpad.net/bugs/166602120:06
naccrobru: ok, looks like it passed on amd64, will trigger the others20:07
naccrobru: will take excuses a bit to see the passes, ithink20:07
barryjbicha: interesting.  i haven't seen this, but then i don't suspend20:16
jbichawell the initial report wasn't about suspend, it was about first boot20:17
jbichamaybe there's multiple issues combined into one report but I didn't know where to split it20:18
barryjbicha: i have seen problems with resolving names right after first boot, but that predates the recent n-m or systemd uploads.  e.g. after first login, i have chromium set up as a start-up app, but after first login post-reboot, most of the tabs cannot load.  reloading always fixes it, so there is definitely something going on around boot20:20
jbichaok, but with the symptoms I experienced and the workaround (just restart resolved), it's very convenient to blame resolved now20:24
=== kees_ is now known as kees
zuldoko: networking-bagpipe and networking-bgpvpn as well please20:29
naccrobru: yeah, amd64 just ticked over, at least, looks like it's passing elsewhere too20:30
robrunacc: thanks!20:31
naccrobru: and sqlparse is now a valid candidate21:01
robrunacc: yay, thanks!21:01
naccrobru: np!21:01
scootergrisenCan anyone help me get danish translation into the Ubuntu ISO live?21:18
scootergrisenSo when i select danish language during boot its translated to danish without having to install danish language.21:18
robrunacc: http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#libseccomp all these regressions appear to me to be transient network issues, can you retry them?21:25
naccrobru: looking21:49
naccrobru: done21:50
robrunacc: thanks!21:50
wgrantSaviq: Not at 4am. Fixing.22:38
Saviqwgrant, duh, was sure you're closer than that on the timezone front... thanks :)22:41
naccjgrimm: ping23:11
jgrimmnacc, pong23:11
naccjgrimm: I *think* your openvpn upload may have inadvertently broken the Canonical VPN cxn with NM on upgrades :) related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848062 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84806223:12
ubottuDebian bug 848062 in openvpn "Warn users of removed tls-remote option" [Normal,Fixed]23:12
naccspecifically, i get "Options error: Unrecognized option or missing or extra parameter(s) in [CMD-LINE]:1: tls-remote (2.4.0)"23:12
sarnoldnacc: from #distro "You have to change VPN -> Advanced -> TLS Authentication -> "Server certificate check" to "Verify name exactly" and remove the /CN: or whatever it is"23:14
jgrimmnacc, fun times!23:14
naccsarnold: yeah, we should put that somewhere, though -- release notes, or in a NEWS file?23:14
jgrimmyeah, release notes at very minimum23:15
naccsarnold: but thank you for the pointer!23:16
naccsarnold: as to the remove the '/CN: ...' it doesn't let that be empty (understandably, i think) -- so does that mean remove the value for /CN?23:18
naccsarnold: nm, i undestand now23:19
sarnoldnacc: I assumed it meant the non-data annotations..23:19
naccjgrimm: so in that particular case, elide the '/CN:' string specifically23:19
jgrimmnacc, correct23:19
naccjgrimm: will you follow up on that with the release notes? i have a feeling it will bite people23:19
jgrimmnacc, yeah i'll go add a blurb now23:20
naccjgrimm: thanks23:21
Laneynacc: FYI you can add extra triggers instead of all-proposed23:48
Laneywhen retrying tests23:49
Laneythey translate into src:proposed things basically23:51

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