Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66812 - [namcap] repo inaccessible on case-insensitive file systems

Attached to Project: Arch Linux
Opened by David Macek (Elieux) - Thursday, 28 May 2020, 17:48 GMT
Last edited by Jonas Witschel (diabonas) - Wednesday, 22 June 2022, 12:02 GMT
Task Type Feature Request
Category Arch Projects
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Namcap can't be checked out on case-insensitive filesystems, such as NTFS (on default settings). This is an issue most prominently on Windows and WSL, but IMO it's generally nice to keep repositories free of symlinks and case conflicts. Could the repository be restructured so that the scripts, sources or both are in a separate directory?

```
> git clone https://git.archlinux.org/namcap.git/
Cloning into 'namcap'...
remote: Enumerating objects: 3020, done.
remote: Counting objects: 100% (3020/3020), done.
remote: Compressing objects: 100% (946/946), done.
remote: Total 3020 (delta 2406), reused 2586 (delta 2069), pack-reused 0R
Receiving objects: 100% (3020/3020), 508.98 KiB | 7.38 MiB/s, done.
Resolving deltas: 100% (2406/2406), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

'namcap'
```

... and the `Namcap` directory is missing.
This task depends upon

Closed by  Jonas Witschel (diabonas)
Wednesday, 22 June 2022, 12:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  namcap 3.3.0-1
Comment by Doug Newgard (Scimmia) - Friday, 29 May 2020, 03:21 GMT
I don't see the point. Unix/Linux is case sensitive, using a case insensitive filesystem for anything related to Unix/Linux isn't sane.
Comment by David Macek (Elieux) - Friday, 29 May 2020, 09:00 GMT
I concede that namcap is probably *used more* on Unix/Linux than non-Unix/Linux, but how does that make namcap *related to* Unix/Linux? It's a tool for checking PKGBUILDs. Note that pacman and makepkg are successfully used non-Unix/Linux systems.
Comment by Chih-Hsuan Yen (yan12125) - Sunday, 10 April 2022, 17:12 GMT
I'm also affected by this issue. I use namcap only on GNU/Linux, but I sync all my files, including a clone of namcap.git, across several devices with various filesystems. Here is a working fix: https://gitlab.archlinux.org/pacman/namcap/-/merge_requests/7

Loading...