briefcase package breaks on debian with umask 0077

[bganne]

Describe the bug

While following step 3 of the Beeware tutorial, I shad the following error when running briefcase package:

(beeware-venv) ben@erebor:~/src/android/beeware/beeware-tutorial/helloworld$ briefcase package

[helloworld] Finalizing application configuration...
Targeting debian:trixie (Vendor base debian)
Determining glibc version... done
Targeting glibc 2.37
Targeting Python3.11


[helloworld] Building .deb package...
Write Debian package control file... done
dpkg-deb: error: control directory has bad permissions 700 (must be >=0755 and <=0775)
Building Debian package...

Error while building .deb package for helloworld.

Log saved to /home/ben/src/android/beeware/beeware-tutorial/helloworld/logs/briefcase.2023_07_21-22_15_34.package.log

(beeware-venv) ben@erebor:~/src/android/beeware/beeware-tutorial/helloworld$

My umask is 0077, the workaround is to change it to 0022:

(beeware-venv) ben@erebor:~/src/android/beeware/beeware-tutorial/helloworld$ umask 0022
(beeware-venv) ben@erebor:~/src/android/beeware/beeware-tutorial/helloworld$ briefcase package

[helloworld] Finalizing application configuration...
Targeting debian:trixie (Vendor base debian)
Determining glibc version... done
Targeting glibc 2.37
Targeting Python3.11

[helloworld] Building .deb package...
Write Debian package control file... done
dpkg-deb: building package 'helloworld' in 'helloworld-0.0.1.deb'.
Building Debian package... done

[helloworld] Packaged dist/helloworld_0.0.1-1~debian-trixie_amd64.deb
(beeware-venv) ben@erebor:~/src/android/beeware/beeware-tutorial/helloworld$

Hope this helps, and thanks for Beeware!

Steps to reproduce

1. change umask to 0077
2. run briefcase package on debian

Expected behavior

Should work with any umask.

Screenshots

No response

Environment

• Operating System: Debian trixie/sid
• Python version: 3.11.4
• Software versions:
  • Briefcase: 0.3.15

Logs

No response

Additional context

No response

[freakboy3742]

Thanks for the report - looks like we've got a patch to fix the problem ready to land(#1370).