Your message dated Tue, 8 Jan 2019 13:42:08 +0100
with message-id <20190108124208.ga14...@msg.df7cb.de>
and subject line Re: Bug#798826: [Reproducible-builds] Bug#798826: DDPO:
displays not-for-us in reproducible builds column for architectures excluded in
the package
has caused the Debian Bug report #798826,
regarding DDPO: displays not-for-us in reproducible builds column for
architectures excluded in the package
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 ow...@bugs.debian.org
immediately.)
--
798826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
On my DDPO page intel-vaapi-driver is displayed as not-for-us in the
reproducible build column which is caused by r.d.n reporting intel-vaapi-driver
as not-for-us on armhf. This is expected since intel-vaapi-driver restricts its
Architecture field to i386, amd64, kfreebsd-i386 and kfreebsd-amd64. So please
ignore results for architectures that are explicitely excluded in the package.
This issue may be an issue in the data provided by r.d.n. In this case please
reassign it.
Cheers
--
Sebastian Ramacher
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Re: Holger Levsen 2015-09-13 <201509131505.06876.hol...@layer-acht.org>
> > * maybe care only about unstable: if a version in unstable is repr.
> > while the lower version in testing is not, then there is no need to
> > notify the user
>
> /reproducible-tracker.json already only includes data about unstable, for
> this
> very reason.
The problems with RB data (not) showing on DDPO have mostly been
sorted out over the last years, so I'm closing this bug now.
Christoph
--- End Message ---
