All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Fabiano Rosas <farosas@suse.de>
Subject: Re: openSUSE container failure
Date: Tue, 3 Feb 2026 10:09:02 +0000	[thread overview]
Message-ID: <aYHJPoaFEfs2G3kI@redhat.com> (raw)
In-Reply-To: <74094b25-73bc-4e76-a7d6-d41e2a22c6b9@linaro.org>

On Tue, Feb 03, 2026 at 10:47:46AM +1000, Richard Henderson wrote:
> E.g. https://gitlab.com/qemu-project/qemu/-/jobs/12960514743
> 
> Annoyingly, the gitlab pipeline drops some critical lines that show the
> error.  Thankfully I can reproduce locally:
> 
> > Resolving package dependencies...
> > 
> > Problem: 1: nothing provides 'rust1.93' needed by the to be installed rust-1.93.0-150500.27.62.1.x86_64
> >  Solution 1: do not install rust-1.93.0-150500.27.62.1.x86_64
> >  Solution 2: break rust-1.93.0-150500.27.62.1.x86_64 by ignoring some of its dependencies
> > 
> > Choose from above solutions by number or cancel [1/2/c/d/?] (c): c
> 
> It does appear that there's no rust package available anymore?
> Should we just drop rust from this image for now?

It appears opensuse repos have pushed broken the Rust packages.  "rust" is
available, but it has a dep on "rust1.93" which is NOT published, the
newest is "rust1.92". 

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2026-02-03 10:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03  0:47 openSUSE container failure Richard Henderson
2026-02-03 10:09 ` Daniel P. Berrangé [this message]
2026-02-03 13:53   ` Fabiano Rosas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aYHJPoaFEfs2G3kI@redhat.com \
    --to=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.