Announcement

Collapse
No announcement yet.

BC4 4.1.7 Respoitory Not Signed.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • peebles
    replied
    Thanks Cris, it's working now.

    This seems to fix my issues with git difftool --dir-diff

    Leave a comment:


  • Chris
    replied
    Code signing of the .deb repository was broken when we released version 4.1.7 on Friday. Our Linux developer just fixed it this afternoon.

    To update from the repository now that it's fixed:
    sudo apt-get update
    sudo apt-get upgrade

    Note the repository is still signed with SHA1, which is still on our list for a future update.

    Leave a comment:


  • Aaron
    replied
    It's an old problem, but as distros are updated it will become more noticeable as they demand better security on their packaged installers.

    Leave a comment:


  • Dave_L
    replied
    This seems to be a new problem with BC 4.1.7. I don't recall the issue occurring with the 4.1.6.

    Leave a comment:


  • Aaron
    replied
    This has not been updated yet, but is still on our To Do list.

    Leave a comment:


  • peebles
    replied
    Same here, please fix.

    Leave a comment:


  • Tecktron
    replied
    Tried to update today and I'm also having this issue.
    Ubuntu 16.04/64

    Leave a comment:


  • Dave_L
    replied
    I have a similar problem in Ubuntu 12.04.5. Synaptic issues a warning that the bcompare upgrade "can't be authenticated."

    Leave a comment:


  • goldsy
    started a topic BC4 4.1.7 Respoitory Not Signed.

    BC4 4.1.7 Respoitory Not Signed.

    Looks like your repository isn't signed.

    Results from running apt-get update:

    Code:
     ... 
    Get:8 http://www.scootersoftware.com bcompare4 Release [1,731 B]                     
    Err:9 http://www.scootersoftware.com bcompare4 Release.gpg                           
      404  Not Found
    Reading package lists... Done                                  
    E: The repository 'http://www.scootersoftware.com bcompare4 Release' is no longer 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.
    I was however able to update directly from BC.
    Last edited by goldsy; 19-Aug-2016, 07:15 PM. Reason: Can't type
Working...
X