Your message dated Thu, 12 Jul 2007 15:36:38 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432467: subversion: svn co on ia64 fails with PROPFIND
errors but works just fine on i686
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: subversion
Version: 1.4.4dfsg1-1
Severity: grave
Justification: renders package unusable
The following command to get a copy of an SVN repository fails on
an ia64 system:
$ svn co http://llvm.org/svn/llvm-project/llvm/trunk anywhere
svn: PROPFIND request failed on '/svn/llvm-project/llvm/trunk'
svn: PROPFIND of '/svn/llvm-project/llvm/trunk': could not connect to server
(http://llvm.org)
On multiple i686 systems, also running sid, also running this version of
subversion, the exact same checkout works just fine. I've compared all
of the config files, and they are the same. Network access to the host
works on both ia64 _and_ i686 systems.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: ia64
Kernel: Linux 2.6.21-2-mckinley (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages subversion depends on:
ii libapr1 1.2.7-8.2 The Apache Portable Runtime Librar
ii libc6.1 2.5-11 GNU C Library: Shared libraries
ii libsvn1 1.4.4dfsg1-1 Shared libraries used by Subversio
subversion recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
[Al Stone]
> I had tried apt-get install --reinstall previously, too, and it
> seemed to think there was no need to change the config files.
That's normal, edited config files aren't touched on reinstall.
> If I can find them and reproduce the problem, I'll pass that on.
> In the meantime, I see no further reason to keep this bug open.
Right, closing. Reopen if you ever figure out how to reproduce the
problem (and it turns out not to be a bad http proxy setting or
something).
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
signature.asc
Description: Digital signature
--- End Message ---
