Bug#955156: marked as done (python3-openshot: Installation broken)

[Debian Bug Tracking System]

Your message dated Wed, 24 Jun 2020 04:33:29 +
with message-id 
and subject line Bug#955156: fixed in libopenshot 0.2.5+dfsg1-1
has caused the Debian Bug report #955156,
regarding python3-openshot: Installation broken
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.)


-- 
955156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-openshot
Version: 0.2.2+dfsg1-1
Severity: grave
Justification: renders package unusable

After the transition to Python 3.8 one is no longer able to install Openshot:

$ sudo apt install python3-openshot
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-openshot : Depends: python3 (< 3.8) but 3.8.2-2 is to be installed
E: Unable to correct problems, you have held broken packages.

Note that I am running testing but the same should apply to sid.

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

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-openshot depends on:
ii  libavutil56  7:4.2.2-1+b1
ii  libc62.30-2
ii  libgcc-s1 [libgcc1]  10-20200324-1
ii  libgcc1  1:10-20200324-1
ii  libjsoncpp1  1.7.4-3.1
pn  libopenshot-audio6   
pn  libopenshot16
pn  libpython3.7 
ii  libqt5core5a 5.12.5+dfsg-9
ii  libstdc++6   10-20200324-1
ii  python3  3.8.2-2

python3-openshot recommends no packages.

python3-openshot suggests no packages.
--- End Message ---
--- Begin Message ---
Source: libopenshot
Source-Version: 0.2.5+dfsg1-1
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated libopenshot 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, 23 Jun 2020 22:46:18 +0200
Source: libopenshot
Architecture: source
Version: 0.2.5+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Anton Gladky 
Closes: 955156
Changes:
 libopenshot (0.2.5+dfsg1-1) unstable; urgency=medium
 .
   * Upload into unstable. (Closes: #955156)
Checksums-Sha1:
 61ef45ffcb97b645eafd9db441304695d595c9a6 2570 libopenshot_0.2.5+dfsg1-1.dsc
 1005ad4be5404730949ebb5965540862437da330 5456 
libopenshot_0.2.5+dfsg1-1.debian.tar.xz
 74db1d279717b26109f7b261051b03eca863 14404 
libopenshot_0.2.5+dfsg1-1_source.buildinfo
Checksums-Sha256:
 f6397925837d4dc4aeda2a8f3f6c3cc9ecfa92748bfd66506a8251b4b18b2a6f 2570 
libopenshot_0.2.5+dfsg1-1.dsc
 2b2508fad12885b7e3df4f446767b7fd950c12a7dc3068380041f22edc8ec448 5456 
libopenshot_0.2.5+dfsg1-1.debian.tar.xz
 007a464c07f4984ed34f02693b63b440d3367a83abe8efd3d4768d1ac3dfe09e 14404 
libopenshot_0.2.5+dfsg1-1_source.buildinfo
Files:
 d934c4008e3e9c9b5cd6ad5015dba8ec 2570 libs optional 
libopenshot_0.2.5+dfsg1-1.dsc
 5ade4272b107a9f15cfdcf74bd283d52 5456 libs optional 
libopenshot_0.2.5+dfsg1-1.debian.tar.xz
 73dcf08c0bb280b05ae8c9cfc10e19b5 14404 libs optional 
libopenshot_0.2.5+dfsg1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl7y1OMACgkQ0+Fzg8+n
/wZuYw//R9nYFoZhKfQ4lraVQesByz/WWHZEUYBkbCKwJUz4UTni8pSpu8jDX5iO

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

[Felix Lechner]

Hi,

> the OpenSSL ./. GPL problem (if one sees it as a problem) is larger

There may be an alternative for some cases mentioned here. The wolfSSL
encryption library is a FIPS-certified, commercial product with a
fully usable, although incomplete, OpenSSL compatibility layer. The
developers are very friendly toward open-source. One of them uses
Ubuntu.

Licensed under the GPL (or alternatively proprietary terms), wolfSSL
avoids the linking problems OpenSSL has been trying to shed for years.
wolfSSL is popular in embedded systems. If you bought an appliance or
a car in the past ten years, you are probably using it already.

In the enterprise space, MariaDB ships with an older, captive version.
For a long time, MySQL relied on it (then called cyaSSL). I do not
know if PostgreSQL can use it.

Here is a list of projects that have been officially ported. [1]

Daniel Stenberg, the creator of cURL, works there. I see the
developers from time to time and receive free support. The library has
been in Debian for five years.

Kind regards
Felix Lechner

[1] https://www.wolfssl.com/community/

Bug#963546: meson: autopkgtest failures

[Jussi Pakkanen]

On Tue, 23 Jun 2020 at 16:36, Gianfranco Costamagna
 wrote:

> Hello, as you can see, two tests can't be run on ppc64el and s390x, because 
> of missing:
> g++-arm-linux-gnueabihf and ldc
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz
> Marking the two tests as "skip-not-installed" works

Thanks, this will be in the next upload.

> Also, I noticed a failure on Ubuntu:
> c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' -I/usr/include 
> -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
> -Wnon-virtual-dtor -std=c++14 -g -pthread -DBOOST_DATE_TIME_DYN_LINK=1 
> -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_SETUP_DYN_LINK=1 
> -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 
> -DBOOST_LOG_DYN_LINK=1 -DBOOST_ALL_NO_LIB -MD -MQ 
> 'extralibexe@exe/extralib.cpp.o' -MF 'extralibexe@exe/extralib.cpp.o.d' -o 
> 'extralibexe@exe/extralib.cpp.o' -c '../test cases/frameworks/1 
> boost/extralib.cpp'
> c++: fatal error: Killed signal terminated program cc1plus
>
> do you have any clue?

At this point Meson is no longer involved. Ninja has invoked c++ and
that process then crashes. Running that command by hand in the same
system should result in the same crash.

>From what I can tell this is either a bug in GCC or there is some
watchdog that kills the process for whatever reason such as running
out of memory. The latter can be a symptom of the former.

Bug#963309: urlwatch: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13

[Maxime Werlen]

Hi,

Thanks for the report. I've found an existing patch upstream for these
pycodestyle violations.
I've packaged the patch in urlwatch-2.18-2 and uploaded the package to
mentors.

Regards,

Maxime

Le dim. 21 juin 2020 à 22:09, Lucas Nussbaum  a écrit :

> Source: urlwatch
> Version: 2.18-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 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_autoreconf -O--buildsystem=pybuild
> >dh_auto_configure -O--buildsystem=pybuild
> > I: pybuild base:217: python3.8 setup.py config
> > running config
> >dh_auto_build -O--buildsystem=pybuild
> > I: pybuild base:217: /usr/bin/python3 setup.py build
> > running build
> > running build_py
> > creating /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/cli.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/mailer.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/__init__.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/storage.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/command.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/worker.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/jobs.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/util.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/config.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/reporters.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/main.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/html2txt.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/handler.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/ical2txt.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/migration.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> > copying lib/urlwatch/filters.py ->
> /<>/.pybuild/cpython3_3.8_urlwatch/build/urlwatch
> >dh_auto_test -O--buildsystem=pybuild
> > I: pybuild base:217: cd
> /<>/.pybuild/cpython3_3.8_urlwatch/build; python3.8 -m nose -v
> test
> > test_filters.test_filters('element_by_tag',) ... ok
> > test_filters.test_filters('element_by_tag_nested',) ... ok
> > test_filters.test_filters('element_by_id',) ... ok
> > test_filters.test_filters('element_by_class',) ... ok
> > test_filters.test_filters('xpath_elements',) ... ok
> > test_filters.test_filters('xpath_text',) ... ok
> > test_filters.test_filters('xpath_exclude',) ... ok
> > test_filters.test_filters('xpath_xml_namespaces',) ... ok
> > test_filters.test_filters('css',) ... ok
> > test_filters.test_filters('css_exclude',) ... ok
> > test_filters.test_filters('css_xml_namespaces',) ... ok
> > test_filters.test_filters('grep',) ... ok
> > test_filters.test_filters('grep_with_comma',) ... ok
> > test_filters.test_filters('json_format',) ... ok
> > test_filters.test_filters('json_format_subfilter',) ... ok
> > test_filters.test_filters('sha1',) ... ok
> > test_filters.test_filters('hexdump',) ... ok
> > test_filters.test_filters('sort',) ... ok
> > test_handler.test_required_classattrs_in_subclasses ... ok
> > test_handler.test_save_load_jobs ... ok
> > test_handler.test_load_config_yaml ... ok
> > test_handler.test_load_urls_txt ... ok
> > test_handler.test_load_urls_yaml ... ok
> > test_handler.test_load_hooks_py ... ok
> > Test that we conform to PEP-8. ... FAIL
> > test_handler.test_run_watcher ... ok
> > test_handler.test_unserialize_shell_job_without_kind ... ok
> > test_handler.test_unserialize_with_unknown_key ... ok
> > test_handler.prepare_retry_test ... ok
> > test_handler.test_number_of_tries_in_cache_is_increased ... ok
> > test_handler.test_report_error_when_out_of_tries ... ok
> > test_handler.test_reset_tries_to_zero_when_successful ... ok
> >
> > ==
> > FAIL: Test that we conform to PEP-8.
> > --
> > Traceback (most recent call last):
> >   File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in
> runTest
> > self.test(*self.arg)
> >   File
> "/<>/.pybuild/cpython3_3.8_urlwatch/build/test/test_handler.py",
> line 83, in test_pep8_conformance
> > assert result.total_errors == 0, "Found #{0} code style
> errors".format(result.total_errors)
> > AssertionError: Found #3 code style errors
> >  >> begin captured stdout << 

Bug#963320: libtgvoip: FTBFS: AttributeError: module 'string' has no attribute 'maketrans'

[Nicholas Guriev]

reassign 963320 gyp
found 963320 0.1+20200513gitcaa6002-1
affects 963320 src:libtgvoip
stop

On Sun, 2020-06-21 at 22:04 +0200, Lucas Nussbaum wrote:
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > gyp --format=cmake --depth=. --generator-output=. -Gconfig=Release 
> > -Goutput_dir=obj-x86_64-linux-gnu 
> > -Dlinux_path_opus_include=/usr/include/opus
> > Traceback (most recent call last):
> >   File "/usr/bin/gyp", line 11, in 
> > load_entry_point('gyp==0.1', 'console_scripts', 'gyp')()
> >   File "/usr/lib/python3/dist-packages/gyp/__init__.py", line 552, in 
> > script_main
> > return main(sys.argv[1:])
> >   File "/usr/lib/python3/dist-packages/gyp/__init__.py", line 545, in main
> > return gyp_main(args)
> >   File "/usr/lib/python3/dist-packages/gyp/__init__.py", line 518, in 
> > gyp_main
> > [generator, flat_list, targets, data] = Load(
> >   File "/usr/lib/python3/dist-packages/gyp/__init__.py", line 98, in Load
> > generator = __import__(generator_name, globals(), locals(), 
> > generator_name)
> >   File "/usr/lib/python3/dist-packages/gyp/generator/cmake.py", line 43, in 
> > 
> > _maketrans = string.maketrans
> > AttributeError: module 'string' has no attribute 'maketrans'
> > make[1]: *** [debian/rules:30: override_dh_auto_configure] Error 1
> 
> The full build log is available from:
>http://qa-logs.debian.net/2020/06/20/libtgvoip_2.4.4-2_unstable.log
> 
> 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!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

The bug is not in the libtgvoip package itself but apparently caused by
incomplete porting GYP to Python 3. Dear GYP maintainer, please fix
CMake generator, switch it to built-in str.maketrans.

I am already working on a new version of the libtgvoip package. It will
not use GYP and not solve the actual issue in the build tool.

Processed: Re: Bug#963320: libtgvoip: FTBFS: AttributeError: module 'string' has no attribute 'maketrans'

[Debian Bug Tracking System]

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

> reassign 963320 gyp
Bug #963320 [src:libtgvoip] libtgvoip: FTBFS: AttributeError: module 'string' 
has no attribute 'maketrans'
Bug reassigned from package 'src:libtgvoip' to 'gyp'.
No longer marked as found in versions libtgvoip/2.4.4-2.
Ignoring request to alter fixed versions of bug #963320 to the same values 
previously set
> found 963320 0.1+20200513gitcaa6002-1
Bug #963320 [gyp] libtgvoip: FTBFS: AttributeError: module 'string' has no 
attribute 'maketrans'
Marked as found in versions gyp/0.1+20200513gitcaa6002-1.
> affects 963320 src:libtgvoip
Bug #963320 [gyp] libtgvoip: FTBFS: AttributeError: module 'string' has no 
attribute 'maketrans'
Added indication that 963320 affects src:libtgvoip
> stop
Stopping processing here.

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

Bug#651313: marked as done (desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:37:18 +
with message-id 
and subject line Bug#963168: Removed package(s) from unstable
has caused the Debian Bug report #651313,
regarding desktopnova-module-gnome: desktopnova seems to be not compatible with 
Gnome 3
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.)


-- 
651313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: desktopnova-module-gnome
Version: 0.8.1-1
Severity: important

Dear Maintainer,

Desktopnova seems to be not compatible with Gnome 3: standard backgrounds of
Gnome 3 are used and backgrounds of desktopnova not.

Thank you.

Pierre Crescenzo



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 
'proposed-updates'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages desktopnova-module-gnome depends on:
ii  desktopnova   0.8.1-1 
ii  libc6 2.13-21 
ii  libgconf2-4   2.32.4-1
ii  libglib2.0-0  2.30.2-4

desktopnova-module-gnome recommends no packages.

desktopnova-module-gnome suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.8.1-1.2+rm

Dear submitter,

as the package desktopnova 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/963168

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Re: Processed (with 1 error): src:ensmallen: fails to migrate to testing for too long: FTBFS armel/armhf/mipsel

[Debian Bug Tracking System]

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

> block 963557 by 961203
Bug #963557 {Done: Paul Gevers } [src:ensmallen] 
src:ensmallen: fails to migrate to testing for too long: FTBFS 
armel/armhf/mipsel
963557 was not blocked by any bugs.
963557 was not blocking any bugs.
Added blocking bug(s) of 963557: 961203
> thanks
Stopping processing here.

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

Bug#938923: marked as done (zyne: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:38:27 +
with message-id 
and subject line Bug#963550: Removed package(s) from unstable
has caused the Debian Bug report #938923,
regarding zyne: Python2 removal in sid/bullseye
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.)


-- 
938923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zyne
Version: 0.1.2-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:zyne

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.1.2-2+rm

Dear submitter,

as the package zyne 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/963550

The version of this package that was in Debian prior to this removal
can still be found using http://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#807648: marked as done (zyne: Fails to start (missing dep for wx?))

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:38:27 +
with message-id 
and subject line Bug#963550: Removed package(s) from unstable
has caused the Debian Bug report #807648,
regarding zyne: Fails to start (missing dep for wx?)
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.)


-- 
807648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zyne
Version: 0.1.2-2
Severity: normal

Dear Maintainer,

Trying to start zyne:
$ zyne 
Traceback (most recent call last):
  File "/usr/bin/zyne", line 3, in 
  import wxversion
  ImportError: No module named wxversion

The executable tries to load several wx libs, but none of them are
mentioned in package dependencies.

Installing python-wxversion leads to
$ zyne
Traceback (most recent call last):
  File "/usr/bin/zyne", line 4, in 
wxversion.select("2.8")
  File "/usr/lib/python2.7/dist-packages/wxversion.py", line 152, in select
raise VersionError("Requested version of wxPython not found")
wxversion.VersionError: Requested version of wxPython not found

I'm not sure what would satisfy 2.8. Doesn't seem that installing
python-wxgtk3.0 will do. The plain lib package I have and I'm not really
familiar with the lib, let alone the Python bindings.

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

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

Versions of packages zyne depends on:
ii  python  2.7.9-1
ii  python-pyo  0.7.6+git20150902.a1d7123d76-1

zyne recommends no packages.

zyne suggests no packages.

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

Dear submitter,

as the package zyne 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/963550

The version of this package that was in Debian prior to this removal
can still be found using http://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#943275: marked as done (snetz: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:36:02 +
with message-id 
and subject line Bug#963096: Removed package(s) from unstable
has caused the Debian Bug report #943275,
regarding snetz: Python2 removal in sid/bullseye
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.)


-- 
943275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snetz
Version: 0.1-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.1-1+rm

Dear submitter,

as the package snetz 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/963096

The version of this package that was in Debian prior to this removal
can still be found using http://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#937212: marked as done (opensips: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:36:25 +
with message-id 
and subject line Bug#963097: Removed package(s) from unstable
has caused the Debian Bug report #937212,
regarding opensips: Python2 removal in sid/bullseye
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.)


-- 
937212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opensips
Version: 2.2.2-3.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:opensips

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 2.2.2-3.1+rm

Dear submitter,

as the package opensips 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/963097

The version of this package that was in Debian prior to this removal
can still be found using http://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#943268: marked as done (woof: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:35:35 +
with message-id 
and subject line Bug#963095: Removed package(s) from unstable
has caused the Debian Bug report #943268,
regarding woof: Python2 removal in sid/bullseye
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.)


-- 
943268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: woof
Version: 20091227-2.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 20091227-2.1+rm

Dear submitter,

as the package woof 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/963095

The version of this package that was in Debian prior to this removal
can still be found using http://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#937437: marked as done (pyfeed: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:34:43 +
with message-id 
and subject line Bug#962985: Removed package(s) from unstable
has caused the Debian Bug report #937437,
regarding pyfeed: Python2 removal in sid/bullseye
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.)


-- 
937437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyfeed
Version: 0.7.4-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pyfeed

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.7.4-2+rm

Dear submitter,

as the package pyfeed 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/962985

The version of this package that was in Debian prior to this removal
can still be found using http://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#947278: marked as done (xmlelements: missing Build-Depends: dh-python)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:35:06 +
with message-id 
and subject line Bug#962986: Removed package(s) from unstable
has caused the Debian Bug report #947278,
regarding xmlelements: missing Build-Depends: dh-python
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.)


-- 
947278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmlelements
Version: 1.0~prerelease-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

xmlelements/experimental FTBFS:

 fakeroot debian/rules clean
dh clean --with=python2,python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/i386-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/i386-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl 
/usr/lib/i386-linux-gnu/perl-base) at (eval 13) line 1.
BEGIN failed--compilation aborted at (eval 13) line 1.

make: *** [debian/rules:35: clean] Error 255


Andreas


xmlelements_1.0~prerelease-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.7.4-2+rm

Dear submitter,

as the package xmlelements 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/962986

The version of this package that was in Debian prior to this removal
can still be found using http://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#947448: marked as done (pyfeed: missing Build-Depends: dh-python)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:34:43 +
with message-id 
and subject line Bug#962985: Removed package(s) from unstable
has caused the Debian Bug report #947448,
regarding pyfeed: missing Build-Depends: dh-python
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.)


-- 
947448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfeed
Version: 1.0~prerelease-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

pyfeed/experimental FTBFS with 

 fakeroot debian/rules clean
dh clean --with=python2,python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 13) line 
1.
BEGIN failed--compilation aborted at (eval 13) line 1.

make: *** [debian/rules:35: clean] Error 255


Andreas
--- End Message ---
--- Begin Message ---
Version: 0.7.4-2+rm

Dear submitter,

as the package pyfeed 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/962985

The version of this package that was in Debian prior to this removal
can still be found using http://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#889019: marked as done (gnome-doc-utils: is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:34:13 +
with message-id 
and subject line Bug#962983: Removed package(s) from unstable
has caused the Debian Bug report #889019,
regarding gnome-doc-utils: is deprecated
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.)


-- 
889019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-doc-utils
Version: 0.20.10-4
Severity: important
Tags: wontfix

(Opening this bug so that it's visible to non-GNOME-team people doing
QA work or considering what to use for their new packages.)

gnome-doc-utils is deprecated. Its most recent upstream release was in
2012, with most changes in its git repository since then being
translation updates.

The replacement is yelp.m4 in yelp-tools, as used in GNOME 3 packages.

Porting guide:
https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure

smcv
--- End Message ---
--- Begin Message ---
Version: 0.20.10-5+rm

Dear submitter,

as the package gnome-doc-utils 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/962983

The version of this package that was in Debian prior to this removal
can still be found using http://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#962040: marked as done (boost1.67: Can not (and should not) fulfill the build dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:33:23 +
with message-id 
and subject line Bug#962950: Removed package(s) from unstable
has caused the Debian Bug report #962040,
regarding boost1.67: Can not (and should not) fulfill the build dependencies
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.)


-- 
962040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost1.67
Version: 1.67.0-18
Severity: serious
Tags: ftbfs

The following packages have unmet dependencies:
 builddeps:boost1.67 : Depends: libicu-dev (< 64) but 67.1-2 is to be installed

This is intentional, see #960623 for background.
--- End Message ---
--- Begin Message ---
Version: 1.67.0-18+rm

Dear submitter,

as the package boost1.67 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/962950

The version of this package that was in Debian prior to this removal
can still be found using http://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#938850: marked as done (xmlelements: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 19:35:06 +
with message-id 
and subject line Bug#962986: Removed package(s) from unstable
has caused the Debian Bug report #938850,
regarding xmlelements: Python2 removal in sid/bullseye
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.)


-- 
938850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xmlelements
Version: 0.7.4-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:xmlelements

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.7.4-2+rm

Dear submitter,

as the package xmlelements 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/962986

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed (with 1 error): src:ensmallen: fails to migrate to testing for too long: FTBFS armel/armhf/mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.12.1-1
Bug #963557 [src:ensmallen] src:ensmallen: fails to migrate to testing for too 
long: FTBFS armel/armhf/mipsel
Marked as fixed in versions ensmallen/2.12.1-1.
Bug #963557 [src:ensmallen] src:ensmallen: fails to migrate to testing for too 
long: FTBFS armel/armhf/mipsel
Marked Bug as done
> blocks -1 by 961203
Unknown command or malformed arguments to command.


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

Bug#963557: src:ensmallen: fails to migrate to testing for too long: FTBFS armel/armhf/mipsel

[Paul Gevers]

Source: ensmallen
Version: 2.12.0-1
Severity: serious
Control: close -1 2.12.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: blocks -1 by 961203

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:ensmallen in
its current version in unstable has been trying to migrate for 61 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ensmallen




signature.asc
Description: OpenPGP digital signature

Bug#963556: src:gxr: fails to migrate to testing for too long: unfixed RC bug

[Paul Gevers]

Source: gxr
Version: 0.13.2-2
Severity: serious
Control: close -1 0.14.0-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 959608

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:gxr in its
current version in unstable has been trying to migrate for 60 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gxr




signature.asc
Description: OpenPGP digital signature

Processed: src:gxr: fails to migrate to testing for too long: unfixed RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.14.0-4
Bug #963556 [src:gxr] src:gxr: fails to migrate to testing for too long: 
unfixed RC bug
Marked as fixed in versions gxr/0.14.0-4.
Bug #963556 [src:gxr] src:gxr: fails to migrate to testing for too long: 
unfixed RC bug
Marked Bug as done
> block -1 by 959608
Bug #963556 {Done: Paul Gevers } [src:gxr] src:gxr: fails to 
migrate to testing for too long: unfixed RC bug
963556 was not blocked by any bugs.
963556 was not blocking any bugs.
Added blocking bug(s) of 963556: 959608

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

Processed: bug 953615 is forwarded to https://github.com/borgbackup/borg/issues/4829

[Debian Bug Tracking System]

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

> forwarded 953615 https://github.com/borgbackup/borg/issues/4829
Bug #953615 {Done: Andrej Shadura } [borgbackup] 
borgbackup: index corruption / data loss
Set Bug forwarded-to-address to 
'https://github.com/borgbackup/borg/issues/4829'.
> thanks
Stopping processing here.

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

Bug#963241: marked as done (primus-nvidia: Failed to load libGL)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 20:28:57 +0200
with message-id <5b911f5d-b81c-ea8b-2d41-1e5685d2d...@debian.org>
and subject line Re: Bug#963241: primus-nvidia: Failed to load libGL
has caused the Debian Bug report #963241,
regarding primus-nvidia: Failed to load libGL
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.)


-- 
963241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: primus-nvidia
Version: 0~20150328-11
Severity: grave
Justification: renders package unusable

Hi,
I tried to launch pvkrun and optirun, but i received the following error in 
both cases:

primus: fatal: failed to load any of the libraries: 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1:/usr/lib/i386-linux-gnu/nvidia/libGL.so.1:/usr/lib/nvidia/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No 
such file or directory
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No 
such file or directory
/usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such file or 
directory

Thanks in advance.

Luigi

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages primus-nvidia depends on:
ii  bumblebee-nvidia 3.2.1-23
ii  nvidia-driver-libs [nvidia-driver-libs-any]  440.82-2
ii  primus   0~20150328-11

Versions of packages primus-nvidia recommends:
ii  nvidia-primus-vk-wrapper  1.5-1

primus-nvidia suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

On 6/23/20 11:08 AM, Luigi Curzi wrote:

Hi,
thanks for the help; i removed old config file, that i had modified some
time ago, and after reinstalling packages, pvkrun started working again.


During the upgrade, dpkg should have asked you what to do with the 
modified configuration file, but the default action is to keep the 
modified version (leaving the new version as *.dpkg-new).


If this starts to hit more people on upgrades, we might consider 
patching bumblebee.conf if it still contains the old LibraryPath after 
the upgrade.


Andreas

PS: it would probably have been good if the conffile would be fully 
commented, s.t. the compiled-in defaults are active unless manually 
overridden in the conffile--- End Message ---

Processed: src:xpra: fails to migrate to testing for too long: FTBFS armel/armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.0.9+dfsg1-1
Bug #963555 [src:xpra] src:xpra: fails to migrate to testing for too long: 
FTBFS armel/armhf
Marked as fixed in versions xpra/3.0.9+dfsg1-1.
Bug #963555 [src:xpra] src:xpra: fails to migrate to testing for too long: 
FTBFS armel/armhf
Marked Bug as done
> block -1 by 956822
Bug #963555 {Done: Paul Gevers } [src:xpra] src:xpra: fails 
to migrate to testing for too long: FTBFS armel/armhf
963555 was not blocked by any bugs.
963555 was not blocking any bugs.
Added blocking bug(s) of 963555: 956822

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

Processed: src:openjdk-11: fails to migrate to testing for too long: FTBFS on armel & mips*el

[Debian Bug Tracking System]

Processing control commands:

> close -1 11.0.7+10-3
Bug #963554 [src:openjdk-11] src:openjdk-11: fails to migrate to testing for 
too long: FTBFS on armel & mips*el
Marked as fixed in versions openjdk-11/11.0.7+10-3.
Bug #963554 [src:openjdk-11] src:openjdk-11: fails to migrate to testing for 
too long: FTBFS on armel & mips*el
Marked Bug as done

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

Bug#963554: src:openjdk-11: fails to migrate to testing for too long: FTBFS on armel & mips*el

[Paul Gevers]

Source: openjdk-11
Version: 11.0.7+9-1
Severity: serious
Control: close -1 11.0.7+10-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:openjdk-11 in
its current version in unstable has been trying to migrate for 68 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=openjdk-11




signature.asc
Description: OpenPGP digital signature

Bug#963555: src:xpra: fails to migrate to testing for too long: FTBFS armel/armhf

[Paul Gevers]

Source: xpra
Version: 3.0.7+dfsg1-1
Severity: serious
Control: close -1 3.0.9+dfsg1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 956822

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:xpra in its
current version in unstable has been trying to migrate for 64 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=xpra




signature.asc
Description: OpenPGP digital signature

Bug#962763: marked as done (renderdoc FTBFS: undefined references to spvtools symbols)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:04:07 +
with message-id 
and subject line Bug#962763: fixed in renderdoc 1.8+dfsg-1
has caused the Debian Bug report #962763,
regarding renderdoc FTBFS: undefined references to spvtools symbols
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.)


-- 
962763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: renderdoc
Version: 1.7+dfsg-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/renderdoc.html
https://buildd.debian.org/status/package.php?p=renderdoc=sid

...
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11 -fstrict-aliasing -fvisibility=hidden 
-fvisibility-inlines-hidden -Wall -Wextra -Wno-unused-variable 
-Wno-unused-parameter -Wno-unused-result -Wno-type-limits 
-Wno-missing-field-initializers -Wno-unknown-pragmas -Wno-reorder 
-Wno-unused-but-set-variable -Wno-maybe-uninitialized -Wno-class-memaccess 
-Wimplicit-fallthrough=2 -O3 -DNDEBUG -Wl,--undefined,force_include_libentry 
-Wl,--version-script,/<>/renderdoc/renderdoc.version 
-Wl,--no-undefined -Wl,-z,relro -shared -Wl,-soname,librenderdoc.so -o 
../lib/librenderdoc.so 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/blit.vert.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/checkerboard.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/glsl_ubos.h.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/glsl_globals.h.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/fixedcol.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/histogram.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/mesh.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/mesh.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/mesh.geom.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/mesh.vert.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/minmaxresult.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/minmaxtile.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/quadresolve.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/quadwrite.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/texdisplay.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/texremap.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/gl_texsample.h.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/gles_texsample.h.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/vk_texsample.h.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/gltext.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/gltext.vert.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/vktext.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/vktext.vert.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/array2ms.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/ms2array.comp.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/trisize.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/trisize.geom.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/deptharr2ms.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/glsl/depthms2arr.frag.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/data/sourcecodepro.ttf.c.o 
CMakeFiles/renderdoc.dir/CMakeFiles/data.src/driver/vulkan/renderdoc.json.c.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_common.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_counters.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_debug.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_postvs.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_overlay.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_outputwindow.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_rendermesh.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_rendertexture.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_rendertext.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_msaa_array_conv.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_driver.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_initstate.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_manager.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_renderstate.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_replay.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_resources.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_program_iterate.cpp.o 
driver/gl/CMakeFiles/rdoc_gl.dir/gl_shader_refl.cpp.o 

Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error

[Michael Meskes]

> I mentioned this in a previous email: the problem is if the upgrade
> breaks and the admin has to consult man pages to work out how to fix
> it.
> (I did just that less than an hour ago in another situation, so I
> don't
> think this is a theoretical concern.)

Another good point, thanks for clarifying.

As mentioned in another email, I'm going to make bsdmainutils a
transitional package, making this issue mood.

Thanks,

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#963413: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> ../utils/md2man.sh libvmem/libvmem.7.md default.man generated/libvmem.7;  
> ../utils/md2man.sh libvmmalloc/libvmmalloc.7.md default.man 
> generated/libvmmalloc.7;
> ../utils/md2man.sh libvmem/vmem_create.3.md default.man 
> generated/vmem_create.3;  ../utils/md2man.sh libvmem/vmem_malloc.3.md 
> default.man generated/vmem_malloc.3;
> man ./generated/libvmem.7 > generated/libvmem.7.txt
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[3]: *** [Makefile:103: generated/libvmem.7.txt] Error 3

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/vmem_1.8-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963448: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wiki2beamer
Version: 0.10.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 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
>dh_update_autotools_config
>dh_autoreconf
>debian/rules execute_after_dh_auto_build
> make[1]: Entering directory '/<>'
> /usr/bin/make -C /<>/doc/man/
> make[2]: Entering directory '/<>/doc/man'
> mkdir man1
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[2]: *** [Makefile:9: man] Error 3

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/wiki2beamer_0.10.0-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963442: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # syntax check.
> bash -n bash_completion.d/pbuilder
> bash -n pbuilderrc
> bash -n pbuilderrc
> bash -n debuild-pbuilder
> bash -n pdebuild
> bash -n pbuilder-apt-config
> bash -n pbuilder-buildpackage
> bash -n pbuilder-buildpackage-funcs
> bash -n pbuilder-checkparams
> bash -n pbuilder-createbuildenv
> bash -n pbuilder-loadconfig
> bash -n pbuilder-modules
> bash -n pbuilder-runhooks
> bash -n pbuilder-satisfydepends-apt
> bash -n pbuilder-satisfydepends-aptitude
> bash -n pbuilder-satisfydepends-checkparams
> bash -n pbuilder-satisfydepends-classic
> bash -n pbuilder-satisfydepends-experimental
> bash -n pbuilder-satisfydepends-funcs
> bash -n pbuilder-satisfydepends-gdebi
> bash -n pbuilder-unshare-wrapper
> bash -n pbuilder-updatebuildenv
> bash -n pdebuild-checkparams
> bash -n pdebuild-internal
> bash -n pbuilder
> bash -n examples/B90lintian
> bash -n examples/B91dpkg-i
> bash -n examples/B92test-pkg
> bash -n examples/C10shell
> bash -n examples/C11screen
> bash -n examples/D10tmp
> bash -n examples/D20addnonfree
> bash -n examples/D65various-compiler-support
> bash -n examples/D80no-man-db-rebuild
> bash -n examples/D90chrootmemo
> bash -n examples/F90chrootmemo
> bash -n examples/B90list-missing
> bash -n examples/B91debc
> bash -n examples/B20autopkgtest
> bash -n examples/execute_installtest.sh
> bash -n examples/execute_paramtest.sh
> bash -n examples/pbuilder-distribution.sh
> bash -n examples/lvmpbuilder/lvmbuilder
> bash -n examples/lvmpbuilder/lib/lvmbuilder-checkparams
> bash -n examples/lvmpbuilder/lib/lvmbuilder-modules
> bash -n examples/lvmpbuilder/lib/lvmbuilder-unimplemented
> bash -n examples/pbuilder-test/000_prepinstall
> bash -n examples/pbuilder-test/001_apprun
> bash -n examples/pbuilder-test/002_libfile
> bash -n examples/pbuilder-test/003_makecheck
> bash -n examples/pbuilder-test/004_ldd
> bash -n examples/rebuild/buildall
> bash -n examples/rebuild/getlist
> LANG=C MANWIDTH=80 man --warnings -l debuild-pbuilder.1 >/dev/null
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[1]: *** [Makefile:163: check] Error 3
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/pbuilder_0.230.4_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** 

Bug#963403: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mp3info
Version: 0.8.5a-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mp3info.o mp3info.c
> gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o textfunc.o textfunc.c
> gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mp3curs.o mp3curs.c
> gcc -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -c -o mp3tech.o mp3tech.c
> mp3info.c: In function ‘main’:
> mp3info.c:287:3: warning: ignoring return value of ‘truncate’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   287 |   truncate(mp3.filename,mp3.datasize);
>   |   ^~~
> mp3tech.c: In function ‘get_id3’:
> mp3tech.c:306:5: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   306 | fread(fbuf,1,3,mp3->file); fbuf[3] = '\0';
>   | ^
> mp3tech.c:316:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   316 |   fread(mp3->id3.title,1,30,mp3->file); 
> mp3->id3.title[30] = '\0';
>   |   ^~~~
> mp3tech.c:317:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   317 |   fread(mp3->id3.artist,1,30,mp3->file); 
> mp3->id3.artist[30] = '\0';
>   |   ^
> mp3tech.c:318:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   318 |   fread(mp3->id3.album,1,30,mp3->file); 
> mp3->id3.album[30] = '\0';
>   |   ^~~~
> mp3tech.c:319:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   319 |   fread(mp3->id3.year,1,4,mp3->file); mp3->id3.year[4] = 
> '\0';
>   |   ^~
> mp3tech.c:320:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   320 |   fread(mp3->id3.comment,1,30,mp3->file); 
> mp3->id3.comment[30] = '\0';
>   |   ^~
> mp3tech.c:324:15: warning: ignoring return value of ‘fread’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   324 |   fread(mp3->id3.genre,1,1,mp3->file);
>   |   ^~~
> In file included from /usr/include/string.h:495,
>  from mp3info.h:31,
>  from mp3curs.c:27:
> In function ‘strncpy’,
> inlined from ‘tagedit_curs’ at mp3curs.c:111:4:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
> ‘__builtin___strncpy_chk’ output truncated before terminating nul copying as 
> many bytes from a string as its length [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> ^~
> mp3curs.c: In function ‘tagedit_curs’:
> mp3curs.c:111:4: note: length computed here
>   111 |strncpy(tag->title,line,strlen(line));
>   |^
> In file included from /usr/include/string.h:495,
>  from mp3info.h:31,
>  from mp3curs.c:27:
> In function ‘strncpy’,
> inlined from ‘tagedit_curs’ at mp3curs.c:113:4:
> /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
> ‘__builtin___strncpy_chk’ output truncated before terminating nul copying as 
> many bytes from a string as its length [-Wstringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos 
> (__dest));
>   |  
> 

Bug#963376: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apcupsd
Version: 3.14.14-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/src/lib'
>   CXX   src/lib/apcconfig.c
> g++ -x c++ -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include 
> -I/<>/src/libusbhid -I/<>/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-exceptions -fno-rtti -Wall -Wno-unused-result  
> -c -o .obj/apcconfig.o apcconfig.c
> man: can't execute col: No such file or directory
> man: command exited with status 127: col -b -p -x | sed -e '/^[[:space:]]*$/{ 
> N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[4]: *** [Makefile:10: apcupsd.man.txt] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/apcupsd_3.14.14-3_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963372: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: console-setup
Version: 1.195
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> >/<>/Fonts/bdf/legacy16a-double.bdf
> groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> >/<>/man/bdf2psf.1.txt
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> >/<>/Fonts/bdf/legacy16b-double.bdf
> groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> >/<>/man/console-setup.5.txt
> /bin/sh: 1: col: not found
> /bin/sh: 1: col: not found
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> >/<>/Fonts/bdf/legacy16c-double.bdf
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> >/<>/Fonts/bdf/legacy16d-double.bdf
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> >/<>/Fonts/bdf/legacy16e-double.bdf
> bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> >/<>/Fonts/bdf/legacy16f-double.bdf
> make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/console-setup_1.195_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963383: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calc
Version: 2.12.7.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/custom'
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o custtbl.o custtbl.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_argv.o c_argv.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_devnull.o c_devnull.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_help.o c_help.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I.. c_sysinfo.c -c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_pzasusb8.o c_pzasusb8.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_pmodm127.o c_pmodm127.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3 -I..   -c -o c_register.o c_register.c
> rm -f libcustcalc.a
> ar qc libcustcalc.a custtbl.o c_argv.o c_devnull.o c_help.o c_sysinfo.o 
> c_pzasusb8.o c_pmodm127.o c_register.o
> ranlib libcustcalc.a
> chmod 0644 libcustcalc.a
> echo '=-=-=-=-= custom/Makefile start of Makefile.simple rule =-=-=-=-='
> =-=-=-=-= custom/Makefile start of Makefile.simple rule =-=-=-=-=
> echo '=-=-=-=-= custom/Makefile end of Makefile.simple rule =-=-=-=-='
> =-=-=-=-= custom/Makefile end of Makefile.simple rule =-=-=-=-=
> rm -f .all
> touch .all
> make[2]: Leaving directory '/<>/custom'
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o addop.o addop.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o assocfunc.o assocfunc.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o blkcpy.o blkcpy.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o block.o block.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o byteswap.o byteswap.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o calcerr.o calcerr.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o codegen.o codegen.c
> gcc  -DCALC_SRC -DCUSTOM -Wall  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -O3 -g3   -c -o comfunc.o comfunc.c
> gcc  -DCALC_SRC -DCUSTOM 

Bug#963355: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/playsid'
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall -I.././ 
> sidptype.c -o sidptype.o -c
> sidptype.c: In function ‘sidReadMemInfo’:
> sidptype.c:109:23: warning: passing argument 2 of ‘latin1’ makes integer from 
> pointer without a cast [-Wint-conversion]
>   109 |   latin1(m->modname, m->modname, strlen(m->modname));
>   |  ~^
>   |   |
>   |   char *
> sidptype.c:52:35: note: expected ‘int’ but argument is of type ‘char *’
>52 | static void latin1(char *dst, int dstlen, char *src)
>   |   ^~
> sidptype.c:109:34: warning: passing argument 3 of ‘latin1’ makes pointer from 
> integer without a cast [-Wint-conversion]
>   109 |   latin1(m->modname, m->modname, strlen(m->modname));
>   |  ^~
>   |  |
>   |  size_t {aka long unsigned int}
> sidptype.c:52:49: note: expected ‘char *’ but argument is of type ‘size_t’ 
> {aka ‘long unsigned int’}
>52 | static void latin1(char *dst, int dstlen, char *src)
>   |   ~~^~~
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -g -fPIC -fPIC -Wall -I.././ -shared 
> -Wl,-z,relro -o sidtype.so sidptype.o
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -fPIC -fPIC -Wall -I.././ cpiinfo.cpp -o 
> cpiinfo.o -c 
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1 
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\" 
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config 
> -I./sidplayfp-git/libsidplayfp/src sidplay.cpp -o sidplay.o -c
> sidplay.cpp:690:2: warning: #warning We can probably REMOVE mixClipAlt2 soon 
> globally [-Wcpp]
>   690 | #warning We can probably REMOVE mixClipAlt2 soon globally
>   |  ^~~
> g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -fPIC -fPIC -Wall -I.././ -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config 
> -I./sidplayfp-git/libsidplayfp/src sidpplay.cpp -o sidpplay.o -c
> sidpplay.cpp:260:2: warning: #warning FIXME, frequency does not take VIC-II 
> model / cpu-freqency into account [-Wcpp]
>   260 | #warning FIXME, frequency does not take VIC-II model / cpu-freqency 
> into account
>   |  ^~~
> sidpplay.cpp: In function ‘int sidOpenFile(uint32_t, moduleinfostruct*, 
> FILE*)’:
> sidpplay.cpp:734:9: warning: ‘char* strncpy(char*, const char*, size_t)’ 
> output may be truncated copying 8 bytes from a string of length 11 
> [-Wstringop-truncation]
>   734 |  strncpy(currentmodname, info->name, _MAX_FNAME);
>   |  ~~~^~~~
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1 
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\" 
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -fPIC -I./sidplayfp-config 
> -I./sidplayfp-git/libsidplayfp/src -o 
> libsidplayfp-builders-resid-builder-resid-builder.o 
> sidplayfp-git/libsidplayfp/src/builders/resid-builder/resid-builder.cpp -c
> g++ -std=c++11 -DHAVE_CONFIG_H=1 -DSIDTUNE_NO_STDIN_LOADER=1 
> -DPACKAGE_NAME=\"sidplayfp\" -DVERSION=\"2.0.1\" 
> -DPACKAGE_VERSION=\"2.0.1-1\" -DPACKAGE_URL=\"\" -g -O2 
> -fdebug-prefix-map=/<>=. 

Bug#963451: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: loadlin
Version: 1.6f-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/src/srclinux'
> gcc -m32 -traditional -c loadlinh.S
> gcc -m32 -D__KERNEL__ -march=i386 -Os -DSTDC_HEADERS -fomit-frame-pointer 
> -fno-strength-reduce -fPIC -ffreestanding -fno-stack-protector -c pgadjust.c 
> -o pgadjust.o
> ld -m elf_i386 -Ttext 0x95010 -N -e startup_32  -o pgadjust loadlinh.o 
> pgadjust.o
> objcopy -O binary pgadjust pgadjust.out
> echo "; 32-bit code, linkaddress: 0x95010" >pgadjust.as
> hexdump -v -e '" DD  " 8/4 "0%Xh," 1/4 "0%Xh\n"' pgadjust.out >>pgadjust.as
> /bin/sh: 1: hexdump: not found
> make[2]: *** [Makefile:19: ../pgadjust.asm] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/loadlin_1.6f-7_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963350: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slashem
Version: 0.0.7E7F3-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/src'
> make[4]: '../include/date.h' is up to date.
> make[4]: Leaving directory '/<>/src'
> cc -DDEBIAN_GTK -g -O2 -fomit-frame-pointer -fstack-protector 
> --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o recover.o recover.c
> recover.c: In function ‘main’:
> recover.c:114:10: warning: ignoring return value of ‘setgid’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   114 |   (void) setgid(getgid());
>   |  ^~~~
> recover.c:115:10: warning: ignoring return value of ‘setuid’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   115 |   (void) setuid(getuid());
>   |  ^~~~
> recover.c: In function ‘restore_savefile’:
> recover.c:308:5: warning: ignoring return value of ‘write’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   308 | write(sfd, (genericptr_t) , sizeof(levc));
>   | ^~
> cc -L/usr/X11R6/lib -Wl,-z,relro -o recover recover.o 
> make[3]: Leaving directory '/<>/util'
> ( cd doc ; /usr/bin/make Guidebook )
> make[3]: Entering directory '/<>/doc'
> tbl tmac.n Guidebook.mn | nroff | col -bx > Guidebook
> /bin/sh: 1: col: not found
> make[3]: *** [Makefile:40: Guidebook] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/slashem_0.0.7E7F3-9_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963365: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Version: 8.15.2-19
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc/op'
> rm -f op.txt
> Note: see README file in case of errors.
> pic -C op.me | eqn -C -Tascii | groff -Tascii -me | ul -t dumb > op.txt
> /bin/sh: 1: ul: not found
> make[2]: *** [Makefile:30: op.txt] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/sendmail_8.15.2-19_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963375: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conky
Version: 1.10.8-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/build-std'
> [  7%] Proccessing man page for docs
> cd /<>/build-std/doc && /usr/bin/xsltproc 
> http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl 
> /<>/doc/docs.xml > /<>/doc/docs.html
> cd /<>/build-std/doc && /usr/bin/db2x_xsltproc -s man 
> /<>/doc/docs.xml -o docs.mxml
> cd /<>/build-std/doc && /usr/bin/db2x_manxml --encoding=utf-8 
> docs.mxml --output-dir /<>/doc
> cd /<>/build-std/doc && /usr/bin/xsltproc 
> http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl 
> /<>/doc/docs.xml > /<>/doc/docs.html
> cd /<>/build-std/doc && /usr/bin/man -P '/usr/bin/less -is' 
> /<>/doc/conky.1 > /<>/README
> /usr/bin/man: can't execute col: No such file or directory
> /usr/bin/man: command exited with status 127: col -b -p -x | sed -e 
> '/^[[:space:]]*$/{ N; /^[[:space:]]*\n[[:space:]]*$/D; }'
> make[4]: *** [doc/CMakeFiles/docs.dir/build.make:68: ../doc/docs.html] Error 3

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/conky_1.10.8-1.1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963361: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hub
Version: 2.7.0~ds1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> hub help hub-alias --plain-text | script/format-ronn hub-alias 
> share/man/man1/hub-alias.1.ronn
> hub help hub-browse --plain-text | script/format-ronn hub-browse 
> share/man/man1/hub-browse.1.ronn
> hub help hub-ci-status --plain-text | script/format-ronn hub-ci-status 
> share/man/man1/hub-ci-status.1.ronn
> hub help hub-compare --plain-text | script/format-ronn hub-compare 
> share/man/man1/hub-compare.1.ronn
> hub help hub-create --plain-text | script/format-ronn hub-create 
> share/man/man1/hub-create.1.ronn
> hub help hub-delete --plain-text | script/format-ronn hub-delete 
> share/man/man1/hub-delete.1.ronn
> hub help hub-fork --plain-text | script/format-ronn hub-fork 
> share/man/man1/hub-fork.1.ronn
> hub help hub-pr --plain-text | script/format-ronn hub-pr 
> share/man/man1/hub-pr.1.ronn
> hub help hub-pull-request --plain-text | script/format-ronn hub-pull-request 
> share/man/man1/hub-pull-request.1.ronn
> hub help hub-release --plain-text | script/format-ronn hub-release 
> share/man/man1/hub-release.1.ronn
> hub help hub-issue --plain-text | script/format-ronn hub-issue 
> share/man/man1/hub-issue.1.ronn
> hub help hub-sync --plain-text | script/format-ronn hub-sync 
> share/man/man1/hub-sync.1.ronn
> hub help hub-am --plain-text | script/format-ronn hub-am 
> share/man/man1/hub-am.1.ronn
> hub help hub-apply --plain-text | script/format-ronn hub-apply 
> share/man/man1/hub-apply.1.ronn
> hub help hub-checkout --plain-text | script/format-ronn hub-checkout 
> share/man/man1/hub-checkout.1.ronn
> hub help hub-cherry-pick --plain-text | script/format-ronn hub-cherry-pick 
> share/man/man1/hub-cherry-pick.1.ronn
> hub help hub-clone --plain-text | script/format-ronn hub-clone 
> share/man/man1/hub-clone.1.ronn
> hub help hub-fetch --plain-text | script/format-ronn hub-fetch 
> share/man/man1/hub-fetch.1.ronn
> hub help hub-help --plain-text | script/format-ronn hub-help 
> share/man/man1/hub-help.1.ronn
> hub help hub-init --plain-text | script/format-ronn hub-init 
> share/man/man1/hub-init.1.ronn
> hub help hub-merge --plain-text | script/format-ronn hub-merge 
> share/man/man1/hub-merge.1.ronn
> hub help hub-push --plain-text | script/format-ronn hub-push 
> share/man/man1/hub-push.1.ronn
> hub help hub-remote --plain-text | script/format-ronn hub-remote 
> share/man/man1/hub-remote.1.ronn
> hub help hub-submodule --plain-text | script/format-ronn hub-submodule 
> share/man/man1/hub-submodule.1.ronn
> ronn --organization=GITHUB --manual="Hub Manual" share/man/man1/*.ronn
>  roff: share/man/man1/hub-alias.1 
>  html: share/man/man1/hub-alias.1.html   +man
>  roff: share/man/man1/hub-am.1
>  html: share/man/man1/hub-am.1.html  +man
>  roff: share/man/man1/hub-apply.1 
>  html: share/man/man1/hub-apply.1.html   +man
>  roff: share/man/man1/hub-browse.1
> tbl::9: unrecognised format '\'
> tbl::9: giving up on this table
>  html: share/man/man1/hub-browse.1.html  +man
>  roff: share/man/man1/hub-checkout.1  
>  html: share/man/man1/hub-checkout.1.html+man
>  roff: share/man/man1/hub-cherry-pick.1   
>  html: share/man/man1/hub-cherry-pick.1.html +man
>  roff: share/man/man1/hub-ci-status.1 
>  html: share/man/man1/hub-ci-status.1.html   +man
>  roff: share/man/man1/hub-clone.1 
>  html: share/man/man1/hub-clone.1.html   +man
>  roff: share/man/man1/hub-compare.1   
>  html: share/man/man1/hub-compare.1.html +man
>  roff: share/man/man1/hub-create.1  

Bug#963359: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glhack
Version: 1.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/src'
> make[4]: '../include/date.h' is up to date.
> make[4]: Leaving directory '/<>/src'
> cc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -O -I../include 
> -Wdate-time -D_FORTIFY_SOURCE=2  -c -o recover.o recover.c
> recover.c: In function ‘restore_savefile’:
> recover.c:308:5: warning: ignoring return value of ‘write’, declared with 
> attribute warn_unused_result [-Wunused-result]
>   308 | write(sfd, (genericptr_t) , sizeof(levc));
>   | ^~
> cc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2  -o 
> recover_glhack recover.o 
> make[3]: Leaving directory '/<>/util'
> ( cd doc ; make Guidebook )
> make[3]: Entering directory '/<>/doc'
> tbl tmac.n Guidebook.mn | nroff -Tascii | col -bx > Guidebook
> /bin/sh: 1: col: not found
> make[3]: *** [Makefile:27: Guidebook] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/glhack_1.2-4_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963306: marked as done (re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding re2c: FTBFS: src/msg/help.cc:3:1: error: expected primary-expression 
before ‘;’ token
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++98  -W  
> -Wall  -Wextra  -Weffc++  -pedantic  -Wformat=2  -Wredundant-decls  
> -Wsuggest-attribute=format  -Wconversion  -Wsign-conversion  
> -Werror=return-type  -O2  -DRE2C_STDLIB_DIR='"/usr/share/re2c/stdlib/"'  -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o src/parse/parser.o src/parse/parser.cc
> src/msg/help.cc:3:1: error: expected primary-expression before ‘;’ token
> 3 | ;
>   | ^
> make[2]: *** [Makefile:2232: src/msg/help.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/re2c_1.3-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963327: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


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

Hi,

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

Relevant part (hopefully):
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for hexdump... no
> configure: error: hexdump is required for tests
> make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/libstorj_1.0.3-1_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,

Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16a.bdf 
> > >/<>/Fonts/bdf/legacy16a-double.bdf
> > groff -mandoc -Tascii /<>/man/bdf2psf.1 | col -bx 
> > >/<>/man/bdf2psf.1.txt
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16b.bdf 
> > >/<>/Fonts/bdf/legacy16b-double.bdf
> > groff -mandoc -Tascii /<>/man/console-setup.5 | col -bx 
> > >/<>/man/console-setup.5.txt
> > /bin/sh: 1: col: not found
> > /bin/sh: 1: col: not found
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16c.bdf 
> > >/<>/Fonts/bdf/legacy16c-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16d.bdf 
> > >/<>/Fonts/bdf/legacy16d-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16e.bdf 
> > >/<>/Fonts/bdf/legacy16e-double.bdf
> > bdfresize -f 2 -b 1 /<>/Fonts/bdf/legacy16f.bdf 
> > >/<>/Fonts/bdf/legacy16f-double.bdf
> > make[1]: *** [Makefile:137: /<>/man/console-setup.5.txt] Error 
> > 127

This was apparently caused by the take-over of several bsd tools
(including col) by util-linux two days ago.
Builds fine again now.

So closing this bug.
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#963378: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


-- 
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xcolorsel
Version: 1.1a-22
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
>  -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO
> -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o RgbText.o RgbText.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from RgbText.c:77:
> /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> RgbText.c: In function ‘printfile’:
> RgbText.c:549:7: warning: unused variable ‘fd’ [-Wunused-variable]
>   549 | FILE *fd;
>   |   ^~
> RgbText.c:545:21: warning: unused variable ‘ptn’ [-Wunused-variable]
>   545 | register char *ptr,*ptn;
>   | ^~~
> RgbText.c: In function ‘query_geometry’:
> RgbText.c:883:16: warning: unused variable ‘requested’ [-Wunused-variable]
>   883 | XtGeometryMask requested;
>   |^
> RgbText.c: In function ‘grab_color’:
> RgbText.c:1135:8: warning: unused variable ‘mycolor’ [-Wunused-variable]
>  1135 | XColor mycolor;
>   |^~~
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
>  -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO
> -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o RgbSink.o RgbSink.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from /usr/include/X11/IntrinsicP.h:51,
>  from RgbSink.c:82:
> /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> RgbSink.c: In function ‘mydisp’:
> RgbSink.c:191:5: warning: unused variable ‘tile’ [-Wunused-variable]
>   191 | int tile,linum;
>   | ^~~~
> gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
>  -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64
>-DFUNCPROTO=15 -DNARROWPROTO
> -DHELPFILE=\"/usr/lib/X11/xcolorsel/Xcolorsel.help\" -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o RgbSrc.o RgbSrc.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from /usr/include/X11/Xlib.h:38,
>  from /usr/include/X11/Intrinsic.h:53,
>  from 

Bug#963377: marked as done (bsdmainutils must depend on bsdextrautils)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 18:49:26 +0200
with message-id <20200623184926.8874b811f379c57b2428f...@mailbox.org>
and subject line Re: Bug#963372: console-setup: FTBFS: /bin/sh: 1: col: not 
found
has caused the Debian Bug report #963372,
regarding bsdmainutils must depend on bsdextrautils
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/build'
> gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 
> -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False 
> -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\"
>  -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 
> -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 
> -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\"  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual 
> -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations 
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow 
> -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op 
> -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas 
> -Wswitch-enum -Wno-cast-qual -c ../button.c
> gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 
> -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False 
> -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\"
>  -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 
> -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 
> -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\"  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual 
> -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations 
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow 
> -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op 
> -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas 
> -Wswitch-enum -Wno-cast-qual -c ../cachedGCs.c
> gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 
> -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False 
> -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\"
>  -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 
> -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 
> -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\"  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -W -Wall -Wbad-function-cast -Wcast-align -Wcast-qual 
> -Wdeclaration-after-statement -Wextra -Winline -Wmissing-declarations 
> -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow 
> -Wstrict-prototypes -Wundef -Wno-inline -Wignored-qualifiers -Wlogical-op 
> -Wvarargs -Wdeclaration-after-statement -Wextra -Wno-unknown-pragmas 
> -Wswitch-enum -Wno-cast-qual -c ../charsets.c
> making VTparse.hin from ../VTparse.def
> gcc -I. -I.. -DHAVE_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 
> -DDEF_ALLOW_FONT=False -DDEF_ALLOW_TCAP=False 
> -DDEF_DISALLOWED_WINDOW=\"1,2,3,4,5,6,7,8,9,11,13,14,18,19,20,21,GetSelection,SetSelection,SetWinLines,SetXprop\"
>  -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -DNARROWPROTO=1 -DFUNCPROTO=15 
> -DOSMAJORVERSION=4 -DOSMINORVERSION=19 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid 
> -I/usr/include/freetype2 -I/usr/include/uuid -I/usr/include/libpng16 
> -DXTSTRINGDEFINES -DDEFCLASS=\"XTerm\"  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -W -Wall 

Processed: affects 963427

[Debian Bug Tracking System]

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

> affects 963427 = ding bsdmainutils
Bug #963427 {Done: Roland Rosenfeld } [ding] bsdmainutils 
must depend on bsdextrautils
Removed indication that 963427 affects src:ding, src:sendmail, src:mcl, 
src:console-setup, src:ocp, src:calc, src:libdap, src:xterm, src:man-db, 
src:pbuilder, src:glhack, src:libstorj, src:mp3info, src:loadlin, src:apcupsd, 
src:hub, src:wiki2beamer, src:vmem, src:xcolorsel, src:zsh, src:slashem, and 
src:conky
Added indication that 963427 affects bsdmainutils and ding
> thanks
Stopping processing here.

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

Bug#807648: your mail

[Tiago Bortoletto Vaz]

#963550

Thanks,

On Tue, Jun 23, 2020 at 08:54:46AM -0400, Tiago Bortoletto Vaz wrote:
> Yes, please. And sorry for the MIA on this.
> 
> I'm doing the RFP later today.
> 
> Bests,
> 
> On Sat, Jun 13, 2020 at 11:09:27PM +0200, Moritz Mühlenhoff wrote:
> > On Mon, Sep 03, 2018 at 11:25:07PM -0400, Tiago Bortoletto Vaz wrote:
> > > Hi, sorry for the long delay.
> > > 
> > > I'm doing a (late) cleanup in my packages and will update Zyne to the new
> > > upstream version, which now runs with python3 and python-wxgtk4.0. I'll 
> > > have
> > > to package a new dependency as well: 
> > > https://github.com/belangeo/pyo-tools.
> > > It will take some time, anyway just for the record that I didn't give up
> > > about this nice synth in Debian.
> > 
> > There hasn't been any further update, let's remove zyne?
> > 
> > Cheers,
> > Moritz

Bug#939334: (no subject)

[ygrek]

 For now this is "fixed" with -unsafe-string in 3.1.7

-- 

Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error

[Colin Watson]

On Tue, Jun 23, 2020 at 01:39:29PM +0200, Michael Meskes wrote:
> Colin Watson wrote:
> > man would be broken between the end of step 1 and the end of step 5.
> > I think this is undesirable and unnecessary.
> 
> Good points. However, I still don't see where this creates problems in
> the upgrade process unless some postinst calls man.

I mentioned this in a previous email: the problem is if the upgrade
breaks and the admin has to consult man pages to work out how to fix it.
(I did just that less than an hour ago in another situation, so I don't
think this is a theoretical concern.)

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: 963158.2

[Debian Bug Tracking System]

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

> unblock 963158 with 963327
Bug #963158 [src:re2c] re2c: CVE-2020-11958
963158 was blocked by: 963442 963383 963377 963403 963359 963349 963355 963451 
963413 963376 963372 963365 963306 963448 963361 963327 963378 963375 963395 
963350
963158 was not blocking any bugs.
Removed blocking bug(s) of 963158: 963350, 963413, 963365, 963327, 963403, 
963355, 963361, 963306, 963451, 963377, 963448, 963359, 963378, 963372, 963375, 
963383, 963376, and 963442
> thanks
Stopping processing here.

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

Processed: #963478 affects more packages

[Debian Bug Tracking System]

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

> affects 963478 + lynkeos.app pikopixel.app price.app
Bug #963478 [libgnustep-gui0.28] libgnustep-gui0.28: Missing sentinel in 
+[NSPDFImageRep imagePasteboardTypes] crashes applications
Added indication that 963478 affects lynkeos.app, pikopixel.app, and price.app
> thanks
Stopping processing here.

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

Bug#888164: marked as done (ruby-packable: FTBFS on ruby2.5: Illegal seek @ rb_io_tell)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 13:49:44 +
with message-id 
and subject line Bug#888164: fixed in ruby-packable 1.3.14-1
has caused the Debian Bug report #888164,
regarding ruby-packable: FTBFS on ruby2.5: Illegal seek @ rb_io_tell
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.)


-- 
888164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-packable
Version: 1.3.8-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


┌──┐
│ Run tests for ruby2.3 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-packable/usr/share/rubygems-integration/all:/root/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Run options: --seed 55512

# Running:

/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:57:
 warning: Enumerator.new without a block is deprecated; use Object#to_enum
.

Finished in 0.006436s, 2641.5416 runs/s, 10721.5511 assertions/s.

17 runs, 69 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-packable/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
/usr/lib/ruby/vendor_ruby/backports/1.8.7/fixnum/div.rb:1: warning: constant 
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/backports/1.8.7/fixnum/fdiv.rb:1: warning: constant 
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/backports/2.1.0/bignum/bit_length.rb:1: warning: 
constant ::Bignum is deprecated
/usr/lib/ruby/vendor_ruby/backports/2.1.0/fixnum/bit_length.rb:1: warning: 
constant ::Fixnum is deprecated
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:86:in
 `pos': Illegal seek @ rb_io_tell -  (Errno::ESPIPE)
from 
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:86:in
 `pack_and_write'
from 
/build/ruby-packable-1.3.8/debian/ruby-packable/usr/lib/ruby/vendor_ruby/packable/extensions/io.rb:62:in
 `write_with_packing'
from /usr/lib/ruby/vendor_ruby/minitest.rb:580:in `puts'



Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-packable.log

Please fix it!

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Source: ruby-packable
Source-Version: 1.3.14-1
Done: =?utf-8?q?C=C3=A9dric_Boutillier?= 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-packable 
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, 23 Jun 2020 15:25:08 +0200
Source: ruby-packable
Architecture: source
Version: 

Bug#807648: your mail

[Tiago Bortoletto Vaz]

> I'm doing the RFP later today.

Request for Removal I meant.

Bests,
 
> Bests,
> 
> On Sat, Jun 13, 2020 at 11:09:27PM +0200, Moritz Mühlenhoff wrote:
> > On Mon, Sep 03, 2018 at 11:25:07PM -0400, Tiago Bortoletto Vaz wrote:
> > > Hi, sorry for the long delay.
> > > 
> > > I'm doing a (late) cleanup in my packages and will update Zyne to the new
> > > upstream version, which now runs with python3 and python-wxgtk4.0. I'll 
> > > have
> > > to package a new dependency as well: 
> > > https://github.com/belangeo/pyo-tools.
> > > It will take some time, anyway just for the record that I didn't give up
> > > about this nice synth in Debian.
> > 
> > There hasn't been any further update, let's remove zyne?
> > 
> > Cheers,
> > Moritz

Bug#963546: meson: autopkgtest failures

[Gianfranco Costamagna]

Source: meson
Version: 0.54.3-1
Severity: serious

Hello, as you can see, two tests can't be run on ppc64el and s390x, because of 
missing:
g++-arm-linux-gnueabihf and ldc
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/m/meson/6017346/log.gz
Marking the two tests as "skip-not-installed" works

diff -Nru meson-0.54.3/debian/tests/control meson-0.54.3/debian/tests/control
--- meson-0.54.3/debian/tests/control   2020-03-27 23:40:23.0 +
+++ meson-0.54.3/debian/tests/control   2020-06-23 13:25:22.0 +
@@ -10,6 +10,8 @@
 # tests are run and thus block broken uploads.
 Tests: exhaustive
 Depends: meson, @builddeps@, valac, rustc, ldc
+Restrictions: skip-not-installable
 
 Tests: crossbuild
 Depends: meson, g++, g++-arm-linux-gnueabihf
+Restrictions: skip-not-installable

Also, I noticed a failure on Ubuntu:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/m/meson/20200616_020946_f376b@/log.gz
Failed test during build: 'test cases/frameworks/1 boost   (static=false)'
Reason: Compiling source code failed.
Skipping: test cases/frameworks/1 boost   (static=false b_vscrt=md)
Skipping: test cases/frameworks/1 boost   (static=false b_vscrt=mdd)
Succeeded test: test cases/frameworks/1 boost   (static=true)
Skipping: test cases/frameworks/1 boost   (static=true b_vscrt=md)
Skipping: test cases/frameworks/1 boost   (static=true b_vscrt=mdd)
Skipping: test cases/frameworks/1 boost   (static=true b_vscrt=mt)
Skipping: test cases/frameworks/1 boost   (static=true b_vscrt=mtd)
Mesonlogs of failing tests

The Meson build system
Version: 0.54.3
Source dir: /tmp/autopkgtest.u568ol/build.zhB/src/test cases/frameworks/1 boost
Build dir: /tmp/autopkgtest.u568ol/build.zhB/src/b 125f976e40
Build type: native build
Project name: boosttest
Project version: undefined
C++ compiler for the host machine: c++ (gcc 9.3.0 "c++ (Ubuntu 9.3.0-13ubuntu1) 
9.3.0")
C++ linker for the host machine: c++ ld.bfd 2.34
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29.2)
Run-time dependency Boost found: YES 1.71.0 (/usr/include)
Run-time dependency Boost (found: date_time, system, thread) found: YES 1.71.0 
(/usr)
Run-time dependency Boost (found: unit_test_framework) found: YES 1.71.0 (/usr)
Dependency boost found: YES 1.71.0 (cached)
Run-time dependency Boost (found: date_time, filesystem, log, log_setup, regex, 
system, thread) found: YES 1.71.0 (/usr)
Run-time dependency Boost (missing: this_should_not_exist_on_any_systen) found: 
NO 
Program python2 found: YES (/usr/bin/python2)
Program python3 found: YES (/usr/bin/python3)
test cases/frameworks/1 boost/meson.build:27: WARNING: Passed invalid keyword 
argument "disabler".
WARNING: This will become a hard error in the future.
Dependency python found: NO
test cases/frameworks/1 boost/meson.build:28: WARNING: Passed invalid keyword 
argument "disabler".
WARNING: This will become a hard error in the future.
Dependency python found: YES (pkgconfig)
Run-time dependency Boost (found: python38) found: YES 1.71.0 (/usr)
Program /usr/bin/python2 found: YES (/usr/bin/python2)
Program /usr/bin/python3 found: YES (/usr/bin/python3)
Run-time dependency Boost found: YES 1.71.0 (/usr/include)
Dependency boost found: YES 1.71.0 (cached)
Build targets in project: 7

Found ninja-1.10.0 at /usr/bin/ninja
[1/14] Compiling C++ object 'utf@exe/unit_test.cpp.o'
[2/14] Linking target utf
[3/14] Compiling C++ object 'nomod@exe/nomod.cpp.o'
[4/14] Linking target nomod
[5/14] Compiling C++ object 'linkedexe@exe/linkexe.cc.o'
[6/14] Linking target linkedexe
[7/14] Compiling C++ object 'extralibexe@exe/extralib.cpp.o'
FAILED: extralibexe@exe/extralib.cpp.o 
c++ -Iextralibexe@exe -I. '-I../test cases/frameworks/1 boost' -I/usr/include 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -std=c++14 -g -pthread -DBOOST_DATE_TIME_DYN_LINK=1 
-DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_SETUP_DYN_LINK=1 
-DBOOST_THREAD_BUILD_DLL=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_THREAD_USE_DLL=1 
-DBOOST_LOG_DYN_LINK=1 -DBOOST_ALL_NO_LIB -MD -MQ 
'extralibexe@exe/extralib.cpp.o' -MF 'extralibexe@exe/extralib.cpp.o.d' -o 
'extralibexe@exe/extralib.cpp.o' -c '../test cases/frameworks/1 
boost/extralib.cpp'
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
[8/14] Compiling C++ object 'python3_module@sha/python_module.cpp.o'
ninja: build stopped: subcommand failed.
 

ninja explain: deps for 'linkedexe@exe/linkexe.cc.o' are missing
ninja explain: linkedexe@exe/linkexe.cc.o is dirty
ninja explain: linkedexe is dirty
ninja explain: deps for 'utf@exe/unit_test.cpp.o' are missing
ninja explain: utf@exe/unit_test.cpp.o is dirty
ninja explain: utf is dirty
ninja explain: deps for 'nomod@exe/nomod.cpp.o' are missing
ninja explain: nomod@exe/nomod.cpp.o is dirty
ninja explain: nomod is dirty
ninja explain: deps for 

Bug#963327: [Pkg-zsh-devel] Processed: Merge duplicates

[Adrian Bunk]

On Tue, Jun 23, 2020 at 02:26:51PM +0200, Michael Meskes wrote:
>...
> > The majority of users are using the default of treating Recommends
> > as dependencies, for them it doesn't make any difference whether
> > Recommends or Depends is used.
> > 
> > Not installing Recommends is supported, and desirable in many
> > embedded/server/container scenarios.
> 
> That's why bsdmainutils Recommends bsdextrautils and always has. The
> only argument here is whether it should be a hard Depends instead.
>...

Yes.

It only makes a difference when not installing Recommends by default,
especially when upgrading from buster.

bsdmainutils does depend on bsdutils.

>...
> > One could make the point that bsdmainutils should
> > be a (transitional?) metapackage depending on all
> > the tools it previously provided.
> 
> That's my thinking, too. The remaining tools in bsdmainutils are ncal
> (which should go into a separate package) and a few tools we could
> switch to util-linux or remove.

This would also make the Depends/Recommends question above obsolete.

> Michael

cu
Adrian

Bug#807648: your mail

[Tiago Bortoletto Vaz]

Yes, please. And sorry for the MIA on this.

I'm doing the RFP later today.

Bests,

On Sat, Jun 13, 2020 at 11:09:27PM +0200, Moritz Mühlenhoff wrote:
> On Mon, Sep 03, 2018 at 11:25:07PM -0400, Tiago Bortoletto Vaz wrote:
> > Hi, sorry for the long delay.
> > 
> > I'm doing a (late) cleanup in my packages and will update Zyne to the new
> > upstream version, which now runs with python3 and python-wxgtk4.0. I'll have
> > to package a new dependency as well: https://github.com/belangeo/pyo-tools.
> > It will take some time, anyway just for the record that I didn't give up
> > about this nice synth in Debian.
> 
> There hasn't been any further update, let's remove zyne?
> 
> Cheers,
> Moritz

Bug#963327: [Pkg-zsh-devel] Processed: Merge duplicates

[Michael Meskes]

> Build breakage out of the void is not nice, usually maintainers
> inform 
> reverse build dependencies them before making such a breaking change.

Yes, correct, and I'm sorry about this. It simply didn't occur to me
that the change would create a build breakage.

> The majority of users are using the default of treating Recommends
> as dependencies, for them it doesn't make any difference whether
> Recommends or Depends is used.
> 
> Not installing Recommends is supported, and desirable in many
> embedded/server/container scenarios.

That's why bsdmainutils Recommends bsdextrautils and always has. The
only argument here is whether it should be a hard Depends instead.

> Installing bsdmainutils from unstable in buster breaks commands like
>   man ncal | cat
> I would not be surprised if there is somewhere in Debian some package
> that would do something like that for whatever good or bad reason in
> a postinst or prerm.

I didn't find any usage of man in a postinst on my system, but I have
not checked all packages.

> BTW: The naming of the packages is confusing.

Agreed.

> "extra" sounds like the more obscure utils,
> enhanching the more commonly used "main" tools.
> Looking at the tools shipped, the opposite seems to be true.

Correct, this has to do with the old naming. The more obscure tools are
still build out of the bsdmainutils sources.

> One could make the point that bsdmainutils should
> be a (transitional?) metapackage depending on all
> the tools it previously provided.

That's my thinking, too. The remaining tools in bsdmainutils are ncal
(which should go into a separate package) and a few tools we could
switch to util-linux or remove.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#963430: Any volunteer to spent some time on the new version of artemis (Was: Bug#963430: artemis: FTBFS: /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied)

[olivier sallou]

On Mon, 2020-06-22 at 10:57 -0300, Emmanuel Arias wrote:
> Hi Andreas, 
> 
> I would be happy to help on artemis. Obviously I will need
> a more experienced developer helping me. :)

do not hesitate to ask for help on mailing list, I'll keep an eye on
it.
I have very few spare time to manage this for now but will gladly help
if possible.

Olivier
> 
> Cheers!
> Emmanuel
> 
> 
> 
> 
>  
> Cheers, 
> Arias Emmanuel
> @eamanu
> yaerobi.com
> 
> 
> On Mon, Jun 22, 2020 at 9:17 AM Andreas Tille 
> wrote:
> > Hi,
> > 
> > we are lagging several upstream versions behind due to new
> > dependencies
> > and other build issues.  I wonder whether somebody might volunteer
> > to
> > update artemis.  It would be great to get the latest version at
> > least
> > before the freeze starts.  While this takes some time I guess
> > having
> > latest artemis is time consuming as well - thus I'm asking here.
> > 
> > Any takers?  Despite I'm the only remaining Uploader this exceeds
> > my
> > current time capacity.
> > 
> > Kind regards
> > 
> >   Andreas.
> > 
> > On Sun, Jun 21, 2020 at 10:26:05PM +0200, Lucas Nussbaum wrote:
> > > Source: artemis
> > > Version: 17.0.1+dfsg-2
> > > Severity: serious
> > > Justification: FTBFS on amd64
> > > Tags: bullseye sid ftbfs
> > > Usertags: ftbfs-20200620 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 javahelper
> > > >dh_update_autotools_config
> > > >dh_autoreconf
> > > >dh_auto_configure
> > > >jh_linkjars
> > > >debian/rules override_dh_auto_build
> > > > make[1]: Entering directory '/<>'
> > > > dh_auto_build -- jar
> > > > make -j4 "INSTALL=install --strip-program=true" jar
> > > > make[2]: Entering directory '/<>'
> > > > CLASSPATH=/usr/share/java/biojava.jar /usr/share/java/j2ssh-
> > core.jar /usr/share/java/ibatis.jar /usr/share/java/log4j-1.2.jar
> > /usr/share/java/postgresql-jdbc3.jar /usr/share/java/picard.jar
> > /usr/share/java/htsjdk.jar /usr/share/java/commons-net.jar
> > /usr/share/java/commons-lang3.jar /usr/share/java/batik-all.jar
> > /usr/share/java/batik-awt-util.jar /usr/share/java/batik-dom.jar
> > /usr/share/java/batik-ext.jar /usr/share/java/batik-svggen.jar
> > /usr/share/java/batik-util.jar /usr/share/java/batik-xml.jar
> > /usr/share/EMBOSS/jemboss/lib/jemboss.jar /<>: javac
> > -source 1.8 -target 1.8   uk/ac/sanger/artemis/Action.java
> > > > CLASSPATH=/usr/share/java/biojava.jar /usr/share/java/j2ssh-
> > core.jar /usr/share/java/ibatis.jar /usr/share/java/log4j-1.2.jar
> > /usr/share/java/postgresql-jdbc3.jar /usr/share/java/picard.jar
> > /usr/share/java/htsjdk.jar /usr/share/java/commons-net.jar
> > /usr/share/java/commons-lang3.jar /usr/share/java/batik-all.jar
> > /usr/share/java/batik-awt-util.jar /usr/share/java/batik-dom.jar
> > /usr/share/java/batik-ext.jar /usr/share/java/batik-svggen.jar
> > /usr/share/java/batik-util.jar /usr/share/java/batik-xml.jar
> > /usr/share/EMBOSS/jemboss/lib/jemboss.jar /<>: javac
> > -source 1.8 -target 1.8 
> >  uk/ac/sanger/artemis/ActionController.java
> > > > /bin/sh: 1: /usr/share/java/j2ssh-core.jar: Permission denied
> > > > make[2]: *** [Makefile:48: uk/ac/sanger/artemis/Action.class]
> > Error 126
> > > 
> > > The full build log is available from:
> > >
> > http://qa-logs.debian.net/2020/06/20/artemis_17.0.1+dfsg-2_unstable.log
> > > 
> > > 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!
> > > 
> > > About the archive rebuild: The rebuild was done on EC2 VM
> > instances from
> > > Amazon Web Services, using a clean, minimal and up-to-date
> > chroot. Every
> > > failed build was retried once to eliminate random failures.
> > > 
> > > ___
> > > Debian-med-packaging mailing list
> > > debian-med-packag...@alioth-lists.debian.net
> > > 
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> > 
-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#963384: marked as done (gnome-desktop3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 11:48:46 +
with message-id 
and subject line Bug#963384: fixed in gnome-desktop3 3.36.3.1-2
has caused the Debian Bug report #963384,
regarding gnome-desktop3: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu 
&& LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p -m0700 /<>/debian/tmp/run
> NO_AT_BRIDGE=1 XDG_RUNTIME_DIR=/<>/debian/tmp/run 
> G_MESSAGES_DEBUG=all xvfb-run -a dh_auto_test
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test
> [0/1] Running all tests.
> 1/2 wall-clockOK 0.77s
> 2/2 wallclock-reftest FAIL   0.12s (killed by signal 6 SIGABRT)
> 
> Ok: 1   
> Expected Fail:  0   
> Fail:   1   
> Unexpected Pass:0   
> Skipped:0   
> Timeout:0   
> 
> 
> The output from the failed tests:
> 
> 2/2 wallclock-reftest FAIL   0.12s (killed by signal 6 SIGABRT)
> 
> --- command ---
> 07:27:43 G_ENABLE_DIAGNOSTICS='0' 
> G_TEST_BUILDDIR='/<>/obj-x86_64-linux-gnu/tests' 
> G_TEST_SRCDIR='/<>/tests' 
> /<>/obj-x86_64-linux-gnu/tests/wallclock-reftest
> --- Listing only the last 100 lines from a long log. ---
> # GnomeDesktop-DEBUG: is_utf8: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.307: is_utf8: FALSE
> # GnomeDesktop-DEBUG: ret: Wed May 28  23:59:59
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.307: ret: Wed May 28  23:59:59
> # Date string is: 'Wed May 28  23:59:59'
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.307: unwatch_fast: "/org/gnome/desktop/interface/" 
> (active: 0, establishing: 1)
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.308: watch_established: "/org/gnome/desktop/interface/" 
> (establishing: 0)
> # Storing test result image at 
> /<>/obj-x86_64-linux-gnu/tests/../meson-logs/C.out.png
> # Storing test result image at 
> /<>/obj-x86_64-linux-gnu/tests/../meson-logs/C.ref.png
> ok 1 /<>/tests/C.ui
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.339: watch_fast: "/org/gnome/desktop/interface/" 
> (establishing: 0, active: 0)
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> dconf-DEBUG: 07:27:43.339: watch_established: "/org/gnome/desktop/interface/" 
> (establishing: 1)
> # GnomeDesktop-DEBUG: clock_format: 24h
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: clock_format: 24h
> # GnomeDesktop-DEBUG: show_weekday: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_weekday: FALSE
> # GnomeDesktop-DEBUG: show_full_date: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_full_date: TRUE
> # GnomeDesktop-DEBUG: show_seconds: FALSE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: show_seconds: FALSE
> # GnomeDesktop-DEBUG: format_string: %b %-e_%R
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: format_string: %b %-e_%R
> # GnomeDesktop-DEBUG: no_enspace: %b %-e_%R
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: no_enspace: %b %-e_%R
> # GnomeDesktop-DEBUG: replaced_format: Jun 21_07:27
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: replaced_format: Jun 21_07:27
> # GnomeDesktop-DEBUG: is_utf8: TRUE
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: is_utf8: TRUE
> # GnomeDesktop-DEBUG: ret: Jun 21 07‎∶27
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: ret: Jun 21 07‎∶27
> # GnomeDesktop-DEBUG: clock_format: 24h
> (/<>/obj-x86_64-linux-gnu/tests/wallclock-reftest:6815): 
> GnomeDesktop-DEBUG: 07:27:43.339: clock_format: 24h
> # GnomeDesktop-DEBUG: show_weekday: TRUE
> 

Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error

[Michael Meskes]

> > Any idea how this scenario could unfold? I cannot imagine how it
> > could
> > get there. What I will do, though, is add a "Breaks: man-db
> > (<<2.9.3-
> > 1)" to bsdmainutils. Actually this is already in git.
> 
> Breaks only ensures that new bsdmainutils can't be unpacked until
> man-db
> is deconfigured.  For example, it would still permit this plausible
> upgrade ordering, which AFAIK apt would have no particular reason to
> avoid:
> 
>  1. deconfigure old man-db
>  2. unpack new bsdmainutils
>  3. configure new bsdmainutils
>  4. (piles of other stuff)
>  5. unpack bsdextrautils
>  6. unpack new man-db
>  7. configure bsdextrautils
>  8. configure man-db
> 
> man would be broken between the end of step 1 and the end of step
> 5.  I
> think this is undesirable and unnecessary.

Good points. However, I still don't see where this creates problems in
the upgrade process unless some postinst calls man.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#963327: [Pkg-zsh-devel] Processed: Merge duplicates

[Adrian Bunk]

On Mon, Jun 22, 2020 at 02:03:10PM +0200, Michael Meskes wrote:
> > I already updated the title of the mass-merged bug to
> > "bsdmainutils must depend on bsdextrautils".
> > 
> > This is anyway mandatory for not breaking upgrades from buster.
> 
> Would you care to elaborate? I didn't find anything that mandates a dependency
> over a recommendation.

It is common practice to have dependencies for one Debian release,
to ensure noone loses during an upgrade what was moved elsewhere.

> Yes, it does break build dependencies but imo they should
> be changed anyway.

Build breakage out of the void is not nice, usually maintainers inform 
reverse build dependencies them before making such a breaking change.

The same is true for runtime dependencies,
where breakage can be much more user-visible.

Worst are breakages it might cause for users upgrading from buster
to bullseye.

The majority of users are using the default of treating Recommends
as dependencies, for them it doesn't make any difference whether
Recommends or Depends is used.

Not installing Recommends is supported, and desirable in many
embedded/server/container scenarios.

The documented way to upgrade to a new stable release is basically
  apt-get upgrade
  apt-get dist-upgrade

Without a dependency the first step might upgrade bsdmainutils,
but will never install bsdextrautils.

I do not know for what tools software like salt or libguestfs in buster 
depends on bsdmainutils, and I definitely do not want our users to learn 
the hard way during an upgrade.

Installing bsdmainutils from unstable in buster breaks commands like
  man ncal | cat
I would not be surprised if there is somewhere in Debian some package
that would do something like that for whatever good or bad reason in
a postinst or prerm.

> Michael

cu
Adrian

BTW: The naming of the packages is confusing.

"extra" sounds like the more obscure utils,
enhanching the more commonly used "main" tools.
Looking at the tools shipped, the opposite seems to be true.

One could make the point that bsdmainutils should
be a (transitional?) metapackage depending on all
the tools it previously provided.

Processed: Re: reverse-depends command is broken because qa.ubuntuwire.org is down

[Debian Bug Tracking System]

Processing control commands:

> close -1
Bug #963538 [ubuntu-dev-tools] reverse-depends command is broken because 
qa.ubuntuwire.org is down
Marked Bug as done

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

Bug#963538: reverse-depends command is broken because qa.ubuntuwire.org is down

[Gianfranco Costamagna]

control: close -1

On Tue, 23 Jun 2020 15:25:08 +0530 Pirate Praveen  
wrote:
> Package: ubuntu-dev-tools
> Version: 0.176
> Severity: grave
> Justification: ships a broken command
> 
> reverse-depends command queries qa.ubuntuwire.org which is down. This 
> is a very useful command and we should get the service up again or 
> possibly run on debian infra if it is down permanently.
> 

the service is back, but yes, if somebody gets the source code for 
ubuntuwire.org service and replicates in Debian,
the tool can be easily adapted to work with two different infrastructures!

G.

Bug#962158: marked as done (lintian: Swapped exit statuses and --fail-on default value require downstream adjustments)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 11:05:20 +
with message-id 
and subject line Bug#962158: fixed in lintian 2.81.0
has caused the Debian Bug report #962158,
regarding lintian: Swapped exit statuses and --fail-on default value require 
downstream adjustments
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.)


-- 
962158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.80.0
Severity: important

[ This probably deserves to be serious, but I'm not sure I can be
  bothered… ]

Hi,

As was mentioned on debian-devel@l.d.o, and on #debian-qa, the new
default is very problematic, and has not been properly justified.

The general expectation is that a linter is supposed to exit non-0
when it finds at least errors. When people use it in manual mode,
they will just see the reported tags, but in automatic settings the
error code is what makes this useful at all.

This change means that any current caller which uses lintian as part
of its acceptance testing will now silently let broken things through
(until someone eventually notices the breakage), some examples of this
in Debian are:

  - dupload/dput/dput-ng
  - sbuild
  - pbuilder
  - check-all-the-things
  - debomatic (?)
  - jenkins-debian-glue
  - pkg-perl-tools
  - dpkg-buildpackage --check-command
  - etc.

Then also any CI setup that uses lintian (say in .gitlab-ci.yml or
.travis, .circleci, or similar stuff).

While these could be adapted in Debian, it would still leave any CI or
in-house setup that calls lintian broken. This is made worse due to the
new option not being available in older releases before the default got
changed, which would imply cumbersome backward compatibility checks that
decide whether to use the new option or not.

If the default change made sense due to some technical rationale, this
effort might be worthwhile, but as it is, this is a bad default that will
require tons of useless work and introduces breakage for no good reason.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.81.0
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated lintian 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, 23 Jun 2020 09:47:18 +0100
Source: lintian
Architecture: source
Version: 2.81.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers 
Changed-By: Chris Lamb 
Closes: 243158 554897 591665 755161 895597 904885 909696 914256 945869 950052 
954459 954860 961709 961973 961975 962157 962158 962448 962583 962601 962671 
963212
Changes:
 lintian (2.81.0) unstable; urgency=medium
 .
   [ Felix Lechner ]
   * Remove command line option --fail-on from the settings in configuration
 files. (Closes: #962157)
   * Use UTF-8 codepoint for copyright sign in copyright files.
 (Closes: #961975)
   * Add tag for architecture-specific paths in debian/not-installed.
 (Closes: #961973)
   * Rename tag to recursive-privilege-change and explain usage of
 runuser(1). (Closes: #895597)
   * Do not enable Perl warnings globally to reduce output clutter from
 external modules.
   * In debian/control, add dh-r to Build-Depends. (See: #961709)
   * Add two test cases from Ansgar's 'colorful' test package.
 (See: #962277)
   * Drop Email::Valid as obsolete and use regex to check emails for fully
 qualified hosts. (See: #962277)
   * Flag the use of acute accents in manpages. (Closes: #554897)
   * Flag ANSI escape characters in all fields of primary packaging control
 files. (See: #962277)
   * In check menus, title-case the hash keys representing field labels to
 make the tag context more human-readable.
   * Rename tag for mailing list on Alioth and convert to classification
 tag. (Closes: #962448)
   * Add a classification tag for field contents in primary package control
 files.
   * Find 

Bug#963211: Still occurs in 1:3.9-3

[Kyle Robbertze]

Control: found -1 1:3.9-3

Hi,

This error is still occurring:

> Unpacking libmu-dbm6:amd64 (1:3.9-3) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libmu-dbm6_1%3a3.9-3_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libmu_dbm.so.6.0.0', which is 
> also in package libmailutils6:amd64 1:3.7-2.1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Cheers
Kyle
-- 

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
⢿⡄⠘⠷⠚⠋⠀ Debian Developer
⠈⠳⣄ https://wiki.debian.org/KyleRobbertze

Processed: Still occurs in 1:3.9-3

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:3.9-3
Bug #963211 {Done: Jordi Mallach } [libmu-dbm6] libmu-dbm6: 
Tries to overwrite `libmu_dbm.so.6.0.0` from `libmailutils6`
Marked as found in versions mailutils/1:3.9-3; no longer marked as fixed in 
versions mailutils/1:3.9-3 and reopened.

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

Bug#962320: (no subject)

[Raul Tambre]

The original crash was fixed in facter 3.11.0-4.2 for me.

Bug#963539: [Pkg-javascript-devel] Bug#963539: npm: autopkgtests failures on various architectures

[Xavier]

Le 23/06/2020 à 12:01, Gianfranco Costamagna a écrit :
> Source: npm
> Version: 6.14.5+ds-1
> Severity: serious
> 
> Hello, looks like npm is failing again its autopkgtests...
> 
> On armhf there is a timeout that I "fixed" with: 
> https://github.com/npm/cli/pull/1454
> 
> on ppc64el there is another failure:
> https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/npm/6017343/log.gz
> 
> and I also spot a s390x failure on Ubuntu:
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200505_235736_15e60@/log.gz
> 
> can you please have another look?
> (in the meanwhile I'm marking that test as flaky in Ubuntu)
> 
> thanks!

Hi,

when trying to launch tests on a s390x machine, I got this kind of error:

Error: Failed to replace env in config: ${prefix}
at /home/yadd/cli-6.14.5/lib/config/core.js:415:13
at String.replace ()
at envReplace (/home/yadd/cli-6.14.5/lib/config/core.js:411:12)
at parseField (/home/yadd/cli-6.14.5/lib/config/core.js:389:7)
at /home/yadd/cli-6.14.5/lib/config/core.js:330:24
at Array.forEach ()
at Conf.add (/home/yadd/cli-6.14.5/lib/config/core.js:328:23)
at ConfigChain.addString
(/home/yadd/cli-6.14.5/node_modules/config-chain/index.js:244:8)
at Conf. (/home/yadd/cli-6.14.5/lib/config/core.js:316:10)
at /home/yadd/cli-6.14.5/node_modules/graceful-fs/graceful-fs.js:123:16

Bug#963287: notmuch: FTBFS: grotty: ():1662: fatal error: output error

[Colin Watson]

On Tue, Jun 23, 2020 at 11:02:02AM +0200, Michael Meskes wrote:
> Colin Watson wrote:
> > However, in order to make buster → bullseye upgrades work properly,
> > I think it's necessary to have bsdmainutils depend on bsdextrautils
> > for at least one release cycle.  Otherwise there may be a point
> > during the upgrade where col isn't installed and so man will be
> > broken; it's worth putting some effort into avoiding that because if
> > the upgrade happens to break then users may need to consult man
> > pages to work out what to do.  The only reliable way I can think of
> > to avoid this kind of problem is to have a hard dependency for a
> > while as a transitional measure.
> 
> Any idea how this scenario could unfold? I cannot imagine how it could
> get there. What I will do, though, is add a "Breaks: man-db (<<2.9.3-
> 1)" to bsdmainutils. Actually this is already in git.

Breaks only ensures that new bsdmainutils can't be unpacked until man-db
is deconfigured.  For example, it would still permit this plausible
upgrade ordering, which AFAIK apt would have no particular reason to
avoid:

 1. deconfigure old man-db
 2. unpack new bsdmainutils
 3. configure new bsdmainutils
 4. (piles of other stuff)
 5. unpack bsdextrautils
 6. unpack new man-db
 7. configure bsdextrautils
 8. configure man-db

man would be broken between the end of step 1 and the end of step 5.  I
think this is undesirable and unnecessary.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#955474: marked as done (FTBFS: fatal error: stropts.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 12:19:03 +0200
with message-id 

and subject line Fixed on the python side
has caused the Debian Bug report #954582,
regarding FTBFS: fatal error: stropts.h: No such file or directory
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.)


-- 
954582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samba
Version: 2:4.11.5+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: de...@kali.org
Usertags: origin-kali

Trying to rebuild samba in sid fails with:

[2422/4221] Linking bin/default/source4/kdc/libdb-glue.so
08:56:24 runner ['/usr/bin/gcc', 
'-Wl,--version-script=/<>/bin/default/source4/kdc/db-glue.vscript',
 '-shared', '-Wl,-h,libdb-glue.so.0', 
'source4/librpc/gen_ndr/ndr_irpc_c.c.18.o', 'source4/kdc/db-glue.c.18.o', 
'source4/kdc/sdb.c.10.o', 
'-o/<>/bin/default/source4/kdc/libdb-glue.so', '-Wl,-Bstatic', 
'-Wl,-Bdynamic', '-L/<>/bin/default/nsswitch', 
'-L/<>/bin/default/libcli/registry', 
'-L/<>/bin/default/source4/libcli/ldap', 
'-L/<>/bin/default/nsswitch/libwbclient', 
'-L/<>/bin/default/libcli/dns', 
'-L/<>/bin/default/libds/common', 
'-L/<>/bin/default/lib/socket', 
'-L/<>/bin/default/libcli/cldap', 
'-L/<>/bin/default/libcli/nbt', 
'-L/<>/bin/default/source4/lib/socket', 
'-L/<>/bin/default/auth/gensec', 
'-L/<>/bin/default/lib/addns', 
'-L/<>/bin/default/libcli/smb', 
'-L/<>/bin/default/source4/lib/http', 
'-L/<>/bin/default/source4/libcli', 
'-L/<>/bin/default/lib/dbwrap', 
'-L/<>/bin/default/source4/lib/events', 
'-L/<>/bin/default/third_party/aesni-intel', 
'-L/<>/bin/default/lib/tdb_wrap', 
'-L/<>/bin/default/source4/auth/kerberos', 
'-L/<>/bin/default/lib/ldb-samba', 
'-L/<>/bin/default/libcli/auth', 
'-L/<>/bin/default/libcli/ldap', 
'-L/<>/bin/default/lib/krb5_wrap', 
'-L/<>/bin/default/libcli/util', 
'-L/<>/bin/default/source3', 
'-L/<>/bin/default/source4/cluster', 
'-L/<>/bin/default/lib', 
'-L/<>/bin/default/lib/util', 
'-L/<>/bin/default/librpc', 
'-L/<>/bin/default/lib/param', 
'-L/<>/bin/default/source4/librpc', 
'-L/<>/bin/default/auth/credentials', 
'-L/<>/bin/default/source4/dsdb', 
'-L/<>/bin/default/source4/heimdal_build', 
'-L/<>/bin/default/lib/replace', 
'-L/<>/bin/default/source4/lib/messaging', 
'-L/<>/bin/default/auth', 
'-L/<>/bin/default/libcli/security', '-L/usr/local/lib', 
'-L/usr/local/lib', '-lsamba-security', '-lcommon-auth', '-lMESSAGING', 
'-lreplace', '-lcom_err-samba4', '-lsamdb', '-lsamba-credentials', 
'-lndr-samba4', '-lkrb5-samba4', '-ldcerpc', '-lsamba-hostconfig', '-lndr', 
'-lMESSAGING-SEND', '-lserver-id-db', '-lsamba-sockets', '-lsamba-util', 
'-lndr-samba', '-lsamba-debug', '-ltalloc-report', '-lcluster', 
'-lmessages-util', '-lroken-samba4', '-lsamba-errors', '-lkrb5samba', 
'-lcli-ldap-common', '-lsamdb-common', '-lcliauth', '-lldbsamba', '-lauthkrb5', 
'-ltdb-wrap', '-lutil-tdb', '-laesni-intel', '-levents', '-lgssapi-samba4', 
'-ldbwrap', '-lndr-standard', '-lndr-krb5pac', '-lndr-nbt', '-lasn1-samba4', 
'-lheimbase-samba4', '-lwind-samba4', '-lhcrypto-samba4', '-lhx509-samba4', 
'-lsmbclient-raw', '-lhttp', '-lcli-smb-common', '-laddns', '-lgensec', 
'-ltevent-util', '-ldcerpc-samba', '-lnetif', '-lcli-nbt', '-ldcerpc-binding', 
'-lcli-cldap', '-lserver-role', '-lmessages-dgm', '-linterfaces', 
'-lsocket-blocking', '-liov-buf', '-lgenrand', '-lutil-setid', '-ltime-basic', 
'-lsys-rw', '-lasn1util', '-lflag-mapping', '-lCHARSET3', '-lsamba3-util', 
'-lsmbconf', '-lsmb-transport', '-lclidns', '-lsamba-modules', '-lwbclient', 
'-lcli-ldap', '-lmsghdr', '-lutil-reg', '-lsmbd-shim', '-lwinbind-client', 
'-lcap', '-lcups', '-lldap', '-llber', '-lnsl', '-lutil', '-lresolv', '-lz', 
'-lsystemd', '-lgnutls', '-lpthread', '-lldb', '-ltalloc', '-ljansson', 
'-ltalloc', '-lcrypt', '-lbsd', '-ltdb', '-ltevent', '-ltalloc', '-ldl', 
'-Wl,-z,relro', '-Wl,-z,now', '-Wl,--as-needed', '-Wl,-z,relro,-z,now', 
'-Wl,-no-undefined', '-Wl,--export-dynamic', '-Wl,--as-needed']
In file included from ../../source4/heimdal_build/krb5-types.h:8,
 from ../../source4/heimdal/lib/krb5/krb5.h:42,
 from ../../lib/replace/system/kerberos.h:33,
 from ../../auth/credentials/pycredentials.c:35:
../../lib/replace/system/network.h:91:10: fatal error: stropts.h: No such file 
or directory
   91 | #include 
  |  ^~~
compilation terminated.


What is weird is that this include is protected by #ifdef:

#ifdef HAVE_STROPTS_H
#include 
#endif

Bug#962320: facter crashes with "free(): invalid pointer"

[Giovanni Mascellani]

Il 13/06/20 11:05, Giovanni Mascellani ha scritto:
> No problems in line of principle, but I am not sure I understand what
> would this solve: the conflict between two different versions of Boost
> arises when the same executable links against both (through different
> dependencies). There is no problem in having both versions installed at
> the same time.
> 
> So, given that we have to make sure that bullseye packages link only
> against 1.71 (or whatever it will be, but just one version), what is to
> be gained by having the Break: indication?

Ping?

Thanks, Giovanni.
-- 
Giovanni Mascellani 
Postdoc researcher - Université Libre de Bruxelles



signature.asc
Description: OpenPGP digital signature

Bug#963300: marked as done (qscintilla2: FTBFS: sipQscipart0.cpp:68074:37: error: no matching function for call to ‘QsciAPIs::QsciAPIs()’)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 10:19:59 +
with message-id 
and subject line Bug#963300: fixed in qscintilla2 2.11.2+dfsg-7
has caused the Debian Bug report #963300,
regarding qscintilla2: FTBFS: sipQscipart0.cpp:68074:37: error: no matching 
function for call to ‘QsciAPIs::QsciAPIs()’
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.)


-- 
963300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qscintilla2
Version: 2.11.2+dfsg-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -c -pipe -fno-exceptions -O2 -Wall -W -D_REENTRANT -fPIC 
> -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DQT_NO_DEBUG -DQT_PLUGIN 
> -DQT_GUI_LIB -DQT_CORE_LIB -I. -I../../../QSciQt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/python3.8 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o sipQscipart0.o 
> sipQscipart0.cpp
> /<>/Python/buildqt5-3.8/Qsci/sipQscipart0.cpp: In function 
> ‘void* array_QsciAPIs(Py_ssize_t)’:
> /<>/Python/buildqt5-3.8/Qsci/sipQscipart0.cpp:68074:37: error: 
> no matching function for call to ‘QsciAPIs::QsciAPIs()’
> 68074 | #line 26 "/usr/share/sip/PyQt5/QtGui/qcolor.sip"
>   | ^
> In file included from /<>/Python/sip/qsciapis.sip:24:
> ../../../QSciQt5/Qsci/qsciapis.h:209:5: note: candidate: 
> ‘QsciAPIs::QsciAPIs(const QsciAPIs&)’
>   209 | QsciAPIs(const QsciAPIs &);
>   | ^~~~
> ../../../QSciQt5/Qsci/qsciapis.h:209:5: note:   candidate expects 1 argument, 
> 0 provided
> ../../../QSciQt5/Qsci/qsciapis.h:73:5: note: candidate: 
> ‘QsciAPIs::QsciAPIs(QsciLexer*)’
>73 | QsciAPIs(QsciLexer *lexer);
>   | ^~~~
> ../../../QSciQt5/Qsci/qsciapis.h:73:5: note:   candidate expects 1 argument, 
> 0 provided
> make[3]: *** [Makefile:427: sipQscipart0.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/qscintilla2_2.11.2+dfsg-6_unstable.log

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!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: qscintilla2
Source-Version: 2.11.2+dfsg-7
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated qscintilla2 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, 23 Jun 2020 12:55:57 +0300
Source: qscintilla2
Architecture: source
Version: 2.11.2+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Closes: 963300
Changes:
 qscintilla2 (2.11.2+dfsg-7) unstable; urgency=medium
 .
   * Team upload.
   * Update debian/watch to find latest releases properly.
   * Add upstream patch to fix the Python signatures of the QsciAbstractAPIs
 and QsciAPIs constructors (closes: #963300).
Checksums-Sha1:
 d249139dffeb5adcab6c9d24382e8ab225c9056a 2920 qscintilla2_2.11.2+dfsg-7.dsc
 131606d14d2c4e3355ef5bb3839f15c35a11f207 110376 
qscintilla2_2.11.2+dfsg-7.debian.tar.xz
 25167243a4f4e6073da3f8ffd6d7cbade8f7f928 12309 
qscintilla2_2.11.2+dfsg-7_source.buildinfo
Checksums-Sha256:
 ce949e7c963a6364c7ddd19b13cf77ecc652234cd607de8f0d7bbb1a3c78922b 2920 
qscintilla2_2.11.2+dfsg-7.dsc
 

Processed: Bug#963300 marked as pending in qscintilla2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963300 [src:qscintilla2] qscintilla2: FTBFS: sipQscipart0.cpp:68074:37: 
error: no matching function for call to ‘QsciAPIs::QsciAPIs()’
Ignoring request to alter tags of bug #963300 to the same tags previously set

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

Bug#963300: marked as pending in qscintilla2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/qscintilla2/-/commit/6ea69788b5c0a9d2367fc29d7ba1dc7686a19751


Add upstream patch to fix the Python signatures of the QsciAPIs ctors.

Closes: #963300.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963300

Bug#963153: ffmpeg breaks r-cran-av autopkgtest: error in 'avcodec_open2 (audio)': Invalid argument

[Andreas Tille]

Hi Sebastian,

if you look at my DDPO page I have *lots* of packages.  I really like if
people are doing sensible work (as you did) *without* my interaction.
I'm really happy if you NMU (that's why I confirmed) or perhaps do a
team upload.  Any help is welcome and I do not want to fiddle around with
the perfectly fine work of you.  So why should I want any more delay or
why should I want it at all?

The only thing I would love you to do is to push your changes to Git
(just given permissions).

Thanks a lot for your work and to bad if other maintainers might have
created a culture of making a fuzz about NMUs

  Andreas.

On Tue, Jun 23, 2020 at 11:39:15AM +0200, Sebastian Ramacher wrote:
> On 2020-06-23 11:15:52 +0200, Andreas Tille wrote:
> > Hi Sebastian,
> > 
> > On Tue, Jun 23, 2020 at 10:50:50AM +0200, Sebastian Ramacher wrote:
> > > Control: notfound -1 ffmpeg/7:4.3-2
> > > Control: tags -1 + patch
> > > 
> > > Hi Andreas
> > > 
> > > ...
> > > The attached patch fixes this issue by generting an empty mp3 with the
> > > default sampling rate of 44.1 KHz during package build instead of
> > > copying the file from libmp3-tag-perl. If you want, I can upload it as
> > > NMU.
> > 
> > Any NMU or team upload is perfectly welcome.
> 
> Uploaded to DELAYED/2 with the attached diff. Please let me know if I
> should delay it longer.
> 
> Cheers
> -- 
> Sebastian Ramacher

> diff -Nru r-cran-av-0.5.0+dfsg/debian/changelog 
> r-cran-av-0.5.0+dfsg/debian/changelog
> --- r-cran-av-0.5.0+dfsg/debian/changelog 2020-05-20 09:34:42.0 
> +0200
> +++ r-cran-av-0.5.0+dfsg/debian/changelog 2020-06-23 11:31:26.0 
> +0200
> @@ -1,3 +1,11 @@
> +r-cran-av (0.5.0+dfsg-3.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/rules: Generate empty mp3 file with ffmpeg with a sample rate
> +supported by all formats used in the tests (Closes: #965153)
> +
> + -- Sebastian Ramacher   Tue, 23 Jun 2020 11:31:26 
> +0200
> +
>  r-cran-av (0.5.0+dfsg-3) unstable; urgency=medium
>  
>* Provide mp3 example properly
> diff -Nru r-cran-av-0.5.0+dfsg/debian/control 
> r-cran-av-0.5.0+dfsg/debian/control
> --- r-cran-av-0.5.0+dfsg/debian/control   2020-05-20 09:34:42.0 
> +0200
> +++ r-cran-av-0.5.0+dfsg/debian/control   2020-06-23 10:26:49.0 
> +0200
> @@ -8,7 +8,7 @@
> dh-r,
> r-base-dev,
> libavfilter-dev,
> -   libmp3-tag-perl
> +   ffmpeg
>  Standards-Version: 4.5.0
>  Vcs-Browser: https://salsa.debian.org/r-pkg-team/r-cran-av
>  Vcs-Git: https://salsa.debian.org/r-pkg-team/r-cran-av.git
> diff -Nru r-cran-av-0.5.0+dfsg/debian/rules r-cran-av-0.5.0+dfsg/debian/rules
> --- r-cran-av-0.5.0+dfsg/debian/rules 2020-05-20 09:34:42.0 +0200
> +++ r-cran-av-0.5.0+dfsg/debian/rules 2020-06-23 10:26:38.0 +0200
> @@ -7,4 +7,4 @@
>  
>  override_dh_install:
>   dh_install
> - cp -a /usr/share/doc/libmp3-tag-perl/examples/empty_10sec.mp3 
> $(debRlib)/$(cranNameOrig)/samples/Synapsis-Wonderland.mp3
> + ffmpeg -f lavfi -i anullsrc=r=44100:cl=mono -t 10 -acodec libmp3lame 
> $(debRlib)/$(cranNameOrig)/samples/Synapsis-Wonderland.mp3




-- 
http://fam-tille.de

Bug#963300: marked as pending in qscintilla2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/qscintilla2/-/commit/6ea69788b5c0a9d2367fc29d7ba1dc7686a19751


Add upstream patch to fix the Python signatures of the QsciAPIs ctors.

Closes: #963300.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963300

Processed: Bug#963300 marked as pending in qscintilla2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963300 [src:qscintilla2] qscintilla2: FTBFS: sipQscipart0.cpp:68074:37: 
error: no matching function for call to ‘QsciAPIs::QsciAPIs()’
Ignoring request to alter tags of bug #963300 to the same tags previously set

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

Bug#963539: npm: autopkgtests failures on various architectures

[Gianfranco Costamagna]

Source: npm
Version: 6.14.5+ds-1
Severity: serious

Hello, looks like npm is failing again its autopkgtests...

On armhf there is a timeout that I "fixed" with: 
https://github.com/npm/cli/pull/1454

on ppc64el there is another failure:
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/npm/6017343/log.gz

and I also spot a s390x failure on Ubuntu:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/n/npm/20200505_235736_15e60@/log.gz

can you please have another look?
(in the meanwhile I'm marking that test as flaky in Ubuntu)

thanks!

Gianfranco

Bug#963300: marked as pending in qscintilla2

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/qscintilla2/-/commit/6ea69788b5c0a9d2367fc29d7ba1dc7686a19751


Add upstream patch to fix the Python signatures of the QsciAPIs ctors.

Closes: #963300.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963300

Bug#963538: reverse-depends command is broken because qa.ubuntuwire.org is down

[Pirate Praveen]

Package: ubuntu-dev-tools
Version: 0.176
Severity: grave
Justification: ships a broken command

reverse-depends command queries qa.ubuntuwire.org which is down. This 
is a very useful command and we should get the service up again or 
possibly run on debian infra if it is down permanently.

Processed: Bug#963300 marked as pending in qscintilla2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963300 [src:qscintilla2] qscintilla2: FTBFS: sipQscipart0.cpp:68074:37: 
error: no matching function for call to ‘QsciAPIs::QsciAPIs()’
Added tag(s) pending.

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

Processed: reassign 963153 to r-cran-av

[Debian Bug Tracking System]

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

> # fix meta data
> reassign 963153 r-cran-av 0.5.0+dfsg-3
Bug #963153 [src:ffmpeg, src:r-cran-av] ffmpeg breaks r-cran-av autopkgtest: 
error in 'avcodec_open2 (audio)': Invalid argument
Bug reassigned from package 'src:ffmpeg, src:r-cran-av' to 'r-cran-av'.
No longer marked as found in versions r-cran-av/0.5.0+dfsg-3.
Ignoring request to alter fixed versions of bug #963153 to the same values 
previously set
Bug #963153 [r-cran-av] ffmpeg breaks r-cran-av autopkgtest: error in 
'avcodec_open2 (audio)': Invalid argument
Marked as found in versions r-cran-av/0.5.0+dfsg-3.
> tags 963153 pending
Bug #963153 [r-cran-av] ffmpeg breaks r-cran-av autopkgtest: error in 
'avcodec_open2 (audio)': Invalid argument
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#963153: ffmpeg breaks r-cran-av autopkgtest: error in 'avcodec_open2 (audio)': Invalid argument

[Sebastian Ramacher]

On 2020-06-23 11:15:52 +0200, Andreas Tille wrote:
> Hi Sebastian,
> 
> On Tue, Jun 23, 2020 at 10:50:50AM +0200, Sebastian Ramacher wrote:
> > Control: notfound -1 ffmpeg/7:4.3-2
> > Control: tags -1 + patch
> > 
> > Hi Andreas
> > 
> > ...
> > The attached patch fixes this issue by generting an empty mp3 with the
> > default sampling rate of 44.1 KHz during package build instead of
> > copying the file from libmp3-tag-perl. If you want, I can upload it as
> > NMU.
> 
> Any NMU or team upload is perfectly welcome.

Uploaded to DELAYED/2 with the attached diff. Please let me know if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru r-cran-av-0.5.0+dfsg/debian/changelog 
r-cran-av-0.5.0+dfsg/debian/changelog
--- r-cran-av-0.5.0+dfsg/debian/changelog   2020-05-20 09:34:42.0 
+0200
+++ r-cran-av-0.5.0+dfsg/debian/changelog   2020-06-23 11:31:26.0 
+0200
@@ -1,3 +1,11 @@
+r-cran-av (0.5.0+dfsg-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Generate empty mp3 file with ffmpeg with a sample rate
+supported by all formats used in the tests (Closes: #965153)
+
+ -- Sebastian Ramacher   Tue, 23 Jun 2020 11:31:26 +0200
+
 r-cran-av (0.5.0+dfsg-3) unstable; urgency=medium
 
   * Provide mp3 example properly
diff -Nru r-cran-av-0.5.0+dfsg/debian/control 
r-cran-av-0.5.0+dfsg/debian/control
--- r-cran-av-0.5.0+dfsg/debian/control 2020-05-20 09:34:42.0 +0200
+++ r-cran-av-0.5.0+dfsg/debian/control 2020-06-23 10:26:49.0 +0200
@@ -8,7 +8,7 @@
dh-r,
r-base-dev,
libavfilter-dev,
-   libmp3-tag-perl
+   ffmpeg
 Standards-Version: 4.5.0
 Vcs-Browser: https://salsa.debian.org/r-pkg-team/r-cran-av
 Vcs-Git: https://salsa.debian.org/r-pkg-team/r-cran-av.git
diff -Nru r-cran-av-0.5.0+dfsg/debian/rules r-cran-av-0.5.0+dfsg/debian/rules
--- r-cran-av-0.5.0+dfsg/debian/rules   2020-05-20 09:34:42.0 +0200
+++ r-cran-av-0.5.0+dfsg/debian/rules   2020-06-23 10:26:38.0 +0200
@@ -7,4 +7,4 @@
 
 override_dh_install:
dh_install
-   cp -a /usr/share/doc/libmp3-tag-perl/examples/empty_10sec.mp3 
$(debRlib)/$(cranNameOrig)/samples/Synapsis-Wonderland.mp3
+   ffmpeg -f lavfi -i anullsrc=r=44100:cl=mono -t 10 -acodec libmp3lame 
$(debRlib)/$(cranNameOrig)/samples/Synapsis-Wonderland.mp3


signature.asc
Description: PGP signature

Processed: reassign 963395 to man-db

[Debian Bug Tracking System]

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

> reassign 963395 man-db
Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug reassigned from package 'bsdmainutils' to 'man-db'.
No longer marked as found in versions bsdmainutils/12.1.1.
Ignoring request to alter fixed versions of bug #963395 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#963534: flatbuffers: FTBFS on alpha and hurd

[Sebastian Ramacher]

Control: severity -1 important

Dear Vasyl

On 2020-06-23 09:31:25 +, Vasyl Gello wrote:
> Source: flatbuffers
> Version: debian/1.11.0+dfsg1-1.5
> Severity: serious
> Tags: patch ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear colleagues,
> 
> My previous symbol adjustment for buster made flatbuffers to show in my 
> personal
> package page. Exploring it, I reached buildd logs and found out that alpha, 
> hurd
> and sh4 builds silently fail. Alpha build fails on symbols and hurd on missing
> PATH_MAX definition.

Build issues on non-release architectures are at most of severity
important. Downgrading accordingly.

Cheers

> 
> I fixed both issues and filed another MR against flatbuffers on Salsa.
> 
> The sh4 failure is trickier because it is basically a gtest failing with bus 
> error,
> so I can not investigate it straight away because I do not posess any sh4 
> hardware.
> 
> I also fixed the Lintian warnings and build-tested it against buster-bpo and 
> sid on
> amd64.
> 
> Please review and merge the patches if they are good to go. After that, we 
> can bump
> the upstream to 1.12.0 released 3 months ago. In the meantime, I would like 
> to have
> the fixed build uploaded to buster-backports because of kodi package 
> depending in it.
> 
> Vasyl
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.15.0-106-generic (SMP w/6 CPU cores)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
> en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#963534: flatbuffers: FTBFS on alpha and hurd

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #963534 [src:flatbuffers] flatbuffers: FTBFS on alpha and hurd
Severity set to 'important' from 'serious'

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

Processed: closing 963395

[Debian Bug Tracking System]

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

> close 963395
Bug #963395 [man-db] bsdmainutils must depend on bsdextrautils
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Bug#963384 marked as pending in gnome-desktop3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #963384 [src:gnome-desktop3] gnome-desktop3: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned 
exit code 1
Added tag(s) pending.

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

Bug#963384: marked as pending in gnome-desktop3

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #963384 in gnome-desktop3 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/gnome-desktop/-/commit/ad3398cf00417a857b002721c32f97d253f4712e


Fix FTBFS by not running tests at build-time

The tests assume that this version of libgnome-desktop has already been
installed system-wide, so they are appropriate to run as autopkgtests
but not at build-time.

Closes: #963384


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/963384

Bug#963534: flatbuffers: FTBFS on alpha and hurd

[Vasyl Gello]

Source: flatbuffers
Version: debian/1.11.0+dfsg1-1.5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear colleagues,

My previous symbol adjustment for buster made flatbuffers to show in my personal
package page. Exploring it, I reached buildd logs and found out that alpha, hurd
and sh4 builds silently fail. Alpha build fails on symbols and hurd on missing
PATH_MAX definition.

I fixed both issues and filed another MR against flatbuffers on Salsa.

The sh4 failure is trickier because it is basically a gtest failing with bus 
error,
so I can not investigate it straight away because I do not posess any sh4 
hardware.

I also fixed the Lintian warnings and build-tested it against buster-bpo and 
sid on
amd64.

Please review and merge the patches if they are good to go. After that, we can 
bump
the upstream to 1.12.0 released 3 months ago. In the meantime, I would like to 
have
the fixed build uploaded to buster-backports because of kodi package depending 
in it.

Vasyl

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

Kernel: Linux 4.15.0-106-generic (SMP w/6 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Processed: unmerging 963395

[Debian Bug Tracking System]

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

> unmerge 963395
Bug #963395 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963306 [bsdmainutils] re2c: FTBFS: src/msg/help.cc:3:1: error: expected 
primary-expression before ‘;’ token
Bug #963327 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963350 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963355 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963359 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963361 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963365 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963372 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963375 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963376 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963377 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963378 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963383 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963403 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963413 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963442 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963448 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Bug #963451 [bsdmainutils] bsdmainutils must depend on bsdextrautils
Disconnected #963395 from all other report(s).
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963306
963327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963327
963350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963350
963355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963355
963359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963359
963361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963361
963365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963365
963372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963372
963375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963375
963376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963376
963377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963377
963378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963378
963383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963383
963395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963395
963403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963403
963413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963413
963442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963442
963448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963448
963451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#963153: ffmpeg breaks r-cran-av autopkgtest: error in 'avcodec_open2 (audio)': Invalid argument

[Andreas Tille]

Hi Sebastian,

On Tue, Jun 23, 2020 at 10:50:50AM +0200, Sebastian Ramacher wrote:
> Control: notfound -1 ffmpeg/7:4.3-2
> Control: tags -1 + patch
> 
> Hi Andreas
> 
> ...
> The attached patch fixes this issue by generting an empty mp3 with the
> default sampling rate of 44.1 KHz during package build instead of
> copying the file from libmp3-tag-perl. If you want, I can upload it as
> NMU.

Any NMU or team upload is perfectly welcome.

Thanks a lot
 Andreas.

-- 
http://fam-tille.de

Bug#963241: primus-nvidia: Failed to load libGL

[Felix Dörre]

Hi,

I believe that your /etc/bumblebee/bumblebee.conf is wrong. In the 
[driver-nvidia]-Section, LibraryPath should read:

LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu

This was a change in the packaged config file in this commit: 
https://salsa.debian.org/nvidia-team/bumblebee/-/commit/ca5ae8859c5009347a85a03d45c510094ef8bc69


I don't know why your config file was not updated, maybe some of the 
other maintainers can explain why this happened.


Kind regards,
Felix Dörre

On 6/21/20 12:15 PM, Luigi wrote:

Package: primus-nvidia
Version: 0~20150328-11
Severity: grave
Justification: renders package unusable

Hi,
I tried to launch pvkrun and optirun, but i received the following error in 
both cases:

primus: fatal: failed to load any of the libraries: 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1:/usr/lib/i386-linux-gnu/nvidia/libGL.so.1:/usr/lib/nvidia/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No 
such file or directory
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object file: No 
such file or directory
/usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such file or 
directory

Thanks in advance.

Luigi

-- System Information:
Debian Release: bullseye/sid
   APT prefers unstable
   APT policy: (990, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages primus-nvidia depends on:
ii  bumblebee-nvidia 3.2.1-23
ii  nvidia-driver-libs [nvidia-driver-libs-any]  440.82-2
ii  primus   0~20150328-11

Versions of packages primus-nvidia recommends:
ii  nvidia-primus-vk-wrapper  1.5-1

primus-nvidia suggests no packages.

-- no debconf information

___
pkg-nvidia-devel mailing list
pkg-nvidia-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel



--
Kind regards,
Felix Dörre

Bug#963241: primus-nvidia: Failed to load libGL

[Luigi Curzi]

Hi,
thanks for the help; i removed old config file, that i had modified some
time ago, and after reinstalling packages, pvkrun started working again.

Luigi

On Tue, Jun 23, 2020 at 10:31 AM Felix Dörre  wrote:

> Hi,
>
> I believe that your /etc/bumblebee/bumblebee.conf is wrong. In the
> [driver-nvidia]-Section, LibraryPath should read:
>
> LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu
>
> This was a change in the packaged config file in this commit:
>
> https://salsa.debian.org/nvidia-team/bumblebee/-/commit/ca5ae8859c5009347a85a03d45c510094ef8bc69
>
> I don't know why your config file was not updated, maybe some of the
> other maintainers can explain why this happened.
>
> Kind regards,
> Felix Dörre
>
> On 6/21/20 12:15 PM, Luigi wrote:
> > Package: primus-nvidia
> > Version: 0~20150328-11
> > Severity: grave
> > Justification: renders package unusable
> >
> > Hi,
> > I tried to launch pvkrun and optirun, but i received the following error
> in both cases:
> >
> > primus: fatal: failed to load any of the libraries:
> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1:/usr/lib/i386-linux-gnu/nvidia/libGL.so.1:/usr/lib/nvidia/libGL.so.1
> > /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1: cannot open shared object
> file: No such file or directory
> > /usr/lib/i386-linux-gnu/nvidia/libGL.so.1: cannot open shared object
> file: No such file or directory
> > /usr/lib/nvidia/libGL.so.1: cannot open shared object file: No such file
> or directory
> >
> > Thanks in advance.
> >
> > Luigi
> >
> > -- System Information:
> > Debian Release: bullseye/sid
> >APT prefers unstable
> >APT policy: (990, 'unstable'), (50, 'experimental')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
> > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
> LANGUAGE=it:en_US (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages primus-nvidia depends on:
> > ii  bumblebee-nvidia 3.2.1-23
> > ii  nvidia-driver-libs [nvidia-driver-libs-any]  440.82-2
> > ii  primus   0~20150328-11
> >
> > Versions of packages primus-nvidia recommends:
> > ii  nvidia-primus-vk-wrapper  1.5-1
> >
> > primus-nvidia suggests no packages.
> >
> > -- no debconf information
> >
> > ___
> > pkg-nvidia-devel mailing list
> > pkg-nvidia-de...@alioth-lists.debian.net
> >
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nvidia-devel
>
>
> --
> Kind regards,
> Felix Dörre
>
>

-- 
Luigi Curzi
home mail: tre...@gmail.com
office mail: luigi.cu...@prometeia.com
cell: +39 334 6189712

Bug#963351: marked as done (node-prelude-ls: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 09:04:17 +
with message-id 
and subject line Bug#963351: fixed in node-prelude-ls 1.2.1+dfsg-1
has caused the Debian Bug report #963351,
regarding node-prelude-ls: FTBFS: dh_auto_test: error: /bin/sh -ex 
debian/tests/pkg-js/test returned exit code 2
to be marked as done.

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

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


-- 
963351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-prelude-ls
Version: 1.1.2+dfsg-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdir -p lib/
> /usr/bin/lsc --compile package.json.ls
> /usr/bin/lsc --output lib --bare --compile "src/Func.ls"
> /usr/bin/lsc --output lib --bare --compile "src/List.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Num.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Obj.ls"
> /usr/bin/lsc --output lib --bare --compile "src/Str.ls"
> /usr/bin/lsc --output lib --bare --compile "src/index.ls"
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -R spec debian/tests/Func.js debian/tests/List.js debian/tests/Num.js 
> debian/tests/Obj.js debian/tests/Str.js debian/tests/index.js
> 
> 
>   apply
> ✓ empty list
> ✓ a couple of args
> ✓ curried
> 
>   curry
> ✓ simple function
> 
>   flip
> ✓ minus op
> 
>   fix
> ✓ single arg
> ✓ multi-arg variation
> 
>   over
> ✓ basic
> ✓ with accessor function
> 
>   memoize
> ✓ memoize test
> ✓ call again when using different arguments
> ✓ that the correct values are returned
> 
>   each
> ✓ empty list as input
> ✓ side effects affect input (and thus result)
> ✓ curried
> 
>   map
> ✓ empty list as input
> ✓ mapping over array
> ✓ curried
> 
>   compact
> ✓ empty list as input
> ✓ compacting array
> 
>   filter
> ✓ empty list as input
> ✓ filtering array
> ✓ filter on true returns original list
> ✓ filter on false returns empty list
> ✓ curried
> 
>   reject
> ✓ empty list as input
> ✓ reject list
> ✓ reject on true returns empty list
> ✓ reject on true returns original list
> ✓ curried
> 
>   partition
> ✓ empty list as input
> ✓ partition list
> ✓ partition on true returns original list as passing, empty list as 
> failing
> ✓ partition on false returns empty list as failing, empty list as passing
> ✓ curried
> 
>   find
> ✓ empty list as input
> ✓ find from list
> ✓ finding nothing when function always false
> ✓ find first item when function always true
> ✓ curried
> 
>   list portions
> head
>   ✓ empty list as input
>   ✓ list
>   ✓ first as alias
> tail
>   ✓ empty list as input
>   ✓ list
>   ✓ one element list
> last
>   ✓ empty list as input
>   ✓ list
>   ✓ one element list
> initial
>   ✓ empty list as input
>   ✓ list
>   ✓ one element list
> 
>   empty
> ✓ empty list as input
> ✓ non-empty list as input
> 
>   reverse
> ✓ empty list as input
> ✓ reverse list, it is unmodified
> 
>   unique
> ✓ empty list as input
> ✓ unique list
> ✓ mixed string/num
> 
>   unique-by
> ✓ empty list as input
> ✓ basic
> ✓ accessor
> ✓ curried
> 
>   fold
> ✓ empty list as input
> ✓ list as input
> ✓ foldl is alias
> ✓ curried
> 
>   fold1
> ✓ empty list as input
> ✓ list as input
> ✓ foldl1 as alais
> ✓ curried
> 
>   foldr
> ✓ empty list as input
> ✓ list as input
> ✓ curried
> 
>   foldr1
> ✓ empty list as input
> ✓ list as input
> ✓ curried
> 
>   unfoldr
> ✓ complex case
> ✓ returning null right away results in a one item list
> ✓ curried
> 
>   concat
> ✓ empty list as input
> ✓ multiple lists
> 
>   concat-map
> ✓ empty list as input
> ✓ using mapping and concatinating
> ✓ curried
> 
>   flatten
> ✓ empty list as input
> ✓ nested lists as input
> ✓ lists with strings
> 
>   difference
> ✓ empty list(s) as input
> ✓ subtract nothing
> ✓ subtract single element
> ✓ subtract multiple elements
> 
>   intersection
> ✓ empty list(s) as input
> ✓ no common elements
> ✓ some common elements
> ✓ all 

Bug#925754: marked as done (libopenshot: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jun 2020 09:00:10 +
with message-id 
and subject line Bug#925754: fixed in libopenshot 0.2.5+dfsg1-1~exp1
has caused the Debian Bug report #925754,
regarding libopenshot: ftbfs with GCC-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.)


-- 
925754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libopenshot
Version: 0.2.2+dfsg1-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/libopenshot_0.2.2+dfsg1-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
 from 
/<>/libopenshot-0.2.2+dfsg1/src/../include/AudioResampler.h:41,
 from 
/<>/libopenshot-0.2.2+dfsg1/src/AudioResampler.cpp:28:
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/colour/juce_PixelFormats.h:361:17:
 note: defined here
  361 | class JUCE_API  PixelRGB
  | ^~~~
make[3]: *** [src/CMakeFiles/openshot.dir/build.make:94: 
src/CMakeFiles/openshot.dir/AudioBufferSource.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: *** [src/CMakeFiles/openshot.dir/build.make:120: 
src/CMakeFiles/openshot.dir/AudioResampler.cpp.o] Error 1
In file included from 
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/juce_graphics.h:104,
 from 
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/juce_gui_basics.h:28,
 from 
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/juce_audio_processors.h:28,
 from 
/usr/include/libopenshot-audio/JuceLibraryCode/JuceHeader.h:20,
 from 
/<>/libopenshot-0.2.2+dfsg1/src/../include/AudioReaderSource.h:40,
 from 
/<>/libopenshot-0.2.2+dfsg1/src/AudioReaderSource.cpp:28:
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/native/juce_RenderingHelpers.h:
 In instantiation of 'void 
juce::RenderingHelpers::EdgeTableFillers::SolidColour::replaceLine(juce::PixelRGB*, juce::PixelARGB, int) const 
[with PixelType = juce::PixelRGB; bool replaceExisting = true]':
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/native/juce_RenderingHelpers.h:636:17:
   required from 'void 
juce::RenderingHelpers::EdgeTableFillers::SolidColour::handleEdgeTableLineFull(int, int) const [with PixelType = 
juce::PixelRGB; bool replaceExisting = true]'
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/native/juce_RenderingHelpers.h:1889:29:
   required from 'void 
juce::RenderingHelpers::ClipRegions::RectangleListRegion::SubRectangleIterator::iterate(Renderer&)
 const [with Renderer = 
juce::RenderingHelpers::EdgeTableFillers::SolidColour; 
SavedStateType = juce::RenderingHelpers::SoftwareRendererSavedState]'
/usr/include/libopenshot-audio/JuceLibraryCode/modules/juce_audio_processors/../juce_gui_basics/../juce_graphics/native/juce_RenderingHelpers.h:1513:13:
   required from 'void