Bug#1142621: systemd-resolved: Cannot install systemd-resolved Depends: systemd (= 257.13-1~deb13u1) but 258.1-2 is to be installed

[Jean-Francois Pirus]

Hi, yes, sorry about that.

My source are currently just stable, but obviously I got some sid
packages in the past, 258.1-2 was installed on 2026-06-02

You can close it.
Thanks.


On Thu, 2026-07-23 at 01:22 +0200, Santiago Vila wrote:
> severity 1142621 normal
> thanks
> 
> On Thu, Jul 23, 2026 at 10:59:09AM +1200, jfp42 wrote:
> > Package: systemd-resolved
> > Version: 257.13-1~deb13u1
> > Severity: serious
> > Justification: unkown
> > 
> > Dear Maintainer,
> > 
> > Cannot install systemd-resolved, only version 257.13-1~deb13u1 is
> > available, but systemd is already at 258.1-2
> 
> Hi. I'm not the systemd maintainer, but I can say that this is most
> probably not a problem in the systemd-resolved package, and for that
> reason I'm adjusting the severity.
> 
> You might want to determine where exactly such 258.1-2 version comes
> from, because
> it's not available anymore, anywhere:
> 
> $ rmadison systemd
> [...]
> systemd    | 257.13-1~deb13u1 | stable                    | source,
> amd64, arm64, armel, armhf, i386, ppc64el, riscv64, s390x
> systemd    | 257.13-1~deb13u1 | stable-debug              | source
> systemd    | 261.1-3          | testing                   | source,
> amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
> systemd    | 261.1-3          | unstable                  | source,
> amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
> systemd    | 261.1-3          | unstable-debug            | source
> 
> 
> My best theory is that you mixed your sources.list lines in a weird
> way which is not really supported (like mixing stable and testing,
> for
> example).
> 
> Thanks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20260723/f6f0249a/attachment.htm>