Your message dated Fri, 26 Aug 2005 10:32:07 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323582: fixed in openafs 1.4rc1-1
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 25 Aug 2005 21:50:04 +0000
>From [EMAIL PROTECTED] Thu Aug 25 14:50:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from faye.voxel.net [69.9.164.210] (fe1c23910dfcc2629ef64f3b6e011781)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E8Pbn-00047J-00; Thu, 25 Aug 2005 14:50:03 -0700
Received: from jack.dev.in.athenacr.com (unknown [66.150.84.1])
by faye.voxel.net (Postfix) with ESMTP id CA18836BA7
for <[EMAIL PROTECTED]>; Thu, 25 Aug 2005 17:50:02 -0400 (EDT)
Subject: openafs: FTBFS if using utf8
From: Andres Salomon <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Thu, 25 Aug 2005 17:50:01 -0400
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
Content-Transfer-Encoding: quoted-printable
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: openafs
Version: 1.3.87-1
Severity: serious
Hi Russ,
On my system, openafs fails to build with the following error:
+ case "i386_linux24" in
+ gcc -pipe -shared -Xlinker -x -g -O2 -Dlinux -DLINUX_PAM -fPIC -o
pam_afs.so.1 afs_setcred.o afs_auth.o afs_util.o afs_account.o
afs_session.o afs_password.o afs_pam_msg.o afs_message.o
AFS_component_version_number.o ../shlibafsauthent/acfg_errors.o ../shlibafs=
authent/afssyscalls.o ../shlibafsauthent/audit.o ../shlibafsauthent/authcli=
ent.o ../shlibafsauthent/authcon.o ../shlibafsauthent/cellconfig.o ../shlib=
afsauthent/client.o ../shlibafsauthent/dirpath.o ../shlibafsauthent/display=
.o ../shlibafsauthent/fileutil.o ../shlibafsauthent/get_krbrlm.o ../shlibaf=
sauthent/kaaux.o ../shlibafsauthent/kaerrors.o ../shlibafsauthent/kalocalce=
ll.o ../shlibafsauthent/kauth.cs.o ../shlibafsauthent/kauth.xdr.o ../shliba=
fsauthent/kautils.o ../shlibafsauthent/ktc_errors.o ../shlibafsauthent/ktc.=
o ../shlibafsauthent/ptclient.o ../shlibafsauthent/pterror.o ../shlibafsaut=
hent/pthread_glock.o ../shlibafsauthent/ptint.cs.o ../shlibafsauthent/ptint=
.xdr.o ../shlibafsauthent/ptuser.o ../shlibafsauthent/read_passwd.o ../shli=
bafsauthent/rmtsysc.o ../shlibafsauthent/rmtsys.cs.o ../shlibafsauthent/rmt=
sysnet.o ../shlibafsauthent/rmtsys.xdr.o ../shlibafsauthent/rxkad_errs.o ..=
/shlibafsauthent/serverLog.o ../shlibafsauthent/snprintf.o ../shlibafsauthe=
nt/token.o ../shlibafsauthent/ubikclient.o ../shlibafsauthent/ubik_int.cs.o=
../shlibafsauthent/ubik_int.xdr.o ../shlibafsauthent/uerrors.o ../shlibafs=
authent/uinit.o ../shlibafsauthent/user.o ../shlibafsauthent/userok.o ../sh=
libafsauthent/writeconfig.o ../shlibafsrpc/afsaux.o ../shlibafsrpc/afscbint=
.cs.o ../shlibafsrpc/afscbint.xdr.o ../shlibafsrpc/AFS_component_version_nu=
mber.o ../shlibafsrpc/afsint.cs.o ../shlibafsrpc/afsint.xdr.o ../shlibafsrp=
c/assert.o ../shlibafsrpc/base64.o ../shlibafsrpc/casestrcpy.o ../shlibafsr=
pc/cbc_encrypt.o ../shlibafsrpc/cksum.o ../shlibafsrpc/com_err.o ../shlibaf=
srpc/crc.o ../shlibafsrpc/crypt_conn.o ../shlibafsrpc/crypt.o ../shlibafsrp=
c/debug_decl.o ../shlibafsrpc/des.o ../shlibafsrpc/error_msg.o ../shlibafsr=
pc/et_name.o ../shlibafsrpc/fasttime.o ../shlibafsrpc/fcrypt.o ../shlibafsr=
pc/key_parity.o ../shlibafsrpc/key_sched.o ../shlibafsrpc/md4.o ../shlibafs=
rpc/md5.o ../shlibafsrpc/misc.o ../shlibafsrpc/new_rnd_key.o ../shlibafsrpc=
/pcbc_encrypt.o ../shlibafsrpc/quad_cksum.o ../shlibafsrpc/rx_conncache.o .=
./shlibafsrpc/rx_event.o ../shlibafsrpc/rx_getaddr.o ../shlibafsrpc/rx_glob=
als.o ../shlibafsrpc/rxkad_client.o ../shlibafsrpc/rxkad_common.o ../shliba=
fsrpc/rxkad_server.o ../shlibafsrpc/rx_misc.o ../shlibafsrpc/rx_multi.o ../=
shlibafsrpc/rx_null.o ../shlibafsrpc/rx.o ../shlibafsrpc/rx_packet.o ../shl=
ibafsrpc/rx_pthread.o ../shlibafsrpc/rx_rdwr.o ../shlibafsrpc/rxstat.cs.o .=
./shlibafsrpc/rxstat.o ../shlibafsrpc/rxstat.ss.o ../shlibafsrpc/rxstat.xdr=
.o ../shlibafsrpc/rx_trace.o ../shlibafsrpc/rx_user.o ../shlibafsrpc/strng_=
to_key.o ../shlibafsrpc/syscall.o ../shlibafsrpc/ticket5.o ../shlibafsrpc/t=
icket.o ../shlibafsrpc/util.o ../shlibafsrpc/weak_key.o ../shlibafsrpc/xdr_=
afsuuid.o ../shlibafsrpc/xdr_arrayn.o ../shlibafsrpc/xdr_array.o ../shlibaf=
srpc/xdr_int32.o ../shlibafsrpc/xdr_int64.o ../shlibafsrpc/xdr.o ../shlibaf=
srpc/xdr_rx.o -lpthread -lpam -lresolv
../shlibafsrpc/AFS_component_version_number.o(.data+0x0): multiple
definition of `cml_version_number' AFS_component_version_number.o(.data
+0x0): first defined
here ../shlibafsrpc/AFS_component_version_number.o(.data.rel.local+0x0):
multiple definition of `AFSVersion'
AFS_component_version_number.o(.data.rel.local+0x0): first defined here
collect2: ld returned 1 exit status make[4]: *** [pam_afs.so.1] Error 1
make[4]: Leaving directory `/foo/openafs-1.3.87/src/pam'=20
(sorry for the stupid wrapping; not sure how to turn it off in
evolution)
The problem is that AFS_component_version_number.o is being included
twice; one in the pam directory, the other in the shlibafsrpc directory.
The reason this happens is due to the following bit of code in
src/pam/Makefile (around line 67):
*linux*) \
$(CC) $(LDFLAGS) $(PAM_CFLAGS) -o $@ afs_setcred.o \
afs_auth.o afs_util.o $(SHOBJS) \
../shlibafsauthent/[a-z]*.o ../shlibafsrpc/[a-z]*.o=
\
$(MT_LIBS) -lpam -lresolv;;\
---------------------------------------
Received: (at 323582-close) by bugs.debian.org; 26 Aug 2005 17:40:14 +0000
>From [EMAIL PROTECTED] Fri Aug 26 10:40:14 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E8i3j-00060i-00; Fri, 26 Aug 2005 10:32:07 -0700
From: Russ Allbery <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#323582: fixed in openafs 1.4rc1-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 26 Aug 2005 10:32:07 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 4
Source: openafs
Source-Version: 1.4rc1-1
We believe that the bug you reported is fixed in the latest version of
openafs, which is due to be installed in the Debian FTP archive:
libopenafs-dev_1.4rc1-1_i386.deb
to pool/main/o/openafs/libopenafs-dev_1.4rc1-1_i386.deb
libpam-openafs-kaserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/libpam-openafs-kaserver_1.4rc1-1_i386.deb
openafs-client_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-client_1.4rc1-1_i386.deb
openafs-dbserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-dbserver_1.4rc1-1_i386.deb
openafs-fileserver_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-fileserver_1.4rc1-1_i386.deb
openafs-kpasswd_1.4rc1-1_i386.deb
to pool/main/o/openafs/openafs-kpasswd_1.4rc1-1_i386.deb
openafs-modules-source_1.4rc1-1_all.deb
to pool/main/o/openafs/openafs-modules-source_1.4rc1-1_all.deb
openafs_1.4rc1-1.diff.gz
to pool/main/o/openafs/openafs_1.4rc1-1.diff.gz
openafs_1.4rc1-1.dsc
to pool/main/o/openafs/openafs_1.4rc1-1.dsc
openafs_1.4rc1.orig.tar.gz
to pool/main/o/openafs/openafs_1.4rc1.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Russ Allbery <[EMAIL PROTECTED]> (supplier of updated openafs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 26 Aug 2005 01:30:21 -0700
Source: openafs
Binary: openafs-client libopenafs-dev openafs-dbserver openafs-modules-source
openafs-fileserver openafs-kpasswd libpam-openafs-kaserver
Architecture: source i386 all
Version: 1.4rc1-1
Distribution: unstable
Urgency: low
Maintainer: Sam Hartman <[EMAIL PROTECTED]>
Changed-By: Russ Allbery <[EMAIL PROTECTED]>
Description:
libopenafs-dev - The AFS distributed filesystem- development libraries
libpam-openafs-kaserver - The AFS distributed filesystem- kaserver PAM module
openafs-client - The AFS distributed filesystem- client support
openafs-dbserver - The AFS distributed filesystem- database server
openafs-fileserver - The AFS distributed filesystem- file server
openafs-kpasswd - The AFS distributed filesystem- old password changing
openafs-modules-source - The AFS distributed filesystem- Module Sources
Closes: 120097 249315 322638 323582 324694
Changes:
openafs (1.4rc1-1) unstable; urgency=low
.
* New upstream version.
* Install pam_afs.krb.so on hppa. I believe the new PAM module build
process fixes the issue that was being worked around before.
* Improve the documentation and scripts for setting up new servers or a
new cell. afs-rootvol can now be run from a client configured to use
dynroot. afs-newcell generates the server CellServDB directly to work
around oddities with bos addhost. There are many other, more minor
improvements as well. Thanks to Faheem Mitha and Sergio Gelato for
analysis and patches. (Closes: #322638)
* Update the configuration transcript to reflect the current packages,
messages, and instructions. Thanks, Faheem Mitha.
* Fill in the server CellServDB with information about the local cell,
if available in the client CellServDB, rather than always initializing
it to contain just the name of the cell.
* Detect AFS caches on non-ext2/ext3 file systems and abort AFS client
initialization. (Closes: #249315)
* Provide a way of setting sysname in afs.conf. (Closes: #324694)
* Don't create the unused /etc/openafs/AFSLog file. (Closes: #120097)
* Redo how library object files are found for the PAM module build to
avoid assuming C locale character set behavior. (Closes: #323582)
* Remove the openafs-client warning against dynroot for the first system
in a cell now that afs-rootvol can cope. Provide some basic
documentation of the CellAlias syntax in that message until we have a
real man page.
* Suggest openafs-doc.
* Update standards version to 3.6.2 for the kernel module packages (no
changes required).
* Translation updates.
- Czech, thanks Martin Sin.
- Vietnamese, thanks Clytie Siddall.
- French, thanks Christian Perrier.
Files:
6f73aebf36a64ab4cccf90267de52cf4 1108 net optional openafs_1.4rc1-1.dsc
8cac45d3fc3c0d63d68092fd9638ee69 4355767 net optional
openafs_1.4rc1.orig.tar.gz
1bc1c0820a608446f009053d5ac86189 115168 net optional openafs_1.4rc1-1.diff.gz
077ea2b10ad48b29261eeca1ce1ef45a 4469272 net extra
openafs-modules-source_1.4rc1-1_all.deb
948acee67bd91462ef4b2cbf13b06b08 1491022 net optional
openafs-client_1.4rc1-1_i386.deb
8eb36ac3b740ea0025369ec91eec6263 193674 net extra
openafs-kpasswd_1.4rc1-1_i386.deb
f3c14db41c5f0d81110fd4b9d29130ac 774976 net optional
openafs-fileserver_1.4rc1-1_i386.deb
4c457b6371e9813752f004bec3b01108 449610 net optional
openafs-dbserver_1.4rc1-1_i386.deb
d6a13c5639e29fc5e3fec8b9db3aa5bc 1128886 libdevel extra
libopenafs-dev_1.4rc1-1_i386.deb
d2488d4711afe347a71c13b666746901 396030 net extra
libpam-openafs-kaserver_1.4rc1-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iQEVAwUBQw9Qb7f2jhx5fmQdAQKBZQgAt1z5p6so2JuXwZnAwScUqnZXfvENSJB2
e8E4LTKAIUNOwlKiyaSLhQPR17jxBV6fvVBI0RZoQxe8R4OG1QoVNAJ6rLE9pWfD
LnA2fSSEFJNh4tea0444fLx7wG9Z0b37JawZp1FCZoy4llzbAJqfToHvwWHot/0c
DWlpGaww0NIJXuU0LgUP+BCBCyaAE7Zd7oJ0hb141xvwg/GCsMAOZHRo5rCRoKkL
OTdcw0EcG0Efe1z+IP9MgytWuGUyn6zDHhdkLSubp+MXp2oa2AsaJUFWIXhQRmXB
otnDFFWjgJ5IUI102ubWyuJWdDQTO7F4SeYyY4j8sKdPdjG1mqThrg==
=igG2
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
