Package: devscripts
Version: 2.8.10
Severity: wishlist
Tags: patch

With ACL-based file systems like AFS, the stat information for a file may
not tell the correct story on whether or not it's writable.  For example:

windlord:/afs/ir/dev/pubsw/debian/libafs-perl> dir debian/changelog
-rw-r--r--  1 rra root 137 Mar  8 20:32 debian/changelog
windlord:/afs/ir/dev/pubsw/debian/libafs-perl> id -un
eagle

I can modify this file because I have an [EMAIL PROTECTED] token, but
debchange aborts, believing that the changelog file is not writable.  The
following one-line patch will tell debchange to use access() rather than
stat() to determine if the changelog is writable.  access(), as a kernel
call, will do the right thing.

There are no backward compatibility issues since debchange already
requires Perl 5.8.  The main benefit will be for OpenAFS users, but other
ACL-controlled file systems may also benefit.

--- devscripts-2.8.10.orig/debchange.pl 2004-11-27 16:18:43.000000000 -0800
+++ devscripts-2.8.10/debchange.pl      2005-03-08 20:28:59.000000000 -0800
@@ -50,6 +50,7 @@
 use 5.008;  # We're using PerlIO layers
 use strict;
 use open ':utf8';  # changelogs are written with UTF-8 encoding
+use filetest 'access';  # use access rather than stat for -w
 use Encode 'decode_utf8';  # for checking whether user names are valid
 use Getopt::Long;
 use File::Copy;

I have tested this patch and confirmed that it solves this problem.

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

Versions of packages devscripts depends on:
ii  debianutils                 2.8.4        Miscellaneous utilities specific t
ii  dpkg-dev                    1.10.27      Package building tools for Debian
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  perl                        5.8.4-6      Larry Wall's Practical Extraction 

-- no debconf information


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

Reply via email to