On 2016-07-25 8:41, Pirate Praveen wrote:
tracker.debian.org/gitlab [1] shows: Marked for autoremoval on 29 July: 827846, 827100, 830241, 830917 high Version of gitlab is marked for autoremoval from testing on Fri 29 Jul 2016. It is affected by 827846, 827100. It depends (transitively) on ruby-mechanize and ruby-omniauth-openid, affected by 830241, 830917. You should try to prevent the removal by fixing these RC bugs. Created: 2016-06-21 Last update: 2016-07-25 01:01
Yes.
But only reverse dependency of ruby-mechanize is yapra, which does not have any reverse dependency.
No. The only reverse-dependcy of ruby-mechanize is ruby-sham-rack - as a Build-Depends - which has ruby-carrierwave as a reverse-dependency. That, in turn, has diaspora and gitlab as reverse-dependencies.
(yarpa has a Recommends on ruby-mechanize, but not a Depends.)
Can you check what is wrong here?
Your understanding of the package dependency tree or what's affected by autoremovals appears to be wrong
Links: ------ [1] http://tracker.debian.org/gitlab
Regards, Adam