Processing commands for cont...@bugs.debian.org:
> fixed 1032620 doctest/2.4.11-1
Bug #1032620 [src:doctest] doctest: new 2.4.10 out, fixes pernicious bugs
Marked as fixed in versions doctest/2.4.11-1.
> close 1032620
Bug #1032620 [src:doctest] doctest: new 2.4.10 out, fixes pernicious bugs
Marked
gimp-gap 2.6.0+dfsg-7 is marked for autoremoval from testing on 2023-08-31
It (build-)depends on packages with these RC bugs:
1041382: gegl: FTBFS with ffmpeg 6.0
https://bugs.debian.org/1041382
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer
gluas 0.1.20-2 is marked for autoremoval from testing on 2023-08-31
It (build-)depends on packages with these RC bugs:
1041382: gegl: FTBFS with ffmpeg 6.0
https://bugs.debian.org/1041382
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_a
gimp-dds 3.0.1-3 is marked for autoremoval from testing on 2023-08-31
It (build-)depends on packages with these RC bugs:
1041382: gegl: FTBFS with ffmpeg 6.0
https://bugs.debian.org/1041382
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail
gtkam 1.0-3 is marked for autoremoval from testing on 2023-08-31
It (build-)depends on packages with these RC bugs:
1041382: gegl: FTBFS with ffmpeg 6.0
https://bugs.debian.org/1041382
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_auto
Package: gimp (maybe gimp-dds as well, imo)
Version: 2.10.34-1
Severity: normal
X-Debbugs-Cc: aidsistgra...@gmail.com
Dear Maintainer, I have made some mediocre experiences actually often with GIMP
and certain functions of it...
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_
Package: sysv-rc-conf
Version: 0.99-7.1
Severity: normal
Dear Maintainer,
* What led up to the situation?
After an upgrade from bullseye to bookworm, sysv-rc-conf was tagged
as upgrading possible.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Using synap
Version: 0.0~git20230110.6956c0e-1+rm
Dear submitter,
as the package grpc-proto has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.deb
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
grpc-proto | 0.0~git20230110.6956c0e-1 | source, all
--- Reason ---
RoQA; Orphaned; Useless
--
Note that the pa
Version: 0.10.2+rm
Dear submitter,
as the package mercurial-buildpackage has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.or
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
mercurial-buildpackage | 0.10.2 | source, amd64, arm64, armel, armhf, i386,
mips64el, mipsel, ppc64el, s390x
--- Reason ---
RoQA; no users left
---
Your message dated Fri, 28 Jul 2023 16:36:32 +
with message-id
and subject line Bug#1026433: Removed package(s) from unstable
has caused the Debian Bug report #743730,
regarding mercurial-buildpackage: s/exiting/existing/ in NAME section of
mercurial-importdsc(1)
to be marked as done.
This m
Your message dated Fri, 28 Jul 2023 16:36:32 +
with message-id
and subject line Bug#1026433: Removed package(s) from unstable
has caused the Debian Bug report #688281,
regarding mercurial-buildpackage: mercurial-importorig leaves files that have
been removed in new upstream version
to be mark
Your message dated Fri, 28 Jul 2023 16:36:32 +
with message-id
and subject line Bug#1026433: Removed package(s) from unstable
has caused the Debian Bug report #588076,
regarding mercurial-buildpackage: unnecessarily Recommends pbuilder
to be marked as done.
This means that you claim that the
14 matches
Mail list logo
