| View previous topic :: View next topic |
| Author |
Message |
Anard
Apprentice
Joined: 01 Oct 2020
Posts: 236
|
 Posted: Sat Mar 30, 2024 7:22 am Post subject: Downgrade trouble after xz mask |
 |
|
[Moderator note: this post, and the first 3 replies, were originally attached to the topic The xz package has been backdoored. This is a more general Portage question due to a mask, not related to the backdoor problem as such. Therefore, I split it off to reduce clutter in the backdoor thread. -Hu]
Hi.
I just saw that portage can't perform update @world as >xz-utils-5.4.6 is masked.
But I can't downgrade. Could you help me please ?
| Code: | # emerge -a1 =app-arch/xz-utils-5.4.2 --backtrack=30
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 21.05 s (backtrack: 3/30).
[ebuild UD ] app-arch/xz-utils-5.4.2 [5.4.6-r1] ABI_X86="-32*"
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
app-arch/xz-utils:0
(app-arch/xz-utils-5.4.2:0/0::gentoo, ebuild scheduled for merge) USE="extra-filters nls -doc -pgo -static-libs -verify-sig" ABI_X86="(64) -32 (-x32)" pulled in by
=app-arch/xz-utils-5.4.2 (Argument)
(app-arch/xz-utils-5.4.6-r1:0/0::gentoo, installed) USE="extra-filters nls -doc -pgo -static-libs -verify-sig" ABI_X86="32 (64) (-x32)" pulled in by
>=app-arch/xz-utils-5.0.5-r1:0/0=[abi_x86_32(-),abi_x86_64(-)] required by (dev-libs/libxml2-2.12.5:2/2::gentoo, installed) USE="ftp icu lzma python readline -debug -examples -static-libs -test" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_11 -python3_10 -python3_12"
>=app-arch/xz-utils-5.0.5-r1:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] required by (dev-libs/libxml2-2.12.5:2/2::gentoo, installed) USE="ftp icu lzma python readline -debug -examples -static-libs -test" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_11 -python3_10 -python3_12" |
Isn't 5.4.2 >= 5.0.5-r1 ? I don't understand what is blocking downgrade...
Thanks
[EDIT]
OK
Seems that USE "dev-libs/libxml2 -lzma" did the trick but I don't understand why...
_________________
"iMack" : GA-H97M-D3H, Intel i7 4790, 16Go DDR3, Intel HD4600, 2x SSD 256Go, HDD 500Go+2To / Clover - macOS Mojave / Gentoo-Xfce
"Portable" : HP 350G3, HDD 500Go / rEFInd - Xubuntu 20.04 / Windows 10 |
|
| Back to top |
|
 |
mani001
Guru
Joined: 04 Dec 2004
Posts: 486
Location: Oleiros
|
| Posted: Sat Mar 30, 2024 1:36 pm Post subject: |
|
|
Anard, I'm having the same problem but just "-lzma"ing dev-libs/libxml2 doesn't do the trick for me (and I don't know if I want to/should mark -lzma globally). Also, I'm to puzzled by the blocking (apparently, nothing requires xz-utils>5.0.5  |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1898
|
| Posted: Sat Mar 30, 2024 2:01 pm Post subject: |
|
|
| Anard wrote: | | Code: | # emerge -a1 =app-arch/xz-utils-5.4.2 --backtrack=30
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 21.05 s (backtrack: 3/30).
[ebuild UD ] app-arch/xz-utils-5.4.2 [5.4.6-r1] ABI_X86="-32*"
|
Isn't 5.4.2 >= 5.0.5-r1 ? I don't understand what is blocking downgrade... |
You have a version restricted entry in package.use. Notice the -32* in the output. the * means changed.
IMHO, package.use entries should not be version restricted unless there's a good reason. Unfortunately, that's what autounmask does without input. |
|
| Back to top |
|
|
prometeh
n00b
Joined: 30 Mar 2024
Posts: 1
|
| Posted: Sat Mar 30, 2024 2:18 pm Post subject: |
|
|
mani001, take a look at all the packages that show in the conflict while trying to downgrade, if they are using a lzma, you have to omit it from the builds of those packages. I needed to add "-lzma" to not only "dev-libs/libxml2" but also to "dev-libs/elfutils", "sys-libs/libunwind" and "media-libs/tiff".
I can also confirm that after downgrading, you can add "lzma" back to the packages. Furthermore, I'm just assuming it's just an order issue during compiling/building packages, but I'm very newbie so take it with a grain of salt  .
EDIT: you might also double-check the "package.use" file/directory for commenting out ">=app-arch/xz-utils-5.6.1 abi_x86_32" as it might have been added during latest "dispatch-conf" command. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22581
|
| Posted: Sat Mar 30, 2024 2:59 pm Post subject: |
|
|
| Anard wrote: | | Code: | | >=app-arch/xz-utils-5.0.5-r1:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] required by (dev-libs/libxml2-2.12.5:2/2::gentoo, installed) USE="ftp icu lzma python readline -debug -examples -static-libs -test" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python3_11 -python3_10 -python3_12" |
[EDIT]
OK
Seems that USE "dev-libs/libxml2 -lzma" did the trick but I don't understand why... |
Your change probably caused dev-libs/libxml2 not to RDEPEND on any version of app-arch/xz-utils in any configuration, thus making the unacceptable USE flags irrelevant. The advice from the posters above me looks sound. If you still need help, show the output of grep -r -e xz-utils -e libxml2 /etc/portage/package.use.
| mani001 wrote: | | Anard, I'm having the same problem but just "-lzma"ing dev-libs/libxml2 doesn't do the trick for me (and I don't know if I want to/should mark -lzma globally). Also, I'm to puzzled by the blocking (apparently, nothing requires xz-utils>5.0.5 |
If the described change does not work for you, then you do not have exactly the same problem. Per Guidelines item #4, please provide us the command(s) you ran and their full output. |
|
| Back to top |
|
|
mani001
Guru
Joined: 04 Dec 2004
Posts: 486
Location: Oleiros
|
| Posted: Sat Mar 30, 2024 3:50 pm Post subject: |
|
|
I ended up globally disabling lzma through ufed, and nothing broke, so s'all good  Actually, I did because in another newer (gentoo-based) computer it's not even on by default.
Thanks for the tips, anyway!! |
|
| Back to top |
|
|
eeckwrk99
Apprentice
Joined: 14 Mar 2021
Posts: 225
Location: Gentoo forums
|
| Posted: Sat Mar 30, 2024 4:13 pm Post subject: |
|
|
Edit: An even simpler solution on another machine of mine:
| Code: | | sudo emerge -1 app-arch/xz-utils dev-libs/libxml2 sys-apps/systemd |
-----
What worked for me to solve the conflict, based on Portage output:
1. Remove the following from /etc/portage/package.use (was added via dispatch-conf recently)
| Code: | # required by sys-apps/systemd-255.3-r1::gentoo[lzma]
# required by sys-kernel/dracut-060_pre20240104-r4::gentoo
# required by @selected
# required by @world (argument)
>=app-arch/xz-utils-5.4.6-r1 abi_x86_32 |
2. Add
| Code: | dev-libs/libxml2 -lzma
sys-apps/systemd -lzma |
to /etc/portage/package.use
3. Re-compile dev-libs/libxml2 and sys-apps/systemd without lzma USE flag:
| Code: | | sudo emerge -1 dev-libs/libxml2 sys-apps/systemd |
4. After running | Code: | | sudo emerge -1 app-arch/xz-utils |
, dispatch-conf wanted to add
| Code: | # required by sys-apps/systemd-255.3-r1::gentoo[lzma]
# required by sys-apps/systemd (argument)
>=app-arch/xz-utils-5.4.2 abi_x86_32 |
to /etc/portage/package.use so I accepted the change and run the command again, app-arch/xz-utils was then correctly downgraded to 5.4.2.
5. Undo step 2 and redo step 3 so that both dev-libs/libxml2 sys-apps/systemd are compiled with lzma USE flag again. |
|
| Back to top |
|
|
Eggplants
n00b
Joined: 22 Oct 2011
Posts: 20
|
| Posted: Sun Mar 31, 2024 6:04 pm Post subject: |
|
|
| eeckwrk99 wrote: | What worked for me to solve the conflict, based on Portage output:
1. Remove the following from /etc/portage/package.use (was added via dispatch-conf recently)
| Code: | # required by sys-apps/systemd-255.3-r1::gentoo[lzma]
# required by sys-kernel/dracut-060_pre20240104-r4::gentoo
# required by @selected
# required by @world (argument)
>=app-arch/xz-utils-5.4.6-r1 abi_x86_32 |
|
I had to replace this last line with:
| Code: |
app-arch/xz-utils abi_x86_32
|
rather than removing it.
The remaining steps work, except since I don't use systemd I didn't re-emerge that. |
|
| 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
