close 1068656 1.6.0-2
thanks
This was fixed in the package, but the changelog entry for -2 didn't make it
into the .changes file for the version that was later uploaded.
Control: tag -1 pending
Hello,
Bug #1068656 in pgsql-http reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1066754 in sentry-python reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1063986 in sentry-python reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Sebastian Ramacher
> Source: cl-plus-ssl
> Version: 20220328.git8b91648-4
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> cl-plus-ssl hardcodeds a dependency on libssl3. Due to the time_t
> transition, the package name changed and the dependency needs to be
> updated.
It
Control: tag -1 pending
Hello,
Bug #101 in pgpcre reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Gregor Riepl
> I pushed a simple patch to add the dependency, would be nice if you could
> release it, @myon? Thanks in advance.
On its way, thanks for the update!
Christoph
Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: flask-babelex -- obsolete
Re: Colin Watson
> Should we just remove this package from Debian? I'm CCing everyone
> who's uploaded it in the past just in case, but I suspect this is an
> easy decision.
Yeah, let's
Control: tag -1 pending
Hello,
Bug #1065000 in pgpool2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Leandro Cunha
> The
> next job would be to make it available through backports and I would
> choose to remove this package from stable. But I would only leave
> bookworm backports due to other bugs found (this CVEs too) and fixed
> in 7.14.7.
> I have to search about the status of backports to
Package: libpam0g
Version: 1.5.3-6
Severity: serious
On my sid system, libpam0g doesn't get upgraded because apt thinks the
libpam0t64 package is good enough:
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating
Re: Vladimir Petko
> armhf has -Werror=implicit-function-declaration enabled in default gcc flags
> of
> gcc-13 13.2.0-16.1.
Huh, why only on armhf? That makes debugging this a bit hard.
> Would it be possible to consider a merge request[1] that addresses this
> issue?
I'm looking now.
Control: tag -1 pending
Hello,
Bug #1053004 in phppgadmin reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Steve Langasek
> If you as maintainer want to close this bug report (indicating that no
> transition is required) or un-tag it 'pending' (indicating that a transition
> may be required but the patch is not ready to upload), and accept any
> fallout if it turns out this is incorrect, that will
Control: tags -1 = moreinfo
Re: Steve Langasek
> If you have any concerns about this patch, please reach out ASAP. Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes
Re: Andrius Merkys
> The patch proposed in #1042610 does not fix test failure. Interestingly, the
> failure seems to be nondeterministic: after patching #1042610 some builds
> succeed. However, I did not manage to find the root cause.
The difference between a working and a failing run is this
Control: tag -1 pending
Hello,
Bug #1054974 in behave reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1042610 in behave reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Helmut Grohne
> Is it ok to call upgrade scenarios failures that cannot be reproduced
> using apt unsupported until we no longer deal with aliasing?
>
> If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
> with no action calling the scenario unsupported.
I think we
Re: Gregor Riepl
> > fatal error: catch2/catch.hpp: No such file or directory
>
> This is caused by significant changes in catch2 3.4.0.
> Some other packages are affected by the same problem, which currently blocks
> migration: https://qa.debian.org/excuses.php?package=catch2
>
> I think this
Control: retitle -1 su/sudo broken
Re: To Debian Bug Tracking System
> Package: libpam-modules-bin
> Version: 1.5.2-8
> Severity: grave
>
> amd64 is unaffected.
Correction: amd64 is affected as well (-8 just had not hit the mirrors
yet when I first tried).
Christoph
Package: libpam-modules-bin
Version: 1.5.2-8
Severity: grave
With pam 1.5.2-8 installed, my i386 chroots can't run su or sudo
anymore:
(sid-i386)root@turing:/home/myon# su -
su: Permission denied
(sid-i386)root@turing:/home/myon# sudo -i
sudo: PAM account management error: Permission denied
Re: Matthias Klose
> Package: src:gcc-arm-none-eabi
> Version: 15:12.3.rel1-1
> Severity: serious
> Tags: sid trixie
>
> a typical upload-and-run-away package upload ...
I think to fix, a simple rebuild of libstdc++-arm-none-eabi is
required (not binnmu-able since it's arch:all).
The original
Control: tag -1 pending
Hello,
Bug #1052755 in psqlodbc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: pg-gvm
Version: 22.4.0-2
Severity: serious
Tags: patch
Hi,
pg-gvm currently ships a single binary package "pg-gvm" that installs
files to /usr/lib/postgresql/15/, but doesn't declare that anywhere;
the packaging doesn't conform to the established PostgreSQL extension
packaging scheme.
Control: tag -1 pending
Hello,
Bug #1051881 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1051881 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1031011 in pgagroal reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1041429 in restrictedpython reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: pfm
Version: 2.0.8-3
Severity: grave
pfm doesn't do anything useful here, it just produces a message popup
saying
Connection to database foo has failed:
invalid command name "pg_connect"
I guess Tcl/Tk has changed since this package was last updated 10 years ago.
-- System
Re: Lucas Nussbaum
> Version: 0.17.0-2
> > (./testapplicationexception:892843): GLib-CRITICAL **: 07:16:59.134: Did
> > not see expected message GLib-GObject-WARNING **: value*out of range*type*
> > not ok /testapplicationexception/Properties/test -
> > GLib-GObject-FATAL-CRITICAL: value "-1"
Re: Timo Röhling
> https://lists.debian.org/debian-devel/2023/07/msg00307.html
Thanks for the explanation, I'm preparing an upload.
Cheers,
Christoph
Control: tag -1 pending
Hello,
Bug #1042157 in uranium reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hi Timo,
did cmake intentionally change Python_SITELIB to point to /usr/local?
Re: Gregor Riepl
> > purelib: directory for site-specific, non-platform-specific files
> > (https://docs.python.org/3/library/sysconfig.html)
> >
> > "site-specific" doesn't sound like packages should install
Re: Gregor Riepl
> This is caused by a change in cmake 3.27.
>
> In 3.26.4-4, Python_SITELIB is /usr/lib/python3/dist-packages.
> In 3.27.1-1, it's /usr/local/lib/python3.11/dist-packages
>
> The documentation for 3.26 states:
> > Information returned by
> >
Re: Gregor Riepl
>
> > > -- Installing:
> > > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM
> > > -- Installing:
> > > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM/ColorImage.py
>
> > > dh_install: warning: Cannot find (any matches for)
> > >
Control: tag -1 pending
Hello,
Bug #25 in xastir reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Adrian Bunk
> 2. the following change:
>
> --- debian/rules.old 2023-07-24 15:36:20.941771419 +
> +++ debian/rules 2023-07-24 15:36:43.133759741 +
> @@ -5,7 +5,7 @@
> # less debug info to avoid running out of address space
> ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
>
Re: Gregor Riepl
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> > severity of this report will be raised before the trixie release.
>
> This issue was due to a missing #include , and it was already fixed
>
Re: Adrian Bunk
> They seem to have renamed the python modules, e.g. in python3-arcus:
Sigh, and thanks for spotting that.
I had hoped that uploading to experimental would have found such
issues over the last year, but was not true. :(
Christoph
Re: Gregor Riepl
>
> Thanks for the quick fix, but I'm not super happy about this solution.
>
> This package *really* installs only platform-independent header files, and I
> think the error is wrong.
>
> But I can see where it's coming from; one of the cmake scripts contains
> boilerplate that
Control: tag -1 pending
Hello,
Bug #1040191 in libnest2d reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1031680 in uranium reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: tony mancill
> In any event, I think the change is good and am planning to upload,
> provided there are no concerns from the Debian Hams.
Looks good to me.
Christoph
Re: Gregor Riepl
> -install(FILES service/charon.service DESTINATION lib/systemd/system)
> +install(FILES service/charon.service DESTINATION /lib/systemd/system)
Thanks for figuring that out!
Uploaded to experimental and unstable.
Christoph
close 1032930 5.0.0-2
thanks
libnest2d (5.0.0-2) unstable; urgency=medium
* Patch incorrect package name in Findclipper.cmake. Closes: #1032930
-- Gregor Riepl Wed, 29 Mar 2023 02:12:38 +0200
Re: Adrian Bunk
> > CVE-2023-22332[0]:
> Christoph, is there a reason why this cannot be fixed with a backport
> or an upgrade to 4.3.5?
Just time (and the RFH on the package that has been open since 2014
and no activity since 2016).
I've just uploaded 4.3.5 to unstable.
Thanks for the poke,
Control: tag -1 pending
Hello,
Bug #1030048 in pgpool2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Black Michael
> Current github master plus one small patch fixes the compilation.
Hi Michael,
I see it has already been merged, thanks!
Let's see if they also tag a new release. Otherwise I'll make a temp
tarball in a few days.
Christoph
Re: Gregor Riepl
> It will be fixed in libarcus 5.0.0-2, which is waiting for release:
> https://salsa.debian.org/3dprinting-team/libarcus/-/commit/c2dfe6eacb2213195619b50f1d1efc7cd519c8f8
>
> @myon: Can you take care of pushing this version, please?
Hi Gregor,
I just uploaded that version.
I
Re: Paul Gevers
> With a recent upload of qcustomplot the autopkgtest of qcustomplot fails in
> testing when that autopkgtest is run with the binary packages of qcustomplot
> from unstable.
I uploaded the pending changes as an NMU, plus ignoring a compiler
warning on stderr:
[ 66%] Building CXX
Control: tag -1 pending
Hello,
Bug #1024100 in libxtrx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1024101 in js8call reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1024104 in wsjtx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Petter Reinholdtsen
> I do not buy into the cancel culture. I further do not find the guilt by
> association argument (his web page is full of bad stuff, so his software
> is bad) convincing. In short, I fail to see it as an argument for
> removing bs1770gain from Debian.
By playing
Re: Ansgar
> I proposed to remove bs1770gain from Debian. Besides the problem from
> #913352, the upstream homepage and domain that we direct users to (via
> Homepage: field and other places) contain extremist content.
>
> I don't think it's worth distributing software that does this in
> Debian.
Re: Filippo Rusconi
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> as per recommendation of release.debian.org, this bug is to inform the
> maintainer of js8call that a transition is currenly in operation.
The usual course is filing bugs at
Control: tag -1 pending
Hello,
Bug #1012538 in chirp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Apostolos Kefalas
> lately chirp received some major work towards python3
>
> https://github.com/kk7ds/chirp/tree/py3
Oh interesting. And no more dealing with mercurial.
Thanks!
Christoph
close 1022478 1.4.2-2
thanks
close 1022522 1:2.0.10-5
thanks
close 1022490 2.17-1
thanks
> > # Python3 bindings
> > python3 host/libraries/libbladeRF_bindings/python/setup.py install
> > --root=debian/tmp/ --prefix=/usr
...
> > Copying bladerf.egg-info to
> > debian/tmp/usr/local/lib/python3.10/dist-packages/bladerf-1.2.1-py3.10.egg-info
> > running install_scripts
> > Installing
Control: tag -1 pending
Hello,
Bug #1022398 in bladerf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
close 1022487 3.5-2
thanks
--
Mit freundlichen GrüÃen,
Christoph Berg
--
Senior Consultant, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Geoff Richardson, Peter
Control: tag -1 pending
Hello,
Bug #1022535 in pg-repack reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1022507 in postgresql-plsh reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1021859 in pgbouncer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1022152 in postgresql reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: To Debian Bug Tracking System
> redmine needs updating for this; one workaround for the testsuite
> would be to "grant create on schema public to public;" to revert to
> the old default.
It's not the testsuite failing; it's already the postinst failing to
install redmine.
Christoph
Source: redmine
Version: 5.0.2-2
Severity: serious
PostgreSQL 15 restricts the CREATE privilege on the default "public"
schema in each database to the database owner; previous all users were
allowed to create new objects.
redmine needs updating for this; one workaround for the testsuite
would be
Control: severity -1 important
Re: Daniele Forsi
> Christoph Berg wrote:
>
> > Is it just broken for me and Bernhard, or for most people?
>
> the version from package 4.36-2 works for me, with "LC_ALL=C tucnak"
> and without LC_ALL set
Ok, let's downgrade it
Re: tony mancill
> > tucnak doesn't start here:
> >
> > $ LC_ALL=C tucnak
>
> Hi Christoph,
>
> Hmm... it starts and runs here, so I don't think it is broken for
> everyone.
Is it just broken for me and Bernhard, or for most people?
Christoph
Re: Bernhard Übelacker
> From [1] it might be possible to use another driver.
> Maybe MESA_LOADER_DRIVER_OVERRIDE=i965 could work for this hardware?
Doesn't help I'm afraid:
$ MESA_LOADER_DRIVER_OVERRIDE=swrast tucnak
libGL error: image driver extension not found
libGL error: failed to load
Re: tony mancill
> Hmm... it starts and runs here, so I don't think it is broken for
> everyone.
Fair enough. It worked for me before in the sense that I could see the
UI, but I never got it to do anything useful for me. I always
attributed it to me being too lazy to read the documentation, but I
Package: tucnak
Version: 4.36-1
Severity: grave
tucnak doesn't start here:
$ LC_ALL=C tucnak
tucnak: ../src/GLX/libglx.c:966: CommonMakeCurrent: Assertion `oldCtxInfo !=
NULL' failed.
Abgebrochen (Speicherabzug geschrieben)
The stack traces look mostly like garbage:
Stack
Control: tag -1 pending
Hello,
Bug #1017706 in postgresql-set-user reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tags -1 unreproducible
Re: Lucas Nussbaum
> Source: thrift
> Version: 0.16.0-5
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220716 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package
Control: tag -1 pending
Hello,
Bug #1012903 in bladerf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Tyler Schwend
> The Debian packaged version is much older than the current version.
The problem with chirp is that upstream isn't moving to python 3, the
porting branch seems stalled:
http://d-rats.com/hg/hgwebdir.cgi/chirp.hg/branches
Christoph DF7CB
Control: clone -1 -2
Control: retitle -2 RM: sdrangelove -- RoM; dead upstream
Control: severity -2 normal
Control: reassign -2 ftp.debian.org
> > Source: sdrangelove
> > Version: 0.0.1.20150707-5
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User:
Control: tag -1 pending
Hello,
Bug #1005611 in pgbadger reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: dh-python
Version: 5.20220101
Severity: serious
Affects: pynest2s
pynest2s 4.13~beta-1 ftbfses on all architectures:
https://buildd.debian.org/status/package.php?p=pynest2d
The reason is that pybuild "'double quotes'" the --builddirectory
argument, making it a relative path since it
Control: tag -1 pending
Hello,
Bug #1002121 in gr-limesdr reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1001811 in postgresql-mysql-fdw reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Lucas Nussbaum
> Source: sdrangelove
> Version: 0.0.1.20150707-5
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on
Control: tag -1 pending
Hello,
Bug #993699 in libxtrx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
> flmsg.cxx: In function ‘void rotate_log(std::string)’:
> flmsg.cxx:2848:24: error: ‘streampos’ is not a member of ‘std::ostringstream’
> {aka ‘std::__cxx11::basic_ostringstream’}
> 2848 | ostringstream::streampos p;
> |^
For the record, the new
Re: Dimitri Fontaine
> Thanks again folks, I really appreciate the time and effort you're putting
> into this, and of course the good results!
I got it working, including a workaround that will automatically
downgrade scram-sha-256 to md5 on the older distributions where
cl-postmodern doesn't
close 995846 3.6.3-1
thanks
Control: tag -1 pending
Hello,
Bug #1001482 in restrictedpython reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Sébastien Villemot
> I’ve uploaded a new cl-esrap. It seems pgloader builds again.
Merci! I'll try to polish the package over the next days.
Christoph
Control: tag -1 pending
Hello,
Bug #997614 in python-parse-type reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: To Sébastien Villemot
> Unfortunately, pgloader still doesn't compile:
> While evaluating the form starting at line 21, column 0
> of
> #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal
> SIMPLE-ERROR:
> Compilation failed: * is not permitted as an argument to
Control: tag -1 pending
Hello,
Bug #997632 in behave reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Sébastien Villemot
> The updated cl-postmodern just entered unstable.
Salut Sébastien,
that is excellent news, thanks!
Unfortunately, pgloader still doesn't compile:
; compiling file "/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp"
(written 12 OCT 2021 03:11:59 PM):
; file:
Source: postgresql-multicorn
Version: 1.4.0-4
Severity: serious
Multicorn is incompatible with PostgreSQL 14 and needs non-trivial
porting while upstream work has stalled for the past two years.
https://github.com/Segfault-Inc/Multicorn/issues/271
In the meantime, it should be removed from
Control: tag -1 pending
Hello,
Bug #1000512 in psqlodbc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Re: Martina Ferrari
> The GH issue you linked seems to be fixed upstream already with this patch:
> https://github.com/prometheus/prometheus/pull/8538/files
Is anyone working on getting this uploaded? prometheus just got
removed from testing.
> On 09/10/2021 19:34, Shengjing Zhu wrote:
> >
Control: tag -1 pending
Re: To Debian Bug Tracking System
> Depends: postgresql-pgsphere, postgresql-q3c
>
> Alternatively, switch it to postgresql-14-pgsphere, postgresql-14-q3c
>
> (pgsphere itself still has problems with PG14 to be resolved, but
> moving to the version-less dependency would
1 - 100 of 593 matches
Mail list logo
