Bug#962000: marked as done (Duplicated news for php-horde-image)
Your message dated Tue, 02 Jun 2020 19:35:25 +0000
with message-id <5ed6a9fd9c48d_148b2b010f15e5c414185@godard.mail>
and subject line Bug#962000 fixed in tracker.debian.org
has caused the Debian Bug report #962000,
regarding Duplicated news for php-horde-image
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
962000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962000
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: wishlist
Dear maintainers,
I have noticed that tracker.debian.org reports duplicated news for
php-horde-image package [1] and others packages in php-horde ecosystem
(php-horde-data, php-horde-cache, php-horde-crypt, et al.).
I'm wondering if this behavior can be changed in the future so that oldest
(but useful) news don't shift too far, and identical news >= 2 are discarded.
I admit that I've not checked everything since number of news per package is
huge. My apologizes for this.
Thanks for considering.
Kind Regards.
[1] https://tracker.debian.org/pkg/php-horde-image
--- End Message ---
--- Begin Message ---
Hello,
Bug #962000 in tracker.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:
https://salsa.debian.org/qa/distro-tracker/-/commit/0fd3ac4589b3cfde96206698bf69ff6060299e89
------------------------------------------------------------------------
debian: better handle 'dak rm' mails
The code processing 'dak rm' mails was working on the assumption that we
get a single mail for all the packages listed in the mail. That
assumption is no longer true as we get a copy for each source package.
We should thus generate a news only for the specific package that was
targetted by the current email otherwise we store multiple news on each
source package listed in the mail.
Closes: #962000
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/962000
--- End Message ---
Reply to: