Bug 1126399

Summary:	basename() returns wrong result
Product:	[Fedora] Fedora	Reporter:	David Anderson <fedora-packaging2>
Component:	php	Assignee:	Remi Collet <fedora>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	fedora, jorton
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-30 01:06:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Anderson 2014-08-04 10:39:21 UTC

Description of problem:

PHP's basename() function returns the wrong result in certain cases (simple test case available).

The PHP developer responding to the relevant PHP bug says that PHP's basename() is just passing through to glibc's basename(), and that the bug is in glibc.

Please see: https://bugs.php.net/bug.php?id=62119

That bug references Debian, but the same issue is reproducible on Fedora 20:
https://bugs.php.net/bug.php?id=67756 (I opened a new bug there because the original bug was reported against PHP 5.3, which is EOL-ed).

Comment 2 Jakub Jelinek 2014-08-04 15:20:17 UTC

I think basename just calls strrchr, which is not locale dependent, so if PHP's basename is locale dependent, I don't see how the problem could be on the glibc side.

Comment 3 Siddhesh Poyarekar 2014-08-05 16:30:18 UTC

Doesn't look like there's a call to the basename function in the reproducer based on my crude test of running it in gdb, setting a breakpoint on basename() and running it.  Reassigning to php to get a reproducer that is definitely known to use the basename function.

Comment 4 Fedora End Of Life 2015-05-29 12:33:33 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-06-30 01:06:25 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.