On Tue, Dec 13, 2016 at 08:43:35AM +0000, Adam D. Barratt wrote:
> On 2016-12-12 20:25, Perl wrote:
> >    * What led up to the situation?
> >    I noticed, since long time ago, that I was not anymore able to use
> >    Apt-Pinning for installing packages from Stable and Testing Releases.
> >    * What exactly did you do (or not do) that was effective (or
> >      ineffective)?
> >      Everytime I try to use "APT-Pinning", I do not get what I want.
> >      Even if I try /testing or -t testing, or any Release other than
> >      Experimental, I only get error or Experimental list of packages.
> >      Finally, apt-cache policy only return Sid and Experimental
> > packages.
> >    * What was the outcome of this action?
> >      If I try
> >     "apt-cache show -t testing linux-image-amd64"
> >      OR
> >     "apt-cache show linux-image-amd64/testing"
> >      I get this with apt-get:
> >     E: Release 'testing' for 'linux-image-amd64' was not found
> >     E: No packages found
> 
> Well, the only testing sources.list entries listed in your report are:
> 
> > #Testing
> > deb-src http://ftp.fr.debian.org/debian/ testing main non-free contrib
> > deb-src http://ftp2.fr.debian.org/debian/ testing main contrib non-free
> 
> So I'm not sure where you're expecting apt to find information about
> *binary* packages in testing from.

I agree with this statement and I think we can close this bug because of it.

Cheers,
Wesley

Reply via email to