Processed (with 1 errors): your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> package cvsps
Ignoring bugs not assigned to: cvsps

> tags 422004 +fixed pending
Bug#422004: cvsps should ignore changesets newer than starttime - timestamp_fuzz
Tags were: patch
Tags added: fixed, pending

> tags 371835 +fixed
Bug#371835: cvsps -u mistakes branchpoint for the parent
Tags were: upstream
Bug#194187: cvsps -u still not working right
Tags added: fixed

> severity 369024 wishlist
Bug#369024: cvsps: manpage does not say that -f argument is a regexp
Severity set to `wishlist' from `normal'

> archive 371835
Bug#371835: cvsps -u mistakes branchpoint for the parent
Bug 371835 cannot be archived

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed (with 1 errors): your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> package cvsps
Ignoring bugs not assigned to: cvsps

> tags 269837 +fixed
Bug#269837: cvs --root does not work ?
There were no tags set.
Tags added: fixed

> archive 269837
Bug#269837: cvs --root does not work ?
Bug 269837 cannot be archived

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#269837: marked as done (cvs --root does not work ?)

[Debian Bug Tracking System]

Your message dated Wed, 05 Sep 2007 13:07:51 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#269837: cvs --root does not work ?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cvsps
Version: 2.0rc1-4
Severity: normal

Hello Marcus,

I cannot make cvsps --root to work

Documentation say:

   --root 
  Override the setting of  CVSROOT  (overrides  working  dir.  and
  environment)

So I would expect the two command below to be equivalent:

cvsps -x --root /home/cvs pari
CVSROOT=/home/cvs cvsps -x pari 

but only the second actually work, the fist fail with:

WARNING: malformed CVS version: no data
WARNING: malformed CVS version str: (UNKNOWN CLIENT)
WARNING: Your CVS client version:
[(UNKNOWN CLIENT)]
and/or server version:
[(UNKNOWN SERVER)]
are too old to properly support the rlog command.
This command was introduced in 1.11.1.  Cvsps
will use log instead, but PatchSet numbering
may become unstable due to pruned empty
directories.

cvs log: No CVSROOT specified!  Please use the `-d' option
cvs [log aborted]: or set the CVSROOT environment variable.

(What I attempt to do is to run cvsps on the CVS server without
any checked out repository) The cvs pserver run on woody, but 
cvsps run in a sid chroot (but should pot use the pserver anyway).

So is it a bug, or did I misunderstand the purpose of --root ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27
Locale: LANG=fr_FR, LC_CTYPE=fr_FR

Versions of packages cvsps depends on:
ii  cvs 1:1.12.9-4   Concurrent Versions System
ii  libc6   2.3.2.ds1-16 GNU C Library: Shared libraries an
ii  zlib1g  1:1.2.1.1-7  compression library - runtime

--- End Message ---
--- Begin Message ---
The documentation was updated to reflect that --cvs-direct needs to be
used

--- End Message ---

Bug#371835: marked as done (cvsps -u mistakes branchpoint for the parent)

[Debian Bug Tracking System]

Your message dated Wed, 05 Sep 2007 13:09:07 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Resolved
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cvsps
Version: 2.1-1
Severity: important

As shown by the script below, "cvsps -u" is confused by commits on
another branch: it seems that if there is a commit on another branch
in the cache already, cvsps gets confused and selects for parent the
branchpoint (if not on trunk) or decides it is the INITIAL commit for
the file (if on trunk).  (Un)comment the last "cvsps -x" to switch
between the 2 cases.

Warning: if you do not see 4 revs in the cvsps output, you probably
hit a transient cvs issue, I'll report it as well.

 script
#!/bin/sh
set -ex

# setup repo and working area
cvs -d $PWD/root init
mkdir root/test
cvs -d $PWD/root co test
cd test

# trunk
mkdir dir
cvs add dir
touch file
cvs add file
cvs ci -m "add file"
sleep 2

cvs tag A

# branch based on trunk
cvs tag -b A_HEAD
cvs up -r A_HEAD
echo >> file
cvs ci -m "branch work"
sleep 2

# init cache
cvsps --norc -x >/dev/null

# back to trunk
cvs up -A
echo >> file
cvs ci -m "trunk work"
sleep 2

# reinit cache to see the bug on the branch rather than on trunk
#cvsps --norc -x >/dev/null

# back to branch again
cvs up -r A_HEAD
echo >> file
cvs ci -m "more branch work"

# trigger problem
cvsps --norc -u
 output with cache reinit after patchset 2 only
PatchSet 1 
Date: 2006/06/07 21:31:30
Author: dwitch
Branch: HEAD
Tag: A 
Log:
add file

Members: 
file:INITIAL->1.1 

-
PatchSet 2 
Date: 2006/06/07 21:31:33
Author: dwitch
Branch: A_HEAD
Tag: (none) 
Log:
branch work

Members: 
file:1.1->1.1.2.1 

-
PatchSet 3 
Date: 2006/06/07 21:31:37
Author: dwitch
Branch: HEAD
Tag: (none) 
Log:
trunk work

Members: 
file:INITIAL->1.2 
 output with cache reinit after patchset 3
PatchSet 1
Date: 2006/06/07 21:23:17
Author: dwitch
Branch: HEAD
Tag: A
Log:
add file

Members:
file:INITIAL->1.1

-
PatchSet 2
Date: 2006/06/07 21:23:19
Author: dwitch
Branch: A_HEAD
Tag: (none)
Log:
branch work

Members:
file:1.1->1.1.2.1

-
PatchSet 3
Date: 2006/06/07 21:23:22
Author: dwitch
Branch: HEAD
Tag: (none)
Log:
trunk work

Members:
file:1.1->1.2

-
PatchSet 4
Date: 2006/06/07 21:23:25
Author: dwitch
Branch: A_HEAD
Tag: (none)
Log:
more branch work

Members:
file:1.1->1.1.2.2


-- 
Yann Dirson<[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> |   Support Debian GNU/Linux:
|  Freedom, Power, Stability, Gratis
 http://ydirson.free.fr/| Check 

--- End Message ---
--- Begin Message ---
The lastest package properly follows the ancestority correctly.
Michael

--- End Message ---

Bug#194187: marked as done (cvsps -u still not working right)

[Debian Bug Tracking System]

Your message dated Wed, 05 Sep 2007 13:09:07 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Resolved
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: cvsps
Version: 2.0rc1-1
Severity: normal
Tags: upstream

cvsps -u is still not OK.  I got a patchset that wanted to go from
the INITIAL commit of a file to its most recent revision with cvsps -u.
cvsps -x correctly gave me the revision 1.22 -> 1.23 patchset.

So, it looks like I still need to cvsps -x everytime, which is really hard
on the poor cvs server.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux khazad-dum 2.4.18 #1 Qua Abr 9 18:13:43 BRT 2003 i686
Locale: LANG=pt_BR, LC_CTYPE=pt_BR

Versions of packages cvsps depends on:
ii  cvs   1:1.11.5-6 Concurrent Versions System
ii  libc6 2.3.1-17   GNU C Library: Shared libraries an
ii  zlib1g1:1.1.4-11 compression library - runtime

-- no debconf information


-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

--- End Message ---
--- Begin Message ---
The lastest package properly follows the ancestority correctly.
Michael

--- End Message ---