Are you sure it works in a pbuilder/chroot ?

dget https://in.terlu.de/\~kreckel/mozillavpn/mozillavpn_2.12.0-1.dsc
and building it

fails with

go: could not create module cache: mkdir /sbuild-nonexistent: permission denied
(maybe an error above)

Cheers

S

Le 08/01/2023 à 00:46, Richard B. Kreckel a écrit :
Could we just upgrade to version 1.12.0 for sid/bookworm, please?

Right now, the mozillavpn package is slated for removal from bookworm. I would be very happy if we could avoid this.

After some tinkering, I got v1.12.0 to work on sid/bookworm. Here's what it takes:

1) Create mozillavpn_2.12.0.orig.tar.gz
   a) download https://github.com/mozilla-mobile/mozilla-vpn-client/archive/refs/tags/v2.12.0.tar.gz    b) unpack it (and discover that directories under 3rdparty/ subdir are empty)    c) drop the contents of https://github.com/mozilla/glean/archive/refs/tags/v52.0.0.tar.gz into 3rdparty/glean/    d) drop the contents of https://github.com/WireGuard/wireguard-tools/archive/refs/heads/master.zip into 3rdparty/wireguard-tools/

2) Based on mozillavpn_2.9.0-1.debian.tar.xz, apply some changes to debian/ directory:    a) -DBUILD_TESTING=OFF to dh_auto_configure argument in debian/rules (without it it FTBFS trying to run some tests and that is also in upstream's rules file)    d) change rm -rf debian/mozillavpn/etc/opt/chrome to rm -rf debian/mozillavpn/etc/opt in debian/rules so purge won't remove /etc/opt/ since there's nothing in there anyway    c) Add packages python3-click and python3-jinja2 to Build-Depnds in debian/control (without these, it FTBFS)    d) remove libqt6* and qt6-qpa-plugins dependencies in debian/control (see #1026957).

This builds for me on amd64.

An alternative to step 1) above is of course to clone from https://github.com/mozilla-mobile/mozilla-vpn-client.git and then git submodule update --init. That only adds some stuff not needed for Debian into the orig.tar.gz.

For the record, I've placed copies of the files at https://in.terlu.de/~kreckel/mozillavpn/.

Also, debian-release should be contacted because of the build failure on mipsel and mpis64el. It makes little sense to insist on these architectures if upstream doesn't care.

Please decide how to proceed and let me know if I can help in any way.

  -richard.

Reply via email to