Re: Can I stay in testing without going etch?
On Thu, May 18, 2006 at 06:17:38PM +0100, Adam Hardy wrote:
> Chris Brotherton on 18/05/06 16:38, wrote:
> >>>IMHO, its better to pre-empt that by pointing to etch instead of
> >>>testing. then when etch ebcomes stable, you'll stabilise and can
> >>>decide on your own when to brave the churning in testing. And I
> >>>suspect that's a lot easier than trying to go through a downgrade
> >>>process.
> >>You mean 'testing' and 'etch' are interchangeable as far as the
> >>sources.list entry goes?
> >>
> >Right now yes, but they won't be once etch is released.
>
> I changed testing to etch in my sources.list and got this error:
>
> W: Couldn't stat source package list http://security.debian.org
> etch/updates/main Packages
> (/var/lib/apt/lists/security.debian.org_dists_etch_updates_main_binary-i386_Packages) - stat (2 No such file or directory)
> W: Couldn't stat source package list http://ftp.debian.skynet.be etch/main
> Packages
> (/var/lib/apt/lists/ftp.debian.skynet.be_ftp_debian_dists_etch_main_binary-i386_Packages) - stat (2 No such file or directory)
> W: Couldn't stat source package list http://ftp.uk.debian.org etch/main
> Packages
> (/var/lib/apt/lists/ftp.uk.debian.org_debian_dists_etch_main_binary-i386_Packages) - stat (2 No such file or directory)
> W: Couldn't stat source package list http://security.debian.org
> etch/updates/main Packages
> (/var/lib/apt/lists/security.debian.org_dists_etch_updates_main_binary-i386_Packages) - stat (2 No such file or directory)
> W: Couldn't stat source package list http://ftp.debian.skynet.be etch/main
> Packages
> (/var/lib/apt/lists/ftp.debian.skynet.be_ftp_debian_dists_etch_main_binary-i386_Packages) - stat (2 No such file or directory)
> W: Couldn't stat source package list http://ftp.uk.debian.org etch/main
> Packages
> (/var/lib/apt/lists/ftp.uk.debian.org_debian_dists_etch_main_binary-i386_Packages) - stat (2 No such file or directory)
>
This is a well known feature of the apt-get/aptitude system. There is a way of supressing
these error message that can be found in the archives, but which I cannot recall. A crude
fix is to simply do apt-get update twice each time you change sources.list. You will find
that the error message never occurs on the *second* update.
Hopefully, someone else following this thread will contribute an explanation of why this
messages happens, and/or the details of what needs to be done to suppress it. For me,
it is a minor annoyance that only happens when I edit my sources.list
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: