All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@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 12:34:50 +0200	[thread overview]
Message-ID: <ZJAvSrRXyng7dqd5@yuki> (raw)
In-Reply-To: <20230619103140.13925-1-pvorel@suse.cz>

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?

> Reported-by: Li Wang <liwang@redhat.com>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
>  ci/debian.minimal.sh | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/ci/debian.minimal.sh b/ci/debian.minimal.sh
> index c314d93fe..b51154b05 100755
> --- a/ci/debian.minimal.sh
> +++ b/ci/debian.minimal.sh
> @@ -1,5 +1,5 @@
>  #!/bin/sh
> -# Copyright (c) 2018-2020 Petr Vorel <pvorel@suse.cz>
> +# Copyright (c) 2018-2023 Petr Vorel <pvorel@suse.cz>
>  set -ex
>  
>  apt="apt remove -y"
> @@ -11,7 +11,6 @@ $apt \
>  	libaio-dev \
>  	libaio1 \
>  	libcap-dev \
> -	libcap2 \
>  	libkeyutils-dev \
>  	libnuma-dev \
>  	libnuma1 \
> -- 
> 2.41.0
> 

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2023-06-19 10:34 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 [this message]
2023-06-19 11:29   ` Petr Vorel

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