On 7/16/20 7:45 AM, Shengjing Zhu wrote:
> On Thu, Jul 16, 2020 at 6:39 PM Reinhard Tartler <[email protected]> wrote:
>>
>> Package: golang-blackfriday
>> Severity: normal
>> Control: block 964378 by -1
>>
>> This upgrade is a requirement of the new go-md2man 2.0 upstream version,
>> which required by github.com/spf13/cobra, which in turns is required
>> by libpod 2.0, and thus blocks #964378.
>>
>
> First, manpage is just a nice-to-have feature for either cobra or
> podman. It shouldn't be a blocker for updating podman to 2.0.
>
You are absolutely correct, I've managed to update spf13/cobra to 0.0.7 while
still using the existing go-md2man package, which allowed me to build a podman
binary.
>> I've actually already updated the package in the experimental branch at
>> https://salsa.debian.org/go-team/packages/golang-blackfriday/-/tree/debian/experimental
>>
>> And did a test rebuild of all packages using ratt(1). Here is the executive
>> summary:
> [..]
>>
>> All buildlogs can be seen at:
>> https://people.debian.org/~siretart/buildlogs_blackfriday_2.0.1-1/
>>
>>
>> I wonder how to proceed. Shall we move ahead with uploading to
>> 'experimental' and file bugs against all packages that need updating, or
>> is it better to move ahead with #964938 and introduce a
>> golang-blackfriday-v2 package that contains a newer copy of the code?
>>
>
> Too many FTBFS, we won't have much time to fix all of it before the
> freeze of bullseye.
>
> I prefer creating a new source package for v2. The API between v1 and
> v2 is completely different.
> https://pkg.go.dev/github.com/russross/blackfriday/[email protected]?tab=doc
> https://pkg.go.dev/github.com/russross/[email protected]?tab=doc
>
Great, thanks for the 2nd opinion. I'll then go ahead with #964938.
best,
-rt
