Processed: severity of 1070217 is serious
Processing commands for cont...@bugs.debian.org: > severity 1070217 serious Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070188: python3-spyder: uninstallable in unstable due to pylint
On Wed, May 01, 2024 at 03:04:56PM +0200, Roland Mas wrote: > Package: python3-spyder > Version: 5.5.1+ds-1 > Severity: important > > Dear Maintainer, > > python3-spyder is no longer installable in sid; it depends (and > build-depends) on pylint (< 3.1~) but pylint is currently 3.1.0-1 in > unstable. > > Loosening the versioned dependency is enough to allow spyder to build, > but I don't know whether that introduces runtime changes or not. Dear Roland, That would be a reasonable thing to do. Version 5.5.4 depends on pylint >= 3.1. I don't have time to do this right now, unfortunately, so if someone else would like to make the required changes and upload a patched version of 5.5.1 in the meantime, please feel free to do so. See https://github.com/spyder-ide/spyder/commit/26244db2750f92aa6cbbfd74252d6aa4daa07811 for the changes required (but obviously don't change python-lsp-server for now!). Best wishes, Julian
Bug#1058419: marked as done (pyannotate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 02 May 2024 04:00:31 +
with message-id
and subject line Bug#1065045: Removed package(s) from unstable
has caused the Debian Bug report #1058419,
regarding pyannotate: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.12 3.11" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1058419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyannotate
Version: 1.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config
> running config
> I: pybuild base:310: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_runtime
> copying pyannotate_runtime/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_runtime
> copying pyannotate_runtime/collect_types.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_runtime
> creating
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools
> copying pyannotate_tools/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools
> creating
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/main.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/parse.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/__main__.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/types.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/infer.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/annotations
> creating
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/fixes
> copying pyannotate_tools/fixes/__init__.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/fixes
> copying pyannotate_tools/fixes/fix_annotate.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/fixes
> copying pyannotate_tools/fixes/fix_annotate_json.py ->
> /<>/.pybuild/cpython3_3.12_pyannotate/build/pyannotate_tools/fixes
> I: pybuild base:310: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_runtime
> copying pyannotate_runtime/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_runtime
> copying pyannotate_runtime/collect_types.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_runtime
> creating
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools
> copying pyannotate_tools/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools
> creating
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/main.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/parse.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/__main__.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/types.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> copying pyannotate_tools/annotations/infer.py ->
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/annotations
> creating
> /<>/.pybuild/cpython3_3.11_pyannotate/build/pyannotate_tools/fixes
> copying
Bug#1058237: marked as done (python-boto: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Thu, 02 May 2024 04:00:02 +
with message-id
and subject line Bug#1058652: Removed package(s) from unstable
has caused the Debian Bug report #1058237,
regarding python-boto: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-boto
Version: 2.49.0-4.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binary
> py3versions: no X-Python3-Version in control file, using supported versions
> dh_testdir
> dh_installdirs
> set -e ; for pyvers in 3.12 3.11; do \
> python$pyvers setup.py install --root
> /<>/debian/python3-boto \
> --install-scripts usr/share/doc/python3-boto/examples/ \
> --install-layout=deb ; \
> done
> /<>/boto/__init__.py:1105: SyntaxWarning: invalid escape
> sequence '\c'
> """
> /<>/boto/pyami/config.py:98: SyntaxWarning: invalid escape
> sequence '\s'
> match = re.match("^#import[\s\t]*([^\s^\t]*)[\s\t]*$", line)
> Traceback (most recent call last):
> File "/<>/setup.py", line 37, in
> from boto import __version__
> File "/<>/boto/__init__.py", line 29, in
> import boto.plugin
> File "/<>/boto/plugin.py", line 40, in
> import imp
> ModuleNotFoundError: No module named 'imp'
> make: *** [debian/rules:28: install] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/python-boto_2.49.0-4.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 2.49.0-4.1+rm
Dear submitter,
as the package python-boto has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1058652
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1060963: paramiko: FTBFS: dh_auto_test: error: pybuild
> E ModuleNotFoundError: No module named 'six' This happens because we unknot the python3-mock -> python3-pbr -> python3-six dependency chain. I did this _on purpose_ to discover missing python3-six (build-)dependencies and/or upstream that needs a cleanup. Here it's of course better to do this long overdue paramiko update than merely adding python3-six as build-dep for a quick fix. Greetings and thank you https://tracker.debian.org/news/1492697/accepted-python-mock-510-1-source-into-unstable/ python-mock (5.1.0-1) unstable; urgency=medium . * Team Upload * New upstream version 5.1.0 (Closes: #717192, #717193, #1030887) (LP: #1248066) * remove obsolete build-dep python3-pbr & python3-unittest2 * use new dh-sequence-python3 https://tracker.debian.org/news/1505240/accepted-python-pbr-600-1-source-into-unstable/ python-pbr (6.0.0-1) unstable; urgency=medium . * New upstream release (Closes: #1060153). * Do not use six anymore.
Bug#1069191: glibc: GLIBC-SA-2024-0004/CVE-2024-2961: ISO-2022-CN-EXT: fix^J out-of-bound writes when writing escape sequence
On Mon, 22 Apr 2024 09:31:39 +0200 Charlemagne Lasse wrote: > Hi, > > Can this be backported to older Debian versions via the security repo? > This bug can be used to execute code when using the PHP engine: > > * https://www.offensivecon.org/speakers/2024/charles-fol.html > * https://www.openwall.com/lists/oss-security/2024/04/18/4 > Indeed.. I know that buster is old-old stable, but starting to get nervous that it doesn't contain the fix that Bullseye and Bookworm have. Especially as we approach the date of a security conference that will talk about this issue. Is anyone on the LTS team working on it for Buster? That might also help trickle down to ELTS for Stretch/Jessie? signature.asc Description: PGP signature
Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386
On Mon, 26 Feb 2024 19:53:49 +0100 Fabio Pedretti wrote: > Ubuntu fixed it with this patch: > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz > Can this fix be added to Debian? Meson has been stuck without moving to testing for a very long time and now it seems to be stalling Mesa in result too. Shmerl.
Processed: openttd: cmake licensing concern for openttd 14.0 source package
Processing control commands: > forwarded -1 https://github.com/OpenTTD/OpenTTD/pull/12603 Bug #1070208 [src:openttd] openttd: cmake licensing concern for openttd 14.0 source package Set Bug forwarded-to-address to 'https://github.com/OpenTTD/OpenTTD/pull/12603'. -- 1070208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070208: openttd: cmake licensing concern for openttd 14.0 source package
Source: openttd Version: 14.0-1 Severity: serious Tags: upstream Justification: Policy 12.5 Control: forwarded -1 https://github.com/OpenTTD/OpenTTD/pull/12603 Dear Maintainer, The build scripts for the initial version 14.0 release of OpenTTD include a CMake file that determines whether and how to add compile-time flags to request that libatomic should be linked. The relevant CMake file addition was sourced[1] from the LLVM codebase, which is licensed under a variant of the Apache 2.0 license with some exception clauses added for the LLVM project. This is not yet documented in the source package. I'm reporting this bug with severity 'serious' because I feel that there is a potential licensing concern here; until that is confirmed one way or the other, I've offered what I believe is a possible resolution (adding the LLVM license -- slightly confusingly _also_ referred to as v14, because that is the version of LLVM where it was introduced, despite v18 being LLVM-current), to upstream[2]. To explain my reasoning: On balance I'd prefer opening a serious-severity bug to prevent migration (that could later be reduced in severity) than to allow the package transition while being aware of a potential problem. Thanks, James [1] - https://github.com/OpenTTD/OpenTTD/pull/10513 [2] - https://github.com/OpenTTD/OpenTTD/pull/12603
Bug#1070015: marked as done (haskel-pandoc: FTBFS on armel: Couldn't match expected type: WriterState -> m a)
Your message dated Wed, 01 May 2024 21:20:13 +
with message-id
and subject line Bug#1070015: fixed in haskell-pandoc 3.1.3-2
has caused the Debian Bug report #1070015,
regarding haskel-pandoc: FTBFS on armel: Couldn't match expected type:
WriterState -> m a
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.)
--
1070015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-pandoc
Version: 3.1.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=haskell-pandoc=armel=3.1.3-1%2Bb1=1713911741=0
[162 of 212] Compiling Text.Pandoc.Writers.Muse
src/Text/Pandoc/Writers/Muse.hs:85:25: error:
• Couldn't match expected type: WriterState -> m a
with actual type: Set.Set Text
• Possible cause: ‘($)’ is applied to too many arguments
In the expression: evalStateT $ runReaderT document env
In an equation for ‘evalMuse’:
evalMuse document env = evalStateT $ runReaderT document env
• Relevant bindings include
document :: Muse m a
(bound at src/Text/Pandoc/Writers/Muse.hs:85:10)
evalMuse :: Muse m a -> WriterEnv -> WriterState -> m a
(bound at src/Text/Pandoc/Writers/Muse.hs:85:1)
|
85 | evalMuse document env = evalStateT $ runReaderT document env
|
src/Text/Pandoc/Writers/Muse.hs:85:38: error:
• Couldn't match expected type ‘WriterState’
with actual type ‘StateT WriterState m a’
• In the second argument of ‘($)’, namely ‘runReaderT document env’
In the expression: evalStateT $ runReaderT document env
In an equation for ‘evalMuse’:
evalMuse document env = evalStateT $ runReaderT document env
• Relevant bindings include
document :: Muse m a
(bound at src/Text/Pandoc/Writers/Muse.hs:85:10)
evalMuse :: Muse m a -> WriterEnv -> WriterState -> m a
(bound at src/Text/Pandoc/Writers/Muse.hs:85:1)
|
85 | evalMuse document env = evalStateT $ runReaderT document env
| ^^^
src/Text/Pandoc/Writers/Muse.hs:233:11: error:
• Couldn't match expected type: ReaderT
WriterEnv (StateT WriterState m) a2
with actual type: Int -> Set.Set Text -> Bool -> WriterState
• Probable cause: ‘($)’ is applied to too few arguments
In a stmt of a 'do' block: modify $ \ st -> st {stUseTags = False}
In the expression:
do modify $ \ st -> st {stUseTags = False}
hang 2 "- " <$> blockListToMuse item
In an equation for ‘bulletListItemToMuse’:
bulletListItemToMuse item
= do modify $ \ st -> ...
hang 2 "- " <$> blockListToMuse item
• Relevant bindings include
bulletListItemToMuse :: [Block] -> Muse m (Doc Text)
(bound at src/Text/Pandoc/Writers/Muse.hs:232:9)
|
233 | modify $ \st -> st { stUseTags = False }
|
src/Text/Pandoc/Writers/Muse.hs:233:20: error:
• Couldn't match expected type: [[Block]]
with actual type: WriterState -> WriterState
• The lambda expression ‘\ st -> ...’ has one value argument,
but its type ‘[[Block]]’ has none
In the second argument of ‘($)’, namely
‘\ st -> st {stUseTags = False}’
In a stmt of a 'do' block: modify $ \ st -> st {stUseTags = False}
|
233 | modify $ \st -> st { stUseTags = False }
|^^^
src/Text/Pandoc/Writers/Muse.hs:243:11: error:
• Couldn't match expected type: ReaderT
WriterEnv (StateT WriterState m) a3
with actual type: Int -> Set.Set Text -> Bool -> WriterState
• Probable cause: ‘($)’ is applied to too few arguments
In a stmt of a 'do' block: modify $ \ st -> st {stUseTags = False}
In the expression:
do modify $ \ st -> st {stUseTags = False}
label' <- local
(\ env -> env {envOneLine = True, envAfterSpace = True})
$ inlineListToMuse' label
let ind = offset' label'
hang ind (nowrap label') . vcat <$> mapM descriptionToMuse defs
In an equation for ‘definitionListItemToMuse’:
Processed: found 1069357 in 0.14.3+ds-1
Processing commands for cont...@bugs.debian.org: > found 1069357 0.14.3+ds-1 Bug #1069357 [src:cpp-httplib] cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 meson test --timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online returned exit code 1 Marked as found in versions cpp-httplib/0.14.3+ds-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1069552 in 1.0.21-13.1
Processing commands for cont...@bugs.debian.org: > found 1069552 1.0.21-13.1 Bug #1069552 [src:freecontact] freecontact: FTBFS on armel: make[1]: *** [Makefile:469: all-recursive] Error 1 Ignoring request to alter found versions of bug #1069552 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1069552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070015: haskel-pandoc: FTBFS on armel: Couldn't match expected type: WriterState -> m a
On Sun, Apr 28, 2024 at 05:14PM, Sebastian Ramacher wrote: > https://buildd.debian.org/status/fetch.php?pkg=haskell-pandoc=armel=3.1.3-1%2Bb1=1713911741=0 I have been trying to understand what is wrong, but haven't found anything. My best guess right now is that this is a GHC bug that manifests due to the time64 transition. Oddly enough, if we run 'build' again it succeeds. My course of action for now is: * Upload a workaround for haskell-pandoc that runs 'build' twice, so we can finish with this transition * Upgrade to GHC 9.6 with the next transition, with the hope that this bug is fixed there * If not, report this upstream -- Ilias
Bug#1070201: scikit-learn: autopkgtest regression on i386 with NumPy 1.26
Source: scikit-learn
Version: 1.4.1.post1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
scikit-learn's autopkgtest regresses on i386 when tested with numpy
1.26 [1]. I've copied what I hope is the relevant part of the log
below.
Regards
Graham
[1] https://ci.debian.net/packages/s/scikit-learn/testing/i386/
1386s === FAILURES
===
35104
1386s __ test_graphviz_toy
___
35105
1386s
35106
1386s def test_graphviz_toy():
35107
1386s # Check correctness of export_graphviz
35108
1386s clf = DecisionTreeClassifier(
35109
1386s max_depth=3, min_samples_split=2, criterion="gini", random_state=2
35110
1386s )
35111
1386s clf.fit(X, y)
35112
1386s
35113
1386s # Test export code
35114
1386s contents1 = export_graphviz(clf, out_file=None)
35115
1386s contents2 = (
35116
1386s "digraph Tree {\n"
35117
1386s 'node [shape=box, fontname="helvetica"] ;\n'
35118
1386s 'edge [fontname="helvetica"] ;\n'
35119
1386s '0 [label="x[0] <= 0.0\\ngini = 0.5\\nsamples = 6\\n'
35120
1386s 'value = [3, 3]"] ;\n'
35121
1386s '1 [label="gini = 0.0\\nsamples = 3\\nvalue = [3, 0]"] ;\n'
35122
1386s "0 -> 1 [labeldistance=2.5, labelangle=45, "
35123
1386s 'headlabel="True"] ;\n'
35124
1386s '2 [label="gini = 0.0\\nsamples = 3\\nvalue = [0, 3]"] ;\n'
35125
1386s "0 -> 2 [labeldistance=2.5, labelangle=-45, "
35126
1386s 'headlabel="False"] ;\n'
35127
1386s "}"
35128
1386s )
35129
1386s
35130
1386s assert contents1 == contents2
35131
1386s
35132
1386s # Test plot_options
35133
1386s contents1 = export_graphviz(
35134
1386s clf,
35135
1386s filled=True,
35136
1386s impurity=False,
35137
1386s proportion=True,
35138
1386s special_characters=True,
35139
1386s rounded=True,
35140
1386s out_file=None,
35141
1386s fontname="sans",
35142
1386s )
35143
1386s contents2 = (
35144
1386s "digraph Tree {\n"
35145
1386s 'node [shape=box, style="filled, rounded", color="black", '
35146
1386s 'fontname="sans"] ;\n'
35147
1386s 'edge [fontname="sans"] ;\n'
35148
1386s "0 [label=0 0.0samples = 100.0%"
35149
1386s 'value = [0.5, 0.5]>, fillcolor="#ff"] ;\n'
35150
1386s "1 [label=value = [1.0, 0.0]>, "
35151
1386s 'fillcolor="#e58139"] ;\n'
35152
1386s "0 -> 1 [labeldistance=2.5, labelangle=45, "
35153
1386s 'headlabel="True"] ;\n'
35154
1386s "2 [label=value = [0.0, 1.0]>, "
35155
1386s 'fillcolor="#399de5"] ;\n'
35156
1386s "0 -> 2 [labeldistance=2.5, labelangle=-45, "
35157
1386s 'headlabel="False"] ;\n'
35158
1386s "}"
35159
1386s )
35160
1386s
35161
1386s assert contents1 == contents2
35162
1386s
35163
1386s # Test max_depth
35164
1386s contents1 = export_graphviz(clf, max_depth=0, class_names=True,
out_file=None)
35165
1386s contents2 = (
35166
1386s "digraph Tree {\n"
35167
1386s 'node [shape=box, fontname="helvetica"] ;\n'
35168
1386s 'edge [fontname="helvetica"] ;\n'
35169
1386s '0 [label="x[0] <= 0.0\\ngini = 0.5\\nsamples = 6\\n'
35170
1386s 'value = [3, 3]\\nclass = y[0]"] ;\n'
35171
1386s '1 [label="(...)"] ;\n'
35172
1386s "0 -> 1 ;\n"
35173
1386s '2 [label="(...)"] ;\n'
35174
1386s "0 -> 2 ;\n"
35175
1386s "}"
35176
1386s )
35177
1386s
35178
1386s assert contents1 == contents2
35179
1386s
35180
1386s # Test max_depth with plot_options
35181
1386s contents1 = export_graphviz(
35182
1386s clf, max_depth=0, filled=True, out_file=None, node_ids=True
35183
1386s )
35184
1386s contents2 = (
35185
1386s "digraph Tree {\n"
35186
1386s 'node [shape=box, style="filled", color="black", '
35187
1386s 'fontname="helvetica"] ;\n'
35188
1386s 'edge [fontname="helvetica"] ;\n'
35189
1386s '0 [label="node #0\\nx[0] <= 0.0\\ngini = 0.5\\n'
35190
1386s 'samples = 6\\nvalue = [3, 3]", fillcolor="#ff"] ;\n'
35191
1386s '1 [label="(...)", fillcolor="#C0C0C0"] ;\n'
35192
1386s "0 -> 1 ;\n"
35193
1386s '2 [label="(...)", fillcolor="#C0C0C0"] ;\n'
35194
1386s "0 -> 2 ;\n"
35195
1386s "}"
35196
1386s )
35197
1386s
35198
1386s assert contents1 == contents2
35199
1386s
35200
1386s # Test multi-output with weighted samples
35201
1386s clf = DecisionTreeClassifier(
35202
1386s max_depth=2, min_samples_split=2, criterion="gini", random_state=2
35203
1386s )
35204
1386s clf = clf.fit(X, y2, sample_weight=w)
35205
1386s
35206
1386s > contents1 = export_graphviz(clf, filled=True, impurity=False,
out_file=None)
35207
1386s
35208
1386s /usr/lib/python3/dist-packages/sklearn/tree/tests/test_export.py:131:
35209
1386s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
35210
1386s /usr/lib/python3/dist-packages/sklearn/utils/_param_validation.py:213:
in wrapper
35211
1386s return func(*args, **kwargs)
35212
1386s /usr/lib/python3/dist-packages/sklearn/tree/_export.py:906: in
export_graphviz
35213
1386s exporter.export(decision_tree)
35214
1386s /usr/lib/python3/dist-packages/sklearn/tree/_export.py:466: in export
35215
1386s self.recurse(decision_tree.tree_, 0,
Bug#1070062: marked as done (waylandpp: Missing build-depends libwayland-egl1-mesa)
Your message dated Wed, 01 May 2024 17:56:11 + with message-id and subject line Bug#1070062: fixed in waylandpp 1.0.0-6 has caused the Debian Bug report #1070062, regarding waylandpp: Missing build-depends libwayland-egl1-mesa 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.) -- 1070062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: waylandpp Version: 1.0.0-4 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The libwayland-egl1-mesa package was a transitional package for libegl1 and libwayland-egl1 and has been removed. You will need to update your build-depends appropriately. Scott K --- End Message --- --- Begin Message --- Source: waylandpp Source-Version: 1.0.0-6 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of waylandpp, 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 1070...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated waylandpp 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: Wed, 01 May 2024 19:27:19 +0200 Source: waylandpp Architecture: source Version: 1.0.0-6 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 1070062 Changes: waylandpp (1.0.0-6) unstable; urgency=medium . * replaced a build-dependency: libwayland-egl1-mesa -> libegl1 Closes: #1070062 Checksums-Sha1: fd70413576b852d0b0b3f00efc14b3019a504aa8 2483 waylandpp_1.0.0-6.dsc e76efa94168ea63602d68a8a10eab9ac69c13442 6876 waylandpp_1.0.0-6.debian.tar.xz 6d6bab618bfee86b850be9b97d1e2b9cdef93312 13742 waylandpp_1.0.0-6_amd64.buildinfo Checksums-Sha256: 7d593bea4e305a92d01e7ed0fa1d3688464f99fd0d2278b3624c4013c48f5957 2483 waylandpp_1.0.0-6.dsc 6e25eef0efc87bd596e226d3fbfdc13f34b6466f81002c86c0343f9be9ba2e89 6876 waylandpp_1.0.0-6.debian.tar.xz b5e053a230f56957159d30785da4dc0e8ed36941c253e966cacadc0c9538a068 13742 waylandpp_1.0.0-6_amd64.buildinfo Files: ab24b46ee8f201202fde0b90e358e291 2483 libs optional waylandpp_1.0.0-6.dsc 5abc858522482a59423596b6ec240743 6876 libs optional waylandpp_1.0.0-6.debian.tar.xz bc02a9aa0dee3e2740d1d405b69b36c1 13742 libs optional waylandpp_1.0.0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmYyfVMACgkQHCgWkHE2 rjlv1BAArZ9qIGmXwcusYajsRpbgoX/585b4wm6KFN6sL1nncnXPqynv/W38LenN jc/EAL5cQXcIbAzPED1qgavPFzVrojcM+/nDZmAKhDRLyA5LxZxdOZcCJmzldU0e ZC+rb2W4f9yViRxUftnsNNoqdcGjgrElzTcrHzAe6gSUkDOAA/8Q2yUIBu4MMkcr bcOtexLCrbKEAOB+4sMYjXhyN/MeGXsSNXE9t89RWMRtcVF6A1pNf0jkNQLkW4Mc uwDzHuFYyt7/k4MfFUpudd5HvnBFkOgxkUdzhn2xWoIuIKQVnWCjnfT0AX0MEWrC evAAN1g2GLMhonPJ2bf/Nqb80FHUzfY7Uqu2jx9jhLQyD9Stc2MUyhJn0SI7ZO6F v5A/RAU7KK6INSn6z9UzkOwrdUNKP/2nBzYY2qe15eHKxEwpcpSSgJQ51/4IY7/d 3g0OCWF5K1OpXITTYHIaHwOg/pHbMGLxbo/ME/JC6zp+WeTvF2d4RD8F8nd9ltIV J6GG/5kuuiI9sn/JIy83LkqFJgNg7lreAAOoJIiDiSdX5gT7c/LOg18/DytN/WmG Up7IVpb8FdFisJvAmQryAP6/tmslSlOoCXeCLYEwZgawS9FOrYUUv3mJUZp30hx0 1e0rSBJ3d58uy9sV4daKL/PPJ2si0WYnSNTUWevTvr3Xct5Ukso= =26PL -END PGP SIGNATURE- pgpLPcQlK3W3E.pgp Description: PGP signature --- End Message ---
Bug#1069557: libkdumpfile: FTBFS on armel: dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2
Hi Lucas, On 4/20/24 8:23 AM, Lucas Nussbaum wrote: Source: libkdumpfile Version: 0.5.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel Hi, During a rebuild of all packages in sid, your package failed to build on armel. Thanks for filing. I've notified upstream: https://github.com/ptesarik/libkdumpfile/issues/80 and will try and reproduce and fix this. Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 OpenPGP_0x8B229D2F7CCC04F2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1067315: marked as done (matplotlib: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed)
Your message dated Wed, 01 May 2024 15:19:24 + with message-id and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1 has caused the Debian Bug report #1067311, regarding matplotlib: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib Version: 3.6.3-1.1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cm-super-minimal, debhelper (>= 7), dh-python, dvipng, > ffmpeg, fonts-noto-cjk, fonts-wqy-zenhei, ghostscript, graphviz, imagemagick, > libfreetype6-dev, libpng-dev, libqhull-dev, locales-all, python3-all-dev, > python3-cairo, python3-cairocffi, python3-certifi (>= 2020.6.20-1), > python3-colorspacious, python3-contourpy, python3-cxx-dev, python3-cycler (>= > 0.10.0), python3-dateutil, python3-fonttools, python3-gi, python3-ipywidgets, > python3-kiwisolver, python3-numpy (>= 1.20.0), python3-numpydoc, > python3-pandas, python3-pikepdf, python3-pil, python3-pil.imagetk, > python3-pkg-resources, python3-pyparsing (>= 1.5.6), python3-pyqt5, > python3-pytest, python3-setuptools, python3-setuptools-scm, python3-tk, > python3-tornado, python3-wxgtk4.0, python3-xarray, tcl8.6-dev, texlive-base, > texlive-fonts-recommended, texlive-latex-extra, texlive-latex-recommended, > texlive-luatex, texlive-science, texlive-xetex, tk8.6-dev, xauth, xvfb, > zlib1g-dev, build-essential, fakeroot > Filtered Build-Depends: cm-super-minimal, debhelper (>= 7), dh-python, > dvipng, ffmpeg, fonts-noto-cjk, fonts-wqy-zenhei, ghostscript, graphviz, > imagemagick, libfreetype6-dev, libpng-dev, libqhull-dev, locales-all, > python3-all-dev, python3-cairo, python3-cairocffi, python3-certifi (>= > 2020.6.20-1), python3-colorspacious, python3-contourpy, python3-cxx-dev, > python3-cycler (>= 0.10.0), python3-dateutil, python3-fonttools, python3-gi, > python3-ipywidgets, python3-kiwisolver, python3-numpy (>= 1.20.0), > python3-numpydoc, python3-pandas, python3-pikepdf, python3-pil, > python3-pil.imagetk, python3-pkg-resources, python3-pyparsing (>= 1.5.6), > python3-pyqt5, python3-pytest, python3-setuptools, python3-setuptools-scm, > python3-tk, python3-tornado, python3-wxgtk4.0, python3-xarray, tcl8.6-dev, > texlive-base, texlive-fonts-recommended, texlive-latex-extra, > texlive-latex-recommended, texlive-luatex, texlive-science, texlive-xetex, > tk8.6-dev, xauth, xvfb, zlib1g-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1776 B] > Get:5 copy:/<>/apt_archive ./ Packages [1564 B] > Fetched 3955 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-ipywidgets : Depends: jupyter-nbextension-jupyter-js-widgets (= > 8.1.1-3) but 8.1.1-2 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/03/19/matplotlib_3.6.3-1.1_unstable.log All bugs filed during this archive rebuild are listed at:
Bug#1067311: marked as done (ipywidgets: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed)
Your message dated Wed, 01 May 2024 15:19:24 + with message-id and subject line Bug#1067311: fixed in ipywidgets 8.1.2-1 has caused the Debian Bug report #1067311, regarding ipywidgets: FTBFS: unsatisfiable build-dependency: jupyter-nbextension-jupyter-js-widgets (= 8.1.1-3) but 8.1.1-2 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1067311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ipywidgets Version: 8.1.1-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240319 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, fonts-font-awesome, > libjs-mathjax, libjs-requirejs, libjs-sizzle, node-ajv, node-backbone, > node-css-loader, node-d3, node-d3-color, node-d3-format, node-es6-promise, > node-expect.js, node-file-loader, node-jquery, node-jquery-ui, > node-jupyterlab, node-jupyterlab-rendermime-interfaces, node-lodash, > node-lumino, node-minipass, node-nouislider, node-postcss, node-process, > node-recast, node-requirejs, node-sanitize-html, node-semver, node-sinon, > node-style-loader, node-types-estree, node-types-sanitize-html, > node-types-underscore, node-typescript, node-underscore, node-url-loader, > npm, pandoc, pkg-js-tools, python3-all, python3-bqplot, python3-comm (>= > 0.2.1), python3-ipykernel, python3-ipython, python3-jsonschema, > python3-jupyter-packaging (>= 0.11.1), python3-matplotlib, python3-nbsphinx, > python3-pytest, python3-pytest-cov, python3-recommonmark, python3-setuptools, > python3-sphinx, python3-sphinx-rtd-theme, python3-traitlets, webpack, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, > fonts-font-awesome, libjs-mathjax, libjs-requirejs, libjs-sizzle, node-ajv, > node-backbone, node-css-loader, node-d3, node-d3-color, node-d3-format, > node-es6-promise, node-expect.js, node-file-loader, node-jquery, > node-jquery-ui, node-jupyterlab, node-jupyterlab-rendermime-interfaces, > node-lodash, node-lumino, node-minipass, node-nouislider, node-postcss, > node-process, node-recast, node-requirejs, node-sanitize-html, node-semver, > node-sinon, node-style-loader, node-types-estree, node-types-sanitize-html, > node-types-underscore, node-typescript, node-underscore, node-url-loader, > npm, pandoc, pkg-js-tools, python3-all, python3-bqplot, python3-comm (>= > 0.2.1), python3-ipykernel, python3-ipython, python3-jsonschema, > python3-jupyter-packaging (>= 0.11.1), python3-matplotlib, python3-nbsphinx, > python3-pytest, python3-pytest-cov, python3-recommonmark, python3-setuptools, > python3-sphinx, python3-sphinx-rtd-theme, python3-traitlets, webpack, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1576 B] > Get:5 copy:/<>/apt_archive ./ Packages [1606 B] > Fetched 3797 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-ipywidgets : Depends: jupyter-nbextension-jupyter-js-widgets (= > 8.1.1-3) but 8.1.1-2 is to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2024/03/19/ipywidgets_8.1.1-4_unstable.log All bugs filed during this
Bug#1066551: marked as done (ramond: FTBFS: src/main.c:164:17: error: implicit declaration of function ‘LOG’ [-Werror=implicit-function-declaration])
Your message dated Wed, 01 May 2024 14:58:50 +
with message-id
and subject line Bug#1066551: fixed in ramond 0.5-5
has caused the Debian Bug report #1066551,
regarding ramond: FTBFS: src/main.c:164:17: error: implicit declaration of
function ‘LOG’ [-Werror=implicit-function-declaration]
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1066551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ramond
Version: 0.5-4.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
Relevant part (hopefully):
> cc -c src/main.c -g -O2 -Werror=implicit-function-declaration
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
> -fcommon -Wdate-time -D_FORTIFY_SOURCE=2 `apr-1-config --includes --cppflags
> --cflags` `pkg-config --cflags libxml-2.0`
> src/main.c: In function ‘rafixd_recvRa’:
> src/main.c:164:17: error: implicit declaration of function ‘LOG’
> [-Werror=implicit-function-declaration]
> 164 | LOG( RAMOND_CRITICAL "! socket recvmsg error: '%s'\n",
> | ^~~
> src/main.c: In function ‘executeActions’:
> src/main.c:570:17: warning: argument 2 null where non-null expected
> [-Wnonnull]
> 570 | setenv("PREFIX", NULL, 1);
> | ^~
> In file included from src/main.h:1,
> from src/main.c:1:
> /usr/include/stdlib.h:673:12: note: in a call to function ‘setenv’ declared
> ‘nonnull’
> 673 | extern int setenv (const char *__name, const char *__value, int
> __replace)
> |^~
> src/main.c:571:17: warning: argument 2 null where non-null expected
> [-Wnonnull]
> 571 | setenv("PREFIX_LEN", NULL, 1);
> | ^~
> /usr/include/stdlib.h:673:12: note: in a call to function ‘setenv’ declared
> ‘nonnull’
> 673 | extern int setenv (const char *__name, const char *__value, int
> __replace)
> |^~
> src/main.c: In function ‘daemonize’:
> src/main.c:844:9: error: implicit declaration of function ‘umask’
> [-Werror=implicit-function-declaration]
> 844 | umask(027);
> | ^
> src/main.c:874:12: error: implicit declaration of function ‘flock’; did you
> mean ‘clock’? [-Werror=implicit-function-declaration]
> 874 | if(flock(pidfile, F_TLOCK, 0) < 0)
> |^
> |clock
> cc1: some warnings being treated as errors
> make[1]: *** [Makefile:26: main.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/03/13/ramond_0.5-4.2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ramond
Source-Version: 0.5-5
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
ramond, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated ramond 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
Bug#1069413: marked as done (rust-coreutils: FTBFS on arm64: make[2]: *** [GNUmakefile:289: test] Error 101)
Your message dated Wed, 01 May 2024 13:37:36 + with message-id and subject line Bug#1069413: fixed in rust-coreutils 0.0.26-1 has caused the Debian Bug report #1069413, regarding rust-coreutils: FTBFS on arm64: make[2]: *** [GNUmakefile:289: test] Error 101 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1069413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-coreutils Version: 0.0.24-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 Hi, During a rebuild of all packages in sid, your package failed to build on arm64. Relevant part (hopefully): > make[2]: Entering directory '/<>' > cargo test --features "base32 base64 basename cat chgrp chmod chown cksum > comm cp csplit cut date dircolors dirname echo env expr factor false fold > hashsum head install link ln ls mkdir mktemp mv nl numfmt od paste pathchk > pinky pr printf ptx pwd readlink realpath rm rmdir seq sort split stat stdbuf > sum tac tail test touch tr true truncate tsort uname unexpand uniq unlink wc > who " --no-default-features > error: failed to select a version for the requirement `uutils_term_grid = > "^0.3"` > candidate versions found which didn't match: 0.6.0 > location searched: directory source `/<>/debian/cargo_registry` > (which is replacing registry `crates-io`) > required by package `uu_ls v0.0.24 (/<>/src/uu/ls)` > perhaps a crate was updated and forgotten to be re-vendored? > make[2]: *** [GNUmakefile:289: test] Error 101 The full build log is available from: http://qa-logs.debian.net/2024/04/20/rust-coreutils_0.0.24-2_unstable-arm64.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240420=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rust-coreutils Source-Version: 0.0.26-1 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of rust-coreutils, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated rust-coreutils 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: Wed, 01 May 2024 14:03:13 +0200 Source: rust-coreutils Architecture: source Version: 0.0.26-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Sylvestre Ledru Closes: 1059268 1067897 1069413 Changes: rust-coreutils (0.0.26-1) unstable; urgency=medium . * New upstream release (Closes: #1067897, #1069413) Adds support for loongarch (Closes: #1059268) * remove librust-failure-dev, librust-failure-derive-dev unused deps * remove help2man from the build deps (not used) Checksums-Sha1: e66efa55e5f9ed9d77e9f1de6a79b5a9ee0ad72f 4837 rust-coreutils_0.0.26-1.dsc bfd2513aff13182cfabef445ee412f67ae03d065 1568984 rust-coreutils_0.0.26.orig.tar.xz d7b0f697aca1125bbd597d4cdae87af52b417368 32076 rust-coreutils_0.0.26-1.debian.tar.xz 909490472ebd4e3b2739ea51baf34603a38fb929 30154 rust-coreutils_0.0.26-1_amd64.buildinfo Checksums-Sha256: bf841a30bd6b44e74175d535bbe84461d16d28731cd6e3f327f949b9fe8d9756 4837 rust-coreutils_0.0.26-1.dsc 7f97d7523759447e20be9638e3fe9cd66461acf7fc179dbaa4d44e6d26128222 1568984 rust-coreutils_0.0.26.orig.tar.xz 899a4934ba84f1a2c8bc9294bb9adf976c94f3ea8be50034f2e93dc4da8a1a5c 32076 rust-coreutils_0.0.26-1.debian.tar.xz
Bug#1067897: marked as done (rust-coreutils - FTBFS with new rust-uutils-term-grid.)
Your message dated Wed, 01 May 2024 13:37:36 +
with message-id
and subject line Bug#1067897: fixed in rust-coreutils 0.0.26-1
has caused the Debian Bug report #1067897,
regarding rust-coreutils - FTBFS with new rust-uutils-term-grid.
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.)
--
1067897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-coreutils
Version: 0.0.24-2
Severity: serious
rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.
After bumping the cargo dependency, the code fails to build with a
bunch of errors.
error[E0432]: unresolved import `term_grid::Cell`
--> src/uu/ls/src/ls.rs:37:17
|
37 | use term_grid::{Cell, Direction, Filling, Grid, GridOptions};
| no `Cell` in the root
|
= help: consider importing one of these items instead:
std::cell::Cell
core::cell::Cell
error[E0063]: missing field `width` in initializer of `GridOptions`
--> src/uu/ls/src/ls.rs:2598:34
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
| ^^^ missing `width`
error[E0061]: this function takes 2 arguments but 1 argument was supplied
--> src/uu/ls/src/ls.rs:2598:24
|
2598 | let mut grid = Grid::new(GridOptions { filling, direction });
|^ -- an
argument of type `Vec<_>` is missing
error[E0599]: no method named `add` found for struct `Grid` in the current scope
--> src/uu/ls/src/ls.rs:2609:18
|
2609 | grid.add(formatted_name);
| ^^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_width` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2612:20
|
2612 | match grid.fit_into_width(width as usize) {
|^^ method not found in `Grid<_>`
error[E0599]: no method named `fit_into_columns` found for struct `Grid` in the
current scope
--> src/uu/ls/src/ls.rs:2618:40
|
2618 | write!(out, "{}", grid.fit_into_columns(1))?;
| method not found in
`Grid<_>`
--- End Message ---
--- Begin Message ---
Source: rust-coreutils
Source-Version: 0.0.26-1
Done: Sylvestre Ledru
We believe that the bug you reported is fixed in the latest version of
rust-coreutils, 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 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sylvestre Ledru (supplier of updated rust-coreutils
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: Wed, 01 May 2024 14:03:13 +0200
Source: rust-coreutils
Architecture: source
Version: 0.0.26-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Sylvestre Ledru
Closes: 1059268 1067897 1069413
Changes:
rust-coreutils (0.0.26-1) unstable; urgency=medium
.
* New upstream release
(Closes: #1067897, #1069413)
Adds support for loongarch (Closes: #1059268)
* remove librust-failure-dev, librust-failure-derive-dev unused deps
* remove help2man from the build deps (not used)
Checksums-Sha1:
e66efa55e5f9ed9d77e9f1de6a79b5a9ee0ad72f 4837 rust-coreutils_0.0.26-1.dsc
bfd2513aff13182cfabef445ee412f67ae03d065 1568984
rust-coreutils_0.0.26.orig.tar.xz
d7b0f697aca1125bbd597d4cdae87af52b417368 32076
rust-coreutils_0.0.26-1.debian.tar.xz
909490472ebd4e3b2739ea51baf34603a38fb929 30154
rust-coreutils_0.0.26-1_amd64.buildinfo
Checksums-Sha256:
bf841a30bd6b44e74175d535bbe84461d16d28731cd6e3f327f949b9fe8d9756 4837
rust-coreutils_0.0.26-1.dsc
7f97d7523759447e20be9638e3fe9cd66461acf7fc179dbaa4d44e6d26128222 1568984
rust-coreutils_0.0.26.orig.tar.xz
899a4934ba84f1a2c8bc9294bb9adf976c94f3ea8be50034f2e93dc4da8a1a5c 32076
rust-coreutils_0.0.26-1.debian.tar.xz
Processed: Re: [Pkg-rust-maintainers] Bug#1019042: rust-qwertone: FTBFS - dep issue
Processing control commands: > severity -1 serious Bug #1019042 [src:qwertone] rust-qwertone: FTBFS - dep issue Severity set to 'serious' from 'important' -- 1019042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1070188 is serious
Processing commands for cont...@bugs.debian.org: > severity 1070188 serious Bug #1070188 [python3-spyder] python3-spyder: uninstallable in unstable due to pylint Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1070188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070186: python3-datalad: Don't recommend python3-boto
Package: python3-datalad Version: 0.19.6-2 Severity: serious Debian Policy § 2.2 says that packages in main (like python3-datalad) are not allowed to have Recommends on packages that are not in main (unless it is only a non-default alternative for a package in main). python3-datalad Recommends: python3-boto but python3-boto has been removed from Testing and will likely be removed from Unstable soon. See https://bugs.debian.org/1058652 The replacement is python3-boto3 but the package will likely need changes to upstream code to work with the new version. Thank you, Jeremy Bícha
Bug#1070184: gnome-maps: Unable to start gnome-maps
Package: gnome-maps Version: 46.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: cqu...@arcor.de I have recently upgraded my Debian testing and it comes with gnome-46.0-1. I am using XFCE 4 desktop and when I try to start gnome-maps nothing happens. From the command line nothing happens, it seems like frozen and after exactly 10 seconds the prompt returns but no window has appeared. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 ii geoclue-2.0 2.7.1-2+b1 ii gir1.2-adw-1 1.5.0-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-3+b3 ii gir1.2-geoclue-2.0 2.7.1-2+b1 ii gir1.2-geocodeglib-2.0 3.26.3-6+b2 ii gir1.2-glib-2.0 [gir1.2-gobject-2.0] 1.78.1-15 ii gir1.2-gtk-4.0 4.12.5+ds-3 ii gir1.2-gweather-4.0 4.4.0-1 ii gir1.2-pango-1.0 1.52.1+ds-1 ii gir1.2-rest-1.0 0.9.1-6+b1 ii gir1.2-secret-1 0.21.4-1+b1 ii gir1.2-shumate-1.0 1.2~beta-3+b1 ii gir1.2-soup-3.0 3.4.4-5+b1 ii gir1.2-xdp-1.0 0.7.1-5+b1 ii gjs 1.79.3-1 ii libc62.37-18 ii libcairo21.18.0-1+b1 ii libglib2.0-0t64 2.78.4-7 ii libglib2.0-bin 2.78.4-7 ii libgtk-4-1 4.12.5+ds-3 ii libjson-glib-1.0-0 1.8.0-2+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpangocairo-1.0-0 1.52.1+ds-1 ii librsvg2-2 2.58.0+dfsg-1 ii libshumate-1.0-1 1.2~beta-3+b1 ii libxml2 2.9.14+dfsg-1.3+b3 gnome-maps recommends no packages. gnome-maps suggests no packages. -- no debconf information
Bug#947039: marked as done (libapache2-mod-auth-pgsql: AuthType Basic configured without corresponding module)
Your message dated Wed, 01 May 2024 12:17:44 + with message-id and subject line Bug#1070165: Removed package(s) from unstable has caused the Debian Bug report #947039, regarding libapache2-mod-auth-pgsql: AuthType Basic configured without corresponding module 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.) -- 947039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libapache2-mod-auth-pgsql Version: 2.0.3-6.1 Severity: serious As far as I can see one of the issues from #666814 has reincarnated the package since Stretch. I could not get the auth module to work at all due to AH01796: AuthType Basic configured without corresponding module Due to the low popcon and auth_dbd being available, I'd assume nobody noticed this at all. -- Bernd Zeimetz Senior Systems Engineer Debian Developer, Palo Alto ACE, RHCE, RHCS-PaaS conova communications GmbH Zentrale Salzburg Karolingerstraße 36a 5020 Salzburg, Austria T +43 662/22 00-313 M +43 676/830 50 313 b.zeim...@conova.com www.conova.com Gesetzliche Pflichtangaben: www.conova.com/impressum www.conova.com/datenschutz smime.p7s Description: S/MIME cryptographic signature --- End Message --- --- Begin Message --- Version: 2.0.3-6.1+rm Dear submitter, as the package libapache2-mod-auth-pgsql has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070165 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1061694: marked as done (gnome-video-arcade: Please stop using libsoup2.4)
Your message dated Wed, 01 May 2024 12:17:15 + with message-id and subject line Bug#1070156: Removed package(s) from unstable has caused the Debian Bug report #1061694, regarding gnome-video-arcade: Please stop using libsoup2.4 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.) -- 1061694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-video-arcade Version: 0.8.8-5 Severity: serious Tags: trixie sid We would like to stop building libsoup2.4 and only use libsoup3 instead. gnome-video-arcade has been archived which means no bug reports, merge requests, or code fixes are being accepted. Maybe we should do like Fedora and remove gnome-video-arcade. Probably lutris and retroarch or MAME itself are better choices. Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 0.8.8-5+rm Dear submitter, as the package gnome-video-arcade has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070156 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1061696: marked as done (gnome-video-arcade: Remove unmaintained package?)
Your message dated Wed, 01 May 2024 12:17:15 + with message-id and subject line Bug#1070156: Removed package(s) from unstable has caused the Debian Bug report #1061696, regarding gnome-video-arcade: Remove unmaintained package? 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.) -- 1061696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-video-arcade Version: 0.8.8-5 Severity: serious X-Debbugs-CC: jo...@debian.org Jordi, what do you think about removing gnome-video-arcade from Debian? See https://bugs.debian.org/1061694 Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 0.8.8-5+rm Dear submitter, as the package gnome-video-arcade has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070156 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1064375: marked as done (rust-gtk: Unmaintained library should not be included in Trixie)
Your message dated Wed, 01 May 2024 12:13:02 + with message-id and subject line Bug#1070092: Removed package(s) from unstable has caused the Debian Bug report #1064375, regarding rust-gtk: Unmaintained library should not be included in Trixie 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.) -- 1064375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-gtk Version: Severity: important Tags: trixie sid Control: block -1 by 1064373 1064374 rust-gtk is no longer maintained upstream. I believe we should not include it in the next Debian Stable release, codenamed Trixie. https://gtk-rs.org/blog/2023/08/28/new-release.html Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 0.18.1-4+rm Dear submitter, as the package rust-gtk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070092 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1066616: marked as done (moonshot-ui: FTBFS: src/moonshot-futils.c:41:34: error: implicit declaration of function ‘getuid’; did you mean ‘getpwuid’? [-Werror=implicit-function-declaration])
Your message dated Wed, 01 May 2024 12:09:52 + with message-id and subject line Bug#1070072: Removed package(s) from unstable has caused the Debian Bug report #1066616, regarding moonshot-ui: FTBFS: src/moonshot-futils.c:41:34: error: implicit declaration of function ‘getuid’; did you mean ‘getpwuid’? [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: moonshot-ui Version: 1.1.0+libsecret~2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount > -I/usr/include/blkid -include config.h -DLOCALEDIR=\""/usr/share/locale"\" > -DMOONSHOT_FLATSTORE_USERS='"/etc/moonshot/flatstore-users"' -I./libmoonshot > -I./libmoonshot -I/usr/include/libsecret-1 -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -pthread > -DMOONSHOT_DBUS_BUS_CONF='"/usr/share/moonshot-ui/dbus/org.janet.Moonshot.conf"' > -DMOONSHOT_DBUS_DAEMON='"/usr/bin/dbus-daemon"' -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O0 -Wall -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c > -o examples/client-client.o `test -f 'examples/client.c' || echo > './'`examples/client.c > src/moonshot-futils.c: In function ‘GetUserName’: > src/moonshot-futils.c:41:34: error: implicit declaration of function > ‘getuid’; did you mean ‘getpwuid’? [-Werror=implicit-function-declaration] >41 |struct passwd *pwd = getpwuid(getuid()); > | ^~ > | getpwuid > examples/client.c:36:5: warning: second argument of ‘main’ should be ‘char > **’ [-Wmain] >36 | int main (intargc, > | ^~~~ > cc1: some warnings being treated as errors > make[4]: *** [Makefile:1645: src/moonshot-moonshot-futils.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/moonshot-ui_1.1.0+libsecret~2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240313=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 1.1.0+libsecret~2+rm Dear submitter, as the package moonshot-ui has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070072 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1068923: marked as done (heat-cfntools: Remove from Debian?)
Your message dated Wed, 01 May 2024 12:07:31 + with message-id and subject line Bug#1070045: Removed package(s) from unstable has caused the Debian Bug report #1068923, regarding heat-cfntools: Remove from Debian? 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.) -- 1068923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: heat-cfntools Version: 1.4.2-4 Severity: serious Control: blocks 1058652 by -1 According to https://launchpad.net/bugs/2052437 "heat-cfntools has officially been retired in the upstream OpenStack project so we should just RM it from the archive" heat-cfntools was already removed from Testing because of https://bugs.debian.org/1058242 Can we file a removal bug for heat-cfntools to allow for the removal of python-boto? Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Version: 1.4.2-4+rm Dear submitter, as the package heat-cfntools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070045 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1069614: marked as done (erfs: no longer functional, should be removed)
Your message dated Wed, 01 May 2024 12:07:03 + with message-id and subject line Bug#1070030: Removed package(s) from unstable has caused the Debian Bug report #1069614, regarding erfs: no longer functional, should be removed 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.) -- 1069614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069614 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: erfs Version: 1.4-1 Severity: important User: debian...@lists.debian.org Usertags: isolation-machine Dear maintainer(s), Your package has an autopkgtest, great. I recently added support for isolation-machine tests on ci.debian.net for amd64 and added your package to the list to use that. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing, but because machine-isolation support by ci.debian.net is new I have not marked this bug as serious (yet). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/packages/e/erfs/testing/amd64/45706002/ 49s autopkgtest [13:48:31]: test upstream-tests: [--- 50s read: Connection reset by peer 50s ERROR: sshfs failed. 50s 1. The volume is already mounted. 50s 2. Wrong SHARE-SECRET. 50s 3. The server can not be reached. 50s autopkgtest [13:48:32]: test upstream-tests: ---] OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 1.4-1+rm Dear submitter, as the package erfs has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070030 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1022392: marked as done (python-ospurge: FTBFS: AttributeError: Mock object has no attribute 'detach_policy_from_cluster')
Your message dated Wed, 01 May 2024 12:08:27 +
with message-id
and subject line Bug#1070061: Removed package(s) from unstable
has caused the Debian Bug report #1022392,
regarding python-ospurge: FTBFS: AttributeError: Mock object has no attribute
'detach_policy_from_cluster'
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.)
--
1022392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ospurge
Version: 2.0.0+2019.10.11.git.990287677b-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2 'ospurge\.tests.*'
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.10
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.10 = disabled ]
> + echo 3.10
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -e .testr.conf ]
> + [ -x /usr/bin/testr-python3 ]
> + TESTR=testr
> + rm -rf .testrepository
> + testr init
> + mktemp -t
> + TEMP_REZ=/tmp/tmp.Unu6GwbI0o
> + + tee /tmp/tmp.Unu6GwbI0o
> PYTHON=python3.10 testr run --parallel --subunit ospurge\.tests.*
> + subunit2pyunit
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
>
Bug#1058242: marked as done (heat-cfntools: FTBFS: ModuleNotFoundError: No module named 'imp')
Your message dated Wed, 01 May 2024 12:07:31 +
with message-id
and subject line Bug#1070045: Removed package(s) from unstable
has caused the Debian Bug report #1058242,
regarding heat-cfntools: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)
--
1058242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heat-cfntools
Version: 1.4.2-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_test --no-py2
> + PKGOS_TEST_PARALLEL=yes
> + PKGOS_TEST_SERIAL=no
> + PYTHONS=disabled
> + PYTHON3S=disabled
> + TEST_PARALLEL_OPT=--parallel
> + TEST_SERIAL_OPT=
> + echo WARNING: --no-py2 is deprecated, and always on.
> WARNING: --no-py2 is deprecated, and always on.
> + shift
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = no ]
> + [ no = yes ]
> + [ 3.12 = disabled ]
> + echo 3.12
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python (python3)
> ===> Testing with python (python3)
> + pwd
> + [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
> + [ -e .stestr.conf ]
> + [ -e .testr.conf ]
> + [ -x /usr/bin/testr-python3 ]
> + TESTR=testr
> + rm -rf .testrepository
> + testr init
> + mktemp -t
> + TEMP_REZ=/tmp/tmp.iGgoleJ75q
> + + tee /tmp/tmp.iGgoleJ75q
> PYTHON=python3.12 testr run --parallel --subunit
> + subunit2pyunit
> runniNon-zero exit code (2) from test listing.
> ng=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60
> ${PYTHON:-python} -m subunit.run discover -t ./ ./heat_cfntools/tests --list
> --- import errors ---
> Failed to import test module: heat_cfntools.tests.test_cfn_helper
> Traceback (most recent call last):
> File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>
> File "/usr/lib/python3.12/unittest/loader.py", line 337, in
> _get_module_from_name
> __import__(name)
> File "/<>/heat_cfntools/tests/test_cfn_helper.py", line 17, in
>
> import boto.cloudformation as cfn
> File "/usr/lib/python3/dist-packages/boto/__init__.py", line 29, in
> import boto.plugin
> File "/usr/lib/python3/dist-packages/boto/plugin.py", line 40, in
> import imp
> ModuleNotFoundError: No module named 'imp'
>
> Failed to import test module: heat_cfntools.tests.test_cfn_hup
> Traceback (most recent call last):
> File "/usr/lib/python3.12/unittest/loader.py", line 394, in _find_test_path
> module = self._get_module_from_name(name)
>
> File "/usr/lib/python3.12/unittest/loader.py", line 337, in
> _get_module_from_name
> __import__(name)
> File "/<>/heat_cfntools/tests/test_cfn_hup.py", line 21, in
>
> from heat_cfntools.cfntools import cfn_helper
> File "/<>/heat_cfntools/cfntools/cfn_helper.py", line 48, in
>
> from boto import cloudformation
> File "/usr/lib/python3/dist-packages/boto/__init__.py", line 29, in
> import boto.plugin
> File "/usr/lib/python3/dist-packages/boto/plugin.py", line 40, in
> import imp
> ModuleNotFoundError: No module named 'imp'
>
> --
> Ran 0 tests in 0.362s
>
> OK
> + cat /tmp/tmp.iGgoleJ75q
> + subunit-filter -s --no-passthrough
> + subunit-stats
> Total tests: 0
> Passed tests: 0
> Failed tests: 0
> Skipped tests: 0
> Seen tags:
> + rm -f /tmp/tmp.iGgoleJ75q
> + testr slowest
> make[1]: *** [debian/rules:25: override_dh_auto_test] Error 3
The full build log is available from:
http://qa-logs.debian.net/2023/12/12/heat-cfntools_1.4.2-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See
Bug#1021924: marked as done (networking-mlnx: FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session.)
Your message dated Wed, 01 May 2024 12:08:00 + with message-id and subject line Bug#1070060: Removed package(s) from unstable has caused the Debian Bug report #1021924, regarding networking-mlnx: FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session. 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.) -- 1021924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: networking-mlnx Version: 1:16.0.0-3 Severity: serious Tags: ftbfs networking-mlnx FTBFS in unstable It appears to be trigger lots of test suite failures and is killed eventually Traceback (most recent call last): File "/<>/networking_mlnx/journal/journal.py", line 91, in run_sync_thread self._sync_progress_rows(context.session) File "/<>/networking_mlnx/journal/journal.py", line 188, in _sync_progress_rows rows = db.get_all_monitoring_db_row_by_oldest(session) File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 140, in wrapped with excutils.save_and_reraise_exception(): File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ self.force_reraise() File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise raise self.value File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 138, in wrapped return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 144, in wrapper with excutils.save_and_reraise_exception() as ectxt: File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ self.force_reraise() File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise raise self.value File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 142, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 186, in wrapped with excutils.save_and_reraise_exception(): File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 227, in __exit__ self.force_reraise() File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 200, in force_reraise raise self.value File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 184, in wrapped return f(*dup_args, **dup_kwargs) File "/<>/networking_mlnx/db/db.py", line 95, in get_all_monitoring_db_row_by_oldest with session.begin(): File "", line 2, in begin File "/usr/lib/python3/dist-packages/sqlalchemy/util/deprecations.py", line 309, in warned return fn(*args, **kwargs) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1327, in begin raise sa_exc.InvalidRequestError( sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session. E: ABORT: Received TERM signal (requesting cleanup and shutdown) Full build log available at https://buildd.debian.org/status/fetch.php?pkg=networking-mlnx=all=1%3A16.0.0-3.1=1665990240=0 --- End Message --- --- Begin Message --- Version: 1:16.0.0-3.1+rm Dear submitter, as the package networking-mlnx has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1070060 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: forward 1069843
Processing commands for cont...@bugs.debian.org: > forwarded 1069843 https://github.com/zarr-developers/zarr-python/issues/1819 Bug #1069843 [src:zarr] zarr: FTBFS: failing tests Set Bug forwarded-to-address to 'https://github.com/zarr-developers/zarr-python/issues/1819'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1069843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1070172: Exception when invoked without options
Package: gcovr
Version: 7.2-1
Severity: grave
Hi,
invoking gcovr 7.2 in an empty directory fails like
$ gcovr
--
GCC Code Coverage Report
Traceback (most recent call last):
File "/usr/bin/gcovr", line 1972, in
print_text_report(covdata)
File "/usr/bin/gcovr", line 822, in print_text_report
OUTPUT.write("Directory: "+options.root+"\n")
~^
TypeError: can only concatenate str (not "NoneType") to str
This makes meson think gcovr is not available, e.g.:
https://gitlab.gnome.org/World/Phosh/phosh-mobile-settings/-/jobs/3839480#L3265
I've marked this as grave as it breaks CI pipelines.
Cheers,
-- Guido
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64
Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gcovr depends on:
ii python33.11.6-1
ii python3-pkg-resources 68.1.2-2
gcovr recommends no packages.
gcovr suggests no packages.
-- no debconf information
Bug#1066703: marked as done (rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’ [-Werror=implicit-function-declaration])
Your message dated Wed, 01 May 2024 10:20:30 + with message-id and subject line Bug#1066703: fixed in rxtx 2.2.0+dfsg-3 has caused the Debian Bug report #1066703, regarding rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’ [-Werror=implicit-function-declaration] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1066703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rxtx Version: 2.2.0+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is most likely caused by a change in dpkg 1.22.6, that enabled -Werror=implicit-function-declaration. For more information, see https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration Relevant part (hopefully): > /bin/bash /<>/libtool --mode=link gcc -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -D_POSIX_SOURCE -D_BSD_SOURCE > -D__need_timespec -Wl,-z,relro -lpthread -release 2.1-7 -o librxtxSerial.la > -rpath /usr/lib/jni /<>/x86_64-pc-linux-gnu/SerialImp.lo; > \ > fi; \ > ) > libtool: compile: gcc -I/<> -Ix86_64-pc-linux-gnu -I. > -I/usr/lib/jvm/java-17-openjdk-amd64/include > -I/usr/lib/jvm/java-17-openjdk-amd64/include/./linux/ -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -D_POSIX_SOURCE -D_BSD_SOURCE -D__need_timespec -c > /<>/./src/SerialImp.c -fPIC -DPIC -o > /<>/x86_64-pc-linux-gnu/.libs/SerialImp.o > In file included from > /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, > from /usr/include/stdio.h:27, > from /usr/lib/jvm/java-17-openjdk-amd64/include/jni.h:39, > from ./gnu_io_RXTXPort.h:2, > from /<>/./src/SerialImp.c:64: > /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > /<>/./src/SerialImp.c: In function ‘uucp_lock’: > /<>/./src/SerialImp.c:5453:23: error: implicit declaration of > function ‘major’ [-Werror=implicit-function-declaration] > 5453 | (int) major( buf.st_dev ), > | ^ > /<>/./src/SerialImp.c:5455:23: error: implicit declaration of > function ‘minor’ [-Werror=implicit-function-declaration] > 5455 | (int) minor( buf.st_rdev ) > | ^ > /<>/./src/SerialImp.c: In function ‘is_device_locked’: > /<>/./src/SerialImp.c:5863:33: error: implicit declaration of > function ‘asprintf’; did you mean ‘vsprintf’? > [-Werror=implicit-function-declaration] > 5863 | asprintf( , "%s/%s%s", > lockdirs[i], > | ^~~~ > | vsprintf > /<>/./src/SerialImp.c: In function ‘fhs_lock’: > /<>/./src/SerialImp.c:5377:9: warning: ignoring return value of > ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] > 5377 | write( fd, lockinfo, 11 ); > | ^ > /<>/./src/SerialImp.c: In function ‘uucp_lock’: > /<>/./src/SerialImp.c:5475:9: warning: ignoring return value of > ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result] > 5475 | write( fd, lockinfo,11 ); > | ^~~~ > /<>/./src/SerialImp.c: In function ‘is_device_locked’: > /<>/./src/SerialImp.c:5940:17: warning: ignoring return value of > ‘read’ declared with attribute ‘warn_unused_result’ [-Wunused-result] > 5940 | read( fd, pid_buffer, 11 ); > | ^~ > /<>/./src/SerialImp.c: In function > ‘Java_gnu_io_RXTXCommDriver_registerKnownPorts’: > /<>/./src/SerialImp.c:4676:43: warning: ‘ handed to > native RXTXCo...’ directive writing 71 bytes into a region of > size between 52 and 62 [-Wformat-overflow=] > 4676 |
Processed: Bug#1066703 marked as pending in rxtx
Processing control commands: > tag -1 pending Bug #1066703 [src:rxtx] rxtx: FTBFS: SerialImp.c:5453:23: error: implicit declaration of function ‘major’ [-Werror=implicit-function-declaration] Added tag(s) pending. -- 1066703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1066703: marked as pending in rxtx
Control: tag -1 pending Hello, Bug #1066703 in rxtx 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/java-team/rxtx/-/commit/b52594e793ffaaf62c3f36f9d5c85f753e78ac40 Fix building with -Werror=implicit-function-declaration (Closes: #1066703) (this message was generated automatically) -- Greetings https://bugs.debian.org/1066703
Processed: reassign 1070102 to src:llvm-toolchain-14, reassign 1055324 to src:libdmapsharing ...
Processing commands for cont...@bugs.debian.org:
> reassign 1070102 src:llvm-toolchain-14 1:14.0.6-12
Bug #1070102 [src:llm-toolchain-14] Requesting patch for llvm-toolchain-14
Warning: Unknown package 'src:llm-toolchain-14'
Bug reassigned from package 'src:llm-toolchain-14' to 'src:llvm-toolchain-14'.
No longer marked as found in versions llm-toolchain-14/1:14.0.6-12.
Ignoring request to alter fixed versions of bug #1070102 to the same values
previously set
Bug #1070102 [src:llvm-toolchain-14] Requesting patch for llvm-toolchain-14
Marked as found in versions llvm-toolchain-14/1:14.0.6-12.
> reassign 1055324 src:libdmapsharing 3.9.13-1
Bug #1055324 [libdmapsharing-4.0-3] libdmapsharing-4.0-3: tries to write to
/build on end-user systems
Warning: Unknown package 'libdmapsharing-4.0-3'
Bug reassigned from package 'libdmapsharing-4.0-3' to 'src:libdmapsharing'.
No longer marked as found in versions libdmapsharing/3.9.13-1.
Ignoring request to alter fixed versions of bug #1055324 to the same values
previously set
Bug #1055324 [src:libdmapsharing] libdmapsharing-4.0-3: tries to write to
/build on end-user systems
Marked as found in versions libdmapsharing/3.9.13-1.
> found 1060951 1.78.1-17
Bug #1060951 [src:gobject-introspection] Build regression in multiarch
g-ir-scanner
Marked as found in versions gobject-introspection/1.78.1-17.
> tags 1060951 - sid trixie
Bug #1060951 [src:gobject-introspection] Build regression in multiarch
g-ir-scanner
Removed tag(s) trixie and sid.
> tags 1064373 - sid trixie
Bug #1064373 [src:squeekboard] squeekboard: Depends on obsolete rust-gtk
Removed tag(s) trixie and sid.
> tags 1069983 + experimental
Bug #1069983 [src:dwarf-fortress] dwarf-fortress: Manual build-depends on NBS
package libgtk2.0-0
Added tag(s) experimental.
> found 1069983 0.47.05+dfsg1-1
Bug #1069983 [src:dwarf-fortress] dwarf-fortress: Manual build-depends on NBS
package libgtk2.0-0
Marked as found in versions dwarf-fortress/0.47.05+dfsg1-1.
> tags 1069984 - sid trixie
Bug #1069984 [src:alire] alire: Build-depends on NBS package libgnatcoll21-dev
Removed tag(s) trixie and sid.
> tags 1069518 - sid trixie
Bug #1069518 {Done: Stuart Prescott } [src:projecteur]
projecteur: FTBFS on armhf: deviceinput.cc:697:64: error: narrowing conversion
of ‘(int32_t)ie.DeviceInputEvent::value’ from ‘int32_t’ {aka ‘int’} to ‘__u16’
{aka ‘short unsigned int’} [-Werror=narrowing]
Removed tag(s) trixie and sid.
> tags 1070062 + sid trixie
Bug #1070062 [src:waylandpp] waylandpp: Missing build-depends
libwayland-egl1-mesa
Added tag(s) sid and trixie.
> notfound 1064808 2.13.0+~2.11.0-1
Bug #1064808 {Done: Salvatore Bonaccorso }
[src:node-sanitize-html] node-sanitize-html: CVE-2024-21501
No longer marked as found in versions node-sanitize-html/2.13.0+~2.11.0-1.
> tags 1015583 + experimental
Bug #1015583 {Done: Patrick Franz } [src:plasma-framework]
plasma-framework: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015677 + experimental
Bug #1015677 {Done: Patrick Franz } [src:syndication]
syndication: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015465 + experimental
Bug #1015465 {Done: Patrick Franz } [src:kwallet-kf5]
kwallet-kf5: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015463 + experimental
Bug #1015463 {Done: Patrick Franz } [src:ktexteditor]
ktexteditor: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015460 + experimental
Bug #1015460 {Done: Patrick Franz } [src:kross] kross:
ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015455 + experimental
Bug #1015455 {Done: Patrick Franz } [src:kjsembed]
kjsembed: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015453 + experimental
Bug #1015453 {Done: Patrick Franz } [src:kirigami2]
kirigami2: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015452 + experimental
Bug #1015452 {Done: Patrick Franz } [src:kio] kio: ftbfs
with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015454 + experimental
Bug #1015454 {Done: Patrick Franz } [src:kjs] kjs: ftbfs
with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015456 + experimental
Bug #1015456 {Done: Patrick Franz } [src:knewstuff]
knewstuff: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015451 + experimental
Bug #1015451 {Done: Patrick Franz } [src:khtml] khtml:
ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015446 + experimental
Bug #1015446 {Done: Patrick Franz } [src:kdelibs4support]
kdelibs4support: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
> tags 1015443 + experimental
Bug #1015443 {Done: Patrick Franz } [src:kdeclarative]
kdeclarative: ftbfs with LTO (link time optimization) enabled
Added tag(s) experimental.
>
Bug#1069945: Acknowledgement (rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io')
On 29/04/2024 09.59, Andreas Beckmann wrote: A possible solution (which also handles all kernels that got the patch Merged in dm-writeboost as https://github.com/akiradeveloper/dm-writeboost/commit/1967beb97d63044043383721759c8928bc6353c6 Andreas
