Your message dated Wed, 19 Jun 2013 09:30:03 +0200
with message-id <20130619073003.gc3...@piware.de>
and subject line Fwd: Bug#712726: Removed package(s) from unstable
has caused the Debian Bug report #701339,
regarding postgresql-8.4: ftbfs with GCC-4.8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
701339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:postgresql-8.4
Version: 8.4.16-1
Severity: important
Tags: sid jessie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.8

The package fails to build in a test rebuild on at least amd64 with
gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The
severity of this report may be raised before the jessie release.

  XXX

The full build log can be found at:
http://people.debian.org/~doko/logs-20130217/gcc48/postgresql-8.4_8.4.16-1_unstable_gcc48.log
The last lines of the build log are at the end of this report.

To build with GCC 4.8, either set CC=gcc-4.8 CXX=g++-4.8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ g++-4.7 g++-4.8 libc6-dev

The test rebuild was done with eglibc-2.17 and GCC-4.8, so some issues
might be caused by the updated glibc.

[...]
Hunk #1 succeeded at 328 (offset 2 lines).
patching file src/bin/initdb/initdb.c
Hunk #1 succeeded at 652 with fuzz 2 (offset 16 lines).
patching file src/bin/pg_ctl/pg_ctl.c
Hunk #1 succeeded at 1735 (offset 218 lines).
make[1]: Entering directory `/«PKGBUILDDIR»/src/test/regress'
make -C ../../../src/port all
make[2]: Entering directory `/«PKGBUILDDIR»/src/port'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/«PKGBUILDDIR»/src/port'
rm -rf ./testtablespace
mkdir ./testtablespace
./pg_regress --inputdir=. --dlpath=. --multibyte=SQL_ASCII 
--load-language=plpgsql  --temp-install=./tmp_check --top-builddir=../../.. 
--schedule=./parallel_schedule  numeric_big
============== creating temporary installation        ==============
============== initializing database system           ==============

pg_regress: initdb failed
Examine /«PKGBUILDDIR»/src/test/regress/log/initdb.log for the reason.
Command was: 
"/«PKGBUILDDIR»/src/test/regress/./tmp_check/install//usr/lib/postgresql/8.4/bin/initdb"
 -D "/«PKGBUILDDIR»/src/test/regress/./tmp_check/data" -L 
"/«PKGBUILDDIR»/src/test/regress/./tmp_check/install//usr/share/postgresql/8.4"
 --noclean > "/«PKGBUILDDIR»/src/test/regress/log/initdb.log" 2>&1
make[1]: *** [bigcheck] Error 2
make[1]: Leaving directory `/«PKGBUILDDIR»/src/test/regress'
patching file src/backend/main/main.c
Hunk #1 succeeded at 328 (offset 2 lines).
patching file src/bin/initdb/initdb.c
Hunk #1 succeeded at 652 with fuzz 2 (offset 16 lines).
patching file src/bin/pg_ctl/pg_ctl.c
Hunk #1 succeeded at 1735 (offset 218 lines).
********* regression.diffs *******
********* log/initdb.log *******
Running in noclean mode.  Mistakes will not be cleaned up.
The files belonging to this database system will be owned by user "root".
This user must also own the server process.

The database cluster will be initialized with locale C.
The default database encoding has accordingly been set to SQL_ASCII.
The default text search configuration will be set to "english".

creating directory /«PKGBUILDDIR»/src/test/regress/./tmp_check/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 24MB
creating configuration files ... ok
creating template1 database in 
/«PKGBUILDDIR»/src/test/regress/./tmp_check/data/base/1 ... ok
initializing pg_authid ... FATAL:  wrong number of index expressions
STATEMENT:  CREATE TRIGGER pg_sync_pg_database   AFTER INSERT OR UPDATE OR 
DELETE ON pg_database   FOR EACH STATEMENT EXECUTE PROCEDURE 
flatfile_update_trigger();
        
child process exited with exit code 1
initdb: data directory "/«PKGBUILDDIR»/src/test/regress/./tmp_check/data" not 
removed at user's request
make: *** [binary-predeb/postgresql-plperl-8.4] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit 
status 2

--- End Message ---
--- Begin Message ---
postgresql-8.4 has just been removed from unstable, so this can be
closed.

Martin

----- Forwarded message from Debian FTP Masters 
<ftpmas...@ftp-master.debian.org> -----

Date: Wed, 19 Jun 2013 07:17:48 +0000
From: Debian FTP Masters <ftpmas...@ftp-master.debian.org>
To: 712726-cl...@bugs.debian.org
Cc: postgresql-...@packages.qa.debian.org, postgresql-...@packages.debian.org
Subject: [Pkg-postgresql-public] Bug#712726: Removed package(s) from unstable
X-Spam-Status: No, score=-1.9 required=3.4 tests=BAYES_00,T_RP_MATCHES_RCVD 
autolearn=no version=3.3.2

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

postgresql-8.4 |   8.4.16-1 | source
postgresql-8.4 |   8.4.17-1 | source
postgresql-plperl-8.4 |   8.4.16-1 | hurd-i386
postgresql-plperl-8.4 |   8.4.17-1 | amd64, armel, armhf, i386, ia64, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc

------------------- Reason -------------------
RoM; Obsoleted by postgresql-9.1
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors (ftp.debian.org
included) until the next dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 712...@bugs.debian.org.

The full log for this bug can be viewed at http://bugs.debian.org/712726

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)

_______________________________________________
Pkg-postgresql-public mailing list
pkg-postgresql-pub...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

----- End forwarded message -----

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to