CVS is broken after last update on SuSE 8.2
I installed the last CVS update on our SuSE 8.2 CVS server last Thursday (May 20). Since then, some users get the error "cvs update: move away <xxx>; it is in the way" when running cvs update. It seemed to be rather machine specific, not user specific (different windows clients, SuSE machine is running pserver). But downgrading to the original version delivered with 8.2 made the errors go away. This is the first time (for me), that a SuSE update broke something rather bad, so I'm confident that this was just a one-time mistake ;-) Is this going to be fixed? It is not really critical at the moment, because the CVS server is an internal machine, but I keep it updated nevertheless. Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \
Markus Gaugusch wrote:
I installed the last CVS update on our SuSE 8.2 CVS server last Thursday
(May 20). Since then, some users get the error "cvs update: move away <xxx>; it is in the way" when running cvs update.
Right...
It seemed to be rather machine specific, not user specific (different windows clients, SuSE machine is running pserver). But downgrading to the original version delivered with 8.2 made the errors go away.
...also to be expected...
This is the first time (for me), that a SuSE update broke something rather bad, so I'm confident that this was just a one-time mistake ;-)
...not really...
Is this going to be fixed? It is not really critical at the moment, because the CVS server is an internal machine, but I keep it updated nevertheless.
...and no. :-) You're misinterpreting the source of the error; it's not Suse, it's CVS. The CVS developers have changed the default action in seveal areas "recently", IIRC. So as Suse pulls those patches in for the updates, you get the "new features". Goto http://www.csvhome.org and check out the some of the changelogs, FAQs, and those sorts of docs. HTH, Kevin
On May 24, Kevin Brannen <kevin_brannen@stercomm.com> wrote:
You're misinterpreting the source of the error; it's not Suse, it's CVS. The CVS developers have changed the default action in seveal areas "recently", IIRC. So as Suse pulls those patches in for the updates, you get the "new features". Goto http://www.csvhome.org and check out the some of the changelogs, FAQs, and those sorts of docs. I've thought that the SuSE update policy is to "fix only bugs and no new features", at least I would have expected a note in the update description when using YOU/fou4s.
I can't imagine that this is right. Markus
Hi folks, Kevin Brannen wrote:
You're misinterpreting the source of the error; it's not Suse, it's CVS. The CVS developers have changed the default action in seveal areas "recently", IIRC. So as Suse pulls those patches in for the updates, you get the "new features". Goto http://www.csvhome.org and check out the some of the changelogs, FAQs, and those sorts of docs.
This is not true. SuSE backports (security) fixes from newer software releases to the "old" release, that was distributed with the SuSE version you own. This is to ensure that your system works correctly after patching. Putting new software releases / features could mean, that software that depends on the package wont run after the update. The fixed SuSE package should just eliminate the security flaw, not change anything else (thats whats the backporting of fixes is for, its not just copy and paste, its backporting). peace, Tom
participants (3)
-
Kevin Brannen -
Markus Gaugusch -
Thomas Seliger