Your message dated Sat, 25 Jul 2009 22:56:03 +0200
with message-id <[email protected]>
and subject line 
has caused the Debian Bug report #517744,
regarding bzr fails to retrieve repository
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
517744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517744
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bzr
Version: 1.5-1.1
Severity: important
X-Debbugs-CC: [email protected]


I recently tried to retrieve a bzr branch (on amd64) but my bzr was
too old[1]. Now I have a ppc machine available which has the Lenny
version but still bzr fails to retrive:

he...@twotofive:/scr/build/debian/cups$ bzr get 
bzr://bzr.debian.org/pkg-cups/cups/lenny
bzr: ERROR: bzrlib.errors.ReadingCompleted: The MediumRequest 
'<bzrlib.smart.medium.SmartClientStreamMediumRequest object at 0x10700590>' has 
already had finish_reading called upon it - the request has been completed and 
no more data may be read.

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 846, in 
run_bzr_catch_errors
    return run_bzr(argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 797, in 
run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.5/site-packages/bzrlib/commands.py", line 499, in 
run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.5/site-packages/bzrlib/builtins.py", line 916, in run
    from_location)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 789, in 
open_tree_or_branch
    bzrdir = klass.open(location)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 667, in open
    return BzrDir.open_from_transport(t, _unsupported=_unsupported)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 704, in 
open_from_transport
    redirected)
  File "/usr/lib/python2.5/site-packages/bzrlib/lazy_import.py", line 125, in 
__call__
    return obj(*args, **kwargs)
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/__init__.py", line 
1616, in do_catching_redirections
    return action(transport)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 681, in 
find_format
    transport, _server_formats=_server_formats)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 1440, in 
find_format
    return format.probe_transport(transport)
  File "/usr/lib/python2.5/site-packages/bzrlib/bzrdir.py", line 1450, in 
probe_transport
    format_string = transport.get(".bzr/branch-format").read()
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/remote.py", line 189, 
in get
    return StringIO(self.get_bytes(relpath))
  File "/usr/lib/python2.5/site-packages/bzrlib/transport/remote.py", line 200, 
in get_bytes
    return smart_protocol.read_body_bytes()
  File "/usr/lib/python2.5/site-packages/bzrlib/smart/protocol.py", line 590, 
in read_body_bytes
    bytes = self._request.read_bytes(bytes_wanted)
  File "/usr/lib/python2.5/site-packages/bzrlib/smart/medium.py", line 370, in 
read_bytes
    raise errors.ReadingCompleted(self)
ReadingCompleted: The MediumRequest 
'<bzrlib.smart.medium.SmartClientStreamMediumRequest object at 0x10700590>' has 
already had finish_reading called upon it - the request has been completed and 
no more data may be read.

bzr 1.5 on python 2.5.2 (linux2)
arguments: ['/usr/bin/bzr', 'get', 'bzr://bzr.debian.org/pkg-cups/cups/lenny']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'de_DE.UTF-8'
plugins:
  launchpad            
/usr/lib/python2.5/site-packages/bzrlib/plugins/launchpad [unknown]
*** Bazaar has encountered an internal error.
    Please report a bug at https://bugs.launchpad.net/bzr/+filebug
    including this traceback, and a description of what you
    were doing when the error occurred.


I tried this with various variations (I intially tried to get the trunk, which 
is at 
http://bzr.debian.org/pkg-cups/cups/debian-trunk/, but here bzr fails as well:
bzr: ERROR: Transport error: Server refuses to fullfil the request
and replacing http->bzr yield again the same (or very similar) error).

So either I'm obviously making something very stupid wrong (but then
I'd expect some kind of error message) or bzr is broken in lenny
(which I can't belive). In the latter case the severity should be
raised, of course.

[1] See bugs.debian.org/502908 

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.24.3-grsec
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bzr depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  python                        2.5.2-3    An interactive high-level object-o
ii  python-central                0.6.8      register and build utility for Pyt

Versions of packages bzr recommends:
pn  bzrtools                      <none>     (no description available)
pn  python-paramiko               <none>     (no description available)

Versions of packages bzr suggests:
pn  bzr-gtk                       <none>     (no description available)
pn  bzr-svn                       <none>     (no description available)
pn  python-pycurl                 <none>     (no description available)
ii  xdg-utils                     1.0.2-6.1  desktop integration utilities from

-- no debconf information
-- 
      Dr. Helge Kreutzmann                     [email protected]
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
This strange error message has since been improved upstream. You
should now just get a warning when opening the log file is failing
server side, rather than a confusing client-side error.


--- End Message ---

Reply via email to