New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3819 - openwrt-keyring 2021-02-20-49283916-2 update conflicts with base-files #8818
Comments
gyogyi: Same issue. openwrt-keyring - 2019-07-25-8080ef34-1 - 2021-02-20-49283916-2
|
pabloalcantara: I fixed forcing the update |
brianjmurrell: @pablo: You worked-around the issue, you didn't fix it. :-) The issue still exists for folks who don't want to force overwrites and break installed package integrity. |
holishing: Version 19.07.7 also has the same problem |
bjonglez: This looks like a bug / omission, but what is the use-case here? Are you really upgrading all packages on a production router on a regular basis? |
brianjmurrell:
Yes. Why wouldn't I? Building a new firmware for each and every router multiplied by each and every package update and then taking the time to and outage to reboot into the new firmware on all of those routers is simply not practical. Packages should be upgradable, and with few exceptions, without a reboot even. This is not new technology. |
yu210148: Hi All, I've run into this too on version 19.07.6. Other than --force-overwrite which some above have suggested is not a great thing to do what are some other options? I'm sorry I have nothing more useful to add. |
gyogyi: My workaround. Rename or delete /etc/opkg/keys/f94b9dd6febac963 Download the openwrt-keyring package. Install the package. Check the updates. Good for now. |
rathann: Confirmed on 19.07.7 with: |
ddnexus: Same on 19.07.7 here too. And the workaround does not work. "Segmentation fault" if you do it from the terminal or:
Collected errors:
* opkg_install_pkg: Failed to verify the signature of /var/opkg-lists/openwrt_base.
* opkg_install_cmd: Cannot install package openwrt-keyring.
if you try to install it from LuCI after renaming the key as indicated.
What are the drawbacks if we don't update the package? |
elaugier: Hello Same issue:
on OpenWrt 19.07.4 r11208-ce6496d796 / LuCI openwrt-19.07 branch git-21.189.23240-7b931da |
gcb:
1,2c1,2 < untrusted comment: Public usign key for 19.07 release builds < RWT5S53W/rrJY9BiIod3JF04AZ/eU1xDpVOb+rjZzAQBEcoETGx8BXEK |
nereocystis: I suggest a small variation on the work around to make sure that correct version of package is downloaded mv /etc/opkg/keys/f94b9dd6febac963 /etc/opkg/keys/f94b9dd6febac963-bad |
OpenWrt 19.07 release is EOL, try to reproduce the issue with latest supported release and feel free to ask for issue reopening if the problem is still present, thanks. |
brianjmurrell:
# opkg upgrade openwrt-keyring
Upgrading openwrt-keyring on root from 2019-07-25-8080ef34-1 to 2021-02-20-49283916-2...
Collected errors:
check_data_file_clashes: Package openwrt-keyring wants to install file /etc/opkg/keys/f94b9dd6febac963
But that file is already provided by package * base-files
Downloading http://downloads.openwrt.org/releases/19.07.7/packages/mips_24kc/base/openwrt-keyring_2021-02-20-49283916-2_mips_24kc.ipk
The text was updated successfully, but these errors were encountered: