Re: announcement: go-md2man-v2 uploaded to NEW queue
On Sat, Oct 24, 2020 at 11:45 PM Drew Parsons <dparsons@debian.org> wrote:
>
> On 2020-10-24 23:29, Shengjing Zhu wrote:
> > On Mon, Sep 28, 2020 at 2:17 PM Drew Parsons <dparsons@debian.org>
> > wrote:
> >>
> >> Just letting the Go Team know, I've uploaded go-md2man-v2 to the NEW
> >> queue.
> >>
> >> go-md2man-v2 will supersede go-md2man, but it gets a new path so I've
> >> treated it as a new package conflicting with the original go-md2man,
> >> following the pattern used for golang-blackfriday-v2.
> >
> > It seems the Conflicts between golang-github-cpuguy83-go-md2man-v2-dev
> > and golang-github-cpuguy83-go-md2man-dev blocks testing migrations of
> > golang-github-spf13-cobra and golang-github-urfave-cli.
> >
> > The two packages haven't been migrated for 19days.
> >
> > I have asked in #debian-release irc channel on Oct 2. And bunk says it
> > may be
> > a bug in britney. However RT hasn't responded yet, or added a hint for
> > them.
> >
> > So I'm trying to move the install path to
> > /usr/share/gocode/src/github.com/cpuguy83/go-md2man/v2/
> > and remove the Conflicts on -dev packages.
>
>
> Thanks Shengjing. Usually such conflicts are direct, hence resolved with
> a Conflicts field. But this case is unusual since the conflict happens
> elsewhere in a different package 5 links down the dependency chain
> (golang-github-docker-notary-dev I think it was). So not really logical
> to use a Conflicts field directly.
@bunk summarized the bug on paste.d.n, but the link expired :(
On https://release.debian.org/britney/update_output.txt,
trying: golang-github-spf13-cobra
skipped: golang-github-spf13-cobra (10, 6, 5)
got: 104+0: a-14:a-0:a-0:a-0:i-89:m-0:m-0:p-0:s-1
* amd64: golang-etcd-server-dev,
golang-github-containers-buildah-dev,
golang-github-containers-common-dev,
golang-github-containers-image-dev, golang-github-docker-docker-dev,
golang-github-docker-leadership-dev, golang-github-docker-libkv-dev,
golang-github-docker-notary-dev,
golang-github-fsouza-go-dockerclient-dev,
golang-github-openshift-imagebuilder-dev,
golang-github-samalba-dockerclient-dev,
golang-github-tonistiigi-fsutil-dev,
golang-github-xordataexchange-crypt-dev
trying: golang-github-urfave-cli
skipped: golang-github-urfave-cli (10, 7, 4)
got: 104+0: a-14:a-0:a-0:a-0:i-89:m-0:m-0:p-0:s-1
* amd64: golang-etcd-server-dev,
golang-github-containers-buildah-dev,
golang-github-containers-common-dev,
golang-github-containers-image-dev, golang-github-docker-docker-dev,
golang-github-docker-leadership-dev, golang-github-docker-libkv-dev,
golang-github-docker-notary-dev,
golang-github-fsouza-go-dockerclient-dev,
golang-github-openshift-imagebuilder-dev,
golang-github-samalba-dockerclient-dev,
golang-github-tonistiigi-fsutil-dev,
golang-github-xordataexchange-crypt-dev
Take golang-etcd-server-dev for example, it depends both
golang-github-spf13-cobra-dev and golang-github-urfave-cli-dev.
And both golang-github-spf13-cobra-dev and
golang-github-urfave-cli-dev needs
golang-github-cpuguy83-go-md2man-dev in testing, needs
golang-github-cpuguy83-go-md2man-v2-dev in unstable.
So migrating one of them, will cause golang-etcd-server-dev uninstallable.
However apt is smart enough to find the upgrade path, to install them
together from unstable. But britney seems not.
--
Shengjing Zhu
Reply to: