seth vidal wrote:
On Tue, 2007-09-18 at 15:42 -0400, James Antill wrote:
then it's just changing the output for a search, right?
That seems like a much better solution to me, yeh. I just wasn't sure
about what the opinion was on breaking backwards compatability on the
UI like that.
Hi!
I realized that the yum release test have to be done by hand some weeks ago.
I now had the time to start translating the wiki page into shell code.
The script requires root privileges. It doesn't have full coverage yet and
the tests that everything is really OK are still a bit weak. May
Florian Festi wrote:
Hi!
I realized that the yum release test have to be done by hand some
weeks ago. I now had the time to start translating the wiki page into
shell code.
The script requires root privileges. It doesn't have full coverage yet
and the tests that everything is really OK are
Tim Lauridsen wrote:
I tested the script with the current yum git master branch
it gives a lot of FAILED (See attached file)
Error: Cannot retrieve repository metadata (repomd.xml) for repository:
fedora. Please verify its path and try again
Hmm, the script currently uses the system's yum
With the recent generation of updateinfo.xml it's become obvious that
info-security is doing the wrong thing, as it displays the entire
updateinfo metadata for each package (when multiple packages can refferr
to the same metadata). This means you can get spammed with the exact
same information
As promised: The next iteration of the script.
Additional notes:
It now covers most test cases from the first list on
http://wiki.linux.duke.edu/YumReleaseTests. Still missing is:
* yum shell (and all sub items)
* yum install somepkg (similar to the yum install somepkg | cat test case)
*
James Antill wrote:
With the recent generation of updateinfo.xml it's become obvious that
info-security is doing the wrong thing, as it displays the entire
updateinfo metadata for each package (when multiple packages can refferr
to the same metadata). This means you can get spammed with the
So currently the only arguments that yum info-security takes are
advisory notices, this patch extends that to fnmatch globs of package
names ... so you can do yum info-security httpd etc.
This also combines some code paths so you can now do:
yum list-security bugzillas httpd
...to just get
