Re: Taskotron misses dropped subpackages

2015-01-28 Thread Michael Schwendt
On Wed, 21 Jan 2015 11:48:55 -0700, Tim Flink wrote: Taskotron doesn't notice if subpackages have been dropped and cause unresolvable dependencies because they are not obsoleted anywhere. This isn't so much something that taskotron's checks missed as it's something we're not even checking

Re: Taskotron misses dropped subpackages

2015-01-28 Thread Michael Schwendt
On Wed, 21 Jan 2015 05:50:35 -0500 (EST), Kamil Paral wrote: Taskotron doesn't notice if subpackages have been dropped and cause unresolvable dependencies because they are not obsoleted anywhere. Yes, depcheck doesn't currently handle that. I've created:

Re: Taskotron misses dropped subpackages

2015-01-21 Thread Tim Flink
On Fri, 16 Jan 2015 11:00:00 +0100 Michael Schwendt mschwe...@gmail.com wrote: Taskotron doesn't notice if subpackages have been dropped and cause unresolvable dependencies because they are not obsoleted anywhere. This isn't so much something that taskotron's checks missed as it's something

Re: Taskotron misses dropped subpackages

2015-01-21 Thread Kamil Paral
Taskotron doesn't notice if subpackages have been dropped and cause unresolvable dependencies because they are not obsoleted anywhere. Yes, depcheck doesn't currently handle that. I've created: https://phab.qadevel.cloud.fedoraproject.org/T384 -- devel mailing list

Taskotron misses dropped subpackages

2015-01-16 Thread Michael Schwendt
Taskotron doesn't notice if subpackages have been dropped and cause unresolvable dependencies because they are not obsoleted anywhere. Examples: jogl2-javadoc, miglayout-examples, glusterfs-regression-tests rubygem-json-doc, rubygem-rake-doc, and more Yum is broken in the same way. And by