I noticed that app-text/pdfsandwich-0.1.7 is masked till some days ago. I cannot find the reason anywhere. May you help me? Is there some program to remove it? Reproducible: Always
The answer is in the mask itself. $ emerge -vp pdfsandwich These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy "pdfsandwich" have been masked. !!! One of the following masked packages is required to complete your request: - app-text/pdfsandwich-0.1.7::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Aaron Bauman <bman@gentoo.org> (2020-06-03) # py2 only. dead upstream. m-n. rdep. # Masked for removal in 15 days - app-text/pdfsandwich-0.1.4-r1::gentoo (masked by: package.mask)
(In reply to Silvio from comment #0) > I noticed that app-text/pdfsandwich-0.1.7 is masked till some days ago. > I cannot find the reason anywhere. “py2 only. dead upstream. m-n. rdep.” from https://packages.gentoo.org/packages/app-text/pdfsandwich I do not know what the ‘m-n. rdep.’ abbreviations mean. Because pdfsandwich does not depend directly on Python, I think the reason is that it depends on media-gfx/exact-image, which is also masked with the same reason given: https://packages.gentoo.org/packages/media-gfx/exact-image TBH, I don't understand the reason for the masks: AFAICT, media-gfx/exact-image does not *need* Python, it provides bindings. Gentoo can choose to not build those (Python 2-only?) bindings. Then all applications that depends on it without using those bindings can still remain.
Related: Bug 727290
*** Bug 727290 has been marked as a duplicate of this bug. ***
(In reply to Erik Quaeghebeur from comment #2) > (In reply to Silvio from comment #0) > > I noticed that app-text/pdfsandwich-0.1.7 is masked till some days ago. > > I cannot find the reason anywhere. > “py2 only. dead upstream. m-n. rdep.” from > https://packages.gentoo.org/packages/app-text/pdfsandwich > > I do not know what the ‘m-n. rdep.’ abbreviations mean. > > Because pdfsandwich does not depend directly on Python, I think the reason > is that it depends on media-gfx/exact-image, which is also masked with the > same reason given: https://packages.gentoo.org/packages/media-gfx/exact-image > > TBH, I don't understand the reason for the masks: AFAICT, > media-gfx/exact-image does not *need* Python, it provides bindings. Gentoo > can choose to not build those (Python 2-only?) bindings. Then all > applications that depends on it without using those bindings can still > remain. It means that the packages were masked because they are a reverse dependency of another package which has python 2 only. If the maintainers or someone wants to remove the python bindings from media-gfx/exact-image then that will solve the problem.
(In reply to Aaron Bauman from comment #5) > It means that the packages were masked because they are a reverse dependency > of another package which has python 2 only. OK. But AFAICT, exact-image uses SWIG to generate the bindings, so the package should be Python 3-compatible even if the ebuild doesn't support that. N.B.: * There is Bug 609768, which may mean that the python bindings weren't being generated anyway. * I looked at the build configuration files and for 0.8.1, it seems to hardcode a python 2.5 path, but for 1.0.2 (cf. Bug 544102), it gets the actual python version. I understand the desire to get rid of anything Python 2, but masking with a removal date only 15 days in the future for a situation like this does feel too quick. I have systems that I only update once a month and I'm sure there are more people like me.
Created attachment 643730 [details] ebuild for exact-image with option of generating python bindings removed (In reply to Aaron Bauman from comment #5) > If the maintainers or someone wants to remove the python bindings from > media-gfx/exact-image then that will solve the problem. OK. Because I'm not experienced enough to fix the python dependency of exact-image and because I don't really care about its python bindings, I have prepared an ebuild for the version currently in the tree without the option to build the python bindings. I've tested that it builds and that pdfsandwich works after emerging the changed exact-image.
Unmasked.
