| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Compare SHA256 to check if versions are really the same | Julian Andres Klode | 2023-08-02 | 1 | -0/+11 |
| | | | | | | | | | | | | | | If we know both SHA256, and they're different, the packages are. This approach stores the SHA256 only at runtime, avoiding the overhead of storing it on-disk, because when we update repositories we update all of them anyhow. Note that pkgCacheGenerator is hidden, so we can just modify its ABI, hooray. Closes: #931175 LP: #2029268 | ||||
| * | Test that tiny differences result in different versions | David Kalnischkies | 2021-06-10 | 1 | -0/+98 |
| Just because two packages have the same version number doesn't mean it is the same package. APT can detect rebuilds and other "inconsistencies", but we had no explicit test for it so far. It turned out to be the wrong track in this branch, but as I wrote it already, lets add it at least. Gbp-Dch: Ignore | |||||
 |
index : apt | |
| Debians commandline package manager |
| summaryrefslogtreecommitdiff |