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

Bug#875498: marked as done (upgrade-reports: systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+deb8u1 is to be installed)

Your message dated Tue, 9 Mar 2021 21:55:37 +0100
with message-id <43b04122-a47b-31d6-d220-2540e920dc6b@debian.org>
and subject line upgrade report for EOL Debian release
has caused the Debian Bug report #875498,
regarding upgrade-reports: systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+deb8u1 is to be installed
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.)


-- 
875498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875498
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Attempting to upgrade Jessie to Stretch

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Replaced Jessie with Stretch in /etc/apt/sources.list
apt-get update
apt-get dist-upgrade


   * What was the outcome of this action?

:/home/david# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Some packages could not be installed. This may mean that
you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 systemd : Breaks: rdnssd (< 1.0.1-5) but 1.0.1-1+deb8u1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.


:/home/david# apt-cache policy rdnssd
rdnssd:
  Installed: 1.0.1-1+deb8u1
  Candidate: 1.0.3-3
  Version table:
     1.0.3-3 0
        700 http://ftp.utexas.edu/debian/ stretch/main amd64 Packages
 *** 1.0.1-1+deb8u1 0
        100 /var/lib/dpkg/status




root@Belldandy:/home/david# dpkg -l | grep rdnssd
ii  rdnssd                                1.0.1-1+deb8u1
amd64        IPv6 recursive DNS server discovery daemon


root@Belldandy:/home/david# dpkg -l | grep systemd
ii  libpam-systemd:amd64                  215-17+deb8u7
amd64        system and service manager - PAM module
ii  libsystemd0:amd64                     215-17+deb8u7
amd64        systemd utility library
ii  libsystemd0:i386                      215-17+deb8u7
i386         systemd utility library
ii  systemd                               215-17+deb8u7
amd64        system and service manager
ii  systemd-sysv                          215-17+deb8u7
amd64        system and service manager - SysV links


root@Belldandy:/home/david# dpkg --get-selections | grep hold
root@Belldandy:/home/david#


I have no held packages.


   * What outcome did you expect instead?

I expected a solution / upgrade path to be found by apt-get dist-upgrade.

I have done a google search and found many people reporting that doing an "apt-
get remove rdnssd" resolves the issue, but I would think that apt-get should
find this upgrade path automatically?

Do I really have to remove this package in order to have an upgrade path?  I
looked at the packages included in Stretch and rdnssd exists in stretch.




-- System Information:
Debian Release: 8.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Dear reporter,

Thanks for taking the time long ago to submit your upgrade report. I'm
closing these reports now because the Debian releases they were reported
against have reached their end-of-life (some long ago).

Unfortunately it's possible that the report I'm now closing may still
have relevant information for the current release (bullseye). If you
believe that's the case, don't hesitate to reopen the bug, retitle it
and provide further information and it will be seen during the current
freeze period of Debian.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: