| === ggherdov`___ is now known as ggherdov` | ||
| glen | is launchpad bzr having difficulties? | 09:02 |
|---|---|---|
| === Spads_ is now known as Spads | ||
| wgrant | glen: What symptoms are you seeing? | 09:06 |
| glen | first timeout and then remote lock | 09:26 |
| glen | 2~ | 09:36 |
| glen | + bzr push | 09:36 |
| glen | Using saved push location: bzr+ssh://bazaar.launchpad.net/+branch/eventum/ | 09:36 |
| glen | Unable to obtain lock held by glen666@bazaar.launchpad.net on taotie (process #16641), acquired 52 minutes, 57 seconds ago. | 09:36 |
| glen | See "bzr help break-lock" for more. | 09:36 |
| glen | bzr: ERROR: Could not acquire lock "(remote lock)": bzr+ssh://bazaar.launchpad.net/%2Bbranch/eventum/ | 09:36 |
| wgrant | Follow the instructions that it gave you. | 09:36 |
| glen | i'm afraikd to do break lock actions as i already once break git<>bzr syncing | 09:36 |
| glen | had to recreate whole git repo part | 09:37 |
| glen | so you say it's safe to break lock? | 09:37 |
| wgrant | How did that break it? | 09:37 |
| glen | not *that* exactly | 09:39 |
| wgrant | glen: As long as the offending bzr process is dead, break-lock is safe and the only way to proceed. | 09:39 |
| glen | ok. thanks. i'll try break lock then | 09:40 |
| glen | yet i have no idea is the offending process dead or not | 09:41 |
| glen | taotie is not under my control | 09:42 |
| glen | but seems now ok. thanks again | 09:42 |
| wgrant | glen: That's true, but it's almost always a safe assumption that the remote process is dead, or at least not going to cause any more damage, if your local one is. | 09:47 |
| wgrant | (taotie is bazaar.launchpad.net:22, so that process is the server-side of your previous SSH connection) | 09:47 |
| bookwar | hi all, can you help me with bug reports acl? I have 'mos' project where bugs supervisors are set to 'mos-all' group. | 10:10 |
| bookwar | But then in this activity log: https://bugs.launchpad.net/mos/+bug/1371723/+activity we have 'Vasilios Tzanoudakis' who is not in this group but he can change the bug status to 'fix released' | 10:10 |
| ubot5 | Ubuntu bug 1371723 in Mirantis OpenStack 6.0.x "To many reconnects in logs" [High,In progress] | 10:10 |
| bookwar | How i can set the restriction, such that only member of mos-all group can change bug statuses? | 10:11 |
| cjwatson | bookwar: That would require a patch to the Launchpad code; only certain bug status transitions (reopening Fix Released; switching away from Won't Fix; switching to Won't Fix, Expired, or Triaged) are restricted at all | 10:31 |
| cjwatson | See lib/lp/bugs/{interfaces,model}/bugtask.py | 10:31 |
| bookwar | cjwatson: thanks | 10:32 |
| === jacekn_ is now known as jacekn | ||
| === elmo_ is now known as elmo | ||
| === cmars` is now known as cmars | ||
| === mattgriffin is now known as mattgriffin-afk | ||
| === mattgriffin-afk is now known as mattgriffin | ||
| === seelaman is now known as IS_hr_bot | ||
| === b is now known as Guest78070 | ||
| === Guest78070 is now known as bac | ||
| === IS_hr_bot is now known as seelaman | ||
| === Ursinha is now known as Ursinha-afk | ||
| === Ursinha-afk is now known as Ursinha | ||
| === Ursinha is now known as Ursinha-afk | ||
| === Ursinha-afk is now known as Ursinha | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!