| Summary: | php-pecl-mcrypt should be named php-mcrypt | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | Marc Krämer <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | php-pecl-mcrypt-1.0.1-5.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2018-10-26 18:35:38 CEST
You're right. Corrected this issue in cauldron and mga6 backports. Thanks. Resolution:
(none) =>
FIXED grr. Have to go eating, I have to rethink this thing. I might have to increase the epoch. Resolution:
FIXED =>
(none) You shouldn't need an epoch. In fact you shouldn't need to do anything special (other than temporarily obsoleting php-pecl-mcrypt to remove it from the repo, but you shouldn't need to keep the obsoletes in after that since it never shipped with that name in a stable release). nope, thats not the point. php-mcrypt was a former internal package, which was built together with php, so the version is 5.6 in mga6. It is not officially supported anymore and was moved to pecl. Now the version is 1.0.1, so the version number is lower than before. And if I'm not missing anything, this is the reason epochs are made for. Oh, I missed the part where it used to be an internal package, sorry. I just saw the failed build attempt for php-mcrypt and forgot. You're absolutely right. Epoch is the way to go. thanks for your advice. Status:
REOPENED =>
RESOLVED |