@L.J shasums in the PKGBUILD are generated maintainer side. Confirming a developer's shasum provided with a /web browser/ seems like a fine thing to do. Feel free to disagree thogh.
Search Criteria
Package Details: servo-nightly-bin 20250209-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/servo-nightly-bin.git (read-only, click to copy) |
---|---|
Package Base: | servo-nightly-bin |
Description: | embeddable, independent, memory-safe, modular, parallel web rendering engine |
Upstream URL: | https://servo.org |
Licenses: | MPL-2.0 |
Conflicts: | servo |
Provides: | servo |
Submitter: | envolution |
Maintainer: | envolution |
Last Packager: | envolution |
Votes: | 34 |
Popularity: | 1.15 |
First Submitted: | 2025-01-12 03:18 (UTC) |
Last Updated: | 2025-02-09 12:51 (UTC) |
Dependencies (2)
- gst-plugins-bad (gst-plugins-bad-gitAUR)
- libunwind (libunwind-carbonAUR, libunwind-gitAUR)
Required by (0)
Sources (4)
envolution commented on 2025-01-15 16:29 (UTC)
L.J commented on 2025-01-15 15:50 (UTC)
Path=/usr/bin/servo
is not a folder, so the desktop entry doesn't work. I figure it should be /usr/lib/servo
? Also hash is wrong... Since it's already included in the pkgbuild, why is a hashfile also being downloaded? It's not used at all, and it should match the first hash already anyways...
envolution commented on 2025-01-14 12:40 (UTC)
@tee shasum updated
tee commented on 2025-01-14 12:28 (UTC)
checksum failure:
==> Validating source files with sha256sums...
servo-20250113.tar.gz ... FAILED
servo-20250113.tar.gz.sha256 ... FAILED
LICENSE ... Passed
servo.desktop ... Passed
==> ERROR: One or more files did not pass the validity check!
-> error making: servo-nightly-bin-exit status 1
envolution commented on 2025-01-12 03:30 (UTC)
Due to previous servo-latest
installations, you may have permissions warnings while installing like:
warning: directory permissions differ on /usr/lib/servo/resources/
filesystem: 644 package: 755
warning: directory permissions differ on /usr/lib/servo/resources/ahem/
filesystem: 644 package: 755
warning: directory permissions differ on /usr/lib/servo/resources/resource_protocol/
filesystem: 644 package: 755
warning: directory permissions differ on /usr/lib/servo/resources/user-agent-js/
filesystem: 644 package: 755
you will need to pacman -R servo-latest
before you install this package. Make sure /usr/lib/servo does not exist before reinstalling. New installs and upgrades and installs following this won't need explicit uninstallation.
An alternate solution is to sudo chmod 755 <all affected directories>
rsm commented on 2024-11-24 17:55 (UTC)
1) I had to fix the problems identified by @Riedler: chmod a+x -R /usr/lib/servo/resources/ 2) Correct the desktop file: A) remove Path=... B) set: Exec=/usr/bin/servo
Riedler commented on 2024-11-11 15:09 (UTC)
yup, still incorrect perms. /usr/lib/servo/servo now correctly has x, but /usr/lib/servo/resources/ doesn't, meaning the directory can't be traversed by users.
Herve_R commented on 2024-06-20 21:39 (UTC)
The directory permissions inside /usr/lib/servo/ are wrong. They miss a +x.
Sateallia commented on 2024-06-07 22:16 (UTC)
@ralphptorres I can't run the installed servo binary without sudo. If I download it manually and extract it in my downloads folder, I can run it just fine. Something to do with permissions?
thread 'main' panicked at ports/servoshell/resources.rs:82:24:
Can't read file: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
ralphptorres commented on 2024-06-04 11:22 (UTC)
Fixed versioning and packaging logics. Can someone verify that the fix works? Thanks.
Pinned Comments
envolution commented on 2025-01-12 03:30 (UTC)
Due to previous
servo-latest
installations, you may have permissions warnings while installing like:you will need to
pacman -R servo-latest
before you install this package. Make sure /usr/lib/servo does not exist before reinstalling. New installs and upgrades and installs following this won't need explicit uninstallation.An alternate solution is to
sudo chmod 755 <all affected directories>