> Yes, sort of:
>
> function is_updated ($up_vers, $debian_vers) {
> if ($up_vers=='') return 0;
> if (!(($debian_vers =~ /\d+\.?/) && ($up_vers =~ /\d+\.?/))) return 0;
> ...
> }
>
> I did some tests and I think that the results of the regex match above
> are flexible enough to not break a
Bluefuture wrote:
Hi Gustavo,
(...)
Btw, I would like to suggest point out (or ommit) the packages where
version naming scheme don't match, like in a52dec. It's the easier
scenario: If the upstream part of the version (upstream or debian)
contains "[a-Z]" and the other doesn't, the version na
Hi Gustavo,
>
>
> What about the false positives like gdm and gnome-screensaver?
>
That page list debian package not in sync with upstream. So if a debian
package has not a well done watch file probably we could have a debian
version more new that the upstream one. I suggest to send a bug with a
Bluefuture wrote:
Hi,
after etch release this is a list of debian packages not in sync with
upstream version[1] with upstream news or changelog data where available
(click on the upstream version number). Packages are sorted with popcon
data.
Great stuff, thanks!
I have also set the dehs "li
Hi,
after etch release this is a list of debian packages not in sync with
upstream version[1] with upstream news or changelog data where available
(click on the upstream version number). Packages are sorted with popcon
data.
I have also set the dehs "live" project directory on alioth readable for
5 matches
Mail list logo
