=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
pstolowskimorning trainguards! any idea why silo 27 failed on dependencies https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-027/+build/7767209 on ppc and arm but built fine on others? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-027/+packages07:07
pstolowskimoreover, the status of the silo in citrain says all has been built fine, but ppa status disagrees?07:10
Mirvpstolowski: unity8 hasn't ever built for arm64 powerpc ppc64el, therefore train thinks it's ok. like it says, dependencies are missing.07:26
Mirvpstolowski: note armhf built fine, just arm64 didn't07:26
pstolowskiMirv, hmm, so all is fine with that silo?07:28
Mirvpstolowski: looks so07:47
pstolowskiMirv, yeah, thanks for explaining!07:47
sil2100So... so hot!07:48
sil2100Mirv, davmor2, ogra_, popey: I would opt for skipping todays morning meeting, not much to discuss07:49
sil2100And I would have to put something on me for the hangout07:49
Mirvogra_: ok then07:52
Mirvsil2100: please don't share more07:52
Mirv(although, likewise)07:52
popeyGO TEAM PYJAMAS!07:56
ogra_bathrobe rockers please :)07:57
ogra_sil2100, hmm now the armhf build has dependency issues too07:58
ogra_failing on obexd-server07:58
sil2100ogra_: anyway, looking into that08:03
sil2100Thanks for the heads up!08:03
ogra_UH !08:04
ogra_so the ubuntu-system-settings landing sits on top of wily packages ?08:04
ogra_(at least that is what the changelog suggests)08:05
ogra_ ubuntu-system-settings (0.3+15.10.20150804-0ubuntu1) wily; urgency=medium08:06
sil2100ogra_: yeah, dual landings work like that08:06
sil2100We don't re-write history, just the top most changelog entry08:06
ogra_well, do you also not re-write dependencies ?08:06
ogra_pulling in the wily bluetooth deps might indeed explain this08:07
ogra_(assuming they are different)08:07
sil2100No, it's the lander that needs to make sure the deps are sane on both platforms08:08
sil2100The recent u-s-s upload didn't have any packaging changes08:09
sil2100But maybe the one before that08:09
sil2100Need to dig into the changes for that08:09
davmor2sil2100: you can just turn off the camera like ogra_ does ;)08:09
ogra_-         qtdeclarative5-ubuntu-settings-components (>> 0.2),08:10
ogra_+         qtdeclarative5-ubuntu-settings-components (>> 0.6),08:10
ogra_thats the only possibly relevant dependency change08:10
sil2100Launchpad doesn't work for me right now08:10
sil2100ogra_: the overlay has 0.6+15.04.20150716-0ubuntu1 of that package08:11
ogra_yeah, and there doesnt seem to be anything that could break it like that08:12
ogra_its not that08:12
sil2100https://lists.launchpad.net/landing-team-changes/msg00368.html <- maybe this landing was responsible?08:13
sil2100As it's trying to install ubuntu-system-settings-online-accounts08:13
ogra_but it most likely is system-settings related ... i386 has the same error (on top of the old dep issue)08:13
ogra_* No-change test rebuild for g++5 ABI transition08:14
ogra_huh ??08:14
ogra_the wily changelog confused me again08:14
sil2100Don't worry about the changelog08:14
sil2100hm, no dep changes there through08:15
ogra_sil2100, if i wouldnt know better, i'd say the seed change from wily landed in vivid08:15
ogra_but thats not possible08:15
sil2100Nothing like that landed: https://lists.launchpad.net/landing-team-changes/08:16
sil2100Ok, I'll try digging into that on my device08:18
ogra_no, but we also have security and updates enabled during build08:18
sil2100Yes, but nothing landed there too re: the seeds08:18
sil2100I think I'm getting close to the problem08:24
sil2100hah, ok, see the problem...08:28
sil2100ogra_: so the problem is in libtimezonemap1 (from the libtimezonemap source)08:28
sil2100ogra_: u-s-s was built against the version in -proposed08:28
sil2100ogra_: since we build out silos with -proposed enabled, and the new libtimezonemap still didn't migrate08:29
ogra_ah !08:29
sil2100So u-s-s is uninstallable with other packages... we need to migrate it08:29
sil2100There's no hard dep, but the binary packages depend on it as that's what it was built against08:29
sil21000.4.3.1 - this needs to go out, let me check excuses08:29
ogra_on a sidenote wily i386 fails too ...08:30
ogra_The following packages have unmet dependencies:08:30
ogra_ ubuntu-touch : Depends: qtmir-android but it is not going to be installed08:30
ogra_                Depends: qtubuntu-android but it is not going to be installed08:30
ogra_(probably not that urgent :) )08:30
sil2100ogra_: yeah, didn't have time for that yet ;) Since emulator is b0rken anyway08:31
ogra_wily ... not vivid though ...08:31
ogra_(not sure if the emulator was broken there too, now it clearly is though :) )08:32
sil2100hmmm, we need to somehow resolve this, I might even consider copying this package to the overlay08:33
sil2100Since it still needs to wait a bit in the SRU queue08:33
sil2100Building against -proposed in the case of an already released series is not a good idea ;)08:33
ogra_at least if your silos dont have proposed-migration too :)08:34
sil2100seb128: would you mind me copying over the binaries of libtimezonemap from -proposed to the overlay? :)08:34
seb128sil2100, please do08:34
seb128unsure what's the issue08:34
sil2100ogra_: true ;p ALthough we would have a slightly different -proposed pocket anyway08:34
ogra_seb128, dep issues08:34
seb128the soname didn't change, why is u-s-s having an updated depends?08:34
ogra_seb128, silos buld against proposed but their packages dont go through the migration08:35
seb128like no public interface changed08:35
sil2100seb128: u-s-s built against the libtimezonemap in -proposed, not sure why it actually hard-depped the binary deps08:35
sil2100It's certainly something worth looking into, but generally copying the package is much faster08:36
ogra_there you go :)08:36
sil2100Oh man, I hate that one08:36
seb128that package always update its shlibs to current08:36
sil2100I once got yelled at for sigining off a package with this in the old times08:36
sil2100Packages copied, I'll re-kick the image build in a moment08:40
=== ljp is now known as lpotter
=== chihchun is now known as chihchun_afk
pstolowskisil2100, hey, we have failure on version check https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/176/console, presumably because we're trying to land in vivid overlay only. what is the best course of action?10:08
sil2100Let me take a look10:09
pstolowskisil2100, we have single trunk for both wily and vivid10:09
pstolowskisil2100, and i don't want to dual land atm due to the issues10:09
sil2100Ah, yeah...10:09
sil2100This is a bit troublesome in overall, since we really wouldn't like to garbage the devel trunk with vivid commits10:10
sil2100Since then there would be one big inconsistency if you want to get back to releasing for wily from trunk10:10
pstolowskisil2100, hmm. would bumping to 0.3 be an option?10:11
sil2100No no, this would be just dodging the check, but the trunk would still be inconsistent10:12
sil2100I would recommend to do something like this:10:12
sil2100Branch off current trunk to some 15.04 branch, change (by a direct push to the 15.04 trunk) the top most debian/changelog entry to include 15.04 in its version number instead of 15.10 and use that branch instead10:13
sil2100Once dual landings are back, you can simply drop using the 15.04 branch completely10:13
sil2100And do everything from trunk once again10:13
sil2100But at least this way trunk will be consistent and not go back in time with releases10:14
pstolowskisil2100, ah, i see, thanks for explaining. will try to do that10:15
pstolowskisil2100, also need to s/wily/vivid/ in that topmost changelog entry?10:17
sil2100pstolowski: yw! I know it's a bit of work, but we already have so much things that the train does wrong that I would at least like to keep all trunk branches 'sacred'10:17
sil2100pstolowski: you could do that, yes, not required but will add to the consistency10:17
pstolowskiheh, interesting view on consistency ;)10:18
pstolowskijamesh, ^ gyi10:20
pstolowskifyi even10:20
=== _salem is now known as salem_
=== alan_g is now known as alan_g|lunch
=== _morphis is now known as morphis
greyback_davmor2: hey, I suspect silo10 has slipped through the spreadsheet->bileto transition, ca you please add it to your trello board?12:44
davmor2sil2100: ^12:50
sil2100greyback_: let me take a look12:51
sil2100greyback_: ok, so it's there, but it's not set as 'Ready for QA'12:51
sil2100greyback_: once you're done with testing you need to mark that it's ready for QA sign-off12:51
sil2100greyback_: like in the spreadsheet, just the fields are called differently12:52
greyback_sil2100: davmor2 oh wow, sorry, I totally missed that13:01
greyback_I thought it said ready for QA13:01
davmor2greyback_: no worries13:02
=== jhodapp|sick is now known as jhodapp
=== alan_g|lunch is now known as alan_g
bfillerrvr: silo 4 has fix for gallery not starting up if you have time to test it13:17
rvrbfiller: Thanks! Busy with other things right now. If not me, someone else will take it for sure :)13:19
bfillerrvr: great, thanks13:19
pstolowskisil2100, heeeeeelp13:21
sil2100pstolowski: what's up?13:22
pstolowskisil2100, made a 'temporary' trunk, here is the MP https://code.launchpad.net/~stolowski/unity-scope-mediascanner/audio-card/+merge/26732513:22
pstolowskisil2100, the silo still fails https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/181/console13:22
sil2100hm, let me seee13:22
pstolowskisil2100, i have no idea where 0.5.4+15.10.20150707-0ubuntu1 comes from13:22
pstolowskisil2100, here is the changelog of the 15.04-trunk http://bazaar.launchpad.net/~unity-team/unity-scope-mediascanner/trunk-15.04/view/head:/debian/changelog where i changed 15.10 to 15.0413:23
sil2100Let me look deeper what's going on13:24
sil2100pstolowski: oh, but it's failing for unity-scopes-shell13:25
sil2100pstolowski: the branches you showed me are for unity-scope-mediascanner - you need to do the same for unity-scopes-shell ;)13:25
pstolowskisil2100, uh, oh, indeed, ovelooked it, sorry13:27
pstolowskisil2100, but that's weird, yesterday i succesfully built unity-scopes-shell in silo 27 without needing to do that13:28
pstolowskiand it was only vivid too13:28
sil2100btw. we need to reconf the silo to target the overlay13:30
sil2100Since now it's targeting the main vivid archive13:30
pstolowskisil2100, oh, which one, 27?13:30
sil2100pstolowski: 00513:30
sil2100I changed it, reconfiguring now13:30
pstolowskisil2100, hmm, and why not 27, it looks the same in bileto?13:31
sil2100I don't know, you showed me links for silo 00513:31
sil2100So I thought you're working on 005?13:31
pstolowskisil2100, yes, i'm working on 5 now, but as i said, yesterday i built unity-scopes-shell in silo 27 (which is supposed to target vivid-overlay)13:32
sil210015:22 < pstolowski> sil2100, the silo still fails https://ci-train.ubuntu.com/job/ubuntu-landing-005-1-build/181/console <- so I wanted to reconfigure this silo to target the overlay13:32
greyback_sil2100: can dual silos still land?13:32
sil2100I can reconf 27 too as well if it's not for overlay13:33
sil2100greyback_: if you're able to test your silo against wily then yes ;p ;p13:33
greyback_sil2100: right so ;)13:33
pstolowskisil2100, both 5 and 27 should target vivid-overlay, i was assuming that when 'vivid' is slected in bileto, it will actually be vivid-overlay?13:34
sil2100pstolowski: no13:34
sil2100pstolowski: since bileto still needs to enable people to land stuff as SRUs, right?13:34
pstolowskisil2100, hmm right13:34
pstolowskisil2100, then please reconfigure both 5 and 2713:35
sil2100pstolowski: so to get something landed to overlay, you select vivid and then 'Destination PPA' select the overlay (it should be available as a auto-complete option)13:35
sil2100On it :)13:35
* pstolowski is back to square one after 2 days of fight with silo 27 :(13:35
sil2100No rebuild required!13:36
sil2100At least not for the retargetting13:36
pstolowskisil2100, ah, cool13:36
pstolowskisil2100, changelog versions etc not affected?13:36
sil2100Should be good now13:36
sil2100pstolowski: right, we're using the same versioning for overlay and vivid for the train13:37
pstolowskisil2100, i haven't updated scopes-shell13:43
pstolowskion it13:43
sil2100Ah :)13:44
pstolowskisil2100, it's complaining about unity8 version now... that brings back the question why it worked in another silo yesterday where i built both unity-scopes-shell and unity813:52
sil2100pstolowski: are you sure it wasn't because it was a dualo silo then?13:53
sil2100Let me check the logs13:53
pstolowskisil2100, it was dual silo originally. then i change to vivid only and reconfigured13:53
sil2100pstolowski: probably the build happened when it was a dual silo still or something13:54
pstolowskisil2100, no, not possible, actually you changed the silo for me yesterday, the new one was vivid from the start13:55
sil2100Looking at the logs13:55
sil2100pstolowski: ah... yeah, it worked for silo 27 as you changed the upstream version to 0.5.513:57
sil2100pstolowski: which camouflaged the issue13:57
sil2100Damn, this would mean you'll release a 15.04 version to trunk with that merge... eh13:58
sil2100Well, I suppose we could live with that13:58
sil2100Don't want to force you rebuilding that silo, just remember it will introduce some uglyiness to your main trunk13:58
pstolowskisil2100, in that case i'd prefer to re-target to our temporary trunk13:59
sil2100I suppose no re-test would be needed as it's the same contents14:00
oSoMoNtrainguards: is it a known issue that autopkgtests for qtcreator-plugin-ubuntu are failing and blocking migration of a number of packages in wily?14:14
sil2100oSoMoN: yes14:15
sil2100oSoMoN: it's caused by seeds14:15
oSoMoNsil2100, is there anything we can do about it? This prevents building new silos for e.g. webbrowser-app, because the jenkins job complains that webbrowser-app 0.23+15.10.20150729-0ubuntu2~gcc5.1 is missing from the changelog14:15
sil2100oSoMoN: we need new seeds updated and uploaded14:15
sil2100oSoMoN: hm, I think it's a different case here14:16
sil2100oSoMoN: so unblocking webbrowser-app from -proposed won't help, as this upload was anyway a direct upload14:17
sil2100oSoMoN: what needs to be done is:14:17
sil2100oSoMoN: first, let's double check if 0.23+15.10.20150729-0ubuntu2~gcc5.1 was a no-change rebuild for gcc14:17
sil2100oSoMoN: if that's the case and we're not missing any real changes, two things can be done:14:18
sil2100oSoMoN: first, the clean but longer method would be to take the missing changelog entries, adding them to the webbrowser-app trunk (by a direct bzr push to trunk) and then rebuilding the webbrowser-app silos14:19
sil2100oSoMoN: second, faster but less cleaner, is simply using the FORCE_REBUILD flag while building, but that will simply override and ignore this changelog entry missing14:19
sil2100Which is not super nice, but since it's a no-change rebuild, no one will cry for not having it in the changelog14:19
oSoMoNsil2100, ok, I’ll take the first option and add the missing changelog entry to trunk14:20
oSoMoNsil2100, thanks for the help!14:20
sil2100oSoMoN: no problem! Any of the two is fine, but yeah ;)14:20
dobeysigh, so many test regressions in proposed14:43
dobeyhmm, i wonder why so many of these packages didn't get picked up and rebuilt in the gcc5 silo ppa14:58
pmcgowanjhodapp, how's your silo 21 coming along?15:10
jhodapppmcgowan, actually silo 38 now :)15:10
jhodapppmcgowan, it's building everything now and if it succeeds, I'll do a quick local sanity check again...if I'm happy it'll be ready for QA15:10
pmcgowangreat davmor2 alecu ^^15:11
alecupmcgowan: thanks15:12
jhodappdavmor2, alecu: so to test this, you'll just go through the listed test plan, which is for media-hub. We want to make sure that no existing use cases are broken.15:13
davmor2jhodapp: I'm going to disappear in a minute but reappear later15:14
jhodappdavmor2, no worries, it's not ready to test yet anyway15:14
davmor2so more likely monday morning then15:14
jhodappthat's perfect...I'll send you an email confirming that it's ready for you on Monday morning15:15
sil2100cihelp: hey! Could we get qtcreator-plugin-ubuntu autopkgtests re-run?15:22
sil2100cihelp: who should I poke regarding those? We landed a seed change that should help15:22
sil2100http://autopkgtest.ubuntu.com/packages/q/qtcreator-plugin-ubuntu/wily/amd64/ (and i386)15:23
fginthersil2100, I have no idea how to rerun those. Is pitti or jibel available? ^15:24
sil2100jibel is off on holidays, might look for pitti in this case15:24
sil2100fginther: thanks!15:24
fginthersil2100, or maybe infinity? ^15:24
alecupstolowski: jhodapp gave a status of the silo we depend on, a few lines above ^^^15:29
pstolowskialecu, great, thanks15:32
pstolowskialecu, we have no clarity what to do with unity8 atm (in terms of branching), i discussed this with tsdgeos but we will wait for monday when other unity8 guys are back15:35
sil2100Mirv: do you have the power to re-run autopkgtests still?15:39
jhodapptsdgeos, also, give silo 38 a try with your music-scope changes15:39
tsdgeosjhodapp: pstolowski was giving it a go i think15:40
jhodapptsdgeos, ok great15:40
jhodappI'm also testing it right now15:40
tsdgeosi'm trying to fix/debug a crash in unity8 startup15:40
jhodappnot the scope stuff, but silo 3815:40
pstolowskijhodapp, we planned to, but i got stuck with the build issues (may need to have separate trunks for all projects involved)15:40
jhodapppstolowski, build issue for the music-scope silo?15:42
pstolowskijhodapp, yes (silo 5)15:43
abeatotrainguards, I am getting a signature error that I do not understand: https://ci-train.ubuntu.com/job/ubuntu-landing-057-1-build/2/console15:45
sil2100abeato: hey! The problem is different15:46
sil21002015-08-07 15:39:54,683 ERROR dch: fatal error at line 1141:15:46
sil2100New version specified (0.108+15.04.20150807-0ubuntu1) is less than15:46
sil2100the current version number (0.108+15.10.20150807-0ubuntu1)!  Use -b to force.15:46
sil2100You need to branch trunk for an older ubuntu series, or do a sync silo from a newer release to an older release.15:46
abeatosil2100, hmm, ok... when I select vivid in the citrain, that's vivid-overlay?15:47
sil2100abeato: no, you need to also add info about the overlay in the 'Destination PPA', it should be in the autocomplete there15:47
sil2100But reconfiguring it doesn't require a rebuild15:48
sil2100Just change it and reconfigure your silo15:48
abeatook, thanks15:48
abeatosil2100, so I select the overlay ppa and keep the target series to "vivid"?15:50
abeatosil2100, I also want to sync a package from https://launchpad.net/~canonical-arm-dev/+archive/ubuntu/ppa/+packages15:51
abeatoI have used ppa:~canonical-arm-dev/ubuntu/ppa,vivid as sync source15:51
abeatois that right?15:51
abeatosil2100, also I am nit sure about what how to reconfigure: does editing the entry+saving does it?15:55
sil2100abeato: after you edit the entry and click save, simply click the 'Assign' button once again (as if reassigning) and proceed15:55
* sil2100 looks if the docs are updated for that15:55
abeatosil2100, ok, got it15:56
sil2100abeato: just in case it's needed: https://wiki.ubuntu.com/citrain/LandingProcess#Modifying_your_existing_landing15:58
abeatosil2100, great, I'll take a look16:00
abeatosil2100, what about the sync I want to do? should it work or I need somebody else to copy the package around (pulseaudio)?16:01
sil2100abeato: pulseaudio hmm... you'd have to ask a trainguard or a core-dev to help with the sync16:01
sil2100Since it's a non-train package16:01
sil2100ogra_: ugh, forgot to kick a new rc-proposed build16:11
sil2100Kicking now16:11
ogra_kick it then :)16:11
ogra_like beckham ;)16:11
jhodappdavmor2, vivid doesn't boot after installing the silo...figuring that out now16:15
=== chihchun_afk is now known as chihchun
boikorobru: hi, you can go ahead and free silo 29, alreadu assigned silo 58 using the requests page16:48
pmcgowandavmor2, what was fixed in the new device tarballs?16:53
davmor2pmcgowan: user wipe mode changes mostly but I think it still needs the the one silo to land too but I'll hit that after, for now it just didn't break anything.17:05
pmcgowandavmor2, thanks17:06
robruboiko: thanks!17:10
dobeyso it's just autopilot-gtk, and kde, blocking the gcc5 transition now, it seems17:36
bregmadi dual landings build separately for each target (eg. wily and overlay), or is it a binary copy?17:38
davmor2robru: silo 48 is mark for qa but it is a wily only build so can I throw it back to you please17:45
robrudavmor2: lemme see17:46
robrudavmor2: alright then17:46
davmor2robru: ta17:47
robruMirv: morphis what's going on in silo 48? why was a wily silo marked as needing QA?17:47
dobeybregma: seems it is not exactly a copy, as each gets different version numbers generated17:49
dobeybregma: so different source packages, but only one ends up getting committed to the vcs upon landing17:50
jhodapprobru, can you please dput qtmultimedia from ppa:jhodapp/ubuntu/ppa to silo 3817:50
dobeymeh, right; devel-proposed doesn't include wily-proposed17:52
robrujhodapp: sure, one sec17:54
robrujhodapp: uh, "a different source with the same version is published in the destination archive"17:55
jhodapprobru, do I have to bump the pkg version each time?17:56
robrujhodapp: yeah 1ubuntu4 is already in there, you'll need to upload a new 1ubuntu5 then17:56
jhodappok great, one min17:56
robrujhodapp: yes! you can't go around having multiple different source packages with the same version number, silly. that defeats the point of having version numbers.17:56
jhodappwell sure, but I never released the last one so thought it may not matter17:56
robrujhodapp: PPAs are basically the same thing as the ubuntu archive. for all intents and purposes putting it in the PPA is "releasing" it, it's just not in the blessed archive that users download from.17:58
jhodapprobru, ack17:58
jhodapprobru, ok try again18:00
robrujhodapp: alright it's in there, you can do a WATCH_ONLY now18:02
jhodappawesome thanks!18:02
=== jhodapp is now known as jhodapp|errand
dobeyhmm, requests seems out of sync with my silo18:19
robrudobey: uh, I just hit publish, I hope you don't mean there's something missing from the PPA18:20
robrudobey: what's out of sync? same MPs are listed18:20
dobeyrobru: no. the ppa is built and all18:20
dobeyrobru: it says "Building" but the packages have been built for hours18:21
dobeyrobru: and when i just set it to "publish without qa" i noticed that someone had apparently set it to "dual" and "qa required" (which were both incorrect)18:21
robrudobey: dashboard should be considered authoritative there. sometimes network issues make the status update in bileto fail.18:21
dobeywell now it's correct for the publishing state at least18:22
robrudobey: as for the other thing, I guess it's possible somebody else was editing your row. not sure who though18:23
dobeyyeah. would be nice to have visible history there18:25
robrudobey: that would have to wait for v2 I'm afraid ;-)18:27
=== jhodapp|errand is now known as jhodapp
=== cwayne is now known as cwayne-afk
dobeyhmm, i guess sil didn't get anywhere with asking for the qtcreator-plugin-ubuntu autopkgtests rebuilds18:54
robrumichi: you forgot to check ONLY_FREE_SILO19:02
robrumichi: I'm also freeing silo 41 since the MP in there was released in your other silo that published.19:18
jhodapprobru, alright, got another qtmultimedia change to dput from ppa:jhodapp/ubuntu/ppa to silo 38 please (hopefully this should be the last one)20:01
jhodapprobru, actually hold off on that for now20:02
jhodapprobru, ok yes, please dput that20:07
robrujhodapp: alright, copied20:24
jhodapprobru, thanks20:44
robrujhodapp: you're welcome20:45
michirobru: thanks. I abandoned some silos, but didn’t know that this isn’t sufficient21:41
robrumichi: no worries. the 'Abandon' link in requests.c.u.c is mostly for if you don't have a silo assigned already, like if you created two requests by mistake.21:47
michiAh, I see.21:47
michiSo, what should I do when I abandon a silo after it’s allocated?21:48
michiBuild again with ONLY_FREE_SILO?21:48
robrumichi: https://ci-train.ubuntu.com/job/ubuntu-landing-032-3-merge-clean/6/console you just about had it here, but you need to check ONLY_FREE_SILO21:48
michirobru: I look at the landing process page and could find anything.21:48
michiMight be good to add a sentence or two. My expectation was that abandon would do all that.21:49
robrumichi: sorry, I'll update that (it's a bit out of date still)21:49
michiSure, no problem. Just mentioning it :)21:49
robrumichi: https://wiki.ubuntu.com/citrain/LandingProcess#Abandon_a_landing ok ;-)21:56
michirobru: Wow, most excellent, thank you! :)21:57
robrumichi: you're welcome!21:57
=== salem_ is now known as _salem

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