Am Wed, Mar 01, 2023 at 12:54:04AM +0100 schrieb Andreas Enge:
> Well, I gave it a try, and it seems to be okay.
I spake too fast. Somehow I took samba/fixed from core-updates instead
of samba/pinned from master, and since I do not quite follow which is what,
I will give up and let someone else
Am Tue, Feb 28, 2023 at 09:55:28PM +0100 schrieb Andreas Enge:
> Am Tue, Feb 28, 2023 at 09:51:49PM +0100 schrieb Andreas Enge:
> > Maybe it is time to merge master back into core-updates?
> Where the vague "it is time to" could be read as "could you please?".
> It is something I have never done,
Am Tue, Feb 28, 2023 at 09:51:49PM +0100 schrieb Andreas Enge:
> Maybe it is time to merge master back into core-updates?
Where the vague "it is time to" could be read as "could you please?".
It is something I have never done, so it makes me nervous. Well, I suppose
I could just merge and try to
Am Tue, Feb 28, 2023 at 01:20:08PM -0500 schrieb Leo Famulari:
> Qtwebkit has been removed from the master branch.
Oh right, I even remember now that you sent messages about it.
Maybe it is time to merge master back into core-updates?
(Although the problem here seems to be unrelated to webkit,
Qtwebkit has been removed from the master branch.
On Tue, Feb 28, 2023, at 13:09, Andreas Enge wrote:
> Am Tue, Feb 28, 2023 at 04:13:52PM +0100 schrieb Andreas Enge:
>> Now I am trying to build all
>> the Qt packages before applying the patch to core-updates; it looks good
>> so far.
>
> It went
Am Tue, Feb 28, 2023 at 04:13:52PM +0100 schrieb Andreas Enge:
> Now I am trying to build all
> the Qt packages before applying the patch to core-updates; it looks good
> so far.
It went well with all the qt* packages.
Then python-pyqt-without-qtwebkit fails already in its configure phase,
In the context of security problems and package removal, I just noticed
(by "./pre-inst-env guix package -A ^qt") that we still have a qtwebkit
package. The latest release dates from 2020, and this also the last
release, if I understand correctly that the project has been abandoned.
However:
Hello Philip, Kiasoc5, Efraim,
thanks a lot for your input!
Indeed I got my information that Qt 5 was phased out from Wikipedia,
which mentioned May 2021 as the end of support. I did not expect there
to be more versions! But then discovered the 5.15.8 version, probably
related to the commercial
On Sun, Feb 26, 2023 at 09:38:43PM -0500, kiasoc5 wrote:
> On 2/26/23 18:43, Philip McGrath wrote:
> > Hi,
> >
> > On Sunday, February 26, 2023 7:44:20 AM EST Andreas Enge wrote:
> > >
> > > In any case, I realised that we are still compiling most packages
> > > (including
> > > KDE) with Qt 5,
On 2/26/23 18:43, Philip McGrath wrote:
Hi,
On Sunday, February 26, 2023 7:44:20 AM EST Andreas Enge wrote:
In any case, I realised that we are still compiling most packages (including
KDE) with Qt 5, which is seriously outdated (not maintained any more in the
free version since May 2021). Qt
Hi,
On Sunday, February 26, 2023 7:44:20 AM EST Andreas Enge wrote:
>
> In any case, I realised that we are still compiling most packages (including
> KDE) with Qt 5, which is seriously outdated (not maintained any more in the
> free version since May 2021). Qt 6.3 support will end in April
Am Sat, Feb 25, 2023 at 07:19:15PM +0100 schrieb Ludovic Courtès:
> Given the test name, one would hope that it’s the usual time bomb of an
> expired X.509 certificate.
Apparently not, just some strange handling of openssl@3; if I understand
correctly, these tests are expected to fail and should
12 matches
Mail list logo
