[RTFACT-12794] Enable the "Acquire-By-Hash" feature for Debian repositories Created: 07/Nov/16  Updated: 10/Dec/17  Resolved: 08/May/17

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Debian, Metadata
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Nihal Reddy Chinna Choudhary Assignee: Liza Dashevski (Inactive)
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: 1 week, 2 days
Time Spent: Not Specified
Original Estimate: 1 week, 2 days

Issue Links:
Duplicate
duplicates RTFACT-12604 Add support for debian "Acquire-by-ha... Resolved
Estimated Resolution Quarter: Q2-17
Support Tickets:

Express Scripts - Support Case, Ericsson Canada - Support Case

Product Backlog: 17-Q1-leaps
Internal Priority: High
Sprint: Leap 13

 Description   

Enable the "Acquire-By-Hash" feature for Debian repositories. This is documented in the official Debian specification:
https://wiki.debian.org/RepositoryFormat#Acquire-By-Hash

With this improvement we will be able to better handle the scenarios where we receive hashsum mismatch errors. When this is enabled the Packages file will be requested by hash value and not by the location given in the Release file



 Comments   
Comment by Uriah Levy [ 07/Nov/16 ]

see:

Comment by Byron Miller [ 11/Apr/17 ]

We're seeing the race condition on our Ubuntu 16.04 instances.

From our puppet runs:

Error: /Stage[main]/Apt::Update/Exec[apt_update]/returns: change from notrun to 0 failed: /usr/bin/apt-get update returned 100 instead of one of [0]
Notice: /Stage[main]/Apt::Update/Exec[apt_update]/returns: Err:23 https://artifactory.mydomain.com/artifactory/Ubuntu xenial-security/main amd64 Packages
Notice: /Stage[main]/Apt::Update/Exec[apt_update]/returns:   Hash Sum mismatch

Any chance we can get this patched into 5.2+?

Comment by Guo Peng Liang [ 01/Aug/17 ]

From my understanding, this has not been resolved yet? This is marked as "RESOLVED" but duplicated to RTFACT-12604, which is still "Ready For Code Review"...

Generated at Mon Dec 16 11:41:19 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.