Extend signkey by more then one year - openSUSE Build Service - openSUSE Mailing Lists

newer
Add Fedora Linux 34 to openSUSE...

Extend signkey by more then one year

older
How to configure package screenshot

Ralf Becker

6 Apr 2021 6 Apr '21

11:19

The PGP key of our project "server:eGroupWare" expired recently and the only way I found is to extend it by one year with: osc signkey --extend server:eGroupWare But that would mean every user of that repo has to reimport the key and that every year. There must be a more convenient way then to bug all users constantly every year. Am I missing something? Regards Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

Reply

Sign in to reply online Use email software

Show replies by date

Bernhard M. Wiedemann

8 Apr 8 Apr

13:08

On 06/04/2021 13.19, Ralf Becker wrote:

But that would mean every user of that repo has to reimport the key and that every year.

There must be a more convenient way then to bug all users constantly every year.

I think, it will just auto-imported by zypper because only the expiry time changed, but the key remained the same.

Reply

Sign in to reply online Use email software

Oliver Marquardt

16:05

New subject: including EPEL packages in CentOS spec files

Hi OBS list, I am currently trying to bundle our package for CentOS 8. However, we require the netCDF library which is now included in the EPEL repo in CentOS and not the basic one. I was wondering whether there is an option to activate the respective repo prior to build requests in the spec file. %pre environment seems not to help as, if I understand correctly, dependencies are checked before any installation of the repo could be done in the prerequisites, or? Does anyone maybe know an example where such a problem is solved within OBS (or at least some cross-distro rpm)? I am grateful for any hints! Cheers, Oliver

Reply

Sign in to reply online Use email software

Neal Gompa

16:08

New subject: including EPEL packages in CentOS spec files

On Thu, Apr 8, 2021 at 12:05 PM Oliver Marquardt wrote:

Hi OBS list, I am currently trying to bundle our package for CentOS 8. However, we require the netCDF library which is now included in the EPEL repo in CentOS and not the basic one. I was wondering whether there is an option to activate the respective repo prior to build requests in the spec file. %pre environment seems not to help as, if I understand correctly, dependencies are checked before any installation of the repo could be done in the prerequisites, or? Does anyone maybe know an example where such a problem is solved within OBS (or at least some cross-distro rpm)? I am grateful for any hints!

You can enable EPEL in your OBS project. In your project meta, just set it up like so: <repository name="CentOS_8"> <path project="Fedora:EPEL:8" repository="standard"/> <path project="CentOS:CentOS-8:Stream" repository="standard"/> <arch>x86_64</arch> </repository> -- 真実はいつも一つ！/ Always, there's only one truth!

Reply

Sign in to reply online Use email software

Oliver Marquardt

9 Apr 9 Apr

07:06

New subject: including EPEL packages in CentOS spec files

Hi Neal and Sebastian, thanks for your hints. Adding the Fedora EPEL to the project meta did the trick. Now crawling through all other dependencies, but that's something I should be able to solve ;) Thanks a lot again for your help! Cheers, Oliver On 4/8/21 6:08 PM, Neal Gompa wrote:

On Thu, Apr 8, 2021 at 12:05 PM Oliver Marquardt wrote:

...
Hi OBS list, I am currently trying to bundle our package for CentOS 8. However, we require the netCDF library which is now included in the EPEL repo in CentOS and not the basic one. I was wondering whether there is an option to activate the respective repo prior to build requests in the spec file. %pre environment seems not to help as, if I understand correctly, dependencies are checked before any installation of the repo could be done in the prerequisites, or? Does anyone maybe know an example where such a problem is solved within OBS (or at least some cross-distro rpm)? I am grateful for any hints!

You can enable EPEL in your OBS project. In your project meta, just set it up like so:

<repository name="CentOS_8"> <path project="Fedora:EPEL:8" repository="standard"/> <path project="CentOS:CentOS-8:Stream" repository="standard"/> <arch>x86_64</arch> </repository>

-- Dr. Oliver Marquardt Weierstraß-Institut für angewandte Analysis und Stochastik 0049 30 20372 474

Reply

Sign in to reply online Use email software

Sebix

8 Apr 8 Apr

19:33

New subject: including EPEL packages in CentOS spec files

Hi, Additionally to what Neal said you can also have a look at how I build for CentOS 7 and 8, with EPEL and CentOS Stream and CentOS modules here: https://build.opensuse.org/project/show/home:sebix:intelmq You'll need to pay special attention to the order of repositories for CentOS, maybe also do some tweaking in the Project Config (prjconf). (I had *a lot* of fun with CentOS and still have) Sebastian On 4/8/21 6:05 PM, Oliver Marquardt wrote:

Hi OBS list, I am currently trying to bundle our package for CentOS 8. However, we require the netCDF library which is now included in the EPEL repo in CentOS and not the basic one. I was wondering whether there is an option to activate the respective repo prior to build requests in the spec file. %pre environment seems not to help as, if I understand correctly, dependencies are checked before any installation of the repo could be done in the prerequisites, or? Does anyone maybe know an example where such a problem is solved within OBS (or at least some cross-distro rpm)? I am grateful for any hints!

Cheers, Oliver

Reply

Sign in to reply online Use email software

1119

Age (days ago)

1122

Last active (days ago)

Download

5 comments

5 participants

tags

participants (5)

Bernhard M. Wiedemann
Neal Gompa
Oliver Marquardt
Ralf Becker
Sebix