Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1288176
| From | Guilhem Moulin <guilhem@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1129016: [pkg-php-pear] Bug#1129016: php-net-ldap2: Version 2.3.0-4 dep8 failures with PHP 8.5 |
| Date | 2026-04-02 10:50 +0200 |
| Message-ID | <MFlUt-c6q5-7@gated-at.bofh.it> (permalink) |
| References | <MstPQ-3ijl-9@gated-at.bofh.it> <Muglr-4vVe-21@gated-at.bofh.it> <MstPQ-3ijl-9@gated-at.bofh.it> <Muglr-4vVe-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Mon, 02 Mar 2026 at 15:29:26 -0300, Renan Rodrigo wrote:
> So passing null means we are not requesting any specific attributes, and
> passing an empty array should work the same, right?
> I tested it with just `[]` and it passed.
Tried it now (with PHP8.4.16 from Debian sid). The empty array appears
to needlessly return all user attributes, so I changed [0] the patch to
use `['1.1']` instead.
With PHP8.4 `['1.1']` works like `[null]` (but the latter is
undocumented and ceases to work with PHP8.5). AFAICT ldap_search(3) is
unclear how an empty attribute array is treated, but is clear [1] that
`{LDAP_NO_ATTRS, NULL}` should be used to avoid fetching any attribute.
--
Guilhem.
[0] https://salsa.debian.org/php-team/pear/php-net-ldap2/-/commit/9b909f5a6a7c0bdad04f11c8ae758990c89d8ca4
[1] https://manpages.debian.org/unstable/libldap-dev/ldap_search_ext.3.en.html#DESCRIPTION
Back to linux.debian.bugs.dist | Previous | Next | Find similar
Bug#1129016: [pkg-php-pear] Bug#1129016: php-net-ldap2: Version 2.3.0-4 dep8 failures with PHP 8.5 Guilhem Moulin <guilhem@debian.org> - 2026-04-02 10:50 +0200
csiph-web