Bug#909352: marked as done (Is squeak-plugins-scratch still useful?)
Your message dated Sun, 09 Jun 2024 04:30:20 + with message-id and subject line Bug#1072784: Removed package(s) from unstable has caused the Debian Bug report #909352, regarding Is squeak-plugins-scratch still useful? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 909352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squeak-plugins-scratch Severity: serious Tags: buster sid Bernhard Übelacker noticed in #892016: <-- snip --> When just installing the packages the plugin so.CameraPlugin gets used from the package squeak-plugins-scratch. But a similar so.CameraPlugin is already packaged with squeak-vm. squeak-vm: /usr/lib/squeak/4.10.2.2614/so.CameraPlugin squeak-plugins-scratch: /usr/lib/scratch/plugins/so.CameraPlugin So this probably should be clarified if the plugins are really needed in both packages. <-- snip --> At first sight I would say that all plugins in squeak-plugins-scratch are already shipped by squeak-vm, but I might be missing something. --- End Message --- --- Begin Message --- Version: 1.4.0.2~svn.r83-3.1+rm Dear submitter, as the package squeak-plugins-scratch has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1072784 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1065944: marked as done (squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you mean ‘pclose’? [-Werror=implicit-function-declarat
Your message dated Sun, 09 Jun 2024 04:30:20 +
with message-id
and subject line Bug#1072784: Removed package(s) from unstable
has caused the Debian Bug report #1065944,
regarding squeak-plugins-scratch: FTBFS on arm{el,hf}: WeDoLinux.c:175:9:
error: implicit declaration of function ‘close’; did you mean ‘pclose’?
[-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1065944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squeak-plugins-scratch
Version: 1.4.0.2~svn.r83-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=squeak-plugins-scratch=armel=1.4.0.2%7Esvn.r83-3.1%2Bb1=1710056636=0
cd wedo/ && \
arm-linux-gnueabi-gcc -std=gnu89 -g -O2
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -g -fPIC -c *.c
WeDoLinux.c: In function ‘WeDoClosePort’:
WeDoLinux.c:175:9: error: implicit declaration of function ‘close’; did you
mean ‘pclose’? [-Werror=implicit-function-declaration]
175 | close(fdWeDo);
| ^
| pclose
cc1: some warnings being treated as errors
make: *** [debian/rules:31: build-stamp] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.4.0.2~svn.r83-3.1+rm
Dear submitter,
as the package squeak-plugins-scratch has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1072784
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1042316: marked as done (python-efilter: FTBFS: make: *** [debian/rules:6: clean] Error 25)
Your message dated Sun, 09 Jun 2024 04:31:46 +
with message-id
and subject line Bug#1072788: Removed package(s) from unstable
has caused the Debian Bug report #1042316,
regarding python-efilter: FTBFS: make: *** [debian/rules:6: clean] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-efilter
Version: 1.5-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:240: python3.11 setup.py clean
> error in efilter setup command: 'install_requires' must be a string or list
> of strings containing valid project/version requirement specifiers; Expected
> end or semicolon (after version specifier)
> pytz >= 2011k
> ~~~^
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:6: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/python-efilter_1.5-2.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.5-2.1+rm
Dear submitter,
as the package python-efilter has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1072788
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1072828: texlive-binaries upgrade breaks therion build
On Sun, Jun 09, 2024 at 12:02:02AM +0200, Preuße, Hilmar wrote: > On 08.06.2024 16:09, Adrian Bunk wrote: > > Hi, Hi Hilmar, >... > Hence I tend to say this is something specific for sbuild environments, > which could have lower priority than "serious". all testing I did for the below statement was plain dpkg-buildpackage in a chroot. > > Downgrading texlive-binaries to 2023.20230311.66589-9 OR > > installing texlive-fonts-recommended works around this issue. > > Why not simply adding texlive-fonts-recommended to BD (which carries the > Type1 fonts of logo10) and then solve the issue? >... Because that doesn't fix whatever the bug is, which might also affect other packages or users. a minimal example inside therion-6.2.1/thbook/ after a failed build seems to be TEXINPUTS="/<>/build/thbook;." /usr/bin/pdftex --output-dir=/<>/build/thbook thbook.tex Did anything break or change regarding --output-dir ? In the working case with the old version the generated file is in debian/.debhelper/generated/_source/home/.texlive2023/texmf-var/fonts/pk/ljfour/public/knuth-lib/logo10.720pk > H. cu Adrian
Bug#1071114: marked as done (plover: unhandled symlink to directory conversion: /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets)
Your message dated Sun, 09 Jun 2024 00:05:53 + with message-id and subject line Bug#1071114: fixed in plover 4.0.0~rc2-0.3 has caused the Debian Bug report #1071114, regarding plover: unhandled symlink to directory conversion: /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1071114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plover Version: 4.0.0~rc2-0.2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: bookworm -> trixie For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 3m55.0s ERROR: installs objects over existing directory symlinks: /usr/lib/python3/dist-packages/plover/assets/american_english_words.txt (plover) != /usr/share/plover/assets/american_english_words.txt (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/commands.json (plover) != /usr/share/plover/assets/commands.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/main.json (plover) != /usr/share/plover/assets/main.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/plover.png (plover) != /usr/share/plover/assets/plover.png (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets /usr/lib/python3/dist-packages/plover/assets/user.json (plover) != /usr/share/plover/assets/user.json (?) /usr/lib/python3/dist-packages/plover/assets -> ../../../../share/plover/assets cheers, Andreas plover_4.0.0~rc2-0.2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: plover Source-Version: 4.0.0~rc2-0.3 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of plover, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1071...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated plover package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jun 2024 19:40:06 -0400 Source: plover Architecture: source Version: 4.0.0~rc2-0.3 Distribution: unstable Urgency: medium Maintainer: Harlan Lieberman-Berg Changed-By: Boyuan Yang Closes: 1071114 Changes: plover (4.0.0~rc2-0.3) unstable; urgency=medium . * Non-maintainer upload. * debian/plover.maintscript: Add symlink_to_dir helper to fix unhandled conversion from symlink to directory. (Closes:
Processed: control
Processing commands for cont...@bugs.debian.org: > severity 1072126 important Bug #1072126 [src:frr] frr: CVE-2024-31948 Severity set to 'important' from 'grave' > quit Stopping processing here. Please contact me if you need assistance. -- 1072126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072828: texlive-binaries upgrade breaks therion build
On 08.06.2024 16:09, Adrian Bunk wrote: Hi, https://buildd.debian.org/status/fetch.php?pkg=therion=amd64=6.2.1-1%2Bb1=1717847632=0 ... FAILED: thbook/thbook.pdf /<>/build/thbook/thbook.pdf I can confirm that the failing command works fine on a normal computer..this is a chroot on arm64. hille@rasppi2:~$ mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 logo10 mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input logo10 This is METAFONT, Version 2.71828182 (TeX Live 2025/dev/Debian) (preloaded base=mf) (/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo10.mf (/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo.mf [77] [69] [84] [65] [70] [80] [83] [79] [78]) ) Font metrics written on logo10.tfm. Output written on logo10.600gf (9 characters, 1748 bytes). Transcript written on logo10.log. mktexpk: /home/hille/.texlive2024/texmf-var/fonts/pk/ljfour/public/knuth-lib/logo10.600pk: successfully generated. /home/hille/.texlive2024/texmf-var/fonts/pk/ljfour/public/knuth-lib/logo10.600pk hille@rasppi2:~$ Hence I tend to say this is something specific for sbuild environments, which could have lower priority than "serious". Downgrading texlive-binaries to 2023.20230311.66589-9 OR installing texlive-fonts-recommended works around this issue. Why not simply adding texlive-fonts-recommended to BD (which carries the Type1 fonts of logo10) and then solve the issue? We may open a new bug "why does mktexpk does not work in an sbuild?", but this could have a lower priority, IMHO. H. -- sigfault
Bug#1072847: lacme: Post-issuance validation fails in the default configuration
Package: lacme Version: 0.8.2-1 Severity: grave Justification: renders package unusable Let's Encrypt has recently rotated its intermediate certificates [0]. The previous intermediate certificates (lets-encrypt-r[34].pem and lets-encrypt-e[12].pem) are concatenated along side the roots (isrgrootx1.pem and isrg-root-x2.pem) and used as trust anchors for validation of the issued X.509 certificate before its deployment. The new intermediates means the validation step now fails. A quick fix is to add R1[0-4].pem and E[5-9].pem to the certificate bundle, however that will cease to work once Let's Encrypt rotates its intermediates again. A proper fix would be to use the intermediate(s) provided during the issuance step as -untrusted (for chain building). -- Guilhem. [0] https://letsencrypt.org/2024/03/19/new-intermediate-certificates signature.asc Description: PGP signature
Processed: block 1068929 with 1071902
Processing commands for cont...@bugs.debian.org: > block 1068929 with 1071902 Bug #1068929 [src:rust-async-lock] Please update for event-listener 5.x Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ 1068929 was not blocked by any bugs. 1068929 was not blocking any bugs. Added blocking bug(s) of 1068929: 1071902 1072842 was not blocked by any bugs. 1072842 was not blocking any bugs. Added blocking bug(s) of 1072842: 1071902 > thanks Stopping processing here. Please contact me if you need assistance. -- 1068929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068929 1072842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 1071902 with 1068929
Processing commands for cont...@bugs.debian.org: > unblock 1071902 with 1068929 Bug #1071902 [src:rust-event-listener] rust-event-listener: event-listener v5 is considered buggy 1071902 was not blocked by any bugs. 1071902 was blocking: 1069575 Removed blocking bug(s) of 1071902: 1072842 and 1068929 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1072842: rust-async-lock: please update to version 3.0+
Processing control commands: > forcemerge -1 1068929 Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ Bug #1068929 [src:rust-async-lock] Please update for event-listener 5.x Severity set to 'wishlist' from 'normal' 1071902 was blocked by: 1068929 1071902 was blocking: 1069575 Removed blocking bug(s) of 1071902: 1068929 1068929 was blocked by: 1068930 1068929 was not blocking any bugs. Removed blocking bug(s) of 1068929: 1068930 Marked as found in versions rust-async-lock/2.6.0-4. Bug #1072842 [src:rust-async-lock] rust-async-lock: please update to version 3.0+ Marked as found in versions rust-async-lock/2.8.0-1. Added tag(s) patch. Merged 1068929 1072842 -- 1068929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068929 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 1072842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1071902 with 1068929
Processing commands for cont...@bugs.debian.org: > block 1071902 with 1068929 Bug #1071902 [src:rust-event-listener] rust-event-listener: event-listener v5 is considered buggy 1071902 was not blocked by any bugs. 1071902 was blocking: 1069575 Added blocking bug(s) of 1071902: 1068929 > thanks Stopping processing here. Please contact me if you need assistance. -- 1071902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072843: poppler: stopped to build Qt6 lib on i386 without coordination with reverse dependencies
Source: poppler Version: 24.02.0-5 Severity: serious X-Debbugs-Cc: sramac...@debian.org poppler (24.02.0-5) unstable; urgency=medium . * Team upload * Stop building Qt6 library on i386 vs dak rm -Rn -b libpoppler-qt6-3t64 libpoppler-qt6-dev -a i386 W: -a/--architecture implies -p/--partial. Will remove the following packages from unstable: libpoppler-qt6-3t64 | 24.02.0-4 | i386 libpoppler-qt6-dev | 24.02.0-4 | i386 Maintainer: Debian freedesktop.org maintainers --- Reason --- -- Checking reverse dependencies... # Broken Build-Depends: photoqt: libpoppler-qt6-dev qpdfview: libpoppler-qt6-dev texworks: libpoppler-qt6-dev This needs coordination with reverse dependencies. The decision is also somewhat inconsistent. Why is support only dropped on i386 and not the other 32 bit architectures? Cheers -- Sebastian Ramacher
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Hello Chris, > > > Per Debian policy this is not the correct solution for naming conflicts. > > > Both > > > maintainer (teams), please find a policy compliant solution together. > > > > The solution for this one seems correct, it's a Conflict + Replaces because > > both packages provide a "sherlock" library. Am I missing something? > > Do both packages provide the same API? IOW: do they provide the same > "type" of library? > If so, then Conficts/Replaces may be appropriate. > > If they share a name but none of the API / features, then it is not > a correct solution. They do not share the same API. > These descriptions do not sound related at all. In this case, > Conflicts/Replaces is not appropriate. I see your point now, it seems like it should be just "Conflicts", do you agree? None of those 2 packages can/should be renamed. Cheers, -- Samuel Henrique
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Hi Samuel, only replying to your question below, with new questions. * Samuel Henrique [240608 14:04]: > For #1072733: > > Chris > > Per Debian policy this is not the correct solution for naming conflicts. > > Both > > maintainer (teams), please find a policy compliant solution together. > > The solution for this one seems correct, it's a Conflict + Replaces because > both packages provide a "sherlock" library. Am I missing something? Do both packages provide the same API? IOW: do they provide the same "type" of library? If so, then Conficts/Replaces may be appropriate. If they share a name but none of the API / features, then it is not a correct solution. Looking at the package descriptions on tracker.d.o: python-sherlock: distributed inter-process locks with a choice of backend sherlock: Find usernames across social networks These descriptions do not sound related at all. In this case, Conflicts/Replaces is not appropriate. Chris
Bug#1072734: marked as done (prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky)
Your message dated Sat, 08 Jun 2024 17:35:29 + with message-id and subject line Bug#1072734: fixed in prometheus-squid-exporter 1.11.0+ds-3 has caused the Debian Bug report #1072734, regarding prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prometheus-squid-exporter Severity: serious Justification: flaky debci is RC as per RT User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The dh-golang-autopkgtest autopkgtest is flaky, and often fails and then passes upon reruns, independently of the reason why it was triggered. As per RT, this is an RC issue. Example: 98s === RUN TestReadFromSquid 98s panic: runtime error: invalid memory address or nil pointer dereference 98s [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0x653bf4] 98s 98s goroutine 7 [running]: 98s github.com/boynux/squid-exporter/collector.TestReadFromSquid.func1() 98s /tmp/autopkgtest-lxc.tnsof3vy/downtmp/autopkgtest_tmp/build/src/github.com/boynux/squid-exporter/collector/client_test.go:39 +0x44 98s created by github.com/boynux/squid-exporter/collector.TestReadFromSquid in goroutine 6 98s /tmp/autopkgtest-lxc.tnsof3vy/downtmp/autopkgtest_tmp/build/src/github.com/boynux/squid-exporter/collector/client_test.go:37 +0x70 98s FAIL github.com/boynux/squid-exporter/collector 0.010s https://ci.debian.net/packages/p/prometheus-squid-exporter/testing/arm64/47447211/ -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: prometheus-squid-exporter Source-Version: 1.11.0+ds-3 Done: Daniel Swarbrick We believe that the bug you reported is fixed in the latest version of prometheus-squid-exporter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Swarbrick (supplier of updated prometheus-squid-exporter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 08 Jun 2024 17:15:51 + Source: prometheus-squid-exporter Architecture: source Version: 1.11.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Daniel Swarbrick Closes: 1072734 Changes: prometheus-squid-exporter (1.11.0+ds-3) unstable; urgency=medium . * Add new 0004-Fix-racy-TestReadFromSquid.patch (Closes: #1072734) Checksums-Sha1: adaf26b917de109450a8fc66be92b0bb055a0c94 2481 prometheus-squid-exporter_1.11.0+ds-3.dsc f46fff215b179475c006cb0b6a1958c746bd107f 6636 prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz 3782142baee35d6cb6b2f112db4212f509436bb8 8467 prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo Checksums-Sha256: 708aec7c6c888533e300ec8c03e52593d898c15b14a4622b82940b8272b0441b 2481 prometheus-squid-exporter_1.11.0+ds-3.dsc 5faedd8402839366f0224c541725a1d6b31fe70399fc60ac9f24d9ef10b311c0 6636 prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz efba94e6e512562a4c1c226b115cfa316aa34db121ea378661b2ae9568682508 8467 prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo Files: 3074217dc74d4c37d62a163486f91f42 2481 net optional prometheus-squid-exporter_1.11.0+ds-3.dsc bcd5ad7a289a867eac56cd6a46664a9f 6636 net optional prometheus-squid-exporter_1.11.0+ds-3.debian.tar.xz 8671c0754c00eea128f705235b807629 8467 net optional prometheus-squid-exporter_1.11.0+ds-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEEMD9oek78sa58GjWjtwAXP7uAWikFAmZkkpYWHGRzd2FyYnJp Y2tAZGViaWFuLm9yZwAKCRC3ABc/u4BaKaV2EACVRLBb0VrQXng+p8/00j7EifyV gECDkNU3KZzMPnzxRTx2AW/KrnIBugrGeZPNFVKzea/cUhRfDM7/qY3B+4jTjzT1 8G/9l0ePPQRIgo6Fde9wTXjdccNSHz82Ka30Bzniy1QyuljoZxJVHdPGPyNCiGQY VgTYDATnIAlO5F3dHY4Ga2CeLh5HFd64Yhq4BoqzQL6C13SS/iASWzBnSovLcOI0 OCjSG1xk9khwlHfl4dQmuQLk/GFh6nP63N0XtUaIiqaVCQ+Dnvtl6fz6v58eYUTu siENECebDwQYRUNLktt4cRRY3uIChZwfGnfVPYZLnkC8pOOCNdZgMRrvHEbORD4M
Processed: Bug#1072734 marked as pending in prometheus-squid-exporter
Processing control commands: > tag -1 pending Bug #1072734 [src:prometheus-squid-exporter] prometheus-squid-exporter: autopkgtest dh-golang-autopkgtest is flaky Added tag(s) pending. -- 1072734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072734: marked as pending in prometheus-squid-exporter
Control: tag -1 pending Hello, Bug #1072734 in prometheus-squid-exporter 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/go-team/packages/prometheus-squid-exporter/-/commit/708bb10fc172cb1864b723275b1e4b992b6dcc84 Add new 0004-Fix-racy-TestReadFromSquid.patch Closes: #1072734 (this message was generated automatically) -- Greetings https://bugs.debian.org/1072734
Bug#1072835: jpeg-xl: Failing autopkgtests
Source: jpeg-xl Version: 0.9.2-5 Severity: serious Tags: experimental jpeg-xl in experimental has failing autopkgtests. https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/ autopkgtest log excerpt == md5sum: traffic_light-0-ec0.ppm: No such file or directory traffic_light-0-ec0.ppm: FAILED open or read traffic_light-0-ec1.pgm: FAILED open or read md5sum: traffic_light-0-ec1.pgm: No such file or directory md5sum: traffic_light-1-ec0.ppm: No such file or directory traffic_light-1-ec0.ppm: FAILED open or read md5sum: traffic_light-1-ec1.pgm: No such file or directory traffic_light-1-ec1.pgm: FAILED open or read md5sum: traffic_light-2-ec0.ppm: No such file or directory traffic_light-2-ec0.ppm: FAILED open or read md5sum: traffic_light-2-ec1.pgm: No such file or directory traffic_light-2-ec1.pgm: FAILED open or read md5sum: traffic_light-3-ec0.ppm: No such file or directory traffic_light-3-ec0.ppm: FAILED open or read md5sum: traffic_light-3-ec1.pgm: No such file or directory traffic_light-3-ec1.pgm: FAILED open or read md5sum: animation_patches-0-ec0.ppm: No such file or directory animation_patches-0-ec0.ppm: FAILED open or read md5sum: animation_patches-0-ec1.pgm: No such file or directory animation_patches-0-ec1.pgm: FAILED open or read md5sum: animation_patches-1-ec0.ppm: No such file or directory animation_patches-1-ec0.ppm: FAILED open or read md5sum: animation_patches-1-ec1.pgm: No such file or directory animation_patches-1-ec1.pgm: FAILED open or read pq_gradient.pgm: OK md5sum: WARNING: 12 listed files could not be read Thank you, Jeremy Bícha
Bug#1063645: markdown: missing required debian/rules targets build-arch and/or build-indep
If you think about fixing this to keep a reverse dependency in Debian: Please consider porting the reverse dep to some other markdown implementation that is still maintained.
Processed: gertty: FTBFS with SQLAlchemy 2.x
Processing commands for cont...@bugs.debian.org: > tags 1069052 + ftbfs Bug #1069052 [src:gertty] FTBFS with SQLAlchemy 2.x Added tag(s) ftbfs. > retitle 1069052 gertty: FTBFS with SQLAlchemy 2.x Bug #1069052 [src:gertty] FTBFS with SQLAlchemy 2.x Changed Bug title to 'gertty: FTBFS with SQLAlchemy 2.x' from 'FTBFS with SQLAlchemy 2.x'. > severity 1069052 serious Bug #1069052 [src:gertty] gertty: FTBFS with SQLAlchemy 2.x Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1069052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072732: update-shells: duplicates entries when a package includes both aliased and canonical shells
Hi, On Sat, 8 Jun 2024 18:10:04 +0200 Helmut Grohne wrote: > On Fri, Jun 07, 2024 at 10:09:04AM +0200, Helmut Grohne wrote: > > My recent bash upload changes it's shells.d snippet to include both > > aliased and canonical shells, which is right in principle, but it causes > > update-shells to duplicate /usr/bin/bash in /etc/shells. While that's > > not breaking anything yet, it's also not nice and kudos to Johannes for > > spotting it. > > > > It also is easy to fix with the attached patch. Would you kindly apply > > it? > > I fear this aspect currently breaks mmdebstrap's autopkgtests, so this > is an rc bug somewhere. While it isn't technically rc for debianutils, I > hope that the simplest way forward is to just upload debianutils. If you > disagree with this assessment, we'll have to adapt mmdebstrap's > autopkgtests until this bug is fixed, which also works, but is kinda > meh. So I am tentatively raising it to rc severity for debianutils > hoping that you agree and let you downgrade in case you disagree. Thanks for > considering. please CC me on the decision, so that I know how I should upload the next version of mmdebstrap. :) Thanks! cheers, josch signature.asc Description: signature
Processed: Re: update-shells: duplicates entries when a package includes both aliased and canonical shells
Processing control commands: > severity -1 serious Bug #1072732 [debianutils] update-shells: duplicates entries when a package includes both aliased and canonical shells Severity set to 'serious' from 'normal' > affects -1 + mmdebstrap Bug #1072732 [debianutils] update-shells: duplicates entries when a package includes both aliased and canonical shells Added indication that 1072732 affects mmdebstrap -- 1072732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072241: src:manpages: fails to migrate to testing for too long: RC bug and B-D not in testing
Am 31.05.24 um 10:32 schrieb Dr. Tobias Quathamer: I couldn't find any explanation in the commit messages or debian/changelog. What's the reason for all those additional dependencies? Can't we get rid of them? I don't see how they are needed for building the package. I did not get a response, so I went ahead and uploaded a version without all those extra Build-Dependencies. Regards, Tobias OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072834: between: Game no longer works due to server error
Package: between Version: 6+dfsg1-4 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: jvalle...@mailbox.org Dear Maintainer, * What led up to the situation? I installed between and tried to run it. * What exactly did you do (or not do) that was effective (or ineffective)? Run the "between" program. * What was the outcome of this action? The following is printed in the terminal: Screen dimensions for fullscreen mode: 640x480 L4 | Sat Jun 8 11:19:18 2024 (506 ms) | general | Checking if requested video mode (640x480) is available L4 | Sat Jun 8 11:19:18 2024 (506 ms) | general | All resolutions available Max note length in song = 16 Response: 301 Moved Permanently 301 Moved Permanently cloudflare The game window opens and shows the title screen. When I press spacebar, it shows "Locating server..." for a second, and then shows the message "ERROR: Badly formatted response from server." (see attachment). There is no way to continue after this point, except to close the window. * What outcome did you expect instead? The game would be playable. It seems to depend on a server that no longer exists. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable'), (100, 'bookworm-fasttrack') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-21-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages between depends on: ii libc6 2.36-9+deb12u7 ii libgcc-s1 12.2.0-14 ii libgl1 1.6.0-1 ii libglu1-mesa [libglu1] 9.0.2-1.1 ii libsdl1.2debian 1.2.15+dfsg2-8 ii libstdc++6 12.2.0-14 between recommends no packages. between suggests no packages. -- no debconf information OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1072642: marked as done (curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also applies to autopkgtest))
Your message dated Sat, 8 Jun 2024 16:46:46 +0200
with message-id
and subject line Re: Bug#1072642: curl: FTBFS (TESTFAIL: These test cases
failed: 241 507) (also applies to autopkgtest)
has caused the Debian Bug report #1072642,
regarding curl: FTBFS (TESTFAIL: These test cases failed: 241 507) (also
applies to autopkgtest)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1072642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: curl
Version: 8.8.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hello,
I did a local rebuild on sid which failed:
srcdir=. /usr/bin/perl -I. ./runtests.pl -a -p ~flaky ~timing-dependent -n -j35
~300 ~301 ~303 ~304 ~306 ~309 ~310 ~325 ~364 ~400 ~401 ~403 ~406 ~407 ~408 ~409
~410 ~414 ~417 ~560 ~678 ~987 ~988 ~989 ~1112 ~1272 ~1470 ~1561 ~1562 ~1630
~1631 ~1632 ~2034 ~2037 ~2041 ~3000 ~3001 ~3102
Using curl: ../src/curl
[...]
test 0241...[HTTP-IPv6 GET (using ip6-localhost)]
241: protocol FAILED!
There was no content at all in the file log/5/server.input.
Server glitch? Total curl failure? Returned: 7
== Contents of files in the log/5/ dir after test 241
=== Start of file http_ipv6_server.log
16:19:15.385882 Running HTTP IPv6 version on port 36339
16:19:15.385966 Wrote pid 68256 to log/5/server/http_ipv6_server.pid
16:19:15.385990 Wrote port 36339 to log/5/server/http_ipv6_server.port
16:19:16.348256 > Client connect
16:19:16.348285 accept_connection 3 returned 4
16:19:16.348310 accept_connection 3 returned 0
16:19:16.348377 Read 88 bytes
16:19:16.348397 Process 88 bytes request
16:19:16.348427 Got request: GET /verifiedserver HTTP/1.1
16:19:16.348443 Are-we-friendly question received
16:19:16.348471 Wrote request (88 bytes) input to log/5/server.input
16:19:16.348499 Identifying ourselves as friends
16:19:16.348570 Response sent (56 bytes) and written to log/5/server.response
16:19:16.348589 special request received, no persistency
16:19:16.348604 > Client disconnect 0
=== End of file http_ipv6_server.log
=== Start of file http_ipv6_verify.log
* Trying [::1]:36339...
* Connected to ::1 (::1) port 36339
> GET /verifiedserver HTTP/1.1
> Host: [::1]:36339
> User-Agent: curl/8.8.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Length: 17
<
{ [17 bytes data]
* Connection #0 to host ::1 left intact
=== End of file http_ipv6_verify.log
=== Start of file http_ipv6_verify.out
WE ROOLZ: 68256
=== End of file http_ipv6_verify.out
=== Start of file server.cmd
Testnum 241
=== End of file server.cmd
=== Start of file server.response
HTTP/1.1 200 OK
Content-Length: 17
WE ROOLZ: 68256
=== End of file server.response
=== Start of file stderr241
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to ip6-localhost port 36339 after 106 ms: Couldn't
connect to server
=== End of file stderr241
=== Start of file trace241
16:19:16.524170 == Info: Host ip6-localhost:36339 was resolved.
16:19:16.524215 == Info: IPv6: (none)
16:19:16.524217 == Info: IPv4: 31.15.64.248
16:19:16.524231 == Info: Trying 31.15.64.248:36339...
16:19:16.567508 == Info: connect to 31.15.64.248 port 36339 from
192.168.178.20 port 40168 failed: Connection refused
16:19:16.567523 == Info: Failed to connect to ip6-localhost port 36339 after
106 ms: Couldn't connect to server
16:19:16.567663 == Info: Closing connection
=== End of file trace241
[...]
test 0507...[multi interface get with non-existing host name]
lib507 returned 0, when expecting 6
507: exit FAILED
== Contents of files in the log/31/ dir after test 507
=== Start of file server.cmd
Testnum 507
=== End of file server.cmd
=== Start of file stderr507
URL: http://non-existing-host.haxx.se/
Test ended with result 0
=== End of file stderr507
=== Start of file stdout507
HTTP/1.1 200 OK
Date: Wed, 05 Jun 2024 16:19:18 GMT
Server: Apache/2.4.59 (Debian)
Last-Modified: Sun, 14 Feb 2016 17:00:04 GMT
ETag: "0-52bbdd4e2cd00"
Accept-Ranges: bytes
Content-Length: 0
Content-Type: text/html
=== End of file stdout507
[...]
2)
TESTDONE: 1700 tests were considered during 522 seconds.
TESTINFO: 195 tests were skipped due to these restraints:
Bug#1066606: marked as done (fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of function ‘PostCompile’ [-Werror=implicit-function-declaration])
Your message dated Sat, 08 Jun 2024 14:35:00 +
with message-id
and subject line Bug#1066606: fixed in fteqcc 3343+svn3400-5
has caused the Debian Bug report #1066606,
regarding fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of
function ‘PostCompile’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fteqcc
Version: 3343+svn3400-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> gcc -Wall -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -Wdate-time -D_FORTIFY_SOURCE=2 -c -o qcctui.o qcctui.c
> qcc_pr_lex.c: In function ‘ParsePrecompilerIf’:
> qcc_pr_lex.c:216:15: warning: unused variable ‘start’ [-Wunused-variable]
> 216 | char *start = pr_file_p;
> | ^
> qcc_pr_lex.c: In function ‘QCC_PR_Precompiler’:
> qcc_pr_lex.c:810:20: warning: unused variable ‘currentsourcefile’
> [-Wunused-variable]
> 810 | extern int currentsourcefile;
> |^
> qccmain.c: In function ‘QCC_WriteData’:
> qccmain.c:1116:40: warning: cast to pointer from integer of different size
> [-Wint-to-pointer-cast]
> 1116 | qcc_typeinfo[i].name = (char
> *)QCC_CopyDupBackString(qcc_typeinfo[i].name);
> |^
> qcd_main.c: In function ‘filefromprogs’:
> qcd_main.c:163:58: warning: logical not is only applied to the left hand side
> of comparison [-Wlogical-not-parentheses]
> 163 | if (!pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION16 &&
> | ^~
> qcd_main.c:163:13: note: add parentheses around left hand side expression to
> silence this warning
> 163 | if (!pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION16 &&
> | ^~~~
> | ( )
> qcd_main.c:164:62: warning: logical not is only applied to the left hand side
> of comparison [-Wlogical-not-parentheses]
> 164 | !pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION32)
> | ^~
> qcd_main.c:164:17: note: add parentheses around left hand side expression to
> silence this warning
> 164 | !pr_progstate[prnum].progs->secondaryversion !=
> PROG_SECONDARYVERSION32)
> | ^~~~
> | ( )
> qccmain.c: In function ‘QCC_main’:
> qccmain.c:2734:19: warning: assignment to ‘void * (*)(hashtable_t *, char *)’
> {aka ‘void * (*)(struct hashtable_s *, char *)’} from incompatible pointer
> type ‘void * (*)(hashtable_t *, const char *)’ {aka ‘void * (*)(struct
> hashtable_s *, const char *)’} [-Wincompatible-pointer-types]
> 2734 | pHash_Get = _Get;
> | ^
> qccmain.c:2755:19: warning: pointer targets in assignment from ‘unsigned char
> *’ to ‘char *’ differ in signedness [-Wpointer-sign]
> 2755 | s = externs->ReadFile("qcc.cfg", s, p);
> | ^
> qccmain.c:2936:27: warning: assignment to ‘void * (*)(hashtable_t *, char *)’
> {aka ‘void * (*)(struct hashtable_s *, char *)’} from incompatible pointer
> type ‘void * (*)(hashtable_t *, const char *)’ {aka ‘void * (*)(struct
> hashtable_s *, const char *)’} [-Wincompatible-pointer-types]
> 2936 | pHash_Get = _GetInsensative;
> | ^
> qcc_pr_comp.c: In function ‘QCC_PR_GenerateFunctionCall’:
> qccmain.c: In function ‘QCC_ContinueCompile’:
> qcc_pr_comp.c:2806:13: warning: variable ‘np’ set but not used
> [-Wunused-but-set-variable]
> 2806 | int np;
> |
Processed: texlive-binaries upgrade breaks therion build
Processing control commands: > affects -1 src:therion Bug #1072828 [texlive-binaries] texlive-binaries upgrade breaks therion build Added indication that 1072828 affects src:therion -- 1072828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072828: texlive-binaries upgrade breaks therion build
Package: texlive-binaries
Version: 2024.20240313.70630+ds-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:therion
https://buildd.debian.org/status/fetch.php?pkg=therion=amd64=6.2.1-1%2Bb1=1717847632=0
...
FAILED: thbook/thbook.pdf /<>/build/thbook/thbook.pdf
cd /<>/thbook && /usr/bin/cmake -E env FORCE_SOURCE_DATE=1
TEXINPUTS="/<>/build/thbook;." /usr/bin/pdftex
--output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex && /usr/bin/cmake
-E env FORCE_SOURCE_DATE=1 TEXINPUTS="/<>/build/thbook;."
/usr/bin/pdftex --output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex && /usr/bin/cmake
-E env FORCE_SOURCE_DATE=1 TEXINPUTS="/<>/build/thbook;."
/usr/bin/pdftex --output-dir=/<>/build/thbook
\\def\\outputsize{0}\\def\\reproducible{}\\input\ thbook.tex
This is pdfTeX, Version 3.141592653-2.6-1.40.26 (TeX Live 2025/dev/Debian)
(preloaded format=pdftex)
restricted \write18 enabled.
entering extended mode
(./thbook.tex No glyph to unicode mapping found! (./etc/supp-mis.tex
loading : Context Support Macros / Miscellaneous (2004.10.26)
) (./etc/supp-pdf.tex
loading : Context Support Macros / PDF
) (./etc/optarg.tex) (./etc/verbatim.tex) (./ch00.tex [1{/var/lib/texmf/fonts/m
ap/pdftex/updmap/pdftex.map} <./pic/thbook.jpg>]
(/<>/build/thbook/version.tex) [2]
Warning: re-run to input a newly generated TOC file [3] [4]) (./ch01.tex
[5 <./pic/ageom.pdf>] [6] [7] [MP to PDF] (./mp/schema.1) [8]) (./ch02.tex
[9] [10 <./pic/agrippa.jpg>]
Overfull \hbox (9.55724pt too wide) in paragraph at lines 96--99
[]\tt [.MM[.DD[@HH[:MM[:SS[.SS]] [- [.MM[.DD[@HH[:MM[:SS[.SS]]
][]
[11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
Overfull \hbox (2.61252pt too wide) in paragraph at lines 824--857
[]\tt ice-pillar[]\rm , []\tt ice-stalactite[]\rm , []\tt ice-stalagmite[]\rm
, []\tt map-connection[]$[]$\rm , []\tt paleo-material[]\rm ,
Overfull \hbox (4.79291pt too wide) in paragraph at lines 824--857
[]\tt photo[]\rm , []\tt root[]\rm , []\tt seed-germination[]\rm , []\tt sink[
]\rm , []\tt spring[]$[]$\rm , []\tt tree-trunk[]\rm , []\tt u[]$[]$\rm , []\tt
vegetable-debris[]\rm ,
[23] [24] [25]
Overfull \hbox (0.4216pt too wide) in paragraph at lines 1015--1031
[]\it passages: []\tt wall[]\rm , []\tt con-tour[]\rm , []\tt slope[]$[]$\rm ,
[]\tt floor-step[]\rm , []\tt pit[]\rm , []\tt pitch[] \rm (syn-onym of pit),
[]\tt ceiling-
Overfull \hbox (0.65195pt too wide) in paragraph at lines 1032--1044
[]\it passage fills: []\tt flow-stone[]\rm , []\tt moon-milk[]\rm , []\tt rock
-border[]$[]$\rm , []\tt rock-edge[]$[]$\rm , []\tt water-flow[]\rm , []\tt aby
ss-
Overfull \hbox (1.1684pt too wide) in paragraph at lines 1045--1053
[]\it equipment: []\tt fixed-ladder[]\rm , []\tt handrail[]\rm , []\tt rope[]\
rm , []\tt rope-ladder[]\rm , []\tt steps[]\rm , []\tt via-ferrata[]\rm , []\tt
walk-
[MP to PDF] (./mp/xsect.1) [26] [27] [28] [29] [30] [31] [32] [33] [34]
[35] [36] [37] [38] [39] [40] [41] [42] [43] [44]) (./ch03.tex [45] [46 <./pic/
herakl.pdf>] [47] [48] [49]
Overfull \hbox (3.98236pt too wide) in paragraph at lines 294--294
[]\tt fonts-setup
[50] [51] [52] [MP to PDF] (./mp/page.1) [53 <./pic/page.pdf>] [54] [55]
[56] [57] [58]
Overfull \hbox (1.67323pt too wide) in paragraph at lines 718--720
[][][]\tt wall-source [] $\mit .$ \rm set source d
ata for pas-sage wall mod-
[59] [60] [61] [62]) (./ch04.tex [63] [64] [65 <./pic/database.pdf>] [66])
(./ch05.tex [67] [68 <./pic/thom.jpg>] [69] [70] [71] [72] [73] [74] [75]
[76] [77]) (./ch06.tex [78] [79] [80] [81] [82] [83] [84] [85] [86] [87]
[88] [89] [90] [91] [92] [93]) (./ch07.tex Warning: skipping the case studies)
[94]
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 logo10
mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600;
nonstopmode; input logo10
This is METAFONT, Version 2.71828182 (TeX Live 2025/dev/Debian) (preloaded
base=mf)
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo10.mf
(/usr/share/texlive/texmf-dist/fonts/source/public/knuth-lib/logo.mf [77]
[69] [84] [65] [70] [80] [83] [79] [78]) )
Font metrics written on /<>/build/thbook/log
o10.tfm.
Output written on /<>/build/thbook/logo10.60
0gf (9 characters, 1748 bytes).
Transcript written on /<>/build/thbook/logo1
0.log.
mktexpk: `mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600; nonstopmode; input
logo10' failed to make logo10.600pk.
kpathsea: Appending font creation commands to
/<>/build/thbook/missfont.log.
)
(\end occurred when \ifeof on line 10 was incomplete)
(see the transcript file for additional information)
!pdfTeX error: /usr/bin/pdftex (file logo10): Font logo10 at 600 not found
==> Fatal error occurred, no output PDF file produced!
...
Downgrading texlive-binaries to 2023.20230311.66589-9 OR
installing texlive-fonts-recommended works around this issue.
Processed: Bug#1066606 marked as pending in fteqcc
Processing control commands: > tag -1 pending Bug #1066606 [src:fteqcc] fteqcc: FTBFS: qccmain.c:3127:17: error: implicit declaration of function ‘PostCompile’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066606: marked as pending in fteqcc
Control: tag -1 pending Hello, Bug #1066606 in fteqcc 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/games-team/fteqcc/-/commit/7d6b0167eab10c97d05ff6ba1595f09ef2bd7635 Add patches from upstream git to fix implicit function declarations Closes: #1066606 (this message was generated automatically) -- Greetings https://bugs.debian.org/1066606
Bug#1063407: marked as done (pybdsf fails to build with Python 3.12 as default)
Your message dated Sat, 08 Jun 2024 13:53:01 +
with message-id
and subject line Bug#1063407: fixed in pybdsf 1.10.3-3
has caused the Debian Bug report #1063407,
regarding pybdsf fails to build with Python 3.12 as default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1063407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pybdsf
Version: 1.10.3-2
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12
Forwarded: https://github.com/lofar-astron/PyBDSF/issues/214
pybdsf fails to build with Python 3.12 as default, also the autopkg test
fails with:
290s autopkgtest [09:33:17]: test command1: [---
292s [31;1mWARNING[0m: Matplotlib pyplot could not be imported.
Plotting is disabled.
293s --> Loaded parameters from file 'tbdsf_process_image.in'.
293s Traceback (most recent call last):
293s File
"/tmp/autopkgtest.Z7dzWY/build.NDT/src/test/tbdsf_process_image.py",
line 5, in
293s img = bdsf.process_image('tbdsf_process_image.in', ncores=2)
293s ^^
293s File "/usr/lib/python3/dist-packages/bdsf/__init__.py", line 256,
in process_image
293s img.process(**kwargs)
293s File "/usr/lib/python3/dist-packages/bdsf/image.py", line 136, in
process
293s success = interface.process(self, **kwargs)
293s ^
293s File "/usr/lib/python3/dist-packages/bdsf/interface.py", line 66,
in process
293s _run_op_list(img, op_chain)
293s File "/usr/lib/python3/dist-packages/bdsf/__init__.py", line 155,
in _run_op_list
293s op(img)
293s File "/usr/lib/python3/dist-packages/bdsf/readimage.py", line 68,
in __call__
293s result = read_image_from_file(image_file, img, img.indir)
293s
293s File "/usr/lib/python3/dist-packages/bdsf/functions.py", line
1079, in read_image_from_file
293s from distutils.version import StrictVersion
293s ModuleNotFoundError: No module named 'distutils'
294s autopkgtest [09:33:21]: test command1: ---]
297s command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: pybdsf
Source-Version: 1.10.3-3
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
pybdsf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated pybdsf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Jun 2024 15:06:52 +0200
Source: pybdsf
Architecture: source
Version: 1.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Maintainers
Changed-By: Ole Streicher
Closes: 1063407
Changes:
pybdsf (1.10.3-3) unstable; urgency=medium
.
* Fix python3.12 build (Closes: #1063407)
* Push Standards-Version to 4.7.0. No changes needed
Checksums-Sha1:
617301a47f4536c2a98881bcf50e20395ff6ac97 2098 pybdsf_1.10.3-3.dsc
62b1d63fd6ebdf4da1b10cc0b479c251d485a8ed 7752 pybdsf_1.10.3-3.debian.tar.xz
Checksums-Sha256:
d1248c0cde891b2ad772db7b8048994fc58be06a4d3206f038b27aafe45e1bb3 2098
pybdsf_1.10.3-3.dsc
73c90702d95fb212db4c4b88a89da528c6032326b8c7d1d848bba98a611f1e40 7752
pybdsf_1.10.3-3.debian.tar.xz
Files:
634167389287f0d7644af75f7d8b482f 2098 python optional pybdsf_1.10.3-3.dsc
eb293059f0f50f518713a1ff019c68a7 7752 python optional
pybdsf_1.10.3-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmZkXRgACgkQcRWv0HcQ
3Peo2Q//Zq700VglPmco98YKlJKnHEBzH8opFwHw6syDScNddNkfRLiL8HyCeMf5
00A1UeUugjd2XUmVt7UiltDUHbIyYLMJF92zLo2f5PPlkIXlrTXQfSDALnxHVG5G
mB03gSX+6BHH40O5WpJ9FAmsO8N4tOxtszS7o49uPLxoz9F7PYmZ5KW6b1x82ItV
C14Pu0UcUdukU5p26R8cpZP2lGMQfgvrw5r1RU4rO2KvUclhnYacpXbPPuopGpTd
Vg/XJVSb4Wuw8X5TmZbouc+kuDBkfWMT6jedOQdjCuLYqz9D0l444F54OQQWhFbs
83FDssRAO6uUNbpzkjKRsRvA8nH6xNB0Rv3lE+rzJb8cMBKorOsI+0/GDLLbZRld
Bug#1072824: odin FTBFS with VTK 9.3.0
Source: odin Version: 2.0.5-5 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=odin=amd64=2.0.5-5%2Bb2=1717847424=0 ... checking for main in -lvtkIOLegacy-7.1... no checking for main in -lvtkIOLegacy-7.0... no checking for main in -lvtkIOLegacy-6.3... no checking for main in -lvtkIOLegacy-6.2... no checking for main in -lvtkIOLegacy-6.1... no checking for main in -lvtkIOLegacy-6.0... no checking for main in -lvtkIOLegacy-9.0... no checking for main in -lvtkIOLegacy-9.1... no checking for main in -lvtkIO... no checking for main in -lvtkRendering... no checking for main in -lvtkGraphics... no checking for main in -lvtkFiltering... no checking for main in -lvtkCommon... no checking for vtkStructuredPoints.h... no checking for vtkArrowSource.h... no configure: error: VTK library missing
Bug#1072823: liggghts FTBFS with VTK 9.3.0
Source: liggghts Version: 3.8.0+repack1-9.1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=liggghts=amd64=3.8.0%2Brepack1-9.1%2Bb2=1717846024=0 ... /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtp(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:170:18: error: ‘class vtkXMLPPolyDataWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 170 | pwriter->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp:187:17: error: ‘class vtkXMLPolyDataWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 187 | writer->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtu(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:209:18: error: ‘class vtkXMLPUnstructuredGridWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 209 | pwriter->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp:226:17: error: ‘class vtkXMLUnstructuredGridWriter’ has no member named ‘SetInput’; did you mean ‘GetInput’? 226 | writer->SetInput(data); | ^~~~ | GetInput /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtr(vtkSmartPointer, int, const char*)’: /<>/src/dump_vtk.cpp:280:43: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 280 | pwriter->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp:297:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 297 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_unstructured_grid(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:322:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 322 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_rectilinear_grid(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:347:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 347 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ /<>/src/dump_vtk.cpp: In member function ‘void LAMMPS_NS::DumpVTK::write_vtk_poly(vtkSmartPointer, int, const char*, char*)’: /<>/src/dump_vtk.cpp:372:42: error: ‘class vtkDataObject’ has no member named ‘GetProducerPort’ 372 | writer->SetInputConnection(data->GetProducerPort()); | ^~~ ...
Bug#1071007:
Hi everybody! Firstly, we have to make it clear that we have two distinct bugs: They seem to be the same because you are bumping into the only files they have in common: __init__.py The first bug was due to Sherlock installing his modules in the root of the package directories. This has so far been resolved by the patch. I sent it upstream, in case he wanted to merge until he changed to another beckand(poetry), however I left him free to accept it or not. And I made clear the reasons why I sent it. https://github.com/sherlock-project/sherlock/pull/2147 The other problem is because there is the same project with the same name as sherlock, although its name is python-sherlock, upstream in its code calls it "sherlock". The question is to solve the problem, one of the projects will have to change the name of both pyproject.toml and also change the name of its main module and create nicknames for its "imports". In my opinion, several files will have to be patched Or as an alternative We could make Sherlock install its modules in the package root again. The question is when Sherlock joins Poetry, we will have the problem again, as there would once again be a directory called Sherlock. Nilson F. Silva
Bug#1072822: gdcm FTBFS with VTK 9.3.0
Source: gdcm Version: 3.0.24-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=gdcm=amd64=3.0.24-1%2Bb2=1717845766=0 ... -- Building Utilities/VTK as a VTK 9 Module CMake Error at /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2121 (message): The `SPDX_DESTINATION` must not be an absolute path. Use `CMAKE_INSTALL_PREFIX` to keep everything in a single installation prefix. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/vtk-9.3/vtkModule.cmake:2667 (_vtk_module_check_destinations) CMakeLists.txt:696 (vtk_module_build) -- Configuring incomplete, errors occurred!
Bug#1072821: wireshark: binNMUs revert t64 transition
Source: wireshark Version: 4.2.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=wireshark=amd64=4.2.5-1%2Bb1=1717834351=0 ... Description: libwireshark-dev - network packet dissection library -- development files libwireshark17 - network packet dissection library -- shared library libwiretap-dev - network packet capture library -- development files libwiretap14 - network packet capture library -- shared library libwsutil-dev - network packet dissection utilities library -- development files libwsutil15 - network packet dissection utilities library -- shared library tshark - network traffic analyzer - console version wireshark - network traffic analyzer - graphical interface wireshark-common - network traffic analyzer - common files wireshark-dev - network traffic analyzer - development tools Changes: wireshark (4.2.5-1+b1) sid; urgency=low, binary-only=yes . * Binary-only non-maintainer upload for amd64; no source changes. * Rebuild against Qt 6.6.2. ... debian/rules: ... ifneq ($(filter noble unstable testing trixie UNRELEASED,$(DEB_DISTRIBUTION)),) sed "$(CONTROL_IN_SED_CMD)" debian/control.t64.in > debian/control else sed "$(CONTROL_IN_SED_CMD)" debian/control.in > debian/control ... sid != unstable
Bug#1069353: plantuml: Re: nncp: FTBFS on arm64: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1
On 07/06/2024 18:24, Andrej Shadura wrote: That was totally a bug in plantuml. My fault that I forgot to merge it with another bug report for the same issue. Thanks, Andrej. I see that the package have returned to testing. I am sorry that I missed https://bugs.debian.org/1068999 I was surprised that a working version suddenly disappeared from trixie.
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands: > tags 1072733 moreinfo Bug #1072733 [sherlock,python3-sherlock] sherlock has an undeclared file conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py Ignoring request to alter tags of bug #1072733 to the same tags previously set > reopen 1071007 = Bug #1071007 [sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py Bug 1071007 is not marked as done; doing nothing. -- 1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007 1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> tags 1072733 moreinfo
Bug #1072733 [sherlock,python3-sherlock] sherlock has an undeclared file
conflict on /usr/lib/python3/dist-packages/sherlock/__init__.py
Added tag(s) moreinfo.
> reopen 1071007 =
Bug #1071007 {Done: Josenilson Ferreira da Silva }
[sherlock] sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions sherlock/0.14.4+git20240531.e5ad3c4-1.
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
1072733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1071007: sherlock: Must not ship /usr/lib/python3/dist-packages/__init__.py
Control: tags 1072733 moreinfo Control: reopen 1071007 = Hello all, I wasn't subscribed to both bugs so I missed some of the replies, I'm subscribed now. I'm sending this reply to both #1072733 and #1071007 because they are related and I'm trying to clarify the situation on both. Summary: #1072733 is a bug caused by a tentative fix of #1071007, I believe Francisco made the right approach there, but maybe I'm missing something, Chris? #1071007 is still not fully fixed as the approach is problematic. We should not submit workarounds to upstream when they already pointed out a PR which should address the issue. If we need to perform a workaround on our side in the meantime, we need to make sure it works and we should not submit it upstream (they already have the proper fix in progress). Plan: Let's try to fix this issue using upstream's PR. If we spot issues with the PR, we can contribute back (but let's make sure it makes sense to upstream). If we end up performing a workaround, let's make sure it works and doesn't cause other issues. It's ok to let the package be removed from testing until this gets fixed. If we really want to avoid the package being removed from testing, we can package a previous release where the issue wasn't present (using the "+really" versioning mechanism). The end goal is to get this fixed before the freeze, so we have time. Now the lengthy replies below: For #1072733: Chris > Per Debian policy this is not the correct solution for naming conflicts. Both > maintainer (teams), please find a policy compliant solution together. The solution for this one seems correct, it's a Conflict + Replaces because both packages provide a "sherlock" library. Am I missing something? Note that this bug is different from #1071007, they look very similar and initially I thought they were a dupe. Nilson > Your package should not be called in d/rules: > export PYBUILD_NAME=python-sherlock > or something similar that wasn't exactly sherlock? We should keep the same name as changing it will cause issues for users, this is a real case of a conflicting library name. For #1071007: Nilson, > I just pushed a new version of shelock with a fix for the problem in the > "master" branch. If that's ok, I'll do a merge. > https://salsa.debian.org/pkg-security-team/sherlock/-/tree/master?ref_type=heads We follow the DEP14 for git branching, that means we do namespacing. When dealing with temp/wip branches, the recommendation is to push to $username/$branchname. If you push to master, it will lead to confusion as to which branch is the main one (it's debian/master). It looks like that branch has been merged into debian/master but master has not been deleted yet. We have to remove that branch. > This led to the bug being reopened twice as RC, leading to its removal from > "testing" even after > pycrc had resolved its conflict issue. We always try to avoid getting a package removed from testing, but sometimes it happens and that's ok, once the issue is fixed the package will get back. This is only worrying when removing the package causes a cascade effect or when we are close to the freeze for stable. We don't have to rush for a fix in this case, it's better to be precise. > I made a pull request to usptream > https://github.com/sherlock-project/sherlock/pull/2147 We should not be submitting this to upstream when they already pointed us to a PR that solves the issue. We have to try working with that PR. If that's not possible, we can patch it ourselves with a different approach, but we should not submit our workaround to upstream because they already have a proper solution in progress. > In accordance with the other Package Uploaders, > Debian Developer, Francisco Vilmar. > I will be closing the bug. > Since the problem itself, with Sherlock installing its modules in the root of the packages, has been fixed. The upload done by Francisco for #1072733 can't be used to close #1071007, he was fixing an issue caused by one of the uploads that tried to fix #1071007, it was not fixing #1071007 itself. > sherlock (0.14.4+git20240531.e5ad3c4-1) unstable; urgency=medium > . > * New upstream version 0.14.4+git20240531.e5ad3c4 > * debian/patches: Adjusted directory installation package (Closes: #1071007) This upload is indeed trying to solve #1071007 by patching the source code instead of pulling the upstream PR. Looking at the list of files shiped [0], the egginfo files are in the wrong place. I also find the following commit confusing: https://salsa.debian.org/pkg-security-team/sherlock/-/commit/fc6e9929b1018d411df599a68d5898e42bfe6560 The commit description does not mention what/why the changes are being made, for example, why the change from dh_auto_install to dh_install. Cheers, [0] https://packages.debian.org/trixie/all/sherlock/filelist -- Samuel Henrique
Bug#1072594: marked as done (goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at /usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.)
Your message dated Sat, 08 Jun 2024 11:04:06 +
with message-id
and subject line Bug#1072594: fixed in goobox 3.6.0-12
has caused the Debian Bug report #1072594,
regarding goobox: FTBFS: UTF-8 "xFC" does not map to Unicode at
/usr/share/perl5/Locale/Po4a/Po.pm line 353, <$fh> line 114.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1072594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:goobox
Version: 3.6.0-11
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
meson setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dpython.bytecompile=-1
The Meson build system
Version: 1.4.1
Source dir: /<>
Build dir: /<>/obj-x86_64-linux-gnu
Build type: native build
Project name: goobox
Project version: 3.6.0
C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-25) 13.2.0")
C linker for the host machine: cc ld.bfd 2.42
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: YES (/usr/bin/pkg-config) 1.8.1
Run-time dependency libcoverart found: YES 1.0.0
Configuring config.h using configuration
Build-time dependency gio-2.0 found: YES 2.80.2
Program /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas found: YES
(/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas)
Configuring org.gnome.Goobox.desktop.in using configuration
Program msgfmt found: YES (/usr/bin/msgfmt)
Program itstool found: YES (/usr/bin/itstool)
Program msgmerge found: YES (/usr/bin/msgmerge)
Program msgfmt found: YES (/usr/bin/msgfmt)
Program msginit found: YES (/usr/bin/msginit)
Program msgmerge found: YES (/usr/bin/msgmerge)
Program xgettext found: YES (/usr/bin/xgettext)
Library m found: YES
Run-time dependency threads found: YES
Run-time dependency glib-2.0 found: YES 2.80.2
Run-time dependency gthread-2.0 found: YES 2.80.2
Run-time dependency gtk+-3.0 found: YES 3.24.42
Run-time dependency gstreamer-1.0 found: YES 1.24.4
Run-time dependency libbrasero-media3 found: YES 3.12.3
Run-time dependency libmusicbrainz5 found: YES 5.1.0
Run-time dependency libdiscid found: YES 0.6.4
Compiler for C supports arguments -Wall: YES
Dependency gio-2.0 found: YES 2.80.2 (cached)
Program /usr/bin/glib-compile-resources found: YES
(/usr/bin/glib-compile-resources)
Dependency glib-2.0 found: YES 2.80.2 (cached)
Program /usr/bin/glib-genmarshal found: YES (/usr/bin/glib-genmarshal)
Message: configuration summary:
project: goobox 3.6.0
prefix: /usr
libcoverart: true
Build targets in project: 95
NOTICE: Future-deprecated features used:
* 0.56.0: {'meson.source_root'}
goobox 3.6.0
User defined options
buildtype : plain
libdir: lib/x86_64-linux-gnu
localstatedir : /var
prefix: /usr
sysconfdir: /etc
wrap_mode : nodownload
python.bytecompile: -1
Found ninja-1.12.1 at /usr/bin/ninja
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
[1/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml --sourcedir
../src --c-name goo --internal --generate --target src/goo-resources.c
--dependency-file src/goo-resources.c.d
[2/104] /usr/bin/glib-compile-resources ../src/goobox.gresource.xml --sourcedir
../src --c-name goo --internal --generate --target src/goo-resources.h
[3/104] /usr/bin/msgfmt ../help/ca/ca.po -o help/ca/goobox-ca.gmo
[4/104] /usr/bin/msgfmt ../help/cs/cs.po -o help/cs/goobox-cs.gmo
[5/104] /usr/bin/msgfmt ../help/de/de.po -o help/de/goobox-de.gmo
[6/104] /usr/bin/msgfmt ../help/el/el.po -o help/el/goobox-el.gmo
[7/104] /usr/bin/msgfmt ../help/es/es.po -o help/es/goobox-es.gmo
[8/104] /usr/bin/glib-genmarshal --prefix goo_marshal --output
src/goo-marshal.h --header ../src/goo-marshal.list --pragma-once
INFO: Reading ../src/goo-marshal.list...
[9/104] /usr/bin/msgfmt ../help/fr/fr.po -o help/fr/goobox-fr.gmo
[10/104] /usr/bin/msgfmt ../help/oc/oc.po -o help/oc/goobox-oc.gmo
[11/104] /usr/bin/msgfmt ../help/pl/pl.po -o help/pl/goobox-pl.gmo
[12/104] /usr/bin/msgfmt ../help/pt_BR/pt_BR.po
Bug#1072816: sploitscan: Configuration files installed in Python modules directory
Package: sploitscan Version: 0.9.1-1 Severity: serious Hi, sploitscan installs configuration files in the system Python modules directory: /usr/lib/python3/dist-packages/sploitscan/templates/report_template.html /usr/lib/python3/dist-packages/sploitscan/config.json As per Debian Policy 10.7.2 configuration files must reside in /etc (or in case of multiple configuration files it is suggested to put them in a subdirectory named after the package). Best regards, Peter
Bug#1064760: marked as done (tailspin: FTBFS: dh_auto_test: error: env DEB_BUILDDIR= /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test returned exit code 101)
Your message dated Sat, 08 Jun 2024 07:05:03 +
with message-id
and subject line Bug#1064760: fixed in tailspin 3.0.1+dfsg-1
has caused the Debian Bug report #1064760,
regarding tailspin: FTBFS: dh_auto_test: error: env DEB_BUILDDIR=
/<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test returned exit
code 101
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1064760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tailspin
Version: 3.0.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cmark-gfm README.md > README.html
> cmark-gfm --to plaintext README.md > README.txt
> cmark-gfm CHANGELOG.md > CHANGELOG.html
> cmark-gfm --to plaintext CHANGELOG.md > CHANGELOG.txt
> dh execute_after_dh_auto_build --buildsystem cargo
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: WARNING: falling back to simply calling upstream cargo,
> because CARGO_HOME does not end with debian/cargo_home:
> Use of uninitialized value in concatenation (.) or string at
> /<>/debian/dh-cargo/lib/Debian/Debhelper/Buildsystem/cargo.pm
> line 296, line 2.
> env DEB_BUILDDIR=
> /<>/tailspin-3.0.0\+dfsg/debian/dh-cargo/bin/cargo test
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] []
> ['-j8'] 0
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--release'],) {}
>Fresh unicode-ident v1.0.12
>Fresh autocfg v1.1.0
>Fresh cfg-if v1.0.0
>Fresh once_cell v1.19.0
>Fresh pin-project-lite v0.2.13
>Fresh memchr v2.7.1
>Fresh tracing-core v0.1.32
>Fresh proc-macro2 v1.0.76
>Fresh crossbeam-utils v0.8.19
>Fresh libc v0.2.152
>Fresh bitflags v1.3.2
>Fresh lazy_static v1.4.0
>Fresh quote v1.0.35
>Fresh utf8parse v0.2.1
>Fresh sharded-slab v0.1.4
>Fresh cc v1.0.83
>Fresh thread_local v1.1.4
>Fresh syn v2.0.48
>Fresh anstyle-parse v0.2.1
>Fresh anstyle-query v1.0.0
>Fresh anstyle v1.0.4
>Fresh smallvec v1.11.2
>Fresh colorchoice v1.0.0
>Fresh serde_derive v1.0.195
>Fresh log v0.4.20
>Fresh scopeguard v1.1.0
>Fresh anstream v0.6.7
>Fresh parking_lot_core v0.9.9
>Fresh serde v1.0.195
>Fresh lock_api v0.4.11
>Fresh mio v0.8.10
>Fresh tracing-subscriber v0.3.18
> warning: method `bold` is never used
> -->
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/fmt/format/mod.rs:1403:8
> |
> 1398 | impl Style {
> | -- method in this implementation
> ...
> 1403 | fn bold(self) -> Self {
> |
> |
> note: the lint level is defined here
> -->
> /<>/debian/cargo_registry/tracing-subscriber-0.3.18/src/lib.rs:191:5
> |
> 191 | unused,
> | ^^
> = note: `#[warn(dead_code)]` implied by `#[warn(unused)]`
>
>Fresh crossbeam-epoch v0.9.18
>Fresh getrandom v0.2.10
>Fresh tracing v0.1.40
> warning: `tracing-subscriber` (lib) generated 1 warning
>Fresh inotify-sys v0.1.5
>Fresh adler v1.0.2
>Fresh strsim v0.10.0
>Fresh gimli v0.28.1
>Fresh heck v0.4.1
>Fresh linux-raw-sys v0.4.12
>Fresh clap_lex v0.6.0
>Fresh option-ext v0.2.0
>Fresh hashbrown v0.12.3
>Fresh bitflags v2.4.2
>Fresh same-file v1.0.6
>Fresh miniz_oxide v0.7.1
>Fresh inotify v0.9.6
>Fresh addr2line v0.21.0
>Fresh dirs-sys v0.4.1
>Fresh clap_builder v4.4.18
>Fresh indexmap v1.9.3
>Fresh rustix v0.38.30
>Fresh walkdir v2.4.0
>Fresh clap_derive v4.4.7
>Fresh tracing-error v0.2.0
> warning: lint `const_err` has been removed: converted into hard error, see
> issue #71800 for more
> information
>-->
> /<>/debian/cargo_registry/tracing-error-0.2.0/src/lib.rs:200:5
> |
> 200 | const_err,
> |
Bug#1063601: marked as done (tailspin FTBFS error: environment variable `CARGO_CHANNEL` not defined at compile time)
Your message dated Sat, 08 Jun 2024 07:05:03 +
with message-id
and subject line Bug#1063601: fixed in tailspin 3.0.1+dfsg-1
has caused the Debian Bug report #1063601,
regarding tailspin FTBFS error: environment variable `CARGO_CHANNEL` not
defined at compile time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1063601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tailspin
Version: 3.0.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=tailspin=amd64=3.0.0%2Bdfsg-1=1706195420=0
Running
`/<>/target/release/build/eyre-15058028a1ebd405/build-script-build`
[eyre 0.6.8] error[E0407]: method `backtrace` is not a member of trait `Error`
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:19:9
[eyre 0.6.8]|
[eyre 0.6.8] 19 | / fn backtrace() -> Option<> {
[eyre 0.6.8] 20 | | let backtrace = Backtrace::capture();
[eyre 0.6.8] 21 | | match backtrace.status() {
[eyre 0.6.8] 22 | | BacktraceStatus::Captured |
BacktraceStatus::Disabled | _ => {}
[eyre 0.6.8] 23 | | }
[eyre 0.6.8] 24 | | unimplemented!()
[eyre 0.6.8] 25 | | }
[eyre 0.6.8]| |_^ not a member of trait `Error`
[eyre 0.6.8]
[eyre 0.6.8] error[E0554]: `#![feature]` may not be used on the stable release
channel
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8]
[eyre 0.6.8] warning: the feature `backtrace` has been stable since 1.65.0 and
no longer requires an attribute to enable
[eyre 0.6.8] -->
/<>/target/x86_64-unknown-linux-gnu/release/build/eyre-eb1eb971e427fb49/out/probe.rs:2:16
[eyre 0.6.8] |
[eyre 0.6.8] 2 | #![feature(backtrace)]
[eyre 0.6.8] |^
[eyre 0.6.8] |
[eyre 0.6.8] = note: `#[warn(stable_features)]` on by default
[eyre 0.6.8]
[eyre 0.6.8] error: aborting due to 2 previous errors; 1 warning emitted
[eyre 0.6.8]
[eyre 0.6.8] Some errors have detailed explanations: E0407, E0554.
[eyre 0.6.8] For more information about an error, try `rustc --explain E0407`.
[eyre 0.6.8] cargo:rustc-cfg=track_caller
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: tailspin
Source-Version: 3.0.1+dfsg-1
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
tailspin, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated tailspin package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 08 Jun 2024 08:35:10 +0200
Source: tailspin
Architecture: source
Version: 3.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard
Changed-By: Jonas Smedegaard
Closes: 1063601 1064760
Changes:
tailspin (3.0.1+dfsg-1) unstable; urgency=medium
.
[ upstream ]
* new release
.
[ Jonas Smedegaard ]
* update copyright info: fix file path
* fix patch 2002;
closes: bug#1063601, #1064760,
thanks to Sebastian Ramacher and Lucas Nussbaum
* add patches 2001_* to accept older versions of crates
* explicitly build-depend on package for crate nu-ansi-term
* declare compliance with Debian Policy 4.7.0
Checksums-Sha1:
aed32144ace2a30635964752ed770d4864e933b5 2669 tailspin_3.0.1+dfsg-1.dsc
dabf90030f3f85e504b962004ad6e19f3543faf3 55420 tailspin_3.0.1+dfsg.orig.tar.xz
b5ad78556537ab81d26885eaa4e3f95481803431 16880
tailspin_3.0.1+dfsg-1.debian.tar.xz
6776c32ecd48f650be494a5ab529735369c28c87 20051
tailspin_3.0.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
e3dfa3d49a49a66d5dcf3197465a1913afffeadc74453d038a86439411ad6431 2669
tailspin_3.0.1+dfsg-1.dsc
Processed: ipython: Ubuntu patch for pytest 8 support
Processing control commands: > tags -1 patch Bug #1063945 [ipython] ipython: autopkgtest regression with pytest 8 Added tag(s) patch. -- 1063945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063945: ipython: Ubuntu patch for pytest 8 support
Package: ipython
Version: 8.20.0-1
Followup-For: Bug #1063945
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch
Hi,
I identified two patches from upstream that solved this issue but
aren't available in the currently packaged version. I applied the
following in Ubuntu to solve the issue:
* Update pytest and tests for pytest 8 compatibility (LP: #2068674).
- d/p/pytest8-nose-tests.patch: update nose-style tests for pytest 8.2+
- d/p/support-pytest-plugin.patch: update pytest plugin for pytest 8.1+
Thanks for considering the patches.
-- System Information:
Debian Release: trixie/sid
APT prefers oracular
APT policy: (500, 'oracular'), (100, 'oracular-proposed')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ipython-8.20.0/debian/patches/pytest8-nose-tests.patch
ipython-8.20.0/debian/patches/pytest8-nose-tests.patch
--- ipython-8.20.0/debian/patches/pytest8-nose-tests.patch 1969-12-31
16:00:00.0 -0800
+++ ipython-8.20.0/debian/patches/pytest8-nose-tests.patch 2024-06-06
17:10:18.0 -0700
@@ -0,0 +1,32 @@
+Description: Update nose-style tests for pytest 8 compatbility
+ Pytest dropped support for nose-style tests in pytest 8. This patch cherry-
+ picks the patch from upstream to fix the offending tests. This patch can
+ be dropped in version 8.24.0.
+Author: Chris Peterson
+Origin: upstream,
https://github.com/ipython/ipython/commit/cdacafdccaf1f562e59b21b3c9f2c1a28eba54da
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipython/+bug/2068674
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063945
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/IPython/core/tests/test_pylabtools.py
b/IPython/core/tests/test_pylabtools.py
+@@ -165,7 +165,7 @@
+ def enable_gui(self, gui):
+ pass
+
+-def setup(self):
++def setup_method(self):
+ import matplotlib
+ def act_mpl(backend):
+ matplotlib.rcParams['backend'] = backend
+@@ -184,7 +184,7 @@
+ self._save_cis = backend_inline.configure_inline_support
+ backend_inline.configure_inline_support = lambda *a, **kw: None
+
+-def teardown(self):
++def teardown_method(self):
+ pt.activate_matplotlib = self._save_am
+ pt.import_pylab = self._save_ip
+ backend_inline.configure_inline_support = self._save_cis
diff -Nru ipython-8.20.0/debian/patches/series
ipython-8.20.0/debian/patches/series
--- ipython-8.20.0/debian/patches/series2024-01-14 16:32:19.0
-0800
+++ ipython-8.20.0/debian/patches/series2024-06-06 17:10:38.0
-0700
@@ -1,2 +1,4 @@
0002-Update-intersphinx-links-for-local-access.patch
0003-Drop-setuptools-data_files.patch
+pytest8-nose-tests.patch
+support-pytest-plugin.patch
diff -Nru ipython-8.20.0/debian/patches/support-pytest-plugin.patch
ipython-8.20.0/debian/patches/support-pytest-plugin.patch
--- ipython-8.20.0/debian/patches/support-pytest-plugin.patch 1969-12-31
16:00:00.0 -0800
+++ ipython-8.20.0/debian/patches/support-pytest-plugin.patch 2024-06-06
17:22:13.0 -0700
@@ -0,0 +1,120 @@
+Description: Update pytest plugin for pytest 8
+ Pytest 8.1 changed the plugin API. This patch cherry-picks the upstream
+ modifications to the plugin for pytest 8.1+ support. This patch can be
+ dropped with upstream version 8.25.0.
+Author: Chris Peterson
+Origin: upstream,
https://github.com/ipython/ipython/commit/7df70a3cd79068be6f98596e427d60a5d0cfe5b3
+Bug: https://github.com/ipython/ipython/issues/14390
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipython/+bug/2068674
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/IPython/testing/plugin/pytest_ipdoctest.py
b/IPython/testing/plugin/pytest_ipdoctest.py
+@@ -38,7 +38,11 @@
+ from _pytest.compat import safe_getattr
+ from _pytest.config import Config
+ from _pytest.config.argparsing import Parser
+-from _pytest.fixtures import FixtureRequest
++
++try:
++from _pytest.fixtures import TopRequest as FixtureRequest
++except ImportError:
++from _pytest.fixtures import FixtureRequest
+ from _pytest.nodes import Collector
+ from _pytest.outcomes import OutcomeException
+ from _pytest.pathlib import fnmatch_ex
+@@ -68,6 +72,8 @@
+ # Lazy definition of output checker class
+ CHECKER_CLASS: Optional[Type["IPDoctestOutputChecker"]] = None
+
++pytest_version = tuple([int(part) for part in pytest.__version__.split(".")])
++
+
+ def
Processed: ipykernel: Ubuntu patch for pytest 8 support
Processing control commands: > tags -1 patch Bug #1070112 [src:ipykernel] ipykernel: nose-style setup/teardown is no longer supported in pytest 8 Ignoring request to alter tags of bug #1070112 to the same tags previously set -- 1070112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070112: ipykernel: Ubuntu patch for pytest 8 support
Package: ipykernel Version: 6.29.3-1 Followup-For: Bug #1070112 X-Debbugs-Cc: chris.peter...@canonical.com User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oracular ubuntu-patch Control: tags -1 patch Hi, I applied the following patch in Ubuntu to fix this issue. * pytest8-nose-deprecation.patch: update tests for pytest 8 compatibility (LP: #2068672). Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers oracular APT policy: (500, 'oracular'), (100, 'oracular-proposed') Architecture: amd64 (x86_64) Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch --- ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch 1969-12-31 16:00:00.0 -0800 +++ ipykernel-6.29.3/debian/patches/pytest8-nose-deprecation.patch 2024-06-06 16:39:16.0 -0700 @@ -0,0 +1,95 @@ +Description: Update tests for pytest 8 compatibility + Pytest 8 deprecated support for nose-style tests. This patch cherrry-picks + changes from upstream to modify tests to run with pytest 8. +Author: Chris Peterson +Origin: upstream, https://github.com/ipython/ipykernel/commit/a7d66ae2197e0d7471ba160542cf5ff7713084b5 +Bug: https://github.com/ipython/ipykernel/issues/1230 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ipykernel/+bug/2068672 +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070112 +Forwarded: not-needed +Last-Update: 2024-06-06 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/tests/__init__.py b/tests/__init__.py +@@ -7,6 +7,8 @@ + import tempfile + from unittest.mock import patch + ++import pytest ++ + from ipykernel.kernelspec import install + + pjoin = os.path.join +@@ -15,7 +17,8 @@ + patchers: list = [] + + +-def setup(): ++@pytest.fixture(autouse=True) ++def _global_setup(): + """setup temporary env for tests""" + global tmp + tmp = tempfile.mkdtemp() +@@ -35,8 +38,8 @@ + # install IPython in the temp home: + install(user=True) + ++yield + +-def teardown(): + for p in patchers: + p.stop() + +--- a/tests/test_eventloop.py b/tests/test_eventloop.py +@@ -42,14 +42,15 @@ + _get_qt_vers() + + +-def setup(): ++@pytest.fixture(autouse=True) ++def _setup_env(): + """start the global kernel (if it isn't running) and return its client""" + global KM, KC + KM, KC = start_new_kernel() + flush_channels(KC) + ++yield + +-def teardown(): + assert KM is not None + assert KC is not None + KC.stop_channels() +--- a/tests/test_message_spec.py b/tests/test_message_spec.py +@@ -21,7 +21,8 @@ + KC: BlockingKernelClient = None # type:ignore + + +-def setup(): ++@pytest.fixture(autouse=True) ++def _setup_env(): + global KC + KC = start_global_kernel() + +--- a/tests/test_async.py b/tests/test_async.py +@@ -8,14 +8,15 @@ + KC = KM = None + + +-def setup_function(): ++@pytest.fixture(autouse=True) ++def _setup_env(): + """start the global kernel (if it isn't running) and return its client""" + global KM, KC + KM, KC = start_new_kernel() + flush_channels(KC) + ++yield + +-def teardown_function(): + assert KC is not None + assert KM is not None + KC.stop_channels() diff -Nru ipykernel-6.29.3/debian/patches/series ipykernel-6.29.3/debian/patches/series --- ipykernel-6.29.3/debian/patches/series 2024-01-11 14:25:38.0 -0800 +++ ipykernel-6.29.3/debian/patches/series 2024-06-06 16:22:48.0 -0700 @@ -1,2 +1,3 @@ 0002-test_simple_print-may-produce-stderr-content-when-ex.patch 0003-Made-build-reproducible-patch-by-Daniel-Shahaf.patch +pytest8-nose-deprecation.patch
Processed: protontricks: Forward pytest 8 support patch from Ubuntu
Processing control commands: > tags -1 patch Bug #1063967 [protontricks] protontricks: autopkgtest regression with pytest 8 Added tag(s) patch. -- 1063967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1063967: protontricks: Forward pytest 8 support patch from Ubuntu
Package: protontricks
Version: 1.10.5-1
Followup-For: Bug #1063967
X-Debbugs-Cc: chris.peter...@canonical.com
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch
Hi,
I applied the following patch in Ubuntu to fix this issue.
* pytest8-caplog.patch: Update tests for pytest 8 compatibility
(LP: #2068659).
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers oracular
APT policy: (500, 'oracular'), (100, 'oracular-proposed')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.0-31-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru protontricks-1.10.5/debian/patches/pytest8-caplog.patch
protontricks-1.10.5/debian/patches/pytest8-caplog.patch
--- protontricks-1.10.5/debian/patches/pytest8-caplog.patch 1969-12-31
16:00:00.0 -0800
+++ protontricks-1.10.5/debian/patches/pytest8-caplog.patch 2024-06-06
12:27:04.0 -0700
@@ -0,0 +1,37 @@
+Description: Update test for pytest 8 comptability
+ Pytest 8 now includes all log levels in the caplog fixture. Apply upstream
+ changes to test case which ensures warning messages are logged. Can be dropped
+ in upstream version 1.11.1
+Author: Chris Peterson
+Origin: upstream,
https://github.com/Matoking/protontricks/commit/bb1da5a0ddcac1cbd577fd54fe947ff6ad1731bc
+Bug: https://github.com/Matoking/protontricks/issues/283
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pytest/+bug/2068659
+Forwarded: not-needed
+Last-Update: 2024-06-06
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/tests/test_gui.py
b/tests/test_gui.py
+@@ -207,7 +207,7 @@
+ assert steam_app == steam_apps[1]
+ assert (
+ "Your system locale is incapable of displaying all characters"
+-in caplog.records[0].message
++in caplog.records[-1].message
+ )
+
+ @pytest.mark.parametrize("gui_cmd", ["yad", "zenity"])
+--- a/tests/conftest.py
b/tests/conftest.py
+@@ -44,6 +44,11 @@
+ logging.getLogger("protontricks").handlers.clear()
+
+
++@pytest.fixture(scope="function", autouse=True)
++def default_caplog(caplog):
++caplog.set_level(logging.INFO)
++
++
+ @pytest.fixture(scope="function")
+ def verbose_logging():
+ """
diff -Nru protontricks-1.10.5/debian/patches/series
protontricks-1.10.5/debian/patches/series
--- protontricks-1.10.5/debian/patches/series 1969-12-31 16:00:00.0
-0800
+++ protontricks-1.10.5/debian/patches/series 2024-06-06 12:26:50.0
-0700
@@ -0,0 +1 @@
+pytest8-caplog.patch
Processed: bug 1072789 is forwarded to https://bugs.launchpad.net/netplan/+bug/1987842
Processing commands for cont...@bugs.debian.org: > forwarded 1072789 https://bugs.launchpad.net/netplan/+bug/1987842 Bug #1072789 [netplan.io] netplan.io: CVE-2022-4968 Changed Bug forwarded-to-address to 'https://bugs.launchpad.net/netplan/+bug/1987842' from 'https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2065738'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1072789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072806: packagesearch:FTBFS:build failed（configure failed）
Source: packagesearch Version: 2.8.2+b1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear packagesearch Maintainer, The packagesearch package build failed on almost all archs caused by configure failed.The crucial buildd log below: ``` -- Found WrapAtomic: TRUE CMake Error at /usr/lib/riscv64-linux-gnu/cmake/Qt6Core/Qt6CoreMacros.cmake:2859 (message): Unexpected arguments: Call Stack (most recent call first): /usr/lib/riscv64-linux-gnu/cmake/Qt6Core/Qt6CoreMacros.cmake:2954 (qt6_standard_project_setup) CMakeLists.txt:9 (qt_standard_project_setup) -- Configuring incomplete, errors occurred! cd obj-riscv64-linux-gnu && tail -v -n \+0 CMakeCache.txt ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=packagesearch=riscv64=2.8.2%2Bb1=1717793575=0 My solution to this issue: This error is caused by incorrect parameters or calls during the CMake configuration process. I can provide a patch to fix this issue.I have tested it on local and it works well.The patch is in the attachment.Please let me know wheather this solution can be accepted. Gui-Yue Best Regards series Description: Binary data fix_configure_failed.patch Description: Binary data
