Bug #5091

Doozer Bionic builds not working

Added by Max Max 6 months ago. Updated about 1 month ago.

Status:FixedStart date:2018-04-29
Priority:HighDue date:
Assignee:Mark Clarkstone% Done:

100%

Category:General
Target version:-
Found in version:* Affected Versions:

Description

Hi, I have been following this guide...

https://tvheadend.org/projects/tvheadend/wiki/AptRepository

...to install tvheadend on ubuntu 18.04 LTS.

This is the command I have used to add the Doozer repo:
echo "deb http://apt.tvheadend.org/stable bionic main" | sudo tee -a /etc/apt/sources.list.d/tvheadend.list

However, "sudo apt-get update" yields this:

$ sudo apt-get update
Hit:1 http://at.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://at.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://at.archive.ubuntu.com/ubuntu bionic-backports InRelease
Ign:4 http://apt.tvheadend.org/stable bionic InRelease
Err:5 http://apt.tvheadend.org/stable bionic Release
404 Not Found [IP: 104.31.94.73 80]
Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists... Done
E: The repository 'http://apt.tvheadend.org/stable bionic 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.

Also, "http://apt.tvheadend.org/stable/dists/" does not contain any entry for "bionic".

Associated revisions

Revision 9b9ee685
Added by Mark Clarkstone 3 months ago

debian: always use gzip compression for deb files (bintray issue) - fixes #5091

Revision 42e737f2
Added by Mark Clarkstone 3 months ago

debian: always use gzip compression for deb files (bintray issue) - fixes #5091

History

#1 Updated by Mark Clarkstone 6 months ago

  • Status changed from New to Accepted

There seems to be an issue with the builder atm, for now you'll have to build manually.

#2 Updated by Mark Clarkstone 4 months ago

Mark Clarkstone wrote:

There seems to be an issue with the builder atm, for now you'll have to build manually.

I've added a workaround for this in PR 1123. This should be resolved when commited :)

#3 Updated by Aengus Walton 4 months ago

Mark Clarkstone wrote:

Mark Clarkstone wrote:

There seems to be an issue with the builder atm, for now you'll have to build manually.

I've added a workaround for this in PR 1123. This should be resolved when commited :)

Any news on this? I see the PR was merged 11 days ago, but there still aren't any bionic builds in the bintray.

This is the one thing that's blocking me (and plenty of others, I imagine) from upgrading - it would be great to see this resolved! If I can help in any way, let me know.

#4 Updated by Mark Clarkstone 4 months ago

Aengus Walton wrote:

Mark Clarkstone wrote:

Mark Clarkstone wrote:

There seems to be an issue with the builder atm, for now you'll have to build manually.

I've added a workaround for this in PR 1123. This should be resolved when commited :)

Any news on this? I see the PR was merged 11 days ago, but there still aren't any bionic builds in the bintray.

This is the one thing that's blocking me (and plenty of others, I imagine) from upgrading - it would be great to see this resolved! If I can help in any way, let me know.

Thanks for the bump on this issue - I'd forgotten to update.

The uploads are being rejected by Bintray (400 bad request), I suspect it's due to this but I can't be sure.

I'm a bit baffled as to why it's only bionic & centos7 though, might be something to do with them being built under docker?

The packages are building fine though.

I'll have to test on Doozer when I get the chance. However I bet perexg might have some idea & already have a fix in mind.

#5 Updated by Mark Clarkstone 4 months ago

  • Priority changed from Normal to High

#6 Updated by Mark Clarkstone 4 months ago

  • % Done changed from 0 to 10

And another update.. After trying a manual upload I've come to the conclusion that the problem appears to be with Bintray, it complains about the deb package being malformed in some way (they're not I've installed them on my machine fine).

I've contacted them for assistance. Will update again when I know more.

#7 Updated by Aengus Walton 3 months ago

Mark Clarkstone wrote:

And another update.. After trying a manual upload I've come to the conclusion that the problem appears to be with Bintray, it complains about the deb package being malformed in some way (they're not I've installed them on my machine fine).

I've contacted them for assistance. Will update again when I know more.

Hi Mark,

thanks for following this up. Has bintray responded?

#8 Updated by Mark Clarkstone 3 months ago

Aengus Walton wrote:

Mark Clarkstone wrote:

And another update.. After trying a manual upload I've come to the conclusion that the problem appears to be with Bintray, it complains about the deb package being malformed in some way (they're not I've installed them on my machine fine).

I've contacted them for assistance. Will update again when I know more.

Hi Mark,

thanks for following this up. Has bintray responded?

Nope :( I'll see if I can reach out to someone else.

#9 Updated by Mathias Neuhaus 3 months ago

others have (had) similar problems as well; there are some ideas here
https://github.com/travis-ci/travis-ci/issues/9656
(comment by stlankes June 2nd)

or probably fixed by Biontry ...
https://github.com/apache/couchdb/issues/1431
(comment by whoali)

#10 Updated by Mark Clarkstone 3 months ago

  • Assignee set to Mark Clarkstone
  • % Done changed from 10 to 90

Mathias Neuhaus wrote:

others have (had) similar problems as well; there are some ideas here
https://github.com/travis-ci/travis-ci/issues/9656
(comment by stlankes June 2nd)

or probably fixed by Biontry ...
https://github.com/apache/couchdb/issues/1431
(comment by whoali)

OK so after a bit of investigation, it is indeed an issue with Bintray (the service doesn't like tar.xz files in the debs). I've resolved it with PR #1136. It will also need to be backported to 4.2.

#11 Updated by Mark Clarkstone 3 months ago

  • Status changed from Accepted to Fixed
  • % Done changed from 90 to 100

#12 Updated by Mathias Neuhaus 3 months ago

Thanx!

#13 Updated by Aengus Walton 2 months ago

That's great! Thanks for this!

#14 Updated by Aengus Walton about 1 month ago

Follow-up: when I do an apt-get update, I get the following:

W: Skipping acquire of configured file 'release/binary-amd64/Packages' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/binary-i386/Packages' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/i18n/Translation-en_US' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/i18n/Translation-en' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/dep11/Components-amd64.yml' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/dep11/icons-48x48.tar' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/dep11/icons-64x64.tar' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/Contents-i386' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/Contents-amd64' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'release/cnf/Commands-amd64' as repository 'https://dl.bintray.com/tvheadend/deb bionic InRelease' doesn't have the component 'release' (component misspelt in sources.list?)

Is this something wrong at your end or at mine?

Also available in: Atom PDF