APT repo recreated (on update / open)

the456gamer
the456gamer
Community Member
in Linux

I'm not sure exactly when this happened, but when updating 1Password through apt, i received messages informing me that the target is configured multiple times.
this occurred because I swapped all external apt repos to use the new deb822 style format, excluding some explicitly automatically managed files

the 1password file was not marked as automatically managed, so it was converted to the new style and removed, but came back.
(i think it was probably on update, but i don't know exactly)

compared to the google chrome file, which i explicitly knew to not touch due to the comment, identical to the other electron based apps
(slack, vscode)

my custom deb822

$ cat external.sources 
# 1Password
Types: deb
URIs: https://downloads.1password.com/linux/debian/amd64
Suites: stable
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/1password-archive-keyring.gpg
Enabled: yes

# Google Chrome
# not present, automatically edited in google-chrome.list

# Mono
Types: deb
URIs: https://download.mono-project.com/repo/debian
Suites: stable-buster
Components: main
Enabled: yes

[SNIP]

$ cat 1password.list
deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/amd64 stable main

$ cat google-chrome.list
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main

1Password Version: 1Password for Linux 8.10.4 (81004032)
Extension Version: Version 2.9.0
OS Version: Linux Debian 11
Browser:_ Firefox 91.13.0esr (64-bit)

Comments

  • FrankyO1P
    FrankyO1P

    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.

  • the456gamer
    the456gamer
    Community Member

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

    Thanks for looking into this

  • 1P_Gem
    1P_Gem

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

  • RogueScholar
    RogueScholar
    Community Member

    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.

  • FrankyO1P
    FrankyO1P

    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

This discussion has been closed.