[00:11] <lifeless> salgado-afk: I'm trying to reproduce now
[00:17]  * SamB wonders why poolie has to ASK jam if he can call him
[00:18] <jam> SamB: because it is 1.5 hours past the end of my work day
[00:18] <SamB> oh, right, work relationship ...
[00:19]  * SamB isn't used to many people in an IRC channel working for the same company
[00:19] <lifeless> more a work call
[00:19] <shikibu> I am trying to do bzr init; bzr add in a quite small directory tree, and bzr seems determined to ignore one of my directories (formassembly/). Any idea why? http://pastebin.com/d5c84f4f1
[00:19] <lifeless> many of us have relationships preceeding working at the same company, but if we're communicating about work respecting work/family balance is easy and important
[00:20] <shikibu> poolie: ?
[00:20] <shikibu> ^
[00:20] <SamB> oh, and not terribly used to people having lives ;-P
[00:21] <lifeless> shikibu: odd
[00:21] <lifeless> shikibu: what does 'bzr add formassembly' do ?
[00:21] <jam> lifeless: global ignores?
[00:22] <lifeless> shikibu: also, perhaps a global ignore as jam says
[00:22] <shikibu> lifeless: http://pastebin.com/d41406944
[00:23] <poolie> shikibu: hi; i'm on the phone to jam
[00:23] <lifeless> shikibu: cat ~/.bazaar/ignore
[00:24] <jam> lifeless: formassebly is a bzr branch
[00:24] <shikibu> not there
[00:24] <jam> shikibu: bzr status formassembly?
[00:24] <shikibu> http://pastebin.com/d515abbf0
[00:24] <lifeless> oh
[00:24] <lifeless> ls -a formassembly
[00:24] <jam> lifeless: that is my guess, at least
[00:24] <shikibu> lifeless: http://pastebin.com/d1c3ef6ca
[00:24] <lifeless> jam: I'm betting svn
[00:25] <shikibu> lifeless: http://pastebin.com/d7427da4a
[00:25] <jam> shikibu, lifeless: could be anything but "bzr status formassembly" makes it clear it is a separate project
[00:25] <jam> which is why we aren't adding it
[00:25] <lifeless> jam wins
[00:25] <jam> and I believe there is an open bug about it
[00:25] <shikibu> ah, I see. thank you@
[00:25] <lifeless> shikibu: you've bzr init'd the subdir formassembly already
[00:25] <shikibu> thank you!
[00:26] <shikibu> yes, i understand now
[00:27] <lifeless> jam: python 2.4 doesn't have SEEK_SET/SEEK_CUR, I'll just define them locally if thats ok
[00:27] <lifeless> jam: but I'll call them SUBUNIT_SET/SUBUNIT_CUR
[00:31] <jam> lifeless: or COUNT_SET/COUNT_CUR, but sure
[00:42] <poolie> lifeless: do they really have to be variables pointing to ints?
[00:55] <lifeless> poolie: well, its an enum
[01:09]  * spiv yawns
[01:22] <poolie> lifeless: that mp was pretty damn timely :)
[01:22] <poolie> it's the secret of good comedy you know :)
[01:26] <lifeless> :)
[01:37] <lifeless> spiv: ping
[01:49] <lifeless> salgado-afk: still up?
[01:52] <salgado-afk> lifeless, yes, but not for very long
[01:52] <lifeless> have you tried with bzr 1.17 or 1.16 ?
[01:52] <lifeless> do they also fail?
[01:53] <salgado-afk> just bzr 1.17
[01:53] <lifeless> and did it fail too?
[01:54] <salgado-afk> I don't quite understand your question, but locally I can't reproduce the error, either with 1.17 or 1.18dev
[01:54] <lifeless> I meanm have you tried to branch from lp with 1.17
[01:55] <salgado-afk> not sure; let me try again
[01:55] <salgado-afk> abentley did that, IIRC
[01:56] <salgado-afk> AttributeError: 'AbsentContentFactory' object has no attribute 'get_bytes_as'
[01:56] <salgado-afk> that's what I get when branching from lp using 1.17
[01:56] <lifeless> ok
[01:56] <lifeless> does the backtrace look the same otherwise?
[01:58] <salgado-afk> I think so, let me paste it
[01:58] <salgado-afk> https://pastebin.canonical.com/20572/
[01:59] <salgado-afk> lifeless, as I mentioned earlier, my temp branch on that project looks weird.  that was the first thing I pushed on that project, and it is a launchpad branch, IIRC
[01:59] <salgado-afk> I pushed it from the DC so that I'd have something to stack on
[01:59] <lifeless> its the same in 1.17
[02:00] <lifeless> which is good
[02:00] <lifeless> thanks
[02:00] <lifeless> I hope to have something for you overnight
[02:00] <salgado-afk> lifeless, great, just let me know if there's anything else I can help with
[02:00] <spiv> salgado-afk: just checking, local and remote are both 2a in this case?
[02:00] <lifeless> don't fix it :)
[02:00] <lifeless> spiv: yes
[02:00] <spiv> Ok, good.
[02:01] <lifeless> I haven't checked if trunk's format is 2a
[02:01] <spiv> lifeless: (bzr.dev currently fails to push between CHK repos with different serializers)
[02:01] <lifeless> but it stacks ok, so I assume it is :P
[02:01] <spiv> (at least in the presence of stacking)
[02:47] <lifeless> spiv: https://bugs.edge.launchpad.net/bzr/+bug/406686
[02:47] <lifeless> and
[02:47] <lifeless> https://bugs.edge.launchpad.net/bzr/+bug/406687
[02:48] <lifeless> spiv: mayI call?
[02:49] <spiv> lifeless: sure
[03:24] <lifeless> spiv: nosmart+lp:~salgado/canonical-identity-provider/test4
[04:04] <poolie> biab
[06:25] <spiv> lifeless: curiously, your merge proposals (and only yours) display in mutt with ^M at the end of every line of the attachment.
[06:26] <lifeless> \o/ evo
[06:26] <lifeless> its probably being correct
[06:40] <fullermd> spiv: ping
[06:40] <spiv> fullermd: pong
[06:40] <fullermd> spiv: Did you ever find anything on bug 389413?
[06:40] <fullermd> I just had a coworker hit what looks like it with merge.
[06:40] <spiv> fullermd: it's probably quite shallow, but I just haven't got it it.
[06:41] <spiv> Presumably a lock isn't being held long enough.
[06:41] <fullermd> 'k
[06:42] <spiv> fullermd: if the traceback isn't obviously the same, feel free to add it to the bug, though.
[07:17] <AfC> Is there a diffstat equivalent in Bazaar land?
[07:18] <mwhudson> AfC: we still have diffstat ?
[07:18] <lifeless> there is a diffstat plugin
[07:18] <AfC> I'm not even sure if it means anything, but it seems the closest I've come across to an abstract quantification of the size of a delta
[07:18] <lifeless> also bzr diff | diffstat :P
[07:18] <AfC> lifeless: oh, it's a command? Sorry didn't know that.
[07:18]  * AfC goes a hunting
[07:19] <AfC> lifeless: so, what would a bzr diffstat plugin be doing that bzr diff | diffstat doesn't? Is that plugin something I should go find?
[07:21] <lifeless> AfC: its easier for folk on windows
[07:21] <AfC> {snort}
[07:21] <AfC> ah
[07:22] <AfC> right
[07:25] <lifeless> it can also do things like hook into the commit template, I suppose
[09:45] <ronny> does bzr have something like keywords that get expaneded to the current data
[09:45] <fullermd> Sorta kinda.
[09:46] <fullermd> Alternately, "Yes, with a plugin, but they mostly don't work, and where they do, they're inconvenient to enable."
[09:48] <ronny> hmk, i'll just add some calls to the bzr version info thing then
[10:04] <ronny> hmm, works fine
[10:32] <ronny> whats the propper way to merge, if a file got created independ in 2 branches
[10:32] <ronny> (it created a .bzrignore.moved file)
[10:34] <bialix> merge old a new file by hands, select wich file history to stay, delete other file and resoove conflict
[10:38] <ronny> ok
[10:48] <sender> anyone an idea of a way to integrated bzr and mantis bugtracker? that bugtracker tab under settings, looks quite promising :)
[10:49] <bialix> it depends on what you mean by "integrate"
[10:50] <sender> bialix: tx, assign a bugnumber to a commit for example
[10:50] <bialix> ah, this should be very easy
[10:51] <bialix> can you show the typical URL to your bugs?
[10:52] <sender> something from the mantis website itself, this is the url to view a certain bug: http://www.mantisbt.org/bugs/view.php?id=7721
[10:52] <sender> bugnumber: 0007721
[10:53] <bialix> so you can assign
[10:54] <bialix> bugtracker_mantis_url = http://www.mantisbt.org/bugs/view.php?id={id}
[10:54] <bialix> and then use
[10:54] <bialix> bzr ci --fixes mantis:7721
[10:55] <sender> great!
[10:55] <bialix> qlog can show you bugs assigned to revisions
[10:56] <bialix> hmm, it seems qlog does not support mantis yet
[10:56] <bialix> I'll add such support
[10:56] <sender> wow that's great
[10:57] <sender> the abbreviation is configurable? "mantis:" could be "bug:" or "m:"?
[10:58] <bialix> it should be the same you put in bugtracker_???_url name
[11:00] <sender> nice. bzr, plugins and support keeps amazing me =)
[11:13] <lifeless> jelmer: I'm doing a talk on subunit at slug tomorrow, ok to mention samba as a user?
[11:19] <sender> bialix: after commit --fixes, I don't see any info on this show up in bzr log, is this correct? bzr qlog crashes (probably the same error that you saw - I guess I don't need to report it?)
[11:19] <bialix> plain log does not show this info, yes
[11:20] <bialix> try to update qbzr from trunk branch
[11:20] <sender> Is there an other way to see that the bugfix is attached to the commit?
[11:20] <sender> ok
[11:20] <bialix> can you pastbin qlog error anyway?
[11:21] <sender> http://pastebin.com/m57605735
[11:23] <jelmer> lifeless: Hi
[11:23] <bialix> sender: no it's different error maybe
[11:23] <jelmer> lifeless: Yes, of course :-)
[11:23] <bialix> sender: try to update your qbzr from trunk and say me if my change helps
[11:24] <bialix> sender: but it smells like new bug
[11:24] <bialix> sender: will be nice to file it as bug report
[11:25] <lifeless> jelmer: whats the name of your C test library?
[11:25] <jelmer> lifeless: libtorture
[11:25] <sender> bialix: qlog from trunk looks perfect
[11:25] <jelmer> lifeless, it's not really usable standalone though, and quite specific to samba at the moment
[11:25] <lifeless> yeah, I know
[11:25] <bialix> sender: file a bug please, mention that qlog crashes when bug_url is unknown
[11:26] <sender> no errormessage and a nice red bar to show bug id, great =)
[11:26] <sender> ok i will, can i retrigger? just remove bugtracker setting?
[11:28] <bialix> no, you have to comment line 59 in qbzr/lib/logmodel.py
[11:29] <bialix> this one: r'|bugs/view.php\?id='      # Mantis bug tracker URL
[11:33] <sender> bialix: if I remove the mantis url from settings, the new qlog still works. commit --fixes refuses. Seems like "qlog crashes when bug_url is unknown" is not the actual bug?
[11:34] <bialix> no
[11:34] <bialix> sender: you have to comment line 59 in qbzr/lib/logmodel.py
[11:34] <bialix> this one: r'|bugs/view.php\?id=' # Mantis bug tracker URL
[11:34] <bialix> qlog does not use bugtracker_XXX_url settings at all
[11:35] <bialix> qlog using internal regexp to parse final bug url
[11:35] <bialix> this is what I mean by bug_url is unknown
[11:35] <bialix> unknown to qlog regexp
[11:36] <bialix> sender ?
[11:36] <sender> yes bialix
[11:36] <bialix> sender: can you test with commented regexp?
[11:36] <sender> yes, def, jst a sec
[11:36] <bialix> ok
[11:37] <sender> bialix: no crash, just no "bug tag"
[11:37] <bialix> hm
[11:38] <bialix> oh
[11:38] <bialix> I know
[11:38] <bialix> recently Gary fixed bug around this feature
[11:38] <fullermd> Darn those people sneakily fixing bugs!
[11:38] <sender> :)
[11:39] <bialix> fullermd: it was actually different bug!
[11:39] <fullermd> If you fix a bug accidentally while fixing another bug, is the bug fix a bug?
[11:40] <sender> ghehe
[11:42] <bialix> err, no
[11:42] <bialix> Gary fixed bug with not very clear symptoms, and in fact he has fixed 2 bugs
[11:42] <fullermd> I think it is.  Luckily, it's easy to fix; you just say "Oh, yeah, I meant to do that".
[11:43] <bialix> or maybe this new bug symptom makes those symptomps more clear
[11:43] <bialix> anyway!
[11:43] <bialix> ta-da!
[11:43] <bialix> and everything worked!
[11:43] <bialix> :-0
[11:47] <sender> great, btw I installed mantis on localhost, and the url for bugs is: http://localhost/view.php?id=1 so without '/bugs/', it seems that mantisbt.org is the exception
[11:54] <konnertz> hi. Pls how to find out the central repository of a checkout?
[11:55] <sender> konnertz: try bzr info
[11:55] <sender> bialix: should: "http://bazaar-vcs.org/3rdPartyTools#Integrated Bug Trackers" be updated with LP, Bugzilla, Redmine, Sharepoint, Fogbugz, Roundup and Mantis?
[11:56] <konnertz> ok sender thx
[12:00] <sender> bialix: I see I can edit the page, can I add those?
[12:07]  * bialix back
[12:07] <bialix> sender: um?
[12:08] <bialix> sender: about localhost: ok, so my regexp is wrong
[12:08] <sender> bialix: but still i got the bug tag in qlog
[12:09] <bialix> sender: about 3rdPartyTools: I don't think qlog support does count there
[12:10] <bialix> sender: I don't understand you, it won't work once you setup different url
[12:11] <sender> bialix: ok will test again
[12:12] <bialix> sender: on commit bzr store exact URL as part of revision metadata
[12:12] <bialix> you can see it in qlog revision details window (bottom left)
[12:16] <sender> ok without the correct regexp I don't see the red tags, but the urls are in (revision details window)
[12:16] <sender> changing the regexp to r'|view.php\?id=' makes those visible
[12:17] <sender> btw it's possible to commit with --fixes mantis:2 eventhough bug nr 2 doesn't exist. is this intended?
[12:17] <fullermd> --fixes doesn't _do_ anything with the bug tracker.  It just saves a URL along with the rev for reference.
[12:19] <sender> fullermd: understood, I guess thatdistributed means
[12:19] <sender> being able to work without connection to the bugtracker (sorry for the newline)
[12:19] <fullermd> Well, not just that...  who knows how $RANDOM_BUGTRACKER works.  How could bzr _tell_ whether the bug existed?
[12:20] <fullermd> (first, you embed an HTML parser...   then an AI engine...)
[12:21] <sender> fullermd: check for 200OK?
[12:21] <sender> fullermd: AI enigine would be nice anyway ;)
[12:21] <fullermd> That wouldn't help.  The bug tracker will return a "WTF?  I don't know what that bug is" page, but it's still a HTML page that's HTTP 200 OK
[12:23] <sender> fullermd: ok that should be part of the bugtracker specific settings then, but def. nasty to implement
[12:25] <fullermd> Yeah.  VERY nasty to implement, exponentially so to maintain.  And what if it needs authentication?  Session state?  etc.  It's an endless garden path.
[12:27] <sender> :) btw would it in a way be possible to show the diff(s) along with the bug in mantis?
[12:28] <fullermd> That would be going the other way; teaching mantis about bzr.
[12:29] <sender> yeah, too bad bzr log doesn't seem to support bugnumbers, or am I missing something?
[12:30] <bialix> you can have more than one revisions with the same bug url
[12:30] <sender> bialix: is there a way to enlist them with log?
[12:31] <bialix> I don't know. fullermd, you know almost everything, what you say?
[12:33] <fullermd> I'm not aware of one offhand.
[12:33] <fullermd> I never use --fixes though, so I'm not much of an authority on it.
[12:34] <bialix> right. I've started to use --fixes heavily after I've started to use QBzr
[12:35] <bialix> QBzr has full support: in qcommit you can easily provide bug url, and then see it in qlog
[12:35] <bialix> IIRC this bug url feature was introduced in bzr core to use with lp as primary target
[12:36] <fullermd> In a quick look around, the only place I see it showing up through the CLI is the long-form testament.
[12:36] <fullermd> It's probably just gotten at the API level anywhere that actually uses it currently.
[12:37] <fullermd> So, as soon as someone reimplements bzrlib in a sensible language like perl...   O:-}
[12:38] <bialix> lol
[13:07] <salgado> lifeless, how can I test your fix for that bug we were debugging yesterday?
[15:39] <dvheumen> Hi, does anyone know which sentence is (more) correct? "warning: \'--allow-writes\' enables unauthenticated ' \
[15:39] <dvheumen>                 'write access to anyone with network access to the server.
[15:39] <dvheumen> woops, sorry
[15:40] <dvheumen> ... enables unauthenticated writes access {to,for} anyone with network access to the server ... (Which is better, 'to' or 'for'?)
[15:41] <bob2> by
[15:42] <dvheumen> bob2: by?
[15:46] <bob2> enables unauthenticated write access by anyone with network access
[15:56] <theAdib> hello all,I am working on a project where I have to program on a win32/linux/mac box. I tried bazaar on my web server using ftp. Bazaar fails updating: FTP temporary error: 451 /repository.bzr/TDD/.bzr/repository/upload/eexq0mvoqcyo
[15:56] <theAdib> zaxulmqz.pack: Append/Restart not permitted, try again. Retrying.
[15:56] <theAdib> and then aborts after 3 failures. I can not change the settings in the ftp server (is part of the webhoster)
[15:57] <theAdib> Do you have a suggestion how to work using bazaar? (My win32 and linux is on one computer)
[15:58] <bob2> they don't provide ssh access?
[16:00] <theAdib> bob2, no, they don't
[16:10] <SamB> theAdib: break out your *old* computer
[16:10] <SamB> use it as an SSH server
[16:12] <theAdib> any way to use the ftp server as a collector for patch-sets and merge them back in an intelligent way?
[16:21] <theAdib> is it possible to put the bzr-repository on an usb stick? And then move this from computer to computer?
[16:25] <bob2> sure
[16:54] <sigmonsays> Does anyone know what bzr: ERROR: Unknown repository format: 'Bazaar RepositoryFormatKintPack6 (bzr 1.9)\n' can be avoided?
[16:54] <sigmonsays> s/what/how/
[16:55]  * sigmonsays mumbles, back in his day you used to cvs checkout without a login.   I still can't 'bzr diff -r parent:' even though 'bzr diff -r submit:' works fine.
[17:12] <Tak> although it would be nice if lp allowed one to grab a tarball of a particular revision
[17:15] <jelmer> Tak: bzr export -r<revision> lp:bzr foo.tar.gz
[17:15] <jelmer> with the last two arguments swapped, sorry
[17:16] <Tak> yeah, but I mean from the web ui
[17:16] <jelmer> ah, right
[17:16] <jelmer> I think there was some work happening in loggerhead to support that
[17:16] <jelmer> Not sure if it's landed yet though, and/or if it is enabled on launchpad
[17:18] <Tak> I can't find it anywhere on launchpad, although it could just be some place I haven't thought to look
[18:31]  * kfogel is away: kfogel-food
[18:36] <askogrand> This might seem like a silly question, but with bazaar can someone check out a single file?
[18:36] <askogrand> as opposed to a folder.
[18:40] <bob2> no
[18:48] <askogrand> is there any version control system that will?
[18:48] <bob2> svn
[18:52] <captainc> Alright, I downloaded the bzr windows installation package and its giving me errors about plugins that are supposed to be in my local python site-packages directory. should i uninstall and reinstall in a different way?
[18:56] <Raim> bob2: svn does not support checkout of single files, only unversioned 'svn cat $URL'
[20:22] <captainc> How do I fix or work around this win32 symlinks issue?
[20:23] <captainc> without cygwin
[20:30] <phinze> hi folks, can someone point me in the direction of (or just give your own offhand) definition for "upstream" and "downstream" in the VCS domain?
[20:30] <phinze> is upstream towards trunk and downstream towards the most remote fork?
[20:30] <phinze> or the other way around?
[20:32] <phinze> actually, just found this, which helped: http://strategiesforsustainability.blogspot.com/2005/10/upstream-vs-downstream.html
[20:32] <Linkadmin> is there a way to configure a plugin against a branch instead of in ~/.bazaar/ ? I'd like to set up the bzr-email plugin to send an email to the dev mailing list on update without making all users install/configure the plugin in their homedirs...
[20:34] <phinze> Linkadmin: you can install the plugin systemwide on your central server and then configure that branch to send emails; let me see if i can find a link that describes that
[20:34] <Linkadmin> i've installed it system-wide already. Wasn't able to find docs on binding a plugin to a branch. That would be *much* appreciated
[20:35] <phinze> ah ok
[20:38] <phinze> so bzr help email is telling you to set post_commit_to and post_commit_sender ... i'm not completely sure but i think you should be able to set those in .bazaar/branch/branch.conf
[20:38] <phinze> s/.bazaar/.bzr/
[20:40] <Linkadmin> tried that on my local branch then bzr commit resulted in a pointlessCommit. I'll try on the central branch instead
[20:40] <phinze> hah, that's a sassy error
[20:41] <Linkadmin> lol yes
[20:42] <phinze> Linkadmin: the other thing to look into would be https://launchpad.net/bzr-hookless-email
[20:42] <phinze> i used that to some success for awhile
[20:42] <phinze> it's nice because it doesn't have to be tied to a particular branch
[20:43] <Linkadmin> it appears the branch.conf change in the central branch on the server worked  :D
[20:43] <Linkadmin> i'll bookmark the other one too, thanks a ton!~
[20:44] <phinze> awesome; good to hear -- i was always wondering whether bzr-email could worth that way :)
[20:45] <Linkadmin> yeah i was really worried that it wouldn't hehe.
[21:24] <lifeless> moin
[22:06] <flvr8> hey, what's the proper thing to do with uncommitted trunk changes before doing a bzr switch to a branch? committing them locally fails (switch complains). we have a central repo, so there'd be nowhere to push them otherwise
[22:07] <lifeless> flvr8: do you want them committed to trunk?
[22:08] <flvr8> nope. (actually i'm asking on behalf of one of the guys in my team). typically the situation is he's working on a feature that'll end up in trunk, but he's not ready to commit. and some fire comes up on production that requires a change to the branch
[22:08] <lifeless> bzr shelve --all
[22:08] <lifeless> when hes done, bzr unshelve
[22:09] <flvr8> excellent. thanks
[22:33] <lifeless> moin jam
[22:33] <abentley> lifeless: bzr-pipeline has that built in-- every branch has a shelf, and switching shelves and unshelves changes.  It works pretty nicely, and I'd like to have it in core.
[22:34] <lifeless> abentley: Something I have with looms that I don't with regular branches is shelve-in-one-place, unshelve-in-another
[22:34] <jam> morning lifeless
[22:34] <jam> evening abentley
[22:35] <abentley> jam: evening.
[22:35] <lifeless> abentley: I really like that; its for moving changes across branches (similar to switch merging)
[22:36] <lifeless> abentley: I think both cases are useful; I agree that having a solid answer to 'stop working on this bit now, but its not ready to commit' is needed, I'd also like to have an easier story for 'move this bit elsewhere' - which is currently 'switch elsewhere' for me
[22:36] <lifeless> abentley: if we can satisfy both use cases in core I'll be ecstatic, and change loom to match the idiom
[22:37] <abentley> lifeless: We already have merge --uncommitted and switch for the second case.  Why don't they satisfy?
[22:38] <lifeless> abentley: merge --uncommitted isn't as interactive as shelve; it doesn't satisfy the 'get one hunk case'. I currently do that by 'shelve; select all but the bit I want to move elsewhere', then either switch or merge --uncommitted
[22:38] <lifeless> then an unshelve
[22:38] <abentley> lifeless: merge --uncommitted -i is exactly as interactive as shelve.
[22:39] <lifeless> oh thats landed. Nice one1
[22:39] <lifeless> s/1/!
[22:40] <lifeless> so, in pipeline, how do you move an uncommitted change to the pipe before/after ?
[22:40] <abentley> lifeless: Yep.  I was also thinking about supporting merge --shelf.
[22:41] <abentley> lifeless: I move changes with standard switch, or with merge --uncommitted PIPE.
[22:41] <lifeless> abentley: salgado's bug yesterday, was it affecting the lp puller/scanner/review stuff?
[22:41] <lifeless> abentley: I thought you said that switching shelves first ?
[22:42] <abentley> lifeless: I was simplifying.  "switch-pipe" shelves first.
[22:42] <lifeless> jam: as you'll have finished work when I get these tweaks done, is there more after them? and do you want a re-review, or can I just grab a local tz-er for an incremental ok?
[22:43] <lifeless> abentley: ah, ok.
[22:43] <abentley> lifeless: I would expect salgado's bug to affect the puller, but I don't actually know.
[22:43] <lifeless> abentley: ok. His bug is a bug in the remote streaming code, the branch itself is intact
[22:43] <jam> lifeless: pretty sure an incremental is fine
[22:43] <lifeless> if the puller is using file: or http: urls it won't be affected
[22:43] <lifeless> jam: thanks
[22:43] <jam> I don't remember any major review that was needed
[22:44] <abentley> lifeless: Those pulls use http IIRC, so we might be okay.
[22:44] <lifeless> cool
[22:44] <lifeless> I won't make a lp task for the bug at this point then
[22:45] <abentley> hmm, no, the scanner uses http.  I bet the puller uses file:  mwhudson?
[22:45] <lifeless> so, you'd like to add per-branch shelves to core?
[22:45] <abentley> lifeless: Yes.
[22:45] <lifeless> along-with or replacing per-tree shelves?
[22:46] <lifeless> It seems like along-with will add some complexity to the ui and how to explain/work with shelves
[22:46] <abentley> lifeless: along-with, I think.  I tried to replace shelf with bzr-pipeline, but it wasn't really nice.
[22:47] <lifeless> by replace with bzr-pipeline, you mean something like doing a commit on switch-pipe (from), and an uncommit on switch-pipe (to) ?
[22:48] <abentley> lifeless: I was trying to unify shelves and (threads|pipes) into a single concept, but it didn't really work out.
[22:48] <lifeless> ah interesting
[22:49] <lifeless> so I was thinking during this conversation that for a branch, just doing a commit on the tip is ~= shelve
[22:49] <abentley> lifeless: You can do "add-pipe -i --no-switch" to get an effect similar to "shelve"
[22:49] <lifeless> when the use case is that you're getting rid of the attached tree (due to switch), and implicitly popping it off when the user returns to the branch
[22:50] <lifeless> but thats likely going to surprise users that attach to the branch with a checkout, so its probably just a completely crack idea
[22:52] <mwhudson> abentley: yes
[22:53] <mwhudson> (well, it used lp-hosted/lp-mirrored, which backs onto a local transport)
[22:53] <lifeless> abentley: so, +1 on some way to stash changes for a branch when there is no tree; I think users wanting to bzr switch will appreciate this a lot
[22:53] <abentley> lifeless: I think you *could* do it as a commit, as long as you record the head somewhere other than last_revision.  Though you lose some of the potential for recording missing files, etc. that shelves have.
[22:53] <lifeless> abentley: I'm not sure about the mechanism of shelf-per-branch, rather than (say) shelves-named-by-branches-in-the-tree
[22:54] <lifeless> abentley: what do shelves do for missing files?
[22:55] <lifeless> abentley: my concern about the mechanism is just ui complication/confusion. It would be good to get a few possible mechanisms under evaluation (something it sounds like you've been doing already) and do set based design on them
[22:55] <abentley> lifeless: Being based on PreviewTree, shelves can represent basically any working tree state.  So if you added a file-id but not a file, you could shelve that.
[22:56] <abentley> lifeless: But I said "potential", because most of our code, like merge, ignores unversioned files.
[22:56] <lifeless> abentley: that makes me start speculating about having a kind of 'missing' in inventories ;)
[22:58] <abentley> lifeless: The shelf on pipes only has space for a single set of changes, and it seems to work out alright.  Maybe I should see about making shelve/unshelve actually use pipes.
[23:00] <abentley> lifeless: That would give us a single concept, but retain the specific shelve/unshelve UI.
[23:01] <lifeless> so, in a non-pipeline, shelve would be as it is, in a pipeline it would add pipes ?
[23:06] <lifeless> abentley: I think there are two broad questions: does shelve need a supercapability over commit? If yes, then we have to use shelve storage. If no we can look at temporary commits.
[23:07] <lifeless> Secondly, what places do we need to be able to shelve things *to* - both for users comfort and tools like pipe/loom/bzr-explorer
[23:19] <abentley> lifeless: sorry, on phone.
[23:20] <lifeless> abentley: no worries, just finishing overnight mail+reviews anyhow


[03:42] <MrcMkS> hi, which hardware do you use for your mirror servers in terms of storage space? thanks
[03:43] <MrcMkS> i mean, the last reference for space needed is from 2021 is 1.5 TB required


[10:38] <blueyed> Where can I find documentation about quilt best practises (patch format/name) for Ubuntu/Debian?
[12:29] <rbasak> blueyed: have you seen https://wiki.debian.org/UsingQuilt?
[12:30] <rbasak> That has some configuration options for formatting which work well (eg. not introducing noise when refreshing if everyone also does the same)
[12:30] <rbasak> I've never seen any real convention about naming. In Ubuntu, I try to follow the pattern set by the Debian maintainer for a package, and if not then just use plain names. I don't see the point in an extension when it can be inferred by the directory it's in.


[09:15] <alan_g> duflu_: did you resolve "The bad news is I can now see stutters..."?
[09:16] <duflu_> alan_g: Nope, but also sufficiently rare that it's not worth blocking on. Only happens (sometimes) when a surface crosses multiple display buffers or transitions to/from bypass
[09:16] <duflu_> Getting better phone performance is more important
[09:16] <duflu_> We can dynamically add triple back in according to demand later
[09:17]  * alan_g wonders if we need to track the issue with a bug (or something)
[09:18] <duflu_> alan_g: After it lands, I'll retest and declare a minor regression
[09:18] <alan_g> OK
[12:28] <anpok> hm why is default_delete a template
[16:31] <alan_g> camako: I'll update this to 31 then? https://code.launchpad.net/~alan-griffiths/mir/libmirserver-ABI-bump/+merge/250602
[16:44] <camako> alan_g, sounds good
[16:44] <camako> AlbertA ^
[16:46] <alan_g> Dne
[16:46] <alan_g> *done


[02:21] <barna> Please help on the channel #ubuntu-br
[02:22] <barna> our bot is not online, channel # ubuntu-ops that is empty.
[02:22] <barna> tranks again IdleOne !
[09:28] <ikonia> @mark #ubuntu mcloy despite being unbanned for cross-posting yesterday posted the same question in #ubuntu #kubuntu #ubuntu-server
[09:30] <mcloy> i am new to irc. i thought my text is not visible in #ubuntu and i asked that to users too. "is my text visible?"  i got no reply and i posted same question in #kubuntu. got no reply. i am banned . any help?
[09:31] <ikonia> if you are new to irc, your account is 1 year old,
[09:31] <ikonia> that seems odd to me
[09:31] <ikonia> mcloy: I explained to you in detail to stop cross-posting, you ignore it and got banned, I explained in more detail, you ingnored it, I explained it again, you ignored it and got banned
[09:31] <ikonia> you then kicked up a fuss that it was personal, so others explained to you that cross-posting wasn't helpful and to stop
[09:31] <ikonia> you got unbanned
[09:32] <ikonia> you then cross-posted again
[09:32] <mcloy> my brothers
[09:32] <ikonia> it seems you don't seem to understand "don't do this"
[09:33] <mcloy> i am new to irc. i thought my text is not visible in #ubuntu and i asked that to users too. "is my text visible?"
[09:33] <ikonia> you are not new to irc
[09:33] <ikonia> you have held the account for over a year
[09:33] <ikonia> you know how to kick up a fuss, pm people, evade bans,
[09:34] <ikonia> you should be able to understand simple instructions "don't cross-post"
[09:34] <mcloy> its my brothers. its mine now
[09:35] <ikonia> I don't know what that means, I'm sorry
[09:35] <ikonia> I'm also a little concerned that you seemed to do the cross-post 30 seconds after I removed myself from being "/away"
[09:35] <ikonia> although I may be reading more into that than I should. I admit
[09:35] <mcloy>  i thought my text is not visible in #ubuntu and i asked that to users too. "is my text visible?"
[09:36] <ikonia> I'm sorry, I don't accept that
[09:36] <ikonia> you know what you are doing,
[09:36] <ikonia> and you where told if you have any queries/issues ask in this channel, do not cross-post
[09:36] <mcloy> you are not sorry. you are getting it personally.
[09:36] <mcloy> stay away from me.
[09:36] <ikonia> at this point, I'll leave it to one of the other operators to deal with you.
[09:37] <ikonia> if none of the other operators are free at this time, I suggest you try later
[09:37] <ikonia> but please don't start pm'ing people again, I'm sure someone will be free at some shortly.
[09:38] <mcloy> i told you i thought my text was not going in the channel. thats why i did it.    YOU JUST NEEDED A REASON TO BAN ME.
[09:39] <bazhang> mcloy, lets lose the caps
[09:40] <mcloy> bazhang,  what now...
[09:40] <bazhang> mcloy, discuss with me
[09:40] <bazhang> not via PM please
[09:41] <bazhang> mcloy, I have a few minutes to discuss this, if you wish.
[09:41] <mcloy> you can see what i typed above . thats the truth. what else i can say...
[09:42] <bazhang> mcloy, you wish to use those few minutes productively, yes?
[09:42] <mcloy> it would be odd to repeat.  i am new to irc. i thought my text is not visible in #ubuntu and i asked that to users too. "is my text visible?"  i got no reply and i posted same question in #kubuntu. got no reply. i am banned . she just needed a reason to ban me. thats all
[09:42] <bazhang> mcloy, if not, come back at some other time in the future.
[09:42] <mcloy> bazhang,  hm
[09:43] <bazhang> ok mcloy then come back at some other time if you just wish to follow the above.
[09:43] <mcloy> bazhang,  i didnt got any warning or kick before a ban. i asked people "is my text visible"
[09:43] <bazhang> askubuntu.com is a good alternative mcloy
[09:43] <mcloy> bazhang,  i didnt understood. what is required?
[09:44] <bazhang> mcloy, its a website
[09:44] <bazhang> www.askubuntu.com
[09:44] <mcloy> can i be unbaned now?
[09:44] <bazhang> mcloy, NO
[09:46] <mcloy> you think i did that intentionaly. and its not a mistake and ikonia  was not trying to find the a reason to ban me?
[09:46] <bazhang> !crosspost | mcloy
[09:47] <ikonia> mcloy: how about I remove the ban from #ubuntu but leave the ban in place in #kubuntu and #ubuntu-server
[09:47] <ikonia> that will activly stop you from cross-posting the same questions in multiple channels ?
[09:47] <mcloy> bazhang, ^
[09:47] <bazhang> mcloy, not going to repeat all the guidelines chat as we did that yesterday. you were originally banned for the same behavior
[09:48] <mcloy> bazhang,  ofcourse. it was  a mistake.
[09:48] <ikonia> mcloy: if I remove the ban in #ubuntu you can get support from the primary channel, and thus stop you cross-posting in #kubuntu and #ubuntu-server any more ?
[09:48] <ikonia> would that be an acceptable way to allow you to use the channel ?
[09:48] <mcloy> i didnt knew the outcome. can you unban me bazhang ?
[09:49]  * mcloy waits for bazhang  voice too
[09:49] <ikonia> mcloy: I've given you a suggestion to get you unbanned from #ubuntu would that work for you ?
[09:49]  * mcloy nods
[09:51] <mcloy> ..?
[09:52] <bazhang> mcloy, I won't unban you at this time. if someone else sees fit to do so, that's their call.
[09:52] <bazhang> and I have to run now.
[09:52] <mcloy> because you think i did that intentionaly. and its not a mistake and ikonia  was not trying to find the a reason to ban me?
[09:54]  * mcloy waits
[09:54] <ikonia> !idle mcloy
[09:55] <ikonia> !idle | mcloy
[09:55]  * mcloy is waiting for his matter
[10:17] <Tm_T> aww
[10:18] <Tm_T> discussed in pm
[10:37] <Tm_T> @mark #ubuntu mcloy keep blaming ikonia, lies about details and tries to talk away from the blame
[11:28] <mcloy> anyone around?
[11:28] <bazhang> yes
[11:28] <mcloy> any second thoughts?
[11:28] <bazhang> about?
[11:28] <mcloy> the ban
[11:29] <bazhang> no
[11:29] <mcloy> plan to?
[11:29] <Tm_T> mcloy: I said, it wont change anytime soon
[11:29] <Tm_T> if you keep failing to listen, it will just move further
[11:30] <mcloy> soon is = ?
[11:30] <Tm_T> several weeks
[11:30] <mcloy> is there a ban time policy for ubuntu?
[11:30] <Tm_T> that bans are infinite until they're resolved
[11:31] <Tm_T> or whatever happens
[11:31] <mcloy> no time policy?
[11:31] <Tm_T> no
[11:31] <mcloy> how can i resolve my ban then?
[11:31] <Tm_T> by following instructions I have given to you
[11:31] <Tm_T> hint: I didn't instruct you to come here at the same day asking about it
[11:32] <mcloy> you gave me many instruction in the last hours. which relates to resolving the ban specificaly?
[11:32] <Tm_T> basicly all of them
[11:32] <Tm_T> in your case, that is
[11:32] <mcloy> can i request you to be concise?
[11:33] <mcloy> and specific
[11:33] <Tm_T> show that you can follow our rules in channels you are not banned for some time, multiple weeks
[11:34] <Tm_T> and perhaps after that we can return discussing to your unbanning
[11:34] <mcloy> i do not have busines in other channels. so i cannot spend time there.
[11:34] <Tm_T> also, you need to show that you take responsibility of your actions and you stop lying or twisting facts
[11:35] <mcloy> i do take responsibility for my acts, and if theres a conflict of lying. you can point it
[11:35] <Tm_T> either way, I cannot trust currently you can use our channels without breaking rules and causing unneeded diturbance, thus I am not going to let you in anytime soon
[11:35] <Tm_T> mcloy: I already did in our conversation in private, did I?
[11:35] <mcloy> as i told , i do not have busines in other channels. so i cannot spend time there.
[11:36] <mcloy> prooving my behaviour
[11:36] <mcloy> how else to resolve
[11:37] <Tm_T> then give us time, multiple weeks, and perhaps if you are honest and show that you understand things then you might be able to back in
[11:37] <Tm_T> that is, after multiple weeks
[11:37] <Tm_T> currently I don't see any other option
[11:37] <Tm_T> use other support channels in the meantime, like our forums, askubuntu etc
[11:37] <mcloy> good idea, but only thing i didnt grasped is what will change in those weeks?
[11:38] <mcloy> how will you know iam honest
[11:38] <Tm_T> by showing that you can listen instructions to stay away for multiple weeks for starters
[11:38] <mcloy> how can i not stay away , as i will be baned for those weeks.........
[11:38] <Tm_T> perhaps I cannot, I think it's my headache, not yours at this point
[11:38] <elky> He means from this channel.
[11:39] <Tm_T> ^
[11:39] <mcloy> this and ubuntu and kubuntu and ubuntu-server
[11:39] <mcloy> elky,
[11:40] <mcloy> how would you jugde me when iam not around. i didnt got the intellegence behind it.     (iam asking to improve and as its concerning me directly.)
[11:41] <Tm_T> mcloy: first thing you need to improve is to stay away from here as requested
[11:41] <Tm_T> if you cannot follow such a simple request, that's enough
[11:42] <mcloy> sure.
[11:42] <mcloy> but i was here as its for ops and user channels.  to resolve the issue.      iam not here offtopic
[11:42] <Tm_T> yes and we won't be discussing your matter until several weeks
[11:43] <mcloy> and iam not forcing anything. just trying to understand . what is the strategy to resolve.
[11:43] <mcloy> how weeks will help. iam wiling to obey.
[11:43] <Tm_T> also when we possibly eventually return to discussion, please, please, stop blaming ikonia, and all the other points I already gave you in private
[11:43] <mcloy> tell me when ill blame him again
[11:43] <Tm_T> mcloy: let's call it a simple test if you can follow instructions
[11:44] <Tm_T> mcloy: you keep saying you're banned only because of ikonia making it personal
[11:44] <mcloy> may i SuGgEsT a way?  unban me and moniter for some time. you can anytime ban again.         if you have a better way to resolve. iam willing to cooperate
[11:44] <Tm_T> no
[11:44] <Tm_T> you will not be unbanned at this time
[11:44] <Tm_T> I repeat, you will NOT be unbanned at this time
[11:45] <Tm_T> you are already banned again
[11:45] <mcloy> ok. its your choice. but tell me how to resolve. (time of weeks will not help resolve the issue.)
[11:45] <Tm_T> mcloy: I already said to you, show me that you can follow simple request of being away several weeks
[11:45] <Tm_T> that's first step
[11:45] <LjL> 1) come back in a couple of weeks, not before
[11:45] <mcloy> how would you jugde me when iam not around. i didnt got the intellegence behind it.     (iam asking to improve and as its concerning me directly.)
[11:45] <LjL> 2) when you come back, stop blaming and ignoring ikonia
[11:46] <LjL> that's the steps
[11:46] <mcloy> LjL, ^
[11:46] <Tm_T> yup
[11:46] <Tm_T> mcloy: anything unclear still? (:
[11:46] <mcloy> it will be odd for me to repeat
[11:47] <mcloy> how would you jugde me when iam not around. i didnt got the intellegence behind it.     (iam asking to improve and as its concerning me directly.) may i SuGgEsT a way?  unban me and moniter for some time. you can anytime ban again.         if you have a better way to resolve. iam willing to cooperate
[11:47] <LjL> mcloy: your question makes sense, but let me put it this way, since we cannot judge people when they're not around, should we never ban anyone?
[11:47] <Tm_T> mcloy: I can judge that you were able to follow the first step
[11:47] <LjL> mcloy: after all, as soon as they're banned, we can't "judge" them anymore
[11:48] <Tm_T> mcloy: I can also judge your response when we return to the discussion then after we have passed those several weeks
[11:48] <mcloy> yes. so wasting some more weeks of mine  plus 2 previous months of ban would be  a better way to resolve?
[11:48] <Tm_T> or anyone of us ops
[11:49] <Tm_T> mcloy: it's better than letting you in yet again rightaway without you showing you can follow any instructions
[11:50] <mcloy> there are certain qualities of a person that makes him op. e.g handle channel abuse. do justice and be reasonable. if you are stubburn and cosistent on you decision. its better for me to part and make milliions of ubuntu users - 1 .
[11:51] <LjL> that is your choice alone
[11:51] <mcloy> guilt / satisfaction / justice is  inside of a person. you can feel it if you want to
[11:51] <mcloy> LjL,  you and Tm_T   have left me no other
[11:51] <LjL> the way i see it, if the ops are being stubborn, at least they aren't the only ones who are being
[11:52] <mcloy> if you see it that way.
[11:52] <Tm_T> mcloy: I have given you a simple instructions how we can begin resolving this
[11:52] <mcloy> Tm_T,  that has no logic to me
[11:52] <LjL> you have an alternative
[11:52] <LjL> appeal to the IRC Council
[11:52] <Tm_T> mcloy: neither there is any logic on letting you back in
[11:53] <mcloy> cross posting was never that sever that it would last 2.5 months
[11:53] <Tm_T> anyway, if you choose not to follow my requests, I don't see what we can gain continuing the discussion here
[11:53] <Tm_T> mcloy: you forget your bandodging?
[11:53] <mcloy> only because you see it that wat
[11:53] <mcloy> way
[11:53] <Tm_T> and I repeat, bans aren't for punishment
[11:53] <mcloy> if you say so...
[11:54] <Tm_T> also there's no set time for bans, it's often up to the users how long the ban sticks
[11:54] <mcloy> it is a punishment and harrasment for me
[11:54] <mcloy> i see it . its not up to me as a user.     iam on decretion of some ops
[11:54] <ikonia> mcloy: I have given you an option of me removing the ban in #ubuntu only so you can use the channel
[11:55] <ikonia> keeping the bans in place in #kubuntu and #ubuntu-server so you can still get support in #ubuntu but stop cross-posting in the other channels
[11:55] <mcloy> if i would be taking options from you. i would have done it yesterday before chating and requestion ops for 5 hours. ikonia
[11:56] <ikonia> ok, so you're rejecting the option of having the ban removed, fair enough.
[11:56] <ikonia> I'll leave it as it is.
[11:56] <Tm_T> sounds fair to me
[11:56] <LjL> mcloy: if you don't even want to accept to have your ban removed because you have something personal against ikonia, that's only your problem, and there is nothing further to discuss
[11:56] <mcloy> freely speaking. i dont think ikonia is viable to be an op.  but thats my personal opinion if you dont like my view
[11:57] <mcloy> ofcourse. everyone is afraid to step a fellow op. despite injustice happens
[11:57] <Tm_T> mcloy: you can express that with lenghty argumentation to irc council if you wish
[11:57]  * mcloy nodes
[11:58] <mcloy> LjL,  i just didnt wanted my matter to be resolve by ikonia
[11:58] <mcloy> that is a choice i have.
[11:58] <LjL> yes, it's a choice you have
[11:58] <mcloy> it can be any other op
[11:58] <LjL> and it results for now in you staying banned
[11:58] <LjL> choices have consequences
[11:58] <mcloy> i know..
[11:58] <LjL> so, come back in a couple of weeks, *or* appeal to the IRC Council
[11:58] <LjL> that's where it's at
[11:58] <mcloy> iam happy today. and was yesterday.
[11:58] <LjL> and it won't change
[11:59] <mcloy> as i told Tm_T   its not just about ban. its about justice and making ubuntu better.       i have many ips. and can change nick. chatting in ubuntu is not a big game for me..  but i didnt
[12:00] <mcloy> i am not happy to see who became operators of #ubuntu .
[12:00] <LjL> mcloy: then if you think there is something wrong, the right venue is a mail to the IRC Council, where you can expose your thoughts in detail to the right people
[12:00] <mcloy> and this opinion is nutral
[12:00] <mcloy> theres no use.
[12:00] <mcloy> on user wont matter
[12:01] <mcloy> i understand i dont own ubuntu .and its not free for humanity
[12:01] <LjL> mcloy: you won't know if there's no use until you try
[12:01] <mcloy> i understand i dont own ubuntu .and its not free for humanity
[12:02] <mcloy> thats all i will say
[12:02] <LjL> ok, if there is nothing further (and i don't think there is at this point), please /part for now. you know what your options are.
[12:03] <mcloy> ya. i would love to see you add a 1 plus to millions of kicks and bans you have me and enjoy.
[12:03] <mcloy> if it would be upto me. ill stay in ubuntu
[12:04]  * mcloy claps
[14:35] <IdleOne> Guest55695: identify!
[14:36] <oCean> friend or foe!?
[14:37] <IdleOne> friend
[16:21] <Mamarok> it's Pici
[16:22] <Fuchs> that doesn't answer the friend or foe question!
[16:22] <Fuchs> ;)
[16:22] <Mamarok> oh yes it does
[16:31] <IdleOne> "it's Pici" should answer any questions you may have.
[16:31] <funkyHat> I had a question about the meaning of life. I suppose you're right.
[16:33] <IdleOne> :)
[16:34] <Fuchs> wouldn't he be Guest4242 then?
[16:35] <funkyHat> Fuchs: a common mistake! 42 is the answer to the "ultimate question", not the meaning of life.
[16:35] <Fuchs> oh, I thought of the meaning of life as a subset until now. Thank you very much for that update <3
[16:36] <funkyHat> ⢁D
[17:09] <ikonia> hi epzil0n
[17:10] <epzil0n> hi there
[17:10] <epzil0n> wazup?
[17:10] <ikonia> can we help you with something ?
[17:10] <ikonia> I suspect your dns hostname has caused some problems
[17:11] <ikonia> is there something you need/want from the operator team ?
[17:11] <epzil0n> Ahh, well int's a bnc and disconnects now and then
[17:11] <epzil0n> no, don't know why i'm this channel
[17:11] <ikonia> epzil0n: well, the hostname it's resolving to isn't really going to work in the ubuntu channels
[17:11] <IdleOne> right but it is offensive and why you got forwarded to this channel
[17:12] <epzil0n> hehe, ok i'll just change that.. only humor nothing else sry
[17:12] <ikonia> epzil0n: thanks
[17:12] <IdleOne> thank you.
[17:12] <epzil0n> np ;)
[17:12] <ikonia> epzil0n: if you change it to something without the bad language, you'll gain access to the channel you wanted
[17:13] <epzil0n> ok
[17:13] <epzil0n> byebye
[17:14] <Unit193> He was from #xubuntu
[17:14] <ikonia> thanks
[18:54] <Myrtti> I've asked him to join here
[18:55] <pgib> didn't know about this chan
[18:56] <Myrtti> so you had a pastebin link?
[18:57] <pgib> right. I went into #ubuntu. upon join, pl099 started sending me messages asking what I do, and asking if I could help him with some bank drop.. sounds like he is trying to scam people, or just being really silly. But I didn't want anyone else to get in trouble from him
[18:59] <IAmNotThatGuy> pgib, can you take a screenshot of the private messages from that person to you and share it through imagebin ?
[18:59] <IAmNotThatGuy> Also, the nick is not registered
[18:59] <Myrtti> there's a pastebin
[18:59] <Myrtti> http://pastebin.com/Uf6fXmzB
[19:01] <Myrtti> I'll nudge him in pm
[19:04] <pgib> http://snag.gy/G1QsR.jpg
[19:05] <Myrtti> alright, thanks, his idle time is 12 minutes so atleast he's not doing it now to anyone else.
[19:05] <Myrtti> I'll keep my eyes open.
[19:06] <pgib> yeah, he stopped messaging me one we stirred up commotion with the !op command
[19:07] <pgib> and now he has quit anyways
[19:07] <IAmNotThatGuy> Might be a troll
[19:07] <Tm_T> thar's new
[21:11] <Corey> Are we "a Ubuntu shop" or "an Ubuntu shop?"
[21:30] <popey> an
[21:31] <popey> unless you pronounce it "you-bun-too"
[21:31] <popey> altohugh even then it sounds odd
[22:09] <Daviey> I think it's a .. as in 'a pending-trademark-approval shop'


[01:12] <axw_> wallyworld: I can't get TestUniterUpgradeConflicts to fail at all, and it's been passed by the landing bot...
[01:13] <axw_> cmars: were you on the latest maltese-falcon when you saw it fail ^^ ?
[01:13] <wallyworld> axw_: it failed for me when casey pinged me, but i think stuff may have landed since
[01:13] <wallyworld> i'll retry
[01:13] <wallyworld> in  bit
[01:13] <axw_> wallyworld: ok, thanks
[01:25] <cmars> axw_, yes, i'll confirm the revno in just a minute
[01:25] <axw_> cmars: thanks
[01:28] <cmars> axw_, yep, still getting a fail in TestUniterUpgradeConflicts at 6425ee2188
[01:29] <axw_> cmars: is it intermittent? I've been running the test in a loop... :/
[01:29] <cmars> axw_, it's as if the resolver doesn't get the unit state change between waitHooks & waitUnitAgent. very repeatable for me
[01:30] <cmars> i haven't seen it pass at all today
[01:30] <axw_> hrm
[01:30] <cmars> running with go1.2.2 (was using 1.5 but got distracted by map ordering bugs, which i've set aside for later)
[01:31] <axw_> I am using 1.4.2... I'll try that
[01:31] <cmars> axw_, anything you'd like me to try, let me know.
[01:31] <axw_> cmars: will do, ta
[01:38] <axw_> cmars: still can't repro with 1.2.2. might be helpful if you could add some debug logging to uniter/resolver.go at the top, to print out the local and remote states, and pastebin a failure
[01:40] <cmars> axw_, ok. in NextOp?
[01:40] <axw_> yes, please
[01:41] <axw_> I keep on doing that while debugging, should probably just leave it in and commit it
[01:43] <cmars> axw_, http://paste.ubuntu.com/12211350/
[01:44] <axw_> cmars: thanks
[03:02] <axw_> cmars: would you please try applying http://paste.ubuntu.com/12211722/, and see whether it fixes the issue? there's a race between the watcher refreshing and us clearing the in-memory resolved mode
[03:07] <cmars> axw_, still failing
[03:08] <axw_> cmars: thanks. thinko, there's race there anyway
[03:14] <axw_> cmars: so, current thinking: upgrade fails, becomes conflicted; agent is restarted and comes up *not* thinking it's conflicted; upgrade error is fixed, and resolved mode is set; agent proceeds to upgrade (setting the resolved mode was unnecessary for this), and because it doesn't think it was conflicted, doesn't clear the resolved mode
[03:16] <cmars> axw_, what stores the "conflicted" state? is that just the state of the git repo (when git used to be used)?
[03:16] <axw_> cmars: it's set in uniter.go when an upgrade op fails
[03:24] <axw_> cmars: tho it looks like verifyWaitingUpgradeError is supposed to cater for this. anyway, gotta go out for lunch, will look again later
[03:25] <cmars> axw_, ok cool. where is local state persisted?
[03:25] <cmars> i think that's the issue.. if we lose the conflicted state
[05:17] <menn0> waigani: if you feel inclined, could you please have a look at http://reviews.vapour.ws/r/2516/
[05:50] <axw_> cmars: only some local state is persisted; conflicted is not
[05:51] <axw_> cmars: what would happen in practice is that the uniter would come up, attempt to upgrade again and become conflicted again (unless the problem was fixed)
[06:29] <axw_> cmars: found it... the SetAgentStatus is failing, and its error wasn't being checked
[07:32] <TheMue> dimitern: ping. I yeasterday evening pushed http://reviews.vapour.ws/r/2504/ again. would you please take a look?
[07:33] <dimitern> TheMue, sure, it's the next on my list :)
[07:33] <TheMue> dimitern: great, thanks
[08:09] <dimitern> TheMue, reviewed
[08:09] <TheMue> dimitern: thx *click*
[08:09] <dimitern> TheMue, I've tried to clarify the need for (bool, error) result on SupportsSpaces
[08:13] <TheMue> dimitern: yep, I've already changed it
[08:14]  * TheMue is typing with one hand, phonecall :/
[08:43] <fwereade> mattyw, just added a card: "make uniter.RunCommands goroutine-safe"
[08:43] <fwereade> mattyw, which contains a short note that might be relevant to actions
[08:43] <fwereade> mattyw, let me know if it's useful
[08:43] <fwereade> s/if/whether/
[08:45] <TheMue> dimitern: so, phone call ended. I don't think an environs function should return a params type. the change of the standard not-support to params should be done inside the server-side API
[08:58] <voidspace> TheMue: dimitern: dooferlad: frobware: I have a suggestion
[08:58] <voidspace> TheMue: dimitern: dooferlad: frobware: why don't we postpone the retrospective/planning for next week
[08:59] <voidspace> when we're face to face
[08:59] <voidspace> so just have a normal standup today
[08:59] <TheMue> voidspace: would be fine for me
[08:59] <dimitern> voidspace, hmm, I'm not sure how are these two related :)
[09:00] <dimitern> voidspace, we'll see each other f2f anyway, but frobware might be interested in how we're doing the retro/planing
[09:00] <voidspace> dimitern: but planning is one of the things that really benefits from being face to face
[09:00] <frobware> voidspace, agreed
[09:00] <voidspace> dimitern: so we can still do a retrospective
[09:01] <voidspace> but planning is one of the things we should be doing next week *anyway*
[09:01] <voidspace> and it seems like a good way to take advantage of being face to face
[09:01] <dimitern> voidspace, good point about the planning
[09:01] <voidspace> dimitern: we could do the retrospective part this morning
[09:01] <voidspace> as there is some benefit to it being fresh in our minds
[09:02] <voidspace> but leave planning and estimation for face to face
[09:03] <voidspace> frobware: standup?
[09:03] <frobware> voidspace, yes, let's see what we want to do and when. :)
[09:04] <voidspace> frobware: we're all in standup - there seems to be consensus that doing the retrospective now is good, but leave planning and estimation until next week
[09:04] <frobware> voidspace, hmm. HO's tells me I'm in the hangout.
[09:04] <dooferlad> frobware: https://plus.google.com/hangouts/_/canonical.com/sapphire
[09:05] <voidspace> frobware: are you logged in with the right google account? I've made that mistake before and it's put me in an empty hangout
[09:05] <voidspace> ah, hi
[09:05] <frobware> voidspace, yep, that was it. ;)
[10:22] <dimitern> voidspace, TheMue, dooferlad, guys, since we have a 1.25 branch now, just a reminder to target your PRs against master and then backport them to 1.25
[10:23] <dimitern> (or vice versa - doesn't matter as long as there is a card for both and they're both done)
[10:23] <voidspace> dimitern: thanks
[10:28]  * dimitern will be back in ~1h
[10:32] <dooferlad> dimitern: http://pastebin.ubuntu.com/12213276/
[10:33] <dimitern> dooferlad, I suspect these are due to the removal of assignPrivateIPAddress
[10:33] <dooferlad> dimitern: it is in export_test.go
[10:33] <dimitern> dooferlad, even if you put it in export_test, in the code where it's used you need a var
[10:33] <dooferlad> dimitern: same package
[10:34] <dimitern> dooferlad, you can't patch a func
[10:34] <dooferlad> ah
[10:35] <dooferlad> dimitern: spot on
[10:35] <dooferlad> dimitern: why not just change the function name then?
[10:35] <dimitern> dooferlad,  :) cheers
[10:36] <dooferlad> dimitern: nevermind
[10:36] <dooferlad> dimitern: because you can't patch a func
[10:36] <dooferlad> heh
[10:36] <dimitern> dooferlad, yeah
[10:36] <dimitern> dooferlad, so if you do var assignPrivateIPAddress = func(...) { .. }, then you can add var AssignPrivateIPAddress = &assign.. in export_test
[10:37] <dimitern> ok, now I'm really away :)
[11:24] <urulama> dimitern: hey, you got a sec to take a look at this https://github.com/go-goose/goose/pull/15
[11:24] <urulama> dimitern: it'll land in "liberty" branch, but would like to get some feedback from you
[11:49] <dimitern> urulama, sure, looking
[12:27] <bogdanteleaga> sinzui, mgz_: is this a known failure? http://juju-ci.vapour.ws:8080/job/github-merge-juju-testing/14/console
[12:38] <dimitern> urulama, reviewed
[12:43] <urulama> dimitern: thanks. not sure that roles are part of v3 ... might have missed it though
[12:44] <dimitern> urulama, it appears so, according to the official API docs
[12:44] <urulama> dimitern: ah, right, doman + role name is globally unique across all domains
[12:45] <dimitern> urulama, yeah, and as commented, in all cases where either ID or Name can be used, we should support both I think, if it's not a lot more work ofc
[13:03] <sinzui> bogdanteleaga: While I am not familiar with the faillures for this job, I would still retry it because mgo_test in juju is a common cause of intermittent faillures
[13:04] <dimitern> sinzui, bogdanteleaga, I was looking at this - it seems the failure only happened after the changes in the "testfix" branch
[13:06] <bogdanteleaga> dimitern, yes, I did notice that but I cannot reproduce it locally
[13:06] <rogpeppe> i've code a PR up for review here which will enable environment providers to generate the boilerplate YAML automatically from the environment schema. reviews appreciated: https://github.com/juju/environschema/pull/6
[13:06] <dimitern> bogdanteleaga, different go versions and/or arch/os ?
[13:06] <rogpeppe> mgz_: this is the kind of thing you were alluding to, i think
[13:06] <bogdanteleaga> dimitern, all it seems to do for mongo is add one extra mongo path
[13:07] <bogdanteleaga> dimitern, 1.2.1 amd64 on trusty
[13:07] <bogdanteleaga> dimitern, I think that's what the box is using
[13:07] <dimitern> bogdanteleaga, yeah, that change seemed innocent enough to me, but .. well
[13:08] <bogdanteleaga> dimitern, it is weird because I ran them about 10 times locally and I got no failure
[13:08] <bogdanteleaga> dimitern, while it failed 3 times consecutively on the ci
[13:08] <dimitern> sinzui, can we tweak that job to run with TEST_LOGGING_CONFIG='<root>=TRACE' ?
[13:09] <dimitern> sinzui, temporarily of course
[13:09] <dimitern> bogdanteleaga, better logging will help - when it fails it seems to take ~1m each time
[13:10] <bogdanteleaga> dimitern, sinzui, tried adding a mongod executable on the new path just in case
[13:10] <bogdanteleaga> doesn't seem to change anything
[13:11] <dimitern> what's more likely to be causing it is if JUJU_MONGOD is set in the job environ I think
[13:13] <bogdanteleaga> yeah, but then that one becomes the first one and nothing should change
[13:15] <dimitern> yeah.. something else is in play
[13:24] <natefinch> I should really remember to take my own advice
[13:59] <wwitzel3> katco: are we starting at 10 or 10:30?
[13:59] <katco> wwitzel3: 10
[14:02] <katco> ericsnow: natefinch: stand up
[14:05] <mgz_> someone want to volunteer to back ou the last change on master to unblock?
[14:05] <mgz_> see bug 1489896
[14:05] <mup> Bug #1489896: Juju cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1489896>
[14:05] <mup> Bug #1489896 opened: Juju cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1489896>
[14:14] <mgz_> I suggest it should be OCR job is no one else steps up
[14:17] <mup> Bug #1489896 changed: Juju cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1489896>
[14:23] <mup> Bug #1480310 changed: systemctl link request failed for service FOO: Unit name FOO is not valid. <blocker> <ci> <systemd> <wily> <juju-core:Fix Released> <systemd (Ubuntu):Fix Released by pitti> <https://launchpad.net/bugs/1480310>
[14:23] <mup> Bug #1489896 opened: Juju cannot upgrade to 1.26-alpha1 <blocker> <ci> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1489896>
[15:32] <mattyw> fwereade, ping?
[15:32] <fwereade> mattyw, pong
[15:32] <mattyw> fwereade, hey hey, would you have 5 minutes to talk about the action pr?
[15:32] <fwereade> mattyw, oops, just saw mail
[15:33] <fwereade> mattyw, sure; and the end result of that retry command iis just what I wanted, yeah
[15:33] <mattyw> fwereade, I'm going to be in chicago next week so wanted to chat before I end up in an awkward timezone
[15:33] <fwereade> mattyw, good idea, thanks
[15:33] <mattyw> fwereade, https://plus.google.com/hangouts/_/gtdt43qnnxyz7gcbbdn5clz4u4a?pqs=1&hl=en&authuser=0
[16:46] <mgz> OCR or anyone else: review please to unblock master: http://reviews.vapour.ws/r/2523/
[17:01] <natefinch> mgz: is that just a straight up revert?
[17:02] <mgz> natefinch: yes
[17:02] <mgz> natefinch: compare with http://reviews.vapour.ws/r/2250/
[17:06] <voidspace> right, EOW
[17:06] <voidspace> bye all
[17:06] <voidspace> see some of you in London next week
[17:06] <natefinch> mgz: ship it
[17:09] <cmars> thanks natefinch.. i lacked context on that one, would have been a good part of my afternoon to review :)
[17:11] <natefinch> cmars: it was just a revert, so all I did was make sure it looked pretty much like the prior commit.
[17:12] <cmars> ah, right. first thing I saw was the size of the diff
[18:31] <ericsnow> natefinch: in moonstone
[20:14] <natefinch> ericsnow: got some trime for a little more help?  I can't figure out how to get basecommand to get the ID from the args... I keep getting empty data for some reason
[20:14] <ericsnow> natefinch: k
[20:39] <natefinch> ericsnow: There's no destroy in the API.. how is destroy different than untrack?
[20:39] <ericsnow> natefinch: destroy on the plugin (I mispoke)
[20:39] <natefinch> oh ok
[21:01] <natefinch> ericsnow, katco: landing that 3 pointer now... just waiting for the landing bot to take it.
[21:01] <katco> natefinch: yay! good work! :D
[21:01] <ericsnow> natefinch: sweet
[21:03] <natefinch> gotta run, but I'll pop back in to double check it really landed for true
[21:47] <natefinch-afk> ericsnow, katco: and, landed!
[21:48] <katco> natefinch-afk: woohoo!
[21:48] <katco> natefinch-afk: good work dude!
[22:17] <bdx> core, dev: Does anyone here know how to add custom cloud-config to maas provisioning....i.e. curtin_userdata preseeed or custom preseed??