Bug#979080: libhtml-template-pro-perl FTCBFS: dependency issues

[gregor herrmann]

On Sun, 03 Jan 2021 14:44:56 +0100, Helmut Grohne wrote:

> On Sat, Jan 02, 2021 at 05:14:45PM +0100, gregor herrmann wrote:
> > BTW, your debdiffs never apply, as the packages evolve in git. E.g.
> > the perl-xs-dev dependency is already added, and we make also other
> > mass changes, and then the Debian janitor also comes along.
> That's useful info and it wasn't obvious to me. Thank you for telling.

You're welcome.
 
> > That's no big deal, I just look at your debdiffs and fix what
> > remains, but it would also be enough to just say "please add
> > <!nocheck> and perl-xs-dev" (or start from the package's git repo).
> Reducing the friction here obviously is a good idea, but at this point,
> I'm unsure how to converge.

It's not really a friction (on our side), more that you might be
doing unnecessary work.

On the other hand …
 
> I strongly prefer working from unstable as that tends to work or has a
> ftbfs bug filed. What is in git tends to not work as well (at least
> outside the perl team).
> 
> Filing a bug has a dual purpose on my side: For one thing, I transmit
> the message and the proposed fixed. However, it also gives me an
> automatic handle of when to retry the package. udd knows when a bug is
> fixed in unstable.
> 
> Before filing a patch, I want to see that it actually works. So I end up
> writing the patch anyway. Not attaching it (even if it doesn't apply to
> git), seems less useful to me.

… I understand your workflow very well.

And from my POV we can just continue in the same way, as I basically
just wanted to say that we typically don't apply your debdiffs
verbatim.
 
> I guess the best course of action atm is skipping perl issues. Given
> more time, the <!nocheck>, perl-xs-dev and multiarch hints will trickle
> into more packages solving a big chunk of the problem with less
> friction.

No, please don't stop :)

Without a notification some packages will sit in git without an
upload for a long time, but we're happy to do uploads if it boosts
cross-buildability. And "notification" can be a bug report, or an
email, or whatever.
 
> Please let me know if you reach a different conclusion.

Maybe it would also work if you just give us a list of packages to
upload with <!nocheck>, perl-xs-dev, and Multiarch:same; and when
they don't cross-build afterwards bugs+patches are still an option.

But that's entirely up to you; whether you want to first try with a
tested patch or after we upload a "modernized" package or something
else - let's continue to improve the cross situation in Debian :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Rigmor Gustafsson: If You Go Away
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Digital Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20210103/21a71432/attachment.sig>