On Tue, Feb 04, 2020 at 01:52:12PM +0100, nico.schloe...@gmail.com wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Thanks everyone for the replies.
>
> I've now manually downloaded the tar file and indeed it's different from
> the what uscan gets me. No idea why that is, but using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks everyone for the replies.
I've now manually downloaded the tar file and indeed it's different from
the what uscan gets me. No idea why that is, but using the manually
downloaded file does the trick.
Cheers,
Nico
On 2020-02-03 at 23:22,
On Mon, Feb 03, 2020 at 10:59:45PM +, PICCA Frederic-Emmanuel wrote:
> maybe this : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831870
This is unrelated.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Feb 03, 2020 at 09:05:53PM +, PICCA Frederic-Emmanuel wrote:
> Maybe a hint.
>
> tar.gz generated via github, seems to cause troubles during the import
> process.
>
> just try to extract the tar.gz via tar and regenerate it from the extracted
> files.
> Maybe it should solve your
On Mon, Feb 03, 2020 at 09:53:40PM +0100, Geert Stappers wrote:
> Elsewhere in the `uscan --verbose` output was download URL. I did
> wget http://gmsh.info/src/gmsh-4.5.2-source.tgz
>
> Then a check on thoses .tgz
> ```
> $ ls -l gmsh-4.5.2-source.tgz ../gmsh-4.5.2-source.tgz
> -rw-r--r-- 1
On Mon, Feb 03, 2020 at 09:12:51PM +0100, Geert Stappers wrote:
> On Mon, Feb 03, 2020 at 09:08:01PM +0100, Geert Stappers wrote:
> > On Mon, Feb 03, 2020 at 09:02:04PM +0100, Nico Schlömer wrote:
> > > On Mon, Feb 3, 2020 at 8:51 PM Geert Stappers wrote:
> > > > On Mon, Feb 03, 2020 at 08:00:47PM
On Mon, Feb 03, 2020 at 08:00:47PM +0100, Nico Schlömer wrote:
> Curiously, when I tar from another location (same file, same md5sum),
> ```
> tar -t -a -f /tmp/gmsh-4.5.2-source.tgz
> ```
> it's all going fine.
I cannot reproduce this.
Note that if you pipe it to less the error is hidden.
--
On Mon, Feb 03, 2020 at 09:08:01PM +0100, Geert Stappers wrote:
> On Mon, Feb 03, 2020 at 09:02:04PM +0100, Nico Schlömer wrote:
> > On Mon, Feb 3, 2020 at 8:51 PM Geert Stappers wrote:
> > > On Mon, Feb 03, 2020 at 08:00:47PM +0100, Nico Schlömer wrote:
> > > ...
> > > > ```
> > > > uscan:
On Mon, Feb 03, 2020 at 09:02:04PM +0100, Nico Schlömer wrote:
> On Mon, Feb 3, 2020 at 8:51 PM Geert Stappers wrote:
> > On Mon, Feb 03, 2020 at 08:00:47PM +0100, Nico Schlömer wrote:
> > ...
> > > Unfortunately, I only get
> > > ```
> > > uscan: error: tar -t -a -f ../gmsh-4.5.2-source.tgz
> Make it possible that the "problem" can be reproduced. Share the URL of the
> git repository
Clone from https://salsa.debian.org/science-team/gmsh and run
```
gbp import-orig --uscan
```
in the checkout.
Cheers,
Nico
On Mon, Feb 3, 2020 at 8:51 PM Geert Stappers wrote:
>
> On Mon, Feb 03,
On Mon, Feb 03, 2020 at 08:00:47PM +0100, Nico Schlömer wrote:
...
> Unfortunately, I only get
> ```
> uscan: error: tar -t -a -f ../gmsh-4.5.2-source.tgz subprocess
> returned exit status 2
...
> ```
> Curiously, when I tar from another location (same file, same md5sum),
> ```
> tar -t
Hi everyone,
I'm trying to update a package via
```
gbp import-orig --uscan
```
Unfortunately, I only get
```
uscan: error: tar -t -a -f ../gmsh-4.5.2-source.tgz subprocess
returned exit status 2
```
I can confirm that this `tar` like gives the error
```
[...]
gmsh-4.5.2-source/.clang-format
tar:
12 matches
Mail list logo