Your message dated Sat, 06 Oct 2007 04:14:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#253943: Debian CVS bug triage - bug #253943
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: cvs
Version: 1:1.12.9-1
Severity: normal

The changes to the loginfo handling as of version 1.12.6 (apart from
warranting a major version bump, but that's not your problem) have faulty
backward compatibility support.

In particular, when one does a cvs add of a directory, the old version
called the loginfo script with a single argument:

    path - New Directory

The new version instead calls loginfo with:

    path - New Directory,NONE,NONE

This broke cvslog.  My guess is that the same may apply to cvs import
(which similarly generates one of these special messages), but I haven't
tested that.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C)

Versions of packages cvs depends on:
ii  debconf                     1.4.25       Debian configuration management sy
ii  libc6                       2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libpam-runtime              0.76-21      Runtime support for the PAM librar
ii  libpam0g                    0.76-21      Pluggable Authentication Modules l
ii  zlib1g                      1:1.2.1.1-3  compression library - runtime

-- debconf information:
  cvs/pserver_repos_individual: true
  cvs/pserver_setspawnlimit: false
  cvs/rotatekeep: 7
  cvs/badrepositories: create
  cvs/pserver_warning: 
  cvs/rotatekeep_individual: 7
  cvs/pserver_repos: all
* cvs/pserver: false
  cvs/cvs_conf_is_dead: 
* cvs/repositories: 
  cvs/rotatekeep_nondefault: no
  cvs/rotate_individual: true
  cvs/pserver_spawnlimit: 400
  cvs/rotatehistory: no


--- End Message ---
--- Begin Message ---
Version: 1:1.12.13-8

Russ Allbery wrote:
> This bug report was complaining about a new version of CVS breaking
> backward compatibility in a rather annoying way for hook scripts.  The
> bug, in that sense, is still present, in that backward compatibility is
> still broken, but the change happened long enough ago that I expect
> everyone has just coped and moved on with their lives.
> 
> As such, it's probably reasonable to close the bug as something that will
> never be fixed.

I agree. The version which had the problem was uploaded pre sarge. This
should indeed give people enough time to cope to the change.

-- 
Lior Kaplan
[EMAIL PROTECTED]

GPG fingerprint:
C644 D0B3 92F4 8FE4 4662  B541 1558 9445 99E8 1DA0


--- End Message ---

Reply via email to