Your message dated Sun, 04 Sep 2022 06:53:02 +
with message-id
and subject line Bug#1013415: fixed in r-cran-rstantools 2.2.0-2
has caused the Debian Bug report #1013415,
regarding r-cran-rstantools: r-cran-rstan needs recompilation autopkgtest
regression with r-cran-rcppparallel
to be marked
Source: golang-github-bmatsuo-lmdb-go
Version: 1.8.0+git20170215.a14b5a3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on s390x.
Because the unstable-to-tes
Source: libpqtypes
Version: 1.5.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on arm64.
Because the unstable-to-testing migration software now blocks on
r
Source: argyll
Version: 2.3.0+repack-1
Severity: serious
Control: close -1 2.3.1+repack-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for m
Processing control commands:
> close -1 2.3.1+repack-1
Bug #1019120 [src:argyll] src:argyll: fails to migrate to testing for too long:
uploader built arch:all binaries
Marked as fixed in versions argyll/2.3.1+repack-1.
Bug #1019120 [src:argyll] src:argyll: fails to migrate to testing for too long
Processing control commands:
> close -1 3:22.1.0-5
Bug #1019119 [src:horizon] src:horizon: fails to migrate to testing for too
long: autopkgtest failure
Marked as fixed in versions horizon/3:22.1.0-5.
Bug #1019119 [src:horizon] src:horizon: fails to migrate to testing for too
long: autopkgtest f
Source: horizon
Version: 3:22.1.0-2
Severity: serious
Control: close -1 3:22.1.0-5
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1018787
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Looks like it might be a QT bug:
https://bugs.kde.org/show_bug.cgi?id=433084
Your message dated Sat, 3 Sep 2022 21:33:36 -0400
with message-id <20220904013336.yohx25q6aoqxoapb@localhost>
and subject line Re: Bug#1018956: kitty: Kitty has broken python 3.9
dependencies
has caused the Debian Bug report #1018956,
regarding kitty: Kitty has broken python 3.9 dependencies
to be
Processing commands for cont...@bugs.debian.org:
> tags 1019106 bookworm sid ftbfs pending
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for
evolution-data-server 3.46
Added tag(s) pending, ftbfs, sid, and bookworm.
>
End of message, stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> fixed 1019106 43~beta-1
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for
evolution-data-server 3.46
Marked as fixed in versions gnome-initial-setup/43~beta-1.
>
End of message, stopping processing here.
Please conta
Processing commands for cont...@bugs.debian.org:
> block 1019106 by 1016765
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for
evolution-data-server 3.46
1019106 was not blocked by any bugs.
1019106 was not blocking any bugs.
Added blocking bug(s) of 1019106: 1016765
>
Source: gnome-initial-setup
Version: 42.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: evolution-3.46
gnome-initial-setup needs to be updated for the big
evolution-data-server transition (which switches to libsoup3 and
librest 0.9).
This is done in the 43 vers
There is a new upstream version of petgraph that uses the new version of
fixedbitset, I suspect the most sensible way to fix this bug is
uploading it and it has been prepared in debcargo-conf (initially
byBlair Noctis with some further tweaking by myself)
However before I upload it, I wanted t
Processing control commands:
> retitle -1 gnuplot and gnuplot-data not available
Bug #1019061 [gnuplot] gnuplot-data not available
Changed Bug title to 'gnuplot and gnuplot-data not available' from
'gnuplot-data not available'.
> reassign -1 src:gnuplot 5.4.4+dfsg1-1
Bug #1019061 [gnuplot] gnuplo
Control: retitle -1 gnuplot and gnuplot-data not available
Control: reassign -1 src:gnuplot 5.4.4+dfsg1-1
This is actually a problem for the binary packages gnuplot-qt,
gnuplot-x11 and gnuplot-nox. The gnuplot metapackage is not
available either, while it is still mentioned at
https://packages.
Processing control commands:
> severity -1 serious
Bug #1019061 [gnuplot] gnuplot-data not available
Severity set to 'serious' from 'important'
--
1019061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags 984256 + pending
Bug #984256 [src:nextepc] nextepc: ftbfs with GCC-11
Added tag(s) pending.
--
984256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 984256 + pending
--
Dear maintainer,
I've prepared an NMU for nextepc (versioned as 0.3.10+nods-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
--
Regards
Sudip
diff -Nru nextepc-0.3.10+nods/debian/changelog
nextepc-0.3.10+nods/debian/c
Processing control commands:
> severity -1 normal
Bug #1018717 [orage] orage: Segmentation fault
Severity set to 'normal' from 'grave'
> forwarded -1 https://gitlab.xfce.org/apps/orage/-/issues/2
Bug #1018717 [orage] orage: Segmentation fault
Set Bug forwarded-to-address to 'https://gitlab.xfce.or
Control: severity -1 normal
Control: forwarded -1 https://gitlab.xfce.org/apps/orage/-/issues/2
Howdy,
Thanks for providing some information and testing on unstable, I was about
to close the bug report as it lacked any information and was clearly a
FrankenDebian[0].
What you're seeing is due
Your message dated Sat, 03 Sep 2022 22:19:39 +
with message-id
and subject line Bug#1011732: fixed in gtk-d 3.10.0-2
has caused the Debian Bug report #1011732,
regarding gtk-d: FTBFS: build-dependency not installable:
libphobos2-ldc-shared98 (>= 1:1.28.0)
to be marked as done.
This means tha
Processing commands for cont...@bugs.debian.org:
> tags 1018796 + ftbfs
Bug #1018796 [mir-core] mir-core: FTBFS with gdc: unrecognized commandline
option -preview=dip1008
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1018796: https://bugs.de
Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id
and subject line Bug#1012219: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1012219,
regarding r-cran-rstan: FTBFS with onetbb/2021.5.0-9 in experimental
to be marked as done.
This means that you claim that the
Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id
and subject line Bug#1012144: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1012144,
regarding r-cran-shinystan: FTBFS with onetbb/2021.5.0-8 in experimental
to be marked as done.
This means that you claim that
Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id
and subject line Bug#1011218: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1011218,
regarding r-cran-brms: FTBFS with onetbb/2021.5.0-8 in experimental
to be marked as done.
This means that you claim that the p
Your message dated Sat, 03 Sep 2022 21:17:08 +
with message-id
and subject line Bug#1015224: fixed in rocksdb 6.11.4-3+deb11u1
has caused the Debian Bug report #1015224,
regarding Illegal instruction (SIGILL) on arm64
to be marked as done.
This means that you claim that the problem has been d
Processing commands for cont...@bugs.debian.org:
> reassign 1013415 r-cran-rstantools 2.2.0-1
Bug #1013415 [src:r-cran-rstan] r-cran-rstantools: r-cran-rstan needs
recompilation autopkgtest regression with r-cran-rcppparallel
Bug reassigned from package 'src:r-cran-rstan' to 'r-cran-rstantools'.
Hi Jeremy,
On Sat, 13 Aug 2022 01:48:54 + Debian FTP Masters
wrote:
gjs (1.73.1-2) unstable; urgency=medium
.
* Rebuild against latest mozjs91 (Closes: #1017063)
You forgot to enforce this with a *versioned* build dependency and now
armhf got build with the old version.
But anywa
Processing commands for cont...@bugs.debian.org:
> reassign 1012144 r-cran-rstan 2.21.5-1
Bug #1012144 [src:r-cran-shinystan] r-cran-shinystan: FTBFS with
onetbb/2021.5.0-8 in experimental
Bug reassigned from package 'src:r-cran-shinystan' to 'r-cran-rstan'.
No longer marked as found in versions
Processing control commands:
> severity 1010578 serious
Bug #1010578 [osmo-mgw] osmo-mgw: FTBFS if systemd is in build environment
Severity set to 'serious' from 'normal'
--
1010578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010578
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Hi all,
On 9/3/22 22:06, Benjamin K Goodrich wrote:
Sorry for the late reply. I am told that StanHeaders can be built
successfully with oneTBB by setting environmental variables like
TBB_INC and TBB_LIB. On CRAN, we would like to use the version of TBB
that comes with the RcppParallel package
[.
Control: tags 1018971 + patch
Control: tags 1018971 + pending
Dear maintainer,
I've prepared an NMU for poppler (versioned as 22.08.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru poppler-22.08.0/debian/changelog poppler-
Processing control commands:
> tags 1018971 + patch
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Added tag(s) patch.
> tags 1018971 + pending
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Added tag(s) pending.
--
1018971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018971
Debia
Your message dated Sat, 3 Sep 2022 20:40:47 +0100
with message-id <05750882-de1f-757a-6810-4173bf599...@debian.org>
and subject line re: librust-once-cell-dev: impossible to satidfy dependency on
librust-parking-lot-core-0.8-dev
has caused the Debian Bug report #1019044,
regarding librust-once-cel
Processing commands for cont...@bugs.debian.org:
> found 1018971 20.09.0-3.1
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Marked as found in versions poppler/20.09.0-3.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1018971: https://bugs.debian.org/cgi-bi
Package: rust-ahash
Version: 0.7.6-4
Severity: serious
The autopkgtest of rust-ahash is failing
https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-ahash/25673987/log.gz
Testing aeshash/u8
thread 'main' panicked at 'aes must be enabled', tests/bench.rs:20:5
stack backtrace:
0: std:
Source: tbb
Version: 2020.3-2.1
Severity: serious
src:tbb: do not migrate. this source is deprecated in favor of
src:onetbb. The RM bug of src:tbb is filed at
https://bugs.debian.org/1014990
Processing control commands:
> reassign -1 swi-prolog-core
Bug #1006818 [eye] eye fails to work on !amd64
Bug reassigned from package 'eye' to 'swi-prolog-core'.
No longer marked as found in versions eye/19.0221.2026~ds-1.
Ignoring request to alter fixed versions of bug #1006818 to the same values
Control: reassign -1 swi-prolog-core
Control: retitle -1 intermediary files embed arch-specific path
Control: affects -1 eye
Quoting Adrian Bunk (2022-08-20 23:16:06)
> On Sat, Mar 05, 2022 at 08:41:47PM +0100, Paul Gevers wrote:
> > Source: eye
> > Version: 19.0221.2026~ds-1
> > Severity: serious
Source: promod3
Version: 3.2.1+ds-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=promod3&arch=amd64&ver=3.2.1%2Bds-4%2Bb1&stamp=1662229682&raw=0
...
CMake Error at cmake_support/FindOPENSTRUCTURE.cmake:37 (message):
Could not find library ost_io. Please specify
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mir-core: FTBFS: ERROR: Unable to detect linker for compiler `ldc2
-L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g -rele
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding stdx-allocator: FTBFS: ../meson.build:1:0: ERROR: Unable to detect
linker for compiler `ldc2 -L=--version /tmp/tmpa3ats9za.
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mir-core: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker
for compiler `ldc2 -L=--version /tmp/tmp22xmb4p4.d -Wl,
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mustache-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker
for compiler `ldc2 -L=--version /tmp/tmp0m23tkec.d -W
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding gir-to-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker
for compiler `ldc2 -L=--version /tmp/tmp7wgoqpvv.d -Wl,
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker
for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,
Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding meson: All ldc related packages FTBFS with 0.63.1-1
to be marked as done.
This means that you claim that the problem has be
Sorry for the late reply. I am told that StanHeaders can be built
successfully with oneTBB by setting environmental variables like
TBB_INC and TBB_LIB. On CRAN, we would like to use the version of TBB
that comes with the RcppParallel package
https://github.com/RcppCore/RcppParallel/pull/144
Altho
Your message dated Sat, 03 Sep 2022 18:49:15 +
with message-id
and subject line Bug#1012928: fixed in flatbuffers 2.0.6+dfsg1-2
has caused the Debian Bug report #1012928,
regarding flatbuffers: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt w
On Sat, 3 Sep 2022, Helge Kreutzmann wrote:
> The upload of manpages-l10n (manpages-fr) was just accepted in
> unstable.
OK, thanks.
AIUI we now need another upload of src:sysvinit in which bin:bootlogd
gets a Replaces and Breaks on manpages-fr (<< 4.15.0-9~), correct?
I can do that this weeken
Source: python-pgmagick
Version: 0.7.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-pgmagick&arch=amd64&ver=0.7.6-1%2Bb3&stamp=1662226834&raw=0
...
./src/_Image.cpp: In function ‘void __Image()’:
./src/_Image.cpp:385:82: error: no matches converting functi
On Sat, Sep 03, 2022 at 08:22:12PM +0300, Adrian Bunk wrote:
> Source: pytango
> Version: 9.3.4-2
> Severity: serious
> Tags: ftbfs
>
> See #972785 for background.
I forgot to include the error message:
https://buildd.debian.org/status/fetch.php?pkg=pytango&arch=amd64&ver=9.3.4-2%2Bb2&stamp=1662
Your message dated Sat, 03 Sep 2022 17:21:50 +
with message-id
and subject line Bug#1000482: fixed in neomutt 20220429+dfsg1-2
has caused the Debian Bug report #1000482,
regarding neomutt: license conflict with libsasl2
to be marked as done.
This means that you claim that the problem has been
Source: pytango
Version: 9.3.4-2
Severity: serious
Tags: ftbfs
See #972785 for background.
Hi,
On Sat, Sep 03, 2022 at 03:31:15PM +0200, Steinar H. Gunderson wrote:
> On Fri, Aug 26, 2022 at 09:07:06PM +0200, Salvatore Bonaccorso wrote:
> > The following vulnerability was published for libapreq2.
> >
> > CVE-2022-22728[0]:
> > | A flaw in Apache libapreq2 versions 2.16 and earlier coul
Processing control commands:
> severity -1 important
Bug #957392 [src:juman] juman: ftbfs with GCC-10
Severity set to 'important' from 'serious'
--
957392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
juman 7.0-3.5 build successfully on the buildds with GCC 12.
Therefore I am lowering the severity of this bug.
Processing commands for cont...@bugs.debian.org:
> block 898400 with 1019044
Bug #898400 [wnpp] ITP: sccache -- compiler cache for fast recompilation of
C/C++/Rust code
898400 was blocked by: 1014217 1014216 969609 1019090
898400 was not blocking any bugs.
Added blocking bug(s) of 898400: 1019044
Processing commands for cont...@bugs.debian.org:
> block 898400 with 1019090
Bug #898400 [wnpp] ITP: sccache -- compiler cache for fast recompilation of
C/C++/Rust code
898400 was blocked by: 1014217 1014216 969609
898400 was not blocking any bugs.
Added blocking bug(s) of 898400: 1019090
> thank
Processing commands for cont...@bugs.debian.org:
> block 1008016 with 1019090
Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for
the Safe Network
1008016 was blocked by: 1013106 1013109 1010099 1013139 1010083 1013115 1013136
1013137 984864 1016409 974118 1010212 101
Processing control commands:
> severity -1 grave
Bug #1019044 [librust-once-cell-dev] librust-once-cell-dev: impossible to
satisfy dependency on librust-parking-lot-core-0.8-dev
Severity set to 'grave' from 'normal'
--
1019044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019044
Debian Bu
Package: librust-petgraph-dev
Version: 0.5.1-2
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
nary package librust-petgraph-dev cannoy be installed, as it depends on
missing package librust-fixedbitset-0.2-dev.
-BEGIN PGP SIGNATURE--
Your message dated Sat, 03 Sep 2022 15:02:50 +
with message-id
and subject line Bug#1017240: fixed in silo-llnl 4.11-3
has caused the Debian Bug report #1017240,
regarding silo-llnl: FTBFS: ./conftest.c:27: undefined reference to `foobar'
to be marked as done.
This means that you claim that t
Hello, ping?
G.
On Wed, 20 Jul 2022 18:42:32 +0200 Gianfranco Costamagna
wrote:
Source: ocaml-odoc
Version: 2.1.0+dfsg-1
Severity: serious
Hello, as said, the autopkgtests are now failing due to new ocaml or new ocaml
libraries.
https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml
Processing commands for cont...@bugs.debian.org:
> tags 1017131 + fixed-upstream
Bug #1017131 [src:aspcud] aspcud: FTBFS: catch.hpp:10822:58: error: call to
non-‘constexpr’ function ‘long int sysconf(int)’
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you n
Your message dated Sat, 3 Sep 2022 16:27:33 +0200
with message-id
and subject line python-ldap 1008355 fixed in 3.4.0-1
has caused the Debian Bug report #1008355,
regarding python-ldap: _slaptest.py fails with "slapd exited before opening
port", breaking other package builds
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> merge 1017314 1017151
Bug #1017314 [src:handbrake] handbrake: FTBFS: ../libhb/decsrtsub.c:223:39:
error: ‘AV_NOPTS_VALUE’ undeclared (first use in this function)
Bug #1017314 [src:handbrake] handbrake: FTBFS: ../libhb/decsrtsub.c:223:39:
error:
On Fri, Aug 26, 2022 at 09:07:06PM +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for libapreq2.
>
> CVE-2022-22728[0]:
> | A flaw in Apache libapreq2 versions 2.16 and earlier could cause a
> | buffer overflow while processing multipart form uploads. A remote
> | a
Your message dated Sat, 3 Sep 2022 14:05:45 +0100
with message-id
and subject line Closing
has caused the Debian Bug report #1017257,
regarding cfgrib: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_test]
Error 13
to be marked as done.
This means that you claim that the problem has been
Hello Thorsten,
On Thu, Sep 01, 2022 at 06:39:18PM +0200, Thorsten Glaser wrote:
> > For Debian, as stated above, I can do another upload removing this
> > file as well.
>
> Thanks. Feel free to reassign/close this bug at will then… or do we
> need another sysvinit upload with updated Replaces/Bre
Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id
and subject line Bug#995387: fixed in dpkg 1.20.12
has caused the Debian Bug report #995387,
regarding dpkg: remove-on-upgrade deletes symlink targets owned by another
package
to be marked as done.
This means that you claim that
Your message dated Sat, 03 Sep 2022 12:49:15 +
with message-id
and subject line Bug#1016620: fixed in nvidia-graphics-drivers-tesla-470
470.141.03-1~deb11u1
has caused the Debian Bug report #1016620,
regarding nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608,
CVE-2022-31615
Your message dated Sat, 03 Sep 2022 12:49:14 +
with message-id
and subject line Bug#1016618: fixed in nvidia-graphics-drivers-tesla-450
450.203.03-1~deb11u1
has caused the Debian Bug report #1016618,
regarding nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608,
CVE-2022-31615
Your message dated Sat, 03 Sep 2022 12:49:13 +
with message-id
and subject line Bug#1016616: fixed in nvidia-graphics-drivers-legacy-390xx
390.154-1~deb11u1
has caused the Debian Bug report #1016616,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608,
CVE-2022-316
Your message dated Sat, 03 Sep 2022 12:49:15 +
with message-id
and subject line Bug#1016614: fixed in nvidia-graphics-drivers-tesla-470
470.141.03-1~deb11u1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608,
CVE-2022-31615
to be mark
Your message dated Sat, 03 Sep 2022 12:49:12 +
with message-id
and subject line Bug#1016614: fixed in nvidia-graphics-drivers
470.141.03-1~deb11u1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608,
CVE-2022-31615
to be marked as done
Your message dated Sat, 03 Sep 2022 12:49:11 +
with message-id
and subject line Bug#1016420: fixed in libreoffice 1:7.0.4-4+deb11u3
has caused the Debian Bug report #1016420,
regarding libreoffice-evolution: Evolution address source indefinitely freezes
UI
to be marked as done.
This means th
Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id
and subject line Bug#1008478: fixed in dpkg 1.20.12
has caused the Debian Bug report #1008478,
regarding dpkg-fsys-usrunmess depends on umask 022
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id
and subject line Bug#1008316: fixed in dpkg 1.20.12
has caused the Debian Bug report #1008316,
regarding dpkg-fsys-usrunmess: Does not deal with untracked kernel modules
to be marked as done.
This means that you claim that the pro
Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id
and subject line Bug#1000421: fixed in dpkg 1.20.12
has caused the Debian Bug report #1000421,
regarding dpkg-shlibdeps: Wrong minimum version requirement on libc6
to be marked as done.
This means that you claim that the problem h
Guillem Jover wrote...
> On Fri, 2022-09-02 at 12:12:06 +0200, Christoph Biedl wrote:
> > Sylvestre Ledru wrote...
> > > I don't think renaming is the right approach against an MS-DOS
> > > software (and I still think that Debian's policy is too binary for
> > > this).
> >
> > As there is a very s
Processing commands for cont...@bugs.debian.org:
> tags 919697 pending
Bug #919697 [arcanist] arcanist: file conflict with arc
Bug #930722 [arcanist] arc, arcanist: Both ship arc binary
Added tag(s) pending.
Added tag(s) pending.
> tags 1003463 pending
Bug #1003463 [arcanist] Functionally broken w
Package: orage
Version: 4.16.0-1
Followup-For: Bug #1018717
Get to reproduce same bug from unstable (instance upgrade from bullseye).
Here a gdb output:
(gdb) bt
#0 0x in ?? ()
#1 0x7711f5f6 in g_hash_table_lookup () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x000
Package: ffmpeg
Version: 7:5.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Repackaging FFMPEG on a Pipewire enabled host, while fulfilling
all dependencies fails on the shlibdeps step with the following message:
Package: libsuperlu-dist-dev
Version: 8.1.0+dfsg1-2
Severity: serious
https://piuparts.debian.org/sid/fail/libsuperlu-dist-dev_8.1.0+dfsg1-2.log
...
Removing libsuperlu-dist-dev:amd64 (8.1.0+dfsg1-2) ...
rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such
file or di
Hi all,
On Thu, 01 Sep 2022 09:31:33 +0200 Paul Gevers wrote:
If you can't (or don't want to) do this soon, I'll upload luajit2 with
only ppc64el dropped from the Architectures field (well, convert `any`
to the list where it builds). Please let me know if you want me to do
that.
I have upload
Your message dated Sat, 03 Sep 2022 11:05:00 +
with message-id
and subject line Bug#1014100: fixed in qiime 2022.8.1-1
has caused the Debian Bug report #1014100,
regarding qiime: autopkgtest needs update for new version of python-decorator
to be marked as done.
This means that you claim that
Your message dated Sat, 03 Sep 2022 09:12:03 +
with message-id
and subject line Bug#1018017: fixed in ukui-greeter 3.0.3.1-1
has caused the Debian Bug report #1018017,
regarding ukui-greeter: FTBFS in unstable
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id
and subject line closing again with source package version
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
to be marked as done.
This means that you claim t
Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id
and subject line closing again with source package version
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
to be marked as done.
This means that you claim t
Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id
and subject line closing again with source package version
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
to be marked as done.
This means that you claim t
Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id
and subject line closing again with source package version
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
to be marked as done.
This means that you claim t
Your message dated Sat, 03 Sep 2022 07:19:29 +
with message-id
and subject line Bug#1013461: fixed in kylin-video 3.1.3-3
has caused the Debian Bug report #1013461,
regarding kylin-video FTBFS with ffmpeg 5.0.1
to be marked as done.
This means that you claim that the problem has been dealt wi
94 matches
Mail list logo
