Re: [gentoo-dev] Re: Common rsync-gen errors, why they happen, and what you can do about it

[Dirkjan Ochtman]

On Wed, Jan 18, 2017 at 5:58 AM, Doug Freed <dwfreed@×××.edu> wrote:
> At some point, the repoman manifest-check, or some variation of it,
> will probably get added to a post-receive hook, which will then abort
> your push if you try to push something that would break the conversion
> process.  That said, you should still be doing your due diligence to
> ensure that eventual hook doesn't yell at you.

This sounds like a much better strategy to me. We're expecting people
to check things that should be easy to check for machines. Yes, some
people (like myself) will always use repoman to commit, but it would
be much better if something this important (because it basically
delays other updates to users everywhere) is checked by an automated
process for every push, and disallows pushes like this.

> I can see if it's something I need to fix with my code.  But it's been
> a while since that's been the case, so all the failures these days are
> primarily for the previously mentioned issues.

That makes sense. My other comment initially reading your email would
be, send those emails to gentoo-core or -project or whatever. If
others don't get to feel the pain (of every half-hour error emails,
for example), they will be much less compelled to fix the problem. So
absorbing this "pain" into just you or infra makes us less scalable as
a distribution, and less likely that someone will feel motivated to
add the extra bits of automation (like a git hook) that will make this
problem go away.

Cheers,

Dirkjan