No announcement yet.

apt issues with new website

  • Time
  • Show
Clear All
new posts

  • apt issues with new website


    I've been using apt to update my bcompare4 with a line like:
    deb [signed-by=/usr/share/keyrings/scootersoftware-keyring.gpg] bcompare4 non-free
    in my sources.list.d directory.

    Recently I've started getting 404 off the URI. I prefer to use apt to keep bcompare up-to-date.

    Is the apt repo coming back? Do I need to change the config?



  • #2
    The URL for the release information ends in /Release, not /InRelease.

    The repository as installed via Beyond Compare 4.4.6 .deb package on Ubuntu 22.04:

    scooter@ub2204:~$ cat /etc/apt/sources.list.d/scootersoftware.list
    deb [signed-by=/usr/share/keyrings/scootersoftware-keyring.gpg] bcompare4 non-free
    That should be all you need to make the repository work.

    It's possible your system has bad information cached, it might help to clear your apt cache, then update.

    scooter@ub2204:~$ sudo apt-get clean
    scooter@ub2204:~$ sudo apt update
    Hit:1 jammy InRelease
    Hit:2 jammy-updates InRelease
    Hit:3 jammy-backports InRelease
    Hit:4 jammy-security InRelease
    Ign:5 bcompare4 InRelease
    Hit:6 bcompare4 Release
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    All packages are up to date.
    It looks like repos can use InRelease or Release files, apt is checking for both, our repo only uses a Release file.​​
    Chris K Scooter Software


    • #3
      Thanks for the help Chris.

      After reading your response and digging deeper, I learned the root cause. I'll post it here in case someone else is affected:
      • Our corporate proxy recently started classifying scootersoftware as "commercially licensed software". As such the proxy started MITM'ing the TLS connection to issue the splash screen about needing a license to use said software (I have a license).
      • Our IS department injects the MITM root cert into our web browsers so one doesn't noticed unless one looks.
      • Apt wasn't putting up with these shenanigans and was rightfully rejecting the connections to
      • I attempted to to go the InReleases URI which apt printed and got the 404 and wrongly assumed it was the scooter dist stuff.
      I added the IS MITM cert to /usr/local/share/ca-certificates/, did the update-ca-certificates dance, and now I can update bcompare via apt.

      Thanks and sorry for the red-herring,