#2283 No way to unset/block inherited tag.extra values
Closed: Fixed 22 days ago by tkopecek. Opened 5 months ago by mikem.

In getBuildConfig tag.extra values are effectively inherited. However, there is no way for a tag to unset a value that an ancestor has set. You can set it to None, but that is not the same as unset.

This matters because we have code that distinguishes when values are unset. One case is the code that checks for mock.new_chroot. It is only when this value is unset that neither --old-chroot nor --new-chroot is passed. Legacy builders with an older mock might not be able to handle these options.

There could easily be other examples.


Metadata Update from @tkopecek:
- Custom field Size adjusted to None
- Issue set to the milestone: 1.23

5 months ago

Metadata Update from @tkopecek:
- Issue tagged with: testing-ready

a month ago

Metadata Update from @jcupova:
- Issue tagged with: testing-done

a month ago

Commit 0b5638c relates to this ticket

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #2530 Merged 14 days ago
  • #2495 Merged 22 days ago