[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#441178: "apt-get -t etch source nano" fetches nano from lenny instead of etch



Package: apt
Version: 0.6.46.4-0.1
Severity: normal

Steps to preproduce:
1) On a debian etch system place the following to /etc/apt/sources.list
deb http://ftp.fi.debian.org/debian/ etch main
deb http://security.debian.org/ etch/updates main
deb-src http://ftp.fi.debian.org/debian sarge main
deb-src http://ftp.fi.debian.org/debian etch main
deb-src http://ftp.fi.debian.org/debian lenny main
deb-src http://ftp.fi.debian.org/debian sid main
2) sudo apt-get update
3) apt-get -t etch source nano

Expected results:
3) apt-get fetches the source code of nano in etch.

Actual results:
3) apt-get fetches the source code of nano in lenny:

$ apt-get -t etch source nano
Reading package lists... Done
Building dependency tree... Done
Need to get 1340kB of source archives.
Get:1 http://ftp.fi.debian.org lenny/main nano 2.0.6-2 (dsc) [701B]
Get:2 http://ftp.fi.debian.org lenny/main nano 2.0.6-2 (tar) [1315kB]
Get:3 http://ftp.fi.debian.org lenny/main nano 2.0.6-2 (diff) [23.9kB]
Fetched 1340kB in 0s (7498kB/s)
dpkg-source: extracting nano in nano-2.0.6
dpkg-source: unpacking nano_2.0.6.orig.tar.gz
dpkg-source: applying ./nano_2.0.6-2.diff.gz

More info:
1) This bug was earlier reported in a comment to 152129. When that bug
got closed I was asked to report it as a new bug.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)

Versions of packages apt depends on:
ii  debian-archive-keyring 2007.07.31~etch1  GnuPG archive keys of the Debian a
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  libgcc1                1:4.1.1-21        GCC support library
ii  libstdc++6             4.1.1-21          The GNU Standard C++ Library v3

apt recommends no packages.

-- no debconf information



Reply to: