Your message dated Sat, 13 Jan 2018 18:01:11 +0100
with message-id <20180113170111.vcrmxfvr5oejb...@betterave.cristau.org>
and subject line Re: Bug#883879: release.debian.org: Upgrade to
linux-image-4.9.0-4-amd64 version in stable-proposed-updates prompts upgrade to
version of linux-cpupower in stable-backports
has caused the Debian Bug report #883879,
regarding release.debian.org: Upgrade to linux-image-4.9.0-4-amd64 version in
stable-proposed-updates prompts upgrade to version of linux-cpupower in
stable-backports
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.)
--
883879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: minor
linux-cpupower version in stable is 4.9.51-1 which corresponds to the kernel
currently in stable that will be upgraded in a few days. I upgraded a day early
or two early. I did upgrade the package with no problems. This is just a heads
up for anyone that this my concern.
Thanks
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Fri, Dec 8, 2017 at 10:42:03 -0800, CJanisch wrote:
> Package: release.debian.org
> Severity: minor
>
> linux-cpupower version in stable is 4.9.51-1 which corresponds to the kernel
> currently in stable that will be upgraded in a few days. I upgraded a day
> early
> or two early. I did upgrade the package with no problems. This is just a heads
> up for anyone that this my concern.
>
Probably due to your pinning configuration that prefers backports over
proposed-updates? We don't seem to have had any other reports of this,
so I'll close it. Thanks for your feedback.
Cheers,
Julien
--- End Message ---
