Re: Bug#207932: Consequences of moving Emacs Manuals to non-free

Selon Peter S Galbraith <[EMAIL PROTECTED]>: > Has anything been uploaded? Not yet. We have just finished to review every file from the etc directory with the help of debian-legal, so we can take the opportunity to move some of them to non-free along with GFDL docs. -- Jérôme Marant -- To UNS

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> writes: > OK. So should I just give Gnus a version consistent with > internal versions, and call it Gnus 5.11.004 ? That might work in practice (because no released Gnus will ever have version 5.11.x), but conceptually it seems wrong because No Gnus is

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> writes: > So, we have either forcing people running Sid's Gnus to > downgrade from No Gnus 0.3+ to 5.10.8, of ship an unreleased version > and complicate versioning for future releases. Not a clean path > going forward. I am inclined to continue to s

Re: Bug#207932: Consequences of moving Emacs Manuals to non-free

J�r�me Marant <[EMAIL PROTECTED]> wrote: > Selon Sven Joachim <[EMAIL PROTECTED]>: > > > The release team has published a file which lists the release policy for > > etch on . This file states > > > > Packages in main cannot require any software

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> writes: > Hi, > > Upstream is planning on releasing Gnus 5.10.8, and No Gnus > version 0.4, in a couple of days. I am soliciting comments on how > Gnus packaging should be done for Debian. > > Sid already contains No guns 0.3, but sets the ve

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> wrote: > On 4 Apr 2006, Aaron M. Ucko told this: > > > Manoj Srivastava <[EMAIL PROTECTED]> writes: > > > >> So, we have either forcing people running Sid's Gnus to downgrade > >> from No Gnus 0.3+ to 5.10.8, of ship an unreleased version and > >> complicate v

Re: schedules Gnus releases

On 4 Apr 2006, Peter S. Galbraith stated: > Manoj Srivastava <[EMAIL PROTECTED]> wrote: > >> Upstream is planning on releasing Gnus 5.10.8, and No Gnus >> version 0.4, in a couple of days. I am soliciting comments on how >> Gnus packaging should be done for Debian. >> >> Sid already contains No g

Re: schedules Gnus releases

On 4 Apr 2006, Aaron M. Ucko told this: > Manoj Srivastava <[EMAIL PROTECTED]> writes: > >> So, we have either forcing people running Sid's Gnus to downgrade >> from No Gnus 0.3+ to 5.10.8, of ship an unreleased version and >> complicate versioning for future releases. Not a clean path going >> f

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> writes: > So, we have either forcing people running Sid's Gnus to > downgrade from No Gnus 0.3+ to 5.10.8, of ship an unreleased version > and complicate versioning for future releases. Not a clean path > going forward. I am inclined to continue to

Re: schedules Gnus releases

Manoj Srivastava <[EMAIL PROTECTED]> wrote: > Upstream is planning on releasing Gnus 5.10.8, and No Gnus > version 0.4, in a couple of days. I am soliciting comments on how > Gnus packaging should be done for Debian. > > Sid already contains No guns 0.3, but sets the version as

schedules Gnus releases

Hi, Upstream is planning on releasing Gnus 5.10.8, and No Gnus version 0.4, in a couple of days. I am soliciting comments on how Gnus packaging should be done for Debian. Sid already contains No guns 0.3, but sets the version as 5.10.6+ . Shipping Gnus 5.10.8 would essentiall

Re: Bug#207932: Consequences of moving Emacs Manuals to non-free

Selon Sven Joachim <[EMAIL PROTECTED]>: > The release team has published a file which lists the release policy for > etch on . This file states > > Packages in main cannot require any software outside of main > for execution or compilation

Re: Bug#207932: Consequences of moving Emacs Manuals to non-free

On Fri, Mar 17 2006, Davide G. M. Salvetti wrote: MS == Manoj Srivastava [2006-3-16] MS> Depends is too strong a relationship; if I have several machines in MS> my LAN, I may only keep extensive documentation on one of them, and MS> use NFS to share share-able directories. I would be annoyed i