Bug 10934 - RRS doesn't notice .lz upgrades
Summary: RRS doesn't notice .lz upgrades
Status: RESOLVED FIXED
Alias: None
Product: Recipe Reporting System (RRS)
Classification: Yocto Project Subprojects
Component: Recipe Reporting System (RRS) (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.5
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-01-17 11:55 UTC by Ross Burton
Modified: 2018-03-19 18:47 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2017-01-17 11:55:44 UTC 
GNU ed in the RRS has an unknown version upgrade (http://recipes.yoctoproject.org/rrs/recipedetail/351/) but the http index should be trivially indexable (http://ftp.gnu.org/gnu/ed/).  I suspect the problem is that all of the tarballs as .tar.lz, and we don't handle that extension in bitbake.
Comment 1 Paul Eggleton 2018-03-19 18:47:59 UTC 
This is apparently no longer an issue, as the ed recipe now shows up as "up-to-date". The RRS itself has no references to tarball types. tar.lz has been handed in bitbake since 2014 but only recently in 2017 we added lzip-native to support unpacking it, and subsequently updated the ed recipe to point to the upstream tar.lz file, so I suspect that was what resolved it.