#9048 Set sidetag_debuginfo_allowed/sidetag_rpm_macros_allowed on fXX-build
Opened 2 months ago by ignatenkobrain. Modified 2 months ago

Having sometimes defining different RPM macro or enabling debuginfo in side tags are quite useful.

Those do not automatically enable any changes, but allow users to modify those settings in side tags.


I have all necessary rights to do this, but do not want to touch this until you agree whether it is ok to do or not :)

We might have to check with FESCo.

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on External (was: Needs Review)
- Issue tagged with: groomed, low-trouble, medium-gain

2 months ago

Why? We are not going to allow this in the final targets, just in the side tags.

My concern is that if you set macros you could build something very differently than it would be build in the normal build tag.

Or make it so the thing doesn't build at all in the normal build tag, only in a side tag with macros...

Perhaps this could be mitigated by comments in the spec or something, but it's pretty undiscoverable otherwise.

What macro(s) would you use this to change?

@kevin so my specific example here is cmake rebuild. I want to rebuild all packages that depend on cmake in a side tag and see what fails. Without pushing any commits to the distgit. That requires change of %dist.

This sounds like essentially trying to use side-tags for one of copr's use-case right?

I would likely feel better about it if we could address the issue of the accidental merge. I.e: have a way to ensure that the side-tag cannot be merged back into the main tag, so that random $koji_admin who hasn't followed that this tag is not meant to be merged, cannot successfully merge it.
Can introduce a conflict or something like this?

Does that make sense?

This sounds like essentially trying to use side-tags for one of copr's use-case right?

If only COPR would build on all architectures Fedora supports and would use koji's -build repo..

I would likely feel better about it if we could address the issue of the accidental merge. I.e: have a way to ensure that the side-tag cannot be merged back into the main tag, so that random $koji_admin who hasn't followed that this tag is not meant to be merged, cannot successfully merge it.

I don't think koji admins are merging side tags? Those should go via bodhi where such things should be detected (I guess they are not, yet?).

Does that make sense?

Sure!

Does that make sense?

It does

I don't think koji admins are merging side tags?

It depends on the type of side-tags we're talking about here, self-service ones or koji-admin created ones (the old fashion ones).
I do not know though if bodhi would accept the old fashion side-tags or not.

I'm talking only about self-service sidetags here. That parameter does not change anything for old-style side tags.

Login to comment on this ticket.

Metadata