Re: automated CI on salsa to prepare MR for new upstream version
- To: Jelmer Vernooij <jelmer@jelmer.uk>
- Cc: debian-devel@lists.debian.org
- Subject: Re: automated CI on salsa to prepare MR for new upstream version
- From: Andreas Tille <andreas@an3as.eu>
- Date: Sat, 25 Feb 2023 10:00:08 +0100
- Message-id: <Y/nOGDxOFN22yxcx@an3as.eu>
- In-reply-to: <Y/Cnhy3BF70u/eKc@an3as.eu>
- References: <5d2dbc5f-a57b-e8d4-ed3b-5b922c9c745d@undef.tools> <71897bea18f1c0b432f999aa719e70417ef94264.camel@debian.org> <92fd9180-4ab3-4d72-bcef-83cd35606306@app.fastmail.com> <Y9FFH8QBde9Je9Gp@lena.dartmouth.edu> <Y+/i6dqLbhYsZBOn@an3as.eu> <Y/AAZjKvtc4yjLPw@mordred.vpn.jelmer.uk> <Y/Cnhy3BF70u/eKc@an3as.eu>
Am Sat, Feb 18, 2023 at 11:25:11AM +0100 schrieb Andreas Tille:
> > Does it call deb-new-upstream as well? That's the one that mainly seems relevant here.
>
> I just learned about deb-new-upstream. Its parsing uscan manually but its not
> very robust and I should probably switch to use deb-new-upstream.
I just learned that routine-update is currently broken due to a changed
output by uscan (need to check this later when I have more time). This
gave me sufficient motivation to check out deb-new-upstream. I admit
that bug #1031913 is some kind of show stopper for me currently to
consider it as a replacement for the current strategy in routine-update
to simply use uscan.
How to you work around this in janitor?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: