Hello, is it possible to add that line : > Provides: golang(%{goipath}) = %{version}-%{release} to that spec http://svnweb.mageia.org/packages/updates/7/golang-github-golang-sys/current/SPECS/golang-github-golang-sys.spec?view=markup please ? I guess maintainer is Umeaboy, not sure
Please can you say why you want this done? What is the problem with the package golang-github-golang-sys-devel as it stands? Is this an enhancement or a bug?
CC: (none) => lewyssmithSource RPM: golang-github-golang-sys => golang-github-golang-sys-0-0.22.20181119git95b1ffb.mga7.src.rpm
Well, I admit, my request is quite light! As we can see here: L31 http://svnweb.mageia.org/packages/updates/7/golang-github-10gen-openssl/current/SPECS/golang-github-10gen-openssl.spec?view=markup#l29 > BuildRequires: golang(github.com/spacemonkeygo/spacelog) This is permit with that the syntax: L32 http://svnweb.mageia.org/packages/updates/7/golang-github-spacemonkeygo-spacelog/current/SPECS/golang-github-spacemonkeygo-spacelog.spec?view=markup#l27 > Provides: golang(%{import_path}) = %{version}-%{release} Which is the case of most of golang package. I'm reviewing all golang packages to learn how it is mostly done and I would love to use a unique syntax like: > BuildRequires: golang(github.com/spacemonkeygo/spacelog) whenever it is possible, instead of : > BuildRequires: golang-github-spacemonkeygo-spacelog-devel Or, using only the second syntaxe, but I would be disturb that most of packages give the first syntax. Why I want this done? → Because I'm a little bit psycho-rigid. What is the problem with the package? → It doesn't give the second syntax. Is this an enhancement or a bug? → More an enhancement, as no other package are using this syntax, everything work yet.
Assigning to Pascal for the SRPM. Hope you can see what the reporter is getting at.
Severity: normal => enhancementAssignee: bugsquad => pterjanCC: lewyssmith => (none)
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD