Am 11.04.2017 16:18 schrieb Andreas Henriksson:
Hello,
On Tue, Apr 11, 2017 at 03:16:47PM +0200, Andreas Beckmann wrote:
Package: libts0
Version: 1.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
for some reason I still had the old libts* installed ...
Preparing to unpack .../libts0_1.8-1_amd64.deb ...
Unpacking libts0:amd64 (1.8-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libts0_1.8-1_amd64.deb (--unpack):
trying to overwrite '/etc/ts.conf', which is also in package tsconf
1.0-11
Errors were encountered while processing:
/var/cache/apt/archives/libts0_1.8-1_amd64.deb
Just wanted to recommend against the solution suggested in subject
of the bug report:
Shipping a file unversioned (like /etc/ts.conf) is very unwise in a
package
like libts0, since it breaks the entire idea of libts0 and potential
future
libts1 (or whatever) being co-installable. You'll commonly see this
handled
by shipping a libfoo-common that carry common unversioned files that
should
work with both libfoo0 and libfoo1.
(Ofcourse sometimes reality comes into the picture and you might have
a good reason to deviate from the common pattern.)
Since ts.conf is in fact still compatible and most probably will stay so
despite possible
major version changes, I'd love to have a prompt, like many other
packages do,
to take the maintainer's version or leave the currently installed one.
I don't yet know how I'd do it as the packager, but wouldn't this be a
straight forward
way to handle the situation?
thanks for the feedback!
Regards,
Andreas Henriksson
