Re: Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Thibaut,
Am 13.04.2014 17:24, schrieb Thibaut Paumard:
The problem here is that B *is* actually A. All files that were
originally in A are now in B. There is no conflict just because the
package has them in version (and package) dependent subdirectories.
So, if you want to keep up-to-date, you should at some point remove
package A and install package B instead. This is what I think is the
use of "replaces".
Apart from special situations, there is no reason to keep package A
installed at all. At least, there no better reason than to keep
package versions A-r and A-(r+1) or B-r and B-(r+1) installed at the
same time.
After B (cpl-plugin-xshoo) is in testing, I will remove A
(cpl-plugin-xsh) from the Debian archive, so this is anyway just for
the translation.
I already removed the Conflicts field.
I think it is also helpful if there is no A anymore and a user wants
to install it.
So, if one renames a package and the renamed package has no conflict
to the old one, there should be no flag set? Just to be sure: it is
correct that there will be no indication at all that cpl-plugin-xsh
was renamed to cpl-plugin-xsh?
Sounds weird to me but if you thinkt it is right, I'll do this.
Best
Ole
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTS3ROAAoJEHEVr9B3ENz3BecP/A75E/aaDmbYTeFVOnKfr+GM
2LZyxEm/h/gh8UA0rBLL/egNnbqJax+SXcFqG3o3Bma7HO+etmWWLpT9z81eM4sD
OF+1wOj5338/rzR+xlhh8JzCoZUyHld45JyBCQfm6Co9/HdAy5tdK4fnANni2OdS
jH9vfroSFykmC5LMKkmw17RMyEey3poN64d0LumhWZpX8Trq6dvZDjewiGizkQc1
P7YU4sKcusS1mGo221fLKGFQvgE+cX3JdkB3k41hkURtZKDHJ3m9k5G6JyjTKsNY
YgejeTVOVNzqWfi07Q+5f9V3HJA7yGYmPnVdkyaXjleEzAej09YfaxpAwuDu3XtB
FMXwPqmjQ75XbuOFCzxA+hro0vqJUHhAh9AcCkgRo3PrPJVktmE2WcYIwxLy0kXG
6M9EQHGJn6nvI68x8iFR2bxpi1Gm79crKlrl9yjq6qsX7dUPg0ZScxT4TLdl9M1N
H5qchByudxHn90yY4CwihIKGhosn8Lt1P9eJIIwxXIEArTD0Q6er1m6YaUBgIflk
IV63o3pJqhhUWPae2dnFmenh1LxNCFEndlWQ9hQVR8CnYNU/Dx5YxAq3VGaH/mCR
zoHh4i6m+t0SAYgexNZT/BcI0zAIQw8fVhDc9knRAMqm5+ycxtVkMjGAmd11Ydyj
+IaZixez1TvO5Oi/LeiP
=xVJZ
-----END PGP SIGNATURE-----
Reply to: