Re: moreutils in sarge-backports newer than in etch

[Martin Zobel-Helas <zobel@ftbfs.de>]

Hi, 

On Mon Apr 16, 2007 at 17:10:18 +0200, Alexander Wirt wrote:
> Nikita V. Youshchenko schrieb am Montag, den 16. April 2007:
> 
> > > ..can, will or should anything be done about this?
> > > 
> > > As etch is released now, it won't likely get a moreutils-0.20...
> > > But I guess those who have already installed 0.20~bpo1 can't be helped
> > > by a change in the bpo archive anyhow...
> > 
> > I think that sarge-backports archive should be split into two.
> > One for systems that are intended to be upgraded to etch somewhen later.
> > This part should not have any packages newer than etch has.
> > Other for systems are not intended to be upgraded to etch. This one may have
> > things from current testing.
> We discussed this and the short answer is no. We don't want to administrate
> another suite. You will have to live with the problem that from now on
> sarge-bpo may destory your upgrade path to etch. I currently don't see any
> other solution. 

well, if you have an internal suite (not published to the outside)
with package information from etch and sarge, you could have the
following in dak.conf:

| VersionChecks
| {
|   MustBeNewerThan
|   {
|     Sarge;
|   };
|   MustBeOlderThan
|   {
|     Etch;
|     Unstable;
|     Experimental;
|   };
| };

Greetings
Martin

-- 
[root@debian /root]# man real-life
No manual entry for real-life