| View previous topic :: View next topic |
| Author |
Message |
Massimo B.
Veteran
Joined: 09 Feb 2005
Posts: 1820
Location: PB, Germany
|
 Posted: Mon Dec 09, 2024 8:05 am Post subject: eix [?] and permissions |
 |
|
Hi,
often I see some [?] status on packages. Usually this is due to wrong permissions in /etc/portage. I'm still not sure how that happens and what the right permissions should be there.
I'm not sure why eix is showing that [?] eventhough it can read all required files.
Currently seen on this packages: | Code: | # eix microsoft-edge-dev
[?] www-client/microsoft-edge-dev
Available versions: ~132.0.2957.7^msd ~132.0.2957.11^msd ~133.0.2992.0^msd {+mip qt5 qt6}
Installed versions: 133.0.2992.0^msd(08:41:53 09.12.2024)(mip qt5 qt6)
Homepage: https://www.microsoft.com/edge
Description: The web browser from Microsoft |
Current status of files: | Code: | # find /etc/portage -type f -exec ls -l {} +
-rw-r----- 1 portage portage 457 13. Jun 2019 /etc/portage/bashrc
-rw-r----- 1 portage portage 64 21. Okt 2015 /etc/portage/categories
-rwxr-xr-x 1 portage portage 787 12. Jun 19:14 /etc/portage/conf-update.d/etckeeper
-rw-r--r-- 1 portage portage 70 15. Mär 2023 /etc/portage/.cvsignore
-rw-r--r-- 1 portage portage 671 21. Okt 2015 /etc/portage/env/cross-arm-unknown-linux-gnueabi/binutils.conf
-rw-r--r-- 1 portage portage 671 21. Okt 2015 /etc/portage/env/cross-arm-unknown-linux-gnueabi/gcc.conf
-rw-r--r-- 1 portage portage 671 21. Okt 2015 /etc/portage/env/cross-arm-unknown-linux-gnueabi/gdb.conf
-rw-r--r-- 1 portage portage 596 21. Okt 2015 /etc/portage/env/cross-arm-unknown-linux-gnueabi/glibc.conf
-rw-r--r-- 1 portage portage 596 21. Okt 2015 /etc/portage/env/cross-arm-unknown-linux-gnueabi/linux-headers.conf
-rw-r----- 1 portage portage 671 3. Dez 2014 /etc/portage/env/cross-powerpc-unknown-linux-gnu/binutils.conf
-rw-r----- 1 portage portage 671 3. Dez 2014 /etc/portage/env/cross-powerpc-unknown-linux-gnu/gcc.conf
-rw-r----- 1 portage portage 671 3. Dez 2014 /etc/portage/env/cross-powerpc-unknown-linux-gnu/gdb.conf
-rw-r----- 1 portage portage 596 3. Dez 2014 /etc/portage/env/cross-powerpc-unknown-linux-gnu/glibc.conf
-rw-r----- 1 portage portage 596 3. Dez 2014 /etc/portage/env/cross-powerpc-unknown-linux-gnu/linux-headers.conf
-rw-r--r-- 1 portage portage 111 8. Sep 2021 /etc/portage/env/debug
-rw-r--r-- 1 portage portage 82 9. Okt 2017 /etc/portage/env/eix-extra-econf
-rw-r--r-- 1 portage portage 81 22. Aug 2023 /etc/portage/env/http_proxy
-rw-r--r-- 1 portage portage 38 8. Sep 2021 /etc/portage/env/installsources
-rw-r--r-- 1 portage portage 138 18. Jul 2022 /etc/portage/env/noccache
-rw-r--r-- 1 root root 29 5. Sep 10:13 /etc/portage/env/no_proxy
-rw-r--r-- 1 portage portage 35 18. Jul 2022 /etc/portage/env/notmpfs
-rw-r--r-- 1 portage portage 41 19. Jan 2022 /etc/portage/env/palemoon
-rw-r--r-- 1 portage portage 1895 3. Dez 08:11 /etc/portage/make.conf/global
-rw-r--r-- 1 portage portage 959 30. Aug 07:06 /etc/portage/make.conf/local
-rw-r----- 1 portage portage 78 26. Aug 08:01 /etc/portage/package.accept_keywords/categories
-rw-r----- 1 portage portage 298 2. Aug 2012 /etc/portage/package.accept_keywords/cross-powerpc-unknown-linux-gnu
-rw-r----- 1 portage portage 2152 18. Okt 10:10 /etc/portage/package.accept_keywords/custom
-rw-r--r-- 1 portage portage 58 10. Nov 2022 /etc/portage/package.accept_keywords/custom.local
-rw-r--r-- 1 portage portage 0 4. Sep 08:22 /etc/portage/package.accept_keywords/temp
-rw-r--r-- 1 portage portage 419 21. Okt 2015 /etc/portage/package.env/cross-arm-unknown-linux-gnueabi
-rw-r----- 1 portage portage 419 3. Dez 2014 /etc/portage/package.env/cross-powerpc-unknown-linux-gnu
-rw-r--r-- 1 portage portage 29 21. Sep 2020 /etc/portage/package.env/custom
-rw-r--r-- 1 portage portage 97 18. Jul 2022 /etc/portage/package.env/debug
-rw-r--r-- 1 portage portage 32 9. Okt 2017 /etc/portage/package.env/extra-econf
-rw-r--r-- 1 portage portage 26 13. Jan 2020 /etc/portage/package.env/noccache
-rw-r--r-- 1 portage portage 309 24. Nov 2022 /etc/portage/package.env/notmpfs
-rw-r--r-- 1 portage portage 219 18. Sep 10:21 /etc/portage/package.env/proxy
-rw-r----- 1 portage portage 1123 9. Dez 08:41 /etc/portage/package.license/custom
-rw-r--r-- 1 portage portage 0 24. Nov 2022 /etc/portage/package.license/custom.local
-rw-r----- 1 portage portage 0 1. Aug 2022 /etc/portage/package.mask/custom
-rw-r----- 1 portage portage 442 26. Mär 2024 /etc/portage/package.mask/repos
-rw-r--r-- 1 portage portage 76 10. Aug 2023 /etc/portage/package.mask/temp
-rw-r----- 1 portage portage 754 17. Okt 07:13 /etc/portage/package.unmask/custom
-rw-r----- 1 portage portage 34 4. Nov 2022 /etc/portage/package.unmask/custom.local
-rw-r----- 1 portage portage 0 16. Feb 2021 /etc/portage/package.unmask/portage
-rw-r--r-- 1 portage portage 0 26. Jul 2022 /etc/portage/package.unmask/temp
-rw-r--r-- 1 portage portage 5548 27. Mär 2024 /etc/portage/package.use/abi_x86_32
-rw-r--r-- 1 portage portage 60 21. Okt 2015 /etc/portage/package.use/cross-arm-unknown-linux-gnueabi
-rw-r----- 1 portage portage 60 3. Dez 2014 /etc/portage/package.use/cross-powerpc-unknown-linux-gnu
-rw-r--r-- 1 portage portage 5773 6. Dez 09:12 /etc/portage/package.use/custom
-rw-r--r-- 1 portage portage 0 11. Jul 08:12 /etc/portage/package.use/custom.local
-rw-r--r-- 1 portage portage 155 1. Aug 2022 /etc/portage/package.use/expand
-rw-r--r-- 1 portage portage 285 26. Jul 2023 /etc/portage/package.use/expand.local
-rw-r--r-- 1 portage portage 744 11. Jul 08:13 /etc/portage/package.use/global
-rw-r--r-- 1 portage portage 0 11. Jul 08:14 /etc/portage/package.use/global.local
-rw-r--r-- 1 portage portage 2815 3. Dez 07:00 /etc/portage/package.use/portage
-rw-r--r-- 1 portage portage 2950 10. Mär 2020 /etc/portage/patches/media-gfx/cropgui-0.4/integer-scaling.patch
-rw-r--r-- 1 portage portage 389 29. Dez 2021 /etc/portage/patches/media-gfx/geeqie-1.5.1/geeqie-rotate.patch
-rw-r--r-- 1 portage portage 459 20. Apr 2020 /etc/portage/patches/net-vpn/vpnc-0.5.3_p550-r3/fortinet.patch
-rw-r--r-- 1 portage portage 14234 12. Dez 2018 /etc/portage/patches/sys-kernel/ck-sources/bcache-patches.patch
-rw-r--r-- 1 portage portage 2580 24. Sep 2019 /etc/portage/patches/xfce-extra/xfce4-statusnotifier-plugin-0.2.1/xfce_bug#15110_teamviewer.patch
-rw-r----- 1 portage portage 1 10. Nov 2022 /etc/portage/profile/package.provided
-rw-r--r-- 1 portage portage 247 21. Okt 2015 /etc/portage/profile/package.use.force/cross-arm-unknown-linux-gnueabi
-rw-r----- 1 portage portage 247 3. Dez 2014 /etc/portage/profile/package.use.force/cross-powerpc-unknown-linux-gnu
-rw-r--r-- 1 portage portage 247 21. Okt 2015 /etc/portage/profile/package.use.mask/cross-arm-unknown-linux-gnueabi
-rw-r----- 1 portage portage 247 3. Dez 2014 /etc/portage/profile/package.use.mask/cross-powerpc-unknown-linux-gnu
-rw-r--r-- 1 portage portage 68 18. Jul 2022 /etc/portage/profile/package.use.mask/custom
-rw-r--r-- 1 portage portage 21 10. Jan 2018 /etc/portage/profile/package.use.mask/profile-17.0.mask
-rw-r--r-- 1 portage portage 0 26. Jul 2022 /etc/portage/profile/package.use.mask/temp
-rw-r--r-- 1 portage portage 14 23. Jan 2017 /etc/portage/profile/use.mask/xall
-rw-r--r-- 1 portage portage 2435 26. Mär 2024 /etc/portage/repos.conf/eselect-repo.conf
-rw-rw---- 1 portage portage 307 7. Jun 2019 /etc/portage/repos.conf/gentoo.conf
-rw-r--r-- 1 portage portage 61 27. Mär 2017 /etc/portage/repos.conf/local.conf
-rw-r--r-- 1 portage portage 148 11. Mär 2019 /etc/portage/repos.conf/oomox-overlay.conf
-rw-r--r-- 1 portage portage 310 8. Jul 2022 /etc/portage/repos.conf/others.conf
-rw-r----- 1 portage portage 208 5. Jun 2012 /etc/portage/rsync_excludes
-rw-rw-r-- 1 root root 132636 28. Okt 13:15 /etc/portage/savedconfig/sys-kernel/linux-firmware-20241017-r3
-rw-r--r-- 1 portage portage 399 28. Mär 2024 /etc/portage/savedconfig/x11-misc/slock-1.5
-rw-r--r-- 1 root root 2838 12. Jun 22:08 /etc/portage/savedconfig/x11-misc/tabbed-0.8-r1
-rw-r--r-- 1 portage portage 10424 21. Okt 13:44 /etc/portage/sets/machine_shared
-rw-r--r-- 1 root portage 134 26. Aug 08:26 /etc/portage/sets/machine_wireless
-rw-r--r-- 1 portage portage 46 13. Jun 10:14 /etc/portage/smart-live-rebuild.conf
|
Usually I repair it like this... | Code: | chown portage:portage -cR /etc/portage/
chmod -cR o+r /etc/portage |
But this time the [?] is still there. How can I solve that? What is the best setting for /etc/portage and how to maintain that?
Curiously this does not affect all packages, like here: | Code: | # eix -I gcc
[U] sys-devel/gcc
Available versions:
(8.5.0) [M]8.5.0-r2^t
(9.5.0) [M]9.5.0^t
(10) [M]10.5.0^t
(11) 11.5.0^t
(12) 12.4.0^t 12.4.1_p20241031^t 12.4.1_p20241114^t **12.4.1_p20241121^t **12.4.1_p20241128^t **12.4.1_p20241205^t **12.5.9999*l^t
(13) ~13.2.0^t 13.3.1_p20240614^t 13.3.1_p20241025^t 13.3.1_p20241115^t **13.3.1_p20241122^t **13.3.1_p20241129^t **13.3.1_p20241206^t **13.4.9999*l^t
(14) 14.2.1_p20241116^t **14.2.1_p20241123^t **14.2.1_p20241130^t **14.2.1_p20241207^t **14.3.9999*l^t
(15) **15.0.0_pre20241117-r2^t **15.0.0_pre20241124^t **15.0.0_pre20241201^t **15.0.0_pre20241208^t **15.0.9999*l^t
{ada cet custom-cflags +cxx d debug default-stack-clash-protection default-znow doc fixed-point +fortran go graphite hardened ieee-long-double jit libgdiagnostics libssp lto modula2 multilib +nls objc objc++ objc-gc (+)openmp pch pgo +pie rust +sanitize +ssp systemtap test time64 valgrind vanilla vtv zstd}
Installed versions: 13.3.1_p20240614(13)^t(12:07:51 29.07.2024)(cet cxx default-stack-clash-protection default-znow fortran multilib nls openmp pie sanitize ssp zstd -ada -custom-cflags -d -debug -doc -fixed-point -go -graphite -hardened -ieee-long-double -jit -libssp -lto -modula2 -objc -objc++ -objc-gc -pch -pgo -systemtap -test -valgrind -vanilla -vtv) 14.2.1_p20241116(14)^t(10:23:15 03.12.2024)(cet cxx default-stack-clash-protection default-znow fortran multilib nls openmp pie sanitize ssp zstd -ada -custom-cflags -d -debug -doc -fixed-point -go -graphite -hardened -ieee-long-double -jit -libssp -lto -modula2 -objc -objc++ -objc-gc -pch -pgo -rust -systemtap -test -time64 -valgrind -vanilla -vtv)
Homepage: https://gcc.gnu.org/
Description: The GNU Compiler Collection
[I] sys-devel/gcc-config
Available versions: 2.11 ~2.12.1 **9999*l {+cc-wrappers +native-symlinks}
Installed versions: 2.11(15:39:45 26.03.2024)(cc-wrappers native-symlinks)
Homepage: https://gitweb.gentoo.org/proj/gcc-config.git/
Description: Utility to manage compilers
[I] x11-misc/gccmakedep
Available versions: 1.0.4
Installed versions: 1.0.4(13:44:06 15.04.2024)
Homepage: https://www.x.org/wiki/ https://gitlab.freedesktop.org/xorg/util/gccmakedep
Description: create dependencies in makefiles using 'gcc -M'
|
_________________
HP ZBook Power 15.6" G8 i7-11800H|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770 |
|
| Back to top |
|
 |
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1487
Location: Earth
|
| Posted: Mon Dec 09, 2024 5:14 pm Post subject: |
|
|
even after eix-update there's a ?
this is a question not a statement !
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
bstaletic
Guru
Joined: 05 Apr 2014
Posts: 453
|
| Posted: Mon Dec 09, 2024 5:42 pm Post subject: |
|
|
If I remember correctly, this happens when the ebuild gets removed from the overlay, so eix can't find the thing you have installed.
Anyway, man eix has a nice OUTPUT section.
| man eix: | [U?] == foo/bar (1.1(1)@01.01.2009; 1.1(1) -> 2.0(2)): description
The status of package foo/bar has changed in the tree (for your settings): The symbols on the left mean that a slot you have installed can be upgraded (without modifying
masks/keywords), and that another slot you have installed was removed/masked. Looking at the versions on the right, it becomes clear that the installed version 1.1 of Slot 1
has been removed or masked, and that there is no other installed version of slot 1. However, a new stable version 2.0 in slot 2 has appeared (i.e. slot 2 did previously not
exist or had no stable version).
Since no version of slot 2 was installed yet, eix cannot decide in this situation whether the symbol "U" is really appropriate: Since eix does no dependency tracking, it does
not know whether the new slot would be pulled in e.g. by your world file, or whether there is only some dependency to your old slot. Therefore, the symbol "U" is only shown in
this situation if UPGRADE_TO_HIGHEST_SLOT=true or if the package is listed in /etc/portage/package.slot_upgrade_allow.
Actually, the output [U?><] == foo/bar ... would be more consistent, because in addition one slot has gained a higher stable version and the highest stable version of another
slot was removed, but since typically this is implicitly implied by "U" or "?", respectively, it was a design decision of the default setting that if U or ? is output then the
symbols < and > will not be output. You can of course build a different DIFF_FORMAT_HEADER_CHANGED string which follows another policy. |
|
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1977
|
| Posted: Mon Dec 09, 2024 8:16 pm Post subject: |
|
|
| The "[?]" is output when an installed package cannot be determined to upgrade, downgrade or stay the same. Like when a package is removed, a slotted version is removed or keywords available to eix dictate that cannot compute. |
|
| Back to top |
|
|
Massimo B.
Veteran
Joined: 09 Feb 2005
Posts: 1820
Location: PB, Germany
|
| Posted: Thu Dec 12, 2024 9:58 am Post subject: |
|
|
Weird, today the issue is gone: | Code: | eix microsoft-edge-dev |head -n1
[U] www-client/microsoft-edge-dev |
The package was not removed, maybe some version was leading to the ? and was updated now in Portage. Don't know.
_________________
HP ZBook Power 15.6" G8 i7-11800H|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
