Bug 7328

Summary:	Package feed publishing tool
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Paul Eggleton <bluelightning>
Component:	devtools / tool chain	Assignee:	Unassigned <unassigned>
Status:	RESOLVED OBSOLETE	QA Contact:	yeoh ee peng <ee.peng.yeoh>
Severity:	enhancement
Priority:	Medium	CC:	alexandru.c.georgescu, bruce.ashfield, jose.perez.carranza, joshuagloe, liezhi.yang, markus.lehtonen, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, ross.burton
Version:	1.8
Target Milestone:	Future
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)
Bug Depends on:	6992
Bug Blocks:

Description Paul Eggleton 2015-02-17 10:27:24 UTC

Develop a simple tool for publishing package feeds; this will have two main functions:

1) Publish only the packages that have materially changed

2) Ensure the indexes are up-to-date

We may also want to consider the problem of packages being produced where version the version hasn't changed but the contents has (this would be an error situation since the package manager won't do an upgrade).

Comment 1 Ross Burton 2015-06-29 13:16:49 UTC

Presumably this won't make M1.  Randy, will you be able to deal with this for M2?

Comment 2 Randy Witt 2015-06-29 15:43:19 UTC

(In reply to comment #1)
> Presumably this won't make M1.  Randy, will you be able to deal with this
> for M2?

Yes. I expected to have the first part finished last week. But some assumptions the package_manager.py indexing code means I'll probably have to refactor some of it.

Comment 3 Paul Eggleton 2015-09-17 14:08:51 UTC

I've split out the "reducing package feed churn" issue to bug 8318 since it's no longer an integral part of the publishing tool.

Comment 4 Randy Witt 2015-09-22 17:24:03 UTC

This is mostly finished now that the "package diffing" is actually done as part of the build.

I need to revisit and make sure that nothing has regressed and submit.

Comment 5 Paul Eggleton 2015-10-16 11:58:21 UTC

So I think the important part of this is now under bug 8318 which is already scheduled for 2.1; I'm downgrading this bug's priority and moving it to 2.1 as well.

Comment 6 Randy MacLeod 2024-10-17 15:16:46 UTC

We have a variety of package workflows and automated tests but there's no need for this particular workflow.