[13:55] <exarkun> Hey, what the hell did Baronos do to this ticket, and how can I keep him away from the rest of my tickets?  https://bugs.launchpad.net/twisted-trac-integration/+bug/898804
[14:14] <dobey> exarkun: looks like he accidentally changed the status, then changed it back is all
[14:27] <exarkun> And I should be happy with that?
[14:48] <nailora> if he should not be allowed to change it in the first place then you are officially allowed to be unhappy. if he was granted the rights at some point, what did you expect to happen?
[14:49] <exarkun> I don't know who he is.  He doesn't have any particular permissions on the project.
[14:50] <nailora> than maybe everyone is allowed to set bug states in your project when what you really want is to restrict that ability.
[14:51] <exarkun> Great.  How can I do that?
[14:52] <exarkun> https://bugs.launchpad.net/pyflakes/+configure-bugtracker is the only obvious place that such might configuration might be done, but there are no options for controlling this on that page.
[14:59] <nailora> sorry, I do not know if/how you can restrict Bug access in that way. Some of the Launchpad maintainers around here should be able to tell you.
[18:36] <maxb> exarkun: all users can edit bug status (except for setting restricted statuses - Triaged and Won't Fix)
[18:37] <maxb> exarkun: Your anger seems disproportionate for a simple mis-click, that was fixed by the user themself only 7 seconds later
[19:09] <george_e> This build has failed: https://launchpadlibrarian.net/86534973/buildlog.txt.gz
[19:09] <george_e> ...but I can't figure out why.
[19:09] <george_e> There's a line "pbuilder-satisfydepends-dummy: Depends: yaml-cpp-dev (>= 0.2.7) but it is not going to be installed."
[19:10] <george_e> But why isn't it going to install yaml-cpp-dev?
[19:10] <george_e> That package exists in the destination PPA for this build.
[19:14] <Ampelbein> george_e: What is the ppa's url?
[19:15] <george_e> Ampelbein: https://code.launchpad.net/~george-edison55/+archive/juju-gui
[19:17] <Ampelbein> george_e: Ok, and where is the sourcepackage you are trying to build?
[19:17] <george_e> Ampelbein: This is the recipe: https://code.launchpad.net/~george-edison55/+recipe/juju-gui-daily
[19:17] <george_e> This is the base branch: https://code.launchpad.net/~george-edison55/juju-gui/trunk
[19:27] <Ampelbein> george_e: Hmm, I could be on the wrong track but: 'dpkg --compare-versions 0.2.7-0~1~precise1 ge 0.2.7' 'echo $?' returns 1 so the version requirement isn't satisfied.
[19:27] <george_e> That's... odd.
[19:28] <george_e> What happens if you add the '-0' to the left-hand side.
[19:29] <Ampelbein> george_e: ?
[19:29] <maxb> I think the subtlety here is that 0.2.7 is actually semantically equivalent to 0.2.7-0 as far as the version comparison is concerned
[19:29] <maxb> this is one reason to avoid the overuse of ~ as a generic separator
[19:30] <Ampelbein> maxb: Yes, sure looks that way.
[19:30] <george_e> Ampelbein: I meant to say "what happens if you compare '0.2.7-0~1~precise1 ge 0.2.7-0'"?
[19:30] <Ampelbein> george_e: So you meant the right side ;-) Result is the same, so maxb's suggestion seems to be correct.
[19:31] <george_e> Sorry, my bad.
[19:32] <Ampelbein> george_e: I suggest a versioning like 0.2.7-1~precise1 in yaml-cpp
[19:32] <george_e> http://bazaar.launchpad.net/~george-edison55/juju-gui/juju-gui-debian/view/head:/control
[19:32] <george_e> Ooops. Wrong file.
[19:32] <george_e> http://bazaar.launchpad.net/~george-edison55/juju-gui/juju-gui-debian/view/head:/changelog
[19:33] <maxb> 0.2.7-1~precise1 is misleading. it hints at being a derivation of 0.2.7-1
[19:33] <george_e> Sorry guys... that was still the wrong link.
[19:33] <george_e> THIS is the right one:
[19:33] <george_e> http://bazaar.launchpad.net/~george-edison55/yaml-cpp/yaml-cpp-debian/view/head:/changelog
[19:34] <george_e> You can see I've specified the version as '0.2.7' in the debain/changelog file.
[19:34] <Ampelbein> george_e: Or you use a version of 0.2.7~ in the Depends: of juju-gui
[19:34] <george_e> Maybe I should ask a question over on #ubuntu-packaging.
[19:34] <Ampelbein> george_e: yes, 0.2.7 is treated as 0.2.7-0 and 0.2.7-0~1~precise1 doesn't fulfill that requirement.
[19:35] <george_e> Well, thanks for finding the source of the problem.
[19:35] <george_e> That one was really confusing me.
[19:35] <maxb> I'd suggest a version like 0.2.7-0george1~precise1
[19:35] <Kiall> "0.2.7-0~1" is pre "0.2.7-0" .. and "0.2.7-0+1" is post "0.2.7-0"
[19:38] <george_e> I can't change the versioning - that is done automatically by the daily build system.
[19:38] <george_e> *versioning of the yaml-cpp-dev package
[19:38] <maxb> that's not correct
[19:38] <george_e> It isn't?
[19:38]  * george_e suddenly remembers...
[19:38] <maxb> only the ~precise1 suffix is enforced
[19:39] <george_e> I totally forgot that the version number is set by the recipe script.
[19:39] <george_e> This means I need to change the recipe script for yaml-cpp, though, right?
[19:39] <maxb> yes
[19:40] <george_e> ...then I'll need to wait for another build :P
[19:40] <maxb> {debupstream}-0bzr{revno} would make it clear that the number is a bzr revno
[19:40] <george_e> Do I need the '0' before 'bzr'?
[19:42] <maxb> it would be wise
[19:43] <maxb> -bzr would be considered a greater version than -999999999999999999999999
[19:46] <jelmer> {debupstream}+bzr{revno} seems like a more commonly used way of writing that
[19:46] <jelmer> hi maxb, btw :)
[19:46] <george_e> jelmer: So I should use that format?
[19:47] <jelmer> george_e: it's up to you, there is no mandatory format
[19:47] <george_e> Well, I'm just wondering if that is the precedent.
[19:47] <maxb> {debupstream}+bzr{revno} sounds like it's a bzr branch of the upstream, rather than a bzr branch of the packaging
[19:47] <jelmer> oh, sorry, I missed a bit of context there
[19:47] <maxb> Best to have a - in there clearly separating the upstream and packaging versions
[19:49] <jelmer> maxb: then again, that suggests a non-native package.. and the recipe will produce a native version
[19:50] <george_e> So... which format should I use?
[19:50] <george_e> '-' or '+'?
[19:52] <exarkun> maxb: You're right.
[19:52] <exarkun> maxb: Initially I was confused by the rendering of the pair of changes.  That probably contributed to my reaction.
[19:52] <george_e> Someone on #ubuntu-packaging suggested '{debupstream}+bzr{revno}-0ubuntu0+{revno:packaging}'.
[19:53] <george_e> I like the idea of having the revision number of the packaging in there.
[19:53] <george_e> That way I can trigger a build if all I change is the packaging.
[19:53] <maxb> that would be appropriate if you had an upstream and a packaging branch involved
[19:53] <maxb> do you?
[19:53] <george_e> Yes.
[19:54] <exarkun> maxb: It might be nice if there was an undo button to fix that kind of mistake.
[19:54] <george_e> I own two branches: the upstream source branch and the packaging branch.
[19:54] <george_e> I am only the author of the packaging branch, but I own both.
[20:01] <jelmer> george_e: it doesn't really matter who owns the branches, anybody can create a recipe for them.
[20:01] <george_e> Right.
[21:47] <penguin42> lp seems to be timing out a lot at the moment (e.g. oops bcb32dd6feaa700af7b9b344107c16be )
[21:48] <penguin42> I am in the dynamic bug listing trial if that makes any difference
[21:52] <george_e> LP seems to be down.
[21:52] <george_e> Up, never mind.
[21:52] <george_e> Some of the pages are loading.
[21:52] <george_e> Some aren't though.
[21:52] <george_e> It seems intermittent.
[21:54] <penguin42> yeh mostly down with an occasional bit of up
[21:55] <george_e> I've only had one page load properly in the last 5 minutes.
[21:56] <george_e> Other people are reporting that it's loading for them.
[21:56] <george_e> I wonder it this is a localized issue.
[21:59] <george_e> I also can't connect to some other websites.
[21:59] <george_e> Maybe some network infrastructure went down.
[22:01] <george_e> Launchpad is loading again.