Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53782 - [kodi] rebuilt is needed

Attached to Project: Community Packages
Opened by John (graysky) - Monday, 24 April 2017, 14:02 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 24 April 2017, 14:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ike Devolder (BlackEagle)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Today's update pulled down a number of packages (listed below) one or more of which are responsible for kodi failing to load. Rebuilding kodi in a update-to-date chroot fixed it. Recommend you do the same and push out 17.1-3.

openssl(1.0.2.k-1->1.1.0.e-1)
coreutils(8.26-1->8.27-1)
libsasl(2.1.26-8->2.1.26-11)
libldap(2.4.44-3->2.4.44-4)
krb5(1.13.7-1->1.15-1)
libssh2(1.8.0-1->1.8.0-2)
icu(58.2-1->58.2-2)
curl(7.53.1-1->7.54.0-2)
glib2(2.50.3-1->2.52.1+4+g2eddcef1e-1)
libsecret(0.18.5-1->0.18.5+14+g9980655-1)
gpgme(1.9.0-1->1.9.0-2)
iputils(20161105.1f2bb12-1->20161105.1f2bb12-2)
ldns(1.7.0-2->1.7.0-3)
libarchive(3.3.1-4->3.3.1-5)
libevent(2.0.22-2->2.0.22-4)
libgudev(231-1->231+1+g0841288-1)
libpulse(10.0-2->10.0-3)
libtiff(4.0.7-2->4.0.7-3)
libxml2(2.9.4+12+ge905f081-5->2.9.4+16+g07418011-1)
openssh(7.4p1-2->7.5p1-2)
pacman(5.0.1-4->5.0.1-5)
python(3.6.0-2->3.6.1-1)
python2(2.7.13-1->2.7.13-2)
xf86-video-intel(1:2.99.917+770+gcb6ba2da-1->1:2.99.917+772+gc72bb27a-1)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 24 April 2017, 14:13 GMT
Reason for closing:  Not a bug
Comment by John (graysky) - Monday, 24 April 2017, 14:09 GMT
...I see now that 17.1-1 is in [community] and 17.1-2 is in [community-testing] so perhaps this is just a timing issue/you already knew a rebuild would be needed.
Comment by Doug Newgard (Scimmia) - Monday, 24 April 2017, 14:09 GMT
What, specifically, is the problem, and what, specifically, version of kodi?

Edit: 17.1-2 is not in community-testing, and hasn't been for hours. Sounds like a mirror issue.
Comment by John (graysky) - Monday, 24 April 2017, 14:12 GMT
@Doug - I didn't have time to debug. I know that after the update, kodi would not start. I know that rebuilding it fixed that. The version in question is 17.1-1. See my comment that posted just a few seconds before your reply.

Loading...