On Wed, Dec 21, 2016 at 6:42 PM, Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
On Wed, 2016-12-21 at 18:34 -0700, Chris Murphy wrote:
> Well it seems to me if a packaging change means some files are going
> to be removed upon updating that package with the new (and changed)
> package, that it's reasonable something somewhere is going to break,
> and that this should cause the build to fail with a warning so at
> least it can involve a human to assess the likelihood for breakage.
Sadly, the world is not so simple. There are all sorts of situations in
which a file being added, removed or renamed will happen with virtually
every rebuild of a given package.
Yep. The should was supposed to be a could.
Note that in the case under discussion, the move was even *known*
and
*expected* by the packager. What wasn't expected was the consequence
that moving the file from a 'core' location to an 'extras' location
would cause GNOME to stop using it. So even if the packager had been
notified of the move, they'd simply have said 'yes, that's fine' and
carried on.
OK so it's just an ordinary oops moment, dust oneself off and get moving again.
--
Chris Murphy