Back in 2014 I wrote:
> I request assistance with maintaining the pgpool2 package in the
> PostgreSQL team. I'm not using the package myself - someone with more
> experience in actually running pgpool2 would be welcome to take care
> of getting the more advanced features (e.g. memcached support) in
, Andres Freund)
While unlikely, a SIGSEGV crash could occur if an incomplete multibyte
character appeared at the end of memory. This was possible both in the
server and in libpq-using applications. (CVE-2025-4207)
-- Christoph Berg Tue, 06 May 2025 17:55:19 +0200
Christoph
@@
+postgresql-common (278) unstable; urgency=medium
+
+ * pg_upgradecluster: Do two vacuumdb runs in analyze hook for PG18+.
+ * t/040_upgrade.t: Verify presence of stats after upgrade.
+ * pg_virtualenv: Adjust to extension_control_path change in PG18.
+
+ -- Christoph Berg Wed, 07 May 2025 17:58:33
@@
+svxlink (24.02-5) unstable; urgency=medium
+
+ * Revert dh_installsysusers change, was not tested enough.
+ * Pre-Depend on adduser instead. (Closes: #1104571)
+
+ -- Christoph Berg Wed, 14 May 2025 20:47:33 +
+
+svxlink (24.02-4) unstable; urgency=medium
+
+ * Drop adduser from preinst scripts
Re: Raphael Hertzog
> How can we determine if the collation information has changed between
> two glibc releases? (cc Aurélien in case he knows)
The problem is, no one knows. Or else PG would already use that info.
You could alternatively use the libicu collations, but these have
effectively the
Re: Raphael Hertzog
> I think it would be nice if that operation could be automated.
> With dpkg triggers, it's easy to schedule a script on the postgresql
> package side when libc6 (or locales?) gets upgraded. We can record the
> libc6 version at installation time, and compare the version in the t
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: postgresql-filed...@packages.debian.org
Control: affects -1 + src:postgresql-filedump
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package postgresql-filedump
It was removed from testing because I had acti
Re: AKASH
>Security & Efficiency: Runs only with sudo, minimizing privilege
>escalations.
I have no words for this.
Christoph
Re: AKASH
> I have been exploring an issue where pg_lsclusters reports the default port
> from postgresql.conf, rather than the actual port in use when a PostgreSQL
> cluster is started with a custom port using pg_ctlcluster (e.g., -o "-p <
> port>").
Can you explain why you need to use these comm
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgboun...@packages.debian.org
Control: affects -1 + src:pgbouncer
User: ftp.debian@packages.debian.org
Usertags: remove
User: debian-...@lists.debian.org
Usertags: armel armhf
User: debian...@lists.debian.org
Usertags: i386
Please remove p
> === BEGIN
>
> A: Christoph Berg
> B: Helmut Grohne
> C: Matthew Garrett
> D: Stefano Rivera
> E: Timo Röhling
> F: Craig Small
> G: Paul Tagliamonte
> H: Matthew Vernon
>
> === END
I vote
H > A = B = C = D = E = F > G
Christoph
signature.asc
Description: PGP signature
Re: Matthew Vernon
> ===BEGIN
> The Technical Committee recommends that Paul Tagliamonte (paultag) be
> appointed by the Debian Project Leader to the Technical Committee.
>
> H: Recommend to Appoint Paul Tagliamonte (paultag)
> F: Further Discussion
> ===END
I vote
H = P > F
Christoph
signa
Re: Chris Hofstaedtler
> https://ci.debian.net/packages/p/postgresql-17/unstable/amd64/58514314/
Hi Chris,
I think this is noise, sometimes the "cleanup" test is still seeing
zombie processes that would usually be reaped the milliseconds before.
734s # Cleanup
735s ok 21 - Cleanup: No clusters l
Re: Anja
> My understanding is that "legitimate interests" requires a straightforward
> opt-out mechanism (which VisiData does provide), but doesn't require
> opt-in. We're going to ensure we meet legitimate interests compliance.
The GDPR mandates privacy by default, so opt-in unless you have good
Re: Anja
> The creator of VisiData goes into great depth here about his decision to
> enable motd by default: https://github.com/saulpw/visidata/issues/913
>
> The privacy page is here: https://www.visidata.org/privacy/.
This privacy policy is incomplete. You are collecting PII (the IP
address of
Re: Aurelien Jarno
> Ok fair enough. That said it's an external archive, so I don't think it
> warrant the severity serious. Downgrading to important.
Well, it's actively breaking software running on Debian.
> > Please remove the unversioned breaks against it, or make it versioned.
>
> We need t
Package: libc6
Version: 2.41-2
Severity: grave
postgresql-15-pllua is still a valid package on apt.postgresql.org.
Please remove the unversioned breaks against it, or make it versioned.
Package: libc6
Source: glibc
Version: 2.41-2
Architecture: ppc64el
Breaks: postgresql-15-pllua
Re: Matthew Garrett
> A) The Technical Committee affirms that base-files should own all
> top-level filesystem aliases, and packages that conflict with this must
> be patched in Debian to avoid creating any aliases that conflict with
> base-files (overrules the systemd maintainer, requires 3:1 m
Re: Matthew Vernon
> On 26/02/2025 16:38, Christoph Berg wrote:
> > Re: Matthew Garrett
> > > B) The Technical Committee requests that base-files create an empty
> > ^^
> > > /usr/lib64 directory, even on archit
Re: Matthew Garrett
> B) The Technical Committee requests that base-files create an empty
^^
> /usr/lib64 directory, even on architectures that do not use lib64. If
> systemd creates a symlink, this will then match the behaviour of
> base-files
Re: Ed Lawson
> > Which version did you use before? The closed source binaries have been
> > removed with rc7 when the SF verification switched to a new scheme.
>
> I was running rc6. I have two computers running wsjtx and neither now
> works in SF mode. Something is off. It was working before
>
Control: tags -1 unreproducible
Re: Ed Lawson
> The current version does not verify the fox
It works for me (without the closed source binaries).
Which version did you use before? The closed source binaries have been
removed with rc7 when the SF verification switched to a new scheme.
Christoph
Re: Jérôme Charaoui
> Would it be possible to rollback the package to 47.7.3, which doesn't cause
> the failure? Or review and adopt the fix proposed in upstream's PR?
IIRC there are a few security fixes in the latest versions, so
reverting wouldn't be ideal.
I don't grok java, so I can't review
Re: AKASH
> Why This Matters
>
>- Eliminates manual steps, making pg_dropcluster --stop more intuitive.
Are you saying that adding a manual confirmation step eliminates a
manual step?
Sorry, this is not going to change.
Christoph
Control: tags -1 = confirmed
Re: Santiago Vila
> It fails here:
>
> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/postgresql-17_17.3-3.rbuild.log.gz
Thanks. The difference is that Debian's and my buildds have "openssl"
preinstalled, while Lucas' and RB's do not:
checking fo
Control: tags -1 unreproducible
Control: severity -1 important
Re: Lucas Nussbaum
> > # Failed test 'pg_stat_ssl with client certificate: matches'
> > # at t/001_ssltests.pl line 731.
Hmm, it does not fail here today, nor in Debian just 3 days ago. We
will see what happens with the next point
Control: retitle -1 pg_lsclusters should show actually used port
Re: AKASH
> It would be useful if `pg_lsclusters` could detect and display all running
> PostgreSQL clusters, including those created manually, for better
> visibility and management.
That won't really work - there is no cluster nam
Re: Helmut Grohne
> > (S) The CTTE reaffirms that avahi-daemon is the default mDNS
> > implementation in Debian trixie. Therefore systemd-resolved should
> > disable the mDNS functionality in its default installation in Debian
> > trixie.
> > (Requires a 3:1 majority overruling a de
Re: Paolo Saggese
> please update the Sid packages to the latest upstream stable release (1.1.6):
>
> https://github.com/pgmodeler/pgmodeler/releases/tag/v1.1.6
Thanks, I had not seen that yet because there is already some "newer"
1.2.0~beta version shadowing it.
> ...and if possible please inc
Source: resource-agents
Version: 1:4.16.0-2
Severity: important
Hi,
looking at
https://ci.debian.net/packages/r/resource-agents/testing/riscv64/ ,
there are a lot of failing test runs. Browsing through the list, it
most often seems to be the mysql test that is failing.
Please fix it, disable thi
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: f...@packages.debian.org
Control: affects -1 + src:flog
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove flog from unstable. I packaged it decades ago because a
customer was using it. Now there are just 4 reported popcon
Re: Gregor Riepl
> Here's a patch that fixes both issues and more:
>
> 1. Fixes setup.py so the unit test data files are copied during the
> installation stage. This makes the unit tests work again.
>
> 2. Removes unit tests from python3-collada package. I'm not sure why they
> were included in
Re: Emmanuel Bourg
> The packages are back on track.
Thanks Emmanuel!
I would never have figured out these maven rules tweaks by myself...
Hopefully future updates are easier!
Christoph
Control: tags -1 moreinfo
Re: Rudy Godoy
> I've experienced this when upgrading my system from stable to testing.
> Somehow the stable's version (postgresql-15) was removed before the install
> of the testing's version (postgresql-17). When configuring, it couldn't
> complete the cluster upgrade b
Control: tags -1 unreproducible
Re: Lucas Nussbaum
> > # Failed test 'Action 'autovac_freeze' self-identifies correctly'
> > # at t/02_autovac_freeze.t line 40.
> > # 'uid=65534 topuid=10 euid=104 path='/tmp' at
> > /usr/lib/x86_64-linux-gnu/perl-base/File/Temp.pm line 686.
Source: libpqtypes
Severity: serious
Since I packaged libpqtypes in 2014, I have never heard back from
anyone using it, neither in Debian, nor outside of it. It's never
mentioned on #postgresql IRC. The upstream version is still the same
as 2014.
If no one uses this, we should remove it.
Christo
Re: Antonio Terceiro
> In the past, I hit a case where upgrading a cluster with a Very Large™
> database via dump/restore took a Very Long™ time. Back then I discovered
> --method=upgrade, and that's what I have been using since.
>
> Is there anything stopping this from being made the default?
Hi
Re: Chris Hofstaedtler
> Please consider enabling data checksums for new clusters on versions
> that support them. From what I can tell, the upstream vibe became
> something along the lines of "they dont hurt performance wise and
> its a good idea generally".
> Unfortunately right now, even cluster
Re: erebion
> Please don't. There's currently nothing else that works as well. I store the
> logs in a folder that gets synced to my other computer using Syncthing.
> Other log software uses a MySQL database, for example, and is not well
> suited for this.
>
> Also, imho alternatives like Klog are
Re: erebion
> starting pyqso no longer works, instead the output is as follows:
Fwiw, I've always been wondering if pyqso has users or if we should
simply remove it since it seems dead upstream.
73,
Christoph DF7CB
Re: Niels Thykier
> This package can probably come truly rootless if the upstream makefile could
> be convinced to not pass `-o root -g root` to `install`.
Fwiw, I just removed the -o -g arguments to install so the package can
build normally with RRR: no. I didn't want to create another snowflake
Re: Matthew Vernon
> Hello,
>
> I call for votes on the below ballot. The vote is open for 7 days, or until
> the outcome is beyond doubt.
I vote
C > B = D > A
Christoph
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-c...@packages.debian.org
Control: affects -1 + src:pg-cron
User: ftp.debian@packages.debian.org
Usertags: remove
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: postgresql...@packages.debian.org
Control: affects -1 + src:postgresql-16
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove postgresql-16 from unstable.
The last remaining rdep was postgresql-16-repmgr, removal of that w
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: rep...@packages.debian.org
Control: affects -1 + src:repmgr
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the 32-bit binaries of postgresql-16-repmgr from
unstable, thanks.
Christoph
Re: Sean Whitton
> > Right, but times are changing. In the past, fail2ban could depend on
> > system-log-daemon and expect files in /var/log/ to appear, but
> > systemd/journalctl keep things elsewhere.
> >
> > Perhaps that is the issue we should be discussing?
>
> What issue exactly do you mean?
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: postgres-decoderb...@packages.debian.org
Control: affects -1 + src:postgres-decoderbufs
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove postgresql-16-decoderbufs from unstable, thanks.
Christoph
Re: Ansgar 🙀
> That would be an argument to *NOT* have random packages "Recommend:
> system-log-daemon" so it is easier to not have it installed at all.
That's what I was trying to say, yes.
> Having "system facilities" that the admins decide to install or not
> install makes keeping optional stu
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: powa-archiv...@packages.debian.org
Control: affects -1 + src:powa-archivist
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove postgresql-16-powa/armel armhf i386 from unstable.
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: postgresql-filed...@packages.debian.org
Control: affects -1 + src:postgresql-filedump
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove postgresql-filedump [armel armhf i386] from unstable.
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-bsd-ind...@packages.debian.org, mba...@debian.org
Control: affects -1 + src:pg-bsd-indent
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove pg-bsd-indent from unstable. The binary it provides was
incorporated into post
Re: Matthew Vernon
> The maintainer is saying that "in all but unusual installations" a
> system-log-daemon would be found installed alongside hippotat-server.
I'm inclined to say logging should be a system facility and nothing
that a "normal" package should depend on. Then if I *don't* want
loggi
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: mobilit...@packages.debian.org
Control: affects -1 + src:mobilitydb
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove postgresql-17-mobilitydb on s390x. Thanks.
Christoph
Re: Marc Haber
> The actual version of the sudo in question isnt here.
1.9.15p5-3+b1.
Upgrading to 1.9.16-2 does not change the problem.
Christoph
Re: Marc Haber
> >From the bug I only see that you're using testing. testing has a sudo
> version from january 2024. If this is a recent breakage, then it was
> another package causing it. PAM is a maze for me.
It's not that old, I would guess at most a few weeks. The way I
noticed is PostgreSQL's
So `sudo -u postgres -i` opens a login shell as postgres and starts systemd.
But `sudo su -`; `su - postgres` opens a login shell as postgres and does not
start systemd.
sudo shouldn't behave differently here; I guess there is some
difference somewhere in the pam configuration.
Christoph
Package: libpam-systemd
Version: 256.7-2
Severity: normal
Hi,
I'm now getting a full user systemd including dbus and pipewire when
logging into the postgres user account:
[0] 15:51 myon@turing:~ $ sudo -iu postgres
[0] 15:51 postgres@turing:~ $ ps xf
PID TTY STAT TIME COMMAND
113664
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgaudit...@packages.debian.org
Control: affects -1 + src:pgaudit-16
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove pgaudit-16 from unstable, we already have pgaudit-17.
Christoph
Re: Helmut Grohne
> The other way is moving this file into an architecture-dependent
> package. Given its reliance on pg_config, why is it not part of
> libpq-dev in the first place? Is moving it there an option? Do you
> happen to know what would break if the file were moved?
pg_config used to be
Re: To Debian Bug Tracking System
> I keep getting cron mails from etckeeper:
>
> Subject: Anacron job 'cron.daily' on maxwell
>
> At least `git gc` has a `--quiet` parameter, I'd guess there's ways to
> make that happen for other operations as well.
Hi,
since it started now on a different mach
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-hint-plan...@packages.debian.org
Control: affects -1 + src:pg-hint-plan-16
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove pg-hint-plan-16 from unstable, there is already
pg-hint-plan-17.
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgpointcl...@packages.debian.org
Control: affects -1 + src:pgpointcloud
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pglogi...@packages.debian.org
Control: affects -1 + src:pglogical
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Christ
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-checks...@packages.debian.org
Control: affects -1 + src:pg-checksums
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-rep...@packages.debian.org
Control: affects -1 + src:pg-repack
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Christ
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: slony...@packages.debian.org
Control: affects -1 + src:slony1-2
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Christop
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgauditlogtof...@packages.debian.org
Control: affects -1 + src:pgauditlogtofile
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: postgresql-peri...@packages.debian.org
Control: affects -1 + src:postgresql-periods
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 no
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pglogical-tic...@packages.debian.org
Control: affects -1 + src:pglogical-ticker
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: tdig...@packages.debian.org
Control: affects -1 + src:tdigest
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Thanks,
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgl-ddl-dep...@packages.debian.org
Control: affects -1 + src:pgl-ddl-deploy
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Than
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-fact-loa...@packages.debian.org
Control: affects -1 + src:pg-fact-loader
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove the binaries related to PostgreSQL 16 from unstable, we
are targetting PostgreSQL 17 now.
Than
Package: wnpp
Severity: normal
X-Debbugs-Cc: libpgj...@packages.debian.org, libscram-j...@packages.debian.org,
libstringprep-j...@packages.debian.org, debian-de...@lists.debian.org, Debian
Java Maintainers , Debian
PostgreSQL Maintainers
Control: affects -1 + src:libpgjava
I request assistance
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pg-auto-failo...@packages.debian.org
Control: affects -1 + src:pg-auto-failover
User: ftp.debian@packages.debian.org
Usertags: remove
Christoph
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgpo...@packages.debian.org
Control: affects -1 + src:pgpool2
User: ftp.debian@packages.debian.org
Usertags: remove
Fwiw, bin:postgresql-16-pgpool2 was already properly decrufted, but
bin:pgpool2 was not removed, even when it's from the sa
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: icu-...@packages.debian.org
Control: affects -1 + src:icu-ext
User: ftp.debian@packages.debian.org
Usertags: remove
Christoph
/changelog 2024-09-25 12:44:52.0 +
@@ -1,3 +1,11 @@
+php-horde-db (2.4.1-8.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use a PG-native catalog query in primaryKey method to fix unstable
+ * ordering. (Closes: #1082106)
+
+ -- Christoph Berg Wed, 25 Sep 2024 14:44:52 +0200
Source: pg-gvm
Severity: important
Hi,
postgresql-17 is already in unstable. Please re-upload pg-gvm so it
moves to providing postgresql-17-pg-gvm (including binaries, will need
to go through NEW).
Let me know when you want me to do that.
Thanks,
Christoph
Source: php-horde-db
Version: 2.4.1-8
Severity: grave
Tags: patch
Hi,
php-horde-db's primaryKey for PostgreSQL relies on undefined ordering
when reading the columns a primary key is defined on. So far it
worked, but in PostgreSQL 17, it fails. The attached patch makes it
use a proper catalog quer
Source: php-horde-db
Version: 2.4.1-8
Severity: grave
Tags: patch
Hi,
php-horde-db's primaryKey() method for PostgreSQL relies on undefined
ordering when reading the columns of a multi-column primary key. So
far this worked, but on PG17 (already in testing, but not the default
version yet), this
Re: Scott Kitterman
> Still builds postgresql-16-pgq-node and depends on cruft postgresql-16-pgq3
Hi Scott,
thanks for the ftp accept!
I'm aware of the dependency chains among the PG extensions, no need
for extra bugs.
Christoph
Re: Paul Gevers
> This happens often enough on some architectures on ci.d.n that the Release
> Team considers this RC. Because the unstable-to-testing migration software
> now blocks on regressions in testing, flaky tests, i.e. tests that flip
> between passing and failing without changes to the li
Source: pygresql
Version: 1:6.0.1-1
Severity: serious
Please port pygresql to PostgreSQL 17. 17.0 will be released in 3
weeks, and 17rc1 is already in unstable. pygresql is the only package
holding back the testing migration of postgresql-17.
67s =
Re: Andreas Tille
> I would like to salvage your package antennavis by following the Package
> Salvaging procedur which is described in Developers Reference[1].
Fwiw, I believe this package is a candidate for removal.
The last upstream version is from 2010. I cannot believe it is still
useful, ev
Re: Sean Whitton
> It has been an honour.
Thank you!
> ===BEGIN BALLOT
>
> A: Christoph Berg
> B: Matthew Garrett
> C: Helmut Grohne
> D: Stefano Rivera
> E: Timo Röhling
> F: Craig Small
> G: Matthew Vernon
> H: Sean Whitton
>
> ===END BALLOT
Package: docker.io
Version: 26.1.4+dfsg1-9
Severity: normal
I just got docker.io upgraded on trixie, and /usr/bin/docker was gone.
I don't think running dockerd without having the cli available makes
sense, please upgrade docker.io's "Recommends: docker-cli" to a
"Depends: docker-cli" so people wo
Package: ftp.debian.org
Severity: normal
Tags: security
X-Debbugs-Cc: py-postgre...@packages.debian.org, Debian Python Team
, Debian Security Team
Control: affects -1 + src:py-postgresql
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove py-postgresql from unstable.
The cu
Re: Luca Boccassi
> > BEGIN BALLOT
> >
> > The Technical Committee declines to overrule the maintainer of
> > base-files, or issue any advice on issues concerning /etc/os-release.
> >
> > We do not think there is a clear proposal on the table for us to assess,
> > and we do not think it is appropri
Re: Rock Storm
> * Package name: gmat
> Version : 2015a
> Upstream Author : National Aeronautics and Space Administration
> * URL : http://gmatcentral.org
Seems to have moved to https://software.nasa.gov/software/GSC-17177-1
> * License : Apache-2.0
> Program
Re: Luca Boccassi
> The TL;DR is a request to override the base-files maintainer, and
> enable moving os-release into a new, independent and separate source
> package, so that these bugs may finally be fixed, and Debian's os-
> release may finally be made compliant with the specification.
If we ar
Re: Matthias Klose
> Package: src:py-postgresql
> Version: 1.2.1+git20180803.ef7b9a9-4
I believe instead of fixing this bug, we should remove
python3-postgresql. I've never seen it being used anywhere in the
wild, and the last version is a git snapshot from 2018. There are no
reverse dependencies,
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pgloa...@packages.debian.org
Control: affects -1 + src:pgloader
User: ftp.debian@packages.debian.org
Usertags: remove
Please remove pgloader/i386 from unstable. The lisp maintainers do not
want to support cl-ironclad on i386 anymore, and p
Re: Gregor Riepl
> - Packaging trimesh for 64-bit archs only
That wouldn't be a problem.
Christoph
Re: Diederik de Haas
> When removing or 'even' purging a linux-image- package, it
> reports the following issue:
>
> rmdir: failed to remove '/lib/modules/': Directory not empty
>
> The reason for that is that there's still a ``modules.weakdep`` file.
I just had the same problem on linux-image-6
Re: Dave Hibberd
> Something didn’t quite add up so I went digging further - it turns out that
> Ubuntu is shipping mysql-* as mysql-* and Debian is shipping mariadb-* as
> mysql-*, see:
> https://salsa.debian.org/mariadb-team/mysql/-/blob/mysql-defaults/debian/master/debian/rules
> for the spec
Re: Teemu Hukkanen
> The package description is incomplete, both the short and long
> description have "FIXME" at the beginning, without a useful description.
Oops, thanks for spotting!
Christoph
Re: Ben Finney
> At https://salsa.debian.org/debian/dput/-/merge_requests/15> is a
> merge request proposing to fix this bug.
>
> Can you try the resulting Dput package, and confirm whether it corrects the
> behaviour in your case?
Hi,
I don't think I have any ssh options set - it was already fa
Re: Stefan Heine
> how can I find, what version of the llvm library a given version of postgres
> is linked to?
It should be visible in the linker flags:
select * from pg_config();
LDFLAGS │ -Wl,-z,relro -Wl,-z,now -L/usr/lib/llvm-16/lib
-Wl,--as-needed
Christoph
Re: Martin-Éric Racine
> Incorrect delayed argument: ValueError: delayed days value must be a decimal
> integer:
`dput -e 0` works around that part of the problem. I then ran into
another problem though:
Uploading to ssh-upload [DELAYED/0-day] (via scp to ssh.upload.debian.org):
Traceback (most
Re: Moritz Mühlenhoff
> Agreed, if the package is actually broken with the version of PostgreSQL
> in stable and if there's no sensible backport for the open security issues,
> then let's rather remove it by the next point release.
Ack.
Christoph
1 - 100 of 1253 matches
Mail list logo
