On Thu, 18 Feb 1999, Wichert Akkerman wrote:
> Previously Santiago Vila wrote:
> > Thanks for answering. So: what's the right priority for a library in
> > slink for which an important package in slink depends on?
>
> Probably the same as the important package.
Well, apparently the ftp.debian.or
Previously Santiago Vila wrote:
> Thanks for answering. So: what's the right priority for a library in
> slink for which an important package in slink depends on?
Probably the same as the important package.
Wihert.
--
=
On Thu, 18 Feb 1999, Richard Braakman wrote:
> Wichert Akkerman wrote:
> > Previously Santiago Vila wrote:
> > > Is this to be considered "distribution-wise"?
> > > i.e. Is this to be applied to hamm, slink, potato, in an independent way?
> >
> > I think so, because packages that may be required
On Thu, 18 Feb 1999, Wichert Akkerman wrote:
> Previously Santiago Vila wrote:
> > Is this to be considered "distribution-wise"?
> > i.e. Is this to be applied to hamm, slink, potato, in an independent way?
>
> I think so, because packages that may be required in release N could
> be obsolete in
Maintainer: Debian Policy List
Severity: normal
Status: pending
This mail is being sent to you because the indicated bug reports have been
marked as overdue (i.e. has been open longer than 9 months). Overdue
reminders are repeated monthly.
#8221 debian-policy ispell suggests non-ex
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> Can you estimate the time you need to prepare this? Can I start to work out
> the details for a policy proposal?
First estimate how many packages are involved. If it's only a
handful, it's not worth it (yet).
Guy
Wichert Akkerman wrote:
> Previously Santiago Vila wrote:
> > Is this to be considered "distribution-wise"?
> > i.e. Is this to be applied to hamm, slink, potato, in an independent way?
>
> I think so, because packages that may be required in release N could
> be obsolete in release N+1 and deserv
Previously Santiago Vila wrote:
> Is this to be considered "distribution-wise"?
> i.e. Is this to be applied to hamm, slink, potato, in an independent way?
I think so, because packages that may be required in release N could
be obsolete in release N+1 and deserve a lower priority there.
Wichert (
8 matches
Mail list logo