From qboosh at pld-linux.org  Fri Aug 16 19:12:51 2024
From: qboosh at pld-linux.org (Jakub Bogusz)
Date: Fri, 16 Aug 2024 19:12:51 +0200
Subject: [packages/Mesa] up to 24.2.0
In-Reply-To: <f0b01aee4c9dc751c6ec4eada692bc017dfc3fa5_refs_heads_master@pld-linux.org>
References: <41950a3bf0bcd3453fac369c25cb78c21da25c82_refs_heads_master@pld-linux.org>
 <f0b01aee4c9dc751c6ec4eada692bc017dfc3fa5_refs_heads_master@pld-linux.org>
Message-ID: <20240816171251.GA25592@mail>

On Fri, Aug 16, 2024 at 04:33:34PM +0200, atler wrote:
> commit f0b01aee4c9dc751c6ec4eada692bc017dfc3fa5
> Author: Jan Palus <atler at pld-linux.org>
> Date:   Fri Aug 16 15:39:08 2024 +0200
> 
>     up to 24.2.0
>     
>     all "megadrivers" (dri/vdpau/va) use symlink to single binary instead of
>     hardlinks. since there's little point in keeping multiple packages just
>     for single symlink, they were into single dri, vdapu and va driver
>     package.

> -%package -n libva-driver-gallium
> +%package -n libva-driver

libva-driver-gallium or libva-driver-mesa, please
(there are another libva-driver-* packages, e.g. libva-driver-intel or
libva-driver-vdpau)


-- 
Jakub Bogusz    http://qboosh.pl/


From atler at pld-linux.org  Sat Aug 17 13:32:33 2024
From: atler at pld-linux.org (Jan Palus)
Date: Sat, 17 Aug 2024 13:32:33 +0200
Subject: [packages/Mesa] up to 24.2.0
In-Reply-To: <20240816171251.GA25592@mail>
References: <41950a3bf0bcd3453fac369c25cb78c21da25c82_refs_heads_master@pld-linux.org>
 <f0b01aee4c9dc751c6ec4eada692bc017dfc3fa5_refs_heads_master@pld-linux.org>
 <20240816171251.GA25592@mail>
Message-ID: <2cef9eed-9d94-4666-b4c7-8eca60c56f6a@pld-linux.org>

On 16.08.2024 19:12, Jakub Bogusz wrote:
> On Fri, Aug 16, 2024 at 04:33:34PM +0200, atler wrote:
>> commit f0b01aee4c9dc751c6ec4eada692bc017dfc3fa5
>> Author: Jan Palus <atler at pld-linux.org>
>> Date:   Fri Aug 16 15:39:08 2024 +0200
>>
>>      up to 24.2.0
>>      
>>      all "megadrivers" (dri/vdpau/va) use symlink to single binary instead of
>>      hardlinks. since there's little point in keeping multiple packages just
>>      for single symlink, they were into single dri, vdapu and va driver
>>      package.
>> -%package -n libva-driver-gallium
>> +%package -n libva-driver
> libva-driver-gallium or libva-driver-mesa, please
> (there are another libva-driver-* packages, e.g. libva-driver-intel or
> libva-driver-vdpau)
Good point, thanks for suggestion. Renamed to libva-driver-gallium and 
aligned libvdpau driver name for consistency (libvdpau-driver-gallium).


From glen at pld-linux.org  Tue Aug 20 12:41:37 2024
From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=C3=A4e?=)
Date: Tue, 20 Aug 2024 13:41:37 +0300
Subject: Fatal glibc error: cannot get entropy for arc4random
In-Reply-To: <ip76z7huaz4b4vexko3q4dxljzs3yqyoorq7slqssyruczybky@w36feutwbb7u>
References: <2345527f-ed26-43c5-afa7-e3ca8849b699@pld-linux.org>
 <893124bf-2f31-4c4e-b350-75633fef8645@maven.pl>
 <ip76z7huaz4b4vexko3q4dxljzs3yqyoorq7slqssyruczybky@w36feutwbb7u>
Message-ID: <09a2a602-1d64-4863-8938-6569b87e4246@pld-linux.org>


On 25.07.2024 11:05, Jan Palus wrote:
> Actually glibc-2.39-6 does not fallback to/dev/*random due to bug in
> arc4random fallback logic (return value checked for ENOSYS instead of
> errno).
>
> It was fixed on Jul 8 (glibc 2.40 does not suffer from it):
>
> https://sourceware.org/git/?p=glibc.git;a=commit;h=184b9e530e6326e668709826903b6d30dc6cac3f


upgraded glibc (glibc-2.40-2-th.x86_64). sshd starts up now, but logins 
still fail


$ ssh localhost
Connection closed by 127.0.0.1 port 22


Aug 20 13:34:44 localhost sshd-session[60905]: error: mm_reap: preauth 
child terminated by signal 31
Aug 20 13:34:44?localhost sshd[60900]: Session process 60905 unpriv 
child crash for connection from?127.0.0.1 to 127.0.0.1


$ ssh localhost
kex_exchange_identification: Connection closed by remote host

Aug 20 13:34:51 localhost sshd[60900]: drop connection #0 from 
[127.0.0.1]:63676 on [127.0.0.1]:22 penalty: caused crash


signal 31, I believe is SIGSYS:

31 SIGSYS     Dump        Bad system call                      No


package versions, just in case, again


glibc-2.40-2.x86_64: equal version installed, skipped
openssl-3.3.1-1.x86_64: equal version installed, skipped
libseccomp-2.5.5-1.x86_64: equal version installed, skipped
openssh-server-9.8p1-1.x86_64: equal version installed, skipped


From arekm at maven.pl  Tue Aug 27 12:08:23 2024
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=C5=9Bkiewicz?=)
Date: Tue, 27 Aug 2024 12:08:23 +0200
Subject: heimdal vs mit krb5
Message-ID: <9bdc46da-cd95-49ef-89f8-4d6e4047b2e3@maven.pl>


Recent postgresql versions require things ("MIT Credential Store") that 
do not exist in current heimdal 7.8.

heimdal 8 is expected to have that (commits are in repository) but I 
don't see it coming especially that latest heimdal release is from 2022.

Should we just switch in Th to maintained implementation - mit krb 5 
(latest release jun 2024) instead?

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )



From baggins at pld-linux.org  Tue Aug 27 23:54:43 2024
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Tue, 27 Aug 2024 23:54:43 +0200
Subject: heimdal vs mit krb5
In-Reply-To: <9bdc46da-cd95-49ef-89f8-4d6e4047b2e3@maven.pl>
References: <9bdc46da-cd95-49ef-89f8-4d6e4047b2e3@maven.pl>
Message-ID: <Zs5LIzdqIq1a02v9@tachikoma>

On Tue, 27 Aug 2024, Arkadiusz Mi?kiewicz via pld-devel-en wrote:

> 
> Recent postgresql versions require things ("MIT Credential Store") that 
> do not exist in current heimdal 7.8.
> 
> heimdal 8 is expected to have that (commits are in repository) but I 
> don't see it coming especially that latest heimdal release is from 2022.
> 
> Should we just switch in Th to maintained implementation - mit krb 5 
> (latest release jun 2024) instead?

The reason we had heimdal instead of MIT was samba 4.0 that needed it.
Since AFAIR we build samba with internal heimdal for long time I don't
have anything against switching to MIT.

Queston is - are you going to take care of all rebuilds and deps?

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From ngompa13 at gmail.com  Wed Aug 28 00:07:09 2024
From: ngompa13 at gmail.com (Neal Gompa)
Date: Tue, 27 Aug 2024 18:07:09 -0400
Subject: heimdal vs mit krb5
In-Reply-To: <Zs5LIzdqIq1a02v9@tachikoma>
References: <9bdc46da-cd95-49ef-89f8-4d6e4047b2e3@maven.pl>
 <Zs5LIzdqIq1a02v9@tachikoma>
Message-ID: <CAEg-Je9WPfmvRncNy8kf_=q9EkFJDDe5OcYysvsjPpAE+MVqwQ@mail.gmail.com>

On Tue, Aug 27, 2024 at 6:04?PM Jan R?korajski <baggins at pld-linux.org> wrote:
>
> On Tue, 27 Aug 2024, Arkadiusz Mi?kiewicz via pld-devel-en wrote:
>
> >
> > Recent postgresql versions require things ("MIT Credential Store") that
> > do not exist in current heimdal 7.8.
> >
> > heimdal 8 is expected to have that (commits are in repository) but I
> > don't see it coming especially that latest heimdal release is from 2022.
> >
> > Should we just switch in Th to maintained implementation - mit krb 5
> > (latest release jun 2024) instead?
>
> The reason we had heimdal instead of MIT was samba 4.0 that needed it.
> Since AFAIR we build samba with internal heimdal for long time I don't
> have anything against switching to MIT.
>
> Queston is - are you going to take care of all rebuilds and deps?

IIRC, these days samba-dc works fine with MIT krb5 too. Samba in
Fedora is built with it and it seems to work okay. You could get away
without using heimdal krb5 entirely.


-- 
?????????/ Always, there's only one truth!