Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-emulation/runc/

[Michael Orlitzky <mjo@gentoo.org>]

On 12/07/2015 01:26 PM, Matt Turner wrote:
>>
>> I fixed it now.
> 
> This is happening with some frequency. Could we install a server-side
> git hook that prevents pushes if an ebuild is added without a Manifest
> change? It wouldn't have to verify anything more than that to catch
> nearly all of these problems.
> 

The last time this happened I had the same idea and sat down to write
one. The pre-push hook would do something like,

  * Get a list of cat/pkg affected by the push

  * Compare that list to profiles/categories to see which ones are
    packages (and should thus have manifests)

  * Verify the integrity of the files in each affected package by using
    something like `repoman manifest-check`

I gave up when I realized that this final step requires network access.
The missing manifest updates are for the distfiles, not the ebuilds. But
you could probably still fake it. For example, if any ebuild files are
added/removed, you expect Manifest to change.