[Assist] signature problems with latest updates...help/guidance please.

Franco Masotti franco.masotti at student.unife.it
Thu Apr 27 23:15:53 BST 2017


On Fri, Apr 28, 2017 at 12:00:03AM +0200, Ben wrote:
> Hi All,
> 
> tl;dr - I saw boatload of updates on 24th April; checked the public Dev
> mailing list here; saw disarray, with some hackers leaving, others
> joining.. I decided to give myself some time to read through those
> emails, and decide what to do
> 
> 
> So, I'm a recent parabola user; it's been 3 months appx.
> 
> Tuesday's update surprized me by its size; hence my checking mailing
> list in case
> 
> fyi: I do run pacman -Syu, at every boot up before getting to work
> 
> Anyways, I wait until this evening, taking time to read through some of
> the recent threads.. And now, this evening, after long day, I decided
> that I could & should go ahead with updating.
> 
> 1. linux-libre was causing issues, due to megver83 signing issue.
> 
> 2. I remember mailing list thread, except that being tired, I ran
> `pacman -S parabola-keyring` first, and then `pacman-key --refresh-keys`
> 
>     + pacman -Syu fails
> 
> 3. I check mailing list, and see on homepage parabola.nu, it should have
> been the other way around...
> 
> 4. I remember libreboot install doc for parabola mentionning a way to
> resolve issues with signatures
> 
>    + pacman-key –populate parabola
>    + pacman-key –refresh-keys
>    + pacman -Sy parabola-keyring
> 
> 5. sort of looks like progress & regression; linux-libre package is no
> longer complained about; but `your-freedom`
> and `pacman` itself get complaints...
> 
> 6. that's when I should have stopped and reached out for help
> 
> 7. but for some stupid (educational..? {I will be remembering this})
> reason, I decide I could join the mailing list tomorrow, and in the
> meantime quickly update the other packages.. I test with `pacman -S
> git`, works fine, and then..
> 
> 8. I run a first biggish bunch:
> 
>     pacman -S `adwaita-icon-theme apache apr apr-util at-spi2-atk
> at-spi2-core atk atkmm baobab ca-certificates-mozilla cairomm cheese
> clutter clutter-gst cogl colord coreutils curl dbus dconf dconf-editor
> ekiga empathy eog evince evolution-data-server exempi folks freerdp
> fuse-common gcr gdk-pixbuf2 gdm gedit gedit-plugins geoclue2
> geocode-glib gjs glib-networking glib2 glibmm gmime`
> 
> 9. updates fine; but when doing next bunch, `pacman -S` fails (At least
> it the damaged stopped there), it errors:
> 
>     `pacman: error while loading shared libraries: libssl.so.1.1: cannot
> open shared object file: No such file or directory`
> 
> 
> 
> Any kind soul(s) can help me? Or point me in right direction..
> 
> I saw on Arch forum, an old 2010 post. It mentions symlinking libssl, so
> as to temporarily get pacman back up & running, and thus be able to run
> `pacman -Syu`... but I'm tired, need sleep, and I know I have yet to
> resolve the darn GPG signature issue...
> 
> Thanks
> 
> Ben
> 
> 
> _______________________________________________
> Assist mailing list
> Assist at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/assist

I had the problem also but I was able to solve it.
Here's what happened to me:

0. Followed the news on the parabola home page.
   Didn't work

1. Tried the same thing you did:
>    + pacman-key –populate parabola
>    + pacman-key –refresh-keys
>    + pacman -Sy parabola-keyring
   Didn't work

2. Disabled signature in pacman.conf

3. 
>    + pacman-key –populate parabola
>    + pacman-key –refresh-keys
>    + pacman -Sy parabola-keyring
    Didn't work

4. Went to the pacman arch wiki article or something similar and found this:
   sudo rm -rf /etc/pacman.d/gnupg (this should remove all the keys -- really --)

5. Then the usual
>    + pacman-key –populate archlinux
>    + pacman-key –populate parabola
>    + pacman-key –init
>    + pacman -Sy parabola-keyring

6. Reenable signature in pacman.conf

7. pacman -Syyu

-- 
Franco Masotti
Co-author of: <https://linuxdifficile.wordpress.com/>
Dev homepage: <https://github.com/frnmst>
Tox ID (voip): 9D855839E4BB0ADBF4F49063BF2ABC1479A7728011F20B563EA104B2EE10FF19DC8C255D8F3D
My public key fingerprint: F13C 27D7 EDF0 4F7C 0A9F  1244 9A11 29F0 4019 6B95
Get my public key like this: $ gpg --keyserver pgp.mit.edu --recv-keys 40196B95
Use Parabola GNU/Linux-libre: <https://www.parabola.nu>
Use Replicant ROM: <http://www.replicant.us/>
Use GNUpot: <https://github.com/frnmst/gnupot>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/assist/attachments/20170428/632e972b/attachment.bin>


More information about the Assist mailing list