Dear Maintainer,

the current debian/watch file fails to detect new upstream versions.

I'm not very familiar with uscan, but the following patch results in
different behaviour.
--- debian/watch.sav	2018-12-20 14:12:43.000000000 +0100
+++ debian/watch	2025-08-19 16:08:44.011871002 +0200
@@ -1,3 +1,4 @@
 version=4
-opts=filenamemangle=s/.+\/(\d+.\d+)\.tar\.gz/$1\/fdm-$1\.tar\.gz/ \
-  https://github.com/nicm/fdm/releases/ .+\/(\d+.\d+)\.tar\.gz
+opts=searchmode=plain,filenamemangle=s/.+\/fdm-(\d+\.\d+)\.tar\.gz/$1\/fdm-$1\.tar\.gz/ \
+  https://api.github.com/repos/nicm/fdm/releases \
+  https://[^:]+\/fdm-(\d+\.\d+)\.tar\.gz

You might wish to consider it, and perhaps upgrade to the latest upstream
version (2.2) which includes several improvements (e.g. support for
oauth2) and probably fixes #1074950.

It's a pity fdm was dropped in trixie.

Best regards,
	g.b.

Hi,

g1pi@libero.it wrote:

Yeah, I think  nobody really is. I was informed,  that there are efforts
to improve the  whole uscan situation, with version 5  of its configura-
tion format.  Because the  way things worked  before always  screwed you
over when github decided to change its web format a little bit.

And this isn't even what I have in the latest development version, where
I am using the much simpler:

  version=4
https://github.com/nicm/fdm/releases/ .+\/(\d+.\d+)\.tar\.gz

…which also  stopped moving at some  point — who knows  when. Your patch
seems to make it  work again, thanks. I'll add it to  the package. But I
am even more looking forward for things like this to be possible:

https://lists.debian.org/debian-devel/2025/08/msg00143.html

Well, there  are various factors that  contributed to this. A  major one
being my  work position, that  drained a ton of  my brain cycles.  I did
keep making updates to the packaging depository at

https://github.com/ft/pkg-fdm

…where you will find a few additional package versions on top of what is
in  unstable; but  unfortunately  I did  a very  poor  job on  following
through to get a sponsor to upload the package into Debian's archive.

So about the  newer version, yeah, the newest package  variant has that,
and actually a snapshot  on top that fixes a couple  of other things (it
is basically  the current state of  fdm's master branch —  it moves very
slowly itself). And about trixie, yeah,  when I noticed, it was unfortu-
nately too deep into the freeze cycles, that I could not get the package
in again.

I dropped the ball there, and that's what  it is for now. I will try and
get an update into unstable as soon as my time permits.