#2 golist processing is arch and tag-specific
Closed 2 years ago by qulogic. Opened 2 years ago by nim.

This is the root cause behind
https://pagure.io/go-rpm-macros/issue/1

When asked to list the files to deploy, golist only answers for the current tags (arch and build options)
https://pagure.io/go-rpm-macros/blob/master/f/bin/go-rpm-integration#_386

Being arch-specific is annoying but not a blocker¹

However @jcajka thinks this will also remove installation of files not covered by current build tags. And that is a huge problem because that makes the result unusable, by any consumer, that needs a different tag combination than the one passed by the source code packager.

¹ The migration of Fedora’s go -devel packages to an arch-specific root can be kludged as evidenced by https://copr.fedorainfracloud.org/coprs/nim/go-rpm-macros/builds/ because they are only installed transiently


@nim This is a blocker, devel packages needs to be noarch, i.e. representing the upstream source with possible Fedora patches applied. No file filtering based on arch tag combination.

Metadata Update from @jcajka:
- Assignee reset

2 years ago

Metadata Update from @nim:
- Issue assigned to jcajka

2 years ago

Metadata Update from @jcajka:
- Assignee reset

2 years ago

Metadata Update from @nim:
- Issue tagged with: BUG

2 years ago

Metadata Update from @nim:
- Issue untagged with: BUG

2 years ago

Metadata Update from @nim:
- Issue tagged with: BUG, core

2 years ago

Metadata Update from @qulogic:
- Issue assigned to qulogic

2 years ago

Metadata Update from @qulogic:
- Issue set to the milestone: 1.0.0

2 years ago

Metadata Update from @qulogic:
- Issue set to the milestone: 0.5.0 (was: 1.0.0)

2 years ago

Should have been fixed by #20.

Metadata Update from @qulogic:
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @qulogic:
- Issue set to the milestone: 0.10.0 (was: 0.5.0)

2 years ago

Login to comment on this ticket.

Metadata