Your message dated Sat, 18 Apr 2026 13:00:18 +1000
with message-id <[email protected]>
and subject line Re: Bug#1132969: tracker.debian.org: AppStream hint seems
never to be updated
has caused the Debian Bug report #1132969,
regarding tracker.debian.org: AppStream hint seems never to be updated
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1132969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1132969
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: normal
Hello,
as an example please see <https://tracker.debian.org/pkg/backintime>.
There you find an AppStream hint (from 23th February) about two missing
screenshots
<https://appstream.debian.org/sid/main/issues/backintime-qt.html>
The error happend because the screenshot hoster (codeborg) was down.
This was nearly two months ago months ago.
The hoster is available again. The appstream hint component should run from
time to
time and see if the error persists. It shouldn't update only if the package
gets
updated (uploaded).
For "backintime" this is a false-positive error.
Thanks
Christian Buhtz
Upstream maintainer of backintime
--- End Message ---
--- Begin Message ---
Hi Christian
On 08/04/2026 21:10, Christian Buhtz wrote:
Package: tracker.debian.org
Severity: normal
Hello,
as an example please see <https://tracker.debian.org/pkg/backintime>.
There you find an AppStream hint (from 23th February) about two missing
screenshots
<https://appstream.debian.org/sid/main/issues/backintime-qt.html>
The error happend because the screenshot hoster (codeborg) was down.
This was nearly two months ago months ago.
The hoster is available again. The appstream hint component should run from
time to
time and see if the error persists. It shouldn't update only if the package
gets
updated (uploaded).
For "backintime" this is a false-positive error.
This is not a false positive.
Let's start at the error message that the appstream checker shows, it says:
/-----
Warnings
screenshot-save-error
Unable to store screenshot for
'https://translate.codeberg.org/media/screenshots/bit_16to9_960x540_mainwindow.png':
Could not load source screenshot for storing: Format der Bilddatei unbekannt
screenshot-save-error
Unable to store screenshot for
'https://translate.codeberg.org/media/screenshots/bit_16to9_1280x720_general_ssh.png':
Could not load source screenshot for storing: Format der Bilddatei unbekannt
-----/
Now I'll hazard a guess that your fluency in German is better than
mine... Image file format unknown.
The URLs that are used by backintime have anti-AI-scrapers sitting in
front of them. Attempting to access those URLs requires a
javascript-aware browser to be able to actually obtain the image.
The appstream checker will have ended up with precisely what I just
ended up when checking the URLs:
/-----
$ wget
https://translate.codeberg.org/media/screenshots/bit_16to9_960x540_mainwindow.png
--2026-04-18 12:48:36--
https://translate.codeberg.org/media/screenshots/bit_16to9_960x540_mainwindow.png
Resolving translate.codeberg.org (translate.codeberg.org)...
217.197.84.142, 2a0a:4580:103f:c0de::3
Connecting to translate.codeberg.org
(translate.codeberg.org)|217.197.84.142|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 516 [text/html]
Saving to: ‘bit_16to9_960x540_mainwindow.png’
bit_16to9_960x540_mainwindow
100%[===========================================>] 516 --.-KB/s
in 0s
2026-04-18 12:48:38 (30.7 MB/s) - ‘bit_16to9_960x540_mainwindow.png’
saved [516/516]
$ file bit_16to9_960x540_mainwindow.png
bit_16to9_960x540_mainwindow.png: HTML document, ASCII text, with very
long lines (516), with no line terminators
$ cat bit_16to9_960x540_mainwindow.png
<!doctype html><meta content="1; url=?trans-rights=human-rights"
http-equiv=refresh><meta content="light dark"
name=color-scheme><title>Cookie monster!</title><body><p>This is an
automated check to get rid of most bots. If you have JavaScript enabled,
it should redirect to the real page soon. If you don't, it still should
redirect soon, but you can <a href="?trans-rights=human-rights">click
here</a> if you're
fast.</p><script>document.cookie="x-robot-challenge-2=passed;path=/";window.location.reload();</script>
-----/
So I would say that "Image format unknown" is exactly what the appstream
checker should say when it receives an HTML+JS challenge page rather
than a PNG image.
I assume that apps trying to consume the appstream data will have the
same problem as they too will not also not have js-aware or a
meta-refresh-aware browser built into them.
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--- End Message ---
