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

Re: How to stop breaking reverse dependencies?



On Tuesday 19 May 2015 03:44 AM, Antonio Terceiro wrote:
> Hi,
> 
> vagrant is now broken in unstable, due to an update of ruby-timers.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785632
> 
> As it turns out, vagrant depends in ruby-listen, that depends on
> ruby-celulloid, that has a strict ~> 1.1.0 dependency on ruby-timers.
> Also, ruby-celluloid is the *only* reverse dependency of ruby-timers, so
> discovering the breakage before the upload should probably require very
> little effort.

ruby-timers was updated only for ruby-celluloid (0.16 needed ~> 4.0.0
ruby-timers). ruby-celluloid 0.16 was uploaded as soon as the tests were
passed (local build was failing, but chroot build succeeded)

> I would like to discuss ideas on how to avoid this type of thing that
> happens *all the time*. Is it possible to make maintainers include
> checking this type of thing in their workflow? Is automation the only
> way out?
> 
> I have already implemented checking dependencies in
> gem2deb-test-runner:
> http://anonscm.debian.org/cgit/pkg-ruby-extras/gem2deb.git/commit/?id=2866cbfafac08ecb1e9e5b8dfebfc2699c9d7dc3

that is a good idea.

> It shouldn't be hard implement a similar check that tests reverse
> dependencies ...

yes, that would be good. We'll definitely need this kind of checks.

> Ideas?
> 


Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: