Bug#1053004: CVE-2019-10784 and CVE-2023-40619
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
Bug#1068656: closing 1068656
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.
Bug#1068656: marked as pending in pgsql-http
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: https://salsa.debian.org/postgresql/pgsql-http/-/commit/f92a339d44e621a56ee174ccaacb9466d819cbb5 Disable build-time tests. (Closes: #1068656) Skip autopkgtest when networking is unavailable. (this message was generated automatically) -- Greetings https://bugs.debian.org/1068656
Bug#1066754: marked as pending in sentry-python
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: https://salsa.debian.org/python-team/packages/sentry-python/-/commit/9708fff7c0ee2bf14b470cde56605317a5609663 New upstream version 1.40.4. (Newer versions don't pass all tests.) Fixes test regression with pytest 8 (Closes: #1063986, #1066754) (this message was generated automatically) -- Greetings https://bugs.debian.org/1066754
Bug#1063986: marked as pending in sentry-python
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: https://salsa.debian.org/python-team/packages/sentry-python/-/commit/9708fff7c0ee2bf14b470cde56605317a5609663 New upstream version 1.40.4. (Newer versions don't pass all tests.) Fixes test regression with pytest 8 (Closes: #1063986, #1066754) (this message was generated automatically) -- Greetings https://bugs.debian.org/1063986
Bug#1066067: cl-plus-ssl: hardcoded libssl3 dependency
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 actually doesn't hard-code the dependency but correctly extracts it from libssl-dev. But since we don't have arch:all binnmus, a new upload was needed anyway. Just did that. Once cl-plus-ssl is installed, please binnmu pgloader to have it pick up the changed dependency. Christoph
Bug#1000001: marked as pending in pgpcre
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: https://salsa.debian.org/postgresql/pgpcre/-/commit/b36dc6e2517979428bac0855fdc5578e3ef8006a Port to PCRE2 (Closes: #101). B-D on pkconf. (this message was generated automatically) -- Greetings https://bugs.debian.org/101
Bug#1067144: [3dprinter-general] Bug#1067144: uranium: missing depend on python3-all for autopkgtest
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
Bug#1064697: flask-babelex: FTBFS: ImportError: cannot import name '_request_ctx_stack' from 'flask' (/usr/lib/python3/dist-packages/flask/__init__.py)
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 just do that. Thanks for looking into the details! Christoph
Bug#1065000: marked as pending in pgpool2
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: https://salsa.debian.org/postgresql/pgpool2/-/commit/0d80c3f9759b682f88740570efce1a59636a8b61 fix -Werror=implicit-function-declaration errors. (Closes: #1065000) (this message was generated automatically) -- Greetings https://bugs.debian.org/1065000
Bug#1053004: CVE-2019-10784 and CVE-2023-40619
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 oldstable. But I'm > also studying the possibility of working with patches for these two > versions. Why would you want to remove it from stable? In closed environments, CVEs are often not a problem. Christoph
Bug#1065425: Does not upgrade from libpam0t64
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 upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ apt-cache policy libpam0t64 libpam0t64: Installed: 1.5.3-4 Candidate: 1.5.3-4 Version table: *** 1.5.3-4 100 100 /var/lib/dpkg/status $ apt-cache policy libpam0g libpam0g: Installed: (none) Candidate: 1.5.3-6 Version table: 1.5.3-6 500 500 http://deb.debian.org/debian sid/main amd64 Packages 1.5.2-9.1+b1 -1 100 /var/lib/dpkg/status Christoph
Bug#1065000: pgpool2: the package fails to build on armhf due to gcc-13 13.2.0-16.1 changes
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. Fwiw, since I have your attention, what's up with resource-agents on noble? I see the source is present in that dist, but no binary? Christoph
Bug#1053004: marked as pending in phppgadmin
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: https://salsa.debian.org/postgresql/phppgadmin/-/commit/921866f35baa59636dabe798675cb2f7e2c6ab52 Import Debian changelog version 7.14.7+dfsg-1 phppgadmin (7.14.7+dfsg-1) unstable; urgency=high * Team upload. * New upstream version. * Fix deserialization of untrusted data. (Closes: #1053004, CVE-2023-40619) * Fix validating the request originated. (Closes: #953945, CVE-2019-10784) * d/watch: Change for get fork source (phppgadmin-mod of ReimuHakurei). * d/upstream: Delete signing-key.asc, the repository changed. * d/copyright: Update for new upstream and update year. * d/control: Update homepage for new repository. * d/patches all applied by new upstream: - Drop credit-utf8. - Drop fix-version-postgres.patch. - Drop php8. - Drop sequence_priviledge. - Drop versionning-adodb5.21. (this message was generated automatically) -- Greetings https://bugs.debian.org/1053004
Bug#1062567: libpg-query: NMU diff for 64-bit time_t transition
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 mark it so that we will > not include it in NMUs to unstable. Is there any writeup on what verification steps I have to do to do that assessment? All I could find so far are very long lists of packages without any explanation, and a wiki page that outlines a plan, but doesn't have any instructions for maintainers. Christoph
Bug#1062567: libpg-query: NMU diff for 64-bit time_t transition
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 available that your package should not be included in the transition, > there is time for us to amend the planned uploads. Hi, I just found out that libpg-query is included because it was thought to be "uninstallable": https://adrien.dcln.fr/misc/armhf-time_t/2024-02-01T09:53:00/logs/libpg-query-dev/apt.log [2024-01-20T03:02:49+00:00] apt-get install libpg-query-dev libprotobuf-c-dev postgresql-server-dev-15 abi-compliance-checker E: Unable to locate package postgresql-server-dev-15 I think that's bogus, the package has not been depending on PG15 for some time. Please exclude it from the NMUs. Also, why did I not get a bug for that? I understand that you can't look at 1500 packages individually, but checking the 40-something on the https://adrien.dcln.fr/misc/armhf-time_t/2024-02-01T09:53:00/summary/results_uninstallable.txt list would surely have been possible? Christoph
Bug#1054974: behave: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
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 diff: dh_auto_test -O--buildsystem=pybuild -I: pybuild base:305: cd /home/myon/debian/nmu/behave/behave/.pybuild/cpython3_3.12_behave/build; python3.12 -m pytest test +I: pybuild base:305: cd /home/myon/debian/nmu/behave/behave/.pybuild/cpython3_3.12_behave/build; python3.12 -m pytest tests I.e. pybuild invokes either "python3.12 -m pytest test" (good) or "python3.12 -m pytest tests" (bad) I tried to drill down where this decision is made but couldn't spot it. As a workaround, we can move the "tests" directory aside. Then it will reliably run the "test" target. (Not pretty, but I want to get the package unstuck.) Christoph
Bug#1054974: marked as pending in behave
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: https://salsa.debian.org/python-team/packages/behave/-/commit/b08c90e9c290f254f160a9d48e3b23d469aa767a Move "tests" directory aside while running test. (Closes: #1054974) (this message was generated automatically) -- Greetings https://bugs.debian.org/1054974
Bug#1042610: marked as pending in behave
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: https://salsa.debian.org/python-team/packages/behave/-/commit/6dbb3d83edccf348aca0443737611a31b40d7635 Fix FTBFS with Sphinx 7.1 and extlinks. (Closes: #1042610) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042610
Bug#1058937: /usr-move: Do we support upgrades without apt?
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 should only deal with problems that can reasonably happen in practice. If an extra hammer is required to hit the problem, we should not spend extra effort on it. Christoph
Bug#1054697: [3dprinter-general] Bug#1054697: slic3r-prusa: FTBFS: test_arrange.cpp:1:10: fatal error: catch2/catch.hpp: No such file or directory
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 bug should be: > > reassign -1 catch2 > affects -1 slic3r-prusa > > Are there any objections if I do this? If that's an intentional upstream change, reassigning to catch2 won't help as it's not a bug in that package. Christoph
Bug#1054505: su/sudo broken on i386
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
Bug#1054505: su/sudo broken on i386
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
sudo: a password is required
amd64 is unaffected.
(sid-i386)root@turing:/home/myon# strace su -
execve("/usr/bin/su", ["su", "-"], 0xffc17124 /* 17 vars */) = 0
brk(NULL) = 0x57956000
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7eef000
...
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = -1 ENOENT (No such
file or directory)
close(4)= 0
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4
connect(4, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = -1 ENOENT (No such
file or directory)
close(4)= 0
read(3, "", 4096) = 0
close(3)= 0
getuid32() = 0
socket(AF_NETLINK, SOCK_RAW, NETLINK_AUDIT) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
readlink("/proc/self/exe", "/usr/bin/su", 4096) = 11
sendto(3, [{nlmsg_len=140, nlmsg_type=0x44c /* NLMSG_??? */,
nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=1, nlmsg_pid=0},
"\x6f\x70\x3d\x50\x41\x4d\x3a\x61\x75\x74\x68\x65\x6e\x74\x69\x63\x61\x74\x69\x6f\x6e\x20\x67\x72\x61\x6e\x74\x6f\x72\x73\x3d\x70"...],
140, 0, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 140
poll([{fd=3, events=POLLIN}], 1, 500) = 1 ([{fd=3, revents=POLLIN}])
recvfrom(3, [{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED,
nlmsg_seq=1, nlmsg_pid=627976}, {error=0, msg={nlmsg_len=140,
nlmsg_type=AUDIT_FIRST_USER_MSG, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK,
nlmsg_seq=1, nlmsg_pid=0}}], 8988, MSG_PEEK|MSG_DONTWAIT,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, [12]) = 36
recvfrom(3, [{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED,
nlmsg_seq=1, nlmsg_pid=627976}, {error=0, msg={nlmsg_len=140,
nlmsg_type=AUDIT_FIRST_USER_MSG, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK,
nlmsg_seq=1, nlmsg_pid=0}}], 8988, MSG_DONTWAIT, {sa_family=AF_NETLINK,
nl_pid=0, nl_groups=}, [12]) = 36
close(3)= 0
socket(AF_NETLINK, SOCK_RAW, NETLINK_AUDIT) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
sendto(3, [{nlmsg_len=124, nlmsg_type=0x44d /* NLMSG_??? */,
nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=2, nlmsg_pid=0},
"\x6f\x70\x3d\x50\x41\x4d\x3a\x61\x63\x63\x6f\x75\x6e\x74\x69\x6e\x67\x20\x67\x72\x61\x6e\x74\x6f\x72\x73\x3d\x3f\x20\x61\x63\x63"...],
124, 0, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 124
poll([{fd=3, events=POLLIN}], 1, 500) = 1 ([{fd=3, revents=POLLIN}])
recvfrom(3, [{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED,
nlmsg_seq=2, nlmsg_pid=627976}, {error=0, msg={nlmsg_len=124, nlmsg_type=0x44d
/* AUDIT_??? */, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=2,
nlmsg_pid=0}}], 8988, MSG_PEEK|MSG_DONTWAIT, {sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, [12]) = 36
recvfrom(3, [{nlmsg_len=36, nlmsg_type=NLMSG_ERROR, nlmsg_flags=NLM_F_CAPPED,
nlmsg_seq=2, nlmsg_pid=627976}, {error=0, msg={nlmsg_len=124, nlmsg_type=0x44d
/* AUDIT_??? */, nlmsg_flags=NLM_F_REQUEST|NLM_F_ACK, nlmsg_seq=2,
nlmsg_pid=0}}], 8988, MSG_DONTWAIT, {sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, [12]) = 36
close(3)= 0
getpid()= 627976
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = -1 ENOENT (No such
file or directory)
close(3)= 0
getpid()= 627976
openat(AT_FDCWD, "/var/log/btmp", O_WRONLY|O_LARGEFILE) = 3
alarm(0)= 0
rt_sigaction(SIGALRM, {sa_handler=0xf7e13d90, sa_mask=[], sa_flags=0},
{sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
alarm(10) = 0
fcntl64(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, NULL, 8) = 0
_llseek(3, 0, [384], SEEK_END) = 0
write(3, "\6\0\0\0\10\225\t\0pts/3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
384) = 384
fcntl64(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
close(3)= 0
munmap(0xf7c6a000, 16392) = 0
munmap(0xf7c37000, 208144) = 0
munmap(0xf7b97000, 651928) = 0
munmap(0xf7b92000, 16416) = 0
munmap(0xf7b8c000, 20488) = 0
munmap(0xf7b87000, 16392) = 0
munmap(0xf7b7f000, 28680) = 0
openat(AT_FDCWD, "/etc/login.defs", O_RDONLY|O_LARGEFILE) = 3
statx(3,
Bug#1050327: gcc-arm-none-eabi update breaks other arm-none-eabi packages
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 reason I was looking into this is hackrf (#1052857), but that got updated yesterday not to build the arm firmware image anymore. Furthermore, when trying to build the hackrf package that still needs the arm toolchain, I'm now getting this: -- Check for working C compiler: /usr/bin/arm-none-eabi-gcc - broken CMake Error at /usr/share/cmake-3.27/Modules/CMakeTestCCompiler.cmake:67 (message): The C compiler "/usr/bin/arm-none-eabi-gcc" is not able to compile a simple test program. It fails with the following output: Change Dir: '/home/myon/debian/nmu/gcc-arm-none-eabi/hackrf/firmware/build_hackrf/CMakeFiles/CMakeScratch/TryCompile-eCZznn' Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f Makefile cmTC_64ef2/fast gmake[2]: Entering directory '/home/myon/debian/nmu/gcc-arm-none-eabi/hackrf/firmware/build_hackrf/CMakeFiles/CMakeScratch/TryCompile-eCZznn' /usr/bin/gmake -f CMakeFiles/cmTC_64ef2.dir/build.make CMakeFiles/cmTC_64ef2.dir/build gmake[3]: Entering directory '/home/myon/debian/nmu/gcc-arm-none-eabi/hackrf/firmware/build_hackrf/CMakeFiles/CMakeScratch/TryCompile-eCZznn' Building C object CMakeFiles/cmTC_64ef2.dir/testCCompiler.c.obj /usr/bin/arm-none-eabi-gcc -g -O2 -ffile-prefix-map=/home/myon/debian/nmu/gcc-arm-none-eabi/hackrf=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -o CMakeFiles/cmTC_64ef2.dir/testCCompiler.c.obj -c /home/myon/debian/nmu/gcc-arm-none-eabi/hackrf/firmware/build_hackrf/CMakeFiles/CMakeScratch/TryCompile-eCZznn/testCCompiler.c cc1: error: '-fcf-protection=full' is not supported for this target So, I'm not going to fix this bug, but perhaps these notes help others. Christoph
Bug#1052755: marked as pending in psqlodbc
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: https://salsa.debian.org/postgresql/psqlodbc/-/commit/14b1e9f9750db820ba956acca728ef7dacb5e951 New upstream version 16.00.. Fixes "bool" FTBFS. (Closes: #1052755) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052755
Bug#1052177: Provides a PostgreSQL extension without depending on the correct server version
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. PostgreSQL 16 is just entering unstable, the package needs to be updated. A branch to fix that is at https://salsa.debian.org/pkg-security-team/pg-gvm/-/merge_requests/1 I plan to NMU this in 10 days to get the PostgreSQL 16 transition forward if I don't hear back otherwise. Thanks, Christoph
Bug#1051881: marked as pending in postgresql
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: https://salsa.debian.org/postgresql/postgresql/-/commit/4c4b928993b8c4a517f055ce63cbeb2e52036ae6 Stop building lib packages, postgresql-16 is in unstable. Use LLVM 15 for JIT support, 16 is not supported yet. (Closes: #1051881) (this message was generated automatically) -- Greetings https://bugs.debian.org/1051881
Bug#1051881: marked as pending in postgresql
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: https://salsa.debian.org/postgresql/postgresql/-/commit/8a5b631833508c9ee61d41433c1073a3c2ce9b56 Use LLVM 15 for JIT support, 16 is not supported yet. (Closes: #1051881) (this message was generated automatically) -- Greetings https://bugs.debian.org/1051881
Bug#1031011: marked as pending in pgagroal
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: https://salsa.debian.org/postgresql/pgagroal/-/commit/50bdc843cb42388e9e597a246b6c1f76c8ca3dce Fix PG protocol on big-endian machines. (Closes: #1031011) (this message was generated automatically) -- Greetings https://bugs.debian.org/1031011
Bug#1041429: marked as pending in restrictedpython
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: https://salsa.debian.org/python-team/packages/restrictedpython/-/commit/01e95e103074c9df2d70cb3d1d4359af68b03150 New upstream version 6.2. (Closes: #1041429, CVE-2023-37271) (this message was generated automatically) -- Greetings https://bugs.debian.org/1041429
Bug#1050375: Invalid command name "pg_connect"
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 Information: Debian Release: trixie/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pfm depends on: ii itcl3 3.4.4-2 ii libpgtcl 1:3.0.0-1 ii postgresql-client 15+253.pgdg+1 ii postgresql-client-10 [postgresql- 10.23-2.pgdg+1 client] ii postgresql-client-11 [postgresql- 11.21-1.pgdg+1 client] ii postgresql-client-12 [postgresql- 12.16-1.pgdg+1 client] ii postgresql-client-13 [postgresql- 13.12-1.pgdg+1 client] ii postgresql-client-14 [postgresql- 14.9-1.pgdg+1 client] ii postgresql-client-15 [postgresql- 15.4-1.pgdg+1 client] ii postgresql-client-16 [postgresql- 16~beta2-2.pgdg+~20230807.1056.ge8386b2 client] ii postgresql-client-17 [postgresql- 17~~devel-1.pgdg+~20230820.0934.g1951d21 client] ii postgresql-client-8.2 [postgresql 8.2.23-11.pgdg+1 -client] ii postgresql-client-8.4 [postgresql 8.4.22-9.pgdg+1 -client] ii postgresql-client-9.3 [postgresql 9.3.25-9.pgdg+1 -client] ii postgresql-client-9.4 [postgresql 9.4.26-8.pgdg+1 -client] ii postgresql-client-9.5 [postgresql 9.5.25-6.pgdg+1 -client] ii postgresql-client-9.6 [postgresql 9.6.24-5.pgdg+1 -client] ii sensible-utils 0.0.20 ii tcl8.6.13 ii tk 8.6.13 pfm recommends no packages. Versions of packages pfm suggests: ii postgresql 15+253.pgdg+1 -- no debconf information Christoph
Bug#1042025: thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
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" of type 'gint' is invalid or out of
> > range for property 'type' of type 'gint'
> > Bail out!
> > /bin/bash: line 6: 892843 Trace/breakpoint trap ${dir}$tst
> > FAIL: testapplicationexception
> > TAP version 13
> > # random seed: R02Sdadbad636988fc61fb41629b59ecfdd6
Fwiw, there is a new 0.18.1 upstream version. Perhaps that works
better.
Christoph
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
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
Bug#1042157: marked as pending in uranium
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: https://salsa.debian.org/3dprinting-team/uranium/-/commit/e5d2fb259d40f65ac490f97ed05ce5673e049ef4 Set DEB_PYTHON_INSTALL_LAYOUT=deb_system, thanks Timo Röhling! (Closes: #1042157) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042157
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
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 anything
> > there.
>
> "site-specific" may be meant from the perspective of the Python interpreter,
> not the whole system, so it does sound correct to me - especially if you
> consider that Python modules are separated into the standard library and
> dist-packages.
>
> > Perhaps the bug is that Python_SITELIB is used and it should be
> > something else?
>
> I've tried Python_STDLIB (=sysconfig.get_path('stdlib')), but that's
> definitely wrong: It points to /usr/lib/python3.11
>
> Python packages are normally installed into /usr/lib/python3/dist-packages/
> (or /usr/lib/python3.11/dist-packages/ if they're interpreter-specific).
> Uranium used to be installed into /usr/lib/python3/dist-packages/, because
> it's a pure Python library and doesn't depend on the interpreter version.
>
> Python_STDARCH and Python_SITEARCH have the same values as Python_STDLIB and
> Python_SITELIB, and I don't see any other useful FindPython[1] variables.
> IMHO, Python_SITELIB is still the best choice, unless there's some other way
> to install Python modules in cmake that doesn't involve these variables.
>
> I'm going to ask the debian-python list for help, perhaps they know more
> about the correct paths to use.
> In the meantime, I do think this issue should block cmake 3.27 migration
> until we've sorted it out, so the bug should be reassigned to cmake.
>
>
> [1] https://cmake.org/cmake/help/latest/module/FindPython.html
>
Christoph
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
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
> > distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False)
> > or else sysconfig.get_path('purelib').
>
> And for 3.27:
> > Information returned by sysconfig.get_path('purelib').
>
> I'm not sure if Debian overrides this in any way, but it's certainly a
> regression.
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 anything
there.
Perhaps the bug is that Python_SITELIB is used and it should be
something else?
Christoph
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
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) > > > "usr/lib/python3/dist-packages/UM" (tried in ., debian/tmp) > > > > > > dh_install: warning: python3-uranium missing files: > > > usr/lib/python3/dist-packages/UM > > > dh_install: error: missing files, aborting > > > make: *** [debian/rules:7: binary] Error 25 > > Those are very strange results. > No files should end up in /usr/local! > > And I haven't been able to reproduce this locally yet. > Investigation ongoing... I can reproduce it here, but haven't investigated yet. Christoph
Bug#999925: marked as pending in xastir
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: https://salsa.debian.org/debian-hamradio-team/xastir/-/commit/d49fb8bc79b05ece58c0103b7a5ce699e128caf9 Temporarily use --without-pcre --without-shapelib to remove the deprecated pcre3 dependency. (Closes: #25) (this message was generated automatically) -- Greetings https://bugs.debian.org/25
Bug#1041870: [3dprinter-general] Bug#1041870: slic3r-prusa FTBFS on i386
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)) > export DEB_CXXFLAGS_MAINT_APPEND += --param ggc-min-expand=5 -g0 > -else ifneq (,$(filter $(DEB_HOST_ARCH), armhf)) The old command was wrong anyway, the pattern list comes first: ifneq (,$(filter armhf, $(DEB_HOST_ARCH))) Doesn't matter when it's a single item without % wildcards, but will explode when adding more architectures. Christoph
Bug#1037614: [3dprinter-general] Bug#1037614: cura-engine: ftbfs with GCC-13
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 > upstream in an unrelated commit. Hi Gregor, thanks for collecting all the patches and putting them together. There's still an issue on i386 left, and at least from looking at the CI tests, it might have been caused by this fix: https://salsa.debian.org/3dprinting-team/cura-engine/-/pipelines Any ideas? I have only an old and super slow notebook here on vacation, so can't really do any C++ debugging now. Christoph
Bug#1040191: [3dprinter-general] Bug#1040191: marked as pending in libnest2d
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
Bug#1040191: marked as pending in libnest2d
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 depends on the installation architecture: Right, I wasn't really happy about making it Arch:any either, but I didn't want to disentangle the cmake files, not knowing if other packages hook into that check somehow. The cost of the change isn't high (small .deb files on the mirrors), and it's still easy to revert if we find a better fix. The whole set of cura packages still has much bigger problems, there's a few failing autopkgtests... :( Christoph
Bug#1040191: marked as pending in libnest2d
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: https://salsa.debian.org/3dprinting-team/libnest2d/-/commit/7b403bf674b3c5798ab6a775f551b1a1ccbbb10a Cmake files check for matching architecture width now, mark package as Arch: any * Cmake files check for matching architecture width now, mark package as Arch: any. (The header files themselves do not change. Closes: #1040191) * Drop M-A: foreign. (this message was generated automatically) -- Greetings https://bugs.debian.org/1040191
Bug#1031680: marked as pending in uranium
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: https://salsa.debian.org/3dprinting-team/uranium/-/commit/8e6f6055c13fcc1b5b25aa5a207ef8d5dab03a4c Compile against current python version. (Closes: #1031680) (this message was generated automatically) -- Greetings https://bugs.debian.org/1031680
Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye
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
Bug#1034210: python3-charon: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
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
Bug#1032930: closing 1032930
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
Bug#1030048: pgpool2: CVE-2023-22332
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, Christoph
Bug#1030048: marked as pending in pgpool2
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: https://salsa.debian.org/postgresql/pgpool2/-/commit/0533b06b7737b73123df72209680ae0400d12a8d New upstream version 4.3.5. (Closes: #1030048) + Fixes Information disclosure vulnerability CVE-2023-22332: A specific database user's authentication information may be obtained by another database user. As a result, the information stored in the database may be altered and/or database may be suspended by a remote attacker who successfully logged in the product with the obtained credentials. (this message was generated automatically) -- Greetings https://bugs.debian.org/1030048
Bug#1026633: Info received (Grig)
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
Bug#1026856: [3dprinter-general] Bug#1026856: cura-engine: FTBFS: 14 tests segfault
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 also gave updating to 5.2.2 a try, but the whole buildsystem has changed and it seems to require a whole new set of patches. Alpine has this: https://git.alpinelinux.org/aports/tree/community/libarcus which seems like a good starting point, but it's likely not doing the right thing wrt to Debian's Pythons versions handling. If someone with more clue than me about sip (is that still needed?), cmake, and pybuild could pick that up, that would be nice. Christoph
Bug#1025777: qcustomplot: autopkgtest regression: collect2: error: ld returned 1 exit status
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 object CMakeFiles/plots.dir/mainwindow.cpp.o /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp: In member function ‘void MainWindow::on_actionSave_Document_triggered()’: /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp:127:59: warning: ‘QRect QPrinter::pageRect() const’ is deprecated: Use pageLayout().paintRectPixels(resolution()) instead. [-Wdeprecated-declarations] 127 | ui->textEdit->document()->setPageSize(printer.pageRect().size()); | ^~ In file included from /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/qprintengine.h:45, from /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/QtPrintSupport:14, from /usr/include/qcustomplot.h:97, from /tmp/tmp.T3AXT8d62g/src/qcpdocumentobject.h:34, from /tmp/tmp.T3AXT8d62g/src/mainwindow.h:32, from /tmp/tmp.T3AXT8d62g/src/mainwindow.cpp:26: /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport/qprinter.h:259:11: note: declared here 259 | QRect pageRect() const; | ^~~~ [ 83%] Building CXX object CMakeFiles/plots.dir/qcpdocumentobject.cpp.o NMU diff: https://salsa.debian.org/science-team/qcustomplot/-/merge_requests/5 Christoph
Bug#1024100: marked as pending in libxtrx
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: https://salsa.debian.org/debian-hamradio-team/libxtrx/-/commit/5878b273c7bf61f13edb23a225e786b296edd9fa Build against qcustomplot 2.1. (Closes: #1024100) (this message was generated automatically) -- Greetings https://bugs.debian.org/1024100
Bug#1024101: marked as pending in js8call
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: https://salsa.debian.org/debian-hamradio-team/js8call/-/commit/5b8cf1247227b8189fbac3b26a32bfc87e286a45 Build against qcustomplot 2.1.0. (Closes: #1024101) (this message was generated automatically) -- Greetings https://bugs.debian.org/1024101
Bug#1024104: marked as pending in wsjtx
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: https://salsa.debian.org/debian-hamradio-team/wsjtx/-/commit/44bdf2e9dddfee0ca2b1a01550fa9c51a00974c3 Build against qcustomplot 2.1.0. (Closes: #1024104) (this message was generated automatically) -- Greetings https://bugs.debian.org/1024104
Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content
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 innocent and claiming that this would be "cancel culture", you are effectively promoting these views. The problem is within bs1770gain, not the rest of Debian. > I removed the controversial text from the running program in response to > #913352, and see no point is doing anything more with that issue. That is by far not enough. The homepage header is still pointing directly to a page with clear nazi content. And even if you remove that, the racism/fascist/nazi crap still part of the source code that we ship. > The bs1770gain program is an excellent tool to adjust the sound level of > media files, and I do not care much about any real or percived political > views of its author. I see no need to spend time studying it, nor > comment on my view of it, in a Debian context. It's not just "views" of the author. The crap is deeply embedded into the source code. This thing needs to go. Christoph
Bug#1024493: Proposed-RM: bs1770gain -- RoQA; inappropriate content
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. +1. The homepage is full of nazi symbols. Let's get rid of it. > If there are no objections from the maintainers, I'll reassign this to > ftp.d.o in the next days. Might be worth considering removal from stable as well. Christoph
Bug#1024101: js8call: QCustomPlot transition
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 some lower severity to inform, and raise to RC when the package is in unstable. At the moment, this bug is RC but it isn't actionable. Christoph
Bug#1012538: marked as pending in chirp
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: https://salsa.debian.org/debian-hamradio-team/chirp/-/commit/f8eec65c1efb93fb30a81b4c11c08a160ee55066 New upstream version 20221106+py3. Switch upstream to github. (Closes: #1012538) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012538
Bug#1012538: knocked out usability - module 'collections' has no attribute 'Callable'
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
Bug#1022478: closing 1022478
close 1022478 1.4.2-2 thanks
Bug#1022522: closing 1022522
close 1022522 1:2.0.10-5 thanks
Bug#1022490: closing 1022490
close 1022490 2.17-1 thanks
Bug#1022398: bladerf: FTBFS: dh_install: error: missing files, aborting
> > # 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 bladerf-tool script to debian/tmp/usr/local/bin > >dh_install > > dh_install: warning: Cannot find (any matches for) > > "usr/lib/python3*/site-packages/*" (tried in ., debian/tmp) The problem here is that setup.py installs into tmp/usr/local despite being told to use --prefix=/usr. I have no idea why it's doing that and couldn't find a sane fix, so I added a "mv usr/local usr" workaround to debian/rules. Christoph
Bug#1022398: marked as pending in bladerf
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: https://salsa.debian.org/debian-hamradio-team/bladerf/-/commit/3b2c203682dede808731068ef37755c8514f853e Fix installation of python bindings. (Closes: #1022398) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022398
Bug#1022487: closing 1022487
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 Lilley Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz
Bug#1022535: marked as pending in pg-repack
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: https://salsa.debian.org/postgresql/pg-repack/-/commit/468cd2fd512f176f95d7c574ca1a3f46aaeffeff New upstream version. Upload for PostgreSQL 15. (Closes: #1022535) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022535
Bug#1022507: marked as pending in postgresql-plsh
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: https://salsa.debian.org/postgresql/postgresql-plsh/-/commit/2dc59db2e036900e5fb1cf2b43aed9d69a9f8f9e New upstream version. * Upload for PostgreSQL 15. (Closes: #1022507) * debian/watch: Look at GitHub tags instead of releases. (this message was generated automatically) -- Greetings https://bugs.debian.org/1022507
Bug#1021859: marked as pending in pgbouncer
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: https://salsa.debian.org/postgresql/pgbouncer/-/commit/af952a729f59ca41d8ccd5a24c960eca37ccdb29 Cherry-pick 04ff38b25e from upstream to fix tests. (Closes: #1021859, but needs 4a6de748d3 in postgresql-15 as well) (this message was generated automatically) -- Greetings https://bugs.debian.org/1021859
Bug#1022152: marked as pending in postgresql
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: https://salsa.debian.org/postgresql/postgresql/-/commit/3500c73817462c0d1588d9fc13dc83554a8c62a3 Stop building lib packages, postgresql-15 is already in unstable.. (Closes: #1022152) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022152
Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
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
Bug#1021791: Testsuite needs updated permissions with PostgreSQL 15
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 to "grant create on schema public to public;" to revert to
the old default.
https://ci.debian.net/data/autopkgtest/testing/arm64/r/redmine/27072176/log.gz
Setting up redmine (5.0.2-2) ...
[33mDon't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.[0m
dbconfig-common: writing config to
/etc/dbconfig-common/redmine/instances/default.conf
creating postgres user redmine/instances/default: already exists.
resetting password: success.
creating database redmine_default: already exists.
dbconfig-common: flushing administrative password
rake aborted!
ActiveRecord::StatementInvalid: PG::InsufficientPrivilege: ERROR: permission
denied for schema public
LINE 1: CREATE TABLE "schema_migrations" ("version" character varyin...
^
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
`exec'
/usr/share/rubygems-integration/all/gems/activerecord-6.1.7/lib/active_record/connection_adapters/postgresql/database_statements.rb:49:in
`block (2 levels) in execute'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/dependencies/interlock.rb:48:in
`block in permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activesupport-6.1.7/lib/active_support/concurrency/share_lock.rb:187:in
`yield_shares'
(Possibly this might need fixing in dbconfig-common.)
Christoph
Bug#1019340: Segfaults on startup
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 then since it doesn't affect me in the sense I'm not using the package (though I probably should once I start doing more VHF contests). But something in there is quite broken, it was still crashing here when I wrote the previous mail. Christoph DF7CB
Bug#1019340: Segfaults on startup
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
Bug#1019340: tucnak: Segfaults on startup
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 driver: swrast libGL error: core dri or dri2 extension not found libGL error: failed to load driver: swrast GLib: unsetenv() is not thread-safe and should not be used after threads are created dbind: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/130/at-spi/bus_0: Datei oder Verzeichnis nicht gefunden GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ Speicherzugriffsfehler (Speicherabzug geschrieben) Christoph
Bug#1019340: Segfaults on startup
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 think last time I actually tried to find some documentation on how to use it, but didn't find anything. (So I ended up using tlf to log a VHF+ contest which is less than ideal because it really doesn't like frequencies that have too many digits.) > Perhaps related to differences in windowing > setups? I'm running xwayland and Gnome. X and awesome here, no desktop environment. > I will poke through the libzia changes. Thanks Christoph
Bug#1019340: Segfaults on startup
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 trace of thread 1472741: #0 0x7febdaa8983c __pthread_kill_implementation (libc.so.6 + 0x8983c) #1 0x7febdaa3da52 __GI_raise (libc.so.6 + 0x3da52) #2 0x7febdaa28469 __GI_abort (libc.so.6 + 0x28469) #3 0x7febdaa28395 __assert_fail_base (libc.so.6 + 0x28395) #4 0x7febdaa36b02 __GI___assert_fail (libc.so.6 + 0x36b02) #5 0x7febd80aa3bf n/a (libGLX.so.0 + 0x53bf) #6 0x7febdc1418a3 n/a (libSDL2-2.0.so.0 + 0x10d8a3) #7 0x7febdc114aba n/a (libSDL2-2.0.so.0 + 0xe0aba) #8 0x7febdc115de6 n/a (libSDL2-2.0.so.0 + 0xe1de6) #9 0x7febdc115ee1 n/a (libSDL2-2.0.so.0 + 0xe1ee1) #10 0x7febdc0650b2 n/a (libSDL2-2.0.so.0 + 0x310b2) #11 0x7febdc0654f8 n/a (libSDL2-2.0.so.0 + 0x314f8) #12 0x5586f25c0438 tucnak_crash (tucnak + 0xb0438) #13 0x7febdc3589d4 z_sig_segv (libzia-4.36.so + 0x169d4) #14 0x7febdaa3daf0 __restore_rt (libc.so.6 + 0x3daf0) #15 0x7febd5ead5ee n/a (crocus_dri.so + 0xad5ee) #16 0x7febd80836e6 glPrimitiveBoundingBox (libGLX_mesa.so.0 + 0x4e6e6) #17 0x7febd8085d32 glPrimitiveBoundingBox (libGLX_mesa.so.0 + 0x50d32) #18 0x7febd80860d3 glPrimitiveBoundingBox (libGLX_mesa.so.0 + 0x510d3) #19 0x7febd5eaf0df n/a (crocus_dri.so + 0xaf0df) #20 0x7febd5eaf21f n/a (crocus_dri.so + 0xaf21f) #21 0x7febd5eb2205 n/a (crocus_dri.so + 0xb2205) #22 0x7febd5f85c92 n/a (crocus_dri.so + 0x185c92) #23 0x7febd5f85f9a n/a (crocus_dri.so + 0x185f9a) #24 0x7febd5eb1de4 n/a (crocus_dri.so + 0xb1de4) #25 0x7febd5eb4d51 n/a (crocus_dri.so + 0xb4d51) #26 0x7febd8077efc n/a (libGLX_mesa.so.0 + 0x42efc) #27 0x7febd80687f2 n/a (libGLX_mesa.so.0 + 0x337f2) #28 0x7febd80a87e3 n/a (libGLX.so.0 + 0x37e3) #29 0x7febd80a9116 n/a (libGLX.so.0 + 0x4116) #30 0x7febd80aa378 n/a (libGLX.so.0 + 0x5378) #31 0x7febdc1418a3 n/a (libSDL2-2.0.so.0 + 0x10d8a3) #32 0x7febdc114aba n/a (libSDL2-2.0.so.0 + 0xe0aba) #33 0x7febdc0a7daa n/a (libSDL2-2.0.so.0 + 0x73daa) #34 0x7febdc0a9e0a n/a (libSDL2-2.0.so.0 + 0x75e0a) #35 0x7febdc09d981 n/a (libSDL2-2.0.so.0 + 0x69981) #36 0x7febdc09fda9 n/a (libSDL2-2.0.so.0 + 0x6bda9) #37 0x7febdc087d3a n/a (libSDL2-2.0.so.0 + 0x53d3a) #38 0x7febdc08e11d n/a (libSDL2-2.0.so.0 + 0x5a11d) #39 0x7febdc08deb6 n/a (libSDL2-2.0.so.0 + 0x59eb6) #40 0x7febdc13a02c n/a (libSDL2-2.0.so.0 + 0x10602c) #41 0x7febdc13b6db n/a (libSDL2-2.0.so.0 + 0x1076db) #42 0x7febdc087e33 n/a (libSDL2-2.0.so.0 + 0x53e33) #43 0x5586f2631edb sdl_event_thread (tucnak + 0x121edb) #44 0x7febdc279c0d n/a (libglib-2.0.so.0 + 0x7ec0d) #45 0x7febdaa87b27 start_thread (libc.so.6 + 0x87b27) #46 0x7febdab0a78c __clone3 (libc.so.6 + 0x10a78c) Stack trace of thread 1472737: #0 0x7febdaaa13db __memmove_sse2_unaligned_erms (libc.so.6 + 0xa13db) #1 0x7febd5f72904 n/a (crocus_dri.so + 0x172904) #2 0x7febd5f34f9d n/a (crocus_dri.so + 0x134f9d) #3 0x7febd5f3831d n/a (crocus_dri.so + 0x13831d) #4 0x7febd5f3e928 n/a (crocus_dri.so + 0x13e928) #5 0x7febdc0a8949 n/a (libSDL2-2.0.so.0 + 0x74949) #6 0x7febdc0a0fc9 n/a (libSDL2-2.0.so.0 + 0x6cfc9) #7 0x7febdc1110f9 n/a (libSDL2-2.0.so.0 + 0xdd0f9) #8 0x7febdc11222c n/a (libSDL2-2.0.so.0 + 0xde22c) #9 0x5586f26337da progress (tucnak + 0x1237da) #10 0x5586f258bb05 main (tucnak + 0x7bb05) #11 0x7febdaa2920a __libc_start_call_main (libc.so.6 + 0x2920a) #12 0x7febdaa292bc __libc_start_main_impl (libc.so.6 + 0x292bc) #13 0x5586f258c0d1 _start (tucnak + 0x7c0d1) Stack trace of thread 1472740: #0 0x7febdaa847ea __futex_abstimed_wait_common64 (libc.so.6 + 0x847ea)
Bug#1017706: marked as pending in postgresql-set-user
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: https://salsa.debian.org/postgresql/postgresql-set-user/-/commit/9b495559b8897ad749d68bc817a3d90eadaae8f1 Add actual description, thanks Jérémy Lal. (Closes: #1017706) (this message was generated automatically) -- Greetings https://bugs.debian.org/1017706
Bug#1015049: thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
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 failed to build > on amd64. > > [1;31;49m*** 6 failures are detected in the test module > > "TSocketInterruptTest" > > [0;39;49mFAIL: TInterruptTest Fwiw thrift builds fine for me. Christoph
Bug#1012903: marked as pending in bladerf
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: https://salsa.debian.org/debian-hamradio-team/bladerf/-/commit/bf52043433e9e6fea378861cf1d42f3464f1c528 Fix build failure with gcc-12. (Closes: #1012903) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012903
Bug#1012538: knocked out usability - module 'collections' has no attribute 'Callable'
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
Bug#1002166: RM: sdrangelove -- RoM; dead upstream
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: lu...@debian.org > > Usertags: ftbfs-20211220 ftbfs-bookworm > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > sdrangelove hasn't really been touched upstream since 2015 (except 3 > more or less boring git commits), so I propose we remove it. Doing that now: Please remove sdrangelove from unstable. Christoph
Bug#1005611: marked as pending in pgbadger
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: https://salsa.debian.org/postgresql/pgbadger/-/commit/2973f8e7de0e039d0120b15522969367231eed48 Fix test failure in syslog test. (Closes: #1005611) (this message was generated automatically) -- Greetings https://bugs.debian.org/1005611
Bug#1003962: Fails with --buildsystem=cmake if builddirectory contains package version with ~ tilde
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 doesn't start with /.
Note how PKGBUILDDIR is duplicated:
dh build-arch --buildsystem=pybuild --with python3 --with sip3
dh_update_autotools_config -a -O--buildsystem=pybuild
dh_autoreconf -a -O--buildsystem=pybuild
dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_configure --buildsystem=cmake
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" -- [...]
...
dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:237: dh_auto_build --buildsystem=cmake
--builddirectory="'/<>/.pybuild/cpython3_3.10/build'" --
cd '/<>/pynest2d-4.13\~beta/.pybuild/cpython3_3.10/build' &&
make -j4 "INSTALL=install --strip-program=true" VERBOSE=1
make[1]: Entering directory
'/<>/'/<>/.pybuild/cpython3_3.10/build''
(For whatever reason make is still happy with the borked path at that point...)
...
/usr/bin/cmake -E touch
/<>/'/<>/.pybuild/cpython3_3.10/build'/src/sippynest2dpart0.cpp
[...]
cmake -E touch: failed to update
"/<>//<>/.pybuild/cpython3_3.10/build/src/sippynest2dpart0.cpp".
I suspect the error is in /usr/share/dh-python/dhpython/build/plugin_cmake.py:
return ('dh_auto_build --buildsystem=cmake'
' --builddirectory="{build_dir}"'
If I replace "{build_dir}" by {build_dir} in that file, the build
succeeds.
Christoph
Bug#1002121: marked as pending in gr-limesdr
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: https://salsa.debian.org/debian-hamradio-team/gr-limesdr/-/commit/6786822db8977e432157a2e270c76eb547e4599c Add patch by Chris Gorman, NZSmartie, and Daniel Estévez to support GNUradio 3.9. (Closes: #1002121) (this message was generated automatically) -- Greetings https://bugs.debian.org/1002121
Bug#1001811: marked as pending in postgresql-mysql-fdw
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: https://salsa.debian.org/postgresql/postgresql-mysql-fdw/-/commit/28e57b9486b6c2d2221b82134f3c4a2eafc27be0 Disable jit for tests; works around "failed to resolve name __mulodi4". Cf. https://github.com/EnterpriseDB/mysql_fdw/pull/227. Closes: #1001811 (this message was generated automatically) -- Greetings https://bugs.debian.org/1001811
Bug#1002166: sdrangelove: FTBFS: gnuradiothread.cpp:139:23: error: no matching function for call to ‘gr::top_block::connect(osmosdr::source::sptr&, int, gr_adaptor_sptr&, int)’
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 amd64. sdrangelove hasn't really been touched upstream since 2015 (except 3 more or less boring git commits), so I propose we remove it. (... and I should finally get around to upload sdrangel.) Christoph
Bug#993699: marked as pending in libxtrx
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: https://salsa.debian.org/debian-hamradio-team/libxtrx/-/commit/d7fecfef1db7054c56c2691bb750242d7e9caed2 Team upload. * Apply upstream patch for soapysdr 0.8 (Closes: #993699) * Bump soapysdr build-dependency to 0.8 * Change all references to soapysdr in debian packaging from 0.7 to 0.8 (this message was generated automatically) -- Greetings https://bugs.debian.org/993699
Bug#984131: flmsg: ftbfs with GCC-11
> 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 upstream version 4.0.19 which I just pushed to
git probably works better with gcc-11, but has problems with xmlrpc:
g++ -DHAVE_CONFIG_H -I. -I. -I./include -I/usr/include/flxmlrpc -Wdate-time
-D_FORTIFY_SOURCE=2 -I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
-I/usr/include/cairo -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I.
-I./include -pipe -Wall -fexceptions -O2 -ffast-math -finline-functions
-fomit-frame-pointer -DNDEBUG -I/usr/include/flxmlrpc -g -O2
-ffile-prefix-map=/srv/projects/afu/flmsg/flmsg=. -fstack-protector-strong
-Wformat -Werror=format-security -c -o blank-dnd/flmsg-dnd_tab.o `test -f
'blank-dnd/dnd_tab.cxx' || echo './'`blank-dnd/dnd_tab.cxx
flmsg.cxx: In function ‘int main(int, char**)’:
flmsg.cxx:1927:17: error: ‘set_pname’ is not a member of ‘XmlRpc’
1927 | XmlRpc::set_pname(pname);
| ^
(I have no plans to fix this since I don't use flmsg.)
Christoph
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
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 understand the newer hash yet. Thanks! Sébastien: The cl-uax-15 autopkgtest is failing: https://qa.debian.org/excuses.php?package=cl-uax-15 (I can reproduce the clisp error here, but not the segfault.) Christoph
Bug#995846: closing 995846
close 995846 3.6.3-1 thanks
Bug#1001482: marked as pending in restrictedpython
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: https://salsa.debian.org/python-team/packages/restrictedpython/-/commit/7e76a5b22f34863ac88bdab3b0fb6f18e2694395 d/tests: Use autodep8 test instead of the zope no-op one. (Closes: #909487, #1001482) (this message was generated automatically) -- Greetings https://bugs.debian.org/1001482
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
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
Bug#997614: marked as pending in python-parse-type
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: https://salsa.debian.org/python-team/packages/python-parse-type/-/commit/f84cbe916839895c0db4d9610340bc33718527ef New upstream version 0.5.6. * Remove obsolete use_2to3 marker. (Closes: #997614) * Bump python3-parse dependency to 1.19.0. (this message was generated automatically) -- Greetings https://bugs.debian.org/997614
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
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 the FUNCTION type > specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp Looking around for something else I discovered #999625 in cl-esrap which fixes this problem. I uploaded the fix in an NMU. (I guess you might also take over that package?) But pgloader still doesn't build: :( ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/abnf/abnf-tmp5FHTGX61.fasl ; compilation finished in 0:00:00.080 While evaluating the form starting at line 21, column 0 of #P"/srv/projects/postgresql/pgloader/pgloader/dumper-2SKVI5f7.lisp":Fatal TYPE-ERROR: The values (# NIL NIL) are not of type (VALUES FUNCTION ) (DUMPER518::BACKTRACE-AS-LIST) ; ; compilation unit aborted ; caught 1 fatal ERROR condition ; caught 51 STYLE-WARNING conditions ; printed 4719 notes Christoph
Bug#997632: marked as pending in behave
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: https://salsa.debian.org/python-team/packages/behave/-/commit/686bd31e88240b0e02a4ad33f7ffbdb51840d750 setup.py: Remove 2to3 attribute. (Closes: #997632) (this message was generated automatically) -- Greetings https://bugs.debian.org/997632
Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
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: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp ; in: DEFUN CALL-WITH-OUTPUT ; (WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; (FUNCALL FUNCTION STREAM)) ; --> LET ; ==> ; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; ; note: could not stack allocate: ;(WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE ELEMENT-TYPE) ; (FUNCALL FUNCTION STREAM)) ; in: DEFUN SLURP-STREAM-STRING ; (WITH-OUTPUT-TO-STRING ; (UIOP/STREAM::OUTPUT NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; (UIOP/STREAM:COPY-STREAM-TO-STREAM UIOP/STREAM::INPUT UIOP/STREAM::OUTPUT ; :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)) ; --> LET ; ==> ; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE) ; ; note: could not stack allocate: ;(WITH-OUTPUT-TO-STRING (OUTPUT NIL :ELEMENT-TYPE ELEMENT-TYPE) ; (COPY-STREAM-TO-STREAM INPUT OUTPUT :ELEMENT-TYPE ELEMENT-TYPE)) ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-tmpGHU3ALSV.fasl ; compilation finished in 0:00:05.412 ; ; compilation unit finished ; printed 2 notes ;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; loading system "asdf-finalizers" ;; loading system "asdf-system-connections" ;; loading system "cffi" ;; loading system "cl+ssl" ;; loading system "mssql" ;; loading file #P"/srv/projects/postgresql/pgloader/pgloader/src/hooks.lisp" ;; loading system "pgloader" Fatal SIMPLE-ERROR: Compilation failed: * is not permitted as an argument to the FUNCTION type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp cat buildapp.log ;; loading file #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; loading #P"/usr/share/common-lisp/source/cl-asdf/build/asdf.lisp" ;; # ;; # ;; (:ASDF3.3 :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :NON-BASE-CHARS-EXIST-P :ASDF-UNICODE :X86-64 :GENCGC :64-BIT :ANSI-CL ... ; processing (DEFVAR *CURRENT-RULE* ...) ; processing (DEFUN COMPILE-RULE ...) ; processing (DEFUN EVAL-EXPRESSION ...) ; processing (DECLAIM (FTYPE # ...)) 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 the FUNCTION type specifier in /usr/share/common-lisp/source/esrap/src/evaluator.lisp (DUMPER518::BACKTRACE-AS-LIST) ; wrote /srv/projects/postgresql/pgloader/pgloader/debian/home/.cache/common-lisp/sbcl-2.1.11.debian-linux-x64/usr/share/common-lisp/source/esrap/src/evaluator-tmpT2G5POAL.fasl ; compilation finished in 0:00:00.144 ; ; compilation unit aborted ; caught 2 fatal ERROR conditions ; caught 48 STYLE-WARNING conditions ; printed 4591 notes I have to admit that I have no clue where to even start debugging this, there is no file called "dumper" in the source tree. Would it be possible that you could have a look? Christoph
Bug#1000589: Incompatible with PostgreSQL 14
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 testing. Christoph
Bug#1000512: marked as pending in psqlodbc
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: https://salsa.debian.org/postgresql/psqlodbc/-/commit/a31db0b2aa8a4c6580c9cfebfa5845ffe711e3a0 Depend on odbcinst. (Closes: #1000512) (this message was generated automatically) -- Greetings https://bugs.debian.org/1000512
Bug#995999: FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
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: > > Package: prometheus > > Version: 2.24.1+ds-1 > > Severity: serious > > X-Debbugs-Cc: z...@debian.org > > > > Hi, > > > > When rebuild packages, I find it FTBFS. > > > > === RUN TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks > > --- FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks (0.05s) > > panic: runtime error: slice bounds out of range [:104326] with capacity > > 104293 [recovered] > > panic: runtime error: slice bounds out of range [:104326] with capacity > > 104293 > > > > goroutine 7 [running]: > > testing.tRunner.func1.2(0x60da60, 0xc0005f8030) > > /usr/lib/go-1.16/src/testing/testing.go:1143 +0x332 > > testing.tRunner.func1(0xc01e00) > > /usr/lib/go-1.16/src/testing/testing.go:1146 +0x4b6 > > panic(0x60da60, 0xc0005f8030) > > /usr/lib/go-1.16/src/runtime/panic.go:965 +0x1b9 > > github.com/prometheus/prometheus/tsdb/chunks.TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks(0xc01e00) > > > > /build/1st/prometheus-2.24.1+ds/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:122 > > +0xc9c > > testing.tRunner(0xc01e00, 0x637600) > > /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef > > created by testing.(*T).Run > > /usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3 > > FAILgithub.com/prometheus/prometheus/tsdb/chunks0.116s > > > > > > It also FTBFS on tests.reproducible-builds.org, ci.debian.net > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html > > https://ci.debian.net/data/autopkgtest/unstable/amd64/p/prometheus/15535224/log.gz > > > > -- > Martina Ferrari (Tina) Christoph
