MADB won't show any newer packages as up to 1st July 2022 (MGA8) and 06.July 2022 (cauldron). See https://madb.mageia.org/rpm/list/listtype/updates/application/0 and https://madb.mageia.org/rpm/list/listtype/updates and https://madb.mageia.org/rpm/list/listtype/updates/release/cauldron/application/0 and Last updated package for MGA8 is "xonotic" from 1st July 2022. Last updated package for cauldron is "eog" from 05. July 2022. For unexperienced users it is nearly impossible to create a bugreport with correct source rpm when MADB shows only outdated versions. (Experienced users can use https://svnweb.mageia.org/packages/ in combination with mirrors or MCC to find correct version numbers but thats not the point here...) Other examples of outdates versions: MADB:virtualbox-6.1.34-1.10.mga8.i586.rpm (Mageia 8, i586 media, core-updates_testing) Reality: virtualbox-6.1.36-1.mga8.i586.rpm (Mageia 8, i586 media, core-updates)
Just fyi, the only part of madb I normally use is http://madb.mageia.org/tools/updates I've never used it to find an srpm. I use rpm -q -i $rpmname|grep ^Source or, if I don't have it installed on this system, "urpmq -i $rpmname|grep ^Source |sort -V", and use the last one listed.
CC: (none) => davidwhodgins
it's sophie on zarb that has stopped updating... @Nanar, can you check it ?
CC: (none) => nanardon
Also, to get a list of rpm packages once I have the srpm name, I use urpmf --sourcerpm $srpm|sort -u For example ... urpmf --sourcerpm libreoffice-7.2.5.2-1.mga8|sort -u Packagers are supposed to include both the list of srpms, and the list of rpm names in any update bug report, to make it easier for the less experienced qa members to participate in testing, especially when we have to rely on a user who is not part of the qa team, such as when specific hardware or knowledge is required.
Thanks David. There is maybe a missunderstanding between us and i described it a little bit onesided when i pointed it down only to source rpm. Lets describe it better in this way: MADB shows no actual package versions since 1st July. An other example (as the one already shown in my initial description): Madb shows as latest kernel (5.15 series): kernel-desktop-5.15.52-1.mga8 According MADB it is still in updates-testing. But in reality we have already kernel-desktop-5.15.55-2.mga8 since 2022-07-20. MADB shows as latest firefox (from 2022-06-28) firefox-91.11.0-1.mga8. https://madb.mageia.org/package/show/application/0/name/firefox But in reality we have firefox-91.12.0-1.mga8 since 2022-07-29 MADB shows no actual package data since one month!
Hello, This is still the case today. For packaging work, this is not comfortable.
CC: (none) => yves.brungard_mageia
You should contact nanardon (see http://sophie.zarb.org/). That's not a Mageia web site…
CC: (none) => thierry.vignaud
It is not optimal madb relies on an external service...
CC: (none) => fri
You do realize that madb also is an external service... Other than that ... feel free to start building a new service :)
Seems fixed...
Resolution: (none) => FIXEDStatus: NEW => RESOLVED