Is it OK to stabilize =dev-python/python-distutils-extra-2.37-r1 ? If so, please CC all arches which have stable keywords for older versions of this package and add STABLEREQ keyword to the bug.
Maintainer timeout (30 days). Arches please go ahead.
amd64 stable
ppc stable
x86 stable. Last arch, closing
you ignored bug 456610 thanks
(In reply to Julian Ospald (hasufell) from comment #5) > you ignored bug 456610 > > thanks If you have a problem with the package, report a bug against it and not babble in stabilization bugs.
(In reply to Michał Górny from comment #6) > (In reply to Julian Ospald (hasufell) from comment #5) > > you ignored bug 456610 > > > > thanks > > If you have a problem with the package, report a bug against it and not > babble in stabilization bugs. I did. So we ignore upstream bugs now when stabilizing packages?
(In reply to Julian Ospald (hasufell) from comment #7) > I did. So we ignore upstream bugs now when stabilizing packages? Enhancement bugs are not blocking stabilization. If there is a serious problem with the package, there should be a Gentoo bug about it. There was also an about 2 months period between this bug was filed and the maintainer timeout.
(In reply to Paweł Hajdan, Jr. from comment #8) > (In reply to Julian Ospald (hasufell) from comment #7) > > I did. So we ignore upstream bugs now when stabilizing packages? > > Enhancement bugs are not blocking stabilization. > > If there is a serious problem with the package, there should be a Gentoo bug > about it. > > There was also an about 2 months period between this bug was filed and the > maintainer timeout. I gave YOU a link to a REGRESSION BUG and told YOU to not stabilize it yet. Do I have to mirror all upstream bug reports now? I still have a package that is affected by that regression and has a <dev-python/python-distutils-extra-2.34 dep. That is bad enough, but now it will also create funny blockers for people with stable arch.