On Fri, Mar 09, 2001 at 07:44:11PM +0100, Martin Schulze wrote:
> zope        updates   2.8-15.3     arm, i386, m68k, powerpc, sparc
>       Security update, DSA 041
>       Packages uploaded, waiting for dinstall

zope 2.1.6-7 is the latest in proposed-updated, 2.3.0-4 is the latest in
unstable. There's some sort of typo there, dunno what. The security team
uploaded 2.1.6-5.3 and -5.4, -6 and -7 were uploaded by the maintainer. The
latter has the lovely reassuring comment:

   * Include Hotfix_2001-02-23, Hotfix_2000-10-11, Hotfix_2000-10-02
     and Hotfix_08_09_2000. I hope they don't have bad side-effects in
     this ancient 2.1.6 version.

-7 is on security.d.o. So I'll assume that's what you meant. Actually, no
need to assume, you mention it later. Dunno what the above was meant to be
at all then.

> nextaw      updates   0.5.1-34potato1  i386, m68k
> nextawg     updates   0.5.1-34potato1  i386, m68k
> xaw3dg-dev  updates   1.3-6.9potato1   i386, m68k
> xaw3dg      updates   1.3-6.9potato1   i386, m68k
> xaw3d       updates   1.3-6.9potato1   i386, m68k
> xaw3dg-dev  updates   1.3-6.9potato1   i386, m68k
> xaw3dg      updates   1.3-6.9potato1   i386, m68k
> xaw3d       updates   1.3-6.9potato1   i386, m68k
>       Security update, DSA 037

The sparc autobuilder built this too, but it doesn't appear to have
made it to security.d.o, and maybe it should? I'll assume it goes in too
as far as r3 is concerned.

> ecpg                updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> libpgperl           updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> libpgsql2           updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> libpgtcl            updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> odbc-postgresql     updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> pgaccess            updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql-client   updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql-contrib  updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql-dev      updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql-doc      updates   6.5.3-25    all
> postgresql-pl       updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql-test     updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> postgresql          updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc
> python-pygresql     updates   6.5.3-25    alpha, arm, i386, m68k, powerpc, 
> sparc

postgresql 6.5.3-25 has been replaced by 6.5.3-26 on i386, m68k and
powerpc. Not sure offhand if it's better to resurrect the -25 debs from
the morgue.

> proftpd     updates   1.2.0pre10-2.0potato1    arm, i386, m68k, sparc
> proftpd     updates   1.2.0pre10-2.0potato1.1  powerpc

proftpd -2.0potato1 is an NMU by Ivo Timmermans, that fixes a string format
                    buffer attack, changes the user/group it runs as and
                    does some other random things.
proftpd -2potato1 is a security upload by Michael Stone, fixing a string
                  format problem, and USER and SIZE memory leaks.

the -2.0potato1 is what's actually in the archive, but doesn't appear to
be based on mstone's upload according to the changelog. Both appear to
have made it onto security.d.o, so I guess we just go with the -2.0potato1
version. Dodgy.

> Rejected packages
> -----------------

> distributed-net         updates   2.8012-potato3  i386, powerpc, sparc
>       No security update
>       Changelog doesn't make me believe that these fixes have to go
>       into stable.  It's contrib anyway.

It's actually non-free, not contrib. The maintainer says that we ought to
be doing this in order to be allowed to distribute it at all; I'm inclined
to allow that in. (In any event, it's non-free, so it doesn't much matter
if it breaks things)

> ibcs-base        stable    981105-1    i386
> ibcs-base        updates   981105-1    sparc
> 
>       Get versions in sync

This was in the Reject half of your email, I guess because ibcs-base wasn't
available for sparc in stable previously. I'm inclined to let it in anyway.
At the very least, the same package is in testing/unstable and doesn't seem
to have generated any huge number of bugs.

> watchdog           updates   5.1-2       arm, i386, m68k, powerpc, sparc
> 
>       I'm not convinced by this changelog why it should go into stable:
> 
>       * Uploaded to stable, adds --noscripts to debhelper invocation, closes:
>         #53298, #61939 (grave).
> 
>       alpha version still missing
> 
>       Maintainer: Johnie Ingram <[EMAIL PROTECTED]>

61939 seems to indicate that upgrades to 5.1-0.3 can potentially crash the
machine because the watchdog daemon gets disabled. That's probably a decent
reason.

> xcal        updates   4.1-9       alpha, i386, powerpc, sparc
>       Misplaced upload, mentions 'stable unstable', changelog says:
>       * closes Bug#80504 (pscal gets January 2001 wrong!)
>       * cleaned up debian/ directory and updated standards
>       arm and m68k missing
>       Maintainer: [EMAIL PROTECTED]

arm's not missing anymore; a calendar program getting days of a month wrong
seems a decent thing to fix.

> xtide       updates   2.2a-1      i386, m68k, powerpc, sparc
>       I don't see a reason why this package should make it into stable.  
> Changelog:
> 
>       * The Debian source archive xtide_2.2.orig.tar.gz was not pristine and
>         included tidal harmonics data downloaded from the XTide web site.
>         It was recently discovered that some of the data included in the above
>         archive may be in violation of copyright.  Therefore, XTide's author
>         removed the data in question from his web site and produced new
>         harmonics files which were included in this 2.2a Debian version.

Copyright violations seem a good reason to pull/fix a package.

> yaboot      updates   0.9-0.30-3  powerpc
>       Misplaced upload, mentions "stable unstable"

It's an upload of a powerpc specific package made by Dan J, though.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

``_Any_ increase in interface difficulty, in exchange for a benefit you
  do not understand, cannot perceive, or don't care about, is too much.''
                      -- John S. Novak, III (The Humblest Man on the Net)

Reply via email to