Riccardo Mottola <[email protected]> writes: > posted this on NetBSD-sparc, but got no answer... so asking here, > maybe it is an infrastructure problem > > I was installing some stuff... and then pkg_add started failing! I > feared an issue on my stem or network, while, simply all packages > disappeared from the server: > > http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/sparc/ > > is empty! no 10.x no 9.x packages anymore. At least 10.0 was there and > 9.4 too I think. > > Something went wrong with the 10.0_2025Q3/ upload and previous > versions where deleted too? > > Riccardo
They were woefully out of date, and we have a policy of only the last three branches for a slow arch (and 2 for one that can be built in reasonable time) on the ftp server, because it has finite space, and running out of space causes all sorts of problems. Generally, contents of the ftp server are copied to archive.netbsd.org and are available there. The larger issue is that nobody within TNF seems to have been doing pkgsrc builds for sparc since the end of 2024. There's only so much data center space and electricity available to the people that do this as a community service. Builds take more than 3 months of full-tilt computing. If somebody who isn't TNF does e.g. sparc builds: while we won't post them on our server, we are happy to link to them in a SEE_ALSO file. For sparc packages on archive: https://archive.netbsd.org/pub/pkgsrc-archive/packages/NetBSD/sparc/ and in particular https://archive.netbsd.org/pub/pkgsrc-archive/packages/NetBSD/sparc/10.0_2024Q4/ https://archive.netbsd.org/pub/pkgsrc-archive/packages/NetBSD/sparc/9.0_2023Q3/All/ these are probably exactly what you were pointing to. Mostly that's just change the pkgin URL s/ftp/archive/ and s/pkgsrc/pkgsrc-archive/. It is routine for builds to age out of the server and only be on archive. What's unusual is that this is coincident with the lack of arrival of new sparc builds. As general information here is the list of package sets on ftp.netbsd.org, with columns being number of packages and kB. The 2024Q2 alpha and 2024Q3 sparc64 sets are too old to be on the server, and will be removed as soon as the 2025Q3 sets catch up. The good news is that there is good coverage of 10/11 for varying architectures, and also 9 for x86/arm. QUARTER: 2024Q2 24998 46464032 ./alpha/10.0_2024Q2 QUARTER: 2024Q3 25055 54695804 ./sparc64/10.0_2024Q3 QUARTER: 2025Q1 30408 66232004 ./powerpc/10.0_2025Q1 QUARTER: 2025Q2 26514 76851368 ./aarch64/10.0_2025Q2 20872 49485368 ./aarch64/9.0_2025Q2 24674 55567684 ./aarch64eb/10.0_2025Q2 4227 4187936 ./earmv4/9.0_2025Q2 22215 50386112 ./earmv6hf/10.0_2025Q2 21198 43769084 ./earmv6hf/9.0_2025Q2 25292 65915120 ./earmv7hf/10.0_2025Q2 24824 60436320 ./earmv7hf/9.0_2025Q2 25911 53790384 ./i386/10.0_2025Q2 23457 44188076 ./i386/9.0_2025Q2 9926 15142016 ./m68k/10.0_2025Q2 3415 2394692 ./m68k/9.0_2025Q2 21917 31126524 ./powerpc/9.0_2025Q2 10666 11355536 ./sh3el/10.0_2025Q2 9295 9135220 ./vax/10.0_2025Q2 27142 62503196 ./x86_64/10.0_2025Q2 27145 61159212 ./x86_64/9.0_2025Q2 QUARTER: 2025Q3 24958 78881980 ./aarch64/10.0_2025Q3 24889 78594272 ./aarch64/11.0_2025Q3 19894 55556588 ./aarch64/9.0_2025Q3 22644 53423844 ./aarch64eb/11.0_2025Q3 18042 42249412 ./alpha/10.0_2025Q3 12870 13911688 ./earmv4/10.0_2025Q3 2235 1558104 ./earmv4/11.0_2025Q3 20923 51316188 ./earmv6hf/10.0_2025Q3 21500 52593504 ./earmv6hf/11.0_2025Q3 19923 46635600 ./earmv6hf/9.0_2025Q3 23780 66315716 ./earmv7hf/10.0_2025Q3 23009 64862496 ./earmv7hf/11.0_2025Q3 23321 63580152 ./earmv7hf/9.0_2025Q3 24479 54523064 ./i386/10.0_2025Q3 24379 53980500 ./i386/11.0_2025Q3 24133 52987952 ./i386/9.0_2025Q3 7676 13773404 ./m68k/10.0_2025Q3 3085 2265620 ./m68k/11.0_2025Q3 18725 26520408 ./powerpc/10.0_2025Q3 1039 1383412 ./powerpc/11.0_2025Q3 12079 16196012 ./riscv64/11.0_2025Q3 3741 2579596 ./sh3el/11.0_2025Q3 14366 21553988 ./sparc64/10.0_2025Q3 6658 7689792 ./vax/10.0_2025Q3 3142 2024116 ./vax/11.0_2025Q3 25619 63072384 ./x86_64/10.0_2025Q3 25515 62856572 ./x86_64/11.0_2025Q3 25365 60889432 ./x86_64/9.0_2025Q3
