Re: providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
To answer my own question, by the trial-and-error method, it seems that the current default needs to be taken out from the conf file. On Sunday, February 26, 2023 at 02:48:52 PM CST, Globe Trotter via devel wrote: Sorry, I had a question on the xserver_arguments in the slim.conf file.

Re: providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
Sorry, I had a question on the xserver_arguments in the slim.conf file. The old (1.3.6) file had xserver_arguments commented out, but the new (1.4.0) file replaces it with xserver_arguments   -nolisten tcp -deferglyphs 16 The default zserver is still the same: default_xserver /usr/bin/X

Re: providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
Sorry, forgot to add: I will ask the slim-fork maintainer if he will sign the release tarballs. On Sunday, February 26, 2023 at 10:51:14 AM CST, Globe Trotter via devel wrote: Todd, I only became aware of this fork yesterday, and have packaged it and put it on bugzilla:

Re: providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
Todd, I only became aware of this fork yesterday, and have packaged it and put it on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2173236 Hopefully, someone who can will review and approve it. Someone did review it, but is not eligible to approve. Thanks! On Sunday, February 26,

Re: providing gpg verification for a package without signature

2023-02-26 Thread Todd Zullinger
Hi, Globe Trotter via devel wrote: > I have been trying to package slim again. The package does not come with a > signature or a gpg key. > > From > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verification > I don't see an option of what to do if there is no

Re: providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
Thanks, so it appears that no GPG verification is needed in this case, then. I thought it was needed for everything. Thanks again for the clarification! On Sunday, February 26, 2023 at 10:29:30 AM CST, Ben Beasley wrote: “Where the upstream project publishes OpenPGP signatures of their

Re: providing gpg verification for a package without signature

2023-02-26 Thread Ben Beasley
“Where the upstream project publishes OpenPGP signatures of their releases, Fedora packages SHOULD verify that signature as part of the RPM build process.” Most upstreams don’t sign their releases this way, so most Fedora packages don’t need to worry about it. If upstream did provide

providing gpg verification for a package without signature

2023-02-26 Thread Globe Trotter via devel
Hello, I have been trying to package slim again. The package does not come with a signature or a gpg key. From https://docs.fedoraproject.org/en-US/packaging-guidelines/#_source_file_verification I don't see an option of what to do if there is no signature provided. Any suggestions or