Repo error

[thelamer]

Today started getting back

E: Failed to fetch https://dl.bintray.com/fedarovich/qbittorrent-cli-debian/dists/bionic/main/binary-amd64/Packages.gz  File has unexpected size (1103 != 1270). Mirror sync in progress? [IP: 34.214.69.171 443]

   Hashes of expected file:

    - Filesize:1270 [weak]

    - SHA256:8a7a3f1c110618151ef5611cea972bec95f17d72b0888ca569cc7814699d122b

    - SHA1:91e02eb198a48d3b9f0a7970f5f8f59b77c5703d [weak]

    - MD5Sum:23fd0c84047b6960e84731f1f4dcff0f [weak]

   Release file created at: Tue, 17 Dec 2019 06:45:46 +0000

Let me know if you need anymore information .

[basecaseFM]

I'm confused. What can be achieved with this project that cant be done with the webui?

On Tue, Dec 17, 2019, 10:14 PM Ryan Kuba notifications@github.com wrote:

Today started getting back

E: Failed to fetch https://dl.bintray.com/fedarovich/qbittorrent-cli-debian/dists/bionic/main/binary-amd64/Packages.gz File has unexpected size (1103 != 1270). Mirror sync in progress? [IP: 34.214.69.171 443]

Hashes of expected file:

- Filesize:1270 [weak]

- SHA256:8a7a3f1c110618151ef5611cea972bec95f17d72b0888ca569cc7814699d122b

- SHA1:91e02eb198a48d3b9f0a7970f5f8f59b77c5703d [weak]

- MD5Sum:23fd0c84047b6960e84731f1f4dcff0f [weak]

Release file created at: Tue, 17 Dec 2019 06:45:46 +0000

Let me know if you need anymore information .

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fedarovich/qbittorrent-cli/issues/25?email_source=notifications&email_token=ACPKYIFUYERMTEEGRJVVGJDQZG5V7A5CNFSM4J4F62F2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBHXAWA, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPKYIAZV3J7IKO32ZU5K6TQZG5V7ANCNFSM4J4F62FQ .

[fedarovich]

I guess, there was some issue with bintray servers. It seems to work now.

[thelamer]

No still busted on my side https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-qbittorrent/detail/master/168/pipeline

[fedarovich]

Hm, I can't understand what's hapenning. Yes, it fails when I try to build your Dockerfile.

But it installs normally if I install it on a usual Ubuntu Bionic system. So if manually run all your commands from RUN section of your Dockerfile it installs successfully.

Do you have any ideas?

[thelamer]

Let me debug on my side I did no further testing outside of the docker build.

[thelamer]

The information is accurate:

curl -sL https://dl.bintray.com/fedarovich/qbittorrent-cli-debian/dists/bionic/main/binary-amd64/Packages.gz | md5sum
81a63559cb09c6c921477315a433e720  -
curl -sLI https://dl.bintray.com/fedarovich/qbittorrent-cli-debian/dists/bionic/main/binary-amd64/Packages.gz |grep Content-Length
Content-Length: 1103

curl -sL https://dl.bintray.com/fedarovich/qbittorrent-cli-debian/dists/bionic/Release | grep main/binary-amd64/Packages.gz
 23fd0c84047b6960e84731f1f4dcff0f             1270 main/binary-amd64/Packages.gz

That Release file needs to be regenerated against the current files in the repo.

[thelamer]

Looks like for bintray you can trigger a metadata calculation using their api:

curl -X POST -umyuser:<API_KEY> https://api.bintray.com/calc_metadata/myorg/myrepo/

Reference: https://www.jfrog.com/confluence/display/BT/Bintray+REST+API#BintrayRESTAPI-ScheduleMetadataCalculation https://blog.bintray.com/2014/12/16/hosting-debian-packages-on-bintray-rocks/

[fedarovich]

Thank you for your help! It seems to work now.

[thelamer]

No, thank you for taking the time to troubleshoot this. You might want to shift to the non V1 endpoint here: https://github.com/fedarovich/qbittorrent-cli/blob/master/setup/linux/publish-packages.sh#L34 Though this just might be a one off sync problem.

[fedarovich]

Yes, I guess I should update this script.