public inbox for gentoo-guru@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philippe Chaintreuil <gentoo_bugs_peep@parallaxshift.com>
To: gentoo-guru@lists.gentoo.org, 1over137 <1over137@anche.no>
Subject: Re: [gentoo-guru] Re: Dev branch failing pkgcheck scan
Date: Fri, 15 Apr 2022 09:28:33 -0400	[thread overview]
Message-ID: <7c43a475-19fa-831d-cbb6-492b00bcd429@parallaxshift.com> (raw)
In-Reply-To: <e1b77c8a21d617ff845540b6b0a14aab96b681f8.camel@anche.no>

On 4/15/2022 9:22 AM, 1over137 wrote:
> Sorry, I think I failed to remove the old ebuild, causing this error.
> Simply removing the old ebuild in the folder (ssmtool-0.6.4.ebuild)
> would fix it. How do I fix it? Do I simply make a new commit?

I can confirm, deleting app-misc/vocabsieve/ssmtool-0.6.4.ebuild makes 
pkgcheck happy.

I'm new here, so I'm not authoritative by any stretch of the 
imagination, but I'd say just submit a new commit that removes the file.

Thanks for the quick response!


  reply	other threads:[~2024-11-24 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 13:06 [gentoo-guru] Dev branch failing pkgcheck scan Philippe Chaintreuil
2022-04-15 13:22 ` [gentoo-guru] " 1over137
2022-04-15 13:28   ` Philippe Chaintreuil [this message]
2022-04-15 14:21     ` Andrew Ammerlaan

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=7c43a475-19fa-831d-cbb6-492b00bcd429@parallaxshift.com \
    --to=gentoo_bugs_peep@parallaxshift.com \
    --cc=1over137@anche.no \
    --cc=gentoo-guru@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