# PECL seems to ignore newer packages

- Thread: https://externals.io/message/103450
- Original archive: https://news-web.php.net/php.internals/103450
- Started by Helmut K. C. Tessarek on 2018-11-19T01:36:10+00:00
- Messages: 3
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #103450 — Helmut K. C. Tessarek — 2018-11-19T01:36:10+00:00

URL: https://externals.io/message/103450#103450

First of all I'm sorry that I'm cross-posting this issue, but it looks
like there are never any replies in pecl-dev (after reading and checking
the archives) and I couldn't find any other mailing list where I could
post this issue to.

There's no support page for php/pecl infrastructure issues (at least I
couldn't find it), thus here I am.

For a while now PECL ignores newer packages and thinks that older
packages are the most recent ones.

e.g. I have the following packages installed:

# pecl list
INSTALLED PACKAGES, CHANNEL PECL.PHP.NET:
=========================================
PACKAGE   VERSION STATE
libsodium 2.0.13  stable
redis     4.1.1   stable

When I try to insall/upgrade to the latest libsodium, I get the
following messages:

# pecl install libsodium
pecl/libsodium is already installed and is the same as the released
version 2.0.13
install failed

# pecl upgrade libsodium
Nothing to upgrade

This is wrong, since the latest version is 2.0.15.

I can't upgrade redis either.

Then I tried to install a new package (which I haven't installed yet):

# pecl install yaml
downloading yaml-2.0.2.tgz ...

As you can see, it tries to install 2.0.2, while the latest version is
actually 2.0.3.

Something is seriously off, but I don't know how to fix this, since it
looks like an issue on the server.
Can someone please explain to me what's going on?

Cheers,
  K. C.

-- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the `NULL` pointer for chaos and madness
   await thee at its end.
*/

---

## #103451 — Helmut K. C. Tessarek — 2018-11-19T03:52:09+00:00

URL: https://externals.io/message/103450#103451 · In reply to: #103450

> First of all I'm sorry that I'm cross-posting this issue, but it looks
> like there are never any replies in pecl-dev (after reading and checking
> the archives) and I couldn't find any other mailing list where I could
> post this issue to.
> 
> There's no support page for php/pecl infrastructure issues (at least I
> couldn't find it), thus here I am.

Please ignore. I got a reply on pecl-dev, which is truly amazing.


-- 
regards Helmut K. C. Tessarek              KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944

/*
   Thou shalt not follow the `NULL` pointer for chaos and madness
   await thee at its end.
*/

---

## #103457 — Christoph M. Becker — 2018-11-19T13:08:22+00:00

URL: https://externals.io/message/103450#103457 · In reply to: #103450

> There's no support page for php/pecl infrastructure issues (at least I
> couldn't find it), thus here I am.

You can file bug reports on <https://bugs.php.net/> for such issues.  If
you choose “PECL” as affected package, respective mails will also be
sent to pecl-dev.

-- 
Christoph M. Becker