• Re: salt removed from mirror

    From Jeremy Stanley@21:1/5 to Johannes Drexl on Fri Aug 9 16:20:01 2024
    On 2024-08-09 13:31:02 +0000 (+0000), Johannes Drexl wrote:
    I tried to install a system with Debian 11 and a preseed file today
    from our internal mirror and found out that the package salt-minion was
    gone. After some research (our mirror snapshots every day) I found out
    that between 2024-06-29 02:00 and 2024-06-30 02:00 the whole salt
    directory was silently dropped from the upstream mirrors. Even packages.debian.org does no longer display any information about it.

    I was under the impression that the software stack of a
    stable/oldstable release does not change anymore (safe for security
    updates and suchlike), so I'm pretty flabberghasted by this. More so as
    I cannot find a mention about this on debian-devel, where I would
    assume such decisions would be discussed prior to the actual doing.

    Can somebody please shed some light on this?

    A quick bit of digging on https://tracker.debian.org/ indicates the
    salt-minion package was not part of Debian 11[*] since it retained
    at least one severe bug[**] which was never fixed. The change you
    observed seems to probably be related to cleanup of lingering
    debian-security content[***]. Hope that helps.

    [*] https://bugs.debian.org/1069654
    [**] https://bugs.debian.org/1009804
    [***] https://bugs.debian.org/1074468
    --
    Jeremy Stanley

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

    iQKTBAABCgB9FiEEl65Jb8At7J/DU7LnSPmWEUNJWCkFAma2JLhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk3 QUU0OTZGQzAyREVDOUZDMzUzQjJFNzQ4Rjk5NjExNDM0OTU4MjkACgkQSPmWEUNJ WClyqxAAon9QRcrBJepMi0sYniblR6YrCUr8iuLVE9Yo3SuEA9b0NNNmSlRuswyp FwxM0sFw8DMy8hYeAz4qaekockJY6sVeZXCEsOKbIDC5Jbpta84PL8WXK7Cu1t7T TGjMxRh1P0hoa44YBIsHi9mWwwANWn0oRLWCRzyl++AKuN4PYFqXJzIsUzxIct7f mnmz506AbXHio6k9op4fB/VzqgwVznaQw5al0PjBGNS25Rr1vO88VDJ+reGMWTOU 8lbCRk9JiO1aVt0M0XwjXWFHrCXuSjwbuAyKfUsWrtd1Guw0xWg7CHzfMM3aUrNx vGRkd5FFygsdHnAEKz8HspYCA93QExZJlmW66KvEavDrNwGgSP50Lz/aVi9rOVYB YcFsFWCtoPZId81JO6vGZ0K3mTmWLt2XagX1H+3UjxlOp1YmZ7vyf2Wb68/QmFyU QqTwXj0eAF3E69uIlpv1bZD/DtMZSF0W3GP09zH2/pDT9CT7E+JSNzptzBKtXWsF XcH4hIUcN2eaefEoFxjMK7Pac+TE7KLdkaL0CP0sQHuw6bI676p3XCdDMlpLsr2B AAcix/aox0rl3cvCwif0WWj/iswsgl5RYC+iyTUp2fb5V1blYRRThwcPGI9bXBrd SMx5WjSLG/jNSrHuV/b3YOFL2yytTXZaQOPDrxFR79xLgAEz6zY=
    =jkY6
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32
  • From Simon McVittie@21:1/5 to Johannes Drexl on Fri Aug 9 16:30:01 2024
    On Fri, 09 Aug 2024 at 13:31:02 +0000, Johannes Drexl wrote:
    I was under the impression that the software stack of a
    stable/oldstable release does not change anymore (safe for security
    updates and suchlike), so I'm pretty flabberghasted by this. More so as
    I cannot find a mention about this on debian-devel, where I would
    assume such decisions would be discussed prior to the actual doing.

    Can somebody please shed some light on this?

    debian-devel primarily deals with development of the next version
    of Debian, and the (old)stable releases are managed by the stable
    release team. Removals and other more major changes in (old)stable are intentionally rare, but can happen.

    In the case of salt, it was removed from Debian 11 in the 11.10 point
    release, as announced in <https://lists.debian.org/debian-stable-announce/2024/06/msg00000.html>.

    This was requested by a security team member in <https://bugs.debian.org/1070175>, prompted by its removal from unstable
    in <https://bugs.debian.org/1069654>, which appears to have been caused by
    not having any volunteers willing to take responsibility for maintaining
    this security-sensitive package.

    Older versions of the salt package continue to be available from <https://snapshot.debian.org/package/salt/> but will not receive any
    security or bug-fix updates. The upstream developers have their own
    newer Debian-compatible packages available, https://docs.saltproject.io/salt/install-guide/en/latest/topics/install-by-operating-system/debian.html
    (these are not supported by the Debian project).

    (Also note that Debian 11 comes to the end of its normal support lifetime
    in a few days' time, on 2024-08-14, although the Debian LTS subproject
    plans to provide limited security maintenance for an additional 2 years.)

    smcv

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Geert Stappers@21:1/5 to Johannes Drexl on Fri Aug 9 23:10:01 2024
    On Fri, Aug 09, 2024 at 03:52:01PM +0000, Johannes Drexl wrote:
    Am Freitag, dem 09.08.2024 um 15:27 +0100 schrieb Simon McVittie:
    On Fri, 09 Aug 2024 at 13:31:02 +0000, Johannes Drexl wrote:
    I was under the impression that the software stack of a
    stable/oldstable release does not change anymore (safe for security updates and suchlike), so I'm pretty flabberghasted by this. More
    so as
    I cannot find a mention about this on debian-devel, where I would
    assume such decisions would be discussed prior to the actual doing.

    Can somebody please shed some light on this?

    debian-devel primarily deals with development of the next version
    of Debian, and the (old)stable releases are managed by the stable
    release team. Removals and other more major changes in (old)stable
    are intentionally rare, but can happen.

    In the case of salt, it was removed from Debian 11 in the 11.10 point release, as announced in <https://lists.debian.org/debian-stable-announce/2024/06/msg00000.html> .

    This was requested by a security team member in <https://bugs.debian.org/1070175>, prompted by its removal from
    unstable in <https://bugs.debian.org/1069654>, which appears to
    have been caused by not having any volunteers willing to take responsibility for maintaining this security-sensitive package.

    While I get the idea behind this, having salt (as a machine management package) removed from the official mirror in a stable release strikes
    me a bit odd - the already installed packages won't be removed, and as
    it is a management package, one could expect this gets installed in
    automated setups. This wouldn't be a problem as such, if the preseed
    file would accept a multitude of mirrors, alas all tests I've done in
    the past only allowed for a single source, and using late_command in
    the preseed to first inject an additional mirror and then install the
    package from there did not work as far as I remember.

    It seems I need to fall back to an old version of mirror & PXE package
    for the installation.

    Older versions of the salt package continue to be available from <https://snapshot.debian.org/package/salt/> but will not receive any security or bug-fix updates. The upstream developers have their own
    newer Debian-compatible packages available, https://docs.saltproject.io/salt/install-guide/en/latest/topics/install-by-operating-system/debian.html
    (these are not supported by the Debian project).

    (Also note that Debian 11 comes to the end of its normal support
    lifetime in a few days' time, on 2024-08-14, although the Debian
    LTS subproject plans to provide limited security maintenance for an additional 2 years.)

    smcv
    Thx, I'm aware I'm on oldstable here, but replacing old systems is
    sometimes not as fast as I'd hope it'd be ;)


    Yes, there is (sadly) some consensus that somebody else should do it.

    Thing that makes me wonder is how to appreciate those that
    take care of salt-stack in Debian.


    Groeten
    Geert Stappers
    --
    Silence is hard to parse

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