On Thu, 13 Jun 2013 13:23:51 +0000 (UTC)
Petr Pisar <ppisar(a)redhat.com> wrote:
On 2013-06-12, Kevin Fenzi <kevin(a)scrye.com> wrote:
> So, there's nothing preventing the side tag and rebuild anytime now
> right? 5.18.0 is out, so we could start that work in rawhide?=20
Currently 5.18.0 does not pass one test when running in mock and koji.
(It's because of the terminal usage in tested perl debugger.) We think
we could have solved this issue in a few days.
Could you explain how the side tag inheritance works? It inherits
everything from rawhide, even builds made after the side tag creation,
except packages whose builds have been already made in the side tag.
Am I right? That means we still get fresh third-party dependencies
yes. However, there's are several downsides:
- Each side tag adds newrepo tasks which increases load a lot.
- If you rebuild perl-foo-1.0-1 in the side tag against the new perl,
then the maintainer has to fix something in rawhide, they would build
perl-foo-1.0-2 in rawhide and when the side tag was merged back over
either everyone would get the older one with the bug, or the newer
one against the old perl. So, it's really important to not take a
long time using a side tag to avoid this problem as much as possible.
I'd like to solve the linking issue before the mass rebuild,
mass rebuild triggers tests on all packages which allows to find
introduced problems very soon. I'd not like to see after bigger delay
that the explicit linkage caused some serious problem and we needed to
revert the linkage change, meaning to mass-rebuild again.
...snip good info about double open issue...
Yeah, I don't have an answer there, but hopefully some smarter folks
will chime in on it. I agree we should come up with a definite plan
before moving forward with mass rebuilding.