All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [COMMITTED][PATCH 1/1] ci/debian.minimal.sh: Keep libcap2
Date: Mon, 19 Jun 2023 13:29:38 +0200	[thread overview]
Message-ID: <20230619112938.GA129463@pevik> (raw)
In-Reply-To: <ZJAvSrRXyng7dqd5@yuki>

> Hi!
> > Trying to remove libcap2 for minimal environment no longer works for
> > Debian 12 bookworm (the new Debian stable release). It looks like
> > libcap2 is required by apt itself:

> > apt remove -y libcap2
> > The following packages have unmet dependencies:
> >  apt : Depends: libapt-pkg6.0 (>= 2.6.1) but it is not going to be installed
> >        Depends: libsystemd0
> >  bsdutils : PreDepends: libsystemd0
> >  util-linux : PreDepends: libsystemd0
> > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

> Shouldn't be removal of libcap-dev enough for us not to compile LTP
> against it? Why do we remove libcap2 in the first place?

Yes, you're right. I'm not sure now, but removing libcap-dev was probably enough
even back then.

NOTE: the other error (on debian stable) is metadata generation with asciidoc,
where it miss docbook2x package. I'll send a patch instead of directly fixing
it.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2023-06-19 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 10:31 [LTP] [COMMITTED][PATCH 1/1] ci/debian.minimal.sh: Keep libcap2 Petr Vorel
2023-06-19 10:34 ` Cyril Hrubis
2023-06-19 11:29   ` Petr Vorel [this message]

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=20230619112938.GA129463@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.