[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2023-10-04 Thread Zara
Thank you for the additional context! That seems like it will solve the problem on newer releases of ubuntu; am I right in thinking that older releases would still suffer from the gap between python-apt and sources.list? We encountered the issue on focal (20.04). -- You received this bug

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2023-10-04 Thread Julian Andres Klode
Note that as we move towards deb822 everywhere there will be less issues of that sort, as the deb822 backend recognizes every option (even unknown ones) and software-properties allows you to edit all of them. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2023-10-04 Thread Julian Andres Klode
This has been fixed a couple of months ago for PPAs and I think other shortcuts; they now use deb822 .sources files with Signed-By parameter. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-apt (Ubuntu) Status: Confirmed => Fix

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2023-10-04 Thread Zara
We encountered this with an ubuntu system using salt, which uses the python-apt package. We have sent a report and patch to python-apt upstream. The package is maintained by debian, and we are uncertain whether debian will consider it a bug, if these options are only used by ubuntu. There wasn't

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-12-12 Thread Julian Alarcon
Related (but not the same)": https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1986513 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title:

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-06-05 Thread Julian Andres Klode
My goal would be to switch to deb822 sources for this with the key embedded in the .sources file. We're still missing the ability to edit those files graphically however, that needs to be implemented first. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-06-04 Thread Marcos Ferreira
I started using Ubuntu 22.04 and this issue started to occour. The 'add-apt-repository' command adds the gpg key of the PPA repository in the trusted.gpg file (/etc/apt/trusted.gpg) As commented above, the PPA repositories are not being included in the sources.list file (/etc/apt/sources.list)

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu.

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-04-13 Thread Bug Watch Updater
** Changed in: software-properties (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-04-13 Thread Julian Alarcon
I'm on Ubuntu 22.04 and I'm getting the warning of deprecated location for keys multiple times. I know that for now I can ignore it, but I'm pretty sure that a lot of people is using PPAS/External Repos and will be scared of the warnings. ** Also affects: python-apt (Ubuntu) Importance:

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2022-01-24 Thread fermulator
Can confirm all of the above. https://fostips.com/apt-key-deprecated-right-way-add-repository https://www.north-47.com/knowledge-base/how-to-securely-install-apps-on-debian-based-linux-distros/ With apt-key being deprecated and a transition to more secure (better) restriction of repository trust

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2021-11-18 Thread Ashley Waite
The 'signed-by' field is not supported in the python-apt classes that are used by add-apt-repository and the gui software-properties. - When adding a new source there's no argument to provide 'signed-by' or 'trusted' options, so those cannot be added via add-apt-repository or the gui

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2021-11-11 Thread Nelson
add-apt-repository also silently deletes the [trusted=yes] option, which is appropriate but undocumented. There needs to be clearer documentation on what options work and what doesn't. Hopefully all options are supported. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2021-10-31 Thread Torsten Bronger
According to https://wiki.debian.org/DebianRepository/UseThirdParty I have to put third-party keys in /usr/share/keyrings, but a command like add-apt-repository -y "deb [signed-by=/usr/share/keyrings/mykey.gpg] https://my.repo/ impish main" fails. If I understand correctly, this means that

[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by

2021-10-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu.