Jump to content

Vigrid

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Vigrid

  1. Hi Carlos, thanks for your response.

    Trying the workaround resulted in an error:

    vigrid@red:~$ sudo apt update
    [sudo] password for vigrid: 
    Hit:1 http://us.archive.ubuntu.com/ubuntu impish InRelease
    Hit:2 http://us.archive.ubuntu.com/ubuntu impish-security InRelease        
    Hit:3 http://apt.pop-os.org/proprietary impish InRelease            
    Hit:5 http://us.archive.ubuntu.com/ubuntu impish-updates InRelease
    Hit:6 http://us.archive.ubuntu.com/ubuntu impish-backports InRelease                                  
    Hit:7 http://apt.pop-os.org/release impish InRelease                                                  
    Ign:4 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ InRelease         
    Get:8 http://us.archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
    Hit:9 https://www.plasticscm.com/plasticrepo/stable/ubuntu ./ Release
    Err:8 http://us.archive.ubuntu.com/ubuntu bionic InRelease
      The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
    Reading package lists... Done
    W: GPG error: http://us.archive.ubuntu.com/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32
    E: The repository 'http://us.archive.ubuntu.com/ubuntu bionic InRelease' is not signed.
    N: Updating from such a repository can't be done securely, and is therefore disabled by default.
    N: See apt-secure(8) manpage for repository creation and user configuration details.

    So I had to request the public key:

    vigrid@red:~$ sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3B4FE6ACC0B21F32
    Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
    Executing: /tmp/apt-key-gpghome.BZyzUO2YQV/gpg.1.sh --recv-keys --keyserver keyserver.ubuntu.com 3B4FE6ACC0B21F32
    gpg: key 3B4FE6ACC0B21F32: public key "Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>" imported
    gpg: Total number processed: 1
    gpg:               imported: 1

    It's not the prettiest way, but then I was able to update my apt database and then successfully install PlasticSCM.

    Thanks a lot!

    • Like 1
  2. I have recently installed Pop!_OS Linux (https://pop.system76.com/), which is based on the Ubuntu distribution.

    I am unable to install the PlasticSCM client using the instruction provided. I have done the preparation steps to add the PlasticSCM repositories into apt, but finalizing the installation results in this:

    vigrid@red:~$ sudo apt-get install plasticscm-cloud
    [sudo] password for vigrid: 
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:
    
    The following packages have unmet dependencies:
     plasticscm-gnome-sharp-mono4 : Depends: libgnome2-0 (>= 2.17.3) but it is not installable
                                    Depends: libgnomeui-0 but it is not installable
    E: Unable to correct problems, you have held broken packages.

    The libgnome2-0 library has been removed as a part of a general removal of GNOME 2 from Ubuntu distributions newer than 18.04.

    Is there a workaround for this? Are there plans to support newer Linux/Ubuntu distributions?

×
×
  • Create New...