Your message dated Sun, 18 Sep 2016 09:25:00 +0000
with message-id <c2186fae-e744-8e1f-4dc3-ab0124681...@thykier.net>
and subject line Re: Bug#822075: apt-file: Fails to install apt-file-2.5.4 due 
to requiring older perl-base-5.20
has caused the Debian Bug report #822075,
regarding apt-file: Fails to install apt-file-2.5.4 due to requiring older 
perl-base-5.20
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 ow...@bugs.debian.org
immediately.)


-- 
822075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-file
Version: 2.5.4
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,


Attempted to install apt-file package and got an error

On 2016/04/20, did a apt-get update/upgrade to ensure current up-to-date.

* What exactly did you do (or not do) that was effective (or ineffective)?

Executed the following command:

   apt-get install apt-file

* What was the outcome of this action?

Package did not install.  Output is:

sudo apt-get install apt-file
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 apt-file : Depends: libapt-pkg-perl but it is not going to be installed
            Depends: liblist-moreutils-perl but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
steve@arca:~/work/shockwave/jsunpack-n/depends/js-1.8.0-rc1-src/Linux_All_DBG.OBJ$
sudo apt-get install libapt-pkg-perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libapt-pkg-perl : Depends: perlapi-5.20.0
E: Unable to correct problems, you have held broken packages.


* What outcome did you expect instead?

apt-fail package to install successfully.



-- System Information:
Debian Release: stretch/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
On Thu, 21 Apr 2016 05:46:53 +0000 Niels Thykier <ni...@thykier.net> wrote:
> [...]
> > [...]
> > 
> > 
> > -- System Information:
> > Debian Release: stretch/sid
>                   ^^^^^^^^^^^
> 
> This information is inconsistent and probably the cause.
>  * It claims your system is a Stretch/sid
>  * But your sources are stable (Jessie)
> 
>                  vvvvvvvvvvvvv    vvvvvvvvvvvvvvvvvvvvv
> >   APT policy: (990, 'stable'), (500, 'stable-updates')
> > [...]
> 
> 
> If this is true, then you are system is not in a supported configuration
> (as you would have to downgrade packages).  This is not limited to
> apt-file, but to many packages.
> 
> For Stretch/sid, the current version of apt-file is 3.0, which is
> installable (provided you have Stretch or/and unstable as your primary
> release and enabled in your sources)
> 
> Thanks,
> ~Niels
> 
> 

Hi,

I am closing this as "not a bug" given the above and no follow ups since
then.

Thanks,
~Niels

--- End Message ---

Reply via email to