I use mini-dinstall as a staging repository that sits in front of an
aptly one. mini-dinstall is useful as it provides all the versions, and
aptly allows me to easily select the versions I want to use.

Aptly (versions before 1.0. THat is: versions before Buster) relies on
MD5 checksums of packages:
https://github.com/smira/aptly/issues/228
https://github.com/smira/aptly/issues/442

Mini-dinstall currently (as of c3615cbdcbf62ec275b047c6739c55a8a424c60b,
0.6.31) does not create MD5 checksums.

For my own archive the following patch was good enough:

diff --git a/mini-dinstall b/mini-dinstall
index 6655c37..ab45f88 100755
--- a/mini-dinstall
+++ b/mini-dinstall
@@ -1150,7 +1150,7 @@ class ArchiveDirIndexer(threading.Thread):
         cmdline = ['apt-ftparchive', type, dir,
                    '-o', 'APT::FTPArchive::AlwaysStat=true',
                    '-o', 'APT::FTPArchive::SHA1=false',
-                   '-o', 'APT::FTPArchive::MD5=false']
+                   '-o', 'APT::FTPArchive::MD5=true']
         if arch:
             cmdline += ['--arch', arch]
         if not nodb_mode:

Howdy,

I presume now that stable has aptly 1.0, which finally supports more than just
MD5, this is a moot point?

There's been a push to deprecate md5sum, and even sha1 in some places, so I
think at this point turning md5sum back on doesn't really make sense.


~Unit 193
Unit193 @ Libera
Unit193 @ OFTC

Howdy,

I presume now that stable has aptly 1.0, which finally supports more than just
MD5, this is a moot point?

There's been a push to deprecate md5sum, and even sha1 in some places, so I
think at this point turning md5sum back on doesn't really make sense.


~Unit 193
Unit193 @ Libera
Unit193 @ OFTC