¡Hola Mr! El 2016-05-15 a las 09:44 +0000, Mr riaas mokiem escribió:
I think it might be possible to work around the uscan bug by only having the URL for stable releases in the watch file. This means you no longer track the unstable releases but it should almost certainly work.
You may also be able to track both stable and unstable releases with 1 URL:http://download.kde.org/(?:un)?stable/plasma/([\d.]+)/libksysguard-([\d.]+) \.tar\.xz
Currently that only checks the unstable versions, as uscan decides which subtrees would visit on every pattern, in the (unstable|stable) case it simply selects unstable as its greater than stable.
Uscan would need to check every pattern alternative for this to work correctly, which is not main use case of uscan and can be easily become overkill.
In particular for the kde packages, I'm not sure if we want to track the unstable versions with uscan at all.
As mentioned before, I think this problem may affect many other KDE packages, mostly from Plasma and Frameworks. The KDE Applications seem to be fine since most of those only seem to track the stable URL.
I think that I've already removed the unstable paths from the watch files for framewors, plasma and apps, in my work in progress repos, that I'm planning to upload shortly.
Happy hacking, -- "The sooner you start to code, the longer the program will take." -- Roy Carlson Saludos /\/\ /\ >< `/
Attachment:
signature.asc
Description: Digital signature