On Sat, 2024-05-25 at 10:06 +0200, Holger Wansing wrote: > > > Am 24. Mai 2024 20:16:35 MESZ schrieb Holger Wansing <hwans...@mailbox.org>: > > > > > > Am 24. Mai 2024 20:10:35 MESZ schrieb Thomas Lange <la...@cs.uni-koeln.de>: > > > > > > > > On Fri, 24 May 2024 20:02:35 +0200, Holger Wansing > > > > > > > > <hwans...@mailbox.org> said: > > > > > > > Hi Thomas, > > > > you fixed this in master branch. > > > > Are you sure about this? > > > > I somehow seem to remember, that debian-master branch is used for > > > packages.d.o ... > > > you are right, debian-master seems to be the correct branch. > > > I will fix it also in debian-master. > > > > > > Do you know if the branch master is used for anything? > > > > Don't know. > > Maybe we should just make debian-master the default branch (instead of the > master one)?
As far as I know the master branch is the shared code between packages.debian.org and packages.ubuntu.com. This is just another indication that packages.debian.org is undermaintained. Seriously, how can I join the team force in making changes to packages.debian.org? I have been looking for a solution since I became a Debian Developer (which is 2017). * The latest pending issue that I care is https://lists.debian.org/debian-www/2023/12/msg00029.html , and it is still not solved yet. * And the continuous 503 Service Unavailable error, which lasted for more than several months and indicates a broken backend instance, is also not resolved: -> % LC_ALL=C wget -vv https://packages.debian.org/unstable/wget2-dev --2024-05-28 15:41:34-- https://packages.debian.org/unstable/wget2-dev Resolving packages.debian.org (packages.debian.org)... 128.31.0.51, 195.192.210.132, 2a02:16a8:dc41:100::132, ... Connecting to packages.debian.org (packages.debian.org)|128.31.0.51|:443... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2024-05-28 15:42:56 ERROR 503: Service Unavailable. Thanks, Boyuan Yang
signature.asc
Description: This is a digitally signed message part
