You are not logged in.

#1 2023-10-29 07:45:17

Henkm
Member
From: Dutch living in Malaysia
Registered: 2015-11-11
Posts: 21

[SOLVED] How to resolve atlas-lapack PKGBUILD mess up

The atlas-lapack PKGBUILD contains two version numbers. One for atlas, which is also used as version number for the package and another one for lapack.

The latest uploader has updated the lapack version from 3.10.0 to 3.11.0 as there was a new version and has also updated the atlas version from 3.10.3 to 3.11.0.
The last is an error as 3.10.3 is still the latest stable release (and the latest unstable is 3.11.41.) I can change the atlas version back to 3.10.3 but that would also lower the package number which I guess is undesirable. Is there an accepted way to solve this or should I decouple package version from atlas version?

ETA: as is, the package does not build.

Last edited by Henkm (2023-10-30 08:48:53)

Offline

#2 2023-10-30 07:47:36

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: [SOLVED] How to resolve atlas-lapack PKGBUILD mess up

Fix the PKGBUILD in AUR, it is orphaned.

Offline

#3 2023-10-30 08:32:15

loqs
Member
Registered: 2014-03-06
Posts: 17,417

Re: [SOLVED] How to resolve atlas-lapack PKGBUILD mess up

Henkm wrote:

I can change the atlas version back to 3.10.3 but that would also lower the package number which I guess is undesirable. Is there an accepted way to solve this or should I decouple package version from atlas version?

PKGBUILD#epoch

Offline

#4 2023-10-30 08:48:40

Henkm
Member
From: Dutch living in Malaysia
Registered: 2015-11-11
Posts: 21

Re: [SOLVED] How to resolve atlas-lapack PKGBUILD mess up

loqs wrote:
Henkm wrote:

I can change the atlas version back to 3.10.3 but that would also lower the package number which I guess is undesirable. Is there an accepted way to solve this or should I decouple package version from atlas version?

PKGBUILD#epoch

Thanks. I'll do that tonight.

Offline

Board footer

Powered by FluxBB