Description of problem: Other shells in Fedora have moved their canonical location to /usr/bin/ to reflect UsrMove, but dash is still at /bin/dash. This causes problems in Fedora 29 because brp-mangle-shebangs now hits "#!/bin/dash" when building RPMs with shebang dependencies, converting it to #!/usr/bin/dash, which DNF can't find. BZ #1541318 Version-Release number of selected component (if applicable): dash-0.5.10.2-1.fc29 How reproducible: Always Steps to Reproduce: See: https://bugzilla.redhat.com/show_bug.cgi?id=1541318#c51 1. Build RPM with a source script using /bin/dash 2. brp-mangle-shebangs mangles shebang in /usr/bin/testdash.sh from /bin/dash to #!/usr/bin/dash 3. Attempt to dnf localinstall the RPM Actual results: Error: Problem: conflicting requests - nothing provides /usr/bin/dash needed by testdash-1-1.fc29.x86_64 Expected results: Smooth install Additional info: Most altshells in RHEL7 are still in /bin/, so this might only be a Fedora 29+ thing in practice. Have not checked RHEL8. Scriptlet for /etc/shells adjustment will probably need to have both locations.
To clarify: The change to brp-mangle-shebangs was made in Fedora 29; Fedora 28 is not affected.
This is still present in Fedora 30. I'm setting this to rawhide since I presume it must be fixed there and then applied to the supported distros. The only workaround is to %define __brp_mangle_shebangs %{nil}, which is not ideal.
Bumping. Can this please be fixed prior to the F31 branch at least?
Huzaifa, are you responsive?
(In reply to Miro Hrončok from comment #4) > Huzaifa, are you responsive? Yes, let me see what i can do.
FEDORA-2019-c05e4425d1 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c05e4425d1
dash-0.5.10.2-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c05e4425d1
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
One issue I've noted is that any packages that previously had depended on "/bin/dash" as a requirement now fail. An F30 RPM built for the previous package release of "dash" without the rewrite ends up with "/bin/dash" as a dependency. The new dash RPM doesn't provide this, so installing my previous package keeps forcing DNF to downgrade the fedora-testing 'dash' package back to the one in the production repo. I suppose this is yet another impossible-to-avoid annoyance of UsrMove to begin with, but if there were any way to cope with this by now in RPM that would be helpful here so that this doesn't have to be timed with dependent packages being rebuilt.
Add this to dash: Provides: /bin/dash
Can this be added in prior to release of this update?
yes
Not to prod, but now that we're in F31 Beta can this be added in? This affects upgrades from F29 and F30 for anything previously dependent on the unmangled path through the workaround above. F29: Problem 2: package xymon-client-4.3.30-1.fc29.x86_64 requires /bin/dash, but none of the providers can be installed - dash-0.5.10.2-1.fc29.x86_64 does not belong to a distupgrade repository F30: Problem: package xymon-client-4.4-0.0.0.fc30.x86_64 requires /bin/dash, but none of the providers can be installed - dash-0.5.10.2-2.fc30.x86_64 does not belong to a distupgrade repository
(In reply to Miro Hrončok from comment #11) > Add this to dash: > > Provides: /bin/dash Any update? Would still like this to be corrected back to F29 before it goes EOL.
This problem still exists. Error: Problem: conflicting requests - nothing provides /bin/dash needed by xxxxx.fc31.x86_64
Huzaifa, can you please respond to comments both here and in the Bodhi bug? Thank you.
FEDORA-2020-f57290bd78 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f57290bd78
FEDORA-2020-e13b2bb631 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e13b2bb631
FEDORA-2020-f13a2ad8be has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f13a2ad8be
Let me know if these work for you!
FEDORA-2020-f13a2ad8be has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f13a2ad8be` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f13a2ad8be See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f57290bd78 has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f57290bd78` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f57290bd78 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-e13b2bb631 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e13b2bb631` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e13b2bb631 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f13a2ad8be has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-e13b2bb631 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.