Hi again,
do you agree that the -f option does what you want when there
is no new upstream version?
I'd like to close this bug since its rather an intended feature
as far as I understand.
Kind regards
Andreas.
--
http://fam-tille.de
On Mon, Apr 20, 2020 at 02:18:31PM +0200, Andreas Tille wrote:
>
> Routine-update does not find a new upstream version so there is no need
> to do an update of the software. You want the -f|--force version if you
Sorry: s/version/option/.
See: routine-update --help
--
http://fam-tille.de
Hi IOhannes,
On Mon, Apr 20, 2020 at 11:12:08AM +0200, IOhannes m zmoelnig wrote:
>
> > E: Uscan did not return tarball name
Well, that's really a feature.
> However, my uscan works nicely.
> It seems that the parsing of the output of `uscan` for a tarball fails.
> I guess this is because the
Package: routine-update
Version: 0.0.2
Severity: normal
Dear Maintainer,
i was happy to learn about the existance of routine-update, and wanted to start
to integrate it into my packaging workflow.
However, it failed me with the first package i tried (pd-csound), with the
following error:
> E: U
4 matches
Mail list logo
