[00:55] <bluesabre> knome: are we attached to the way the headers are  currently on the release notes, or can I fix the sections?
[00:55] <knome> feel free to fix anything that isn't right
[00:55] <bluesabre> cool
[00:55] <bluesabre> I'm sure somebody will come in behind me and do the same :D
[00:55] <knome> especially now that we aren't doing includes from the main release notes, whatever works for us is goof
[00:56] <knome> err
[00:56] <knome> good
[00:56] <bluesabre> goof
[00:56] <bluesabre> I like it
[00:56] <knome> :)
[00:56] <knome> maybe that too
[00:57] <bluesabre> Changes made, http://wiki.xubuntu.org/releases/17.04/release-notes
[00:58] <bluesabre> probably going to tidy up the issues list as well
[01:00] <knome> mhm
[01:00] <knome> i'll look at the release announcement for the website tomorrow
[02:02] <bluesabre> Alrighty, done messing with the release notes http://wiki.xubuntu.org/releases/17.04/release-notes
[02:02] <bluesabre> flocculant: allllllll yours :)
[06:27] <flocculant> bluesabre: thanks re release note :)
[06:28] <flocculant> but on the other thing do you mean some xfce package would stop getting updated in the archive? cos that doesn't make sense to me?
[10:00] <bluesabre> flocculant: I mean that we'd stop updating the package for that and any other non-EOL releases
[10:20] <ochosi> hey bluesabre
[10:20] <bluesabre> hey ochosi
[10:20] <ochosi> if you wanna update your quick and dirty packaging with the updated patch, i can get more testing for it
[10:21] <ochosi> as i said, functionally it was already working fine. it was just the primary entry that was added to the menu twice (silly me)
[10:24] <bluesabre> ochosi: fails to build
[10:24] <bluesabre> xfce4-panel/xfce4-panel/panel/panel-preferences-dialog.c:501: undefined reference to `panel_str_is_empty'
[10:24] <bluesabre> bbabl
[10:33] <ochosi> woot? crap. built for me. never check in stuff after midnight :(
[10:33] <ochosi> i'll check again tonight
[11:08] <flocculant> bluesabre: mmk - seems a bit meh but ok :) I might have ubuntu supported for 5 years and really prefer parole to the gnome thing :)
[11:08] <flocculant> just wanted it right in my head - someone was trying to get help in #x yesterday
[13:00] <stevehope> question on the release notes, For new installs a swap file will be used instead of a swap partition. < does this apply to upgrades?
[13:04] <encomjones> why a swap file instead of a swap partition
[13:18] <knome> stevehope, no, existing partitioning will always be kept, including swap
[13:19] <knome> encomjones, i don't remember where, but there's an explanation on the rationale behind that in some developers blog somewhere
[13:19] <knome> eg. this isn't an active decision by the xubuntu team, but we are (at least) good enough with the change that we won't strive to differ from the ubuntu desktop here
[13:21] <encomjones> okely dokely
[13:26] <stevehope> knome, thanks, didn't recall a change in swap during testing, maybe clarification?
[13:31] <stevehope> Existing linux swap partitions retained...
[13:35] <stevehope> So in the event of an upgrade user doesn't remove legacy swap, thinking its now a file, breaking new and old installs
[13:36] <stevehope> *post install
[13:41] <stevehope> the reasoning may be too conveluted, lol it's how I think :P
[13:44] <stevehope> or you could replace the word "new" with the correct term for what you intend 'clean' ;)
[13:46] <knome> yes, that might do it...
[13:47] <knome> though "clean" is a correct term too :P
[13:47] <knome> but maybe it wouldn't hurt to mention that "Upgrades aren't affected by this."
[13:48] <knome> though then i'm not sure how many people who upgrade read the release announement/notes
[13:48] <knome> or for that matter, how many people in general read them :P
[13:53] <stevehope> I'm quite new here, still getting a feel for expectations of edit / not significant enough to warrant change here
[13:55] <stevehope> i used to work in q&a
[13:57] <stevehope> * despite the fact that I have the spelling of an eight year old =]
[14:06] <knome> no worries :)
[14:06] <knome> it's always good to have more people looking at things
[14:06] <knome> history has proven us that not enough people read the release notes or even the announcement...
[14:15] <stevehope> i'ld prefer to try to just give my suggestion instead of trying to be verbose... ie new = [clean, upgrade]; clean != new if thats ok?
[14:56] <knome> pleia2, ochosi: i'm going to pick up a delivery from the netherlands in a bit...
[14:56] <knome> ->
[16:09] <flocculant> knome: flying?
[16:34] <ochosi> knome: oookay? i thought we were expecting something from .hu..?
[16:57] <stevehope> @knome "history has proven us that not enough people read the release notes or even the announcement..." because more often than not, the contents isn't current or correct, self fulfilling prophecy
[16:57] <meetingology> stevehope: Error: "knome" is not a valid command.
[16:58] <stevehope> knome "history has proven us that not enough people read the release notes or even the announcement..." because more often than not, the contents isn't current or correct, self fulfilling prophecy
[17:12] <flocculant> bluesabre: changed the changelog bit - a lot
[17:12] <flocculant> stevehope: added re swap file and upgrade
[17:14] <ochosi> crap, just fixed another small issue in greybird :/
[17:14] <stevehope> :)
[17:14] <flocculant> hi ochosi :)
[17:17] <ochosi> how're things flocculant?
[17:17] <flocculant> I'll be glad when it's Friday ;)
[17:17] <flocculant> other than that - everything is tickety boo :D
[17:17] <stevehope> if friday gold day?
[17:17] <stevehope> is
[17:18] <flocculant> friday is long weekend ;) and also release+1 day ...
[17:19] <stevehope> ah, I'm retired i'm still on my last long weekend
[17:20] <flocculant> bluesabre - couple more smoke tests for the tracker and assuming no respins overnight I'll mark the release in the morning
[17:20] <flocculant> and anyone else wondering :(
[17:20] <flocculant> ugh
[17:20] <flocculant> :)
[17:26] <stevehope> ill get the incomplete 386 desktops ISOs, so they have a result
[17:26] <flocculant> stevehope: doing those here too :)
[17:27] <stevehope> well two tests are better than one and I'm already zsync'ing si might as well keep going
[17:28] <flocculant> stevehope: I hope you hang around during the next cycle - we can find you things to do - we need to test testcases against new early in the cycle - getting closer to LTS cycle so we'll be thinking about package testing again
[17:28] <flocculant> and yea - as many results as possible is good :D
[17:31] <flocculant> stevehope: do you use hardware or vm's?
[17:33] <stevehope> Both, I use one or the other, depends on the specific test
[17:35] <flocculant> k - useful to know :)
[17:35] <stevehope> as i have a limited selection of hardware to test with, if Im emulating I use virtualbox
[17:36] <flocculant> righ
[17:36] <flocculant> t
[17:37] <flocculant> I have a very limited selection of hardware - so mostly hardware test only at milestones - though I will be using the 'next' version as soon as the toolchain is open and we actually have 17.10 available
[17:38] <flocculant> then I kill it with the help of ochosi bluesabre and Unit193's ppa's and things during the cycle :p
[17:38] <stevehope> * I run virutalbox in the default setting for a Ubuntu 64 system, with ISO in cd, with the exception i give the virtualbox 4gb ram for performance
[17:38] <flocculant> I think slickymaster / slickymasterWork uses vbox, me and akxwi-dave (afaik) both use kvm now
[17:39] <flocculant> I do for sure :)
[17:40] <slickymasterWork> nopes flocculant
[17:40] <stevehope> I intend to learn kvm, have in installed, exploring docker-machine to manage vm's kvm next
[17:40] <slickymasterWork> for a while now I've only been using VMware
[17:43] <stevehope> would you recommend VMware over kvm in general?
[17:44] <flocculant> slickymasterWork: oh right - some thing other than kvm still though
[17:44] <slickymasterWork> I'm using it on windows hosts stevehope, not on linux hosts
[17:44] <slickymasterWork> yes, flocculant
[17:45] <flocculant> stevehope: I find kvm/qemu to be a lot quicker - though could obviously not be the case in reality
[17:45] <stevehope> ah, i guess you're up to speed on bash on ubuntu on windows and the other parts of the win linux subsystem
[17:47] <stevehope> i was playing around with it before i swtiched to xubuntu for all my computers https://msdn.microsoft.com/en-us/commandline/wsl/about
[17:49] <flocculant> stevehope: can you go to http://wiki.xubuntu.org/releases/17.04/release-notes - I added workround to the system encryption locale issue - does it make sense to you?
[17:49] <flocculant> or indeed anyone else who happens to be idling the day away reading in here :)
[17:50] <flocculant> having checked it out - I can at least confirm the bug and workround :D
[17:51] <slickymasterWork> I would put some sort of separation between the bug description and the start of the workaround explanation, flocculant
[17:52] <flocculant> what like a space?
[17:52] <slickymasterWork> I dunno
[17:52] <slickymasterWork> you already have a space
[17:52] <flocculant> cos there is one of those :D
[17:52] <slickymasterWork> maybe the word workaround in bold
[17:52] <flocculant> hang on
[17:52] <slickymasterWork> ou underlined
[17:54] <flocculant> check now
[17:54] <slickymasterWork> excellent
[17:54] <flocculant> :)
[17:55] <slickymasterWork> just one last thing flocculant, there's an extra space between ( and Use, in ( Use F3)
[17:56] <knome> flocculant hasn't learned the importance of whitespace (or lack of it) yet apparently :P
[17:56] <stevehope> Yes, other suggestion though *ducks* "System encryption password set before setting keyboard locale (1047384) Workround: Start the installation with the correct keymap. ( Use F3) to set your keymap before booting either installation option" not correct, the crypt password was moved from some acsii display, grub? to the slides, in one of the recent respins, current workaround, goto next slide to set keyboard, back up one slide.
[17:56] <flocculant> lol
[17:56] <slickymasterWork> hey knome
[17:56] <flocculant> slickymasterWork: > http://wiki.xubuntu.org/releases/17.04/release-notes?do=revisions
[17:56] <knome> good evening
[17:56] <slickymasterWork> i saw it flocculant
[17:56] <knome> i anvil it
[17:56] <knome> :Ð
[17:57] <slickymasterWork> lol
[17:57] <flocculant> slickymasterWork: did you see the revison reason :D
[17:57] <flocculant> stevehope: don't understand what you're saying there
[17:57] <slickymasterWork> nopes flocculant, just saw the revision made
[17:57] <slickymasterWork> will see it now
[17:57] <flocculant> and good evening knome :)
[17:57] <flocculant> slickymasterWork: :p
[17:58] <slickymasterWork> hahahah flocculant
[17:58] <stevehope> if you step through the instalation slides you'll get it
[17:58] <knome> i'll move stuff to the announcement on the website soon unless you are planning huge changes :P
[17:58]  * slickymasterWork not trying to steal the nitpicking position in the team which is already taken
[17:58] <flocculant> stevehope: I'm not talking about slides - and our slides don't mention that afaik - I'm referring to a bug
[17:59] <flocculant> slickymasterWork: you and kryten share that crown - always too late with the comments though normally :D
[17:59] <slickymasterWork> that's true
[17:59] <flocculant> :)
[18:02] <stevehope> I know the bug you are reffering to, i was present in a zesty final ISO, then a respin created a new slide to enter the password in the slide interface, instead of dropping to ascii, and having to enter it there, the only issue now is moving the keyboard select back 1 slide, and the bug is totally gone
[18:02] <stevehope> *it was present
[18:03] <flocculant> not sure then - not something I saw
[18:05] <flocculant> knome: 9 attempts to login to x.org :(
[18:06] <flocculant> would have been so much quicker just to ask you if you started the announcement post yet :D
[18:07] <stevehope> I don't want to be perceived as new most irritating nittpicker, I can understand if you think it's a nit not worth picking, if you simply don't believe me enter the information manually on an encrypted install yourself
[18:08] <flocculant> stevehope: not at all - I really don't get what you mean here - can you screenshot it?
[18:08] <stevehope> yes
[18:08] <flocculant> cool
[18:09] <flocculant> cos nit-picking is what qa should do anyway - as long as it's not about circles or ellipses :p
[18:09] <knome> flocculant, not yet
[18:10] <knome> but i'm digging into it literally now
[18:13] <stevehope> I would have to find one of the previous spins in final, for the previous display, which I consider a complete waste of time, I will prepare install screenshots of current behaviour to save you actually reading the order of the slide's, I don't consider this a constructive exercise though
[18:14] <flocculant> stevehope: oh
[18:14] <flocculant> if it happened - but doesn't now I'd not worry too much
[18:19] <akxwi-dave> flocculant: I use KVm on main machine, virtualbox on laptop and another PC, along with bare meta
[18:24] <knome> ok, draft at https://xubuntu.org/?p=4295&preview=true
[18:25] <knome> do we want to list all of the notable issues on the announcement? i was thinking we might condense the parole bugs to one line about parole having issues...
[18:25] <knome> also not sure if sgt-puzzles and indicator plugin are worthy enough
[18:26] <knome> the bugs, that is
[18:26] <knome> also created https://xubuntu.org/release/17-04/ if somebody wants to get poetic
[18:27] <knome> i also notice that we create links with non-existent links... they just point to the page itself so it's *just fine* to have that for a day (though i'll fix that later)
[18:28] <knome> we also seem to be linking to direct download locations
[18:28] <knome> which is a bit meh
[18:28] <knome> so meh
[18:28] <knome> i'll remove the "release"
[18:28] <knome> need to fix THAT
[18:28] <flocculant> knome: re parole - I'd have them on one line - detail is elsewhere
[18:28] <knome> yep
[18:28] <knome> let me work that out
[18:29] <flocculant> we recommend you to use > we recommend that you use
[18:29] <knome> maybe mention thunar's issues first?
[18:29] <flocculant> yea
[18:29] <flocculant> I'd not get too specific on any tbh - specifics are on release note
[18:30] <flocculant> list of new package versions (since 14.04 LTS), < remove the (14.04) bit
[18:31] <knome> draft updated
[18:31] <knome> oh right, yes
[18:31] <knome> see, i'm copy-pasting from the 16.04 announcement :P
[18:32] <flocculant> :)
[18:32] <knome> and new update
[18:32] <knome> bbiab
[18:33] <flocculant> you really should release lock :p
[18:33] <flocculant> available as Torrents > torrents and later too
[18:38] <knome> ugh
[18:38] <knome> saved and released
[18:38] <knome> not the article, the lock...
[18:41] <flocculant> knome: looks ok - ty
[18:41] <flocculant> in other news ... is Show all mirrors with full information supposed to do more than it actually does?
[18:41] <knome> what does it do?
[18:42] <flocculant> just shows what you are already looking at :)
[18:42] <knome> have you got JS enabled?
[18:42] <flocculant> *shrug*
[18:42] <knome> well it's supposed to expand the list
[18:42] <knome> and, yeah..
[18:42] <knome> urgh
[18:43] <knome> need to fix that too for non-js-enabled
[18:45] <flocculant> no java installed here seems
[18:45] <flocculant> guess I had no reason up to now
[18:46] <knome> java != javascript
[18:46] <flocculant> knome: you want me to bug report that? so it's not forgotten?
[18:46] <knome> that would be nice, thanks
[18:46] <knome> guess i'll report the release bug myself
[18:47] <stevehope> re encryption entry in encrypted install, is now the 3rd interactive slide, this was done to address the old method of entering password in a low res acsii type interface, slide 3 was added, however it was inserted before current slide 4 where the keyboard localization is set, the bug is almost fully addressed, the keyboard localiztion simplely need to be set as slide 3. not it's current order: 1, 2, drive password, keyboard should be 1, 2, keyboa
[18:50] <flocculant> knome: about:config tells me javascript is true
[18:50] <knome> weird then
[18:50] <stevehope> is there still a need for me to screenshot the slides individally?
[18:50] <knome> flocculant, how many links do you see before the "all mirrors" link?
[18:51] <flocculant> knome: if you mean countries - 13
[18:52] <knome> ok,
[18:52] <knome> and when you click the link do you still only see 13?
[18:52] <flocculant> yea
[18:52] <knome> yeah, it should show more, and an "info" link for each
[18:52] <flocculant> though url is now http://xubuntu.org/getxubuntu/#show-all
[18:53] <knome> that's expected
[18:53] <knome> which browser?
[18:53] <flocculant> ff 52
[18:53] <knome> me too...
[18:53] <knome> https://temp.knome.fi/xubuntu/temp/mirror-links.png
[18:53] <knome> this is what you should get after clicking
[18:54] <flocculant> knome: ack - not sure I have 'ever' seen that
[18:56] <flocculant> stevehope: ohhh ... when you're talking about slides you're talking about the installation stages - yea that's right, I see what you're saying now :)
[18:56] <flocculant> hence the workround
[18:57] <flocculant> set keymap before installation gets that far
[18:58] <knome> flocculant, since your bug is so random, so is debug... what do you see when you go to view-source:http://xubuntu.org/wp-content/themes/xubuntu-theme/xubuntu-fifteen/script-releases.js?ver=2
[18:58] <flocculant> knome: might be my 'kicking around forever and a day' ff profile - works on a default iso boot
[18:58] <knome> or in other words, do you see some codE?
[18:58] <knome> some caching might be related too
[18:58] <knome> and once you load that page....
[18:58] <flocculant> http://paste.ubuntu.com/24369199/
[18:58] <knome> press F5 and see if it updates
[18:59] <knome> that looks as it should though
[19:00] <flocculant> knome: seeing info now
[19:00] <knome> so apparently cache
[19:00] <flocculant> and more links
[19:02] <flocculant> really should remember to f5 before I say anything lol
[19:03] <knome> commented on the bug - leaving open as i'll do $something for it anyway
[19:03] <knome> that *should* fix the cache issue for people
[19:04] <flocculant> ok
[19:04] <flocculant> ty :)
[19:04] <knome> yw
[19:04] <knome> happy to help, especially as this let me discover that other, more critical bug :P
[19:05] <flocculant> :)
[19:05] <knome> too bad i have to fix it now...
[19:05] <flocculant> ha ha ha
[19:06] <knome> but there's two sides to that too.. fortunately it's an easy fix but otoh, is hould have noticed this before...
[19:09] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [greybird] r505 Revert workaround for broken border in progressbar (#153)... (by Simon Steinbeiß)
[22:15] <bluesabre> flocculant: thanks, release notes are looking pretty darn good now
[22:16] <bluesabre> next release, the changelogs will just need to be s/zesty/acrobatic/ and that will be done for the cycle
[22:38] <krytarik> flocculant: Indeed found something to nitpick on in the release notes: "Workround:" :D


[02:40] <niemeyer> Night all
[11:53] <_mup_> txzookeeper/session-event-handling r40 committed by<EMAIL_ADDRESS>[11:53] <_mup_> allow connection using existing session, test session expiration, additional symbol name translation for exceptions.
[13:06] <_mup_> txzookeeper/session-event-handling r41 committed by<EMAIL_ADDRESS>[13:06] <_mup_> pep8isms
[13:17] <kim0> do I really need to type "yes" to the ssh authenticity question
[13:21] <niemeyer> kim0: How do you mean?
[13:22] <kim0> ensemble status
[13:22] <kim0> I get the ssh yes/no prompt
[13:22] <kim0> same for debug-hooks
[13:23] <kim0> niemeyer: that is normal right ?
[13:24] <niemeyer> kim0: You mean the prompt asking you if the fingerprint for the server is valid?
[13:24] <kim0> yes
[13:24] <niemeyer> kim0: Yeah, that's usual when connecting to a new server
[13:24] <kim0> Would be great if Ensemble would get the machine log .. and verify it for me
[13:24]  * kim0 grabs his wish list bag
[13:25] <kim0> Also if ensemble had a presistent connection to bootstrap node :) and perhaps run locally under a screen session with "watch status" and debug-log ..etc all running
[13:27] <kim0> niemeyer: I think I am see'ing strange behaviour which I hope someoen can help me with since I really want to write this "write a formula doc". I just launched a mysql SU, and a drupal SU (based on an almost empty new formula)
[13:28] <kim0> fired debug-hooks drupal/0 .. works
[13:28] <kim0> add-relation drupal mysql
[13:28] <kim0> I am not getting any new windows in the debug-hooks screen
[13:29] <niemeyer> Hmm
[13:30] <niemeyer> kim0: Thinking
[13:30] <kim0> sure
[13:30] <kim0> I think I saw this yesterday
[13:30] <kim0> when I closed the debug-hooks screen ..
[13:30] <kim0> hooks suddenly started firing
[13:30] <kim0> it's like it was stuck
[13:30] <niemeyer> kim0: That's normal
[13:30] <kim0> but I always blame myself :)
[13:30] <niemeyer> kim0: Hooks are serially executed
[13:31] <kim0> well there were not opening new windows in screen session
[13:31] <kim0> they should right ?
[13:31] <niemeyer> kim0: You won't get another hook window until you stop the existing one
[13:31] <kim0> there was no existing one .. I was waiting for it
[13:31] <kim0> just like now .. there's only window 0 in screen
[13:32] <niemeyer> kim0: and what's 0?
[13:32] <hazmat> kim0, it was disabled (the ssh fingerprint confirm prompt)
[13:32] <kim0> niemeyer: just a shell
[13:32] <hazmat> but it leaves things open to man in the middle
[13:32] <hazmat> we should pull it down though automatically
[13:32] <niemeyer> hazmat: Do you have any ideas of what might be going on for kim0?
[13:32] <kim0> hazmat: yeah .. check my wish list :) we could ec2-get-console-output and verify it :)
[13:33] <niemeyer> kim0: WE can do better than that
[13:33] <niemeyer> kim0: We should inject the host key
[13:33] <niemeyer> kim0: That's in our wishlist already :)
[13:33] <hazmat> niemeyer, man in the middle was the primary reason fingerprint checking was renabled yes?
[13:33]  * hazmat reads through log
[13:33] <niemeyer> hazmat: That's right
[13:33] <kim0> niemeyer: cool !
[13:34] <kim0> niemeyer: cloud-init can inject host key already indeed .. that's even better
[13:34] <hazmat> indeed, we should probably make use of that, but we need to store in zk for multi-client access
[13:35] <hazmat> kim0, okay.. so you've got a debug hook session on drupal or mysql?
[13:35] <hazmat> when doing the add relation
[13:35] <kim0> drupal
[13:35] <kim0> hazmat: debug-hooks drupal/0
[13:35] <kim0> hazmat: add-relation drupal mysql
[13:35] <kim0> that's it .. no new window in screen
[13:35] <hazmat> kim0, okay.. so you do debugs for  install & start?
[13:36] <hazmat> or are you debugging after start?
[13:36] <kim0> the sequence was
[13:36] <kim0> deploy mysql
[13:36] <kim0> deploy drupal
[13:36] <kim0> debug-hooks drupal/0
[13:36] <kim0> debug-log
[13:36] <kim0> add-relation mysql drupal
[13:36] <hazmat> kim0, could you paste your debug-log
[13:36] <kim0> I got a "install" or "start" hook here can't remember .. which I closed
[13:37] <kim0> I expected to get the db-relation-changed one after it .. but didn't
[13:37] <kim0> sure
[13:37] <hazmat> kim0, by closing are you exiting the shell or just closing the window?
[13:37] <hazmat> hmm
[13:37] <hazmat> i don't think i've tested closing the window instead of exiting the shell
[13:37] <kim0> hazmat: ctrl + d
[13:37] <kim0> exit shell
[13:37] <kim0> hazmat: log http://paste.ubuntu.com/616692/
[13:37] <hazmat> hmm that should be fine
[13:38] <niemeyer> hazmat: Should be equivalent
[13:38] <kim0> hazmat: status → http://paste.ubuntu.com/616694/
[13:38] <hazmat> niemeyer, yeah.. but on the close window case, there is still a callback to screen to close the window after the process exit
[13:38] <hazmat> but ctrl +d vs. exit is equiv
[13:39] <niemeyer> hazmat: I don't understand that distinction
[13:39] <hazmat> kim0, odd it seems like the unit hasn't picked up the relation
[13:39] <kim0> :s
[13:39] <kim0> can u connect to the env ?
[13:39] <niemeyer> hazmat: The callback will execute after the shell process exits, right?  Either option would kill it
[13:40] <niemeyer> hazmat: IOW, closing the window also terminates the shell
[13:40] <niemeyer> hazmat: This would happen if the hook wasn't executed
[13:40] <hazmat> niemeyer, right, but we have  another process checking on the shell and then instructing screen to kill the window, which is probably just a noop at that point
[13:40] <hazmat> niemeyer, its unrelated to what kim0 is seeing
[13:41] <niemeyer> hazmat: I mean, the relation not showing up
[13:41] <niemeyer> kim0: Can you please paste ps auxw for that machine?
[13:41] <niemeyer> kim0: The drupal one
[13:41] <kim0> niemeyer: from the debug-hooks screen is ok right ?
[13:41] <niemeyer> hazmat: Hmm.. unless we're running the shell script with -e, and screen exits with 1 because the window wasn't there?
[13:42]  * niemeyer doing guess work
[13:42] <niemeyer> kim0: Yeah
[13:42] <kim0> http://paste.ubuntu.com/616696/
[13:43] <niemeyer> hazmat: "install".. there's an old hook running still
[13:44] <kim0> I hope I didn't do something stupid at the end :)
[13:44] <niemeyer> kim0: I suspect your window 0 has the install hook running
[13:44] <niemeyer> kim0: Can you please paste "env" from that window
[13:45] <kim0> http://paste.ubuntu.com/616698/
[13:45] <hazmat> niemeyer, window 0 is never used for hooks its .. its always a shell
[13:45] <kim0> window 0 is always there
[13:45] <kim0> yeah
[13:45] <niemeyer> hazmat: It's trivial to shift windows around
[13:46] <hazmat> niemeyer, but the names are distinct on the windows
[13:46] <kim0> http://paste.ubuntu.com/616699/ is the install hook itself
[13:46] <niemeyer> Ok, but that's not the case either way
[13:46] <niemeyer> Still, we have a hook running
[13:46] <niemeyer> hazmat: Ok
[13:46] <hazmat> the debug stuff names the windows by hook , except window 0 which is named 'shell' afaicr
[13:47]  * kim0 nods
[13:47] <niemeyer> kim0: What's in /tmp/tmpLjxVDG-install
[13:47] <kim0> niemeyer: http://paste.ubuntu.com/616700/
[13:47] <kim0> scary script
[13:47] <hazmat> so it seems somehow the debug window was ended but the underlying debug process is still alive.
[13:48] <niemeyer> hazmat: Yeah, it's still in the sleep loop
[13:48] <niemeyer> hazmat: Which confirms your initial theory
[13:49] <kim0> I probably closed the window too fast, if you think it needs time to do anything
[13:49] <hazmat> it might be a different signal gets sent besides HUP that needs to be caught here
[13:49] <hazmat> kim0, it shouldn't matter
[13:50] <hazmat> we should never rely on user timing
[13:50] <kim0> yeah I know
[13:50] <niemeyer> hazmat: TERM, KILL
[13:51] <niemeyer> hazmat: Wait.. the HUP is catching the outside signal
[13:51] <niemeyer> hazmat: That's not the problem.. that script is still running
[13:51] <hazmat> yeah.. its not in the screen process
[13:52] <niemeyer> kim0: One more: /proc/1585/environ
[13:53] <kim0> http://paste.ubuntu.com/616708/
[13:53] <kim0> niemeyer: not sure why it has no newlines
[13:53] <kim0> doh
[13:53] <niemeyer> hazmat: We should monitor it from outside instead of expecting it to do stuff before it dies
[13:53] <kim0> sorry .. pastebinit error
[13:53] <niemeyer> kim0: That's the file format indeed
[13:54] <kim0> niemeyer: http://paste.ubuntu.com/616709/
[13:54] <kim0> this is complete
[13:54] <niemeyer> hazmat: e.g. writing to hook.pid when the process starts
[13:55]  * kim0 probably just uncovered a pastebinit bug
[13:55] <hazmat> niemeyer, yeah.. and then just doing something like kill -0 `cat hook.pid`  for the sleep condition
[13:55] <niemeyer> hazmat: RIght
[13:56]  * hazmat files a bug
[13:56] <niemeyer> hazmat: Another handy issue for a brain breaker.. will paste that conversation in a bug.
[13:56] <niemeyer> hazmat: Oh, ok :)
[13:56] <niemeyer> hazmat: Please paste the log for context
[13:56] <niemeyer> hazmat: Thanks
[13:56] <niemeyer> kim0: Alright.. we know what's wrong
[13:56] <kim0> great :)
[13:56] <niemeyer> kim0: For fixing your problem right now,
[13:57] <niemeyer> kim0: kill 1585
[13:57] <kim0> got it
[13:57] <kim0> thanks
[13:57] <niemeyer> kim0: np
[13:57] <kim0> wonder why no one else is hitting this
[13:57] <niemeyer> kim0: Thanks a lot for your help uncovering the bug
[13:57] <niemeyer> kim0: It's the way the debug-hook window was closed
[13:58] <kim0> ah so you close it clike ctrl-a c
[13:58] <kim0> ok
[13:58] <kim0> not c .. whatever closes windows :)
[14:00] <kim0> ew
[14:00] <kim0> ok probably hitting a new one
[14:01] <kim0> I killed the process .. got the window for db-relation-changed
[14:01] <kim0> relation-get inside it says →  No ENSEMBLE_AGENT_SOCKET/-s option found
[14:01] <kim0> env dump http://paste.ubuntu.com/616713/
[14:02] <kim0> hazmat: could you please as well
[14:03]  * hazmat looks
[14:03] <hazmat> kim0, that's the env from window 0 ?
[14:03] <hazmat> or the debug window?
[14:03] <kim0> hazmat: no win 1
[14:03] <kim0> the db-relation-changed window
[14:03] <kim0> db-relation-joined actually
[14:04] <hazmat> it doesn't look like it has the debug environment variables sourced
[14:04] <niemeyer> That's the shell isn't it?
[14:05] <niemeyer> SUDO_COMMAND=/usr/bin/byobu -xRS drupal-0-hook-debug -t shell
[14:06] <niemeyer> kim0: I think the paste is bogus
[14:07] <niemeyer> kim0: Or maybe I just misunderstand what the variables mean
[14:07] <kim0> I can repaste manually
[14:07] <kim0> anything to look for ?
[14:08] <niemeyer> kim0: Just thinking how to get the pid for the parent shell
[14:08] <kim0> ps -elf | grep $$ ?
[14:08] <kim0> it'd be listed in ppid field
[14:08] <niemeyer> kim0: echo $BASHPID
[14:09] <kim0> 9229
[14:09] <niemeyer> kim0: echo $PPID
[14:09] <kim0> 935
[14:09]  * kim0 feels like a shell
[14:09] <niemeyer> Ok, cool
[14:09] <niemeyer> kim0: Hehe :-)
[14:09] <kim0> :)
[14:10] <niemeyer> kim0: Yeah, looks like a failure in source it indeed
[14:10] <niemeyer> sourcing
[14:10] <kim0> we don't log those steps somewhere ?
[14:10] <niemeyer> Can't imagine how that could happen, though, even if we killed the process
[14:11] <niemeyer> kim0: Nope, this is the bootstrapping of debugging itself.. we might indeed have to log it in the future
[14:11] <niemeyer> kim0: Can you please paste the new process list so we can reach the new hook
[14:12] <kim0> http://paste.ubuntu.com/616722/
[14:13] <kim0> guess no one uses debug-hooks really :)
[14:13]  * kim0 afk for 5 mins
[14:15] <niemeyer> kim0: We do, but we don't generally kill processes in the middle
[14:15] <hazmat> kim0, just me ;-)
[14:15] <hazmat> need to run a quick errand, back in a bit
[14:23] <niemeyer> kim0: Let me know when you're back.. we can follow on a bit if you're interested
[14:24] <kim0> niemeyer: back
[14:25] <niemeyer> kim0: Ok, let's see /tmp/tmpR1UhMY-db-relation-joined then
[14:25] <kim0> niemeyer: http://paste.ubuntu.com/616737/
[14:26] <niemeyer> kim0: Ok, please figure ENSEMBLE_DEBUG from /proc/9187/environ, and list $ENSEMBLE_DEBUG/env.sh
[14:28] <kim0> niemeyer: can't see ENSEMBLE_DEBUG .. paste http://paste.ubuntu.com/616742/
[14:30] <niemeyer> kim0: Hmm.. I guess it wasn't exported
[14:31]  * niemeyer htinks
[14:31] <niemeyer> thinks
[14:34] <niemeyer> kim0: Ok, let's try to find by force: cd /tmp && find -name env.sh
[14:34] <niemeyer> kim0: Will probably see more than one
[14:35] <kim0> niemeyer: 3 of em
[14:35] <niemeyer> kim0: Ok, let's fine the one with db-relation-joined
[14:36] <kim0> http://paste.ubuntu.com/616746/
[14:36] <kim0> http://paste.ubuntu.com/616747/
[14:36] <kim0> http://paste.ubuntu.com/616748/
[14:37] <kim0> niemeyer: I tried grep'ing .. doesn't have joined in them
[14:37] <niemeyer> kim0: Well, that's likely the issue then.. let me check
[14:39] <niemeyer> kim0: That's weird..
[14:39] <niemeyer> kim0: All of them have ENSEMBLE_AGENT_SOCKET
[14:39] <kim0> maybe none of them is sourced
[14:40] <niemeyer> kim0: This is the right one for db-relation-joined: http://paste.ubuntu.com/616747/
[14:41] <niemeyer> kim0: Can you please paste the hook.sh file living in the same directory?
[14:41] <niemeyer> kim0: Well, that's the thing
[14:41] <niemeyer> kim0: There's no easy way for bash to be executed without this being sourced
[14:41] <kim0> niemeyer: http://paste.ubuntu.com/616754/
[14:41] <niemeyer> kim0: As you can see..
[14:42] <niemeyer> kim0: That prior paste is from /tmp/tmp.Sj2ilkd53B/env.sh, right?
[14:42] <kim0> double checking
[14:43] <kim0> should be yes
[14:43] <niemeyer> kim0: Ok, so there's really no way for bash to be executed without it being sourced, which is awkward..
[14:44] <niemeyer> kim0: You got a bash, without the env variables, but the only way for that bash to have come up, was through the sourcing line
[14:44] <niemeyer> Hmmm
[14:44] <kim0> thinking as well
[14:46] <kim0> niemeyer: parent process for the Window1 shell, is byobu, not the hook.sh ?
[14:47] <niemeyer> kim0: Yeah, that's strange
[14:47] <kim0> hook.sh should still be running if it fired us right
[14:47] <niemeyer> kim0: Indeed
[14:47] <niemeyer> kim0: This would also justify the previous issue as well, interestingly
[14:48] <niemeyer> kim0: Hmm
[14:48] <niemeyer> kim0: Let me do a local test, hold on
[14:49] <kim0> niemeyer: pstree -p .. if that's helpful http://paste.ubuntu.com/616757/
[14:51] <hazmat>   nice.. half way to my walking desk finished
[14:51] <kim0> hazmat: walking desk ?
[14:52] <hazmat> kim0, treadmill with keyboard tray and monitor stand
[14:52] <kim0> oh that's new to me ... sounds cool indeed :)
[14:52] <hazmat> kim0,  http://opinionator.blogs.nytimes.com/2010/02/23/stand-up-while-you-read-this/ ... http://www.nytimes.com/2008/09/18/health/nutrition/18fitness.html
[14:53] <hazmat> kim0, lots of a good evidence for the benefits vs sitting in a chair all day
[14:53] <kim0> yeah that's intuitive
[14:53] <hazmat> the only problem is that the treadmill weighs 250 pounds.. just carried it up the stairs.. so most of the way done on the setup
[14:54]  * hazmat catches up the irc log to get up to speed on debug-hooks
[14:54] <kim0> hazmat: congrats :) send pics to warthogs :)
[14:56] <kim0> niemeyer: I'm going for a late lunch .. I have inserted your ssh key into ec2-67-202-22-46.compute-1.amazonaws.com (drupal/0) should you want to login to it
[14:56] <niemeyer> kim0: Cheers
[14:56] <niemeyer> kim0: Will check it out
[14:56] <kim0> cool
[15:16] <niemeyer> hazmat: I suspect both issues likely boil down to the way the shell is being executed
[15:16] <niemeyer> hazmat: It's doing a two-step execution, and it's not entirely clear why
[15:16] <hazmat> niemeyer, what's strange is that it works sometimes
[15:16] <hazmat> writing up a reply to tom for his questions on list
[15:16] <niemeyer> hazmat: It first creates a window, which spawns an outside shell by screen itself
[15:17] <niemeyer> hazmat: then overwrites a shell onto it
[15:17] <niemeyer> hazmat: I suspect we may be hitting some race within screen itself
[15:17] <niemeyer> hazmat: Is there a reason why you coded it like that, or is it safe to change?
[15:18] <hazmat> niemeyer, its safe to change, i thought that creation was per your suggestion
[15:19] <niemeyer> hazmat: It's unrelated to my suggestion
[15:19] <hazmat> the openstack nova screen setup does a similiar setup
[15:19] <niemeyer> hazmat: It's executing two shells for no reason
[15:19] <niemeyer> hazmat: Rather than only hook.sh
[15:19] <hazmat> right
[15:19] <hazmat> so instead of creating the window it should just exec in the named window?
[15:20] <niemeyer> hazmat: The "screen" command of screen takes an executable as an argument
[15:20] <niemeyer> hazmat: -X screen -t .. hook.sh
[15:20] <niemeyer> hazmat: The shell I'm seeing in kim0's is the shell from the first screen command, not the one from the exec
[15:21] <hazmat> niemeyer, that sounds good to me
[16:01] <kim0> hope that bug got caught
[16:03] <niemeyer> kim0: Sounds like so..
[16:03] <niemeyer> kim0: Will try something this afternoon
[16:03] <kim0> awesome
[16:03] <niemeyer> kim0: Thanks for all your help
[16:03] <kim0> All thanks to you :)
[16:15]  * hazmat lunches
[16:20]  * niemeyer too
[17:42] <kim0> hmm
[17:42] <kim0>         state: install_error
[17:43] <kim0> if service is having install_error .. any facility to figure out what went wrong
[17:46] <kim0> ok I could figure it out
[17:51] <niemeyer> kim0: I was kind of expecting that..
[17:51] <niemeyer> kim0: Is that the service we were debugging?
[17:51] <kim0> niemeyer: I shutdown the env and started a fresh
[17:51] <niemeyer> kim0: Oh, ok
[17:51] <niemeyer> kim0: ensemble log, ensemble debug-hook, etc
[17:52] <kim0> niemeyer: does the log not provide hooks stdout any more ?
[17:52] <kim0> is it supressed by default
[17:52] <niemeyer> kim0: It does, but you have to turn it on earlier
[17:52] <niemeyer> We should really have a feature where it logs by default
[17:52] <niemeyer> and rotates them out after a while
[17:52] <niemeyer> kim0: Otherwise, the best bet is logging in the machine and checking logs
[17:53] <niemeyer> kim0: You should be able to retry, though
[17:53] <niemeyer> kim0: Run debug-hook
[17:53] <niemeyer> kim0: and then run ensemble resolved with the --retry argument
[17:59] <kim0> niemeyer: hmm .. service unit is stuck somehow
[17:59] <kim0> here is status http://paste.ubuntu.com/616891/
[17:59] <kim0> I hope you don't mind all the questions
[17:59] <niemeyer> kim0: Not at all.. I'm actually going to fix some of the issues you found today
[18:00] <kim0> yeah .. the basic workflow should be smoother ..
[18:01] <kim0> so, I had an error in a hook, now I have no idea how to nudge things and get them back
[18:01] <niemeyer> kim0: resolved, as I mentioned above
[18:02] <kim0> bin/ensemble resolved --retry drupal/1
[18:02] <kim0> tried this
[18:02] <niemeyer> kim0: Ok, what happened next?
[18:02] <kim0> debug-log only shows mysql related messages
[18:02] <kim0> and status is the same
[18:03] <niemeyer> kim0: Have you actually fixed the original reason why your hook failed?
[18:03] <kim0> niemeyer: yes I did
[18:04] <niemeyer> kim0: Why was it failing before?
[18:04] <kim0> niemeyer: ssh'ed into the machine .. and ran it
[18:04] <kim0> niemeyer: some cd to a non existent directoyy
[18:04] <kim0> niemeyer: I ran the script inside the instance .. it is fine now
[18:04] <niemeyer> kim0: Is it returning successfully now? (exit status 0)
[18:04] <kim0> checking again
[18:06] <kim0> can't really check again accurately
[18:06] <kim0> ensemble-log giving errors because it's running outside the environment
[18:06] <kim0> apt-get saying packages already installed ..etc
[18:06] <kim0> but yeah it seems correct
[18:07] <niemeyer> kim0: So how did you run it befor?
[18:07] <niemeyer> e
[18:07] <kim0> niemeyer: in a debug-hooks session
[18:07] <kim0> /var/lib/ensemble/units/drupal-1/formula/hooks/install
[18:07] <niemeyer> kim0: If apt-get install is failing, it won't work as a hook either
[18:08] <kim0> it's just saying .. the package is already installed
[18:08] <kim0> the script is fine trust me :)
[18:08] <niemeyer> kim0: :)
[18:09] <niemeyer> kim0: If you have already executed it by hand, you can just say "resolved"
[18:09] <niemeyer> kim0: Without --retry
[18:09] <niemeyer> kim0: But I suspect that fuzzing may have triggered something else.. that "state: null" isn't really great
[18:09] <kim0> yeah
[18:09] <niemeyer> kim0: Try the resolved trick
[18:10] <kim0> did that
[18:10] <niemeyer> kim0: This just states to Ensemble "I have resolved the problem"
[18:10] <kim0> still null
[18:11] <niemeyer> kim0: Ok, try redeploying the fixed formula then
[18:11] <niemeyer> kim0: We'll have to investigate a bit that scenario
[18:11] <niemeyer> kim0: (--retry with a broken script, etc)
[18:11] <kim0> how do I redeploy
[18:12] <niemeyer> kim0: But first, I'll fix the debug-hook stuff we debugged this morning
[18:12] <kim0> ok np ..
[18:12] <niemeyer> kim0: Same thing you did earlier?
[18:12] <kim0> I'll pick this up later
[18:12] <kim0> fresh environment .. ok
[18:13] <kim0> In the tutorial .. I'm assuming the formula is going to have errors
[18:13] <niemeyer> kim0: Nope
[18:13] <niemeyer> kim0: Just remove the unit
[18:13] <niemeyer> kim0: and add it again
[18:13] <kim0> ok
[18:13] <niemeyer> kim0: Yeah, that's a good thing
[18:13] <niemeyer> kim0: You can also upgrade the formula in general
[18:13] <kim0> says, error state cannot be upgraded
[18:13] <niemeyer> kim0: This is what we're preparing Ensemble to be able to do
[18:14] <kim0> or so
[18:14] <niemeyer> kim0: Error?  Change, upgrade..
[18:14] <kim0> says like, formula is in error state .. so it cannot be upgraded
[18:14] <kim0> I lost the exact message though
[18:15] <niemeyer> kim0: Yeah, you have to resolve it first..
[18:15] <kim0> Ok .. I'll need to try this again (recovering from a formula with errors )
[18:15] <kim0> and will discuss again with you
[18:15] <niemeyer> kim0: Because otherwise we can't assume a known state
[18:15] <niemeyer> kim0: Imagine an install hook failed in the middle
[18:16] <kim0> that's what it was :D
[18:16] <kim0> so I just need to know the recommended recovery steps
[18:16] <niemeyer> kim0: Right.. simply upgrading won't really yield a working system necessarily
[18:16] <niemeyer> kim0: Because half of it executed
[18:16] <kim0> how to know what went wrong .. release a fix .. start recovering
[18:17] <niemeyer> kim0: What we want is this:
[18:17] <niemeyer> kim0: install failed: check logs, fix it or retry, upgrade if wanted
[18:18] <niemeyer> kim0: With debug-hook if desired, to understand what's going on
[18:18] <kim0> then use "resolved" right ?
[18:18] <niemeyer> kim0: Right, after the "fix it or retry"
[18:18] <niemeyer> kim0: Or during it actually.. retry is done with resolved
[18:19] <kim0> is there a way to upload the fixed new hook ?
[18:20] <niemeyer> kim0: upgrade-formula
[18:20] <kim0> which refuses to work in error state ?
[18:20] <niemeyer> kim0: Yes, which is the right thing to do
[18:21] <kim0> ok .. so I'd still need to upload my fixed hook
[18:21] <niemeyer> kim0: The error state must be acknowledged by the administrator
[18:21] <niemeyer> kim0: and if an install hook blows up in the middle, upgrading a new install hook with the error fixed won't necessarily make it work
[18:22] <niemeyer> kim0: mkdir foo, run twice, breaks
[18:22] <kim0> so our recommended approach is kill the instance, and start a fresh machine ?
 kim0: What we want is this:
 kim0: install failed: check logs, fix it or retry, upgrade if wanted
 kim0: With debug-hook if desired, to understand what's going on
[18:22] <kim0> the "fixing and trying" cycle is what I'm trying to grasp
[18:23] <niemeyer> kim0: Fixing it means fixing the actual problem within the formula..
[18:23] <kim0> and what about the trying
[18:23] <niemeyer> kim0: Sorry, within the service unit
[18:23] <kim0> on a new instance ?
[18:23] <niemeyer> kim0: If there's nothing to do.. you just run "resolved"
[18:23] <kim0> ah
[18:24] <kim0> so I fix the problem manually .. then run resolved
[18:24] <niemeyer> kim0: Yes, that's one way to do it
[18:24] <niemeyer> kim0: The other way to do it is to code an idempotent hook
[18:24] <niemeyer> kim0: This enables you to run resolved and upgrade a new formula
[18:24] <kim0> and use, resolved --retry
[18:24] <kim0> right ?
[18:25] <niemeyer> kim0: If that's what you want to do
[18:25] <niemeyer> kim0: The problem is really quite simple
[18:25] <niemeyer> kim0: When a hook fails, Ensemble will stop running hooks until the admin acknowledges it
[18:26] <niemeyer> kim0: If you run ensemble resolved, it forgets about the old hook, and continues execution
[18:26] <niemeyer> kim0: If you want to run the old hook again before continuing, you run resolved --retry
[18:26] <niemeyer> kim0: and that's it
[18:26] <niemeyer> kim0: Whether you upgrade the formula, change the hook in place to try things out, run debug-hook, run ensemble log, etc, is really up to you
[18:27] <niemeyer> kim0: We're coding tools to give you everything you need to understand how things are behaving
[18:27] <niemeyer> kim0: and fixing them
[18:27] <kim0> I guess the workflow I had in mind is .. install hook blows up .. I ssh into machine .. figure out why it blew up .. then I fix the hook *locally* .. then somehow ensemble would upload the new version and run that
[18:27] <kim0> but the workflow you explained is perfectly fine
[18:27] <kim0> thanks
[18:28] <niemeyer> kim0: Well, maybe there are further options we can develop around this
[18:29] <kim0> Yeah, recovering from broken formulas should be smooth .. since people are going to make all sorts of mistakes :D
[18:29] <kim0> niemeyer: thanks for all the explanation and patience :)
[18:29] <niemeyer> kim0: No worries
[18:29] <niemeyer> kim0: Good to talk about that stuff.. it's important to learn how other people feel about the system too
[18:30]  * kim0 nods
[18:45]  * SpamapS just discovered resolved yesterday btw
[18:45] <SpamapS> would have saved me quite a few remove-relation/add-relation cycles ;)
[18:47] <niemeyer> SpamapS: Sorry about that :-)
[18:49] <SpamapS> Yes shame on you guys for making the thing work welle nough to survive hundreds and hundreds of remove/adds.
[18:50] <_mup_> ensemble/close-zk-port r240 committed by<EMAIL_ADDRESS>[18:50] <_mup_> Do not open zk port on AWS firewall.
[18:51] <niemeyer> SpamapS: Yeah, good thing we are in a polishing cycle.. :)
[18:58] <_mup_> Bug #791973 was filed: Ensemble shouldn't open the EC2 firewall for zk access <Ensemble:Confirmed> < https://launchpad.net/bugs/791973 >
[19:11] <niemeyer> hazmat:   sudo -u ubuntu screen -dmS $SESSION_NAME
[19:11] <niemeyer> hazmat: -u ubuntu?  Shouldn't this be root?
[19:12] <niemeyer> Also, this command seems to create a new session, irrespective of whether there's an existing one with the same name
[19:14] <hazmat> its connecting to the ubuntu user's screen session from the login shell
[19:15] <niemeyer> hazmat: Yes, but isn't the ubuntu user connecting to root's screen using sudo?
[19:15] <hazmat> niemeyer, no its not that requires a setuid binary screen program
[19:15] <niemeyer> hazmat: Using sudo?
[19:16] <hazmat> niemeyer, that would be fine
[19:16] <hazmat> i thought you where referring to multi-user screen
[19:16] <niemeyer> hazmat: ssh -t ubuntu@%s sudo byobu -xRS %s-hook-debug -t shell
[19:16] <hazmat> sounds good
[19:16] <niemeyer> hazmat: The debug-hook command connects a session from root
[19:17] <niemeyer> hazmat: Which means doing -u ubuntu would put the session in another place
[19:17] <niemeyer> Ok, I'll fix that as well
[19:24] <niemeyer> So there's apparently no way to start a screen session unless it doesn't yet exist.. :(
[19:33] <niemeyer> Ok, I'll give tmux a try..
[19:38] <niemeyer> smoser!
[19:38] <niemeyer> smoser: Was just reminding of you while hacking a shell script
[19:39] <niemeyer> smoser: exec &> foo.. that's an awesome trick I learned with you recently :)
[19:39] <smoser> that is bash only
[19:39] <smoser> exec > foo 2>&1
[19:40] <smoser> would be the posix shell equivalent
[19:40] <niemeyer> smoser: Nice
[19:40] <niemeyer> smoser: Will use that
[19:53] <niemeyer> hazmat: If  a sigspec is EXIT (0) the command arg is executed on exit from the shell.
[19:53] <niemeyer> hazmat: Looks handy
[19:53] <niemeyer> hazmat: Sorry, that was a quote
[19:53] <niemeyer> Wonder if that will *always* execute
[19:54]  * niemeyer tests
[19:55] <niemeyer> Yeah, works
[20:29] <_mup_> ensemble/expose-hook-commands r242 committed by<EMAIL_ADDRESS>[20:29] <_mup_> Implemented open-port, close-port hook commands
[20:29] <jimbaker>  biab
[20:42] <_mup_> ensemble/debug-hook-fixes r240 committed by<EMAIL_ADDRESS>[20:42] <_mup_> Fixed several issues in the debug-hook shell payload, and replaced
[20:42] <_mup_> screen with tmux to handle concurrent session creation without races.
[20:42] <_mup_> Let's see if this works in real test cases now.
[20:45] <niemeyer> What's the proper format to put ensemble-branch in the environment's file again?  I recall we had a weird issue with one of the url forms, and I killed my commented option by mistake.
[20:46] <niemeyer> jimbaker, hazmat, bcsaller: ?
[20:46] <bcsaller> niemeyer: ensemble-branch: lp:~bcsaller/ensemble/config-set-lifecycle
[20:47] <niemeyer> bcsaller: Does that work?  Nice, I think that was one of the formats which was not working
[20:47] <bcsaller> its been working for me
[20:47] <niemeyer> bcsaller: Super, thanks
[20:48] <niemeyer> bcsaller: It was a crazy issue we had in the sprint..  Launchpad was just barfing on https or http or lp, can't recall which one..
[20:50] <SpamapS> niemeyer: I'm thinking of uploading principia-tools to the ensemble ppa... thoughts before I do that?
[20:50] <niemeyer> SpamapS: No, it sounds good
[20:51] <niemeyer> 2011-06-02 16:50:32,617 ERROR ProviderError: Interaction with machine provider failed: ConnectionTimeoutException('could not connect before timeout after 1 retries',)
[20:51] <niemeyer> Feels like a regression on the waiting behavior
[21:23] <niemeyer> kim0: You were right.. debug-hook needed some good debugging by itself
[21:40] <_mup_> ensemble/debug-hook-fixes r241 committed by<EMAIL_ADDRESS>[21:40] <_mup_> - Add additional hook names to valid list on debug-hook.
[21:40] <_mup_> - Fix debug-hook shell template.
[22:06] <_mup_> Bug #792071 was filed: relation-get blowing up badly during install hook <Ensemble:New> < https://launchpad.net/bugs/792071 >
[22:16] <niemeyer> Observing debug-hooks actually working is beautiful!
[22:17] <niemeyer> Do changes on one side, exit.. boom! The other side pops up!
[22:23]  * niemeyer ponders about how to execute a script by piping it on stdin
[22:24] <niemeyer> Hah, /bin/bash -
[22:58] <kim0> niemeyer: great news!
[22:59] <kim0> so it's working as it should now .. woohoo
[22:59] <kim0> niemeyer: Would you think it'd be better for debug-hooks to open the hook code in vim in the new screen window, instead of dropping me in a blank shell ?
[23:03] <niemeyer> kim0: Hmm
[23:03] <niemeyer> kim0: No, probably not.. this would likely pass the wrong idea about what you can do within the debug hooks session
[23:04] <niemeyer> kim0: It's useful to look at the script, but you're free to do pretty much anything
[23:04] <kim0> hmm
[23:04] <kim0> to debug the hook .. I had to figure out where it was
[23:04] <kim0> and for that I used "find /"
[23:04] <kim0> which sux ofc
[23:05] <niemeyer> kim0: Yeah, I noticed this as well
[23:05] <bcsaller> it should cd you into the formula directory I think
[23:05] <niemeyer> kim0: That's a failure in the hook execution logic
[23:05] <bcsaller> I think we have a bug for that
[23:05] <niemeyer> kim0: Hooks should always be executed within the formula directory
[23:05] <niemeyer> kim0: When debugging or not
[23:05] <niemeyer> bcsaller: Hey!
[23:06] <bcsaller> :)
[23:06] <kim0> bcsaller: the cd into hooks dir, sounds like a good compromise .. is it planned
[23:06] <bcsaller> kapil and I agreed it was a good idea when we talked about it
[23:07] <niemeyer> Agreed, that's important even for plain hooks
[23:07] <niemeyer> I mean, when executing the real ones rather than debugging
[23:11] <_mup_> ensemble/expose-hook-commands r243 committed by<EMAIL_ADDRESS>[23:11] <_mup_> Testing on args and logging for port commands
[23:21] <niemeyer> Woohay
[23:31] <kim0> expose merged ?
[23:42] <niemeyer> kim0: Not yet
[23:42] <niemeyer> jimbaker: Is hard at work on it
[23:46] <_mup_> ensemble/debug-hook-fixes r242 committed by<EMAIL_ADDRESS>[23:46] <_mup_> - Use the real unit name as the session, since tmux is happy with that.
[23:46] <_mup_> - Send an initialization script with a simple tmux.conf when firing
[23:46] <_mup_>   ssh through the debug-hooks command.  Use screen shortcuts since
[23:46] <_mup_>   people will be happier with that.
[23:46] <_mup_> [WIP]
[23:47] <niemeyer> Okay, time to step out and do something else..
[23:47] <niemeyer> See y'all tomorrow!
[23:54] <jimbaker> kim0, the expose work is getting close - hook commands are almost ready for review, i have most of the remaining provisioning work already done from a spike branch, and the ec2 group authorization model maps readily against what is necessary for a provider
[23:55] <kim0> jimbaker: sounds like great news .. rock on :)
[23:56] <SpamapS> Hmm.. I've been thinking about proposing a specification for 'machine-info-get' .. Teyo from Puppet suggested that they'd be interested in collaborating on a library to collect info about the current machine.. and it would be really useful to have this...
[23:57] <SpamapS> So I'm thinking the machine agent should have some of this information available.. some from the machine provider, some from this library
[23:58] <SpamapS> That would solve the 'Whats my private IP? Whats my public IP?' case.
[23:58] <SpamapS> How would I propose such a spec?


[13:38] <h00k> greetings
[13:45] <EgyParadox> hi
[13:46] <h00k> EgyParadox: hello. I don't remember meeting you. Where-about in the state are you from?
[13:46] <EgyParadox> I am from Egypt
[13:47] <EgyParadox> not from US
[13:47] <EgyParadox> but I noticed that the WI team is active
[13:47] <EgyParadox> and I used to live there
[13:48] <h00k> EgyParadox: ah, welcome
[13:48] <h00k> We are somewhat active
[13:49] <h00k> we try, anyway
[13:49] <EgyParadox> yeah I noticed there are many events
[13:50] <EgyParadox> The Egyptian became somehow active only recently
[13:51] <h00k> EgyParadox: Yeah, we have some Ubuntu hours going on, we are going to try the Global Jam, too
[13:53] <EgyParadox> nice
[13:54] <EgyParadox> We just had our ubuntu our
[13:54] <EgyParadox> hour*
[13:54] <EgyParadox> it was fun, we haven't had the global jam yet
[13:58] <EgyParadox> What about the number of people attending the events?
[13:59] <h00k> EgyParadox: usually, for the Ubuntu Hour, it is around 3-4, from what it sounds like
[14:00] <EgyParadox> what about release parties?
[14:00] <EgyParadox>  /install fests
[14:06] <h00k> We had one...what, 2 years ago now, and another 6 months after, but not for the last 2 releases
[14:06] <EgyParadox> I mean the numberof people attending
[14:07] <h00k> http://anthonyrhook.com/blog/2009/11/08/release-party-success/
[14:07] <h00k> we had 16 on the first one
[14:07] <h00k> I don't remember how many at the one in Madison
[14:08] <h00k> maybe... 12? 14?
[14:08] <EgyParadox> I am surprised
[14:09] <h00k> :)
[14:09] <h00k> Now that my wedding is over, maybe I'll throw something down for Oneric
[14:10] <EgyParadox> I think 100+ attended our first release party
[14:10] <EgyParadox> :)
[14:10] <EgyParadox> Congratulations
[14:10] <h00k> Thanks
[14:10] <h00k> EgyParadox: that's awesome
[14:10] <EgyParadox> yeah
[14:10] <EgyParadox> it was a nice start
[14:11] <EgyParadox> *install fest
[14:12] <EgyParadox> first install fest*
[14:12] <EgyParadox> https://wiki.ubuntu.com/EgyptTeam/Events/2010-05-08-LucidReleaseParty
[14:13] <h00k> It'd be fun to get shirts, or tell people that are attending to get some sort of Ubuntu swag to wear it
[14:16] <EgyParadox> Yeah
[14:16] <EgyParadox> We put some artwork for the designs so anybody could print
[14:17] <EgyParadox> This is our first release party
[14:17] <EgyParadox> https://wiki.ubuntu.com/EgyptTeam/Events/2010-10-30-Cairo-release-party-for-Ubuntu-Maverick-Meerkat
[14:18] <EgyParadox> https://wiki.ubuntu.com/EgyptTeam/Artwork
[14:24] <h00k> I think we talkeda bout borrowing a wiki header like yours
[14:24] <h00k> :( https://wiki.ubuntu.com/WisconsinTeam
[14:25] <EgyParadox> We did talk?
[14:26] <h00k> We did talk about a nice wiki header like yours, I have to check my logs
[14:26] <EgyParadox> I can't remember
[14:26] <EgyParadox> was it thelinuxer?
[14:27] <h00k> Oh, no, I mean the LoCo talked about it
[14:27] <h00k> not you/I
[14:27] <EgyParadox> oh ok
[14:27] <EgyParadox> I thought in the US more people would attend events
[14:27] <h00k> It's hard with Wisconsin being spread out
[14:28] <EgyParadox> Why?
[14:29] <h00k> We seem to have some people interested in the Madison/Milwaukee area, but the further north you get, it's more spread-out
[14:32] <EgyParadox> I thought its the other way aroujd
[14:32] <EgyParadox> around*
[14:36] <EgyParadox> ?
[14:36] <h00k> EgyParadox: as in...?
[14:36] <h00k> I just sent an email out, a call for artwork
[14:38] <EgyParadox> I thought it would be more spread in Madison/MIlwaukee
[14:38] <h00k> EgyParadox: there is more of a concentration down there
[14:38] <h00k> As in, more people
[14:38] <EgyParadox> oh ok
[14:41] <h00k> EgyParadox: you have a magazine cover for artwork?!
[14:41] <h00k> https://lists.ubuntu.com/archives/ubuntu-us-wi/2011-August/000376.html
[14:41] <h00k> er
[14:42] <h00k> https://wiki.ubuntu.com/EgyptTeam/Artwork?action=AttachFile&do=get&target=Prototype.jpg
[14:43] <EgyParadox> There were plans for a magazine
[14:43] <EgyParadox> but I dont know what happened really
[14:43] <EgyParadox> I think there is
[14:43] <EgyParadox> I am not responsible for art work
[14:46] <h00k> Cool, though.
[16:08] <EgyParadox> What about other states?
[16:08] <h00k> EgyParadox: what about them?
[16:08] <mikeputnam> h00k: Μπορώ να φάω σπασμένα γυαλιά χωρίς να πάθω τίποτα.
[16:09] <mikeputnam> something UTF8 in Greek ^^^
[16:09] <h00k> mikeputnam: what
[16:09] <mikeputnam> did it work?
[16:09] <h00k> mikeputnam: yes, I could see that ;)
[16:09] <h00k> mikeputnam: Yeah, I fixed it
[16:09] <h00k> ■▎⡈❩
[16:09] <h00k> .screenrc doesn't always do UTF8, even if you tell it to
[16:09] <mikeputnam> screen!?
[16:09] <h00k> mikeputnam: YES!
[16:09] <h00k> mikeputnam: irssi
[16:09] <mikeputnam> tsk-tsk
[16:09] <h00k> mikeputnam: what's wrong with that?
[16:10] <mikeputnam> http://tmux.sourceforge.net/
[16:10] <EgyParadox> Are they active like the WI team?
[16:10] <mikeputnam> much more excellenter
[16:10] <h00k> EgyParadox: some probably are, I'm not sure
[16:20] <h00k> mikeputnam: I have used terminator in the past
[16:20] <h00k> mikeputnam: I just run screen on my VPS where my irssi runs
[16:20] <h00k> mikeputnam: locally, I've been playing with byobu lately
[16:22] <mikeputnam> h00k: http://blog.dustinkirkland.com/2011/06/anyone-interested-in-byobu-profiles-for.html
[16:22] <h00k> mikeputnam: cool
[16:23] <mikeputnam> h00k: i highly recommend tmux over screen
[16:23] <h00k> apparently ;)
[16:23] <mikeputnam> i also op #tmux
[16:23] <mikeputnam> and wrote the web page
[16:23]  * mikeputnam <= fanbois
[16:32] <h00k> nice
[20:43] <mikeputnam> big solar flare today http://iswa.gsfc.nasa.gov:8080/IswaSystemWebApp/iSWACygnetStreamer?timestamp=2038-01-23+00%3A44%3A00&window=-1&cygnetId=261
[20:44] <h00k> Interesting
[20:44] <h00k> I wonder when that's going to knock out phones ^.^


[01:05] <fazer> balloons ^^^
[05:45] <Kamran_> Is anyone online.....
[06:16] <McIntireEvan> With GCI coming to an end, I just want to give a quick thanks to all the admins and mentors this year, it was a blast, and I've loved working with ubuntu and will continue to do so for hopefully a long time to come
[06:17] <McIntireEvan> balloons, jose ^^ Thanks you guys!
[06:18] <McIntireEvan> Also, congrats in advance to the winners/finalists :)
[12:38] <MatthewAllen> I'd like to throw out a thankyou to all the admins and mentors that have been there to help us all throughout Code-In this year, was my first time competing and first time contributing to open source and I'd like to thank you all for making it great fun and looking out for us when we needed a hand. Good luck and well done to the finalists :)
[12:39] <tsimonq2> McIntireEvan, MatthewAllen: Are you gonna contribute to Ubuntu outside of GCI? If so, you can probably find most of us in #ubuntu-offtopic. I don't know about the others, but I'm willing to provide a bit of help. :)
[12:44] <knome> i would think this channel will be around for quite some time too (as long as people use it)
[12:52] <MatthewAllen> tsimonq2, I've been mainly contributing with bug fixing on the QA-Tracker so I'll stick around on the Ubuntu-Quality IRC most likely
[12:53] <tsimonq2> MatthewAllen: alright, I'm there if you need anything :)
[12:53] <tsimonq2> MatthewAllen: QA is pretty fun too :D
[12:59] <knome> tsimonq2, "too" implies #ubuntu-offtopic is fun, but i don't know if i can agree with that :P
[13:36] <malevasquez> MatthewAllen is right, big thanks to all the mentors & admins that helped us with everything! It was a great experience :)
[13:37] <malevasquez> I'll definitely keep contributing now that Code-In is over
[15:34] <xcub> Thank you to all the admins and mentors this year! You guys made my introduction to open source contribution a much more fun experience :)
[15:44] <balloons> Good morning!
[15:45] <DanChapman> morning balloons :-)
[15:45] <balloons> I can do a final update today
[16:09] <balloons> Any last minute tasks?
[16:09] <balloons> ;)
[16:30] <McIntireEvan> tsimonq2: yup, Ive been working on the terminal app some, i plan to do that and more :)
[16:34] <McIntireEvan> btw, who else here that participated is a senior? You all know where youre going to college yet?
[16:36] <malevasquez> McIntireEvan: I'm still a junior :(
[16:36] <malevasquez> Where are you planning to go to college?
[16:39] <McIntireEvan> well Im still waiting to hear bacl from my top choice, University of Maryland, College Park, but I hear bacl from them this week and Im confident :)
[16:44] <malevasquez> Awesome, good luck!
[16:45] <McIntireEvan> Thanks! :)
[16:50] <balloons> the big finish!
[16:51] <knome> not the big finnish?
[16:52] <balloons> would we need to vote on the latter?
[16:52] <knome> hmmh. depends :P
[16:54] <balloons> http://people.canonical.com/~nskaggs/gcileaderboard.html
[16:55] <balloons> Congrats to the top students!
[16:56] <McIntireEvan> Congrats all :)
[16:58] <malevasquez> Wow that's pretty cool
[16:58] <malevasquez> Congrats everyone!
[16:59] <balloons> malevasquez, you knocked out alot of tasks! Well done
[17:00] <malevasquez> balloons, thank you so much for your help
[17:00] <balloons> you are all quite welcome. It's been a whirlwind, but I've enjoyed helping all of you
[17:02] <McIntireEvan> i had hoped to do a tonnnn of tasks this year, but school and timr zones said otherwise. Either way, im happy with the tasks I did and the stuff Ive already done outside of the tasks
[17:04] <wxl> man it was unfortunate that i had to work the last weekend :(
[17:07] <wxl> thanks for picking up the slack for me balloons
[17:14] <balloons> no worries wxl


[05:46] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.6 => 4.0.0-1ubuntu8.7] (ubuntu-server, virt)
[05:47] -queuebot:#ubuntu-release- Unapproved: libvirt (cosmic-proposed/main) [4.6.0-2ubuntu3.2 => 4.6.0-2ubuntu3.3] (ubuntu-server, virt)
[07:50] <juliank> sil2100: we can release apt/trusty
[07:50] <juliank> the regressions are not regressions
[07:59] <ginggs> these are not the regressions you are looking for
[08:18] -queuebot:#ubuntu-release- New: accepted golang-github-go-xorm-core [amd64] (disco-proposed) [0.6.2-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [amd64] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [armhf] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [ppc64el] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:18] -queuebot:#ubuntu-release- New: accepted golang-github-teris-io-shortid [amd64] (disco-proposed) [1.0+git20171029.771a37c-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [i386] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [arm64] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:18] -queuebot:#ubuntu-release- New: accepted hcloud-cli [s390x] (disco-proposed) [1.11.0+git20190206.5780af6-1]
[08:19] -queuebot:#ubuntu-release- New: accepted sat-pubsub [amd64] (disco-proposed) [0.3.0a1-1]
[08:19] -queuebot:#ubuntu-release- New: accepted uefitool [arm64] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted uefitool [i386] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted uefitool [s390x] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted uefitool [amd64] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted uefitool [ppc64el] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted uefitool [armhf] (disco-proposed) [0.26.0-1]
[08:20] -queuebot:#ubuntu-release- New: accepted vue-router.js [amd64] (disco-proposed) [3.0.2+ds-1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [amd64] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [armhf] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [ppc64el] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [arm64] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [s390x] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[08:27] -queuebot:#ubuntu-release- New: accepted libreoffice [i386] (disco-proposed) [1:6.2.1~rc1-0ubuntu1]
[09:19] -queuebot:#ubuntu-release- New: rejected masakari [source] (disco-proposed) [7.0.0~b1-0ubuntu1]
[09:28] -queuebot:#ubuntu-release- New source: flatbuffers (disco-proposed/primary) [1.10.0-0ubuntu1]
[09:32] -queuebot:#ubuntu-release- New: accepted lazarus [amd64] (disco-proposed) [2.0.0+dfsg-1]
[09:32] -queuebot:#ubuntu-release- New: accepted lazarus [armhf] (disco-proposed) [2.0.0+dfsg-1]
[09:32] -queuebot:#ubuntu-release- New: accepted sagemath [amd64] (disco-proposed) [8.6-5]
[09:32] -queuebot:#ubuntu-release- New: accepted sagemath [armhf] (disco-proposed) [8.6-5]
[09:32] -queuebot:#ubuntu-release- New: accepted sagemath [ppc64el] (disco-proposed) [8.6-5]
[09:32] -queuebot:#ubuntu-release- New: accepted lazarus [arm64] (disco-proposed) [2.0.0+dfsg-1]
[09:32] -queuebot:#ubuntu-release- New: accepted sagemath [arm64] (disco-proposed) [8.6-5]
[09:32] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [i386] (disco-proposed) [0.9.0-5]
[09:32] -queuebot:#ubuntu-release- New: accepted lazarus [i386] (disco-proposed) [2.0.0+dfsg-1]
[09:32] -queuebot:#ubuntu-release- New: accepted sagemath [i386] (disco-proposed) [8.6-5]
[10:14] -queuebot:#ubuntu-release- New: rejected waylandpp [source] (disco-proposed) [0.2.4-0ubuntu1]
[10:17] -queuebot:#ubuntu-release- New: rejected flatbuffers [source] (disco-proposed) [1.10.0-0ubuntu1]
[10:25] -queuebot:#ubuntu-release- New sync: libmarc-charset-perl (disco-proposed/primary) [1.35-2]
[10:26] -queuebot:#ubuntu-release- New: accepted libmarc-charset-perl [sync] (disco-proposed) [1.35-2]
[10:28] -queuebot:#ubuntu-release- New: rejected libmarc-charset-perl [source] (disco-proposed) [1.35-2build1]
[10:34] -queuebot:#ubuntu-release- New source: initramfs-tools-devices (disco-proposed/primary) [0.3]
[10:34] -queuebot:#ubuntu-release- New binary: libmarc-xml-perl [amd64] (disco-proposed/universe) [1.0.5-1] (no packageset)
[10:38] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (cosmic-proposed/universe) [2.0.0-0ubuntu2 => 2.0.0-0ubuntu2.1] (no packageset)
[10:38] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (bionic-proposed/universe) [1.4.1-0ubuntu1 => 1.4.1-0ubuntu1.1] (no packageset)
[10:38] -queuebot:#ubuntu-release- New: accepted libmarc-xml-perl [amd64] (disco-proposed) [1.0.5-1]
[10:48] -queuebot:#ubuntu-release- Unapproved: opencryptoki (cosmic-proposed/universe) [3.10.0+dfsg-0ubuntu1 => 3.10.0+dfsg-0ubuntu1.1] (no packageset)
[10:53] <ogra> abeato, infinity, vorlon initramfs-tools-devices uploaded to the dingo ... (please move out of NEW)
[10:53] <abeato> ogra, thank you!
[10:56] -queuebot:#ubuntu-release- New: accepted python-os-ken [source] (disco-proposed) [0.3.1-0ubuntu1]
[10:58] -queuebot:#ubuntu-release- New: rejected fwupd-snap [source] (disco-proposed) [1.0]
[10:59] -queuebot:#ubuntu-release- New binary: sagetex [amd64] (disco-proposed/universe) [3.2+ds-2] (no packageset)
[10:59] <vorlon> ogra, abeato: ta
[11:00] -queuebot:#ubuntu-release- New binary: python-os-ken [amd64] (disco-proposed/none) [0.3.1-0ubuntu1] (no packageset)
[11:08] -queuebot:#ubuntu-release- Unapproved: maven-debian-helper (bionic-proposed/universe) [2.3~exp1 => 2.3.2~18.04.1] (no packageset) (sync)
[11:19] <cjwatson> doko: I've turned the transition tracker back on using the trusty chroot, because I haven't been able to get ben working in bionic and don't have time to fix it.  If you want to pursue this then I suggest getting ben working in bionic, or finding people who can fix it
[11:22] -queuebot:#ubuntu-release- Unapproved: accepted maven-debian-helper [sync] (bionic-proposed) [2.3.2~18.04.1]
[11:23] -queuebot:#ubuntu-release- Unapproved: skiboot (cosmic-proposed/main) [6.1-2 => 6.1-2ubuntu0.1] (core)
[11:25] -queuebot:#ubuntu-release- Unapproved: skiboot (bionic-proposed/main) [5.10~rc4-1ubuntu1.1 => 5.10~rc4-1ubuntu1.2] (core)
[11:31] <doko> cjwatson: ta
[11:33] -queuebot:#ubuntu-release- New binary: libcatmandu-marc-perl [amd64] (disco-proposed/universe) [1.24-1] (no packageset)
[11:35] -queuebot:#ubuntu-release- New: accepted libcatmandu-marc-perl [amd64] (disco-proposed) [1.24-1]
[11:35] -queuebot:#ubuntu-release- New: accepted sagetex [amd64] (disco-proposed) [3.2+ds-2]
[11:35] -queuebot:#ubuntu-release- New: accepted python-os-ken [amd64] (disco-proposed) [0.3.1-0ubuntu1]
[12:10] -queuebot:#ubuntu-release- New sync: dd-plist (bionic-proposed/primary) [1.20-1~18.04.1]
[12:11] -queuebot:#ubuntu-release- Unapproved: plexus-languages (bionic-proposed/universe) [0.9.5-2 => 0.9.10-1~18.04.1] (no packageset) (sync)
[12:13] -queuebot:#ubuntu-release- Unapproved: testng (bionic-proposed/universe) [6.9.12-2 => 6.9.12-2ubuntu1] (no packageset) (sync)
[12:14] -queuebot:#ubuntu-release- Unapproved: libcommons-lang3-java (bionic-proposed/universe) [3.5-2ubuntu1 => 3.8-1~18.04.2] (no packageset) (sync)
[12:18] -queuebot:#ubuntu-release- New sync: dd-plist (bionic-proposed/primary) [1.20-1~18.04.1]
[12:19] -queuebot:#ubuntu-release- New: rejected dd-plist [sync] (bionic-proposed) [1.20-1~18.04.1]
[12:23] -queuebot:#ubuntu-release- Unapproved: accepted testng [sync] (bionic-proposed) [6.9.12-2ubuntu1]
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted plexus-languages [sync] (bionic-proposed) [0.9.10-1~18.04.1]
[12:25] -queuebot:#ubuntu-release- Unapproved: accepted libcommons-lang3-java [sync] (bionic-proposed) [3.8-1~18.04.2]
[12:40] -queuebot:#ubuntu-release- New: accepted dd-plist [sync] (bionic-proposed) [1.20-1~18.04.1]
[12:50] -queuebot:#ubuntu-release- Unapproved: clojure1.8 (bionic-proposed/universe) [1.8.0-5 => 1.8.0-7ubuntu1~18.04.1] (no packageset) (sync)
[12:51] -queuebot:#ubuntu-release- Unapproved: gradle (bionic-proposed/universe) [3.4.1-7ubuntu1 => 4.4.1-3~18.04.1] (no packageset) (sync)
[12:51] -queuebot:#ubuntu-release- Unapproved: jtreg (bionic-proposed/universe) [4.2-b10-1 => 4.2-b13-1ubuntu0.1~18.04.1] (no packageset) (sync)
[12:52] -queuebot:#ubuntu-release- Unapproved: maven-compiler-plugin (bionic-proposed/universe) [3.6.2-2ubuntu2 => 3.8.0-1ubuntu1~18.04.1] (no packageset) (sync)
[12:52] -queuebot:#ubuntu-release- Unapproved: surefire (bionic-proposed/universe) [2.20.1-3build1 => 2.22.0-1~18.04.1] (no packageset) (sync)
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted clojure1.8 [sync] (bionic-proposed) [1.8.0-7ubuntu1~18.04.1]
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted gradle [sync] (bionic-proposed) [4.4.1-3~18.04.1]
[12:58] -queuebot:#ubuntu-release- Unapproved: accepted jtreg [sync] (bionic-proposed) [4.2-b13-1ubuntu0.1~18.04.1]
[13:00] -queuebot:#ubuntu-release- Unapproved: accepted maven-compiler-plugin [sync] (bionic-proposed) [3.8.0-1ubuntu1~18.04.1]
[13:00] -queuebot:#ubuntu-release- Unapproved: accepted surefire [sync] (bionic-proposed) [2.22.0-1~18.04.1]
[13:03] -queuebot:#ubuntu-release- Unapproved: gradle-debian-helper (bionic-proposed/universe) [1.6ubuntu1 => 2.0.2~18.04.1] (no packageset) (sync)
[13:04] -queuebot:#ubuntu-release- Unapproved: groovy (bionic-proposed/universe) [2.4.15-1ubuntu1 => 2.4.16-1ubuntu1~18.04.1] (no packageset) (sync)
[13:08] -queuebot:#ubuntu-release- Unapproved: accepted gradle-debian-helper [sync] (bionic-proposed) [2.0.2~18.04.1]
[13:20] -queuebot:#ubuntu-release- Unapproved: accepted groovy [sync] (bionic-proposed) [2.4.16-1ubuntu1~18.04.1]
[13:34] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [source] (cosmic-proposed) [2.6.0-0ubuntu7.2]
[13:39] <bdmurray> xnox: bug 1790831 is also missing SRU information
[14:18] -queuebot:#ubuntu-release- Unapproved: accepted evolution-data-server [source] (cosmic-proposed) [3.30.5-0ubuntu<IP_ADDRESS>]
[14:25] -queuebot:#ubuntu-release- Unapproved: accepted evolution-ews [source] (cosmic-proposed) [3.30.5-0ubuntu<IP_ADDRESS>]
[14:26] -queuebot:#ubuntu-release- New source: masakari (disco-proposed/primary) [7.0.0~b1-0ubuntu2]
[14:37] -queuebot:#ubuntu-release- Unapproved: accepted evolution [source] (cosmic-proposed) [3.30.5-0ubuntu<IP_ADDRESS>]
[14:46] -queuebot:#ubuntu-release- New binary: mutter [amd64] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[14:46] -queuebot:#ubuntu-release- New binary: mutter [s390x] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[14:47] -queuebot:#ubuntu-release- New binary: mutter [i386] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[14:47] -queuebot:#ubuntu-release- New binary: mutter [ppc64el] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[14:48] <LocutusOfBorg> infinity, https://launchpad.net/ubuntu/+source/libmarc-charset-perl/+publishinghistory what did happen?
[14:51] <infinity> LocutusOfBorg: britney lost its mind?
[14:51] <LocutusOfBorg> do you think you can fix it? or is it better to no-change rebuild and reupload? I think the former
[14:51] <infinity> LocutusOfBorg: I've already copied it back.
[14:53] <infinity> Oh, britney had promoted it.  I guess I'll copy to release.
[14:58] -queuebot:#ubuntu-release- New binary: mutter [armhf] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[14:58] <LocutusOfBorg> meh, I don't think to coincidences...
[14:58] <cjwatson> I'll grep logs
[14:58] <cjwatson> Though not right now
[15:07] <cjwatson> <PlainPackageCopyJob to copy package libmarc-charset-perl from ubuntu, PROPOSED pocket, in ubuntu disco to ubuntu, RELEASE pocket, in ubuntu disco, including binaries>
[15:07] <cjwatson> raised CannotCopy:
[15:07] <cjwatson> libmarc-charset-perl 1.35-2 in disco (binaries conflicting with the existing ones)
[15:07] <cjwatson> I reckon that this is a problem specific to having copied the binaries forward from xenial, somehow
[15:07] <cjwatson> Not the usual thing
[15:08] -queuebot:#ubuntu-release- New binary: mutter [arm64] (disco-proposed/main) [3.31.90-2~fakesync] (desktop-core, desktop-extra)
[15:08] <cjwatson> Not sure exactly why but it may need a no-change rebuild to get things fixed up
[15:08] <cjwatson> Or maybe not; if it publishes then all is good
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [amd64] (disco-proposed) [3.31.90-2~fakesync]
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [armhf] (disco-proposed) [3.31.90-2~fakesync]
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [ppc64el] (disco-proposed) [3.31.90-2~fakesync]
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [arm64] (disco-proposed) [3.31.90-2~fakesync]
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [s390x] (disco-proposed) [3.31.90-2~fakesync]
[15:11] -queuebot:#ubuntu-release- New: accepted mutter [i386] (disco-proposed) [3.31.90-2~fakesync]
[15:18] <LocutusOfBorg> cjwatson, so, you think we are good? I see it is published
[15:19] <infinity> Might have been goofy because there was a powerpc build.
[15:19] <infinity> Going to wait until I see the result in rmadison, but I think it's okayish now.
[15:20] <LocutusOfBorg> yes, I checked rmadison and it wasn't happy... interesting the powerpc thing..
[15:20]  * apw wonders how it was not ok before and became ok this time
[15:20] <LocutusOfBorg> apw, I was wondering the same, maybe the second copy was done from proposed to proposed again, or from disco/* to disco-proposed
[15:20] <LocutusOfBorg> so powerpc wasn't there anymore
[15:26] <cjwatson> A powerpc build is a fair guess, yes
[15:26] <cjwatson> Not sure precisely, not going to trace now since it isn't a systemic problem with copies
[15:27] <LocutusOfBorg>  libmarc-charset-perl | 1.35-2 | xenial/universe  | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
[15:27] <LocutusOfBorg>  libmarc-charset-perl | 1.35-2 | disco/universe   | source, amd64, arm64, armhf, i386, ppc64el, s390x
[15:28] <infinity> Yeah, this is a known bug.  I don't remember the number.
[15:29] -queuebot:#ubuntu-release- New binary: poppler [s390x] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:29] <infinity> Copying forward from xenial works.  Copying back from disco-proposed to disco fails.
[15:29] <infinity> My second copy was from xenial to disco, bypassing that.
[15:29] -queuebot:#ubuntu-release- New binary: poppler [amd64] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:30] -queuebot:#ubuntu-release- New binary: poppler [i386] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:30] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:35] -queuebot:#ubuntu-release- New binary: poppler [arm64] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:38] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (cosmic-proposed/main) [1.5ubuntu<IP_ADDRESS> => 1.5ubuntu<IP_ADDRESS>] (desktop-core, ubuntu-server)
[15:47] -queuebot:#ubuntu-release- New binary: nvidia-cuda-toolkit [ppc64el] (disco-proposed/multiverse) [10.0.130-2] (no packageset)
[15:47] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (cosmic-proposed) [18.01-0ubuntu4.2]
[15:48] -queuebot:#ubuntu-release- New binary: poppler [armhf] (disco-proposed/main) [0.74.0-0ubuntu1] (desktop-core, ubuntu-server)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (bionic-proposed) [18.01-0ubuntu3.3]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [amd64] (disco-proposed) [0.74.0-0ubuntu1]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [armhf] (disco-proposed) [0.74.0-0ubuntu1]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [ppc64el] (disco-proposed) [0.74.0-0ubuntu1]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [arm64] (disco-proposed) [0.74.0-0ubuntu1]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [s390x] (disco-proposed) [0.74.0-0ubuntu1]
[15:50] -queuebot:#ubuntu-release- New: accepted poppler [i386] (disco-proposed) [0.74.0-0ubuntu1]
[15:51] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (xenial-proposed) [16.03-0ubuntu<IP_ADDRESS>]
[15:52] -queuebot:#ubuntu-release- New source: masakari (disco-proposed/primary) [7.0.0~b1-0ubuntu2]
[15:52] -queuebot:#ubuntu-release- New binary: nvidia-cuda-toolkit [amd64] (disco-proposed/multiverse) [10.0.130-2] (no packageset)
[15:58] -queuebot:#ubuntu-release- New: rejected masakari [source] (disco-proposed) [7.0.0~b1-0ubuntu2]
[15:59] -queuebot:#ubuntu-release- New: accepted masakari [source] (disco-proposed) [7.0.0~b1-0ubuntu2]
[16:02] -queuebot:#ubuntu-release- New: accepted nvidia-cuda-toolkit [amd64] (disco-proposed) [10.0.130-2]
[16:02] -queuebot:#ubuntu-release- New: accepted nvidia-cuda-toolkit [ppc64el] (disco-proposed) [10.0.130-2]
[16:02] -queuebot:#ubuntu-release- New binary: masakari [amd64] (disco-proposed/none) [7.0.0~b1-0ubuntu2] (no packageset)
[16:10] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (cosmic-proposed) [3:14.0.1-0ubuntu2]
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (cosmic-proposed) [1.5ubuntu<IP_ADDRESS>]
[16:32] -queuebot:#ubuntu-release- New: accepted masakari [amd64] (disco-proposed) [7.0.0~b1-0ubuntu2]
[16:40] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [1.1ubuntu<IP_ADDRESS>~16.04.1 => 1.1ubuntu<IP_ADDRESS>~16.04.2] (desktop-core, ubuntu-server)
[16:49] -queuebot:#ubuntu-release- Unapproved: libxcb (bionic-proposed/main) [1.13-1 => 1.13-2~ubuntu18.04] (core, xorg)
[16:55] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (bionic-proposed/main) [1.1ubuntu<IP_ADDRESS> => 1.1ubuntu<IP_ADDRESS>] (desktop-core, ubuntu-server)
[17:05] -queuebot:#ubuntu-release- Unapproved: lmdb (bionic-proposed/universe) [0.9.21-1 => 0.9.21-1ubuntu2~bionic18.04] (kubuntu)
[17:13] -queuebot:#ubuntu-release- New binary: golang-github-codahale-hdrhistogram [amd64] (disco-proposed/none) [0.0~git20161010.3a0bb77-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: golang-github-yudai-golcs [amd64] (disco-proposed/none) [0.0~git20170316.ecda9a5-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: golang-github-crossdock-crossdock-go [amd64] (disco-proposed/none) [0.0~git20160816.049aabb-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: golang-github-uber-go-atomic [amd64] (disco-proposed/universe) [1.3.2+git20181018.8dc6146-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (bionic-proposed) [1.1ubuntu<IP_ADDRESS>]
[18:57] -queuebot:#ubuntu-release- New binary: vala [s390x] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[18:58] -queuebot:#ubuntu-release- New binary: vala [amd64] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[19:00] -queuebot:#ubuntu-release- New binary: vala [i386] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[19:00] -queuebot:#ubuntu-release- New binary: vala [ppc64el] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[19:11] -queuebot:#ubuntu-release- New binary: vala [armhf] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[19:12] -queuebot:#ubuntu-release- New binary: vala [arm64] (disco-proposed/universe) [0.43.90-1] (ubuntu-desktop)
[21:08] <tsimonq2> infinity: So people upload to Cosmic to get things into Disco? :P
[21:08] <tsimonq2> (email)
[21:09] <infinity> tsimonq2: I'm the king of bad copy and paste (and an inability to proof read)
[21:09] <tsimonq2> :)
[21:11] <infinity> tsimonq2: Like, even after you pointed it out, and I was pretty sure you must be right, I had to re-read it three times to notice the word "cosmic" in there.
[21:16] <rbasak> It's OK. I'm not sure uploading to cosmic-roposed will work anyway :)
[21:17] <rbasak> My proof reading usually improves significantly only when doing it after sending/submitting.
[21:17] <tsimonq2> ¯\_(ツ)_/¯
[21:17] <tsimonq2> This is why I reread emails an obnoxious number of times before sending them. :P