[bts-link] source package src:lasi

2021-11-04 Thread debian-bts-link
#
# bts-link upstream status pull for source package src:lasi
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #984083 (http://bugs.debian.org/984083)
# Bug title: lasi: ftbfs with GCC-11
#  * https://sourceforge.net/p/lasi/bugs/9/
#  * remote status changed: (?) -> open
usertags 984083 + status-open

thanks



Bug#998487: glogic: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times

2021-11-04 Thread Lucas Nussbaum
Source: glogic
Version: 2.6-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3
>dh_update_autotools_config
>dh_autoreconf
> configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times
> /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> configure.ac:3: the top level
> /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> configure.ac:12: the top level
> autom4te: error: /usr/bin/m4 failed with exit status: 1
> aclocal: error: /usr/bin/autom4te failed with exit status: 1
> autoreconf: error: aclocal failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/glogic_2.6-5_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.



Bug#998508: deb-gview: FTBFS: configure.ac:25: error: AM_INIT_AUTOMAKE expanded multiple times

2021-11-04 Thread Lucas Nussbaum
Source: deb-gview
Version: 0.2.11.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
> configure.ac:25: error: AM_INIT_AUTOMAKE expanded multiple times
> /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> configure.ac:24: the top level
> /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from...
> configure.ac:25: the top level
> autom4te: error: /usr/bin/m4 failed with exit status: 1
> aclocal: error: /usr/bin/autom4te failed with exit status: 1
> autoreconf: error: aclocal failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:6: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/deb-gview_0.2.11.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.



Bug#998530: python-jenkinsapi: FTBFS: Unable to create file /sbuild-nonexistent/.cache/pylint/jenkinsapi.views1.stats: [Errno 2] No such file or directory: '/sbuild-nonexistent/.cache/pylint/jenkinsap

2021-11-04 Thread Lucas Nussbaum
Source: python-jenkinsapi
Version: 0.3.11-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 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 '/<>'
> pylint jenkinsapi/*.py
> * Module jenkinsapi.api
> jenkinsapi/api.py:83: [C0209(consider-using-f-string), get_artifacts] 
> Formatting a regular string which could be a f-string
> jenkinsapi/api.py:108: [C0209(consider-using-f-string), search_artifacts] 
> Formatting a regular string which could be a f-string
> jenkinsapi/api.py:148: [C0209(consider-using-f-string), block_until_complete] 
> Formatting a regular string which could be a f-string
> jenkinsapi/api.py:155: [C0209(consider-using-f-string), block_until_complete] 
> Formatting a regular string which could be a f-string
> jenkinsapi/api.py:165: [C0209(consider-using-f-string), get_view_from_url] 
> Formatting a regular string which could be a f-string
> jenkinsapi/api.py:179: [C0209(consider-using-f-string), 
> get_nested_view_from_url] Formatting a regular string which could be a 
> f-string
> * Module jenkinsapi.artifact
> jenkinsapi/artifact.py:42: [C0209(consider-using-f-string), Artifact.save] 
> Formatting a regular string which could be a f-string
> jenkinsapi/artifact.py:103: [C0209(consider-using-f-string), 
> Artifact._verify_download] Formatting a regular string which could be a 
> f-string
> jenkinsapi/artifact.py:136: [C0209(consider-using-f-string), 
> Artifact.__repr__] Formatting a regular string which could be a f-string
> * Module jenkinsapi.build
> jenkinsapi/build.py:85: [C0209(consider-using-f-string), Build.get_revision] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:88: [C0209(consider-using-f-string), 
> Build.get_revision_branch] Formatting a regular string which could be a 
> f-string
> jenkinsapi/build.py:91: [C0209(consider-using-f-string), Build.get_repo_url] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:226: [C0209(consider-using-f-string), 
> Build.get_artifacts] Formatting a regular string which could be a f-string
> jenkinsapi/build.py:420: [C0209(consider-using-f-string), 
> Build.block_until_complete] Formatting a regular string which could be a 
> f-string
> jenkinsapi/build.py:442: [C0209(consider-using-f-string), 
> Build.get_resultset] Formatting a regular string which could be a f-string
> jenkinsapi/build.py:494: [C0209(consider-using-f-string), Build.get_console] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:510: [C0209(consider-using-f-string), Build.stream_logs] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:544: [C0209(consider-using-f-string), Build.stop] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:560: [C0209(consider-using-f-string), Build.get_env_vars] 
> Formatting a regular string which could be a f-string
> jenkinsapi/build.py:573: [C0209(consider-using-f-string), Build.toggle_keep] 
> Formatting a regular string which could be a f-string
> * Module jenkinsapi.credentials
> jenkinsapi/credentials.py:45: [C0209(consider-using-f-string), 
> Credentials.__str__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:72: [C0209(consider-using-f-string), 
> Credentials.__getitem__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:93: [C0209(consider-using-f-string), 
> Credentials.__setitem__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:110: [C0209(consider-using-f-string), 
> Credentials.__setitem__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:133: [C0209(consider-using-f-string), 
> Credentials.__delitem__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:138: [C0209(consider-using-f-string), 
> Credentials.__delitem__] Formatting a regular string which could be a f-string
> jenkinsapi/credentials.py:212: [C0209(consider-using-f-string), 
> CredentialsById.__getitem__] Formatting a regular string which could be a 
> f-string
> * Module jenkinsapi.executor
> jenkinsapi/executor.py:33: [C0209(consider-using-f-string), Executor.__str__] 
> Formatting a regular string which could be a f-string
> * Module jenkinsapi.executors
> jenkinsapi/executors.py:29: [C0209(consider-using-f-string), 
> Executors.__str__] Formatting a regular string which could be a f-string
> jenkinsapi/executors.py:36: [C0209(consider-using-f-string), 
> Executors.__iter__] Formatti

golang-github-lunny-nodb is marked for autoremoval from testing

2021-11-04 Thread Debian testing autoremoval watch
golang-github-lunny-nodb 0.0~git20160621.0.fc1ef06-5 is marked for autoremoval 
from testing on 2021-12-10

It (build-)depends on packages with these RC bugs:
997965: golang-github-siddontang-go-snappy: fails to migrate to testing for too 
long: uploader built arch:all binaries
 https://bugs.debian.org/997965



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl



golang-github-siddontang-go-snappy is marked for autoremoval from testing

2021-11-04 Thread Debian testing autoremoval watch
golang-github-siddontang-go-snappy 0.0~git20140704.0.d8f7bb8-5 is marked for 
autoremoval from testing on 2021-12-10

It is affected by these RC bugs:
997965: golang-github-siddontang-go-snappy: fails to migrate to testing for too 
long: uploader built arch:all binaries
 https://bugs.debian.org/997965



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl