Bug 27970 - bashdb - bash debugger missing in mga8 repositories, existed in mga7
Summary: bashdb - bash debugger missing in mga8 repositories, existed in mga7
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-29 08:48 CET by Per Nelvig
Modified: 2020-12-29 18:00 CET (History)
1 user (show)

See Also:
Source RPM: bashdb-4.4.1.0.1-9.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Per Nelvig 2020-12-29 08:48:21 CET
Description of problem:
Found out that bashdb is missing in mageia 8 repos.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Dave Hodgins 2020-12-29 09:23:19 CET
No mention of it in dev or sysadmin mailing lists for 2020.

Found http://pkgsubmit.mageia.org/autobuild/results.php?run=2018-01-10&include_success=true
which shows ...
bashdb-4.3.0.9-7.mga7.src.rpm	 Removed	 missing_dep

The last build history shows ...
A requested package cannot be installed:
bashdb-5.0.1.1.2-2.mga8.src (due to unsatisfied bash[< 5.1])
While some packages may have been installed, there were failures.
A requested package cannot be installed:
bashdb-5.0.1.1.2-2.mga8.src (due to unsatisfied bash[< 5.1])
I: [iurt_root_command] ERROR: urpmi

https://sourceforge.net/projects/bashdb/files/bashdb/5.0-1.1.2/ is the latest
source, so it looks like the package is no longer being maintained or compatible
with the current version of bash.

Unmaintained packages that fail to build are being dropped from cauldron in
preparation for version freeze which will be soon.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX
CC: (none) => davidwhodgins

Comment 2 David Walser 2020-12-29 18:00:11 CET
Per Nelvig, if you find later that upstream has released a version compatible with Bash 5.1, please re-open this bug and we can re-introduce the bashdb package.  Until that happens, there is nothing that we can do.

Note You need to log in before you can comment on or make changes to this bug.