and look for your e-mail address in that message.
Packages published for old distributions must have a lower Version-Release than packages for newer distributions.
(This is an automated bugzilla submission.
In an effort to get some of these upgrade problems fixed up I have taken a look
at this bug.
As far as I can tell the FC-6 branch of this package was updated when fc4 and
fc5 were updated and rebuild, but FC-6 was never built.
A mock rebuild of the existing FC-6 branch works fine here.
So, I think all that needs to be done here is a build request.
If you could do that it would be great. If I don't hear from you in a few days I
will do so myself to get this fixed up.
stupidity of fe cvs setup made it put the tag on the wrong subdir, and then
refuse to make the tag in the right place. i think there may be no way to get
an fc6 build without a rel bump just to make it allow make tag.
Odd. Which directory has the wrong tag in it?
What do you get from doing a 'make tag' in the FC-6 branch directory?
You should be able to use 'cvs status -v' to see the tags on each file/revision...
You may be able to use 'export TAG_OPTS=-F' then 'make tag' to force the tag...
The safest course may well be to just bump the release on fc6/devel at least and
re-tag them with the new release.
magilla 23 % make tag
cvs tag -c monotone-0_31-1_fc6
ERROR: The tag monotone-0_31-1_fc6 is already applied on a different branch
ERROR: You can not forcibly move tags between branches
cvs tag: Pre-tag check failed
cvs [tag aborted]: correct the above errors first!
make: *** [tag] Error 1
to the rescue.
Yeah, you have this tag in your devel branch already. Possibly you did a 'make
tag' after the branch but before updating your common directory so it was seeing
devel as fc6, when it should have been fc7.
As suggested in comment #6 you should bump the release to
add a changelog entry, make tag, and make plague.
Hey Roland. Have you had a chance to push this fix out?
If you like I would be happy to push out a fixed version for you...
This should get fixed soon, as it's affecting users in a released version...
pls go ahead and push the rebuild
pls keep .spec identical committed on all branches, though build is needed only
well, I will need to bump the release/add a changelog for fc6.
No other branches will be affected...
diff -u -r1.19 monotone.spec
--- monotone.spec 12 Nov 2006 03:15:47 -0000 1.19
+++ monotone.spec 22 Dec 2006 04:18:39 -0000
@@ -1,6 +1,6 @@
Summary: A free, distributed version control system
@@ -164,6 +164,9 @@
+* Thu Dec 21 2006 Kevin Fenzi <firstname.lastname@example.org> - 0.31-1.1
+- Bump and rebuild to fix upgrade path
* Sat Nov 11 2006 Roland McGrath <email@example.com> - 0.31-1
- Updated for 0.31 release.
Is that acceptable?
keep .spec identical committed on all branches, though build is needed only for fc6
ok, so you would prefer me checking in the above change on all branches, but
only building the fc6 one? That could cause some confusion down the line, but I
will do so if you prefer it.
yes, keep branches identical always
i don't care if you do superfluous builds or not
ok, fc5/fc6/devel branches all bumped and checked in and builds fired off.
fc4 is already divergent from the other branches, perhaps fc4 has too old a
boost-devel to work with the new monotone version? I left it as it was.
Oddly I see the newer boost-devel in fc4/updates-testing, but never released.
This was fixed by Kevin's rebuild. fc4 is indeed dead.