Processed: pypdf2: new upstream version available, fixes #1010821
Processing control commands: > reassign 1010821 pypdf2 2.4.2-1 Bug #1010821 [src:xml2rfc] PyPDF2 fails to read a PDF file with a beginbfchar entry with an empty second element Bug reassigned from package 'src:xml2rfc' to 'pypdf2'. No longer marked as found in versions xml2rfc/3.12.4-1. Ignoring request to alter fixed versions of bug #1010821 to the same values previously set Bug #1010821 [pypdf2] PyPDF2 fails to read a PDF file with a beginbfchar entry with an empty second element There is no source info for the package 'pypdf2' at version '2.4.2-1' with architecture '' Unable to make a source version for version '2.4.2-1' Marked as found in versions 2.4.2-1. -- 1010821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010821 1015296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806930: closing 806930
close 806930 thanks Howdy, My apoligies this wasn't addressed in a stable release of Debian, but as it's now fixed in all supported versions of Debian, and libcurl is used so it shouldn't happen again, I'm closing this report. Hopefully you still use pianobar, and hopefully you use something newer than oldoldoldstable. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Processed: closing 806930
Processing commands for cont...@bugs.debian.org: > close 806930 Bug #806930 [pianobar] pianobar needs update for new server SSL certificate Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 806930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008342: pngnq need a rebuild on buildd
Hi, This bug don't exist in my local machine now. It's need a rebuild on buildd. -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature Description: OpenPGP digital signature
Bug#1013281: closed by Debian FTP Masters (reply to Pierre Gruet ) (Bug#1013281: fixed in batik 1.14-2)
> We have two things here: > - The org.apache.batik.apps.rasterizer.Main class has been moved to > another jar: /usr/share/java/batik-svgrasterizer.jar; > - Some Class-Path and Main-Class indications are missing in the jars we > ship in libbatik-java. > > I believe your call would be OK right now if you tried > rasterizer -m image/png -scriptSecurityOff -w 1920 > /tmp/ramdisk/svgproc-b83e35c457f48904da8a39a01d230d48.svg > > rasterizer is a script lying in /usr/bin that we ship in libbatik-java. > > > (FYI, I installed Inkscape on my system to have an alternate SVG renderer) I’ve tried several different SVGs: # rasterizer -d /tmp/rampdisk/ -m image/png -scriptSecurityOff -w 1920 /usr/share/inkscape/icons/multicolor/symbolic/actions/xml-node-delete-symbolic.svg.2019_12_27_20_11_26.0.svg [warning] /usr/bin/rasterizer: JVM flavor 'sun' not understood About to transcode 1 SVG file(s) Converting xml-node-delete-symbolic.svg.2019_12_27_20_11_26.0.svg to /tmp/rampdisk/xml-node-delete-symbolic.svg.2019_12_27_20_11_26.0.png ... … success This says success, but there is no output file. # rasterizer -d /tmp/rampdisk/ -m image/png -scriptSecurityOff -w 1920 /usr/share/apache2/icons/apache_pb.svg [warning] /usr/bin/rasterizer: JVM flavor 'sun' not understood About to transcode 1 SVG file(s) Converting apache_pb.svg to /tmp/rampdisk/apache_pb.png ... Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xmlgraphics/java2d/color/NamedColorSpace at org.apache.batik.bridge.SVGShapeElementBridge.createShapePainter(SVGShapeElementBridge.java:117) at org.apache.batik.bridge.SVGDecoratedShapeElementBridge.createFillStrokePainter(SVGDecoratedShapeElementBridge.java:58) at org.apache.batik.bridge.SVGDecoratedShapeElementBridge.createShapePainter(SVGDecoratedShapeElementBridge.java:84) at org.apache.batik.bridge.SVGShapeElementBridge.buildGraphicsNode(SVGShapeElementBridge.java:91) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:224) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:171) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:219) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:171) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:219) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:171) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:82) at org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(SVGAbstractTranscoder.java:210) at org.apache.batik.transcoder.image.ImageTranscoder.transcode(ImageTranscoder.java:92) at org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(XMLAbstractTranscoder.java:142) at org.apache.batik.transcoder.SVGAbstractTranscoder.transcode(SVGAbstractTranscoder.java:158) at org.apache.batik.apps.rasterizer.SVGConverter.transcode(SVGConverter.java:1008) at org.apache.batik.apps.rasterizer.SVGConverter.execute(SVGConverter.java:719) at org.apache.batik.apps.rasterizer.Main.execute(Main.java:954) at org.apache.batik.apps.rasterizer.Main.main(Main.java:1007) Caused by: java.lang.ClassNotFoundException: org.apache.xmlgraphics.java2d.color.NamedColorSpace at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) ... 19 more No output here of course. > Please tell me if you need it in bullseye or if calling > rasterizer ... > is OK for you. I do not have a "testing" box try out the fix and rasterizer on bullseye seems to have same/similar problems.
Bug#1015025: marked as done (pytest-xdist: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Tue, 19 Jul 2022 00:34:25 + with message-id and subject line Bug#1015025: fixed in pytest-xdist 2.5.0-5 has caused the Debian Bug report #1015025, regarding pytest-xdist: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-xdist Version: 2.5.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9_pytest-xdist/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10_pytest-xdist/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using options from > pytest-xdist-2.5.0/debian/source/options: > --extend-diff-ignore=^src/_pytest/_version.py$ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-xdist using existing > ./pytest-xdist_2.5.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > pytest-xdist-2.5.0/src/xdist/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-xdist_2.5.0-4.diff.WQquCB > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:57:32Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-xdist_2.5.0-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pytest-xdist Source-Version: 2.5.0-5 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of pytest-xdist, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated pytest-xdist 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: Mon, 18 Jul 2022 20:07:15 -0400 Source: pytest-xdist Architecture: source Version: 2.5.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Scott Talbert Closes: 1015025 Changes: pytest-xdist (2.5.0-5) unstable; urgency=medium . * Fix FTBFS due to _version.py path change (Closes: #1015025) Checksums-Sha1: 27fc5f2568af6dd794e7114d0a
Bug#1015025: marked as pending in pytest-xdist
Control: tag -1 pending Hello, Bug #1015025 in pytest-xdist 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/pytest-xdist/-/commit/58daacd2ce663e7bcdb54a93db3a723c0a6e9f79 Fix FTBFS due to _version.py path change (Closes: #1015025) (this message was generated automatically) -- Greetings https://bugs.debian.org/1015025
Processed: Bug#1015025 marked as pending in pytest-xdist
Processing control commands: > tag -1 pending Bug #1015025 [src:pytest-xdist] pytest-xdist: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015291: haskell-crypto-numbers FTBFS: error: Variable not in scope
Source: haskell-crypto-numbers
Version: 0.2.7-10
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-crypto-numbers&suite=sid
...
Crypto/Number/Prime.hs:82:6: error:
Variable not in scope: nextPrimeInteger :: Integer -> Integer
|
82 | (nextPrimeInteger n, rng)
|
Crypto/Number/Prime.hs:92:10: error:
• Variable not in scope:
testPrimeInteger :: Integer -> Int# -> Int#
• Perhaps you meant ‘testBitInteger’ (imported from
GHC.Integer.GMP.Internals)
|
92 | case testPrimeInteger n tries of
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015290: haskell-hsini FTBFS: error: Couldn't match type
Source: haskell-hsini
Version: 0.5.1.2-6
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-hsini&suite=sid
...
tst/ReaderI.hs:118:27: error:
• Couldn't match type: String -> IniFile
with:
template-haskell-2.17.0.0:Language.Haskell.TH.Syntax.Q
template-haskell-2.17.0.0:Language.Haskell.TH.Syntax.Exp
Expected: template-haskell-2.17.0.0:Language.Haskell.TH.Lib.Internal.ExpQ
Actual: String -> IniFile
• Probable cause: ‘OptionContL’ is applied to too few arguments
In the expression: OptionContL
In the untyped splice: $OptionContL
|
118 | expected = Right $OptionContL "foo"
| ^^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"build", "--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"build", "--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 642
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015289: haskell-genvalidity FTBFS: error: Could not find module ‘Data.RelativeValidity’
Source: haskell-genvalidity
Version: 0.11.0.0-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-genvalidity&suite=sid
...
src/Data/GenRelativeValidity.hs:9:1: error:
Could not find module ‘Data.RelativeValidity’
Use -v (or `:set -v` in ghci) to see a list of the files searched for.
|
9 | import Data.RelativeValidity
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015288: haskell-test-framework-th-prime FTBFS: Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
Source: haskell-test-framework-th-prime
Version: 0.0.10-4
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-test-framework-th-prime&suite=sid
...
Test/Framework/TH/Prime/Parser.hs:41:20: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: ListE (map toCase cases)
In the first argument of ‘TupE’, namely
‘[ListE (map toCase cases), ListE (map toProp props)]’
In the second argument of ‘($)’, namely
‘TupE [ListE (map toCase cases), ListE (map toProp props)]’
|
41 | return $ TupE [ListE (map toCase cases), ListE (map toProp props)]
|
Test/Framework/TH/Prime/Parser.hs:41:46: error:
• Couldn't match expected type ‘Maybe Exp’ with actual type ‘Exp’
• In the expression: ListE (map toProp props)
In the first argument of ‘TupE’, namely
‘[ListE (map toCase cases), ListE (map toProp props)]’
In the second argument of ‘($)’, namely
‘TupE [ListE (map toCase cases), ListE (map toProp props)]’
|
41 | return $ TupE [ListE (map toCase cases), ListE (map toProp props)]
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1013281: marked as done (libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main)
Your message dated Mon, 18 Jul 2022 22:18:55 + with message-id and subject line Bug#1013281: fixed in batik 1.14-2 has caused the Debian Bug report #1013281, regarding libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main 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.) -- 1013281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libbatik-java Version: 1.12-4 Severity: grave Justification: renders package unusable Dear Maintainer, Been using this kind of call against a Jessie install of this package for years: java -jar /usr/share/java/batik-rasterizer.jar -m image/png -scriptSecurityOff -w 1920 /tmp/ramdisk/svgproc-b83e35c457f48904da8a39a01d230d48.svg After upgrading system to bullseye, the same call produces this error: Error: Could not find or load main class org.apache.batik.apps.rasterizer.Main Caused by: java.lang.ClassNotFoundException: org.apache.batik.apps.rasterizer.Main From what I can tell, this was repackaged from having the actual code inside to the jar to being references to other jars. However it looks as if all of the manifests now have a "lib/" prefixed to the classpaths and this causes java to fail at finding any usable source. As a test, I created a symlink called lib inside /usr/share/java/ that simply points back to the same directory. There were still some errors, but it looked like java could at least find some of the other jars it was looking at. This might turn out to be a repackaging problem since the source package on the Apache site does come with all the jars stored into a "lib" directory. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libbatik-java depends on: ii java-wrappers 0.3 ii libjaxp1.3-java 1.3.05-6 ii libxalan2-java2.7.2-4 ii libxml-commons-external-java 1.4.01-5 ii libxmlgraphics-commons-java 2.4-2~deb11u1 Versions of packages libbatik-java recommends: ii default-jre 2:1.11-72 Versions of packages libbatik-java suggests: ii librhino-java 1.7.7.2-3 -- no debconf information --- End Message --- --- Begin Message --- Source: batik Source-Version: 1.14-2 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of batik, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated batik 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: Mon, 18 Jul 2022 23:48:46 +0200 Source: batik Architecture: source Version: 1.14-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Pierre Gruet Closes: 1013281 Changes: batik (1.14-2) unstable; urgency=medium . * Team upload * Adding classpaths and main classes in the manifests of the built jars (Closes: #1013281) * Reworking debian/watch: - Raising its version to 4 - Using secure URI * Raising Standards version to 4.6.1 (no change) * Refreshing d/copyright * Getting rid of unneeded versioned dependencies in d/control . [ Andrius Merkys ] * Remove Onkar Shinde from the uploaders list per request. Thanks for your contributions. Checksums-Sha1: b38e7dd180953a9e1abc92754ae5be39a6d1741a 2127 batik_1.14-2.dsc 26608e9a415a33d8d81d5784a48730e01901dc6f 32832 batik_1.14-2.debian.tar.xz d9f532d36eefc57d7f9733da08b2e911c1d24be1 15001 batik_1.14-2_source.buildinfo Checksums-Sha256: a977fafc3939954602b700674c3ba8ff9336ffdfb94403c671006b5793a59c53 2127 batik_1.14-2.dsc 6e9bbbf6d26115ae21e45de815e1e43352489e4957d0cbd1ff259e6082105669 32832 batik_1.14-2.debian.tar.
Bug#1013281: libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main
Control: tags -1 pending Hello Brian, Thanks for the bug report. On Mon, 20 Jun 2022 10:25:33 -0500 Brian Blood wrote: > Package: libbatik-java > Version: 1.12-4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > > Been using this kind of call against a Jessie install of this package for years: > > java -jar /usr/share/java/batik-rasterizer.jar -m image/png -scriptSecurityOff -w 1920 /tmp/ramdisk/svgproc-b83e35c457f48904da8a39a01d230d48.svg > > > After upgrading system to bullseye, the same call produces this error: > > Error: Could not find or load main class org.apache.batik.apps.rasterizer.Main > Caused by: java.lang.ClassNotFoundException: org.apache.batik.apps.rasterizer.Main > We have two things here: - The org.apache.batik.apps.rasterizer.Main class has been moved to another jar: /usr/share/java/batik-svgrasterizer.jar; - Some Class-Path and Main-Class indications are missing in the jars we ship in libbatik-java. I believe your call would be OK right now if you tried rasterizer -m image/png -scriptSecurityOff -w 1920 /tmp/ramdisk/svgproc-b83e35c457f48904da8a39a01d230d48.svg rasterizer is a script lying in /usr/bin that we ship in libbatik-java. If you have to use a java -jar /usr/share/java/svgrasterizer.jar ... syntax, then it will be possible starting from version 1.14-2 that I am about to upload to unstable, and which will end up in bookworm soon. Please tell me if you need it in bullseye or if calling rasterizer ... is OK for you. Best regards, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main
Processing control commands: > tags -1 pending Bug #1013281 [libbatik-java] libbatik-java: Running rasterizer fails with inability to load main class org.apache.batik.apps.rasterizer.Main Added tag(s) pending. -- 1013281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015063: marked as done (stopt: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Mon, 18 Jul 2022 21:35:55 + with message-id and subject line Bug#1015063: fixed in stopt 5.1+dfsg-4 has caused the Debian Bug report #1015063, regarding stopt: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1015063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stopt Version: 5.1+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > 18: realValue 6.17011 interp 6.17092 > 18: SPARSE LOC CORREL 0.9 > 18: * > 18: realValue 6.17011 interp 6.16892 > 18: > 18: [1;32;49m*** No errors detected > 18: [0;39;49m > 86/88 Test #18: MyTestForGridAndRegressedValue . Passed 58.03 > sec > 35: 197.658632s wall, 288.17s user + 1.21s system = 289.38s CPU > (146.4%) > 35: 5.455737s wall, 24.17s user + 0.05s system = 24.22s CPU > (443.9%) > 35: valSimu 6.09393e+07 valueOptim 6.03449e+07 > 35: > 35: [1;32;49m*** No errors detected > 35: [0;39;49m > 87/88 Test #35: MyTestForGasStorageGlobal .. Passed 632.26 > sec > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2022/07/16/stopt_5.1+dfsg-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: stopt Source-Version: 5.1+dfsg-4 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of stopt, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated stopt 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: Mon, 18 Jul 2022 23:08:07 +0200 Source: stopt Architecture: source Version: 5.1+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Math Team Changed-By: Pierre Gruet Closes: 1015063 Changes: stopt (5.1+dfsg-4) unstable; urgency=medium . * Providing an empty override for dh_auto_test-indep so that tests are not run twice during a full build (Closes: #1015063) Checksums-Sha1: 78eb036ca6adecbf4c6ad9383a4400f7e921 3054 stopt_5.1+dfsg-4.dsc a491b67f94efe67bbc95743eaf39e735390dadb8 20608 stopt_5.1+dfsg-4.debian.tar.xz f21b4d1f10969d50eb4b3076d64df27c801e3c92 6164 stopt_5.1+dfsg-4_source.buildinfo Checksums-Sha256: 529f8c353e1f31dcce5251571d2ac75554a194ee4b20e3ffae31e7f51ffa5162 3054 stopt_5.1+dfsg-4.dsc 9bd55fcf93889de8ea4de4eb46efb16b04f541cf5be6b6024da537c12965f77c 20608 stopt_5.1+dfsg-4.debian.tar.xz ceb64668987f9034fa4dd95ae07e8754aab480464adb86819bdc78b9b1845954 6164 stopt_5.1+dfsg-4_source.buildinfo Files: 6ce4cec5cdbf01bfd7333d153057ddcd 3054 math optional stopt_5.1+dfsg-4.dsc 51583542ac21ebd3d410ba94b59e1348 20608 math optional stopt_5.1+dfsg-4.debian.tar.xz 49556c5317204d0c2b8104ba6bf3a815 6164 math optional stopt_5.1+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEM8soQxPpC9J9y0UjYAMWptwndHYFAmLVzPEACgkQYAMWptwn dHb77RAAml9c/vpjP1vsP+ckztLXNA4PM1QLJL
Bug#1013920: marked as done (rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
Your message dated Mon, 18 Jul 2022 22:48:23 +0200 with message-id <099e2ea5-c141-c46c-c537-9b47c67fd...@debian.org> and subject line has caused the Debian Bug report #1013920, regarding rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel") 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.) -- 1013920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely serious situation that exposes debian to a greater level of risk that was undergone for the last Mozilla-Foundation Trademark fiasco, iceweasel Rust's Trademark requirements are that "you must seek our explicit permission before distributing patches". Uses that require explicit approval Distributing a **MODIFIED VERSION** of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team. there are dozens of such patches and every single one of them, unless explicit permission has been sought, is a DIRECT Trademark violation https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/ the over-ride of the Trademark on "Free" software is Lawful and in this case makes rust (and cargo) non-free software. unlike the Iceweasel debacle, the linux kernel is upstream merging rust, potentially making the entire linux kernel critically dependent on a non-free compiler. there is the additional issue that although Debian might seek and be granted explicit permission for a Trademark License Grant to Distribute, that does not cover Derivatives, which would also need to explicitly seek their own permission https://www.debian.org/derivatives/ https://devuan.org this has been discussed that DFSG Guideline 8 is violated by even attempting to seek a License specific to Debian https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html this is an extremely serious situation that either requires pulling rust and cargo from debian or a rename of both rust and cargo exactly as was done with iceweasel. failure to do so is also extremely serious because Unlawful Distribution may still be considered grounds for financial compensation as well as a Legal Notice to Cease and Desist, and also to remove all public and private use of the Trademark from all Records. mailing lists, bugtracker, debian archives - everything. this one cannot be ignored. -- System Information: --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 36152--- End Message ---
Bug#1015284: haskell-githash FTBFS: error: Couldn't match expected type
Source: haskell-githash
Version: 0.1.4.0-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-githash&suite=sid
...
test/GitHashSpec.hs:14:21: error:
• Couldn't match expected type: Language.Haskell.TH.Syntax.Code
Language.Haskell.TH.Syntax.Q t0
with actual type: Language.Haskell.TH.Syntax.Q
(Language.Haskell.TH.Syntax.TExp (Either
String GitInfo))
• In the expression: tGitInfoCwdTry
In the Template Haskell splice $$tGitInfoCwdTry
In the expression: $$tGitInfoCwdTry
• Relevant bindings include
egi :: t0 (bound at test/GitHashSpec.hs:14:13)
|
14 | let egi = $$tGitInfoCwdTry
| ^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"build", "--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"build", "--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 642
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015281: haskell-vault FTBFS: Encountered missing or private dependencies: base >=4.5 && <4.15
Source: haskell-vault
Version: 0.3.1.4-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-vault&suite=sid
...
hlibrary.setup: Encountered missing or private dependencies:
base >=4.5 && <4.15
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 622
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015280: haskell-pipes-zlib FTBFS: error: Couldn't match type
Source: haskell-pipes-zlib
Version: 0.4.4.2-3
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-pipes-zlib&suite=sid
...
src/Pipes/Zlib.hs:81:13: error:
• Couldn't match type: forall x'1 x1.
Proxy x'1 x1 () B.ByteString m0 ()
with: Proxy x' x () B.ByteString m1 a0
Expected: Popper -> Proxy x' x () B.ByteString m1 a0
Actual: Popper -> Producer' B.ByteString m0 ()
• In the first argument of ‘(=<<)’, namely ‘fromPopper’
In a stmt of a 'do' block:
fromPopper =<< liftIO (feedInflate inf bs)
In the expression:
do fromPopper =<< liftIO (feedInflate inf bs)
flush inf
leftover <- liftIO $ getUnusedInflate inf
if B.null leftover then
go p' inf
else
return $ Left (yield leftover >> p')
• Relevant bindings include
p' :: Producer B.ByteString m1 b (bound at src/Pipes/Zlib.hs:80:21)
res :: Either b (B.ByteString, Producer B.ByteString m1 b)
(bound at src/Pipes/Zlib.hs:77:7)
p :: Producer B.ByteString m1 b (bound at src/Pipes/Zlib.hs:76:8)
go :: Producer B.ByteString m1 b
-> Inflate
-> Proxy
x'
x
()
B.ByteString
m1
(Either (Proxy X () () B.ByteString m1 b) b)
(bound at src/Pipes/Zlib.hs:76:5)
|
81 | fromPopper =<< liftIO (Z.feedInflate inf bs)
| ^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015274: haskell-cryptonite FTBFS: error: Variable not in scope
Source: haskell-cryptonite
Version: 0.26-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-cryptonite&suite=sid
...
Crypto/Number/Compat.hs:76:43: error:
• Variable not in scope:
powModSecInteger :: Integer -> Integer -> Integer -> Integer
• Perhaps you meant one of these:
‘gmpPowModSecInteger’ (line 76),
‘powModInteger’ (imported from GHC.Integer.GMP.Internals)
|
76 | gmpPowModSecInteger b e m = GmpSupported (powModSecInteger b e m)
|
Crypto/Number/Compat.hs:107:32: error:
Variable not in scope: nextPrimeInteger :: Integer -> Integer
|
107 | gmpNextPrime n = GmpSupported (nextPrimeInteger n)
|
Crypto/Number/Compat.hs:116:10: error:
• Variable not in scope:
testPrimeInteger :: Integer -> Int# -> Int#
• Perhaps you meant ‘testBitInteger’ (imported from
GHC.Integer.GMP.Internals)
|
116 | case testPrimeInteger n tries of
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1013275: marked as done (toil: FTBFS with Python 3.10 only)
Your message dated Mon, 18 Jul 2022 19:22:08 +
with message-id
and subject line Bug#1013275: fixed in toil 5.6.0-7
has caused the Debian Bug report #1013275,
regarding toil: FTBFS with Python 3.10 only
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.)
--
1013275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: toil
Version: 5.6.0-6
Severity: important
Tags: ftbfs
Hi Maintainer
Toil hardcodes python3.9 and will FTBFS when Python 3.10 is the only
supported Python version. I've copied what I hope is the relevant
part of the log below, which shows the python3.10 tests being
attempted with python3.9.
Regards
Graham
=== FAILURES ===
___ ToilDebugFileTest.testFetchJobStoreFiles ___
Traceback (most recent call last):
File "/<>/src/toil/test/utils/toilDebugTest.py", line
31, in setUp
subprocess.check_call([python,
os.path.abspath('src/toil/test/utils/ABCWorkflowDebug/debugWorkflow.py')])
File "/usr/lib/python3.10/subprocess.py", line 364, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python3.10/subprocess.py", line 345, in call
with Popen(*popenargs, **kwargs) as p:
File "/usr/lib/python3.10/subprocess.py", line 966, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.10/subprocess.py", line 1842, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'python3.9'
--- End Message ---
--- Begin Message ---
Source: toil
Source-Version: 5.6.0-7
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
toil, 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 1013...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated toil 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: Mon, 18 Jul 2022 17:39:37 +0200
Source: toil
Architecture: source
Version: 5.6.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 1013275
Changes:
toil (5.6.0-7) unstable; urgency=medium
.
* Team upload.
* Packaging update
* Standards-Version: 4.6.1 (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
* Drop unnecessary dependency on build-essential.
* Make sure the doc applies to Debian installations with Python3
* Update lintian-overrides
* Set python3.10 instead of python3.9 in setting_version.patch
Closes: #1013275
Checksums-Sha1:
79c30dbc91a521cdaf1b719b6a63931cf9a4fdfc 2522 toil_5.6.0-7.dsc
09f1c7feec436d082b44e24a5ca60efe76c668ce 15512 toil_5.6.0-7.debian.tar.xz
b9a90fc823ebfc17c49ae8f12f305cf290879def 10679 toil_5.6.0-7_amd64.buildinfo
Checksums-Sha256:
3f8b216e218f5930e9a5274e5ac7ce0c2e7f1e41a2ef5e4aaade491f31815778 2522
toil_5.6.0-7.dsc
e96b50e75828e45e161935a2e1340b27862f0894456a0dd143501a8358fd7058 15512
toil_5.6.0-7.debian.tar.xz
b9d3ead5723c95d11350e640a4d5c6404080987292ffbb56dc21eedd99a7ab09 10679
toil_5.6.0-7_amd64.buildinfo
Files:
ba8dc109e8ac385d1386dc82fac7cbee 2522 net optional toil_5.6.0-7.dsc
d22934b61fb6017f518d4fc272a42965 15512 net optional toil_5.6.0-7.debian.tar.xz
f90250a0a9d3ef54f48b7cc0c4db4509 10679 net optional
toil_5.6.0-7_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmLVr4ERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGMiA//SpU4HZpLD3Hl0wPWSWQiqMyTsvVhcTFt
13wMmN6YsX+DkaodsHvfTCrcS8Wl9S74QHbOCixTlxfw1ViKuSpgy2bK5Q/hajmO
WXWP6TT4NZj5m9Mjlsjb8yuWeBUXHyqOsvF5Qfe7W//EGJEvRLviC7DADkws6L8N
tQTi1roLG+an9wFuXtWiYfrdzURREk7lzGzQVawS7+ngfPe4aMURZpaxmG+XxrBf
6g02zvTXSru9IAnLV7JPd2tVKwt4G3zkDeuRW6zm4pKrTOQcr8yzPYcJTK6f+QQr
HoZ51jyD2rj0bFFU67XG39LVXQi16FNjmSbafveK5Q+X8tFRZOPV8JpmvAkNDsNq
NflQf9ZzEx8R0ah8j4fzqVqLoF0jqbOk8OCBduTLf0OiAMlffqFvM6qrEemhL0R7
1fey7a5GrObMgmUkWFDyB5F6Gn7Gd81zW46PvwJN8P51zadOx7x+cJhOsGPp39kZ
PFXkBYG60m+J3H8ZKIdCwnG5807Om
Processed: [bts-link] source package src:scikit-learn
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:scikit-learn > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1003165 (http://bugs.debian.org/1003165) > # Bug title: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, > ppc64el and s390x > # * https://github.com/scikit-learn/scikit-learn/issues/22503 > # * remote status changed: open -> closed > # * closed upstream > tags 1003165 + fixed-upstream Bug #1003165 [src:scikit-learn] scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x Added tag(s) fixed-upstream. > usertags 1003165 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1003165 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015052: marked as done (borgbackup: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 18 Jul 2022 17:49:11 + with message-id and subject line Bug#1015052: fixed in borgbackup 1.2.1-2 has caused the Debian Bug report #1015052, regarding borgbackup: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015052 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: borgbackup Version: 1.2.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_clean > # make sure system libraries are used > find . -name blake2.h -delete > find . -name lz4.h -delete > find . -name zstd.h -delete > find . -name xxhash.h -delete > find . -name xxhash.c -delete > make[1]: Leaving directory '/<>' > dpkg-source -b . > dpkg-source: warning: cannot import key in > borgbackup-1.2.1/debian/upstream/signing-key.asc since GnuPG is not installed > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building borgbackup using existing > ./borgbackup_1.2.1.orig.tar.gz > dpkg-source: info: building borgbackup using existing > ./borgbackup_1.2.1.orig.tar.gz.asc > gpgv: Signature made Sun Jun 5 21:37:21 2022 UTC > gpgv:using RSA key 2F81AFFBAB04E11FE8EE65D4243ACFA951F78E01 > gpgv:issuer "t...@waldmann-edv.de" > gpgv: Can't check signature: No public key > dpkg-source: warning: cannot verify signature > ./borgbackup_1.2.1.orig.tar.gz.asc > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/xxh64/xxhash.h, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/xxh64/xxhash.c, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/zstd/lib/zstd.h, use --include-removal to override > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/zstd/lib/common/xxhash.h, use --include-removal to > override > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/zstd/lib/common/xxhash.c, use --include-removal to > override > dpkg-source: warning: ignoring deletion of file > src/borg/algorithms/lz4/lib/lz4.h, use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > borgbackup-1.2.1/src/borg/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/borgbackup_1.2.1-1.diff.xvcyvd > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:41:38Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/borgbackup_1.2.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: borgbackup Source-Version: 1.2.1-2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of borgbackup, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if app
Processed: [bts-link] source package gitlab
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package gitlab > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #995073 (http://bugs.debian.org/995073) > # Bug title: gitlab: yarnpkg fails with error An unexpected error occurred: > "Release not found: 2.4.2". > # * https://github.com/yarnpkg/berry/issues/3496 > # * remote status changed: open -> closed > # * closed upstream > tags 995073 + fixed-upstream Bug #995073 [gitlab] gitlab: yarnpkg fails with error An unexpected error occurred: "Release not found: 2.4.2". Added tag(s) fixed-upstream. > usertags 995073 - status-open Usertags were: status-open. There are now no usertags set. > usertags 995073 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 995073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ruby-jmespath
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-jmespath > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1014807 (http://bugs.debian.org/1014807) > # Bug title: ruby-jmespath: CVE-2022-32511 > # * https://github.com/jmespath/jmespath.rb/pull/55 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1014807 + fixed-upstream Bug #1014807 [src:ruby-jmespath] ruby-jmespath: CVE-2022-32511 Added tag(s) fixed-upstream. > usertags 1014807 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014010: marked as done (haskell-ghc-event FTBFS: Encountered missing or private dependencies: base >=4.7 && <4.15)
Your message dated Mon, 18 Jul 2022 16:49:47 +
with message-id
and subject line Bug#1014010: fixed in haskell-ghc-events 0.17.0.3-1
has caused the Debian Bug report #1014010,
regarding haskell-ghc-event FTBFS: Encountered missing or private dependencies:
base >=4.7 && <4.15
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.)
--
1014010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-ghc-events
Version: 0.13.0-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-ghc-events
...
hlibrary.setup: Encountered missing or private dependencies:
base >=4.7 && <4.15
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 620
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: haskell-ghc-events
Source-Version: 0.17.0.3-1
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
haskell-ghc-events, 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 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated haskell-ghc-events
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: Mon, 18 Jul 2022 19:35:50 +0300
Source: haskell-ghc-events
Architecture: source
Version: 0.17.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Ilias Tsitsimpis
Closes: 1014010
Changes:
haskell-ghc-events (0.17.0.3-1) unstable; urgency=medium
.
* New upstream release (Closes: #1014010)
* Declare compliance with Debian policy 4.6.1
* Remove retired developer, Joachim Breitner, from Uploaders.
Checksums-Sha1:
fb9e26961f004e1d92c42304a66594c71238615b 2483 haskell-ghc-events_0.17.0.3-1.dsc
ae1b6ba5bf753e6cbe3c25ba2e77ce8566a57bcc 1498692
haskell-ghc-events_0.17.0.3.orig.tar.gz
1fe3f10881166a43140b577a1006054ba34f49ab 3908
haskell-ghc-events_0.17.0.3-1.debian.tar.xz
c72326a8e87b87c2e9dedb9be4605f408c07cae8 8612
haskell-ghc-events_0.17.0.3-1_amd64.buildinfo
Checksums-Sha256:
8ddbcb5f4ce5dc157ffef37376312b62b4a93d4afef4fed85607640a753e14e9 2483
haskell-ghc-events_0.17.0.3-1.dsc
bb8cd1998227a77d8874c2982fbf8e9ef210d80f7ae9c9bf3f6d90cdbce8a054 1498692
haskell-ghc-events_0.17.0.3.orig.tar.gz
71e131b6b0760ba8df56dab031ecc4695c1e2b62e47400a6ed60760e79eadd6b 3908
haskell-ghc-events_0.17.0.3-1.debian.tar.xz
d4ca3867fb3fe82ddb1d27b452ae1a29d41897be20a3a7e411ffaa99d09e3742 8612
haskell-ghc-events_0.17.0.3-1_amd64.buildinfo
Files:
2ef004394c8cb3831e727e55329591d9 2483 haskell optional
haskell-ghc-events_0.17.0.3-1.dsc
ac11ae399d0bdee0160008b7396dc12b 1498692 haskell optional
haskell-ghc-events_0.17.0.3.orig.tar.gz
e0d64132ee5e654625bfb293e83f2918 3908 haskell optional
haskell-ghc-events_0.17.0.3-1.debian.tar.xz
3f2331a752b192b6cf3d3d580d325aff 8612 haskell optional
haskell-ghc-events_0.17.0.3-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmLVjH0UHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDxOtQ//eUZCfXACg9jo4+Kssj4B143dd7wQ
JSBVSACZ54XD6PlYEjFb4w0SqT580J/OBisE4tyvr28/BFb/EPoXNg4OIqza6hxi
UArSx98GXZyxr1NGy910ZFAWKcnMNk2zyolRiCoSrsB9F5p8D2iCAK8/c4yKgSoq
bdWbdMsIQ92mkX+XRepsApn
Bug#1014011: marked as done (haskell-topograph FTBFS: Encountered missing or private dependencies: base >=4.6 && <4.15)
Your message dated Mon, 18 Jul 2022 16:37:49 +
with message-id
and subject line Bug#1014011: fixed in haskell-topograph 1.0.0.1-2
has caused the Debian Bug report #1014011,
regarding haskell-topograph FTBFS: Encountered missing or private dependencies:
base >=4.6 && <4.15
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.)
--
1014011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-topograph
Version: 1.0.0.1-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-topograph
...
hlibrary.setup: Encountered missing or private dependencies:
base >=4.6 && <4.15
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 620
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: haskell-topograph
Source-Version: 1.0.0.1-2
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
haskell-topograph, 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 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated haskell-topograph
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: Mon, 18 Jul 2022 19:23:57 +0300
Source: haskell-topograph
Architecture: source
Version: 1.0.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Ilias Tsitsimpis
Closes: 1014011
Changes:
haskell-topograph (1.0.0.1-2) unstable; urgency=medium
.
* Declare compliance with Debian policy 4.6.1
* Patch for newer dependencies (Closes: #1014011)
Checksums-Sha1:
c6979ba1e92c10fa0e505cd5bce4a7bcaacb6cbd 2549 haskell-topograph_1.0.0.1-2.dsc
2070b63df0c731d38584f4633e8c46d3f646d332 2772
haskell-topograph_1.0.0.1-2.debian.tar.xz
40dedf15d6a97a2f396057f996834fe6438ac681 8810
haskell-topograph_1.0.0.1-2_amd64.buildinfo
Checksums-Sha256:
651981849933adabb62394d868b69cd2548288381500c37b17ded2c1c1922539 2549
haskell-topograph_1.0.0.1-2.dsc
aa0207e9e69bbeee12244b054ec501f7c92a5f9e0b0b2b759266169135a519c4 2772
haskell-topograph_1.0.0.1-2.debian.tar.xz
299eb2cdc2d7afc520c00dab2f66087f3d6d4a0a6d7baa0e942377ed5935f1e8 8810
haskell-topograph_1.0.0.1-2_amd64.buildinfo
Files:
852cd793c7445cbcdc427afb4f4e3024 2549 haskell optional
haskell-topograph_1.0.0.1-2.dsc
48dec04b96f627b5cf0454aebfcffce1 2772 haskell optional
haskell-topograph_1.0.0.1-2.debian.tar.xz
27b2139072c03f36a480c2e1d3da39f2 8810 haskell optional
haskell-topograph_1.0.0.1-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmLViYsUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDxeuBAArZ2yJwPAfn1MiJZbg7SQ5YHJsYYv
kmGMLzYQ1EGWrVwbmK3au/Kg1xxpp9TIFSqEPnJeYfMRkQRHbzMzvmaL6l0Acb99
UyhcDibDjWBlJsqcZJcdlYzA7kwPhB5ucKlrvJDwZGsenAwvft5gXP0X4HMlWO7+
xJMtILwdNoMgxH7yUIfUOSPbQ6gvGQR44IPJZubpmR/ImnY0V625I/y2KoFFni43
JmoucyQG5yXz4Xt+gEUq37cHMuYJaxykSKgkdRU2x/f7pPPgr6TG2ZxhZzyTI+nu
IRgxDwtsSfHvUEz16tmJCAm/XhuVyjZFQCShwV08vmN1SNnftjhGP0O/ra/owUFw
vrWIAIj+LrHwJL0Jlv7EnCzedGMyqS+X6/1GMunc5olK/QHKGBf9jIyki9asL1X1
na8rF/yBHYC0gdGW1yVqjZkDsVU/VMvoWQ0YWkcm+/eXhwc7I3qb3HQMJUOJO/Wr
yYBPY3UqMHdtb+HSto35Pipj5z/bKV05JY62FhTP0GTKS23YlT5htPNDr/vtodPD
0FCj66guYnqNMVdqo3xQV17uq
Bug#1014025: marked as done (haskell-blaze-textual FTBFS: error: Ambiguous occurrence ‘quotRemInteger’)
Your message dated Mon, 18 Jul 2022 16:34:26 +
with message-id
and subject line Bug#1014025: fixed in haskell-blaze-textual 0.2.2.1-1
has caused the Debian Bug report #1014025,
regarding haskell-blaze-textual FTBFS: error: Ambiguous occurrence
‘quotRemInteger’
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.)
--
1014025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-blaze-textual
Version: 0.2.1.0-9
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-blaze-textual&suite=sid
...
Blaze/Text/Int.hs:117:30: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at Blaze/Text/Int.hs:26:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
Blaze/Text/Int.hs:30:1-32
(and originally defined in ‘GHC.Integer’)
|
117 | splith p (n:ns) = case n `quotRemInteger` p of
|
Blaze/Text/Int.hs:122:30: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at Blaze/Text/Int.hs:26:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
Blaze/Text/Int.hs:30:1-32
(and originally defined in ‘GHC.Integer’)
|
122 | splitb p (n:ns) = case n `quotRemInteger` p of
|
Blaze/Text/Int.hs:138:22: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at Blaze/Text/Int.hs:26:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
Blaze/Text/Int.hs:30:1-32
(and originally defined in ‘GHC.Integer’)
|
138 | putH (n:ns) = case n `quotRemInteger` maxInt of
|
Blaze/Text/Int.hs:147:22: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at Blaze/Text/Int.hs:26:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
Blaze/Text/Int.hs:30:1-32
(and originally defined in ‘GHC.Integer’)
|
147 | putB (n:ns) = case n `quotRemInteger` maxInt of
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 707
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
--- End Message ---
--- Begin Message ---
Source: haskell-blaze-textual
Source-Version: 0.2.2.1-1
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
haskell-blaze-textual, 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 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated
haskell-blaze-textual 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: Mon, 18 Jul 2022 19:26:18 +0300
Source: haskell-blaze-textual
Architecture: source
Version: 0.2.2.1-1
Bug#1015268: olm: jasmine tests fail with nodejs 18
Source: olm Version: 3.2.11~dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, nodejs 18 exposes `global.fetch` API which makes some code believe it is sitting in a real browser. olm test fails because of that. A workaround is to invoke it with NODE_OPTIONS="--no-experimental-fetch" jasmine --config=test/jasmine.json Jérémy -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1015260: nqc: Get "Inappropriate ioctl for device" when trying to "nqc -firmware firm0332.lgo"
Package: nqc Version: 3.1.r6-7 Severity: grave Justification: renders package unusable X-Debbugs-Cc: s.achte...@rug.nl Compiling works fine, but code cannot be downloaded to the RCX 2.0 via the device /dev/usb/legousbtower0. stty also gives: stty: /dev/usb/legousbtower0: Inappropriate ioctl for device -- System Information: Debian Release: 11.4 APT prefers stable APT policy: (990, 'stable'), (600, 'unstable'), (500, 'stable-security'), (400, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nqc depends on: ii libc62.33-8 ii libgcc-s1 [libgcc1] 10.2.1-6 ii libstdc++6 10.2.1-6 nqc recommends no packages. nqc suggests no packages. -- no debconf information
Bug#1011734: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(@cert_with_extensions.extensions["authorityKeyIdentifier"]).to eq(expected_authorityKeyIdentifier)
Package: ruby-certificate-authority Followup-For: Bug #1011734 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch Control: tags -1 patch Hi, This was caused by a string format change in openssl >= 3.0. I created an upstream issue with more information [1]. In Ubuntu, we applied this patch to resolve the FTBFS: * debian/patches/0004-remove-keyid-prefix-from-test-string.patch: Remove 'keyid:' prefix from test string to fix build with openssl >= 3.0. (LP: #1981458) Thanks, Nick [1] https://github.com/cchandler/certificate_authority/issues/62 diff -Nru ruby-certificate-authority-1.0.0/debian/patches/0004-remove-keyid-prefix-from-test-string.patch ruby-certificate-authority-1.0.0/debian/patches/0004-remove-keyid-prefix-from-test-string.patch --- ruby-certificate-authority-1.0.0/debian/patches/0004-remove-keyid-prefix-from-test-string.patch 1969-12-31 19:00:00.0 -0500 +++ ruby-certificate-authority-1.0.0/debian/patches/0004-remove-keyid-prefix-from-test-string.patch 2022-07-12 11:00:53.0 -0400 @@ -0,0 +1,21 @@ +Description: Remove 'keyid:' prefix from x509 v3 authorityKeyIdentifier test + This test case does a simple check for the expected authorityKeyIdentifier value + on a certificate, which includes a 'keyid:' prefix. This prefix was removed in + OpenSSL 3.0, which causes this test case to fail. Just remove the prefix from the + expected string to fix the test. +Author: Nick Rosbrook +Bug: https://github.com/cchandler/certificate_authority/issues/62 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ruby-certificate-authority/+bug/1981458 +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011734 +Last-Update: 2022-07-12 +--- a/spec/units/certificate_spec.rb b/spec/units/certificate_spec.rb +@@ -423,7 +423,7 @@ + expect(@cert_with_extensions.extensions["subjectKeyIdentifier"]).to eq(expected_subjectKeyIdentifier) + + expected_authorityKeyIdentifier = CertificateAuthority::Extensions::AuthorityKeyIdentifier.new +- expected_authorityKeyIdentifier.identifier = "keyid:4C:58:CB:25:F0:41:4F:52:F4:28:C8:81:43:9B:A6:A8:A0:E6:92:E5" ++ expected_authorityKeyIdentifier.identifier = "4C:58:CB:25:F0:41:4F:52:F4:28:C8:81:43:9B:A6:A8:A0:E6:92:E5" + expect(@cert_with_extensions.extensions["authorityKeyIdentifier"]).to eq(expected_authorityKeyIdentifier) + + expected_authorityInfoAccess = CertificateAuthority::Extensions::AuthorityInfoAccess.new diff -Nru ruby-certificate-authority-1.0.0/debian/patches/series ruby-certificate-authority-1.0.0/debian/patches/series --- ruby-certificate-authority-1.0.0/debian/patches/series 2022-02-20 17:24:24.0 -0500 +++ ruby-certificate-authority-1.0.0/debian/patches/series 2022-07-12 11:00:53.0 -0400 @@ -1,3 +1,4 @@ 0001-Build-a-string-config-for-OpenSSL-Config-as-opposed-.patch 0002-gemspec-don-t-use-git-to-get-list-of-files.patch 0003-gemspec-don-t-load-file-from-lib-explicitly.patch +0004-remove-keyid-prefix-from-test-string.patch
Processed: Re: ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(@cert_with_extensions.extensions["authorityKeyIdentifier"]).to eq(expected_authorityKeyIdentifier)
Processing control commands: > tags -1 patch Bug #1011734 [src:ruby-certificate-authority] ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(@cert_with_extensions.extensions["authorityKeyIdentifier"]).to eq(expected_authorityKeyIdentifier) Added tag(s) patch. -- 1011734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015146: marked as done (rust-cbindgen_0.23.0-1~deb10u1_s390x-buildd.changes REJECTED)
Your message dated Mon, 18 Jul 2022 14:32:35 + with message-id and subject line Bug#1015146: fixed in rust-cbindgen 0.23.0-1~deb10u2 has caused the Debian Bug report #1015146, regarding rust-cbindgen_0.23.0-1~deb10u1_s390x-buildd.changes REJECTED 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.) -- 1015146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-cbindgen Version: 0.23.0-1~deb10u1 Severity: serious X-Debbugs-Cc: po...@debian.org On 2022-07-16 15:34, Debian FTP Masters wrote: > > > cbindgen_0.23.0-1~deb10u1_s390x.deb: has 1 file(s) with a timestamp too far > in the past: > usr/share/doc/cbindgen/changelog.gz (Thu Nov 29 21:33:09 1973) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rust-cbindgen Source-Version: 0.23.0-1~deb10u2 Done: Emilio Pozuelo Monfort We believe that the bug you reported is fixed in the latest version of rust-cbindgen, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emilio Pozuelo Monfort (supplier of updated rust-cbindgen 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: Mon, 18 Jul 2022 10:24:11 +0200 Source: rust-cbindgen Architecture: source Version: 0.23.0-1~deb10u2 Distribution: buster Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Emilio Pozuelo Monfort Closes: 1015146 Changes: rust-cbindgen (0.23.0-1~deb10u2) buster; urgency=medium . * Use override_ target instead of execute_after_, the latter is not supported in buster's debhelper. This fixes files with too old timestamps. Closes: #1015146. Checksums-Sha1: ba0f6d2f187da903110f224a67c0ddaa704aa3f7 2224 rust-cbindgen_0.23.0-1~deb10u2.dsc 09ba3b08ca7e4ef0241a3319237a2311a4239671 129761 rust-cbindgen_0.23.0.orig.tar.gz d03e2c253d799066fa09a73390b11190e9d65277 2315632 rust-cbindgen_0.23.0-1~deb10u2.debian.tar.xz e15bd4f8bd85aa16599e1603fe32c04bc0969dfa 5825 rust-cbindgen_0.23.0-1~deb10u2_source.buildinfo Checksums-Sha256: 6977b62fde59fabb2e16aff7648ba662d106a36278eef1e9d3c4903e58947898 2224 rust-cbindgen_0.23.0-1~deb10u2.dsc db3d1e30e7faf7e3fe375e058109e3d32380989b01d8f9ca5861b30a7357ef21 129761 rust-cbindgen_0.23.0.orig.tar.gz aba61d99a9d850772c9945425a89744ebbb43bf0cfc813f34e343f968c145db2 2315632 rust-cbindgen_0.23.0-1~deb10u2.debian.tar.xz 21fb8d641b8e688a7ad529c94a4b12f32c02e765bb18280420c4c849528df896 5825 rust-cbindgen_0.23.0-1~deb10u2_source.buildinfo Files: 90fba3ba28c78ad3c8ba5282d32af2c7 2224 utils optional rust-cbindgen_0.23.0-1~deb10u2.dsc a651b2d3e93c0d88b1b79c96b792d63d 129761 utils optional rust-cbindgen_0.23.0.orig.tar.gz dbcce6bbdd231528defc3777b0ed707e 2315632 utils optional rust-cbindgen_0.23.0-1~deb10u2.debian.tar.xz 505494b93157c646abb3e94af9262a8c 5825 utils optional rust-cbindgen_0.23.0-1~deb10u2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAmLVHWkACgkQnUbEiOQ2 gwKoNg//U+zwOJYs2jBNqYfiZJT3NjsYAzDkrMpAJuBudB2AZfs6psCCe4nTxUTG iJ2OkuwFoK206QQQjWOPAq1zRZOli/3oZlOWsHVs/s3SpgrnMrGmGCEg7c0NJhdB udah9JhBWukVlot44/BeRsc6ClOL0QWA5yLDyPt5CyViNH6VcoLs9IJm/YmD9vl3 74eDNQy1KHZJcyvWBn2mN/f1mIl3ypeYipc+pluezxHSILlqspL5PTyPI//bK6oz s76g6PQjl3wTbFSxgIVd8p7tetvCk8IdDIw4LNUGk00634kdG+gc3MxsoP6PgGUv SC5jVwmnYygrRVO08xaKl1LAaqn86/4nE+rL2M4amgcZ/VeQBmzFP5FYX72f3QOU m9j8Jd36GaQ2oeucmrFPyNTpp2/2m3PmLak6dPzP3OLzjU0eqYMzTs1NaDxy1urW hPovu3LXCG25dLaRrF21nf1LxgZhmPWrtz2ZEm95m+TtfOls65Tclev2v1Aw+36J N6ND0fQ75jeODXVT1kGRG/+mVjQwUKVxcSomHRrUBvRrRrkW9lbiXow7007S3t7h UxtlzmZCdYf+TxlNlWPOOZGo8F8wdhr6NvLCGDx6xpcA19Tm9JdOLwxJfPrl2qCw aXXdvXl890SGLRHObzAp/IwbNqNZ+8Ii5AL3E9GMqgUZhmjvLbo= =Nacb -END PGP SIGNATURE End Message ---
Processed: lower severity of #1014435
Processing commands for cont...@bugs.debian.org: > package libvirt-daemon-system-systemd Limiting to bugs with field 'package' containing at least one of 'libvirt-daemon-system-systemd' Limit currently set to 'package':'libvirt-daemon-system-systemd' > severity 1014435 important Bug #1014435 [libvirt-daemon-system-systemd] libvirt-daemon-system-systemd: virbr0 default fails to connect Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014435: libvirt-daemon-system-systemd: virbr0 default fails to connect
On Tue, Jul 05, 2022 at 08:06:44PM -0500, Tim McConnell wrote: > Package: libvirt-daemon-system-systemd > Version: 8.4.0-1 > Severity: grave > Justification: renders package unusable This doesn't feel right. According to [1], "grave" means that the bug makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package The fact that a single libvirt feature (the default network) has been reported as not working by a single person (I just tested it on my machine and it seems okay) doesn't match the description of the severity IMO. I'll lower it to "important", which indicates a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone and seems to describe the actual impact much more accurately. > Virbr0 won't connect to external network.It did once, I was able to install > Debian from a net install image. Now it tells me the Virtual Machine can't > connect. Please be more specific. Does the VM fail to start? If so, what is the exact error message? Or does the VM boot up, but the guest OS is unable to connect to the Internet? Can the guest OS ping the host, or does that not work either? If you try performing another installation, does that work? [1] https://www.debian.org/Bugs/Developer#severities -- Andrea Bolognani Resistance is futile, you will be garbage collected. signature.asc Description: PGP signature
Bug#1004508: ocrad: autopkgtest regression: undefined reference to `png_g*
In order to avoid future problems with compiling `ocradcheck`, would it be better to build an additional binary package (ocradcheck or ocrad-test) which can be installed during autopkgtest? This seems less error-prone. -Nick
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
ah! some fascinating news (from another discussion) pulled up the fact that ADA converted to a Certification Mark, back in 1987 http://archive.adaic.com/pol-hist/policy/trademrk.txt In order to be a validated Ada compiler, a compiler must pass an extensive suite of programs called the Ada Compiler Validation Capability (ACVC). The AJPO has adopted a certification mark to show that a compiler has passed the ACVC and is a validated compiler or a compiler derived from a validated base compiler as defined in the Ada Compiler Validations Procedures and Guidelines (version 1.1 of which was issued in January 1987). The certification mark may also be used on certain literature accompanying or documenting a validated compiler. Information concerning the proper use of the certification mark was distributed to interested parties during the summer of 1987. *that* is what the Rust Foundation *should* be doing. messing about prohibiting patching is going to end in tears. if they instead state, "You must run the Test Suite (unmodified, as provided by us), and it the results are a 100% pass then you're free and clear to distribute without limitation [and use the word "rust"] in the distributed package" then *that* would solve all of the problems. unfortunately, as i said in comment #40 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920#40 if the Rust Foundation tries right now to convert the Trademark into a Certification Mark it will be DENIED because they are selling product (hats, T-shirts) and a Certification Mark Holder cannot compete with its Licensees. if they stop selling T-shirts and Merchandise and give assurances to the Trademark Office that they will not do so then they should be ok to convert to a Certification Mark. l.
Processed: Re: Bug#1015191: vice: FTBFS against ffmpeg 5
Processing control commands: > severity -1 important Bug #1015191 [vice] vice: FTBFS against ffmpeg 5 Severity set to 'important' from 'serious' -- 1015191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015191: vice: FTBFS against ffmpeg 5
Control: severity -1 important Hi Andreas, On Sun, Jul 17, 2022 at 2:39 PM Andreas Beckmann wrote: > vice FTBFS against ffmpeg 5: Indeed. Upstream says there will be no support for two FFmpeg releases. Until 4.3.x+ is alive and well, there will be no 5.y support. Thus already uploaded a vice update which disables FFmpeg support, not to fail with 5.y until then. I let this bug report open until the support lands for that. Regards, Laszlo/GCS
Bug#1015253: haskell-misfortune FTBFS: No instance for (mtl-2.2.2:Control.Monad.Reader.Class.MonadReader g0 IO) arising from a use of ‘sample’
Source: haskell-misfortune
Version: 0.1.1.2-10
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-misfortune&suite=sid
...
src/Data/Fortune.hs:238:10: error:
• No instance for (mtl-2.2.2:Control.Monad.Reader.Class.MonadReader
g0 IO)
arising from a use of ‘sample’
• In a stmt of a 'do' block: i <- sample (uniform 0 (n - 1))
In the expression:
do f <- sample file
n <- getNumFortunes f
i <- sample (uniform 0 (n - 1))
T.unpack <$> getFortune f i
In an equation for ‘randomFortuneFromRandomFile’:
randomFortuneFromRandomFile file
= do f <- sample file
n <- getNumFortunes f
i <- sample (uniform 0 (n - 1))
|
238 | i <- sample (uniform 0 (n-1))
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015252: haskell-hmatrix FTBFS: Couldn't match expected type ‘Int’ with actual type ‘CSR -> Int’
Source: haskell-hmatrix
Version: 0.20.0.0-1
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-hmatrix&suite=sid
...
src/Internal/Sparse.hs:125:24: error:
• Couldn't match expected type ‘Int’ with actual type ‘CSR -> Int’
• Probable cause: ‘nRows’ is applied to too few arguments
In the ‘nRows’ field of a record
In the expression: SparseR {..}
In an equation for ‘fromCSR’:
fromCSR csr
= SparseR {..}
where
gmCSR @ CSR {..} = csr
nRows = csrNRows
nCols = csrNCols
|
125 | fromCSR csr = SparseR {..}
|^^
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015251: haskell-formatting FTBFS: Ambiguous occurrence ‘quotRemInteger’
Source: haskell-formatting
Version: 6.3.7-2
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-formatting&suite=sid
...
src/Data/Text/Format/Int.hs:121:30: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at src/Data/Text/Format/Int.hs:27:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
src/Data/Text/Format/Int.hs:34:1-32
(and originally defined in ‘GHC.Integer’)
|
121 | splith p (n:ns) = case n `quotRemInteger` p of
|
src/Data/Text/Format/Int.hs:126:30: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at src/Data/Text/Format/Int.hs:27:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
src/Data/Text/Format/Int.hs:34:1-32
(and originally defined in ‘GHC.Integer’)
|
126 | splitb p (n:ns) = case n `quotRemInteger` p of
|
src/Data/Text/Format/Int.hs:144:26: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at src/Data/Text/Format/Int.hs:27:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
src/Data/Text/Format/Int.hs:34:1-32
(and originally defined in ‘GHC.Integer’)
|
144 | putH (n:ns) = case n `quotRemInteger` maxInt of
|
src/Data/Text/Format/Int.hs:152:26: error:
Ambiguous occurrence ‘quotRemInteger’
It could refer to
either ‘GHC.Num.quotRemInteger’,
imported from ‘GHC.Num’ at src/Data/Text/Format/Int.hs:27:17-30
or ‘GHC.Integer.GMP.Internals.quotRemInteger’,
imported from ‘GHC.Integer.GMP.Internals’ at
src/Data/Text/Format/Int.hs:34:1-32
(and originally defined in ‘GHC.Integer’)
|
152 | putB (n:ns) = case n `quotRemInteger` maxInt of
|
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"haddock", "--builddir=dist-ghc", "--with-haddock=/usr/bin/haddock",
"--with-ghc=ghc", "--verbose=2", "--html", "--hoogle", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 709
Debian::Debhelper::Buildsystem::Haskell::Recipes::haddock_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1015242: gcc Trademark violation on the horizon
Control: severity -1 wishlist if it's on the horizon, it's clearly not release-critical now.
Processed: Re: gcc Trademark violation on the horizon
Processing control commands: > severity -1 wishlist Bug #1015242 [gcc] gcc Trademark violation on the horizon Severity set to 'wishlist' from 'serious' -- 1015242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015249: haskell-boomerang FTBFS: Encountered missing or private dependencies: template-haskell <2.17
Source: haskell-boomerang
Version: 1.4.6-2
Severity: serious
Tags: ftbfs bookworm sid
https://buildd.debian.org/status/package.php?p=haskell-boomerang&suite=sid
...
hlibrary.setup: Encountered missing or private dependencies:
template-haskell <2.17
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"configure", "--ghc", "-v2", "--package-db=/var/lib/ghc/package.conf.d",
"--prefix=/usr", "--libdir=/usr/lib/haskell-packages/ghc/lib",
"--libexecdir=/usr/lib", ...) called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 622
Debian::Debhelper::Buildsystem::Haskell::Recipes::configure_recipe()
called at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Bug#1013916: marked as done (missing dependency)
Your message dated Mon, 18 Jul 2022 11:04:05 + with message-id and subject line Bug#1013916: fixed in cron 3.0pl1-148 has caused the Debian Bug report #1013916, regarding missing dependency 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.) -- 1013916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron-daemon-common Version: 3.0pl1-144 This package seems to have a dependency fault in that it needs "addgroup" as part of its postinst but doesn't declare a dependency on the package "adduser" that provides "addgroup". This e.g. causes debootstrap to fail in some configurations: # debootstrap --variant=minbase --include=cron --exclude=apt bookworm /trial http://deb.debian.org/debian regards, Ralph. --- End Message --- --- Begin Message --- Source: cron Source-Version: 3.0pl1-148 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of cron, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated cron 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: Mon, 18 Jul 2022 12:52:27 +0200 Source: cron Architecture: source Version: 3.0pl1-148 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Georges Khaznadar Closes: 1013916 Changes: cron (3.0pl1-148) unstable; urgency=medium . * moved the dependency on adduser from packahe cron to package cron-daemon-common. Closes: #1013916; thanks, Mark Hindley! Checksums-Sha1: 75278cea5bdecd282582dd0cede50c1d25dfd7da 2129 cron_3.0pl1-148.dsc 08f632c7eb4176564114cda667dac65ffc27b039 111568 cron_3.0pl1-148.debian.tar.xz ead2123570dfbd59ff88c20f19bc5833050cc45f 5898 cron_3.0pl1-148_source.buildinfo Checksums-Sha256: c47ea6429d3873edcf6a5746fef48cbb4056eaced05bafa1e4136095933dcce4 2129 cron_3.0pl1-148.dsc fe9024f9afd7f560c265d93b4622688fd0e91f81e0bcb2d78403e5ef37e2f25c 111568 cron_3.0pl1-148.debian.tar.xz dc71bb144391af0c7ee134411b9eaf6f86e39dcbdd009361bc933926319e0f84 5898 cron_3.0pl1-148_source.buildinfo Files: 9a763584ed987ef17d4b3f79a26df2d2 2129 admin important cron_3.0pl1-148.dsc 450733abada4a5193715b9a41efe5858 111568 admin important cron_3.0pl1-148.debian.tar.xz fd8fc828117f61126e9ff2c12ef2dfb1 5898 admin important cron_3.0pl1-148_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmLVO80UHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnhFhAAlDz3dn0k/D0KR8pyaADMha4zEymE u/VPhDHhuDbS2ByQrBRLgA4HyT7ZyeMeqZfZNsiJxAxcnjCK4zMvH66dh0MJ06Q3 4IuFcClwR2/+W7w/c4qcCeWxgvmAvnAJjMHpVLuW9KVpiDNwfeM0Ro+CJSmc9S6T CzE1OD3IyYdUCBBVNPNLPsVsNhaKd9SEI3kPFU4SOWZfvwpwudsVx42qp4x1UFZG 2R3e6sXoHVc1a2by7QpCro/LKjIFKu8NWwYt+klcwhM/cmgXJt9jU4716+M7cwnv FswUX+B89TPusCnbtIVWf20oTtVyMMrHelKPoGDaAMVSmmrEtGDjXj8rK/zbrfo3 LAtr7JAgCj0VJNqe3lWIo2COCzjxArQb04MVGBKBMq5nrr3C6eV9+NToCE13ZE+P bYjROmSgoYTRGnHJ7W1SVq5ZmeuT4l0dvj7nEF9JbIMmKOtelupAcgEcRty4vHNr OmHqlWjYuadtgf0iSczmu+/8dMehLnuENgvUPMPqhKF1pScT+bV11njZHdrV0TVQ wAEXaP4mweOR2SNTozKtmCW5lgDZ/EU103Cid33Lmk0gVxnjl8d4mVUqa07EL3m6 Nu1ppoCUi3H9/vzSR5KanNmrJbstyEgB0OZr2Vu0eudh6slZEaC+k9pDdI2Aydm+ EUV47cPCrYO1HLk= =DVEy -END PGP SIGNATURE End Message ---
Bug#1015077: marked as done (python-asdf: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Mon, 18 Jul 2022 10:34:16 + with message-id and subject line Bug#1015077: fixed in python-asdf 2.12.0-2 has caused the Debian Bug report #1015077, regarding python-asdf: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 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.) -- 1015077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-asdf Version: 2.12.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3,sphinxdoc --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of > dash-separated 'upload-dir' will not be supported in future versions. Please > use the underscore name 'upload_dir' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of > dash-separated 'show-response' will not be supported in future versions. > Please use the underscore name 'show_response' instead > warnings.warn( > running clean > removing '/<>/.pybuild/cpython3_3.9_asdf/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of > dash-separated 'upload-dir' will not be supported in future versions. Please > use the underscore name 'upload_dir' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of > dash-separated 'show-response' will not be supported in future versions. > Please use the underscore name 'show_response' instead > warnings.warn( > running clean > removing '/<>/.pybuild/cpython3_3.10_asdf/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building python-asdf using existing > ./python-asdf_2.12.0.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: warning: ignoring deletion of directory asdf.egg-info > dpkg-source: warning: ignoring deletion of file > asdf.egg-info/dependency_links.txt, use --include-removal to override > dpkg-source: warning: ignoring deletion of file asdf.egg-info/top_level.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file asdf.egg-info/SOURCES.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file asdf.egg-info/PKG-INFO, use > --include-removal to override > dpkg-source: warning: ignoring deletion of file asdf.egg-info/requires.txt, > use --include-removal to override > dpkg-source: warning: ignoring deletion of file > asdf.egg-info/entry_points.txt, use --include-removal to override > dpkg-source: info: local changes detected, the modified files are: > python-asdf-2.12.0/asdf/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/python-asdf_2.12.0-1.diff.tQuWhq > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:55:36Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/python-asdf_2.12.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You'
Processed: toil: FTBFS with Python 3.10 only
Processing control commands: > severity -1 serious Bug #1013275 [src:toil] toil: FTBFS with Python 3.10 only Severity set to 'serious' from 'important' -- 1013275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign to boost
Processing commands for cont...@bugs.debian.org: > reassign 1015095 libboost1.74-tools-dev Bug #1015095 [src:libzeep] libzeep: FTBFS: make[3]: *** [CMakeFiles/doc.dir/build.make:76: ../doc/html/index.html] Error 1 Bug reassigned from package 'src:libzeep' to 'libboost1.74-tools-dev'. No longer marked as found in versions libzeep/5.1.7-1. Ignoring request to alter fixed versions of bug #1015095 to the same values previously set > found 1015095 libboost1.74-tools-dev/1.74.0.3 Bug #1015095 [libboost1.74-tools-dev] libzeep: FTBFS: make[3]: *** [CMakeFiles/doc.dir/build.make:76: ../doc/html/index.html] Error 1 The source libboost1.74-tools-dev and version 1.74.0.3 do not appear to match any binary packages Marked as found in versions libboost1.74-tools-dev/1.74.0.3. > affects 1015095 libzeep Bug #1015095 [libboost1.74-tools-dev] libzeep: FTBFS: make[3]: *** [CMakeFiles/doc.dir/build.make:76: ../doc/html/index.html] Error 1 Added indication that 1015095 affects libzeep > End of message, stopping processing here. Please contact me if you need assistance. -- 1015095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003495: marked as done (gcc-xtensa-lx106: reproducible builds: embeds path to various binaries)
Your message dated Mon, 18 Jul 2022 10:18:55 + with message-id and subject line Bug#1003495: fixed in gcc-xtensa-lx106 10 has caused the Debian Bug report #1003495, regarding gcc-xtensa-lx106: reproducible builds: embeds path to various binaries 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.) -- 1003495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-xtensa-lx106 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: usrmerge shell X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The paths to various binaries are embedded which differs on a usrmerge vs. non-usrmerge system. https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/gcc-xtensa-lx106.html ./usr/lib/gcc/xtensa-lx106-elf/10.3.1/install-tools/fixincl /bin/sed vs. /usr/bin/sed ./usr/lib/gcc/xtensa-lx106-elf/10.3.1/install-tools/mkheaders for·shell·in·$CONFIG_SHELL·$SHELL·/bin/bash·/bin/sh·"";·do vs. for·shell·in·$CONFIG_SHELL·$SHELL·/bin/sh·/bin/sh·"";·do Patch attached which passes variables to configure to use the non-usrmerge locations, as usrmerge installations typically have compatibility symlinks, but not vice-versa. The patch also sets variables to ensure consistent values for bash, which can be triggered when /bin/sh points to bash. This patch alone does not fix all reproducibility issues (e.g. build paths, which are only tested on unstable and experimental), but it should build reproducibly in bookworm/testing once binutils-xtensa-lx106 is built with deterministic archives enabled: https://bugs.debian.org/1003494 Thanks for maintaining gcc-xtensa-lx106! live well, vagrant From cf21d21676939698399a9f8ee6b0048f9dbefc5b Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Tue, 11 Jan 2022 02:53:34 + Subject: [PATCH] debian/rules: Pass variables to configure to make the package build reproducibly regardless of usrmerge. The variables SED, SHELL, BASH and CONFIG_SHELL should all point to their non-usrmerge locations. https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html --- debian/rules | 4 1 file changed, 4 insertions(+) diff --git a/debian/rules b/debian/rules index eb94981..c9fae9a 100755 --- a/debian/rules +++ b/debian/rules @@ -80,6 +80,10 @@ configure_flags = \ --without-newlib \ "--with-pkgversion=$(deb_version)" \ --without-included-gettext \ + SED=/bin/sed \ + SHELL=/bin/sh \ + BASH=/bin/bash \ + CONFIG_SHELL=/bin/bash \ $(buildflags) \ $(target_tools) -- 2.30.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: gcc-xtensa-lx106 Source-Version: 10 Done: Jonathan McDowell We believe that the bug you reported is fixed in the latest version of gcc-xtensa-lx106, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan McDowell (supplier of updated gcc-xtensa-lx106 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: Mon, 18 Jul 2022 08:32:48 +0100 Source: gcc-xtensa-lx106 Architecture: source Version: 10 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Packaging Team Changed-By: Jonathan McDowell Closes: 961090 1003495 Changes: gcc-xtensa-lx106 (10) unstable; urgency=medium . * Enable D compiler. Thanks to Witold Baryluk. (Closes: #961090) * Update to GCC 11 * Fix compilation with usrmerge by forcibly configuring paths. Thanks to Vagrant Cascadian (Closes: #1003495) Checksums-Sha1: 32e27afdb8a2b5a66ec080b5052e09389fbe 1944 gcc-xtensa-lx106_10.dsc c1fb5ea6e8684b14a85a10e64f28e2dbcfac2379 8840 gcc-xtensa-lx106_10.tar.xz b0d74275321a89d69e79ef81e5520bc6974ae6f7 7815 gcc-xtensa-lx106_10_amd64.buildinfo Checksums-Sha256: 8250f04170280f94c7fd4fef0aedc469d3cd9a53213ed8e18ab36b9a09e63b59 1944 gcc-xtensa-lx106_10.dsc 15dc34de4e11ed4e0867512a2db2ef89ac9f7983b3d764fb6988c886511646f2 8840 gcc-xtensa-lx106_10.tar.xz 4310ba0101fbd51e24f1
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
On Mon, Jul 18, 2022 at 11:06 AM Sylvestre Ledru wrote: > > This bug is fixed. i can see that you believe that to be true, otherwise you would not have closed it. what i am upset by is that you did not consider my opinion or insight to be worth consulting. i am deeply offended by that. l.
Processed (with 5 errors): Re: Bug#1013920 closed by Sylvestre Ledru (Re: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation a
Processing commands for cont...@bugs.debian.org:
> reopen 1013920
Bug #1013920 {Done: Sylvestre Ledru } [rust-all]
rust-all: Debian violating Rust Trademark (as serious a situation as
"iceweasel")
Bug reopened
Ignoring request to alter fixed versions of bug #1013920 to the same values
previously set
> sorry, Sylvestre, if you could possibly wait, on something this serious,
Unknown command or malformed arguments to command.
> for a response as to whether the fix is valid, that will avoid me having
Unknown command or malformed arguments to command.
> to spend my time reopening the issue or creating a second bugreport.
Unknown command or malformed arguments to command.
> On Mon, Jul 18, 2022 at 10:21 AM Debian Bug Tracking System
Unknown command or malformed arguments to command.
> wrote:
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
1013920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
This bug is fixed. Please don't reopen it. We are both now compliant with the DFSG and the Rust trademark. I do understand that you feel differently but this worked well for years for Firefox and Thunderbird and Debian derivatives. This isn't a different situation. Regards, Sylvestre / / Le 18/07/2022 à 11:29, Luke Kenneth Casson Leighton a écrit : reopen 1013920 sorry, Sylvestre, if you could possibly wait, on something this serious, for a response as to whether the fix is valid, that will avoid me having to spend my time reopening the issue or creating a second bugreport. On Mon, Jul 18, 2022 at 10:21 AM Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the rust-all package: #1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel") It has been closed by Sylvestre Ledru. ___ Pkg-rust-maintainers mailing list pkg-rust-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Jul 18, 2022 at 10:16 AM Sylvestre Ledru wrote: > > Thanks for bringing it to our attention, I have consulted with the Rust > foundation, we have agreed a change, we think this change solves it. ah! we may have just had some cross-over. > See > https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ > for the updated policy. did you mean the sections "fixing local paths" (etc)? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920#60 no, that would not be sufficient. it still violates DFSG (most of it). there is also the issue that even placing a public copy of source code on a git repository also constitutes "Distribution". i gave some suggestions which would be much more reasonable (and general) already, they may have been missed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920#40 those much more general statements basically say "we trust you not to do any damage under our name" the new additions basically say: "you're clearly too stupid to be trusted so we're going to lock out your rights" it should therefore come as no surprise that trying to go in that direction would directly conflict with everything that DFSG strives towards. l.
Bug#1013920: closed by Sylvestre Ledru (Re: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
reopen 1013920 sorry, Sylvestre, if you could possibly wait, on something this serious, for a response as to whether the fix is valid, that will avoid me having to spend my time reopening the issue or creating a second bugreport. On Mon, Jul 18, 2022 at 10:21 AM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the rust-all package: > > #1013920: rust-all: Debian violating Rust Trademark (as serious a situation > as "iceweasel") > > It has been closed by Sylvestre Ledru .
Bug#1000916: marked as done (vboot-utils: Please upgrade to llvm-toolchain-12 or 13)
Your message dated Mon, 18 Jul 2022 09:36:20 + with message-id and subject line Bug#1000916: fixed in vboot-utils 0~R99-14469.B-2 has caused the Debian Bug report #1000916, regarding vboot-utils: Please upgrade to llvm-toolchain-12 or 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.) -- 1000916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000916 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vboot-utils Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -13 (or -12). Bookworm won't ship with llvm-toolchain-11 llvm-defaults is now pointing to -13. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: vboot-utils Source-Version: 0~R99-14469.B-2 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of vboot-utils, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sophie Brun (supplier of updated vboot-utils 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: Mon, 18 Jul 2022 11:08:11 +0200 Source: vboot-utils Architecture: source Version: 0~R99-14469.B-2 Distribution: unstable Urgency: medium Maintainer: Sophie Brun Changed-By: Sophie Brun Closes: 1000916 Changes: vboot-utils (0~R99-14469.B-2) unstable; urgency=medium . * Fix switch to llvm-toolchain-13: use libfuzzer-13-dev (Closes: #1000916) Checksums-Sha1: 060755b0e684d44aaf674e4a5c05c118cc92fa96 2383 vboot-utils_0~R99-14469.B-2.dsc 41a091d1085ffb064bbfc4442da61bd35358fefb 11212 vboot-utils_0~R99-14469.B-2.debian.tar.xz 33f8ae4c3fdcbb8753de3c9eeb4fdd2835e2c469 6572 vboot-utils_0~R99-14469.B-2_source.buildinfo Checksums-Sha256: 6a0e9d54d0a7f8c91129cbe5b25ef10aa38a966c1c31fb1d8e90ed870414a0be 2383 vboot-utils_0~R99-14469.B-2.dsc 5123ba09886e1e4ef7abbe9284bfe80657a15252df85f7a09a71f9cb4ca39fe2 11212 vboot-utils_0~R99-14469.B-2.debian.tar.xz 1944cb76780645b7cff896a2c79cc065d718ed8a1fd26c5b68fe69812fc040b2 6572 vboot-utils_0~R99-14469.B-2_source.buildinfo Files: f45ccbda84fd68301a01d81066849085 2383 admin optional vboot-utils_0~R99-14469.B-2.dsc 680f5906ad6130b823f2a47ff5601aaa 11212 admin optional vboot-utils_0~R99-14469.B-2.debian.tar.xz 1ac5af66a00a3090b54ed2ad68118038 6572 admin optional vboot-utils_0~R99-14469.B-2_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Signed by Sophie Brun iQIzBAEBCgAdFiEEOyG45orlwW+H9TItV5J4OyBv7jAFAmLVJV0ACgkQV5J4OyBv 7jCmVQ/+LSchjN4uFDda35sAt4vU3C2/OCpS9bZ+IDewMt27VWLEl6aq1VgkNp0A zMKe2TK0oHfNnhSKEkSocP1FnQ+QhjH3WAlWxh9UQ8kw6EmFt7bLaNsg8FkzMO2W o3K86czl1JvRFYUjuIQqDmZQhNU7Z5KHwsCf7+A3Dchv5xJYGLLbTq1mLN2cEHnm +CrJII+3PxACfhCuFqKHPkc/zxZKIhsAjVqzCRvsCNrqpEhowKV8CWgSEoWyVGLh yfOC7Esh+4xFbeOjUvCDAuRFei4QiS26618sYJVxDpzFT9iffikPTqjkCmdNnwXu 9L9qdPgZ5mu1yo6w7M7Lcuv10Vtj22hpfZ224uPqPCDSIEJj5UQlFimM1GqJqpAn Uz6R1S1o1RlxIUnSed/u8/ba11Mx3h3P+XQjfW/XOfLpqnmpq7PwecJ5VpU3+B5r nfygUVrpmf9rJiCFcUMC2of2cHUa9xRusv4JIkgS+Fvxj8UEIEZ0Q4U41Ln0O7fq r9IIFsyH11/xMmtL/+vFgE6IYrx0SeOf9YA3WzxMSQ5ZM9AA8Yj0ctcDE287qj+R 2KOyR5038207jRd5eER2usarCxSw5fAuT3OmudIleCqGNXT5FOtxNBxZtzLMm+VU mHXNJ2AmFqYeiDCLetBePah/bYNrO6e46md55ibWCLsOgXuUfEU= =5zzC -END PGP SIGNATURE End Message ---
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
i've opened up a second bug for gcc because it is also about to become affected, not in the same way, but in a worse way. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015242 whilst 50% of DFSG 2 is violated by the Rust Trademark (as it stands, with the new clauses), gcc is in an even worse situation because the Rust Trademark conficts directly with the GPL as well. this is a complex multi-faceted issue: please do not close the bugreport until all facets of the conflict brought to your attention have been resolved. or... you can... but that will force me into the position of re-raising another report, and i am too busy to do that, and you risk me giving up and not caring. l.
Bug#1013920: marked as done (rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))
Your message dated Mon, 18 Jul 2022 11:18:18 +0200 with message-id <4d5219fe-cc00-35aa-5373-44f990f3e...@debian.org> and subject line Re: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel") has caused the Debian Bug report #1013920, regarding rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel") 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.) -- 1013920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely serious situation that exposes debian to a greater level of risk that was undergone for the last Mozilla-Foundation Trademark fiasco, iceweasel Rust's Trademark requirements are that "you must seek our explicit permission before distributing patches". Uses that require explicit approval Distributing a **MODIFIED VERSION** of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team. there are dozens of such patches and every single one of them, unless explicit permission has been sought, is a DIRECT Trademark violation https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/ the over-ride of the Trademark on "Free" software is Lawful and in this case makes rust (and cargo) non-free software. unlike the Iceweasel debacle, the linux kernel is upstream merging rust, potentially making the entire linux kernel critically dependent on a non-free compiler. there is the additional issue that although Debian might seek and be granted explicit permission for a Trademark License Grant to Distribute, that does not cover Derivatives, which would also need to explicitly seek their own permission https://www.debian.org/derivatives/ https://devuan.org this has been discussed that DFSG Guideline 8 is violated by even attempting to seek a License specific to Debian https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html this is an extremely serious situation that either requires pulling rust and cargo from debian or a rename of both rust and cargo exactly as was done with iceweasel. failure to do so is also extremely serious because Unlawful Distribution may still be considered grounds for financial compensation as well as a Legal Notice to Cease and Desist, and also to remove all public and private use of the Trademark from all Records. mailing lists, bugtracker, debian archives - everything. this one cannot be ignored. -- System Information: --- End Message --- --- Begin Message --- fixed 1013920 thanks Le 27/06/2022 à 13:52, lkcl a écrit : Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely serious situation that exposes debian to a greater level of risk that was undergone for the last Mozilla-Foundation Trademark fiasco, iceweasel Rust's Trademark requirements are that "you must seek our explicit permission before distributing patches". Uses that require explicit approval Distributing a **MODIFIED VERSION** of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team. there are dozens of such patches and every single one of them, unless explicit permission has been sought, is a DIRECT Trademark violation https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/ the over-ride of the Trademark on "Free" software is Lawful and in this case makes rust (and cargo) non-free software. unlike the Iceweasel debacle, the linux kernel is upstream merging rust, potentially making the entire linux kernel critically dependent on a non-free compiler. there is the additional issue that although Debian might seek and be granted explicit permission for a Trademark License Grant to Distribute, that does not cover Derivatives, which would also need to explicitly seek their own permission https://www.debian.org/derivatives/ https://devuan.org this has been disc
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
Distributing a modified version of the Rust programming language or the Cargo package manager, provided that the modifications are limited to: * porting the software to a different architecture * fixing local paths * adding patches that have been released upstream * adding patches that have been reported upstream, provided * that the patch is removed if it is not accepted upstream note that this excludes the right to: * add a patch to add documentation Documentation updates should be done upstream. * add a patch to add a Debian README This is purely Debian documentation. They do not impact Rustc. * add a patch to add a debian/copyright file Same. * add a patch to add optimisations As the initial packager of Rustc (and llvm), I would reject such changes. Optimisations should be done upstream and not downstream. * add a patch to fix serious security vulnerabilities Such patches are part of the "adding patches that have been released upstream" all of the limitations whilst looking perfectly reasonable are unfortunately in direct conflict with not only 50% of the DFSG but also in direct violation of the GPL (under which gcc is released). gcc specific issues should be on the gcc side, not rustc. Cheers, Sylvestre
Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
Thanks for bringing it to our attention, I have consulted with the Rust foundation, we have agreed a change, we think this change solves it. See https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ for the updated policy. Cheers, Sylvestre Le 27/06/2022 à 13:52, lkcl a écrit : Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely serious situation that exposes debian to a greater level of risk that was undergone for the last Mozilla-Foundation Trademark fiasco, iceweasel Rust's Trademark requirements are that "you must seek our explicit permission before distributing patches". Uses that require explicit approval Distributing a **MODIFIED VERSION** of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team. there are dozens of such patches and every single one of them, unless explicit permission has been sought, is a DIRECT Trademark violation https://sources.debian.org/patches/rustc/1.36.0+dfsg1-2/ the over-ride of the Trademark on "Free" software is Lawful and in this case makes rust (and cargo) non-free software. unlike the Iceweasel debacle, the linux kernel is upstream merging rust, potentially making the entire linux kernel critically dependent on a non-free compiler. there is the additional issue that although Debian might seek and be granted explicit permission for a Trademark License Grant to Distribute, that does not cover Derivatives, which would also need to explicitly seek their own permission https://www.debian.org/derivatives/ https://devuan.org this has been discussed that DFSG Guideline 8 is violated by even attempting to seek a License specific to Debian https://www.mail-archive.com/debian-legal@lists.debian.org/msg45464.html this is an extremely serious situation that either requires pulling rust and cargo from debian or a rename of both rust and cargo exactly as was done with iceweasel. failure to do so is also extremely serious because Unlawful Distribution may still be considered grounds for financial compensation as well as a Legal Notice to Cease and Desist, and also to remove all public and private use of the Trademark from all Records. mailing lists, bugtracker, debian archives - everything. this one cannot be ignored. -- System Information: ___ Pkg-rust-maintainers mailing list pkg-rust-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers
Bug#1015242: gcc Trademark violation on the horizon
Package: gcc Version: 4:9.2.1-3.1 Severity: serious Tags: upstream Justification: Policy 2.1 short version: gcc is about to become more problematic than rustc with respect to violation of a non-free Trademark License created by the Rust (Mozilla) Foundation. https://developers.slashdot.org/story/22/07/17/0110250/gcc-rust-approved-by-steering-committee-beta-likely-next-april with gcc being literally the bedrock of FOSS that's about to become an extremely serious situation. unfortunately, unlike the rustc scenario the non-Free Rust Trademark License directly conflicts with the GPL *as well*: Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. the rust Trademark Licence explicitly restricts and curtails those rights. this is in addition to violating 50% of DFSG Section 2 as already outlined in bug #1013920. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920#60 -- System Information:
Bug#1012219: Please adjust StanHeaders to new version of (one)tbb
Control: tags -1 upstream Control: forwarded -1 Ben Goodrich Hi Ben, Debian is migrating from old tbb to onetbb (currently version 2021.5.0). When trying to build rstan version 2.21.5 which includes StanHeaders we get the error you can find here in our CI: https://salsa.debian.org/r-pkg-team/r-cran-rstan/-/jobs/3011219 In file included from /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/core.hpp:4, from /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/mat.hpp:6, from /usr/lib/R/site-library/StanHeaders/include/stan/math/rev/mat.hpp:12, from ./stan/model/log_prob_grad.hpp:4, from ./stan/model/test_gradients.hpp:7, from ./stan/services/diagnose/diagnose.hpp:10, from stan_fit.cpp:33: /usr/lib/R/site-library/StanHeaders/include/stan/math/prim/core/init_threadpool_tbb.hpp:9:10: fatal error: tbb/task_scheduler_init.h: No such file or directory 9 | #include | ^~~ compilation terminated. It seems StanHeaders need to be adapted to onetbb. There is a tbb -> onetbb transition guide: https://oneapi-src.github.io/oneTBB/main/tbb_userguide/Migration_Guide.html Hope this helps Andreas. -- http://fam-tille.de
Processed: Please adjust StanHeaders to new version of (one)tbb
Processing control commands: > tags -1 upstream Bug #1012219 [src:r-cran-rstan] r-cran-rstan: FTBFS with onetbb/2021.5.0-9 in experimental Added tag(s) upstream. > forwarded -1 Ben Goodrich Bug #1012219 [src:r-cran-rstan] r-cran-rstan: FTBFS with onetbb/2021.5.0-9 in experimental Set Bug forwarded-to-address to 'Ben Goodrich '. -- 1012219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")
https://developers.slashdot.org/story/22/07/17/0110250/gcc-rust-approved-by-steering-committee-beta-likely-next-april and now it becomes Unlawful for Debian to distribute gcc with patches, as well [without the explicit consent of the Mozilla Foundation, an action which is in direct violation of DFSG] On Mon, Jun 27, 2022 at 3:38 PM lkcl wrote: > > the alternative is to work with the Mozilla Foundation to rewrite their > Trademark License. > > the *intent* is clear, they do not trust Licensees (distributors) to "damage" > the rust API, which is perfectly reasonable. > > therefore, why don't they just say that? > > "if a distributor performs source code modifications to a > published revision that cause security holes, cause API or > language incompatibilities or cause other end-user > complaints, then this a Trademark Violation" > > something along these lines is waaay more sensible than pissing about trying > to completely unreasonably "lock down" the source code. this appears to have been added recently (or i missed it): Distributing a modified version of the Rust programming language or the Cargo package manager, provided that the modifications are limited to: * porting the software to a different architecture * fixing local paths * adding patches that have been released upstream * adding patches that have been reported upstream, provided * that the patch is removed if it is not accepted upstream note that this excludes the right to: * add a patch to add documentation * add a patch to add a Debian README * add a patch to add a debian/copyright file * add a patch to add optimisations * add a patch to fix serious security vulnerabilities * convey to others the right to modify [GPL Copyright License requirement] all of the limitations whilst looking perfectly reasonable are unfortunately in direct conflict with not only 50% of the DFSG but also in direct violation of the GPL (under which gcc is released). l.
Bug#1014492: guzzle: CVE-2022-31090 CVE-2022-31091
Hi David, I set pkg-php-p...@lists.alioth.debian.org as maintainer and corrected the upstream version in the gbp.conf (used as template the PHPGroup Wiki: https://wiki.debian.org/Teams/DebianPHPGroup/Composer#debian.2Fgbp.conf). I pushed now again, if there are any other changes to be done, please let me know. Regards Katharina On Saturday, 2022-07-16, 09:26:10 (GMT +0200), David Prévot wrote: > Hi Katharina, > > Le Thu, Jul 07, 2022 at 10:56:06AM +0200, Katharina Drexel a écrit : > […] > > thanks for the hints. I pushed a new version in the repo > > (https://salsa.debian.org/php-team/pear/php-guzzlehttp-guzzle). > > TBD: someone should upload it in the debian repo. > > You may wish to CC: pkg-php-p...@lists.alioth.debian.org for such > request, or even better, actually set the list as Maintainers so > everyone is made aware of the bug (before receiving hundreds of > autoremoval warnings). > > The current repository is a mess, can you properly set up gbp please? > > Regards > > David signature.asc Description: PGP signature
