[Spce-user] Upgrade Failure to 3.8.2
Matthias Hohl
matthias.hohl at telematica.at
Fri Jun 19 03:10:08 EDT 2015
I fixed it with:
apt-get install ngcp-keyring
now it works.
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von
Matthias Hohl
Gesendet: Freitag, 19. Juni 2015 01:49
An: Alex Lutay; Spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Upgrade Failure to 3.8.2
Just this?
apt-get update && apt-get upgrade && \
ngcp-update-db-schema && ngcp-update-cfg-schema && \
ngcpcfg apply
Von meinem iPhone gesendet
Am 19.06.2015 um 01:42 schrieb Matthias Hohl <matthias.hohl at telematica.at
<mailto:matthias.hohl at telematica.at> >:
It is mr3.7.2
What shoud i do now..?
Von meinem iPhone gesendet
Am 18.06.2015 um 17:16 schrieb Alex Lutay <alutay at sipwise.com
<mailto:alutay at sipwise.com> >:
Dear Matthias,
Can you please share the release you are upgrading from?
2.8/mr3.7.*/mr3.8.1?
Other releases are not supported for upgrade to mr3.8.2
P.S. the error points you to missed key, as you noticed in release notes
https://www.sipwise.org/news/announcements/sipprovider-mr3-8-2-released/
Move Sipwise Debian repository from 1024bit GPG key to 4096bit key
we switched NGCP repository to stronger GPG keys.
mr3.8.1 already has taht key, so you probably update from 2.8,
please check the warning here if so:
https://www.sipwise.org/doc/mr3.8.2/spce/ar01s03.html#_upgrade_from_previous_2_8_lts_version_to_mr3_8_2
WARNING: be sure you are using the latest 2.8 LTS version before upgrading
to
mr3.8.2 LTS version. mr3.8.2 LTS version uses new repository GPG key
which should be installed in 2.8 LTS version before further upgrade to
mr3.8.2 LTS version. For upgrading the 2.8 LTS version to the latest 2.8
packages version, execute the following commands as root:
apt-get update && apt-get upgrade && \
ngcp-update-db-schema && ngcp-update-cfg-schema && \
ngcpcfg apply
Thank you!
On 06/18/2015 03:25 PM, Matthias Hohl wrote:
I tried to prepare the upgrade and I got this error if I do "apt-get
update"
W: GPG error: http://deb.sipwise.com wheezy Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 773236EFF411xxxx
What is going wrong?
--
Alexander Lutay
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150619/faa75e1c/attachment-0001.html>
More information about the Spce-user
mailing list