public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Andreas Fink <finkandreas@web.de>
Subject: Re: [gentoo-dev] sys-devel/autoconf wrong dependency?
Date: Wed, 31 Jan 2024 08:15:29 -0800	[thread overview]
Message-ID: <5b93076c-dd76-4bb8-aac7-04ca58adec40@gentoo.org> (raw)
In-Reply-To: <20240131135653.7b5ef23c@anfink-laptop>


[-- Attachment #1.1: Type: text/plain, Size: 1032 bytes --]

On 1/31/24 04:56, Andreas Fink wrote:
> With the move of sys-devel/autoconf to dev-build/autoconf the ebuild
> has some inconsistency, namely in the RDEPEND section, it is saying:
> 
> RDEPEND="
>          ${BDEPEND}
>          >=dev-build/autoconf-wrapper-20231224
>          sys-devel/gnuconfig
>          !~sys-devel/${P}:2.5
> "
> 
> This should probably be `!~dev-build/${P}:2.5`. It shows up in the
> following as a problem:
> emerge -auvDN --changed-deps=y --with-bdeps=y @world # --> merges autoconf-2.72-r1
> 
> Now:
> emaint --fix all # --> fixes dependency from sys-devel/autoconf to dev-build/autoconf
> 
> and again a full system update:
> emerge -auvDN --changed-deps=y --with-bdeps=y @world # --> merges autoconf-2.72-r1
> 
> This would want to again install autoconf, due to the changed-deps flag.
> 
> I am quite sure that this is not the intended behaviour, or is it?
> 
> Best
> Andreas
> 

Yeah, that's not intended. Reported as https://bugs.gentoo.org/923424.
-- 
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-01-31 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 12:56 [gentoo-dev] sys-devel/autoconf wrong dependency? Andreas Fink
2024-01-31 16:15 ` Zac Medico [this message]
2024-01-31 16:22 ` Ulrich Mueller

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=5b93076c-dd76-4bb8-aac7-04ca58adec40@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=finkandreas@web.de \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox