It seems that instead of the oryginal minicom-2.3.tar.gz there is a minicom-2.2.tar.gz renamed to minicom-2.3.tar.gz. Both minicom-2.2.tar.gz and minicom-2.3.tar.gz are identical. # grep minicom-2...tar.gz /usr/portage/net-dialup/minicom/Manifest DIST minicom-2.2.tar.gz 720536 RMD160 2796e731078507160c466e952f3c9f6144b9c3f4 SHA1 75018c283f0d037d49a93fa077a186adde263569 SHA256 cc0406714ece77f5b1b1cb9e85e937531de556a72f962a3532c02da41b154d64 DIST minicom-2.3.tar.gz 720536 RMD160 2796e731078507160c466e952f3c9f6144b9c3f4 SHA1 75018c283f0d037d49a93fa077a186adde263569 SHA256 cc0406714ece77f5b1b1cb9e85e937531de556a72f962a3532c02da41b154d64 root:/usr/portage/distfiles# ls -l minicom-2.* -rw-rw-r-- 1 portage portage 720536 Oct 31 2006 minicom-2.2.tar.gz -rw-rw-r-- 1 portage portage 720536 Apr 15 02:28 minicom-2.3.tar.gz root:/usr/portage/distfiles# md5sum minicom-2.* 13933c8777839f00e3730df23599dc93 minicom-2.2.tar.gz 13933c8777839f00e3730df23599dc93 minicom-2.3.tar.gz The oryginal minicom-2.3.tar.gz is different: # md5sum minicom-2.3.tar.gz 0ebe7a91898384ca906787cc4e2c3f25 minicom-2.3.tar.gz # ls -l minicom-2.3.tar.gz -rw-r--r-- 1 root root 789162 Apr 19 02:52 minicom-2.3.tar.gz Reproducible: Always Steps to Reproduce:
Believe it or not, I've downloaded that file from the home page, so I suggest you to verify on the homepage first.
No, I'm not going to waste tour time: yes, I did it before I committed my bug report. The file in the "URL:" filed of this bug is different and it comes exactly from http://alioth.debian.org/projects/minicom/ http://alioth.debian.org/frs/?group_id=30018: 2.3 2008-02-24 12:18 minicom-2.3.tar.gz 771 KB 2.2 2006-10-16 08:10 minicom-2.2.tar.gz 704 KB BTW: what good is releasing an old, *identical* version as a new one?
Ah, you're right! Seems that $STUPID_NUM is the one that selects minicom version after all. Dumb way to publish your release if you ask me... Anyway, fixed in minicom-2.3-r1. Thanks!
