Your message dated Thu, 3 Mar 2022 20:36:50 +0100
with message-id <[email protected]>
and subject line apparently fixed long time ago, but never closed
has caused the Debian Bug report #906744,
regarding /usr/lib/php/20151012/yaml.so: cannot open shared object file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
906744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906744
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php-yaml
Version: 2.0.2+1.3.1-2
Severity: grave
Justification: renders package unusable

php-yaml (2.0.2+1.3.1-2) has a regression over (2.0.0+1.3.0-2+b1):

root@tglase:~ # /usr/lib/php/sessionclean
PHP Warning:  PHP Startup: Unable to load dynamic library 
'/usr/lib/php/20160303/yaml.so' - /usr/lib/php/20160303/yaml.so: cannot open 
shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library 
'/usr/lib/php/20151012/yaml.so' - /usr/lib/php/20151012/yaml.so: cannot open 
shared object file: No such file or directory in Unknown on line 0
PHP Warning:  PHP Startup: Unable to load dynamic library 
'/usr/lib/php/20151012/yaml.so' - /usr/lib/php/20151012/yaml.so: cannot open 
shared object file: No such file or directory in Unknown on line 0

tglase@tglase:~ $ dpkg -L php-yaml | sort
/.
/etc
/etc/php
/etc/php/7.0/mods-available/yaml.ini
/etc/php/7.1/mods-available/yaml.ini
/etc/php/7.2
/etc/php/7.2/mods-available
/etc/php/7.2/mods-available/yaml.ini
/usr
/usr/lib
/usr/lib/php
/usr/lib/php/20170718
/usr/lib/php/20170718/yaml.so
/usr/share
/usr/share/doc
/usr/share/doc/php-yaml
/usr/share/doc/php-yaml/changelog.Debian.gz
/usr/share/doc/php-yaml/copyright

Now, the previous version still had the .so files:

tglase@tglase:~ $ paxtar -xf php-yaml_2.0.0+1.3.0-2+b1_x32.deb -O data.tar.xz | 
paxtar tJf - | sort
.
./etc
./etc/php
./etc/php/7.0
./etc/php/7.0/mods-available
./etc/php/7.0/mods-available/yaml.ini
./etc/php/7.1
./etc/php/7.1/mods-available
./etc/php/7.1/mods-available/yaml.ini
./etc/php/7.2
./etc/php/7.2/mods-available
./etc/php/7.2/mods-available/yaml.ini
./usr
./usr/lib
./usr/lib/php
./usr/lib/php/20151012
./usr/lib/php/20151012/yaml.so
./usr/lib/php/20160303
./usr/lib/php/20160303/yaml.so
./usr/lib/php/20170718
./usr/lib/php/20170718/yaml.so
./usr/share
./usr/share/doc
./usr/share/doc/php-yaml
./usr/share/doc/php-yaml/changelog.Debian.gz
./usr/share/doc/php-yaml/changelog.Debian.x32.gz
./usr/share/doc/php-yaml/copyright

Since the new version *does* ship the mods-available for php 7.0 and 7.1
but does NOT ship the corresponding .so files I consider it a fail to
function for users.


-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages php-yaml depends on:
ii  libapache2-mod-php7.2 [phpapi-20170718]  7.2.9-1
ii  libc6                                    2.27-5
ii  libyaml-0-2                              0.2.1-1
ii  php-common                               1:62
ii  php7.2-cli [phpapi-20170718]             7.2.9-1

php-yaml recommends no packages.

php-yaml suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi,

Closing this bug. It was reassigned and marked fixed after the initial closure, which reopened the bug (in 2018).

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---

Reply via email to