public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Some packages in need of updates
Date: Mon, 07 Nov 2022 14:08:09 +0100	[thread overview]
Message-ID: <59e175ce-c91d-2baa-a0e6-366692bb531e@ipfire.org> (raw)
In-Reply-To: <87bf9f85-4675-92fd-f8cc-322485e364f0@ipfire.org>

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

Hi Peter,

On 07/11/2022 12:17, Peter Müller wrote:
> 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. :-/
Welcome back.
> 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:

I have been away visiting family so not been able to do any package update work but I am now back home.

I already have zlib, libxml2, expat on my list to work on so I will have a look at those and the others.

> - 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.
Previously I had asked about updating that header but Michael had replied not to bother with it. If it should be done then I will have a look mat it in future but could you or Michael confirm that it should be updated if the end year is earlier than the current year?
> 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.

I have also been working on the python3 update before my family visit but had some problems and waiting for feedback on a mail of mine. Will raise it at the conf call this evening.


Regards,

Adolf.


> Thank you in advance, and best regards,
> Peter Müller

  reply	other threads:[~2022-11-07 13:08 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 [this message]
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
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=59e175ce-c91d-2baa-a0e6-366692bb531e@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