- Jun 09, 2022
-
-
Chuan Liu authored
-
- Jun 06, 2022
-
-
myml authored
-
- Apr 29, 2022
-
-
Chuan Liu authored
-
- Apr 27, 2022
-
-
Russell Greene authored
-
Russell Greene authored
-
- Apr 25, 2022
-
-
Samuel Mutel authored
-
Chuan Liu authored
-
- Apr 13, 2022
-
-
Benj Fassbind authored
-
- Apr 12, 2022
-
-
Markus Muellner authored
-
Markus Muellner authored
-
- Apr 05, 2022
-
-
Benj Fassbind authored
-
Benj Fassbind authored
-
Benj Fassbind authored
-
Benj Fassbind authored
-
Benj Fassbind authored
-
- Apr 04, 2022
-
-
Benj Fassbind authored
-
Reinhold Gschweicher authored
-
Ubuntu authored
-
Matt Bearup authored
-
- Mar 30, 2022
-
-
Maciej Gol authored
-
- Feb 13, 2022
-
-
Lorenzo Bolla authored
Fix #1032
-
Lorenzo Bolla authored
Fix #1034
-
- Feb 11, 2022
-
-
Benj Fassbind authored
-
- Feb 08, 2022
-
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
- Feb 05, 2022
-
-
Luciano Lionello authored
-
- Jan 31, 2022
-
-
Ratchanan Srirattanamet authored
dpkg-gencontrol can be called with -v flag which set binary package's version separated from source version. When this happen, the Source field will contain version number in addition to source package name. This tripped Aptly's dbgsym restriction, which check for exact source package name, which in turn prevents the dbgsym & the whole .changes file from being imported. From the git history, it seems like this condition is a leftover from when Aptly filter dbgsym packages using "*-dbgsym". So, I decided to remove it. A test case has been added to prevent regression.
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
We use go modules now.
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
Also, update "pkg/errors" library.
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-
Lorenzo Bolla authored
-