From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pending patches for upcoming Core Update 154
Date: Fri, 05 Feb 2021 16:19:32 +0000 [thread overview]
Message-ID: <69824307-B951-4F7E-9DFC-043C0A82D579@ipfire.org> (raw)
In-Reply-To: <2c73c6f9-836a-346a-0cb8-db11b9f6f5bb@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4163 bytes --]
Hello,
Okay with me, if someone is happy to maintain it :)
-Michael
> On 5 Feb 2021, at 11:38, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi all,
>
> On 05/02/2021 12:10, Michael Tremer wrote:
>> Hi,
>> I am not sure if the console is a good place for this.
>> Do people not use stuff on the web for this?
>
> You can do it on the web but this package does give a lot of information but I have it installed on my desktop pc. As I work on IPFire via ssh from my desktop then if I need to use sipcalc I can just open a terminal on my desktop and run it.
>
> Regards,
> Adolf
>> -Michael
>>> On 5 Feb 2021, at 03:58, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>
>>> Adolf,
>>>
>>> And one more request - very low priority. Can sipcalc be added as on IPFire Add-on?
>>>
>>> This came up in a thread:
>>> https://community.ipfire.org/t/open-vpn-no-ping-to-192-168-0-240/4089/2?u=jon
>>>
>>> This may already be on Peter's to-do list.
>>>
>>>
>>> Jon
>>>
>>>
>>>> On Feb 4, 2021, at 9:02 PM, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>>
>>>> Hi Adolf,
>>>>
>>>> Could I add a request for sqlite3? The current version is about 2 years old.
>>>>
>>>> [root(a)ipfire ~]# sqlite3
>>>> SQLite version 3.26.0 2018-12-01 12:34:55
>>>> Enter ".help" for usage hints.
>>>> Connected to a transient in-memory database.
>>>> Use ".open FILENAME" to reopen on a persistent database.
>>>> sqlite>
>>>>
>>>> And with the blessing and approval of the Devs, can REGEXP be added to sqlite3? I don't know the security risk of this so if it cannot be done because of security that is fine.
>>>>
>>>> Best regards,
>>>> Jon
>>>>
>>>>
>>>>
>>>>> On Jan 30, 2021, at 7:51 AM, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>>
>>>>> Hallo all,
>>>>>
>>>>> I am currently working on screen-4.8.0
>>>>>
>>>>>
>>>>> My process for the packages I work on is I see an "interesting" package name in the list of programs being built and I check if it is up to date or not. If it is not then I have a go at it.
>>>>>
>>>>> If any of you have packages that you think it would be good/useful for me to work on then let me know and I will have a go. Otherwise I will keep on working on things that look "interesting" to me.
>>>>>
>>>>> Have a great weekend.
>>>>>
>>>>> Adolf.
>>>>>
>>>>> Sent from my Desktop Computer
>>>>>
>>>>> On 30/01/2021 14:08, Peter Müller wrote:
>>>>>> Hello Matthias, hello *,
>>>>>>
>>>>>> thanks for your reply.
>>>>>>
>>>>>> Glad you mention and take care of libgcrypt, that one is important. :-)
>>>>>>
>>>>>> Meanwhile, I am trying to get IPFire 2.x build working on my workstation [sic], working on
>>>>>>
>>>>>> - binutils 2.36, which requires patching the kernel and hyperscan
>>>>>> - hyperscan 5.4.0
>>>>>> - libseccomp 2.5.1
>>>>>> - Postfix 3.5.9
>>>>>>
>>>>>> for Core Update 154.
>>>>>>
>>>>>> freetype unfortunately continues to break most recent ghostscript, and I have not yet found
>>>>>> out why. In addition, ghostscript-fonts-std seems to be heavily outdated (8.11 != 9.x), but
>>>>>> I have not found a suitable source for some more current RPMs flying around at OpenSuSE.
>>>>>>
>>>>>> Thanks, and best regards,
>>>>>> Peter Müller
>>>>>>
>>>>>>> On 27.01.2021 18:15, Peter Müller wrote:
>>>>>>>> Hello *,
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>> to avoid redundancies: I am currently working on Postfix 3.5.9 and (more important) sudo
>>>>>>>> 1.9.5p2 for upcoming Core Update 154. Both fix some security issues; I am pretty sure you
>>>>>>>> have heard of CVE-2021-3156 affecting the latter by now.
>>>>>>>>
>>>>>>>> There might be some minor stuff (USB/PCI database files, etc.) to do as well, but I have
>>>>>>>> not checked that, yet. :-)
>>>>>>>
>>>>>>> My two cents - working ('Devel' does it, I'm only watching ;-) ) on:
>>>>>>>
>>>>>>> libgcrypt => 1.9.1
>>>>>>> libgpg-error => 1.41
>>>>>>> libassuan => 2.5.4
>>>>>>>
>>>>>>> Best,
>>>>>>> Matthias
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks, and best regards,
>>>>>>>> Peter Müller
>>>>>>>>
>>>>>>>
>>>>
>>>
next prev parent reply other threads:[~2021-02-05 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26ED65B8-154A-4476-B9E6-7DCD58078E0C@gmail.com>
2021-02-05 11:10 ` Michael Tremer
2021-02-05 11:38 ` Adolf Belka
2021-02-05 16:19 ` Michael Tremer [this message]
2021-02-05 17:31 ` Adolf Belka
2021-02-05 17:46 ` Michael Tremer
2021-02-05 17:59 ` Adolf Belka
[not found] <AC2550F9-7FCE-4533-90BF-B8E46F825D8E@gmail.com>
2021-02-05 8:32 ` Adolf Belka
2021-02-05 11:10 ` Michael Tremer
2021-01-27 17:15 Peter Müller
2021-01-27 19:04 ` Peter Müller
2021-01-27 19:13 ` Adolf Belka
2021-01-27 19:58 ` Peter Müller
2021-01-27 20:05 ` Adolf Belka
2021-01-28 20:20 ` Peter Müller
2021-01-30 16:29 ` Michael Tremer
2021-01-30 17:26 ` Peter Müller
2021-02-01 11:17 ` Michael Tremer
2021-01-30 13:00 ` Matthias Fischer
2021-01-30 13:08 ` Peter Müller
2021-01-30 13:51 ` Adolf Belka
2021-01-30 16:52 ` Adolf Belka
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=69824307-B951-4F7E-9DFC-043C0A82D579@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