Search Criteria
Package Details: mooltipass-udev 2019120501-2
Git Clone URL: | https://aur.archlinux.org/mooltipass-udev.git (read-only, click to copy) |
---|---|
Package Base: | mooltipass-udev |
Description: | Udev rules to connect Mooltipass devices |
Upstream URL: | https://github.com/mooltipass/mooltipass-udev |
Licenses: | |
Submitter: | bobsaintcool |
Maintainer: | bobsaintcool |
Last Packager: | bobsaintcool |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2017-02-11 15:54 |
Last Updated: | 2020-03-31 23:34 |
Latest Comments
1 2 Next › Last »
bobsaintcool commented on 2018-04-24 09:15
I'm now signing stuff with the same key but set another identity back to my main GPG keys[0].
[0] https://pgp.mit.edu/pks/lookup?search=0xF7181B2010660E6F&op=index
frankenstein20 commented on 2018-04-24 08:45
I still get the key error. is the url to your key still valid?
bobsaintcool commented on 2017-06-13 08:25
Hi,
The key has been uploaded into public repository[0], please import it into you GNUPG keyring or opt to not use GPG.
Note that you must not import my key into the distribution keyring.
Thanks.
[0] http://pgp.mit.edu/pks/lookup?search=0xDCD99CC69BFC6A5C&op=index
enricostn commented on 2017-06-12 11:24
[code]
==> Verifying source file signatures with gpg...
mooltipass-udev-2017021102.tar.gz ... FAILED (unknown public key DCD99CC69BFC6A5C)
==> ERROR: One or more PGP signatures could not be verified!
[/code]
How can I solve this problem? Thanks!
bobsaintcool commented on 2017-06-07 11:33
Thank for the feedback.
I've change a bit my workflow, hope I won't introduce such bug again.
visibilityspots commented on 2017-06-07 08:56
The integrity check is failing, please have a look at https://wiki.archlinux.org/index.php/PKGBUILD#sha256sums to get it fixed in the PKGBUILD file.
the correct sha256 checksum is: 2c79f2e0487ccf564c3edc548393080b6a5a5cfcf997d213ff5d89ce969ffd59
$ sha256sum mooltipass-udev-2017021102.tar.gz.asc
2c79f2e0487ccf564c3edc548393080b6a5a5cfcf997d213ff5d89ce969ffd59 mooltipass-udev-2017021102.tar.gz.asc
PKGBUILD:
sha256sums=('428c8284fd9bd52a0e0b38de2b3262158090038051b16210e9ebba2bc0859f8a'
'2c79f2e0487ccf564c3edc548393080b6a5a5cfcf997d213ff5d89ce969ffd59')
bobsaintcool commented on 2017-05-08 14:13
Oops, got it for the next time.
NicoHood commented on 2017-05-08 14:04
You do not need to push the pgkrel if you only edit the PKGBUILDs comment. People dont need to rebuild the whole software for that.
bobsaintcool commented on 2017-05-08 14:03
@plague-doctor my could is now uploaded on general PGP key server and could be for example grab here[0]
[0] https://pgp.mit.edu/pks/lookup?op=vindex&search=0xF7181B2010660E6F
plague-doctor commented on 2017-05-04 22:41
Where can we find your keys then?