Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39942 - [bashdb] fails because bash is too new
Attached to Project:
Community Packages
Opened by Roman Neuhauser (roman-neuhauser) - Friday, 18 April 2014, 15:47 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 23 April 2014, 16:45 GMT
Opened by Roman Neuhauser (roman-neuhauser) - Friday, 18 April 2014, 15:47 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 23 April 2014, 16:45 GMT
|
Detailsthere's no newer version of bashdb AFAICT. is it still useful, given that our bash has moved on? or maybe the configure is just conservative, and it would actually work with 4.3?
checking for bash... /usr/bin/bash configure: WARNING: You have Bash GNU bash, version 4.3.0(1)-release (x86_64-unknown-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. installed. configure: error: This package is only known to work with Bash 4.1 or 4.2. ==> ERROR: A failure occurred in build(). Aborting... |
This task depends upon