Processing changes file: glib2.0_2.74.6-2+deb12u3_armhf-buildd.changes
ACCEPT
Processing commands for cont...@bugs.debian.org:
> block 1071926 with 1050237
Bug #1071926 [gnome-shell-extension-appindicator]
gnome-shell-extension-appindicator fails to install - dependency issue
1071926 was not blocked by any bugs.
1071926 was not blocking any bugs.
Added blocking bug(s) of 1
Processing control commands:
> affects -1 + src:polymake
Bug #1071948 [release.debian.org] nmu: polymake_4.11-2
Added indication that 1071948 affects src:polymake
--
1071948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: polym...@packages.debian.org
Control: affects -1 + src:polymake
User: release.debian@packages.debian.org
Usertags: binnmu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
nmu polymake_4.11-2 . ANY . unstable . -m "rebuild against libsi
Processing changes file: systemd_252.25-1~deb12u1_armel-buildd.changes
ACCEPT
Processing changes file: systemd_252.25-1~deb12u1_ppc64el-buildd.changes
ACCEPT
Your message dated Sun, 26 May 2024 17:48:20 +0900
with message-id <20240526174820.2f3b86e9@jet>
and subject line Re: Your mail
has caused the Debian Bug report #1066031,
regarding nmu: zeromq3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Hi,
while I contacted the release team previously[0] there was no response
so far. I tried to establish this first contact since I consider the
release team of really high relevance. Meanwhile I have added some
more information to my contact mails including advertising a DebConf
event (see below
8 matches
Mail list logo
