Bug 531717

http://git.fedorahosted.org/git/?p=mash;a=commitdiff;h=71baa6362d91056f7a6ced6c268b801051709f55

Added, will show up in rawhide eventually.

> blacklist = ['dmraid-devel', 'ghc-devel', ...

There is no ghc-devel package.  Can blacklist use '*'?
It should be 'ghc-*-devel'.

Not as of now, unfortunately.

This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Still true for F15.

New problem: since ghc-*-prof is not multilib but
since ghc-*-devel is and we started merging ghc-*-prof into
ghc-*-devel this is breaking repoclosure for new
ghc-*-devel.i686 packages in x86_64.  (This only affects
F15 and earlier: F16 doesn't have any ghc-*-prof packages any more.)

The last comment is obsolete or no longer true.

This is still causing problems for yum, autoqa, and repoclosure
of packages in updates-testing, etc.

How about this patch?:

diff --git a/mash/multilib.py b/mash/multilib.py
index cd4ff01..011a6e7 100644
--- a/mash/multilib.py
+++ b/mash/multilib.py
@@ -182,6 +182,8 @@ class DevelMultilibMethod(RuntimeMultilibMethod):
             for (p_name, p_flag, (p_e, p_v, p_r)) in po.provides:
                 if p_name == 'kernel-devel':
                     return False
+        if po.name.startswith('ghc-') and po.name.endswith('-devel'):
+            return False
         if po.name.endswith('-devel'):
             return True
         return False

Recent example of problem in autoqa:

http://autoqa.fedoraproject.org/results/283643-autotest/qa07.qa.fedoraproject.org/depcheck/results/haskell-platform-201.html

(In reply to comment #8)
> +        if po.name.startswith('ghc-') and po.name.endswith('-devel'):
> +            return False
>          if po.name.endswith('-devel'):
>              return True
>          return False

Hmm, I guess:

          if po.name.endswith('-devel') and not po.name.startswith('ghc-'):
              return True
          return False

would be simpler and maybe more efficient.

Why not just:

        if po.name.startswith('ghc-'):
            return False

?

(In reply to comment #11)
>         if po.name.startswith('ghc-'):
>             return False
> 
> ?

Ok sure, I think that should work fine too. :)

(I was just targeting "ghc-*-devel" explicitly since I think
the devel packages are the ones triggering multilib, but probably
that function is not too computationally intensive anyway?)

Committed to master.

Thanks - when do you think this change will go into production?

Not sure, is there a rush?

Note that the packages that are currently in the tree dropping out could conceivably cause some upgade issues that would need to be worked around.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This looks fixed in the F18 release.

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.