| Summary: | the updates-testing repos are not marked as useable for update | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Philippe Didier <philippedidier> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins |
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpmdrake | CVE: | |
| Status comment: | |||
|
Description
Philippe Didier
2023-09-17 15:06:50 CEST
I close this stupid bug report I should have read the wiki to know how to allow updates from updates-testing repos Resolution:
(none) =>
INVALID For testing updates, rather then enabling updates testing as an updates repo which will result in all testing packages that are updates for packages you already have installed being selected, it's recommended to use qarepo so only the packages listed in the bug report get included. Those packages are the ones that will be moved from updates testing to updates when the update is pushed. https://wiki.mageia.org/en/QA_Repo I do keep one install where I have the testing repos enabled. That's needed to help catch cases where one update being tested will cause a conflict with another update that's being tested, but it shouldn't be done that way for normal testing of an update. CC:
(none) =>
davidwhodgins (In reply to Dave Hodgins from comment #2) > For testing updates, rather then enabling updates testing as an updates repo > which will result in all testing packages that are updates for packages you > already have installed being selected, it's recommended to use qarepo so only > the packages listed in the bug report get included. Those packages are the > ones that will be moved from updates testing to updates when the update is > pushed. > https://wiki.mageia.org/en/QA_Repo > > I do keep one install where I have the testing repos enabled. That's needed > to help catch cases where one update being tested will cause a conflict with > another update that's being tested, but it shouldn't be done that way for > normal testing of an update. Hi Dave For a long time I have been proceeding this way : I downloaded the packages to test From http distrib coffee : https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/8/x86_64/media/core/updates_testing/ I copied them in a local directory and added this local repo in rpmdrake with the Mageia distrib key Then try to install them It worked for Mageia8 For mock packages inside Mageia9 I have proceed the same way from the same mirror https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/x86_64/media/core/updates_testing/ (I have tried to enable the updates-testing repo inside rpmdrake, this didn't work so I went back to my old process) But that's how I got a problem with the invalid gpgkey https://bugs.mageia.org/show_bug.cgi?id=32230 Maybe a mirror problem ? Doesn't look like it http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/x86_64/media/core/release/distribution-gpg-keys-1.89-1.mga9.noarch.rpm Sorry for the noise... And thanks for your answers the problem was between the chair and the keyboard I can always download and copy the updated rpms to test in a local directory and add this local repo in rpmdrake with the Mageia distrib key as I did before No need to enable updates-testing repo for updates |