Processed: bug 997170 is forwarded to n...@uk.ibm.com

[Debian Bug Tracking System]

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

> forwarded 997170 n...@uk.ibm.com
Bug #997170 [src:nmon] nmon: FTBFS: lmon16m.c:5478:45: error: format not a 
string literal and no format arguments [-Werror=format-security]
Set Bug forwarded-to-address to 'n...@uk.ibm.com'.
> thanks
Stopping processing here.

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

Bug#997476: python-uvicorn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Sandro Tosi]

> > === FAILURES 
> > ===
> > _ test_supported_upgrade_request[H11Protocol] 
> > __
> >
> > protocol_cls = 
> >
> > @pytest.mark.parametrize("protocol_cls", HTTP_PROTOCOLS)
> > def test_supported_upgrade_request(protocol_cls):
> > app = Response("Hello, world", media_type="text/plain")
> >
> > protocol = get_connected_protocol(app, protocol_cls, ws="wsproto")
> > protocol.data_received(UPGRADE_REQUEST)
> >
> > >   assert b"HTTP/1.1 426 " in protocol.transport.buffer
> > E   AssertionError: assert b'HTTP/1.1 426 ' in b'HTTP/1.1 400 
> > \r\nSec-WebSocket-Version: 13\r\ncontent-length: 0\r\n\r\n'
> > E+  where b'HTTP/1.1 400 \r\nSec-WebSocket-Version: 
> > 13\r\ncontent-length: 0\r\n\r\n' =  > 0x7f5dfc10cf10>.buffer
> > E+where  = 
> >  > 0x7f5dfc104fd0>.transport
> >
> > tests/protocols/test_http.py:685: AssertionError
> > __ test_supported_upgrade_request[HttpToolsProtocol] 
> > ___
> >
> > protocol_cls =  > 'uvicorn.protocols.http.httptools_impl.HttpToolsProtocol'>
> >
> > @pytest.mark.parametrize("protocol_cls", HTTP_PROTOCOLS)
> > def test_supported_upgrade_request(protocol_cls):
> > app = Response("Hello, world", media_type="text/plain")
> >
> > protocol = get_connected_protocol(app, protocol_cls, ws="wsproto")
> > protocol.data_received(UPGRADE_REQUEST)
> >
> > >   assert b"HTTP/1.1 426 " in protocol.transport.buffer
> > E   AssertionError: assert b'HTTP/1.1 426 ' in b'HTTP/1.1 400 
> > \r\nSec-WebSocket-Version: 13\r\ncontent-length: 0\r\n\r\n'
> > E+  where b'HTTP/1.1 400 \r\nSec-WebSocket-Version: 
> > 13\r\ncontent-length: 0\r\n\r\n' =  > 0x7f5dfb815af0>.buffer
> > E+where  = 
> >  > 0x7f5dfb815670>.transport

This is due to the version of uvicorn in the archive is not compatible
with wsproto 1.0.0, https://github.com/encode/uvicorn/issues/868;
that's fixed in https://github.com/encode/uvicorn/pull/892 which was
released in 0.14.0 and 0.15.0.

I've started upgrading the package in git to 0.15.0, but that requires
a newer version of httpx than the one in the archive and that requires
python-charset-normalizer, which is currently in NEW.

uvicorn unittests are also failing, apparently because a test HTTP
daemon on port 8000 is not running, i've opened
https://github.com/encode/uvicorn/discussions/1231 asking for help

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#960223: marked as done (taskd: Unsuitable for stable release)

[Debian Bug Tracking System]

Your message dated Tue, 2 Nov 2021 00:26:51 -0300
with message-id <20211102032651.sn2lyyg6duvodsg7@debian>
and subject line Re: taskd: Unsuitable for stable release
has caused the Debian Bug report #960223,
regarding taskd: Unsuitable for stable release
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.)


-- 
960223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: taskd
Severity: serious
Justification: Policy 3.3

taskd has not been uploaded for two releases, and development appears to
be dead upstream. I've long ceased to use it, and the install base
appears (per popcon) to be minimal.

Consequently, this is filed to have it removed from testing, and will
proceed to RM in future if the situation doesn't change.
--- End Message ---
--- Begin Message ---
On Sun, 10 May 2020 18:48:30 + Gordon Ball  wrote:
> Package: taskd
> Severity: serious
> Justification: Policy 3.3
> 
> taskd has not been uploaded for two releases, and development appears to
> be dead upstream. I've long ceased to use it, and the install base
> appears (per popcon) to be minimal.
>
> Consequently, this is filed to have it removed from testing, and will
> proceed to RM in future if the situation doesn't change.

Source: taskd
Source-Version: 1.1.0+dfsg-4
Done: Sergio Cipriano 

Recently, a new version was uploaded into unstable with changes that make taskd
suitable for release. There are still pending fixes, but I believe this bug can
now be closed.

I am currently working on reviving taskd (check #993864 for more details).

Also, after a while without any updates, development is gradually happening 
upstream.

--
Cheers,
Sergio Cipriano


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

Bug#996371: marked as done (ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)

[Debian Bug Tracking System]

Your message dated Tue, 02 Nov 2021 03:19:59 +
with message-id 
and subject line Bug#996371: fixed in ruby-roo 2.8.3-2
has caused the Debian Bug report #996371,
regarding ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:  
NoMethodError:
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.)


-- 
996371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-roo
Version: 2.8.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-roo was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>  NoMethodError:
>undefined method `encode' for URI:Module
>  # ./lib/roo/spreadsheet.rb:27:in `extension_for'
>  # ./lib/roo/spreadsheet.rb:8:in `open'
>  # ./spec/lib/roo/spreadsheet_spec.rb:39:in `block (5 levels) in  (required)>'
> 
> Finished in 4.28 seconds (files took 1.82 seconds to load)
> 239 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/lib/roo/csv_spec.rb:27 # Roo::CSV#parse with headers: true 
> doesn't blow up
> rspec ./spec/lib/roo/csv_spec.rb:41 # Roo::CSV#parse_with_clean_option with 
> clean: true doesn't blow up
> rspec ./spec/lib/roo/spreadsheet_spec.rb:37 # Roo::Spreadsheet.open for a url 
> that is csv treats the url as CSV
> 
> Coverage report generated for RSpec to /<>/coverage. 1395 / 1885 
> LOC (74.01%) covered.
> Stopped processing SimpleCov as a previous error not related to SimpleCov has 
> been detected
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-roo/ruby-roo_2.8.3-1+rebuild1633393685_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-roo
Source-Version: 2.8.3-2
Done: Unit 193 

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated ruby-roo 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: SHA384

Format: 1.8
Date: Mon, 01 Nov 2021 22:55:10 -0400
Source: ruby-roo
Architecture: source
Version: 2.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Unit 193 
Changed-By: Unit 193 
Closes: 996371
Changes:
 ruby-roo (2.8.3-2) unstable; urgency=medium
 .
   * d/p/ruby3.0_compatibility.patch:
 - Grab two patches from upstream to fix compatibility with Ruby 3.0.
   (Closes: #996371)
   * d/u/metadata: Generate.
   * d/control, d/copyright: Update my email address.
   * d/control:
 - Bump DH compat to 13.
 - Rely on ${ruby:Depends} rather than listing everything explicitly.
   * d/rules: Utilize --gem-install method.
   * d/watch: Bump version to 4.
   * Update Standards-Version to 4.6.0.
Checksums-Sha1:
 093349ca3963eba0daf0891c457f31e711424b54 1995 ruby-roo_2.8.3-2.dsc
 d3c93cef6fd83c9ac03b20c6400ccbcc5ed9363a 4387441 ruby-roo_2.8.3.orig.tar.gz
 cd8ff746ee68c540a5872151c9868a67efd039bb 3576 ruby-roo_2.8.3-2.debian.tar.xz
 3e4cd13e74e5197fdf16ce5a63f28befee44731b 9620 ruby-roo_2.8.3-2_amd64.buildinfo
Checksums-Sha256:
 53773b0ddcd329f4c274f1eac9aec0b332cd278c6f98d25bf6ace7db8e7f9f42 1995 
ruby-roo_2.8.3-2.dsc
 698d0600cc5bad8b9a4869a1bd79170d72a0f606c46784afac125da4291110f0 4387441 
ruby-roo_2.8.3.orig.tar.gz
 144fe4d5e882973394a66830d2427d1c55ecd33a906e2a6c12d9d90cb4571732 3576 
ruby-roo_2.8.3-2.debian.tar.xz
 1b3feb1d35e06f8d35cfb66cbf4d0df0697d52901f5b48439c226e4375bc763b 9620 

Bug#983229: proj transition has started

[Olly Betts]

On Tue, Oct 26, 2021 at 05:35:48AM +0200, Sebastiaan Couwenberg wrote:
> PROJ 8.2.0 is scheduled for release next week, just wait for that.

Oh, I see this has been uploaded.  I'll try to sort out updating the
survex package to use it.

Cheers,
Olly

Processed: properly close aom bugs

[Debian Bug Tracking System]

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

> fixed 997806 3.2.0-1
Bug #997806 {Done: Boyuan Yang } [src:aom] aom: possible ABI 
breakage; causes ffmpeg autopkgtests failures
Marked as fixed in versions aom/3.2.0-1.
> fixed 972467 3.2.0-1
Bug #972467 {Done: Boyuan Yang } [src:aom] aom: Please 
package new upstream stable release (2.0.0)
Marked as fixed in versions aom/3.2.0-1.
> fixed 988211 3.2.0-1
Bug #988211 {Done: Boyuan Yang } [src:aom] CVE-2021-30473
Marked as fixed in versions aom/3.2.0-1.
> fixed 982184 3.2.0-1
Bug #982184 {Done: Boyuan Yang } [src:aom] aom: reduce 
Build-Depends
Marked as fixed in versions aom/3.2.0-1.
> fixed 997983 3.2.0-1
Bug #997983 {Done: Boyuan Yang } [libaom-dev] Please upload 
version 3 from experimental to unstable
Ignoring request to alter fixed versions of bug #997983 to the same values 
previously set
> fixed 952564 3.2.0-1
Bug #952564 {Done: Boyuan Yang } [libaom0] please get the 
latest libaom v1.0.0-errata1-avif to archives, even if only to experimental.
There is no source info for the package 'libaom0' at version '3.2.0-1' with 
architecture ''
Unable to make a source version for version '3.2.0-1'
Marked as fixed in versions 3.2.0-1.
>
End of message, stopping processing here.

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

Bug#998212: easytag: overwrites tags containing UTF8 data with random rubbish

[Norbert Preining]

Hi

> What kind of files / tags did you process with easytag? If these files

that were mp3, not sure about what version of tags since they were gone
afterwards. At least they displayed fine in all music players I used.
But yes, I guess it is common here in Japan that id3v1 tags are coded in
UTF8 (or even ShiftJIS).

I still consider overwriting tags when there was an error during
preparation, irrespective of the correctness of the original tags,
a serious problem. easytag should *not* write broken tags.

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#997605: marked as done (pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 23:36:48 +
with message-id 
and subject line Bug#997605: fixed in pprofile 2.1.0-1
has caused the Debian Bug report #997605,
regarding pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.
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.)


-- 
997605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pprofile
Version: 2.0.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pprofile
> dpkg-buildpackage: info: source version 2.0.5-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Josue Ortega 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from pprofile-2.0.5/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in pprofile setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:8: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pprofile_2.0.5-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pprofile
Source-Version: 2.1.0-1
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated pprofile package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 17:11:59 -0600
Source: pprofile
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 997605
Changes:
 pprofile (2.1.0-1) unstable; urgency=medium
 .
   * New upstream release (2.1.0):
 + Refresn debian/patches. Removes obsolete command
   use_2to3. Closes: #997605
   * debian/watch: Update regex to use Github /tags endpoint.
   * Bump Standards-Version to 4.6.0. No changes required.
Checksums-Sha1:
 1c3830c283149a6117df82e01e2ac76c6199cb46 1930 pprofile_2.1.0-1.dsc
 c889c9a879e2c987afe36029bc2aac8f4207bac4 55534 pprofile_2.1.0.orig.tar.gz
 4fe4f55c40cd79afd5227108c74c13ccc284fce0 3788 pprofile_2.1.0-1.debian.tar.xz
 1204fe75554f63cb9d51bb92363ce15ff217dfbf 6389 pprofile_2.1.0-1_amd64.buildinfo
Checksums-Sha256:
 a7b51a472521be7b7bfab8aa736e34a930a5d760dd1bff33b90c23313f9f0bbf 1930 
pprofile_2.1.0-1.dsc
 6317954ddb9fca330e3c45766de6eae595b0e86071540e426832b2fd9764d276 55534 
pprofile_2.1.0.orig.tar.gz
 67dd945ca248f6d4330c1e128ada9602f9c4b21067bb917139528c503d830feb 3788 
pprofile_2.1.0-1.debian.tar.xz
 3ca881e8561fb1bc69b6e77bbb2a3f327d52cd88c617580acb2b475689cec6fc 6389 
pprofile_2.1.0-1_amd64.buildinfo
Files:
 3a358322a0c78c289eee08ad78bc5f46 1930 python optional pprofile_2.1.0-1.dsc
 9b71c7ff7ab9c6b63bc6c7af15aa1a42 55534 python optional 
pprofile_2.1.0.orig.tar.gz
 88c7256fa178cb931d771180b06a4624 3788 python optional 

Bug#995979: marked as done (pamix FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 23:04:39 +
with message-id 
and subject line Bug#995979: fixed in pamix 1.6~git20180112.ea4ab3b-4
has caused the Debian Bug report #995979,
regarding pamix FTBFS: error: format not a string literal and no format 
arguments [-Werror=format-security]
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.)


-- 
995979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pamix
Version: 1.6~git20180112.ea4ab3b-3
Severity: serious
Tags: ftbfs

pamix fails to build from source in unstable on amd64, because ncurses
added format string annotations to some functions. A non-parallel build
now ends as follows:

| [ 53%] Building CXX object CMakeFiles/pamix.dir/src/pamix_ui.cpp.o
| /usr/bin/c++ -DFEAT_UNICODE -I"/<>/include" -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT 
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o -MF 
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o.d -o 
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o -c "/<>/src/pamix_ui.cpp"
| /<>/src/pamix_ui.cpp: In member function ‘void 
pamix_ui::redrawAll()’:
| /<>/src/pamix_ui.cpp:106:52: error: format not a string literal 
and no format arguments [-Werror=format-security]
|   106 |   mvprintw(lineNumber++, 1, applicationName.c_str());
|   |^
| /<>/src/pamix_ui.cpp:124:64: error: format not a string literal 
and no format arguments [-Werror=format-security]
|   124 |   mvprintw(curY, curX + remainingChars + 1, displayName.c_str());
|   |^
| /<>/src/pamix_ui.cpp: In member function ‘void 
pamix_ui::drawHeader() const’:
| /<>/src/pamix_ui.cpp:187:22: warning: format ‘%d’ expects 
argument of type ‘int’, but argument 5 has type ‘std::map >::size_type’ {aka ‘long unsigned int’} [-Wformat=]
|   187 |  mvprintw(0, 1, "%d/%d", m_Entries->empty() ? 0 : m_SelectedEntry + 
1, m_Entries->size());
|   | ~^
 ~
|   |  |
|
|   |  int  
std::map >::size_type {aka 
long unsigned int}
|   | %ld
| cc1plus: some warnings being treated as errors
| make[3]: *** [CMakeFiles/pamix.dir/build.make:163: 
CMakeFiles/pamix.dir/src/pamix_ui.cpp.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:86: CMakeFiles/pamix.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:139: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
| make: *** [debian/rules:7: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: pamix
Source-Version: 1.6~git20180112.ea4ab3b-4
Done: Josue Ortega 

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated pamix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 16:41:22 -0600
Source: pamix
Architecture: source
Version: 1.6~git20180112.ea4ab3b-4
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Closes: 995979
Changes:
 pamix (1.6~git20180112.ea4ab3b-4) unstable; urgency=medium
 .
   * Add patch to fix FTBFS error due to missing format arguments passed to
 mvprintw. (Closes: #995979)
   * Update package to use debhelper-compat (= 13)
   * Bump Standards-Version to 4.6.0:
 + debian/compat: Document Rules-Requires-Root as no.
   * Bump 

Bug#998297: mu-editor: FTBFS: AssertionError: Expected 'SendScintilla' to be called once. Called 0 times.

[Andreas Beckmann]

Source: mu-editor
Version: 1.1.0~alpha2+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

mu-editor/experimental recently started to FTBFS:

=== FAILURES ===
_ test_tidy_code_valid_python __

@pytest.mark.skipif(sys.version_info < (3, 6), reason="Requires Python3.6")
def test_tidy_code_valid_python():
"""
Ensure the "good case" works as expected (the code is reformatted and Mu
shows a status message to confirm so).
"""
mock_view = mock.MagicMock()
mock_view.current_tab.text.return_value = "print('hello')"
ed = mu.logic.Editor(mock_view)
ed.show_status_message = mock.MagicMock()
ed.tidy_code()
tab = mock_view.current_tab
>   tab.SendScintilla.assert_called_once_with(tab.SCI_SETTEXT,
  b'print("hello")\n')

tests/test_logic.py:3474: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
args = (, 
b'print("hello")\n')
kwargs = {}, msg = "Expected 'SendScintilla' to be called once. Called 0 times."

def assert_called_once_with(self, /, *args, **kwargs):
"""assert that the mock was called exactly once and that that call was
with the specified arguments."""
if not self.call_count == 1:
msg = ("Expected '%s' to be called once. Called %s times.%s"
   % (self._mock_name or 'mock',
  self.call_count,
  self._calls_repr()))
>   raise AssertionError(msg)
E   AssertionError: Expected 'SendScintilla' to be called once. Called 
0 times.

/usr/lib/python3.9/unittest/mock.py:918: AssertionError
-- Captured log call ---
ERRORmu.logic:logic.py:1508 cannot import name 'PY36_VERSIONS' from 'black' 
(/usr/lib/python3/dist-packages/black/__init__.py)
=== warnings summary ===
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_with_attached_known_device_and_forced
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_forced_with_attached_device_as_not_windows
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_force_flash_user_specified_device_path
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_force_flash_empty_script
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_force_with_attached_device_as_windows
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_device_has_latest_firmware_encounters_serial_problem_windows
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_with_attached_device_has_latest_firmware_encounters_problem
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_device_has_latest_firmware_encounters_serial_problem_unix
.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py::test_flash_with_attached_device_has_latest_firmware
  
/build/mu-editor-1.1.0~alpha2+dfsg1/.pybuild/cpython3_3.9_mu-editor/build/mu/modes/microbit.py:256:
 DeprecationWarning: Function 'semver.parse' is deprecated. Deprecated since 
version 2.10.0.  This function will be removed in semver 3. Use the respective 
'semver.VersionInfo.parse' instead.
semver.parse(version_info['release'])

.pybuild/cpython3_3.9_mu-editor/build/tests/modes/test_microbit.py: 10 warnings
  
/build/mu-editor-1.1.0~alpha2+dfsg1/.pybuild/cpython3_3.9_mu-editor/build/mu/modes/microbit.py:272:
 DeprecationWarning: Function 'semver.compare' is deprecated. Deprecated since 
version 2.10.0.  This function will be removed in semver 3. Use the respective 
'semver.VersionInfo.compare' instead.
if semver.compare(board_version,

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 
FAILED tests/test_logic.py::test_tidy_code_valid_python - AssertionError: Exp...
== 1 failed, 820 passed, 19 warnings in 6.51s ==
E: pybuild pybuild:354: test: plugin distutils failed with: exit code=1: cd 
'/build/mu-editor-1.1.0~alpha2+dfsg1/.pybuild/cpython3_3.9_mu-editor/build'; 
python3.9 -m pytest --random-order
Traceback (most recent call last):
  File "/usr/bin/pybuild", line 352, in main
run(func, i, version, c)
  File "/usr/bin/pybuild", line 302, in run
result = func(context, args)
  File "/usr/share/dh-python/dhpython/build/base.py", line 282, in wrapped_func
raise Exception(msg)
Exception: exit code=1: cd 
'/build/mu-editor-1.1.0~alpha2+dfsg1/.pybuild/cpython3_3.9_mu-editor/build'; 
python3.9 -m pytest --random-order
rm -fr -- /tmp/dh-xdg-rundir-Uw9IX9A5
dh_auto_test: error: pybuild --test 

Bug#997163: marked as done (nudoku: FTBFS: main.c:546:89: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 22:19:14 +
with message-id 
and subject line Bug#997163: fixed in nudoku 2.1.0-0.1
has caused the Debian Bug report #997163,
regarding nudoku: FTBFS: main.c:546:89: error: format not a string literal and 
no format arguments [-Werror=format-security]
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.)


-- 
997163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997163
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nudoku
Version: 1.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"nudoku\" -DPACKAGE_TARNAME=\"nudoku\" 
> -DPACKAGE_VERSION=\"1.0.0\" -DPACKAGE_STRING=\"nudoku\ 1.0.0\" 
> -DPACKAGE_BUGREPORT=\"jub...@iodoru.org\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"nudoku\" -DVERSION=\"1.0.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 
> -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE__BOOL=1 
> -DHAVE_MALLOC=1 -DHAVE_ATEXIT=1 -DHAVE_STRDUP=1 -I.   -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.c
> main.c: In function ‘main’:
> main.c:546:89: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>   546 | 
> mvwprintw(status, 0, 6, t);
>   |   
>   ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:363: main.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/nudoku_1.0.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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nudoku
Source-Version: 2.1.0-0.1
Done: Martin 

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

Debian distribution maintenance software
pp.
Martin  (supplier of updated nudoku package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 20:33:46 +
Source: nudoku
Binary: nudoku nudoku-dbgsym
Architecture: source amd64
Version: 2.1.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Vetter 
Changed-By: Martin 
Description:
 nudoku - ncurses based sudoku games
Closes: 997163
Changes:
 nudoku (2.1.0-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * New upstream release
   * Update Vcs fields to salsa.debian.org
   * Bump debhelper version to 13
   * Change build dep from libncurses5-dev to libncurses-dev
   * Add R³=no
   * Add build dependency on pkg-config
   * Add upstream patch to fix build fail with ncurses 6.3 (Closes: #997163)
Checksums-Sha1:
 e1e4fefea548e5ee350452ab4f903b07bda2be22 1847 nudoku_2.1.0-0.1.dsc
 fd28945728bc47ec60f8e10efc6a150bb83f5ee2 31592 nudoku_2.1.0.orig.tar.gz
 15f55e7a703d6529d322cc31713b0e802857 2620 nudoku_2.1.0-0.1.debian.tar.xz
 d1db633c19a40073498847a2277f6ef56fc3e35a 16404 
nudoku-dbgsym_2.1.0-0.1_amd64.deb
 ebe98b9c941fbbfe77e7be15179d17bd58625b90 6160 nudoku_2.1.0-0.1_amd64.buildinfo
 d6075e26c5a2dd5bb467e479cd86bffe09caedd2 16368 nudoku_2.1.0-0.1_amd64.deb
Checksums-Sha256:
 0835007960c973627dd3b66f3fa6f199c906bebcc822eb1270bc6c4e3abd745f 1847 
nudoku_2.1.0-0.1.dsc
 eeff7f3adea5bfe7b88bf7683d68e9a597aabd1442d1621f21760c746400b924 31592 
nudoku_2.1.0.orig.tar.gz
 

Bug#997618: marked as done (python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 22:19:33 +
with message-id 
and subject line Bug#997618: fixed in python-jsmin 3.0.0-1
has caused the Debian Bug report #997618,
regarding python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is 
invalid.
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.)


-- 
997618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jsmin
Version: 2.2.2-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=pybuild --with python3 --verbose
>dh_auto_clean -O--buildsystem=pybuild -O--verbose
>   pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean 
> error in jsmin setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:4: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-jsmin_2.2.2-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-jsmin
Source-Version: 3.0.0-1
Done: gustavo panizzo 

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

Debian distribution maintenance software
pp.
gustavo panizzo  (supplier of updated python-jsmin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 01 Nov 2021 21:53:00 +
Source: python-jsmin
Architecture: source
Version: 3.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: gustavo panizzo 
Changed-By: gustavo panizzo 
Closes: 997618
Changes:
 python-jsmin (3.0.0-1) unstable; urgency=medium
 .
   * New upstream release
   * [95ab73] Import upstream release 3.0.0 (Closes: #997618)
   * [f0c691] Take a patch from upstream master to fix a failing test
   * [338813] Update the version of the watch file, no changes needed
   * [2bc233] Bump standards version to 4.6.0.1, no changes needed
   * [10ea0e] Set the debhelper compat level to 13
   * [3808da] Do not require root to build the package
Checksums-Sha1:
 095673537e3e6e1121cd39e84d118bf36ab95f31 1372 python-jsmin_3.0.0-1.dsc
 462339aaa6d41a8d8d430b7fa01fb9d3f1eb4dc0 11519 python-jsmin_3.0.0.orig.tar.gz
 e5a23899def32e32259d2ccad19ab5608222c456 3680 
python-jsmin_3.0.0-1.debian.tar.xz
 cb859c62c2afd4d12ee7ba28b7554e790b472dad 5744 
python-jsmin_3.0.0-1_amd64.buildinfo
Checksums-Sha256:
 4dc622c73a461839a7b39ee79466771a1c06acbf047f78947c875e916fddfb81 1372 
python-jsmin_3.0.0-1.dsc
 88fc1bd6033a47c5911dbcada7d279c7a8b7ad0841909590f6a742c20c4d2e08 11519 
python-jsmin_3.0.0.orig.tar.gz
 cbf1b05d23075de48bd7d2f7cf7ec05ce8e9082607869652c01040bfc40dbf2f 3680 
python-jsmin_3.0.0-1.debian.tar.xz
 ee98b8dcaf23605f540a588cd97958a4d30b98b9304c98d2ed290bf8514efb33 5744 
python-jsmin_3.0.0-1_amd64.buildinfo
Files:
 1247d3b86b1dcd9254fec80881cbcee9 1372 python optional python-jsmin_3.0.0-1.dsc
 a65df9e83d0b69fd2fafe15a017ac0fc 11519 python optional 
python-jsmin_3.0.0.orig.tar.gz
 2a66fa17151899fba3e510d7c363853e 3680 python optional 
python-jsmin_3.0.0-1.debian.tar.xz
 569a94b1b7a3878483e9d140e8537f3f 5744 python optional 
python-jsmin_3.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#998296: adios: autopktest failure

[Sebastian Ramacher]

Source: adios
Version: 1.13.1-29
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

autopkgtests fail with:
| Broken autopkgtest-satdep:amd64 Depends on libadios-mpi-dev:amd64 < none @un 
H >
|   Removing autopkgtest-satdep:amd64 because I can't find 
libadios-mpi-dev:amd64

See https://ci.debian.net/data/autopkgtest/testing/amd64/a/adios/16336328/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#997167: marked as done (ncdc: FTBFS: src/uit_dl.c:227:25: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 22:04:00 +
with message-id 
and subject line Bug#997167: fixed in ncdc 1.22.1-3
has caused the Debian Bug report #997167,
regarding ncdc: FTBFS: src/uit_dl.c:227:25: error: format not a string literal 
and no format arguments [-Werror=format-security]
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.)


-- 
997167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncdc
Version: 1.22.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.  -I./src -I./deps -I./deps/ylib -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/p11-kit-1  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o src/uit_hub.o 
> src/uit_hub.c
> In file included from src/uit_dl.c:28:
> src/uit_dl.h:266:3: warning: ‘GStaticMutex’ is deprecated: Use 'GMutex' 
> instead [-Wdeprecated-declarations]
>   266 |   GStaticMutex lock;
>   |   ^~~~
> In file included from /usr/include/glib-2.0/glib.h:112,
>  from src/ncdc.h:61,
>  from src/uit_dl.c:27:
> /usr/include/glib-2.0/glib/deprecated/gthread.h:133:9: note: declared here
>   133 | typedef struct
>   | ^~
> src/uit_dl.c: In function ‘t_draw’:
> src/uit_dl.c:227:25: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>   227 | mvprintw(bottom, 0, hash);
>   | ^~~~
> gcc -DHAVE_CONFIG_H -I.  -I./src -I./deps -I./deps/ylib -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/p11-kit-1  -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> src/uit_main.o src/uit_main.c
> src/uit_fl.c: In function ‘uit_fl_queue’:
> src/uit_fl.c:215:7: warning: ‘g_memdup’ is deprecated: Use 'g_memdup2' 
> instead [-Wdeprecated-declarations]
>   215 |   fl_load_async(fn, loadmatch, g_memdup(, 8));
>   |   ^
> In file included from /usr/include/glib-2.0/glib.h:82,
>  from src/ncdc.h:61,
>  from src/uit_fl.c:27:
> /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
>   257 | gpointer  g_memdup (gconstpointer mem,
>   |   ^~~~
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:711: src/uit_dl.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ncdc_1.22.1-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ncdc
Source-Version: 1.22.1-3
Done: Boris Pek 

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

Debian distribution maintenance software
pp.
Boris Pek  (supplier of updated ncdc 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, 02 Nov 2021 00:46:09 +0300
Source: ncdc
Architecture: source
Version: 1.22.1-3
Distribution: unstable
Urgency: medium
Maintainer: Boris Pek 
Changed-By: Boris Pek 
Closes: 997167
Changes:
 ncdc (1.22.1-3) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.6.0 (was 4.5.1): no changes required.
   * Add patch to fix build with -Werror=format-security compiler 

Bug#997136: marked as done (asterisk: FTBFS: configure: error: *** ANSI C header files not found.)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 22:03:29 +
with message-id 
and subject line Bug#997136: fixed in asterisk 1:16.16.1~dfsg-3
has caused the Debian Bug report #997136,
regarding asterisk: FTBFS: configure: error: *** ANSI C header files not found.
to be marked as done.

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

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


-- 
997136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk
Version: 1:16.16.1~dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> checking for working alloca.h... yes
> checking for alloca... yes
> checking for dirent.h that defines DIR... yes
> checking for library containing opendir... none required
> checking for egrep... (cached) /bin/grep -E
> configure: error: *** ANSI C header files not found.
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> It was created by asterisk configure trunk, which was
> generated by GNU Autoconf 2.71.  Invocation command line was
> 
>   $ ./configure 'CFLAGS=-fgnu89-inline -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
> 'LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' --host=x86_64-linux-gnu 
> --build=x86_64-linux-gnu --prefix=/usr '--mandir=${prefix}/share/man' 
> '--infodir=${prefix}/share/info' --disable-asteriskssl --with-gsm 
> --with-imap=system --without-pwlib --without-sdl
> 
> ## - ##
> ## Platform. ##
> ## - ##
> 
> hostname = ip-172-31-13-130
> uname -m = x86_64
> uname -r = 4.19.0-6-cloud-amd64
> uname -s = Linux
> uname -v = #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)
> 
> /usr/bin/uname -p = unknown
> /bin/uname -X = unknown
> 
> /bin/arch  = unknown
> /usr/bin/arch -k   = unknown
> /usr/convex/getsysinfo = unknown
> /usr/bin/hostinfo  = unknown
> /bin/machine   = unknown
> /usr/bin/oslevel   = unknown
> /bin/universe  = unknown
> 
> PATH: /usr/local/sbin/
> PATH: /usr/local/bin/
> PATH: /usr/sbin/
> PATH: /usr/bin/
> PATH: /sbin/
> PATH: /bin/
> PATH: /usr/games/
> PATH: /<>/debian/dummyprogs/
> 
> 
> ## --- ##
> ## Core tests. ##
> ## --- ##
> 
> configure:3957: looking for aux files: install-sh config.guess config.sub
> configure:3970:  trying ./
> configure:3981:   ./install-sh found
> configure:3999:   ./config.guess found
> configure:3999:   ./config.sub found
> configure:4119: checking build system type
> configure:4134: result: x86_64-pc-linux-gnu
> configure:4154: checking host system type
> configure:4168: result: x86_64-pc-linux-gnu
> configure:4231: checking for x86_64-linux-gnu-gcc
> configure:4252: found /usr/bin/x86_64-linux-gnu-gcc
> configure:4263: result: x86_64-linux-gnu-gcc
> configure:4343: checking for C compiler version
> configure:4352: x86_64-linux-gnu-gcc --version >&5
> x86_64-linux-gnu-gcc (Debian 11.2.0-10) 11.2.0
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> configure:4363: $? = 0
> configure:4352: x86_64-linux-gnu-gcc -v >&5
> Using built-in specs.
> COLLECT_GCC=x86_64-linux-gnu-gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
> OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
> OFFLOAD_TARGET_DEFAULT=1
> Target: x86_64-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Debian 11.2.0-10' 
> --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
> --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
> --with-gcc-major-version-only --program-suffix=-11 
> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
> --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> --with-default-libstdcxx-abi=new --enable-gnu-unique-object 
> --disable-vtable-verify --enable-plugin --enable-default-pie 
> --with-system-zlib --enable-libphobos-checking=release 
> --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
> --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
> --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
> 

Bug#998295: puma: 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips

[Sebastian Ramacher]

Source: puma
Version: 5.3.2-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

puma fails to build on amd64 and mips*el:
| Errors & Failures:
|
|   1) Failure:
| TestIntegrationSingle#test_hot_restart_does_not_drop_connections_threads 
[/<>/test/helpers/integration.rb:308]:
|   0 unexpected_response
|   3 refused
|   0 read timeout
|   0 reset
| 997 success
| 565 success after restart
|   1 restart count
| Expected no refused connections.
| Expected: 0
|   Actual: 3
|
| 401 runs, 1086 assertions, 1 failures, 0 errors, 6 skips

https://buildd.debian.org/status/fetch.php?pkg=puma=amd64=5.3.2-3%2Bb1=1635692756=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#998124: meson: gnome module missing install_dir fix for c_template

[Jussi Pakkanen]

On Mon, 1 Nov 2021 at 23:33, Joshua Peisach  wrote:

> Nemo (Cinnamon's file manager) is failing to build with this same "KeyError: 
> 'install_dir'" issue, and I feel like it is a 0.60 regression as previous 
> versions didn't fail.
>
> Hope this gets fixed soon.

This is already fixed upstream and will be in 0.60.1 which will be out soonish;

https://github.com/mesonbuild/meson/pull/9484

Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma

[stefaca]

I can confirm this. Upgrade of KDE on testing is totally broken at the moment. 

On Sat, 23 Oct 2021 15:57:47 +0200 Chris Nospam  wrote:
> KDE/Plasma (package dependencies) are currently completely broken under 
testing. Is there currently a chance to (somehow simply) block the partial 
transition of plasma 5.23 to testing (so that not related package updates are 
easy)? Selectively upgrading single packages with dependencies one after the 
other from the mass provided in testing is rather cumbersome.
> 
> Currently I get the following (sorry for the german locale):
> 
> root@xxx:~# apt-get dist-upgrade
> Paketlisten werden gelesen… Fertig
> Abhängigkeitsbaum wird aufgebaut… Fertig
> Statusinformationen werden eingelesen… Fertig
> Paketaktualisierung (Upgrade) wird berechnet… Fertig
> Die folgenden NEUEN Pakete werden installiert:
>   libkdecorations2private9
> Die folgenden Pakete werden aktualisiert (Upgrade):
>   bluedevil breeze breeze-cursor-theme breeze-gtk-theme drkonqi
>   kactivitymanagerd kde-config-gtk-style kde-config-sddm kde-config-updates
>   kde-style-breeze kgamma5 kinfocenter kmenuedit kscreen ksshaskpass
>   kwayland-integration kwin-style-breeze kwrited libkdecorations2-5v5
>   libkf5screen-bin libkf5screen7 libpam-kwallet-common libpam-kwallet5 milou
>   oxygen-sounds plasma-discover plasma-discover-common plasma-disks
>   plasma-integration plasma-pa polkit-kde-agent-1
> 31 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
> Es müssen 96,2 MB an Archiven heruntergeladen werden.
> Nach dieser Operation werden 47,1 MB Plattenplatz zusätzlich benutzt.
> Möchten Sie fortfahren? [J/n] n
> Abbruch.
> 
> All packages shown above are from version 4:5.23.0 whereas the others would 
stay on 4:5.21.x. Unfortunately, it is not sufficient to set 
libkdecorations2-5v5 on hold, as it would remove plasma-desktop:
> 
> root@xxx:~# apt-mark hold libkdecorations2-5v5
> libkdecorations2-5v5 auf Halten gesetzt.
> root@xxx:~# apt-get dist-upgrade
> Paketlisten werden gelesen… Fertig
> Abhängigkeitsbaum wird aufgebaut… Fertig
> Statusinformationen werden eingelesen… Fertig
> Paketaktualisierung (Upgrade) wird berechnet… Fertig
> Die folgenden Pakete wurden automatisch installiert und werden nicht mehr 
benötigt:
>   accountsservice apt-config-icons-hidpi apt-config-icons-large
>   apt-config-icons-large-hidpi bluedevil bluez bluez-obexd breeze-gtk-theme
>   bup bup-doc gtk2-engines-pixbuf ibus-data ieee-data kde-config-gtk-style
>   kde-config-sddm kde-config-updates kgamma5 khotkeys khotkeys-data
>   kinfocenter kmenuedit kscreen kup-backup kwrited libaccountsservice0
>   libibus-1.0-5 libkpmcore11 libqt5designer5 libqt5help5 libscim8v5
>   libxcb-record0 oxygen-sounds par2 partitionmanager plasma-desktop-data
>   plasma-discover plasma-discover-common plasma-disks python3-fuse
>   python3-pylibacl python3-pyqt5 python3-pyqt5.sip python3-pyxattr
>   python3-software-properties python3-tornado qml-module-org-kde-activities
>   qml-module-org-kde-kcm qml-module-org-kde-kitemmodels smartmontools
>   software-properties-common software-properties-kde systemsettings
>   xsettings-kde
> Verwenden Sie »apt autoremove«, um sie zu entfernen.
> Die folgenden Pakete werden ENTFERNT:
>   kde-plasma-desktop plasma-desktop
> Die folgenden Pakete sind zurückgehalten worden:
>   breeze breeze-cursor-theme kde-config-gtk-style kde-style-breeze
>   kwin-style-breeze libkdecorations2-5v5 plasma-integration
> Die folgenden Pakete werden aktualisiert (Upgrade):
>   bluedevil breeze-gtk-theme drkonqi kactivitymanagerd kde-config-sddm
>   kde-config-updates kgamma5 kinfocenter kmenuedit kscreen ksshaskpass
>   kwayland-integration kwrited libkf5screen-bin libkf5screen7
>   libpam-kwallet-common libpam-kwallet5 milou oxygen-sounds plasma-discover
>   plasma-discover-common plasma-disks plasma-pa polkit-kde-agent-1

Processed: Re: meson: gnome module missing install_dir fix for c_template

[Debian Bug Tracking System]

Processing control commands:

> tags 998124 + confirmed
Bug #998124 [meson] meson: gnome module missing install_dir fix for c_template
Added tag(s) confirmed.

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

Bug#998238: marked as done (syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 21:19:18 +
with message-id 
and subject line Bug#998238: fixed in syncany 0.4.9~alpha-4
has caused the Debian Bug report #998238,
regarding syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.
to be marked as done.

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

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


-- 
998238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syncany
Version: 0.4.9~alpha-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

syncany recently started to FTBFS:

:syncany-lib:debianMavenPom (Thread[Task worker for ':',5,main]) started.
:syncany-lib:debianMavenPom
Putting task artifact state for task ':syncany-lib:debianMavenPom' into context 
took 0.0 secs.
Up-to-date check for task ':syncany-lib:debianMavenPom' took 0.0 secs. It is 
not up-to-date because:
  No history is available.
Passing through org.junit:junit-bom:jar:debian
Replacing org.hsqldb:hsqldb:jar:2.3.1  ->  org.hsqldb:hsqldb:jar:debian
Replacing javax.xml.bind:jaxb-api:jar:2.3.1  ->  
javax.xml.bind:jaxb-api:jar:debian
Passing through javax.xml.bind:jaxb-api-parent:jar:debian
Passing through javax.activation:javax.activation-api:jar:debian
javax.activation:javax.activation-api:debian is relocated to 
com.sun.activation:javax.activation:debian. Please update your dependencies.
Passing through com.sun.activation:javax.activation:jar:debian
Passing through com.sun.activation:all:jar:debian
:syncany-util:compileJava FAILED
:syncany-util:compileJava (Thread[Daemon worker,5,main]) completed. Took 0.248 
secs.
Generating pom file 
/build/syncany-0.4.9~alpha/syncany-lib/build/debian/syncany-lib.pom
:syncany-lib:debianMavenPom (Thread[Task worker for ':',5,main]) completed. 
Took 0.095 secs.
:syncany-cli:processResources (Thread[Task worker for ':' Thread 2,5,main]) 
completed. Took 0.507 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':syncany-util:compileClasspath'.
> Could not resolve commons-io:commons-io:2.4.
  Required by:
  project :syncany-util
   > Could not resolve commons-io:commons-io:2.4.
  > Could not parse POM 
/usr/share/maven-repo/commons-io/commons-io/debian/commons-io-debian.pom
 > Could not resolve org.junit:junit-bom:debian.
> No cached version of org.junit:junit-bom:debian available for 
offline mode.
> No cached version of org.junit:junit-bom:debian available for 
offline mode.
   > No cached version of commons-io:commons-io:2.4 available for offline mode.
   > No cached version of commons-io:commons-io:2.4 available for offline mode.

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':syncany-util:compileClasspath'.


Andreas


syncany_0.4.9~alpha-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: syncany
Source-Version: 0.4.9~alpha-4
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated syncany package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 12:55:02 -0700
Source: syncany
Architecture: source
Version: 0.4.9~alpha-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 998238
Changes:
 syncany (0.4.9~alpha-4) experimental; urgency=medium
 .
   * Team upload.
   * Add build-dep on junit5 (Closes: #998238)
   * Use debhelper-compat 13
 - Disable tests; system-rules dependency not available in Debian
   * Set Rules-Requires-Root: no in debian/control
   * Update Vcs URLs to point to Salsa
   * Bump Standards-Version to 4.6.0
 - Remove get-orig-source 

Processed: severity of 998285 is important

[Debian Bug Tracking System]

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

> severity 998285 important
Bug #998285 [src:libgig] libgig: fails to clean after build
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#998294: src:vulkan-validationlayers: fails to migrate to testing for too long: FTBFS on mips*el

[Paul Gevers]

Source: vulkan-validationlayers
Version: 1.2.162.0-1
Severity: serious
X-Debbugs-CC: d...@duckcorp.org
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:vulkan-validationlayers has been trying to
migrate for 61 days [2]. Hence, I am filing this bug. It turns out that
the package FTBFS on mips*el since the upload of 1.2.182.0-1.

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 tagged this bug to only affect sid and bookworm, 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=vulkan-validationlayers




OpenPGP_signature
Description: OpenPGP digital signature

Processed: ruby-batch-loader has been autoremoved, so ruby-graphql can migrate

[Debian Bug Tracking System]

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

> reassign 995358 src:ruby-batch-loader 2.0.1+dfsg-2
Bug #995358 [src:ruby-graphql, src:ruby-batch-loader] ruby-graphql breaks 
ruby-batch-loader autopkgtest: uninitialized constant 
GraphQL::StaticValidation::Validator::Timeout
Bug reassigned from package 'src:ruby-graphql, src:ruby-batch-loader' to 
'src:ruby-batch-loader'.
No longer marked as found in versions ruby-batch-loader/2.0.1+dfsg-2 and 
ruby-graphql/1.11.8-2.
Ignoring request to alter fixed versions of bug #995358 to the same values 
previously set
Bug #995358 [src:ruby-batch-loader] ruby-graphql breaks ruby-batch-loader 
autopkgtest: uninitialized constant 
GraphQL::StaticValidation::Validator::Timeout
Marked as found in versions ruby-batch-loader/2.0.1+dfsg-2.
> thanks
Stopping processing here.

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

Bug#996731: marked as done (src:golang-github-go-macaron-i18n: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 21:04:23 +
with message-id 
and subject line Bug#996731: fixed in golang-github-go-macaron-i18n 
0.0~git20160612.0.ef57533-8.1
has caused the Debian Bug report #996731,
regarding src:golang-github-go-macaron-i18n: fails to migrate to testing for 
too long: uploader built arch:all binaries
to be marked as done.

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

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


-- 
996731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-go-macaron-i18n
Version: 0.0~git20160612.0.ef57533-7
Severity: serious
Control: close -1 0.0~git20160612.0.ef57533-8
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:golang-github-go-macaron-i18n 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 bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-go-macaron-i18n
Source-Version: 0.0~git20160612.0.ef57533-8.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated 
golang-github-go-macaron-i18n 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: Sun, 17 Oct 2021 21:45:29 +0200
Source: golang-github-go-macaron-i18n
Architecture: source
Version: 0.0~git20160612.0.ef57533-8.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Paul Gevers 
Closes: 996731
Changes:
 golang-github-go-macaron-i18n (0.0~git20160612.0.ef57533-8.1) unstable; 
urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #996731)
Checksums-Sha1:
 aae560c20d015455da67152b3d2de79b294e85e2 2281 
golang-github-go-macaron-i18n_0.0~git20160612.0.ef57533-8.1.dsc
 f7d98312a7e540d050e36f7d5f185c60280601fa 2760 
golang-github-go-macaron-i18n_0.0~git20160612.0.ef57533-8.1.debian.tar.xz
Checksums-Sha256:
 b46d8eddade6cc698a17e118e2fcc9d6610a473bdafc9f255de230076d494f0e 2281 
golang-github-go-macaron-i18n_0.0~git20160612.0.ef57533-8.1.dsc
 e177b28367a0be81a712fe8a9a11289d2442c603af2eccb8adc2e482add07174 2760 
golang-github-go-macaron-i18n_0.0~git20160612.0.ef57533-8.1.debian.tar.xz
Files:
 4e76bbefad9ba2d8c33cb49fd4adf6a7 2281 devel extra 
golang-github-go-macaron-i18n_0.0~git20160612.0.ef57533-8.1.dsc
 

Processed: src:phosh: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.13.1-1
Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long
Marked as fixed in versions phosh/0.13.1-1.
Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long
Marked Bug as done

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

Bug#998293: src:phosh: fails to migrate to testing for too long

[Paul Gevers]

Source: phosh
Version: 0.8.0-1
Severity: serious
Control: close -1 0.13.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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

I checked the output of britney [3], it says this:
trying: phosh
skipped: phosh (0, 1, 128)
got: 26+0: a-1:a-23:a-0:a-0:i-0:m-0:m-1:p-0:s-1
* mipsel: phosh-phone

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 bookworm, 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=phosh
[3] https://release.debian.org/britney/update_output.txt



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998285: libgig: fails to clean after build

[Sebastian Ramacher]

Control: tags -1 important

On 2021-11-01 20:58:14 +0100, Andreas Beckmann wrote:
> Source: libgig
> Version: 4.3.0~ds1-1
> Severity: serious
> 
> Hi,
> 
> libgig fails to build twice in a row since it cannot clean up after a
> successful build:
> 
>dh_clean
> rm: cannot remove './doc/html': Is a directory
> dh_clean: error: rm -f -- debian/libgig-dev.substvars 
> debian/libgig10.substvars debian/libakai0.substvars debian/gigtools.substvars 
> debian/libgig-doc.substvars ./doc/html debian/files returned exit code 1
> make: *** [debian/rules:6: clean] Error 25
> 
> 
> This looks like you want to have 'doc/html/' (note the trailing slash)
> in debian/clean instead.

Such bugs have always been important at most.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#996723: marked as done (src:python-pluggy: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 20:36:29 +
with message-id 
and subject line Bug#996723: fixed in python-pluggy 0.13.0-7.1
has caused the Debian Bug report #996723,
regarding src:python-pluggy: fails to migrate to testing for too long: uploader 
built arch:all binaries
to be marked as done.

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

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


-- 
996723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pluggy
Version: 0.13.0-6
Severity: serious
Control: close -1 0.13.0-7
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:python-pluggy 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 bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pluggy
Source-Version: 0.13.0-7.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated python-pluggy 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: Sun, 17 Oct 2021 21:01:40 +0200
Source: python-pluggy
Architecture: source
Version: 0.13.0-7.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Paul Gevers 
Closes: 996723
Changes:
 python-pluggy (0.13.0-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #996723)
Checksums-Sha1:
 b76cfc62ba8d91b820be9a047904eb9268de8c83 1862 python-pluggy_0.13.0-7.1.dsc
 b4e25d1a079016aba8d75b887f1c7b322191fc4f 3136 
python-pluggy_0.13.0-7.1.debian.tar.xz
Checksums-Sha256:
 0a67c713697925a75d215f1dea448637f0a3411538c763fa55b74270de9dc696 1862 
python-pluggy_0.13.0-7.1.dsc
 e9fada6c2009f9261c7a43d9f669253ff44c9dce88b07f85915a878b27e037c4 3136 
python-pluggy_0.13.0-7.1.debian.tar.xz
Files:
 e7285c25e22d296b86eff4888661bf16 1862 python optional 
python-pluggy_0.13.0-7.1.dsc
 8c03fbc7035f12718205d33e927aa02b 3136 python optional 
python-pluggy_0.13.0-7.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFscyoACgkQnFyZ6wW9
dQqOwwf/RbiunocQ9D+dVAEsCWdFArDU6o9a2qygfiRaAl8zC3SS1jw25VxOPqQa
GBXLB8xBEt7lyXZimSkTVuBbtEGwt5JcinIpFHtzHGeKUcYJm6iWxWyPkDI05V1n
pi/8GcY6D/A8fSe4KFGxa8Q7+7+ilfXzEb79U6oCiNSlnNKT72rhIJG9QHP9evA9
M9IRy/KkN6p5SgiOCoyHTFzimfSVT2YPgX5JD34fzO5+biiGFz9Og7Q/3/avJuXV

Bug#996721: marked as done (src:pyzbar: fails to migrate to testing for too long: uploader build arch:all binaries)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 20:36:34 +
with message-id 
and subject line Bug#996721: fixed in pyzbar 0.1.8-3.1
has caused the Debian Bug report #996721,
regarding src:pyzbar: fails to migrate to testing for too long: uploader build 
arch:all binaries
to be marked as done.

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

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


-- 
996721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyzbar
Version: 0.1.8-2
Severity: serious
Control: close -1 0.1.8-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:pyzbar 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 bookworm, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyzbar
Source-Version: 0.1.8-3.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated pyzbar 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: Sun, 17 Oct 2021 20:58:04 +0200
Source: pyzbar
Architecture: source
Version: 0.1.8-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Paul Gevers 
Closes: 996721
Changes:
 pyzbar (0.1.8-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #996721)
Checksums-Sha1:
 500cb3151f6af917c27768525128597e7d4a10ed 1935 pyzbar_0.1.8-3.1.dsc
 8545b0b71770de9ce0b7a288600225b7280ce048 3040 pyzbar_0.1.8-3.1.debian.tar.xz
Checksums-Sha256:
 3438d726f6d1f04cd868ec9cdda9460fa46e70e5a57eb7417fba1b5cbab2d053 1935 
pyzbar_0.1.8-3.1.dsc
 31039a8b7e537dd9071d6d44c0408d350a083e7e0e951c68265da79e5257a9ce 3040 
pyzbar_0.1.8-3.1.debian.tar.xz
Files:
 601a8dc496fdd65a83e770b56711d238 1935 python optional pyzbar_0.1.8-3.1.dsc
 9adab49d0ed43603834870c8aa1e3628 3040 python optional 
pyzbar_0.1.8-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFscoEACgkQnFyZ6wW9
dQruCgf/W9nh4mdssCu2kEO0MiFEmX6a5BUuYDQFiWS1rKTNFPpsXibU0k3Hxi1u
KyHeErW/iFHW3PtPM/KIejOPJyRuMO1z1ht8apKRfNqweuTylyKRBSvUR9IE8Io1
Kk76SBP/4Ld93BVr/R2evGo4742jIzp5Z7TwzYXW8H4154wPPbnMIpl8Zhew+3kF
NXWdDjSUK9Oor8ubU49/U41OyNbXHGGSURcYr5s9VobAAF3nmguhwwJXa3eEobTK
SAO+T7Nu6l7gjlx11IQsobPB5fFWwe5ZGwBI6nPx9V1xHFiLilFfppAG+vAropAR
8SL/PiyUejbaYAm/es2fh04vXnJdGQ==
=n/c9
-END PGP SIGNATURE End 

Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array

[Jerome BENOIT]

On Mon, 1 Nov 2021 20:49:58 +0100 Paul Gevers  wrote:
Hello Paul,


Is this run on all cores? Our armhf worker has 160 cores, so you may be
running into limits you didn't expect.


This would be a surprising bug, indeed.
I will have a closer look. But I think I have ultimately
to contact the upstream author.

Otherwise, is there a way to limit the number of cores to use
through an environment variable (or something along this way) ?


Cheers,
Jerom




--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



OpenPGP_signature
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> found 982794 78.14.0esr-1+b1
Bug #982794 [firefox-esr] firefox-esr/armhf: fails on non-NEON systems
Marked as found in versions firefox-esr/78.14.0esr-1.
>
End of message, stopping processing here.

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

Bug#998290: gnunet: fails to install: gnunet.postinst: 91: tempfile: not found

[Andreas Beckmann]

Package: gnunet
Version: 0.14.0-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up gnunet (0.14.0-6) ...
  Creating new GNUnet group gnunet: done.
  Creating new GNUnet user gnunet: done.
  Creating new secured GNUnet group gnunetdns: done.
  Updating files and directories permissions: done.
  Writing new configuration file:/var/lib/dpkg/info/gnunet.postinst: 91: 
tempfile: not found
  dpkg: error processing package gnunet (--configure):
   installed gnunet package post-installation script subprocess returned error 
exit status 127
  Processing triggers for libc-bin (2.32-4) ...
  Errors were encountered while processing:
   gnunet


cheers,

Andreas


gnunet_0.14.0-6.log.gz
Description: application/gzip

Bug#998288: node-clipanion: FTBFS: Cannot find type definition file for 'yup'.

[Andreas Beckmann]

Package: node-clipanion
Version: 2.6.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-clipanion FTBFS in a minimal chroot:

   dh_auto_build --buildsystem=nodejs
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ rollup -c

./sources/advanced/index.ts → lib, lib...
(!) Plugin typescript: @rollup/plugin-typescript TS2688: Cannot find type 
definition file for 'yup'.
  The file is in the program because:
Entry point of type library 'yup' specified in compilerOptions
created lib, lib in 1.6s
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/clipanion
/bin/sh -ex debian/tests/pkg-js/test
+ export FORCE_COLOR=1
+ mocha --require ts-node/register --extension ts tests

TSError: ⨯ Unable to compile TypeScript:
sources/advanced/Command.ts(440,21): error TS2571: Object is of type 'unknown'.
sources/advanced/Command.ts(441,21): error TS2571: Object is of type 'unknown'.

at createTSError (/usr/share/nodejs/ts-node/src/index.ts:513:12)
at reportTSError (/usr/share/nodejs/ts-node/src/index.ts:517:19)
at getOutput (/usr/share/nodejs/ts-node/src/index.ts:752:36)
at Object.compile (/usr/share/nodejs/ts-node/src/index.ts:968:32)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1056:42)
at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1059:12)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. 
(/build/node-clipanion-2.6.2/sources/advanced/index.ts:1:1)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1056:23)
at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1059:12)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. 
(/build/node-clipanion-2.6.2/tests/advanced.test.ts:6:1)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Module.m._compile (/usr/share/nodejs/ts-node/src/index.ts:1056:23)
at Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Object.require.extensions. [as .ts] 
(/usr/share/nodejs/ts-node/src/index.ts:1059:12)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.exports.requireOrImport 
(/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:56:20)
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:8: binary] Error 25


Andreas


node-clipanion_2.6.2-1.log.gz
Description: application/gzip

Bug#998287: r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3

[Paul Gevers]

Source: r-cran-pdftools
Version: 3.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

Your package r-cran-pdftools has an autopkgtest, great. However, it
fails. Can you please investigate the situation and fix it? I copied
some of the output at the bottom of this report.

The release team has announced [1] that failing autopkgtest are now
considered RC in testing.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-pdftools/16361110/log.gz

autopkgtest [17:58:47]: test run-unit-test: [---
BEGIN TEST poppler.R

R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(pdftools)
Using poppler version 20.09.0
>
BEGIN TEST testthat.R

R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.

> library(testthat)
> library(pdftools)
Using poppler version 20.09.0
>
> test_check("pdftools")
══ Skipped tests
═══
• On CRAN (1)

══ Failed tests

── Failure (test-chinese.R:7:3): reading Chinese text
──
`text` does not match "風險因素".
Actual value: "
T\+2\\n\\n\\n\\n17,300,000\\n\\n\\n\\n299,900\\n\\n\\n\\n\\n

36\.8%\\n34\.9%\\n4,300,000
  6,900,000 7,100,000\\n300,000\\n\\n\\n
  3\.7%   1\.5%   3\.4%0\.1%\\n\\n\\n\\n\\n
   80%\\n  10%
80%\\n\\n\\n\\n\\n   – 31 –\\n"
Backtrace:
█
 1. └─testthat::expect_match(text, "風險因素") test-chinese.R:7:2
 2.   └─testthat:::expect_match_(...)
── Failure (test-chinese.R:11:3): reading Chinese text
─
nrow(fonts) not equal to 3.
1/1 mismatches
[1] 1 - 3 == -2
── Failure (test-chinese.R:13:3): reading Chinese text
─
fonts\$name\[2\] does not match "MSung".
Actual value: ""
Backtrace:
█
 1. └─testthat::expect_match(fonts$name[2], "MSung") test-chinese.R:13:2
 2.   └─testthat:::expect_match_(...)
── Failure (test-chinese.R:14:3): reading Chinese text
─
fonts\$name\[3\] does not match "MHei".
Actual value: ""
Backtrace:
█
 1. └─testthat::expect_match(fonts$name[3], "MHei") test-chinese.R:14:2
 2.   └─testthat:::expect_match_(...)

[ FAIL 4 | WARN 0 | SKIP 1 | PASS 20 ]
Error: Test failures
Execution halted
autopkgtest [17:58:49]: test run-unit-test: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998286: r-cran-psych: autopkgtest regression since mid October 2021

[Paul Gevers]

Source: r-cran-psych
Version: 2.1.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
X-Debbugs-CC: debian...@lists.debian.org

Dear maintainer(s),

Your package has an autopkgtest, great! However, since somewhere between
20 October and 1 November 2021 it started to fail [1] in testing. Can
you fix the situation?

Paul

[1] https://ci.debian.net/packages/r/r-cran-psych/

autopkgtest [01:28:04]: test vignette: [---
BEGIN VIGNETTE vignettes/intro.Rnw
Warning in log((1 - cc2)) : NaNs produced
Output file:  intro.tex
BEGIN VIGNETTE vignettes/scoring.Rnw
Error in loadNamespace(key[1]) : there is no package called 'knitr'
Calls:  ... loadNamespace -> withRestarts -> withOneRestart
-> doWithOneRestart
Execution halted
autopkgtest [01:28:08]: test vignette: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#998285: libgig: fails to clean after build

[Andreas Beckmann]

Source: libgig
Version: 4.3.0~ds1-1
Severity: serious

Hi,

libgig fails to build twice in a row since it cannot clean up after a
successful build:

   dh_clean
rm: cannot remove './doc/html': Is a directory
dh_clean: error: rm -f -- debian/libgig-dev.substvars debian/libgig10.substvars 
debian/libakai0.substvars debian/gigtools.substvars debian/libgig-doc.substvars 
./doc/html debian/files returned exit code 1
make: *** [debian/rules:6: clean] Error 25


This looks like you want to have 'doc/html/' (note the trailing slash)
in debian/clean instead.


Andreas


libgig_4.3.0~ds1-1_twice.log.gz
Description: application/gzip

Bug#998156: contains non-DFSG-free files

[Henry Cejtin]

Your right, but I think (not on the basis of real knowledge) that
ml-nlffigen isn't used in either the compilation
of the MLton compiler, nor by the MLton compiler in compiling user
code.  I thought that it was
for a MLton compiler user to use, and had been tweaked so that the
output was usable by MLton.

I certainly could be wrong about this.

Bug#995021: osmnx: autopkgtest regression on armhf: iteration over a 0-d array

[Paul Gevers]

Hi Jerome,

On 24-09-2021 22:23, Paul Gevers wrote:
> The above exception was the direct cause of the following exception:
> 
> def test_elevation():
> 
> G = ox.graph_from_address(address=address, dist=500,
> dist_type="bbox", network_type="bike")
> rasters = list(Path("tests/input_data").glob("elevation*.tif"))
> 
> # add node elevations from a single raster file (some nodes will
> be null)
> G = ox.elevation.add_node_elevations_raster(G, rasters[0], cpus=1)

 ^^^
Suddenly strikes me, compared to the next failing line...

> # add node elevations from multiple raster files
>>   G = ox.elevation.add_node_elevations_raster(G, rasters)

Is this run on all cores? Our armhf worker has 160 cores, so you may be
running into limits you didn't expect.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#937945: Removal of python-neuroshare (Was: python-neuroshare: Python2 removal in sid/bullseye)

[Andreas Tille]

Am Mon, Nov 01, 2021 at 08:28:50PM +0100 schrieb Moritz Mühlenhoff:
> Am Sun, Feb 09, 2020 at 01:18:27PM +0100 schrieb Andreas Tille:
> > Hi,
> > 
> > I've taken over this package into Debian Med team to
> > 
> >https://salsa.debian.org/med-team/python-neuroshare
> > 
> > It needs some remaining work to port for Python3 which I
> > can not do right now.  Any help is welcome.
> 
> What's the status? https://github.com/G-Node/python-neuroshare
> hasn't seen any commits since five years, should it be removed?

The people listed as Uploaders should have the last say.

Kind regards

  Andreas. 

-- 
http://fam-tille.de

Bug#998281: uhd: FTBFS during binary-indep only build

[Andreas Beckmann]

Source: uhd
Version: 4.1.0.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

uhd/experimental FTBFS when building only the arch-all packages as done
on the buildd:
https://buildd.debian.org/status/fetch.php?pkg=uhd=all=4.1.0.4-1=1634959755=0

 fakeroot debian/rules binary-indep
dh binary-indep --sourcedirectory=host --with python3 --with numpy3 
--buildsystem=cmake+ninja
   dh_testroot -i -O--sourcedirectory=host -O--buildsystem=cmake\+ninja
   dh_prep -i -O--sourcedirectory=host -O--buildsystem=cmake\+ninja
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
cp debian/uhd-host.limits debian/uhd-host/etc/security/limits.d/uhd.conf
cp: cannot create regular file 
'debian/uhd-host/etc/security/limits.d/uhd.conf': No such file or directory
make[1]: *** [debian/rules:33: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:17: binary-indep] Error 2

You probably need to split the override_dh_auto_install target into
separate override_dh_auto_install-arch and
override_dh_auto_install-indep targets.


Andreas

Bug#937945: python-neuroshare: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

Am Sun, Feb 09, 2020 at 01:18:27PM +0100 schrieb Andreas Tille:
> Hi,
> 
> I've taken over this package into Debian Med team to
> 
>https://salsa.debian.org/med-team/python-neuroshare
> 
> It needs some remaining work to port for Python3 which I
> can not do right now.  Any help is welcome.

What's the status? https://github.com/G-Node/python-neuroshare
hasn't seen any commits since five years, should it be removed?

Cheers,
 Moritz

Bug#937194: opencaster: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

Am Fri, Jan 29, 2021 at 09:56:46PM + schrieb Thorsten Alteholz:
> Hi Moritz,
> 
> On Fri, 29 Jan 2021, Moritz Mühlenhoff wrote:
> > opencaster seems dead upstream, should it be removed or are
> > you planning to port it to Python 3 yourself?
> 
> I don't plan to do the porting myself, so I think at the moment it should be
> better removed.

Ack, now filed an RM bug.

Cheers,
Moritz

Bug#998261: marked as done (jsbundle-web-interfaces: autopkgtest regression: node: command not found)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 19:18:30 +
with message-id 
and subject line Bug#998261: fixed in jsbundle-web-interfaces 
1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2
has caused the Debian Bug report #998261,
regarding jsbundle-web-interfaces: autopkgtest regression: node: command not 
found
to be marked as done.

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

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


-- 
998261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jsbundle-web-interfaces
Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of jsbundle-web-interfaces the autopkgtest of
jsbundle-web-interfaces fails in testing when that autopkgtest is run
with the binary packages of jsbundle-web-interfaces from unstable. It
passes when run with only packages from testing. In tabular form:

passfail
jsbundle-web-interfaces from testing
1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1
all others  from testingfrom testing

I copied some of the output at the bottom of this report. It seems that
when you dropped the (Build-)Depends, you forgot it was needed for the test.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=jsbundle-web-interfaces

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jsbundle-web-interfaces/16336344/log.gz

bash: line 1: node: command not found
autopkgtest [15:09:56]: test command1




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: jsbundle-web-interfaces
Source-Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated jsbundle-web-interfaces 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 20:07:16 +0100
Source: jsbundle-web-interfaces
Architecture: source
Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 998261
Changes:
 jsbundle-web-interfaces (1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2) unstable; 
urgency=medium
 .
   * fix revert to build-depend on nodejs (used during build after all);
 closes: bug#998261, thanks to Paul Gevers
Checksums-Sha1:
 5678990bb7d024b1b4eec621276c19151ddd275b 3741 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.dsc
 3f3a1d99858304a804c8d45510d9fd88a7be1cd2 17004 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.debian.tar.xz
 68c4600ca30b4532df8724ed9aa4477c27e7aa0d 13246 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2_amd64.buildinfo
Checksums-Sha256:
 ff0ac815b23ddb275738919adc5bef814c84512925bb33d5a33cba7ecd62af01 3741 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.dsc
 85c72ab1cb1b26f87868c66f7cdfad158f709979dccd0156d6e0d06a1b536723 17004 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.debian.tar.xz
 709803f38210fd6723300631966db43f71921078f9e204fbe1fbbfea7910eb3f 13246 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2_amd64.buildinfo
Files:
 50818f6efcba9c7daa7e262d25467248 3741 javascript optional 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.dsc
 6c774dc0529b82561b3faf09087d6c03 17004 javascript optional 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2.debian.tar.xz
 6a42ffb2357f6e480e7d3a086d8f456d 13246 javascript optional 
jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2_amd64.buildinfo

Bug#996486: marked as done (bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 19:18:36 +
with message-id 
and subject line Bug#997927: fixed in leveldb 1.23-3
has caused the Debian Bug report #997927,
regarding bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE
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.)


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

Dear Maintainer,

Since 2021-10-12 bitcoind fails to start on my machine:

```
# fgrep leveldb /var/log/syslog
Oct 12 20:00:34 vinco bitcoind[1103]: /usr/bin/bitcoind: symbol lookup error: 
/usr/bin/bitcoind: undefined symbol: _ZTIN7leveldb6Logger
```

This is list of updated packages just before first failure (from 
/var/log/apt/history.log):

```
Start-Date: 2021-10-12  19:59:47
Commandline: apt full-upgrade
Requested-By: vincas (1000)
Install: libraqm0:amd64 (0.7.0-4, automatic)
Upgrade: libffi8:amd64 (3.4.2-2, 3.4.2-3), libffi8:i386 (3.4.2-2,
3.4.2-3), libntfs-3g89:amd64 (1:2021.8.22-2, 1:2021.8.22-3),
ntfs-3g:amd64 (1:2021.8.22-2, 
1:2021.8.22-3), libleveldb1d:amd64 (1.22-3, 1.23-2), licensecheck:amd64
(3.2.11-1, 3.2.13-1), python3-pkg-resources:amd64 (52.0.0-4, 58.2.0-1),
python3-packa
ging:amd64 (20.9-2, 21.0-1), python3-pil:amd64 (8.1.2+dfsg-0.3,
8.3.2-1), libisl23:amd64 (0.23-1, 0.24-2), python3-setuptools:amd64
(52.0.0-4, 58.2.0-1), dkm
s:amd64 (2.8.7-1, 2.8.7-2)
End-Date: 2021-10-12  20:00:07
```

It seems libleveldb1d 1.23-2 broke bitcoind?

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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bitcoind depends on:
ii  libboost-filesystem1.74.0  1.74.0-11
ii  libc6  2.32-4
ii  libdb5.3++ 5.3.28+dfsg1-0.8
ii  libevent-2.1-7 2.1.12-stable-1
ii  libevent-pthreads-2.1-72.1.12-stable-1
ii  libgcc-s1  11.2.0-9
ii  libleveldb1d   1.23-2
ii  libminiupnpc17 2.2.1-1
ii  libsqlite3-0   3.36.0-2
ii  libstdc++6 11.2.0-9
ii  libzmq54.3.4-1

Versions of packages bitcoind recommends:
ii  tor  0.4.5.10-1+b1

Versions of packages bitcoind suggests:
ii  bash-completion  1:2.11-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: leveldb
Source-Version: 1.23-3
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated leveldb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 19:37:05 +0100
Source: leveldb
Architecture: source
Version: 1.23-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 997927
Changes:
 leveldb (1.23-3) unstable; urgency=medium
 .
   [ Thomas Goirand  ]
   * Re-enable RTTI support (closes: #997927).
Checksums-Sha1:
 5635b3afa5a1c243c447d02590549c487a7d2f9c 2044 leveldb_1.23-3.dsc
 a589e9ca315252267a7770ecd72801ca88c74fe9 10072 leveldb_1.23-3.debian.tar.xz
Checksums-Sha256:
 8261e3ee14d3bb7380c8cdaf5c16e8fe3c495c5f9ae85be4916df3d97317d826 2044 
leveldb_1.23-3.dsc
 191a2b654ec10fe4292b0e2a65860587f02f7021a3cce4fc030460a0a6895472 10072 
leveldb_1.23-3.debian.tar.xz
Files:
 7a963284ae467613419f570175dbe579 2044 database optional leveldb_1.23-3.dsc
 5ab57e578d14d151fdc6e520c6a62276 10072 database optional 

Bug#997927: marked as done (Please re-enable RTTI support in leveldb)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 19:18:36 +
with message-id 
and subject line Bug#997927: fixed in leveldb 1.23-3
has caused the Debian Bug report #997927,
regarding Please re-enable RTTI support in leveldb
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.)


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

Hi,

I've tried building Ceph 16.2.x, though it fails because RTTI support has
been disabled in leveldb 1.23. Please re-enable support for it, as per
attached patch. Please see related Ceph bug report:

https://tracker.ceph.com/issues/53060

Note the issues opened against leveldb on Github:

https://github.com/google/leveldb/issues?q=is%3Aissue+is%3Aopen+rtti

Note that the issue is also in snappy for which I'll send another bug
report (though this one is runtime, not at Ceph build time).

Cheers,

Thomas Goirand (zigo)
diff -Nru leveldb-1.23/debian/changelog leveldb-1.23/debian/changelog
--- leveldb-1.23/debian/changelog   2021-10-12 08:01:25.0 +0200
+++ leveldb-1.23/debian/changelog   2021-10-27 11:40:18.0 +0200
@@ -1,3 +1,10 @@
+leveldb (1.23-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add RTTI support.
+
+ -- Thomas Goirand   Wed, 27 Oct 2021 11:40:18 +0200
+
 leveldb (1.23-2) unstable; urgency=medium
 
   * Upload to Sid.
diff -Nru leveldb-1.23/debian/patches/enable-rtti.patch 
leveldb-1.23/debian/patches/enable-rtti.patch
--- leveldb-1.23/debian/patches/enable-rtti.patch   1970-01-01 
01:00:00.0 +0100
+++ leveldb-1.23/debian/patches/enable-rtti.patch   2021-10-27 
11:40:09.0 +0200
@@ -0,0 +1,21 @@
+Description: Enable rtti
+ We need RTTI support because of Ceph
+Author: Thomas Goirand 
+Forwarded: no
+Last-Update: 2021-10-27
+
+--- leveldb-1.23.orig/CMakeLists.txt
 leveldb-1.23/CMakeLists.txt
+@@ -71,9 +71,9 @@ else(CMAKE_CXX_COMPILER_ID STREQUAL "MSV
+   string(REGEX REPLACE "-fexceptions" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-exceptions")
+ 
+-  # Disable RTTI.
+-  string(REGEX REPLACE "-frtti" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+-  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-rtti")
++  # We need RTTI support if code that uses leveldb uses typeid (e.g. ceph).
++#  string(REGEX REPLACE "-frtti" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
++#  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fno-rtti")
+ endif(CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+ 
+ # Test whether -Wthread-safety is available. See
diff -Nru leveldb-1.23/debian/patches/series leveldb-1.23/debian/patches/series
--- leveldb-1.23/debian/patches/series  2021-07-18 07:36:30.0 +0200
+++ leveldb-1.23/debian/patches/series  2021-10-27 11:39:29.0 +0200
@@ -2,3 +2,4 @@
 0113-cmake_memenv.patch
 0120-external_testing.patch
 1001-fix_bloom_test.patch
+enable-rtti.patch
--- End Message ---
--- Begin Message ---
Source: leveldb
Source-Version: 1.23-3
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated leveldb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 19:37:05 +0100
Source: leveldb
Architecture: source
Version: 1.23-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 997927
Changes:
 leveldb (1.23-3) unstable; urgency=medium
 .
   [ Thomas Goirand  ]
   * Re-enable RTTI support (closes: #997927).
Checksums-Sha1:
 5635b3afa5a1c243c447d02590549c487a7d2f9c 2044 leveldb_1.23-3.dsc
 a589e9ca315252267a7770ecd72801ca88c74fe9 10072 leveldb_1.23-3.debian.tar.xz
Checksums-Sha256:
 8261e3ee14d3bb7380c8cdaf5c16e8fe3c495c5f9ae85be4916df3d97317d826 2044 
leveldb_1.23-3.dsc
 191a2b654ec10fe4292b0e2a65860587f02f7021a3cce4fc030460a0a6895472 10072 
leveldb_1.23-3.debian.tar.xz
Files:
 

Processed: Bug#998261 marked as pending in jsbundle-web-interfaces

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #998261 [src:jsbundle-web-interfaces] jsbundle-web-interfaces: autopkgtest 
regression: node: command not found
Added tag(s) pending.

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

Bug#998261: marked as pending in jsbundle-web-interfaces

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

Bug #998261 in jsbundle-web-interfaces 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/js-team/jsbundle-web-interfaces/-/commit/373d5e7fc7ed32a8854bc72df918d6aac2024e3d


fix revert to build-depend on nodejs (used during build after all); closes: 
bug#998261, thanks to Paul Gevers


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998261

Bug#998265: epigrass: autopkgtest regression: The 'panel' distribution was not found

[Paul Gevers]

Source: epigrass
Version: 3.0.3+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of epigrass the autopkgtest of epigrass fails in
testing when that autopkgtest is run with the binary packages of
epigrass from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
epigrass   from testing3.0.3+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=epigrass

https://ci.debian.net/data/autopkgtest/testing/amd64/e/epigrass/16032967/log.gz

Traceback (most recent call last):
  File "/usr/bin/epirunner", line 33, in 
sys.exit(load_entry_point('epigrass==3.0.3', 'console_scripts',
'epirunner')())
  File "/usr/bin/epirunner", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 850, in exec_module
  File "", line 228, in
_call_with_frames_removed
  File "/usr/lib/python3/dist-packages/Epigrass/manager.py", line 20, in

from Epigrass.simobj import graph, edge, siteobj
  File "/usr/lib/python3/dist-packages/Epigrass/simobj.py", line 19, in

from Epigrass import models
  File "/usr/lib/python3/dist-packages/Epigrass/models.py", line 14, in

from epimodels.continuous.models import SIR, SEIR
  File "/usr/lib/python3/dist-packages/epimodels/continuous/models.py",
line 12, in 
import numba
  File "/usr/lib/python3/dist-packages/numba/__init__.py", line 19, in

from numba.core import config
  File "/usr/lib/python3/dist-packages/numba/core/config.py", line 16,
in 
import llvmlite.binding as ll
  File "/usr/lib/python3/dist-packages/llvmlite/binding/__init__.py",
line 4, in 
from .dylib import *
  File "/usr/lib/python3/dist-packages/llvmlite/binding/dylib.py", line
3, in 
from llvmlite.binding import ffi
  File "/usr/lib/python3/dist-packages/llvmlite/binding/ffi.py", line
137, in 
from pkg_resources import resource_filename
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3243, in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3226, in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
3255, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
568, in _build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
886, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
772, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'panel' distribution was not
found and is required by epigrass
autopkgtest [12:13:19]: test run-unit-test




OpenPGP_signature
Description: OpenPGP digital signature

Bug#974778: llvmlite: Please upgrade to llvm-toolchain-11

[Drew Parsons]

Source: llvmlite
Version: 0.35.0-3
Followup-For: Bug #974778
Control: affects -1 src:numba

Now that bullseye is released, please proceed fixing this bug now,
i.e. please package llvmlite 0.37.

It's required in order to package numba 0.54, which is needed to fix
problems on armel.

Processed: Re: llvmlite: Please upgrade to llvm-toolchain-11

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:numba
Bug #974778 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Bug #974801 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Bug #974824 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-11
Added indication that 974778 affects src:numba
Added indication that 974801 affects src:numba
Added indication that 974824 affects src:numba

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

Bug#998261: jsbundle-web-interfaces: autopkgtest regression: node: command not found

[Paul Gevers]

Source: jsbundle-web-interfaces
Version: 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of jsbundle-web-interfaces the autopkgtest of
jsbundle-web-interfaces fails in testing when that autopkgtest is run
with the binary packages of jsbundle-web-interfaces from unstable. It
passes when run with only packages from testing. In tabular form:

passfail
jsbundle-web-interfaces from testing
1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-1
all others  from testingfrom testing

I copied some of the output at the bottom of this report. It seems that
when you dropped the (Build-)Depends, you forgot it was needed for the test.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=jsbundle-web-interfaces

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jsbundle-web-interfaces/16336344/log.gz

bash: line 1: node: command not found
autopkgtest [15:09:56]: test command1




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:osslsigncode: fails to migrate to testing for too long: unresolved RC bugs

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.2-1
Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing 
for too long: unresolved RC bugs
Marked as fixed in versions osslsigncode/2.2-1.
Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing 
for too long: unresolved RC bugs
Marked Bug as done
> block -1 by 993451 993452
Bug #998259 {Done: Paul Gevers } [src:osslsigncode] 
src:osslsigncode: fails to migrate to testing for too long: unresolved RC bugs
998259 was not blocked by any bugs.
998259 was not blocking any bugs.
Added blocking bug(s) of 998259: 993452 and 993451
> tags 993451 ftbfs
Bug #993451 [osslsigncode] osslsigncode: timestamp-based tests fail on amd64 
(sometimes)
Added tag(s) ftbfs.
> severity 993451 serious
Bug #993451 [osslsigncode] osslsigncode: timestamp-based tests fail on amd64 
(sometimes)
Severity set to 'serious' from 'normal'
> tags 993452 ftbfs
Bug #993452 [osslsigncode] osslsigncode: MSI tests fail on big-endian 
architectures
Added tag(s) ftbfs.
> severity 993452 serious
Bug #993452 [osslsigncode] osslsigncode: MSI tests fail on big-endian 
architectures
Severity set to 'serious' from 'normal'

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

Bug#998259: src:osslsigncode: fails to migrate to testing for too long: unresolved RC bugs

[Paul Gevers]

Source: osslsigncode
Version: 2.1-1
Severity: serious
Control: close -1 2.2-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 993451 993452
Control: tags 993451 ftbfs
Control: severity 993451 serious
Control: tags 993452 ftbfs
Control: severity 993452 serious

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:osslsigncode 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 bookworm, 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=osslsigncode




OpenPGP_signature
Description: OpenPGP digital signature

Bug#996387: marked as done (ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 18:04:37 +
with message-id 
and subject line Bug#996387: fixed in ruby-sigar 0.7.3-3
has caused the Debian Bug report #996387,
regarding ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error: 
rpc/rpc.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.)


-- 
996387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sigar
Version: 0.7.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-sigar was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> gcc -fdebug-prefix-map=/<>=. -I. 
> -I/usr/include/x86_64-linux-gnu/ruby-2.7.0 
> -I/usr/include/ruby-2.7.0/ruby/backward -I/usr/include/ruby-2.7.0 -I. 
> -Wdate-time -D_FORTIFY_SOURCE=2   -I../../include -I../../src/os/linux 
> -U_FILE_OFFSET_BITS -DRB_HAS_RE_ERROR -DRB_RUBY_19 -fPIC -g -O2 
> -ffile-prefix-map=/build/ruby2.7-yGW2TI/ruby2.7-2.7.4=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o 
> sigar_util.o -c sigar_util.c
> sigar_util.c: In function ‘sigar_proc_list_procfs_get’:
> sigar_util.c:167:5: warning: ‘readdir_r’ is deprecated 
> [-Wdeprecated-declarations]
>   167 | while (readdir_r(dirp, , ) == 0) {
>   | ^
> In file included from sigar_util.c:31:
> /usr/include/dirent.h:183:12: note: declared here
>   183 | extern int readdir_r (DIR *__restrict __dirp,
>   |^
> sigar_util.c: In function ‘sigar_proc_fd_count’:
> sigar_util.c:210:5: warning: ‘readdir_r’ is deprecated 
> [-Wdeprecated-declarations]
>   210 | while (readdir_r(dirp, , ) == 0) {
>   | ^
> In file included from sigar_util.c:31:
> /usr/include/dirent.h:183:12: note: declared here
>   183 | extern int readdir_r (DIR *__restrict __dirp,
>   |^
> sigar_util.c: At top level:
> sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
>   742 | #include 
>   |  ^~~
> compilation terminated.
> make[1]: *** [Makefile:245: sigar_util.o] Error 1


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sigar/ruby-sigar_0.7.3-2+rebuild1633395509_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-sigar
Source-Version: 0.7.3-3
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-sigar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 17:47:46 +0100
Source: ruby-sigar
Architecture: source
Version: 0.7.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Daniel Leidert 
Closes: 996387
Changes:
 ruby-sigar (0.7.3-3) unstable; urgency=medium
 .
   * Team upload.
   * d/compat: Remove file.
   * d/control: Add Rules-Requires-Root field.
 (Build-Depends): Add libtirpc-dev. Use debhelper-compat.
 (Standards-Version): Bump to 4.6.0.
 (Depends): Add ${ruby:Depends}.
   * d/patches/996387-fix-ftbfs-missing-rpc-header.patch: Add patch.
 - Use libtirpc-dev to provide rpc/rpc.h and others after libc6-dev stopped
   shipping them (closes: #996387).
   * d/patches/*: Refresh patches and add DEP-3 headers.
   * d/patches/series: Enable new patch.
Checksums-Sha1:
 39772c6a166e9b21de25011f5d7bef58954051ee 1979 ruby-sigar_0.7.3-3.dsc
 76671e4e631b2d6b15fd619ce760d6cf665169c5 5448 ruby-sigar_0.7.3-3.debian.tar.xz
 8b511ca61d69ead9d4baa2979f808ba50e43 9386 
ruby-sigar_0.7.3-3_amd64.buildinfo
Checksums-Sha256:
 

Bug#998258: node-liftoff: FTBFS: TypeError: isPlainObject is not a function

[Andreas Beckmann]

Source: node-liftoff
Version: 3.1.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-liftoff/experimental recently started to FTBFS with

  dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
No build command found, searching known files
   dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/liftoff
/bin/sh -ex debian/tests/pkg-js/test
+ mocha -t 2 -b -R spec test/index


  Liftoff
buildEnvironment
  undefined should locate local module using cwd if no config is found
  undefined should locate global module using NODE_PATH if defined
  undefined if cwd is explicitly provided, don't use search_paths
  undefined should find case sensitive configPath
  - should find module in the directory next to config
  - should require the package sibling to the module
  undefined should set cwd to match the directory of the config file as 
long as cwd wasn't explicitly provided
  for developing against yourself
- should find and load package.json
- should clear modulePackage if package.json is of different project
- should use `index.js` if `main` property in package.json does not 
exist
prepare
  undefined should set the process.title to the moduleName
  undefined should return early if completions are available and requested
  undefined should call prepare with liftoff instance as context
  undefined should pass environment to first argument of prepare callback
  undefined should throw if 2nd arg is not a function
execute
  undefined should pass environment to first argument of execute callback
  undefined should throw if 2nd arg is not a function
  - should skip respawning if process.argv has no values from v8flags in it
  - should respawn if process.argv has values from v8flags in it
  - should throw if v8flags is a function and it causes an error
  - should respawn if v8flag is set by forcedFlags
  - should respawn if v8flag is set by both cli flag and forcedFlags
  - should emit a respawn event if a respawn is required
  - should respawn if process.argv has v8flags with values in it
  - should respawn if v8flags is empty but forcedFlags are specified
requireLocal
  - should attempt pre-loading local modules if they are requested
  - should attempt pre-loading a local module if it is requested
  - should attempt pre-loading local modules but fail
  - should pre-load a local module only once even if be respawned
  - should emit `require` with the name of the module and the required 
module
  undefined should emit `requireFail` with an error if a module can't be 
found.
configFiles
  undefined should be empty if not specified
  1) should find multiple files if specified


  14 passing (49ms)
  18 pending
  1 failing

  1) Liftoff
   configFiles
 should find multiple files if specified:
 TypeError: isPlainObject is not a function
  at expandPath (/usr/share/nodejs/fined/index.js:19:8)
  at fined (/usr/share/nodejs/fined/index.js:14:22)
  at /build/node-liftoff-3.1.0/index.js:122:21
  at /build/node-liftoff-3.1.0/object-map/index.js:18:19
  at /usr/lib/nodejs/for-own/index.js:16:17
  at forIn (/usr/lib/nodejs/for-in/index.js:12:12)
  at forOwn (/usr/lib/nodejs/for-own/index.js:14:3)
  at module.exports (object-map/index.js:17:3)
  at /build/node-liftoff-3.1.0/index.js:121:14
  at /build/node-liftoff-3.1.0/object-map/index.js:18:19
  at /usr/lib/nodejs/for-own/index.js:16:17
  at forIn (/usr/lib/nodejs/for-in/index.js:12:12)
  at forOwn (/usr/lib/nodejs/for-own/index.js:14:3)
  at module.exports (object-map/index.js:17:3)
  at Liftoff.buildEnvironment (index.js:119:19)
  at Liftoff.prepare (index.js:171:18)
  at Context. (test/index.js:410:11)
  at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
  at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
  at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:681:10)
  at /usr/share/nodejs/mocha/lib/runner.js:804:12
  at next (/usr/share/nodejs/mocha/lib/runner.js:596:14)
  at /usr/share/nodejs/mocha/lib/runner.js:606:7
  at next (/usr/share/nodejs/mocha/lib/runner.js:489:14)
  at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:574:5)
  at processImmediate (internal/timers.js:461:21)



dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:5: binary] Error 25


Andreas


node-liftoff_3.1.0-5.log.gz
Description: application/gzip

Processed: severity of 994456 is important

[Debian Bug Tracking System]

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

> # I don't think this warrants an RC bug
> severity 994456 important
Bug #994456 [src:ruby-stackprof] ruby-stackprof: flaky autopkgtests
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#998255: fbzx: FTBFS with GCC 11: error: reference to 'byte' is ambiguous

[Andreas Beckmann]

Source: fbzx
Version: 3.1.0-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

Hi,

fbzx FTBFS with GCC 11 which defaults to -std=c++17:

g++ -c -O2 -Wdate-time -D_FORTIFY_SOURCE=2 `pkg-config --cflags sdl 
libpulse-simple alsa` -D D_SOUND_PULSE -D D_SOUND_ALSA -D D_SOUND_OSS -o 
cargador.o cargador.cpp
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:56:17: error: reference to 'byte' is ambiguous
   56 | byte F,A, C,B, E,D, L,H, IXl,IXh, IYl,IYh, P,S;
  | ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/bits/char_traits.h:39,
 from /usr/include/c++/11/string:40,
 from tape.hh:30,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: 'enum 
class std::byte'
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:28:23: note: 'typedef unsigned char byte'
   28 | typedef unsigned char byte;
  |   ^~~~
z80free/Z80free.h:75:9: error: reference to 'byte' is ambiguous
   75 | byteR;  /* Refresh */
  | ^~~~
In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
 from /usr/include/c++/11/bits/char_traits.h:39,
 from /usr/include/c++/11/string:40,
 from tape.hh:30,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
/usr/include/c++/11/bits/cpp_type_traits.h:404:30: note: candidates are: 'enum 
class std::byte'
  404 |   enum class byte : unsigned char;
  |  ^~~~
In file included from emulator.hh:22,
 from tape.hh:35,
 from computer.hh:26,
 from cargador.hh:20,
 from cargador.cpp:20:
z80free/Z80free.h:28:23: note: 'typedef unsigned char byte'
   28 | typedef unsigned char byte;
  |   ^~~~
[...]

Andreas


fbzx_3.1.0-1.log.gz
Description: application/gzip

Bug#997309: marked as done (django-countries: FTBFS: AttributeError: 'CountryField' object has no attribute 'db_collation')

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 17:34:32 +
with message-id 
and subject line Bug#997309: fixed in django-countries 7.2.1-1
has caused the Debian Bug report #997309,
regarding django-countries: FTBFS: AttributeError: 'CountryField' object has no 
attribute 'db_collation'
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.)


-- 
997309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-countries
Version: 6.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in 
> scripts instead.
> set -e; \
> for python in python3.9; do \
>   PYTHONPATH="." DJANGO_SETTINGS_MODULE=django_countries.tests.settings 
> $python /usr/bin/django-admin test django_countries.tests;\
> done
> Creating test database for alias 'default'...
> Traceback (most recent call last):
>   File "/usr/bin/django-admin", line 33, in 
> sys.exit(load_entry_point('Django==3.2.8', 'console_scripts', 
> 'django-admin')())
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 419, in execute_from_command_line
> utility.execute()
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 413, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 23, in run_from_argv
> super().run_from_argv(argv)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 354, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 398, in execute
> output = self.handle(*args, **options)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/test.py", 
> line 55, in handle
> failures = test_runner.run_tests(test_labels)
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 725, in 
> run_tests
> old_config = self.setup_databases(aliases=databases)
>   File "/usr/lib/python3/dist-packages/django/test/runner.py", line 643, in 
> setup_databases
> return _setup_databases(
>   File "/usr/lib/python3/dist-packages/django/test/utils.py", line 179, in 
> setup_databases
> connection.creation.create_test_db(
>   File "/usr/lib/python3/dist-packages/django/db/backends/base/creation.py", 
> line 74, in create_test_db
> call_command(
>   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
> line 181, in call_command
> return command.execute(*args, **defaults)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 398, in execute
> output = self.handle(*args, **options)
>   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
> 89, in wrapped
> res = handle_func(*args, **kwargs)
>   File 
> "/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", 
> line 202, in handle
> pre_migrate_apps = pre_migrate_state.apps
>   File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 48, 
> in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>   File "/usr/lib/python3/dist-packages/django/db/migrations/state.py", line 
> 208, in apps
> return StateApps(self.real_apps, self.models)
>   File "/usr/lib/python3/dist-packages/django/db/migrations/state.py", line 
> 258, in __init__
> self.real_models.append(ModelState.from_model(model, exclude_rels=True))
>   File "/usr/lib/python3/dist-packages/django/db/migrations/state.py", line 
> 407, in from_model
> fields.append((name, field.clone()))
>   File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
> line 512, in clone
> name, path, args, kwargs = self.deconstruct()
>   File "/<>/django_countries/fields.py", line 343, in deconstruct
> name, path, args, kwargs = super().deconstruct()
>   File "/usr/lib/python3/dist-packages/django/db/models/fields/__init__.py", 
> line 1089, in deconstruct
> if self.db_collation:
> AttributeError: 'CountryField' object has no attribute 'db_collation'
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1


The full build log is available from:

Bug#997411: marked as done (libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 17:20:12 +
with message-id 
and subject line Bug#997411: fixed in libstatgen 1.0.15-2
has caused the Debian Bug report #997411,
regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstatgen
Version: 1.0.15-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p debian/libstatgen-dev/usr/include/libStatGen/
> cp -L include/* debian/libstatgen-dev/usr/include/libStatGen/
> ln -s libStatGen.so.0 libStatGen.so
> d-shlibmove --commit \
> --multiarch \
> --devunversioned \
> --exclude-a \
> libStatGen.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libstatgen0/usr/lib/x86_64-linux-gnu
> mv ./libStatGen.la debian/libstatgen-dev/usr/lib/x86_64-linux-gnu || true
> mv ./libStatGen.so debian/libstatgen-dev/usr/lib/x86_64-linux-gnu
> mv /<>/libStatGen.so.0 
> debian/libstatgen0/usr/lib/x86_64-linux-gnu
> PKGDEV=libstatgen-dev
> PKGSHL=libstatgen0
> mv: cannot stat './libStatGen.la': No such file or directory
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libstatgen0/DEBIAN/symbols doesn't match 
> completely debian/libstatgen0.symbols
> --- debian/libstatgen0.symbols (libstatgen0_1.0.15-1_amd64)
> +++ dpkg-gensymbolsg7dqfg 2021-10-23 07:27:53.388462560 +
> @@ -1636,6 +1636,7 @@
>   _ZN9FastQFile11interleavedEv@Base 1.0.15
>   _ZNK13VcfRecordInfo11getInfoPairB5cxx11Ei@Base 1.0.15
>   
> _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE4findERKS5_@Base
>  1.0.14
> + 
> _ZNSt10_HashtableINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_SaIS5_ENSt8__detail9_IdentityESt8equal_toIS5_ESt4hashIS5_ENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb1ELb19_M_rehashEmRKm@Base
>  1.0.15-1
>   _ZNSt12_Destroy_auxILb0EE9__destroyIP6StringEEvT_S4_@Base 1.0.14
>   _ZNSt12_Destroy_auxILb0EE9__destroyIPN9IndexBase9ReferenceEEEvT_S5_@Base 
> 1.0.14
>   _ZNSt12_Vector_baseIN5Cigar13CigarOperatorESaIS1_EED1Ev@Base 1.0.14
> @@ -1656,6 +1657,8 @@
>   
> _ZNSt6vectorIhSaIhEE17_M_realloc_insertIJRKhEEEvN9__gnu_cxx17__normal_iteratorIPhS1_EEDpOT_@Base
>  1.0.14
>   
> _ZNSt6vectorIhSaIhEE17_M_realloc_insertIJhEEEvN9__gnu_cxx17__normal_iteratorIPhS1_EEDpOT_@Base
>  1.0.14
>   
> _ZNSt6vectorIiSaIiEE17_M_realloc_insertIJiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base
>  1.0.14
> + _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1IS3_EEPKcRKS3_@Base 
> 1.0.15-1
> + _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2IS3_EEPKcRKS3_@Base 
> 1.0.15-1
>   _ZNSt7__cxx119to_stringEx@Base 1.0.15
>   _ZZNSt8__detail18__to_chars_10_implIyEEvPcjT_E8__digits@Base 1.0.15
>   bQualityConvertor@Base 1.0.14
> @@ -1739,7 +1742,7 @@
>   (c++)"std::_Deque_base 
> >::_M_initialize_map(unsigned long)@Base" 1.0.14
>   (c++)"std::_Hashtable std::char_traits, std::allocator >, 
> std::__cxx11::basic_string, std::allocator 
> >, std::allocator, 
> std::allocator > >, std::__detail::_Identity, 
> std::equal_to, 
> std::allocator > >, std::hash std::char_traits, std::allocator > >, 
> std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
> std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits true, true> >::_M_find_before_node(unsigned long, 
> std::__cxx11::basic_string, std::allocator 
> > const&, unsigned long) const@Base" 1.0.14
>   (c++)"std::_Hashtable std::char_traits, std::allocator >, 
> std::__cxx11::basic_string, std::allocator 
> >, 

Processed: Bug#997309 marked as pending in django-countries

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997309 [src:django-countries] django-countries: FTBFS: AttributeError: 
'CountryField' object has no attribute 'db_collation'
Added tag(s) pending.

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

Bug#997309: marked as pending in django-countries

[Michael Fladischer]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/django-countries/-/commit/d92a6692beea3aaf8fef17ed0302de78f01aa5ac


Upload to unstable (Closes: #997309).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997309

Bug#998156: contains non-DFSG-free files

[Florian Weimer]

* Henry Cejtin:

> (I assume you meant ml-nlffigen.)  ml-nlffigen is part of SML/NJ, not
> part of MLton.

/usr/bin/mlnlffigen is part of mlton-tools.

I believe the code generation requirements are different for MLton and
SML/NJ.

Processed: Bug#996387 marked as pending in ruby-sigar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996387 [src:ruby-sigar] ruby-sigar: FTBFS with ruby3.0: 
sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
Added tag(s) pending.

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

Bug#996387: marked as pending in ruby-sigar

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996387 in ruby-sigar 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/ruby-team/ruby-sigar/-/commit/669d232f187b28f33e0b624bde0defd296acbd9a


Fix FTBFS with recent libc6-dev version missing rpc/rpc.h

  * d/control (Build-Depends): Add libtirpc-dev.
  * d/patches/996387-fix-ftbfs-missing-rpc-header.patch: Add patch.
- Use libtirpc-dev to provide rpc/rpc.h and others after libc6-dev stopped
  shipping them (closes: #996387).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996387

Bug#997330: marked as done (cpl-plugin-amber: FTBFS: configure: error: Installed cfitsio (unknown) is too old)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:48:48 +
with message-id 
and subject line Bug#997330: fixed in cpl-plugin-amber 4.4.1+dfsg-1
has caused the Debian Bug report #997330,
regarding cpl-plugin-amber: FTBFS: configure: error: Installed cfitsio 
(unknown) is too old
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.)


-- 
997330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-amber
Version: 4.4.0+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> checking whether gcc supports -pthread... yes
> checking for pthread_create in -lpthread... yes
> checking for pthread.h... yes
> checking for cfitsio... yes
> checking for a cfitsio version >= 3.310... no
> configure: error: Installed cfitsio (unknown) is too old
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/cpl-plugin-amber_4.4.0+dfsg-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-amber
Source-Version: 4.4.1+dfsg-1
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated cpl-plugin-amber 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 12:03:30 +0100
Source: cpl-plugin-amber
Architecture: source
Version: 4.4.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 997330
Changes:
 cpl-plugin-amber (4.4.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 4.4.1+dfsg. Closes: #997330
   * Rediff patches
   * Push Standards-Version to 4.6.0. No changes required
Checksums-Sha1:
 edf0c7106b58309a58c46fcd4f0b2c039159e51c 2443 cpl-plugin-amber_4.4.1+dfsg-1.dsc
 145ed0e33101c9250cc7279618f4ce3db32d29ae 854124 
cpl-plugin-amber_4.4.1+dfsg.orig.tar.xz
 d68071e77b9f938e33a9955ea9340883da8dffa1 9608 
cpl-plugin-amber_4.4.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
 3c880fc764de26a923bad1e06455524922bfbc8c014579dc12bf14abab67f8c3 2443 
cpl-plugin-amber_4.4.1+dfsg-1.dsc
 f18a09ccf897e897e507dee86f8359ba1ff5d4362f8875d856e1856658a97367 854124 
cpl-plugin-amber_4.4.1+dfsg.orig.tar.xz
 61be7b05d140701457b52da0fdac0faa32c18a22a0e1f026b56dbdb28dcf746e 9608 
cpl-plugin-amber_4.4.1+dfsg-1.debian.tar.xz
Files:
 4d8192324b7888d83da59a65dbb65d93 2443 science optional 
cpl-plugin-amber_4.4.1+dfsg-1.dsc
 d7c0c1bbfcfa7a667260e9bb61afc2f8 854124 science optional 
cpl-plugin-amber_4.4.1+dfsg.orig.tar.xz
 73ffb59e3ba5e3564d4810503c11cb69 9608 science optional 
cpl-plugin-amber_4.4.1+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmGAGEUACgkQcRWv0HcQ
3PdX2A//fBM4OVFf26/PGTwD9vDgfyjczkzWBHb3kziBy61gF1P8/VaLZhiqjhrn
xAzMkRsu8RZDiaaAp6m66iCGBTawACqVPQbkcMe+poXJIfeN1q2EUMH797Xygo47
dJNIfLckyqJNz65qgI38EW+p5CI2Y1LaOHSXaaviNW7jLcf9fpHUwH6VpdNiEDdU
+wFsS4rDQNVcVYE5N+/uLOks0uFCU8+UMxuUSHiHaQeZHwOlGOA45h98vQ7soYYQ
zKmqRdTjVx5dJzuy5E5T+iI3PF+jgnLCTLTA2MYeGjJgoFbSKgCFNYuJCW3+IxpV
Icl78seb6yZYkxQNHH4qvV0yYbxLOHZK9I4Crb6JONpQot4ScNbxN2sW9+lqH1N3
AD/NXRlvVTNThAW0Fkl4OIWzjXu0g0eMYO6S6eQYOEJrSSRf37A9E8ZWYZcu/Ti3
uE5RT27BC2x8924aR+1qLDTuJnMHTplKttUyvoObp7/EoJiLalG9Yy9kIMhWQx9m
eIypDfvaoaPebLW+nxDUcdy+gRjPjc/O+f+HjRGSoFvfhdLF2/Yclq61HL8tUaX9
E4deoaCiR2uBsnsp8H684Kw6vYm+29NVgu+vAkwJySRecq1MowhNvZ/Vdmzu7gJ1

Bug#997292: marked as done (wsclean: FTBFS: ld: libwsclean.so.2: undefined reference to `H5::DataSpace::selectAll() const')

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:50:04 +
with message-id 
and subject line Bug#997292: fixed in wsclean 3.0-1
has caused the Debian Bug report #997292,
regarding wsclean: FTBFS: ld: libwsclean.so.2: undefined reference to 
`H5::DataSpace::selectAll() const'
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.)


-- 
997292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wsclean
Version: 2.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=c++11 -O3 -Wall -DNDEBUG  -Wl,-z,relro -rdynamic 
> CMakeFiles/wsclean.dir/wscleanmain.cpp.o -o wsclean  
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/hdf5/serial:
>  libwsclean.so.2 -lcasa_ms -lcasa_fits -lcfitsio -lm -lcasa_scimath 
> -lcasa_measures -lcasa_scimath_f -lcasa_tables -lcasa_casa 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so -lcrypto -lcurl -lpthread 
> -lsz -lz -ldl -lm -lm -ldl -lboost_system -lcasa_scimath -lcasa_measures 
> -lcasa_scimath_f -lcasa_tables -lcasa_casa 
> /usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so -lcrypto -lcurl -lpthread 
> -lsz -lz -ldl -ldl -lboost_system 
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSpace::selectAll() const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::FileAccPropList::DEFAULT'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSpace::getSimpleExtentDims(unsigned long long*, unsigned long long*) 
> const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::H5Location::openDataSet(char const*, H5::DSetAccPropList const&) const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to `H5::DataSet::~DataSet()'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::PredType::NATIVE_FLOAT'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSet::read(void*, H5::DataType const&, H5::DataSpace const&, 
> H5::DataSpace const&, H5::DSetMemXferPropList const&) const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DSetMemXferPropList::DEFAULT'
> /usr/bin/ld: libwsclean.so.2: undefined reference to `H5::DataSet::getSpace() 
> const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::FileCreatPropList::DEFAULT'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSpace::~DataSpace()'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSpace::DataSpace(int, unsigned long long const*, unsigned long long 
> const*)'
> /usr/bin/ld: libwsclean.so.2: undefined reference to `H5::H5File::H5File(char 
> const*, unsigned int, H5::FileCreatPropList const&, H5::FileAccPropList 
> const&)'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DataSpace::getSimpleExtentNdims() const'
> /usr/bin/ld: libwsclean.so.2: undefined reference to 
> `H5::DSetAccPropList::DEFAULT'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/wsclean_2.10.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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: wsclean
Source-Version: 3.0-1
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated wsclean 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: 

Bug#997195: marked as done (cpl-plugin-vimos: FTBFS: vimos_flat_normalise.cc:479:23: error: aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:49:00 +
with message-id 
and subject line Bug#997195: fixed in cpl-plugin-vimos 4.1.6+dfsg-1
has caused the Debian Bug report #997195,
regarding cpl-plugin-vimos: FTBFS: vimos_flat_normalise.cc:479:23: error: 
aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined
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.)


-- 
997195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-vimos
Version: 4.1.1+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -std=gnu++11 
> -DHAVE_CONFIG_H -I. -I..  -D_XOPEN_SOURCE -I../casu/src -I../mosca/hdrl 
> -I../mosca/libmosca  -I../vimos -I../casu/src -I../mosca/libmosca 
> -I../libpil/pil -I../libpil/kazlib -I../external/libwcs -I../irplib 
> -I/usr/include/cpl -I/usr/include -I/usr/include/cext -I/usr/include 
> -I/usr/include/cfitsio  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o vimos_calib_impl.lo vimos_calib_impl.cc
> libtool: compile:  g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I.. -D_XOPEN_SOURCE 
> -I../casu/src -I../mosca/hdrl -I../mosca/libmosca -I../vimos -I../casu/src 
> -I../mosca/libmosca -I../libpil/pil -I../libpil/kazlib -I../external/libwcs 
> -I../irplib -I/usr/include/cpl -I/usr/include -I/usr/include/cext 
> -I/usr/include -I/usr/include/cfitsio -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c vimos_calib_impl.cc  -fPIC -DPIC -o 
> .libs/vimos_calib_impl.o
> moses.c: In function ‘mos_wavelength_calibration_raw’:
> moses.c:6424:19: warning: argument 1 range [18446744071562067968, 
> 18446744073709551615] exceeds maximum object size 9223372036854775807 
> [-Walloc-size-larger-than=]
>  6424 | have_it = cpl_calloc(ny, sizeof(int));
>   |   ^~~
> In file included from /usr/include/cpl.h:45,
>  from ./fors_tools.h:31,
>  from moses.c:39:
> /usr/include/cpl_memory.h:35:7: note: in a call to allocation function 
> ‘cpl_calloc’ declared here
>35 | void *cpl_calloc(size_t, size_t) CPL_ATTR_CALLOC;
>   |   ^~
> In file included from ../mosca/libmosca/vector_utils.h:178,
>  from vimos_flat_normalise.cc:37:
> ../mosca/libmosca/vector_utils.tcc: In member function ‘void 
> mosca::vector_polynomial::fit(const std::vector&, std::vector&, const 
> std::vector&, size_t&)’:
> ../mosca/libmosca/vector_utils.tcc:371:13: warning: ‘cpl_polynomial* 
> cpl_polynomial_fit_1d_create(const cpl_vector*, const cpl_vector*, cpl_size, 
> double*)’ is deprecated [-Wdeprecated-declarations]
>   370 | m_pol_fit = cpl_polynomial_fit_1d_create
>   | 
>   371 | (xpos, filtered_values, polyorder, NULL);
>   | ^~~~
> In file included from /usr/include/cpl_image_resample.h:33,
>  from /usr/include/cpl_image.h:31,
>  from /usr/include/cpl.h:28,
>  from vimos_flat_normalise.h:31,
>  from vimos_flat_normalise.cc:34:
> /usr/include/cpl_polynomial.h:111:18: note: declared here
>   111 | cpl_polynomial * cpl_polynomial_fit_1d_create(const cpl_vector *,
>   |  ^~~~
> In file included from ../mosca/libmosca/image_spline_fit.h:47,
>  from vimos_flat_normalise.cc:38:
> ../mosca/libmosca/image_spline_fit.tcc: In function ‘void 
> mosca::image_pol_1d_fit(mosca::image&, int, double)’:
> ../mosca/libmosca/image_spline_fit.tcc:255:13: warning: ‘cpl_polynomial* 
> cpl_polynomial_fit_1d_create(const cpl_vector*, const cpl_vector*, cpl_size, 
> double*)’ is deprecated [-Wdeprecated-declarations]
>   254 | cpl_polynomial * pol_fit = cpl_polynomial_fit_1d_create
>   |
>   255 | (xpos_final, values_final, polyorder, NULL);
>   | ^~~
> In file included from /usr/include/cpl_image_resample.h:33,
>  from /usr/include/cpl_image.h:31,
>  from /usr/include/cpl.h:28,
>  from 

Bug#997214: marked as done (cpl-plugin-fors: FTBFS: fors_flat_normalise.cc:582:23: error: aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:48:54 +
with message-id 
and subject line Bug#997214: fixed in cpl-plugin-fors 5.5.7+dfsg-1
has caused the Debian Bug report #997214,
regarding cpl-plugin-fors: FTBFS: fors_flat_normalise.cc:582:23: error: 
aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined
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.)


-- 
997214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-fors
Version: 5.5.6+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -std=gnu++11 
> -DHAVE_CONFIG_H -I. -I..  -I../mosca/hdrl -I../mosca/libmosca -I../irplib 
> -I/usr/include/cpl -I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra  -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o fors_img_science_impl.lo 
> fors_img_science_impl.cc
> In file included from ../mosca/libmosca/vector_utils.h:178,
>  from fors_flat_normalise.cc:37:
> ../mosca/libmosca/vector_utils.tcc: In member function ‘void 
> mosca::vector_polynomial::fit(const std::vector&, std::vector&, const 
> std::vector&, size_t&)’:
> ../mosca/libmosca/vector_utils.tcc:371:13: warning: ‘cpl_polynomial* 
> cpl_polynomial_fit_1d_create(const cpl_vector*, const cpl_vector*, cpl_size, 
> double*)’ is deprecated [-Wdeprecated-declarations]
>   370 | m_pol_fit = cpl_polynomial_fit_1d_create
>   | 
>   371 | (xpos, filtered_values, polyorder, NULL);
>   | ^~~~
> In file included from /usr/include/cpl_image_resample.h:33,
>  from /usr/include/cpl_image.h:31,
>  from /usr/include/cpl.h:28,
>  from ./fors_flat_normalise.h:31,
>  from fors_flat_normalise.cc:34:
> /usr/include/cpl_polynomial.h:111:18: note: declared here
>   111 | cpl_polynomial * cpl_polynomial_fit_1d_create(const cpl_vector *,
>   |  ^~~~
> In file included from ../mosca/libmosca/image_spline_fit.h:47,
>  from fors_flat_normalise.cc:38:
> ../mosca/libmosca/image_spline_fit.tcc: In function ‘void 
> mosca::image_pol_1d_fit(mosca::image&, int, double)’:
> ../mosca/libmosca/image_spline_fit.tcc:255:13: warning: ‘cpl_polynomial* 
> cpl_polynomial_fit_1d_create(const cpl_vector*, const cpl_vector*, cpl_size, 
> double*)’ is deprecated [-Wdeprecated-declarations]
>   254 | cpl_polynomial * pol_fit = cpl_polynomial_fit_1d_create
>   |
>   255 | (xpos_final, values_final, polyorder, NULL);
>   | ^~~
> In file included from /usr/include/cpl_image_resample.h:33,
>  from /usr/include/cpl_image.h:31,
>  from /usr/include/cpl.h:28,
>  from ./fors_flat_normalise.h:31,
>  from fors_flat_normalise.cc:34:
> /usr/include/cpl_polynomial.h:111:18: note: declared here
>   111 | cpl_polynomial * cpl_polynomial_fit_1d_create(const cpl_vector *,
>   |  ^~~~
> libtool: compile:  g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I.. -I../mosca/hdrl 
> -I../mosca/libmosca -I../irplib -I/usr/include/cpl -I/usr/include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wextra -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> fors_img_science_impl.cc  -fPIC -DPIC -o .libs/fors_img_science_impl.o
> fors_flat_normalise.cc: In function ‘void dump_vector(const 
> std::vector&)’:
> fors_flat_normalise.cc:582:23: error: aggregate ‘std::stringstream ss’ has 
> incomplete type and cannot be defined
>   582 | std::stringstream ss;
>   |   ^~
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -std=gnu++11 
> -DHAVE_CONFIG_H -I. -I..  -I../mosca/hdrl -I../mosca/libmosca -I../irplib 
> -I/usr/include/cpl -I/usr/include  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wextra  -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c -o fors_img_screen_flat_impl.lo 
> fors_img_screen_flat_impl.cc
> In file included from ../mosca/libmosca/profile_providers.h:126,
>  from 

Bug#997294: marked as done (skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `ZSTD_freeDCtx')

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:36:10 +
with message-id 
and subject line Bug#997294: fixed in skesa 2.4.0-3
has caused the Debian Bug report #997294,
regarding skesa: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
undefined reference to `ZSTD_freeDCtx'
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.)


-- 
997294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: skesa
Version: 2.4.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> c++ -std=c++11 -fdiagnostics-color=never -o kmercounter kmercounter.o 
> glb_align.o -L /<>/NGS/vdb_out/lib64 -lncbi-ngs-c++ -lncbi-vdb 
> -L /<>/NGS/ngs_out/lib64 -lngs-c++ -Wl,-Bstatic  
> -lboost_program_options -lboost_iostreams -lboost_regex -lboost_timer 
> -lboost_chrono -lboost_system -Wl,-Bdynamic -lrt -ldl -lm  -lpthread -lz
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `ZSTD_freeDCtx'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `ZSTD_decompressDCtx'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `ZSTD_createDCtx'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `ZSTD_isError'
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: 
> undefined reference to `ZSTD_getErrorName'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/skesa_2.4.0-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: skesa
Source-Version: 2.4.0-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated skesa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 17:12:21 +0100
Source: skesa
Architecture: source
Version: 2.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 997294
Changes:
 skesa (2.4.0-3) unstable; urgency=medium
 .
   * Versioned Build-Depends: libncbi-vdb-dev (>= 2.11.2+dfsg-2)
 Closes: #997294
Checksums-Sha1:
 4beacfdb3d160a60dbfb3b7d3bfbda261072b601 2103 skesa_2.4.0-3.dsc
 f338dfe56b00e778788db70b251253ecaa718131 16108 skesa_2.4.0-3.debian.tar.xz
 73f7b799e840404209e14eb08e36e690eb8eb555 7843 skesa_2.4.0-3_amd64.buildinfo
Checksums-Sha256:
 c9d2974c43c5df2d8f28ff80df47231ab5ca2b59e33562918cc748b9d4b41929 2103 
skesa_2.4.0-3.dsc
 c5d5a06e27da4e6f63fa3bff68a20f5dd6e910348d8a6a066269247bb7cdc5bb 16108 
skesa_2.4.0-3.debian.tar.xz
 39b37a936f7c221030255b05fe6ac872a6711351f2509114ae607aacca499870 7843 
skesa_2.4.0-3_amd64.buildinfo
Files:
 c7da5f9e102f671e209a3c04497e94e6 2103 science optional skesa_2.4.0-3.dsc
 58740793a35571659e8af465d24db3a1 16108 science optional 
skesa_2.4.0-3.debian.tar.xz
 d12f178363b3f89ad485f08ea6e40909 7843 science optional 
skesa_2.4.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmGAEsYRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHSSg/+OqbKidunLk2g/qIYVeXeXsTyTgK6wR9w
YFEY/DQKtgX9c+bOStehJKIRSQjo8tvtmcNnndRP4DzJtKYfWApiTFkq0eJbYh0o

Bug#997133: More information in the ubuntu bugtracker

[Reinhard Tartler]

the ubuntu tracker claims this is golang 1.16 related:
https://bugs.launchpad.net/debian/+source/consul/+bug/1940152

not sure how to proceed here, though...

-- 
regards,
Reinhard

Bug#997450: marked as done (libseqlib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:18:58 +
with message-id 
and subject line Bug#997450: fixed in libseqlib 1.2.0+dfsg-7
has caused the Debian Bug report #997450,
regarding libseqlib: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libseqlib
Version: 1.2.0+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> # Trick to get also headers moved by d-shlibmove
> cp -a SeqLib debian # note: also GenomicRegionCollection.cpp is really needed 
> by freebayes
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
>   --movedev debian/SeqLib usr/include \
>   --override s/libfml0-dev/libfml-dev/ \
>   --override s/libssw0-dev/libssw-dev/ \
> src/.libs/libseqlib.so
> Library package automatic movement utility
>  --> libfml-dev package exists.
>  --> libhts-dev package exists.
>  --> libjsoncpp-dev package exists.
>  --> libssw-dev package exists.
>  --> zlib1g-dev package exists.
> set -e
> install -d -m 755 debian/libseqlib-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libseqlib2/usr/lib/x86_64-linux-gnu
> mv src/.libs/libseqlib.a debian/libseqlib-dev/usr/lib/x86_64-linux-gnu
> mv src/.libs/libseqlib.so debian/libseqlib-dev/usr/lib/x86_64-linux-gnu
> mv /<>/src/.libs/libseqlib.so.2 
> debian/libseqlib2/usr/lib/x86_64-linux-gnu
> mv /<>/src/.libs/libseqlib.so.2.0.0 
> debian/libseqlib2/usr/lib/x86_64-linux-gnu
> PKGDEV=libseqlib-dev
> PKGSHL=libseqlib2
> install -d -m 755 debian/libseqlib-dev/usr/include
> mv debian/SeqLib debian/libseqlib-dev/usr/include
> mkdir -p 
> /<>/debian/libseqlib-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> mv libseqlib.pc 
> /<>/debian/libseqlib-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libseqlib2/DEBIAN/symbols doesn't match 
> completely debian/libseqlib2.symbols
> --- debian/libseqlib2.symbols (libseqlib2_1.2.0+dfsg-6_amd64)
> +++ dpkg-gensymbolsV0YJZ1 2021-10-23 06:33:49.535493580 +
> @@ -16,14 +16,14 @@
>   _ZN6SeqLib10BWAWrapper10SetGapOpenEi@Base 1.2.0
>   _ZN6SeqLib10BWAWrapper11SetZDropoffEi@Base 1.2.0
>   
> (optional)_ZN6SeqLib10BWAWrapper11seqlib_add1EPK6kseq_tP8bntseq_tPhPlPiS8_PP9bntamb1_t@Base
>  1.2.0
> - 
> (optional)_ZN6SeqLib10BWAWrapper11seqlib_add1EPK6kseq_tP8bntseq_tPhPxPiS8_PP9bntamb1_t@Base
>  1.2.0
> +#MISSING: 1.2.0+dfsg-6# 
> (optional)_ZN6SeqLib10BWAWrapper11seqlib_add1EPK6kseq_tP8bntseq_tPhPxPiS8_PP9bntamb1_t@Base
>  1.2.0
>   _ZN6SeqLib10BWAWrapper12SetBandwidthEi@Base 1.2.0
>   
> _ZN6SeqLib10BWAWrapper14ConstructIndexERKSt6vectorINS_17UnalignedSequenceESaIS2_EE@Base
>  1.2.0
>   _ZN6SeqLib10BWAWrapper15SetGapExtensionEi@Base 1.2.0
>   
> _ZN6SeqLib10BWAWrapper15seqlib_make_pacERKSt6vectorINS_17UnalignedSequenceESaIS2_EEb@Base
>  1.2.0
>   _ZN6SeqLib10BWAWrapper16SetReseedTriggerEf@Base 1.2.0
>   _ZN6SeqLib10BWAWrapper18SetMismatchPenaltyEi@Base 1.2.0
> - 
> (optional)_ZN6SeqLib10BWAWrapper18seqlib_add_to_annsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_P9bntann1_tj@Base
>  1.2.0
> +#MISSING: 1.2.0+dfsg-6# 
> (optional)_ZN6SeqLib10BWAWrapper18seqlib_add_to_annsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_P9bntann1_tj@Base
>  1.2.0
>   
> (optional)_ZN6SeqLib10BWAWrapper18seqlib_add_to_annsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_P9bntann1_tm@Base
>  1.2.0
>   _ZN6SeqLib10BWAWrapper18seqlib_bwt_pac2bwtEPKhi@Base 1.2.0
>   _ZN6SeqLib10BWAWrapper24Set3primeClippingPenaltyEi@Base 1.2.0
> @@ -43,12 +43,12 @@
>   
> _ZN6SeqLib13GenomicRegionC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_9BamHeaderE@Base
>  1.2.0
>   
> 

Bug#996227: ruby-ferret (was: [RFH] Fix FTBFSes to kick off the ruby3.0 transition)

[Daniel Leidert]

Am Montag, dem 01.11.2021 um 16:53 +0100 schrieb Daniel Leidert:
> Am Mittwoch, dem 27.10.2021 um 11:02 -0300 schrieb Lucas Kanashiro:
> 
> [..]
> > * ruby-ferret
> [..]
> 
> Also a candidate for an RoM. Dead for 4 years, no reverse build-deps. Requires
> a lot of patches and seems to be seriously broken with Ruby 3.0 [1].
> 
> [1] https://github.com/dbalmain/ferret/issues/14

Well, it seems the NetBSD community has a patch:
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/textproc/ruby-ferret/patches/

Please note, that Fedora applied a bunch of other patches as well before they
removed the package:

https://src.fedoraproject.org/rpms/rubygem-ferret/tree/a0b3fd879133bf69f6ea59d35b54ec857358e959

I haven't checked, if all of them have been applied to the Debian package as
well.

Regards, Daniel

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#997249: marked as done (mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap')

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 16:04:26 +
with message-id 
and subject line Bug#997249: fixed in mpsolve 3.2.1-5
has caused the Debian Bug report #997249,
regarding mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap'
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.)


-- 
997249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpsolve
Version: 3.2.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccYvjt2w.o: in function `main':
> ./conftest.c:34: undefined reference to `yywrap'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/mpsolve_3.2.1-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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mpsolve
Source-Version: 3.2.1-5
Done: Doug Torrance 

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated mpsolve package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 11:51:45 -0400
Source: mpsolve
Built-For-Profiles: noudeb
Architecture: source
Version: 3.2.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Closes: 997249
Changes:
 mpsolve (3.2.1-5) unstable; urgency=medium
 .
   * debian/patches/autoconf-2.70.patch
 - New patch; adjust configure.ac to work with autoconf 2.70
   (Closes: #997249).
Checksums-Sha1:
 0e6dd18a1885727b91069600c6195243ab87d5b8 2656 mpsolve_3.2.1-5.dsc
 c92ab5e3437dce24b96beca15ceae27bb91499dc 10348 mpsolve_3.2.1-5.debian.tar.xz
 42339ae8512bfbe75eb40002da5c8083e65187a2 17106 mpsolve_3.2.1-5_source.buildinfo
Checksums-Sha256:
 53394c35b64ef352be96fef161cdf50453f6948990ff74dfebced3ae04b5c471 2656 
mpsolve_3.2.1-5.dsc
 ac34a4b73f488251e45c878ec6f23964a7b97991068b459995c841d088eb2210 10348 
mpsolve_3.2.1-5.debian.tar.xz
 998c6402c6fa1df12d4fc7eda65ae1c402a9da578a776632069481312ec5356d 17106 
mpsolve_3.2.1-5_source.buildinfo
Files:
 e04ba58d248a8a7776623ef0cc097429 2656 science optional mpsolve_3.2.1-5.dsc
 1158b92ccc37859da8af020127fbbd0c 10348 science optional 
mpsolve_3.2.1-5.debian.tar.xz
 8f6ec00b6579ea0d2cc8a3d2ddda55bd 17106 science optional 
mpsolve_3.2.1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmGADTAXHGR0b3JyYW5j
ZUBwaWVkbW9udC5lZHUACgkQkdxKd57FyRAPIQ//TrYOdOepxfjm1jOGfsudUOrb
4U+Vos/dPNpDciAgVtXFx3kire/3gzz+yswQByzAkvNIV3j249skB1H6kSsHlE1G
0wCX1Uk18s7NB6Vpxjq+Hf0dRZ9dvMDodEXMgKjQcxoKfBsAZt0hUebrgnCkX+sC
5TI8KVbidtvetKK1nRfKTB+S1xsKFYNJKFPDDhQZ7BAkRyR72bpgQ81SmnQ0XBiw
TwAVWpb02zQnwmvSqDLkF2pr6ip61/18qjYZp3agghDfFpVUIsebhaeMfSbHr7Hq
R0QNl2YHtHL3D1aUAVSix6moecrFwLRwab+15AXRNcU9Rsk/R79fTW90pYw5v/6L
ewfVCAvhLehSd4K+YZUIe7ctcTawbN+LVYRQUlJEX6GH8gvHx/rUIcHskddUNU8G
2DsWOjmbviHFiTUnu/dutzK0xot5TSWhu8A+pEoRnVwvy9Ux1J4eOO8Hp5FmYy9U
oIZgRYvMo1i9rKRvPkd0uEEgxx3blONY8Q3cw0HPoPnc6qPCwHXwz0VEiNyfBAax
YR+7wgsI5VCkiel+CDPsmS4LyFbMCcCEQIbwSlG1K1aKSSvagnpgetjTejuVpI2i
lE5wyRem7N+/wIcb+nu02LosGLOuadsV1kjhZHnaA1tt0QR1eA7R1g1QzhhXgkbS
mt6YJ9CN1DQHwk8cikQ=
=UJT/
-END PGP SIGNATURE End Message ---

Bug#998205: plasma-desktop: unable to log into Plasma desktop

[Patrick Franz]

Hi Gary,

KDE Plasma is currently broken in testing. Do you have a mixed Plasma, 
e.g. some packages from 5.21.5 and some from 5.23.0 ?

If yes, then please see the following bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726


-- 
Med vänliga hälsningar

Patrick Franz

Bug#998238: syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.

[Markus Koschany]

Am Montag, dem 01.11.2021 um 07:20 -0700 schrieb tony mancill:
> On Mon, Nov 01, 2021 at 02:06:32PM +0100, Andreas Beckmann wrote:
> > Source: syncany
> > Version: 0.4.9~alpha-3
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> > 
> > Hi,
> > 
> > syncany recently started to FTBFS:
> 
> [...]
> I will freshen a few other things in the package and upload later today.

Thanks for handling this tony!

Cheers,

Markus


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

Bug#996530: marked as done (yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 15:35:32 +
with message-id 
and subject line Bug#996530: fixed in yard 0.9.26-1
has caused the Debian Bug report #996530,
regarding yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:   cannot load 
such file -- webrick
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.)


-- 
996530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yard
Version: 0.9.24-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, yard was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>   cannot load such file -- webrick
> # ./lib/yard/server/webrick_adapter.rb:2:in `'
> # ./spec/server/webrick_servlet_spec.rb:4:in `'
> 
> Top 0 slowest examples (0 seconds, 0.0% of total time):
> 
> Finished in 0.0001 seconds (files took 0.90378 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 

Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit build dependency on it.

The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/yard/yard_0.9.24-1+rebuild1633401329_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: yard
Source-Version: 0.9.26-1
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated yard 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: Fri, 22 Oct 2021 14:27:51 +0200
Source: yard
Architecture: source
Version: 0.9.26-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Cédric Boutillier 
Closes: 996530
Changes:
 yard (0.9.26-1) unstable; urgency=medium
 .
   * Update team name
   * Use github as source
   * New upstream version 0.9.26
   * update Debian packaging
   * change to EXCLUDELIST_APPEND
   * rules: use execute_{before,after}
   * Refresh patches
   * (build)depend on ruby-webrick (Closes: #996530)
Checksums-Sha1:
 0a22ea8471e605bda168c573def8936745fa73e9 1599 yard_0.9.26-1.dsc
 9e9b377b51f68d7c05a68873cea30c39c673b03e 930901 yard_0.9.26.orig.tar.gz
 d0327f8fdda22670a7f8f4bf75bc6c6916604715 81120 yard_0.9.26-1.debian.tar.xz
 754c2a12487293d4bd1a1060e169f1c6f90cd236 9213 yard_0.9.26-1_amd64.buildinfo
Checksums-Sha256:
 fa02b15f8e05100644baef5bb89964d38ca64ed917ea55856a8f4b2419c1f3b7 1599 
yard_0.9.26-1.dsc
 9a19bd02c32a67909275e416ad0da192239d75d8171a65b481f747c6bd2b0375 930901 
yard_0.9.26.orig.tar.gz
 c57c21c683fc1e709d3c48a1376e2ff1b8d5cd78eb05f558d8a4ac8009b176dc 81120 
yard_0.9.26-1.debian.tar.xz
 4e5e4c61b8282aef50ab80e08b447b73354151c69e1db50acbd250d85725e456 9213 
yard_0.9.26-1_amd64.buildinfo
Files:
 d1c617b01be91fccbe550c674bd7985e 1599 ruby optional yard_0.9.26-1.dsc
 3f0d50c2fd62f405b7606a6bccc7a2bd 930901 ruby optional yard_0.9.26.orig.tar.gz
 9c67d6ca66e29a8b1e57b2d0e55dd1ea 81120 ruby optional 
yard_0.9.26-1.debian.tar.xz
 2ef0ba77a419c5ddda407dd3703c2dcd 9213 ruby optional 
yard_0.9.26-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCYYAEhAAKCRBSaZq2P58r
wzaqAQCQBO7S9eer2JV86VWV2TaUeSE27UW5Mccb65c/ThEoRgEA+ujXh40k4o+6
hyhYaIBLUh1g5wzzn+E1rHedc3qTtww=
=MRxK
-END PGP SIGNATURE End Message ---

Processed: Bug#996313 marked as pending in ruby-libvirt

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996313 [src:ruby-libvirt] ruby-libvirt: FTBFS with ruby3.0: 
common.c:27:10: fatal error: st.h: No such file or directory
Added tag(s) pending.

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

Bug#997249: mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap'

[Torrance, Douglas]

Control: tags -1 confirmed

On Sat, 23 Oct 2021 21:18:43 +0200 Lucas Nussbaum  wrote:

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


I believe this became an issue when autoconf was bumped from 2.69 to 2.71
in unstable a few months ago.

Fortunately, it has been reported [1] and fixed [2] upstream.  I'll adapt
the patch to quilt and upload a new version shortly.

[1] https://github.com/robol/MPSolve/issues/27
[2] https://github.com/robol/MPSolve/commit/3a89087


signature.asc
Description: PGP signature

Processed: Re: mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #997249 [src:mpsolve] mpsolve: FTBFS: ./conftest.c:34: undefined reference 
to `yywrap'
Added tag(s) confirmed.

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

Bug#996313: marked as pending in ruby-libvirt

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #996313 in ruby-libvirt 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/libvirt-team/ruby-libvirt/-/commit/197454a43bd8c2c562ba698ed94ab00f76aeaf88


Fix FTBFS with Ruby 3.0

  * d/patches/996313-fix-ext-build-with-ruby3.patch: Add patch.
- Use 'include ' to fix build with Ruby 3 (closes: #996313).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996313

Bug#996952: marked as done (libkolabxml ftbfs with GCC 11)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 15:04:50 +
with message-id 
and subject line Bug#996952: fixed in libkolabxml 1.2.0-3
has caused the Debian Bug report #996952,
regarding libkolabxml ftbfs with GCC 11
to be marked as done.

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

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


-- 
996952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libkolabxml
Version: 1.2.0-2
Severity: serious
Tags: sid bookworm patch

libkolabxml ftbfs with GCC 11, two more symbols need marking as optional.

patch at
http://launchpadlibrarian.net/564865144/libkolabxml_1.2.0-2build1_1.2.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: libkolabxml
Source-Version: 1.2.0-3
Done: Sandro Knauß 

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated libkolabxml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Nov 2021 15:52:39 +0100
Source: libkolabxml
Architecture: source
Version: 1.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Kolab Maintainers 
Changed-By: Sandro Knauß 
Closes: 996952
Changes:
 libkolabxml (1.2.0-3) unstable; urgency=medium
 .
   [ Sandro Knauß ]
   * Update standards version to 4.6.0, no changes needed.
   * Add Multi-Arch hints.
   * Merge DEB_BUILD_OPTIONS with DEB_BUILD_MAINT_OPTIONS
   * Make blhc pass, by adding a ignore line.
 .
   [ Matthias Klose ]
   * Mark two more symbols as optional. (Closes: #996952)
 .
   [ Sandro Knauß ]
   * No need to forward Debian internal patches.
   * Update symbols
Checksums-Sha1:
 d498658783bda7050b0bce8c380b532b116e9c0b 2506 libkolabxml_1.2.0-3.dsc
 3e7bfc684ca022978e2231418037df6e15bc0ed6 56192 
libkolabxml_1.2.0-3.debian.tar.xz
Checksums-Sha256:
 e92cfe58922a953f335f31133c90a4efbb0ad337ba676d0d2e2264384b074c86 2506 
libkolabxml_1.2.0-3.dsc
 daab7db859049f4dbeb84e7b379e61575118d459a9f50da423b483959e127ea0 56192 
libkolabxml_1.2.0-3.debian.tar.xz
Files:
 c3ccb6efaf2bfb27e92983f6d1568d4c 2506 libs optional libkolabxml_1.2.0-3.dsc
 aaa784190ee75450536cd12125c92aec 56192 libs optional 
libkolabxml_1.2.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmF//5YRHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjYXExAAr2/yeAvcV52bAZGshR9uZe9SGR3PBeGN
JiHcWcxRxCyEb7N25rE4pTT0taaXAPmhM0tF6C4hVHHuUtIHggds+JY1ShCit4MW
T6l6ZEsQJHJQ+jpksF+Fl2a1TVBnaxgrvKv/ctBPQaAhVJXhAmMIsYQzAMD7mguJ
BIl7S2XXAVVZeovF4eHQv0zoAEWTB+L76PQgl1Y5RDxEIBDQpQXYbuQk30FGZLZV
dvncUD9sOCIjH0TN+SmTbyq/k4bD7aNBxk0JLFMTM4F4k8gU9xzq1M/UZN4Eeccw
kixHd5T6L+fKynKOJrfOKfEW1D3Gj1aPcK7Vg96+iGAdrvg/35F7TTCvCgGqlulG
QmkylNMvXDic/1PMIF07/IUD/8hqCYk0IK9TkFlpzpRU09QUucI/NDACjOcXWWrb
EyydhWehQXI/GFMYYkQzEtS736p8p9I3XX5LhbAru3KjRuUdKKkufBf3EhBTwM+z
LbjNIhGfCoOfWIhyv6lBLzWrP32qcGhGygVW0zJjU0IfQwOGsrt2eCtL8Y/YSkJO
uP8D1qhKTsiDr+5w/kdkcncJ4fMNIm5B8tmr4/I/IUHYZxPI9eO0hUKCe/rXFu/+
0aA3ZE8WmQY+IGNORtCt3JPvJJdNYLA3YlRcsEi/FT6ljYSBKXhUYyl1HPJmF5Ck
8mK7liBbYlg=
=5U/r
-END PGP SIGNATURE End Message ---

Bug#984015: marked as done (cif-tools: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 14:49:08 +
with message-id 
and subject line Bug#984015: fixed in cif-tools 1.0.0-4
has caused the Debian Bug report #984015,
regarding cif-tools: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cif-tools
Version: 1.0.0-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/cif-tools_1.0.0-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
mkdir -p obj
>> src/pdb2cif.cpp
>> src/cif2pdb.cpp
>> src/cif-diff.cpp
>> src/cif-drop.cpp
In file included from src/cif2pdb.cpp:41:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from src/pdb2cif.cpp:42:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from src/cif-drop.cpp:40:
/usr/include/cif++/Cif++.hpp:461:50: error: ‘optional’ is not a member of ‘std’
  461 | struct ItemReference::item_value_as>
  |  ^~~~
/usr/include/cif++/Cif++.hpp:41:1: note: ‘std::optional’ is defined in header 
‘’; did you forget to ‘#include ’?
   40 | #include "cif++/CifUtils.hpp"
  +++ |+#include 
   41 | 
/usr/include/cif++/Cif++.hpp:461:59: error: template argument 1 is invalid
  461 | struct ItemReference::item_value_as>
  |   ^
/usr/include/cif++/Cif++.hpp:461:60: error: expected unqualified-id before ‘>’ 
token
  461 | struct ItemReference::item_value_as>
  |^~
In file included from 

Bug#998156: contains non-DFSG-free files

[Henry Cejtin]

(I assume you meant ml-nlffigen.)  ml-nlffigen is part of SML/NJ, not
part of MLton.

On Mon, Nov 1, 2021 at 8:34 AM Florian Weimer  wrote:
>
> * Henry Cejtin:
>
> > As far as I know, the ckit stuff is just included because it needed
> > some tweaks to work under MLton.
> > I don't think that any of "our" stuff depends on it.
>
> I think mlnffigen needs ckit.

Bug#997651: marked as done (python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not callable)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 14:30:03 +
with message-id 
and subject line Bug#997651: fixed in python-ara 1.5.7-1
has caused the Debian Bug report #997651,
regarding python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not 
callable
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.)


-- 
997651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ara
Version: 1.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYTHON=python3 python3 -m sphinx -b html doc/source 
> debian/python-ara-doc/usr/share/doc/python-ara-doc/html
> Running Sphinx v4.2.0
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 18 source files that are out of date
> updating environment: [new config] 18 added, 0 changed, 0 removed
> reading sources... [  5%] ansible-configuration
> reading sources... [ 11%] ansible-role-ara-api
> reading sources... [ 16%] ansible-role-ara-web
> reading sources... [ 22%] api-configuration
> reading sources... [ 27%] api-documentation
> reading sources... [ 33%] api-security
> reading sources... [ 38%] api-usage
> reading sources... [ 44%] ara-api-lookup
> reading sources... [ 50%] ara-manage
> reading sources... [ 55%] ara-plugin-configuration
> reading sources... [ 61%] ara-record
> reading sources... [ 66%] container-images
> reading sources... [ 72%] contributing
> reading sources... [ 77%] distributed-sqlite-backend
> reading sources... [ 83%] faq
> reading sources... [ 88%] index
> reading sources... [ 94%] installation
> reading sources... [100%] playbook-names-and-labels
> 
> /<>/doc/source/ara-manage.rst:25: WARNING: Command 'ara-manage 
> --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:32: WARNING: Command 'ara-manage 
> prune --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:41: WARNING: Command 'ara-manage 
> changepassword --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:48: WARNING: Command 'ara-manage 
> createsuperuser --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:55: WARNING: Command 'ara-manage 
> makemigrations --help' failed: [Errno 2] No such file or directory: 
> 'ara-manage'
> /<>/doc/source/ara-manage.rst:64: WARNING: Command 'ara-manage 
> migrate --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:76: WARNING: Command 'ara-manage 
> runserver --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> /<>/doc/source/ara-manage.rst:86: WARNING: Command 'ara-manage 
> generate --help' failed: [Errno 2] No such file or directory: 'ara-manage'
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  5%] ansible-configuration
> writing output... [ 11%] ansible-role-ara-api
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/highlighting.py", line 127, in 
> get_lexer
> lexer = lexer_classes[lang](**opts)
> TypeError: 'AnsibleYamlJinjaLexer' object is not callable
> The full traceback has been saved in /tmp/sphinx-err-9sp7oh5b.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:19: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-ara_1.4.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!

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-ara
Source-Version: 1.5.7-1
Done: 

Processed: owner 998238

[Debian Bug Tracking System]

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

> owner 998238 tmanc...@debian.org
Bug #998238 [src:syncany] syncany: FTBFS: Could not resolve 
commons-io:commons-io:2.4.
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#998238: syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.

[tony mancill]

On Mon, Nov 01, 2021 at 02:06:32PM +0100, Andreas Beckmann wrote:
> Source: syncany
> Version: 0.4.9~alpha-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Hi,
> 
> syncany recently started to FTBFS:

Hi Andreas,

Thank you for the bug report.  The recent upload of commons-io [1]
included this change to its POM:

+  
+
+  
+org.junit
+junit-bom
+5.7.2
+pom
+import
+  
+
+  

This, in turn, causes Gradle to look for junit5 during the build of
syncany.  I'm not certain that this build dependency should transitively
leak into projects that have build dependencies on commons-io, but
syncany builds again after adding junit5 to the build-deps, so the fix
is quite simple.

I will freshen a few other things in the package and upload later today.

Cheers,
tony

[1] 
https://tracker.debian.org/news/1269886/accepted-commons-io-2110-1-source-into-unstable/

Bug#998156: contains non-DFSG-free files

[Florian Weimer]

* Henry Cejtin:

> As far as I know, the ckit stuff is just included because it needed
> some tweaks to work under MLton.
> I don't think that any of "our" stuff depends on it.

I think mlnffigen needs ckit.

Bug#997484: marked as pending in sqlalchemy

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/sqlalchemy/-/commit/2e6b9b0c871247a2e06ddfd81aa0bd8c14ee0b57


Add missing python3-greenlet (build-)depends (Closes: #997484).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997484

Processed: Bug#997484 marked as pending in sqlalchemy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997484 [python3-sqlalchemy] python3-sqlalchemy: Undeclared dependency on 
python3-greenlet
Added tag(s) pending.

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

Bug#998241: cufflinks: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times

[Andreas Beckmann]

Source: cufflinks
Version: 2.2.1+dfsg.1-8
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

Hi,

cufflinks recently started to FTBFS:

   dh_autoreconf
sh: 1: svnversion: not found
configure.ac:113: error: AM_INIT_AUTOMAKE expanded multiple times
/usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
configure.ac:16: the top level
/usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
configure.ac:113: the top level
autom4te: error: /usr/bin/m4 failed with exit status: 1
aclocal: error: /usr/bin/autom4te failed with exit status: 1
autoreconf: error: aclocal failed with exit status: 1
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:10: binary] Error 25


Andreas


cufflinks_2.2.1+dfsg.1-8.log.gz
Description: application/gzip

Processed: tagging 984213

[Debian Bug Tracking System]

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

> tags 984213 + help
Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#997447: marked as done (libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 13:33:57 +
with message-id 
and subject line Bug#997447: fixed in libbpp-popgen 2.4.1-6
has caused the Debian Bug report #997447,
regarding libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
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.)


-- 
997447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-popgen
Version: 2.4.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
> --movedev debian/tmp/usr/include/* usr/include \
> --movedev debian/tmp/usr/lib/*/cmake 
> usr/lib/x86_64-linux-gnu \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libbpp-core-dev package exists.
>  --> libbpp-seq-dev package exists.
> set -e
> install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.a 
> debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so 
> debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8 
> debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu
> mv 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8.0.0 
> debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu
> PKGDEV=libbpp-popgen-dev
> PKGSHL=libbpp-popgen8
> install -d -m 755 debian/libbpp-popgen-dev/usr/include
> mv debian/tmp/usr/include/Bpp debian/libbpp-popgen-dev/usr/include
> install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake 
> debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libbpp-popgen8/DEBIAN/symbols doesn't match 
> completely debian/libbpp-popgen8.symbols.amd64
> --- debian/libbpp-popgen8.symbols.amd64 (libbpp-popgen8_2.4.1-5_amd64)
> +++ dpkg-gensymbolseF3Nca 2021-10-23 07:34:38.348480986 +
> @@ -61,6 +61,7 @@
>   _ZN3bpp11PopgenlibIOD1Ev@Base 2.4.1
>   _ZN3bpp11PopgenlibIOD2Ev@Base 2.4.1
>   _ZN3bpp11RandomTools9getSampleImEEvRKSt6vectorIT_SaIS3_EERS5_b@Base 2.4.1
> + 
> _ZN3bpp11VectorTools11countValuesINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESt3mapIT_mSt4lessIS9_ESaISt4pairIKS9_mEEERKSt6vectorIS9_SaIS9_EE@Base
>  2.4.1-5
>   _ZN3bpp11VectorTools3covIddEET0_RKSt6vectorIT_SaIS4_EES8_b@Base 2.4.1
>   
> _ZN3bpp11VectorTools6uniqueINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESt6vectorIT_SaIS9_EERKSB_@Base
>  2.4.1
>   _ZN3bpp11VectorTools6uniqueImEESt6vectorIT_SaIS3_EERKS5_@Base 2.4.1
> @@ -662,7 +663,7 @@
>   
> _ZN3bpp9TextTools8toStringIcEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEET_@Base
>  2.4.1
>   
> _ZN3bpp9TextTools8toStringIiEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEET_@Base
>  2.4.1
>   
> _ZN3bpp9TextTools8toStringImEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEET_@Base
>  2.4.1
> - _ZN3bppdvIdEESt6vectorIT_SaIS2_EERKS4_S6_@Base 2.4.1
> +#MISSING: 2.4.1-5# _ZN3bppdvIdEESt6vectorIT_SaIS2_EERKS4_S6_@Base 2.4.1
>   _ZN3bppdvIdiEESt6vectorIT_SaIS2_EERKS4_RKT0_@Base 2.4.1
>   _ZN3bppmiIdiEESt6vectorIT_SaIS2_EERKS4_RKT0_@Base 2.4.1
>   _ZN3bppmlIdEESt6vectorIT_SaIS2_EERKS4_S6_@Base 2.4.1
> @@ -759,6 +760,7 @@
>   _ZNK3bpp19VectorSiteContainer7valueAtEmm@Base 2.4.1
>   
> _ZNK3bpp19VectorSiteContainerclERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEm@Base
>  2.4.1
>   _ZNK3bpp19VectorSiteContainerclEmm@Base 2.4.1
> + _ZNK3bpp20AbstractCoreSequence11getCommentsB5cxx11Ev@Base 2.4.1-5
>   _ZNK3bpp20AbstractCoreSequence7getNameB5cxx11Ev@Base 2.4.1
>   

Bug#997444: marked as done (libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 13:33:51 +
with message-id 
and subject line Bug#997444: fixed in libbpp-phyl 2.4.1-6
has caused the Debian Bug report #997444,
regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-phyl
Version: 2.4.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
> --movedev debian/tmp/usr/include/* usr/include \
> --movedev debian/tmp/usr/lib/*/cmake 
> usr/lib/x86_64-linux-gnu \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libbpp-core-dev package exists.
>  --> libbpp-seq-dev package exists.
> set -e
> install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.a 
> debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so 
> debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12 
> debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12.0.0 
> debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu
> PKGDEV=libbpp-phyl-dev
> PKGSHL=libbpp-phyl12
> install -d -m 755 debian/libbpp-phyl-dev/usr/include
> mv debian/tmp/usr/include/Bpp debian/libbpp-phyl-dev/usr/include
> install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake 
> debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libbpp-phyl12/DEBIAN/symbols doesn't match 
> completely debian/libbpp-phyl12.symbols.amd64
> --- debian/libbpp-phyl12.symbols.amd64 (libbpp-phyl12_2.4.1-5_amd64)
> +++ dpkg-gensymbols4Wyklv 2021-10-23 07:11:36.721941783 +
> @@ -270,7 +270,7 @@
>   _ZN3bpp12TreeTemplateINS_4NodeEE9getNextIdEv@Base 2.4.1
>   _ZN3bpp12TreeTemplateINS_4NodeEE9scaleTreeEd@Base 2.4.1
>   _ZN3bpp12TreeTemplateINS_4NodeEEC1ERKNS_4TreeE@Base 2.4.1
> - _ZN3bpp12TreeTemplateINS_4NodeEEC1ERKS2_@Base 2.4.1
> +#MISSING: 2.4.1-5# _ZN3bpp12TreeTemplateINS_4NodeEEC1ERKS2_@Base 2.4.1
>   _ZN3bpp12TreeTemplateINS_4NodeEED0Ev@Base 2.4.1
>   _ZN3bpp12TreeTemplateINS_4NodeEED1Ev@Base 2.4.1
>   _ZN3bpp12WordAlphabetD0Ev@Base 2.4.1
> @@ -428,6 +428,9 @@
>   
> _ZN3bpp16ApplicationTools13displayResultIjEEvRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKT_@Base
>  2.4.1
>   
> _ZN3bpp16ApplicationTools18getStringParameterERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKSt3mapIS6_S6_St4lessIS6_ESaISt4pairIS7_S6_EEES8_S8_bi@Base
>  2.4.1
>   
> _ZN3bpp16ApplicationTools18getVectorParameterIiEESt6vectorIT_SaIS3_EERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKSt3mapISB_SB_St4lessISB_ESaISt4pairISC_SB_EEEccSD_SD_bb@Base
>  2.4.1
> + _ZN3bpp16BadCharExceptionD0Ev@Base 2.4.1-5
> + _ZN3bpp16BadCharExceptionD1Ev@Base 2.4.1-5
> + _ZN3bpp16BadCharExceptionD2Ev@Base 2.4.1-5
>   _ZN3bpp16BipartitionTools12areIdenticalERKNS_15BipartitionListEmS3_mb@Base 
> 2.4.1
>   _ZN3bpp16BipartitionTools13areCompatibleERKNS_15BipartitionListEmS3_mb@Base 
> 2.4.1
>   
> _ZN3bpp16BipartitionTools19MRPEncodeMultilabelERKSt6vectorIPNS_15BipartitionListESaIS3_EE@Base
>  2.4.1
> @@ -987,6 +990,7 @@
>   
> _ZN3bpp22AbstractTreeLikelihood38ConstNoPartitionBranchModelDescriptionD0Ev@Base
>  2.4.1
>   
> _ZN3bpp22AbstractTreeLikelihood38ConstNoPartitionBranchModelDescriptionD1Ev@Base
>  2.4.1
>   
> 

Bug#997413: marked as done (libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 13:34:03 +
with message-id 
and subject line Bug#997413: fixed in libbpp-qt 2.4.1-6
has caused the Debian Bug report #997413,
regarding libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-qt
Version: 2.4.1-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
> --movedev debian/tmp/usr/include/* usr/include \
> --movedev debian/tmp/usr/lib/*/cmake 
> usr/lib/x86_64-linux-gnu \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
>  --> libbpp-core-dev package exists.
>  --> libbpp-phyl-dev package exists.
>  --> qtdeclarative5-dev package exists.
> set -e
> install -d -m 755 debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libbpp-qt2/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.a 
> debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so 
> debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so.2 
> debian/libbpp-qt2/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so.2.0.0 
> debian/libbpp-qt2/usr/lib/x86_64-linux-gnu
> PKGDEV=libbpp-qt-dev
> PKGSHL=libbpp-qt2
> install -d -m 755 debian/libbpp-qt-dev/usr/include
> mv debian/tmp/usr/include/Bpp debian/libbpp-qt-dev/usr/include
> install -d -m 755 debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake 
> debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libbpp-qt2/DEBIAN/symbols doesn't match 
> completely debian/libbpp-qt2.symbols.amd64
> --- debian/libbpp-qt2.symbols.amd64 (libbpp-qt2_2.4.1-5_amd64)
> +++ dpkg-gensymbolsF9z94J 2021-10-23 07:35:46.410284620 +
> @@ -133,7 +133,7 @@
>   _ZN3bpp18MouseListenerGroupD0Ev@Base 2.4.1
>   _ZN3bpp18MouseListenerGroupD1Ev@Base 2.4.1
>   _ZN3bpp18MouseListenerGroupD2Ev@Base 2.4.1
> - 
> _ZN3bpp19AbstractTreeDrawing22addTreeDrawingListenerEPNS_19TreeDrawingListenerE@Base
>  2.4.1
> +#MISSING: 2.4.1-5# 
> _ZN3bpp19AbstractTreeDrawing22addTreeDrawingListenerEPNS_19TreeDrawingListenerE@Base
>  2.4.1
>   _ZN3bpp19AbstractTreeDrawing8setXUnitEd@Base 2.4.1
>   _ZN3bpp19AbstractTreeDrawing8setYUnitEd@Base 2.4.1
>   _ZN3bpp19TreeDrawingNodeInfoD0Ev@Base 2.4.1
> @@ -185,6 +185,7 @@
>   
> _ZN3bpp21AbstractGraphicDevice25setCurrentForegroundColorERKNS_8RGBColorE@Base
>  2.4.1
>   _ZN3bpp21AbstractGraphicDevice8setXUnitEd@Base 2.4.1
>   _ZN3bpp21AbstractGraphicDevice8setYUnitEd@Base 2.4.1
> + _ZN3bpp21AbstractGraphicDeviceC2Ev@Base 2.4.1-5
>   _ZN3bpp21AbstractGraphicDeviceD2Ev@Base 2.4.1
>   _ZN3bpp21NodeNotFoundExceptionD0Ev@Base 2.4.1
>   _ZN3bpp21NodeNotFoundExceptionD1Ev@Base 2.4.1
> @@ -391,17 +392,19 @@
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
>  2.4.1
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
>  2.4.1
>   
> _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
>  2.4.1
> - 
> _ZNSt6vectorIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
>  2.4.1
> +#MISSING: 2.4.1-5# 
> _ZNSt6vectorIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
>  2.4.1
>   
> 

Bug#997202: marked as done (deepin-movie-reborn: FTBFS: compositing_manager.cpp:48:10: fatal error: mpv/qthelper.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 13:33:28 +
with message-id 
and subject line Bug#997202: fixed in deepin-movie-reborn 5.7.15-1
has caused the Debian Bug report #997202,
regarding deepin-movie-reborn: FTBFS: compositing_manager.cpp:48:10: fatal 
error: mpv/qthelper.hpp: 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.)


-- 
997202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-movie-reborn
Version: 5.7.6.147-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src/libdmr && /usr/bin/c++ 
> -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -D_LIBDMR_ 
> -Ddmr_EXPORTS -I/<>/obj-x86_64-linux-gnu/src/libdmr 
> -I/<>/src/libdmr 
> -I/<>/obj-x86_64-linux-gnu/src/libdmr/dmr_autogen/include 
> -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/<>/src/ON -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src/libdmr/ON -I/<>/src/libdmr/../common 
> -I/<>/src/libdmr/../backends/mpv -isystem 
> /usr/include/libdtk-5.2.2/DCore/../DWidget -isystem 
> /usr/include/libdtk-5.2.2/DCore/../DGui -isystem 
> /usr/include/libdtk-5.2.2/DCore -isystem /usr/include/x86_64-linux-gnu/qt5 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -O3 
> -DNDEBUG -fPIC -fPIC -MD -MT src/libdmr/CMakeFiles/dmr.dir/dvd_utils.cpp.o 
> -MF CMakeFiles/dmr.dir/dvd_utils.cpp.o.d -o 
> CMakeFiles/dmr.dir/dvd_utils.cpp.o -c 
> /<>/src/libdmr/dvd_utils.cpp
> AutoMoc: Reading dependencies from 
> "SRC:/obj-x86_64-linux-gnu/src/deepin-movie_autogen/P66WHCG54J/moc_thumbnail_worker.cpp.d"
> AutoMoc: Generating 
> "SRC:/obj-x86_64-linux-gnu/src/deepin-movie_autogen/QKKKL5DD5S/moc_online_sub.cpp",
>  because it doesn't exist, from "SRC:/src/libdmr/online_sub.h"
> /usr/lib/qt5/bin/moc -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB 
> -DQT_X11EXTRAS_LIB -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src -I/<>/obj-x86_64-linux-gnu 
> -I/<> -I/<>/src/ON -I/<>/src/widgets 
> -I/<>/src/common -I/<>/src/libdmr 
> -I/<>/src/backends/mpv -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
> -I/usr/include/x86_64-linux-gnu/qt5/QtX11Extras 
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent 
> -I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
> -I/usr/include/x86_64-linux-gnu/qt5/QtSql -I/usr/include/libdtk-5.2.2/DWidget 
> -I/usr/include/libdtk-5.2.2/DGui -I/usr/include/libdtk-5.2.2/DCore 
> -I/usr/include/x86_64-linux-gnu/qt5/MprisQt 
> -I/usr/include/x86_64-linux-gnu/qt5/DBusExtended 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/c++/11 
> -I/usr/include/x86_64-linux-gnu/c++/11 -I/usr/include/c++/11/backward 
> -I/usr/lib/gcc/x86_64-linux-gnu/11/include -I/usr/local/include 
> -I/usr/include --include 
> /<>/obj-x86_64-linux-gnu/src/deepin-movie_autogen/moc_predefs.h 
> --output-dep-file -o 
> /<>/obj-x86_64-linux-gnu/src/deepin-movie_autogen/QKKKL5DD5S/moc_online_sub.cpp
>  /<>/src/libdmr/online_sub.h
> AutoMoc: Reading dependencies from 
> "SRC:/obj-x86_64-linux-gnu/src/deepin-movie_autogen/QKKKL5DD5S/moc_online_sub.cpp.d"
> AutoMoc: Generating 
> "SRC:/obj-x86_64-linux-gnu/src/deepin-movie_autogen/QKKKL5DD5S/moc_player_backend.cpp",
>  because it doesn't exist, from "SRC:/src/libdmr/player_backend.h"
> /usr/lib/qt5/bin/moc -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_WIDGETS_LIB 
> -DQT_X11EXTRAS_LIB -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src -I/<>/obj-x86_64-linux-gnu 
> -I/<> 

Bug#998240: texlive: causes lgrind to FTBFS

[Andreas Beckmann]

Package: texlive
Version: 2021.20210921-1
Severity: serious
Tags: sid bookworm
Control: affects -1 + src:lgrind

Hi,

lgrind recently started to FTBFS:

latex lgrind.dtx
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./lgrind.dtx
LaTeX2e <2021-06-01> patch level 1
L3 programming layer <2021-08-27>
(/usr/share/texlive/texmf-dist/tex/latex/base/ltxdoc.cls
Document Class: ltxdoc 2020/12/05 v2.1b Standard LaTeX documentation class
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2021/02/12 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/base/doc.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)))
Writing index file lgrind.idx
Writing glossary file lgrind.glo
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def)
No file lgrind.aux.
(./lgrind.dtx [1] [2] [3] [4] [5]
(/usr/share/texlive/texmf-dist/tex/latex/base/ts1cmtt.fd) [6] [7]

LaTeX Warning: Reference `underscore' on page 8 undefined on input line 461.

[8]
! Missing } inserted.
 
}
l.540 % \item[\^] 
  The beginning of a line
?
! Emergency stop.
 
}
l.540 % \item[\^] 
  The beginning of a line
Output written on lgrind.dvi (8 pages, 27616 bytes).
Transcript written on lgrind.log.
make: *** [debian/rules:13: build-stamp] Error 1


The offending line + some context:

 537 % The meta-symbols and their meanings are:
 538 % \begin{description}
 539 % \item[\$] The end of a line
 540 % \item[\^] The beginning of a line
 541 % \item[$\backslash$d] A delimiter (space, tab, newline, start of line)
 542 % \item[$\backslash$a] Matches any string of symbols (like `.*' in lex)
 543 % \item[$\backslash$p] Matches any identifier. In a procedure definition


I'm not sure which package is responsible for that ... starting with 'texlive'
which is the only relevant B-D of lgrind. Please reassign as needed.


Andreas


lgrind_3.67-4.log.gz
Description: application/gzip

Processed: texlive: causes lgrind to FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:lgrind
Bug #998240 [texlive] texlive: causes lgrind to FTBFS
Added indication that 998240 affects src:lgrind

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

Bug#997443: marked as done (libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 01 Nov 2021 13:18:29 +
with message-id 
and subject line Bug#997443: fixed in libbpp-core 2.4.1-7
has caused the Debian Bug report #997443,
regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
997443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbpp-core
Version: 2.4.1-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_install
> d-shlibmove --commit \
>   --multiarch \
>   --devunversioned \
>   --exclude-la \
> --movedev debian/tmp/usr/include/* usr/include \
> --movedev debian/tmp/usr/lib/*/cmake 
> usr/lib/x86_64-linux-gnu \
> debian/tmp/usr/lib/*/*.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libbpp-core4/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.a 
> debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so 
> debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4 
> debian/libbpp-core4/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4.1.0 
> debian/libbpp-core4/usr/lib/x86_64-linux-gnu
> PKGDEV=libbpp-core-dev
> PKGSHL=libbpp-core4
> install -d -m 755 debian/libbpp-core-dev/usr/include
> mv debian/tmp/usr/include/Bpp debian/libbpp-core-dev/usr/include
> install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake 
> debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match 
> completely debian/libbpp-core4.symbols.amd64
> --- debian/libbpp-core4.symbols.amd64 (libbpp-core4_2.4.1-6_amd64)
> +++ dpkg-gensymbolsRNzVfi 2021-10-23 07:25:01.267809587 +
> @@ -74,7 +74,7 @@
>   _ZN3bpp11MatrixTools3powINS_9RowMatrixIdvRKT_mRS4_@Base 2.4.1
>   _ZN3bpp11MatrixTools3powIdEEvRKNS_6MatrixIT_EEdRS4_@Base 2.4.1
>   _ZN3bpp11MatrixTools4copyINS_9RowMatrixIdEES3_EEvRKT_RT0_@Base 2.4.1
> - 
> _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EERKSt6vectorIS3_SaIS3_EES6_RS4_@Base
>  2.4.1
> +#MISSING: 2.4.1-6# 
> _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EERKSt6vectorIS3_SaIS3_EES6_RS4_@Base
>  2.4.1
>   _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EES6_RS4_@Base 2.4.1
>   _ZN3bpp11MatrixTools5covarIdEEvRKNS_6MatrixIT_EERS4_@Base 2.4.1
>   _ZN3bpp11RandomTools12randGaussianEddRKNS_13RandomFactoryE@Base 2.4.1
> @@ -106,6 +106,7 @@
>   _ZN3bpp11Uniform01QDD1Ev@Base 2.4.1
>   _ZN3bpp11VectorTools3covIddEET0_RKSt6vectorIT_SaIS4_EES8_b@Base 2.4.1
>   _ZN3bpp11VectorTools4testEv@Base 2.4.1
> + 
> _ZN3bpp11VectorTools5pasteIjEENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKSt6vectorIT_SaIS9_EERKS7_@Base
>  2.4.1-6
>   _ZN3bpp11VectorTools6breaksERKSt6vectorIdSaIdEEj@Base 2.4.1
>   _ZN3bpp11VectorTools6sumExpIdEET_RKSt6vectorIS2_SaIS2_EES7_@Base 2.4.1
>   _ZN3bpp12BracketPointD0Ev@Base 2.4.1
> @@ -1980,7 +1981,7 @@
>   _ZNK3bpp7Simplex5cloneEv@Base 2.4.1
>   _ZNK3bpp8RGBColor5cloneEv@Base 2.4.1
>   _ZNK3bpp8RGBColor5toHexB5cxx11Ev@Base 2.4.1
> - _ZNK3bpp8RGBColorltERKS0_@Base 2.4.1
> +#MISSING: 2.4.1-6# _ZNK3bpp8RGBColorltERKS0_@Base 2.4.1
>   _ZNK3bpp9BppString5cloneEv@Base 2.4.1
>   _ZNK3bpp9BppString5toSTLB5cxx11Ev@Base 2.4.1
>   _ZNK3bpp9ColMatrixIdE15getNumberOfRowsEv@Base 2.4.1
> @@ -2164,7 +2165,8 @@
>   
> _ZNSt3mapIKN3bpp8RGBColorENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4lessIS2_ESaISt4pairIS2_S8_EEEixERS2_@Base
>  2.4.1
>   
> 

Bug#998238: syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.

[Andreas Beckmann]

Source: syncany
Version: 0.4.9~alpha-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

syncany recently started to FTBFS:

:syncany-lib:debianMavenPom (Thread[Task worker for ':',5,main]) started.
:syncany-lib:debianMavenPom
Putting task artifact state for task ':syncany-lib:debianMavenPom' into context 
took 0.0 secs.
Up-to-date check for task ':syncany-lib:debianMavenPom' took 0.0 secs. It is 
not up-to-date because:
  No history is available.
Passing through org.junit:junit-bom:jar:debian
Replacing org.hsqldb:hsqldb:jar:2.3.1  ->  org.hsqldb:hsqldb:jar:debian
Replacing javax.xml.bind:jaxb-api:jar:2.3.1  ->  
javax.xml.bind:jaxb-api:jar:debian
Passing through javax.xml.bind:jaxb-api-parent:jar:debian
Passing through javax.activation:javax.activation-api:jar:debian
javax.activation:javax.activation-api:debian is relocated to 
com.sun.activation:javax.activation:debian. Please update your dependencies.
Passing through com.sun.activation:javax.activation:jar:debian
Passing through com.sun.activation:all:jar:debian
:syncany-util:compileJava FAILED
:syncany-util:compileJava (Thread[Daemon worker,5,main]) completed. Took 0.248 
secs.
Generating pom file 
/build/syncany-0.4.9~alpha/syncany-lib/build/debian/syncany-lib.pom
:syncany-lib:debianMavenPom (Thread[Task worker for ':',5,main]) completed. 
Took 0.095 secs.
:syncany-cli:processResources (Thread[Task worker for ':' Thread 2,5,main]) 
completed. Took 0.507 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':syncany-util:compileClasspath'.
> Could not resolve commons-io:commons-io:2.4.
  Required by:
  project :syncany-util
   > Could not resolve commons-io:commons-io:2.4.
  > Could not parse POM 
/usr/share/maven-repo/commons-io/commons-io/debian/commons-io-debian.pom
 > Could not resolve org.junit:junit-bom:debian.
> No cached version of org.junit:junit-bom:debian available for 
offline mode.
> No cached version of org.junit:junit-bom:debian available for 
offline mode.
   > No cached version of commons-io:commons-io:2.4 available for offline mode.
   > No cached version of commons-io:commons-io:2.4 available for offline mode.

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException:
 Could not resolve all files for configuration ':syncany-util:compileClasspath'.


Andreas


syncany_0.4.9~alpha-3.log.gz
Description: application/gzip

Bug#998237: arb: FTBFS with glibc 2.32 due to rpc header removal

[Andreas Beckmann]

Source: arb
Version: 6.0.6-4
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

Hi,

arb FTBFS in sid:

g++ -fPIC -g -O2 -ffile-prefix-map=/build/arb-6.0.6=. -fstack-protector-strong 
-Wformat -Werror=format-security -O3 -pipe -fmessage-length=0 -fshow-column 
-funit-at-a-time -fPIC -fno-common -fstrict-aliasing 
-fno-diagnostics-show-caret -rdynamic -W -Wall -DNDEBUG -DDEVEL_RELEASE 
-DARB_64  -DLINUX   -DIN_ARB_ARBDB -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 
-c arbdb.cxx -I. -I/build/arb-6.0.6/INCLUDE -I/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include
arbdb.cxx:15:10: fatal error: rpc/types.h: No such file or directory
compilation terminated.
make[5]: *** [Makefile:74: arbdb.o] Error 1

rpc/types.h is no longer shipped by libc6-dev, please use libtirpc-dev
and -I/usr/include/tirpc instead.


Andreas


arb_6.0.6-4.log.gz
Description: application/gzip