Description of problem: In some bugs this tool fail to fill subject and source fields with accurate information. By example bug#33413 Field subject is "Updated java java java java-latest-openjdk packages fix security vulnerabilities", and source field is empty. Bug#33409 , subject field is "Updated 0 0 packages fix security vulnerabilities" and source field is empty Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run mga-advisor 2. in bug number field put one of the bugs refered if are not solved yet 3. click on retrive info 4. see the error described
Hi katnatek, Subject field is populated with a list of packages recovered from Source RPM field. The two defects are in fact the same misbehavior. A regular expression is applied to the names read in Source RPM. This rule detect a first occurrence of a dash followed by a number and keep what is before which include any word, _, -, +. The aim is to have the source name, without version nor release extension. Dot is not considered as valid in the name. In cases of java-1.8.0-openjdk, part -1.8.0-openjdk is seen as a version/release number, thus is removed and we get only "java". In case of gtk+2.0-2.24.33-5.mga9.src.rpm, the dot of 2.0 is not included in the part name, thus the name is reduced to the 0 after the dot. If I include the dot as possible character in the name, I catch the version number with the name, and I don't want that. I don't any solution as I think that these names are ambiguous. Perhaps some rpm gurus how to deal with that. For now, I suggest to leave this corner case as is.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33729
Before open other bug Since maybe the relocation of servers, the tool become too slow to get the information of the bugs Exist a way to debug/find the cause?
I have done a branch for usage with libdnf5. This is based on: - getting the packages cited in Source RPM field, - extracting the name - searching the package in Testing reposotories having said name - adding the source package names removing .src at end. File dnfmadbbase comes from MADb config.py.in has to be copied in config.py and adapted to the location where dnf cache will be written and to the mirror to use.