[Parted-maintainers] Bug#276887: libparted1.6-0: can't fulfill the Recommends in sarge

[Sven Luther]

On Mon, Oct 18, 2004 at 02:43:33PM +0200, Andreas Barth wrote:
> * Sven Luther (sven.luther@wanadoo.fr) [041018 14:30]:
> > On Sun, Oct 17, 2004 at 11:40:53PM +0200, Adrian Bunk wrote:
> > > On Sun, Oct 17, 2004 at 11:48:43PM +0200, Sven Luther wrote:
> > > > On Sun, Oct 17, 2004 at 12:54:14PM +0200, Adrian Bunk wrote:
> > > > > The recommends on libreiserfs0.3-0 can't be fulfilled in sarge.
> 
> > > > Is that not clear enough ? It is not a dependency nor build-dependency
> > > > anymore, and this should most assuredly be enough ? Mmm, maybe i could just as
> 
> > > A package management tool can handle Recommends like Depends to help 
> > > users (and section 2.2.1. of your policy treats Recommends similar to 
> > > Depends and Build-Depends).
> 
> > So, a Suggest would be ok then ? 
> 
> No. Either drop the relationship in total (and e.g. only document it in
> README.Reiserfs), or keep it as recommends. A broken binary relationship
> is always a bug, Depends is serious or grave, Recommends is important,
> and Suggests is normal or minor. So, either you fix that bug (and drop
> that relationship in total), or you don't fix it. (Of course,
> downgrading a bug from serious to important might make sense to allow a
> package to be in sarge, but at least I don't see the advantages of
> downgrading from important to normal.)

I will drop the dependency for now. That said, the real bug is that
libreiserfs was dropped. I have chatted a bit with the parted folk about this,
and there seems to be a newer libreiserfs upstream, which may fix the worries
we have with it. It seems to me the real trouble we had with the reiserfs
thingy was that the debian maiuntainer of it was MIA or something, and didn't
communicate with its upstream, which is why it was dropped. 

Could you as RM-assistant investigate a bit about this, and maybe we should
check if the new reiserfsporgs (or progreiserfs, i never remember which is the
right one) upstream would be fixed enough to consider it again
sarge-releasable or something ? With a new debian maintainer maybe, not me
though, as i scarcely use reiserfs.

> (See http://release.debian.org/sarge_rc_policy.txt for that broken
> recommends is not RC, but of course nevertheless a bug.)

Ok.

Friendly,

Sven Luther