Hi Adam, Thanks for following up. Responses are inline. We expect at least the Maintainer and Upstream-mirror values to be filled > in, > and your trace file is missing one or both of them. >
I've updated our ftpsync.conf, this shouldn't be an issue anymore. armel, mipsel and s390x are all currently supported architectures and > would be expected to appear on all Debian mirrors. > We don't currently have the disk space to support more architectures but plan to be able to accommodate this in the future. Let us know if you have more questions, thanks. -- Amber Jennings (she/her) | Computer Action Team (503) 725-5420 | CC: supp...@cat.pdx.edu https://cat.pdx.edu | https://support.cat.pdx.edu On Fri, Mar 22, 2024 at 10:33 AM Adam D. Barratt <a...@adam-barratt.org.uk> wrote: > Control: tags -1 + moreinfo > > Hi, > > Apologies for the delay in getting back to you. > > On Mon, 2023-12-11 at 23:52 +0000, Sage Imel wrote: > > Site: mirrors.cat.pdx.edu > > Archive-architecture: amd64 arm64 armhf hurd-amd64 i386 riscv64 > > Our automated checks noticed an issue with your mirror: > > o The trace file at > http://mirrors.cat.pdx.edu/debian/project/trace/mirrors.cat.pdx.edu > is missing some required information. > > We expect at least the Maintainer and Upstream-mirror values to be > filled in, > and your trace file is missing one or both of them. > > As an additional note, is there a reason that you only mirror a subset > of Debian's official architectures? > > Architectures-Configuration: EXCLUDE alpha arm armel hppa hurd-i386 ia64 > kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc s390 s390x sh sparc > > armel, mipsel and s390x are all currently supported architectures and > would be expected to appear on all Debian mirrors. > > Regards, > > Adam >
