Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

On 2019-04-14 15:14, Samuel Thibault wrote:
> Svante Signell, le dim. 14 avril 2019 14:29:48 +0200, a ecrit:
> > On Sun, 2019-04-14 at 11:33 +0200, Samuel Thibault wrote:
> > > Svante Signell, le dim. 14 avril 2019 10:52:19 +0200, a ecrit:
> > > > 
> > > > I cannot follow your reasoning here, e.g. at  
> > > > http://ftp.ports.debian.org/debian-ports/pool-hurd-i386/main/g/glibc/
> > > > there are no source packages, only binary ones. How would I ever
> > > > get
> > > > hold of your source changes to build that version of glibc?
> > > 
> > > That version of glibc is in the "unreleased" distribution, not
> > > "unstable". See the main/binary-hurd-i386/Packages.gz files of the
> > > different distribs:
> > > 
> > > http://ftp.ports.debian.org/debian-ports/dists/
> > 
> > Yes, the glibc version is there, but where are the sources, i.e.
> > the *2.27.orig.tar.*, *2.27-8+hurd.1.debian.tar.* and *2.27-
> > 8+hurd.1.dsc files?

First of all note that hurd-i386 on debian-ports is a bit peculiar as
only the unreleased suite is available. This package should have been
obsoleted by the newer 2.28 versions from unstable now that they are
also buildable on hurd.

There are two issues there.
- The original upload doesn't contain the source files, that's why there
  are not available. If the upload had contained the sources file, they
  would have been present in the same directory.
- The upload should have been rejected as the sources are not present.
  This works for other architectures, so there is probably a bug in
  mini-dak which doesn't check that properly for architectures with only
  unreleased.

> They were not uploaded at the time. I don't know if the current
> debian-port upload queue can now take them for the unreleased distrib.

mini-dak is based on .changes file. For that you need to upload the
source and binaries all together.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
[email protected]                 http://www.aurel32.net

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlyzPs8ACgkQE4jA+Jno
M2tSLQ/+PyRfn7U7Feid2SWXxyjwtoSkcR2d9k8MkzQBBSI+BaP+3g7r3gzSiVgA
kmDWraylvJfISLHj6wjwTSnd1c74jqSylnsXoPkgbP0Ykb+YrIVjPT8aXH6T/0+w
WO2U+sYUTP2cnRD1HrnGRiaEl66hxNaecopWXzczxodPZVdkYDw7ygyQ/PdVhjJz
OC2ao2RMGoAJN08Wx+t8mxm8JggUKxrPtcvT3FXABbApkE3Ps/AKN6WrZQgEJDjc
D5yLa8GQvLiGA2ehA653JORrGFCEkqZU5r11RKXv7O8DbN6zSaEnf/ZJ+wLIsive
i0q8gnOZJEwfxU4MRxFlsrCgm6OQKW2357KA0sa0KQ3UL1Z2M9ovAqdahrfcsDWx
GhSTa7mTr5ZSkP6DtkvcSwJszCHsXLbErrG3Qz2Z68/M/e0WW7r6X3CKeAyWZ15w
LPSeE34j9d8Mnaok2O0RBF4yx63W9ENZvQrHPzIPFF+7A0bJXVFsr8bBCdT3lqxT
HR6SbR3gsH0gVS43LLwEMcOMJ8pVPRpjrDwzj1E1omImM0lY4sDUiBYik7KfUyYl
s70qyYxlDlpC4Yw8i5+1N4OaA2VDLX7AyXdTvqjlnWFIFKNKDPNGIji6KIUrGh40
4tcIXYeiqplkwmSzRjaXS9WBvS8CdRKLbKiwraxr+wWWiXGf2/M=
=cIT/
-----END PGP SIGNATURE-----