Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Cura: update to 4.13.1
Date: Tue, 29 Mar 2022 17:48:15 +0200	[thread overview]
Message-ID: <20220329154815.tgWACe4OZFzmEBEYiy0f9hdTg2pIFAXhkdsj7r5hoo4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35001@inbox.vuxu.org>

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

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

Cura: update to 4.13.1
https://github.com/void-linux/void-packages/pull/35001

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

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

#### Local build testing
- I built this PR locally for my native architecture, x64-glibc

Todo:
- [ ] UFP(Reader|Writer) plugin fails, because libCharon is absent (I haven't packaged it yet). The error dialog appears twice, and clicking the "Remove plugin" button on both dialogs crashes cura.
- [x] ~~Ultimaker appears to have forgotten to tag a new release for pynest2d~~
  - the pynest2d repo hasn't changed in the past 3 releases. No need for a version bump

      parent reply	other threads:[~2022-03-29 15:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 19:07 [PR PATCH] WIP: Cura: update to 4.13 karl-nilsson
2022-01-11 20:23 ` [PR PATCH] [Updated] " karl-nilsson
2022-01-11 21:48 ` [PR PATCH] [Closed]: " karl-nilsson
2022-01-21  5:05 ` [PR PATCH] [Updated] " karl-nilsson
2022-01-28 16:10 ` karl-nilsson
2022-01-28 16:10 ` karl-nilsson
2022-03-01 23:12 ` karl-nilsson
2022-03-24  4:03 ` karl-nilsson
2022-03-24  4:25 ` karl-nilsson
2022-03-24  4:34 ` karl-nilsson
2022-03-24  4:36 ` [PR PATCH] [Updated] " karl-nilsson
2022-03-29 14:09 ` WIP: Cura: update to 4.13.1 ahesford
2022-03-29 15:24 ` [PR PATCH] [Updated] " karl-nilsson
2022-03-29 15:24 ` karl-nilsson
2022-03-29 15:41 ` karl-nilsson
2022-03-29 15:48 ` ahesford [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=20220329154815.tgWACe4OZFzmEBEYiy0f9hdTg2pIFAXhkdsj7r5hoo4@z \
    --to=ahesford@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).