| View previous topic :: View next topic |
| Author |
Message |
guyuming
Apprentice
Joined: 19 Nov 2020
Posts: 250
|
 Posted: Wed Jan 08, 2025 12:24 pm Post subject: failed to install bashdb since pkgcore require bash-5.1 |
 |
|
My recent emerge --sync and upgrade was in 2024//11/14.
And i am currently not able to install bashdb.
Searching in this forum show almost the same issue here in Sept 2024: https://forums.gentoo.org/viewtopic-t-1170855-highlight-bashdb.html
So, anyway i can revert the bash version back so that i can use bashdb?
| Code: | b*>sudo emerge --ask --verbose bashdb
* IMPORTANT: 23 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* Last emerge --sync was 2024年11月14日 星期四 00时10分00秒.
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 14.80 s (backtrack: 0/20).
[ebuild N ] app-shells/bashdb-5.0.1.1.2::gentoo USE="-test" 561 KiB
[blocks B ] >=app-shells/bash-5.1 (">=app-shells/bash-5.1" is soft blocking app-shells/bashdb-5.0.1.1.2)
Total: 1 package (1 new), Size of downloads: 561 KiB
Conflict: 1 block (1 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-shells/bashdb-5.0.1.1.2:0/0::gentoo, ebuild scheduled for merge) pulled in by
bashdb
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages
b*>eix -I bash
[I] app-shells/bash
Available versions:
(2.05b) [P]2.05b_p13
(3.0) [P]3.0_p22
(3.1) [P]3.1_p23
(3.2) [P]3.2_p57
(4.0) [P]4.0_p44
(4.1) [P]4.1_p17
(4.2) [P]4.2_p53
(4.3) [P]4.3_p48-r2
(4.4) [P]4.4_p23-r2
(0) 5.0_p18-r2 5.1_p16-r13 5.2_p26-r6 ~5.2_p26-r8 5.2_p37 **5.3_alpha-r5 **5.3_alpha_p20241015 **5.3_alpha_p20241018 **5.3_alpha_p20241022 **5.3_alpha_p20241026 **5.3_alpha_p20241028 **5.3_alpha_p20241101 **5.3_alpha_p20241102 **5.3_alpha_p20241104 **5.3_alpha_p20241108 **9999*l
{afs bashlogger examples mem-scramble +net nls pgo plugins +readline static verify-sig}
Installed versions: 5.2_p37(01时26分56秒 2024年10月07日)(net nls readline -afs -bashlogger -examples -mem-scramble -pgo -plugins -verify-sig)
Homepage: https://tiswww.case.edu/php/chet/bash/bashtop.html https://git.savannah.gnu.org/cgit/bash.git
Description: The standard GNU Bourne again shell
[I] dev-libs/tree-sitter-bash
Available versions: 0.21.0-r1^t 0.23.1^t ~0.23.2^t {debug python test PYTHON_TARGETS="python3_10 python3_11 python3_12 python3_13"}
Installed versions: 0.23.1^t(20时22分59秒 2024年12月09日)(python -debug -test PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13")
Homepage: https://github.com/tree-sitter/tree-sitter-bash
Description: Bash grammar for Tree-sitter
Found 2 matches
b*>sudo emerge --ask --verbose =app-shells/bash-5.0_p18-r2
* IMPORTANT: 23 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
* Last emerge --sync was 2024年11月14日 星期四 00时10分00秒.
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 86.11 s (backtrack: 3/20).
[ebuild UD ] app-shells/bash-5.0_p18-r2::gentoo [5.2_p37::gentoo] USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins (-pgo%) (-verify-sig%)" 9,950 KiB
Total: 1 package (1 downgrade), Size of downloads: 9,950 KiB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
app-shells/bash:0
(app-shells/bash-5.0_p18-r2:0/0::gentoo, ebuild scheduled for merge) USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins" ABI_X86="(64)" pulled in by
=app-shells/bash-5.0_p18-r2 (Argument)
(app-shells/bash-5.2_p37-1:0/0::gentoo, installed) USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -pgo -plugins -verify-sig" ABI_X86="(64)" pulled in by
>=app-shells/bash-5.1[readline] required by (sys-apps/pkgcore-0.12.28:0/0::gentoo, installed) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 (-python3_13)" |
^^ ^^^ |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22960
|
| Posted: Wed Jan 08, 2025 3:04 pm Post subject: |
|
|
According to the output provided, you cannot have old bash and current pkgcore. You cannot have bashdb and new bash. Therefore, your choices are:- Omit bashdb.
- Depclean pkgcore, use bash-5.0, and use bashdb.
- Downgrade pkgcore to a version that allows bash-5.0, use bash-5.0, and use bashdb.
The oldest pkgcore still visible to me requires bash-5.1, so option 3 requires obtaining an older pkgcore from history. Do you need pkgcore installed? How would you like to proceed? |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2076
|
| Posted: Wed Jan 08, 2025 9:37 pm Post subject: |
|
|
| Honestly, I'm not even sure why that blocker is in the ebuild, and it's terrible UX. If it really can't work with latest stable bash, it should be last-rited, not least as it currently will encourage users to do something horribly dangerous (downgrade bash). |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2076
|
| Posted: Thu Jan 09, 2025 12:28 am Post subject: |
|
|
| sam_ wrote: | | Honestly, I'm not even sure why that blocker is in the ebuild, and it's terrible UX. If it really can't work with latest stable bash, it should be last-rited, not least as it currently will encourage users to do something horribly dangerous (downgrade bash). |
configure aborts on newer versions (or anything not matching a whitelist).
I've reworked things and slotted old bash (we always do that but hadn't done it recently for 5.0/5.1), pushed bashdb-5.0.1.1.2-r1 to accommodate that, and also pushed 5.1_pre20240617. There isn't yet a version that works with bash-5.2. |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 477
Location: Naarm/Melbourne, Australia
|
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 2076
|
| Posted: Thu Jan 09, 2025 1:01 am Post subject: |
|
|
| Not a fork, but rather the original upstream maintainer. bashdb-5.1_pre20240617 is using that. The bash-52 branch doesn't yet work with 5.2 (at least configure rejects it), though. |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 477
Location: Naarm/Melbourne, Australia
|
|
| Back to top |
|
|
guyuming
Apprentice
Joined: 19 Nov 2020
Posts: 250
|
| Posted: Thu Jan 09, 2025 4:40 am Post subject: |
|
|
Thanks all for ur attention!
I just recall that i can still use the set -x option for now. |
|
| Back to top |
|
|
|
Portage & Programming
