Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
IvanR
8 months agoNew Contributor
1Password 8.10 or higher for Ubuntu
Just got an email reminder to update 1Password for Linux fue to expiring public key. The email also said the following: No action is required for users who’ve already updated 1Password for Linux to...
user41a8
8 months agoNew Contributor
Hmmm. Interesting. Thanks, AJCxZ0!
In my case, the file inside `/etc/apt/sources.list.d` is `1password.list.distUpgrade` and it reads just as it apparently should:
# This file is automatically added and configured by the 1Password package. Modifications may be overwritten.
deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https://downloads.1password.com/linux/debian/amd64 stable mainSo I don't know why that's not reflected in the output from `apt info 1password'.
Edit: I see that a number of packages (not all) in `/etc/apt/sources.list.d` have both a `.list` and a `.list.distUpgrade` file. Apparently this should be the case for 1password?
Edit 2: So I'm reading here
https://askubuntu.com/questions/457174/difference-between-sources-list-and-sources-list-distupgrade
that the `.list.distUpgrade` files are backups created with distro upgrades. Seems like the solution then would be
cp 1password.list.distUpgrade 1password.listRight?
AJCxZ0
8 months agoSilver Expert
Glad you found the cause of the behaviour. This is Ubuntu's way of disabling third party sources during a version upgrade, but leaves us to deal with the results.
Since 1Password doesn't have anything in `1password.list` which is specific to the Ubuntu release or even Ubuntu, you can simply re-enable the source by renaming the file, i.e. `mv -v 1password.list.distUpgrade 1password.list`. The next update will check this source and you should see the package upgrade offered.
Note that you should not have any `.distUpgrade` files left after you finish your post-upgrade work. The source files should be renamed (like this one) to re-enable the source, replaced with a new source specific to the new release, or removed. I recommend `-v` for file operations - mv, cp, rm, ... - as a matter of habit because it shows what actually happened rather than what you intended, which makes fixing mistakes so much easier.