1 |
On Mon, Dec 7, 2015 at 1:26 PM, Matt Turner <mattst88@g.o> wrote: |
2 |
> On Mon, Dec 7, 2015 at 10:19 AM, Robin H. Johnson <robbat2@g.o> wrote: |
3 |
>> On Mon, Dec 07, 2015 at 05:16:01AM +0000, Doug Goldstein wrote: |
4 |
>>> commit: 37c1ec7ef31a51206421f03a2df489ec7d7ca244 |
5 |
>>> Author: Doug Goldstein <cardoe <AT> gentoo <DOT> org> |
6 |
>>> AuthorDate: Mon Dec 7 05:14:50 2015 +0000 |
7 |
>>> Commit: Doug Goldstein <cardoe <AT> gentoo <DOT> org> |
8 |
>>> CommitDate: Mon Dec 7 05:15:22 2015 +0000 |
9 |
>>> URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37c1ec7e |
10 |
>>> |
11 |
>>> app-emulation/runc: version bump |
12 |
>>> |
13 |
>>> bump to latest upstream release. |
14 |
>>> |
15 |
>>> Signed-off-by: Doug Goldstein <cardoe <AT> gentoo.org> |
16 |
>>> |
17 |
>>> app-emulation/runc/runc-0.0.5.ebuild | 52 ++++++++++++++++++++++++++++++++++++ |
18 |
>>> 1 file changed, 52 insertions(+) |
19 |
>> You did not update the Manifest or use repoman, and thus blocked the |
20 |
>> rsync tree. |
21 |
>> |
22 |
>> I fixed it now. |
23 |
> |
24 |
> This is happening with some frequency. Could we install a server-side |
25 |
> git hook that prevents pushes if an ebuild is added without a Manifest |
26 |
> change? It wouldn't have to verify anything more than that to catch |
27 |
> nearly all of these problems. |
28 |
> |
29 |
|
30 |
That would not work for ebuilds which do not have any distfiles |
31 |
associated with them. |