From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Some packages in need of updates
Date: Tue, 29 Nov 2022 23:26:09 +0100 [thread overview]
Message-ID: <a9f92e88-f411-bd1d-244d-1929162b0534@ipfire.org> (raw)
In-Reply-To: <182423A2-FFBB-4BB5-8386-A6F79EF54EB1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]
On 29/11/2022 14:03, Michael Tremer wrote:
> Hello Adolf,
>
> I think we should remain on the stable branch.
Okay. I will leave fcron alone then.
Regards,
Adolf
>
> Not being sure what the changes are, I cannot imagine that we would need anything that is bleeding edge and fcron works just fine for us at the moment.
>
> Best,
> -Michael
>
>> On 25 Nov 2022, at 11:34, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Peter et al,
>>
>> In the first list you mentioned an update for fcron.
>>
>> The current version of fcron in IPFire is 3.2.1 which is the most up to date version from the Stable branch.
>>
>> There are versions 3.3.0 from Aug 2016 and 3.3.1 from Dec 2021 which are part of the Development branch.
>>
>> I would just like to have it confirmed that it is the latest Dev Branch version (3.3.1) that is being looked at for the update.
>>
>> Regards,
>>
>> Adolf.
>>
>> On 18/11/2022 16:38, Peter Müller wrote:
>>> Hello *,
>>>
>>> to add some packages to the initially posted list:
>>> - bash
>>> - libassuan
>>> - libpipeline
>>> - libuv
>>> - libxcrypt
>>> - OpenVPN
>>> - pcmciautils
>>> - qemu & qemu-ga
>>> - readline
>>> - sed
>>> - swig
>>> - usbutils
>>> - xz
>>>
>>> I am happy to take care of some of them, should the contributors typically doing
>>> package updates (Adolf and Matthias) experience capacity issues. Just drop me a line. :-)
>>>
>>> As for Core Update 172, it will be kept open until November 23, to await the outcome
>>> of Mozilla's ultimate to TrustCor Systems (and to pick up changes to their root CA
>>> store as quickly as possible).
>>>
>>> Thanks, and best regards,
>>> Peter Müller
>>>
>>>
>>>> Hello list,
>>>>
>>>> above all, apologies for being rather quiet recently. Yes, you guessed it, this is due to
>>>> ${dayjob} and non-IPFire-related todo lists, ever-growing as they are. :-/
>>>>
>>>> Since we currently have plenty of space left for upcoming Core Update 172, it would be great
>>>> if someone could take care of the following packages, which all seem to be in need of an
>>>> update:
>>>> - bird
>>>> - curl
>>>> - dehydrated
>>>> - expat
>>>> - fcron
>>>> - libedit
>>>> - libpng
>>>> - libxml2 ?
>>>> - libvirt
>>>> - ncat
>>>> - nginx
>>>> - nmap
>>>> - OpenSSL
>>>> - sudo
>>>> - zlib
>>>>
>>>> Please ensure to update the date in the copyright header, to make it more obvious which LFS
>>>> files have already collected some dust and which have not. :-) As always, your packaging efforts
>>>> and sniffing for updates is highly appreciated - many, many thanks.
>>>>
>>>> On that note, I screwed up the update of strongSwan 5.9.8, which I will take care of in due
>>>> course. Right now, the only thing scheduled for Core Update 172 on my end is to replace the
>>>> custom generation of Diffie-Hellman parameters in OpenVPN with those recommended by RFC 7919.
>>>>
>>>> Thank you in advance, and best regards,
>>>> Peter Müller
>
next prev parent reply other threads:[~2022-11-29 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 11:17 Peter Müller
2022-11-07 13:08 ` Adolf Belka
2022-11-18 15:38 ` Peter Müller
2022-11-20 18:10 ` Adolf Belka
2022-11-20 18:28 ` Matthias Fischer
2022-11-24 17:37 ` Adolf Belka
2022-11-25 11:34 ` Adolf Belka
2022-11-29 13:03 ` Michael Tremer
2022-11-29 22:26 ` Adolf Belka [this message]
2022-11-20 19:40 Michael Tremer
2022-11-22 15:46 ` Adolf Belka
2022-11-23 10:26 ` Michael Tremer
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=a9f92e88-f411-bd1d-244d-1929162b0534@ipfire.org \
--to=adolf.belka@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