control: tags -1 + moreinfo
control: severity -1 important
thanks
Hi Andreas,
as usual: thanks for this bug report and all the other piuparts bug reports you
are filing! \o/
On Wed, May 10, 2023 at 02:03:17PM +0200, Andreas Beckmann wrote:
> Package: tuxmath-data
> Severity: serious
> during
control: tags -1 + moreinfo
control: severity -1 important
thanks
Hi Andreas,
as usual: thanks for this bug report and all the other piuparts bug reports you
are filing! \o/
On Wed, May 10, 2023 at 02:03:17PM +0200, Andreas Beckmann wrote:
> Package: tuxmath-data
> Severity: serious
> during
On Thu, May 11, 2023 at 07:11:17AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> I don't think it would be lying. It would be saying: "I'm trying to verify
> something that was built on a buildd by reproducing its environment."
exactly.
[...]
> make[1]: Leaving directory
hi kpcyrd,
On Mon, May 08, 2023 at 02:08:09AM +0200, kpcyrd wrote:
> I was using github actions to compile my project but had trouble matching
> the binary, even when[...]
thanks for sharing your findings here!
[...]
> This can be run without root privileges if user namespaces are enabled. The
The (translated) debian-edu-bullseye manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
The (translated) debian-edu-bookworm manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
control: tags -1 + wontfix
thanks
On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> That bug is currently blocking from using munin on not systemd systems.
I'm not planning on supporting legacy initscripts myself. And despite tagging
this bug 'wontfix' for the time being I will
On Thu, May 04, 2023 at 07:50:37PM +0200, Holger Levsen wrote:
> [ Checklist ]
> [x] *all* changes are documented in the d/changelog
> [x] I reviewed all changes and I approve them
> [x] attach debdiff against the package in (old)stable
> [x] the issue is verified as fixed
On Thu, May 04, 2023 at 07:50:37PM +0200, Holger Levsen wrote:
> [ Checklist ]
> [x] *all* changes are documented in the d/changelog
> [x] I reviewed all changes and I approve them
> [x] attach debdiff against the package in (old)stable
> [x] the issue is verified as fixed
debian/changelog 2023-05-04 19:09:45.0 +0200
@@ -1,3 +1,17 @@
+debian-security-support (1:12+2023.05.04) unstable; urgency=medium
+
+ [ Holger Levsen ]
+ * set DEB_NEXT_VER_ID=13 in anticipation of the bookworm release.
+Closes: #1034077. Thanks to Stuart Prescott.
+ * secu
debian/changelog 2023-05-04 19:09:45.0 +0200
@@ -1,3 +1,17 @@
+debian-security-support (1:12+2023.05.04) unstable; urgency=medium
+
+ [ Holger Levsen ]
+ * set DEB_NEXT_VER_ID=13 in anticipation of the bookworm release.
+Closes: #1034077. Thanks to Stuart Prescott.
+ * secu
,14 @@
+debian-security-support (1:11+2023.05.04) bullseye; urgency=medium
+
+ [ Holger Levsen ]
+ * set DEB_NEXT_VER_ID=12 as bookworm is the next release. Closes: #1034077.
+Thanks to Stuart Prescott.
+
+ [ Sylvain Beucler ]
+ * security-support-limited: add gnupg1, see #982258.
+
+ -- Holg
,14 @@
+debian-security-support (1:11+2023.05.04) bullseye; urgency=medium
+
+ [ Holger Levsen ]
+ * set DEB_NEXT_VER_ID=12 as bookworm is the next release. Closes: #1034077.
+Thanks to Stuart Prescott.
+
+ [ Sylvain Beucler ]
+ * security-support-limited: add gnupg1, see #982258.
+
+ -- Holg
Hi,
On Fri, Apr 14, 2023 at 11:16:16AM +, Holger Levsen wrote:
> > Incrementing to DEB_NEXT_VER_ID=12 in the next bullseye point release seems
> > reasonable to me; also incrementing in bookworm to DEB_NEXT_VER_ID=13 would
> > be logical.
> I'll ponder about this is a
On Wed, Apr 26, 2023 at 12:40:09PM -0700, Vagrant Cascadian wrote:
> Yes, ideally SOURCE_DATE_EPOCH does not matter. It is a workaround to
> embed a (hopefully meaningful) timestamp, when from a reproducible
> builds perspective, ideally there would be no timestamp at all in the
> resulting
On Thu, Apr 27, 2023 at 10:58:46AM +0200, Marc Haber wrote:
> My gut feeling is that we are wasting prescious time of numerous
> skilled Debian Developers to find ugly workarounds to something that
> should be done in dpkg, but isnt being done because one dpkg
> maintainer has decided to not go
hi,
this is a reminder for our next IRC meeting on #reproducible-builds
on the last Tuesday of the month, which is tomorrow in most timezones,
in a bit more than 24h. As usual we meet at 15 UTC on irc.oftc.net.
The meeting is supposed to last between 1-2h, maybe rather an hour, as
of course we
package: distro-info
severity: wishlist
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
affects: extrepo-data, developers-reference
hi!
On Fri, Apr 14, 2023 at 12:24:52PM -0700, Vagrant Cascadian wrote:
> On 2023-04-14, Holger Levsen wrote:
> > i'm wondering whether distro-in
package: distro-info
severity: wishlist
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org
affects: extrepo-data, developers-reference
hi!
On Fri, Apr 14, 2023 at 12:24:52PM -0700, Vagrant Cascadian wrote:
> On 2023-04-14, Holger Levsen wrote:
> > i'm wondering whether distro-in
Dear James,
many thanks also from me for your work on this and sharing your findings here.
I'm another happy sphinx user affected by those problems. :)
somewhat related:
i'm wondering whether distro-info should respect SOURCE_DATE_EPOCH:
src:developers-reference builds different content
On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote:
> since some years, tracker.d.o is thankfully showing results from
> https://tests.reproducible-builds.org/debian - which was and is awesome!
> However, these are just continious integration test results and
> not based on
On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote:
> since some years, tracker.d.o is thankfully showing results from
> https://tests.reproducible-builds.org/debian - which was and is awesome!
> However, these are just continious integration test results and
> not based on
On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote:
> since some years, tracker.d.o is thankfully showing results from
> https://tests.reproducible-builds.org/debian - which was and is awesome!
> However, these are just continious integration test results and
> not based on
On Thu, Apr 13, 2023 at 02:43:43PM -0700, Vagrant Cascadian wrote:
> > Any progress on that front? What can be done to change things so that the
> > packages people normally *use* are reproducible?
the Debian packages people normally use *are* already reproducible (well, 80-90%
of them, at
. Closes: #1033451.
+
+ -- Holger Levsen Mon, 27 Mar 2023 20:40:47 +0200
+
debian-edu-config (2.12.31) unstable; urgency=medium
* sbin/debian-edu-pxeinstall: adjust for memtest86+ 6.10-4, thanks to
diff -Nru debian-edu-config-2.12.31/sbin/debian-edu-ltsp-install
debian-edu-config-2.12.32/sbin
. Closes: #1033451.
+
+ -- Holger Levsen Mon, 27 Mar 2023 20:40:47 +0200
+
debian-edu-config (2.12.31) unstable; urgency=medium
* sbin/debian-edu-pxeinstall: adjust for memtest86+ 6.10-4, thanks to
diff -Nru debian-edu-config-2.12.31/sbin/debian-edu-ltsp-install
debian-edu-config-2.12.32/sbin
Hi,
I forgot to mention one thing: this will be better in future, because
since 3 weeks debian/README.source contains this:
# ToDo list for a new Debian release
At the beginning of each new Debian release cycle, these steps need to be done:
- create a new git branch for the old release
-
Hi Stuart,
On Sun, Apr 09, 2023 at 12:45:13AM +1000, Stuart Prescott wrote:
> Following up the conversation in #d-release...
thank you for that!
> Looking at some released versions of /usr/bin/check-support-status:
> - buster (10.13, 1:10+2022.08.23) has DEB_NEXT_VER_ID=11
> - bullseye (11.6,
Package: reprotest
Version: 0.7.23
Severity: wishlist
Dear Maintainer,
i guess reprotest maybe should grow an option to do
--control-build /path/to/packages/
--vary=build_path=/use/this/build/path ...
to make it easier to use reprotest to compare against an
Package: reprotest
Version: 0.7.23
Severity: wishlist
Dear Maintainer,
i guess reprotest maybe should grow an option to do
--control-build /path/to/packages/
--vary=build_path=/use/this/build/path ...
to make it easier to use reprotest to compare against an
hi,
someone on irc wondered about icons and Debian packages so I noticed
https://www.debian.org/doc/packaging-manuals/menu-policy/
prominently linked from https://www.debian.org/doc/devel-manuals#policy
But then I though the menu system has been deprecated as eg noted in
#975631:
On Tue, Nov
package: jenkins.debian.org
severity: important
hi,
when deploying on osuosl3, running bookworm:
Traceback (most recent call last):
File "/srv/jenkins/bin/deploy_kgb.py", line 19, in
passwords = yaml.load(fd)
^
TypeError: load() missing 1 required positional
The (translated) debian-edu-bullseye manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
The (translated) debian-edu-bookworm manual in PDF, ePUB or HTML formats are
available at https://jenkins.debian.net/userContent/debian-edu-doc//
To understand this mail better, please read
/usr/share/doc/debian-edu-doc/README.
This mail is automatically send by a cronjob run by Holger Levsen
control: tags -1 + +upstream
thanks
On Fri, Mar 31, 2023 at 07:43:56AM +0200, Helmut Grohne wrote:
> I noticed that the example configuration included in the nginx_* plugins
> does not work. Nowadays, localhost tends to resolve to ::1 and with the
> example configuration, this yields an error.
On Mon, Mar 27, 2023 at 12:09:07PM +, Debian Bug Tracking System wrote:
> Bug #1032440 in www.debian.org reported by you has been fixed in the Git
> repository.
> You can see the commit message below and you can check the diff of the fix at:
>
>
On Mon, Mar 27, 2023 at 12:09:07PM +, Debian Bug Tracking System wrote:
> Bug #1032440 in www.debian.org reported by you has been fixed in the Git
> repository.
> You can see the commit message below and you can check the diff of the fix at:
>
>
hi,
this is a reminder for our next IRC meeting on #reproducible-builds
on the last Tuesday of the month, which is tomorrow in most timezones,
in a bit more than 24h. As usual we meet at 15 UTC on irc.oftc.net,
which for many this time is a different localtime than last month!
The meeting is
hangelog 2023-03-23
22:38:23.0 +0100
@@ -1,3 +1,16 @@
+debian-security-support (1:12+2023.03.23) unstable; urgency=medium
+
+ * d/README.source: list steps to be done at the beginning of each release
+cycle to avoid bugs like #1033312.
+
+ -- Holger Levsen Thu, 23 Mar 2023
hangelog 2023-03-23
22:38:23.0 +0100
@@ -1,3 +1,16 @@
+debian-security-support (1:12+2023.03.23) unstable; urgency=medium
+
+ * d/README.source: list steps to be done at the beginning of each release
+cycle to avoid bugs like #1033312.
+
+ -- Holger Levsen Thu, 23 Mar 2023
Holger Levsen pushed to branch master at Debian Security Tracker /
security-tracker
Commits:
764399b1 by Holger Levsen at 2023-03-22T01:08:35+01:00
LTS: claim curl
Signed-off-by: Holger Levsen hol...@layer-acht.org
- - - - -
1 changed file:
- data/dla-needed.txt
Changes
Moin.
As in the last years there will be a Debian Reunion Hamburg 2023 event taking
place in the former Victoria Kaserne (barracks), now called Fux, which is a
collective space located in a historical monument in Hamburg Altona.
The event dates are from Tuesday, May 23rd until Tuesday, the 30th
On Mon, Mar 20, 2023 at 02:03:41PM +0100, Joost van Baal-Ilić wrote:
> That would be thursday august 16, 2023. Seems our friends in La Paz, Bolivia
> are already planning: https://wiki.debian.org/DebianDay/2023 .
this will be during CCCamp taking place from Aug 15-19 in Ziegeleipark
Mildenberg
On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote:
> So, after some delay from me and some further delays from various
> Debian machines committing suicide [1], I've got bookworm live builds
> running again. \o/
this is great news! thanks and kudos to everyone involved!
--
cheers,
On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote:
> So, after some delay from me and some further delays from various
> Debian machines committing suicide [1], I've got bookworm live builds
> running again. \o/
this is great news! thanks and kudos to everyone involved!
--
cheers,
On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote:
> So, after some delay from me and some further delays from various
> Debian machines committing suicide [1], I've got bookworm live builds
> running again. \o/
this is great news! thanks and kudos to everyone involved!
--
cheers,
On Sun, Mar 19, 2023 at 03:13:47PM +, Steve McIntyre wrote:
> So, after some delay from me and some further delays from various
> Debian machines committing suicide [1], I've got bookworm live builds
> running again. \o/
this is great news! thanks and kudos to everyone involved!
--
cheers,
On Thu, Mar 16, 2023 at 06:00:06PM +, Holger Levsen wrote:
> aaah, thanks! I only checked /usr/share/doc/logcheck/NEWS.Debian.gz
> but not /usr/share/doc/logcheck-database/NEWS.Debian.gz
now that I read it and followed the advice and the very nice
sed example there,
urity-support (1:12+2023.03.17) unstable; urgency=medium
[ Moritz Muehlenhoff ]
* security-support-limited: add note about libspring-java.
[ Holger Levsen ]
* security-support-limited: Add openjdk-21 and drop openjdk-17 as the latter
is the default (and supported) JDK in book
urity-support (1:12+2023.03.17) unstable; urgency=medium
[ Moritz Muehlenhoff ]
* security-support-limited: add note about libspring-java.
[ Holger Levsen ]
* security-support-limited: Add openjdk-21 and drop openjdk-17 as the latter
is the default (and supported) JDK in book
On Thu, Mar 16, 2023 at 01:31:37PM +, Richard Lewis wrote:
> I dont understand - logcheck rules cater for both formats since 1.4.1 iirc
> and this is already explained in NEWS.Debian. (and i thought that included
> instructions for updating local rules in that)
it's not. just checked the NEWS
On Thu, Mar 16, 2023 at 05:52:44PM +, Richard Lewis wrote:
> Is it not the first entry, from version 1.4.0 from dec 2022 in
> /usr/share/doc/logcheck-database/README.logcheck-database.gz ??
aaah, thanks! I only checked /usr/share/doc/logcheck/NEWS.Debian.gz
but not
| h01ger: thanks for the bug report, but something got mixed up there:
rsyslog uses rfc3339, not short-iso-precise
short-iso-precise is an output format of journalctl that is similar to
rfc3339 but differs in the presentation of the timezone information
*g*, thanks
mbiebl: this is also why
a properly placed [:]? might be all that's need
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
All data, over time, approaches deleted, or public. (@quinnnorton)
signature.asc
On Thu, Mar 16, 2023 at 07:53:22AM -0400, Roberto C. Sánchez wrote:
> Can we have a clear statement of what "directly affects people"?
for those having lost people due to covid, hearing someone say
it's a hoax, is definitly painful. and this affects Debian directly:
so far we know about one
Package: logcheck
Version: 1.4.2
Severity: wishlist
Dear Maintainer,
since bookworm rsyslog defaults to timestamps in short-iso-precise format,
while logcheck rules (and journald) still default to the old rule format,
and while the default logcheck rules in the package are easily switched,
this
On Mon, Mar 13, 2023 at 03:58:45PM +0100, Moritz Mühlenhoff wrote:
> Am Mon, Mar 13, 2023 at 01:43:11PM +0100 schrieb Holger Levsen:
> > * security-support-limited:
> > - for golang and openjdk-17, point to the bookworm manual instead the
> > one
> > f
On Mon, Mar 13, 2023 at 03:58:45PM +0100, Moritz Mühlenhoff wrote:
> Am Mon, Mar 13, 2023 at 01:43:11PM +0100 schrieb Holger Levsen:
> > * security-support-limited:
> > - for golang and openjdk-17, point to the bookworm manual instead the
> > one
> > f
On Sat, Mar 11, 2023 at 10:19:44PM +, Remus-Gabriel Chelu wrote:
> Please find attached the Romanian translation of the «munin» file.
thank you, this will be included in the next upload.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
-support-limited:
- for golang and openjdk-17, point to the bookworm manual instead the one
for bullseye.
- add mozjs102 based on package description (and #959804).
- drop mozjs52 and mozjs60 as they were only present in buster.
-- Holger Levsen Sun, 05 Mar 2023 20:39:38 +0100
-support-limited:
- for golang and openjdk-17, point to the bookworm manual instead the one
for bullseye.
- add mozjs102 based on package description (and #959804).
- drop mozjs52 and mozjs60 as they were only present in buster.
-- Holger Levsen Sun, 05 Mar 2023 20:39:38 +0100
On Sat, Mar 11, 2023 at 11:05:16PM +0100, Dashamir Hoxha wrote:
> What do you think about this?
I think the project name is "Debian Edu/Skolelinux" and we had this discussions
several times for a long time (a long time ago, as in: >10y) and I'm not
interested in having it again, because this
On Sun, Mar 12, 2023 at 06:11:51PM +, Pete Batard wrote:
> I will venture that this is because, and this is not criticism per se, most
> distributions currently make that process quite difficult or fraught with so
> many hurdles that people who would want to use FST will not yet bother
>
On Sun, Mar 12, 2023 at 06:11:51PM +, Pete Batard wrote:
> I will venture that this is because, and this is not criticism per se, most
> distributions currently make that process quite difficult or fraught with so
> many hurdles that people who would want to use FST will not yet bother
>
On Sun, Mar 12, 2023 at 03:36:33PM +0100, Sven Joachim wrote:
> After taking a closer look, this seems to be all red herring. Sbuild
> uses apt for resolving the build dependencies, and while apt prefers
> virtual packages over real ones, it has no problem to use the virtual
> one (libncurses-dev
Package: ubuntu-core-launcher
Version: 2.57.6-1+b3
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package ubuntu-core-launcher (from the source
package snapd) after the release of bookworm, it has been released with buster
and
Package: verbiste-el
Version: 0.1.47-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package verbiste-el (from the source package
verbiste) after the release of bookworm, it has been released with buster and
bullseye already...
Package: x11proto-core-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-core-dev (from the source package
xorgproto) after the release of bookworm, it has been released with buster and
bullseye
Package: libuim-data
Version: 1:1.8.8-9.2
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libuim-data (from the source package uim)
after the release of bookworm, it has been released with buster and bullseye
already...
Package: x11proto-core-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-core-dev (from the source package
xorgproto) after the release of bookworm, it has been released with buster and
bullseye
Package: skytools3-ticker
Version: 3.5-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package skytools3-ticker (from the source package
pgqd) after the release of bookworm, it has been released with buster and
bullseye already...
Package: idle3
Version: 3.11.2-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package idle3 (from the source package
python3-defaults) after the release of bookworm, it has been released with
buster and bullseye already...
Package: python3-dicom
Version: 2.3.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package python3-dicom (from the source package
pydicom) after the release of bookworm, it has been released with buster and
bullseye already...
Package: x11proto-record-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-record-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and
Package: x11proto-present-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-present-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and
Package: x11proto-randr-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-randr-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: x11proto-record-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-record-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and
Package: x11proto-present-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-present-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and
Package: x11proto-randr-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-randr-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: x11proto-fonts-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-fonts-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: xul-ext-treestyletab
Version: 3.5.20-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package xul-ext-treestyletab (from the source
package tree-style-tab) after the release of bookworm, it has been released
with buster and
Package: xul-ext-treestyletab
Version: 3.5.20-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package xul-ext-treestyletab (from the source
package tree-style-tab) after the release of bookworm, it has been released
with buster and
Package: pyotherside
Version: 1.6.0-2
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package pyotherside (from the source package
pyotherside) after the release of bookworm, it has been released with buster
and bullseye already...
Package: libwagon-java
Version: 3.5.3-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libwagon-java (from the source package
wagon) after the release of bookworm, it has been released with buster and
bullseye already...
Package: libwagon-java
Version: 3.5.3-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libwagon-java (from the source package
wagon) after the release of bookworm, it has been released with buster and
bullseye already...
Package: x11proto-fonts-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-fonts-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: libtiff5-dev
Version: 4.5.0-5
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libtiff5-dev (from the source package
tiff) after the release of bookworm, it has been released with buster and
bullseye already...
Package: x11proto-video-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-video-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: x11proto-xext-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-xext-dev (from the source package
xorgproto) after the release of bookworm, it has been released with buster and
bullseye
Package: x11proto-xf86vidmode-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-xf86vidmode-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster
Package: x11proto-xext-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-xext-dev (from the source package
xorgproto) after the release of bookworm, it has been released with buster and
bullseye
Package: x11proto-video-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-video-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster and bullseye
Package: x11proto-xf86vidmode-dev
Version: 2022.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package x11proto-xf86vidmode-dev (from the source
package xorgproto) after the release of bookworm, it has been released with
buster
Package: hunspell-gl-es
Version: 1:7.5.0-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package hunspell-gl-es (from the source package
libreoffice-dictionaries) after the release of bookworm, it has been released
with buster and
Package: hunspell-gl-es
Version: 1:7.5.0-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package hunspell-gl-es (from the source package
libreoffice-dictionaries) after the release of bookworm, it has been released
with buster and
Package: myspell-ru
Version: 0.99g5-29
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package myspell-ru (from the source package
rus-ispell) after the release of bookworm, it has been released with buster and
bullseye already...
Package: libplexus-container-default1.5-java
Version: 2.1.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libplexus-container-default1.5-java (from
the source package plexus-containers) after the release of bookworm, it has
Package: libplexus-classworlds2-java
Version: 2.7.0-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libplexus-classworlds2-java (from the
source package plexus-classworlds) after the release of bookworm, it has been
released
Package: libplexus-container-default1.5-java
Version: 2.1.1-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libplexus-container-default1.5-java (from
the source package plexus-containers) after the release of bookworm, it has
Package: libplexus-classworlds2-java
Version: 2.7.0-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional
Please drop the transitional package libplexus-classworlds2-java (from the
source package plexus-classworlds) after the release of bookworm, it has been
released
601 - 700 of 22803 matches
Mail list logo
