Processed: tag forwarded

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1052824 https://github.com/flycheck/flycheck/issues/2036
Bug #1052824 [src:flycheck] flycheck: FTBFS if gawk is installed
Ignoring request to change the forwarded-to-address of bug#1052824 to the same 
value
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052744: marked as done (snek: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for this target)

[Debian Bug Tracking System]

Your message dated Wed, 27 Sep 2023 05:35:56 +
with message-id 
and subject line Bug#1052744: fixed in snek 1.9-2
has caused the Debian Bug report #1052744,
regarding snek: FTBFS: cc1: error: ‘-fcf-protection=full’ is not supported for 
this target
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.)


-- 
1052744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snek
Version: 1.9-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/ports/itsybitsy5v'
> lola -DSNEK_SLICE -DSNEK_DICT -o snek-gram.h ../../snek-gram.ll
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-gpio.builtin ../../snek-eeprom.builtin 
> ../../chips/avr/snek-avr.builtin ../itsybitsy5v/snek-itsybitsy5v.builtin -o 
> snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-gpio.builtin ../../snek-eeprom.builtin 
> ../../chips/samd21/snek-altos.builtin ../../snek-math.builtin 
> ../../snek-input.builtin snek-crickit.builtin -o snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-eeprom.builtin ../../snek-gpio.builtin 
> ../../chips/atmega/snek-atmega.builtin snek-grove.builtin 
> ../../chips/atmega/snek-328p.builtin ../../snek-draw.builtin -o snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-gpio.builtin ../../snek-eeprom.builtin 
> ../../chips/samd21/snek-altos.builtin ../../snek-math.builtin 
> ../../snek-input.builtin snek-feather.builtin -o snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-eeprom.builtin ../../snek-gpio.builtin 
> ../../chips/atmega/snek-atmega.builtin ../../snek-input.builtin 
> ../../chips/atmega/snek-328p.builtin -o snek-builtin.h
> python3 ../../ao/make-product.py -v 1.9 -p SnekItsyBitsy3v > ao-product.h
> python3 ../../ao/make-product.py -i 0x002c -V 0xfffe -v 1.9 -p SnekCrickit > 
> ao-product.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-eeprom.builtin ../../snek-gpio.builtin 
> ../../chips/atmega/snek-atmega.builtin ../../chips/atmega/snek-328p.builtin 
> -o snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin snek-ev3.builtin ../../snek-math.builtin 
> ../../snek-eeprom.builtin ../../snek-input.builtin -o snek-builtin.h
> python3 ../../snek-builtin.py ../../snek-keyword.builtin 
> ../../snek-base.builtin ../../snek-gpio.builtin ../../snek-eeprom.builtin 
> ../../chips/avr/snek-avr.builtin ../itsybitsy5v/snek-itsybitsy5v.builtin -o 
> snek-builtin.h
> avr-gcc -c -DF_CPU=800UL -mmcu=atmega32u4 -g 
> -fdebug-prefix-map=/<>=. -Wall -Wcast-align -Wextra 
> -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes 
> -Wmissing-declarations -Wnested-externs -Wshadow -D_DEFAULT_SOURCE  -I../..  
> -DSNEK_VERSION='"1.9"' -DSNEK_NO_FILE -Waddr-space-convert -I. 
> -I../itsybitsy5v -I../../chips/avr -I../../ao -I../.. -std=c99 -Os 
> -frename-registers -funsigned-char -fno-jump-tables -mcall-prologues -g 
> -fdebug-prefix-map=/<>=. -Wall -Wcast-align -Wextra 
> -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes 
> -Wmissing-declarations -Wnested-externs -Wshadow -D_DEFAULT_SOURCE  -I../..  
> -DSNEK_VERSION='"1.9"' -DSNEK_NO_FILE -o snek-builtin.o ../../snek-builtin.c
> arm-none-eabi-gcc -c -mlittle-endian -mcpu=cortex-m0 -mthumb 
> -I../../chips/samd21 -I../../ao -I../.. -I. -std=c18 -Os -g 
> -specs=picolibc.specs -DPICOLIBC_FLOAT_PRINTF_SCANF 
> -fdebug-prefix-map=/<>=. -Wall -Wcast-align -Wextra 
> -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes 
> -Wmissing-declarations -Wnested-externs -Wshadow -Wimplicit-fallthrough 
> -D_DEFAULT_SOURCE  -I../..  -DSNEK_VERSION='"1.9"' -o snek-builtin.o 
> ../../snek-builtin.c
> python3 ../../ao/make-product.py -i 0x8022 -V 0x239A -v 1.9 -p SnekFeather > 
> ao-product.h
> sed -e 's;@ICONDIR@;/usr/share/icons/hicolor/scalable/apps;g' -e 
> 's;@BINDIR@;/usr/bin;g' -e 's;@SNEKLIB@;/usr/share/snek;' -e 
> 's;@SHAREDIR@;/usr/share/snek;' -e 's/@SNEK_VERSION@/1.9/' -e 
> 's/@SNEK_VERSION_DASH@/1-9/' -e 's;@SNEK_ROOT@;../..;' -e 
> 's/@SNEK_DATE@/2022-12-20/' snek-grove-install.in > 

Processed: limit source to gnustep-base, tagging 1052840

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source gnustep-base
Limiting to bugs with field 'source' containing at least one of 'gnustep-base'
Limit currently set to 'source':'gnustep-base'

> tags 1052840 + pending
Bug #1052840 [src:gnustep-base] gnustep-base: FTBFS: dh_auto_test: error: make 
-j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit 
code 2
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1051909: marked as done (ring: FTBFS: error: using typedef-name ‘using dht::Logger = struct dht::log::Logger’ after ‘struct’)

[Debian Bug Tracking System]

Your message dated Wed, 27 Sep 2023 04:19:34 +
with message-id 
and subject line Bug#1051909: fixed in ring 20230922.0~ds1-1
has caused the Debian Bug report #1051909,
regarding ring: FTBFS: error: using typedef-name ‘using dht::Logger = struct 
dht::log::Logger’ after ‘struct’
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.)


-- 
1051909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ring
Version: 20230206.0~ds2-1.3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

ring fails to build from source. From my build log on amd64:

| /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -std=gnu++17 
-DHAVE_CONFIG_H -I. -I..  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-fvisibility=hidden -DLIBJAMI_BUILD -DASIO_STANDALONE 
-I/<>/daemon/contrib/x86_64-linux-gnu/include  -DPJ_AUTOCONF=1 
-I/usr/include/jsoncpp  -I/<>/daemon/src 
-I/<>/daemon/src/config -I/<>/daemon/src/media 
-I/<>/daemon/test -I/<>/daemon/src/jami  
-DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE 
-DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 
-DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 
-O3 -Wno-deprecated -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -MT client/conversation_interface.lo -MD -MP -MF 
$depbase.Tpo -c -o client/conversation_interface.lo 
client/conversation_interface.cpp &&\
| mv -f $depbase.Tpo $depbase.Plo
| make[4]: *** [Makefile:2669: account_factory.lo] Error 1
| make[4]: *** Waiting for unfinished jobs
| libtool: compile:  g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I.. 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD 
-DASIO_STANDALONE "-I/<>/daemon/contrib/x86_64-linux-gnu/include" 
-DPJ_AUTOCONF=1 -I/usr/include/jsoncpp "-I/<>/daemon/src" 
"-I/<>/daemon/src/config" "-I/<>/daemon/src/media" 
"-I/<>/daemon/test" "-I/<>/daemon/src/jami" 
-DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE 
-DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 
-DPJ_AUTOCONF=1 -I../src/jamidht/eth -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG=1 
-O3 -Wno-deprecated -g -O2 "-ffile-prefix-map=/<>=." 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -MT client/conversation_interface.lo -MD -MP -MF 
client/.deps/conversation_interface.Tpo -c client/conversation_interface.cpp -o 
client/conversation_interface.o
| make[4]: *** [Makefile:2669: call.lo] Error 1
| make[4]: *** [Makefile:2669: manager.lo] Error 1
| make[4]: *** [Makefile:2669: conference.lo] Error 1
| In file included from ./jamidht/account_manager.h:28,
|  from ./jamidht/conversation_module.h:25,
|  from ./jamidht/jamiaccount.h:49,
|  from client/datatransfer.cpp:26:
| ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logger 
= struct dht::log::Logger’ after ‘struct’
|43 | struct Logger;
|   |^~
| In file included from /usr/include/opendht/dhtrunner.h:28,
|  from ./connectivity/connectionmanager.h:24,
|  from ./jamidht/jamiaccount.h:46:
| /usr/include/opendht/logger.h:117:7: note: ‘using dht::Logger = struct 
dht::log::Logger’ has a previous declaration here
|   117 | using Logger = log::Logger;
|   |   ^~
| In file included from ./jamidht/account_manager.h:28,
|  from ./jamidht/conversation_module.h:25,
|  from ./jamidht/jamiaccount.h:49,
|  from client/configurationmanager.cpp:39:
| ./jamidht/namedirectory.h:43:8: error: using typedef-name ‘using dht::Logger 
= struct dht::log::Logger’ after ‘struct’
|43 | struct Logger;
|   |^~
| In file included from /usr/include/opendht/dhtrunner.h:28,
|  from ./connectivity/connectionmanager.h:24,
|  from ./jamidht/jamiaccount.h:46:
| /usr/include/opendht/logger.h:117:7: note: ‘using dht::Logger = struct 
dht::log::Logger’ has a previous declaration here
|   117 | using Logger = log::Logger;
|   |   ^~
| In file included from ./jamidht/account_manager.h:28,
|  from ./jamidht/conversation_module.h:25,
|  from ./jamidht/jamiaccount.h:49,
|  

Bug#1053090: libxsimd-dev: arm64 error in xtensor: usage of batch type with unsupported type

[Drew Parsons]

Package: libxsimd-dev
Version: 10.0.0-3
Severity: serious
Justification: debci

libxsimd-dev 10 triggers an error in xtensor tests on arm64
xsimd passes its own tests, and xtensor passes on other arches (except
armel which has known issues)

The error output from
https://ci.debian.net/data/autopkgtest/unstable/arm64/x/xtensor/38197207/log.gz
is

127s [ 26%] Building CXX object 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly.cpp.o
127s /usr/bin/g++ -DXSIMD_ENABLE_XTL_COMPLEX -DXTENSOR_USE_XSIMD  
-DXSIMD_ENABLE_XTL_COMPLEX=1 -march=native -std=c++14 -Wunused-parameter 
-Wextra -Wreorder -Wconversion -Wno-sign-conversion  -Wold-style-cast 
-Wunused-variable -ftemplate-backtrace-limit=0 -O3 -DNDEBUG -MD -MT 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly.cpp.o -MF 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly.cpp.o.d -o 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly.cpp.o -c 
/tmp/autopkgtest-lxc.1p570fd4/downtmp/autopkgtest_tmp/test_xoptional_assembly.cpp
131s In file included from /usr/include/xsimd/types/xsimd_batch.hpp:493,
131s  from /usr/include/xsimd/xsimd.hpp:61,
131s  from /usr/include/xtensor/xtensor_config.hpp:61,
131s  from /usr/include/xtensor/xexception.hpp:24,
131s  from /usr/include/xtensor/xstorage.hpp:21,
131s  from /usr/include/xtensor/xbuffer_adaptor.hpp:21,
131s  from /usr/include/xtensor/xarray.hpp:19,
131s  from 
/tmp/autopkgtest-lxc.1p570fd4/downtmp/autopkgtest_tmp/test_xoperation.cpp:13:
131s /usr/include/xsimd/types/xsimd_traits.hpp: In instantiation of ‘struct 
xsimd::detail::static_check_supported_config_emitter’:
131s /usr/include/xsimd/types/xsimd_traits.hpp:84:19:   required from ‘void 
xsimd::detail::static_check_supported_config() [with T = bool; A = 
xsimd::neon64]’
131s /usr/include/xsimd/types/xsimd_api.hpp:437:55:   required from 
‘xsimd::simd_return_type xsimd::broadcast_as(From) [with To = int; 
A = neon64; From = bool; simd_return_type = batch_bool]’
131s /usr/include/xtensor/xscalar.hpp:952:53:   required from 
‘xt_simd::simd_return_type 
>::value_type, requested_type> xt::xscalar::load_simd(size_type) const 
[with align = xt::inner_aligned_mode; requested_type = int; long unsigned int N 
= 4; CT = bool; xt_simd::simd_return_type >::value_type, requested_type> = 
xsimd::batch_bool; typename 
xt::xcontainer_inner_types >::value_type = bool; size_type = 
long unsigned int]’
...
131s /usr/include/xtensor/xarray.hpp:510:30:   required from 
‘xt::xarray_container::xarray_container(const 
xt::xexpression&) [with E = xt::xfunction >, 
xt::layout_type::row_major, xt::svector, true>, xt::xtensor_expression_tag>&, 
xt::xscalar >; EC = xt::uvector 
>; xt::layout_type L = xt::layout_type::row_major; SC = xt::svector, true>; Tag = 
xt::xtensor_expression_tag]’
131s 
/tmp/autopkgtest-lxc.1p570fd4/downtmp/autopkgtest_tmp/test_xoperation.cpp:378:28:
   required from ‘void xt::DOCTEST_ANON_SUITE_131::DOCTEST_ANON_TMP_150() [with 
TypeParam = xt::xarray_container >, xt::layout_type::row_major, 
xt::svector, true>, 
xt::xtensor_expression_tag>]’
131s 
/tmp/autopkgtest-lxc.1p570fd4/downtmp/autopkgtest_tmp/test_xoperation.cpp:372:9:
   required from 
‘xt::DOCTEST_ANON_SUITE_131::{anonymous}::DOCTEST_ANON_TMP_150ITERATOR >::DOCTEST_ANON_TMP_150ITERATOR(const char*, unsigned int, int) [with 
Type = xt::xarray_container >, xt::layout_type::row_major, 
xt::svector, true>, 
xt::xtensor_expression_tag>; Rest = {xt::xtensor_container >, 2, xt::layout_type::row_major, 
xt::xtensor_expression_tag>}]’
131s 
/tmp/autopkgtest-lxc.1p570fd4/downtmp/autopkgtest_tmp/test_xoperation.cpp:372:9:
   required from here
131s /usr/include/xsimd/types/xsimd_traits.hpp:64:43: error: static assertion 
failed: usage of batch type with unsupported type
131s64 | static_assert(!A::supported() || 
xsimd::has_simd_register::value,
131s   |   
^~~~
131s /usr/include/xsimd/types/xsimd_traits.hpp:64:43: note: ‘((! 
xsimd::neon64::supported()) || ((bool)std::integral_constant::value))’ evaluates to false


Since xsimd passes it's own test, this might be a bug in xtensor.
Filing against libxsimd-dev to pause migration to testing.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

libxsimd-dev depends on no packages.

libxsimd-dev recommends no packages.

Versions of packages libxsimd-dev suggests:
ii  libxsimd-doc  

Bug#1053089: lxdm: LXDM boots to a blank black screen with no options

[VastOne]

Package: lxdm
Version: 0.5.3-5
Severity: critical
Justification: breaks the whole system




-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxdm depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  gtk2-engines   1:2.20.2-5+b1
ii  gtk2-engines-pixbuf2.24.33-2
ii  iso-codes  4.15.0-1
ii  libc6  2.37-10
ii  libcairo2  1.18.0-1
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1
ii  libglib2.0-0   2.78.0-2
ii  libgtk-3-0 3.24.38-5
ii  libpam-modules 1.5.2-7
ii  libpam-runtime 1.5.2-7
ii  libpam0g   1.5.2-7
ii  libpango-1.0-0 1.51.0+ds-2
ii  libpangocairo-1.0-01.51.0+ds-2
ii  librsvg2-common2.54.7+dfsg-2
ii  libx11-6   2:1.8.6-1
ii  libxcb11.15-1
ii  x11-utils  7.7+5

Versions of packages lxdm recommends:
pn  desktop-base  

Versions of packages lxdm suggests:
pn  lxde-common  

-- Configuration Files:
/etc/lxdm/lxdm.conf [Errno 13] Permission denied: '/etc/lxdm/lxdm.conf'

-- debconf information:
* shared/default-x-display-manager: lxdm

Bug#1052745: marked as done (ruby-guard: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: expect(@output).to eq result)

[Debian Bug Tracking System]

Your message dated Wed, 27 Sep 2023 10:28:27 +0900
with message-id 
and subject line Re: [DRE-maint] Bug#1052745: ruby-guard: FTBFS: ERROR: Test 
"ruby3.1" failed: Failure/Error: expect(@output).to eq result
has caused the Debian Bug report #1052745,
regarding ruby-guard: FTBFS: ERROR: Test "ruby3.1" failed:  Failure/Error: 
expect(@output).to eq result
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.)


-- 
1052745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-guard
Version: 2.18.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  Failure/Error: expect(@output).to eq result
> 
>expected: "  +-+---+\n  | Plugin  | Guardfile |\n  
> +-+---+\n  | Another | ✔...   | ✘ |\n  | More
> | ✘ |\n  | Test| ✔ |\n  +-+---+\n"
> got: "  +-+---+\n  | Plugin  | Guardfile |\n  
> +-+---+\n  | Another | ✔...en| ✘|\n  | More   
>  | ✘|\n  | Test| ✔|\n  +-+---+\n"
> 
>(compared using ==)
> 
>Diff:
>@@ -1,9 +1,9 @@
>   +-+---+
>   | Plugin  | Guardfile |
>   +-+---+
>-  | Another | ✔ |
>-  | Even| ✘ |
>-  | More| ✘ |
>-  | Test| ✔ |
>+  | Another | ✔|
>+  | Even| ✘|
>+  | More| ✘|
>+  | Test| ✔|
>   +-+---+
>  # ./spec/lib/guard/dsl_describer_spec.rb:75:in `block (3 levels) in  (required)>'
> 
> Finished in 14.23 seconds (files took 0.69417 seconds to load)
> 456 examples, 1 failure, 1 pending
> 
> Failed examples:
> 
> rspec ./spec/lib/guard/dsl_describer_spec.rb:73 # Guard::DslDescriber#list 
> lists the available Guards declared as strings or symbols
> 
> Randomized with seed 8058
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/ruby-guard_2.18.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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 ---
Package: ruby-guard
Version: 2.18.1-2

fixed with just-quick-fix.

ignore unicode emoji ambiguous whitespaces with formatador 0.3+ 
https://salsa.debian.org/ruby-team/ruby-guard/-/commit/c6d8b2de51df1dbcf42d2ce1df706ef4f2b4a1d2

See also:

* https://github.com/guard/guard/pull/986#issuecomment-1303991720
* https://github.com/geemus/formatador/pull/26
* 
https://github.com/hamano/locale-eaw#%E7%B5%B5%E6%96%87%E5%AD%97%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6
 (in Japanese)
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature
--- End Message ---

Bug#1042911: (Still?) breaks Emacs 29.1 unattended-upgrade

[Manphiz]

Farblos  writes:

> Packages that attempted to upgrade:
>  [..snip..]
>  elpa-muse elpa-org emacs-bin-common emacs-common
>  emacs-common-non-dfsg emacs-el emacs-lucid
>  [..snip..]
>
> Packages with upgradable origin but kept back:
>  Debian testing:
>  [..snip..]
>   elpa-muse
>  [..snip..]
>
> Package installation log:
>  [..snip..]
> 
> In toplevel form:
> muse-split.el:41:2: Error: Cannot open load file: No such file or directory, 
> assoc
>

So, unattended-upgrades decided to keep back elpa-muse, therefore when
byte-compiling it was still attempting to handle the old 3.20+dfsg-7,
and hence failed with the same error when byte-compiling on Emacs 29+.

So it's curious that elpa-muse was kept back given that it doesn't
introduce new dependencies.  I wonder whether this is because of
`Unattended-Upgrade::MinimalSteps "true"', which just divide the
upgrades into smaller batch and elpa-muse didn't make it to the same
batch as Emacs unfortunately.

-- 
Manphiz

Bug#1053010: node-jss_10.10.0+ds1+~0.3.1-3_all-buildd.changes REJECTED

[Aurelien Jarno]

Package: node-jss
Version: 10.10.0+ds1+~0.3.1-3
Severity: serious

On 2023-09-26 16:19, Debian FTP Masters wrote:
> 
> 
> Version check failed:
> Your upload included the binary package node-css-initials, version 0.3.1~, 
> for all,
> however unstable already has version 0.3.1~.
> Uploads to unstable must have a higher version than present in unstable.
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

Bug#1042911: (Still?) breaks Emacs 29.1 unattended-upgrade

[Farblos]

On 2023-09-19  19:50, Nicholas D Steeves wrote:
> On Fri, 15 Sep 2023 14:35:08 +0200 "Farblos"  
> wrote:
>> Not sure whether this is still relevant or just bad luck or whatever ... my
>> unattended-upgrade failed today because of this issue.  Logs available
>> on request.  Work-around was to remove version 3.20+dfsg-7, retrigger
>> the unattended upgrade, install version 3.20+dfsg-8.
> 
> So 3.20+dfsg-7 is broken by emacs29 such that it can only be
> uninstalled, and not upgraded.  I'm confident that your logs will show
> that the -7 is unpacked but no longer configured.

I finally found the time to double-check the logs (attached if you're
interested).  I think with unattended upgrades ("u-u") the situation is
a bit different, but I'm by no means an expert here.  U-u by default is
configured to do minimal bits of installation, and AFAIU the logs, u-u
therefore attempts to upgrade emacs-common while -7 is still fully
installed.  Which fails, for reasons described earlier in this report.

Anyway, there is probably nothing that could be done about that, so
just leaving the information here for others to find.
X-Gnus-Coding-System: -*- coding: utf-8; -*-

Unattended upgrade result: All upgrades installed

Warning: A reboot is required to complete this upgrade, or a previous one.

Packages that attempted to upgrade:
 accountsservice apparmor apparmor-utils aspell at-spi2-common binutils
 binutils-common binutils-x86-64-linux-gnu bluetooth bluez bpftool
 bsdextrautils bsdutils cpp cpp-12 cpp-13 cron cron-daemon-common
 cryptsetup cryptsetup-bin cryptsetup-initramfs curl dbus dbus-bin
 dbus-daemon dbus-session-bus-common dbus-system-bus-common
 dbus-user-session debhelper debianutils dictionaries-common dmidecode
 dos2unix dpkg dpkg-dev e2fsprogs elpa-muse elpa-org emacs-bin-common
 emacs-common emacs-common-non-dfsg emacs-el emacs-lucid fdisk file
 firefox-esr firmware-linux-free fontconfig fontconfig-config
 fonts-opensymbol fwupd g++ g++-13 gcc gcc-12 gcc-12-base gcc-13
 gcc-13-base gettext gettext-base gir1.2-atk-1.0 gir1.2-fprint-2.0
 gir1.2-freedesktop gir1.2-glib-2.0 gir1.2-gtk-3.0 gir1.2-ibus-1.0
 gir1.2-pango-1.0 grep gsettings-desktop-schemas gtk-update-icon-cache
 ibus ibus-data inetutils-telnet inetutils-traceroute
 intel-media-va-driver jq kmod libaccountsservice0 libaom3
 libapparmor1 libasan8 libasound2 libasound2-data libaspell15
 libatk-bridge2.0-0 libatk1.0-0 libatomic1 libatopology2 libatspi2.0-0
 libavcodec60 libavdevice60 libavfilter9 libavformat60 libavutil58
 libbabeltrace1 libbinutils libblkid1 libblockdev-crypto3
 libblockdev-fs3 libblockdev-loop3 libblockdev-mdraid3
 libblockdev-nvme3 libblockdev-part3 libblockdev-swap3
 libblockdev-utils3 libblockdev3 libbluetooth3 libbrlapi0.8 libc++1-15
 libc++abi1-15 libcaca0 libcairo-gobject2 libcairo2 libcc1-0
 libcom-err2 libcryptsetup12 libctf-nobfd0 libctf0 libcurl3-gnutls
 libcurl4 libdbus-1-3 libdbusmenu-glib4 libdbusmenu-gtk3-4
 libdebhelper-perl libdpkg-perl libedit2 libegl-mesa0 libext2fs2
 libfdisk1 libfontconfig1 libfprint-2-2 libfreetype6 libfwupd2 libgbm1
 libgcc-12-dev libgcc-13-dev libgcc-s1 libgccjit0 libgfortran5
 libgirepository-1.0-1 libgl1-mesa-dri libglapi-mesa libglib2.0-0
 libglib2.0-data libglx-mesa0 libgnutls30 libgomp1 libgprofng0
 libgstreamer-plugins-base1.0-0 libgstreamer1.0-0 libgtk-3-0
 libgtk-3-common libhwasan0 libhwy1 libibus-1.0-5 libidn2-0
 libigdgmm12 libimlib2 libitm1 libjq1 libjson-c5 libkmod2 libldb2
 liblerc4 liblibreoffice-java libllvm15 liblmdb0 liblsan0 liblzma5
 libm17n-0 libmagic-mgc libmagic1 libmbedcrypto7 libmount1 libmujs3
 libnet-http-perl libnetfilter-conntrack3 libnghttp2-14 libnm0 libnss3
 libonig5 libopenmpt0 libpam-modules libpam-modules-bin libpam-runtime
 libpam-systemd libpam0g libpango-1.0-0 libpangocairo-1.0-0
 libpangoft2-1.0-0 libpangoxft-1.0-0 libpcap0.8 libpcre2-32-0
 libpcre2-8-0 libpipewire-0.3-0 libplacebo292 libpmem1 libpostproc57
 libpsl5 libpython3.11 libpython3.11-minimal libpython3.11-stdlib
 libqpdf29 libquadmath0 libreoffice-base-core libreoffice-calc
 libreoffice-common libreoffice-core libreoffice-draw libreoffice-gtk3
 libreoffice-help-common libreoffice-help-en-us libreoffice-impress
 libreoffice-java-common libreoffice-style-colibre libreoffice-writer
 librubberband2 libsamplerate0 libsdl2-2.0-0 libsecret-1-0
 libsecret-common libsensors-config libsensors5 libsframe1
 libsmartcols1 libsmbclient libsndfile1 libspa-0.2-modules
 libsqlite3-0 libss2 libssh-4 libssh-gcrypt-4 libstdc++-13-dev
 libstdc++6 libswresample4 libswscale7 libsysfs2 libsystemd-shared
 libsystemd0 libtomcrypt1 libtsan2 libubsan1 libudev1 libuno-cppu3
 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
 libuno-salhelpergcc3-3 libunoloader-java libunwind-15 liburi-perl
 libuuid1 libv4l-0 libv4l2rds0 libv4lconvert0 libwayland-client0
 libwayland-cursor0 libwayland-egl1 libwayland-server0 libwbclient0
 libxmlb2 libzvbi-common libzvbi0 linux-image-amd64 linux-libc-dev
 lm-sensors logsave m4 

Bug#1052954: marked as done (rccl: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/kfd/kfd/topology/nodes/')

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 21:29:01 +
with message-id 
and subject line Bug#1052954: fixed in rccl 5.3.3-3
has caused the Debian Bug report #1052954,
regarding rccl: FTBFS: FileNotFoundError: [Errno 2] No such file or 
directory: '/sys/class/kfd/kfd/topology/nodes/'
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.)


-- 
1052954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rccl
Version: 5.3.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release 
> -DAMDGPU_TARGETS="gfx803;gfx900;gfx906;gfx908;gfx90a;gfx1010;gfx1011;gfx1030" 
> -DROCM_SYMLINK_LIBS=OFF -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF 
> -DBUILD_TESTS=ON
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_CXX_COMPILER=hipcc 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release 
> -DAMDGPU_TARGETS=gfx803\;gfx900\;gfx906\;gfx908\;gfx90a\;gfx1010\;gfx1011\;gfx1030
>  -DROCM_SYMLINK_LIBS=OFF -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF 
> -DBUILD_TESTS=ON ..
> Re-run cmake no build system arguments
> -- The CXX compiler identification is Clang 15.0.7
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - failed
> -- Check for working CXX compiler: /usr/bin/hipcc
> -- Check for working CXX compiler: /usr/bin/hipcc - broken
> CMake Error at /usr/share/cmake-3.27/Modules/CMakeTestCXXCompiler.cmake:60 
> (message):
>   The C++ compiler
> 
> "/usr/bin/hipcc"
> 
>   is not able to compile a simple test program.
> 
>   It fails with the following output:
> 
> Change Dir: 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY'
> 
> Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f 
> Makefile cmTC_05a3d/fast
> gmake[2]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY'
> /usr/bin/gmake  -f CMakeFiles/cmTC_05a3d.dir/build.make 
> CMakeFiles/cmTC_05a3d.dir/build
> gmake[3]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY'
> Building CXX object CMakeFiles/cmTC_05a3d.dir/testCXXCompiler.cxx.o
> /usr/bin/hipcc   -gdwarf-4 -g -O2 -ffile-prefix-map=/<>=. 
> -Xarch_host -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -MD 
> -MT CMakeFiles/cmTC_05a3d.dir/testCXXCompiler.cxx.o -MF 
> CMakeFiles/cmTC_05a3d.dir/testCXXCompiler.cxx.o.d -o 
> CMakeFiles/cmTC_05a3d.dir/testCXXCompiler.cxx.o -c 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY/testCXXCompiler.cxx
> Traceback (most recent call last):
>   File "/usr/bin/rocm_agent_enumerator", line 260, in 
> main()
>   File "/usr/bin/rocm_agent_enumerator", line 244, in main
> target_list = readFromKFD()
>   ^
>   File "/usr/bin/rocm_agent_enumerator", line 193, in readFromKFD
> for node in sorted(os.listdir(topology_dir)):
>
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/sys/class/kfd/kfd/topology/nodes/'
> error: option 'cf-protection=return' cannot be specified on this target
> error: option 'cf-protection=branch' cannot be specified on this target
> 2 errors generated when compiling for gfx803.
> gmake[3]: *** [CMakeFiles/cmTC_05a3d.dir/build.make:79: 
> CMakeFiles/cmTC_05a3d.dir/testCXXCompiler.cxx.o] Error 1
> gmake[3]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY'
> gmake[2]: *** [Makefile:127: cmTC_05a3d/fast] Error 2
> gmake[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-Q32ETY'
> 
> 
> 
>   
> 
>   CMake will not be able to correctly generate this 

Bug#1052795: marked as done (rust-geo-types: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 21:29:19 +
with message-id 
and subject line Bug#1052795: fixed in rust-geo-types 0.7.11-1
has caused the Debian Bug report #1052795,
regarding rust-geo-types: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-geo-types
Version: 0.7.7-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling autocfg v1.1.0
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=autocfg 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/autocfg-1.1.0 
> CARGO_PKG_AUTHORS='Josh Stone ' 
> CARGO_PKG_DESCRIPTION='Automatic cfg for Rust compiler features' 
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='Apache-2.0 OR MIT' 
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=autocfg 
> CARGO_PKG_REPOSITORY='https://github.com/cuviper/autocfg' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.1.0 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name autocfg 
> /<>/debian/cargo_registry/autocfg-1.1.0/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=6818d4eba8c02e55 -C extra-filename=-6818d4eba8c02e55 
> --out-dir /<>/target/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>Compiling num-traits v0.2.15
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/num-traits-0.2.15 
> CARGO_PKG_AUTHORS='The Rust Project Developers' 
> CARGO_PKG_DESCRIPTION='Numeric traits for generic mathematics' 
> CARGO_PKG_HOMEPAGE='https://github.com/rust-num/num-traits' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=num-traits 
> CARGO_PKG_REPOSITORY='https://github.com/rust-num/num-traits' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.15 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=15 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build 
> /<>/debian/cargo_registry/num-traits-0.2.15/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=6cf08f159be44974 
> -C extra-filename=-6cf08f159be44974 --out-dir 
> /<>/target/debug/build/num-traits-6cf08f159be44974 -L 
> dependency=/<>/target/debug/deps --extern 
> autocfg=/<>/target/debug/deps/libautocfg-6818d4eba8c02e55.rlib 
> --cap-lints warn`
>  Running 
> `/<>/target/debug/build/num-traits-6cf08f159be44974/build-script-build`
> [num-traits 0.2.15] cargo:rustc-cfg=has_i128
> [num-traits 0.2.15] cargo:rustc-cfg=has_to_int_unchecked
> [num-traits 0.2.15] cargo:rustc-cfg=has_reverse_bits
> [num-traits 0.2.15] cargo:rustc-cfg=has_leading_trailing_ones
> [num-traits 0.2.15] cargo:rustc-cfg=has_int_assignop_ref
> [num-traits 0.2.15] cargo:rustc-cfg=has_div_euclid
> [num-traits 0.2.15] cargo:rustc-cfg=has_copysign
> [num-traits 0.2.15] cargo:rerun-if-changed=build.rs
>  Running `CARGO=/usr/bin/cargo 

Bug#1052762: marked as done (ceph-common has an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 21:25:22 +
with message-id 
and subject line Bug#1052762: fixed in ceph 18.2.0+ds-3
has caused the Debian Bug report #1052762,
regarding ceph-common has an undeclared file conflict
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.)


-- 
1052762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-common
Version: 18.2.0+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + radosgw

ceph-common has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/bin/rgw-gap-list
 * /usr/bin/rgw-gap-list-comparator
are contained in the packages
 * ceph-common/18.2.0+ds-1 as present in experimental
 * radosgw/16.2.11+ds-2 as present in bookworm|trixie|unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 18.2.0+ds-3
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
ceph, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph 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: Tue, 26 Sep 2023 20:45:31 +0200
Source: ceph
Architecture: source
Version: 18.2.0+ds-3
Distribution: experimental
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 1052762
Changes:
 ceph (18.2.0+ds-3) experimental; urgency=medium
 .
   * [1b72d20] Add extraopts += -DWITH_RADOSGW_SELECT_PARQUET=OFF to avoid
 download at build time when building arrow.
   * [ee65aa1] reaks: + Replaces: radosgw (<< 18) (Closes: #1052762).
Checksums-Sha1:
 f88a46ba8c80b95249d11859ccfd2e0aba40b3c6 8604 ceph_18.2.0+ds-3.dsc
 a6831be31dc1071012311e87279ce6d1e67160f0 118652 ceph_18.2.0+ds-3.debian.tar.xz
 3aacde553af839c19a08825e097e4c600220568d 44880 ceph_18.2.0+ds-3_amd64.buildinfo
Checksums-Sha256:
 e1c917c86f2f2990900d7c4d0bb2127ee12d94fd24ff0faaca4b5b4ccf195300 8604 
ceph_18.2.0+ds-3.dsc
 c201f3d7feb81068731306b88c0245f134461fdbee675a911ef414dd458a4077 118652 
ceph_18.2.0+ds-3.debian.tar.xz
 47834661ac6f02241cfa8cf99c8fcbee03bb3160bbfd3c05e85de315cf63a8de 44880 
ceph_18.2.0+ds-3_amd64.buildinfo
Files:
 957a11d97a912ba57a81699c14cc6ad9 8604 admin optional ceph_18.2.0+ds-3.dsc
 f4f682b278274348375d307eda5d6cc5 118652 admin optional 
ceph_18.2.0+ds-3.debian.tar.xz
 d57c857d28880fe7ffa7b694ac2ed03b 44880 admin optional 
ceph_18.2.0+ds-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmUTQ0gACgkQ1BatFaxr
Q/7XVA//czeO7Sx4Kxot8ENKqc8VuZl8+VwE6YpYuJejqqkknDgSdYXWWzl0S8ep
A5BL3OFNF9wt5FgiHW3OmMHxi9FNuMLE870TuranC82eR1C2b2nVzoiICYb2+SUb
wYhQbV8QwQTtMeGDRj1O/mZAE/UGmimY9QfLZw8E8ihFkiYxjjRM95ESqEztEobp
O++nQMs9aFILqIyoS9ckrrPKs01E7FNhmB4jQFu/YGMlEAcVA85v4coxCuSK8JIM
pPxj1lWevQIQj6oK8q6K+g7yOMTSBA938j/A8GIczBiQha4wlaXS69M7IDotMb01
n6uqBMa3+zWv1DgegkZT0S7H24/7wcdVwO/BHzCCFTj0U2sIXZxbIXzqP/ys0l7i
igun6BwEz32mjdP3jofIFPo1U4D0D9R2LEKYGSyw1cA827lZ5++bRUeli+WD09tq
vxVjEUkij+StACAB4nKFT1sNTP0YCf8Wb8os2FZMu3cfxdJHVMXhJXgueFaWQCAT
2ZfGJOJcsSFXIVlljHMOZu57yZ5OaFLoHFFnrCyQDcpaqEcTU63rZUx8jHOizkBD
la0dKPCzb5bEsCr8A18E4Id4mZR4eIuLkBHN0dAArH/3Y4NlVt9NODtkqq/LWNTo
Uydjx8GihrR96sr09qFPyAY6Ul6ITKC0HCU7gyVN/VsnF7LUBb4=
=CnUh
-END PGP SIGNATURE End Message ---

Bug#1052808: marked as done (rust-clipboard: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 22:03:11 +0100
with message-id <83b2c21d-ed3e-5afb-e99b-cee50d861...@p10link.net>
and subject line re: rust-xcb: panics at 'misaligned pointer dereference: 
address must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize
has caused the Debian Bug report #1052799,
regarding rust-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-clipboard
Version: 0.5.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> xvfb-run --server-args="-screen 0 1280x800x24" \
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling memchr v2.5.0
>Compiling libc v0.2.147
>Compiling bitflags v1.3.2
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/libc-0.2.147 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='Raw 
> FFI bindings to platform libraries like libc.
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=libc CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.147 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=147 
> CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build 
> /<>/debian/cargo_registry/libc-0.2.147/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=9f17b2f878ed97f7 
> -C extra-filename=-9f17b2f878ed97f7 --out-dir 
> /<>/target/debug/build/libc-9f17b2f878ed97f7 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.5.0 
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss' 
> CARGO_PKG_DESCRIPTION='Safe interface to memchr.' 
> CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_LICENSE=Unlicense/MIT CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=memchr 
> CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=2.5.0 CARGO_PKG_VERSION_MAJOR=2 
> CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2018 
> /<>/debian/cargo_registry/memchr-2.5.0/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=720e37c6401c0433 
> -C extra-filename=-720e37c6401c0433 --out-dir 
> /<>/target/debug/build/memchr-720e37c6401c0433 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=bitflags 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/bitflags-1.3.2 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='A 
> macro to generate structures which behave like bitflags.
> ' CARGO_PKG_HOMEPAGE='https://github.com/bitflags/bitflags' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=bitflags 
> CARGO_PKG_REPOSITORY='https://github.com/bitflags/bitflags' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.3.2 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=3 CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name bitflags --edition=2018 
> /<>/debian/cargo_registry/bitflags-1.3.2/src/lib.rs 
> 

Bug#1052799: marked as done (rust-xcb: panics at 'misaligned pointer dereference: address must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 22:03:11 +0100
with message-id <83b2c21d-ed3e-5afb-e99b-cee50d861...@p10link.net>
and subject line re: rust-xcb: panics at 'misaligned pointer dereference: 
address must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize
has caused the Debian Bug report #1052799,
regarding rust-xcb: panics at 'misaligned pointer dereference: address must be 
a multiple of 0x4' in xcb::xproto::SendEventDest::serialize
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.)


-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-x11-clipboard
Version: 0.6.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> xvfb-run --server-args="-screen 0 1280x800x24" \
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling memchr v2.5.0
>Compiling libc v0.2.147
>Compiling bitflags v1.3.2
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.5.0 
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss' 
> CARGO_PKG_DESCRIPTION='Safe interface to memchr.' 
> CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_LICENSE=Unlicense/MIT CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=memchr 
> CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=2.5.0 CARGO_PKG_VERSION_MAJOR=2 
> CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2018 
> /<>/debian/cargo_registry/memchr-2.5.0/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=720e37c6401c0433 
> -C extra-filename=-720e37c6401c0433 --out-dir 
> /<>/target/debug/build/memchr-720e37c6401c0433 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/libc-0.2.147 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='Raw 
> FFI bindings to platform libraries like libc.
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=libc CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.147 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=147 
> CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build 
> /<>/debian/cargo_registry/libc-0.2.147/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=9f17b2f878ed97f7 
> -C extra-filename=-9f17b2f878ed97f7 --out-dir 
> /<>/target/debug/build/libc-9f17b2f878ed97f7 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=bitflags 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/bitflags-1.3.2 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='A 
> macro to generate structures which behave like bitflags.
> ' CARGO_PKG_HOMEPAGE='https://github.com/bitflags/bitflags' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=bitflags 
> CARGO_PKG_REPOSITORY='https://github.com/bitflags/bitflags' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.3.2 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=3 CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name bitflags --edition=2018 
> 

Processed: reassign 1052808 to src:rust-xcb, forcibly merging 1052799 1052808, affects 1052799

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1052808 src:rust-xcb
Bug #1052808 {Done: Peter Green } [src:rust-clipboard] 
rust-clipboard: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test 
--all returned exit code 101
Bug reassigned from package 'src:rust-clipboard' to 'src:rust-xcb'.
No longer marked as found in versions rust-clipboard/0.5.0-3.
Ignoring request to alter fixed versions of bug #1052808 to the same values 
previously set
> forcemerge 1052799 1052808
Bug #1052799 {Done: James McCoy } [src:rust-xcb] rust-xcb: 
panics at 'misaligned pointer dereference: address must be a multiple of 0x4' 
in xcb::xproto::SendEventDest::serialize
Bug #1052808 {Done: Peter Green } [src:rust-xcb] 
rust-clipboard: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test 
--all returned exit code 101
Set Bug forwarded-to-address to 
'https://github.com/rust-x-bindings/rust-xcb/pull/230'.
Added indication that 1052808 affects src:rust-x11-clipboard
The source rust-xcb and version 1.2.2-1 do not appear to match any binary 
packages
Marked as fixed in versions rust-xcb/1.2.2-1.
Marked as found in versions rust-xcb/1.2.0-1.
Added tag(s) fixed-upstream and upstream.
Merged 1052799 1052808
> affects 1052799 src:rust-clipboard
Bug #1052799 {Done: James McCoy } [src:rust-xcb] rust-xcb: 
panics at 'misaligned pointer dereference: address must be a multiple of 0x4' 
in xcb::xproto::SendEventDest::serialize
Bug #1052808 {Done: Peter Green } [src:rust-xcb] 
rust-clipboard: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test 
--all returned exit code 101
Added indication that 1052799 affects src:rust-clipboard
Added indication that 1052808 affects src:rust-clipboard
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
1052808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052677: Fixed in 1.0.7-1

[Damon Tarry]

Looks like this was already fixed in 1.0.7-1 a couple of weeks ago. I
updated and the problem went away. Sorry for the dupe.

Bug#1052808: marked as done (rust-clipboard: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 21:55:43 +0100
with message-id <255972f9-1937-6895-b023-a86243541...@debian.org>
and subject line re: [Pkg-rust-maintainers] Bug#1052808: rust-clipboard: FTBFS: 
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
has caused the Debian Bug report #1052808,
regarding rust-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-clipboard
Version: 0.5.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> xvfb-run --server-args="-screen 0 1280x800x24" \
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling memchr v2.5.0
>Compiling libc v0.2.147
>Compiling bitflags v1.3.2
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/libc-0.2.147 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='Raw 
> FFI bindings to platform libraries like libc.
> ' CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc' 
> CARGO_PKG_LICENSE='MIT OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=libc CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.2.147 CARGO_PKG_VERSION_MAJOR=0 
> CARGO_PKG_VERSION_MINOR=2 CARGO_PKG_VERSION_PATCH=147 
> CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build 
> /<>/debian/cargo_registry/libc-0.2.147/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=9f17b2f878ed97f7 
> -C extra-filename=-9f17b2f878ed97f7 --out-dir 
> /<>/target/debug/build/libc-9f17b2f878ed97f7 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/memchr-2.5.0 
> CARGO_PKG_AUTHORS='Andrew Gallant :bluss' 
> CARGO_PKG_DESCRIPTION='Safe interface to memchr.' 
> CARGO_PKG_HOMEPAGE='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_LICENSE=Unlicense/MIT CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=memchr 
> CARGO_PKG_REPOSITORY='https://github.com/BurntSushi/memchr' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=2.5.0 CARGO_PKG_VERSION_MAJOR=2 
> CARGO_PKG_VERSION_MINOR=5 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2018 
> /<>/debian/cargo_registry/memchr-2.5.0/build.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 
> --cfg 'feature="default"' --cfg 'feature="std"' -C metadata=720e37c6401c0433 
> -C extra-filename=-720e37c6401c0433 --out-dir 
> /<>/target/debug/build/memchr-720e37c6401c0433 -L 
> dependency=/<>/target/debug/deps --cap-lints warn`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=bitflags 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/bitflags-1.3.2 
> CARGO_PKG_AUTHORS='The Rust Project Developers' CARGO_PKG_DESCRIPTION='A 
> macro to generate structures which behave like bitflags.
> ' CARGO_PKG_HOMEPAGE='https://github.com/bitflags/bitflags' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=bitflags 
> CARGO_PKG_REPOSITORY='https://github.com/bitflags/bitflags' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.3.2 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=3 CARGO_PKG_VERSION_PATCH=2 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name bitflags --edition=2018 
> 

Bug#1052799: closing 1052799

[James McCoy]

close 1052799 1.2.2-1
thanks

rust-xcb (1.2.2-1) unstable; urgency=medium

Processed: closing 1052799

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1052799 1.2.2-1
Bug #1052799 [src:rust-xcb] rust-xcb: panics at 'misaligned pointer 
dereference: address must be a multiple of 0x4' in 
xcb::xproto::SendEventDest::serialize
The source 'rust-xcb' and version '1.2.2-1' do not appear to match any binary 
packages
Marked as fixed in versions rust-xcb/1.2.2-1.
Bug #1052799 [src:rust-xcb] rust-xcb: panics at 'misaligned pointer 
dereference: address must be a multiple of 0x4' in 
xcb::xproto::SendEventDest::serialize
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): forcibly merging 1052799 1052808, affects 1052799

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 1052799 1052808
Bug #1052799 [src:rust-xcb] rust-xcb: panics at 'misaligned pointer 
dereference: address must be a multiple of 0x4' in 
xcb::xproto::SendEventDest::serialize
Unable to merge bugs because:
package of #1052808 is 'src:rust-clipboard' not 'src:rust-xcb'
Failed to forcibly merge 1052799: Did not alter merged bugs.

> affects 1052799 src:rust-clipboard
Failed to mark 1052799 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/1052799 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1052799 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1052799 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
1052808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: tracker: datetime build tests failing on 32-bit

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1035903 +experimental +upstream
Bug #1035903 [src:tracker] tracker: datetime build tests failing on 32-bit
Added tag(s) experimental.
Bug #1035903 [src:tracker] tracker: datetime build tests failing on 32-bit
Added tag(s) upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1035903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052762: marked as pending in ceph

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1052762 in ceph 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/ceph-team/ceph/-/commit/ee65aa1ab4229b0dabbe9399419cdd189612ed3c


reaks: + Replaces: radosgw (<< 18) (Closes: #1052762).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052762

Processed: Bug#1052762 marked as pending in ceph

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052762 [ceph-common] ceph-common has an undeclared file conflict
Added tag(s) pending.

-- 
1052762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1042900, tagging 1052822, tagging 1052916, tagging 1052907, tagging 1052905, tagging 1052894 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1042900 + sid trixie
Bug #1042900 [elpa-pointback] Breaks Emacs 29.1 upgrade: pointback.el:34:2: 
Error: Cannot open load file: No such file or directory, assoc
Added tag(s) sid and trixie.
> tags 1052822 + experimental
Bug #1052822 [src:mini-buildd] mini-buildd: FTBFS: make[1]: *** 
[debian/rules:11: override_dh_auto_build] Error 25
Added tag(s) experimental.
> tags 1052916 + experimental
Bug #1052916 [src:golang-github-iovisor-gobpf] golang-github-iovisor-gobpf: 
FTBFS: make[1]: *** [debian/rules:16: copyright-scan] Error 1
Added tag(s) experimental.
> tags 1052907 + experimental
Bug #1052907 [src:cloudkitty] cloudkitty: FTBFS: tests fail
Added tag(s) experimental.
> tags 1052905 + experimental
Bug #1052905 [src:python-oslo.serialization] python-oslo.serialization: FTBFS: 
tests fail
Added tag(s) experimental.
> tags 1052894 + experimental
Bug #1052894 [src:python-croniter] python-croniter: FTBFS: tests fail directory
Added tag(s) experimental.
> tags 1052885 + experimental
Bug #1052885 [src:horizon] horizon: FTBFS: make[1]: tests fail
Added tag(s) experimental.
> tags 1052881 + experimental
Bug #1052881 [src:embree] embree: FTBFS: ! LaTeX Error: File `puenc-greek.def' 
not found.
Added tag(s) experimental.
> tags 1052870 + experimental
Bug #1052870 [src:golang-mongodb-mongo-driver] golang-mongodb-mongo-driver: 
FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 
go.mongodb.org/mongo-driver/benchmark go.mongodb.org/mongo-driver/bson 
go.mongodb.org/mongo-driver/bson/bsoncodec 
go.mongodb.org/mongo-driver/bson/bsonoptions 
go.mongodb.org/mongo-driver/bson/bsonrw 
go.mongodb.org/mongo-driver/bson/bsonrw/bsonrwtest 
go.mongodb.org/mongo-driver/bson/bsontype 
go.mongodb.org/mongo-driver/bson/mgocompat 
go.mongodb.org/mongo-driver/bson/primitive 
go.mongodb.org/mongo-driver/cmd/docbuilder 
go.mongodb.org/mongo-driver/cmd/godriver-benchmark 
go.mongodb.org/mongo-driver/event 
go.mongodb.org/mongo-driver/examples/documentation_examples 
go.mongodb.org/mongo-driver/internal 
go.mongodb.org/mongo-driver/internal/randutil 
go.mongodb.org/mongo-driver/internal/testutil 
go.mongodb.org/mongo-driver/internal/testutil/assert 
go.mongodb.org/mongo-driver/internal/testutil/helpers 
go.mongodb.org/mongo-driver/internal/testutil/israce 
go.mongodb.org/mongo-driver/mongo go.mongodb.org/mongo-driver/mongo/address 
go.mongodb.org/mongo-driver/mongo/description 
go.mongodb.org/mongo-driver/mongo/gridfs 
go.mongodb.org/mongo-driver/mongo/options 
go.mongodb.org/mongo-driver/mongo/readconcern 
go.mongodb.org/mongo-driver/mongo/readpref 
go.mongodb.org/mongo-driver/mongo/testatlas 
go.mongodb.org/mongo-driver/mongo/testaws 
go.mongodb.org/mongo-driver/mongo/writeconcern go.mongodb.org/mongo-driver/tag 
go.mongodb.org/mongo-driver/version go.mongodb.org/mongo-driver/x/bsonx 
go.mongodb.org/mongo-driver/x/bsonx/bsoncore 
go.mongodb.org/mongo-driver/x/mongo/driver 
go.mongodb.org/mongo-driver/x/mongo/driver/auth 
go.mongodb.org/mongo-driver/x/mongo/driver/auth/internal/awsv4 
go.mongodb.org/mongo-driver/x/mongo/driver/connstring 
go.mongodb.org/mongo-driver/x/mongo/driver/dns 
go.mongodb.org/mongo-driver/x/mongo/driver/drivertest 
go.mongodb.org/mongo-driver/x/mongo/driver/examples/cluster_monitoring 
go.mongodb.org/mongo-driver/x/mongo/driver/examples/count 
go.mongodb.org/mongo-driver/x/mongo/driver/examples/server_monitoring 
go.mongodb.org/mongo-driver/x/mongo/driver/examples/workload 
go.mongodb.org/mongo-driver/x/mongo/driver/mongocrypt 
go.mongodb.org/mongo-driver/x/mongo/driver/mongocrypt/options 
go.mongodb.org/mongo-driver/x/mongo/driver/ocsp 
go.mongodb.org/mongo-driver/x/mongo/driver/operation 
go.mongodb.org/mongo-driver/x/mongo/driver/session 
go.mongodb.org/mongo-driver/x/mongo/driver/topology 
go.mongodb.org/mongo-driver/x/mongo/driver/uuid 
go.mongodb.org/mongo-driver/x/mongo/driver/wiremessage returned exit code 1
Added tag(s) experimental.
> tags 1052868 + experimental
Bug #1052868 [src:aodh] aodh: FTBFS: tests failed
Added tag(s) experimental.
> tags 1052851 + experimental
Bug #1052851 [src:heat-dashboard] heat-dashboard: FTBFS: AttributeError: 
'NoneType' object has no attribute 'read'
Added tag(s) experimental.
> tags 1052825 + experimental
Bug #1052825 [src:golang-github-spf13-cast] golang-github-spf13-cast: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/spf13/cast returned exit code 1
Added tag(s) experimental.
> tags 1052819 + experimental
Bug #1052819 [src:golang-github-mattn-go-runewidth] 
golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go 
test -vet=off -v -p 8 github.com/mattn/go-runewidth returned exit code 1
Added tag(s) experimental.
> tags 1052798 + experimental
Bug #1052798 [src:watcher-dashboard] watcher-dashboard: FTBFS: AttributeError: 
'NoneType' object has no attribute 'read'
Added tag(s) experimental.
> tags 1052797 + experimental
Bug #1052797 

Bug#1052850: marked as done (elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 20:37:31 +
with message-id 
and subject line Bug#1052850: fixed in elan 3.0.0-1
has caused the Debian Bug report #1052850,
regarding elan: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build 
returned exit code 101
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elan
Version: 2.0.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> touch debian/cargo-checksum.json
> make[1]: Leaving directory '/<>'
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into 
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
> error: failed to select a version for the requirement `remove_dir_all = 
> "^0.7.0"`
> candidate versions found which didn't match: 0.8.2
> location searched: directory source `/<>/debian/cargo_registry` 
> (which is replacing registry `crates-io`)
> required by package `elan v2.0.0 (/<>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/elan_2.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: elan
Source-Version: 3.0.0-1
Done: Christopher Hoskin 

We believe that the bug you reported is fixed in the latest version of
elan, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated elan package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Sep 2023 20:22:31 +0100
Source: elan
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher Hoskin 
Changed-By: Christopher Hoskin 
Closes: 1052850
Changes:
 elan (3.0.0-1) unstable; urgency=medium
 .
   * Fix "FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build
 returned exit code 101" update dependencies (Closes:
 #1052850)
   * Import new upstream version (3.0.0)
Checksums-Sha1:
 9281adb328f47555a9d4213ae08644ced3a35abf 2718 elan_3.0.0-1.dsc
 314aaac4553f525637f881acd17de823f6d961d9 95653 elan_3.0.0.orig.tar.gz
 17dbd54e37599b04e6db11e73caa8ac24ed479fa 5932 elan_3.0.0-1.debian.tar.xz
 c5c264fc6f4da881fe8b2c3e241ba0d43632e5a8 18405 elan_3.0.0-1_amd64.buildinfo
Checksums-Sha256:
 aed28b1d7d299bddb16697a9397c3b43aeb09c335b11df36f0672b0ffdbc4287 2718 
elan_3.0.0-1.dsc
 

Bug#1052769: marked as done (inputplug: FTBFS: build-dependency not installable: librust-gethostname-0.2+default-dev (>= 0.2.1-~~))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 21:06:45 +0100
with message-id 
and subject line re: inputplug: FTBFS: build-dependency not installable: 
librust-gethostname-0.2+default-dev (>= 0.2.1-~~)
has caused the Debian Bug report #1052769,
regarding inputplug: FTBFS: build-dependency not installable: 
librust-gethostname-0.2+default-dev (>= 0.2.1-~~)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: inputplug
Version: 0.4.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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-cargo (>= 24), cargo, 
> rustc, libstd-rust-dev, librust-anyhow-1.0+default-dev, 
> librust-nix-0+default-dev (>= 0.19.0-~~), librust-pidfile-rs-0.1+default-dev, 
> librust-structopt-0.3+default-dev, librust-x11rb-0.8+default-dev, pkgconf | 
> pkg-config, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-cargo (>= 24), cargo, 
> rustc, libstd-rust-dev, librust-anyhow-1.0+default-dev, 
> librust-nix-0+default-dev (>= 0.19.0-~~), librust-pidfile-rs-0.1+default-dev, 
> librust-structopt-0.3+default-dev, librust-x11rb-0.8+default-dev, pkgconf, 
> 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 [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [878 B]
> Get:5 copy:/<>/apt_archive ./ Packages [883 B]
> Fetched 2370 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...
> 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:
>  librust-x11rb-dev : Depends: librust-gethostname-0.2+default-dev (>= 
> 0.2.1-~~) but it is not installable
> 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/2023/09/25/inputplug_0.4.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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 ---

Fixed by the upload of rust-x11rb 0.8.1-7--- End Message ---

Processed: Re: Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed upstream
Bug #1052973 [src:octave-image] octave-image: FTBFS: make: *** 
[debian/rules:12: binary] Error 1
Added tag(s) confirmed and upstream.

-- 
1052973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052973: octave-image: FTBFS: make: *** [debian/rules:12: binary] Error 1

[Rafael Laboissière]

Control: tags -1 + confirmed upstream

* Lucas Nussbaum  [2023-09-26 15:46]:


Source: octave-image
Version: 2.14.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build 
on amd64.



Relevant part (hopefully):


 Summary: 2073 tests, 1744 passed, 36 known failures, 0 skipped
 Some tests failed.  Giving up...
 make: *** [debian/rules:12: binary] Error 1


I think that this problem is triggered by a changing in behavior of the 
mkoctfile program, in the way it process its arguments, between versions 
8.2 and 8.3 of Octave. I will try to get to this, as time permits.


Best,

Rafael Laboissière

Processed: Re: Bug#1052677: ffmpeg armhf uses NEON instructions

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libhwy1 1.0.7-7
Bug #1052677 [ffmpeg] ffmpeg armhf uses NEON instructions
Bug reassigned from package 'ffmpeg' to 'libhwy1'.
No longer marked as found in versions ffmpeg/7:6.0-6.
Ignoring request to alter fixed versions of bug #1052677 to the same values 
previously set
Bug #1052677 [libhwy1] ffmpeg armhf uses NEON instructions
Marked as found in versions highway/1.0.7-7.
> severity -1 serious
Bug #1052677 [libhwy1] ffmpeg armhf uses NEON instructions
Severity set to 'serious' from 'normal'
> retitle -1 libhwy1: baseline violation
Bug #1052677 [libhwy1] ffmpeg armhf uses NEON instructions
Changed Bug title to 'libhwy1: baseline violation' from 'ffmpeg armhf uses NEON 
instructions'.

-- 
1052677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1023565: closing 1023565

[Barak A. Pearlmutter]

close 1023565 
thanks
dleyna is back, baby!

Processed: closing 1023565

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1023565
Bug #1023565 [mopidy-dleyna] mopidy-dleyna: depends on orphaned/removed dleyna
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1023565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 1052799 to rust-xcb: panics at 'misaligned pointer dereference: address must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1052799 rust-xcb: panics at 'misaligned pointer dereference: address 
> must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize
Bug #1052799 [src:rust-xcb] rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
Changed Bug title to 'rust-xcb: panics at 'misaligned pointer dereference: 
address must be a multiple of 0x4' in xcb::xproto::SendEventDest::serialize' 
from 'rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 1052799 to src:rust-xcb, affects 1052799, tagging 1052799 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1052799 src:rust-xcb 1.2.0-1
Bug #1052799 [src:rust-x11-clipboard] rust-x11-clipboard: FTBFS: dh_auto_test: 
error: /usr/share/cargo/bin/cargo test --all returned exit code 101
Bug reassigned from package 'src:rust-x11-clipboard' to 'src:rust-xcb'.
No longer marked as found in versions rust-x11-clipboard/0.6.1-1.
Ignoring request to alter fixed versions of bug #1052799 to the same values 
previously set
Bug #1052799 [src:rust-xcb] rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
Marked as found in versions rust-xcb/1.2.0-1.
> affects 1052799 src:rust-x11-clipboard
Bug #1052799 [src:rust-xcb] rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
Added indication that 1052799 affects src:rust-x11-clipboard
> tags 1052799 + upstream fixed-upstream
Bug #1052799 [src:rust-xcb] rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
Added tag(s) fixed-upstream and upstream.
> forwarded 1052799 https://github.com/rust-x-bindings/rust-xcb/pull/230
Bug #1052799 [src:rust-xcb] rust-x11-clipboard: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo test --all returned exit code 101
Set Bug forwarded-to-address to 
'https://github.com/rust-x-bindings/rust-xcb/pull/230'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052763: libgnuastro18 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgnuastro_make.so

[Mohammad Akhlaghi]

Hi Helmut,

Thank you very much for the complete explanation.

Will this problem be fixed if we separate 'libgnuastro_make' as a 
separate package in 'debian/control'?


I would indeed love to read the Debian policy in full detail as it 
evolves. I did read most parts when I was helping the Debian-Astro team 
package it several years ago. But I am finding it harder and harder to 
find the time: I am the developer of Gnuastro, I am not a packager (but 
I love to do it as best as possible for the sake of the users). If the 
above is no the solution, can you point me to the sub-section about this?


Generally, it would be great if Lintian could complain about such 
issues. Before every push to salsa.debian.org (for the Debian astro team 
to inspect before pushing), I run it like below and correct all the 
important/relevant errors/warnings.


lintian -E -I --pedantic ...

Thank you very much,
Mohammad

Bug#1052964: marked as done (rust-ascii: FTBFS: error[E0170]: pattern binding `a` is named the same as one of the variants of the type `ascii::AsciiChar`)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 18:50:52 +
with message-id 
and subject line Bug#1052964: fixed in rust-ascii 1.0.0-2
has caused the Debian Bug report #1052964,
regarding rust-ascii: FTBFS: error[E0170]: pattern binding `a` is named the 
same as one of the variants of the type `ascii::AsciiChar`
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.)


-- 
1052964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-ascii
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling ascii v1.0.0 (/<>)
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=ascii 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Thomas Bahn 
> :Torbjørn Birch Moltu :Simon 
> Sapin ' CARGO_PKG_DESCRIPTION='ASCII-only equivalents 
> to `char`, `str` and `String`.' CARGO_PKG_HOMEPAGE='' 
> CARGO_PKG_LICENSE='Apache-2.0 / MIT' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=ascii 
> CARGO_PKG_REPOSITORY='https://github.com/tomprogrammer/rust-ascii' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.0.0 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name ascii src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib 
> --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 
> 'feature="default"' --cfg 'feature="std"' -C metadata=89234ed414d4cc11 -C 
> extra-filename=-89234ed414d4cc11 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn 
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix 
> /<>=/usr/share/cargo/registry/ascii-1.0.0 --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=ascii 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Thomas Bahn 
> :Torbjørn Birch Moltu :Simon 
> Sapin ' CARGO_PKG_DESCRIPTION='ASCII-only equivalents 
> to `char`, `str` and `String`.' CARGO_PKG_HOMEPAGE='' 
> CARGO_PKG_LICENSE='Apache-2.0 / MIT' CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=ascii 
> CARGO_PKG_REPOSITORY='https://github.com/tomprogrammer/rust-ascii' 
> CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=1.0.0 CARGO_PKG_VERSION_MAJOR=1 
> CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' 
> CARGO_PRIMARY_PACKAGE=1 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name ascii src/lib.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 
> 'feature="default"' --cfg 'feature="std"' -C metadata=a801788db4998630 -C 
> extra-filename=-a801788db4998630 --out-dir 
> /<>/target/x86_64-unknown-linux-gnu/debug/deps --target 
> x86_64-unknown-linux-gnu -C 
> incremental=/<>/target/x86_64-unknown-linux-gnu/debug/incremental
>  -L dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps -C debuginfo=2 --cap-lints warn 
> -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix 
> /<>=/usr/share/cargo/registry/ascii-1.0.0 --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
> warning: use of deprecated method `std::error::Error::description`: use the 
> Display impl or to_string()
>--> src/ascii_string.rs:675:20
> |
> 675 | self.error.description()
> |^^^
> |
> = note: `#[warn(deprecated)]` on by default
> 
> warning[E0170]: pattern binding `a` is named the same as one of the variants 
> of the type 

Processed: Bug#1052776 marked as pending in golang-github-prometheus-exporter-toolkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052776 [src:golang-github-prometheus-exporter-toolkit] 
golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web 
github.com/prometheus/exporter-toolkit/web/kingpinflag returned exit code 1
Added tag(s) pending.

-- 
1052776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052776: marked as pending in golang-github-prometheus-exporter-toolkit

[Martina Ferrari]

Control: tag -1 pending

Hello,

Bug #1052776 in golang-github-prometheus-exporter-toolkit reported by you has 
been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-prometheus-exporter-toolkit/-/commit/387077d53faa18a0ba6c4853949681f38daccdaa


debian/patches: Add patch to fix test errors with go >= 1.21.

Closes: #1052776


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052776

Bug#1052874: marked as done (rust-x11rb: FTBFS: build-dependency not installable: librust-gethostname-0.2+default-dev (>= 0.2.1-~~))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 18:22:31 +
with message-id 
and subject line Bug#1052874: fixed in rust-x11rb 0.8.1-7
has caused the Debian Bug report #1052874,
regarding rust-x11rb: FTBFS: build-dependency not installable: 
librust-gethostname-0.2+default-dev (>= 0.2.1-~~)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-x11rb
Version: 0.8.1-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-gethostname-0.2+default-dev (>= 0.2.1-~~), 
> librust-nix-0+default-dev (>= 0.25-~~), python3-xcbgen, xcb-proto, 
> libxcb1-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-gethostname-0.2+default-dev (>= 0.2.1-~~), 
> librust-nix-0+default-dev (>= 0.25-~~), python3-xcbgen, xcb-proto, 
> libxcb1-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 [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [893 B]
> Get:5 copy:/<>/apt_archive ./ Packages [823 B]
> Fetched 2325 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...
> 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:
>  sbuild-build-depends-main-dummy : Depends: 
> librust-gethostname-0.2+default-dev (>= 0.2.1-~~) but it is not installable
> 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/2023/09/25/rust-x11rb_0.8.1-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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-x11rb
Source-Version: 0.8.1-7
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-x11rb, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-x11rb 
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: Tue, 26 Sep 2023 15:37:59 +
Source: rust-x11rb
Architecture: source
Version: 0.8.1-7
Distribution: 

Processed: Bug#1052954 marked as pending in rccl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052954 [src:rccl] rccl: FTBFS: FileNotFoundError: [Errno 2] No such 
file or directory: '/sys/class/kfd/kfd/topology/nodes/'
Added tag(s) pending.

-- 
1052954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052954: marked as pending in rccl

[Christian Kastner]

Control: tag -1 pending

Hello,

Bug #1052954 in rccl 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/rocm-team/rccl/-/commit/b936acd42edaa2c278c693477add9c7d2560ef05


Filter cf-protection hardening from device code

Fixes a FTBFS with dpkg >= 1.22

Closes: #1052954


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052954

Bug#1052996: radicale FTBFS with the nocheck build profile

[Helmut Grohne]

Source: radicale
Version: 3.1.8-2
Severity: serious
Tags: ftbfs

radicale fails to build from source in unstable when adding the nocheck
build profile. Since trixie, such a failure is considered
release-critical. A build log ends as follows:

|debian/rules execute_after_dh_auto_install
| make[1]: Entering directory '/<>'
| 
PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 PYTHONPATH="/<>/debian/tmp/usr/lib/python3.11/dist-packages" 
help2man --name "a simple calendar server" --no-info --version-string="3.1.8-2" 
--output  debian/radicale.1  radicale || { 
PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
 PYTHONPATH="/<>/debian/tmp/usr/lib/python3.11/dist-packages"  
radicale --help; false; }
| help2man: can't get `--help' info from radicale
| Try `--no-discard-stderr' if option outputs to stderr
| Traceback (most recent call last):
|   File "/<>/debian/tmp/usr/bin/radicale", line 33, in 
| sys.exit(load_entry_point('Radicale==3.1.8', 'console_scripts', 
'radicale')())
|  
^^
|   File "/<>/debian/tmp/usr/bin/radicale", line 25, in 
importlib_load_entry_point
| return next(matches).load()
|
|   File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
| module = import_module(match.group('module'))
|  
|   File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
| return _bootstrap._gcd_import(name[level:], package, level)
|
|   File "", line 1204, in _gcd_import
|   File "", line 1176, in _find_and_load
|   File "", line 1126, in _find_and_load_unlocked
|   File "", line 241, in _call_with_frames_removed
|   File "", line 1204, in _gcd_import
|   File "", line 1176, in _find_and_load
|   File "", line 1147, in _find_and_load_unlocked
|   File "", line 690, in _load_unlocked
|   File "", line 940, in exec_module
|   File "", line 241, in _call_with_frames_removed
|   File 
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/__init__.py",
 line 33, in 
| from radicale.app import Application
|   File 
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/app/__init__.py",
 line 38, in 
| from radicale.app.base import ApplicationBase
|   File 
"/<>/debian/tmp/usr/lib/python3.11/dist-packages/radicale/app/base.py",
 line 29, in 
| import defusedxml.ElementTree as DefusedET  # isort:skip
| ^^
| ModuleNotFoundError: No module named 'defusedxml'
| make[1]: *** [debian/rules:41: execute_after_dh_auto_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:61: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Helmut

Bug#1052927: marked as done (qt6-imageformats: FTBFS: -- Package 'libmng', required by 'virtual:world', not found)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 17:55:08 +
with message-id 
and subject line Bug#1052927: fixed in qt6-imageformats 6.4.2-5
has caused the Debian Bug report #1052927,
regarding qt6-imageformats: FTBFS: --   Package 'libmng', required by 
'virtual:world', not found
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.)


-- 
1052927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt6-imageformats
Version: 6.4.2-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_auto_configure -- \
>   --log-level=STATUS \
>   -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu \
>   
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON -GNinja -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu --log-level=STATUS 
> -DCMAKE_LIBRARY_PATH=x86_64-linux-gnu ..
> -- The CXX compiler identification is GNU 13.2.0
> -- The C compiler identification is GNU 13.2.0
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
> -- Found Threads: TRUE  
> -- Performing Test HAVE_STDATOMIC
> -- Performing Test HAVE_STDATOMIC - Success
> -- Found WrapAtomic: TRUE  
> -- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so   
> -- CMAKE_BUILD_TYPE was set to: 'None'
> -- Check for feature set changes
> -- CMAKE_STRIP (original): /usr/bin/strip
> -- Performing Test strip --keep-section
> -- Performing Test strip --keep-section - TRUE
> -- CMAKE_STRIP (used by Qt): 
> /<>/obj-x86_64-linux-gnu/lib/qt6/libexec/qt-internal-strip
> -- Found JPEG: /usr/lib/x86_64-linux-gnu/libjpeg.so (found version "62") 
> -- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR) 
> -- Found TIFF: /usr/lib/x86_64-linux-gnu/libtiff.so (found version "4.5.1")  
> CMake Error at 
> /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicTargetHelpers.cmake:257 
> (set_property):
>   Attempt to promote imported target "Threads::Threads" to global scope (by
>   setting IMPORTED_GLOBAL) which is not built in this directory.
> Call Stack (most recent call first):
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicWalkLibsHelpers.cmake:252 
> (__qt_internal_promote_target_to_global)
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtPublicWalkLibsHelpers.cmake:225 
> (__qt_internal_walk_libs)
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFindPackageHelpers.cmake:12 
> (__qt_internal_walk_libs)
>   /usr/lib/x86_64-linux-gnu/cmake/Qt6/QtFindPackageHelpers.cmake:181 
> (qt_find_package_promote_targets_to_global_scope)
>   src/imageformats/configure.cmake:19 (qt_find_package)
>   src/plugins/imageformats/CMakeLists.txt:9 (include)
> 
> 
> -- Checking for module 'libmng'
> --   Package 'libmng', required by 'virtual:world', not found
> -- Found Libmng: /usr/lib/x86_64-linux-gnu/libmng.so  
> -- Performing Test HAVE_DASH_UNDEFINED_SYMBOLS
> -- Performing Test HAVE_DASH_UNDEFINED_SYMBOLS - Success
> -- Performing Test HAVE_DASH_DASH_NO_UNDEFINED
> -- Performing Test HAVE_DASH_DASH_NO_UNDEFINED - Success
> -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.13")  
> -- Found WrapSystemZLIB: TRUE  
> -- Using system ZLIB.
> -- Found WrapZLIB: TRUE  
> -- The following packages have been found:
> 
>  * Qt6BuildInternals (required version >= 6.4.2)
>  * Qt6CoreTools (required version >= 6.4.2)
>  * Qt6Core (required version >= 6.4.2)
>  * OpenGL
>  * XKB (required version >= 0.5.0), XKB API common to servers and clients., 
> 
>  * Vulkan
>  * WrapVulkanHeaders
>  * Qt6GuiTools (required 

Processed: retitle 1052964 to rust-ascii: FTBFS: error[E0170]: pattern binding `a` is named the same as one of the variants of the type `ascii::AsciiChar` ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1052964 rust-ascii: FTBFS: error[E0170]: pattern binding `a` is named 
> the same as one of the variants of the type `ascii::AsciiChar`
Bug #1052964 [src:rust-ascii] rust-ascii: FTBFS: warning: use of deprecated 
method `std::error::Error::description`: use the Display impl or to_string()
Changed Bug title to 'rust-ascii: FTBFS: error[E0170]: pattern binding `a` is 
named the same as one of the variants of the type `ascii::AsciiChar`' from 
'rust-ascii: FTBFS: warning: use of deprecated method 
`std::error::Error::description`: use the Display impl or to_string()'.
> tags 1052964 + upstream fixed-upstream
Bug #1052964 [src:rust-ascii] rust-ascii: FTBFS: error[E0170]: pattern binding 
`a` is named the same as one of the variants of the type `ascii::AsciiChar`
Added tag(s) fixed-upstream and upstream.
> forwarded 1052964 https://github.com/tomprogrammer/rust-ascii/pull/98
Bug #1052964 [src:rust-ascii] rust-ascii: FTBFS: error[E0170]: pattern binding 
`a` is named the same as one of the variants of the type `ascii::AsciiChar`
Set Bug forwarded-to-address to 
'https://github.com/tomprogrammer/rust-ascii/pull/98'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1052947 is forwarded to https://github.com/zkry/yaml.el/issues/51

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1052947 https://github.com/zkry/yaml.el/issues/51
Bug #1052947 [src:yaml-el] yaml-el: FTBFS: make: *** [debian/rules:7: binary] 
Error 25
Set Bug forwarded-to-address to 'https://github.com/zkry/yaml.el/issues/51'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#999962: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)

[Nicholas D Steeves]

control: tag -1 pending

Manphiz  writes:

> Nicholas D Steeves  writes:
>
>> Manphiz  writes:
>>
>>> Nicholas D Steeves  writes:
 Manphiz  writes:
> Manphiz  writes:
>
>>> BTW, I'm not a DD or DMD yet so I'm probably not able to submit to
>>> delayed queue yet, right?
>>
>> Right, the upload to the delayed queue using dput is something else, and
>> any uploads you make to ftp-master will not succeed.  I'm not sure if
>> mentors.debian.net has a delayed queue, and I can't see how that would
>> be useful--other than for practise.  Did you find the relevant section
>> in the Developer's Reference?
>>
>
> Uploaded to mentors[1].  Tried to search for NMU and mentors related
> contents in the Developer's Reference but didn't find much.  I guess
> mentors should be safer than the delayed queue.

mentors.debian.net != ftp.upload.debian.org

Each of those hosts has its own queue, naturally, because they're
different hosts.

Developers-reference §5.11 is the relevant section.

>> Before we get to the upload you need to submit an nmudiff of the source
>> package.  On a related note, if you don't know about these yet,
>> "msmtp-mta" and "apt-file" are really useful.  Msmtp-mta is an
>> alternative to other MTAs (useful for laptops, and Spwhitton told me
>> about apt-file :)  It's technically possible to use debdiff, but
>> "nmudiff" is a tool like "reportbug", but I'm not sure if nmudiff will
>> function without an mta, unlike reportbug.
>>
>
> Also sent the nmudiff to this bug.  Good thing that my postfix still
> works :)

Thank you, and oh good :) 

While technically it would be ok to upload directly (0 day), because
we've given the maintainer a lot of time to react to this bug, I've
chosen to upload to delayed=2.

Congrats on your first (sponsored) nmu!
Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: Re: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #62 [src:silversearcher-ag] silversearcher-ag: depends on obsolete 
pcre3 library
Ignoring request to alter tags of bug #62 to the same tags previously set

-- 
62: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052763: libgnuastro18 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgnuastro_make.so

[Helmut Grohne]

Hi Mohammad,

On Tue, Sep 26, 2023 at 07:08:24PM +0200, Mohammad Akhlaghi wrote:
> The 'libgnuastro_make.so' is declared within the
> 'debian/libgnuastro18.install' file (see [1] below); a comment there also
> described what it is (an extension-library for GNU Make, described in [2]).

Yes. It is declared there and it is also declared for libgnuastro17. If
you try installing both together, you make dpkg very unhappy.

> Could you please point me to any other place that it should be declared?

It also is declared here:

https://sources.debian.org/src/gnuastro/0.19-1/debian/libgnuastro17.install/#L6

Since these are shared libraries they really should be coinstallable.
Either of them must cease shipping this file. Since you cannot change
libgnuastro17 anymore, the one to change is libgnuastro18.

I also note that this is the development library link. It does not
belong in the shared library package. Please take your time and read up
in the Debian policy on this matter.

Your gnuastro upload also started a transition. However, it misses a
transition bug.

Maintaining a shared library is a non-trivial responsibility and this
shows significant signs of things going wrong.

> This is an important bug and I will fix it as soon as I know the solution.

Thank you.

Helmut

Processed: Bug#1052828

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1052828 + upstream
Bug #1052828 [src:trurl] trurl: FTBFS: dh_auto_test: error: make -j8 test 
returned exit code 2
Added tag(s) upstream.
> tags 1052828 + confirmed
Bug #1052828 [src:trurl] trurl: FTBFS: dh_auto_test: error: make -j8 test 
returned exit code 2
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052828: trurl: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Michael Ablassmeier]

hi,

On Tue, Sep 26, 2023 at 05:36:10PM +0200, Michael Ablassmeier wrote:
> i can reproduce this, also with the most recent upstream version,
> not quite sure where the issue is in detail yet.

the problem is caused by the fact that a more recent libcurl
version (8.3.0) is now shipped within sid and something may
have changed in libcurl that causes the tests to fail.

Upstream confirmed this (they seem to use an older libcurl
version in their gitlab CI so didnt catch this one).

Lets wait until this is sorted and then we might either
skip those tests for now or upload an updated trurl
version either with patch or more recent upstream
version.

bye,
- michael

Bug#1052968: marked as done (hipcub: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/kfd/kfd/topology/nodes/')

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 17:19:12 +
with message-id 
and subject line Bug#1052968: fixed in hipcub 5.3.3-5
has caused the Debian Bug report #1052968,
regarding hipcub: FTBFS: FileNotFoundError: [Errno 2] No such file or 
directory: '/sys/class/kfd/kfd/topology/nodes/'
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.)


-- 
1052968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hipcub
Version: 5.3.3-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_LIBDIR=lib 
> -DAMDGPU_TARGETS="gfx803;gfx900;gfx906;gfx908;gfx90a;gfx1010;gfx1011;gfx1030" 
> -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF -DBUILD_TEST=ON
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb cmake 
> -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_CXX_COMPILER=hipcc 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release 
> -DCMAKE_INSTALL_LIBDIR=lib 
> -DAMDGPU_TARGETS=gfx803\;gfx900\;gfx906\;gfx908\;gfx90a\;gfx1010\;gfx1011\;gfx1030
>  -DBUILD_FILE_REORG_BACKWARD_COMPATIBILITY=OFF -DBUILD_TEST=ON ..
> Re-run cmake no build system arguments
> -- The CXX compiler identification is Clang 15.0.7
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - failed
> -- Check for working CXX compiler: /usr/bin/hipcc
> -- Check for working CXX compiler: /usr/bin/hipcc - broken
> CMake Error at /usr/share/cmake-3.27/Modules/CMakeTestCXXCompiler.cmake:60 
> (message):
>   The C++ compiler
> 
> "/usr/bin/hipcc"
> 
>   is not able to compile a simple test program.
> 
>   It fails with the following output:
> 
> Change Dir: 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH'
> 
> Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f 
> Makefile cmTC_c2fcb/fast
> gmake[2]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH'
> /usr/bin/gmake  -f CMakeFiles/cmTC_c2fcb.dir/build.make 
> CMakeFiles/cmTC_c2fcb.dir/build
> gmake[3]: Entering directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH'
> Building CXX object CMakeFiles/cmTC_c2fcb.dir/testCXXCompiler.cxx.o
> /usr/bin/hipcc   -gdwarf-4 -g -O2 -ffile-prefix-map=/<>=. 
> -Xarch_host -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -MD 
> -MT CMakeFiles/cmTC_c2fcb.dir/testCXXCompiler.cxx.o -MF 
> CMakeFiles/cmTC_c2fcb.dir/testCXXCompiler.cxx.o.d -o 
> CMakeFiles/cmTC_c2fcb.dir/testCXXCompiler.cxx.o -c 
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH/testCXXCompiler.cxx
> Traceback (most recent call last):
>   File "/usr/bin/rocm_agent_enumerator", line 260, in 
> main()
>   File "/usr/bin/rocm_agent_enumerator", line 244, in main
> target_list = readFromKFD()
>   ^
>   File "/usr/bin/rocm_agent_enumerator", line 193, in readFromKFD
> for node in sorted(os.listdir(topology_dir)):
>
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/sys/class/kfd/kfd/topology/nodes/'
> error: option 'cf-protection=return' cannot be specified on this target
> error: option 'cf-protection=branch' cannot be specified on this target
> 2 errors generated when compiling for gfx803.
> gmake[3]: *** [CMakeFiles/cmTC_c2fcb.dir/build.make:79: 
> CMakeFiles/cmTC_c2fcb.dir/testCXXCompiler.cxx.o] Error 1
> gmake[3]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH'
> gmake[2]: *** [Makefile:127: cmTC_c2fcb/fast] Error 2
> gmake[2]: Leaving directory 
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-B5wYLH'
> 
> 
> 
>   
> 
>   CMake will not be able to correctly generate this 

Bug#1052965: marked as done (libhandy-1: FTBFS: Failed to load icon `avatar-default-symbolic')

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 17:19:21 +
with message-id 
and subject line Bug#1052965: fixed in libhandy-1 1.8.2-3
has caused the Debian Bug report #1052965,
regarding libhandy-1: FTBFS: Failed to load icon `avatar-default-symbolic'
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.)


-- 
1052965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhandy-1
Version: 1.8.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> xvfb-run -s -noreset dh_auto_test
>   cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 
> MESON_TESTTHREADS=8 meson test
> ninja: Entering directory `/<>/obj-x86_64-linux-gnu'
> ninja: no work to do.
>  1/30 test-action-row   OK  0.21s
>  2/30 test-carousel OK  0.22s
>  3/30 test-application-window   OK  0.24s
>  4/30 test-deck OK  0.20s
>  5/30 test-combo-rowOK  0.22s
>  6/30 test-carousel-indicator-dots  OK  0.24s
>  7/30 test-avatar   FAIL0.27s   killed by signal 
> 5 SIGTRAP
> >>> NO_AT_BRIDGE=1 G_TEST_SRCDIR=/<>/tests 
> >>> G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
> >>> PYTHONDONTWRITEBYTECODE=yes G_DEBUG=gc-friendly,fatal-warnings 
> >>> MALLOC_PERTURB_=133 MALLOC_CHECK_=2 GSETTINGS_BACKEND=memory 
> >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src 
> >>> /<>/obj-x86_64-linux-gnu/tests/test-avatar
> 
>  8/30 test-expander-row OK  0.12s
>  9/30 test-carousel-indicator-lines OK  0.31s
> 10/30 test-header-group OK  0.09s
> 11/30 test-flap OK  0.12s
> 12/30 test-header-bar   OK  0.12s
> 13/30 test-leaflet  OK  0.10s
> 14/30 test-preferences-groupOK  0.10s
> 15/30 test-keypad   OK  0.13s
> 16/30 test-preferences-row  OK  0.09s
> 17/30 test-preferences-page OK  0.11s
> 18/30 test-squeezer OK  0.08s
> 19/30 test-search-bar   OK  0.10s
> 20/30 test-status-page  OK  0.10s
> 21/30 test-swipe-group  OK  0.09s
> 22/30 test-preferences-window   OK  0.13s
> 23/30 test-tab-view OK  0.09s
> 24/30 test-value-object OK  0.08s
> 25/30 test-view-switcherOK  0.08s
> 26/30 test-tab-bar  OK  0.12s
> 27/30 test-view-switcher-barOK  0.08s
> 28/30 test-window   OK  0.08s
> 29/30 test-window-handleOK  0.08s
> 30/30 test-style-managerOK  0.30s
> 
> Ok: 29  
> Expected Fail:  0   
> Fail:   1   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> 
> Full log written to 
> /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt
> ==> meson-logs/testlog.txt <==
> Log of Meson test suite run on 2023-09-26T06:34:22.684555
> 
> Inherited environment: DEB_HOST_GNU_SYSTEM=linux-gnu DFLAGS=-frelease 
> DEB_BUILD_ARCH_BITS=64 DEB_TARGET_GNU_CPU=x86_64 DEB_HOST_ARCH_OS=linux 
> USER=user42 CXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection' DEB_BUILD_GNU_TYPE=x86_64-linux-gnu 
> DEB_TARGET_MULTIARCH=x86_64-linux-gnu OBJCFLAGS='-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection' 
> DPKG_GENSYMBOLS_CHECK_LEVEL=4 DH_INTERNAL_OPTIONS='' DEB_BUILD_ARCH_CPU=amd64 
> DEB_HOST_ARCH_LIBC=gnu DEB_HOST_ARCH_ABI=base 
> HOME=/<>/debian/.debhelper/generated/_source/home 
> APT_CONFIG=/var/lib/sbuild/apt.conf SCHROOT_CHROOT_NAME=sid-amd64-sbuild 
> DEB_BUILD_ARCH_ENDIAN=little LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,-O1 
> -Wl,-z,defs' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_GNU_SYSTEM=linux-gnu 
> MAKEFLAGS=w SCHROOT_UID=1001 DEB_BUILD_ARCH_OS=linux 
> DEB_TARGET_GNU_TYPE=x86_64-linux-gnu 

Bug#1052176: marked as done (rust-bcder: CVE-2023-39914: BER/CER/DER decoder panics on invalid input (RUSTSEC-2023-0062))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 17:19:53 +
with message-id 
and subject line Bug#1052176: fixed in rust-bcder 0.7.3-1
has caused the Debian Bug report #1052176,
regarding rust-bcder: CVE-2023-39914: BER/CER/DER decoder panics on invalid 
input (RUSTSEC-2023-0062)
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.)


-- 
1052176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-bcder
Version: 0.6.1-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/NLnetLabs/bcder/pull/74
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rust-bcder.

CVE-2023-39914[0]:
| NLnet Labs’ bcder library up to and including version 0.7.2 panics
| while decoding certain invalid input data rather than rejecting the
| data with an error. This can affect both the actual decoding stage
| as well as accessing content of types that utilized delayed
| decoding.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-39914
https://www.cve.org/CVERecord?id=CVE-2023-39914
[1] https://github.com/NLnetLabs/bcder/pull/74
[2] https://nlnetlabs.nl/downloads/bcder/CVE-2023-39914.txt
[3] https://rustsec.org/advisories/RUSTSEC-2023-0062.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: rust-bcder
Source-Version: 0.7.3-1
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
rust-bcder, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated rust-bcder package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Sep 2023 13:03:46 -0400
Source: rust-bcder
Architecture: source
Version: 0.7.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: James McCoy 
Closes: 1052176
Changes:
 rust-bcder (0.7.3-1) unstable; urgency=medium
 .
   * Team upload.
   * Package bcder 0.7.3 from crates.io using debcargo 2.6.0
   * Fix various decoding issues that can lead to a panic on invalid data
 (Closes: #1052176, CVE-2023-39914)
Checksums-Sha1:
 288f6a01f3d6d27bf21a3a0403c4994ca1e32f98 2298 rust-bcder_0.7.3-1.dsc
 87f6a8416fd2c04cc5aaeb93114baf3782bb786a 63569 rust-bcder_0.7.3.orig.tar.gz
 d2d24650613bb28523420d063985f972fcdd0791 3064 rust-bcder_0.7.3-1.debian.tar.xz
 ab0895c43fb5f7e52703da42158c3ff35ed97aa0 7582 
rust-bcder_0.7.3-1_source.buildinfo
Checksums-Sha256:
 7b3003f0ea64474122fa8cb63fb3a74dfc0e6c0daa6b8c93b8f5c95f56a1ef81 2298 
rust-bcder_0.7.3-1.dsc
 bf16bec990f8ea25cab661199904ef452fcf11f565c404ce6cffbdf3f8cbbc47 63569 
rust-bcder_0.7.3.orig.tar.gz
 de56f882b5c77417abc34cf985c02062e7b17a83cbba203a4e7be35c0719b1d8 3064 
rust-bcder_0.7.3-1.debian.tar.xz
 3aa5e35d8fdd74c6e9e4f2b17639febb2bbd53db86749f8f415783ad1bc0b07a 7582 
rust-bcder_0.7.3-1_source.buildinfo
Files:
 e92d69f3e4201308da5a9646c9d7d645 2298 rust optional rust-bcder_0.7.3-1.dsc
 8c96bb7f45ba327946ec46636a96c99d 63569 rust optional 
rust-bcder_0.7.3.orig.tar.gz
 5055470e145b8ba2746878de2f781444 3064 rust optional 
rust-bcder_0.7.3-1.debian.tar.xz
 3af9f855dae086d0d0bd9041730281af 7582 rust optional 
rust-bcder_0.7.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmUTDvVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9sMoBAAlzl8pN1SL+M3d9ggrXQwLSUmipMb/90JiqaieG18IyaMIWF7ztM87xNO
vWFmVZDnvWBZK3KN2qlb8a8OMWrfOlV5C7b4uhdQtBPJY+mQ4+mbpSREQ4Pw4A7c
3nnm3BchX5lKiPIyLTaOxtaU/sA/dO1ia+Y88JnzdPUwwY4Y3nIxbtc6N5CV/3Jo
v/AhvBmZnWyh0HIR8z9XZd5E6+ocyvMKw81rLLk2Mc0iFGR1VwILffMjkCj38IRl
JEPxOP1QAzBTRr9/VK9b8msWX1zmd9NXyaNhBH0dWuvuUwpmBWB9GreRVJb2vfh+
9MjgIspunpHZza4eQQ8QhQkbkYn6Rc1FbnOIJsL0bdX4aUIU5wjyk49dk4VqAukz

Processed: Bug#1052965 marked as pending in libhandy-1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052965 [src:libhandy-1] libhandy-1: FTBFS: Failed to load icon 
`avatar-default-symbolic'
Added tag(s) pending.

-- 
1052965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052965: marked as pending in libhandy-1

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1052965 in libhandy-1 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/gnome-team/libhandy-1/-/commit/ffb8a89166adc4fa37d22be3626e7a9267e65858


Build-depend on librsvg2-common

We need the SVG loader for the avatar-default-symbolic icon.

Closes: #1052965


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052965

Bug#1052763: libgnuastro18 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgnuastro_make.so

[Mohammad Akhlaghi]

Thank you very much for this report,

The 'libgnuastro_make.so' is declared within the 
'debian/libgnuastro18.install' file (see [1] below); a comment there 
also described what it is (an extension-library for GNU Make, described 
in [2]).


Could you please point me to any other place that it should be declared? 
This is an important bug and I will fix it as soon as I know the solution.


Thank you very much,
Mohammad


[1] 
https://sources.debian.org/src/gnuastro/0.20-1/debian/libgnuastro18.install


[2] https://www.gnu.org/software/make/manual/html_node/Loading-Objects.html

Processed: Bug#1052968 marked as pending in hipcub

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052968 [src:hipcub] hipcub: FTBFS: FileNotFoundError: [Errno 2] No 
such file or directory: '/sys/class/kfd/kfd/topology/nodes/'
Added tag(s) pending.

-- 
1052968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052968: marked as pending in hipcub

[Christian Kastner]

Control: tag -1 pending

Hello,

Bug #1052968 in hipcub 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/rocm-team/hipcub/-/commit/97247d25e7b4574622959e4d55a52b968a4f3dc6


Filter cf-protection hardening from device code

Fixes a FTBFS with dpkg >= 1.22

Closes: #1052968


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052968

Bug#908947: marked as done (recent version for stable-(updates|backports))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:36:08 +
with message-id 
and subject line Bug#1052158: Removed package(s) from unstable
has caused the Debian Bug report #908947,
regarding recent version for stable-(updates|backports)
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.)


-- 
908947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: youtube-dl
Version: 2017.05.18.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the version of youtube-dl that is shipped with stretch does not work
anymore for the youtube website, making the package unusable for some
videos. It should be updated to a more recent version. If this is not
possible by Debian policy, stretch-backport should provide a recent
version.

Best regards,
Thierry


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages youtube-dl depends on:
ii  dpkg   1.18.25
ii  python33.5.3-1
ii  python3-pkg-resources  33.1.1-1

Versions of packages youtube-dl recommends:
ii  ca-certificates  20161130+nmu1+deb9u1
ii  curl 7.52.1-5+deb9u7
ii  ffmpeg   7:3.2.12-1~deb9u1
ii  mplayer  2:1.3.0-6
ii  rtmpdump 2.4+20151223.gitfa8646d.1-1+b1
ii  wget 1.18-5+deb9u2

youtube-dl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2021.12.17-2+rm

Dear submitter,

as the package youtube-dl 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/1052158

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#947745: marked as done (recent version for stable-(updates|backports))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:36:08 +
with message-id 
and subject line Bug#1052158: Removed package(s) from unstable
has caused the Debian Bug report #908947,
regarding recent version for stable-(updates|backports)
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.)


-- 
908947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: youtube-dl
Version: 2019.01.17-1.1
Severity: grave

Justification: renders package unusable

Dear maintainer,

the buster version has quit working with yt. The error message is: "YouTube
said: This video is unavailable." 2019.09.28-1 works. Due to the package's
volatility (which causes this grave bug) and given its fairly stable
dependencies, migrating recent versions into stable-updates might well be the
neatest fix to this, imho.

See also #908947.

Cheers
Kevin



-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages youtube-dl depends on:
ii  python33.7.3-1
ii  python3-pkg-resources  40.8.0-1

Versions of packages youtube-dl recommends:
ii  aria21.34.0-4
ii  ca-certificates  20190110
ii  curl 7.64.0-4
ii  ffmpeg   7:4.1.4-1~deb10u1
ii  mpv  0.29.1-1
ii  phantomjs2.1.1+dfsg-2
ii  python3-pyxattr  0.6.1-1
ii  rtmpdump 2.4+20151223.gitfa8646d.1-2
ii  wget 1.20.1-1.1

youtube-dl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2021.12.17-2+rm

Dear submitter,

as the package youtube-dl 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/1052158

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#1036272: marked as done (youtube-dl - Should this be released with Bookworm?)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:36:08 +
with message-id 
and subject line Bug#1052158: Removed package(s) from unstable
has caused the Debian Bug report #1036272,
regarding youtube-dl - Should this be released with Bookworm?
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.)


-- 
1036272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: youtube-dl
Version: 2021.12.17-2
Severity: serious

We have a maintained and uptodate fork of this package in the archive
and the release: yt-dlp.  Do we really need to release this package in a
not so usable state?

Hint: transitional packages are supposed to be at the target of a
transiton and more empty.

Bastian

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 2021.12.17-2+rm

Dear submitter,

as the package youtube-dl 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/1052158

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#943690: marked as done (src:sphinxcontrib-youtube: Maintainer email address not working)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:34:39 +
with message-id 
and subject line Bug#1051789: Removed package(s) from unstable
has caused the Debian Bug report #943690,
regarding src:sphinxcontrib-youtube: Maintainer email address not working
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.)


-- 
943690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sphinxcontrib-youtube
Version: 1.0-1
Severity: serious
Justification: Policy 3.3

Policy requires a maintainer email address that accepts mail.  Mail for
this maintainer has been failing:

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  thomi.richa...@canonical.com
host mx.canonical.com [91.189.95.10]
SMTP error from remote mail server after RCPT 
TO::
550 5.1.1 : Recipient address rejected:
User unknown in virtual alias table

 Given the error, it seems unlikely to be temporary.

 Scott K
--- End Message ---
--- Begin Message ---
Version: 1.0-1.1+rm

Dear submitter,

as the package sphinxcontrib-youtube 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/1051789

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#896369: marked as done (python-sphinxcontrib.youtube: sphinxcontrib.youtube fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:34:39 +
with message-id 
and subject line Bug#1051789: Removed package(s) from unstable
has caused the Debian Bug report #896369,
regarding python-sphinxcontrib.youtube: sphinxcontrib.youtube fails to import
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.)


-- 
896369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sphinxcontrib.youtube
Version: 1.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-sphinxcontrib.youtube importing the module 
sphinxcontrib.youtube
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/sphinxcontrib/youtube.py", line 9, in 

from sphinx.util.compat import Directive
ImportError: cannot import name Directive

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.0-1.1+rm

Dear submitter,

as the package sphinxcontrib-youtube 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/1051789

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#896348: marked as done (python3-sphinxcontrib.youtube: sphinxcontrib.youtube fails to import)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:34:39 +
with message-id 
and subject line Bug#1051789: Removed package(s) from unstable
has caused the Debian Bug report #896348,
regarding python3-sphinxcontrib.youtube: sphinxcontrib.youtube fails to import
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.)


-- 
896348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sphinxcontrib.youtube
Version: 1.0-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-sphinxcontrib.youtube importing the module 
sphinxcontrib.youtube
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/sphinxcontrib/youtube.py", line 9, in 

from sphinx.util.compat import Directive
ImportError: cannot import name 'Directive'

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.0-1.1+rm

Dear submitter,

as the package sphinxcontrib-youtube 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/1051789

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#1052011: marked as done (iscsitarget-dkms: Module fails to compile)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 18:33:48 +0200
with message-id <0fb82718-f272-0546-bc84-2e4288c52...@debian.org>
and subject line Re: iscsitarget-dkms: Module fails to compile
has caused the Debian Bug report #1052011,
regarding iscsitarget-dkms: Module fails to compile
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.)


-- 
1052011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iscsitarget-dkms
Version: 1.4.20.3+svn502-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: t...@tee-jay.org.uk

Dear Maintainer,

Trying to install this package dkms fails to compile the module


make.log is as follows:
DKMS make.log for iscsitarget-1.4.20.3+svn502 for kernel 6.1.21+ (armv7l)
Fri 15 Sep 23:04:56 BST 2023
make: Entering directory '/usr/src/linux-headers-6.1.21+'
  CC [M]  /var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/tio.o
  CC [M]  /var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.o
  CC [M]  /var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/nthread.o
  CC [M]  /var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/wthread.o
In file included from 
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/nthread.c:16:
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.h:274:19: error: 
field ‘rx_hash’ has incomplete type
  274 |  struct hash_desc rx_hash;
  |   ^~~
In file included from 
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/tio.c:7:
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.h:274:19: error: 
field ‘rx_hash’ has incomplete type
  274 |  struct hash_desc rx_hash;
  |   ^~~
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.h:275:19: error: 
field ‘tx_hash’ has incomplete type
  275 |  struct hash_desc tx_hash;
  |   ^~~
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.h:275:19: error: 
field ‘tx_hash’ has incomplete type
  275 |  struct hash_desc tx_hash;
  |   ^~~
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/nthread.c: In function 
‘iscsi_conn_init_read’:
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/nthread.c:45:17: error: 
‘struct msghdr’ has no member named ‘msg_iov’; did you mean ‘msg_inq’?
   45 |  conn->read_msg.msg_iov = conn->read_iov;
  | ^~~
  | msg_inq
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/nthread.c:46:16: error: 
‘struct msghdr’ has no member named ‘msg_iovlen’
   46 |  conn->read_msg.msg_iovlen = 1;
  |^
In file included from ./include/linux/kernel.h:26,
 from ./include/linux/cpumask.h:10,
 from ./include/linux/smp.h:13,
 from ./include/linux/lockdep.h:14,
 from ./include/linux/spinlock.h:63,
 from ./include/linux/wait.h:9,
 from ./include/linux/wait_bit.h:8,
 from ./include/linux/fs.h:6,
 from ./include/linux/highmem.h:5,
 from ./include/linux/bvec.h:10,
 from ./include/linux/blk_types.h:10,
 from ./include/linux/blkdev.h:9,
 from 
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/iscsi.h:11,
 from 
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/tio.c:7:
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/tio.c: In function 
‘tio_add_data’:
./include/linux/minmax.h:20:28: warning: comparison of distinct pointer types 
lacks a cast
   20 |  (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
  |^~
./include/linux/minmax.h:26:4: note: in expansion of macro ‘__typecheck’
   26 |   (__typecheck(x, y) && __no_side_effects(x, y))
  |^~~
./include/linux/minmax.h:36:24: note: in expansion of macro ‘__safe_cmp’
   36 |  __builtin_choose_expr(__safe_cmp(x, y), \
  |^~
./include/linux/minmax.h:45:19: note: in expansion of macro ‘__careful_cmp’
   45 | #define min(x, y) __careful_cmp(x, y, <)
  |   ^
/var/lib/dkms/iscsitarget/1.4.20.3+svn502/build/kernel/tio.c:75:25: note: in 
expansion of macro ‘min’
   75 |  const size_t to_copy = min(tio->pg_cnt * PAGE_SIZE - iter->size, len);
  | ^~~
./include/linux/minmax.h:20:28: warning: comparison of distinct pointer types 
lacks a cast
   20 |  (!!(sizeof((typeof(x) *)1 == 

Bug#1052822: mini-buildd: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 25

[Stephan Sürken]

Hi Lucas,

On Tue, 2023-09-26 at 14:43 +0200, Lucas Nussbaum wrote:
> Source: mini-buildd
> Version: 2.0.8
> Severity: serious
(..)
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
(..)
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
(..)
> > hostname: Name or service not known

is ``hostname [-f]`` not working in the build environment?

I see that ``m-b-self-signed-cerificate --help`` fails, which would add
up. Also, 2.0.8 was a source-only upload and already 'got thru' previously.

Hth!

Stephan


signature.asc
Description: This is a digitally signed message part

Bug#954560: marked as done (debdry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:53 +
with message-id 
and subject line Bug#1051718: Removed package(s) from unstable
has caused the Debian Bug report #954560,
regarding debdry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p "3.7 3.8" 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.)


-- 
954560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debdry
Version: 0.2.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

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_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_debdry/build/debdrylib
> copying debdrylib/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_debdry/build/debdrylib
> copying debdrylib/tree.py -> 
> /<>/.pybuild/cpython3_3.7_debdry/build/debdrylib
> copying debdrylib/auto.py -> 
> /<>/.pybuild/cpython3_3.7_debdry/build/debdrylib
> copying debdrylib/debdry.py -> 
> /<>/.pybuild/cpython3_3.7_debdry/build/debdrylib
> running build_scripts
> creating build
> creating build/scripts-3.7
> copying and adjusting debdry -> build/scripts-3.7
> copying git-debdry-build -> build/scripts-3.7
> changing mode of build/scripts-3.7/debdry from 644 to 755
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_debdry/build/debdrylib
> copying debdrylib/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_debdry/build/debdrylib
> copying debdrylib/tree.py -> 
> /<>/.pybuild/cpython3_3.8_debdry/build/debdrylib
> copying debdrylib/auto.py -> 
> /<>/.pybuild/cpython3_3.8_debdry/build/debdrylib
> copying debdrylib/debdry.py -> 
> /<>/.pybuild/cpython3_3.8_debdry/build/debdrylib
> running build_scripts
> creating build/scripts-3.8
> copying and adjusting debdry -> build/scripts-3.8
> copying git-debdry-build -> build/scripts-3.8
> changing mode of build/scripts-3.8/debdry from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_debdry/build; 
> python3.7 -m unittest discover -v 
> test_plainfield (test.test_control.TestCombine) ... ERROR
> test_smartfield_plain (test.test_control.TestCombine) ... ERROR
> test_smartfield_smart (test.test_control.TestCombine) ... ERROR
> test_plainfield (test.test_control.TestDiff) ... ERROR
> test_smartfield_plain (test.test_control.TestDiff) ... ERROR
> test_smartfield_smart (test.test_control.TestDiff) ... ERROR
> test_deps (test.test_fieldmerge.TestDeps) ... 
> /<>/.pybuild/cpython3_3.7_debdry/build/test/test_fieldmerge.py:61:
>  DeprecationWarning: Please use assertEqual instead.
>   self.assertEquals(f.to_string(), result)
> ok
> test_plain (test.test_fieldmerge.TestDeps) ... ok
> test_plain (test.test_fieldmerge.TestUploaders) ... ok
> test_smart (test.test_fieldmerge.TestUploaders) ... ok
> test_1 (test.test_tree.TestParse) ... ok
> 
> ==
> ERROR: test_plainfield (test.test_control.TestCombine)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/test/test_control.py", 
> line 59, in test_plainfield
> """)
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/test/test_control.py", 
> line 43, in assertCombines
> c = c1.combine("control", "./control", c2)
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/debdrylib/tree.py", line 
> 314, in combine
> res.write()
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/debdrylib/tree.py", line 
> 293, in write
> outfd.write(self.to_string())
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/debdrylib/tree.py", line 
> 282, in to_string
> sections.append(self.source.to_string())
>   File 
> "/<>/.pybuild/cpython3_3.7_debdry/build/debdrylib/tree.py", line 
> 417, in to_string
> return apt_pkg.rewrite_section(section, self.REWRITE_ORDER,
> AttributeError: module 'apt_pkg' has no attribute 

Processed: tagging 1031842, tagging 877016, tagging 1007310, tagging 1044927, tagging 1007651, tagging 1007279 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1031842 + sid experimental
Bug #1031842 [src:xdg-desktop-portal-gnome] xdg-desktop-portal-gnome: 44 
appears incompatible with GNOME Shell 43
Added tag(s) experimental and sid.
> tags 877016 + sid trixie
Bug #877016 [cpufrequtils] Time to drop cpufrequtils?
Added tag(s) sid and trixie.
> tags 1007310 - bookworm
Bug #1007310 {Done: Bas Wijnen } [src:z80asm] z80asm: please 
consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1044927 + experimental
Bug #1044927 {Done: Patrick Matthäi } [src:glusterfs] 
glusterfs: Fails to build source after successful build
Added tag(s) experimental.
> tags 1007651 - bookworm
Bug #1007651 {Done: Bastian Germann } [src:dmitry] dmitry: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007279 - bookworm
Bug #1007279 {Done: Bastian Germann } [src:yapps2] yapps2: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007064 - bookworm
Bug #1007064 {Done: Bastian Germann } [src:linklint] linklint: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007608 - bookworm
Bug #1007608 {Done: Bastian Germann } [src:awardeco] awardeco: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007321 - bookworm
Bug #1007321 {Done: Chris Lawrence } [src:makexvpics] 
makexvpics: please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007452 - bookworm
Bug #1007452 {Done: Bastian Germann } [src:xless] xless: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007489 - bookworm
Bug #1007489 {Done: Bastian Germann } [src:4g8] 4g8: please 
consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007390 - bookworm
Bug #1007390 {Done: Bastian Germann } 
[src:openoffice.org-en-au] openoffice.org-en-au: please consider upgrading to 
3.0 source format
Removed tag(s) bookworm.
> tags 1007600 - bookworm
Bug #1007600 {Done: Bastian Germann } [src:xfaces] xfaces: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1045959 + experimental
Bug #1045959 {Done: Thomas Goirand } [src:python-wrapt] 
python-wrapt: Fails to build source after successful build
Added tag(s) experimental.
> tags 1007320 - bookworm
Bug #1007320 {Done: Bastian Germann } [src:samhain] samhain: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007314 - bookworm
Bug #1007314 {Done: Bastian Germann } [src:swish-e] swish-e: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1049446 + experimental
Bug #1049446 {Done: Paul Gevers } [src:cpp-httplib] 
src:cpp-httplib: fails to migrate to testing for too long: unresolved RC issue
Added tag(s) experimental.
> reassign 1032634 src:babeltrace 1.5.11-1
Bug #1032634 {Done: Michael Jeanson } [libbabeltrace-ctf1] 
please drop transitional package libbabeltrace-ctf1 from src:babeltrace
Bug reassigned from package 'libbabeltrace-ctf1' to 'src:babeltrace'.
No longer marked as found in versions babeltrace/1.5.11-1.
No longer marked as fixed in versions babeltrace/1.5.11-2.
Bug #1032634 {Done: Michael Jeanson } [src:babeltrace] 
please drop transitional package libbabeltrace-ctf1 from src:babeltrace
Marked as found in versions babeltrace/1.5.11-1.
> fixed 1032634 1.5.11-2
Bug #1032634 {Done: Michael Jeanson } [src:babeltrace] 
please drop transitional package libbabeltrace-ctf1 from src:babeltrace
Marked as fixed in versions babeltrace/1.5.11-2.
> reassign 1032633 src:babeltrace 1.5.11-1
Bug #1032633 {Done: Michael Jeanson } 
[libbabeltrace-ctf-dev] please drop transitional package libbabeltrace-ctf-dev 
from src:babeltrace
Bug reassigned from package 'libbabeltrace-ctf-dev' to 'src:babeltrace'.
No longer marked as found in versions babeltrace/1.5.11-1.
No longer marked as fixed in versions babeltrace/1.5.11-2.
Bug #1032633 {Done: Michael Jeanson } [src:babeltrace] 
please drop transitional package libbabeltrace-ctf-dev from src:babeltrace
Marked as found in versions babeltrace/1.5.11-1.
> fixed 1032633 1.5.11-2
Bug #1032633 {Done: Michael Jeanson } [src:babeltrace] 
please drop transitional package libbabeltrace-ctf-dev from src:babeltrace
Marked as fixed in versions babeltrace/1.5.11-2.
> tags 1047889 + experimental
Bug #1047889 {Done: Daniel Baumann } 
[src:pendulum] pendulum: Fails to build source after successful build
Added tag(s) experimental.
> tags 1007329 - bookworm
Bug #1007329 {Done: Bastian Germann } [src:loadwatch] 
loadwatch: please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007029 - bookworm
Bug #1007029 {Done: Keith Packard } 
[src:binutils-arm-none-eabi] binutils-arm-none-eabi: please consider upgrading 
to 3.0 source format
Removed tag(s) bookworm.
> tags 1007491 - bookworm
Bug #1007491 {Done: Bastian Germann } [src:libranlip] 
libranlip: please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 

Bug#1015138: marked as done (gnome-books: FTBFS: ../data/meson.build:6:0: ERROR: Sandbox violation: Tried to grab file gd-main-view.h from a nested subproject.)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:24 +
with message-id 
and subject line Bug#1051655: Removed package(s) from unstable
has caused the Debian Bug report #1015138,
regarding gnome-books: FTBFS: ../data/meson.build:6:0: ERROR: Sandbox 
violation: Tried to grab file gd-main-view.h from a nested subproject.
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.)


-- 
1015138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-books
Version: 40.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-books
> Project version: 40.0
> C compiler for the host machine: cc (gcc 11.3.0 "cc (Debian 11.3.0-4) 11.3.0")
> C linker for the host machine: cc ld.bfd 2.38.90.20220713
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gdk-pixbuf-2.0 found: YES 2.42.8
> Run-time dependency gjs-1.0 found: YES 1.72.0
> Run-time dependency evince-document-3.0 found: YES 42.3
> Run-time dependency evince-view-3.0 found: YES 42.3
> Run-time dependency glib-2.0 found: YES 2.72.3
> Run-time dependency gnome-desktop-3.0 found: YES 42.3
> Run-time dependency gobject-introspection-1.0 found: YES 1.72.0
> Run-time dependency gtk+-3.0 found: YES 3.24.34
> Run-time dependency tracker-sparql-3.0 found: YES 3.1.2
> Run-time dependency webkit2gtk-4.0 found: YES 2.36.4
> Library m found: YES
> Run-time dependency libgepub-0.6 found: YES 0.6.0
> Checking for function "cairo_surface_set_device_scale" with dependencies 
> gjs-1.0, evince-document-3.0, evince-view-3.0, glib-2.0, gnome-desktop-3.0, 
> gobject-introspection-1.0, gtk+-3.0, tracker-sparql-3.0, webkit2gtk-4.0, -lm: 
> YES 
> 
> Executing subproject libgd 
> 
> libgd| Project name: libgd
> libgd| Project version: undefined
> libgd| C compiler for the host machine: cc (gcc 11.3.0 "cc (Debian 11.3.0-4) 
> 11.3.0")
> libgd| C linker for the host machine: cc ld.bfd 2.38.90.20220713
> libgd| Dependency gtk+-3.0 found: YES 3.24.34 (cached)
> libgd| Library m found: YES
> libgd| Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached)
> libgd| Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached)
> libgd| Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner)
> libgd| Dependency gobject-introspection-1.0 found: YES 1.72.0 (cached)
> libgd| Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler)
> libgd| Build targets in project: 5
> libgd| Subproject libgd finished.
> 
> Configuring config.h using configuration
> Configuring config.js using configuration
> ../src/meson.build:82: WARNING: Project targets '>= 0.49.0' but uses feature 
> introduced in '0.50.0': install arg in configure_file.
> Configuring org.gnome.Books.service using configuration
> ../src/meson.build:90: WARNING: Project targets '>= 0.49.0' but uses feature 
> introduced in '0.50.0': install arg in configure_file.
> Configuring org.gnome.Books using configuration
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> 
> ../data/meson.build:6:0: ERROR: Sandbox violation: Tried to grab file 
> gd-main-view.h from a nested subproject.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-07-16T05:58:32.557833
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-books
> Project version: 40.0
> Sanity testing C compiler: cc
> Is cross compiler: False.
> Sanity check compiler command line: cc 

Bug#1037375: marked as done (gnome-books: build-depends on transitional package libgdk-pixbuf2.0-dev)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:24 +
with message-id 
and subject line Bug#1051655: Removed package(s) from unstable
has caused the Debian Bug report #1037375,
regarding gnome-books: build-depends on transitional package 
libgdk-pixbuf2.0-dev
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.)


-- 
1037375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-books
Version: 40.0-3
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 40.0-3+rm

Dear submitter,

as the package gnome-books 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/1051655

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#1040322: marked as done (debdry: should not ship test data in /usr/lib/python3/dist-packages/control)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:53 +
with message-id 
and subject line Bug#1051718: Removed package(s) from unstable
has caused the Debian Bug report #1040322,
regarding debdry: should not ship test data in 
/usr/lib/python3/dist-packages/control
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.)


-- 
1040322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdry
Version: 0.2.2-1
Severity: serious

debdry creates a control file in its test suite. This file happens to
get installed into /usr/lib/python3/dist-packages/control and this
happens to cause an undeclared file conflict with python3-kombu. I'm
filing this with debdry, because it clearly should not be installing
this file.

Helmut
--- End Message ---
--- Begin Message ---
Version: 0.2.2-1+rm

Dear submitter,

as the package debdry 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/1051718

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#1019269: marked as done (gnome-books: Adapt to libgepub 0.7)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:24 +
with message-id 
and subject line Bug#1051655: Removed package(s) from unstable
has caused the Debian Bug report #1019269,
regarding gnome-books: Adapt to libgepub 0.7
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.)


-- 
1019269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-books
Version: 40.0-3
Severity: serious
Tags: bookworm sid ftbfs

gnome-books needs to be updated to build against libgepub 0.7. This is
probably a fairly simple change except that
https://bugs.debian.org/1015138 is a bit awkward to deal with.

GNOME doesn't support GNOME Books any more. The recommended
replacement app is Foliate.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 40.0-3+rm

Dear submitter,

as the package gnome-books 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/1051655

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#1014423: marked as done (gnome-books: unmaintained, depends on gnome-online-miners)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:31:24 +
with message-id 
and subject line Bug#1051655: Removed package(s) from unstable
has caused the Debian Bug report #1014423,
regarding gnome-books: unmaintained, depends on gnome-online-miners
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.)


-- 
1014423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-books
Version: 40.0-3
Severity: serious

gnome-books has been archived. That means that bug reports, bug fixes,
translations, etc. are no longer being accepted for it.

https://gitlab.gnome.org/GNOME/gnome-books

We will likely need to remove gnome-books from Debian soon because its
dependency, gnome-online-miners, is interfering with completing the
libsoup3 transition for evolution-data-server and friends. That
transition is required to package GNOME 43.

The recommended replacement app is foliate which is already available
in Debian Unstable.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 40.0-3+rm

Dear submitter,

as the package gnome-books 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/1051655

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#1052035: marked as done (ulex0.8: FTBFS: Error: This expression has type char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected of type 'a ref)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:27:42 +
with message-id 
and subject line Bug#1051377: Removed package(s) from unstable
has caused the Debian Bug report #1052035,
regarding ulex0.8: FTBFS: Error: This expression has type char Stream.t -> 
(MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected 
of type 'a ref
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.)


-- 
1052035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ulex0.8
Version: 1.2-2
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=ulex0.8=amd64=1.2-2%2Bb5=1694049779=0

ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
+ ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
findlib: [WARNING] Interface topdirs.cmi occurs in several directories: 
/usr/lib/ocaml, /usr/lib/ocaml/compiler-libs
File "pa_ulex.ml", line 267, characters 26-44:
267 |   let old_parse_implem = !Pcaml.parse_implem in
^^
Error: This expression has type
 char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status
   but an expression was expected of type 'a ref
Command exited with code 2.
make[2]: *** [Makefile:5: all] Error 10

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.2-2+rm

Dear submitter,

as the package ulex0.8 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/1051377

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#1051398: marked as done (collada2gltf: Missing source in d/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:28:07 +
with message-id 
and subject line Bug#1051399: Removed package(s) from unstable
has caused the Debian Bug report #1051398,
regarding collada2gltf: Missing source in d/copyright
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.)


-- 
1051398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: collada2gltf
Version: 20140924-9
Severity: serious

The upstream source is missing from d/copyright. This is a Policy violation.
Please add the upstream URL where the tarball was obtained.
--- End Message ---
--- Begin Message ---
Version: 20140924-9+rm

Dear submitter,

as the package collada2gltf 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/1051399

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#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Mark Hindley]

Control: tags -1 unreproducible

Lucas,

Thanks for this. However, I am currently unable to repoduce this failure in my
customary pbuilder setup. And it doesn't appear at reproducible builds either[1]

On Tue, Sep 26, 2023 at 03:45:26PM +0200, Lucas Nussbaum wrote:
> 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.

My successful pbuilder log is attached.

Mark


[1]  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/insserv.html

dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (= 13) 
po-debconf
W: Unmet build-dependency in source
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building insserv using existing ./insserv_1.24.0.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building insserv in insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: building insserv in insserv_1.24.0-1.dsc
I: Generated dsc will be overwritten by build result; not generating changes 
file
dpkg-source: info: unapplying 0005-Fix-spelling-error-in-manpage.patch
dpkg-source: info: unapplying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: unapplying warn_in_ignore_mode.patch
dpkg-source: info: unapplying 110_portmap.patch
dpkg-source: info: unapplying 11_debian_conf.patch
dpkg-source: info: unapplying install-binaries-ignore-PREFIX.patch
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.20068
I: forking: cp -al /var/cache/pbuilder/base-sid.cow 
/var/cache/pbuilder/build/cow.20068
I: removed stale ilistfile /var/cache/pbuilder/build/cow.20068/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.20068 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts '  '--no-pre-clean'' 
--buildplace /var/cache/pbuilder/build/cow.20068 --buildresult 
/home/mark/src/debian/build --mirror http://deb.debian.org/debian 
--distribution sid --no-targz --internal-chrootexec 'chroot 
/var/cache/pbuilder/build/cow.20068 cow-shell' 
/home/mark/src/debian/build/insserv_1.24.0-1.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Tue Sep 26 17:05:48 BST 2023
I: pbuilder-time-stamp: 1695744348
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage for 
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.dsc]
I: copying [/home/mark/src/debian/build/insserv_1.24.0.orig.tar.gz]
I: copying [/home/mark/src/debian/build/insserv_1.24.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (insserv_1.24.0-1.dsc)
dpkg-source: info: extracting insserv in insserv-1.24.0
dpkg-source: info: unpacking insserv_1.24.0.orig.tar.gz
dpkg-source: info: unpacking insserv_1.24.0-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying install-binaries-ignore-PREFIX.patch
dpkg-source: info: applying 11_debian_conf.patch
dpkg-source: info: applying 110_portmap.patch
dpkg-source: info: applying warn_in_ignore_mode.patch
dpkg-source: info: applying 
0004-Fix-spurious-warnings-about-unknown-virtual-dependen.patch
dpkg-source: info: applying 0005-Fix-spelling-error-in-manpage.patch
I: using fakeroot in build.
I: Installing the build-deps
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
starting
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D04add-backports 
finished
I: user script /var/cache/pbuilder/build/cow.20068/tmp/hooks/D05apt-update 
starting

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 http://deb.debian.org/debian unstable InRelease [195 kB]
Get:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index 
[63.6 kB]
Ign:2 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
Get:3 http://deb.debian.org/debian unstable/main Translation-en.diff/Index 
[63.6 kB]
Ign:3 http://deb.debian.org/debian unstable/main 

Processed: Re: Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible
Bug #1052942 [src:insserv] insserv: FTBFS: insserv: Could not read script 
nolsbheader: No such file or directory
Added tag(s) unreproducible.

-- 
1052942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052918: marked as done (golang-github-appc-goaci: FTBFS: make: *** [debian/rules:7: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:25:52 +
with message-id 
and subject line Bug#1051333: Removed package(s) from unstable
has caused the Debian Bug report #1052918,
regarding golang-github-appc-goaci: FTBFS: make: *** [debian/rules:7: binary] 
Error 25
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-appc-goaci
Version: 0.1.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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
> dh binary --buildsystem=golang --with=golang
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/appc/goaci github.com/appc/goaci/proj2aci
> src/github.com/appc/goaci/proj2aci/cmake.go:27:2: cannot find package 
> "golang.org/x/tools/go/vcs" in any of:
>   /usr/lib/go-1.21/src/golang.org/x/tools/go/vcs (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/tools/go/vcs 
> (from $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 
> github.com/appc/goaci github.com/appc/goaci/proj2aci returned exit code 1
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/golang-github-appc-goaci_0.1.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: 0.1.1-2+rm

Dear submitter,

as the package golang-github-appc-goaci 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/1051333

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#995113: marked as done (dpkg-sig: mangles "Files" field of .changes files, but not "Checksums-*")

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:21:11 +
with message-id 
and subject line Bug#1049449: Removed package(s) from unstable
has caused the Debian Bug report #995113,
regarding dpkg-sig: mangles "Files" field of .changes files, but not 
"Checksums-*"
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.)


-- 
995113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-sig
Version: 0.13.1+nmu4
Severity: serious
X-Debbugs-Cc: ftpmas...@debian.org

dpkg-sig mangles the "Files" field of .changes files here:

https://sources.debian.org/src/dpkg-sig/0.13.1+nmu4/dpkg-sig/#L828

However, it does not modify the "Checksums-*" fields as well.  This
results in broken files.  Note that the last maintainer upload for
dpkg-sig was in 2006[1] where there were no "Checksums-*" fields yet.

Besides this bug, I'm not sure if keeping dpkg-sig in the archive is
useful given it has not been maintained for well over a decade.

Ansgar

  [1]: https://tracker.debian.org/news/461737/accepted-dpkg-sig-013-source-all/
--- End Message ---
--- Begin Message ---
Version: 0.13.1+nmu4+rm

Dear submitter,

as the package dpkg-sig 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/1049449

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#1002312: marked as done (gnu-smalltalk-browser: Smalltalk browser fails to start)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:21:42 +
with message-id 
and subject line Bug#1049451: Removed package(s) from unstable
has caused the Debian Bug report #1002312,
regarding gnu-smalltalk-browser: Smalltalk browser fails to start
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.)


-- 
1002312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnu-smalltalk-browser
Version: 3.2.5-1.3+b3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: be...@fams.de

Dear Maintainer,

   * What led up to the situation?

Tried to run the GNU Smalltalk Browser application.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Installed the gst-smalltalk-browser package and run 'gst-browser' from the
command line.

   * What was the outcome of this action?

Got the following error message:

a Smalltalk Stream:2: Aborted
a Smalltalk Stream:2: Error occurred while not in byte code interpreter!!
/lib/libgst.so.7(+0x74607)[0x7f429c214607]
/lib/x86_64-linux-gnu/libc.so.6(+0x3cef0)[0x7f429c017ef0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f429c017e71]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x112)[0x7f429c001536]
/lib/libgst.so.7(+0x10c04)[0x7f429c1b0c04]
/lib/x86_64-linux-gnu/libsigsegv.so.2(+0x129c)[0x7f429bfd629c]
/lib/x86_64-linux-gnu/libc.so.6(+0x3cef0)[0x7f429c017ef0]
/lib/x86_64-linux-
gnu/libgobject-2.0.so.0(g_type_check_is_value_type+0x1e)[0x7f427a1d4a7e]
/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x216bae)[0x7f427a4cbbae]
/lib/x86_64-linux-
gnu/libgtk-x11-2.0.so.0(gtk_list_store_new+0xa8)[0x7f427a3e8cf8]
Aborted

Application stopped.

   * What outcome did you expect instead?

Starting the GNU Smalltalk browser.

   * Other related information.

This seems to be to https://stackoverflow.com/questions/52766461/gst-browser-
fails-to-start though the bug is different from the ones linked from there.
libgtk2.0-dev and libgtk2.0-0 are both installed, which are referenced as a
solution to the problem.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 gnu-smalltalk-browser depends on:
ii  gnu-smalltalk 3.2.5-1.3+b3
ii  gnu-smalltalk-common  3.2.5-1.3
ii  libgtk2-gst   3.2.5-1.3+b3

gnu-smalltalk-browser recommends no packages.

gnu-smalltalk-browser suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.2.5-1.3+rm

Dear submitter,

as the package gnu-smalltalk 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/1049451

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#1042195: marked as done (rust-sha3-0.9: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 16:17:57 +
with message-id 
and subject line Bug#1042909: Removed package(s) from unstable
has caused the Debian Bug report #1042195,
regarding rust-sha3-0.9: FTBFS: build-dependency not installable: 
librust-block-padding-0.2+default-dev
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.)


-- 
1042195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-sha3-0.9
Version: 0.9.1-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-block-buffer-0.9+block-padding-dev, 
> librust-block-buffer-0.9+default-dev, librust-digest-0.9+default-dev, 
> librust-digest-0.9+std-dev, librust-keccak-0.1+default-dev, 
> librust-opaque-debug-0.3+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-block-buffer-0.9+block-padding-dev, 
> librust-block-buffer-0.9+default-dev, librust-digest-0.9+default-dev, 
> librust-digest-0.9+std-dev, librust-keccak-0.1+default-dev, 
> librust-opaque-debug-0.3+default-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 [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [466 B]
> Get:5 copy:/<>/apt_archive ./ Packages [542 B]
> Fetched 1965 B in 0s (136 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  librust-block-buffer-0.9+block-padding-dev : Depends: 
> librust-block-padding-0.2+default-dev but it is not installable
> 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/2023/07/26/rust-sha3-0.9_0.9.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.9.1-2+rm

Dear submitter,

as the package rust-sha3-0.9 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/1042909

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.

Processed: 1052773

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1052773 https://github.com/jaraco/tempora/issues/25
Bug #1052773 [src:python-tempora] python-tempora: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/jaraco/tempora/issues/25'.
> tags 1052773 + confirmed
Bug #1052773 [src:python-tempora] python-tempora: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) confirmed.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1052773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052261: marked as done (librust-pkcs5-dev: impossible to install: depends on missing package librust-scrypt-0.11-dev)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 19:06:08 +0300
with message-id 
and subject line rust-scrypt is now in unstable
has caused the Debian Bug report #1052261,
regarding librust-pkcs5-dev: impossible to install: depends on missing package 
librust-scrypt-0.11-dev
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.)


-- 
1052261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-pkcs5-dev
Version: 0.7.1-1+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

librust-pkcs5-dev depends on missing package librust-scrypt-0.11-dev
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmUJ1HsACgkQLHwxRsGg
ASGCyQ/+KIHJJDQnT6vwGP0i13f7Xo/lF/2ZOw0MBASlV+8a5/520+1YN4QqXAll
u+BCXHCrRyz6Q4OnMsJdCKOBXWWnGOHHW10En6JENWRFRn2xdsp93Vc+2n4mGMx3
6JhI2kobfH5Vlr0wr1bYI1ydnOefyAA5SaHMiAJLHvznisvpbUJaD9U8yVk30ncG
yFBKEBY05u83rzGh27GHDb/+//nBob2i/tOIplWR5ynz8+4T7CKbrGEiV1obVfZu
dNUdixJ4pqsKFS3iyBp4NrPzJXSD+Ne5s02mO+Xy3arOUb2jDw/08B1xMA6ZkbLL
UALEeauPxdUQuKQiJAKxNFfJk7Z0Bab4cNRtim/Uy8t9jrWSLJ49cKwd+J9jfhPa
xMvqyQl68nO1W1P6RXQDOm2WZDNIUOLuMaUULyMjLWXRqOwgwUSs4NLqNpbPh8LI
rPYze43mnvKCG3y/yk28H2LOK6n+4FhEXWsykn5Lf0xL5uec4DKtK/FRh84MB9D1
dmWtdYjgacrHaPzBnBesBwsm0oWl+mup7/4vIXrK1aee+zyMb4Pfkm8e1FYpCqKG
o1T1CeSOfy1u5a7a5eyMHrPHov1oIeFkoumQtZVXGUp+2fkxeq22mg2lSytFFyBk
QbuMKJPc3THsAg4Q6P8AqttFxL5hmxdGc+ZQUnVNvw1nQdMYOe8=
=ewt/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
rust-scrypt is now in unstable.

cu
Adrian--- End Message ---

Bug#1039529: applied patch to ITK

[Steven Robbins]

Hi,

Just FYI: I applied the suggested patch  (thanks Flavien!) to ITK.  Let me 
know if "sight" now builds.

-Steve


signature.asc
Description: This is a digitally signed message part.

Processed: retitle 1052965 to libhandy-1: FTBFS: Failed to load icon `avatar-default-symbolic'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1052965 libhandy-1: FTBFS: Failed to load icon 
> `avatar-default-symbolic'
Bug #1052965 [src:libhandy-1] libhandy-1: FTBFS: # Handy-DEBUG: Settings portal 
not found: Failed to execute child process ?dbus-launch? (No such file or 
directory)
Changed Bug title to 'libhandy-1: FTBFS: Failed to load icon 
`avatar-default-symbolic'' from 'libhandy-1: FTBFS: # Handy-DEBUG: Settings 
portal not found: Failed to execute child process ?dbus-launch? (No such file 
or directory)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052707: marked as done (node-glob has an unsatisfiable dependency on node-mismatch (>= 9))

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 15:49:56 +
with message-id 
and subject line Bug#1052707: fixed in node-minimatch 9.0.3-3
has caused the Debian Bug report #1052707,
regarding node-glob has an unsatisfiable dependency on node-mismatch (>= 9)
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.)


-- 
1052707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-glob
Version: 8.0.3+~cs8.4.15-3
Severity: serious
Tags: ftbfs
Control: affects -1 + src:node-shiny-server

node-shiny-server FTBFS, because one of its build-depends, node-glob has
an unsatisfiable dependency on node-mismatch (>= 9). It does not seem
like this resolves itself. Thus filing an FTBFS bug. Note that this bug
is filed with node-glob as it causes the FTBFS, not because it FTBFS
itself.

Helmut
--- End Message ---
--- Begin Message ---
Source: node-minimatch
Source-Version: 9.0.3-3
Done: Jérémy Lal 

We believe that the bug you reported is fixed in the latest version of
node-minimatch, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-minimatch 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: Tue, 26 Sep 2023 17:26:15 +0200
Source: node-minimatch
Binary: node-minimatch
Built-For-Profiles: nocheck
Architecture: source all
Version: 9.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 node-minimatch - Convert glob expressions into RegExp objects for Node.js
Closes: 1052707
Changes:
 node-minimatch (9.0.3-3) unstable; urgency=medium
 .
   * Team upload
   * ts-node is required for nocheck profile
   * binary upload to break circular dependency. Closes: #1052707.
Checksums-Sha1:
 ea91a9d80c99da7529c74c95a2eea5fd8a70c0bd 2161 node-minimatch_9.0.3-3.dsc
 cd36ee1671051fd5c1eb8344f6010419a093f955 4424 
node-minimatch_9.0.3-3.debian.tar.xz
 0b247595fd85df696fa715de2c20dc4b31dd0236 50824 node-minimatch_9.0.3-3_all.deb
 9a1179ba316454225cb085d55f2870981fd304cd 8765 
node-minimatch_9.0.3-3_amd64.buildinfo
Checksums-Sha256:
 b7d42b0742fabed5096c2090e5a600969bcb12137a76c6b253d3a9dfc477994f 2161 
node-minimatch_9.0.3-3.dsc
 4d4643f4bcbe5479ac540f338d5ff3cbdf4b06617a08ed442995e2381dc24927 4424 
node-minimatch_9.0.3-3.debian.tar.xz
 b400c84c2a41aa9ad8e903d839d977a95e681a01a3207e3edf2e994a85a58151 50824 
node-minimatch_9.0.3-3_all.deb
 92afb46a686c70789346c10e5db06bfd64ea10ef671f31842686fb490d45e5c5 8765 
node-minimatch_9.0.3-3_amd64.buildinfo
Files:
 3bff8601e3d2da4963cb418c9c196c5a 2161 javascript optional 
node-minimatch_9.0.3-3.dsc
 5f9388e5070ac7fe3eeab39c08eed903 4424 javascript optional 
node-minimatch_9.0.3-3.debian.tar.xz
 b1cdaae17bc5e337999285ab1c31 50824 javascript optional 
node-minimatch_9.0.3-3_all.deb
 8f084ff3632a3d5f221a444ac7af328c 8765 javascript optional 
node-minimatch_9.0.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmUS+OcSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN09YIP/10BHAL0oiJAHt23PwvvfUhbEUVEOhoA
J7VdcWJgM8QHlo4+uhWjLljRnSm91pnP/PmEypIke40A6EdVzhxLGCKH0I8hI1+B
QA+jUvf4qaJ516txShzxFxL3t7v857apEeom8yuFjqOD4FviTHh9UkwrGklNKQB1
R9J/vJA0CfKG3fSujVu/qjTPob3DdLOsuDywN+XD0i3jq9gAW0x3NQWz/2LyQbzD
MUuutsqzrLKmztMP20NN7sCw+BMc+aGjnHsv+P/Qo+AX7Q5jAWvLp5No7qH5eeAk
r0oVIExkTM1hpuX46W4d6GaHj9025hGYzDvPBBtWxeF1GlgajFD9WrWgGEJKHGru
0JtLibM4SU1D4wwKayl250vGj7gDx5+PtFR5cVWvOJv/Qpv8kgyBJLIRXwo0wjvc
liYOAciJdZIKWFQaXOonSyENkjf9gomjdd58v34kWPO8GyOqU1/8bKKveSvKgLwX
sfxKZ2DAKfFCUYJd6jM8U86+GGjNTx5wJp2X8SKk8kNAEqn0GGHCaPZb0QJEcjxo
BbePjS/wUfPeHPIuuSCK9XACqFpin4TRPQTW6H0qNokApzxfdwfKUgGCE8GVAaZl
HaxKfcQPxDXqjZUiHVm+LMbqvzVqpdnMFgmvoTnUusJmzQ9YCMarowSdzS01kAmg
FAeLRKBc8bNV
=l8QI
-END PGP SIGNATURE End Message ---

Bug#1037411: marked as done (nautilus-owncloud: menu doesn't appear due to nautilus API changes)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 15:50:12 +
with message-id 
and subject line Bug#1037411: fixed in owncloud-client 4.2.0.11670+dfsg-1
has caused the Debian Bug report #1037411,
regarding nautilus-owncloud: menu doesn't appear due to nautilus API changes
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.)


-- 
1037411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nautilus-owncloud
Version: 2.11.0.8354+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: micha...@gmail.com

Dear Maintainer,

The version of nautilus shipped in bookworm has a different API from
what is expected by the shell extension in the nautilus-owncloud
package. The sync status icons are correctly displayed, but the owncloud
menu doesn't appear, making this package essentially unusable.

When starting nautilus, the following error is displayed:

TypeError: MenuExtension_ownCloud.get_file_items() missing 1 required 
positional argument: 'files'

The bug has been fixed in https://github.com/owncloud/client/pull/10075
and would need to be backported to the stable package version. It looks
like some work was done in
https://salsa.debian.org/owncloud-team/owncloud-client/-/merge_requests/2
but never completed.

Best regards,
Micha

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nautilus-owncloud depends on:
ii  nautilus  43.2-1
ii  owncloud-client   2.11.0.8354+dfsg-1+b1
ii  owncloud-client-data  2.11.0.8354+dfsg-1
ii  python3   3.11.2-1+b1
ii  python3-nautilus  4.0-1+b1

nautilus-owncloud recommends no packages.

Versions of packages nautilus-owncloud suggests:
pn  nautilus-script-manager  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: owncloud-client
Source-Version: 4.2.0.11670+dfsg-1
Done: Pierre-Elliott Bécue 

We believe that the bug you reported is fixed in the latest version of
owncloud-client, 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 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated owncloud-client 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Sep 2023 17:06:45 +0200
Source: owncloud-client
Architecture: source
Version: 4.2.0.11670+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ownCloud for Debian maintainers 

Changed-By: Pierre-Elliott Bécue 
Closes: 1037411 1052645
Changes:
 owncloud-client (4.2.0.11670+dfsg-1) unstable; urgency=medium
 .
   * New upstream release 4.2.0.11670+dfsg
 (Closes: #1052645, #1037411)
Checksums-Sha1:
 497235956694f63dfc305774789363855cdef96d 2976 
owncloud-client_4.2.0.11670+dfsg-1.dsc
 ac52af2a3d7c60642a6bafbcc1b78e7a9dc62b1d 3917988 
owncloud-client_4.2.0.11670+dfsg.orig.tar.xz
 aa60cf78982650a354407d5a021bed9c0fa176e8 20592 
owncloud-client_4.2.0.11670+dfsg-1.debian.tar.xz
 aea1e2e9a6195dc14c91099c61b28e90b615a2bb 22356 
owncloud-client_4.2.0.11670+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 ab6efb04bee26d7f0303cf71bfd799673c5675892e48327fd46ef8839fb35e36 2976 
owncloud-client_4.2.0.11670+dfsg-1.dsc
 db0805912735b06bdcf64fefca8869c00faf1b9e30e425b1d8d100104669ced6 3917988 
owncloud-client_4.2.0.11670+dfsg.orig.tar.xz
 f231f41b487c7a157989b01b3ff5705137709666cf60214bfee95a61bb22d73b 20592 
owncloud-client_4.2.0.11670+dfsg-1.debian.tar.xz
 ee0babfe80dfc839ef0dc174abc9db9a604f44bb194eaa26c71ca556ecda6201 22356 
owncloud-client_4.2.0.11670+dfsg-1_amd64.buildinfo
Files:
 feb11cf5d5efbdae2d02896585896d0a 2976 net optional 
owncloud-client_4.2.0.11670+dfsg-1.dsc
 b1367ea51845d4b6672d4c5a80863273 3917988 net optional 
owncloud-client_4.2.0.11670+dfsg.orig.tar.xz
 

Processed: Re: Bug#1052828: trurl: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1052828 https://github.com/curl/trurl/issues/239
Bug #1052828 [src:trurl] trurl: FTBFS: dh_auto_test: error: make -j8 test 
returned exit code 2
Set Bug forwarded-to-address to 'https://github.com/curl/trurl/issues/239'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052828: trurl: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Michael Ablassmeier]

hi,

On Tue, Sep 26, 2023 at 03:24:16PM +0200, Lucas Nussbaum wrote:
> > 96: failed --verify --json ftp://example.org '' git://curl.se/
> > --- stdout --- 
> > expected:
> > [{'url': 'ftp://example.org/', 'parts': {'scheme': 'ftp', 'host': 
> > 'example.org', 'path': '/'}}]
> > got:
> > [{'url': 'ftp://example.org/', 'parts': {'scheme': 'ftp', 'host': 
> > 'example.org', 'path': '/'}}]
> > --- returncode --- 
> > expected:
> > 9
> > got:
> > 9
> > --- stderr --- 
> > expected:
> > 'trurl error: No host part in the URL []\ntrurl error: Try trurl -h for 
> > help\n'
> > got:
> > 'trurl error: Malformed input to a URL function []\ntrurl error: Try trurl 
> > -h for help\n'

i can reproduce this, also with the most recent upstream version,
not quite sure where the issue is in detail yet.

Will forward upstream.

bye,
- michael

Processed: tagging 1052656, tagging 1037602, tagging 1041999, tagging 1051573, tagging 1050676, tagging 1051980 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1052656 + sid trixie
Bug #1052656 [src:python-duniterpy] python-duniterpy 1.1.0-3 regressed with 
python-libnacl 2.1.0-1
Added tag(s) sid and trixie.
> tags 1037602 + experimental
Bug #1037602 {Done: Thomas Goirand } [src:ceph] ceph: ftbfs 
with GCC-13
Added tag(s) experimental.
> tags 1041999 + sid trixie
Bug #1041999 [src:tgt] tgt: Drop glusterfs support for 32-bit architectures
Added tag(s) trixie and sid.
> tags 1051573 + experimental
Bug #1051573 {Done: Dennis Braun } [src:bambootracker] 
bambootracker: FTBFS with RtAudio 6
Added tag(s) experimental.
> tags 1050676 + experimental
Bug #1050676 [graphviz] enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: 
Assertion `np->cells[0]' failed.
Added tag(s) experimental.
> tags 1051980 + experimental
Bug #1051980 [src:lib2geom] FTBFS on i386: angle-test/bezier-test fail
Added tag(s) experimental.
> tags 1050236 + experimental
Bug #1050236 [inkscape] inkscape: FTBFS: 30 - test_lpe (Failed)
Added tag(s) experimental.
> tags 1042226 + experimental
Bug #1042226 {Done: Thomas Goirand } [src:python-eventlet] 
python-eventlet: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] 
Error 1
Added tag(s) experimental.
> tags 1028104 + experimental
Bug #1028104 {Done: Andreas Beckmann } [libboost-dev] 
libboost-dev: Boost with C++20 uses unavailable std functions
Ignoring request to alter tags of bug #1028104 to the same tags previously set
> tags 1042051 + experimental
Bug #1042051 {Done: Adrian Bunk } [src:sqlalchemy] sqlalchemy: 
FTBFS: Could not import extension sphinxcontrib.jquery (exception: No module 
named 'sphinxcontrib')
Added tag(s) experimental.
> tags 1038630 + experimental
Bug #1038630 [cinnamon] cinnamon: depends on obsolete policykit-1-gnome
Added tag(s) experimental.
> tags 1052430 + sid trixie
Bug #1052430 [pastedeploy] pastedeploy: FTBFS against dh-python 6.20230825
Added tag(s) trixie and sid.
> found 1052430 3.0.1-5
Bug #1052430 [pastedeploy] pastedeploy: FTBFS against dh-python 6.20230825
There is no source info for the package 'pastedeploy' at version '3.0.1-5' with 
architecture ''
Unable to make a source version for version '3.0.1-5'
Marked as found in versions 3.0.1-5.
> tags 1051880 + experimental
Bug #1051880 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:faust] faust: FTBFS with llvm-toolchain-16 as default
Added tag(s) experimental.
> tags 1052513 + experimental
Bug #1052513 [src:intel-compute-runtime] intel-compute-runtime: FTBFS
Added tag(s) experimental.
> found 1039427 4.2-2.4
Bug #1039427 [xsp] xsp: ships sysv-init script without systemd unit
There is no source info for the package 'xsp' at version '4.2-2.4' with 
architecture ''
Unable to make a source version for version '4.2-2.4'
Marked as found in versions 4.2-2.4.
> tags 1039427 + sid trixie
Bug #1039427 [xsp] xsp: ships sysv-init script without systemd unit
Added tag(s) trixie and sid.
> tags 1051560 + experimental
Bug #1051560 [src:jpeg-xl] jpeg-xl: FTBFS: failing test conformance_tooling_test
Added tag(s) experimental.
> fixed 1051560 0.9.0~git20230623.689da0f-4
Bug #1051560 [src:jpeg-xl] jpeg-xl: FTBFS: failing test conformance_tooling_test
Marked as fixed in versions jpeg-xl/0.9.0~git20230623.689da0f-4.
> tags 1051189 + experimental
Bug #1051189 [intel-opencl-icd] intel-opencl-icd: Uninstallable since 
intel-graphics-compiler 1.0.14896.8-1 upload
Added tag(s) experimental.
> tags 1051336 + sid trixie
Bug #1051336 [src:cecil] cecil: New upstream version available
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1028104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028104
1037602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037602
1038630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038630
1039427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039427
1041999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041999
1042051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042051
1042226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042226
1050236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050236
1050676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050676
1051189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051189
1051336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051336
1051560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051560
1051573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051573
1051880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051880
1051980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051980
1052430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052430
1052513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052513
1052656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052879: marked as done (cdist: FTBFS: make[1]: *** [debian/rules:36: override_dh_install] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 15:04:52 +
with message-id 
and subject line Bug#1052879: fixed in cdist 7.0.0-3
has caused the Debian Bug report #1052879,
regarding cdist: FTBFS: make[1]: *** [debian/rules:36: override_dh_install] 
Error 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cdist
Version: 7.0.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_install
> jdupes --linksoft --recurse debian/cdist-doc
> jdupes: unrecognized option '--linksoft'
> Try `jdupes --help' for more information.
> make[1]: *** [debian/rules:36: override_dh_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/cdist_7.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: cdist
Source-Version: 7.0.0-3
Done: Axel Beckert 

We believe that the bug you reported is fixed in the latest version of
cdist, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated cdist package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 26 Sep 2023 16:22:40 +0200
Source: cdist
Architecture: source
Version: 7.0.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Closes: 1052879
Changes:
 cdist (7.0.0-3) unstable; urgency=high
 .
   * QA upload.
   * debian/rules: Fix jdupes invocation wrt. --linksoft → --link-soft
 option renaming. (Closes: #1052879)
Checksums-Sha1:
 9c2a56a31b8b5ad162e45c30fb4a816057b81c23 1994 cdist_7.0.0-3.dsc
 d18fc0941c3982eae4cad32bd1e7173e1bdc22f2 7788 cdist_7.0.0-3.debian.tar.xz
 ccca1cd0870aac663ec1d792f2ccab2d0c6ee8d2 8275 cdist_7.0.0-3_source.buildinfo
Checksums-Sha256:
 4a19538351196d72dce1bf92e8e4e79f36832f53dd41d5ce56ca887616642991 1994 
cdist_7.0.0-3.dsc
 d2887b2ec43da4efe5d5ad502077c82ebab066c95d7fb05ce383ad10789a4e79 7788 
cdist_7.0.0-3.debian.tar.xz
 9b7e1dba1548e0c98a5b782380eae0ebc745ae50627c2e93baa5894f9a615d6a 8275 
cdist_7.0.0-3_source.buildinfo
Files:
 e3a2f1ade9ff07c4b18bc6da49b4518a 1994 admin optional cdist_7.0.0-3.dsc
 07e9260fe741ca5b6db45e1f7626460b 7788 admin optional 
cdist_7.0.0-3.debian.tar.xz
 bfcfa4d10eafe9cfc2523a133e7efe00 8275 admin optional 
cdist_7.0.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAmUS6dAACgkQa+Zjx1o1
yXWbHA/+J6armbYfRM30Zs9lbqM49OEqz5SLYriNimqGB13LUAry0FqJgPcapVnA
ZN5ZfCnqxRmW+zqQHO8ufJoAxEXU4w435EDp1VTl4XrBJfOez+UTH8iWcL4Zl+2E
uSoLwEZZozPVk0cyqYpTzMbJG4hN9uQtoDFJiHpJ42rl9h8elxyVXCa1ganS7ADH
AE1XqTLCW4mCt6Os5XjlsGTiUOGYlGOKaU6GTbdup7LQlNZM0u2v77hYMsdGeJvn
Y9rtQa1kQxqHA0/QdarU9ZgYHEH7ptcUSCmIIlw97qm9pzwajifloM442IEGhIel
B7MuTehv+Zp/k0UsCPV+oiaG9g5kdMzjGJcQzbJpzjtq19zs9YRPoHaquv8etAmQ
9PJxTsKYtEmlCFEIKCgfev64X6lP/scxebTpEkjgu+3ztvkpwoQFU4wCx6OR0OFQ
ZGJHjp1TknPByhXrk7Zj0roqUTepWD4wbi/MU+2eOmsuWO00oGtodczQ6A+xoM7x
rKmAe7HqyyUBhXRzVpRbvBj6f47JqGw74OcpnsJIqO0i4LW+hzTXcn9UIF3pQHIE
rFMtYHswhbSgfkPp5MkquE6fxE6kW+Gen59gvP/AlSs0rJZ9rSFr2Qm6hFFIdZEI
CM0Q5OKebca4wvDKbPL02cDXCsmkSO2F+/OoNB6Y9PJD/Rtg3Hg=

Processed: Bug#1052957 marked as pending in debian-edu-fai

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052957 {Done: Mike Gabriel } [src:debian-edu-fai] 
debian-edu-fai: FTBFS: dpkg-gencontrol: error: the Depends field contains an 
arch-specific dependency but the package 'debian-edu-fai' is architecture all
Added tag(s) pending.

-- 
1052957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052957: marked as pending in debian-edu-fai

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1052957 in debian-edu-fai reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-edu/debian-edu-fai/-/commit/d3d0e7c6284a732c8f931ff622de5b5c4386c875


debian/control: Move memtest86+ (for archs amd64 + i386) to Recommends: field 
as we can't have arch-specific dependencies in arch-all bin:pkgs. (Closes: 
#1052957).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052957

Bug#1052957: marked as done (debian-edu-fai: FTBFS: dpkg-gencontrol: error: the Depends field contains an arch-specific dependency but the package 'debian-edu-fai' is architecture all)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 15:06:33 +
with message-id 
and subject line Bug#1052957: fixed in debian-edu-fai 2023.09.26.3
has caused the Debian Bug report #1052957,
regarding debian-edu-fai: FTBFS: dpkg-gencontrol: error: the Depends field 
contains an arch-specific dependency but the package 'debian-edu-fai' is 
architecture all
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.)


-- 
1052957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-edu-fai
Version: 2023.09.26.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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 '/<>'
> dh_fixperms
> # contains password hashes
> chmod 640 debian/debian-edu-fai/etc/debian-edu/debian-edu-fai.conf
> make[1]: Leaving directory '/<>'
>dh_missing
>dh_installdeb
>dh_gencontrol
> dpkg-gencontrol: error: the Depends field contains an arch-specific 
> dependency but the package 'debian-edu-fai' is architecture all
> dh_gencontrol: error: dpkg-gencontrol -pdebian-edu-fai -ldebian/changelog 
> -Tdebian/debian-edu-fai.substvars -Pdebian/debian-edu-fai returned exit code 
> 25
> dh_gencontrol: error: Aborting due to earlier error
> make: *** [debian/rules:13: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/debian-edu-fai_2023.09.26.2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: debian-edu-fai
Source-Version: 2023.09.26.3
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
debian-edu-fai, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated debian-edu-fai 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: Tue, 26 Sep 2023 16:53:13 +0200
Source: debian-edu-fai
Architecture: source
Version: 2023.09.26.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Mike Gabriel 
Closes: 1052957
Changes:
 debian-edu-fai (2023.09.26.3) unstable; urgency=medium
 .
   * debian/control:
 + Move memtest86+ (for archs amd64 + i386) to Recommends: field as we can't
   have arch-specific dependencies in arch-all bin:pkgs. (Closes: #1052957).
Checksums-Sha1:
 3e30912a11f1d0805379f298fe180108478b6d19 1730 debian-edu-fai_2023.09.26.3.dsc
 84e9f82dc64505a7cdf3fff2841821175ffb56d8 75384 
debian-edu-fai_2023.09.26.3.tar.xz
 032500500dc1c1d0eb68db92fa3abca30d967d03 6741 
debian-edu-fai_2023.09.26.3_source.buildinfo
Checksums-Sha256:
 a51227f24f9a425eb343edb95db43dbbc64536cb40e8720eae2f82a2000a051a 1730 
debian-edu-fai_2023.09.26.3.dsc
 c08bfa244abaff7e36e5e5675e0db4c0e6dd7d561cccffbe1f23cafb5118ab4f 75384 
debian-edu-fai_2023.09.26.3.tar.xz
 2d8d0530e6acd456d8ada3971e5cc5945eb65fe43200b4ad5ca4e4eaebc454ec 6741 
debian-edu-fai_2023.09.26.3_source.buildinfo
Files:
 5d3e56cdf2085eb92483f56b0a67fe97 1730 admin optional 
debian-edu-fai_2023.09.26.3.dsc
 377911adef9ba1c2150935c9fa6c5bff 75384 admin optional 
debian-edu-fai_2023.09.26.3.tar.xz
 2e7ff0a0177936177ce1d95920c2aa5b 6741 admin optional 
debian-edu-fai_2023.09.26.3_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1052895: marked as done (lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1)

[Debian Bug Tracking System]

Your message dated Tue, 26 Sep 2023 11:07:06 -0400
with message-id 
and subject line Re: Bug#1052895: lsof: FTBFS: make[2]: *** [Makefile:28: all] 
Error 1
has caused the Debian Bug report #1052895,
regarding lsof: FTBFS: make[2]: *** [Makefile:28: all] Error 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lsof
Version: 4.95.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[2]: Entering directory '/<>/tests'
> `cat config.cc`  -I. -I.. `cat config.cflags` -c LTlib.c \
> -o LTlib.o
> `cat config.cc`  -I. -I.. `cat config.cflags` LTbasic.c \
> LTlib.o `cat config.xobj` -o LTbasic
> `cat config.cc`  -I. -I.. `cat config.cflags` LTnlink.c \
> LTlib.o `cat config.xobj` -o LTnlink
> `cat config.cc`  -I. -I.. `cat config.cflags` LTsock.c \
> LTlib.o `cat config.xobj` -o LTsock `cat config.ldflags`
> `cat config.cc`  -I. -I.. `cat config.cflags` LTszoff.c \
> LTlib.o `cat config.xobj` -o LTszoff
> `cat config.cc`  -I. -I.. `cat config.cflags` LTunix.c \
> LTlib.o `cat config.xobj` -o LTunix `cat config.ldflags`
> /<>/tests
> 
> Basic test:
> LTbasic ... OK
> 
> Standard tests:
> LTnlink ... OK
> LTsock ... ERROR!!!  can't get IP address for ip-10-84-234-119
>Errno 0: Success
> LTszoff ... OK
> LTunix ... OK
> Failed tests: 1
> 
> See 00FAQ and 00TEST for more information.
> make[2]: *** [Makefile:28: all] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/lsof_4.95.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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 ---

This is a duplicate of #1011914, closing.


On Tue, Sep 26 2023 at 03:37:26 PM +02:00:00, Lucas Nussbaum 
 wrote:

Source: lsof
Version: 4.95.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org 
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):

 make[2]: Entering directory '/<>/tests'
 `cat config.cc`  -I. -I.. `cat config.cflags` -c LTlib.c \
 -o LTlib.o
 `cat config.cc`  -I. -I.. `cat config.cflags` LTbasic.c \
 LTlib.o `cat config.xobj` -o LTbasic
 `cat config.cc`  -I. -I.. `cat config.cflags` LTnlink.c \
 LTlib.o `cat config.xobj` -o LTnlink
 `cat config.cc`  -I. -I.. `cat config.cflags` LTsock.c \
 LTlib.o `cat config.xobj` -o LTsock `cat config.ldflags`
 `cat config.cc`  -I. -I.. `cat config.cflags` LTszoff.c \
 LTlib.o `cat config.xobj` -o LTszoff
 `cat config.cc`  -I. -I.. `cat config.cflags` LTunix.c \
 LTlib.o `cat config.xobj` -o LTunix `cat config.ldflags`
 /<>/tests

 Basic test:
 LTbasic ... OK

 Standard tests:
 LTnlink ... OK
 LTsock ... ERROR!!!  can't get IP address for ip-10-84-234-119
Errno 0: Success
 LTszoff ... OK
 LTunix ... OK
 Failed tests: 1

 See 00FAQ and 00TEST for more information.
 make[2]: *** [Makefile:28: all] Error 1



The full build log is available from:


All bugs filed during this archive rebuild are listed at:

or:


A list of current common problems and possible solutions is available 
at
 . You're welcome to 
contribute!


If you reassign this bug to another package, please mark it as 
'affects'-ing

this package. See 

If you fail to reproduce this, 

Processed: Re: python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/vulndb/db'

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dh-python
Bug #1052854 [src:python-vulndb] python-vulndb: FTBFS: FileNotFoundError: 
[Errno 2] No such file or directory: 
'/<>/.pybuild/cpython3_3.11/build/vulndb/db'
Bug reassigned from package 'src:python-vulndb' to 'dh-python'.
No longer marked as found in versions python-vulndb/0.1.3-2.
Ignoring request to alter fixed versions of bug #1052854 to the same values 
previously set
> found -1 6.20230825
Bug #1052854 [dh-python] python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No 
such file or directory: 
'/<>/.pybuild/cpython3_3.11/build/vulndb/db'
Marked as found in versions dh-python/6.20230825.
> affects -1 python-vulndb borgbackup
Bug #1052854 [dh-python] python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No 
such file or directory: 
'/<>/.pybuild/cpython3_3.11/build/vulndb/db'
Added indication that 1052854 affects python-vulndb and borgbackup

-- 
1052854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1052854: python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/vulndb/db'

[Gianfranco Costamagna]

control: reassign -1 dh-python
control: found -1 6.20230825
control: affects -1 python-vulndb borgbackup

hello, I see a TON of FTBFS bugs for python failures
I suspect the reason for them to fail is
* Remove *.egg-info directories in clean step, as part of Debian's wider
  effort to improve clean targets. Thanks Stuart Prescott for the patch.

in latest dh-python
now, SOURCES.txt is created usually based on files that are under git 
versioning, but we don't have git installed during build
cleaning up that directory during clean step, makes it not correctly being 
re-created
I presume we should assign them back to dh-python and check with python 
maintainers if we can do something
creating egg-info from scratch, is for sure something I really like, but maybe 
not so feasible in general

for borgbackup I crafted an hacky patch to add on MANIFEST.in file an 
additional file 
https://salsa.debian.org/debian/borgbackup/-/blob/master/debian/patches/7793.patch

The problem of this kind of patches is:
 1) is fragile and changes on every upstream release (specially for tests 
containing a ton of subfiles)
 2) can't be upstreamed easily
so I don't think deleting egg-info during clean as default is a sane thing to do

maybe this can mitigate indeed 
https://salsa.debian.org/python-team/tools/dh-python/-/commit/3d42f08deb9ffb0d2f7a689dbc5a314ab5ded6c4

What is the opinion of dh-python maintainers? Feel free to reassign back if you 
don't agree

thanks

Gianfranco
On Tue, 26 Sep 2023 14:44:47 +0200 Lucas Nussbaum  wrote:

Source: python-vulndb
Version: 0.1.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 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:291: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.

> !!
> 
> 

> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 

> 
> !!

>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:291: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.

> !!
> 
> 

> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 

> 
> !!

>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11/build/vulndb
> copying vulndb/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb
> copying vulndb/db_vuln.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb
> creating /<>/.pybuild/cpython3_3.11/build/vulndb/tests
> copying vulndb/tests/test_load_all_json.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/tests
> copying vulndb/tests/test_db_vuln.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/tests
> copying vulndb/tests/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/tests
> creating /<>/.pybuild/cpython3_3.11/build/vulndb/constants
> copying vulndb/constants/wasc.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/constants
> copying vulndb/constants/__init__.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/constants
> copying vulndb/constants/cwe.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/constants
> copying vulndb/constants/owasp.py -> 
/<>/.pybuild/cpython3_3.11/build/vulndb/constants


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1052902: yosys: FTBFS: make[2]: *** [Makefile:971: docs/gen_images] Error 2

[Daniel Gröber]

Hi Lucas,

On Tue, Sep 26, 2023 at 03:43:28PM +0200, Lucas Nussbaum wrote:
> Source: yosys
> Version: 0.33-5
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie
>
> The full build log is available from:
> http://qa-logs.debian.net/2023/09/25/yosys_0.33-5_unstable.log

Is the buildinfo file for the rebuild available somewhere too? I'd like to
diff the build environment against what the buildds had.

Thanks,
--Daniel



signature.asc
Description: PGP signature

Bug#1052906: fig2dev: FTBFS: +Failed to convert pdf to eps: No such file or directory

[Roland Rosenfeld]

On Di, 26 Sep 2023, Lucas Nussbaum wrote:

> Source: fig2dev
> Version: 1:3.2.9-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230925 ftbfs-trixie

> During a rebuild of all packages in sid, your package failed to build
> on amd64.

This is an regression with ghostscript 10.02.0, which seems to have
problems with the option "-sPageList=1" in the call
 gs -dSAFER -sDEVICE=eps2write -sPageList=1 -o line.eps line.pdf

This results in the failed tests 17 and 108.

I'm not sure, whether this should be fixed/worked around in fig2dev or
in ghostscript, I reported it as https://bugs.debian.org/1052652

The failed test 106 is a consequence of different rendering of the new
ghostscript version, which results in a file with a little more black
pixels than former versions.  I'll adapt the allowed range in the test
soon.

Greetings
Roland

Processed: Re: Bug#1052871: libauthen-sasl-cyrus-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #1052871 [src:libauthen-sasl-cyrus-perl] libauthen-sasl-cyrus-perl: FTBFS: 
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) confirmed.

-- 
1052871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems