Bug #3274
closed
Unbound 1.4.21_1 install fails
100%
Description
According to control files "pkg_config.8.xml" and "pkg_config.8.xml.amd64" the package version of Unbound has been updated to 1.4.21_1, but the version numbers in the dependency URLs (in two places) do not reflect this change. On "files.pfsense.org", however, there are "unbound-1.4.21_1.tbz", "unbound-1.4.21_1-i386.pbi" and "unbound-1.4.21_1-amd64.pbi" available since Oct 7, 2013, already.
I would be glad if this could be fixed ASAP because due to this breakage I got stuck now with reinstalling one of our appliances. There does not seem to be a possibility to select a different/older version as a workaround. Or at least it is not obvious to me.
Files
Updated by Justin Irwin over 11 years ago
I am able to install 1.4.21_1 but the Unbound binary is still 1.4.20.
Updated by Uwe Doering over 11 years ago
- File install.txt install.txt added
- File files.txt files.txt added
I attached two files that show what I mean. In the install log you can see that pfSense 2.0.2-RELEASE-amd64, installed yesterday from scratch shortly before I went on to install Unbound, tries to download "unbound-1.4.21.tbz", which is not on "files.pfsense.org", as you can see in the other attachment, the relevant excerpt from the file index.
Obviously, if you can install it and I cannot, and in your case it is even the previous version of the binary, there must be some difference in the meta data we use which controls what to do during the install procedure. But unfortunately I have too little insight into pfSense's package manager internals to find out what it is.
Updated by Warren Baker over 11 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:3c7e7ebe4eeeeca998bb7b323322eb70ccd4f281.
Updated by Warren Baker over 11 years ago
Applied in changeset commit:c5abc3905311d69e442989712cceb391719f6deb.
Updated by Uwe Doering over 11 years ago
Warren, thanks a lot for your quick reaction! Your second stab at fixing it worked for me, on both of my appliances by now. The bug ticket can be closed in my opinion.
Updated by Warren Baker over 11 years ago
- Status changed from Feedback to Closed