XPost: linux.debian.bugs.dist

Hi Ted,

On Sun, Jun 04, 2017 at 02:46:08PM -0400, Theodore Ts'o wrote:

I'm going to confess complete ignorance to what's going on with mips.
In the past my modus operandi is that I would make changes in response
to requests to the MIPS porters, in some cases with incomplete
understand why they were needed in the first place.

My bias would be to remove *all* of the mips specific exceptions in
the debian directory, and then see if things still build on mips, and
if there are any known problems caused by the mips installer or mips bootpath. And if we do need to add back any exceptions for the MIPS architecture, let's make sure it's very clearly documented why they
are there. Because at the moment, I'm a bit embarassed at my
inability to answer your perfectly reasonable questions. :-)

I think the approach is reasonable. I did put
debian-mips@lists.debian.org into X-Debbugs-Cc for this reason and am
full quoting your reply to that list now to have them object.

Does that seem reasonable? Are you willing to work with me to figure
out whether such a plan is going to cause problems with the installer
team, et. al? And I assume that because we're just about to release
Debian stable, this is really a post stretch activity, yes? Or is the current state sufficient undesirable that it rises to the level of
release critical? (I don't think so, but I'm willing to be
pursuaded.)

I actually thought that severity wishlist would have made it perfectly
clear that this is intended post-stretch, but I can spell it out
explicitly: No, I didn't expect this to be fixed in stretch.

The context of my work is making Debian cross buildable and
bootstrappable. Preferably, reproducibly. At least for the first part we
know roughly 1300 packages are cross buildable. So this bug really is a
drop in the bucket.

So let's give d-mips@l.d.o time to object until stretch is released.

Helmut

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.bugs.dist
To: 864144@bugs.debian.org
Copy: debian-mips@lists.debian.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Q1qWsEUEoWe9gPWOOKtGxaA0SvhsWnOud
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

On 04/06/17 20:51, Helmut Grohne wrote:

Hi Ted,

On Sun, Jun 04, 2017 at 02:46:08PM -0400, Theodore Ts'o wrote:

I'm going to confess complete ignorance to what's going on with mips.
In the past my modus operandi is that I would make changes in response
to requests to the MIPS porters, in some cases with incomplete
understand why they were needed in the first place.

My bias would be to remove *all* of the mips specific exceptions in
the debian directory, and then see if things still build on mips, and
if there are any known problems caused by the mips installer or mips
bootpath. And if we do need to add back any exceptions for the MIPS
architecture, let's make sure it's very clearly documented why they
are there. Because at the moment, I'm a bit embarassed at my
inability to answer your perfectly reasonable questions. :-)

I think the approach is reasonable. I did put
debian-mips@lists.debian.org into X-Debbugs-Cc for this reason and am
full quoting your reply to that list now to have them object.

From what I can tell, the only purpose of the extra mips libraries is to support some old bootloaders/firmware - arcboot being the only package I
know which used this. No "normal" packages in the archive would have
been able to use them unless they were statically linked. Since arcboot
was removed, I think it should be safe to remove these special libraries
from e2fsprogs.

Thanks,
James


--Q1qWsEUEoWe9gPWOOKtGxaA0SvhsWnOud--

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

iQIzBAEBCgAdFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlk0baEACgkQx/Fnbeot Ae/9uQ//d4xazBm3VbXrYCpMQTVOh8YmH/QFc3fJrYcB/GteL/YXU4KXyFDul/zb CglNd4kZjAAsNFeLPvudBj9HkFl7GADunCBAHfODgzPJ+ybBdXdmIC3ZGxaq7m4J T92uZ2XJ1U+d3ro7LXKXWUVQxKBPBQbHy1RwQr4VvfIojih4UuPecuSWAmvCZf9a ij6JnnKA/CT+M+OTGaY3hEe5Tu4lB76JdBwcJWghA/L3Vn5qMD0t9vTmQamJSBK4 8YtEWIKVPM787Kpf8hQBwuGNHXS849EOkfwlq1cDHQ4FH9BhgvfLaVYn/CWBdqDQ 4SqV0x1kIxdM+VPZ1EoXRl4wBxd9iOpaklUfS2VBAk9x/CJKAm/KkSxCiwRID9PV er0zuOud+Kqr/TgYeCWQeC3T7FPA2HfEF50+2ZCoC6sN2LU5VQ3KufenWQpiRrhx yFE5zdGJfVh0EPOf5Iqr7h1YKbA+UMarIArmW61LOiBB6pzKkb96hq3auxXiStQq vXLxiWNvZH1fUxhn4h0XJjeOgbj8q0w8nyH81cf9PyHpG24Bwja544DPPSo+A/3r gafBY/iKHm2jKuniYGdjvtAPSwRyb6HKsQNN0uem/GbJcQGPV+ZHMCyCtA7I8hTK KWqPLPjng2yblNke1Vm/aMt4z55OwNenTY5zAK5B/3LIMpW8c/8=
=li2e
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)