zamb3zi commented on issue #3966:
URL: https://github.com/apache/couchdb/issues/3966#issuecomment-1074745866


   I'm having the same issue on Debian Buster:
   ```
   #  apt update
   Hit:1 http://security.debian.org/debian-security buster/updates InRelease
   Hit:2 http://cdn-fastly.deb.debian.org/debian buster InRelease
   Err:3 https://apache.jfrog.io/artifactory/couchdb-deb buster InRelease
     403  Forbidden [IP: 13.32.80.86 443]
   Reading package lists... Done
   E: Failed to fetch 
https://apache.jfrog.io/artifactory/couchdb-deb/dists/buster/InRelease  403  
Forbidden [IP: 13.32.80.86 443]
   E: The repository 'https://apache.jfrog.io/artifactory/couchdb-deb buster 
InRelease' 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.
   ```
   
   and Debian Stretch:
   ```
   # apt update
   Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
   Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease
   Hit:4 https://deb.nodesource.com/node_8.x stretch InRelease
   Hit:3 http://cdn-fastly.deb.debian.org/debian stretch Release
   Ign:6 https://apache.jfrog.io/artifactory/couchdb-deb stretch InRelease
   Err:7 https://apache.jfrog.io/artifactory/couchdb-deb stretch Release
     403  Forbidden
   Reading package lists... Done
   E: The repository 'https://apache.jfrog.io/artifactory/couchdb-deb stretch 
Release' does not have a Release file.
   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.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to