Merge lp:~xnox/ubuntu-archive-scripts/exclude-community into lp:ubuntu-archive-scripts

[Dimitri John Ledkov]

platform now has community seed, that is currently imply community-maas seed.

These are packages that are in the maas snap, but are optional and only used for support of legacy/community hardware. Those packages should stay in universe and had MIR NACKed by security.

[Steve Langasek (vorlon)]

Had you seen this feedback from Colin?

<cjwatson> Listing it before supported but not having supported inherit from it (in STRUCTURE) ought to work, I think
<cjwatson> Probably better than hacking it using -e

Did you decide against this for some reason?

review: Needs Information

[Dimitri John Ledkov (xnox)]

I have seen this feedback from colin.

community-maas is listed before supported, and it does not inherit from it.

And none of the maas packages are in the supported seed.

However, components-missmatches doesn't look just at the supported seed.

Instead it looks at "all", which includes all of the seeded, supported, and community packages, and tries to pull "all" into main.

Thus I either have to move community-maas out of "ubuntu(platform)" seed repositories, or make components-missmatches exclude "community", or make components-missmatches only look at "supported,desktop,server,etc".

I don't want to split supported/community-maas seeds across different repositories, and excluding community seems easier than maintaining a long include list of the defined seeds in ubuntu STRUCTURE.

[Steve Langasek (vorlon)]

review: Approve

=== modified file 'archive-reports'
--- archive-reports	2020-02-06 12:22:12 +0000
+++ archive-reports	2020-04-09 13:51:33 +0000
@@ -210,6 +210,7 @@
 				-d "$OUT/$name.dot" -o "$OUT/$name.txt.new" \
 				--html-output-file "$OUT/$name.html" \
 				--csv-file "$OUT/$name.csv" \
+				--exclude "community" \
 				"$@"
 			if [ "$name" = component-mismatches ]; then
 				process-component-mismatches-diff \