Gary Jennejohn wrote:
> > >
> > > > csup already has a CVS mode, at least in 9-current. I don't use older
> > > > versions of FreeBSD so I don't know whether it supports CVS there.
> > >
> > > It does at least down to 7.x.
> >
> > High time to fix this botheration, isn't it?
> >
>
> This has
On Mon, 21 Jun 2010 08:45:17 +0700
Victor Sudakov wrote:
> Christian Weisgerber wrote:
> >
> > > csup already has a CVS mode, at least in 9-current. I don't use older
> > > versions of FreeBSD so I don't know whether it supports CVS there.
> >
> > It does at least down to 7.x.
>
> High time t
Christian Weisgerber wrote:
>
> > csup already has a CVS mode, at least in 9-current. I don't use older
> > versions of FreeBSD so I don't know whether it supports CVS there.
>
> It does at least down to 7.x.
High time to fix this botheration, isn't it?
--
Victor Sudakov, VAS4-RIPE, VAS47-RI
Gary Jennejohn wrote:
> csup already has a CVS mode, at least in 9-current. I don't use older
> versions of FreeBSD so I don't know whether it supports CVS there.
It does at least down to 7.x.
--
Christian "naddy" Weisgerber na...@mips.inka.de
___
On Tue, 15 Jun 2010 09:28:37 +0700
Victor Sudakov wrote:
> Jonathan Noack wrote:
> > >> But to hell with this. I started the topic because I think something
> > >> is wrong with SVN to CVS export, which upsets cvsup and causes
> > >> "Checksum mismatch" errors. Is anybody willing to look at it?
On Mon, June 14, 2010 00:43, Victor Sudakov wrote:
> Victor Sudakov wrote:
>> But to hell with this. I started the topic because I think something
>> is wrong with SVN to CVS export, which upsets cvsup and causes
>> "Checksum mismatch" errors. Is anybody willing to look at it?
>
> I see nobody is
Jonathan Noack wrote:
> >> But to hell with this. I started the topic because I think something
> >> is wrong with SVN to CVS export, which upsets cvsup and causes
> >> "Checksum mismatch" errors. Is anybody willing to look at it?
> >
> > I see nobody is ever going to fix this? Cvsup mails me a bu
Victor Sudakov wrote:
> I see nobody is ever going to fix this? Cvsup mails me a bunch of
> "Checksum mismatch" errors on every run, with a risk of overlooking
> real errors.
It is particularly egregious when a tag is laid down, like today.
csup(1) ends up refetching a big chunk of the tree from
On Mon, 14 Jun 2010 11:43:08 +0700
Victor Sudakov wrote:
> Victor Sudakov wrote:
>
> [dd]
>
> >
> > But to hell with this. I started the topic because I think something
> > is wrong with SVN to CVS export, which upsets cvsup and causes
> > "Checksum mismatch" errors. Is anybody willing to loo
Victor Sudakov wrote:
[dd]
>
> But to hell with this. I started the topic because I think something
> is wrong with SVN to CVS export, which upsets cvsup and causes
> "Checksum mismatch" errors. Is anybody willing to look at it?
I see nobody is ever going to fix this? Cvsup mails me a bunch of
On Tue, 5 Jan 2010 08:32, stephen@ wrote:
Victor Sudakov wrote:
But to hell with this. I started the topic because I think something
is wrong with SVN to CVS export, which upsets cvsup and causes
"Checksum mismatch" errors. Is anybody willing to look at it?
I second Victor's request.
Tho
Victor Sudakov wrote:
But to hell with this. I started the topic because I think something
is wrong with SVN to CVS export, which upsets cvsup and causes
"Checksum mismatch" errors. Is anybody willing to look at it?
I second Victor's request.
___
f
ere are lots of messages
> "Checksum mismatch -- will transfer entire file" about all kinds of
> downloaded files, e.g.
http://old.nabble.com/CVSup-src-file-Edits-almost-alway-triggering-Checksum-mismatch-and-Fixup-td24980888.html
Seems like you're facing the same problem. Sim
Peter Jeremy wrote:
>
> >So, branching a native CVS repo would still produce a massive change
> >and download of RCS files by cvsup?
>
> Yes - because the RCS file includes all the metadata - ie tags. This
> is very visible when (eg) the ports tree is tagged.
Then I fail to understand the dif
On 2010-Jan-04 20:37:49 +0600, Victor Sudakov
wrote:
>Erik Trulsson wrote:
>> It will add the tag to the file of course. (In CVS tags are stored inside
>> each RCS file.)
Actually, FreeBSD's CVS checkin scripts were hacked many years ago to
unexpand $FreeBSD$ on checkin so that the actual repo
Erik Trulsson wrote:
> > Peter Jeremy wrote:
> > > >I also see that many "changes" in the CVS seem to be useless: there
> > > >are no changes other than file version increments.
> > >
> > > SVN metadata changes will appear in CVS as version changes only. The
> > > most obvious/common case is bran
Erik Trulsson wrote:
> > > SVN metadata changes will appear in CVS as version changes only. The
> > > most obvious/common case is branching - branching a native CVS repo
> > > just adds the branch tags. Branching a SVN repo replicates the tree
> > > and the SVN->CVS exporter turns the branch into
On Mon, Jan 04, 2010 at 07:03:16PM +0600, Victor Sudakov wrote:
> Peter Jeremy wrote:
> > >I also see that many "changes" in the CVS seem to be useless: there
> > >are no changes other than file version increments.
> >
> > SVN metadata changes will appear in CVS as version changes only. The
> > m
Peter Jeremy wrote:
> >I also see that many "changes" in the CVS seem to be useless: there
> >are no changes other than file version increments.
>
> SVN metadata changes will appear in CVS as version changes only. The
> most obvious/common case is branching - branching a native CVS repo
> just ad
On 2010-Jan-03 21:45:03 +0600, Victor Sudakov
wrote:
>I also see that many "changes" in the CVS seem to be useless: there
>are no changes other than file version increments.
SVN metadata changes will appear in CVS as version changes only. The
most obvious/common case is branching - branching a
Doug Barton wrote:
I was not going to reply on this thread at all, but the amount of
random speculation has now reached a pathological level.
The spurious new line at the end of a file has nothing to do with svn,
it is an artifact of how the file was originally transferred to the
cvsup mirror. T
age as a reassuring sign that the system is working exactly as
> designed. :)
Except for the fact that the -L0 switch has become completely useless.
All the "Checksum mismatch -- will transfer entire file" are L0
messages, i.e. they ARE error messages.
--
Vic
so see a file from ports corrupted:
>
> ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
> ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
[dd]
>
> This was grepped through the last few months. Are any of these specific
> files 'impo
I was not going to reply on this thread at all, but the amount of
random speculation has now reached a pathological level.
The spurious new line at the end of a file has nothing to do with svn,
it is an artifact of how the file was originally transferred to the
cvsup mirror. The checksum mismatch
ports corrupted:
ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
ports/Mk/bsd.port.mk,v: Checksum mismatch -- will transfer entire file
lots of messages
> >>"Checksum mismatch -- will transfer entire file" about all kinds of
> >>downloaded files, e.g.
> >>
> >>
> >>src/lib/libc/posix1e/acl_delete_entry.c,v: Checksum mismatch -- will
> >>transfer entire file
> >
> &
lots of messages
"Checksum mismatch -- will transfer entire file" about all kinds of
downloaded files, e.g.
src/lib/libc/posix1e/acl_delete_entry.c,v: Checksum mismatch -- will
transfer entire file
I also see a bunch of these, almost every time I do a csup. Looking
back in my logs,
ecksum mismatch -- will transfer entire file" about all kinds of
> downloaded files, e.g.
>
>
> src/lib/libc/posix1e/acl_delete_entry.c,v: Checksum mismatch -- will transfer
> entire file
I also see a bunch of these, almost every time I do a csup. Looking
back in my logs, I s
Colleagues,
I cvsup the FreeBSD CVS repository daily from cvsup.ru.freebsd.org.
Both the client and the server run CVSup Software version: SNAP_16_1h,
Protocol version: 17.0.
Recently I noticed that there are lots of messages
"Checksum mismatch -- will transfer entire file" about al
29 matches
Mail list logo
