From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: rust: Update to 1.67 - wanted - useful? ;-)
Date: Mon, 30 Jan 2023 19:34:01 +0100 [thread overview]
Message-ID: <21CC254D-0FF0-499D-9C3A-6E38D791EB8C@ipfire.org> (raw)
In-Reply-To: <677e1a22-9ae2-42d7-d9d6-dd52f76c4bcf@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]
Hello,
> On 30 Jan 2023, at 18:48, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 29.01.2023 21:57, Michael Tremer wrote:
>> Hello,
>>
>>> On 29 Jan 2023, at 18:18, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> right now I'm running a second clean build on current 'next'. Just to be
>>> *absolutely* sure that this works.
>>
>> Great!
>
> Second build ran through without errors.
>
>>> But: while uploading the sources of 'rust 1.67', I'm getting "out of
>>> disk space" errors.
>>>
>>> Seems that ~1.4GB source code is bit too much for git.ipfire.org ath the
>>> moment, sorry.
>>
>> Yes, the partition for the source ran out of space.
>>
>> I increased the size, but 1.4G per release seems to be very excessive…
>
> Yep. I was a bit puzzled, too.
>
> 1.65: 1.3GB, 1.67: 1.4GB - where will this end up when 2.0 comes out!?
> Estimated: ~4.7GB!? ;-)
>
> I'm ready to push - shall I?
Yes, please.
-Michael
>
> Best,
> Matthias
>
>> -Michael
>>
>>> Best,
>>> Matthias
>>>
>>> On 29.01.2023 15:27, Michael Tremer wrote:
>>>> Hello Matthias,
>>>>
>>>>> On 28 Jan 2023, at 14:37, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> after the last drama I hardly dare to ask, but: are we interested in a
>>>>> 'rust 1.67' update, now that the update to 'rust 1.65' is in 'next'?
>>>>
>>>> Generally yes, because we should follow upstream as close as possible when there is such a fast pace from upstream. I am sure there are plenty of bug fixes and security fixes included in this release.
>>>>
>>>> However, with the massive amount of work it takes, I believe that we do not need to jump to every single release. We have other things to take care of after all.
>>>>
>>>> So, if it is an easy jump, feel free to send patches. :)
>>>>
>>>> Thank you for all your effort. I know how much pain packaging Rust is.
>>>>
>>>> All the best,
>>>> -Michael
>>>>
>>>>> Changelog:
>>>>> =>
>>>>> https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1670-2023-01-26
>>>>>
>>>>> First tests and build (I was curious): only lfs and rootfile updates are
>>>>> needed.
>>>>>
>>>>> *duckandcover*... ;-)
>>>>>
>>>>> Best,
>>>>> Matthias
>>>>
>>>
>>
>
prev parent reply other threads:[~2023-01-30 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 13:37 Matthias Fischer
2023-01-29 14:27 ` Michael Tremer
2023-01-29 17:18 ` Matthias Fischer
2023-01-29 20:57 ` Michael Tremer
2023-01-30 17:48 ` Matthias Fischer
2023-01-30 18:34 ` Michael Tremer [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=21CC254D-0FF0-499D-9C3A-6E38D791EB8C@ipfire.org \
--to=michael.tremer@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