search

ntop / n2n

Peer-to-peer VPN
GNU General Public License v3.0
6.07k stars 927 forks source link

ntop packaging #1084

Open schoekek opened 1 year ago

schoekek commented 1 year ago

I use the apt repo at https://packages.ntop.org/apt-stable/bullseye to sync my local aptly instance. Unfortunately, all packages on https://packages.ntop.org are rebuilt, even if the version number in the package name has not changed. Occasionally, however, the content of the package changes slightly, so that the checksum no longer fits and error messages occur when synchronizing with aptly. For example: ERROR: unable to publish: unable to process packages: error linking file to /var/cache/aptly/public/pool/main/n/ntop-license/ntop-license_1.0_amd64.deb: file already exists and is different It should be ensured that the Debian guidelines are followed: https://www.debian.org/doc/debian-policy/ch-binary.html#uniqueness-of-version-numbers

Best regards carsten

hamishcoleman commented 1 year ago

This is indeed quite an annoying thing to happen. I dont have any insight into the ntop auto builder, so I cannot help from that end. But, I wonder if we can improve the build process to remove the slight changes.

Do you happen to have copies of two examples with the same version but different contents?

schoekek commented 1 year ago

Unfortunately no, because I deleted the relevant files. Also, these are not synchronized because the md5 sum is not correct despite the same serial number in the file name.

hamishcoleman commented 1 year ago

I'll download the daily over the next couple of days and see what I can see.

-- Use Linux! @.* ***** O- *** ... why haven't you indolent fleshers transformed the whole galaxy into chocolate?'' Give us time.''

schoekek commented 1 year ago

here is a current example: first md5 is currently in local repo cache and second is from current ntop package repo https://packages.ntop.org/apt-stable/bullseye/x64/ntop-license_1.0_amd64.deb

The md5 sums are different, but the package version number is 1.0.

md5sum /var/cache/aptly/public/pool/main/n/ntop-license/ntop-license_1.0_amd64.deb 95fac5d0a65da4e55d2dabeeaa6218f3 /var/cache/aptly/public/pool/main/n/ntop-license/ntop-license_1.0_amd64.deb md5sum /home/schoekek/ntop-license_1.0_amd64.deb f3cadb0ae87b554e76d12b389acdd588 /home/schoekek/ntop-license_1.0_amd64.deb

hamishcoleman commented 1 year ago

I've grabbed two different daily builds of the n2n package and was able to find three places in them that differ from build to build. Two of these are things that I can fix in the n2n internal build process to remove, but one is caused by some extra steps that the packages.ntop.org is applying - and I have no visibility or control over.

schoekek commented 1 year ago

@lucaderi can you help?