All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Richard Weinberger <richard@nod.at>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [AUH] erofs-utils: upgrading to 20191016 SUCCEEDED
Date: Thu, 3 Jun 2021 11:12:31 +0200	[thread overview]
Message-ID: <CANNYZj97RXVD0K0knaBHmZ24twfK06bZrFzjhsAtT0wUT27=Ag@mail.gmail.com> (raw)
In-Reply-To: <MADEUP.1684EE085BD427A1.11265@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

Bogus tag, please ignore. I have queued a patch to correct this. (there is
currently no new version to update to)

Alex

On Thu, 3 Jun 2021 at 03:24, <auh@auh.yoctoproject.org> wrote:

> Hello,
>
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe *erofs-utils* to
> *20191016* has Succeeded.
>
> Next steps:
>     - apply the patch: git am 0001-erofs-utils-upgrade-1.2.1-20191016.patch
>     - check the changes to upstream patches and summarize them in the
> commit message,
>     - compile an image that contains the package
>     - perform some basic sanity tests
>     - amend the patch and sign it off: git commit -s --reset-author --amend
>     - send it to the appropriate mailing list
>
> Alternatively, if you believe the recipe should not be upgraded at this
> time,
> you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> automatic upgrades would no longer be attempted.
>
> Please review the attached files for further information and build/update
> failures.
> Any problem please file a bug at
> https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

      reply	other threads:[~2021-06-03  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  1:24 [AUH] erofs-utils: upgrading to 20191016 SUCCEEDED auh
2021-06-03  9:12 ` Alexander Kanavin [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='CANNYZj97RXVD0K0knaBHmZ24twfK06bZrFzjhsAtT0wUT27=Ag@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.