The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

Index of /debian/pool/main/libc/libcrypt-twofish-perl/


../
libcrypt-twofish-perl_2.17-2+b1_amd64.deb          01-Nov-2018 16:29               17492
libcrypt-twofish-perl_2.17-2+b1_arm64.deb          01-Nov-2018 13:59               18572
libcrypt-twofish-perl_2.17-2+b1_i386.deb           01-Nov-2018 14:41               17960
libcrypt-twofish-perl_2.17-2.debian.tar.xz         30-Sep-2017 15:04                3020
libcrypt-twofish-perl_2.17-2.dsc                   30-Sep-2017 15:04                2299
libcrypt-twofish-perl_2.17.orig.tar.gz             05-Nov-2013 12:53               13851
libcrypt-twofish-perl_2.18-1+b2_amd64.deb          20-Oct-2022 19:41               17672
libcrypt-twofish-perl_2.18-1+b2_arm64.deb          20-Oct-2022 16:27               17668
libcrypt-twofish-perl_2.18-1+b2_i386.deb           20-Oct-2022 17:18               17656
libcrypt-twofish-perl_2.18-1+b5_amd64.deb          15-Oct-2024 09:51               18048
libcrypt-twofish-perl_2.18-1+b5_arm64.deb          15-Oct-2024 10:07               18148
libcrypt-twofish-perl_2.18-1+b5_i386.deb           15-Oct-2024 09:46               17908
libcrypt-twofish-perl_2.18-1.debian.tar.xz         28-Nov-2020 03:11                2748
libcrypt-twofish-perl_2.18-1.dsc                   28-Nov-2020 03:11                2453
libcrypt-twofish-perl_2.18-1_amd64.deb             28-Nov-2020 04:28               18020
libcrypt-twofish-perl_2.18-1_arm64.deb             28-Nov-2020 04:28               18248
libcrypt-twofish-perl_2.18-1_i386.deb              28-Nov-2020 04:28               17680
libcrypt-twofish-perl_2.18.orig.tar.gz             28-Nov-2020 03:11               13904

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.