Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-babel7&arch=all&ver=7.10.5%2B~cs65.71.38-2&stamp=1595148206&raw=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd babel-plugin-dynamic-import-node && babeljs-7 src --out-dir lib
ReferenceError: /<>/babel-plugin-dynamic-import-node/src/index.js:
isArray is not defined
at /usr/share/nodejs/lodash/_baseOrderBy.js:24:7
at arrayMap (/usr/share/nodejs/lodash/_arrayMap.js:19:21)
at baseOrderBy (/usr/share/nodejs/lodash/_baseOrderBy.js:23:17)
at /usr/share/nodejs/lodash/sortBy.js:48:10
at apply (/usr/share/nodejs/lodash/_apply.js:18:25)
at /usr/share/nodejs/lodash/_overRest.js:35:12
at PluginPass.exit
(/usr/share/nodejs/@babel/core/lib/transformation/block-hoist-plugin.js:58:43)
at newFn (/usr/share/nodejs/@babel/traverse/lib/visitors.js:175:21)
at NodePath._call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:42:17) {
code: 'BABEL_TRANSFORM_ERROR'
}
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
Bug#965352: libopenmpi3: breaks tests in client programs
Package: libopenmpi3
Version: 4.0.4-2
Severity: serious
Justification: breaks dependent packages
A number of packages have lately started failing debci tests,
in particular mpi4py and dolfin. dolfin is also failing some build-time
tests.
I've run mpi4py tests on debci for both testing and unstable. They're
still passing in testing, where openmpi is 4.0.4-1, but failing in
unstable with openmpi 4.0.4-2. I'm not absolutely certain, but it
seems like one of the changes in openmpi 4.0.4-2 might be making
problems.
Debci indicates that mpi4py 3.0.3-5 isn't passing
test/test_rma.py::TestRMASelf::testGetAccumulate
Test log in
https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mpi4py/6342921/log.gz
Apparently there's a segfault in an mpi test (single process test pass).
The problem can be reproduced at the command line in an mpi4py source
dir with python3-mpi4py installed (manual testing also shows
TestRMASelf::testStartComplete is failing, separate from
testGetAccumulate):
$ mpirun -n 2 python3 -m pytest test/test_rma.py -v
= test session starts ==
platform linux -- Python 3.8.4, pytest-4.6.11, py-1.8.1, pluggy-0.13.0 --
/usr/bin/python3
= test session starts ==
platform linux -- Python 3.8.4, pytest-4.6.11, py-1.8.1, pluggy-0.13.0 --
/usr/bin/python3
cachedir: .pytest_cache
hypothesis profile 'default' ->
database=DirectoryBasedExampleDatabase('/home/drew/projects/python/build/mpi4py/.hypothesis/examples')
rootdir: /home/drew/projects/python/build/mpi4py, inifile: setup.cfg
plugins: xdist-1.32.0, doctestplus-0.7.0, astropy-header-0.1.2,
filter-subpackage-0.1.1, cov-2.8.1, remotedata-0.3.2, mpi-0+unknown,
forked-1.2.0, arraydiff-0.3, openfiles-0.5.0, hypothesis-5.16.0
collecting ... cachedir: .pytest_cache
hypothesis profile 'default' ->
database=DirectoryBasedExampleDatabase('/home/drew/projects/python/build/mpi4py/.hypothesis/examples')
rootdir: /home/drew/projects/python/build/mpi4py, inifile: setup.cfg
plugins: xdist-1.32.0, doctestplus-0.7.0, astropy-header-0.1.2,
filter-subpackage-0.1.1, cov-2.8.1, remotedata-0.3.2, mpi-0+unknown,
forked-1.2.0, arraydiff-0.3, openfiles-0.5.0, hypothesis-5.16.0
collected 36 items
collected 36 items
test/test_rma.py::TestRMASelf::testAccumulate
test/test_rma.py::TestRMASelf::testAccumulate PASSED [ 2%]
test/test_rma.py::TestRMASelf::testAccumulateProcNullReplace PASSED
[ 2%]PASSED [ 5%]
test/test_rma.py::TestRMASelf::testAccumulateProcNullSum
test/test_rma.py::TestRMASelf::testAccumulateProcNullReplace PASSED [
8%]PASSED [ 5%]
test/test_rma.py::TestRMASelf::testCompareAndSwap
test/test_rma.py::TestRMASelf::testAccumulateProcNullSum PASSED [
8%]PASSED
[ 11%]test/test_rma.py::TestRMASelf::testCompareAndSwap
test/test_rma.py::TestRMASelf::testFence PASSED [ 13%]
test/test_rma.py::TestRMASelf::testFenceAll PASSED [ 16%]
test/test_rma.py::TestRMASelf::testFetchAndOp PASSED [ 19%]
test/test_rma.py::TestRMASelf::testFlush PASSED [ 22%]
test/test_rma.py::TestRMASelf::testGetAccumulate PASSED [ 25%]
test/test_rma.py::TestRMASelf::testGetAccumulateProcNull PASSED [ 27%]
test/test_rma.py::TestRMASelf::testGetProcNull PASSED[ 30%]
test/test_rma.py::TestRMASelf::testPostWait PASSED [ 33%]
test/test_rma.py::TestRMASelf::testPutGet PASSED [ 36%]
test/test_rma.py::TestRMASelf::testPutProcNull PASSED[ 38%]
test/test_rma.py::TestRMASelf::testStartComplete FAILED [ 41%]
test/test_rma.py::TestRMASelf::testStartCompletePostTest PASSED [ 44%]
test/test_rma.py::TestRMASelf::testStartCompletePostWait PASSED [ 47%]
test/test_rma.py::TestRMASelf::testSync PASSED [ 50%]
test/test_rma.py::TestRMAWorld::testAccumulate
--
Primary job terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--
--
mpirun noticed that process rank 1 with PID 0 on node monte exited on signal 11
(Segmentation fault).
--
The tests pass with mpirun -n 1.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU t
Bug#965174: marked as done (node-globby build depends on the babeljs provides that will not be in bullseye)
Your message dated Mon, 20 Jul 2020 11:04:50 +0530 with message-id and subject line node-babel7 now provides babeljs has caused the Debian Bug report #965174, regarding node-globby build depends on the babeljs provides that will not be in bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-globby Version: 7.1.1-2 Severity: serious Tags: ftbfs bullseye sid Control: block 960748 by -1 node-globby build depends on the babeljs provides that will not be in bullseye due to #960748. --- End Message --- --- Begin Message --- Closing. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
Bug#965176: marked as done (node-ramda build depends on the babeljs provides that will not be in bullseye)
Your message dated Mon, 20 Jul 2020 11:04:50 +0530 with message-id and subject line node-babel7 now provides babeljs has caused the Debian Bug report #965176, regarding node-ramda build depends on the babeljs provides that will not be in bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-ramda Version: 0.26.1+dfsg-2 Severity: serious Tags: ftbfs bullseye sid Control: block 960748 by -1 node-ramda build depends on the babeljs provides that will not be in bullseye due to #960748. --- End Message --- --- Begin Message --- Closing. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
Bug#963333: marked as done (python-sievelib: FTBFS: AttributeError: 'ParsedRequirement' object has no attribute 'match_markers')
Your message dated Mon, 20 Jul 2020 05:18:47 +
with message-id
and subject line Bug#960577: fixed in python-sievelib 1.1.1-3.2
has caused the Debian Bug report #960577,
regarding python-sievelib: FTBFS: AttributeError: 'ParsedRequirement' object
has no attribute 'match_markers'
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.)
--
960577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-sievelib
Version: 1.1.1-3.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py clean
> Traceback (most recent call last):
> File "setup.py", line 40, in
> INSTALL_REQUIRES = get_requirements(path.join(HERE, "requirements.txt"))
> File "setup.py", line 33, in get_requirements
> if req.match_markers():
> AttributeError: 'ParsedRequirement' object has no attribute 'match_markers'
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
> python3.8 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.8
> returned exit code 13
> make: *** [debian/rules:15: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/python-sievelib_1.1.1-3.1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-sievelib
Source-Version: 1.1.1-3.2
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
python-sievelib, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated python-sievelib 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, 06 Jul 2020 14:47:15 +0300
Source: python-sievelib
Architecture: source
Version: 1.1.1-3.2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
Changed-By: Adrian Bunk
Closes: 960577
Changes:
python-sievelib (1.1.1-3.2) unstable; urgency=low
.
* Non-maintainer upload.
* Backport upstream build fixes. (Closes: #960577)
Checksums-Sha1:
0657001bb5c4fbd27cdc59e44c1331cf1e64de98 2165 python-sievelib_1.1.1-3.2.dsc
963ab01d1ea133a90c5f96999130b5ccdef6f62d 4260
python-sievelib_1.1.1-3.2.debian.tar.xz
Checksums-Sha256:
a48f2d5a1bdc5b819144d91c03defbc2e652819a9ee66235acbc83a58e905d72 2165
python-sievelib_1.1.1-3.2.dsc
64d05a485dedd2526fd6bfb57052dcc75775e4365d9d4510fbcfe8dda79cdf17 4260
python-sievelib_1.1.1-3.2.debian.tar.xz
Files:
cb0ed9d0f92add766c67451fdc7a811d 2165 python optional
python-sievelib_1.1.1-3.2.dsc
4cd1176721a8763617d36bacb4d47576 4260 python optional
python-sievelib_1.1.1-3.2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8DEREACgkQiNJCh6LY
mLGu8Q//X10V6c6gsPNbvJTFc6gFGzbDmugB2p6RpC5y3kDVy732rRV/QBtCu942
H0bWZOwsebaPTN8qrdg8qH77n6i0ehim+EEftVEiU++YqeamGMOW8Erk/hFIh/U9
DUDcG2jI8YI9nrJ/p1/4dGz72WwLrkxp+BkfPSDfiJiihJkUJMFWBqfdyCIMkcKz
rIdCScYVlN88YyJSj0M7OdoL7W8TnAO4AMHI+LI5Es2M0WQQ2H2hFhNd+dyGixVP
lY1TR4X38USFq3mMU1vnIv5iV75mVPlxORqJFMPozSgXR6HeOyT2yTMyXNnz+VLd
saqEJk8b6HoyufNNVwXIPrGwoK7zTvrMqGIbbQ02wPRLVLt09wmtQJKjdBsHsIYo
cjEUqxgs9vnKRyb7uYprwAm8EDHCEv3PfKicMQPO/bdXTKJ4X75vktzszwxcPFTz
HlzqbOftXy8au/x7A8uxv4IN1VbtvwN4cs8nXCimfr1yILjlU527neoePiM1h776
czdLymXxvQMfPVjrgO9+MDOLME0LXoQCTyMxUq4xkhUDGIsMeHazp9cdHsvV+9dW
UJlRIvx3TNM5WFaJPYMaDrK00+fRu8hSQxZdq8qn+oKKMDuxUxemg5WzyRPaeQRW
WtHPjHn7zxaVK3gHrDWfMJ+5KuISc/hHeQBQ
Bug#960577: marked as done (python-sievelib FTBFS with python3-pip 20.1)
Your message dated Mon, 20 Jul 2020 05:18:47 +
with message-id
and subject line Bug#960577: fixed in python-sievelib 1.1.1-3.2
has caused the Debian Bug report #960577,
regarding python-sievelib FTBFS with python3-pip 20.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.)
--
960577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-sievelib
Version: 1.1.1-3.1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-sievelib
...
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
Traceback (most recent call last):
File "setup.py", line 40, in
INSTALL_REQUIRES = get_requirements(path.join(HERE, "requirements.txt"))
File "setup.py", line 33, in get_requirements
if req.match_markers():
AttributeError: 'ParsedRequirement' object has no attribute 'match_markers'
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.8 setup.py clean
dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.8
returned exit code 13
make: *** [debian/rules:15: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: python-sievelib
Source-Version: 1.1.1-3.2
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
python-sievelib, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated python-sievelib 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, 06 Jul 2020 14:47:15 +0300
Source: python-sievelib
Architecture: source
Version: 1.1.1-3.2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team
Changed-By: Adrian Bunk
Closes: 960577
Changes:
python-sievelib (1.1.1-3.2) unstable; urgency=low
.
* Non-maintainer upload.
* Backport upstream build fixes. (Closes: #960577)
Checksums-Sha1:
0657001bb5c4fbd27cdc59e44c1331cf1e64de98 2165 python-sievelib_1.1.1-3.2.dsc
963ab01d1ea133a90c5f96999130b5ccdef6f62d 4260
python-sievelib_1.1.1-3.2.debian.tar.xz
Checksums-Sha256:
a48f2d5a1bdc5b819144d91c03defbc2e652819a9ee66235acbc83a58e905d72 2165
python-sievelib_1.1.1-3.2.dsc
64d05a485dedd2526fd6bfb57052dcc75775e4365d9d4510fbcfe8dda79cdf17 4260
python-sievelib_1.1.1-3.2.debian.tar.xz
Files:
cb0ed9d0f92add766c67451fdc7a811d 2165 python optional
python-sievelib_1.1.1-3.2.dsc
4cd1176721a8763617d36bacb4d47576 4260 python optional
python-sievelib_1.1.1-3.2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl8DEREACgkQiNJCh6LY
mLGu8Q//X10V6c6gsPNbvJTFc6gFGzbDmugB2p6RpC5y3kDVy732rRV/QBtCu942
H0bWZOwsebaPTN8qrdg8qH77n6i0ehim+EEftVEiU++YqeamGMOW8Erk/hFIh/U9
DUDcG2jI8YI9nrJ/p1/4dGz72WwLrkxp+BkfPSDfiJiihJkUJMFWBqfdyCIMkcKz
rIdCScYVlN88YyJSj0M7OdoL7W8TnAO4AMHI+LI5Es2M0WQQ2H2hFhNd+dyGixVP
lY1TR4X38USFq3mMU1vnIv5iV75mVPlxORqJFMPozSgXR6HeOyT2yTMyXNnz+VLd
saqEJk8b6HoyufNNVwXIPrGwoK7zTvrMqGIbbQ02wPRLVLt09wmtQJKjdBsHsIYo
cjEUqxgs9vnKRyb7uYprwAm8EDHCEv3PfKicMQPO/bdXTKJ4X75vktzszwxcPFTz
HlzqbOftXy8au/x7A8uxv4IN1VbtvwN4cs8nXCimfr1yILjlU527neoePiM1h776
czdLymXxvQMfPVjrgO9+MDOLME0LXoQCTyMxUq4xkhUDGIsMeHazp9cdHsvV+9dW
UJlRIvx3TNM5WFaJPYMaDrK00+fRu8hSQxZdq8qn+oKKMDuxUxemg5WzyRPaeQRW
WtHPjHn7zxaVK3gHrDWfMJ+5KuISc/hHeQBQ+OcsLbQcQjuXXZ8=
=xR0Y
-END PGP SIGNATURE End Message ---
Bug#965173: marked as done (node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye)
Your message dated Mon, 20 Jul 2020 10:27:12 +0530 with message-id and subject line node-babel7 now provides babeljs has caused the Debian Bug report #965173, regarding node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-rollup-plugin-buble Version: 0.19.8-2 Severity: serious Tags: ftbfs Control: block 960748 by -1 node-rollup-plugin-buble build depends on the babeljs provides that will not be in bullseye due to #960748. --- End Message --- --- Begin Message --- This can be closed now. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
Bug#964884: gplaycli does not seem to be suitable for stable releases
Correct me if I'm wrong Matlink, but I believe that this is the first Google API change/breakage in gplaycli's 4+ year history of being included in Debian? I'm not seeing a huge risk with allowing bullseye to release with this package (although obviously I can't predict the future). I know that the token dispenser breaks on a regular basis, but the package is still useful without that.
Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation
On Sat, 18 Jul 2020 at 12:04, Bart Van Assche wrote:
> Net-SNMP version 5.7.3, the version included in Debian, is no longer
> maintained upstream.
>
I just tested it on snmpd v5.8 released around July 2018 and it has this
issue too.
A patch has been applied to the Net-SNMP v5.8 and master branches that
> removes the EXTEND MIB from the list with default MIBs. See also commit
> c2b96ee74439 ("snmpd: Disable NET-SNMP-EXTEND-MIB support by default").
>
Is the single line removal in that commit all it needs? From what I can see
the patch for v5.8 and master branches is just importing c2b96ee74439
That will make things very easy to fix.
Since Net-SNMP already
> supports other mechanisms for extending snmpd, e.g. the extend and
> extendfix directives in snmpd.conf, I propose to disable the EXTEND MIB.
>
I'm happy to see it go, for the reasons you point out.
Oddly enough, if you set the user in the configuration file and set it on
the command line with the -u flag, the configuration file parameter wins.
root 41574 0.0 0.0 23592 13768 ?Ss 13:12 0:00
/usr/sbin/snmpd -LOw -u Debian-snmp -g Debian-snmp -I -smux mteTrigger
mteTriggerConf -f -p /run/snmpd.pid
- Craig
Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
On Mon, Jul 20, 2020 at 1:40 AM Yao Wei wrote: > There's a serious bug when I am uploading afdko package, that one of the > binaries in this package "tx" has name conflicting with > transifex-client. As transifex-client is client for the proprietary Transifex service, personally I would just add a conflict. Also talk to upstream about choosing a more appropriate name for the tx program, that is way too short even if it weren't conflicting with another package. Probably making all the commands in the afdko package subcommands of a new afdko command would be the way to go (similar to how git uses subcommands). -- bye, pabs https://wiki.debian.org/PaulWise
Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
Hi, There's a serious bug when I am uploading afdko package, that one of the binaries in this package "tx" has name conflicting with transifex-client. https://bugs.debian.org/965151 I am currently considering doing it by moving all binaries of afdko from /usr/bin to /usr/bin/afdko, and then creating another package afdko-legacy, that, similar to node-legacy before node changed the name to ax25-node, symlinks all binaries from /usr/bin/afdko back to /usr/bin. This will decrease the mess of one package having multiple binaries, and ensure the compatibility of font building scripts that invokes afdko tx. Does it require CTTE agreement since afdko-legacy is also in conflict with tx? Another python module package that's in my ITP also invokes afdko's tx: https://bugs.debian.org/962383 How other packages that depends on nodejs did when its name was nodejs? And how did they use nodejs on package building and/or run-time? Ref on nodejs vs node CTTE: https://lists.debian.org/debian-devel-announce/2012/07/msg2.html Thanks, Yao Wei signature.asc Description: PGP signature
Bug#965301: opendht FTBFS in unstable.
On Sun, Jul 19, 2020 at 03:30:18AM +0100, peter green wrote: > Secondly on architectures where the build can be attempted it is failing > with > > > [ 3%] Building CXX object CMakeFiles/opendht-static.dir/src/utils.cpp.o > > /usr/bin/c++ -DASIO_STANDALONE -DOPENDHT_LOG=true -DOPENDHT_PEER_DISCOVERY > > -DPACKAGE_VERSION=\"2.1.0\" -I/<>/. -I/<>/include > > -I/<>/include/opendht > > -I/<>/obj-x86_64-linux-gnu/include -g -O2 > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type > > -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden > > -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -fPIC > > -std=gnu++14 -o CMakeFiles/opendht-static.dir/src/utils.cpp.o -c > > /<>/src/utils.cpp > > In file included from /usr/include/msgpack/adaptor/cpp11/chrono.hpp:14, > > from /usr/include/msgpack/type.hpp:38, > > from /usr/include/msgpack.hpp:22, > > from /<>/include/opendht/utils.h:23, > > from /<>/src/utils.cpp:23: > > /usr/include/msgpack/v1/adaptor/cpp11/chrono.hpp:20:10: fatal error: > > boost/numeric/conversion/cast.hpp: No such file or directory > >20 | #include > > | ^~~ > > compilation terminated. > > I am ccing the msgpack-c maintainers in case this is a problem in that > package. Yes, in this case it is, since that code doesn't require explicit opt-in to use boost. I'll update libmsgpack-dev's Depends. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#965350: kgb-bot: autopkgtest makes assumption about exact merge commit message
Source: kgb-bot Version: 1.56-1 Tags: upstream Severity: serious Justification: tests fail with up-to-date Git Affects: src:git >From >https://ci.debian.net/data/autopkgtest/testing/amd64/k/kgb-bot/6323993/log.gz: | not ok 71 | | # Failed test at t/52-client-git.t line 393. | # got: 'Merge branch 'allnew' into master' | # expected: 'Merge branch 'allnew'' Can the test change to avoid hard-coding the merge commit message? By relaxing that test, it would be more likely to continue working as Git evolves over time. Relevant Git change: v2.28.0-rc0~15^2~9 (489947cee50, "fmt-merge-msg: stop treating `master` specially", 2020-06-23). Thanks, Jonathan
Bug#956523: mousetweaks ends with segmentation fault
Control: forwarded -1 https://gitlab.gnome.org/GNOME/mousetweaks/-/issues/8
On Sun, 12 Apr 2020 at 12:50:42 +0200, Gero Treuner wrote:
> I'm using Gnome with Wayland (but stacktrace doesn't look like the
> issue is in that area anyway).
mousetweaks only supports X11, not Wayland. Please use the "GNOME on Xorg"
session type if you require the mouse accessibility features that it
provides ("hover click" and "simulated secondary click").
The crash[1] appears to be because mousetweaks assumes that the default
GDK display is X11. There is a merge request available upstream[2]
to make it exit more or less gracefully when run in a Wayland session,
instead of just crashing.
However, it will likely never *work* under Wayland, because in a Wayland
environment, ordinary client programs do not have sufficient control over
the compositor to do what mousetweaks does. In a Wayland environment,
the mouse accessibility features that mousetweaks provides have to be
implemented as part of the compositor itself, which was done in GNOME
3.34.x (for both Wayland and X11) and will be available as part of
Debian 11.
[1] https://gitlab.gnome.org/GNOME/mousetweaks/-/issues/8
[2] https://gitlab.gnome.org/GNOME/mousetweaks/-/merge_requests/3
> It looks to me that mousetweaks is founded on outdated Gnome bases and
> is not fit to serve for this purpose anymore.
As far as I know, it should still work in an X11 environment, such as
"GNOME on Xorg". It's also used by the GNOME-derived Cinnamon environment,
which I believe is purely an X11 environment and does not implement a
Wayland compositor, for their equivalent feature.
On Sun, 19 Jul 2020 at 22:05:16 +0300, Emre Uyguroglu wrote:
> See [1]https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/269
> The package should be dropped, it still ships with SID and segfaults as well
> same functionality is provided by "gnome-control-center -> universal access->
> click assist" now
In testing/unstable, you are correct to say that GNOME no longer needs
this. A future gnome-control-center upload will remove the Recommends.
It seems to still be used by Cinnamon, so I've opened a separate bug
asking whether the Cinnamon maintainers want to take over maintenance
of mousetweaks. If they do not, then yes, it should probably be dropped.
smcv
Processed: Re: Bug#956523: mousetweaks ends with segmentation fault
Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/mousetweaks/-/issues/8 Bug #956523 [mousetweaks] mousetweaks ends with segmentation fault Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/mousetweaks/-/issues/8'. -- 956523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964623: pmdk: FTBFS: test failed
Control: block -1 by 964457 On Thu, Jul 09, 2020 at 01:27:34PM +0200, Lucas Nussbaum wrote: > Source: pmdk > Version: 1.8-1 > Severity: serious > Relevant part (hopefully): > > pmem_check_version@@LIBPMEM_1.0 This is caused by #964457 which appends decoration to symbols once if there should be none, or twice when there should be one. Meow. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i. ⠈⠳⣄
Bug#965278: meson 0.55.0 causes build failures
On Sat, 18 Jul 2020 at 20:12, Adrian Bunk wrote: > I cannot judge whether this is a meson regression, > or existing bugs that just happened to work with > older meson. I don't know much about the internals of gobject-introspection but this seems like a case of broken typelib files or paths to them. At least one of those bugs is related to Vala. A new version of Vala was uploaded at the beginning of this month. This might or might not be related.
Bug#936392: marked as done (dh-virtualenv: Python2 removal in sid/bullseye)
Your message dated Sun, 19 Jul 2020 21:19:19 + with message-id and subject line Bug#936392: fixed in dh-virtualenv 1.2.1-1 has caused the Debian Bug report #936392, regarding dh-virtualenv: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dh-virtualenv Version: 1.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:dh-virtualenv If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: dh-virtualenv Source-Version: 1.2.1-1 Done: Jyrki Pulliainen We believe that the bug you reported is fixed in the latest version of dh-virtualenv, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jyrki Pulliainen (supplier of updated dh-virtualenv 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, 19 Jul 2020 22:36:19 +0300 Source: dh-virtualenv Architecture: source Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Jyrki Pulliainen Changed-By: Jyrki Pulliainen Closes: 936392 Changes: dh-virtualenv (1.2.1-1) unstable; urgency=medium . * New upstream release (Closes: #936392) Checksums-Sha1: 15bcbb1c72463934eb8ad084d5709ca95aed2de6 1931 dh-virtualenv_1.2.1-1.dsc b37705eb919090c9ce5145d0a2ae72c1c5116ca8 62891 dh-virtualenv_1.2.1.orig.tar.gz 26973b40b3865b5b483101efb1f6cb9a4b04fdf1 2428 dh-virtualenv_1.2.1-1.debian.tar.xz ca8dd8cb2d5d6e02ebbc4d3aaaf162ae276a 7645 dh-virtualenv_1.2.1-1_amd64.buildinfo Checksums-Sha256: 39571447b046a10a9c1092e3b05276f8d7a2506948484f0aaad61c8ac1df609f 1931 dh-virtualenv_1.2.1-1.dsc 590057ecdf7fdec729d093dc52d395ad80fc110d53827cf53931eb3fb0557661 62891 dh-virtualenv_1.2.1.orig.tar.gz 9dd4a3e774b879fd57b0570c2963933fd580ecb5ff8
Processed: severity of 965332 is serious, tagging 965332
Processing commands for cont...@bugs.debian.org: > severity 965332 serious Bug #965332 [src:bluefish] bluefish: FTBFS on all: did not handle arch:all build well in debian/rules Severity set to 'serious' from 'grave' > tags 965332 + ftbfs Bug #965332 [src:bluefish] bluefish: FTBFS on all: did not handle arch:all build well in debian/rules Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 965332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942958: marked as done (dh-virtualenv: Python2 removal in sid/bullseye)
Your message dated Sun, 19 Jul 2020 21:19:19 + with message-id and subject line Bug#936392: fixed in dh-virtualenv 1.2.1-1 has caused the Debian Bug report #936392, regarding dh-virtualenv: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dh-virtualenv Version: 1.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: dh-virtualenv Source-Version: 1.2.1-1 Done: Jyrki Pulliainen We believe that the bug you reported is fixed in the latest version of dh-virtualenv, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jyrki Pulliainen (supplier of updated dh-virtualenv 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, 19 Jul 2020 22:36:19 +0300 Source: dh-virtualenv Architecture: source Version: 1.2.1-1 Distribution: unstable Urgency: medium Maintainer: Jyrki Pulliainen Changed-By: Jyrki Pulliainen Closes: 936392 Changes: dh-virtualenv (1.2.1-1) unstable; urgency=medium . * New upstream release (Closes: #936392) Checksums-Sha1: 15bcbb1c72463934eb8ad084d5709ca95aed2de6 1931 dh-virtualenv_1.2.1-1.dsc b37705eb919090c9ce5145d0a2ae72c1c5116ca8 62891 dh-virtualenv_1.2.1.orig.tar.gz 26973b40b3865b5b483101efb1f6cb9a4b04fdf1 2428 dh-virtualenv_1.2.1-1.debian.tar.xz ca8dd8cb2d5d6e02ebbc4d3aaaf162ae276a 7645 dh-virtualenv_1.2.1-1_amd64.buildinfo Checksums-Sha256: 39571447b046a10a9c1092e3b05276f8d7a2506948484f0aaad61c8ac1df609f 1931 dh-virtualenv_1.2.1-1.dsc 590057ecdf7fdec729d093dc52d395ad80fc110d53827cf53931eb3fb0557661 62891 dh-virtualenv_1.2.1.orig.tar.gz 9dd4a3e774b879fd57b0570c2963933fd580ecb5ff8eec9937f74e913085f64e 2428 dh-virtualenv_1.2.1-1.debian.tar.xz 128b789116922ee3fd33d0a0fcc50f6fab03fc51ad4ceee8a92fc5e02b8644bd 7645 dh-virtualenv_1.2.1-1_amd64.build
Bug#965306: marked as done (adplay: FTBFS: error: no matching function for call to ‘CSurroundopl::CSurroundopl(Copl*&, Copl*&, bool)’)
Your message dated Sun, 19 Jul 2020 20:43:44 + with message-id and subject line Bug#965306: fixed in adplay 1.8.1-1 has caused the Debian Bug report #965306, regarding adplay: FTBFS: error: no matching function for call to ‘CSurroundopl::CSurroundopl(Copl*&, Copl*&, bool)’ 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.) -- 965306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adplay Version: 1.8-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) adplay currently fails to build: | adplay.cc: In function ‘int main(int, char**)’: | adplay.cc:410:50: error: no matching function for call to ‘CSurroundopl::CSurroundopl(Copl*&, Copl*&, bool)’ | 410 | opl = new CSurroundopl(a, b, cfg.bits == 16); | | ^ | In file included from adplay.cc:52: | /usr/include/adplug/surroundopl.h:67:3: note: candidate: ‘CSurroundopl::CSurroundopl(COPLprops*, COPLprops*, bool)’ |67 | CSurroundopl(COPLprops *a, COPLprops *b, bool output16bit); | | ^~~~ | /usr/include/adplug/surroundopl.h:67:27: note: no known conversion for argument 1 from ‘Copl*’ to ‘COPLprops*’ |67 | CSurroundopl(COPLprops *a, COPLprops *b, bool output16bit); | |~~~^ | /usr/include/adplug/surroundopl.h:51:7: note: candidate: ‘constexpr CSurroundopl::CSurroundopl(const CSurroundopl&)’ |51 | class CSurroundopl: public Copl | | ^~~~ | /usr/include/adplug/surroundopl.h:51:7: note: candidate expects 1 argument, 3 provided See https://buildd.debian.org/status/fetch.php?pkg=adplay&arch=amd64&ver=1.8-2%2Bb1&stamp=1595115090&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: adplay Source-Version: 1.8.1-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of adplay, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated adplay 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, 19 Jul 2020 15:39:23 -0400 Source: adplay Architecture: source Version: 1.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Closes: 965306 Changes: adplay (1.8.1-1) unstable; urgency=medium . * QA upload. * New upstream maintenance upload. + Fix compatibility with new adplug. (Closes: #965306) * debian/control: Mark Rules-Requires-Root: no. Checksums-Sha1: fe94cf06cc12e91b5a15373f16bfe9bc7d917c08 1890 adplay_1.8.1-1.dsc 6b67cbd2bb6ddeccf529571a7fed328a587ec57a 4 adplay_1.8.1.orig.tar.gz 03d5398ca1b84790e72325510352006f2eaa5cc9 4028 adplay_1.8.1-1.debian.tar.xz 778c769d6c750352f14e2c1ecd2fdbb25538aef4 9868 adplay_1.8.1-1_amd64.buildinfo Checksums-Sha256: 2d1c2b80740a721ae9aa4268a6e5eb2775c184d13999d541dd7292f8bd78039c 1890 adplay_1.8.1-1.dsc 5fa1d475740bf88f5a618c1a79b52d1b0faf0c70b1c3f181114711fd2c84aa2d 4 adplay_1.8.1.orig.tar.gz 185d5f43b3d1b07c405ad3364508b18d2c38db1ee546fe1fc056fb8f7f1fac1b 4028 adplay_1.8.1-1.debian.tar.xz 63fa1b44e6db68e079905022be6e162b728ba5f0e44737e15de6416d80215e19 9868 adplay_1.8.1-1_amd64.buildinfo Files: f3b6843ba9789d87dfc09ed6a5504881 1890 sound optional adplay_1.8.1-1.dsc 363ff7b7edaaf3a69b865ac111f33cc7 4 sound optional adplay_1.8.1.orig.tar.gz d4241bc4ae20691c58246de76e185a90 4028 sound optional adplay_1.8.1-1.debian.tar.xz f661e23e69563253debc665575199479 9868 sound optional adplay_1.8.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl8Upn0ACgkQwpPntGGC Ws7R4A/+MfK3M7ht/O+cJprEz0mAaxaSHHhRf0e4rQVYwNrd4Yk6ZjppvWU4aDJ5 xEqdr+gcPGwAPQG2VekqN7DphW2Md4O7X3OQukE7uEyBA0syVO+liqXfcmcPQ5Qc ScpVYpSd9vQIdXhN8JRw3SI2Zdpb/47Zhd4yuGKIZUfxRxihVt7CFFtKtCftxIc1 YT5KZjxXXscfGTgC7JEb5JCGhzGv7kNTIauS5qswn2eNfktq6LJcIOV1UhUtEB7D hE7Hz4wulqy0oUQZBF
Bug#942958: dh-virtualenv: Python2 removal in sid/bullseye - reopen 942958
Good catch, I'll push a new release :) On Sun, Jul 19, 2020 at 12:57 AM Sandro Tosi wrote: > Control: reopen -1 > > This bug was closed, but the package has still some dependencies towards > Python2 packages, in details: > > (binary:dh-virtualenv)Depends->python-virtualenv > > Re-opening, so that they can be taken care of. > -- - Jyrki
Bug#965151: afdko-bin: /usr/bin/tx is already shipped by transifex-client
X-Debbugs-CC: debian-fo...@lists.debian.org On Sun, 19 Jul 2020 20:55:33 +0200 Adam Borowski wrote: > On Sat, Jul 18, 2020 at 03:36:48PM -0400, Boyuan Yang wrote: > > X-Debbugs-CC: debian-fo...@lists.debian.org m...@debian.org > > > > On Thu, 16 Jul 2020 23:19:31 +0200 Andreas Beckmann > > wrote: > > > Package: afdko-bin > > > Version: 3.4.0+dfsg1-2 > > > Severity: serious > > > > > > Preparing to unpack .../afdko-bin_3.4.0+dfsg1-2_amd64.deb ... > > > Unpacking afdko-bin (3.4.0+dfsg1-2) ... > > > dpkg: error processing archive /var/cache/apt/archives/afdko- > > bin_3.4.0+dfsg1-2_amd64.deb (--unpack): > > >trying to overwrite '/usr/bin/tx', which is also in package > > transifex-client 0.13.9-1 > > > Errors were encountered while processing: > > >/var/cache/apt/archives/afdko-bin_3.4.0+dfsg1-2_amd64.deb > > > > > > If the conflicting situation cannot be resolved then, as > > > last resort, the two packages have to declare a mutual > > > Conflict. > > > > AFAICT a mutual conflict could be the only reasonable solution. @mwei > > what do you think? > > The policy is very clear: > > #10.1. > > # Two different packages must not install programs with different > # functionality but with the same filenames. (The case of two programs > # having the same functionality but different implementations is handled > # via “alternatives” or the “Conflicts” mechanism. See Maintainer > # Scripts and Conflicting binary packages - Conflicts respectively.) If > # this case happens, one of the programs must be renamed. The > # maintainers should report this to the "debian-devel" mailing list and > # try to find a consensus about which program will have to be renamed. > # If a consensus cannot be reached, *both* programs must be renamed. > > Thus, a mutual conflict is not allowed. Two random packages without a > relation are not expected to conflict: there's no reason someone who hacks > on some software that uses Transifex to manage their translation wouldn't > also want to deal with fonts -- we're in the "breaks unrelated software" > land. > > This issue pops up on debian-devel quite often, and the consensus is that > exceptions shouldn't be given. Major cases: "node": axnode vs node.js, > "git" vs gnuit. In this case a discussion on debian-devel may be needed. Just FYI: SUSE chose to use the alternatives system to solve this problem as can be seen in https://opensuse.pkgs.org/tumbleweed/opensuse-oss-x86_64/python3-afdko-3.4.0-2.1.i586.rpm.html . -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#956523: This package is deprecated
See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/269 The package should be dropped, it still ships with SID and segfaults as well same functionality is provided by "gnome-control-center -> universal access-> click assist" now
Bug#965151: afdko-bin: /usr/bin/tx is already shipped by transifex-client
On Sat, Jul 18, 2020 at 03:36:48PM -0400, Boyuan Yang wrote: > X-Debbugs-CC: debian-fo...@lists.debian.org m...@debian.org > > On Thu, 16 Jul 2020 23:19:31 +0200 Andreas Beckmann > wrote: > > Package: afdko-bin > > Version: 3.4.0+dfsg1-2 > > Severity: serious > > > > Preparing to unpack .../afdko-bin_3.4.0+dfsg1-2_amd64.deb ... > > Unpacking afdko-bin (3.4.0+dfsg1-2) ... > > dpkg: error processing archive /var/cache/apt/archives/afdko- > bin_3.4.0+dfsg1-2_amd64.deb (--unpack): > >trying to overwrite '/usr/bin/tx', which is also in package > transifex-client 0.13.9-1 > > Errors were encountered while processing: > >/var/cache/apt/archives/afdko-bin_3.4.0+dfsg1-2_amd64.deb > > > > If the conflicting situation cannot be resolved then, as > > last resort, the two packages have to declare a mutual > > Conflict. > > AFAICT a mutual conflict could be the only reasonable solution. @mwei > what do you think? The policy is very clear: #10.1. # Two different packages must not install programs with different # functionality but with the same filenames. (The case of two programs # having the same functionality but different implementations is handled # via “alternatives” or the “Conflicts” mechanism. See Maintainer # Scripts and Conflicting binary packages - Conflicts respectively.) If # this case happens, one of the programs must be renamed. The # maintainers should report this to the "debian-devel" mailing list and # try to find a consensus about which program will have to be renamed. # If a consensus cannot be reached, *both* programs must be renamed. Thus, a mutual conflict is not allowed. Two random packages without a relation are not expected to conflict: there's no reason someone who hacks on some software that uses Transifex to manage their translation wouldn't also want to deal with fonts -- we're in the "breaks unrelated software" land. This issue pops up on debian-devel quite often, and the consensus is that exceptions shouldn't be given. Major cases: "node": axnode vs node.js, "git" vs gnuit. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i. ⠈⠳⣄
Bug#965317: gnome-shell: failed to write to XWayland
Hi, Thank you for fast reply. I have nothing about xwayland crash in log, only this: gnome-shell[1119]: Connection to xwayland lost Enabled extensions: * gnome-shell-extension-dashtodock ( 68-1) * gnome-shell-extension-autohidetopbar ( 20200627-1 ) * user themes ( minwaita-vanilla theme, not default adwaita ) * workspace indicator Gnome-shell is crashing like this every few days, randomly. Hard to tell what can be related with this issue: running virtualbox, firefox, thunderbird, ... On 19.07.2020 14:02, s...@debian.org wrote: On Sun, 19 Jul 2020 at 12:58:06 +0200, EdiD wrote: Gnome-shell crashes and (systemd) restarts DE. All running applications are killed. Errors from log: gnome-shell[1119]: WL: error in client communication (pid 1119) gnome-shell[1179]: (EE) failed to write to XWayland fd: Broken pipe I suspect this is happening because Xwayland has crashed (you can find out by looking at previous lines in the system log). If it is, please report that as a bug in Xwayland, with a backtrace: https://wiki.debian.org/HowToGetABacktrace It is unlikely to be possible to fix this without either a backtrace, or a sequence of instructions to reproduce the same crash. smcv
Bug#908493: marked as done (Duplicate of tao-pegtl)
Your message dated Sun, 19 Jul 2020 18:38:36 + with message-id and subject line Bug#965142: Removed package(s) from unstable has caused the Debian Bug report #908493, regarding Duplicate of tao-pegtl 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.) -- 908493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pegtl Severity: important Hello, newer version of 'pegtl' is now also present in Debian as 'tao-pegtl' source package. I suggest removing source package 'pegtl' in favor of 'tao-pegtl' in order not to duplicate code/effort. There seems to be no Debian packages depending on 'pegtl'. Best, Andrius -- Andrius Merkys Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325 LT-10257 Vilnius, Lithuania --- End Message --- --- Begin Message --- Version: 1.3.1-1+rm Dear submitter, as the package pegtl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/965142 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Mark Hymers (the ftpmaster behind the curtain)--- End Message ---
Bug#943198: marked as done (onetime: Python2 removal in sid/bullseye)
Your message dated Sun, 19 Jul 2020 18:40:08 + with message-id and subject line Bug#965231: Removed package(s) from unstable has caused the Debian Bug report #943198, regarding onetime: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 943198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: onetime Version: 1.122-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.122-1+rm Dear submitter, as the package onetime has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/965231 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Mark Hymers (the ftpmaster behind the curtain)--- End Message ---
Bug#937237: marked as done (parallelpython: Python2 removal in sid/bullseye)
Your message dated Sun, 19 Jul 2020 18:37:23 + with message-id and subject line Bug#965100: Removed package(s) from unstable has caused the Debian Bug report #937237, regarding parallelpython: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:parallelpython Version: 1.6.6-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:parallelpython If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.6.6-1+rm Dear submitter, as the package parallelpython has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/965100 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Mark Hymers (the ftpmaster behind the curtain)--- End Message ---
Bug#965332: bluefish: FTBFS on all: did not handle arch:all build well in debian/rules
Source: bluefish Version: 2.2.11+svn-r8872-1 Severity: grave X-Debbugs-CC: j...@debian.org Hi, Thanks for updating package bluefish. However as in https://buildd.debian.org/status/package.php?p=bluefish, the new version currently FTBFS on arch:all. Current debian/rules override for dh_install did not handle the split build of arch:any and arch:all packages. As seen in https://buildd.debian.org/status/fetch.php?pkg=bluefish&arch=all&ver=2.2.11%2Bsvn-r8872-1&stamp=1595163359&raw=0 , when building for arch:all, some files are not present thus a "rm" call will fail the build. Please consider using rm -f or dinstinguish between dh_install-arch and dh_install-indep. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#964220: vdr: FTBFS with glibc 2.31 (uses removed stime function)
control: tag -1 + pending
Dear maintainer,
On 2020-07-13 23:41, Aurelien Jarno wrote:
> control: severity -1 serious
>
> On 2020-07-03 22:12, Aurelien Jarno wrote:
> > Source: vdr
> > Version: 2.4.1-4
> > Severity: important
> > Tags: patch upstream
> >
> > Dear maintainer,
> >
> > vdr fail to build from source with glibc 2.31:
> >
> > | g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> > -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD -DSDNOTIFY
> > -DLIRC_DEVICE=\"/var/run/lirc/lircd\" -DVIDEODIR=\"/var/lib/video\"
> > -DCONFDIR=\"/var/lib/vdr\" -DARGSDIR=\"/etc/vdr/conf.d\"
> > -DCACHEDIR=\"/var/cache/vdr\" -DRESDIR=\"/usr/share/vdr\"
> > -DPLUGINDIR=\"/usr/lib/vdr/plugins\" -DLOCDIR=\"/usr/share/locale\"
> > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -o
> > eitscan.o eitscan.c
> > | eit.c: In constructor ‘cTDT::cTDT(const u_char*)’:
> > | eit.c:394:13: error: ‘stime’ was not declared in this scope; did you mean
> > ‘ctime’?
> > | 394 | if (stime(&dvbtim) == 0)
> > | | ^
> > | | ctime
> > | make[2]: *** [Makefile:135: eit.o] Error 1
> > | make[2]: *** Waiting for unfinished jobs
> > | make[2]: Leaving directory '/<>'
> > | dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true"
> > PREFIX=/usr VIDEODIR=/var/lib/video LIBDIR=/usr/lib/vdr/plugins SDNOTIFY=1
> > VERBOSE=1 returned exit code 2
> > | make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25
> > | make[1]: Leaving directory '/<>'
> > | make: *** [debian/rules:14: build] Error 2
> > | dpkg-buildpackage: error: debian/rules build subprocess returned exit
> > status 2
> >
> > The full build log is available there:
> > http://qa-logs.debian.net/2020/06/24/vdr_2.4.1-4_unstable_glibc-exp.log
> >
> > The stime function has been marked as obsolete for some time, and since
> > glibc 2.31 it is no longer available to newly linked binaries. The
> > clock_settime function should be used instead.
> >
> > You will find attached a patch fixing that. It would be nice if it can
> > be fixed relatively soon so that we can start the transition.
>
> Note that glibc 2.31 is now in unstable. I am therefore increasing the
> severity to serious.
I have prepared an NMU for vdr (versioned as 2.4.1-4.), fixing the build
issue with glibc 2.31. You will find the diff attached. I have uploaded
it to DELAYED/7. Please feel free to tell me if I should delay it longer
or cancel it altogether.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru vdr-2.4.1/debian/changelog vdr-2.4.1/debian/changelog
--- vdr-2.4.1/debian/changelog 2019-11-01 12:11:11.0 +
+++ vdr-2.4.1/debian/changelog 2020-07-19 17:22:51.0 +
@@ -1,3 +1,11 @@
+vdr (2.4.1-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to replace the obsolete stime function (removed in glibc 2.31)
+by clock_settime. (Closes: #964220)
+
+ -- Aurelien Jarno Sun, 19 Jul 2020 19:22:51 +0200
+
vdr (2.4.1-4) unstable; urgency=medium
* Dropped python build dependency - not actually used in build
diff -Nru vdr-2.4.1/debian/patches/glibc-stime.patch vdr-2.4.1/debian/patches/glibc-stime.patch
--- vdr-2.4.1/debian/patches/glibc-stime.patch 1970-01-01 00:00:00.0 +
+++ vdr-2.4.1/debian/patches/glibc-stime.patch 2020-07-19 17:22:51.0 +
@@ -0,0 +1,15 @@
+The obsolete stime function is no longer available to newly linked binaries
+since glibc 2.31. Replace it by clock_settime.
+
+--- a/eit.c
b/eit.c
+@@ -391,7 +391,8 @@ cTDT::cTDT(const u_char *Data)
+ if (abs(diff) > MAX_TIME_DIFF) {
+ mutex.Lock();
+ if (abs(diff) > MAX_ADJ_DIFF) {
+-if (stime(&dvbtim) == 0)
++struct timespec ts = { .tv_sec = dvbtim };
++if (clock_settime(CLOCK_REALTIME, &ts) == 0)
+isyslog("system time changed from %s (%ld) to %s (%ld)", *TimeToString(loctim), loctim, *TimeToString(dvbtim), dvbtim);
+ else
+esyslog("ERROR while setting system time: %m");
diff -Nru vdr-2.4.1/debian/patches/series vdr-2.4.1/debian/patches/series
--- vdr-2.4.1/debian/patches/series 2019-11-01 12:11:11.0 +
+++ vdr-2.4.1/debian/patches/series 2020-07-19 17:22:51.0 +
@@ -6,3 +6,4 @@
allow-verbose-libsi-build.patch
use-cpp-flags.patch
configurable-pkg-config.patch
+glibc-stime.patch
Processed: Re: Bug#964220: vdr: FTBFS with glibc 2.31 (uses removed stime function)
Processing control commands: > tag -1 + pending Bug #964220 [src:vdr] vdr: FTBFS with glibc 2.31 (uses removed stime function) Added tag(s) pending. -- 964220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#964223: linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function)
Processing control commands: > tag -1 + pending Bug #964223 [src:linuxtv-dvb-apps] linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function) Added tag(s) pending. -- 964223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964223: linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function)
control: tag -1 + pending
Dear maintainer,
On 2020-07-13 23:44, Aurelien Jarno wrote:
> control: severity -1 serious
>
> On 2020-07-03 22:27, Aurelien Jarno wrote:
> > Source: linuxtv-dvb-apps
> > Version: 1.1.1+rev1500-1.2
> > Severity: important
> > Tags: patch upstream
> >
> > linuxtv-dvb-apps fails to build from source with glibc 2.31:
> >
> > | CC dvbdate
> > | dvbdate.c: In function ‘set_time’:
> > | dvbdate.c:312:6: warning: implicit declaration of function ‘stime’; did
> > you mean ‘ctime’? [-Wimplicit-function-declaration]
> > | 312 | if (stime(new_time)) {
> > | | ^
> > | | ctime
> > | /usr/bin/ld: /tmp/cchQDddv.o: in function `set_time':
> > | ./util/dvbdate/dvbdate.c:312: undefined reference to `stime'
> > | /usr/bin/ld: ./util/dvbdate/dvbdate.c:312: undefined reference to `stime'
> > | collect2: error: ld returned 1 exit status
> > | make[3]: *** [../../Make.rules:82: dvbdate] Error 1
> > | make[3]: Leaving directory '/<>/util/dvbdate'
> > | make[2]: *** [Makefile:10: all] Error 2
> > | make[2]: Leaving directory '/<>/util'
> > | make[1]: *** [Makefile:14: all] Error 2
> > | make[1]: Leaving directory '/<>'
> > | dh_auto_build: error: make -j1 returned exit code 2
> > | make: *** [debian/rules:4: build] Error 25
> > | dpkg-buildpackage: error: debian/rules build subprocess returned exit
> > status 2
> >
> > The full build log is available there:
> > http://qa-logs.debian.net/2020/06/24/linuxtv-dvb-apps_1.1.1+rev1500-1.2_unstable_glibc-exp.log
> >
> > The stime function has been marked as obsolete for some time, and since
> > glibc 2.31 it is no longer available to newly linked binaries. The
> > clock_settime function should be used instead.
> >
> > You will find attached a patch fixing that. It would be nice if it can
> > be fixed relatively soon so that we can start the transition.
> >
>
> Note that glibc 2.31 is now in unstable. I am therefore increasing the
> severity to serious.
I have prepared an NMU for linuxtv-dvb-apps (versioned as
1.1.1+rev1500-1.3), fixing the build issue with glibc 2.31. You will
find the diff attached. I have uploaded it to DELAYED/7. Please feel
free to tell me if I should delay it longer or cancel it altogether.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2018-01-23 17:52:14.0 +
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/changelog 2020-07-19 17:11:31.0 +
@@ -1,3 +1,11 @@
+linuxtv-dvb-apps (1.1.1+rev1500-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add a patch to replace the obsolete stime function (removed in glibc 2.31)
+by clock_settime. (Closes: #964223)
+
+ -- Aurelien Jarno Sun, 19 Jul 2020 19:11:31 +0200
+
linuxtv-dvb-apps (1.1.1+rev1500-1.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch 1970-01-01 00:00:00.0 +
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/glibc-stime.patch 2020-07-19 17:11:31.0 +
@@ -0,0 +1,16 @@
+The obsolete stime function is no longer available to newly linked binaries
+since glibc 2.31. Replace it by clock_settime.
+
+--- a/util/dvbdate/dvbdate.c
b/util/dvbdate/dvbdate.c
+@@ -309,7 +309,9 @@ int atsc_scan_date(time_t *rx_time, unsi
+ */
+ int set_time(time_t * new_time)
+ {
+- if (stime(new_time)) {
++ struct timespec ts = { .tv_sec = new_time };
++
++ if (clock_settime(CLOCK_REALTIME, &ts)) {
+ perror("Unable to set time");
+ return -1;
+ }
diff -Nru linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series
--- linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2018-01-23 17:50:35.0 +
+++ linuxtv-dvb-apps-1.1.1+rev1500/debian/patches/series 2020-07-19 17:11:31.0 +
@@ -9,3 +9,4 @@
use-ldflags.patch
fix-build-libpng16.patch
dst_test-no-set-id.patch
+glibc-stime.patch
Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
severity 965091 important thanks Hi, On 2020-07-15 23:21, Thorsten Glaser wrote: > Package: libc6 > Version: 2.31-1 > Severity: grave > Justification: renders package unusable > > This is related to #965086 and #965087 (and, in fact, possibly > causing them). After a glibc upgrade half the system services > (postfix, sshd, apt-get(!)) don’t work any more. The set of packages involved in the glibc transition is ready and this bug is the only thing blocking the migration to testing. The patch fixing that issue is being developed upstream, but not fully ready yet. I am therefore downgraded the severity of this bug given that: - The x32 port is not an official port and doesn't have testing. Having this glibc package in testing won't change anything for that port. - The libc6-x32 is affected by the issue, but x32 syscalls are disabled by default in the debian kernels. This doesn't mean that the bug won't be fixed. Once the package has migrated to testing and we have a patch upstream, I'll do another upload fixing the issue. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
Processing commands for cont...@bugs.debian.org: > severity 965091 important Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 2.30] Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965328: qtwebengine-opensource-src: FTBFS on i386
Source: qtwebengine-opensource-src Version: 5.14.2+dfsg1-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) The binNMU of qtwebengine-opensource-src for the re2 transition failed on i386: | g++ -Wl,-z,relro -Wl,--as-needed -Wl,--no-keep-memory -Wl,-z,now @/<>/src/core/release/QtWebEngineCore_o.rsp -Wl,--start-group @/<>/src/core/release/QtWebEngineCore_a.rsp -Wl,--end-group -Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -m32 -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now -Wl,-O1 -Wl,--enable-new-dtags -Wl,-whole-archive -lqtwebenginecoreapi -Wl,-no-whole-archive -Wl,--no-undefined -Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQt5WebEngineCore.so.5 -o libQt5WebEngineCore.so.5.14.2 /usr/lib/i386-linux-gnu/libQt5Quick.so /usr/lib/i386-linux-gnu/libQt5Gui.so /usr/lib/i386-linux-gnu/libQt5QmlModels.so /usr/lib/i386-linux-gnu/libQt5WebChannel.so /usr/lib/i386-linux-gnu/libQt5Qml.so /usr/lib/i386-linux-gnu/libQt5Network.so /usr/lib/i386-linux-gnu/libQt5Positioning.so /usr/lib/i386-linux-gnu/libQt5Core.so -lpthread -lGL -lpthread -ldl -lrt -licui18n -licuuc -licudata -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -levent -lresolv -lz -ljpeg -lpng16 -lwebpmux -lwebpdemux -lwebp -lfreetype -lexpat -lfontconfig -lharfbuzz -lre2 -lsnappy -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lXrandr -lXss -ldbus-1 -lpci -lasound -lavcodec -lavformat -lavutil -lvpx -lm -lopus -lxml2 -lxslt -lminizip -llcms2 -L/<>/src/core/api/release -lGL | /usr/bin/ld: /<>/src/core/release/obj/third_party/openh264/openh264_common_yasm/dct.o: warning: relocation in read-only section `.text' | /usr/bin/ld: warning: creating DT_TEXTREL in a shared object | collect2: error: ld returned 1 exit status | make[5]: *** [Makefile.core_module:89: ../../lib/libQt5WebEngineCore.so.5.14.2] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src&arch=i386&ver=5.14.2%2Bdfsg1-2%2Bb1&stamp=1595153578&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: xrdp: diff for NMU version 0.9.12-1.1
Processing control commands: > tags 964573 + patch Bug #964573 [src:xrdp] xrdp: CVE-2020-4044 Added tag(s) patch. > tags 964573 + pending Bug #964573 [src:xrdp] xrdp: CVE-2020-4044 Added tag(s) pending. -- 964573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964573: xrdp: diff for NMU version 0.9.12-1.1
Control: tags 964573 + patch
Control: tags 964573 + pending
Dear maintainer,
I've prepared an NMU for xrdp (versioned as 0.9.12-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
I can defintively cancel it if you prefer to do either a maintainer
upload or even better to rebase to the new upstream version.
Regards,
Salvatore
diff -Nru xrdp-0.9.12/debian/changelog xrdp-0.9.12/debian/changelog
--- xrdp-0.9.12/debian/changelog 2020-01-11 02:40:04.0 +0100
+++ xrdp-0.9.12/debian/changelog 2020-07-19 17:11:20.0 +0200
@@ -1,3 +1,12 @@
+xrdp (0.9.12-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * xrdp-sesman can be crashed remotely over port 3350 (CVE-2020-4044)
+(Closes: #964573)
+ * Fixed CVE-2020-4044 CI errors
+
+ -- Salvatore Bonaccorso Sun, 19 Jul 2020 17:11:20 +0200
+
xrdp (0.9.12-1) unstable; urgency=low
* Update Homepage link
diff -Nru xrdp-0.9.12/debian/patches/Fix-for-CVE-2020-4044.patch xrdp-0.9.12/debian/patches/Fix-for-CVE-2020-4044.patch
--- xrdp-0.9.12/debian/patches/Fix-for-CVE-2020-4044.patch 1970-01-01 01:00:00.0 +0100
+++ xrdp-0.9.12/debian/patches/Fix-for-CVE-2020-4044.patch 2020-07-19 17:11:20.0 +0200
@@ -0,0 +1,1270 @@
+From: matt335672 <30179339+matt335...@users.noreply.github.com>
+Date: Fri, 12 Jun 2020 09:56:47 +0100
+Subject: Fix for CVE-2020-4044
+Origin: https://github.com/neutrinolabs/xrdp/commit/ba2f727c9a2acbee59c27b5883b36b43b022ea9c
+Bug-Debian: https://bugs.debian.org/964573
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2020-4044
+
+Reported by: Ashley Newson
+---
+ sesman/libscp/libscp_types.h | 4 +
+ sesman/libscp/libscp_v0.c | 335
+ sesman/libscp/libscp_v1s.c | 336 +++--
+ sesman/libscp/libscp_v1s_mng.c | 164 +---
+ sesman/scp.c | 12 +-
+ 5 files changed, 592 insertions(+), 259 deletions(-)
+
+diff --git a/sesman/libscp/libscp_types.h b/sesman/libscp/libscp_types.h
+index 8cb9166c515f..84e6c4651e7e 100644
+--- a/sesman/libscp/libscp_types.h
b/sesman/libscp/libscp_types.h
+@@ -59,6 +59,10 @@
+
+ #include "libscp_types_mng.h"
+
++/* Max server incoming and outgoing message size, used to stop memory
++ exhaustion attempts (CVE-2020-4044) */
++#define SCP_MAX_MESSAGE_SIZE 8192
++
+ struct SCP_CONNECTION
+ {
+ int in_sck;
+diff --git a/sesman/libscp/libscp_v0.c b/sesman/libscp/libscp_v0.c
+index 61bf4fdae43a..55168b4f515f 100644
+--- a/sesman/libscp/libscp_v0.c
b/sesman/libscp/libscp_v0.c
+@@ -34,6 +34,65 @@
+
+ extern struct log_config *s_log;
+
++/** Maximum length of a string (two bytes + len), excluding the terminator
++ *
++ * Practially this is limited by [MS-RDPBCGR] TS_INFO_PACKET
++ * */
++#define STRING16_MAX_LEN 512
++
++/**
++ * Reads a big-endian uint16 followed by a string into a buffer
++ *
++ * Buffer is null-terminated on success
++ *
++ * @param s Input stream
++ * @param [out] Output buffer (must be >= (STRING16_MAX_LEN+1) chars)
++ * @param param Parameter we're reading
++ * @param line Line number reference
++ * @return != 0 if string read OK
++ */
++static
++int in_string16(struct stream *s, char str[], const char *param, int line)
++{
++int result;
++
++if (!s_check_rem(s, 2))
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s len missing",
++line, param);
++result = 0;
++}
++else
++{
++unsigned int sz;
++
++in_uint16_be(s, sz);
++if (sz > STRING16_MAX_LEN)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s too long (%u chars)",
++line, param, sz);
++result = 0;
++}
++else
++{
++result = s_check_rem(s, sz);
++if (!result)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s data missing",
++line, param);
++}
++else
++{
++in_uint8a(s, str, sz);
++str[sz] = '\0';
++}
++}
++}
++return result;
++}
+ /* client API */
+ /**/
+ enum SCP_CLIENT_STATES_E
+@@ -71,10 +130,24 @@ scp_v0c_connect(struct SCP_CONNECTION *c, struct SCP_SESSION *s)
+ }
+
+ sz = g_strlen(s->username);
++if (sz > STRING16_MAX_LEN)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: username too long",
++__LINE__);
++return SCP_CLIENT_STATE_SIZE_ERR;
++}
+ out_uint16_be(c->out_s, sz);
+ out_uint8a(c->out_s, s->username, sz);
+
+ sz = g_strlen(s->password);
++if (sz > STRING16_MAX_LEN)
++{
++
Bug#964573: xrdp: CVE-2020-4044
Hi
Attached ist the debdiff as prepared for buster-security, will send
shortly as well the one for unstable.
Regards,
Salvatore
diff -Nru xrdp-0.9.9/debian/changelog xrdp-0.9.9/debian/changelog
--- xrdp-0.9.9/debian/changelog 2019-01-13 13:49:36.0 +0100
+++ xrdp-0.9.9/debian/changelog 2020-07-19 17:02:11.0 +0200
@@ -1,3 +1,13 @@
+xrdp (0.9.9-1+deb10u1) buster-security; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * libscp v1 server set height twice, and not set width
+ * xrdp-sesman can be crashed remotely over port 3350 (CVE-2020-4044)
+(Closes: #964573)
+ * Fixed CVE-2020-4044 CI errors
+
+ -- Salvatore Bonaccorso Sun, 19 Jul 2020 17:02:11 +0200
+
xrdp (0.9.9-1) unstable; urgency=medium
[ Thorsten Glaser ]
diff -Nru xrdp-0.9.9/debian/patches/Fix-for-CVE-2020-4044.patch
xrdp-0.9.9/debian/patches/Fix-for-CVE-2020-4044.patch
--- xrdp-0.9.9/debian/patches/Fix-for-CVE-2020-4044.patch 1970-01-01
01:00:00.0 +0100
+++ xrdp-0.9.9/debian/patches/Fix-for-CVE-2020-4044.patch 2020-07-19
17:02:11.0 +0200
@@ -0,0 +1,1270 @@
+From: matt335672 <30179339+matt335...@users.noreply.github.com>
+Date: Fri, 12 Jun 2020 09:56:47 +0100
+Subject: Fix for CVE-2020-4044
+Origin:
https://github.com/neutrinolabs/xrdp/commit/ba2f727c9a2acbee59c27b5883b36b43b022ea9c
+Bug-Debian: https://bugs.debian.org/964573
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2020-4044
+
+Reported by: Ashley Newson
+---
+ sesman/libscp/libscp_types.h | 4 +
+ sesman/libscp/libscp_v0.c | 335
+ sesman/libscp/libscp_v1s.c | 336 +++--
+ sesman/libscp/libscp_v1s_mng.c | 164 +---
+ sesman/scp.c | 12 +-
+ 5 files changed, 592 insertions(+), 259 deletions(-)
+
+diff --git a/sesman/libscp/libscp_types.h b/sesman/libscp/libscp_types.h
+index 8cb9166c515f..84e6c4651e7e 100644
+--- a/sesman/libscp/libscp_types.h
b/sesman/libscp/libscp_types.h
+@@ -59,6 +59,10 @@
+
+ #include "libscp_types_mng.h"
+
++/* Max server incoming and outgoing message size, used to stop memory
++ exhaustion attempts (CVE-2020-4044) */
++#define SCP_MAX_MESSAGE_SIZE 8192
++
+ struct SCP_CONNECTION
+ {
+ int in_sck;
+diff --git a/sesman/libscp/libscp_v0.c b/sesman/libscp/libscp_v0.c
+index 61bf4fdae43a..55168b4f515f 100644
+--- a/sesman/libscp/libscp_v0.c
b/sesman/libscp/libscp_v0.c
+@@ -34,6 +34,65 @@
+
+ extern struct log_config *s_log;
+
++/** Maximum length of a string (two bytes + len), excluding the terminator
++ *
++ * Practially this is limited by [MS-RDPBCGR] TS_INFO_PACKET
++ * */
++#define STRING16_MAX_LEN 512
++
++/**
++ * Reads a big-endian uint16 followed by a string into a buffer
++ *
++ * Buffer is null-terminated on success
++ *
++ * @param s Input stream
++ * @param [out] Output buffer (must be >= (STRING16_MAX_LEN+1) chars)
++ * @param param Parameter we're reading
++ * @param line Line number reference
++ * @return != 0 if string read OK
++ */
++static
++int in_string16(struct stream *s, char str[], const char *param, int line)
++{
++int result;
++
++if (!s_check_rem(s, 2))
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s len missing",
++line, param);
++result = 0;
++}
++else
++{
++unsigned int sz;
++
++in_uint16_be(s, sz);
++if (sz > STRING16_MAX_LEN)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s too long (%u chars)",
++line, param, sz);
++result = 0;
++}
++else
++{
++result = s_check_rem(s, sz);
++if (!result)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: %s data missing",
++line, param);
++}
++else
++{
++in_uint8a(s, str, sz);
++str[sz] = '\0';
++}
++}
++}
++return result;
++}
+ /* client API */
+
/**/
+ enum SCP_CLIENT_STATES_E
+@@ -71,10 +130,24 @@ scp_v0c_connect(struct SCP_CONNECTION *c, struct
SCP_SESSION *s)
+ }
+
+ sz = g_strlen(s->username);
++if (sz > STRING16_MAX_LEN)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: username too long",
++__LINE__);
++return SCP_CLIENT_STATE_SIZE_ERR;
++}
+ out_uint16_be(c->out_s, sz);
+ out_uint8a(c->out_s, s->username, sz);
+
+ sz = g_strlen(s->password);
++if (sz > STRING16_MAX_LEN)
++{
++log_message(LOG_LEVEL_WARNING,
++"[v0:%d] connection aborted: password too long",
++__LINE__);
++
Bug#962275: marked as done (snort: Failed to start LSB)
Your message dated Sun, 19 Jul 2020 15:19:18 + with message-id and subject line Bug#962275: fixed in snort 2.9.15.1-3 has caused the Debian Bug report #962275, regarding snort: Failed to start LSB 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.) -- 962275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snort Version: 2.9.15.1-2 Severity: grave Dear Maintainer, installation of 'snort' fails with a subprocess error (fresh install, /etc/snort doesn't exist before installation. Accepting the propose d network settings: 192.168.0.0/16). Aptitude output: ** Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Preconfiguring packages ... Snort configuration: interface default not set, using 'eth0' Selecting previously unselected package snort-common-libraries. (Reading database ... 649619 files and directories currently installe d.) Preparing to unpack .../0-snort-common-libraries_2.9.15.1-2_amd64.deb ... Unpacking snort-common-libraries (2.9.15.1-2) ... Preparing to unpack .../1-snort-rules-default_2.9.15.1-2_all.deb ... Unpacking snort-rules-default (2.9.15.1-2) ... Preparing to unpack .../2-snort-common_2.9.15.1-2_all.deb ... Unpacking snort-common (2.9.15.1-2) ... Selecting previously unselected package libdaq2. Preparing to unpack .../3-libdaq2_2.0.7-2_amd64.deb ... Unpacking libdaq2 (2.0.7-2) ... Selecting previously unselected package snort. Preparing to unpack .../4-snort_2.9.15.1-2_amd64.deb ... Unpacking snort (2.9.15.1-2) ... Preparing to unpack .../5-oinkmaster_2.0-4_all.deb ... Unpacking oinkmaster (2.0-4) ... Setting up oinkmaster (2.0-4) ... Setting up snort-common (2.9.15.1-2) ... Setting up libdaq2 (2.0.7-2) ... Setting up snort-rules-default (2.9.15.1-2) ... Setting up snort-common-libraries (2.9.15.1-2) ... Setting up snort (2.9.15.1-2) ... Snort configuration: interface default not set, using 'eth0' WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:4 3 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 259261 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:43 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:43 holly snort[259273]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:43 holly snort[259275]: Starting Jun 05 13:41:43 holly systemd[1]: snort.service: Control process exit ed, code=exited, status=1/FAILURE Jun 05 13:41:43 holly systemd[1]: snort.service: Failed with result ' exit-code'. Jun 05 13:41:43 holly systemd[1]: Failed to start LSB: Lightweight ne twork intrusion detection system. dpkg: error processing package snort (--configure): installed snort package post-installation script subprocess returne d error exit status 1 Processing triggers for systemd (245.5-3) ... Processing triggers for man-db (2.9.2-1) ... Processing triggers for libc-bin (2.30-8) ... Errors were encountered while processing: snort [ Rootkit Hunter version 1.4.6 ] File updated: searched for 181 files, found 152 needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up snort (2.9.15.1-2) ... Snort configuration: interface default set, using eth0 WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) sin
Bug#964671: comedilib: FTBFS: ccQsDx8i.s: Error: invalid attempt to declare external version name as default in symbol `comedi_internal_trigger@@v0.9.0'
Hi again
I got a fast response from upstream author Ian Abbott. The fix
is in fact very simple :)
https://groups.google.com/forum/#!topic/comedi_list/WyvwzALQSJ4
I fill fix the package ASAP.
diff --git a/lib/insn_config_wrappers.c b/lib/insn_config_wrappers.c
index 7d43313..61efecf 100644
--- a/lib/insn_config_wrappers.c
+++ b/lib/insn_config_wrappers.c
@@ -262,7 +262,7 @@ int _comedi_set_gate_source(comedi_t *device, unsigned
subdevice, unsigned chann
}
EXPORT_ALIAS_DEFAULT(_comedi_internal_trigger,comedi_internal_trigger,0.9.0);
-int comedi_internal_trigger(comedi_t *dev, unsigned subd, unsigned trignum)
+int _comedi_internal_trigger(comedi_t *dev, unsigned subd, unsigned trignum)
{
comedi_insn insn;
lsampl_t data[1];
Regards
Gudjon
Bug#965308: jackd won't start
Control: tags -1 + moreinfo On 2020-07-19 10:14:58 +0200, Arnaldo Pirrone wrote: > Package: jackd2 > Version: 1.9.14~dfsg-0.1 > Severity: grave > X-Debbugs-Cc: it9...@gmail.com > > Hi, after the update jackd is not starting anymore. Apparently this is > related. > > Sun Jul 19 10:05:53 2020: ERROR: Can't load "/usr/lib/x86_64-linux- > gnu/jack/jack_alsa.so": /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: undefined > symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE I suspect this is caused by an old libjack library somewhere in /usr/local. Could you please provide the output of ldd -r /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so to confirm that? Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: Re: Bug#965308: jackd won't start
Processing control commands: > tags -1 + moreinfo Bug #965308 [jackd2] jackd won't start Added tag(s) moreinfo. -- 965308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964044: marked as done (mrpt: FTBFS: test failure)
Your message dated Sun, 19 Jul 2020 13:19:58 + with message-id and subject line Bug#964044: fixed in mrpt 1:2.0.4-2 has caused the Debian Bug report #964044, regarding mrpt: FTBFS: test failure 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.) -- 964044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrpt Version: 1:2.0.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) binNMUs of mrpt failed to build: | [--] 1 test from RawlogGrabberApp | [ RUN ] RawlogGrabberApp.CGenericCamera_AVI | [CCameraSensor::initialize] Opening camera... | [CCameraSensor::initialize] FFmpeg stream: /<>/share/mrpt/datasets/dummy_video.avi... | [CCameraSensor::initialize] Done! | Rawlog grabbed objects: 1 | /<>/libs/apps/src/RawlogGrabberApp_unittest.cpp:94: Failure | Expected: (app.rawlog_saved_objects) >= (REQUIRED_GRAB_OBS), actual: 1 vs 3 | [ FAILED ] RawlogGrabberApp.CGenericCamera_AVI (1511 ms) | [--] 1 test from RawlogGrabberApp (1511 ms total) See https://buildd.debian.org/status/fetch.php?pkg=mrpt&arch=amd64&ver=1%3A2.0.4-1%2Bb1&stamp=1593549279&raw=0 for example Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mrpt Source-Version: 1:2.0.4-2 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of mrpt, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated mrpt 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: Fri, 17 Jul 2020 08:14:20 +0200 Source: mrpt Binary: mrpt-doc libmrpt-bayes2.0 libmrpt-bayes-dev libmrpt-comms2.0 libmrpt-comms-dev libmrpt-config2.0 libmrpt-config-dev libmrpt-containers2.0 libmrpt-containers-dev libmrpt-core2.0 libmrpt-core-dev libmrpt-detectors2.0 libmrpt-detectors-dev libmrpt-expr2.0 libmrpt-expr-dev libmrpt-graphs2.0 libmrpt-graphs-dev libmrpt-graphslam2.0 libmrpt-graphslam-dev libmrpt-gui2.0 libmrpt-nanogui2.0 libmrpt-gui-dev libmrpt-nanogui-dev libmrpt-hmtslam2.0 libmrpt-hmtslam-dev libmrpt-hwdrivers2.0 libmrpt-hwdrivers-dev libmrpt-img2.0 libmrpt-img-dev libmrpt-io2.0 libmrpt-io-dev libmrpt-kinematics2.0 libmrpt-kinematics-dev libmrpt-maps2.0 libmrpt-maps-dev libmrpt-math2.0 libmrpt-math-dev libmrpt-nanoflann-dev libmrpt-nav2.0 libmrpt-nav-dev libmrpt-obs2.0 libmrpt-obs-dev libmrpt-opengl2.0 libmrpt-opengl-dev libmrpt-poses2.0 libmrpt-poses-dev libmrpt-random2.0 libmrpt-random-dev libmrpt-rtti2.0 libmrpt-rtti-dev libmrpt-ros1bridge2.0 libmrpt-ros1bridge-dev libmrpt-serialization2.0 libmrpt-serialization-dev libmrpt-slam2.0 libmrpt-slam-dev libmrpt-system2.0 libmrpt-system-dev libmrpt-tclap-dev libmrpt-tfest2.0 libmrpt-tfest-dev libmrpt-topography2.0 libmrpt-topography-dev libmrpt-typemeta-dev libmrpt-vision2.0 libmrpt-vision-dev libmrpt-vision-lgpl2.0 libmrpt-vision-lgpl-dev libmrpt-apps2.0 libmrpt-apps-dev libmrpt-common-dev libmrpt-dev mrpt-common mrpt-apps Architecture: source Version: 1:2.0.4-2 Distribution: unstable Urgency: medium Maintainer: José Luis Blanco Claraco Changed-By: Gianfranco Costamagna Description: libmrpt-apps-dev - Mobile Robot Programming Toolkit - apps development package libmrpt-apps2.0 - Mobile Robot Programming Toolkit - apps library libmrpt-bayes-dev - Mobile Robot Programming Toolkit - bayes development package libmrpt-bayes2.0 - Mobile Robot Programming Toolkit - bayes library libmrpt-common-dev - Mobile Robot Programming Toolkit - common development files libmrpt-comms-dev - Mobile Robot Programming Toolkit - comms development package libmrpt-comms2.0 - Mobile Robot Programming Toolkit - comms library libmrpt-config-dev - Mobile Robot Programming Toolkit - config development package libmrpt-config2.0 - Mobile Robot Programming Toolkit - config library libmrpt-containers-dev - Mobile Robot Programming Toolkit - containers development package libmrpt-cont
Processed: Reassign bug
Processing commands for cont...@bugs.debian.org:
> reassign 965320 libdaq2
Bug #965320 {Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?=
} [snort] daq: Missing sf_n_errors symbol in libsfbpf.so.0
Bug reassigned from package 'snort' to 'libdaq2'.
No longer marked as found in versions snort/2.9.15.1-2.
No longer marked as fixed in versions daq/2.0.7-4.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
965320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965320: marked as done (daq: Missing sf_n_errors symbol in libsfbpf.so.0)
Your message dated Sun, 19 Jul 2020 12:48:33 + with message-id and subject line Bug#965320: fixed in daq 2.0.7-4 has caused the Debian Bug report #965320, regarding daq: Missing sf_n_errors symbol in libsfbpf.so.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.) -- 965320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snort Version: 2.9.15.1-2 Severity: grave Dear Maintainer, installation of 'snort' fails with a subprocess error (fresh install, /etc/snort doesn't exist before installation. Accepting the propose d network settings: 192.168.0.0/16). Aptitude output: ** Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Preconfiguring packages ... Snort configuration: interface default not set, using 'eth0' Selecting previously unselected package snort-common-libraries. (Reading database ... 649619 files and directories currently installe d.) Preparing to unpack .../0-snort-common-libraries_2.9.15.1-2_amd64.deb ... Unpacking snort-common-libraries (2.9.15.1-2) ... Preparing to unpack .../1-snort-rules-default_2.9.15.1-2_all.deb ... Unpacking snort-rules-default (2.9.15.1-2) ... Preparing to unpack .../2-snort-common_2.9.15.1-2_all.deb ... Unpacking snort-common (2.9.15.1-2) ... Selecting previously unselected package libdaq2. Preparing to unpack .../3-libdaq2_2.0.7-2_amd64.deb ... Unpacking libdaq2 (2.0.7-2) ... Selecting previously unselected package snort. Preparing to unpack .../4-snort_2.9.15.1-2_amd64.deb ... Unpacking snort (2.9.15.1-2) ... Preparing to unpack .../5-oinkmaster_2.0-4_all.deb ... Unpacking oinkmaster (2.0-4) ... Setting up oinkmaster (2.0-4) ... Setting up snort-common (2.9.15.1-2) ... Setting up libdaq2 (2.0.7-2) ... Setting up snort-rules-default (2.9.15.1-2) ... Setting up snort-common-libraries (2.9.15.1-2) ... Setting up snort (2.9.15.1-2) ... Snort configuration: interface default not set, using 'eth0' WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:4 3 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 259261 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:43 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:43 holly snort[259273]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:43 holly snort[259275]: Starting Jun 05 13:41:43 holly systemd[1]: snort.service: Control process exit ed, code=exited, status=1/FAILURE Jun 05 13:41:43 holly systemd[1]: snort.service: Failed with result ' exit-code'. Jun 05 13:41:43 holly systemd[1]: Failed to start LSB: Lightweight ne twork intrusion detection system. dpkg: error processing package snort (--configure): installed snort package post-installation script subprocess returne d error exit status 1 Processing triggers for systemd (245.5-3) ... Processing triggers for man-db (2.9.2-1) ... Processing triggers for libc-bin (2.30-8) ... Errors were encountered while processing: snort [ Rootkit Hunter version 1.4.6 ] File updated: searched for 181 files, found 152 needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up snort (2.9.15.1-2) ... Snort configuration: interface default set, using eth0 WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Resul
Bug#951143: marked as done (bluefish: Please migrate to enchant-2)
Your message dated Sun, 19 Jul 2020 12:48:28 + with message-id and subject line Bug#951143: fixed in bluefish 2.2.11+svn-r8872-1 has caused the Debian Bug report #951143, regarding bluefish: Please migrate to enchant-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 951143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bluefish Version: 2.2.10-3 Severity: important Control: block 947979 by -1 Dear bluefish maintainer, Your package is affected by an ongoing transition from enchant(1) to enchant- 2. You may find the transition information at https://release.debian.org/transitions/html/enchant-2.html and https://bugs.debian.org/947979 . Current bluefish source code in Debian does not support enchant-2 yet. Please consider working with upstream for a complete enchant-2 support. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: bluefish Source-Version: 2.2.11+svn-r8872-1 Done: Jonathan Carter We believe that the bug you reported is fixed in the latest version of bluefish, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated bluefish 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, 18 Jul 2020 11:34:15 +0200 Source: bluefish Architecture: source Version: 2.2.11+svn-r8872-1 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Jonathan Carter Closes: 593413 593427 692284 730543 857330 892502 951143 Changes: bluefish (2.2.11+svn-r8872-1) unstable; urgency=medium . * New upstream snapshot (Closes: #593413, #593427, #692284, #730543, #857330, #892502) * Use libenchant-2-dev instead of libenchant-dev (Closes: #951143) * Use secure URI in watch file * Remove trailing whitespaces in changelog * Remove ancient versioned dependencies on intltool, libglib2.0-dev, libgtk-3-dev and libgucharmap-2-90-dev * Upgrade to debhelper-compat (13) * Add usr/share/bluefish and to bluefish.install * Add Python3:Depends substvar dependency for bluefish binary package * Add debian/not-installed to list unwanted .la files * Remove "-Wl --as-needed" from debian/rules (now default in bullsey build process) Checksums-Sha1: a97e140cdb431804cbbf35f1c7d1f36c748d13d7 2229 bluefish_2.2.11+svn-r8872-1.dsc 8f98b1347b7c72c07899764126d3ef8a7ba56aec 2959320 bluefish_2.2.11+svn-r8872.orig.tar.xz af45e97739d14b8629c261778a779d3155aa9e8d 18368 bluefish_2.2.11+svn-r8872-1.debian.tar.xz df5e0ec975fde0af8ccd33fad26bfd6af1715b2e 15321 bluefish_2.2.11+svn-r8872-1_source.buildinfo Checksums-Sha256: 7eb4d27d53c33591291e1c00e96641dbe0619b4fafce01978df45e8277aa412f 2229 bluefish_2.2.11+svn-r8872-1.dsc 7e0308bfd215d1c677e3e6b96d2ac9676cb4163d8ad0470cbc266dcd6ce42db7 2959320 bluefish_2.2.11+svn-r8872.orig.tar.xz 747a9ba349a8f0940cda0ce6180dff84091c8a9968c268b5d7d79fdbfa8744d5 18368 bluefish_2.2.11+svn-r8872-1.debian.tar.xz b7b1c0539e864835cb96a450aad208cf787c0ba8882bbe73b6af9c0475d5d6d0 15321 bluefish_2.2.11+svn-r8872-1_source.buildinfo Files: 2361b52b681d02e0883b9534b8c84862 2229 web optional bluefish_2.2.11+svn-r8872-1.dsc 0930ac7ff4283e11615f014ff25a9d63 2959320 web optional bluefish_2.2.11+svn-r8872.orig.tar.xz 71ff00bd41692acbe5311e85ea7f4a4d 18368 web optional bluefish_2.2.11+svn-r8872-1.debian.tar.xz 925e7f09bbc14e0db1f5834698241bcb 15321 web optional bluefish_2.2.11+svn-r8872-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl8UPVoPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmh0EcP+wc21yDFVcIZamOj2FfzVa86HzzBk6hV+nnp cZ27vE7X8J0T/mziibFkxmEGPN7BVjohZvr3VwFK4qkT37i6D0JMvowNNJyjQc8b 3b548q2JyvU/qI/tCdaokLPZM9RqPmV+AJdnEmxl16lzqqFXkiLTXWGL0F0QSpxs sL6t1navunbK0uNpj/l+eLKinGSutqM+HMIW0hqcstNR/xeXL8uI0GnIdJW95JU/ U1Tr1rbWNi2nDzMfjJcX2YLt/4gGiWw9k3Q4bwNQOemUOoRdD+foQKWuPn8ycLmD ZYUqIhWEtJBoqE4fv19ofKGJjJmYkXQ+Vh8xVI4jL2r3TBVjnRp/AUuOo36ZTH6a /ZzNTB+RmK3
Bug#962275: snort: Failed to start LSB
An update on this bug: The missing symbols issue is really a problem in the daq library. A patch introduced in 2.0.7-1 to fix some FTBFS bugs (959617, 958101) actually disabled symbols in the library which are required. This will be soon fixed. The issue related to the library location is a little bit more tricky to fix. I have seen that the RedHat package (rpm - in snort.spec) actually does this by modifying snort.conf when the package is built (using sed) to change the library patch for the dynamicengine. I might need to introduce something similar in the Debian package. Saludos Javier
Processed (with 2 errors): Copying Snort bug to daq
Processing commands for cont...@bugs.debian.org: > clone 962275 -1 Bug #962275 [snort] snort: Failed to start LSB Bug 962275 cloned as bug 965320 > reassign -1 Unknown command or malformed arguments to command. > retitle -1 daq: Missing sf_n_errors symbol in libsfbpf.so.0 Bug #965320 [snort] snort: Failed to start LSB Changed Bug title to 'daq: Missing sf_n_errors symbol in libsfbpf.so.0' from 'snort: Failed to start LSB'. > tag -1 pending Bug #965320 [snort] daq: Missing sf_n_errors symbol in libsfbpf.so.0 Added tag(s) pending. > block 962275 -1 Unknown command or malformed arguments to command. > quit Stopping processing here. Please contact me if you need assistance. -- 962275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962275 965320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965317: gnome-shell: failed to write to XWayland
On Sun, 19 Jul 2020 at 12:58:06 +0200, EdiD wrote: > Gnome-shell crashes and (systemd) restarts DE. All running applications are > killed. Errors from log: > > gnome-shell[1119]: WL: error in client communication (pid 1119) > gnome-shell[1179]: (EE) failed to write to XWayland fd: Broken pipe I suspect this is happening because Xwayland has crashed (you can find out by looking at previous lines in the system log). If it is, please report that as a bug in Xwayland, with a backtrace: https://wiki.debian.org/HowToGetABacktrace It is unlikely to be possible to fix this without either a backtrace, or a sequence of instructions to reproduce the same crash. smcv
Processed: fixed 964786 in 2.2.1-1
Processing commands for cont...@bugs.debian.org:
> fixed 964786 2.2.1-1
Bug #964786 {Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?=
} [src:daq] src:daq: fails to migrate to testing for too long:
unhandled RC bug
Marked as fixed in versions daq/2.2.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965317: gnome-shell: failed to write to XWayland
Package: gnome-shell Version: 3.36.3-1 Severity: grave Justification: causes non-serious data loss Gnome-shell crashes and (systemd) restarts DE. All running applications are killed. Errors from log: gnome-shell[1119]: WL: error in client communication (pid 1119) gnome-shell[1179]: (EE) failed to write to XWayland fd: Broken pipe Very frustrating because all unsaved work is lost. Seems like this is most problematic release since i can remember. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii evolution-data-server3.36.4-1 ii gir1.2-accountsservice-1.0 0.6.55-2 ii gir1.2-atspi-2.0 2.36.0-2 ii gir1.2-freedesktop 1.64.1-1 ii gir1.2-gcr-3 3.36.0-2 ii gir1.2-gdesktopenums-3.0 3.36.1-1 ii gir1.2-gdm-1.0 3.36.2-1 ii gir1.2-geoclue-2.0 2.5.6-1 ii gir1.2-glib-2.0 1.64.1-1 ii gir1.2-gnomebluetooth-1.03.34.1-1 ii gir1.2-gnomedesktop-3.0 3.36.3.1-2 ii gir1.2-gtk-3.0 3.24.20-1 ii gir1.2-gweather-3.0 3.36.0-1 ii gir1.2-ibus-1.0 1.5.22-5 ii gir1.2-mutter-6 3.36.3-1 ii gir1.2-nm-1.01.26.0-1 ii gir1.2-nma-1.0 1.8.30-1 ii gir1.2-pango-1.0 1.44.7-4 ii gir1.2-polkit-1.00.105-28 ii gir1.2-rsvg-2.0 2.48.7-1 ii gir1.2-soup-2.4 2.70.0-1 ii gir1.2-upowerglib-1.00.99.11-2 ii gjs 1.64.3-1 ii gnome-backgrounds3.36.0-1 ii gnome-settings-daemon3.36.1-1 ii gnome-shell-common 3.36.3-1 ii gsettings-desktop-schemas3.36.1-1 ii libatk-bridge2.0-0 2.34.1-3 ii libatk1.0-0 2.36.0-2 ii libc62.30-8 ii libcairo21.16.0-4 ii libecal-2.0-13.36.4-1 ii libedataserver-1.2-243.36.4-1 ii libgcr-base-3-1 3.36.0-2 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgirepository-1.0-11.64.1-1 ii libgjs0g 1.64.3-1 ii libgles2 1.3.1-1 ii libglib2.0-0 2.64.3-2 ii libglib2.0-bin 2.64.3-2 ii libgnome-autoar-0-0 0.2.4-2 ii libgnome-desktop-3-193.36.3.1-2 ii libgraphene-1.0-01.10.2-1 ii libgstreamer1.0-01.16.2-2 ii libgtk-3-0 3.24.20-1 ii libical3 3.0.8-2 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-6-03.36.3-1 ii libnm0 1.26.0-1 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii libpolkit-agent-1-0 0.105-28 ii libpolkit-gobject-1-00.105-28 ii libpulse-mainloop-glib0 13.0-5 ii libpulse013.0-5 ii libsecret-1-00.20.3-1 ii libsystemd0 245.6-2 ii libwayland-server0 1.18.0-1 ii libx11-6 2:1.6.9-2+b1 ii libxfixes3 1:5.0.3-2 ii mutter 3.36.3-1 ii python3 3.8.2-3 Versions of packages gnome-shell recommends: ii bolt 0.9-1 ii chrome-gnome-shell10.1-5 ii gdm3 3.36.2-1 ii gkbd-capplet 3.26.1-1 ii gnome-control-center 1:3.36.4-1 ii gnome-menus 3.36.0-1 ii gnome-user-docs 3.36.2-1 ii ibus 1.5.22-5 ii iio-sensor-proxy 3.0-1 i
Bug#964786: marked as done (src:daq: fails to migrate to testing for too long: unhandled RC bug)
Your message dated Sun, 19 Jul 2020 11:03:36 + with message-id and subject line Bug#964786: fixed in daq 2.0.7-3 has caused the Debian Bug report #964786, regarding src:daq: fails to migrate to testing for too long: unhandled RC bug 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.) -- 964786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: daq Version: 2.0.4-3 Severity: serious Control: close -1 2.0.7-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 960479 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:daq in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=daq signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: daq Source-Version: 2.0.7-3 Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= We believe that the bug you reported is fixed in the latest version of daq, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated daq 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, 19 Jul 2020 11:50:12 +0200 Source: daq Architecture: source Version: 2.0.7-3 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Closes: 818893 960479 964786 Changes: daq (2.0.7-3) unstable; urgency=medium . * debian/control: - Remove duplicate Build-Dep on libpcap0.8-dev - Add Dependency on libdaq-dev on libpcap0.8-dev, libdumbnet-dev, libnetfilter-queue-dev. (Closes: #960479, #964786) Thanks to Adrian Bunk for spotting this error which is due the following: $ daq-modules-config --static --libs -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet - Remove Build-Dep on dh-autoreconf (lintian warning) - Remove duplicate Section: (lintian warning) . * debian/libdaq2.install, debian/libdaq-dev.install: Add daq plugins into the binary package (added usr/lib/*/daq/*.so) and remove from -dev package (Closes: #818893) * debian/libdaq-dev.install: Remove static libraries (usr/lib/*/lib*.a) * debian/watch: Created file to look up for new versions Checksums-Sha1: 39d93ed01b7fa950b7bf3d4cd41797dc0f7121da 1809 daq_2.0.7-3.dsc 657285de4512b9bd2e70f4d8705bb06e41f6 7384 daq_2.0.7-3.debian.tar.xz bdf7dcbda7e2c96c3c40f346a85698c08443eb84 7152 daq_2.0.7-3_i386.buildinfo Checksums-Sha256: 4c1af1706e3c98ade2bf4c935ebfb4e6ccae246bd194faa31a199416104169fd 1809
Bug#960479: marked as done (libdaq-dev: Missing dependencies on libdumbnet-dev, libnetfilter-queue-dev, libpcap0.8-dev)
Your message dated Sun, 19 Jul 2020 11:03:36 + with message-id and subject line Bug#960479: fixed in daq 2.0.7-3 has caused the Debian Bug report #960479, regarding libdaq-dev: Missing dependencies on libdumbnet-dev, libnetfilter-queue-dev, libpcap0.8-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdaq-dev Version: 2.0.7-2 Severity: serious Tags: ftbfs Control: affects -1 src:snort https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/snort.html ... checking for dlsym in -ldl... yes checking for daq_load_modules in -ldaq_static... no ERROR! daq_static library not found, go get it from http://www.snort.org/. ... configure:13020: checking for daq_load_modules in -ldaq_static configure:13045: gcc -o conftest -g -O2 -ffile-prefix-map=/build/1st/snort-2.9.15.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -Wl,-z,relro -Wl,-z,now -lpcre -ldumbnet conftest.c -ldaq_static -ldumbnet -lpcre -lpcap -lnsl -lm -lm -lcrypto -ldl -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet >&5 /usr/bin/ld: cannot find -lnfnetlink /usr/bin/ld: cannot find -lnetfilter_queue collect2: error: ld returned 1 exit status ... This is due to: $ daq-modules-config --static --libs -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet $ --- End Message --- --- Begin Message --- Source: daq Source-Version: 2.0.7-3 Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?= We believe that the bug you reported is fixed in the latest version of daq, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña (supplier of updated daq 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, 19 Jul 2020 11:50:12 +0200 Source: daq Architecture: source Version: 2.0.7-3 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Javier Fernández-Sanguino Peña Closes: 818893 960479 964786 Changes: daq (2.0.7-3) unstable; urgency=medium . * debian/control: - Remove duplicate Build-Dep on libpcap0.8-dev - Add Dependency on libdaq-dev on libpcap0.8-dev, libdumbnet-dev, libnetfilter-queue-dev. (Closes: #960479, #964786) Thanks to Adrian Bunk for spotting this error which is due the following: $ daq-modules-config --static --libs -L/usr/lib/x86_64-linux-gnu -ldaq_static_modules -lsfbpf -lpcap -lsfbpf -lnfnetlink -lnetfilter_queue -lsfbpf -lpcap -ldumbnet - Remove Build-Dep on dh-autoreconf (lintian warning) - Remove duplicate Section: (lintian warning) . * debian/libdaq2.install, debian/libdaq-dev.install: Add daq plugins into the binary package (added usr/lib/*/daq/*.so) and remove from -dev package (Closes: #818893) * debian/libdaq-dev.install: Remove static libraries (usr/lib/*/lib*.a) * debian/watch: Created file to look up for new versions Checksums-Sha1: 39d93ed01b7fa950b7bf3d4cd41797dc0f7121da 1809 daq_2.0.7-3.dsc 657285de4512b9bd2e70f4d8705bb06e41f6 7384 daq_2.0.7-3.debian.tar.xz bdf7dcbda7e2c96c3c40f346a85698c08443eb84 7152 daq_2.0.7-3_i386.buildinfo Checksums-Sha256: 4c1af1706e3c98ade2bf4c935ebfb4e6ccae246bd194faa31a199416104169fd 1809 daq_2.0.7-3.dsc 2160d84bf40dcac8b292ea77020fa55a3cb91b1d36dc94344c3c2baadf6c363b 7384 daq_2.0.7-3.debian.tar.xz 63ee0de8527645bdb9d23a732900806607e607955390777dcc021d8746231499 7152 daq_2.0.7-3_i386.buildinfo Files: 640b403a803d1402cd406a221849711d 1809 libs optional daq_2.0.7-3.dsc 6c4467e0820238bcd4b6a0b1cb4358e5 7384 libs optional daq_2.0.7-3.debian.tar.xz 4821266b5f18c84abf1b2dd75b497e71 7152 libs optional daq_2.0.7-3_i386.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEFQ8Kq6ttIR
Bug#964608: marked as done (kronosnet: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Sun, 19 Jul 2020 10:48:46 + with message-id and subject line Bug#964608: fixed in kronosnet 1.18-1 has caused the Debian Bug report #964608, regarding kronosnet: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kronosnet Version: 1.16-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[6]: Entering directory '/<>/libnozzle/tests' > SKIP: api_nozzle_set_down_test > SKIP: api_nozzle_close_test > SKIP: api_nozzle_set_up_test > SKIP: api_nozzle_open_test > SKIP: api_nozzle_get_mac_test > SKIP: api_nozzle_get_mtu_test > SKIP: api_nozzle_set_mtu_test > SKIP: api_nozzle_set_mac_test > SKIP: api_nozzle_get_handle_by_name_test > SKIP: api_nozzle_run_updown_test > SKIP: api_nozzle_get_fd_test > SKIP: api_nozzle_get_name_by_handle_test > SKIP: api_nozzle_del_ip_test > SKIP: api_nozzle_add_ip_test > SKIP: api_nozzle_get_ips_test > SKIP: int_execute_bin_sh_command_test > > Testsuite summary for kronosnet 1.16 > > # TOTAL: 16 > # PASS: 0 > # SKIP: 16 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > > make[6]: Leaving directory '/<>/libnozzle/tests' > make[5]: Leaving directory '/<>/libnozzle/tests' > make[4]: *** [Makefile:1472: check-am] Error 2 > make[4]: Leaving directory '/<>/libnozzle/tests' > make[3]: *** [Makefile:675: check-recursive] Error 1 > make[3]: Leaving directory '/<>/libnozzle' > make[2]: *** [Makefile:568: check-recursive] Error 1 > make[2]: Leaving directory '/<>' > make[1]: *** [Makefile:867: check] Error 2 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/07/09/kronosnet_1.16-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: kronosnet Source-Version: 1.18-1 Done: =?utf-8?q?Ferenc_W=C3=A1gner?= We believe that the bug you reported is fixed in the latest version of kronosnet, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner (supplier of updated kronosnet 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, 19 Jul 2020 10:42:59 +0200 Source: kronosnet Architecture: source Version: 1.18-1 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Ferenc Wágner Closes: 964608 Changes: kronosnet (1.18-1) unstable; urgency=medium . * [c86d5b2] New upstream release (1.18) (Closes: #964608) * [82e8201] Delete upstreamed patch * [69db591] Acknowledge new symbols Checksums-Sha1: c08c8fe8bd974d69ff6a5d7628ffa18e10a3ec71 2960 kronosnet_1.18-1.dsc de4e35c32a0376262ba7672555ba3d846de5ce9e 489540 kronosnet_1.18.orig.tar.xz e5de11b7a1995e11636d7543a3d15022b8d4eb4a 833 kronosnet_1.18.orig.tar.xz.asc 30efb932712e5383e2281ed69702b50263150b0d 9572 kronosnet_1.18-1.debian.tar.xz 2d5ac94ec0f9ee7cb51bd6d2634bd034c20923af 7940 kronosnet_1.18-1_amd64.buildinfo Checksums-Sha256: 8ba985c91492638993a8c2b35a8121e39c3b2677ee312ec706d20323f81c81f8 2960 kronosnet_1.18-1.dsc fa5238b843cbf41c0408780665db8ebe131c3cf38b71d8365ff3ab67a614fea8 489540 kronosnet_1.18.orig.tar.xz d41abf0a264
Bug#964836: marked as done (haskell-heist: BD-Uninstallable)
Your message dated Sun, 19 Jul 2020 12:47:06 +0200 with message-id <20200719104706.gd3626...@ramacher.at> and subject line Re: Bug#964836: haskell-heist: BD-Uninstallable has caused the Debian Bug report #964836, regarding haskell-heist: BD-Uninstallable 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.) -- 964836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-heist Version: 1.1.0.1-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-heist build-depends on missing: - libghc-hashable-dev:amd64 (< 1.3) libghc-hashable-dev is at version 1.3.0.0-2. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 1.1.0.1-3 On 2020-07-11 00:07:58 +0200, Sebastian Ramacher wrote: > Source: haskell-heist > Version: 1.1.0.1-2 > Severity: serious > Tags: ftbfs sid bullseye > Justification: fails to build from source (but built successfully in the past) > > haskell-heist build-depends on missing: > - libghc-hashable-dev:amd64 (< 1.3) > > libghc-hashable-dev is at version 1.3.0.0-2. Fixed in 1.1.0.1-3. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Processed: tagging 942064
Processing commands for cont...@bugs.debian.org: > tags 942064 + bullseye sid Bug #942064 [src:profphd] profphd: autopkgtest failure Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 942064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964832: marked as done (haskell-th-desugar: template-haskell >=2.8 && <2.15)
Your message dated Sun, 19 Jul 2020 12:44:51 +0200 with message-id <20200719104451.gc3626...@ramacher.at> and subject line Re: Bug#964832: haskell-th-desugar: template-haskell >=2.8 && <2.15 has caused the Debian Bug report #964832, regarding haskell-th-desugar: template-haskell >=2.8 && <2.15 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.) -- 964832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-th-desugar Version: 1.9-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-th-desugar currently fails to build: | CallStack (from HasCallStack): | die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-3.0.1.0:Distribution.Simple.Configure | configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in Cabal-3.0.1.0:Distribution.Simple.Configure | configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in Cabal-3.0.1.0:Distribution.Simple | confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in Cabal-3.0.1.0:Distribution.Simple.UserHooks | configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in Cabal-3.0.1.0:Distribution.Simple | defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in Cabal-3.0.1.0:Distribution.Simple | defaultMain, called at Setup.hs:2:8 in main:Main | hlibrary.setup: Encountered missing or private dependencies: | template-haskell >=2.8 && <2.15 See https://buildd.debian.org/status/fetch.php?pkg=haskell-th-desugar&arch=amd64&ver=1.9-1%2Bb1&stamp=159924&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 1.10-1 On 2020-07-10 23:51:59 +0200, Sebastian Ramacher wrote: > Source: haskell-th-desugar > Version: 1.9-1 > Severity: serious > Tags: ftbfs sid bullseye > Justification: fails to build from source (but built successfully in the past) > > haskell-th-desugar currently fails to build: > | CallStack (from HasCallStack): > | die', called at > libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in > Cabal-3.0.1.0:Distribution.Simple.Configure > | configureFinalizedPackage, called at > libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in > Cabal-3.0.1.0:Distribution.Simple.Configure > | configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 > in Cabal-3.0.1.0:Distribution.Simple > | confHook, called at > libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in > Cabal-3.0.1.0:Distribution.Simple.UserHooks > | configureAction, called at > libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in > Cabal-3.0.1.0:Distribution.Simple > | defaultMainHelper, called at > libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in > Cabal-3.0.1.0:Distribution.Simple > | defaultMain, called at Setup.hs:2:8 in main:Main > | hlibrary.setup: Encountered missing or private dependencies: > | template-haskell >=2.8 && <2.15 Fixed in 1.10-1. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#964671: comedilib: FTBFS: ccQsDx8i.s: Error: invalid attempt to declare external version name as default in symbol `comedi_internal_trigger@@v0.9.0'
Hi Lucas Thanks. Sorry for a late response. On Thursday, 9 July 2020 12:44:06 CEST you wrote: > > /tmp/ccQsDx8i.s: Error: invalid attempt to declare external version name > > as default in symbol `comedi_internal_trigger@@v0.9.0' make[4]: *** > > [Makefile:652: libcomedi_la-insn_config_wrappers.lo] Error 1 This is the best reference I can find: https://github.com/alsa-project/alsa-lib/issues/6 But I still don't know how to solve the issue. I will discuss this with upstream. Regards Gudjon
Bug#965311: uuagc: source missing
Package: src:uuagc Version: 0.9.52.2-1 Severity: serious The source for the program is missing. The changelog explicitly states so: * Do not use UUAGC for compilation, since the AG sources are missing. Fallback to using the included Haskell sources (Closes: #912241). However packages in Debian are supposed to include source code. Ansgar
Processed: affects 964879
Processing commands for cont...@bugs.debian.org: > affects 964879 request-tracker4 Bug #964879 [libgnupg-interface-perl] request-tracker4: FTBFS: broken by libgnupg-interface-perl Added indication that 964879 affects request-tracker4 > thanks Stopping processing here. Please contact me if you need assistance. -- 964879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > notforwarded 965307 Bug #965307 [sssd] sssd-ad: Login issues with SSSD 2.3 for AD back end Unset Bug forwarded-to-address > forwarded 965307 https://github.com/SSSD/sssd/issues/5183 Bug #965307 [sssd] sssd-ad: Login issues with SSSD 2.3 for AD back end Set Bug forwarded-to-address to 'https://github.com/SSSD/sssd/issues/5183'. > End of message, stopping processing here. Please contact me if you need assistance. -- 965307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965308: jackd won't start
Package: jackd2 Version: 1.9.14~dfsg-0.1 Severity: grave X-Debbugs-Cc: it9...@gmail.com Hi, after the update jackd is not starting anymore. Apparently this is related. Sun Jul 19 10:05:53 2020: ERROR: Can't load "/usr/lib/x86_64-linux- gnu/jack/jack_alsa.so": /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: undefined symbol: _ZN4Jack17JackServerGlobals26on_device_reservation_loopE -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.8-xanmod2 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 jackd2 depends on: ii coreutils 8.32-2 ii debconf [debconf-2.0] 1.5.74 ii libasound2 1.2.2-2.3 ii libc6 2.31-1 ii libdbus-1-31.12.20-1 ii libexpat1 2.2.9-1 ii libgcc-s1 10.1.0-6 ii libjack-jackd2-0 1.9.14~dfsg-0.1 ii libreadline8 8.0-4 ii libsamplerate0 0.1.9-2 ii libsndfile11.0.28-8 ii libstdc++6 10.1.0-6 ii python33.8.2-3 ii python3-dbus 1.2.16-3 Versions of packages jackd2 recommends: ii jackd2-firewire 1.9.14~dfsg-0.1 ii libpam-modules 1.3.1-5 ii qjackctl 0.6.2-1 Versions of packages jackd2 suggests: pn jack-tools pn meterbridge -- debconf information: * jackd/tweak_rt_limits: true
Processed: your mail
Processing commands for cont...@bugs.debian.org: > clone 965143 -1 Bug #965143 [sssd] sssd: SSSD 2.3 won't let log in or use sudo Bug 965143 cloned as bug 965307 > retitle -1 sssd-ad: Login issues with SSSD 2.3 for AD back end Bug #965307 [sssd] sssd: SSSD 2.3 won't let log in or use sudo Changed Bug title to 'sssd-ad: Login issues with SSSD 2.3 for AD back end' from 'sssd: SSSD 2.3 won't let log in or use sudo'. > tags -1 patch fixed-upstream Bug #965307 [sssd] sssd-ad: Login issues with SSSD 2.3 for AD back end Added tag(s) fixed-upstream and patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 965143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965143 965307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964840: marked as done (haskell-aeson-extra: BD-Uninstallable)
Your message dated Sun, 19 Jul 2020 07:48:30 + with message-id and subject line Bug#964840: fixed in haskell-aeson-extra 0.4.1.3-1 has caused the Debian Bug report #964840, regarding haskell-aeson-extra: BD-Uninstallable 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.) -- 964840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-aeson-extra Version: 0.4.1.1-5 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-aeson-extra build-depends on missing: - libghc-base-compat-batteries-dev:amd64 (< 0.11) libghc-base-compat-batteries-dev is at version 0.11.1-3. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: haskell-aeson-extra Source-Version: 0.4.1.3-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-aeson-extra, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-aeson-extra 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, 18 Jul 2020 10:07:47 +0300 Source: haskell-aeson-extra Architecture: source Version: 0.4.1.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 964840 Changes: haskell-aeson-extra (0.4.1.3-1) unstable; urgency=medium . [ Sean Whitton ] * New upstream release (Closes: #964840) . [ Ilias Tsitsimpis ] * Bump std-version to 4.5.0 Checksums-Sha1: 14aa0a53a4fc600534ba3f873c776e8fcbce8be2 4364 haskell-aeson-extra_0.4.1.3-1.dsc 3e2e371f9c01b4b74750fdfa23619209cd8a892c 11584 haskell-aeson-extra_0.4.1.3.orig.tar.gz 10623f0b5a60d0fbefe30e923364e9f7899157fe 3332 haskell-aeson-extra_0.4.1.3-1.debian.tar.xz 7eb95d2e6c1c55cadc9d4da65e0e77a9ce03f467 5776 haskell-aeson-extra_0.4.1.3-1_source.buildinfo Checksums-Sha256: 50bcd2ba18f1f96b1eb6dc98a576d64dbe427ba6ce0a0620f4218f37bf2c0b6f 4364 haskell-aeson-extra_0.4.1.3-1.dsc 22e3e2b6d243fb9bc660899dbb677cb6f1f8c348cfc7464082b60ce3fcdc25cc 11584 haskell-aeson-extra_0.4.1.3.orig.tar.gz c898fa078dab4e8094240fd0c7f28827f1e17763aeb91d979c878fe9b421c7d6 3332 haskell-aeson-extra_0.4.1.3-1.debian.tar.xz a696a9db0d519d6a338f425dfb7711a3bbd53c5f3f117ff4c1fed6a3b26d0c80 5776 haskell-aeson-extra_0.4.1.3-1_source.buildinfo Files: 526d9168f5c7f7a49b376a4915c61a03 4364 haskell optional haskell-aeson-extra_0.4.1.3-1.dsc a057bd607ee46769311519abd72f30d8 11584 haskell optional haskell-aeson-extra_0.4.1.3.orig.tar.gz 6e18ef7191d3e08210774b012250610b 3332 haskell optional haskell-aeson-extra_0.4.1.3-1.debian.tar.xz ebe27cc2d21501291cd3a3e6330f4af2 5776 haskell optional haskell-aeson-extra_0.4.1.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8T+SwUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDyLPxAAqvDPmjmrTuFneECkDFQbqYDoXpz9 h7owwUtLvktm7KmllwrUBAktPhw4b+KoDhkr3HaS+J1UNRyqQVsyMXA1h9J3Rzma KN7X3uKwMiTkcIAyOTX42i/hVsgPDXYAsgzBhKeHuPPcI1LzxxmalKh4bg4k2fqo R9/SxeNf748gp5svUU0SsFohzC8KjZ8Vtsk6+mRrEdJekCUY9W9HGL5QwFGX8hRb iOg3KWdA+qplJOQrLCNO0EGYvWBPDS8YVT1y6Qq3QB91NZmnJFgywMGZ8zmSS4l6 YfPkRZRleJxQwT2WieLg7+p+3vxHsuzPe0VaWC8TOABB5974mEmqj+pRNxfOUQpd J5VHZ4g9CW9+0ainwvsDz3CNh4yRtAXx9abkt3AYnVKCZIEbVwdgL11+Qr8Qg+6l urRSrB8CgnQwbW/O+qiU6Vb2qN0vOcfbZTUeseT/gsh2/ykbmlNIBFtg4M2FhfcL mu2ziUv5qpvHfThVXwMT0oE8M7IJR0nUkLFz5vWK3Lxe1UEXl8uqgX1Rux9rFkgu BMuDgUL1AKik/rDMFxrGPH8ea95Z84/zuyRXq4K4T5qnXh5XrORVclB0nxXuWiRx FFQaMHHWH46jCGzi9j7omxMnAlmnQYcSxqrrJf5OtHaOGapKiC4jNdfK8Fnh/QHb TRjATTeKlLnWK4Y= =azLK -END PGP SIGNATURE End Message ---
Bug#912241: marked as done (uuagc FTBFS: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern.)
Your message dated Sun, 19 Jul 2020 07:50:01 + with message-id and subject line Bug#912241: fixed in uuagc 0.9.52.2-2 has caused the Debian Bug report #912241, regarding uuagc FTBFS: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern. 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.) -- 912241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uuagc Version: 0.9.52.1-2 Severity: serious Tags: ftbfs uuagc fails to build from source in unstable on the official buildds for any arch tried thus far: https://buildd.debian.org/status/fetch.php?pkg=uuagc&arch=amd64&ver=0.9.52.1-2&stamp=1538622922&raw=0 | src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern. | First definition: "src-ag/Patterns.ag"(line 22, column 23). | Other definition: "src-ag/Patterns.ag"(line 22, column 23). | src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized attribute copy of nonterminal Patterns. | First definition: "src-ag/Patterns.ag"(line 22, column 23). | Other definition: "src-ag/Patterns.ag"(line 22, column 23). ... | make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: uuagc Source-Version: 0.9.52.2-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of uuagc, 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 912...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated uuagc 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, 18 Jul 2020 11:52:12 +0300 Source: uuagc Architecture: source Version: 0.9.52.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 912241 Changes: uuagc (0.9.52.2-2) unstable; urgency=medium . * Do not use UUAGC for compilation, since the AG sources are missing. Fallback to using the included Haskell sources (Closes: #912241). Checksums-Sha1: 097e682b85826fadba6bb745c8189175bfea0bd9 2208 uuagc_0.9.52.2-2.dsc 14317207ae79769a7b3acc7a77f56abdd782fc1c 6192 uuagc_0.9.52.2-2.debian.tar.xz c5945232ef92158ae1cbb7b990548307f79c9cae 5660 uuagc_0.9.52.2-2_source.buildinfo Checksums-Sha256: 70466ca470ba07ddc736a61fb83d9f448832712f302bf41bee0ab675d8254285 2208 uuagc_0.9.52.2-2.dsc 80ed9553d54dd82f391cb5cc9f4475cb96efc3eb0452ef9aeea1e522c6371788 6192 uuagc_0.9.52.2-2.debian.tar.xz 51ac845caadffd45723cb57b02acbf37598cda813d3bdc19720239c297857cc2 5660 uuagc_0.9.52.2-2_source.buildinfo Files: 517c582f2a6efd68d99ebe51fba8f4ed 2208 devel optional uuagc_0.9.52.2-2.dsc de473140b48ca81567753845dc589e28 6192 devel optional uuagc_0.9.52.2-2.debian.tar.xz e871e60dc90e47930e79987933f1afe6 5660 devel optional uuagc_0.9.52.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8T+aMUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDxnUhAAxiQN/63yyhn3WVg6wsooy+aveoIP mHwK5GRiwFW0I6Eii8Az8x5PxpuGRU99Pa4z/7UGoSsK1WNv4+C+KmsfF5NnnTa7 w3ZPx21UE+yzF2vQm49+9TOUA6D6qp1k4LdzhBqxJVt24YKpdjjI6IJKZQimY96G 1Gu6WntkjRl6RUnNEzJmzFjmCi/XX+S9hVxGLugL/9oJ+JIh24PmTwqkj0dXJ1MB Y32tEKItDqc997lURIQpdd07+Qn55Gfk/uQ4zNwqL3XdTrZsnp3lG2eCE8fenWIr 8+0RzofV/m+o0jHy4Nrys7NOllltFohgb31E+CE4iIKpofCAqQQHtbARdOEBRCFE eueHDfmGZPBnT/2qI0/+3e8TlYZPllb+wKA673mxDvsr+6QjcarqFPv33gzolwE1 vPmcS2HyBXQTVZlXk7yozhlYOF4i5ZTM9pumIm6V5kdDlv2r+1IjNFXyJURelY3m 5SO4iG57UBM3UGk1H++7tEFqsfel+LTWnlu2SbqS2KuOTqQLTPqxtjShKrZA3uPY v2aE0/gMLfpZzrR2AfcYswVBhaXj3pWKqpNRB7Bh8fz+KumL0PP9375JyS8h4bx/ 7pVNIljXHXP8NNV/8Phoqu3yqowj9MUI12HWvCVinc5nFiQuDNCh8wzCmPF6Ou39 /WG4JUe6g1jAe3Q= =HbBK -END PGP SIGNATURE End Message ---
Bug#964841: marked as done (haskell-servant-server: BD-Uninstallable)
Your message dated Sun, 19 Jul 2020 07:49:37 + with message-id and subject line Bug#964841: fixed in haskell-servant-server 0.16.2-2 has caused the Debian Bug report #964841, regarding haskell-servant-server: BD-Uninstallable 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.) -- 964841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-servant-server Version: 0.16.2-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-servant-server build-depends on missing: - libghc-base-compat-dev:amd64 (< 0.11) libghc-base-compat-dev is at version 0.11.1-1. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: haskell-servant-server Source-Version: 0.16.2-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-servant-server, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-servant-server 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, 18 Jul 2020 11:26:21 +0300 Source: haskell-servant-server Architecture: source Version: 0.16.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 964841 Changes: haskell-servant-server (0.16.2-2) unstable; urgency=medium . * Patch for newer deps (Closes: #964841) * Re-enable tests on s390x Checksums-Sha1: 99479f6830e972cb5a2c5c8eb3d47a531e172ac2 5275 haskell-servant-server_0.16.2-2.dsc f23492b42ada74f98c99ce66bb8e04f43e321d6e 4056 haskell-servant-server_0.16.2-2.debian.tar.xz 74b4e2c0c1c7b87f906d93812333e0b42c2d2c1b 5793 haskell-servant-server_0.16.2-2_source.buildinfo Checksums-Sha256: 00ffd97abdd6a3509b3599776c9b2202d82349742c374522a74a99dfccee9e3f 5275 haskell-servant-server_0.16.2-2.dsc 286b157cb78b1b82e3bbe77a320063566a663937c99f9b56f842771b2752d4e8 4056 haskell-servant-server_0.16.2-2.debian.tar.xz ff0ef99a8b625997240eddb54e5b6012ce19449492c45df873a618a086798d0e 5793 haskell-servant-server_0.16.2-2_source.buildinfo Files: 6695a2eb19d8c5a15c91372fa39ca51a 5275 haskell optional haskell-servant-server_0.16.2-2.dsc 42a58d36d6777318c20674e614b85964 4056 haskell optional haskell-servant-server_0.16.2-2.debian.tar.xz 0b6bb32f25e2f388182241005b5aab48 5793 haskell optional haskell-servant-server_0.16.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8T+YsUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDwDcQ/3Tw7r2VsVod/e1fSjOe4fLuPbU2wt zu03rDKFMHUvgZ/P/6adn/xg+5eQ3cMamMW4FuU+y2u82S5EQjfKWmHV/sF5CdYl 8hna+7cIozYrT2iBGzAOB6O/CC4by3HPrEXYZGr0fyq1Q5IsTjTBdgg1l17dPj5f BKmAwi99xyVsYjPSV4bCprCJlb3YReyrXwxBQqKJWIJtG7pItc5Q4WYOsV/M2YPe AAKsOpWquloJUnxizHGjtmDWxYRo/Qf8e6WcDGAjwsng116nUXPXvF6b0q1JDuRN t7UITDDEkCbpDoHHHl3Mt6CWeBulT/sdquoqI+yZTA82CTbC3aNoKz3GXMLVtkzl 5KMMGa3ZpNmR3Q2cnvadIBubhRpOAIDU9UldjCdr2s1n2upN9ru6hSiDwLXlX2zS eKGfE1wlZImhfzqK1vR9uKPIyr46p8BaDM7hPzl/oULme1fXN2pmkCxAWcShZrzb nb6lhplnbNVDqmVOA+Eoy/+fnKiitVzVlddeK2jOvBT9yrXo3haI4afS8BH5jeOJ 1QbAl5eRSCx9sgP9XMK2O8X7gnYilNdLB3U1uXENIKoOPuWUTaghKURZI43bGvgY 1wyCzaXK39PgMbB2Ja9lGwC3jwKBLPGTGDk5EZ5qnhZ5wGnpkZzUlZ1/xgiFm52c AQ/rUC47oT3IDg== =yq+Y -END PGP SIGNATURE End Message ---
Bug#965306: adplay: FTBFS: error: no matching function for call to ‘CSurroundopl::CSurroundopl(Copl*&, Copl*&, bool)’
Source: adplay Version: 1.8-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) adplay currently fails to build: | adplay.cc: In function ‘int main(int, char**)’: | adplay.cc:410:50: error: no matching function for call to ‘CSurroundopl::CSurroundopl(Copl*&, Copl*&, bool)’ | 410 | opl = new CSurroundopl(a, b, cfg.bits == 16); | | ^ | In file included from adplay.cc:52: | /usr/include/adplug/surroundopl.h:67:3: note: candidate: ‘CSurroundopl::CSurroundopl(COPLprops*, COPLprops*, bool)’ |67 | CSurroundopl(COPLprops *a, COPLprops *b, bool output16bit); | | ^~~~ | /usr/include/adplug/surroundopl.h:67:27: note: no known conversion for argument 1 from ‘Copl*’ to ‘COPLprops*’ |67 | CSurroundopl(COPLprops *a, COPLprops *b, bool output16bit); | |~~~^ | /usr/include/adplug/surroundopl.h:51:7: note: candidate: ‘constexpr CSurroundopl::CSurroundopl(const CSurroundopl&)’ |51 | class CSurroundopl: public Copl | | ^~~~ | /usr/include/adplug/surroundopl.h:51:7: note: candidate expects 1 argument, 3 provided See https://buildd.debian.org/status/fetch.php?pkg=adplay&arch=amd64&ver=1.8-2%2Bb1&stamp=1595115090&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
