From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Cc: Doug Goldstein <cardoe@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-emulation/runc/
Date: Mon, 7 Dec 2015 10:26:57 -0800 [thread overview]
Message-ID: <CAEdQ38F_Ld6zMNpAnG9Xxs6oPUTDT9kyspO7-4X8UCLJOfe00g@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20151207T181502-104689130Z@orbis-terrarum.net>
On Mon, Dec 7, 2015 at 10:19 AM, Robin H. Johnson <robbat2@gentoo.org> wrote:
> On Mon, Dec 07, 2015 at 05:16:01AM +0000, Doug Goldstein wrote:
>> commit: 37c1ec7ef31a51206421f03a2df489ec7d7ca244
>> Author: Doug Goldstein <cardoe <AT> gentoo <DOT> org>
>> AuthorDate: Mon Dec 7 05:14:50 2015 +0000
>> Commit: Doug Goldstein <cardoe <AT> gentoo <DOT> org>
>> CommitDate: Mon Dec 7 05:15:22 2015 +0000
>> URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37c1ec7e
>>
>> app-emulation/runc: version bump
>>
>> bump to latest upstream release.
>>
>> Signed-off-by: Doug Goldstein <cardoe <AT> gentoo.org>
>>
>> app-emulation/runc/runc-0.0.5.ebuild | 52 ++++++++++++++++++++++++++++++++++++
>> 1 file changed, 52 insertions(+)
> You did not update the Manifest or use repoman, and thus blocked the
> rsync tree.
>
> 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.
next prev parent reply other threads:[~2015-12-07 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1449465322.37c1ec7ef31a51206421f03a2df489ec7d7ca244.cardoe@gentoo>
2015-12-07 18:19 ` [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: app-emulation/runc/ Robin H. Johnson
2015-12-07 18:26 ` Matt Turner [this message]
2015-12-07 18:49 ` Michael Orlitzky
2015-12-07 18:58 ` Mike Gilbert
2015-12-07 19:20 ` Matt Turner
2015-12-07 19:36 ` [gentoo-dev] git update hook: detecting missing Manifest DIST entries Robin H. Johnson
2015-12-08 0:47 ` Peter Stuge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEdQ38F_Ld6zMNpAnG9Xxs6oPUTDT9kyspO7-4X8UCLJOfe00g@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=cardoe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox