*** This bug is a duplicate of bug 1872258 ***
https://bugs.launchpad.net/bugs/1872258
Jonathan:
Actually that sounds like a question for the update-manager developers,
so I've asked it there and subscribed you to it:
https://answers.launchpad.net/ubuntu/+source/update-
*** This bug is a duplicate of bug 1872258 ***
https://bugs.launchpad.net/bugs/1872258
** This bug has been marked a duplicate of bug 1872258
GS injects invalid metadata, causing "AppStream cache update completed, but
some metadata was ignored"
--
You received this bug notification
Hi Jonathan and Dan:
> I don't think either apt nor snap auto-updates will handle this.
I don't think so either, and nor will manual snap updates ("snap
refresh" command).
My assumption is that deb-to-snap and snap-to-deb transitions are
limited to development releases. It would be very
On Wed, Apr 22, 2020 at 02:53:48PM -, Jonathan Kamens wrote:
> I understand that, but in this particular case we're talking about a
> transition from a deb to a snap, not a snap update.
Aha, apologies, I misread your previous comment.
> Apparently there's special logic in update-manager to
I understand that, but in this particular case we're talking about a
transition from a deb to a snap, not a snap update. Apparently there's
special logic in update-manager to handle this, and perhaps in do-
release-upgrade as well, but I don't think either apt nor snap auto-
updates will handle
On Wed, Apr 22, 2020 at 10:24:41AM -, Jonathan Kamens wrote:
> I'm a bit concerned about that, though, because the reason why I didn't
> get that update is because I pretty much exclusively use apt to do my
> updates, and apparently that's no longer sufficient to get all the
> updates needed
I think Naël is correct that this problem goes away when gnome-software
is replaced by snap-store. Or, at least, it appears to have gone away
for me when I did that.
I'm a bit concerned about that, though, because the reason why I didn't
get that update is because I pretty much exclusively use
Hi Jonathan and Dan:
> I am not sure what you mean. There is no "snap-store" deb on my
> 20.04 system, nor does "apt search snap-store" yield any results.
It's a snap application, which you'll see in the output of the "snap
list" command if it is installed. It provides the Ubuntu Software
On Tue, Apr 14, 2020 at 11:19:53AM -, Naël wrote:
> With the replacement of gnome-software by snap-store in 20.04, this bug
> is no longer apparent. Only users who manually (re-)install gnome-
> software will see it.
I have an up-to-date focal system and I am still seeing this.
--
You
>With the replacement of gnome-software by snap-store in 20.04, this bug
is no longer apparent. Only users who manually (re-)install gnome-
software will see it.
I am not sure what you mean. There is no "snap-store" deb on my 20.04
system, nor does "apt search snap-store" yield any results.
With the replacement of gnome-software by snap-store in 20.04, this bug
is no longer apparent. Only users who manually (re-)install gnome-
software will see it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Please disregard my previous comment. Looking at the code, I realize
that the maintainer packaged the upstream gnome-software "3.36.0" tag,
not the "gnome-3-36" branch, which makes a lot more sense indeed.
So even though the fix is made upstream, it is NOT YET released, and
therefore not packaged
The fix was made upstream on Mar 24 [1], released as part of gnome-
software 3.36 on Apr 3 [2], which was packaged for Ubuntu today Apr 6
[3]. I'd say it's just a matter of hours before it's available in the
repository :)
[1]
Is there a fix yet, I too have this error.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1861631
Title:
"The AppStream system cache was updated, but some components were
This bug is still present because the change that Matthias did was
unintentionally undone the following week. So it was not shipped as it
should have been, as part of gnome-software 3.35.91, which is the
current version in Ubuntu. I have signaled this issue upstream.
--
You received this bug
** Changed in: gnome-software (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1861631
Title:
"The AppStream system cache was updated,
Technically, PPAs with AppStream data or other repositories with broken data
can trigger this as well.
AppStream could make a guess who is to blame for the breakage and give a more
specific error, but that will require some more extensive code changes.
--
You received this bug notification
Agreed, if the intent is for people to file bugs then it should be
clearer.
(Alternatively, might there be a better way for us to report this on
Ubuntu as a "crash", if users truly can't do anything about it?)
--
You received this bug notification because you are a member of Ubuntu
Desktop
I believe this error message needs rework, people have no idea what
AppStream is or where they can find the verbose log or why they even see
that.
** Changed in: appstream (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop
This error message is shown not to alert users, but rather make users report
these issues to the distributor, as this particular issue means the distributor
has a mistake in their metadata somewhere.
In this case it's not Ubuntu's fault directly, but rather GNOME Software
injecting invalid
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: appstream (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
21 matches
Mail list logo
