[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041523: marked as done (tracker.debian.org: displays autopkgtest for other src:package on same page)



Your message dated Thu, 20 Jul 2023 12:42:43 +0200
with message-id <6416f911-ffc2-05bb-7d82-56f0863b97f8@debian.org>
and subject line Re: Bug#1041523: tracker.debian.org: displays autopkgtest for other src:package on same page
has caused the Debian Bug report #1041523,
regarding tracker.debian.org: displays autopkgtest for other src:package on same page
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.)


-- 
1041523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041523
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The tracker at <https://tracker.debian.org/pkg/dhcpcd> shows autopkgtest results for both this src:package and for another src:package.

While the two packages are related, they are NOT the same package.

src:dhcpcd is the only src:package that should be tracked by this page. src:dhcpcd5 should be tracked by its own existing page.

Martin-Éric

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmS5CngACgkQrh+Cd8S0
17agfhAAhLTK9gTHfX3K9LXWp23n6Z7i0QWgstakul89zGxIzd1wucR22rpn4n6g
bIcMkoBDrCZ9OUaM8icZQiL5zvFzt7ug45weOoMN225mOtbe5iwQ5pWeoF1WeVZP
ieNaYIhE28ITWNaE5nBuFBuY8QRUHC+YXJfgljysJcYh7IvCeuoF+2wn/SWRRURI
xinWvFNzFdN9+bnWKqriVZnrQw9BY5rt+oyES8foUTlj9bLbxkhqc7nIwWC7hFCe
Rh/Mxt4/HagvDcpIRiuAPqnSc0cBAg63cOpo0cN+1q+cp29fkmPVCbV9Ip4RcrVW
HMjSyWnJpkhD3lLVVLdlkNT7+3ArIN18/H4Q85ao5C8cwUaZmE+H2tK3jKX9r5sc
8WHKDPaiuZbt5bvnKp0uVnyXbXdgU/N7hH+rZbmbIReX0sPsSnOtCyzHD3ALFQ2M
Rm3Rbl7KVbgRzGQgT6LtpYnpfQlFUG7dd4dqbuFKi5TUz5v9618LhGwJv7QXFqEF
ouVIKfgme7vER/nU4cVg4OtVdOTCN+eFrLjr4FGcYQAmVbdS+Eryz79NqGFHoEWu
O9S92iDwUyUy7VGdElAAzKX5n74GbWzWv3ZCgHtOxWAF6zpc4qRycPdaoDBQbpAw
IC2S5HqHri/hCsdORyGODCfEkhqaIW3iqpFOekdJp/GeOSCgWCI=
=ApSG
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On 20/07/2023 12.20, Martin-Éric Racine wrote:
The tracker at <https://tracker.debian.org/pkg/dhcpcd> shows autopkgtest results for both this src:package and for another src:package.

That is correct. The avalability of new binary packages from src:dhcpcd triggers autopkgtests (that depend on these binary packages) in all source packages (see e.g. src:glibc for a package triggering autopkgtests in many other source packages). And the tracker shows information about all triggered autopkgtests related to the src:dhcpcd upload.

dhcpd/dhcpd5 is a bit special here since that was a source package rename ...

You should file an RM bug against ftp.debian.org to get rid of the obsolete dhcpcd5 source package in sid (automatic cruft removal does not seem to catch that).


Andreas

--- End Message ---

Reply to: