| Summary: | ifuse needed for ios devices. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Patrick Hibbs <codebase7> |
| Component: | New RPM package request | Assignee: | Juan Luis Baptiste <juan.baptiste> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | as9902613, mageia, rverschelde |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Patrick Hibbs
2013-04-25 03:04:27 CEST
Assigning to Juancho as he imported it in cauldron: http://svnweb.mageia.org/packages/cauldron/ifuse/ Status:
NEW =>
ASSIGNED In progress, related bug: 10338 The package is ready and I have tested it with an amarok updated package (see bug 10338) and works fine. Now the issue is that backports aren't open yet, so there it seems there's no way to have it available on mga 3 repos for now until there's a decision about the backports repository. Backport is for new release of packages. As ifuse was not available in 3, I think you can provide it as an update. I did it in the past for other requests. I would agree with Damien. It's debatable of course. This is fixing a bug for common hardware which we already attempt and fail to support properly, rather than just introducing it because you'd like to see it in 3, so can go as an update rather than backport. No resistance to doing so here at least. Ok, I always thought that new packages couldn't be introduced to a stable release as I couldn't submit for example to core/release, and backports are still closed. So can I submit ifuse to core/updates_testing without issues ? if true I'll do it later when I have access to one of my mga 3 systems. That's right Juan. Ordinarily introducing a new package would be a backport but I think this is actually a bug fix and could go through updates. We do support this hardware, just fail at the moment. You can see our updates policy here: https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29 There is a case for it being update and a case for it being backport. You could always ask on dev ML for more opinions. I know the policy and that case isn't explictly mentioned, the closest one is this: "We will make exceptions for packages that did not make it into mga1 and are additions to the distribution, provided they do not impact any other packages and can pass full QA." It should be updated (or changed now that mga 1 is EOL) to say something like: "We will make exceptions for packages that are additions to the distribution but needed by an existing package to add important functionality, provided they do not impact any other packages and can pass full QA." WDYT ? Me too i am with the impression that the policy is "a new rpm cannot be added" but only can be added in backports. CC:
(none) =>
dglent Is there any progress on whether this should be provided as an update to Mageia 3? CC:
(none) =>
remi I think we should go ahead and push it to core/updates_testing, fixing this missing feature is crucial. When is this fix coming to MGA3? I desperately need it. CC:
(none) =>
as9902613
Dimitrios Glentadakis
2014-07-01 06:45:45 CEST
CC:
dglent =>
(none) To prepare the update, I suppose I should use mga 4 version of ifuse and not cauldron's to avoid breaking future upgrades ? Mageia 3 is EOL. I believe this was fixed in Mageia 4. Please re-open and change the version assignment if that's not the case. Status:
ASSIGNED =>
RESOLVED |