Re: postgresql buggy
On Mon, Oct 21, 2002 at 03:52:16PM +0200, Stefano Zacchiroli wrote:
> On Mon, Oct 21, 2002 at 02:37:25PM +0200, J?r?me Marant wrote:
> > I guess libpgsql2 is broken on sparc.
>
> I guess it, too, but seemed to me that Sven was a bit more informed
> about our guessing ;)
> Maybe I'm wrong ...
Ok, the info i have is as follows :
looking at the pts for postgresql :
# 3 days old (needed 2 days)
# postgresql (source, alpha, arm, hppa, i386, ia64, m68k, mips,
mipsel, powerpc, s390, sparc) is buggy! (4 > 0)
# Not considered
# Depends: postgresql perl
# Depends: postgresql pam
# Depends: postgresql python2.2
This is for 7.2.3-0.2, which was NMUed 3 days ago, as the maintainer
has told me. I don't really know all that much more, but looking at the
buildd logs, i get :
* 7.2.3-0.2 (alpha) (latest build at Oct 16 05:41: successful)
* 7.2.3-0.2 (hppa) (latest build at Oct 16 05:50: successful)
* 7.2.3-0.2 (powerpc) (latest build at Oct 16 05:46: successful)
* 7.2.3-0.2 (ia64) (latest build at Oct 16 05:52: successful)
* 7.2.3-0.2 (s390) (latest build at Oct 16 05:56: successful)
* 7.2.3-0.2 (sparc) (latest build at Oct 16 05:57: successful)
* 7.2.3-0.2 (m68k) (latest build at Oct 16 12:26: successful)
* 7.2.3-0.2 (mipsel) (latest build at Oct 16 09:16: successful)
* 7.2.3-0.2 (mips) (latest build at Oct 17 09:42: successful)
* 7.2.3-0.2 (arm) (latest build at Oct 17 13:01: successful)
So, This mean that 7.2.3-0.2 was built on all the arches sucessfully.
Looking at the archives, i have :
lftp ftp.debian.org:/debian/pool/main/p/postgresql> ls -l libpgsql2_7.2.3-0.2*
-rw-rw-r-- 1 1176 1176 77806 Oct 16 10:02 libpgsql2_7.2.3-0.2_alpha.deb
-rw-rw-r-- 1 1176 1176 66052 Oct 17 18:02 libpgsql2_7.2.3-0.2_arm.deb
-rw-rw-r-- 1 1176 1176 77958 Oct 16 13:17 libpgsql2_7.2.3-0.2_hppa.deb
-rw-rw-r-- 1 1176 1176 66372 Oct 16 08:32 libpgsql2_7.2.3-0.2_i386.deb
-rw-rw-r-- 1 1176 1176 90786 Oct 16 15:32 libpgsql2_7.2.3-0.2_ia64.deb
-rw-rw-r-- 1 1176 1176 66150 Oct 16 16:32 libpgsql2_7.2.3-0.2_m68k.deb
-rw-rw-r-- 1 1176 1176 65558 Oct 17 18:02 libpgsql2_7.2.3-0.2_mips.deb
-rw-rw-r-- 1 1176 1176 65152 Oct 16 20:04 libpgsql2_7.2.3-0.2_mipsel.deb
-rw-rw-r-- 1 1176 1176 67996 Oct 16 10:32 libpgsql2_7.2.3-0.2_powerpc.deb
-rw-rw-r-- 1 1176 1176 68640 Oct 16 17:17 libpgsql2_7.2.3-0.2_s390.deb
-rw-rw-r-- 1 1176 1176 67728 Oct 16 11:17 libpgsql2_7.2.3-0.2_sparc.deb
So, the package is available on all arches.
The problem you encounter on sparc is not due to this, i think, but may
be more specific, you better check it yourself, in case it is an
incompatibility with libpgsql2 version 7.2.3 or something such.
Anyway, there are many open bugs, 7 release critical bugs and and 6
important ones, which i guess are the ones stopping postgresql of
entering testing. Many of those bugs are many days old, almost a year.
They are :
Grave functionality bugs - outstanding
(A list of all such bugs used to be available).
* #155419: postgresql: buffer overflow in date/time routines
Package: postgresql; Severity: grave; Reported by: "Florian
Weimer" <Weimer@CERT.Uni-Stuttgart.DE>; Tags: security, upstream, woody;
77 days old.
* #157306: postgresql from stable fails to install.
Package: postgresql; Severity: grave; Reported by: rich walker
<rw@shadow.org.uk>; Tags: woody; 62 days old.
* #160470: postgres upgrade report
Package: postgresql; Severity: grave; Reported by: Peter Palfrader
<weasel@debian.org>; merged with #160476; 40 days old.
* #160476: postgres upgrade report
Package: postgresql; Severity: grave; Reported by: Peter Palfrader
<weasel@debian.org>; merged with #160470; 40 days old.
* #160673: postgresql: OPAQUE security problem
Package: postgresql; Severity: grave; Reported by: "Florian
Weimer" <Weimer@CERT.Uni-Stuttgart.DE>; Tags: security, upstream; 38 days old.
* #165060: postgresql: int8 value out of range on sparc
Package: postgresql; Severity: grave; Reported by: Brian Macy
<bmacy@macykids.net>; Tags: sid, upstream.
Serious policy violations - outstanding
(A list of all such bugs used to be available).
* #157765: postgresql_7.2.1-4(powerpc/unstable): FTBFS: missing chmod +x
Package: postgresql; Severity: serious; Reported by:
rmurray@cyberhqz.com (Ryan Murray); 60 days old.
Important bugs - outstanding
(A list of all such bugs used to be available).
* #134897: upgrade needs to cope with incorrect old binaries
Package: postgresql; Severity: important; Reported by:
debian-bugreports-20020220@ira.abramov.org; 242 days old.
* #136574: postgresql: Broken 7.1->7.2 upgrade when user has NOCREATEDB
Package: postgresql; Severity: important; Reported by: "J.H.M.
Dassen" <dm@zensunni.demon.nl>; 232 days old.
* #143677: postgresql: pg_restore unable to import pg_dump database with encoding = UNICODE
Package: postgresql; Severity: important; Reported by: JP
Sugarbroad <taral@taral.net>; 184 days old.
* #146926: Testing for 'NULL' changes with silent failure between
7.1 and 7.2; likely to be mistaken for data corruption on upgrade
Package: postgresql; Severity: important; Reported by: Mike Bilow
<mike@bilow.com>; Tags: patch; 160 days old.
* #152295: python-pygresql: Two problems with python and postgresql:
Package: python-pygresql; Severity: important; Reported by: Martin
Lesser <m-lesser@better-com.de>; 104 days old.
* #161815: postgresql: pg_dump crashes while dumping a view
Package: postgresql; Severity: important; Reported by: "Michael Bravo"
<mbravo@tag-ltd.spb.ru>; Tags: patch, upstream; 29 days old.
I guess some of these bugs are old, some may even be closable, and so
on. That said, the testing excuses file speaks about 4 bugs that are new
to 7.2.3 over the testing packages. These are those needing fixed.
Ok, i really don't know more about this, Stefano, maybe you could ask
the maintainer or NMUer about those ?
BTW, i will make a new upload of ocaml, to fix the __ctype_b bug.
Friendly,
Sven Luther
Reply to: