Hello, thanks for your bug report. On Sun, Nov 09, 2014 at 05:34:02PM +0100, Andreas Beckmann wrote: > Package: ruby-activemodel,ruby-activesupport > Version: 2:4.1.6-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts replaces-without-breaks > > Hi, > > during a test with piuparts and DOSE tools I noticed your package causes > removal of files that also belong to another package, leaving the other > package installed but crippled. > This is caused by using Replaces without corresponding Breaks. > > This is a serious bug violating policy 7.6, see > http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces > and also see the footnote that describes this incorrect behavior > http://www.debian.org/doc/debian-policy/footnotes.html#f53 > > The ruby-activemodel package has the following relevant relationships: > > Conflicts: N/A > Breaks: N/A > Replaces: ruby-activemodel-3.2, ruby-activemodel-4.0 > > Since you intend to completely replace these packages, I suggest to add > > Breaks: ruby-activemodel-3.2, ruby-activemodel-4.0 > > (lintian may warn about a missing (<< $VER) clause - you can either ignore > that or make something up like (<< 2:4.1) - which should go to the Replaces > as well) > > The same applies to the ruby-activesupport package which > > Replaces: ruby-activesupport-2.3, ruby-activesupport-3.2, > ruby-activesupport-4.0 > > The other packages built from src:rails may have similar problems, I didn't > check in deep. They should be adjusted for consistency anyway. > > But I could create test setups with crippled ruby-activemodel-3.2 and > ruby-activemodel-3.2 after installation and removal of the above two packages. > This may be an issue on wheezy -> jessie upgrades.
The Breaks: relationships were there originally, but removing them was how I achieved a successfull upgrade from wheezy in the first place, after some hours of trial and error. aptitude would figure the upgrade out just fine, but apt-get wouldn't. Looking back, what I didn't do was upgrading apt first, then upgrading the rest of the system. Maybe that would help. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
