Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Soren Stoutner Newsgroups: linux.debian.maint.python Subject: Re: Uscan: watch and changelog Date: Fri, 29 Mar 2024 19:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Mar 29 18:29:44 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.474 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no Organization: Debian MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2197201.NGdLjkp3rO"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-Debian-User: soren X-Mailing-List: archive/latest/21691 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2158506.IkYkc9Iarl@soren-desktop Approved: robomod@news.nic.it Lines: 61 Sender: robomod@news.nic.it X-Original-Cc: c.buhtz@posteo.jp X-Original-Date: Fri, 29 Mar 2024 11:29:14 -0700 X-Original-Message-ID: <2158506.IkYkc9Iarl@soren-desktop> X-Original-References: <4V5hyG6V92z9rxM@submission02.posteo.de> <4V5nC10CM4z6twb@submission01.posteo.de> Xref: csiph.com linux.debian.maint.python:15681 --nextPart2197201.NGdLjkp3rO Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii"; protected-headers="v1" From: Soren Stoutner To: debian-python@lists.debian.org Cc: c.buhtz@posteo.jp Subject: Re: Uscan: watch and changelog Date: Fri, 29 Mar 2024 11:29:14 -0700 Message-ID: <2158506.IkYkc9Iarl@soren-desktop> Organization: Debian In-Reply-To: <4V5nC10CM4z6twb@submission01.posteo.de> MIME-Version: 1.0 On Friday, March 29, 2024 10:16:56 AM MST c.buhtz@posteo.jp wrote: > There is no "opts=". So again. Why would you suggest to use "opts="? I want to > learn. I don't want to fight. One of the interesting things about uscan is there are often multiple different ways to connect to an upstream source and get what you want out of it. So, for example, if upstream posts tarballs, you can scan the HTML for those and find one that matches the latest version number in the changelog (or one with a newer version number, which uscan can use to notify you an update is available). However, uscan also speaks git. If you use `opts=git`, then instead of scanning the HTML looking for a tarball, it connects through git and looks at the tags to find a suitable release. It then clones that commit and uses the source to produce a tarball. Some upstream repositories both produce release tarballs and tag their releases in git, so either approach would work. Some only do one or the other. -- Soren Stoutner soren@debian.org --nextPart2197201.NGdLjkp3rO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmYHCHoACgkQwufLJ66w tgMZzQ//W2NOyE1UE3MWBnvIrBQdWJp+/BVqTf8j7LVJZTgi/2BbJHABgyBIJ40E O+z/+MSndwBXobUkp9V5F/JCjZpRyFWL79Sb2I6ebPpMwSZAcT11+5Awp5CAwsZc o85x7yva91pgxcRTcg1c1jzT2PjGtQOni40kiauHsdtyDilXDAzaKJ+SARWgjX5y 5ItYqM7tvx4Ie1w1OrxM9eaQSsnoG4bHjim4S9dJCAe50JoFO80XChs+ki4VfF9c 43N844615sIDQejLHDpsWfb2VUOZahtyDyFAwsM/sq4G4FV5+DPVsRW0WzJpJ2Ln 0RNMRRsnrErf6ZUv/tFOoBYmJTOw5TSjDgSjKEGSJYAkAQh/OhtD5MlHyEc3Z4nd pBgXQrlupF6nmpxOn8jliFMX175jHYhmrW0ng1R3MFN0Gi1DLKL8j5vSIGDR4+pC ugm0LbL3/5UsaxJAKp/T6miFqS87Ucg9ayXRHhGDm82Og9EjgWX+3F/1vtWbWQp7 Up80VqRQsDfeTAd0vHTfoQpIXyVR4rXvZdRcsircRozRHAvaHGHYMwcq8NJbjFLr Czyz9LROsuisNJh02Mf3pC23d45rcFcnfXmtmenEGoEKGwLpnm3VSlsFYCb0Mmsw iA7ug9E8GOx9MQBsfF9YZoz0Le/z3oakpW+WV/hBcN4KUl3ny44= =eRC5 -----END PGP SIGNATURE----- --nextPart2197201.NGdLjkp3rO--