Comments on: Buildd status pages http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/ Crazy world, crazy thoughts ... crazy blog ! Thu, 05 Jan 2012 07:01:06 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Mehdi http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/comment-page-1/#comment-7480 Mehdi Thu, 17 Jun 2010 09:54:05 +0000 http://blog.dogguy.org/?p=127#comment-7480 That's already done for backports.org as you can see in [1] (it was announced recently [2]). Concerning, debian-ports.org, they should update their setup first to be able to use the new implementation. AFAIK, they don't use any PGSql database yet. [1] https://buildd.debian.org/status/package.php?p=pkglab&suite=lenny-backports [2] http://lists.debian.org/debian-devel-announce/2010/01/msg00005.html That’s already done for backports.org as you can see in [1] (it was announced recently [2]). Concerning, debian-ports.org, they should update their setup first to be able to use the new implementation. AFAIK, they don’t use any PGSql database yet.

[1] https://buildd.debian.org/status/package.php?p=pkglab&suite=lenny-backports
[2] http://lists.debian.org/debian-devel-announce/2010/01/msg00005.html

]]> By: foo http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/comment-page-1/#comment-7477 foo Thu, 17 Jun 2010 02:27:02 +0000 http://blog.dogguy.org/?p=127#comment-7477 Please get your new implementation installed on buildd.debian-ports.org and on the backports.org buildds. Please get your new implementation installed on buildd.debian-ports.org and on the backports.org buildds.

]]> By: Cùran http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/comment-page-1/#comment-7476 Cùran Wed, 16 Jun 2010 20:41:42 +0000 http://blog.dogguy.org/?p=127#comment-7476 Another option for packages without a log would be to query the projectdb (something like rmadison/dak ls with dates). Another option for packages without a log would be to query the projectdb (something like rmadison/dak ls with dates).

]]> By: Mehdi http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/comment-page-1/#comment-7475 Mehdi Wed, 16 Jun 2010 20:06:27 +0000 http://blog.dogguy.org/?p=127#comment-7475 Thanks! Unfortunately, the database says that it (plasma-widget-yawp) was last modified on "2010-05-03 13:50:39", which corresponds to the date of the last upload (the last time there was a change on that arch for that package). That should be fixed in the database. In the meantime, I can skip the "For" field for "Installed" packages with "no log" (most likely packages uploaded by their maintainer), but that's only a workaound to hide some outdated information. Same thing for cmake. Workaround applied in https://buildd.debian.org/~mehdi/pgstatus/package.php?p=plasma-widget-yawp Thanks!

Unfortunately, the database says that it (plasma-widget-yawp) was last modified on “2010-05-03 13:50:39″, which corresponds to the date of the last upload (the last time there was a change on that arch for that package). That should be fixed in the database. In the meantime, I can skip the “For” field for “Installed” packages with “no log” (most likely packages uploaded by their maintainer), but that’s only a workaound to hide some outdated information.

Same thing for cmake.

Workaround applied in https://buildd.debian.org/~mehdi/pgstatus/package.php?p=plasma-widget-yawp

]]> By: Cùran http://blog.dogguy.org/index.php/2010/06/16/buildd-status-pages/comment-page-1/#comment-7474 Cùran Wed, 16 Jun 2010 19:48:08 +0000 http://blog.dogguy.org/?p=127#comment-7474 Hi Mehdi, first, let me thank you for your efforts! Now, I'd like to point out a small bug (I'm not sure, it's in your code or just exposed by it) to you: the binary uploaded with the package itself, say the amd64 binaries, have a wrong timespan given in the "For" column, see e.g. [0], where the upload of the latest version happened just two days ago, so there is no way, it can have the status installed with that version for (atm) over 44 days. I see similar offsets for other packages I (co-)maintain, e.g. [1]. Thanks, Cùran [0] https://buildd.debian.org/status/package.php?p=plasma-widget-yawp [1] https://buildd.debian.org/status/package.php?p=cmake Hi Mehdi,
first, let me thank you for your efforts!

Now, I’d like to point out a small bug (I’m not sure, it’s in your code or just exposed by it) to you: the binary uploaded with the package itself, say the amd64 binaries, have a wrong timespan given in the “For” column, see e.g. [0], where the upload of the latest version happened just two days ago, so there is no way, it can have the status installed with that version for (atm) over 44 days. I see similar offsets for other packages I (co-)maintain, e.g. [1].

Thanks,
Cùran

[0] https://buildd.debian.org/status/package.php?p=plasma-widget-yawp
[1] https://buildd.debian.org/status/package.php?p=cmake

]]>