Bug#968637: freeimage: FTBFS against libraw 0.20.0
Upstream seem to have a fix for this. https://sourceforge.net/p/freeimage/svn/1842/
Bug#957439: libforms: ftbfs with GCC-10
On Tue, 2020-08-25 at 17:30 -0400, Peter S Galbraith wrote: > Thanks so much! I am on vacation so *should* have time to look into this > soonish. Would you like to take over the package? I would be happy for > you to do that! Great, thanks. Please note that the upstream commit isn't exactly a clean logical commit so it may be hard to fix this FTBFS in Debian unless upstream can be convinced to make a new release. If you contact them you may want to also get them to start making clean logical commits and remove all the generated files. I already have too many packages so I don't want to accumulate more, I just wanted libforms to stay in Debian so that mancala stays in Debian too. If you decide to orphan it I'll try to fix future RC bugs though. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#957439: libforms: ftbfs with GCC-10
Thanks so much! I am on vacation so *should* have time to look into this soonish. Would you like to take over the package? I would be happy for you to do that! Peter > Control: tags -1 + fixed-upstream > Control: forwarded -1 > https://git.savannah.nongnu.org/cgit/xforms.git/commit/?id=2c1a9f151baf50887a517280645ec23379fb96f8 > > On Fri, 17 Apr 2020 11:04:17 + Matthias Klose wrote: > > > The package fails to build in a test rebuild on at least amd64 with > > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. > > This issue has been fixed in the upstream git repository (link above): > >Fix GCC 19 linker problem (hopefully) and some other minor changes > > I verified that the GCC 10 build failure is fixed, but it still FTBFS > because the debian/*.install files need to be updated to use wildcards. > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise > > -- Peter S. Galbraith, Debian Developer http://people.debian.org/~psg GPG key 4096/70D4A979 6309 28AE 8EB3 AB57 22F3 03BC 17DC 3CC4 70D4 A979
Processed: Bug#966436 marked as pending in ruby-mini-magick
Processing control commands: > tag -1 pending Bug #966436 [src:ruby-mini-magick] scrambled property in identify -verbose output Added tag(s) pending. -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966436: marked as pending in ruby-mini-magick
Control: tag -1 pending Hello, Bug #966436 in ruby-mini-magick reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-mini-magick/-/commit/58f4acbfe7f398a28dd421b97d354e60ed01ada4 Add a patch to fix 'identify' parsing (Closes: #966436) (this message was generated automatically) -- Greetings https://bugs.debian.org/966436
Bug#960965: marked as done (kazoo: autopkgtest regression: kazoo.handlers.threading.KazooTimeoutError: Connection time-out)
Your message dated Tue, 25 Aug 2020 21:19:31 +
with message-id
and subject line Bug#960965: fixed in kazoo 2.7.0-3
has caused the Debian Bug report #960965,
regarding kazoo: autopkgtest regression:
kazoo.handlers.threading.KazooTimeoutError: Connection time-out
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.)
--
960965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kazoo
Version: 2.7.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of kazoo the autopkgtest of kazoo fails in testing
when that autopkgtest is run with the binary packages of kazoo from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
kazoo from testing2.7.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=kazoo
https://ci.debian.net/data/autopkgtest/testing/amd64/k/kazoo/5541537/log.gz
+ export ZOOKEEPER_PATH=/usr/share/java
+ + dpkgawk {print $3}
-l
+ grep libzookeeper-java
+ sed -E s/([0-9]+:)?([^-]+)([-~+].+)?/\2/
+ export ZOOKEEPER_VERSION=3.4.13
+ python3 -m nose -d -v kazoo.tests
/tmp/autopkgtest-lxc.c_g8cpxq/downtmp/build.xs6/src/kazoo/protocol/serialization.py:114:
SyntaxWarning: "is" with a literal. Did you mean "=="?
read_only = bool_struct.unpack_from(bytes, offset)[0] is 1
/tmp/autopkgtest-lxc.c_g8cpxq/downtmp/build.xs6/src/kazoo/protocol/serialization.py:449:
SyntaxWarning: "is" with a literal. Did you mean "=="?
return cls(t, done is 1, err), offset
test_barrier_exists (kazoo.tests.test_barrier.KazooBarrierTests) ...
SLF4J: Detected both log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on
the class path, preempting StackOverflowError.
SLF4J: See also http://www.slf4j.org/codes.html#log4jDelegationLoop for
more details.
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:72)
at
org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:45)
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.(QuorumPeerMain.java:67)
Caused by: java.lang.IllegalStateException: Detected both
log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on the class path,
preempting StackOverflowError. See also
http://www.slf4j.org/codes.html#log4jDelegationLoop for more details.
at
org.slf4j.impl.Log4jLoggerFactory.(Log4jLoggerFactory.java:54)
... 8 more
SLF4J: Detected both log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on
the class path, preempting StackOverflowError.
SLF4J: See also http://www.slf4j.org/codes.html#log4jDelegationLoop for
more details.
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:72)
at
org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:45)
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.(QuorumPeerMain.java:67)
Caused by: java.lang.IllegalStateException: Detected both
log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on the class path,
preempting StackOverflowError. See also
http://www.slf4j.org/codes.html#log4jDelegationLoop for more details.
at
org.slf4j.impl.Log4jLoggerFactory.(Log4jLoggerFactory.java:54)
... 8 more
SLF4J: Detected both log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on
the class
Bug#957470: FTBFS Bugs in Debian revdeps dahdi-tools and libpri
On 19/08/2020 12:31, Bernhard Schmidt wrote: Hi Tzafrir, could you have a look at Bug#957117 and #957470? They are causing Asterisk to be removed from testing. Uploaded a fix for dahdi-tools. As for libpri: this is basically using index from data[0] that is the end of the header. My "fix" is to silence those checks (see patches). There hopefully seems to be some upstream work, but I'm not sure how long it would take. -- Tzafrir ~/Proj/Salsa/pkg-voip/libpri/libpri/libpri-gerrit ~/Proj/Salsa/hpc/perftest/perftest ~/Proj/Salsa/pkg-voip/libpri/libpri/libpri-gerrit diff --git a/Makefile b/Makefile index 077b8bf..825a6fe 100644 --- a/Makefile +++ b/Makefile @@ -70,6 +70,7 @@ CFLAGS ?= -g CFLAGS += $(CPPFLAGS) CFLAGS += -Wall -Werror -Wstrict-prototypes -Wmissing-prototypes CFLAGS += -fPIC $(ALERTING) $(LIBPRI_OPT) $(COVERAGE_CFLAGS) +CFLAGS += -Wno-zero-length-bounds -Wno-stringop-overflow INSTALL_PREFIX=$(DESTDIR) INSTALL_BASE=/usr libdir?=$(INSTALL_BASE)/lib
Bug#956982: marked as done (adns: ftbfs with GCC-10)
Your message dated Tue, 25 Aug 2020 22:52:00 +0200 with message-id <36330200.MvuTd3xYt6@johansson> and subject line adns 1.6.0-1 successfully builds from source has caused the Debian Bug report #956982, regarding adns: ftbfs with GCC-10 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.) -- 956982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:adns Version: 1.5.1-0.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/adns_1.5.1-0.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] 939 | #define GET_W(cb,tv) ((tv)=0,(tv)|=(GETIL_B((cb))<<8), (tv)|=GETIL_B(cb), (tv)) | ~~~^~~ ../src/reply.c:60:3: note: in expansion of macro ‘GET_W’ 60 | GET_W(cbyte,arcount); | ^ gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -Wno-pointer-sign -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fpic -I. -I../src -I./../src -c -o general_p.o ../src/general.c gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -Wno-pointer-sign -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fpic -I. -I../src -I./../src -c -o setup_p.o ../src/setup.c gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -Wno-pointer-sign -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fpic -I. -I../src -I./../src -c -o transmit_p.o ../src/transmit.c gcc -g -O2 -Wall -Wmissing-prototypes -Wwrite-strings -Wstrict-prototypes -Wcast-qual -Wpointer-arith -Wno-pointer-sign -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fpic -I. -I../src -I./../src -c -o parse_p.o ../src/parse.c In file included from ../src/parse.c:27: ../src/parse.c: In function ‘adns__findrr_anychk’: ../src/internal.h:939:73: warning: right-hand operand of comma expression has no effect [-Wunused-value] 939 | #define GET_W(cb,tv) ((tv)=0,(tv)|=(GETIL_B((cb))<<8), (tv)|=GETIL_B(cb), (tv)) | ~~~^~~ ../src/parse.c:219:3: note: in expansion of macro ‘GET_W’ 219 | GET_W(cbyte,tmp); *type_r= tmp; | ^ ../src/internal.h:939:73: warning: right-hand operand of comma expression has no effect [-Wunused-value] 939 | #define GET_W(cb,tv) ((tv)=0,(tv)|=(GETIL_B((cb))<<8), (tv)|=GETIL_B(cb), (tv)) | ~~~^~~ ../src/parse.c:220:3: note: in expansion of macro ‘GET_W’ 220 | GET_W(cbyte,tmp); *class_r= tmp; | ^ ../src/internal.h:944:27: warning: right-hand operand of comma expression has no effect [-Wunused-value] 940 | #define GET_L(cb,tv) ( (tv)=0,\ | ~~ 941 | (tv)|=(GETIL_B((cb))<<24), \ | 942 | (tv)|=(GETIL_B((cb))<<16), \ | 943 | (tv)|=(GETIL_B((cb))<<8), \ |
Bug#960965: marked as pending in kazoo
Control: tag -1 pending Hello, Bug #960965 in kazoo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/kazoo/-/commit/14ad5625051205aaee9572e678cc489dfcb6c31d Removed autopkgtest (Closes: #960965). (this message was generated automatically) -- Greetings https://bugs.debian.org/960965
Processed: Bug#960965 marked as pending in kazoo
Processing control commands: > tag -1 pending Bug #960965 [src:kazoo] kazoo: autopkgtest regression: kazoo.handlers.threading.KazooTimeoutError: Connection time-out Added tag(s) pending. -- 960965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 966436 in ruby-mini-magick/4.9.5-2
Processing commands for cont...@bugs.debian.org: > found 966436 ruby-mini-magick/4.9.5-2 Bug #966436 [src:ruby-mini-magick] scrambled property in identify -verbose output Marked as found in versions ruby-mini-magick/4.9.5-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 966436 to src:ruby-mini-magick
Processing commands for cont...@bugs.debian.org: > reassign 966436 src:ruby-mini-magick Bug #966436 [src:imagemagick] scrambled property in identify -verbose output Bug reassigned from package 'src:imagemagick' to 'src:ruby-mini-magick'. No longer marked as found in versions imagemagick/8:6.9.11.24+dfsg-1n and imagemagick/8:6.9.11.24+dfsg-1. Ignoring request to alter fixed versions of bug #966436 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957673: marked as done (perftest: ftbfs with GCC-10)
Your message dated Tue, 25 Aug 2020 20:36:09 + with message-id and subject line Bug#957673: fixed in perftest 4.4+0.29-1 has caused the Debian Bug report #957673, regarding perftest: ftbfs with GCC-10 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.) -- 957673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:perftest Version: 4.4+0.5-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/perftest_4.4+0.5-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] checking for rdma_create_event_channel in -lrdmacm... yes checking for umad_init in -libumad... yes checking for log in -lm... yes checking for infiniband/verbs_exp.h... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-am make[2]: Entering directory '/<>' gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/send_bw.o src/send_bw.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/multicast_resources.o src/multicast_resources.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/get_clock.o src/get_clock.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/perftest_communication.o src/perftest_communication.c In file included from /usr/include/x86_64-linux-gnu/sys/time.h:21, from src/get_clock.c:43: /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/perftest_parameters.o src/perftest_parameters.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/perftest_resources.o src/perftest_resources.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/raw_ethernet_resources.o src/raw_ethernet_resources.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o src/send_lat.o src/send_lat.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -D_GNU_SOURCE -O3 -g -O2 -fdebug-prefix-map=/<>=.
Bug#957117: marked as done (dahdi-tools: ftbfs with GCC-10)
Your message dated Tue, 25 Aug 2020 20:33:41 + with message-id and subject line Bug#957117: fixed in dahdi-tools 1:3.1.0-1 has caused the Debian Bug report #957117, regarding dahdi-tools: ftbfs with GCC-10 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.) -- 957117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dahdi-tools Version: 1:3.0.0-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/dahdi-tools_3.0.0-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxtalk_la-xlist.lo `test -f 'xlist.c' || echo './'`xlist.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c xlist.c -fPIC -DPIC -o .libs/libxtalk_la-xlist.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c xlist.c -o libxtalk_la-xlist.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxtalk_la-debug.lo `test -f 'debug.c' || echo './'`debug.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c debug.c -fPIC -DPIC -o .libs/libxtalk_la-debug.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c debug.c -o libxtalk_la-debug.o >/dev/null 2>&1 /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wno-unknown-pragmas -Werror -DXTALK_DLL -DXTALK_DLL_EXPORTS -I./include -I. -I/usr/include/libusb-1.0 -DXTALK_OPTIONS_FILE=\"/etc/dahdi/xpp.conf\" -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o libxtalk_la-xtalk-xusb.lo `test -f 'xtalk-xusb.c' || echo './'`xtalk-xusb.c libtool: compile: gcc -DHAVE_CONFIG_H -I.
Bug#968079: marked as done (libapache2-mod-wsgi: Package is not installable. Needs older Python2.)
Your message dated Tue, 25 Aug 2020 19:49:44 + with message-id and subject line Bug#968079: fixed in mod-wsgi 4.7.1-2 has caused the Debian Bug report #968079, regarding libapache2-mod-wsgi: Package is not installable. Needs older Python2. 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.) -- 968079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libapache2-mod-wsgi Version: 4.6.8-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to install the package, the following message is displayed: == begin Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be installed Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be installed Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed E: Unable to correct problems, you have held broken packages. == end The problem is that my Python2 is: python22.7.18-2 amd64 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libapache2-mod-wsgi depends on: ii apache2-bin [apache2-api-20120211] 2.4.43-1 ii libc6 2.31-3 ii libpython2.72.7.18-1 pn python libapache2-mod-wsgi recommends no packages. libapache2-mod-wsgi suggests no packages. --- End Message --- --- Begin Message --- Source: mod-wsgi Source-Version: 4.7.1-2 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of mod-wsgi, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated mod-wsgi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Aug 2020 07:40:03 -0300 Source: mod-wsgi Architecture: source Version: 4.7.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Emmanuel Arias Closes: 937062 968079 Changes: mod-wsgi (4.7.1-2) unstable; urgency=medium . [ Emmanuel Arias ] * Remove py2 support. Closes: #937062. - No need to instal older py2 packages. Closes: #968079. * Set myself as Uploaders. * d/rules: Stop use dh --paralel, it's not longer need. * d/tests: Remove autopkgtest for py2. * d/source/lintian-overrides: Override lintian error. - Override a false positive about the python3 dependency and python3 helper is not used. . [ Sergio Durigan Junior ] * d/copyright: Update download URL. * d/control: Remove needless dh-autoreconf B-D. * d/rules: Simplify "pkgdir" variable. Checksums-Sha1: d4eb626dfbbd4c8573e5a89f2a0742abea43395f 2081 mod-wsgi_4.7.1-2.dsc 31d1873cbc7e7128270ff7de6bb96e3d0deeef83 10572 mod-wsgi_4.7.1-2.debian.tar.xz 85dc8b0d6f10392531b1b2516d0881984d1941f8 7034 mod-wsgi_4.7.1-2_amd64.buildinfo Checksums-Sha256: 43527bdd98391864b0f8860f5901d6c7cc9bea73e65857a4a377640ff34e37d7 2081 mod-wsgi_4.7.1-2.dsc 642d7f15edfc4b893e1cee5caf1aadcfce813c509b0b23057fbec0de3a25cbfe 10572 mod-wsgi_4.7.1-2.debian.tar.xz 94e8f269ccbfad994a171209ff546b3e944656699282e5e651c3fb67b10f301f 7034 mod-wsgi_4.7.1-2_amd64.buildinfo Files: e4628829db972d525f6f77b8a1e7f077 2081 httpd
Bug#937062: marked as done (mod-wsgi: Python2 removal in sid/bullseye)
Your message dated Tue, 25 Aug 2020 19:49:44 + with message-id and subject line Bug#937062: fixed in mod-wsgi 4.7.1-2 has caused the Debian Bug report #937062, regarding mod-wsgi: 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.) -- 937062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mod-wsgi Version: 4.6.5-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:mod-wsgi 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: mod-wsgi Source-Version: 4.7.1-2 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of mod-wsgi, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated mod-wsgi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Aug 2020 07:40:03 -0300 Source: mod-wsgi Architecture: source Version: 4.7.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Emmanuel Arias Closes: 937062 968079 Changes: mod-wsgi (4.7.1-2) unstable; urgency=medium . [ Emmanuel Arias ] * Remove py2 support. Closes: #937062. - No need to instal older py2 packages. Closes: #968079. * Set myself as Uploaders. * d/rules: Stop use dh --paralel, it's not longer need. * d/tests: Remove autopkgtest for py2. * d/source/lintian-overrides: Override lintian error. - Override a false positive about the python3 dependency and python3 helper is not used. . [ Sergio Durigan Junior ] * d/copyright: Update download URL. * d/control: Remove needless dh-autoreconf B-D. * d/rules: Simplify "pkgdir" variable. Checksums-Sha1: d4eb626dfbbd4c8573e5a89f2a0742abea43395f 2081 mod-wsgi_4.7.1-2.dsc
Processed: duperemove: diff for NMU version 0.11.1-3.1
Processing control commands: > tags 957152 + patch Bug #957152 [src:duperemove] duperemove: ftbfs with GCC-10 Added tag(s) patch. > tags 957152 + pending Bug #957152 [src:duperemove] duperemove: ftbfs with GCC-10 Added tag(s) pending. -- 957152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957152: duperemove: diff for NMU version 0.11.1-3.1
Control: tags 957152 + patch
Control: tags 957152 + pending
Dear maintainer,
I've prepared an NMU for duperemove (versioned as 0.11.1-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru duperemove-0.11.1/debian/changelog duperemove-0.11.1/debian/changelog
--- duperemove-0.11.1/debian/changelog 2019-01-10 13:18:07.0 +
+++ duperemove-0.11.1/debian/changelog 2020-08-25 19:37:15.0 +0100
@@ -1,3 +1,11 @@
+duperemove (0.11.1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-10. (Closes: #957152)
+- Use upstream patch.
+
+ -- Sudip Mukherjee Tue, 25 Aug 2020 19:37:15
+0100
+
duperemove (0.11.1-3) unstable; urgency=medium
* Add cross.patch (Closes: #918500)
diff -Nru
duperemove-0.11.1/debian/patches/0005-Fix-declare_alloc_tracking-macro-229.patch
duperemove-0.11.1/debian/patches/0005-Fix-declare_alloc_tracking-macro-229.patch
---
duperemove-0.11.1/debian/patches/0005-Fix-declare_alloc_tracking-macro-229.patch
1970-01-01 01:00:00.0 +0100
+++
duperemove-0.11.1/debian/patches/0005-Fix-declare_alloc_tracking-macro-229.patch
2020-08-25 19:11:37.0 +0100
@@ -0,0 +1,57 @@
+From 58dd49fb429339b7104c23224f45aa99c5d160a0 Mon Sep 17 00:00:00 2001
+From: Nikolay Borisov
+Date: Wed, 10 Jun 2020 18:27:12 +0300
+Subject: [PATCH] Fix declare_alloc_tracking macro (#229)
+
+This macro erroneously omitted using the passed _type argument when
+defining gmutex. Furthermore, every mutex defined by the macro is
+accessed via static functions implying it's private. Thus also make
+it static.
+---
+
+upstream link:
https://github.com/lorddoskias/duperemove/commit/58dd49fb429339b7104c23224f45aa99c5d160a0
+
+ memstats.h | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/memstats.h b/memstats.h
+index e01005f..6f79cd6 100644
+--- a/memstats.h
b/memstats.h
+@@ -57,7 +57,7 @@ static inline void decrement_counters(unsigned long long
*num_type,
+ }
+
+ #define declare_alloc_tracking(_type) \
+-GMutexalloc_##_mutex;
\
++static GMutex alloc_##_type##_mutex; \
+ unsigned long long num_##_type = 0; \
+ unsigned long long max_##_type = 0; \
+ static inline struct _type *malloc_##_type(void) \
+@@ -65,7 +65,7 @@ static inline struct _type *malloc_##_type(void)
\
+ struct _type *t = malloc(sizeof(struct _type)); \
+ if (t) \
+ increment_counters(_##_type, _##_type, 1ULL,\
+- _##_mutex);\
++ _##_type##_mutex); \
+ return t; \
+ } \
+ static inline struct _type *calloc_##_type(int n) \
+@@ -73,13 +73,13 @@ static inline struct _type *calloc_##_type(int n)
\
+ struct _type *t = calloc(n, sizeof(struct _type)); \
+ if (t) \
+ increment_counters(_##_type, _##_type, n, \
+- _##_mutex);\
++ _##_type##_mutex); \
+ return t; \
+ } \
+ static inline void free_##_type(struct _type *t) \
+ { \
+ if (t) {\
+- decrement_counters(_##_type, _##_mutex); \
++ decrement_counters(_##_type, _##_type##_mutex);
\
+ free(t);\
+ } \
+ } \
+--
+2.20.1
+
diff -Nru duperemove-0.11.1/debian/patches/series
duperemove-0.11.1/debian/patches/series
--- duperemove-0.11.1/debian/patches/series 2019-01-10 11:24:57.0
+
+++ duperemove-0.11.1/debian/patches/series 2020-08-25 19:12:30.0
+0100
@@ -2,3 +2,4 @@
0002-Add-a-few-compiled-executables-to-.gitignore.patch
0003-Open-the-target-O_RDONLY-for-root-for-BTRFS_IOC_FILE.patch
0004-Allow-pkg-config-to-be-substituted.patch
+0005-Fix-declare_alloc_tracking-macro-229.patch
Bug#967124: patch for chromium bugs 965960 and 967124, possible NMU.
I have prepared a patch for chromium addressing bugs 965960 and 967124 Bug 965960 (crash on 32-bit) was caused by lack of support in the sandbox for the 64-bit time syscalls that have recently been added to Linux/glibc. I added __NR_clock_gettime64, __NR_clock_nanosleep_time64 and __NR_utimensat_time64 to the syscall whitelist. I also added __NR_clock_gettime64, __NR_clock_nanosleep_time64 to the code that filters the "clock" parameter for the __NR_clock_gettime and __NR_clock_nanosleep syscalls. After doing this the browser seemed to be usable on both Debian sid i386 and raspbian bullseye. These changes are in the patch debian/patches/allow-time64-syscalls.patch Regarding bug 967124 I started by replacing all references to "/usr/bin/python" and "env python" (mostly shebangs) with the versioned equivilents using sed. These changes are in the patch debian/patches/use-explicit-python2-sed.patch. I then changed the build-dependency from python to python2 and tried a build. This build failed with an error about being unable to find python. Some digging tracked it down to a reference to unversioned python in "gn", which I patched. This change is in debian/patches/use-explicit-python2-gn.patch . The build was then successful. I have uploaded the fixes to Raspbian bullseye. A debdiff can be found at https://debdiffs.raspbian.org/main/c/chromium/chromium_83.0.4103.116-3+rpi1.debdiff I may or may not NMU this in Debian later.
Bug#964513: marked as done (gtk+4.0: FTBFS: error: ‘VK_RESULT_RANGE_SIZE’ undeclared)
Your message dated Tue, 25 Aug 2020 15:04:50 +0100 with message-id <20200825140450.ga1796...@espresso.pseudorandom.co.uk> and subject line Re: Bug#964513: gtk+4.0: FTBFS: error: ‘VK_RESULT_RANGE_SIZE’ undeclared has caused the Debian Bug report #964513, regarding gtk+4.0: FTBFS: error: ‘VK_RESULT_RANGE_SIZE’ undeclared 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.) -- 964513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtk+4.0 Version: 3.98.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, gtk+4.0 recently started to FTBFS: [163/1487] cc -Igdk/ffe01f7@@gdk@sta -Igdk -I../../../gdk -I. -I../../.. -Igdk/x11 -I../../../gdk/x11 -Igdk/wayland -Igtk/css -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/includ e/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/graphene-1.0 -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include -I/usr/include/gio-unix-2.0 -f diagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -DG_LOG_USE_STRUCTURED=1 -DGLIB_MIN_REQUIRED_VERSION=GLIB_VERSION_2_58 -DGLIB_MAX_ALLOWED_VERSION=GLIB_VERSION_2_60 '-DGTK_VERSION="3.98.2"' -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/build/gtk+4. 0-3.98.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -mfpmath=sse -msse -msse2 -DGTK_COMPILATION '-DG_LOG_DOMAIN="Gdk"' -fno-strict-aliasing -Wcast-align -Wduplicated-branches -Wduplicated-cond -W format=2 -Wformat-nonliteral -Wformat-security -Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op -Wmisleading-indentation -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wnull-dereference -Wold-style-defi nition -Wpointer-arith -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=implicit -Werror=implicit-fallthrough -Werror=init-self -Werror=int-to-pointer- cast -Werror=main -Werror=missing-braces -Werror=missing-declarations -Werror=missing-prototypes -Werror=nonnull -Werror=pointer-to-int-cast -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=vla -Werror=write-strings -fvisibility=hidden -MD -MQ 'gdk/ffe01f7@@gdk@sta/gdkvulkancontext.c.o' -MF 'gdk/ffe01f7@@gdk@sta/gdkvulkancontext.c.o.d' -o 'gdk/ffe01f7@@gdk@sta/gdkvulkancontext.c.o' -c ../../../gdk/gdkvulkancontext.c FAILED: gdk/ffe01f7@@gdk@sta/gdkvulkancontext.c.o cc -Igdk/ffe01f7@@gdk@sta -Igdk -I../../../gdk -I. -I../../.. -Igdk/x11 -I../../../gdk/x11 -Igdk/wayland -Igtk/css -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/graphene-1.0 -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include -I/usr/include/gio-unix-2.0 -fdiagnostics -color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -DG_LOG_USE_STRUCTURED=1 -DGLIB_MIN_REQUIRED_VERSION=GLIB_VERSION_2_58 -DGLIB_MAX_ALLOWED_VERSION=GLIB_VERSION_2_60 '-DGTK_VERSION="3.98.2"' -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/build/gtk+4.0-3.98.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -mfpmath=sse -msse -msse2 -DGTK_COMPILATION '-DG_LOG_DOMAIN="Gdk"' -fno-strict-aliasing -Wcast-align -Wduplicated-branches -Wduplicated-cond -Wformat=2 -W format-nonliteral -Wformat-security -Wignored-qualifiers -Wimplicit-function-declaration -Wlogical-op -Wmisleading-indentation -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wnull-dereference -Wold-style-definition -Wpo inter-arith -Wshadow -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=implicit -Werror=implicit-fallthrough -Werror=init-self -Werror=int-to-pointer-cast -Werro r=main -Werror=missing-braces -Werror=missing-declarations -Werror=missing-prototypes -Werror=nonnull -Werror=pointer-to-int-cast -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=vla -Werror=write-strings
Bug#968993: lilypond: CVE-2020-17353
Source: lilypond Version: 2.20.0-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.19.81+really-2.18.2-13 Hi, The following vulnerability was published for lilypond. CVE-2020-17353[0]: | scm/define-stencil-commands.scm in LilyPond through 2.20.0, and 2.21.x | through 2.21.4, when -dsafe is used, lacks restrictions on embedded-ps | and embedded-svg, as demonstrated by including dangerous PostScript | code. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-17353 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17353 [1] http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=b84ea4740f3279516905c5db05f4074e777c16ff Regards, Salvatore
Processed: lilypond: CVE-2020-17353
Processing control commands: > found -1 2.19.81+really-2.18.2-13 Bug #968993 [src:lilypond] lilypond: CVE-2020-17353 Marked as found in versions lilypond/2.19.81+really-2.18.2-13. -- 968993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 956084 in 2:1.9.4-7
Processing commands for cont...@bugs.debian.org:
> # for the BTS affected graph
> found 956084 2:1.9.4-7
Bug #956084 {Done: Guillem Jover } [inetutils-telnetd]
inetutils-telnetd: CVE-2020-10188
Marked as found in versions inetutils/2:1.9.4-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
956084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Patch available on salsa
Processing control commands: > tag -1 patch Bug #966751 [src:libapache2-mod-python] libapache2-mod-python: Unversioned Python removal in sid/bullseye Added tag(s) patch. -- 966751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Patch available on salsa
Processing control commands: > tag -1 patch Bug #883157 [src:libapache2-mod-python] libapache2-mod-python: Please support for Python3 Added tag(s) patch. -- 883157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883157: Patch available on salsa
Control: tag -1 patch There is a patch available on https://salsa.debian.org/python-team/modules/libapache2-mod-python which is not in the last upload's Vcs-Git.
Bug#954195: gnome-music fails to start
Package: gnome-music Version: 3.36.3-1 Followup-For: Bug #954195 Dear Maintainer, gnome-music still fails to start on version 3.36.3-1 in sid with the following traceback: $ gnome-music Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gnomemusic/scrobbler.py", line 81, in _new_client_callback manager.call_is_supported_provider( AttributeError: 'NoneType' object has no attribute 'call_is_supported_provider' -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/6 CPU threads) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.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 gnome-music depends on: ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii gir1.2-dazzle-1.03.36.0-1 ii gir1.2-glib-2.0 1.64.1-1 ii gir1.2-goa-1.0 3.36.0-1 ii gir1.2-grilo-0.3 0.3.12-1 ii gir1.2-gst-plugins-base-1.0 1.16.2-4 ii gir1.2-gstreamer-1.0 1.16.2-2 ii gir1.2-gtk-3.0 3.24.22-1 ii gir1.2-mediaart-2.0 1.9.4-2 ii gir1.2-soup-2.4 2.70.0-1 ii gir1.2-totemplparser-1.0 3.26.5-1 ii gir1.2-tracker-2.0 2.3.4-1+b1 ii gnome-settings-daemon3.36.1-1 ii grilo-plugins-0.30.3.11-1 ii libc62.31-3 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgtk-3-0 3.24.22-1 ii libpango-1.0-0 1.46.0-2 ii libpangocairo-1.0-0 1.46.0-2 ii python3 3.8.2-3 ii python3-gi 3.36.0-4 ii python3-gi-cairo 3.36.0-4 ii python3-requests 2.23.0+dfsg-2 ii tracker 2.3.4-1+b1 gnome-music recommends no packages. gnome-music suggests no packages. -- debconf-show failed
Bug#965979: marked as done (freerdp2: CVE-2020-15103)
Your message dated Tue, 25 Aug 2020 08:21:57 + with message-id and subject line Bug#965979: fixed in freerdp2 2.2.0+dfsg1-1 has caused the Debian Bug report #965979, regarding freerdp2: CVE-2020-15103 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.) -- 965979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freerdp2 Version: 2.1.2+dfsg1-2 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/FreeRDP/FreeRDP/pull/6381 X-Debbugs-Cc: Debian Security Team Hi, The following vulnerability was published for freerdp2. CVE-2020-15103[0]: | Integer overflow due to missing input sanitation in rdpegfx channel If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15103 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15103 [1] https://github.com/FreeRDP/FreeRDP/pull/6381 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: freerdp2 Source-Version: 2.2.0+dfsg1-1 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of freerdp2, 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. Mike Gabriel (supplier of updated freerdp2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Aug 2020 09:17:57 +0200 Source: freerdp2 Architecture: source Version: 2.2.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Closes: 965979 Changes: freerdp2 (2.2.0+dfsg1-1) unstable; urgency=medium . * New upstream release. + CVE-2020-15103: Integer overflow due to missing input sanitation in rdpegfx channel. (Closes: #965979). * debian/patches: + Drop 0001-mask-CACHED_BRUSH-when-checking-brush-style.patch. Applied upstream. * debian/copyright: + Update copyright attributions. * debian/libfreerdp2-2.symbols: + Update symbols. * debian/libfreerdp-server2-2.symbols: + Update symbols. Checksums-Sha1: 712529fd09f28dde25156efb3cd2be3c58cb58c2 3553 freerdp2_2.2.0+dfsg1-1.dsc e1f8d3401ba4197c722c822ed0a4459592a3eaca 1939508 freerdp2_2.2.0+dfsg1.orig.tar.xz 3cb45911cd4c249e8a322aabc9d9705690e40012 42804 freerdp2_2.2.0+dfsg1-1.debian.tar.xz 1856ac869f2b81d85361bf8d6bfcc96513b75552 16238 freerdp2_2.2.0+dfsg1-1_source.buildinfo Checksums-Sha256: bd237f3bb0e887779083831a6d0c22acb500de830925d02c8acca26b04e790b0 3553 freerdp2_2.2.0+dfsg1-1.dsc 2bbf503ee8ad52b57c636d50c1b1bc78dbc54a54b2d60e695365a514f8ae6a52 1939508 freerdp2_2.2.0+dfsg1.orig.tar.xz 97d355127aaa5b17719a14cea75d963ad50473b67b228eb958d44008bedfd4c5 42804 freerdp2_2.2.0+dfsg1-1.debian.tar.xz cbd12e2ea56f5eb8b6c326a3b77445008547b6e849f3b3138f2cc300c2694483 16238 freerdp2_2.2.0+dfsg1-1_source.buildinfo Files: d6a40fd4f33318f8ea8414f9fa7f494d 3553 x11 optional freerdp2_2.2.0+dfsg1-1.dsc 05aa9bbb07776b572432fff2582df9d0 1939508 x11 optional freerdp2_2.2.0+dfsg1.orig.tar.xz 6ec40458b2d02ac1779a8ddb151f2275 42804 x11 optional freerdp2_2.2.0+dfsg1-1.debian.tar.xz 6b79c8ca7aedd28f7db11f415b469323 16238 x11 optional freerdp2_2.2.0+dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl9EwhUVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxSocP/R+teZgB17QXPrZIe52OkEjIfCa5 DWgo1G5tFPhxuttpx+FGNLTxz+Gala0tyGAGiM6ia/75BRH/wsD16Ys7gYT+qiAF SzKBDO14o6iuvU5FwpHFMBG3rZE41TJG722B/eAHfe4kNl0e8aQKZBC7xxjFyawh f+8tFA2FWTV4JVjQ7iBSNvCGxeJ3lyo0pnZd7/+jGJOWkAyl5IcB2nqjvFXt45hb AWSsZuU4xVl54jq8BTchhpk3qV7vnG6eeH2a1h+ow/Ly5K8u/tuH5hwFBrMwxPYS lj6PbOszIp/8RQdSQCdX7gemQzuOhTC9Y6TYb/oumT9JH1hqq9Mo9YkBvLPMbuf0 xMeXN6NchLyvicRryNdeDpEfjOksePLEXcvcrSZIgmkp/i1/QrCwRGCt+6iGuOe6 vnEnXHAPeT1fzV+ivJv+zv0nclc7188UwA+9cq4sSUC5k1uy80hroZ/VgtBGcdrS
