public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Some packages in need of updates
Date: Sun, 20 Nov 2022 19:28:06 +0100	[thread overview]
Message-ID: <95da458a-5bfb-106a-c4be-3b6382d173ec@ipfire.org> (raw)
In-Reply-To: <fc56e18a-47ee-46b1-8887-52f0ceea3f11@ipfire.org>

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

Hi,

indeed, not easy.

Does this link help?

=>
https://kernel.googlesource.com/pub/scm/linux/kernel/git/brodo/pcmciautils/+/refs/tags/pcmciautils-018/

Leads to:

=>
https://kernel.googlesource.com/pub/scm/linux/kernel/git/brodo/pcmciautils/+archive/refs/tags/pcmciautils-018.tar.gz

HTH,
Matthias

On 20.11.2022 19:10, Adolf Belka wrote:
> Hi Peter,
> 
> I have done update patches for most of the packages listed below.
> One I had problems with was pcmciautils as I could not find a location 
> for the source tarball. I tried my usual trick to see where Arch Linux 
> gets it from but they no longer have pcmciautils as a package in the 
> standard repos or the AUR , so it is no longer available anywhere on 
> Arch Linux.
> 
> Do you have any info on where I can get the source tarball from?
> 
> 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
> 


  reply	other threads:[~2022-11-20 18:28 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 [this message]
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=95da458a-5bfb-106a-c4be-3b6382d173ec@ipfire.org \
    --to=matthias.fischer@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