[ISSUE] nsxiv checksum error

[ISSUE] nsxiv checksum error

[rickalex21]

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

New issue by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.13_1 x86_64 GenuineIntel uptodate rFFF

### Package(s) Affected

nsxiv 32

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No.

### Expected behaviour

Build the package without errors.

### Actual behaviour

I think the checksum may need to be updated?

template file updated by me to work:

```text
checksum=49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
# 12/10/2023 They have not updated the checksum? 
#checksum=09d1d72b3cbcf17a04e26beb5e81acc9495aaba1f8f1be907bdcd8e4e3007db3
```

ERROR as the template file is right now:

```text
=> ERROR: SHA256 mismatch for 'v32.tar.gz:'
49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
=> ERROR: nsxiv-32_1: couldn't verify distfiles, exiting...
```

### Steps to reproduce

Try building with xbps-src.

Re: nsxiv checksum error

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1849562790

Comment:
could just be codeberg changing the way they generate those tarballs. could also be a retag. you could use diffoscope to compare the old and new tarballs (get the old from https://sources.voidlinux.org/nsxiv-32/)

Re: nsxiv checksum error

[rickalex21]

[-- Attachment #1: Type: text/plain, Size: 184 bytes --]

New comment by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1850242408

Comment:
I don’t know what a diffoscope is. 

Re: nsxiv checksum error

[rickalex21]

[-- Attachment #1: Type: text/plain, Size: 188 bytes --]

New comment by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1850242408

Comment:
I will see if I can figure it out later. 

Re: nsxiv checksum error

[rickalex21]

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

New comment by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1852729915

Comment:
@classabbyamp it looks like there are no differences?

I did:

diffoscope dir1 dir2

and also diff -qr

not sure why I’m getting different hashes ?

Re: nsxiv checksum error

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1852732256

Comment:
i bet it's just metadata or compression differences. diffoscope knows how to diff archives, so you could diff the tarballs directly instead of extracting

Re: nsxiv checksum error

[rickalex21]

[-- Attachment #1: Type: text/plain, Size: 218 bytes --]

New comment by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1852760140

Comment:
It gives me a weird comparison:

![](https://i.imgur.com/nULeZY6.png)

Re: nsxiv checksum error

[sgn]

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1853540980

Comment:
> Format-specific differences are supported for Gzipped files but no file-specific differences were detected;

They're the same. Probably because of https://lore.kernel.org/git/a812a664-67ea-c0ba-599f-cb79e2d96694@gmail.com/

Re: nsxiv checksum error

[sgn]

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/47684#issuecomment-1853540980

Comment:
> Format-specific differences are supported for Gzipped files but no file-specific differences were detected;

They're the same. Probably because of https://lore.kernel.org/git/a812a664-67ea-c0ba-599f-cb79e2d96694@gmail.com/

            $ sha256sum old/v32.tar.gz <(zcat old/v32.tar.gz) \
                    new/v32.tar.gz <(zcat new/v32.tar.gz)
            09d1d72b3cbcf17a04e26beb5e81acc9495aaba1f8f1be907bdcd8e4e3007db3 old/v32.tar.gz
            4952f27cc17a704c88d2f0bbd0e937018ea6545e0ce5bba26cb6578625aa597b /proc/self/fd/12
            49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90 new/v32.tar.gz
            4952f27cc17a704c88d2f0bbd0e937018ea6545e0ce5bba26cb6578625aa597b /proc/self/fd/13

Re: [ISSUE] [CLOSED] nsxiv checksum error

[sgn]

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

Closed issue by rickalex21 on void-packages repository

https://github.com/void-linux/void-packages/issues/47684

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.13_1 x86_64 GenuineIntel uptodate rFFF

### Package(s) Affected

nsxiv 32

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

No.

### Expected behaviour

Build the package without errors.

### Actual behaviour

I think the checksum may need to be updated?

template file updated by me to work:

```text
checksum=49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
# 12/10/2023 They have not updated the checksum? 
#checksum=09d1d72b3cbcf17a04e26beb5e81acc9495aaba1f8f1be907bdcd8e4e3007db3
```

ERROR as the template file is right now:

```text
=> ERROR: SHA256 mismatch for 'v32.tar.gz:'
49ef1eb775ef6c34f55dada7a3f446c9c5c6773c9e208509ffef27a656338a90
=> ERROR: nsxiv-32_1: couldn't verify distfiles, exiting...
```

### Steps to reproduce

Try building with xbps-src.