#1680: [freeze break] Tag Fixes for F11 Mass Rebuild Failures

[Fedora Release Engineering]

#1680: [freeze break] Tag Fixes for F11 Mass Rebuild Failures
------------------------------+---------------------------------------------
  Reporter:  mjakubicek       |       Owner:  rel-eng at lists.fedoraproject.org
      Type:  task             |      Status:  new                            
 Milestone:  Fedora 11 Final  |   Component:  koji                           
Resolution:                   |    Keywords:                                 
------------------------------+---------------------------------------------
Comment (by mjakubicek):

 Replying to [comment:1 rdieter]:
 > My that's a lot.  I'd tend to think that shipping packages that are
 actually buildable (and benefit from the mass rebuild and all) is
 generally a good thing, despite the lack of testing here (in alpha, beta).

 I should note here that I believe that the fixes I've made were indeed
 rather small (however sometimes not trivial to find out:), they mostly
 consist of following items:

  * gcc 4.4 header includes & glibc changes (const char* vs. char* etc.)
  * mono one-line patches
  * java patches to avoid naming variables as "enum" since this is a
 reserved word in java >= 1.5
  * java missing BR (if there is another way how to find out what package
 provides foo.bar.baz java package than querying java-people like lkundrak
 and dbhole who then grep all they .jars for the given string, I (and they
 too:) would be happy to know about)
  * other missing BR.

 I've also tried to fix trivial bugs that were assigned to the given
 packages, like missing requires and similar.

 ...and yes, all the patches I've made have been upstreamed (bugtracker,
 mailing list, author e-mail, in this availability order) except of
 packages which were really outdated, in that case, this is clearly noted
 along with the PatchX: line in the spec file ("Not sent upstream, please
 update the package first." -- or similar comments).

 One exception is itpp-4.0.6-1.fc11, which (as can be seen from the release
 number) has been updated to the next maintenance release (4.0.0 => 4.0.6).

 To sum up: I don't think that these new builds contain something bad that
 was not there before;)

 > +1 (ish)
 >
 > As an aside, I'm concerned about the maintainers of these packages not
 being responsive during f-11 development...

 Me too -- some of them have currently inactive accounts as I received
 undeliverable e-mail notification after the commit, but many probably just
 don't care, or even don't know there is something bad with their packages
 (even some which are @redhat.com -- I tried to contact those people via
 IRC, some of them promised to fix their packages).

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1680#comment:2>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project