1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • Re: [gentoo-user] No binary llvm-19.1.4 package

    From Eli Schwartz@21:1/5 to Jacques Montier on Sun Dec 8 16:20:01 2024
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------ao3S1WP0rlnGNM0keWsCWcf2
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    On 12/8/24 6:14 AM, Jacques Montier wrote:
    I have two Gentoo OS that are supposedly identical.


    If the entire contents of /etc/portage are identical, then in theory you
    should always get the same packages on both machines. Is it just the
    package list or the entire portage configuration that is identical?


    My emerge world :
    emerge -auvDN --with-bdeps=y --binpkg-respect-use=y --keep-going world

    emerge --info for the second OS in an attached file.


    Where could this difference be coming from?


    Your use of --binpkg-respect-use=y deletes one form of diagnostic. The
    default behavior of portage without that flag specified is for portage to:

    - respect USE flags
    - verbosely log a warning if binaries were ineligible due to USE flags

    With that flag set to =y, the verbose warning log is disabled. That is all.

    Can you try running emerge without that flag? It should print a message
    that looks a bit like this:


    !!! The following binary packages have been ignored due to non matching USE:

    =dev-lang/python-3.13.1 llvm_slot_18 -verify-sig
    =dev-lang/python-3.13.1 llvm_slot_18 -pgo -verify-sig

    NOTE: The --binpkg-respect-use=n option will prevent emerge
    from ignoring these binary packages if possible.
    Using --binpkg-respect-use=y will silence this warning.

    If the issue is USE flags, then that will tell you. The lines printed
    are valid package.use lines which would cause you to start using that
    binary package.


    --
    Eli Schwartz

    --------------ao3S1WP0rlnGNM0keWsCWcf2--

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZ1W4nwUDAAAAAAAKCRCEp9ErcA0vV0ws AP9YlfS61YKOcBz8O5e9m3+Nt5tSdrUQGdttVOFgaQ7BpwEAvM3UepEW7cQkFgX0Jvpy0cv92QAL 6mpoXmI8CrpetA4=
    =Vbcr
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eli Schwartz@21:1/5 to Dr Rainer Woitok on Sun Dec 8 18:50:01 2024
    To: [email protected]

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------CrZVYaiiLirIrEHgGFJHu4pF
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    On 12/8/24 12:39 PM, Dr Rainer Woitok wrote:
    Eli,

    On Sun, 8 Dec 2024 10:17:50 -0500 you wrote:

    ...
    Your use of --binpkg-respect-use=y deletes one form of diagnostic. The
    default behavior of portage without that flag specified is for portage to: >>
    - respect USE flags
    - verbosely log a warning if binaries were ineligible due to USE flags

    With that flag set to =y, the verbose warning log is disabled. That is all.

    I've seen this remark somewhere and have therefore removed this option
    from my "make.conf" file already some time ago, but I have still to see
    this message. Is it also issued with "--pretend" and does it go to std-
    out or just to the log file? If the former, it's probably suppressed by
    the "--quiet" option in my "make.conf". I will try with that option re- moved.

    Thanks for reminding me :-)

    Sincerely,
    Rainer


    Yes, with emerge --pretend it will still print the same message to the
    console. It will be suppressed by --quiet.


    --
    Eli Schwartz

    --------------CrZVYaiiLirIrEHgGFJHu4pF--

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZ1XbwwUDAAAAAAAKCRCEp9ErcA0vV8ob APwIhnGt3Ak3I+s1X24Lgu7MkXD4VZbx6lU2zTwFUpCEhwEAwYNmiAJOhTS0NiiSmerP+33UZPJZ UniIXm/rRK47bw4=
    =rSfz
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Sun Dec 8 23:30:01 2024
    On Sunday 8 December 2024 16:17:15 GMT Jacques Montier wrote:

    I saw that the two directories /etc/portage were different, particularly
    the make.conf files. So i copied the first one to replace the second, and everything went back to normal.

    I would have difficulty detecting where the differences between the two directories came from.

    Have you looked into meld? http://meldmerge.org/

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)