Hello, change is now committed on git repo.
G.
On Wed, 10 Jan 2024 09:30:18 +0100 Gianfranco Costamagna
wrote:
control: tags -1 patch
hello, I'm attaching something that might be considered as a patch, the problem
was not in the checkout itself, but more in the version log.
---
control: tags -1 patch
hello, I'm attaching something that might be considered as a patch, the problem
was not in the checkout itself, but more in the version log.
--- a/lib/Devscripts/Uscan/git.pm 2023-04-03 01:03:04.0 +0200
+++ b/lib/Devscripts/Uscan/git.pm 2024-01-10
Hello,
I'm facing this too.
```d/watch
version=4
options=uversionmangle=s/-?([^\d.]+)/~$1/;tr/A-Z/a-z/,\
mode=git,gitmode=full,gitexport=all \
https://github.com/bcit-ci/CodeIgniter \
heads/master
```
Upstream's main branch is "develop". uscan takes this one instead of the
requested "master"
Hi uscan maintainers,
Any potential update?
From the tracked bugs this problem is blocking at least two packages
from moving forward to close their own bugs.
Best regards,
Agathe.
Hi,
On Thu, 26 Aug 2021 16:40:38 +0200 Yadd wrote:
> could you try using "heads/Beta" instead of "refs/heads/Beta" ?
Here is the output when using `heads/Beta` instead of `refs/heads/Beta`:
> uscan --verbose --no-download --debug
> uscan info: uscan (version 2.21.3) See uscan(1) for help
>
Hi,
could you try using "heads/Beta" instead of "refs/heads/Beta" ?
Package: devscripts
Version: 2.21.3
Severity: important
X-Debbugs-Cc: deb...@microjoe.org
Dear Maintainer,
While trying to use uscan to scan for upstream commits on a specific
branch instead of the default on, I tried to use refs/heads/ as
explained in the uscan man page.
Here is the content of
7 matches
Mail list logo
