Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release
Added by David jrm about 6 years ago
Hi there,
it seems there is any issue with the bionic repositor.. Anyone else with same issue?
Can someone check if there are issues with bintray?
Thx
Replies (20)
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Rob Q about 6 years ago
I'm having the same problem with the repository for stable release on CentOS 7.
dl.bintray.com..."Forbidden!"
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone about 6 years ago
Seems Bintray are having issues or we've hit our quota again :/
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by David jrm about 6 years ago
Should I raise it as a bug? or it is fine here?
Thx
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Frank Zappa about 6 years ago
Is there any news about this?
I've got every day warning messages by updating my ssource lists!
Thanks,
WebEye
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone about 6 years ago
Frank Zappa wrote:
Is there any news about this?
I've got every day warning messages by updating my ssource lists!Thanks,
WebEye
Thanks for the bump. This should be resolved now, what issues are you still having? What is the error?
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Frank Zappa about 6 years ago
Thanks for support!
I've got following line in my source.list
deb https://dl.bintray.com/tvheadend/deb bionic release
also tested
deb https://dl.bintray.com/tvheadend/deb bionic release-4.2
And got following output by updating sources:
# sudo apt-get update OK:1 http://ubuntu.mirror.lrz.de/ubuntu bionic InRelease OK:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates InRelease OK:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-security InRelease Ign:4 https://dl.bintray.com/tvheadend/deb bionic InRelease OK:5 https://dl.bintray.com/tvheadend/deb bionic Release Paketlisten werden gelesen... Fertig W: Das Laden der konfigurierten Datei »release/binary-i386/Packages« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?) W: Das Laden der konfigurierten Datei »release/binary-amd64/Packages« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?) W: Das Laden der konfigurierten Datei »release/i18n/Translation-de_DE« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?) W: Das Laden der konfigurierten Datei »release/i18n/Translation-de« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?) W: Das Laden der konfigurierten Datei »release/i18n/Translation-en« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?) W: Das Laden der konfigurierten Datei »release/cnf/Commands-amd64« wird übersprungen, da das Depot »https://dl.bintray.com/tvheadend/deb bionic InRelease« die Komponente »release« nicht enthält. (Schreibfehler bei der Angabe der Komponente in sources.list?)
# uname -srvmpio Linux 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic
Thanks again,
WebEye
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone about 6 years ago
Frank Zappa wrote:
...
Bintray is still having issues it would appear, this time it's only affecting bionic, for the moment you can ignore that error and add/use the apt.tvheadend.org repository instead.
Hopefully they'll fix it soon!
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Frank Zappa about 6 years ago
Thanks Mark,
do the Doozer repository include the "release" repo-component?
I don't want to go to stable to avoid bugs....
According to your Wiki, they have only stable and unstable!
WebEye
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone about 6 years ago
If you want release just download the deb instead & dpkg -i it
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Frank Zappa about 6 years ago
Ok,
thank you....
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Rob Walker about 6 years ago
Seems i'm getting an error with apt.tvheadend.org
then it run "apt-get update"
W: The repository 'http://apt.tvheadend.org/unstable stretch Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Method gave invalid 103 Redirect message
Contents of "/etc/apt/sources.list.d/tvheadend.list"
deb http://apt.tvheadend.org/unstable stretch main
which is from the guide
Example:
echo "deb http://apt.tvheadend.org/unstable xenial main" | sudo tee -a /etc/apt/sources.list.d/tvheadend.list
just changed xenial to stretch
I've Followed the guide from https://apt.tvheadend.org/projects/tvheadend/wiki/AptRepository
and all seems ok.
Running debian Stretch and TVHeadend 4.3-1361~ge1c03470d currently but its missing recordings so wanted to upgrade
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by jody gugelhop about 6 years ago
repository issues it seems see https://tvheadend.org/boards/5/topics/34306
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Peter Brockamp about 6 years ago
SIC, another month almost passed by and still no change. This is really kind of annoying...
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone about 6 years ago
Peter Brockamp wrote:
SIC, another month almost passed by and still no change. This is really kind of annoying...
Please re-read the AptRepositories page
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Rob Q about 6 years ago
It feels like Centos/el7 have been left hanging. What do we do?
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Peter Brockamp about 6 years ago
Mark Clarkstone wrote:
Please re-read the AptRepositories page
You are right, wasn't aware that bintray is out of service. I changed my settings accordingly, the error message is gone and it installed a more current version of TVH.
THX for the hint!
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Frank Zappa almost 6 years ago
Thanks,
the new deb is working now....
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Rob Q almost 6 years ago
Can those of us on RPM download the branch release package build directly from Doozer?
For example, I'm looking at getting tvheadend-4.2.7-17~g45cc65a.el7.x86_64.rpm.
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Mark Clarkstone almost 6 years ago
Rob Q wrote:
Can those of us on RPM download the branch release package build directly from Doozer?
For example, I'm looking at getting tvheadend-4.2.7-17~g45cc65a.el7.x86_64.rpm.
I don't see why not.
RE: Forbidden access to https://dl.bintray.com/tvheadend/deb bionic Release - Added by Hans Schneider almost 6 years ago
I had the same problem with the other release. The problem was that bintray banned the account. They unbanned it today (I had email contact with the support). For me it works now. I think the bionic release should be fine then too.