public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: v2 version of borgbackup fuse patch set to fix bug#12611
Date: Sun, 07 Aug 2022 09:36:55 +0000	[thread overview]
Message-ID: <f067cd90-df34-2cc3-4148-5e3472ae5583@ipfire.org> (raw)
In-Reply-To: <dd05fcda-1b0d-938f-47e6-ba4fa68f4fcc@ipfire.org>

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

Hello Adolf,

thanks for your reply.

I just merged the third patch of version 3 of your patch series (this one:
https://patchwork.ipfire.org/project/ipfire/patch/20220806213556.66027-3-adolf.belka(a)ipfire.org/),
which resulted in the armv6l rootfile being added, as you can see here:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=30ea66cf4b1161d682b489e29096111ddc120c4f

Unless something else has changed from version 2 to 3 in your patch series,
then that should be everything required from my end. :-)

Thanks, and best regards,
Peter Müller


> Hi Peter,
> 
> I have submitted a v3 version of the patchset with a modified python3-pyfuse3 rootfile specific for the armv6l architecture. That should stop the failures that are occurring with the nightly builds for the armv6l version.
> 
> Regards,
> 
> Adolf.
> 
> 
> On 06/08/2022 16:43, Peter Müller wrote:
>> Hello Adolf,
>>
>> better late than never: Thank you for your mail and the second version of
>> the patchset. As you already noticed, I merged it a while ago. :-)
>>
>> On that occasion, apologies for not coordinating all the package updates
>> with you. I kind of went down the rabbit hole when I started with one thing
>> that I stumbled across, but did not mean to short-circuit you intentionally.
>>
>> So, thanks in advance for having volounteered to update Perl and Python
>> last week, and looking forward to your patches, as usual.
>>
>> All the best,
>> Peter Müller
>>
>>
>>> Hi Peter,
>>>
>>> The v2 version of the borgbackup fuse patch set to fix bug#12611 has been built and tested and worked as expected. Have marked the old version in patchwork as superseded.
>>>
>>> This v2 patch set is good to be merged in once it has been reviewed.
>>>
>>>
>>> Best regards,
>>>
>>> Adolf
>>>

      reply	other threads:[~2022-08-07  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  9:34 Adolf Belka
2022-08-06 14:43 ` Peter Müller
2022-08-06 15:54   ` Michael Tremer
2022-08-06 21:42   ` Adolf Belka
2022-08-07  9:36     ` Peter Müller [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=f067cd90-df34-2cc3-4148-5e3472ae5583@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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