Hi Dmitry, [...] >> What do you suggest we do now? Should we declare mutual ‘Conflicts’ between >> this package and 'golang-speter-go-exp-math-dec-inf'? > > Breaks/Replaces in one package should be enough, if we are going to keep one > package. Then perhaps we could remove older package?
I guess if we are going to remove the older package then one could also
use Replaces/Conflicts? This way the old package will be replaced by the
new one completely. I tried this and it seems to work fine. See [1] for
what I would propose as a change -- any comments?
AFAICS there are not many packages that depend on the old
golang-speter-go-exp-math-dec-inf-dev:
$ apt-cache rdepends golang-speter-go-exp-math-dec-inf-dev
golang-speter-go-exp-math-dec-inf-dev
Reverse Depends:
golang-github-appc-spec-dev
golang-github-appc-spec-dev
which is maintained by you... and integestingly already depends on
golang-gopkg-inf.v0-dev? [2]
I guess it would then only need removing the obsolete b-dep from
golang-github-appc-spec-dev and an upload of the new golang-gopkg-inf.v0?
Cheers
Sascha
[1]
https://salsa.debian.org/go-team/packages/golang-gopkg-inf.v0/blob/master/debian/control
[2]
https://salsa.debian.org/go-team/packages/golang-github-appc-spec/blob/master/debian/control
signature.asc
Description: OpenPGP digital signature
