Re: Packages still in Potato

2002-04-18 Thread Bart Schuller
On Wed, Apr 17, 2002 at 09:39:12PM +0200, Peter Makholm wrote:
> If a package works, has no new upstream versions and doesn't get
> outdated policywise there is no need for a new version of the package
> just because we're making a new release.

The "making a release" may not be the best reason. But a regular
interval certainly is. One of my packages hasn't been updated since
potato. It turns out to no longer compile from source. however, that
kind of bug is typically only found when a buildd tries to build a new
version.

It's not enough for the packages to be able to run, they have to be
buildable as well. And because that depends on the state of the rest of
the system, we will have to test for it once in a while.

Bit rot really does exist.

-- 
Bart.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-17 Thread Carlos Laviola
David Starner ([EMAIL PROTECTED]) wrote:
> On Wed, Apr 17, 2002 at 09:39:12PM +0200, Peter Makholm wrote:
> > If a package works, has no new upstream versions and doesn't get
> > outdated policywise there is no need for a new version of the package
> > just because we're making a new release.
> 
> And what makes you think there has been no new upstream versions for all
> those packages? I know that mdate has had substaintially newer versions
> out for almost two years now.

RCS hasn't had a new upstream version in 7 years.

-- 
Carlos Laviola   <[EMAIL PROTECTED]>
Debian GNU/Linux 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-17 Thread Peter Makholm
David Starner <[EMAIL PROTECTED]> writes:

> And what makes you think there has been no new upstream versions for all
> those packages?

Nothing. I commented on you general opinion.

-- 
Emacs er det eneste moderne styresystem der ikke er multitrådet.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-17 Thread David Starner
On Wed, Apr 17, 2002 at 09:39:12PM +0200, Peter Makholm wrote:
> If a package works, has no new upstream versions and doesn't get
> outdated policywise there is no need for a new version of the package
> just because we're making a new release.

And what makes you think there has been no new upstream versions for all
those packages? I know that mdate has had substaintially newer versions
out for almost two years now.

-- 
David Starner - [EMAIL PROTECTED]
"It's not a habit; it's cool; I feel alive. 
If you don't have it you're on the other side." 
- K's Choice (probably referring to the Internet)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-17 Thread Peter Makholm
[EMAIL PROTECTED] (Otto Wyss) writes:

> IMO each package should at least once per release upload a status
> report. Also there was ample time for the transition of each package to

Disagreed. We should make package uploads just to make uploads.

If a package works, has no new upstream versions and doesn't get
outdated policywise there is no need for a new version of the package
just because we're making a new release.

(Well it might be impossible for a package in potato not being
policywise outdated)

-- 
Emacs er det eneste moderne styresystem der ikke er multitrådet.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-11 Thread Josip Rodin
On Wed, Apr 10, 2002 at 03:57:26PM -0400, Bob Hilliard wrote:
>  These packages have not needed any updates.
[...]
>   Is it really necessary to make a new upload, rather
> than copying or linking these packages to the pool?
> 
>  I will make a new upload before the woody release if it is
> necessary to do so.  Please let me know it this is required.

It's not necessary.

Otto's mails seem to be useful only as a way to find invalid "Maintainer:"
fields, because the good maintainers won't care and could only get misled
into thinking they need to upload, and the bad ones will ignore the mail
anyway.

-- 
 2. That which causes joy or happiness.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-11 Thread Paul Slootman
On Wed 10 Apr 2002, Bob Hilliard wrote:
> Otto Wyss <[EMAIL PROTECTED]> writes:
> 
> > Packages: dict-easton, dict-gazetteer, dict-hitchcock
>  
> > The listed packages are still located in the Potato directory,
> > possibly because there wasn't any update necessary during the full
> > Woody development phase, but maybe also because there is no interest
> > in these packages. So please check your packages and do an upload,
> > so they get into the pool, or orphan them so others can take over or
> > they get removed.
>  
> > Please inform me what you are doing or not doing. This way I may ask
> > others to do NMU's just in case.
> 
>  These packages have not needed any updates.  The last update was
> solely to add the /usr/share/doc directory.  I had not contemplated
> another upload until post-woody, when the /usr/doc symlink could be
> removed.  In previous releases (before the pool concept was adopted),
> the unstable directory contained symlinks to the unstable directory,
> and the last step before release was converting any remaining symlinks
> to hard links.  Is it really necessary to make a new upload, rather
> than copying or linking these packages to the pool?
> 
>  I will make a new upload before the woody release if it is
> necessary to do so.  Please let me know it this is required.

I got a similar message from him.
He hadn't done his research all that well either, as one of my packages
_had_ been uploaded since potato, but for some reason isn't built on arm
and hence isn't migrating to woody.

Besides, I'm fairly confident that packages won't silently disappear
from woody just because they're not currently in /pool/, the situation
isn't that different from earlier releases where the files were still in
the previous release's hierarchy, and were moved to the new release
hierarchy when that was released (or was it when it was frozen).

I'de hate to see a flurry of useless uploads just because of an
(incorrect) perceived threat to the packages' existence.


Paul Slootman


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Packages still in Potato

2002-04-10 Thread Bob Hilliard
Otto Wyss <[EMAIL PROTECTED]> writes:

> Packages: dict-easton, dict-gazetteer, dict-hitchcock
 
> The listed packages are still located in the Potato directory,
> possibly because there wasn't any update necessary during the full
> Woody development phase, but maybe also because there is no interest
> in these packages. So please check your packages and do an upload,
> so they get into the pool, or orphan them so others can take over or
> they get removed.
 
> Please inform me what you are doing or not doing. This way I may ask
> others to do NMU's just in case.

 These packages have not needed any updates.  The last update was
solely to add the /usr/share/doc directory.  I had not contemplated
another upload until post-woody, when the /usr/doc symlink could be
removed.  In previous releases (before the pool concept was adopted),
the unstable directory contained symlinks to the unstable directory,
and the last step before release was converting any remaining symlinks
to hard links.  Is it really necessary to make a new upload, rather
than copying or linking these packages to the pool?

 I will make a new upload before the woody release if it is
necessary to do so.  Please let me know it this is required.

Bob
-- 
   _
  |_)  _  |_   Robert D. Hilliard  <[EMAIL PROTECTED]>
  |_) (_) |_)  1294 S.W. Seagull Way   <[EMAIL PROTECTED]>
   Palm City, FL  USA  GPG Key ID: 390D6559 
   PGP Key ID: A8E40EB9



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]