#815202 packages: machines and sponsors information is outdated

Package:
www.debian.org
Source:
www.debian.org
Submitter:
Paul Wise
Date:
2024-05-25 09:39:03 UTC
Severity:
minor
#815202#5
Date:
2016-02-20 01:26:23 UTC
From:
To:
The packages site says the two packages mirrors are piatti and rore but
these were decommissioned a long time ago. It would be best to generate
the machines and sponsors info from Debian LDAP on a regular basis so
that this information never gets out of date. Some combination of
the description, purpose, sponsor and allowedGroups LDAP fields should
be enough to find the right hosts and display the right info. picconi
and pkgmirror-1and1 are the current hosts for this service.

https://packages.debian.org/about/sponsors.html
#815202#10
Date:
2016-03-29 08:31:25 UTC
From:
To:
Patches welcome ;)
#815202#15
Date:
2016-03-31 23:21:38 UTC
From:
To:
Le 29/03/2016 10:31, Frank Lichtenheld a écrit :


Sorry, it's not a patch...


Perhaps the script https://db.debian.org/machines.cgi could be a code
base. picconi and pkgmirror-1and1 are listed in this page:

"""
picconi.debian.org packages.debian.org master [...]
pkgmirror-1and1.debian.org packages.debian.org mirror [...]
"""

I don't know in which repository ./machines.cgi is (at least not in the
website repo).
#815202#20
Date:
2016-04-01 04:43:53 UTC
From:
To:
DSA would very much like to kill the existing codebase behind the
db.d.o website in favour of a rewrite in django:

https://github.com/Debian/ud

The existing codebase is available here:

https://anonscm.debian.org/cgit/mirror/userdir-ldap-cgi.git/tree/machines.cgi
#815202#25
Date:
2016-04-05 01:05:03 UTC
From:
To:
Le 01/04/2016 06:43, Paul Wise a écrit :

There are no commit since two years, so I'm not sure it's still alive.

I tried to extract the useful code from the script. It depends on the
libnet-ldapapi-perl package and the configuration of the machine which
is running the LDAP.

The syntax is correct but I can't run it on the machine (I don't have
the access rights).

However, I wonder if this perl script is the best strategy:

- Perhaps providing the full data in JSON format by db.d.o would provide
an easy access for several Debian services/tools.
- Or providing a python script which could be reused by the django site
in the future?

Whatever the chosen solution, I can't try to it due to lack of access
rights. (I think it's normal I don't have it.)
#815202#30
Date:
2016-04-05 05:06:57 UTC
From:
To:
Nevertheless, it is the way forward.

The Debian LDAP can be accessed from any machine, anonymous access
will only return the public data (including hostname stuff). So you
shouldn't need to run on db.d.o nor read the config file at all.

Direct LDAP access should be machine-readable enough for almost all
services and others can easily add a proxy script.

I agree that any future machines list in ud (one doesn't exist yet)
should have some filtering options.
#815202#35
Date:
2016-04-05 23:39:02 UTC
From:
To:
Le 05/04/2016 07:06, Paul Wise a écrit :

Thank you for these infos, I ignored them. :-)

I attached 2 scripts (one in Perl, one in Python) allowing to get the
names of the machines providing packages.debian.org service. I think
some checks about LDAP errors could be added but it's a start.

I guess the perl script could be included in order to fix the current
bug report.
#815202#40
Date:
2016-04-17 21:47:44 UTC
From:
To:
Le 05/04/2016 07:06, Paul Wise a écrit :
Perhaps I am wrong but
https://github.com/Debian/ud is the future for the ldap web interface
(db.debian.org), not for packages.debian.org, isn't it?



To merge the previous Perl patch to packages.debian.org:
- clone http://anonscm.debian.org/cgit/webwml/packages.git/ repository,
check out to the debian-master branch
- move the template static/about/sponsors.tmpl templates/html/
- create a new module lib/Packages/DoAboutSponsors.pm. The request to
the LDAP would be inserted inside.
- modify (at least) lib/Packages/Dispatcher.pm by:
 - including DoAboutSponsors.pm
 - modify do_dispatch to bind the url to the new module. (I didn't
understand it completely)

(I fail to write the patch so I wrote the previous paragraph in hope  it
could help someone else.)

I can do a pull/request to github with a modified version of the
previous code if you want.
#815202#45
Date:
2016-04-17 23:04:32 UTC
From:
To:
Correct.
#815202#50
Date:
2016-12-24 03:03:58 UTC
From:
To:
Dear Customer,

This is to confirm that your item has been shipped at December 23.

Please check the attachment for complete details!

With appreciation,
Kyle Akers,
USPS Senior Station Manager.
#815202#55
Date:
2016-12-26 18:21:00 UTC
From:
To:
Dear Customer,

Your item has arrived at the USPS Post Office at December 23, but the courier was unable to deliver parcel to you.

Please check the attachment for details!

Kind thoughts,
Leonard Hicks,
USPS Parcels Operation Manager.
#815202#60
Date:
2016-12-27 10:22:54 UTC
From:
To:
Dear Customer,



Your item has arrived at the USPS Post Office at December 24, but the courier was unable to deliver parcel to you.



You can find more details in this e-mail attachment!



All the best,

Herbert Schaefer,

USPS Senior Support Manager.
#815202#65
Date:
2017-01-01 10:49:43 UTC
From:
To:
Dear Customer,



USPS courier was unable to contact you for your parcel delivery.



Please check the attachment for complete details!



Yours sincerely,

Herbert Lambert,

USPS Office Manager.
#815202#70
Date:
2024-05-25 09:32:03 UTC
From:
To:
No progress for the last 7 years :-(

I have just updated the sponsors list manually for now.


Holger