[Bug 1181366] Review Request: mumble - Voice chat suite aimed at gamers (un-retire)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1181366



--- Comment #8 from Peter Robinson <pbrobinson@xxxxxxxxx> ---
> > I'm up to nothing with mumble. If you read the change log it's a mass
> > rebuild. 
> 
> Why would a mass rebuild build f22 or f21 packages when no such branches
> exist for the package?

They were retired after mass rebuild. If you look at the dates the mass rebuild
was August 17th, and they were retired November 17th because the maintainer
hadn't bothered to fix them prior to F-21 GA and it would have been broken for
GA.

> That doesn't explain why there orphaned. At a best guess Ice was orphaned by
> the owning developer for reasons unknown, I can't find the original email
> message in devel, simply that it was orphaned.

Yes it does. One of the packages that mumble depends on was broken. You'll need
to follow the break crumbs for the exact reason but the packages retired prior
to F-21 were only those that had broken soname deps so basically you wouldn't
have been able to do a "yum install mumble" due to broken deps.

> > Given they were both orphaned due to non building deps there might be others
> > up the dep tree that have issues and need to be fixed.
> 
> Mumble yes, it requires ice, as do several other packages. I've already
> emailed devel to see if I resurrect Ice if they would be willing to
> resurrect their packages which depended on it.

If you look at the ice retirement logs for ice it was retired due to other
broken deps. Have you tried grabbing the last .src.rpm and doing a scratch
build and seeing what deps it's missing. 

> OK, so either way, your builds having nothing to do with your interest in
> mumble, simply some erroneous automated script. I say erroneous because
> there are no active f21 or f22 branches for mumble, yet it was built in koji
> by the mass rebuild scripts.

It was part of a rel-eng mass rebuild as can be seen in the logs, you need to
look at the dates as the package was retired 3 months later.

Even with it retired you can check out the package branches and see why, you
can get the last .src.rpm from koji and check why it fails etc, see in the git
logs why it was retired etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review




[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]