On Thu, 12 Mar 2026 10:04:45 -0400 Thomas Dickey <[email protected]> wrote: > Revisiting #1122181, I see that its proposed patch fixes the issue which > I reported in #1130447.
Hi Thomas, I am not one of uscan maintainers nor know about its internals, but thanks a lot for all the detailed analysis. By the way, this seems to be the same problem as #1112388. Cc'ing. The problem with the patch proposed by Uwe is that on package build it breaks one test (with 6 ASSERT error messages) ... testWatch4NonNativeDlUversion_uversionmangle uscan warn: In debian/watch no matching files for version 1.0-rc-1 in watch line ASSERT:uscan: exit_code!=0 but exit_code=0 expected:<1> but was:<0> ASSERT:foo-1.0-rc-1.tar.gz missing: opts="uversionmangle=s/-([a-z]+-)/~$1/" @@@url@@@/([\d][\d\.a-z-]+)/@PACKAGE@/ooo/ @PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@ debian uupdate ASSERT:foo_1.0~rc-1.orig.tar.gz missing: opts="uversionmangle=s/-([a-z]+-)/~$1/" @@@url@@@/([\d][\d\.a-z-]+)/@PACKAGE@/ooo/ @PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@ debian uupdate ./test_uscan_mangle: line 327: cd: /tmp/shunit.mjso1e/tmp/uscan_mangle.24LyCq/foo-1.0~rc-1: No such file or directory ASSERT:pristine tarball is not extracted dpkg-parsechangelog: error: cannot open file debian/changelog: No such file or directory ASSERT:uscan: Version should be 1.0~rc-1-1 but found expected:<> but was:<1.0~rc-1-1> ASSERT:file that must be present is excluded in the tarball ... Ran 75 tests. FAILED (failures=6) Change you propose causes even more ASSERT lines (34). Regards, -- Agustin
