Yeah, this is really annoying. Every time I `apt upgrade`, 1password recreates the `1password.list` file in `/etc/apt/sources.list.d` when I've already switched to using the `.sources` format. Please stop creating the `.list` file and breaking apt. I have to manually `rm` the file every time 1password gets an update.

Thanks roy_orbison​ for the patch, I did something similar but just commented out the `installDebChannel` function entirely. 

Hopefully this can get fixed upstream properly.

Hey RogueScholar,

Thank you for reaching out and sharing your feedback. I'll go ahead and pass this information along to the team. We also greatly appreciate your kind words 😄

Franky

Hi 1P_Gem,

Just as an aside to this, I'd like to propose something to the development team regarding the management of the APT repository file placed in /etc/apt/sources.list.d. What if they were to switch to placing a file there in the Deb822 control data format just as the original poster (and myself) have done? With that done, it would then be a relatively trivial matter to add the ability for users to select the release channel that they want to receive updates from on APT-based Linux distributions in every bit the same way they can on Windows currently. It would only involve manipulating the value of the Suites: key in that file to match the release channel selected plus all slower-moving ones, space delimited. They could even tie into the PackageKit Session API to trigger the system to fetch and install updates on-demand from within the 1Password app in a package manager-agnostic fashion, bringing the Linux app up to feature parity with its Windows counterpart as it already is in almost every other way.

The APT developers are moving fast and breaking things lately (a la the commit 2+ weeks ago to apt 1.7.0dev that borked the repository signing key management of every Chromium-based browser, without apology or reversion…) and with Debian Bookworm switching to shipping only the Deb822 format, it's virtually certain that this change to 1Password will have to happen at some point in the not-too-distant future. Going one step further, since Linux users are far more prone to working on the command line you could also tie in the ability to manipulate the release channel and pause updates/pin the currently installed version through the 1Password CLI, just as TeamViewer has offered in their own CLI for at least the last four years. Really, that last part (manipulating the release channel and pausing updates from the CLI) would be cool to see on Windows, too.

Anyhow, I know you guys have plenty of other irons in the fire so I'll stop there, I just wanted to get the idea down and into your hands while it was fresh in my mind. Thanks again for all the hard work; I can assure you that it doesn't pass unnoticed.

Hi @the456gamer! On behalf of my colleague Franky, you're very welcome. If you have any further questions or concerns, let us know 😄

I don't need help at the moment, as I disabled the entry in my file.

Thanks for looking into this

Hi @the456gamer,

Thanks for bringing this to our attention. I'd like to ask, do you need any assistance with resolving the multiple target issue?

I understand you would also like to see a comment included in the sources. I'll go ahead and pass along your feedback and this request to the team.

Looking forward to hearing from you.