Bug#1005438: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl"
Hi Marcin,
On Sat, 26 Feb 2022 at 20:47, Marcin Owsiany wrote:
>
> Dnia Tue, Feb 22, 2022 at 08:57:25AM +0100, Andreas Tille napisał(a):
> > I had a look into this issue since a Debian Med package received a
> > testing removal warning. I can confirm the build fails with
> >
> >Segmentation fault
> >
> > in the build time test suite.
>
> Just out of curiosity I ran the tests during build under GDB (simply
> inserting "gdb --args" right before the "{interpreter}" in the
> overrite_dh_auto_test rule in debian/rules).
>
> It seems like the segfault is in the freetype library, when loading a font,
> rather than in pygame (though I guess the root cause could be pygame passing
> garbage to freetype? - I have zero knowledge about the API).
>
> Cc-ing Hugh in case he can provide some hints about what might be going on
> here.
>
> This does not change the fact that it would be great to move to pygame2 :-)
This test failure occurs in the ftfont test, which is an alternative
for the older SDL font API.
The cause does seem to be a change in FreeType 2.11.1, as the tests
pass with FreeType 2.11.0. Unfortunately, I can't see any relevant
changes easily. I suspect pygame might be dereferencing a NULL pointer
somewhere.
I did some testing and found that pygame 2.1.0 is the first recent
version not affected by the FreeType test issue.
I'll keep digging, but I'd strongly suggest migrating to the most
recent upstream version as soon as possible, as I had no problems
building it.
Hugh
Bug#1006384: swi-prolog breaks logol autopkgtest: Program exited with wrong status code
Dear Olivier, sorry for the delay with my message and thanks for your input. olivier sallou писал 2022-02-25 12:12: > ok, > after a quick look, issue is Logol is compiled against swi-prolog, and > there is an ABI issue I think, getting error: > > incompatible version (file: 67, Prolog: 68)] > > Recompiling logol in sid against swi-prolog 8.4.2+dfsg-2 results in > correct execution/tests. > > So, 2 things: > > * As swi-prolog is only a debian update (-1 to -2), I wonder why we > have this break now > * Possible fix is to rebuild logol package against this version in > sid, with a dep requirement on swi-prolog>=8.4.2+dfsg-2. But I don't > know how this should be managed (logol in testing will still prevent > swi-prolog to go, and logol in sid won't either go to testing because > will need swi-prolog version from sid...) It is not just Debian update. I've uploaded new upstream version of SWI-Prolog on Feb 15 (upgrade from 8.2.4 to 8.4.2). It is a new major update of stable branch of SWI-Prolog, and it breaks compatibility. As I can see logol tests failed already with 8.4.2+dfsg-1. There was an issue with ODBC support for SWI-Prolog on 32-bit platforms, so I uploaded 8.4.2+dfsg-2 fixing this issue. I think swi-prolog and (updated) logol may migrate simultaneously as it is the case for swi-prolog and eye (another package depending on swi-prolog). Otherwise, we could ask someone from Debian Release team to trigger the migration for the involved packages. Cheers! Lev > Le jeu. 24 févr. 2022 à 19:36, Paul Gevers a > écrit : > >> Source: swi-prolog, logol >> Control: found -1 swi-prolog/8.4.2+dfsg-2 >> Control: found -1 logol/1.7.9+dfsg-1 >> Severity: serious >> Tags: sid bookworm >> X-Debbugs-CC: debian...@lists.debian.org >> User: debian...@lists.debian.org >> Usertags: breaks needs-update >> >> Dear maintainer(s), >> >> With a recent upload of swi-prolog the autopkgtest of logol fails in >> >> testing when that autopkgtest is run with the binary packages of >> swi-prolog from unstable. It passes when run with only packages from >> >> testing. In tabular form: >> >> passfail >> swi-prolog from testing8.4.2+dfsg-2 >> logol from testing1.7.9+dfsg-1 >> all others from testingfrom testing >> >> I copied some of the output at the bottom of this report. >> >> Currently this regression is blocking the migration of swi-prolog to >> >> testing [1]. Due to the nature of this issue, I filed this bug >> report >> against both packages. Can you please investigate the situation and >> reassign the bug to the right package? >> >> More information about this bug and the reason for filing it can be >> found on >> > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation >> >> Paul >> >> [1] https://qa.debian.org/excuses.php?package=swi-prolog >> >> > https://ci.debian.net/data/autopkgtest/testing/amd64/l/logol/19529867/log.gz >> >> calling logol with parameters -g 1799.logol -s 1799.fasta -dna >> log4j:ERROR setFile(null,true) call failed. >> java.io.FileNotFoundException: /var/log/logol/logol.log (Permission >> denied) >> at java.base/java.io [1].FileOutputStream.open0(Native >> Method) >> at java.base/java.io >> [1].FileOutputStream.open(FileOutputStream.java:298) >> at java.base/java.io >> [1].FileOutputStream.(FileOutputStream.java:237) >> at java.base/java.io >> [1].FileOutputStream.(FileOutputStream.java:158) >> at >> org.apache.log4j.FileAppender.setFile(FileAppender.java:294) >> at >> org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) >> at >> > org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) >> at >> > org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) >> at >> > org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) >> at >> > org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) >> at >> > org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) >> at >> > org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) >> at >> > org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) >> at >> > org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) >> at >> > org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) >> at org.apache.log4j.LogManager.(LogManager.java:127) >> at org.apache.log4j.Logger.getLogger(Logger.java:117) >> at org.irisa.genouest.logol.Logol.(Unknown Source) >> For help, use option -h >> INFO org.irisa.genouest.logol.Logol - Using configuration file: >> /usr/share/logol/prolog/logol.properties >> INFO org.irisa.genouest.logol.Logol - option g called with >> 1799.logol >> INFO org.irisa.genouest.logol.Logol - option s called with >> 1799.fasta >> INFO org.irisa.genouest.logol.Logol - No maximum solutions defined, >> >> using defaults >> INFO org.ir
Bug#1006596: libxrt-utils: ships /usr/bin/mpd, already provided by mpd
Package: libxrt-utils Version: 202020.2.8.832+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb ... Unpacking libxrt-utils (202020.2.8.832+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/mpd', which is also in package mpd 0.23.5-1+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb cheers, Andreas mpd=0.23.5-1+b1_libxrt-utils=202020.2.8.832+dfsg-1.log.gz Description: application/gzip
Bug#1006557: toybox: Causes initramfs-tools trigger to fail without giving a reason
Hi Antoni, Antoni Villalonga wrote: > I've checked why it works on my system. I've tested the package on a Debian > Live environment where /bin is symlink to /usr/bin. \o/ Already suspected such a thing. But it's not related to the live system but to the installation time. In more recent Debian installations that symlink is there by default. Keyword here is "usrmerge" or "merged /usr". But it's usefulness and sanity are debated. > I'll push it to Salsa ASAP. Salsa seems still broken. :-/ Had to do my last upload without pushing to Salsa first, too. Anyway, I appreciated your prompt response! Thanks! Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1006539: marked as done (wine: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2)
Your message dated Mon, 28 Feb 2022 00:04:15 + with message-id and subject line Bug#1006539: fixed in wine 6.0.2~repack-3 has caused the Debian Bug report #1006539, regarding wine: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2 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.) -- 1006539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine Version: 6.0.2~repack-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Installation of wine fails with: Unpacking wine (6.0.2~repack-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-A9njpR/91-wine_6.0.2~repack-2_all.deb (--unpack): trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-A9njpR/91-wine_6.0.2~repack-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Cheers -- Package-specific info: /usr/bin/wine points to /usr/bin/wine-stable. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wine depends on: ii wine32 6.0.2~repack-2 ii wine64 6.0.2~repack-2 wine recommends no packages. Versions of packages wine suggests: pn dosbox pn exe-thumbnailer | kio-extras pn playonlinux pn q4wine pn winbind pn wine-binfmt ii winetricks0.0+20210206-2 Versions of packages libwine depends on: ii libasound2 1.2.6.1-2 ii libc62.33-7 ii libfaudio0 22.02-1 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.11.1+dfsg-1 ii libglib2.0-0 2.70.4-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgstreamer-plugins-base1.0-0 1.20.0-2 ii libgstreamer1.0-01.20.0-1 ii liblcms2-2 2.12~rc1-2 ii libldap-2.4-22.4.59+dfsg-1+b1 ii libmpg123-0 1.29.3-1 ii libopenal1 1:1.19.1-2 ii libpcap0.8 1.10.1-4 ii libpulse015.0+dfsg1-4 ii libudev1 250.3-2 ii libunwind8 1.3.2-2 ii libvkd3d11.2-11 ii libx11-6 2:1.7.2-2+b1 ii libxext6 2:1.3.4-1 ii libxml2 2.9.12+dfsg-6 ii libz-mingw-w64 1.2.11+dfsg-3 ii ocl-icd-libopencl1 [libopencl1] 2.2.14-3 Versions of packages libwine recommends: ii fonts-liberation 1:1.07.4-11 ii fonts-wine 6.0.2~repack-2 ii gstreamer1.0-plugins-good 1.20.0-2 ii libasound2-plugins 1.2.6-1 pn libcapi20-3 ii libcups2 2.4.1op1-1 ii libdbus-1-31.12.22-1 ii libgl1 1.4.0-1 ii libgl1-mesa-dri21.3.5-1 ii libgnutls303.7.3-4+b1 ii libgsm11.0.19-1 ii libgssapi-krb5-2 1.19.2-2 ii libjpeg62-turbo1:2.1.2-1 ii libkrb5-3 1.19.2-2 ii libodbc2 2.3.9-5 ii libosmesa6 21.3.5-1 ii libpng16-161.6.37-3 ii libsdl2-2.0-0 2.0.20+dfsg-2 ii libtiff5 4.3.0-4+b1 ii libv4l-0 1.22.1-2 ii libvulkan1 1.3.204.0-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor11:1.2.0-2 ii libxfixes3 1:6.0.0-1 ii libxi6 2:1.8-1 ii libxinerama1 2:1.1.4-3 ii libxrandr2 2:1.5.2-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.34-4 ii libxxf86vm1
Bug#1006557: toybox: Causes initramfs-tools trigger to fail without giving a reason
On Sun, Feb 27, 2022 at 09:02:17PM +0100, Axel Beckert wrote: > Package: toybox > Version: 0.8.6+dfsg-2 > Severity: serious > > Hi, > > since I upgraded toybox to 0.8.6+dfsg-2, the initramfs-tools trigger > fails on my machine: > > Processing triggers for initramfs-tools (0.140) ... > update-initramfs: Generating /boot/initrd.img-5.16.0-3-amd64 > E: /usr/share/initramfs-tools/hooks/zy-toybox failed with return 1. > update-initramfs: failed for /boot/initrd.img-5.16.0-3-amd64 with 1. > dpkg: error processing package initramfs-tools (--configure): > installed initramfs-tools package post-installation script subprocess > returned error exit status 1 > > Unfortunately /usr/share/initramfs-tools/hooks/zy-toybox doesn't note > what exactly went wrong. > > [...] > Changing > > TB_BIN=/usr/bin/toybox > > to > > TB_BIN=/bin/toybox > > fixes this. Hi Axel, Thanks for reporting the bug and the fix. I've checked why it works on my system. I've tested the package on a Debian Live environment where /bin is symlink to /usr/bin. \o/ Your fix proposal is correct. I'll push it to Salsa ASAP. Thanks for your time! -- Antoni Villalonga https://friki.cat/
Processed: closing 891436
Processing commands for cont...@bugs.debian.org: > close 891436 1.14.0-1 Bug #891436 [src:gnome-commander] gnome-commander: build dependency needs updating to scour Marked as fixed in versions gnome-commander/1.14.0-1. Bug #891436 [src:gnome-commander] gnome-commander: build dependency needs updating to scour Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 891436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 868417
Processing commands for cont...@bugs.debian.org: > close 868417 1.14.0-1 Bug #868417 [src:gnome-commander] gnome-commander: Please drop the (build-)dependency against gnome-vfs Marked as fixed in versions gnome-commander/1.14.0-1. Bug #868417 [src:gnome-commander] gnome-commander: Please drop the (build-)dependency against gnome-vfs Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 868417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 868417, reopening 868417, unarchiving 891436, reopening 891436, unarchiving 785125 ...
Processing commands for cont...@bugs.debian.org:
> # src:gnome-commander was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 868417
Bug #868417 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: Please drop the (build-)dependency
against gnome-vfs
Unarchived Bug 868417
> reopen 868417
Bug #868417 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: Please drop the (build-)dependency
against gnome-vfs
'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 1.4.8-1.1+rm.
> unarchive 891436
Bug #891436 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: build dependency needs updating to scour
Unarchived Bug 891436
> reopen 891436
Bug #891436 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: build dependency needs updating to scour
'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 1.4.8-1.1+rm.
> unarchive 785125
Bug #785125 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: Via USB attatched data storage device do not
appear in list of mounted devices
Unarchived Bug 785125
> reopen 785125
Bug #785125 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: Via USB attatched data storage device do not
appear in list of mounted devices
'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 1.4.8-1.1+rm.
> unarchive 886076
Bug #886076 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: Depends on gconf
Unarchived Bug 886076
> reopen 886076
Bug #886076 {Done: Debian FTP Masters }
[src:gnome-commander] gnome-commander: Depends on gconf
'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 1.4.8-1.1+rm.
> unarchive 441933
Bug #441933 {Done: Debian FTP Masters }
[gnome-commander] sometimes calculations are really off
Unarchived Bug 441933
> reopen 441933
Bug #441933 {Done: Debian FTP Masters }
[gnome-commander] sometimes calculations are really off
'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 1.4.8-1.1+rm.
> unarchive 638669
Bug #638669 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: Gnome Commander segfaults when adding a
program to "other favorite apps"
Unarchived Bug 638669
> reopen 638669
Bug #638669 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: Gnome Commander segfaults when adding a
program to "other favorite apps"
'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 1.4.8-1.1+rm.
> unarchive 657696
Bug #657696 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: opening smb share 'domain' field not works
Unarchived Bug 657696
> reopen 657696
Bug #657696 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: opening smb share 'domain' field not works
'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 1.4.8-1.1+rm.
> unarchive 663348
Bug #663348 {Done: Debian FTP Masters }
[gnome-commander] src/xcb_io.c:273: poll_for_event error
Unarchived Bug 663348
> reopen 663348
Bug #663348 {Done: Debian FTP Masters }
[gnome-commander] src/xcb_io.c:273: poll_for_event error
'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 1.4.8-1.1+rm.
> unarchive 712599
Bug #712599 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: external media are not embedded/no icon of
memory stick
Unarchived Bug 712599
> reopen 712599
Bug #712599 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: external media are not embedded/no icon of
memory stick
'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 1.4.8-1.1+rm.
> unarchive 773911
Bug #773911 {Done: Debian FTP Masters }
[gnome-commander] gnome-commander: Can't access SMB shares
Unarchived Bug 773911
> reopen 773911
Bug #773911 {Done: Debian FTP Masters }
[gnome-commander] gnome-
Bug#1005335: marked as done (eslint: Please update to node-regenerate-unicode-properties 10)
Your message dated Sun, 27 Feb 2022 21:48:35 +
with message-id
and subject line Bug#1005335: fixed in eslint 6.4.0~dfsg+~6.1.9-4
has caused the Debian Bug report #1005335,
regarding eslint: Please update to node-regenerate-unicode-properties 10
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.)
--
1005335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: eslint
Version: 6.4.0~dfsg+~6.1.9-2
Severity: wishlist
Tags: patch
Hi,
node-regenerate-unicode-properties API changed. Here is a patch to use
version 10 (pushed to experimental)
Cheers,
Yadd
diff --git a/debian/control b/debian/control
index 138fd942..ae22a9a6 100644
--- a/debian/control
+++ b/debian/control
@@ -53,7 +53,7 @@ Build-Depends:
node-progress ,
node-proxyquire ,
node-recast ,
- node-regenerate-unicode-properties ,
+ node-regenerate-unicode-properties (>= 10) ,
node-regexpp ,
node-semver ,
node-shelljs ,
@@ -99,7 +99,7 @@ Depends:
node-mkdirp,
node-optionator,
node-progress,
- node-regenerate-unicode-properties,
+ node-regenerate-unicode-properties (>= 10),
node-regexpp,
node-semver,
node-strip-json-comments,
diff --git a/debian/patches/1001_use_regenerate-unicode-properties.patch
b/debian/patches/1001_use_regenerate-unicode-properties.patch
index 5fa41188..717046e2 100644
--- a/debian/patches/1001_use_regenerate-unicode-properties.patch
+++ b/debian/patches/1001_use_regenerate-unicode-properties.patch
@@ -11,9 +11,9 @@ This patch header follows DEP-3:
http://dep.debian.net/deps/dep3/
//--
-const LETTER_PATTERN = require("./utils/patterns/letters");
-+const letters =
require("regenerate-unicode-properties/General_Category/Letter.js"),
-+lettersUppercase =
require("regenerate-unicode-properties/General_Category/Uppercase_Letter.js"),
-+lettersLowercase =
require("regenerate-unicode-properties/General_Category/Lowercase_Letter.js");
++const letters =
require("regenerate-unicode-properties/General_Category/Letter.js").characters,
++lettersUppercase =
require("regenerate-unicode-properties/General_Category/Uppercase_Letter.js").characters,
++lettersLowercase =
require("regenerate-unicode-properties/General_Category/Lowercase_Letter.js").characters;
const astUtils = require("./utils/ast-utils");
//--
@@ -54,7 +54,7 @@ This patch header follows DEP-3:
http://dep.debian.net/deps/dep3/
"natural-compare": "^1.4.0",
"optionator": "^0.8.2",
"progress": "^2.0.0",
-+"regenerate-unicode-properties": "^1.0.0",
++"regenerate-unicode-properties": "^10.0.0",
"regexpp": "^2.0.1",
"semver": "^6.1.2",
"strip-ansi": "^5.2.0",
--- End Message ---
--- Begin Message ---
Source: eslint
Source-Version: 6.4.0~dfsg+~6.1.9-4
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
eslint, 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 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated eslint 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: Sun, 27 Feb 2022 22:33:14 +0100
Source: eslint
Architecture: source
Version: 6.4.0~dfsg+~6.1.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jonas Smedegaard
Closes: 1005335
Changes:
eslint (6.4.0~dfsg+~6.1.9-4) unstable; urgency=medium
.
* add patches cherry-picked upstream:
+ stop use deprecated Node.js module leche
and adjust whitespace tolerance;
stop build-depend on node-leche
+ remove loose-parser tests;
stop build-depend on node-acorn
+ use newer Node.js module espree;
tighten build-dependency on node-espree
* update patch 1001 to use newer API;
tighten (build-)dependency on node-regenerate-unicode-properties;
closes: bug#1005335, thanks to Yadd
* unfuzz patches
Checksums-Sha1:
30be5cd4a6412f2881d7
Bug#1006571: wine64-development-tools: /usr/bin/function_grep.pl is already shipped by wine64-tools
Package: wine64-development-tools Version: 6.1~repack-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package wine64-development-tools. Preparing to unpack .../wine64-development-tools_6.1~repack-1_amd64.deb ... Unpacking wine64-development-tools (6.1~repack-1) ... dpkg: error processing archive /var/cache/apt/archives/wine64-development-tools_6.1~repack-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/function_grep.pl', which is also in package wine64-tools 6.0.2~repack-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/wine64-development-tools_6.1~repack-1_amd64.deb cheers, Andreas wine64-tools=6.0.2~repack-2_wine64-development-tools=6.1~repack-1.log.gz Description: application/gzip
Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools
Control: tags -1 +patch El vie, 25 feb 2022 a las 8:51, Lionel Élie Mamane () escribió: > > On Fri, Feb 25, 2022 at 12:51:32AM +0100, Agustin Martin wrote: > > El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane > > () escribió: > > > I have been looking at popcons and seems that regarding ispell dicts > > ifrench-gut is way more popular than ifrench, but on the hunspell side > > the winner is hunspell-fr (which pulls hunspell-fr-classical) > > > I do not know about the merits of the different ispell dicts, but > > keeping ifrench-gut ispell dict seems reasonable. On the other hand, > > unless it provides something better, dropping myspell-fr-gut as a real > > dict seems also reasonable, but this really requires more feedback > > from french users. > > If the -gut variant has a "better" word list, then I expect it is > better for both ispell and myspell? Hi, Lionel, myspell is gone, only hunspell is available and supports old myspell dictionaries like this one. Usually hunspell specific dicts are better than old myspell and ispell dicts, but sometimes they are just different and each one has its merits. Note that hunspell-fr-*dicts come from different source (https://grammalecte.net/home.php?prj=fr) than both ispell french dicts. If you think is useful to keep a myspell/hunspell version of gutenberg dict I am attaching a patch with a possible migration to ispellaff2myspell. In my limited tests it works better than old dict since it includes ' and - as wordchars. Whether to remove it or not in favour of hunspell-fr-* is something that can be decided later by french dicts maintainers (and will require some coordination). I have also noticed that while package contains a couple of patches with dpatch extension it does nor really use dpatch, so that would not be a problem, The mismatch in ispell hash format should be fixed by the new build (although I suggest to migrate to ispell-autobuildhash), so this patch should be enough if no side effects are found, I would also suggest some cleanup of ancient stuff and other improvements, but what needs quick action is the myspell-tools build-dep, which I think should be addressed by attached patch. Regards, -- Agustin diff -u ifrench-gut-1.0/debian/changelog ifrench-gut-1.0/debian/changelog diff -u ifrench-gut-1.0/debian/control ifrench-gut-1.0/debian/control --- ifrench-gut-1.0/debian/control +++ ifrench-gut-1.0/debian/control @@ -3,7 +3,7 @@ Section: text Priority: optional Standards-Version: 3.9.8 -Build-Depends: debhelper (>> 10), ispell (>= 3.3.02), dictionaries-common-dev (>= 1.10.5), myspell-tools +Build-Depends: debhelper (>> 10), ispell (>= 3.3.02), dictionaries-common-dev (>= 1.10.5), hunspell-tools #Homepage: http://www.gutenberg.eu.org/distributions/rubrique9.html Package: ifrench-gut diff -u ifrench-gut-1.0/debian/rules ifrench-gut-1.0/debian/rules --- ifrench-gut-1.0/debian/rules +++ ifrench-gut-1.0/debian/rules @@ -25,10 +25,10 @@ # Add here commands to compile the package. ./makehash - is2my-spell.pl francais.aff > fr-pre.aff - LC_ALL=C sed -e 's/^SET.*/SET ISO8859-15/;s/^TRY.*/TRY aeioàéèêîâsinrtlcdugmphbyfvkwôûëöïù½/' \ - -e 's/^\([PS]FX[[:space:]]\+.[[:space:]]\+[^[:space:]]\+[[:space:]]\+[^[:space:]]\+[[:space:]]\+\)\([^[:space:]]\+\)$$/\1\2/' \ - fr-pre.aff > fr.aff + ispellaff2myspell \ + --charset=latin0 \ + --myheader=debian/fr_FR@GUT.header \ + francais.aff > fr.aff wc -l < francais.dico > francais.dico.cnt cat francais.dico.cnt francais.dico > fr.dic only in patch2: unchanged: --- ifrench-gut-1.0.orig/debian/fr_FR@GUT.header +++ ifrench-gut-1.0/debian/fr_FR@GUT.header @@ -0,0 +1,19 @@ +# -*- coding: iso-8859-15 -*- +# +# Converted from ifrench-gut francais.aff affix file by +# ispellaff2myspell +# +# From ifrench-gut francais.aff affix file: +# +# Francais-GUTenberg v1.0 +# Fichier d'affixes pour le français +# Copyright 1999, Christophe Pythoud et GUTenberg +# - + +SET ISO8859-15 + +TRY aeioàéèêîâsinrtlcdugmphbyfvkwôûëöïù½ + +WORDCHARS -' + +# -
Processed: Re: Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools
Processing control commands: > tags -1 +patch Bug #1006132 [src:ifrench-gut] ifrench-gut: please stop build-depending on myspell-tools Added tag(s) patch. -- 1006132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006539: wine: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2
It is not just /usr/share/wine/wine/nls/c_037.nls that is conflicting. A forced install of 6.0.2~repack-2 emits the following warnings: Unpacking wine (6.0.2~repack-2) over (5.0.3-3) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_1.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_1.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10001.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10001.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10002.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10002.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10003.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10003.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10004.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10004.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10005.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10005.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10006.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10006.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10007.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10007.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10008.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10008.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10010.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10010.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10017.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10017.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10021.nls', which is also in package libwine:i386 6.0.2~repack-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/wine/wine/nls/c_10021
Bug#1006557: toybox: Causes initramfs-tools trigger to fail without giving a reason
Package: toybox Version: 0.8.6+dfsg-2 Severity: serious Hi, since I upgraded toybox to 0.8.6+dfsg-2, the initramfs-tools trigger fails on my machine: Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.16.0-3-amd64 E: /usr/share/initramfs-tools/hooks/zy-toybox failed with return 1. update-initramfs: failed for /boot/initrd.img-5.16.0-3-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Unfortunately /usr/share/initramfs-tools/hooks/zy-toybox doesn't note what exactly went wrong. I've added a "set -x" to /usr/share/initramfs-tools/hooks/zy-toybox and it fails as follows: ~ # dpkg --configure -a Setting up initramfs-tools (0.140) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.16.0-3-amd64 + echo + exit 0 + TB_BIN=/usr/bin/toybox + [ n = ] + [ -r /usr/share/initramfs-tools/hook-functions ] + . /usr/share/initramfs-tools/hook-functions + [ -f /var/tmp/mkinitramfs_Z7BaTH/bin/sh ] + rm -f /var/tmp/mkinitramfs_Z7BaTH/bin/toybox + copy_exec /usr/bin/toybox /bin/toybox + local src target x nonoptlib ret + src=/usr/bin/toybox + target=/bin/toybox + copy_file binary /usr/bin/toybox /bin/toybox + local type src target link_target + type=binary + src=/usr/bin/toybox + target=/bin/toybox + [ -f /usr/bin/toybox ] + return 2 + return 1 E: /usr/share/initramfs-tools/hooks/zy-toybox failed with return 1. update-initramfs: failed for /boot/initrd.img-5.16.0-3-amd64 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools dpkg --configure -a 5.13s user 2.38s system 96% cpu 7.800 total Changing TB_BIN=/usr/bin/toybox to TB_BIN=/bin/toybox fixes this. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages toybox depends on: ii libc6 2.33-7 ii libcrypt1 1:4.4.27-1.1 toybox recommends no packages. toybox suggests no packages. -- no debconf information
Bug#1006132: ifrench-gut: please stop build-depending on myspell-tools
Hi, On Thu, Feb 24, 2022 at 01:51:58PM +0100, Agustin Martin wrote: > I also wonder how relevant is myspell-fr-gut compared to > hunspell-fr-classical, hunspell-fr-comprehensive and > hunspell-fr-revised. If it is no longer needed it could be made a > transitional package to hunspell-fr making this particular problem > disappear (although not others). That's probably for the best. And if we go that way we should file a bug against firefox-l10-fr (and firefox-esr and thunderbird) to change their Recommends. But what about the ispell dictionary? src:ifrench provides a Quebec's variant, that I can't believe to be similar to the GUTemberg variant, even with me not knowing a single word of French. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#992065: marked as done (mpich: libhdf5-mpich-dev upgrade problems if libmpich1.0-dev is still installed)
Your message dated Sun, 27 Feb 2022 16:49:53 + with message-id and subject line Bug#992065: fixed in mpich 4.0.1-1 has caused the Debian Bug report #992065, regarding mpich: libhdf5-mpich-dev upgrade problems if libmpich1.0-dev is still installed 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.) -- 992065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mpich Version: 3.4.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libhdf5-mpich-dev During an piuparts upgrade test of libhdf5-mpich-dev on the upgrade path squeeze -> wheezy -> jessie -> stretch -> buster -> bullseye I observed this failure: Setting up libhdf5-mpich-dev (1.10.6+repack-4) ... update-alternatives: priority must be an integer Use 'update-alternatives --help' for program usage information. dpkg: error processing package libhdf5-mpich-dev (--configure): installed libhdf5-mpich-dev package post-installation script subprocess returned error exit status 2 mpi alternative setting after the failure (after upgrade squeeze...bullseye): # update-alternatives --query mpi Name: mpi Link: /usr/include/mpi Slaves: libmpi++.a /usr/lib/libmpi++.a libmpi++.so /usr/lib/libmpi++.so libmpi.a /usr/lib/libmpi.a libmpi.so /usr/lib/libmpi.so mpiCC /usr/bin/mpiCC mpiCC.1.gz /usr/share/man/man1/mpiCC.1.gz mpicc /usr/bin/mpicc mpicc.1.gz /usr/share/man/man1/mpicc.1.gz mpicxx /usr/bin/mpicxx mpicxx.1.gz /usr/share/man/man1/mpicxx.1.gz mpif77 /usr/bin/mpif77 mpif77.1.gz /usr/share/man/man1/mpif77.1.gz mpif90 /usr/bin/mpif90 mpif90.1.gz /usr/share/man/man1/mpif90.1.gz mpireconfig /usr/bin/mpireconfig mpireconfig.1.gz /usr/share/man/man1/mpireconfig.1.gz Status: auto Best: /usr/lib/mpich/include Value: /usr/lib/mpich/include Alternative: /usr/lib/mpich/include Priority: 10 Slaves: libmpi++.a /usr/lib/mpich/lib/libpmpich++.a libmpi++.so /usr/lib/mpich/lib/shared/libpmpich++.so libmpi.a /usr/lib/mpich/lib/libmpich.a libmpi.so /usr/lib/mpich/lib/shared/libmpich.so mpiCC /usr/bin/mpiCC.mpich mpiCC.1.gz /usr/share/man/man1/mpiCC.mpich.1.gz mpicc /usr/bin/mpicc.mpich mpicc.1.gz /usr/share/man/man1/mpicc.mpich.1.gz mpicxx /usr/bin/mpicxx.mpich mpicxx.1.gz /usr/share/man/man1/mpicxx.mpich.1.gz mpif77 /usr/bin/mpif77.mpich mpif77.1.gz /usr/share/man/man1/mpif77.mpich.1.gz mpif90 /usr/bin/mpif90.mpich mpif90.1.gz /usr/share/man/man1/mpif90.mpich.1.gz mpireconfig /usr/bin/mpireconfig.mpich mpireconfig.1.gz /usr/share/man/man1/mpireconfig.mpich.1.gz and after fresh installation in bullseye: # update-alternatives --query mpi Name: mpi Link: /usr/bin/mpicc Slaves: hdf5-mpi.pc /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5-mpi.pc mpiCC /usr/bin/mpiCC mpic++ /usr/bin/mpic++ mpicxx /usr/bin/mpicxx mpif77 /usr/bin/mpif77 mpif90 /usr/bin/mpif90 mpifort /usr/bin/mpifort Status: auto Best: /usr/bin/mpicc.mpich Value: /usr/bin/mpicc.mpich Alternative: /usr/bin/mpicc.mpich Priority: 40 Slaves: hdf5-mpi.pc /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5-mpich.pc mpiCC /usr/bin/mpicxx.mpich mpic++ /usr/bin/mpicxx.mpich mpicxx /usr/bin/mpicxx.mpich mpif77 /usr/bin/mpifort.mpich mpif90 /usr/bin/mpifort.mpich mpifort /usr/bin/mpifort.mpich OK, that is still an ancient mpi alternative at the time libhdf5-mpich-dev.postinst runs ... Probably caused by libmpich1.0-dev providing libmpich-dev and therefore no newer libmpich-dev getting installed. Trying to add some Breaks/Replaces ... tests running ... BTW, installing libmpich-dev in the failure state causes Selecting previously unselected package mpich. Preparing to unpack .../31-mpich_3.4.1-4_amd64.deb ... Unpacking mpich (3.4.1-4) ... dpkg: error processing archive /tmp/apt-dpkg-install-S2t7dN/31-mpich_3.4.1-4_amd64.deb (--unpack): trying to overwrite '/usr/bin/mpicc.mpich', which is also in package libmpich1.0-dev 1.2.7-9.1 Andreas libhdf5-mpich-dev_1.10.6+repack-4.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mpich Source-Version: 4.0.1-1 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of mpich, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance so
Bug#1005899: mplayer: should not release with bookworm
On Thu, Feb 17, 2022 at 08:45:59PM +0100, Sebastian Ramacher wrote: > On 2022-02-17 19:13:08 +0100, Reimar Döffinger wrote: > > > > > On 16 Feb 2022, at 23:25, Sebastian Ramacher wrote: > > > > > > Let's stop pretending that mplayer is maintained. > > > > What is your criteria for "maintained"? In Debian or upstream? Upstream > > issues are still addressed from time to time, there are still several > > people around that can address issues, in particular security issues. > > It's definitely not maintained in Debian. Looking at the recent history > of mplayer uploads, I did most of them without any bug triaging. So > that's not what I would consider mplaer being maintained. As to the bugs, I have looked through them from time to time and they all looked outdated, were not reproducible or definitely not relevant anymore (like G3 PowerPC). I didn't want to meddle with them beyond a quick check as I don't know much about the process. > If you want to pick up maintenance of mplayer in Debian, please feel > free do that. I asked one person with at least some knowledge about all that, but they seemed to think that Debian requirements are too high relative to the time they have available. > > > The upstream mailing > > > list infrastructure is gone > > > > I have absolutely no idea why you claim that. > > It's there and working. > > Yesterday evening lists.mplayerhq.hu failed to resolve. Otherwise I > would have forwarded the build failure with ffmpeg 5.0. In the end, this > will need to be fixed for bookworm. Compilation with FFmpeg 5.0 has been fixed since a while in our repo. Finally we've also built the release packages, though not done the final steps for releasing yet (download links etc). http://mplayerhq.hu/MPlayer/releases/MPlayer-1.5.tar.xz is the release that supports FFmpeg 5.0
Bug#1006549: ccextractor: FTBFS with gpac 2.0
Source: ccextractor Version: 0.93+ds2-1 Severity: serious Tags: ftbfs sid bookworm patch Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org ccextractor FTBFS with gpac 2.0. The attached patch fixes this issue. Cheers -- Sebastian Ramacher --- ccextractor-0.93+ds2.orig/src/lib_ccx/params.c +++ ccextractor-0.93+ds2/src/lib_ccx/params.c @@ -1,6 +1,7 @@ #include "png.h" #include "protobuf-c.h" #include "zlib.h" +#include "gpac/setup.h" #include "gpac/version.h" #include "lib_ccx.h" #include "ccx_common_option.h" signature.asc Description: PGP signature
Bug#1001376: marked as done (libtrilinos-tpetra-dev: missing Breaks+Replaces: libtrilinos-teuchos-dev (<< 13))
Your message dated Sun, 27 Feb 2022 15:11:20 +0100 with message-id and subject line libtrilinos-tpetra-dev: missing Breaks+Replaces: libtrilinos-teuchos-dev (<< 13) has caused the Debian Bug report #1001376, regarding libtrilinos-tpetra-dev: missing Breaks+Replaces: libtrilinos-teuchos-dev (<< 13) 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.) -- 1001376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtrilinos-tpetra-dev Version: 13.2.0-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libtrilinos-tpetra-dev_13.2.0-1~exp1_amd64.deb ... Unpacking libtrilinos-tpetra-dev:amd64 (13.2.0-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libtrilinos-tpetra-dev_13.2.0-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/include/trilinos/KokkosCompat_ClassicNodeAPI_Wrapper.hpp', which is also in package libtrilinos-teuchos-dev:amd64 12.18.1-2+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libtrilinos-tpetra-dev_13.2.0-1~exp1_amd64.deb cheers, Andreas libtrilinos-teuchos-dev=12.18.1-2+b1_libtrilinos-tpetra-dev=13.2.0-1~exp1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 13.2.0-1--- End Message ---
Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)
On Sun, 27 Feb 2022 12:21:47 +0100 Francesco Poli wrote: > On Sat, 26 Feb 2022 22:08:17 +0100 Ricardo Mones wrote: > > > On Tue, 15 Feb 2022 22:12:54 +0100 > > "Francesco Poli (wintermute)" wrote: > [...] > > > Files: UltimateClawsMail0.5.1/* > [...] > > > License: CC-BY-NC-SA-3.0 > [...] > > > > > > This is non-free, since it's non-commercial. > > > Please persuade its upstream copyright holder to re-license it > > > under DFSG-free terms (such as the GNU GPL) or drop the theme > > > from the package. > > > > Curiously enough, upstream site¹ says it's licensed under GPL: > > > > > The author of the Ultimate Gnome theme has graciously allowed me to > > > publish Ultimate Claws Mail under the GPL rather than Creative Commons. > > > UCM is now licensed under the GPL v3. > > That's encouraging! Thanks for investigating. > > > > > But the themeinfo metadata included in the tarball still says CC... > > Very awkward... > > > not sure > > if the above is enough to update the license on Debian's copyright and > > themeinfo or not though. What do you think? > [...] > > I think the best way forward is to get in touch with upstream copyright > holders and seek clarification. That can be difficult, since I'm unable to find any address of the Author within the upstream website or tarball. Furthermore seems that discussion already happened: https://code.google.com/archive/p/ultimate-claws-mail/issues/1 > Ideally, the metadata included in the upstream distribution tar archive > should be consistent with the statement on the upstream website. > > I would be great, if that theme were clearly and explicitly licensed > under the terms of the GNU GPL. Yeah, agreed, but given I doubt that can be possible at this point to make upstream release a new tarball just to fix those bits, specially without a contact address. Will try to ask upstream if somebody has his contact, otherwise I'm afraid the only solution will be the removal. regards, -- Ricardo Mones http://people.debian.org/~mones «Try to divide your time evenly to keep others happy.» pgpH20VA1nL_d.pgp Description: Firma digital OpenPGP
Bug#1005527: marked as done (python-wsproto: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Sun, 27 Feb 2022 13:20:27 +
with message-id
and subject line Bug#1005527: fixed in python-wsproto 1.1.0-1
has caused the Debian Bug report #1005527,
regarding python-wsproto: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
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.)
--
1005527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wsproto
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config
> running config
> I: pybuild base:237: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/__init__.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/handshake.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/events.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/frame_protocol.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/typing.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/extensions.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/connection.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> copying src/wsproto/utilities.py ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> running egg_info
> writing src/wsproto.egg-info/PKG-INFO
> writing dependency_links to src/wsproto.egg-info/dependency_links.txt
> writing requirements to src/wsproto.egg-info/requires.txt
> writing top-level names to src/wsproto.egg-info/top_level.txt
> reading manifest file 'src/wsproto.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/build'
> no previously-included directories found matching 'compliance/reports'
> no previously-included directories found matching
> 'compliance/auto-tests-server-config.json'
> no previously-included directories found matching
> 'compliance/auto-tests-client-config.json'
> no previously-included directories found matching
> 'compliance/autobahntestsuite-venv'
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> warning: no previously-included files matching '*.pyo' found anywhere in
> distribution
> warning: no previously-included files matching '*.swo' found anywhere in
> distribution
> warning: no previously-included files matching '*.swp' found anywhere in
> distribution
> warning: no previously-included files matching '*.map' found anywhere in
> distribution
> warning: no previously-included files matching '*.yml' found anywhere in
> distribution
> warning: no previously-included files matching '*.DS_Store' found anywhere in
> distribution
> warning: no previously-included files matching '.coverage' found anywhere in
> distribution
> adding license file 'LICENSE'
> writing manifest file 'src/wsproto.egg-info/SOURCES.txt'
> copying src/wsproto/py.typed ->
> /<>/.pybuild/cpython3_3.10_wsproto/build/wsproto
> I: pybuild base:237: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/__init__.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/handshake.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/events.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/frame_protocol.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/typing.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/extensions.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/connection.py ->
> /<>/.pybuild/cpython3_3.9_wsproto/build/wsproto
> copying src/wsproto/utilities.py ->
> /<>/.pybuild/cpython3_3.9_wsprot
Bug#1006547: diaspora-installer: incompatible with ruby3.0
Source: diaspora-installer Version: 0.7.15.0+debian1 Severity: serious Tags: upstream Justification: makes the package unsuitable After ruby-defaults switched to ruby3.0 as default, diaspora-installer started failing its autopkgtest. The failure looks like this: 8<8<8<- Installing gems with rubygems ... [DEPRECATED] The `--frozen` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local frozen 'true'`, and stop using this flag [DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local path 'vendor/bundle'`, and stop using this flag [DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'development test'`, and stop using this flag [DEPRECATED] The `--with` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local with 'postgresql'`, and stop using this flag [DEPRECATED] Your lockfile contains a single rubygems source section with multiple remotes, which is insecure. Make sure you run `bundle install` in non frozen mode and commit the result to make your lockfile secure. Fetching gem metadata from https://gems.diasporafoundation.org/.. Fetching gem metadata from https://rubygems.org/... Your bundle is locked to diaspora_federation-rails (0.2.6) from rubygems repository https://gems.diasporafoundation.org/, https://rubygems.org/ or installed locally, but that version can no longer be found in that source. That means the author of diaspora_federation-rails (0.2.6) has removed it. You'll need to update your bundle to a version other than diaspora_federation-rails (0.2.6) that hasn't been removed in order to install. dpkg: error processing package diaspora-installer (--configure): installed diaspora-installer package post-installation script subprocess returned error exit status 7 dpkg: dependency problems prevent configuration of autopkgtest-satdep: autopkgtest-satdep depends on diaspora-installer; however: Package diaspora-installer is not configured yet. 8<8<8<- I went to investigate inside a testbed, by copy the diaspora source that was downloaded into /tmp, and running `bundle` by hand from there. Then I get this: 8<8<8<- diaspora@autopkgtest-lxc-kiettk:/$ cp -r /var/cache/diaspora-installer/diaspora-0.7.15.0 /tmp/d diaspora@autopkgtest-lxc-kiettk:/$ cd /tmp/d diaspora@autopkgtest-lxc-kiettk:/tmp/d$ bundle Bundler 2.3.5 is running, but your lockfile was generated with 1.17.3. Installing Bundler 1.17.3 and restarting using that version. Fetching gem metadata from https://rubygems.org/. Fetching bundler 1.17.3 Installing bundler 1.17.3 /tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:29: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. [ this warning repeated *a lot* of times ] Fetching gem metadata from https://gems.diasporafoundation.org/.. Fetching gem metadata from https://rubygems.org/./tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:118: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. /tmp/d/vendor/bundle/ruby/3.0.0/gems/bundler-1.17.3/lib/bundler/shared_helpers.rb:118: warning: Pathname#untaint is deprecated and will be removed in Ruby 3.2. [ this warning repeated *a lot* of times ] Fetching gem metadata from https://gems.diasporafoundation.org/.. diaspora_federation-0.2.6 requires ruby version ~> 2.1, which is incompatible with the current version, ruby 3.0.2p107 8<8<8<- I went looking into github, and saw that there were a new release of diaspora, 0.7.16.0, that pulled diaspora_federation 0.2.7. I though that could resolve the issue, and tried to update like this: 8<8<8<- commit 051a42d95d25087e32f225e0ed4c264ccd4d4923 Author: Antonio Terceiro Date: Sun Feb 27 09:20:04 2022 -0300 Update diaspora to 0.7.16.0 for compatibility with ruby3.0+ diff --git a/debian/changelog b/debian/changelog index 06a7254..f652f44 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +diaspora-installer (0.7.16.0+debian1) experimental; urgency=medium + + * Team upload. + * Update diaspora to 0.7.16.0 for compatibility with ruby3.0+ + + -- Antonio Terceiro Sun, 27 Feb 2022
Bug#998553: marked as done (libdbi-drivers: FTBFS: 211104 9:49:12 [ERROR] mysqld got signal 11 ;)
Your message dated Sun, 27 Feb 2022 12:20:18 + with message-id and subject line Bug#998553: fixed in libdbi-drivers 0.9.0-10 has caused the Debian Bug report #998553, regarding libdbi-drivers: FTBFS: 211104 9:49:12 [ERROR] mysqld got signal 11 ; 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.) -- 998553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdbi-drivers Version: 0.9.0-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/debian/buildtests' > gcc test_dbi_lib.c -export-dynamic -shared -Wl,-soname,libtest_dbi_lib.so -o > libtest_dbi_lib.so -ldbi -fPIC > test_dbi_lib.c: In function ‘init_db’: > test_dbi_lib.c:26:5: warning: ‘dbi_initialize’ is deprecated > [-Wdeprecated-declarations] >26 | return dbi_initialize(dir); > | ^~ > In file included from test_dbi_lib.c:20: > /usr/include/dbi/dbi.h:169:27: note: declared here > 169 | int LIBDBI_API_DEPRECATED dbi_initialize(const char *driverdir); > | ^~ > gcc test_dl.c -o test_dl -ldl > rm -rf all-libs > mkdir -p all-libs > olddir=`pwd` && cd ../.. && rootdir=`pwd` && for f in `find drivers -name > 'libdbd*.so'` ; do ln -vs $rootdir/$f $olddir/all-libs ; done > '/<>/debian/buildtests/all-libs/libdbdpgsql.so' -> > '/<>/drivers/pgsql/.libs/libdbdpgsql.so' > '/<>/debian/buildtests/all-libs/libdbdfreetds.so' -> > '/<>/drivers/freetds/.libs/libdbdfreetds.so' > '/<>/debian/buildtests/all-libs/libdbdsqlite3.so' -> > '/<>/drivers/sqlite3/.libs/libdbdsqlite3.so' > '/<>/debian/buildtests/all-libs/libdbdmysql.so' -> > '/<>/drivers/mysql/.libs/libdbdmysql.so' > ./test_dl G all-libs > num drivers = 4 > ./test_dl N all-libs > num drivers = 4 > make[1]: Leaving directory '/<>/debian/buildtests' > # Testing sqlite3 > mkdir -p /<>/debian/sqlite3tests > ( echo i; \ > echo n; \ > echo ./drivers/sqlite3/.libs; \ > echo sqlite3; \ > echo /<>/debian/sqlite3tests; \ > echo libdbitest; ) | ./tests/test_dbi > > libdbi-drivers test program: $Id: test_dbi.c,v 1.72 2013/02/24 15:06:57 > mhoenicka Exp $ > > test instance-based (i) or legacy (l) libdbi interface? [i] log query (y|n)? > [n] libdbi driver directory? [/usr/lib/x86_64-linux-gnu/dbd] 1 drivers > available: sqlite3 > test which driver? database directory? [DEFAULT] database name? [libdbitest] > encoding? [] > Connection information: > > Legacy mode: 0 > Log query: 0 > Driverdir: ./drivers/sqlite3/.libs > Drivername:sqlite3 > Dbdir: /<>/debian/sqlite3tests > Initial Database: libdbitest > Database: libdbitest > Username: > Password: > Hostname: > Version: > Initial tables schema: CREATE TABLE test_datatypes ( the_char > CHAR,the_uchar CHAR,the_short SMALLINT,the_ushort SMALLINT,the_long > INT,the_ulong INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float > FLOAT4,the_double FLOAT8,the_driver_string > VARCHAR(255),the_conn_quoted_string VARCHAR(255),the_conn_quoted_string_copy > VARCHAR(255),the_conn_escaped_string > VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_numstring > VARCHAR(255),the_empty_string VARCHAR(255),the_null_string > VARCHAR(255),the_binary_quoted_string BLOB,the_binary_escaped_string > BLOB,the_datetime DATETIME,the_datetime_tz DATETIME,the_date DATE,the_time > TIME,the_time_tz TIME,id INTEGER AUTO INCREMENT) > Initial sub schema: > 0: > 1: > 2: > 3: > 4: > Initial data schema: INSERT INTO test_datatypes > (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_numstring,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz) > VALUES > (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can > ''we'' "quote" this properly?','Can ''we'' "quote" this properly
Bug#1006538: marked as done (plasma-workspace-data: ChangePassword.qml is in both plasma-workspace-data 4:5.24.2-1 and plasma-desktop-data 4:5.23.5-2 preventing upgrade)
Your message dated Sun, 27 Feb 2022 12:04:04 + with message-id and subject line Bug#1006538: fixed in plasma-workspace 4:5.24.2-2 has caused the Debian Bug report #1006538, regarding plasma-workspace-data: ChangePassword.qml is in both plasma-workspace-data 4:5.24.2-1 and plasma-desktop-data 4:5.23.5-2 preventing upgrade 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.) -- 1006538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-workspace-data Version: 4:5.24.2-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade: Preparing to unpack .../plasma-workspace-data_4%3a5.24.2-1_all.deb ... Unpacking plasma-workspace-data (4:5.24.2-1) over (4:5.23.5-1) ... dpkg: error processing archive /var/cache/apt/archives/plasma-workspace-data_4%3 a5.24.2-1_all.deb (--unpack): trying to overwrite '/usr/share/kpackage/kcms/kcm_users/contents/ui/ChangePassw ord.qml', which is also in package plasma-desktop-data 4:5.23.5-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) * What exactly did you do (or not do) that was effective (or ineffective)? removed plasma-desktop and plasma-workspace, then reinstalled plasma-desktop and plasma-workspace, taking care to re-install packages automatically removed in the process and taking care to remove packages automatically added in the process. * What was the outcome of this action? Successful upgrade. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers experimental APT policy: (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-rc5+ (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) -- no debconf information --- End Message --- --- Begin Message --- Source: plasma-workspace Source-Version: 4:5.24.2-2 Done: Patrick Franz We believe that the bug you reported is fixed in the latest version of plasma-workspace, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Franz (supplier of updated plasma-workspace 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: Sun, 27 Feb 2022 12:41:51 +0100 Source: plasma-workspace Architecture: source Version: 4:5.24.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Patrick Franz Closes: 1006538 Changes: plasma-workspace (4:5.24.2-2) unstable; urgency=medium . [ Pino Toscano ] * Bump the plasma-desktop-data breaks/replaces of plasma-workspace-data to 4:5.24.0. (Closes: #1006538) Checksums-Sha1: c637b1d70ef431da601ac03c03f6d751615b5ed4 5795 plasma-workspace_5.24.2-2.dsc d5a1c925753b0d0ee740f6f524ff62ccfd79d41a 47412 plasma-workspace_5.24.2-2.debian.tar.xz e1a0337541003cbcf4c45bc3151eb4c22cde7388 17980 plasma-workspace_5.24.2-2_source.buildinfo Checksums-Sha256: 9e64d7de563e14ab13dafaaab4d25addf1331fb4ee1985304876b8bcf45af997 5795 plasma-workspace_5.24.2-2.dsc da91a05b626c302ecd93212cd5076b9181e45bb53be48967254a9b2dd7e6ef7b 47412 plasma-workspace_5.24.2-2.debian.tar.xz b00b228fa81a8402deb39615d70fef09aad7efd7aad1bda55324638e599151be 17980 plasma-workspace_5.24.2-2_source.buildinfo Files: 3c08974544840018f343734bb0f1eee1 5795 kde optional plasma-workspace_5.24.2-2.dsc 8cae93ebbca5cc29c841817fa271129a 47412 kde optional plasma-workspace_5.24.2-2.debian.tar.xz 3d77b9ecb5ec7fc16c5e93058843aacc 17980 kde optional plasma-workspace_5.24.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYodBXDR68cxZHu3Knp96YDB3/lYFAmIbY6wACgkQnp96YDB3 /lZxog//Xgd+vm0BnBzHGj4mq+fwVq+/IfIPAVRVD+BGi6b+4cYcR/GWk8pT/m6n CJkXBSWompirqvmKFHybrxMHdD9AanMfpmESLrR75inIqsWbRjd5eyB0KrREWQmR /89aGCHhymWY+lB58rx0PklEBmhz+0N0hIYafilPdgwFDzIqgYPQGnPU23vNPgw
Bug#1006536: marked as done (python-prov fails its autopkgtest with rdflib 6.1.1-1)
Your message dated Sun, 27 Feb 2022 11:35:50 + with message-id and subject line Bug#1006536: fixed in python-prov 2.0.0-2 has caused the Debian Bug report #1006536, regarding python-prov fails its autopkgtest with rdflib 6.1.1-1 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.) -- 1006536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-prov Version: 2.0.0-1 Severity: serious Tags: patch X-Debbugs-Cc: jo...@jones.dk Hi Jonas, With recent upload of rdflib, python-prov fails its autopkgtest as seen here[1] (I did not paste logs as this clutters my terminal really) It is also FTBFS since it runs the same tests at build time. Upstream has fixed it in this commit[2] - please apply this and upload to unblock the transition [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-prov/19607711/log.gz [2]: https://github.com/trungdong/prov/commit/0b6b73bdf1f1fe1781b8ed1e329499d4df99c431 Regards, Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) 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 --- End Message --- --- Begin Message --- Source: python-prov Source-Version: 2.0.0-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of python-prov, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated python-prov 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: Sun, 27 Feb 2022 12:26:23 +0100 Source: python-prov Architecture: source Version: 2.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Jonas Smedegaard Closes: 1006536 Changes: python-prov (2.0.0-2) unstable; urgency=medium . * add patch cherry-picked upstream to ensure rdflib 6+ returns bytes when serializing tests; closes: bug#1006536, thanks to Nilesh Patra * add patch cherry-picked upstream to raise an exception when an empty URI is registered as a namespace Checksums-Sha1: 84b9d26722c047a4ec78d6dcccb91b0193c14a35 2374 python-prov_2.0.0-2.dsc 209e79a2a86011bfed6cd5ac34a43b5a88b23949 8452 python-prov_2.0.0-2.debian.tar.xz a74aaa028b2ee2af8ac453e336f410491ce4c0ec 9663 python-prov_2.0.0-2_amd64.buildinfo Checksums-Sha256: 90fd9f22dec18b94c4156c4e95df88ea2418dbf4dbbaf6968792a9709132c917 2374 python-prov_2.0.0-2.dsc 2a3ee9e8bc59f215075e83118b932351655a706398c387a3f4c5505c8d8e0829 8452 python-prov_2.0.0-2.debian.tar.xz 719847fb8367b6bf0e60a613930833fddd2f4b45a90cac5048b06ac6e58929b7 9663 python-prov_2.0.0-2_amd64.buildinfo Files: 914897a0159132da84094309f399781b 2374 python optional python-prov_2.0.0-2.dsc 7aaf658000bfef1c47fc46ea920bae15 8452 python optional python-prov_2.0.0-2.debian.tar.xz 825552ee8289c5ac6579669c21ff42a9 9663 python optional python-prov_2.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIbYOkACgkQLHwxRsGg ASE/Aw//dwrhjtj4ngwgqCObRcVb58cnycpV1Vj6KCif3KjIAiC3dUnhjvzbn/5p qQb2o5uieRPnVjjLuD7ARNRUXwxX6THwHuMaiq2EeOoVhOI6W5f57q0B1AVSdNIG vgvLKEEh5hGAfBSNlP3lsO+NtzertVOhedbIrsh53+0+5/Jvc620tQfYzbr46a/k uQYygqFYQgCMXRs7KvLvdtxteIYYW6XNQs4lh2amH9loTyJGlNHZH87L+JNk3r/E 5HLTtXr4+cGi8myOSYdy4jBavY475sllwndBjzaj9xDcCW36dp+/hGO+kmU4KTVu EpSTnoBwcC4kmOsyziO5BjemCPGnesA8Yjv+zFjVPjvBDJIf4RnL7I+9mtKjICj8 9xo1g8CXEmO+tr9Dy9kRm3i1r+yLn0R4yBEjfq0mW8JuqFiZcmpr1i11ry2+5Wgs tH4LT9osoSd4IhKQN4WHoStrTVSFafHiYXh+N8+GkwnC14mtKQhPmyY8t7axz67Y 70QwhFWFeAojzTn7F8DzKNpRF8R4mow+jU1tsqY85OGmk2fMhu3wfrjWznshug8j wITwYnGIZghGgXz2+wztQ0hUoTb/OoTROkvzfrsmIXOpkQ6Zx7Nk4QquVHhCSvdf vrpGBs6WccQty4BcRqd8liL/ehNr4ViBzYlNRVHszNvsT2hLaw0= =/pIQ -END PGP SIGNATURE End Message ---
Processed: Bug#1006536 marked as pending in python-prov
Processing control commands: > tag -1 pending Bug #1006536 [src:python-prov] python-prov fails its autopkgtest with rdflib 6.1.1-1 Added tag(s) pending. -- 1006536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006536: marked as pending in python-prov
Control: tag -1 pending Hello, Bug #1006536 in python-prov reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-prov/-/commit/a605728c3fa9a575febd85cbf3a0cb0c176bde66 add patch cherry-picked upstream to ensure rdflib 6+ returns bytes when serializing tests; closes: bug#1006536, thanks to Nilesh Patra (this message was generated automatically) -- Greetings https://bugs.debian.org/1006536
Bug#995354: Requires to package ruby-thread-local
At least, updating to async-http 0.56.0 or later will satisfy dependency. https://rubygems.org/gems/async-http/versions/0.56.0 async-http 0.56.0 or later requires protocol-http >= 0.22.0 < 0.23, but ruby-protocol-http 0.22.5-1 is packaged in sid. It also adds new development dependency for localhost, but ruby-localhost is already packaged in sid.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1006538 serious Bug #1006538 [plasma-workspace-data] plasma-workspace-data: ChangePassword.qml is in both plasma-workspace-data 4:5.24.2-1 and plasma-desktop-data 4:5.23.5-2 preventing upgrade Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1006538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006540: renpy: Move package to experimental while porting is still in progress
Package: renpy Version: 7.3.5+dfsg-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: onit...@gmail.com Dear Maintainer, Please consider moving the Debian Ren'Py package from sid to experimental. It is currently in an unusable state, because the Python 3 porting process is still ongoing. It doesn't make any sense to have it in testing right now, and unstable is probably not ideal either. FWIW, the package currently doesn't install properly: --- snip --- Setting up renpy (7.3.5+dfsg-2) ... File "/usr/share/games/renpy/launcher/game/gui7/code.py", line 283 l = re.sub(ur'_\((\".*?\")\)', replace, l) ^ SyntaxError: invalid syntax File "/usr/share/games/renpy/launcher/game/pefile.py", line 88 IMAGE_ORDINAL_FLAG = 0x8000L ^ SyntaxError: invalid syntax --- snip, similar errors follow --- According to [1], there are preliminary Ren'Py 8 releases with Python 3 support. It would be great to have packages built from the upstream nightlies [2], so people can start testing them in Debian. Thank you! [1] https://github.com/renpy/renpy/issues/2003#issuecomment-1016741906 [2] https://nightly.renpy.org/current-8/index.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages renpy depends on: ii fonts-dejavu-core 2.37-2 ii fonts-motoya-l-cedar 1.01-5 ii fonts-nanum 20200506-1 ii fonts-roboto-hinted 2:0~20170802-3 ii python-renpy 7.3.5+dfsg-2 ii python3 3.9.8-1 ii python3-pygame-sdl2 7.4.10-1+b1 Versions of packages renpy recommends: ii python-tk2.7.18-1 ii python2 [python-ctypes] 2.7.18-3 ii zenity 3.41.0-2 renpy suggests no packages. -- no debconf information
Bug#1006539: wine: trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2
Package: wine Version: 6.0.2~repack-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org Installation of wine fails with: Unpacking wine (6.0.2~repack-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-A9njpR/91-wine_6.0.2~repack-2_all.deb (--unpack): trying to overwrite '/usr/share/wine/wine/nls/c_037.nls', which is also in package libwine:amd64 6.0.2~repack-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-A9njpR/91-wine_6.0.2~repack-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Cheers -- Package-specific info: /usr/bin/wine points to /usr/bin/wine-stable. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wine depends on: ii wine32 6.0.2~repack-2 ii wine64 6.0.2~repack-2 wine recommends no packages. Versions of packages wine suggests: pn dosbox pn exe-thumbnailer | kio-extras pn playonlinux pn q4wine pn winbind pn wine-binfmt ii winetricks0.0+20210206-2 Versions of packages libwine depends on: ii libasound2 1.2.6.1-2 ii libc62.33-7 ii libfaudio0 22.02-1 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.11.1+dfsg-1 ii libglib2.0-0 2.70.4-1 ii libgphoto2-6 2.5.27-1 ii libgphoto2-port122.5.27-1 ii libgstreamer-plugins-base1.0-0 1.20.0-2 ii libgstreamer1.0-01.20.0-1 ii liblcms2-2 2.12~rc1-2 ii libldap-2.4-22.4.59+dfsg-1+b1 ii libmpg123-0 1.29.3-1 ii libopenal1 1:1.19.1-2 ii libpcap0.8 1.10.1-4 ii libpulse015.0+dfsg1-4 ii libudev1 250.3-2 ii libunwind8 1.3.2-2 ii libvkd3d11.2-11 ii libx11-6 2:1.7.2-2+b1 ii libxext6 2:1.3.4-1 ii libxml2 2.9.12+dfsg-6 ii libz-mingw-w64 1.2.11+dfsg-3 ii ocl-icd-libopencl1 [libopencl1] 2.2.14-3 Versions of packages libwine recommends: ii fonts-liberation 1:1.07.4-11 ii fonts-wine 6.0.2~repack-2 ii gstreamer1.0-plugins-good 1.20.0-2 ii libasound2-plugins 1.2.6-1 pn libcapi20-3 ii libcups2 2.4.1op1-1 ii libdbus-1-31.12.22-1 ii libgl1 1.4.0-1 ii libgl1-mesa-dri21.3.5-1 ii libgnutls303.7.3-4+b1 ii libgsm11.0.19-1 ii libgssapi-krb5-2 1.19.2-2 ii libjpeg62-turbo1:2.1.2-1 ii libkrb5-3 1.19.2-2 ii libodbc2 2.3.9-5 ii libosmesa6 21.3.5-1 ii libpng16-161.6.37-3 ii libsdl2-2.0-0 2.0.20+dfsg-2 ii libtiff5 4.3.0-4+b1 ii libv4l-0 1.22.1-2 ii libvulkan1 1.3.204.0-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor11:1.2.0-2 ii libxfixes3 1:6.0.0-1 ii libxi6 2:1.8-1 ii libxinerama1 2:1.1.4-3 ii libxrandr2 2:1.5.2-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.34-4 ii libxxf86vm11:1.1.4-1+b2 Versions of packages libwine suggests: ii cups-bsd 2.4.1op1-1 ii gstreamer1.0-libav 1.20.0-1 ii gstreamer1.0-plugins-bad 1.20.0-4+b1 ii gstreamer1.0-plugins-ugly 1.20.0-1+b1 ii ttf-mscorefonts-installer 3.8 Versions of packages wine32 depends on: ii libc62.33-7 ii libwine 6.0.2~repack-2 wine32 recommends no packages. Versions of packages wine32 suggests: pn wine32-preloader Versions of packages wine64 depends on: ii libc62.33-7 ii libwine 6.0.2~repack-2 Versions of packages wine64 recommends: ii wine32 6.0.2~repack-2 Versions of packages wine64 suggests: pn wine64-preloader Versions of packages wine is related to: pn dxvk pn dxvk-wine32-development pn dxvk-wine64-development ii fonts-wine 6.0.2~repack-2 -- no debconf information -- Sebastian Ramacher
Bug#1005773: marked as done (ortools-samples: ships /usr/bin/knapsack, /usr/bin/tsp)
Your message dated Sun, 27 Feb 2022 09:20:23 + with message-id and subject line Bug#1005773: fixed in ortools 8.2+ds-2 has caused the Debian Bug report #1005773, regarding ortools-samples: ships /usr/bin/knapsack, /usr/bin/tsp 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.) -- 1005773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ortools-samples Version: 8.2+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. I do not think that Breaks+Replaces would be an appropriate solution in this case. Given the package name (ortools-samples), I'm not sure whether these example binaries belong to /usr/bin at all ..., at least not with such generic names. >From the attached log (scroll to the bottom...): Preparing to unpack .../ortools-samples_8.2+ds-1_amd64.deb ... Unpacking ortools-samples (8.2+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/ortools-samples_8.2+ds-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/knapsack', which is also in package ruby-knapsack 1.18.0-2 Errors were encountered while processing: /var/cache/apt/archives/ortools-samples_8.2+ds-1_amd64.deb Preparing to unpack .../ortools-samples_8.2+ds-1_amd64.deb ... Unpacking ortools-samples (8.2+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/ortools-samples_8.2+ds-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/tsp', which is also in package task-spooler 1.0.1+dfsg1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ortools-samples_8.2+ds-1_amd64.deb cheers, Andreas ruby-knapsack=1.18.0-2_ortools-samples=8.2+ds-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ortools Source-Version: 8.2+ds-2 Done: Agathe Porte We believe that the bug you reported is fixed in the latest version of ortools, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Agathe Porte (supplier of updated ortools 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: SHA256 Format: 1.8 Date: Sat, 26 Feb 2022 12:00:30 +0100 Source: ortools Architecture: source Version: 8.2+ds-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Agathe Porte Closes: 1005773 Changes: ortools (8.2+ds-2) unstable; urgency=medium . * patch: drop references to removed absl::container target * Move samples in /usr/lib instead of /usr/bin (Closes: #1005773) Checksums-Sha1: 24afaf2527255e5284b21aafa64041d3a5deb8fc 2638 ortools_8.2+ds-2.dsc dbbcec5160a1004deb1354b7cd95f7cb931fa082 8316 ortools_8.2+ds-2.debian.tar.xz 5e044d44d5091cd94313ba2712ee6c28e8085248 11563 ortools_8.2+ds-2_source.buildinfo Checksums-Sha256: 2f87cfb2f8c56e0959370e4fc691aaae3bbf42576791c4586d172e0eb506 2638 ortools_8.2+ds-2.dsc 00bc37359633d51eb41da923d27b6b9f294d7d2e4e7418925c8528d42f122329 8316 ortools_8.2+ds-2.debian.tar.xz c7c1ceac397e09ac2f821970c2e6c7fc21fa237002b0ad198fb83d691f0b803c 11563 ortools_8.2+ds-2_source.buildinfo Files: 9841ce74a16c0ac2ea21affa9b3200b1 2638 science optional ortools_8.2+ds-2.dsc 8a2f00f33e7554dce557e0f1bc797206 8316 science optional ortools_8.2+ds-2.debian.tar.xz ed29ffb35f6c8fc4b8c7a831f3e42fc5 11563 science optional ortools_8.2+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmIbPhUACgkQEWhSvN91 FcDxphAAnk73Qhmqoti7BBR+96dK7FGK3djnzf4M7xGiWXpMuAQ8Di4g/sjAQDdK sJ3u0n+dNRl7h1DIioVwjDvWpI7pzbOCrBEsN+Z3R5XY8DqafHUe8kv1En8iXEdk nRcIqwd75FbDQ+/HvjuHqtI1MDfP6WnoePkgoATFrhKYAsbGiQhT7VqNwhqLYhUC wt/pErNem6W2mXCs+5AB1h5UYUInsgszIov9NUC+dEsLaxfNn7Wq6iB5PYARTOSx /q8g3iNUG0X8Ht2xBHmMvR18tjQPmGpK32WdC4h6DzcTio4FWPOKLBbVuLFYv9pY /0DDX8znATvCojQSJb2eYYhOF+0TlOl3f22NZXhVoIPDX4mCDxvrmm25MAAdkQjW lMYNIyov0SdbJgPF6vhNaaKhOhejQD/R4Mc/lJfbqF6dG
Bug#1006537: dask: autopkgtest failure on 32 bit, mismatch in size of data structure.
Package: dask Version: 2022.01.0+dfsg-1 Severity: serious The autopkgtest for dask is once-again failing on 32-bit architectures, this is blocking the fix for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005962 from migrating to testing. > assert buf.getvalue() == expected E assert " E Int64Index: 4 entries, 0 to 3 E Data columns (total 3 columns): E# Column Non-Null Count Dtype E --- -- -- - E0 x 4 non-null int64 E1 y 4 non-null category... E E ...Full output truncated (7 lines hidden), use '-vv' to show /usr/lib/python3/dist-packages/dask/dataframe/tests/test_dataframe.py:3612: AssertionError I think the most likely explanation is that the memory usage of the data structure is indeed lower on 32-bit architectures and that this does not indicate a bug. As such I have prepared a patch that adjusts the expected result in the test based on the pointer size on the current architecture. diff -Nru dask-2022.01.0+dfsg/debian/changelog dask-2022.01.0+dfsg/debian/changelog --- dask-2022.01.0+dfsg/debian/changelog2022-02-21 01:11:53.0 + +++ dask-2022.01.0+dfsg/debian/changelog2022-02-27 07:27:00.0 + @@ -1,3 +1,11 @@ +dask (2022.01.0+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Adjust test_dataframe.py for different data structure sizes on 32-bit +architectures. + + -- Peter Michael Green Sun, 27 Feb 2022 07:27:00 + + dask (2022.01.0+dfsg-1) unstable; urgency=medium * New upstream release diff -Nru dask-2022.01.0+dfsg/debian/patches/series dask-2022.01.0+dfsg/debian/patches/series --- dask-2022.01.0+dfsg/debian/patches/series 2022-02-20 22:18:36.0 + +++ dask-2022.01.0+dfsg/debian/patches/series 2022-02-27 07:27:00.0 + @@ -9,3 +9,4 @@ use-youtube-nocookie.patch reproducible-config-autofunction.patch 32bit-comatibility.patch +test-dataframe-32-bit.patch diff -Nru dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch --- dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch 1970-01-01 00:00:00.0 + +++ dask-2022.01.0+dfsg/debian/patches/test-dataframe-32-bit.patch 2022-02-27 07:27:00.0 + @@ -0,0 +1,25 @@ +Description: Adjust test_dataframe.py for different data structure sizes on 32-bit architectures. +Author: Peter Michael Green + +Index: dask-2022.01.0+dfsg/dask/dataframe/tests/test_dataframe.py +=== +--- dask-2022.01.0+dfsg.orig/dask/dataframe/tests/test_dataframe.py dask-2022.01.0+dfsg/dask/dataframe/tests/test_dataframe.py +@@ -3597,6 +3597,8 @@ def test_categorize_info(): + # Verbose=False + buf = StringIO() + ddf.info(buf=buf, verbose=True) ++pointersize = np.array([0],dtype=np.uintp).itemsize ++bytecount = 128 + pointersize * 46 + expected = ( + "\n" + "Int64Index: 4 entries, 0 to 3\n" +@@ -3607,7 +3609,7 @@ def test_categorize_info(): + " 1 y 4 non-null category\n" + " 2 z 4 non-null object\n" + "dtypes: category(1), object(1), int64(1)\n" +-"memory usage: 496.0 bytes\n" ++"memory usage: "+str(bytecount)+".0 bytes\n" + ) + assert buf.getvalue() == expected +
Bug#1006536: python-prov fails its autopkgtest with rdflib 6.1.1-1
Source: python-prov Version: 2.0.0-1 Severity: serious Tags: patch X-Debbugs-Cc: jo...@jones.dk Hi Jonas, With recent upload of rdflib, python-prov fails its autopkgtest as seen here[1] (I did not paste logs as this clutters my terminal really) It is also FTBFS since it runs the same tests at build time. Upstream has fixed it in this commit[2] - please apply this and upload to unblock the transition [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-prov/19607711/log.gz [2]: https://github.com/trungdong/prov/commit/0b6b73bdf1f1fe1781b8ed1e329499d4df99c431 Regards, Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) 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
