Wrong permissions in tar archive #93933
Labels
No Label
legacy module
Development Management
legacy module
Platforms, Builds, Tests & Devices
legacy module
Python API
legacy module
Rendering & Cycles
legacy project
3.3
legacy project
Development Management
legacy project
Documentation
legacy project
Infrastructure: Blender Buildbot
legacy project
Infrastructure: Websites
legacy project
Platform: macOS
legacy project
Platforms, Builds, Tests & Devices
legacy project
Platform: Windows
legacy project
Python API
legacy project
Render & Cycles
Priority::Low
Priority::Normal
Priority::Unbreak Now!
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Information from Developers
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Report
Type::To Do
No Milestone
No project
No Assignees
7 Participants
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-buildbot#93933
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Ubuntu 20.04
Graphics card: RX 480
Blender Version
Broken: 2.93.5
Worked: 2.93.4
Short description of error
All the files in tar.xz archive has drwx------ or -rw------- permissions since version 2.93.5. Previously the permissions were drwxr-xr-x or -rw-r--r--.
Exact steps for others to reproduce the error
tar -tvf <filename>.Added subscriber: @DimaM
Added subscribers: @dr.sybren, @iss
@dr.sybren can you check?
I can't reproduce here with 2.93.7
The latest release candidate of Blender 2.93.6 has right permissions too. But the 2.93.6 release has wrong permissions. Blender 3.0 release is ok.
Blender 2.83.18 has this issue too.
It seems like files from this page [https:*builder.blender.org/download/daily/archive/ ]] are ok, even stable versions. But from this https:*www.blender.org/download/lts/2-83/ and this [ https:*www.blender.org/download/lts/2-93/ | https:*www.blender.org/download/lts/2-93/ pages are not ok.
Added subscriber: @lichtwerk
This looks like an issue with the LTS build pipeline. Maybe @lichtwerk can shed some light on this?
Added subscriber: @ankitm
similar but for macOS and different release versions blender/blender#93236 (3.0 mac: non admin users can't run blender)
Added subscriber: @brecht
Afaict, this is out of my reach, I think @brecht needs to jump in.
I fixed the umask now for the Linux buildbot workers, so the next time using the deploy builder it should work.
The reason the Blender 3.0 release is ok is because I happened to run the script for that manually, and the umask problem only happens for the buildbot worker daemons.
Not sure what the policy is for re-deploying a release, I guess we should not because the hashes change?
Added subscribers: @Jeroen-Bakker, @dfelinto
Thx!
Has this always been the case for previous releases?
(just asking because I cant really tell how many people are affected, if this might be a "known thing" and people usually know their way around -- to get an idea how "severe" this really is, see below)
Also not sure, would also summon @Jeroen-Bakker, @dfelinto reg. how "severe" this really is, see above
Just to be clear, are 2.93.7 and 3.0 ok on Linux? How about the latest 2.83?
3.0 is OK (as @brecht said, this was done manually).
2.93.7 & 2.83.18 are "affected".
Changed status from 'Needs Triage' to: 'Confirmed'
2.93.8 and 2.83.19 are ok
2.93.9 and 2.83.20 are ok too
Changed status from 'Confirmed' to: 'Resolved'
The building machinery is now fully working then. Thanks for the reporting.