So, when trying to upload the latest Xdebug release I get this
incorrect nonsense preventing me from making a release:
ERROR:
The compliance between the package version in package.xml and
extension source code couldn't be reliably determined. This check fixes
the (unintended) version mismatch in `phpinfo()` and the PECL website.
To pass please #define PHP_MYEXTNAME_VERSION "2.2.4" in your
php_myextname.h or any other header file and use it for
zend_module_entry definition.
Both version strings have to match.
This pisses me off. Do not ever block uploads because of some arbitrary
rule of how you should think my code should look like. The versions
numbers are correct and properly defined with a constant:
php_xdebug.h:#define XDEBUG_VERSION "2.2.4"
Requiring that this constant should ahve PHP in it is stupid and
arbitrary decision that doesn't help anybody. If and only if you want
to enforce those rules, do it in the package state, and never when
everything is ready to go to just be rejected.
Besides that, the code that checks for this doesn't seem to be in PECL
web either:
derick@whisky:~ $ cd dev/php/peclweb
[GIT: master]
derick@whisky:~/dev/php/peclweb $ git remote -v
origin git@git.php.net:/web/pecl.git (fetch)
origin git@git.php.net:/web/pecl.git (push)
[GIT: master]
derick@whisky:~/dev/php/peclweb $ git pull
Already up-to-date.
[GIT: master]
derick@whisky:~/dev/php/peclweb $ grep -r "compliance between" *
It looks like the last commit was in december 2012 which is clearly a lie.
Where is the current code?
cheers,
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine
So, when trying to upload the latest Xdebug release I get this
incorrect nonsense preventing me from making a release:ERROR: The compliance between the package version in package.xmland
extension source code couldn't be reliably determined. This check
fixes
the (unintended) version mismatch inphpinfo()and the PECL
website.
To pass please #define PHP_MYEXTNAME_VERSION "2.2.4" in
your
php_myextname.h or any other header file and use it for
zend_module_entry definition.
Both version strings have to match.This pisses me off. Do not ever block uploads because of some arbitrary
rule of how you should think my code should look like. The versions
numbers are correct and properly defined with a constant:php_xdebug.h:#define XDEBUG_VERSION "2.2.4"Requiring that this constant should ahve PHP in it is stupid and
arbitrary decision that doesn't help anybody. If and only if you want
to enforce those rules, do it in the package state, and never when
everything is ready to go to just be rejected.Besides that, the code that checks for this doesn't seem to be in PECL
web either:derick@whisky:~ $ cd dev/php/peclweb [GIT: master] derick@whisky:~/dev/php/peclweb $ git remote -v origin git@git.php.net:/web/pecl.git (fetch) origin git@git.php.net:/web/pecl.git (push) [GIT: master] derick@whisky:~/dev/php/peclweb $ git pull Already up-to-date. [GIT: master] derick@whisky:~/dev/php/peclweb $ grep -r "compliance between" *It looks like the last commit was in december 2012 which is clearly a lie.
Where is the current code?cheers,
Derick--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine--
the current code is in the old_auth branch.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
So, when trying to upload the latest Xdebug release I get this
incorrect nonsense preventing me from making a release:ERROR: The compliance between the package version in package.xmland
extension source code couldn't be reliably determined. This check
fixes
the (unintended) version mismatch inphpinfo()and the PECL
website.
To pass please #define PHP_MYEXTNAME_VERSION "2.2.4" in
your
php_myextname.h or any other header file and use it for
zend_module_entry definition.
Both version strings have to match.This pisses me off. Do not ever block uploads because of some arbitrary
rule of how you should think my code should look like. The versions
numbers are correct and properly defined with a constant:php_xdebug.h:#define XDEBUG_VERSION "2.2.4"Requiring that this constant should ahve PHP in it is stupid and
arbitrary decision that doesn't help anybody. If and only if you want
to enforce those rules, do it in the package state, and never when
everything is ready to go to just be rejected.Besides that, the code that checks for this doesn't seem to be in PECL
web either:derick@whisky:~ $ cd dev/php/peclweb [GIT: master] derick@whisky:~/dev/php/peclweb $ git remote -v origin git@git.php.net:/web/pecl.git (fetch) origin git@git.php.net:/web/pecl.git (push) [GIT: master] derick@whisky:~/dev/php/peclweb $ git pull Already up-to-date. [GIT: master] derick@whisky:~/dev/php/peclweb $ grep -r "compliance between" *It looks like the last commit was in december 2012 which is clearly a lie.
Where is the current code?cheers,
Derick--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
Posted with an email client that doesn't mangle email: alpine--
the current code is in the old_auth branch.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446
And this has been defined for years. So far Derick is the only one to
complain about this check (not sure how long it has been there) but
this definitively prevents the frequent releases with wrong version
numbers.
Also this is a pecl issue, not internals btw.
Cheers,
Pierre
@pierrejoye | http://www.libgd.org
and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446And this has been defined for years. So far Derick is the only one to
complain about this check
Lies. The thread that discusses that (which is definitely not years
ago), has at least two other people arguing against an arbitraty block.
So not the first. Stop making shit up like "it has been defined for
years".
Also this is a pecl issue, not internals btw.
I don't care whether you think it is not an internals thing or not. I
think it is relevant, as it once again shows how you manage to frustrate
contributors.
cheers,
Derick
and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446And this has been defined for years. So far Derick is the only one to
complain about this checkLies.
Indeed... not
The thread that discusses that (which is definitely not years
ago), has at least two other people arguing against an arbitraty block.
So not the first. Stop making shit up like "it has been defined for
years".
Steph did it, and it was more than 2 years ago, so "years ago" is correct.
Also this is a pecl issue, not internals btw.
I don't care whether you think it is not an internals thing or not. I
think it is relevant, as it once again shows how you manage to frustrate
contributors.
Do I? I only managed to get many distributions happier and users to
get correct versions and package meta. You managed to waste many
people precious time by pestering about a non issue, only because you
are too lazy to apply simple rules. So please, re consider both the
way you do things like that and your language, which actually annoy
much more contributors than you may actually admit.
Cheers,
Pierre
@pierrejoye | http://www.libgd.org
So, when trying to upload the latest Xdebug release I get this
incorrect nonsense preventing me from making a release:ERROR: The compliance between the package version in package.xmland
extension source code couldn't be reliably determined. This check
fixes
the (unintended) version mismatch inphpinfo()and the PECL
website.
To pass please #define PHP_MYEXTNAME_VERSION "2.2.4" in
your
php_myextname.h or any other header file and use it for
zend_module_entry definition.
Both version strings have to match.This pisses me off. Do not ever block uploads because of some arbitrary
rule of how you should think my code should look like. The versions
numbers are correct and properly defined with a constant:php_xdebug.h:#define XDEBUG_VERSION "2.2.4"and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446
Perhaps, I don't mind a check for an incorrect version, but when you
decide to block things because you can not determine anything, then it's
just stupid. Hannes very nicely summed that up in this post (even though
that is about the LICENSE file requirement).
http://permalink.gmane.org/gmane.comp.php.pecl.devel/10336
and in:
http://permalink.gmane.org/gmane.comp.php.pecl.devel/10339
And Johannes in (more on topic with the version nr):
http://permalink.gmane.org/gmane.comp.php.pecl.devel/10342
But the problem is not checking for it, the problem is blocking an
upload of a package that is perfectly valid and correct.
cheers,
Derick
So, when trying to upload the latest Xdebug release I get this
incorrect nonsense preventing me from making a release:ERROR: The compliance between the package version in package.xmland
extension source code couldn't be reliably determined. This check
fixes
the (unintended) version mismatch inphpinfo()and the PECL
website.
To pass please #define PHP_MYEXTNAME_VERSION "2.2.4" in
your
php_myextname.h or any other header file and use it for
zend_module_entry definition.
Both version strings have to match.This pisses me off. Do not ever block uploads because of some arbitrary
rule of how you should think my code should look like. The versions
numbers are correct and properly defined with a constant:php_xdebug.h:#define XDEBUG_VERSION "2.2.4"and here is a link to the relevant discussion about this change:
http://comments.gmane.org/gmane.comp.php.devel/82446Perhaps, I don't mind a check for an incorrect version, but when you
decide to block things because you can not determine anything, then it's
just stupid. Hannes very nicely summed that up in this post (even though
that is about the LICENSE file requirement).http://permalink.gmane.org/gmane.comp.php.pecl.devel/10336
and in:
http://permalink.gmane.org/gmane.comp.php.pecl.devel/10339
And Johannes in (more on topic with the version nr):
http://permalink.gmane.org/gmane.comp.php.pecl.devel/10342
But the problem is not checking for it, the problem is blocking an
upload of a package that is perfectly valid and correct.
The package is not correct, while working.
We have discussed the naming and this requirement years ago. Many
developers have annoyed by the lack of checks for the version, license
or other things making the package meta information wrong. This has
been a disturbing point for our users and distributions. Now you moved
the checks to warning, allowing one to release invalid packages,
without even waiting for a reply or answer. Just like what happened
last time for the license check. This is an unacceptable behavior. And
that pisses us off, if I may use the same wording that you do.
Please update your code and that's it. There is no point to discuss or
argue about this for ages while it takes you 5 seconds to do it, even
more as you are the only one complaining about that.
Cheers.
Pierre
@pierrejoye | http://www.libgd.org