Package: ftp.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear FTP Masters,

As of Reposurgeon 4.0, the Python-to-Go conversion has been completed
with major performance improvement.

However, as Debian buildd results for 4.2-1 show, reposurgeon
no longer builds on 32-bit architectures:
https://buildd.debian.org/status/logs.php?pkg=reposurgeon&ver=4.2-1

I inquired upstream at https://gitlab.com/esr/reposurgeon/issues/255,
and author Eric S. Raymond @esr replied:

    I haven't bothered to keep the code 32-bit-compatible because
    4GB isn't enough address space for medium to large large
    repository conversions.  The manual page already says:

    Because the code is designed for dealing with large data sets,
    it has been optimized for 64-bit machines and no particular effort
    has been made to keep it 32-bit clean.  Various counters may
    overflow if you try using it to lift a large repository on a
    32-bit machine.

When Julien Rivaud suggested replacing int by int64 throughout the code,
Eric further replied:

    @frnchfrgg Unfortunately changing int to int64 would be
    more of a pain than you've perhaps realized yet.
    Range clauses and various system-library things are wired to int;
    we'd have to add an annoying number of castS and var statements
    to fix that.

    I don't think it's worth the complexity increment.  After
    fifteen years of adverse selection, repositories small enough
    not to blow out a 4GB limit but not already converted are
    increasingly rare, meaning that a true 32-bit build is not
    much good for anything but passing its own regression tests.
    I wrote about the adverse-selection effect in 2014:
    http://esr.ibiblio.org/?p=6216

Soon after, Eric updated the INSTALL documentation
https://gitlab.com/esr/reposurgeon/-/blob/master/INSTALL.adoc:

    You will need 64-bit hardware. This code is not intended to
    run on 32-bit machines (which have an address space too small to be
    useful for repository surgery) and won't build on them.


So, I went ahead to remove [armel armhf i386 mipsel] from Architecture
list in debian/control:
See https://salsa.debian.org/debian/reposurgeon/commit/5f8db4c

And proceeded to file this Bug report to you so as to allow
reposurgeon to be migrated to testing.

Many thanks!

Anthony Fok


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

iQIzBAEBCAAdFiEEFCQhsZrUqVmW+VBy6iUAtBLFms8FAl5IX9wACgkQ6iUAtBLF
ms+n/w/+IRwi/WS1Gc69DL0jmhG86WdmFJLmoxIcAiFAAf6LighG3Ix8lxi1oON5
poUEaCHsUF9ktzenUekLxVafJA4YxlducMdIyk9zlhKUQfdrVL1uDZwkE6FS0ZAT
QRUApk4BsABX1uDvERXc+4pBWcif1/SLLyY3J5SRtDXFjLbXLD9rNT9QuDanFiL2
nN0eDzhy61s0nlNUdGTjl5i9EPVY9m253FHV7U93oNQRPjJFhVWGphAGzdImjpk1
hxl1qiSIRbO/d9OHbNPporp4YoSdCOIlGsitQAyWn5JLQZlD1GIJSOw3FDsxi2DX
QMNEWG0t3hto6UhxjSsbodpHWD3YunOppwDYiJR34Bj760iPhTYvDIlKEuWcMFSK
OKlYthnd53XuewJRHZ/ADsvW5EJ7QYroIMCf6RcR4+MC738EK8ZkILxB8MDIbiRI
l3+F59yD3cm3rWZUIzFxycvTZakUzw72hAWlb7n5z5tB9+G29rk5wbl9Lvg/3C2e
dH/oDw0VkiQo6ATPHm8Kj0uvhqS+86D9QfczFynsVd0xyp0ZE7av7KQZHtk1G95m
ujx9lHpWSTZmHvcMpCIhCSaROVmV3RTgpFvsxCi/5oRgG170iTVGSMKBxNcBrETM
BZ/Tx/IIlM1gFwhCdEzNMaFYblU60g+yA8XgCW7kjct24t0UWgI=
=iBtj
-----END PGP SIGNATURE-----

Reply via email to