Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
On 7/7/20 2:21 AM, John Scott wrote:
> Rebuilding dspdfviewer to see how it would fare with Poppler in
> experimental, I found it FTBFS in unstable unconditionally.
>
> /<>/pdfviewerwindow.cpp: In member function
> ‘void PDFViewerWindow::reposition()’:
> /<>/pdfviewerwindow.cpp:119:89: error:
Your message dated Wed, 08 Jul 2020 08:37:56 +
with message-id
and subject line Bug#964475: fixed in apt 2.1.7
has caused the Debian Bug report #964475,
regarding dpkg breaks apt autopkgtest: dpkg: error: unknown option
--foreign-architecture
to be marked as done.
This means that you claim
On 2020-07-06, at 19:11:09 +, Vasyl Gello wrote:
> July 6, 2020 6:58:05 PM UTC, Mattia Rizzolo написав(-ла):
> > On Mon, Jul 06, 2020 at 05:10:30AM +, Vasyl Gello wrote:
> > > Thanks for contributing the security release! I checked your
> > > changes and pushed them to the team repo. I
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
Your message dated Wed, 08 Jul 2020 09:44:48 +0200
with message-id <18e5c4f9-8e52-4d57-9647-8817ca623...@rene-engelhard.de>
and subject line
has caused the Debian Bug report #964505,
regarding Upgradin package from 1:6.4.5~rc1-2 fails
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 964505 serious
Bug #964505 [libreoffice-l10n-de] Upgradin package from 1:6.4.5~rc1-2 fails
Severity set to 'serious' from 'normal'
> fixed 964505 1:7.0.0~rc1-4
Bug #964505 [libreoffice-l10n-de] Upgradin package from 1:6.4.5~rc1-2 fails
Hi,
On Fri, 3 Jul 2020 15:36:56 +0100 Mark Hindley wrote:
> On Tue, Jun 30, 2020 at 07:43:52PM +0200, Ansgar wrote:
> > On Tue, 2020-06-30 at 17:45 +0100, Mark Hindley wrote:
> > > I am struggling to understand how libelogind0 came to be installed in the
> > > build
> > > in the first place.
Source: openzwave-controlpanel
Version: 0.2a+git20161006.a390f35-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source
Hi,
openzwave-controlpanel recently started to FTBFS with
g++ -g -O2
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Package: libextractor-plugins-all
Version: 1:1.9-4
Severity: serious
There is a typo in the Depends field, it should say
libextractor-plugin-exiv2 instead of libextractor-plugin-exiv.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message
Processing commands for cont...@bugs.debian.org:
> found 964471 1:7.0.0~rc1-1
Bug #964471 {Done: Rene Engelhard } [libreoffice-l10n-ru]
libreoffice-l10n-ru: error when configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Marked as
Your message dated Wed, 08 Jul 2020 06:37:47 +
with message-id
and subject line Bug#964315: fixed in openms 2.5.0+cleaned1-5
has caused the Debian Bug report #964315,
regarding openms FTBFS on mipsel: cc1plus: out of memory
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 08 Jul 2020 08:41:49 +
with message-id
and subject line Bug#963546: fixed in meson 0.55.0~rc2-1
has caused the Debian Bug report #963546,
regarding meson: autopkgtest failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Control: tag -1 pending
Hello,
Bug #963337 in python-mkdocs 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:
Control: tag -1 pending
Hello,
Bug #963280 in seafile-client 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:
Control: tag -1 pending
Hello,
Bug #963337 in python-mkdocs 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:
Processing control commands:
> tag -1 pending
Bug #963337 [src:python-mkdocs] python-mkdocs: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.8 returned exit code 13
Added tag(s) pending.
--
963337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963337
Debian Bug Tracking
Processing control commands:
> tag -1 pending
Bug #963280 [src:seafile-client] seafile-client: FTBFS:
./build/CMakeFiles/CMakeTmp/./build/CMakeFiles/CMakeTmp/src.c:11: undefined
reference to `pthread_create'
Added tag(s) pending.
--
963280:
Processing control commands:
> tag -1 pending
Bug #963337 [src:python-mkdocs] python-mkdocs: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.8 returned exit code 13
Ignoring request to alter tags of bug #963337 to the same tags previously set
--
963337:
Processing commands for cont...@bugs.debian.org:
> # protobuf transition started
> severity 963244 serious
Bug #963244 [src:mozc] mozc FTBFS with Protobuf 3.12.3
Ignoring request to change severity of Bug 963244 to the same value.
> severity 963246 serious
Bug #963246 [src:vg] vg FTBFS with
Source: php-yaml
Version: 2.1.0+1.3.2-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=php-yaml=sid
...
=
TEST RESULT SUMMARY
-
Control: severity -1 serious
Control: close -1 1.25.0+ds-1
On Sun, Jun 21, 2020 at 01:37:54PM +0200, László Böszörményi wrote:
> Source: vg
> Severity: normal
> Justification: fails to build from source (but built successfully in the past)
> Tags: upstream ftbfs
>
> Hi,
>
> Soon the Protobuf
Processing control commands:
> severity -1 serious
Bug #963246 [src:vg] vg FTBFS with Protobuf 3.12.3
Ignoring request to change severity of Bug 963246 to the same value.
> close -1 1.25.0+ds-1
Bug #963246 [src:vg] vg FTBFS with Protobuf 3.12.3
Marked as fixed in versions vg/1.25.0+ds-1.
Bug
Your message dated Wed, 08 Jul 2020 11:34:27 +
with message-id
and subject line Bug#964538: fixed in php-yaml 2.1.0+2.0.4+1.3.2-1
has caused the Debian Bug report #964538,
regarding php-yaml FTBFS on 32bit: Test PECL bug #74949 [tests/bug_79494.phpt]
failed
to be marked as done.
This means
Your message dated Wed, 08 Jul 2020 12:04:23 +
with message-id
and subject line Bug#963337: fixed in python-mkdocs 1.0.4+dfsg-2
has caused the Debian Bug report #963337,
regarding python-mkdocs: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
to be
On Wed, 2020-07-08 at 11:04 +0200, Johannes Schauer wrote:
> What is happening here is, that aspcud chooses libelogind0 for installation
> and
> then apt decides that it refuses to install it because it doesn't want to
> remove libsystemd0 in favor of libelogind0 and by that replace an important
Processing commands for cont...@bugs.debian.org:
> severity 963244 serious
Bug #963244 [src:mozc] mozc FTBFS with Protobuf 3.12.3
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963244:
How utterly bizarre. The original report said this also happened for i386
and amd64 for Ubuntu, and for other packaging I build foma in parallel for
all supported Debian, Ubuntu, Fedora, RHEL, OpenSUSE, and macOS - and this
parallel build fail has never happened. So I figured it was safe. But
Your message dated Wed, 08 Jul 2020 10:19:11 +
with message-id
and subject line Bug#962879: fixed in cylc 8.0~a1-5
has caused the Debian Bug report #962879,
regarding python3-cylc: should depend on fonts-font-awesome and/or
fonts-glyphicons-halflings (not fonts-glewlwyd)
to be marked as
On Wed, Jul 08, 2020 at 09:07:25AM +0100, Jeremy Sowden wrote:
...
> The new upstream release added extra checks to ensure that the object at
> the end of the path is a device file of the right sort before opening
> it:
...
> However, the error messages still leak information, allowing the user to
Package: make-dfsg
Version: 4.3-4
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch
In Ubuntu, the attached patch was applied to achieve the following:
The autopkgtests for flatpak-builder/s390x where failing with
echo Building
Processing control commands:
> tags 963764 + help
Bug #963764 [node-node-sass] node-node-sass: uses embedded old security-buggy
libsass
Added tag(s) help.
--
963764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 963764 + help
Hello,
The upstream has updated the libsass support to 3.6.3 [1], it's just not
released yet. I have successfully used head of their git repository to
build node-node-sass without the embedded libsass copy (there were a
couple of failing mocha tests, however).
I
Package: src:mutrace
Version: 0.2.0-3.2
Severity: serious
Tags: sid bullseye
mutrace should not depend on the shared binutils libraries. These are non-public
ABIs, and are changing frequently. If you have to use the dependency, then
please use the static libraries and mark the binary packages
Package: src:dropwatch
Version: 1.5.3-1
Severity: serious
Tags: sid bullseye
dropwatch should not depend on the shared binutils libraries. These are
non-public ABIs, and are changing frequently. If you have to use the dependency,
then please use the static libraries and mark the binary packages
Your message dated Wed, 08 Jul 2020 10:51:31 +
with message-id
and subject line Bug#962221: fixed in xawtv 3.107-1
has caused the Debian Bug report #962221,
regarding xawtv: CVE-2020-13696
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> found -1 1:0.9.18+r243-7
Bug #916192 {Done: Ghislain Antony Vaillant } [src:foma]
foma ftbfs from source
Marked as found in versions foma/1:0.9.18+r243-7 and reopened.
--
916192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916192
Debian Bug Tracking System
Control: found -1 1:0.9.18+r243-7
On Wed, Apr 24, 2019 at 07:51:04PM +, Debian Bug Tracking System wrote:
>...
> foma (1:0.9.18+r243-6) unstable; urgency=medium
> .
>* Team upload.
>* Drop parallel builds.
> Thanks to Adrian Bunk (Closes: #916192)
>...
This bug has been
Quoting mer...@debian.org (2020-07-08 15:13:06)
> The upstream has updated the libsass support to 3.6.3 [1], it's just
> not released yet. I have successfully used head of their git
> repository to build node-node-sass without the embedded libsass copy
> (there were a couple of failing mocha
Your message dated Wed, 08 Jul 2020 09:48:53 +
with message-id
and subject line Bug#963280: fixed in seafile-client 7.0.8-1
has caused the Debian Bug report #963280,
regarding seafile-client: FTBFS:
./build/CMakeFiles/CMakeTmp/./build/CMakeFiles/CMakeTmp/src.c:11: undefined
reference to
Your message dated Wed, 08 Jul 2020 09:48:37 +
with message-id
and subject line Bug#964449: fixed in backward-cpp 1.5-2
has caused the Debian Bug report #964449,
regarding autopkg test failures with binutils 2.35
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 08 Jul 2020 13:19:32 +
with message-id
and subject line Bug#949393: fixed in storebackup 3.2.1-2
has caused the Debian Bug report #949393,
regarding storebackup: CVE-2020-7040: denial of service and symlink attack
vector via fixed lockfile path /tmp/storeBackup.lock
Processing commands for cont...@bugs.debian.org:
> unarchive 916192
Bug #916192 {Done: Ghislain Antony Vaillant } [src:foma]
foma ftbfs from source
Unarchived Bug 916192
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
916192:
Package: src:dropwatch
Version: 1.5.3-1
Severity: serious
Tags: sid bullseye
dropwatch build times out in the testsuite, no output available in the build
log.
Quoting Nilesh Patra (2020-07-08 16:26:34)
> On Wed, 8 Jul 2020, 19:30 Jonas Smedegaard, wrote:
> > Please strongly consider to not only make the package link with
> > system-shared libsass, but also repackage upstream tarball with
> > embedded code copy removed, to ensure not accidentally
Quoting Nilesh Patra (2020-07-08 17:00:01)
> On Wed, 8 Jul 2020, 20:22 Jonas Smedegaard, wrote:
>
> > Quoting Nilesh Patra (2020-07-08 16:26:34)
> > > On Wed, 8 Jul 2020, 19:30 Jonas Smedegaard, wrote:
> > > > Please strongly consider to not only make the package link with
> > > > system-shared
Your message dated Wed, 08 Jul 2020 14:42:17 +
with message-id
and subject line Bug#964464: fixed in kimageannotator 0.3.1-5
has caused the Debian Bug report #964464,
regarding libkimageannotator-common: missing Breaks+Replaces:
libkimageannotator0 (<< 0.3.1-4)
to be marked as done.
This
Quoting Nilesh Patra (2020-07-08 17:13:49)
> On Wed, 8 Jul 2020, 20:38 Jonas Smedegaard, wrote:
> > If we expect this package to evolve badly, then we should *not* keep
> > an embedded copy of libsass, but instead remove this package and all
> > its reverse dependencies, because libsass has
On Wed, Jul 08, 2020 at 03:44:21PM +0200, Ansgar wrote:
> On Wed, 2020-07-08 at 11:04 +0200, Johannes Schauer wrote:
> > What is happening here is, that aspcud chooses libelogind0 for installation
> > and
> > then apt decides that it refuses to install it because it doesn't want to
> > remove
Hello,
On Wed, 08 Jul 2020 11:22:18 +0200 Andreas Beckmann wrote:
>
> openzwave-controlpanel recently started to FTBFS with
>
libmicrohttpd has recent API changes. The attached patch file should fix
the ftbfs with libmicrohttpd 0.9.71. It also fixes a gcc warning with
uninitialized value.
Source: mini-buildd
Version: 1.1.38
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
mini-buildd/experimental FTBFS with
[...]
I: Generating src/mini-buildd-super-portext.1...
Traceback (most recent call last):
File "setup.py", line 96, in
setuptools.setup(
On Wed, 8 Jul 2020, 20:22 Jonas Smedegaard, wrote:
> Quoting Nilesh Patra (2020-07-08 16:26:34)
> > On Wed, 8 Jul 2020, 19:30 Jonas Smedegaard, wrote:
> > > Please strongly consider to not only make the package link with
> > > system-shared libsass, but also repackage upstream tarball with
> >
Hi,
On Wed, 8 Jul 2020, 19:30 Jonas Smedegaard, wrote:
> Quoting mer...@debian.org (2020-07-08 15:13:06)
> > The upstream has updated the libsass support to 3.6.3 [1], it's just
> > not released yet. I have successfully used head of their git
> > repository to build node-node-sass without the
Source: vuls
Version: 0.7.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
vuls/experimental recently started to FTBFS:
debian/rules build
dh build --buildsystem=golang --with=golang
dh: warning: Compatibility levels before 10
On Wed, 8 Jul 2020, 20:38 Jonas Smedegaard, wrote:
> Quoting Nilesh Patra (2020-07-08 17:00:01)
> > On Wed, 8 Jul 2020, 20:22 Jonas Smedegaard, wrote:
> >
> > > Quoting Nilesh Patra (2020-07-08 16:26:34)
> > > > On Wed, 8 Jul 2020, 19:30 Jonas Smedegaard, wrote:
> > > > > Please strongly
Processing control commands:
> retitle -1 don't just run /bin/true in autopkgtest
Bug #964406 [src:onionbalance] onionbalance: autopkgtest regression:
debian/tests/upstream does not exist
Changed Bug title to 'don't just run /bin/true in autopkgtest' from
'onionbalance: autopkgtest regression:
Control: retitle -1 don't just run /bin/true in autopkgtest
Hi,
Although you "fixed" bug #964406 (without closing it), your solution is
unacceptable by the release team. Your autopkgtest must be testing your
installed package to some degree, or be marked as superficial. Your
autopkgtest is only
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
Your message dated Wed, 08 Jul 2020 18:03:37 +
with message-id
and subject line Bug#959579: fixed in adapta-gtk-theme 3.95.0.11-2
has caused the Debian Bug report #959579,
regarding adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> tag 964507 + pending
Bug #964507 [src:libextractor] libextractor: typo in Testsuite-Triggers:
libextractor-plugin[s]-all
Added tag(s) pending.
> tag 964508 + pending
Bug #964508 [libextractor-plugins-all] libextractor-plugins-all: not
Source: nageru
Version: 2.0.0-3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
nageru currently fails to build:
| FAILED: shared/a4d2686@@shared@sta/httpd.cpp.o
| c++ -Ishared/a4d2686@@shared@sta -Ishared -I../shared -I.
On Wed, Jul 08, 2020 at 08:26:36PM +0200, Steinar H. Gunderson wrote:
> Has libmicrohttpd changed ABI or something? I assume the size of size_t
> hasn't changed :-)
Indeed, they broke the API:
Wed 08 Apr 2020 10:53:01 PM CEST
Introduce `enum MHD_Result` for #MHD_YES/#MHD_NO to avoid using
On Wed, Jul 08, 2020 at 08:15:01PM +0200, Sebastian Ramacher wrote:
> | ../shared/httpd.cpp:47:25: error: invalid conversion from ‘int (*)(void*,
> MHD_Connection*, const char*, const char*, const char*, const char*, size_t*,
> void**)’ {aka ‘int (*)(void*, MHD_Connection*, const char*, const
Source: kazoo
Version: 2.6.1-6
Severity: serious
Control: close -1 2.7.0-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 960965
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync
Processing control commands:
> close -1 8.1.0+r23-4
Bug #964567 [src:android-platform-art] src:android-platform-art: fails to
migrate to testing for too long: FTBFS on arm64
Marked as fixed in versions android-platform-art/8.1.0+r23-4.
Bug #964567 [src:android-platform-art]
Processing control commands:
> close -1 2.7.0-2
Bug #964569 [src:kazoo] src:kazoo: fails to migrate to testing for too long:
autopkgtest failure
Marked as fixed in versions kazoo/2.7.0-2.
Bug #964569 [src:kazoo] src:kazoo: fails to migrate to testing for too long:
autopkgtest failure
Marked Bug
Source: android-platform-art
Version: 8.1.0+r23-3
Severity: serious
Control: close -1 8.1.0+r23-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync
Processing control commands:
> close -1 1:16.0.0~rc1-2
Bug #964570 [src:neutron-fwaas] src:neutron-fwaas: fails to migrate to testing
for too long: piuparts regression
Marked as fixed in versions neutron-fwaas/1:16.0.0~rc1-2.
Bug #964570 [src:neutron-fwaas] src:neutron-fwaas: fails to migrate to
Source: neutron-fwaas
Version: 1:15.0.1-1
Severity: serious
Control: close -1 1:16.0.0~rc1-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Processing commands for cont...@bugs.debian.org:
> tags 947051 + ftbfs bullseye sid
Bug #947051 [src:latencytop] latencytop: Non-sensical source format and version
Added tag(s) ftbfs, bullseye, and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947051:
Your message dated Wed, 08 Jul 2020 20:34:46 +
with message-id
and subject line Bug#964406: fixed in onionbalance 0.2.0-3
has caused the Debian Bug report #964406,
regarding don't just run /bin/true in autopkgtest
to be marked as done.
This means that you claim that the problem has been
Control: notfound -1 CVE-2020-4044
Control: found -1 0.9.12-1
On Wed, Jul 08, 2020 at 10:28:43PM +0200, Salvatore Bonaccorso wrote:
> Source: xrdp
> Version: CVE-2020-4044
Sorry for the broken report (not sure how I managed to do that broken
version using), fixing the metadata.
Regards,
Processing control commands:
> notfound -1 CVE-2020-4044
Bug #964573 [src:xrdp] xrdp: CVE-2020-4044
The source 'xrdp' and version 'CVE-2020-4044' do not appear to match any binary
packages
No longer marked as found in versions xrdp/CVE-2020-4044.
> found -1 0.9.12-1
Bug #964573 [src:xrdp] xrdp:
Processing commands for cont...@bugs.debian.org:
> notfound 962497 r-base/4.0.1-1
Bug #962497 {Done: =?utf-8?q?Dylan_A=C3=AFssi?= }
[src:r-base, src:r-cran-data.table] r-base breaks r-cran-data.table
autopkgtest: 'origin' must be supplied
No longer marked as found in versions r-base/4.0.1-1.
>
Control: tags -1 + moreinfo
Hi,
Jeremy Turnbull wrote (9 Sep 2019):
> Package: tasksel
> Version: 3.53
> Severity: critical
> Justification: breaks unrelated software
First of all, I wonder why this did not came to notice for such a long time.
I thought RC bugs would trigger an automatic
Processing control commands:
> tags -1 + moreinfo
Bug #939813 [tasksel] tasksel: selected packages marked for removal on apt
full-upgrade
Added tag(s) moreinfo.
--
939813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Source: xrdp
Version: CVE-2020-4044
Severity: grave
Tags: security upstream
Hi,
The following vulnerability was published for xrdp.
CVE-2020-4044[0]:
| The xrdp-sesman service before version 0.9.13.1 can be crashed by
| connecting over port 3350 and supplying a malicious payload. Once the
|
Your message dated Wed, 08 Jul 2020 21:34:08 +
with message-id
and subject line Bug#963360: fixed in ocaml-ffmpeg 0.4.2-1
has caused the Debian Bug report #963360,
regarding ocaml-ffmpeg: FTBFS: Error: Unbound type constructor Codec_id.video
to be marked as done.
This means that you claim
On 2020-07-07 17:54, Kunal Mehta wrote:
> Upstream libkiwix ticket discussing the issue is
> https://github.com/kiwix/kiwix-lib/issues/373, but I (and upstream) believe
> this is an unexexpected breaking change in libmicrohttpd.
According to
Your message dated Thu, 09 Jul 2020 04:18:36 +
with message-id
and subject line Bug#964495: fixed in libkiwix 9.3.0+dfsg-1
has caused the Debian Bug report #964495,
regarding libmicrohttpd: New 0.97.1-1 version causes libkiwix to FTBFS
to be marked as done.
This means that you claim that the
83 matches
Mail list logo
