public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Evans <grknight@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-MDB2/
Date: Mon, 7 Oct 2019 16:34:38 -0400	[thread overview]
Message-ID: <ea998d1c-21b3-c63c-6604-77ebef3031a1@gentoo.org> (raw)
In-Reply-To: <4456dde862edc283eca22ea4e5f4e3815385b869.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

On 10/7/2019 4:03 PM, Michał Górny wrote:
> On Mon, 2019-09-30 at 20:39 +0000, Brian Evans wrote:
>> commit:     36fc30fda1d8d8c3ac725c18cc74bc39bf2d98c2
>> Author:     Brian Evans <grknight <AT> gentoo <DOT> org>
>> AuthorDate: Mon Sep 30 19:01:12 2019 +0000
>> Commit:     Brian Evans <grknight <AT> gentoo <DOT> org>
>> CommitDate: Mon Sep 30 20:38:59 2019 +0000
>> URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36fc30fd
>>
>> dev-php/PEAR-MDB2: Mark stable on all arches
>>
>> No code changes.  Pure dependency change
>>
>> Package-Manager: Portage-2.3.76, Repoman-2.3.17
>> RepoMan-Options: --force
> 
> Why did you use '--force' here?  This doesn't seem the kind of change
> that would require using it.

Because of other changes in the same series which caused it to fail and
this was step 1 of the fix.

Cleaning the old rev removed the need for force.

Brian



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

      reply	other threads:[~2019-10-07 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1569875939.36fc30fda1d8d8c3ac725c18cc74bc39bf2d98c2.grknight@gentoo>
2019-10-07 20:03 ` [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: dev-php/PEAR-MDB2/ Michał Górny
2019-10-07 20:34   ` Brian Evans [this message]

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=ea998d1c-21b3-c63c-6604-77ebef3031a1@gentoo.org \
    --to=grknight@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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