1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: openssh-server uninstallable

    From Dan Ritter@21:1/5 to Andy Wood on Wed Apr 30 13:30:01 2025
    Andy Wood wrote:
    Is anybody else being hit by a problem with openssh-server after the 1:10.0p1-2 migration into testing the other day?

    The following packages have unmet dependencies:
    openssh-server : Depends: openssh-client (= 1:9.9p2-2) but 1:10.0p1-2 is to be installed
    E: Unable to correct problems, you have held broken packages.
    E: The following information from --solver 3.0 may provide additional context:
    Unable to satisfy dependencies. Reached two conflicting decisions:
    1. openssh-server:amd64=1:9.9p2-2 is selected for install
    2. openssh-server:amd64=1:9.9p2-2 Depends openssh-client (= 1:9.9p2-2)
    but none of the choices are installable:
    [no choices]

    That's testing: sometimes it's broken. Looks like a timing issue
    which will resolve itself when 1:10.0p2-2 is uploaded. In the
    meantime, 1:10.0p1-2 is available.

    You should be prepared for things like this if you run testing;
    it's not meant for daily use.

    -dsr-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joe@21:1/5 to Dan Ritter on Wed Apr 30 14:10:01 2025
    On Wed, 30 Apr 2025 07:08:04 -0400
    Dan Ritter <dsr@randomstring.org> wrote:

    Andy Wood wrote:
    Is anybody else being hit by a problem with openssh-server after
    the 1:10.0p1-2 migration into testing the other day?

    The following packages have unmet dependencies:
    openssh-server : Depends: openssh-client (= 1:9.9p2-2) but
    1:10.0p1-2 is to be installed
    E: Unable to correct problems, you have held broken packages.
    E: The following information from --solver 3.0 may provide
    additional context: Unable to satisfy dependencies. Reached two
    conflicting decisions: 1. openssh-server:amd64=1:9.9p2-2 is
    selected for install 2. openssh-server:amd64=1:9.9p2-2 Depends openssh-client (= 1:9.9p2-2) but none of the choices are
    installable: [no choices]

    That's testing: sometimes it's broken. Looks like a timing issue
    which will resolve itself when 1:10.0p2-2 is uploaded. In the
    meantime, 1:10.0p1-2 is available.

    You should be prepared for things like this if you run testing;
    it's not meant for daily use.


    I think it is unusual, things don't normally move to testing until they
    have functioned reasonably well in unstable for a while. It is unstable
    which normally has a short list of non-upgradable things, though
    occasionally it's a long list.

    I also think the whole point of testing is to be pushed hard in daily
    use, in order to identify the bugs holding up the next release. Nobody
    wants the new stable to have received only limited and cautious testing
    before release.

    --
    Joe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Guthausen@21:1/5 to Andy Wood on Wed Apr 30 13:20:01 2025
    On Wed, 30 Apr 2025 09:53:34 +0100
    Andy Wood <ayup.gromit@gmail.com> wrote:

    Is anybody else being hit by a problem with openssh-server after the 1:10.0p1-2 migration into testing the other day?
    [...]
    E: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting
    decisions: 1. openssh-server:amd64=1:9.9p2-2 is selected for install

    Your package list assumes an older version
    of openssh-server, which is not provided by
    the repository. Try:

    apt update
    --
    kind regards
    Frank

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

    iQGzBAEBCgAdFiEE86z15c6qwvuAkhy+zDIN/uu9BloFAmgSBggACgkQzDIN/uu9 BloQ0Av+LloXbEj3w+nwf4GWwlF7y4hP57JSNsT2pCZKAPNaHmaEZMarVHvN168R nZ43ZurzDmJCxUx87jjjL4xdPcasGOm58Th6P32pK32Ude4a5rizh38oWZ6y2hZf EKpGfIKXrxEwrQsUt85/75oQwm5txIhmoUp5vJ8d66R0KRuZoCfXCwhaXYW1HbAc +SpURR386tBC6V5pkP8PxQNt9b7BFJ/jURv2M278N4jCI78+sDapdla2DfFmaLR4 Tmq6dElxak5Q1gZD1SW4VCVKhVQ5H/7q+tiacOpL+83HRemlCAjvZkRqP1xGWpLV utHQXqbIFY3oKnqvNNFVtEDRhJdnavcKhlOK3va29b9102ESQ9iSC0dhQ3Rveug6 zod/3OFhRffXOtMVj2O27/hXpSWxXHrbbmbKfZyh1To68nftb2Q0O6G0L5PX9NUB XflqkAuwPE1Qxbzuc/NXG4k8iyNWYnt/jgU0kH+7A/vM4lgEWHW6vmbI21TcgZKa
    oIevwvkL
    =kQAv
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonathan Dowland@21:1/5 to Joe on Wed Apr 30 15:00:02 2025
    On Wed Apr 30, 2025 at 1:04 PM BST, Joe wrote:
    I think it is unusual, things don't normally move to testing until
    they have functioned reasonably well in unstable for a while.

    Packages normally auto-migrate from unstable to testing, usually after 5
    days. See https://www.debian.org/doc/manuals/developers-reference/pkgs.html#basics

    --
    Please do not CC me for listmail.

    👱🏻 Jonathan Dowland
    ✎ jmtd@debian.org
    🔗 https://jmtd.net

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)