Just another headshup:
I'll push php7 and php-8 package to staging today. I'll create a
rebuild list for all modules. Once this is done I would move them to
[testing] and we can check the scripts we provide for PHP 8
compatibility and update their dependency for PHP 7 if needed.
Greetings,
Pierr
The module rebuild todo list is now available at
https://archlinux.org/todo/php-8-and-php7-module-rebuild/
On Fri, Jan 8, 2021 at 5:11 PM Pierre Schmitz wrote:
>
> Just another headshup:
>
> I'll push php7 and php-8 package to staging today. I'll create a
> rebuild list for all modules. Once this
I will soon move the packages to [testing]. Thanks for everybody
helping out. I'll then set up a todo list to check for compatibility
with packages depending on PHP.
Some notes:
* I have built xdebug for PHP8; I'll let the maintainer decide if a
php7 version might be of use
* I will simply drop ph
php7 is now in [extra] an php 8 and the rebuilt modules are available
in [testing].
I have created a new todo list to check compatibility of packages that
depend on PHP: https://archlinux.org/todo/php-8-compatibility/
Greetings,
Pierre
On Sat, Jan 16, 2021 at 3:05 PM Pierre Schmitz wrote:
>
>
To speed things up I'll go ahead and update the remaining packages to
my best knowledge. I'll also send a news draft later.
Greetings,
Pierre
On Mon, Jan 18, 2021 at 6:51 PM Pierre Schmitz wrote:
>
> php7 is now in [extra] an php 8 and the rebuilt modules are available
> in [testing].
>
> I hav
Thank you for you working on Arch for such a long time.
Take care,
Pierre
On Thu, Jan 21, 2021 at 2:08 PM Bartłomiej Piotrowski via
arch-dev-public wrote:
>
> Hi everyone,
>
> I'm stepping down as a developer. It's been mostly fantastic ride for
> the last 10 years but it's clear to me now that
Hi all,
I'd like to move the PHP 8 rebuild to [extra] soon. Here is a little
news draft to mainly inform users about the new php7 package for
legacy software:
---
The php package has been updated to version 8.0(1). Please refer to
the upstream migration guide(2). As some applications are not
comp
stall them. I'll probably post
this tomorrow or the day after.
Greetings,
Pierre
On Mon, Jan 25, 2021 at 8:19 PM Chester Wisniewski wrote:
>
> I would recommend changing "postfix" to suffix. Postfix is a package, suffix
> works better in English.
>
> Chester
>
&g
Hi all,
while reading Allan's RFC about increasing Arch's CPU requirements(*)
I had the idea to start tracking the different x86_64 architecture
level using pkgstats. I am sure whether to drop support for old CPUs
is not a matter of "if" but "when"; similar as it was with i686.
Therefore it should
I just updated the server to also accept x86_64 feature levels, ARM
and even i686. There is a new version of pkgstats (>= 3.1.0; currently
in [testing]) which is able to detect feature levels. ARM support is
pretty early, but x86_64 should be fine (using Intel's cpuid library).
If you like to chec
-public
> wrote:
> >
> > On 3/14/21 3:07 PM, Pierre Schmitz via arch-dev-public wrote:
> > > I just updated the server to also accept x86_64 feature levels, ARM
> > > and even i686. There is a new version of pkgstats (>= 3.1.0; currently
> > > in [tes
Hi all,
Since Aug 30 07:17:11 CEST the "community.files" database
(repos.archlinux.org/community/os/x86_64/community.files) seems to be
corrupted. The package "ipguard-1.04-6" has an empty "desc" file. The
"files" file has content though. Also the regular "community.db" file
does seem fine. I also
o community. I have kept a copy of the
> broken files db if anyone wants it, but it seems that
> "ipguard-1.04-6/desc" had 1230 NUL bytes instead of 1230 bytes of
> package details.
>
> On Mon, 30 Aug 2021 at 13:58, Pierre Schmitz via arch-dev-public
> wrote:
> >
&g
Hi all,
I did have some trouble build the current ISO image. As archiso
requires to be run as root I had to work around some issues with GPG.
As those did no longer work I thought I manually sign the artifacts.
This did work fine, but later on I noticed that when using Netboot
(PXE), mkinicpio-arc
On Mon, Nov 1, 2021 at 5:10 PM David Runge wrote:
> ... use an ephemeral PGP key (which is fine, as
> it is not relevant whether it is a specific PGP key, only that the
> *correct* PGP key is used to validate the root image).
Thanks for your insights. I think I now found the missing peaces.
Using
Hi Jelle, (also forwarding to dev-public)
definitely yes, OpenSSL 3.0 is on my wish list! :-)
I did not want to jump on it at day one though. Even the last minor
updates were quite painful and we still have packages requiring
version 1.0 and are still not compatible with 1.1.
While they claim th
Hi all,
a little heads up as it takes longer than expected. I'll start the PHP
8.1 update and the required rebuilds soon. I noticed some unexpected
incompatibilities and I'd like to look into these first. I'll also
evaluate if we could drop the php7 packages at the same time.
Greetings,
Pierre
deprecations but no hard errors).
Greetings,
Pierre
On Mon, Dec 6, 2021 at 6:13 PM David Runge via arch-dev-public
wrote:
>
> On 2021-12-06 17:58:57 (+0100), Levente Polyak via arch-dev-public wrote:
> > On 12/6/21 17:48, David Runge via arch-dev-public wrote:
> > > On 2021-1
just a small update: This is going to be a little more complicated and
I suggest we tackle this at the beginning of next year. I got some
very helpful feedback from our community (Thanks a lot loqs).
* We might be able to drop version 1.0 (which is no longer maintained
by upstream anyway). packages
eady existed
==> WARNING: Repo lock [community] (x86_64) was not locked!
Greetings,
Pierre
On Mon, Aug 30, 2021 at 11:56 PM David Runge wrote:
>
> On 2021-08-30 22:35:39 (+0200), Pierre Schmitz via arch-dev-public wrote:
> > Thanks for looking into this. It's still weird but
Thanks a lot for your work! I already managed to migrate to OpenSearch
without major issues.
I am a little confused about the java dependency. It requires
java-runtime instead of java-runtime-headless as Elasticsearch did.
However on launch I get the following warning: "no-jdk distributions
that d
New version was just released and claims
to support anything newer than PHP 7.2
* dokuwiki: unclear; might need patches
Greetings,
Pierre
On Mon, Dec 6, 2021 at 6:53 PM David Runge wrote:
>
> On 2021-12-06 18:32:49 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > In general we c
PHP 7.2
> * dokuwiki: unclear; might need patches
>
> Greetings,
>
> Pierre
>
> On Mon, Dec 6, 2021 at 6:53 PM David Runge wrote:
> >
> > On 2021-12-06 18:32:49 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > > In general we could provide PHP 7 till
a follow up:
* Retiring OpenSSL 1.0 will take place here:
https://archlinux.org/todo/openssl-10-retirement/ This wont affect the
1.1 -> 3.0 transition though.
* I have placed an openssl-1.1 package into [staging] that should make
it easier to migrate as it provides the 1.1 version of libcrypto.so
Hi David,
I am very sorry. I misjudged the urgency of this topic. I assumed
signing the additional uid is more a "ncie to have", since pacman and
wkd already works fine. I opened the ticket at
https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/143
so we can create the merge requests
r stalled on PHP
> > 8 support. We might need to drop this as well
> > * phpldapadmin: might work. New version was just released and claims
> > to support anything newer than PHP 7.2
> > * dokuwiki: unclear; might need patches
> >
> > Greetings,
> >
> > Pierre
>
Thanks! Let me know if I may support you. Wrangling with PHP scripts
is at least more fun than using gpg...
On Sun, Jan 16, 2022 at 5:03 PM David Runge wrote:
>
> On 2022-01-16 16:40:00 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > So far everything looks fine. I am even u
Runge wrote:
>
> On 2022-01-16 17:11:44 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > Thanks! Let me know if I may support you.
>
> It went quite okay (but I had to remove parts of the patch series as
> they apply to files that we do have in our tarball).
>
> n
wrote:
> >
> > On 2022-01-16 17:11:44 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > > Thanks! Let me know if I may support you.
> >
> > It went quite okay (but I had to remove parts of the patch series as
> > they apply to files that we do have in our tar
would end up with more packages we need less testing and will be
able to move faster.
*) https://www.php.net/supported-versions.php
On Sat, Jan 22, 2022 at 10:57 AM David Runge wrote:
>
> On 2022-01-21 17:51:17 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > I just relea
On Sat, Jan 22, 2022 at 9:45 PM David Runge wrote:
> On 2022-01-22 20:45:45 (+0100), Pierre Schmitz via arch-dev-public wrote:
> ...
> > 1) Let's no longer package software that requires older versions of
> > PHP. Personally I would run such complex software with very
Hi all,
I have prepared a openssl-3.0 and 1.1 packages with the bootstrapped
dependencies. In addition to this there is a hopefully complete todo
list: https://archlinux.org/todo/openssl-30/ containing about 500
packages.
Next steps:
1) Let's agree on a time window where no other rebuild can take
ys two versions apart.
> >
> > I would give option 3 a try. I'd like to get rid of versioned
> > constraints then and reduce the amount of third party modules. While
> > we would end up with more packages we need less testing and will be
> > able to move faster.
&g
On Sat, Jan 29, 2022 at 2:49 PM Allan McRae via arch-dev-public
wrote:
> Assuming we need people to help the x86_64_v3 port, I would post a news
> item and have people apply. We have advertised developer positions in
> the past and received dozens of applications, and readily filled the
> availab
ia arch-dev-public
> wrote:
> > Pierre Schmitz via arch-dev-public
> > on
> > Sun, 2022/01/23 12:50:
> > > Next steps:
> > > 1) Let's agree on a time window where no other rebuild can take
> > > place
> > > within our staging repos. How
Christian Hesse wrote:
>
> Pierre Schmitz via arch-dev-public on
> Sun, 2022/01/23 12:50:
> > Next steps:
> > 1) Let's agree on a time window where no other rebuild can take place
> > within our staging repos. How about at least the first two weeks in
> > Feb
I'd still suggest to provide two different php versions as mentioned
some time ago: the current "php" and "php-legacy" which will always be
the oldest supported version. These may provide the versions as you
suggested: php-legacy provides php=7.4 (and will be updated to 8.0
soon)
The benefit of no
37 matches
Mail list logo
