Hi, Am Sonntag, den 24.06.2018, 12:06 +0300 schrieb Ilias Tsitsimpis: > On Sat, Jun 23, 2018 at 08:31AM, Mikolaj Konarski wrote: > > On Fri, Jun 22, 2018 at 08:12PM, Joachim Breitner wrote: > > > Note that I intentionally did not make it completely ignore revisions. > > > Consider this situation: > > > > > > * Debian has text-1.0 and foo-1.0 > > > * foo-1.0r0 depends on text < 1.1 > > > * Later someone added a revision to foo, and > > > foo-1.0r1 depends on text < 1.2 > > > * I plan to upgrade text to 1.1, so I bump it in the package plan. I > > > do this to find out what packages this will break. > > > > > > Under the current scheme, test-packages will not complain, because foo > > > is compatible with 1.1. I go ahead and upgrade text. > > The above will break as soon as you upload text-1.1 on Debian, since the > uploaded foo-1.0 depends on 'text < 1.1', right? correct! The important bit for me is not “will it break”, but “will be be able to fix it”. It used to be (many years ago) that we would upgrade a package, other packages break, and would stay broken for non-trivial amounts of time until upstream did something. Cheers, Joachim -- Joachim “nomeata” Breitner • nomeata@debian.org • https://j.oach.im/
Attachment:
signature.asc
Description: This is a digitally signed message part