Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: hatch-1.3.1/hatchling-1.6.0
Date: Wed, 03 Aug 2022 13:58:20 +0200	[thread overview]
Message-ID: <20220803115820.w8QZaCnM4KBbzGbfcKGCFJRJzQUcjSmL_MhV9GWTCN8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37892@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

hatch-1.3.1/hatchling-1.6.0
https://github.com/void-linux/void-packages/pull/37892

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

I've tried building and testing all packages that depend on hatchling, and except for hatch everything went smoothly. The test failures in hatch don't look very problematic to me though. Should we just deselect those?

Log: https://pastebin.com/raw/uywdGiZY

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-08-03 11:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06  9:45 [PR PATCH] hatchling 1.4.1 1 jcgruenhage
2022-07-06  9:54 ` [PR PATCH] [Updated] " jcgruenhage
2022-07-06 15:38 ` icp1994
2022-07-21  6:44 ` jcgruenhage
2022-07-21  6:45 ` jcgruenhage
2022-07-21  6:45 ` [PR PATCH] [Updated] " jcgruenhage
2022-07-21  7:04 ` hatch-1.3.1/hatchling-1.5.0 icp1994
2022-07-21  9:25 ` hatch-1.3.1/hatchling-1.5.0 jcgruenhage
2022-07-23  2:30 ` [PR REVIEW] hatch-1.3.1/hatchling-1.5.0 classabbyamp
2022-07-31 21:46 ` jcgruenhage
2022-07-31 21:46 ` [PR PATCH] [Updated] hatch-1.3.1/hatchling-1.5.0 jcgruenhage
2022-07-31 21:48 ` hatch-1.3.1/hatchling-1.5.0 jcgruenhage
2022-08-02  6:03 ` hatch-1.3.1/hatchling-1.6.0 icp1994
2022-08-02 16:13 ` hatch-1.3.1/hatchling-1.6.0 jcgruenhage
2022-08-02 16:17 ` [PR PATCH] [Updated] hatch-1.3.1/hatchling-1.6.0 jcgruenhage
2022-08-02 16:18 ` hatch-1.3.1/hatchling-1.6.0 jcgruenhage
2022-08-03 11:58 ` sgn [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=20220803115820.w8QZaCnM4KBbzGbfcKGCFJRJzQUcjSmL_MhV9GWTCN8@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).