[MIR] appstream

Bug #1538293 reported by Robert Ancell
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
appstream (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre

Bug Description

[Availability]
In Universe

[Rationale]
Require for GNOME Software to be in main (bug 1536870)

[Security]
No known security issues.

[Quality assurance]
Runs well in Debian / Ubuntu.

[Dependencies]
All in main.

[Standards compliance]
No known issues.

[Maintenance]
Will be maintained in Debian and also by Ubuntu desktop team.

tags: added: gnome-software-ubuntu
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I will review this MIR.

Changed in appstream (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

There are multiple binary packages in appstream source. Do you need all of them, or just libappstream(3|-dev)? Do you also need libappstreamqt? What about the appstream binary?

The package has no team subscriber to watch for bugs; this should be added.

Finally; I noticed some lintian warnings for the binary packages:
I: libappstream3: hardening-no-fortify-functions usr/lib/x86_64-linux-gnu/libappstream.so.0.9.0
I: libappstream3: no-symbols-control-file usr/lib/x86_64-linux-gnu/libappstream.so.0.9.0
I: libappstreamqt1: no-symbols-control-file usr/lib/x86_64-linux-gnu/libAppstreamQt.so.0.9.0

Changed in appstream (Ubuntu):
status: New → Incomplete
Revision history for this message
Matthias Klumpp (ximion) wrote :

For GNOME Software to work, the appstream binary and GLib library are needed, the Qt stuff is (obviously) not essential for that.
(the other issues I can't answer, I leave that to Robert)

Revision history for this message
Matthias Klumpp (ximion) wrote :

I forgot to mention, the Qt things are needed to KDE Discover in universe, so should not be dropped but can be put in universe.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Right, the question was just to know whether there was more required than the appstream and libappstream3 binaries, to further define the MIR and avoid putting libappstreamqt1 in main if it's not necessary.

Revision history for this message
Iain Lane (laney) wrote :

the desktop bugs team is now subscribed

Is the lintian thing a blocker?

Regarding your question about the binary packages - component-mismatches will tell us what's going to go into main, no? Or are you trying to somehow blacklist a package from ever going in?

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

It doesn't especially matter to me which packages make it to main or not, but we shouldn't move packages around if they don't need to be. Knowing what is affected also shows that there has been some work put in preparing the MIR request.

As for the lintian warnings, no, it's not a blocker but they should also be fixed if possible.

MIR approved.

Changed in appstream (Ubuntu):
status: Incomplete → Fix Committed
Revision history for this message
Matthias Klose (doko) wrote :

Override component to main
appstream 0.9.1-1 in xenial amd64: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial arm64: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial armhf: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial i386: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial powerpc: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial ppc64el: universe/admin/optional/100% -> main
appstream 0.9.1-1 in xenial s390x: universe/admin/optional/100% -> main
7 publications overridden.

Changed in appstream (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.