[Pkg-postgresql-public] postgresql-q3c_1.5.0-3_amd64.changes is NEW
binary:postgresql-q3c is NEW. binary:postgresql-q3c is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processing of postgresql-q3c_1.5.0-3_amd64.changes
postgresql-q3c_1.5.0-3_amd64.changes uploaded successfully to localhost along with the files: postgresql-q3c_1.5.0-3.dsc postgresql-q3c_1.5.0-3.debian.tar.xz postgresql-q3c-dbgsym_1.5.0-3_amd64.deb postgresql-q3c_1.5.0-3_amd64.buildinfo postgresql-q3c_1.5.0-3_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] postgresql-10 10~rc1-1 MIGRATED to testing
FYI: The status of the postgresql-10 source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 10~rc1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] postgresql-common 185 MIGRATED to testing
FYI: The status of the postgresql-common source package in Debian's testing distribution has changed. Previous version: 184 Current version: 185 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] pgagent 3.4.1-5 MIGRATED to testing
FYI: The status of the pgagent source package in Debian's testing distribution has changed. Previous version: 3.4.1-4 Current version: 3.4.1-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] pglogical_2.0.1-1_amd64.changes is NEW
binary:postgresql-10-pglogical is NEW. binary:postgresql-10-pglogical is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processing of pglogical_2.0.1-1_amd64.changes
pglogical_2.0.1-1_amd64.changes uploaded successfully to localhost along with the files: pglogical_2.0.1-1.dsc pglogical_2.0.1.orig.tar.gz pglogical_2.0.1-1.debian.tar.xz pglogical_2.0.1-1_amd64.buildinfo postgresql-10-pglogical-dbgsym_2.0.1-1_amd64.deb postgresql-10-pglogical_2.0.1-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#876788: postgresql-q3c FTBFS with PostgreSQL 10
Source: postgresql-q3c
Version: 1.5.0-2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-q3c.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2017-09-05 19:02:30.0 -1200
+++ debian/control.chBILN 2017-09-23 12:16:00.910794389 -1200
@@ -11,17 +11,17 @@
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-q3c.git
Vcs-Git: https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-q3c.git
-Package: postgresql-9.6-q3c
+Package: postgresql-10-q3c
Architecture: any
-Depends: postgresql-9.6,
+Depends: postgresql-10,
${misc:Depends},
${shlibs:Depends}
-Description: PostgreSQL 9.6 extension used for indexing the sky
+Description: PostgreSQL 10 extension used for indexing the sky
Q3C, an extension for PostgreSQL, is designed for the work with large
astronomical catalogues or any catalogs of objects on the sphere.
.
This extension allows a user to perform fast circular, elliptical or
polygonal searches on the sky as well as fast cross-matches.
.
- This package provides a module for PostgreSQL 9.6.
+ This package provides a module for PostgreSQL 10.
Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
updatecontrol'.
If you are seeing this message in a buildd log, a sourceful upload is required.
/usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target
'debian/control' failed
make: *** [debian/control] Error 1
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] pglogical_2.0.1-1_source.changes REJECTED
Source-only uploads to NEW are not allowed. binary:postgresql-10-pglogical is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processing of pglogical_2.0.1-1_source.changes
/pglogical_2.0.1-1_source.changes is already present on target host: pglogical_2.0.1-1_source.buildinfo Either you already uploaded it, or someone else came first. Job pglogical_2.0.1-1_source.changes removed. Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processing of pglogical_2.0.1-1_source.changes
pglogical_2.0.1-1_source.changes uploaded successfully to localhost along with the files: pglogical_2.0.1-1.dsc pglogical_2.0.1.orig.tar.gz pglogical_2.0.1-1.debian.tar.xz pglogical_2.0.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Bug#857770: src:postgresql-debversion: please provide a unversioned binary package
Hi Christoph, On 23.09.2017 21:41, Christoph Berg wrote: > Re: Ole Streicher 2017-09-22 >> I would just do this for my own packages (pqsphere and q3c), which would >> allow to collect experiences; but ofcourse I don't want to shoot into >> your feet with the packaging at the postgresql site. > > The plan seems sensible, so please go ahead, it will be an interesting > experiment. The plethora of mini packages we have now isn't ideal. I just uploaded q3c as a single binary package. pgsphere will follow after some discussion with the main users (hi Markus :-) ) > My main concern is supporting upgrades cleanly. Imagine "your" package > had already been around in jessie, and the user had postgresql-9.4 + > postgresql-q3c installed where q3c provided the 9.4 extension. Now the > user upgrades to stretch, gets postgresql-9.6 installed (e.g. via > postgresql.deb), the 9.4 cluster will still work, but the upgraded > postgresql-q3c package from stretch suddenly doesn't provide the 9.4 > anymore, but only 9.6, rendering q3c broken in the 9.4 cluster. This can be addressed by introducing Postgresql-versioned Provides. If the q3c package would support f.e. 9.6 and 10, it can have Provides: postgresql-9.6-q3c, postgresql-10-q3c If you then need q3c for a specific version, you can install/depend on this specific version. This also allows a smooth transition between the multi-binary-package approach and the single binary package. This is already implemented in the uploaded version. > Maybe we could just claim that the user should upgrade their database > at the same time, and for many extensions this will not be a problem. > But for extensions providing datatypes (I think that includes q3c), > the .so module is needed for dumping the old data, so at least > dump-restore upgrades are affected. pg_upgrade should still work, > though. (Making pg_upgradecluster use that by default is another > story.) This may indeed need some work; however I need some advice here. Best regards Ole ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Hi Christoph, > > Is this really so bad for your usecase? It is certainly more vanilla > > and straightforward... reducing the bus number for these important > > packages! > > Not sure what you meant here. The package is maintained by the same > people independently from what the source format is. If you make your Debian packaging "native" it's just another hurdle for someone to get over when they want to hack or contribute to your package. Doing this in a generic way is almost always a better way simply for this reason/ > Do you want me to change it before it can pass NEW? No... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] pgpool2_3.6.6-2_amd64.changes is NEW
binary:postgresql-10-pgpool2 is NEW. binary:postgresql-10-pgpool2 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Processing of pgpool2_3.6.6-2_amd64.changes
pgpool2_3.6.6-2_amd64.changes uploaded successfully to localhost along with the files: pgpool2_3.6.6-2.dsc pgpool2_3.6.6.orig.tar.gz pgpool2_3.6.6-2.debian.tar.xz libpgpool-dev_3.6.6-2_amd64.deb libpgpool0_3.6.6-2_amd64.deb pgpool2-dbg_3.6.6-2_amd64.deb pgpool2_3.6.6-2_amd64.buildinfo pgpool2_3.6.6-2_amd64.deb postgresql-10-pgpool2_3.6.6-2_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Re: Chris Lamb 2017-09-25 <1506327842.2246848.1117103624.47cf3...@webmail.messagingengine.com> > Hi Christoph, > > > The deeper problem here is that "have debian/ inside upstream's git > > tree" is really a pain > > Indeed. My trade-offs of all the options *usually* results in going with > *not* including debian/ in upstream's (ie. my!) git and having foo.git > and pkg-foo.git. Having to merge stuff all the time is exactly what I mean by "pain" upthread. Making the package native instead makes builds from git Just Work. > Is this really so bad for your usecase? It is certainly more vanilla > and straightforward... reducing the bus number for these important > packages! Not sure what you meant here. The package is maintained by the same people independently from what the source format is. Do you want me to change it before it can pass NEW? Christoph ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Hi Christoph, > The deeper problem here is that "have debian/ inside upstream's git > tree" is really a pain Indeed. My trade-offs of all the options *usually* results in going with *not* including debian/ in upstream's (ie. my!) git and having foo.git and pkg-foo.git. Is this really so bad for your usecase? It is certainly more vanilla and straightforward... reducing the bus number for these important packages! Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Re: Chris Lamb 2017-09-25 <1506324211.2234630.1117054560.72a88...@webmail.messagingengine.com> > Hm. That seems wasteful.. But, outside of ftpmaster hat, are you really > really sure you want native packages for something that isn't Debian > specific? :) The deeper problem here is that "have debian/ inside upstream's git tree" is really a pain, unless the package is format 1.0 or 3.0 (native). Otherwise, (likely non-debian-savvy) upstreams will have a hard time building packages from HEAD because each time there's a change outside debian/, the build will fail because it doesn't match the tarball. Maybe I should make pg-dirtyread source format 1.0, and have it build the diff against the latest tarball (which still exists even for 3.0 (native) because of the archive.tar.gzs from GitHub) like in the old days. Christoph signature.asc Description: PGP signature ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
[Pkg-postgresql-public] Bug#876669: postgresql: cannot make standard postgresql clusters log to stderr or syslog
Re: Daniel Kahn Gillmor 2017-09-24 <150621934369.835.11298534420205898532.report...@alice.fifthhorseman.net> > So I'd like the cluster to log to stderr (or syslog), to have it not > have to contemplate log rotation at all. I've uncommented the > following in /etc/postgresql/9.6/main/postgresql.conf: > > log_destination = 'stderr' > logging_collector = off > > but this doesn't prevent the postgres process from re-opeing > /var/log/postgresql/postgresql-9.6-main.log. I've traced the startup > code as far as pg_ctlcluster to where it looks like it's enforcing the > logging to /var/log, but i can't figure out how to get it to stop. The log file on disk is necessary in many configurations because only elog() is redirected to the configured log destination, while things that print directly to stderr (most frequent offender would be errors from an archive_command) would otherwise get lost. Also, that file logs errors that occur before the logging config has been activated, like syntax errors in postgresql.conf. I realize that setups that really just want to catch stderr to feed it elsewhere have a problem here. > And pg_ctlcluster seems to define the active logging to the filesystem > as part of the "start" subcommand :/ Maybe we should add a switch to pg_ctl.conf, catch_stderr = on/off. > How can i get it to not write to these logs? Did you give 'syslog' a try, btw? It should mostly do what you want, until there is a proper fix. Christoph signature.asc Description: PGP signature ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Hi Christoph, > > Did you mean these pg-* packages to be native? If so, please explain why in > > the > > package :) > > I'm upstream now. Do you want a new upload with that explanation? Hm. That seems wasteful.. But, outside of ftpmaster hat, are you really really sure you want native packages for something that isn't Debian specific? :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes
Re: Chris Lamb 2017-09-24 > Did you mean these pg-* packages to be native? If so, please explain why in > the > package :) I'm upstream now. Do you want a new upload with that explanation? Christoph signature.asc Description: PGP signature ___ Pkg-postgresql-public mailing list Pkg-postgresql-public@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
