Issues found in current buildd logs for libtk-img:
In the last run, there were no currently detectable issues found in the logs of libtk-img.Scanned logs (date is the date the log was generated, not the date it was scanned):
- alpha 1:1.4.16+dfsg1-1+b1 2024-03-09 16:56
- amd64 1:1.4.16+dfsg1-1+b1 2024-03-09 11:04
- arm64 1:1.4.16+dfsg1-1+b1 2024-03-09 10:53
- armel 1:1.4.16+dfsg1-1+b1 2024-03-12 10:01
- armhf 1:1.4.16+dfsg1-1+b1 2024-03-12 10:06
- hppa 1:1.4.16+dfsg1-1+b1 2024-03-09 10:38
- hurd-i386 1:1.4.16+dfsg1-1+b1 2024-03-09 18:34
- i386 1:1.4.16+dfsg1-1+b1 2024-03-09 11:11
- ia64 1:1.4.16+dfsg1-1+b1 2024-03-09 17:56
- loong64 1:1.4.16+dfsg1-1+b1 2024-03-09 10:54
- m68k 1:1.4.16+dfsg1-1+b1 2024-03-17 07:49
- mips64el 1:1.4.16+dfsg1-1+b1 2024-03-09 12:28
- powerpc 1:1.4.16+dfsg1-1+b1 2024-03-16 16:42
- ppc64 1:1.4.16+dfsg1-1+b1 2024-03-09 11:02
- ppc64el 1:1.4.16+dfsg1-1+b1 2024-03-09 10:39
- riscv64 1:1.4.16+dfsg1-1+b1 2024-03-09 14:07
- s390x 1:1.4.16+dfsg1-1+b1 2024-03-09 11:45
- sh4 1:1.4.16+dfsg1-1+b1 2024-03-15 07:07
- sparc64 1:1.4.16+dfsg1-1+b1 2024-03-09 13:15
- x32 1:1.4.16+dfsg1-1+b1 2024-03-09 13:07