Your message dated Wed, 2 May 2018 13:02:51 +0200
with message-id <b6d55cf7-b95c-d083-11de-4f547c707...@debian.org>
and subject line Re: googletest: breakage due to files moved to other packages
has caused the Debian Bug report #897104,
regarding googletest: breakage due to files moved to other packages
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.)
--
897104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: googletest
Version: 1.8.0-9
Severity: serious
Control: affects -1 src:apt src:flightcrew src:protobuf src:synergy src:aff4
src:meson src:fmtlib src:cctz
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apt.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flightcrew.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/protobuf.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/synergy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aff4.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fmtlib.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cctz.html
The proper way, also for stretch -> buster upgrades, would be to move
the contents of the googletest binary package elsewhere and turn it
into an empty meta package depending on all other packages.
--- End Message ---
--- Begin Message ---
On Sat, 28 Apr 2018 17:21:35 +0300 Adrian Bunk <b...@debian.org> wrote:
> Package: googletest
> Version: 1.8.0-9
> Severity: serious
> Control: affects -1 src:apt src:flightcrew src:protobuf src:synergy src:aff4
> src:meson src:fmtlib src:cctz
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apt.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flightcrew.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/protobuf.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/synergy.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/aff4.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/meson.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fmtlib.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cctz.html
>
> The proper way, also for stretch -> buster upgrades, would be to move
> the contents of the googletest binary package elsewhere and turn it
> into an empty meta package depending on all other packages.
This is being fixed in the rdeps, with most of them fixed (in sid or
experimental) or with patches or updates in the delayed queue. Let's track this
in the bugs for the rdepends since those are the packages that need to be
changed.
Emilio
--- End Message ---
