That does sound annoying, however I'm not sure how to reproduce it. I tried:
stirling: /tmp$ mkdir lp2068011
stirling: /tmp$ cd lp2068011/
stirling: /tmp/lp2068011$ touch sitecustomize.py
stirling: /tmp/lp2068011$ sudo snap install ppa-dev-tools
[sudo] password for bryce:
ppa-dev-tools 0.5.0 from Bryce Harrington installed
stirling: /tmp/lp2068011$ /snap/bin/ppa create lp2068011-test
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=Rs4jdBN3hCgv0GDrVQwD&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
PPA 'lp2068011-test' created for the following architectures:
Offhand, it's not obvious what in ppa-dev-tools would trigger that kind of behavior. Can you try reproducing it some different ways to see if you can narrow down where the error is coming in?
Hi Adrien,
That does sound annoying, however I'm not sure how to reproduce it. I tried:
stirling: /tmp$ mkdir lp2068011 /launchpad. net/+authorize- token?oauth_ token=Rs4jdBN3h Cgv0GDrVQwD& allow_permissio n=DESKTOP_ INTEGRATION)
stirling: /tmp$ cd lp2068011/
stirling: /tmp/lp2068011$ touch sitecustomize.py
stirling: /tmp/lp2068011$ sudo snap install ppa-dev-tools
[sudo] password for bryce:
ppa-dev-tools 0.5.0 from Bryce Harrington installed
stirling: /tmp/lp2068011$ /snap/bin/ppa create lp2068011-test
The authorization page:
(https:/
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
PPA 'lp2068011-test' created for the following architectures:
i386, amd64, armhf, ppc64el, s390x, arm64, powerpc
The PPA can be viewed at:
https:/ /launchpad. net/~bryce/ +archive/ ubuntu/ lp2068011- test
You can upload packages to this PPA using:
dput ppa:bryce/ lp2068011- test <source.changes>
Wait for the uploads to build and publish using:
ppa wait ppa:bryce/ lp2068011- test
To add the repository and to your system:
sudo add-apt-repository -yus {the_ppa.address}
sudo apt-get install <package(s)>
stirling: /tmp/lp2068011$
Offhand, it's not obvious what in ppa-dev-tools would trigger that kind of behavior. Can you try reproducing it some different ways to see if you can narrow down where the error is coming in?