[DRE-maint] Bug#738488: Bug#738488: ruby-tilt: Broke compatibility with all rdepends

Antonio Terceiro terceiro at debian.org
Sun Feb 23 15:41:59 UTC 2014


On Sun, Feb 23, 2014 at 11:33:15PM +0900, Youhei SASAKI wrote:
> Hi,
> 
> First, sorry for my upload...

Don't worry, this type of thing happens. Your work is still very
appreciated.

> At Thu, 20 Feb 2014 18:07:32 -0300,
> Antonio Terceiro <terceiro at debian.org> wrote:
> >
> > [1  <text/plain; us-ascii (quoted-printable)>]
> > On Sun, Feb 09, 2014 at 11:51:39PM +0100, Christian Hofstaedtler wrote:
> > > Package: ruby-tilt
> > > Version: 2.0.0-1
> > > Severity: grave
> > > Tags: upstream
> > > Justification: renders package unusable
> > >
> > > Dear Maintainer,
> > >
> > > tilt 2.0 broke compatibility in various ways.
> > > This causes sinatra to FTBFS, and the same goes for other rdepends.
> > >
> > > Unsure what upstream's plan is with regard to migration.
> >
> > This also broke rails in a very nasty way.
> >
> > I think we should probably revert this new upstream version, and
> > reapproach the new upstream version in a different way by first making
> > sure reverse dependencies still work.
> >
> > Youhei, can you please look at this?
> 
> Now I check current package and upstream repository. It's difficult for
> me to introduce backward compatibility layer. So I agree revert. But I
> don't know procedure. How do I revert? with epoch? or create new package
> like ruby-tilt-1.4?

I wouldn't like to *not* add yet another versioned package like this.
Assuming this revert is temporary until we figure out a way forward, the
best way is to make a new upload based on the previous version using a
version number like 2.0.0+really1.4.1-1.

I think it's easier for me to do it than to explain how, so I went ahead
and did it. Check the git repository! :-)

> > We have to check reverse dependencies before uploading new upstream
> > versions!
> 
> I agree deeply. sorry again.

One of the reasons I am working on debci/ci.debian.net is to have this
sort of thing tested automatically for us, so 1) this type of think will
not reach testing and 2) we could even upload to experimental and have
all reverse dependencies tested in the cases we know there might be
issues with reverse dependencies.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20140223/d3f2300d/attachment.sig>


More information about the Pkg-ruby-extras-maintainers mailing list