vcswatch reports that
this package seems to have a new changelog entry (version
1.1-3.1, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 78fbc978fdce8f0ea6b408b5332b533d58d177d8
Author: Alexandre Detiste <tchet@debian.org>
Date: Fri Feb 9 19:54:26 2024 +0100
typo
commit 7d7cb0e47a95bc855f947e32af264a7f71ddc5fb
Author: Alexandre Detiste <tchet@debian.org>
Date: Fri Feb 9 19:38:41 2024 +0100
close FTCBFS bug #1063459 with changelog
commit da03e440eab9dc15074215a8d6a5e99a0d64b7f0
Author: Helmut Grohne <helmut@subdivi.de>
Date: Fri Feb 9 19:34:36 2024 +0100
pushover fails to cross build from source for multiple reasons. The
immediate failure is a failure to find SDL2_image.pc using the build
architecture pkg-config. What initially looks like wrongly hard coding a
build architecture pkg-config turns out to be a correct use: It actually
needs SDL2_image for a build-time utility and SDL2_image is not used at
all for host objects. Therefore, the relevant build dependency should be
annotated :native. Once this is fixed, a build architecture compiler
invocation fails to understand host architecture compiler flags.
Recently, Debian started employing architecture-dependent compiler flags
such as -mbranch-protection=standard (arm64) and this fails all over the
place. I propose extending the build system to tell "_NATIVE" flags
apart like it does with compilers already. The defaults are chosen such
that backwards-compatibility is retained. Once passing these from
debian/rules, pushover actually cross builds. Do you mind applying this
patch?
Helmut
-------------- next part --------------
commit 7ae8d321a4093daff1a261a0d3dec752636cf9df
Author: Alexandre Detiste <tchet@debian.org>
Date: Sun Dec 17 16:06:59 2023 +0100
add non-working watch file: Gitlab.com gives uscan a 403
curl of the url by hand does work (???)