Hello, On Mon, 19 Nov 2018 at 02:20, Helmut K. C. Tessarek <tessa...@evermeet.cx> wrote: > > 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. > */ >
Hello, I've recently done quite some upgrades to the app including partial migration to PDO, but am not sure yet why is this one happening exactly... It seems like the XML files haven't got updated when the releases were done. Is it possible that the script /path/to/pecl/project/root/generatePECL_REST.php is a cron job? If someone with access to the server can confirm this and set it to run the new location of: /path/to/pecl/project/root/bin/generate-rest.php https://github.com/php/web-pecl/blob/master/bin/generate-rest.php Another option is also that the environment variable for setting the xml folder is used on the server and the configuration doesn't match... I've pushed a quick revert of the possible cron job script to the repo to see if this updates the xml files... -- Peter Kokot
