| View previous topic :: View next topic |
| Author |
Message |
picarica
Apprentice
Joined: 11 Aug 2018
Posts: 285
|
 Posted: Thu Mar 28, 2024 3:52 pm Post subject: how to resolve vague conflicts? |
 |
|
so hello i was merginy @installed and i noticed i had some weird conflicts which i was not sure why was ittt conflicting, it didnt sate what package was pulling the version wanting to be merged it onlyy listed the confclited copy
here is screenshot i iddnt wanted to copy it it would loose the pretty terminal colors |
|
| Back to top |
|
 |
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1539
|
| Posted: Thu Mar 28, 2024 4:15 pm Post subject: Re: how to resolve vague conflicts? |
|
|
It's not a conflict. It can be resolved and portage successfully does so only printing a warning a new version of something is available but something else holds on to the older version. It'll fade away as soon as that other thing gets updated to depend on the newer version.
| picarica wrote: | | so hello i was merginy @installed |
The more important question is what were you trying to achieve with that. This is the first time I heard of @installed and I had to look it up. Interestingly it's as documented as it probably is useful (not at all I guess).
Best Regards,
Georgi |
|
| Back to top |
|
|
picarica
Apprentice
Joined: 11 Aug 2018
Posts: 285
|
| Posted: Thu Mar 28, 2024 5:03 pm Post subject: Re: how to resolve vague conflicts? |
|
|
| logrusx wrote: | It's not a conflict. It can be resolved and portage successfully does so only printing a warning a new version of something is available but something else holds on to the older version. It'll fade away as soon as that other thing gets updated to depend on the newer version.
| picarica wrote: | | so hello i was merginy @installed |
The more important question is what were you trying to achieve with that. This is the first time I heard of @installed and I had to look it up. Interestingly it's as documented as it probably is useful (not at all I guess).
Best Regards,
Georgi |
i just used it beacuse some of my libs were broken somehow
i found out here and so iam recompiling just in case |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1539
|
| Posted: Thu Mar 28, 2024 6:27 pm Post subject: Re: how to resolve vague conflicts? |
|
|
| picarica wrote: | | logrusx wrote: | It's not a conflict. It can be resolved and portage successfully does so only printing a warning a new version of something is available but something else holds on to the older version. It'll fade away as soon as that other thing gets updated to depend on the newer version.
| picarica wrote: | | so hello i was merginy @installed |
The more important question is what were you trying to achieve with that. This is the first time I heard of @installed and I had to look it up. Interestingly it's as documented as it probably is useful (not at all I guess).
Best Regards,
Georgi |
i just used it beacuse some of my libs were broken somehow
i found out here and so iam recompiling just in case |
Nowhere there I see a mention of @installed. How did you come up with ti?
You've been pointed to the correct command in that same thread.
If you want to rebuild reverse dependencies use revdep-rebuild -L <path to library>
If you insist on rebuilding everything emerge --emptytree @wolrd
Best Regards,
Georgi |
|
| Back to top |
|
|
freke
l33t
Joined: 23 Jan 2003
Posts: 977
Location: Somewhere in Denmark
|
| Posted: Fri Mar 29, 2024 12:17 am Post subject: |
|
|
| Code: | ns ~ # cat /usr/share/portage/config/sets/portage.conf
# WARNING: default set configuration, DO NOT CHANGE.
# If you want to change anything redefine the relevant section in
# /etc/portage/sets.conf. Any changes to this file will be lost on the next
# portage update, and configuration errors here might upset portage in
# unexpected ways.
# Not much that could be changed for world, so better leave it alone
[world]
class = portage.sets.base.DummyPackageSet
packages = @profile @selected @system
[profile]
class = portage.sets.ProfilePackageSet.ProfilePackageSet
[selected]
class = portage.sets.files.WorldSelectedSet
[selected-packages]
class = portage.sets.files.WorldSelectedPackagesSet
[selected-sets]
class = portage.sets.files.WorldSelectedSetsSet
# Same as for world, though later portage versions might use a different class
[system]
class = portage.sets.profiles.PackagesSystemSet
# For security there are multiple classes available, but differences are
# rather small (normally there should be no visible difference):
# - AffectedSet: include all GLSAs that cover a vulnerable package
# - NewAffectedSet: include all GLSAs that cover a vulnerable package and
# haven't been applied previously
# - NewGlsaSet: include all GLSAs that haven't been applied
# - SecuritySet: include all GLSAs
[security]
class = portage.sets.security.NewAffectedSet
# A superset of the classic <parameter>world</parameter> target, a set created
# by this class contains SLOT atoms to match all installed packages. Note that
# use of this set makes it impossible for emerge to solve blockers by automatic
# uninstallation of blocked packages.
[installed]
class = portage.sets.dbapi.EverythingSet
# The following treats all files in /etc/portage/sets as a package set called
# '$filename'.
[usersets]
class = portage.sets.files.StaticFileSet
multiset = true
directory = %(PORTAGE_CONFIGROOT)setc/portage/sets
world-candidate = True
# Set to rebuild all packages that need a preserved lib that only remains due
# to FEATURES=preserve-libs
[preserved-rebuild]
class = portage.sets.libs.PreservedLibraryConsumerSet
# Installed ebuilds with "live" property.
[live-rebuild]
class = portage.sets.dbapi.VariableSet
variable = PROPERTIES
includes = live
# Installed ebuilds that inherit from known live eclasses.
[deprecated-live-rebuild]
class = portage.sets.dbapi.VariableSet
variable = INHERITED
includes = bzr cvs darcs git-2 git-r3 golang-vcs mercurial subversion
# Installed packages that own files inside /lib/modules.
[module-rebuild]
class = portage.sets.dbapi.OwnerSet
files = /lib/modules
exclude-files = /usr/src/linux*
# Installed packages that own files inside /usr/lib/xorg/modules,
# excluding the package that owns /usr/bin/Xorg.
[x11-module-rebuild]
class = portage.sets.dbapi.OwnerSet
files = /usr/lib*/xorg/modules
exclude-files = /usr/bin/Xorg
# Binary packages that have a different build time from a currently
# installed package of the exact same version.
[rebuilt-binaries]
class = portage.sets.dbapi.RebuiltBinaries
# Installed packages for which the subslot of the highest visible ebuild
# version is different than the currently installed version.
[changed-subslot]
class = portage.sets.dbapi.SubslotChangedSet
# Installed packages for which the highest visible ebuild
# version is lower than the currently installed version.
[downgrade]
class = portage.sets.dbapi.DowngradeSet
# Installed packages for which there are no visible ebuilds
# corresponding to the same $CATEGORY/$PN:$SLOT.
[unavailable]
class = portage.sets.dbapi.UnavailableSet
# Installed packages for which corresponding binary packages
# are not available.
[unavailable-binaries]
class = portage.sets.dbapi.UnavailableBinaries
# Installed packages for which vdb *DEPEND entries are outdated compared
# to the matching portdb entry.
[changed-deps]
class = portage.sets.dbapi.ChangedDepsSet
# Installed packages for which vdb *DEPEND includes dev-lang/go.
[golang-rebuild]
class = portage.sets.dbapi.VariableSet
variable = BDEPEND
includes = dev-lang/go
# Installed packages for which vdb *DEPEND includes virtual/rust
[rust-rebuild]
class = portage.sets.dbapi.VariableSet
variable = BDEPEND
includes = virtual/rust |
Seems like we have a few different sets I never knew about  |
|
| Back to top |
|
|
wjb
l33t
Joined: 10 Jul 2005
Posts: 609
Location: Fife, Scotland
|
| Posted: Fri Mar 29, 2024 11:31 am Post subject: |
|
|
Another method to get the list of sets...
| Code: | # emerge @neddy
emerge: There are no sets to satisfy 'neddy'. The following sets exist:
changed-deps
changed-subslot
deprecated-live-rebuild
downgrade
golang-rebuild
installed
live-rebuild
module-rebuild
ocaml-rebuild
preserved-rebuild
profile
rebuilt-binaries
rust-rebuild
security
selected
selected-packages
selected-sets
system
unavailable
unavailable-binaries
wjb-core
wjb-dev
world
x11-module-rebuild
|
 |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1660
|
| Posted: Fri Mar 29, 2024 12:31 pm Post subject: |
|
|
| wjb wrote: | Another method to get the list of sets...
| Code: | # emerge @neddy
emerge: There are no sets to satisfy 'neddy'. The following sets exist: |
|
Why trigger an error when you can just emerge --list-sets |
|
| Back to top |
|
|
mkyral
Apprentice
Joined: 06 May 2007
Posts: 185
Location: Czech Republic
|
| Posted: Sat Mar 30, 2024 10:28 am Post subject: |
|
|
It's shorter  |
|
| Back to top |
|
|
|
Portage & Programming
