[Discussion] Debian appstream generator update delay

[sidt]

From https://appstream.debian.org/sid/index.html, it appears that the Debian appstream generation was last done on Sep 2 ( Last updated on: 2023-09-02 20:55 [UTC] )

Any reason why it hasn't been updated ?

[sunrat]

¯\_(ツ)_/¯

[sidt]

Any idea whom to contact ? I don't find one in the appstream website.

[donald]

I emailed one of the admins, hopefully they can fix it or tell us whom to ask next.

Thank you for catching this.

[cds60601]

Looks like that date is the same for all suites

[cds60601]

Something that might be telling, if you click on the logs tag at the bottom of the main page, you are lead to here.
If you click into 2023, looking at the time stamps, one can deduce that the data is compiled once a month (or there about).
This could explain the date of a month ago. I suppose that this might change in the next day or two. Just guessing of course.

[donald]

It seems that one of the architectures being removed caused an issue. This has been fixed, however we are waiting for our git instance to come back online after maintenance. You should see the updates later today. Thank you for letting us know!

[sidt]

It seems to work now, which is good news.

But, it's also a bit disappointing that this was broken close to a month and no one noticed it. Lots of apps depend on an updated Appstream data to work properly.

Hope this doesn't repeat in future.

Thanks for everyone involved!

[donald]

We are people and we are admittedly fallible. But YOU caught the error so someone WAS paying attention. I understand from the email exchange that a notification email about the service not working was not sent, that has been corrected and the initial error corrected so this should not occur again.

Without clear and disastrous failure there is no rubble from which to build the steps to the future, so to speak.

[sidt]

I understand from the email exchange ...

Are the e-mails available to view to public (group e-mail), or private?

a notification email about the service not working was not sent, that has been corrected and the initial error corrected so this should not occur again.

Sounds good.

I think, maybe we should have a cron job, which independently checks whether the dates in the generated files are recent (<N days old etc). This should capture issues in any layer (Appstream Generator/System/Storage etc).

Without clear and disastrous failure there is no rubble from which to build the steps to the future, so to speak.

Agree.

[donald]

I understand from the email exchange ...

Are the e-mails available to view to public (group e-mail), or private?

Developer to Developer personal emails.

a notification email about the service not working was not sent, that has been corrected and the initial error corrected so this should not occur again.

Sounds good.

I think, maybe we should have a cron job, which independently checks whether the dates in the generated files are recent (<N days old etc). This should capture issues in any layer (Appstream Generator/System/Storage etc).

I do not know how the service is set up, so unfortunately I cannot really give you any answers here. I am sending them a link them to this thread, perhaps they will comment.

[sidt]

I do not know how the service is set up, so unfortunately I cannot really give you any answers here. I am sending them a link them to this thread, perhaps they will comment.

Sure. Thanks!