Your message dated Fri, 15 Sep 2023 16:04:19 +0100
with message-id
<7cb762708020a0e2361ee102d02b2d9a63a126ce.ca...@adam-barratt.org.uk>
and subject line Re: Bug#612476: www.debian.org: Links to build logs logs
missing on https://buildd.debian.org/pkg.cgi?pkg=libpano13
has caused the Debian Bug report #612476,
regarding www.debian.org: Links to build logs logs missing on
https://buildd.debian.org/pkg.cgi?pkg=libpano13
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.)
--
612476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612476
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: www.debian.org
Severity: normal
Until recently the state column on
https://buildd.debian.org/pkg.cgi?pkg=libpano13 provided direct links
to the respective build logs. They are gone.
Also the logs link
(https://buildd.debian.org/build.cgi?pkg=libpano13&dist=sid) points to
a page with outdated information. - Build for info 2.9.17~beta2-1,
both sid and experimental have newer versions.
cu Andreas
--- End Message ---
--- Begin Message ---
On Tue, 2011-02-08 at 18:52 +0100, Andreas Metzler wrote:
> Until recently the state column on
> https://buildd.debian.org/pkg.cgi?pkg=libpano13 provided direct links
> to the respective build logs. They are gone.
>
> Also the logs link
> (https://buildd.debian.org/build.cgi?pkg=libpano13&dist=sid) points
> to
> a page with outdated information. - Build for info 2.9.17~beta2-1,
> both sid and experimental have newer versions.
>
I'm not sure what the specific issues in this case were, but the status
pages have been reworked in the meantime, and certainly now have the
links to logs (albeit in the "status" column, rather than "state").
Given that the report is now 12 years old, I'm going to take the
liberty of closing it and assuming that the issues have been resolved.
If you have current examples of problems, please either re-open the
report or file a new one.
Regards,
Adam
--- End Message ---
