Age | Commit message (Collapse) | Author | Files | Lines |
|
This will make it possible to track key/value attributes for each file,
so that we can track interesting information and pass it to the various
programs parsing the debian/files file.
|
|
We can easily know the name of the calling unit test, and can thus infer
the pathname for the data directory, instead of having to duplicate the
name, and potentially ending with it being out of sync.
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
This method scans all fragment files inside a directory and loads
each of them.
|
|
|
|
Regression introduced in commit ab15fd24dd1a8207ab1463410338f24283989f7c.
Packages can contain colons in their filenames if the upstream version
contains colons.
Reported-by: Jakub Wilk <jwilk@debian.org>
|
|
When we are constructing a .changes file we add the source artifacts
to the distribution manually, before loading the distribution list
from debian/files.
We should allow ~ in the filename as that's a valid character in a
version number.
Regression introduced in commit ab15fd24dd1a8207ab1463410338f24283989f7c.
Reported-by: Niels Thykier <niels@thykier.net>
|
|
|
|
|
|
This guarantees the debian/files and anything parsing it via this module
get reproducible results regardless of things such as parallel builds.
Reported-by: Jérémy Bobbio <lunar@debian.org>
|
|
|
|
|