Your message dated Sun, 2 Jul 2006 13:11:16 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Close
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: apt-proxy
Severity: grave
Justification: renders package unusable
Package cannot by installed due to unme dependiences:
The following packages have unmet dependencies:
apt-proxy: Depends: python-twisted (>= 1.3.0-7) but it is not going to be
installed or
python2.3 (< 2.3.5-1) but 2.3.5-14 is to be installed
Depends: python-twisted (>= 1.0.0) but it is not going to be
installed
E: Broken packages
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-generic
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
--- End Message ---
--- Begin Message ---
Le juillet 2, 2006 06:56 AM, Bartosz Cisek a écrit :
> Filipus Klutiero wrote:
> > Are you sure this wouldn't be due to python-twisted being "uninstallable
> > on your system"?
>
> You might by right because several hours later I finaly installed
> apt-proxy on that system. I used diferent repository, one of
> amd64.debian.net mirror. I saw many other packages of python-twisted. I
> read in few posts that previous python-twisted package was splitted into
> smaller ones and that caused a problem.
>
> Strange that official repo didn't work.
Since this is most likely an amd64-specific bug opened against the wrong
package and the submitter can't reproduce anymore, I'm closing this bug. If
anyone using amd64 etch can reproduce this, please investigate which package
is causing this issue and open a bug against it if that's not already done.
--- End Message ---
