nextcloud / nextcloud/nextcloudpi
Noticed that ncp-diag was not executable
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I noticed that ncp-diag was not executable
Please add that to the permission fixer.
System information
NextCloudPi version v1.50.2
NextCloudPi image NextCloudPi_docker_09-29-22
OS Debian GNU/Linux 11. 5.10.0-19-amd64 (x86_64)
automount no
USB devices none
datadir /data/nextcloud/data
data in SD no
data filesystem btrfs
data disk usage 1.9G/895G
rootfs usage 11G/29G
swapfile /dev/sda1
dbdir /data/database
Nextcloud check ok
Nextcloud version 24.0.5.1
HTTPD service up
PHP service up
MariaDB service up
Redis service up
HPB service up
Postfix service up
Internet check ok
public IP REMOVED SENSITIVE VALUE
public IP REMOVED SENSITIVE VALUE
Port check 80 closed
Port check 443 closed
IP REMOVED SENSITIVE VALUE
gateway REMOVED SENSITIVE VALUE
Interface eth0
certificates REMOVED SENSITIVE VALUE
NAT loopback no
Uptime 53min
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the permission fixer and the handling for ncp-diag. Confirm how the fixer determines executable permissions, add ncp-diag to its scope, and verify that the file is executable after the fixer runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100