Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
The current code was not taking into account the different coverage
ranges, with their different colors, and different images for the
completion bar. Refactor the code into functions, while we are at it.
|
|
All arguments are files to modify.
|
|
Newer lcov versions already produce UTF-8 encoded output, so there's no
need to use our local html prolog.
Ref: #590562
|
|
Add correct summary values, create a percentage bar, and remove the
lcov-epilog template, which was being inserted in every and each
generated lcov html file, not just the indices.
The injection should be considered fragile, as it depends on the input
report not changing its structure. But this is no worse than using the
local prolog and epilog html templates.
|
|
This compressor has been superseded by xz when it comes to compression
ratio, and in cases where higher compatibility or raw speed is desired
gzip is still the better option.
Issue a warning for now for the -Zbzip2 option value, the support for
that value will get disabled at a later point.
|
|
And clarify the comment on the designated initializers.
|
|
There's still at least one scenario that can only be covered by
--control-path, and as long as that's the case the command will
not get removed.
Ref: #699647
|
|
doxygen now produces a warning, let's use the default instead.
|
|
|
|
This gets rid of some warnings due to deprecated options.
|
|
This substantially reduces the image sizes.
|
|
The current version in Debian oldstable (lenny) is already 5.10.0, once
the current Debian stable release becomes oldstable (squeeze) it will
be 5.10.1, so bumping it is pretty safe and conservative.
|
|
The named options are not future-proof, as they will not allow to easily
create packages with specific formats once a future new version gets
introduced. The new option will also allow to request specific minor
revision of a major format, for testing purposes for example.
This also makes the code more explicit as it now refers to specific
format versions when building it.
|
|
This guarantees that the -e option will be set even if the script is
invoked as an argument to sh.
Warned-by: lintian
|
|
This makes sure no path will be interpreted as a revision.
|
|
|
|
|
|
These replace the now deprecated --control-path command, as these do
not rely on any specific database layout.
|
|
Update C99 assumptions, refer to KNF, add link to the Linux CodingStyle,
add some notes about doxygen markup, add missing blank lines and fix
some more typos.
|
|
|
|
Signed-off-by: Niels Thykier <niels@thykier.net>
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
|
|
For now document the database locking “interface”.
Closes: #670897
|
|
The the format has several deficiencies that have been addressed by
upstream in xz. Although unpacking will be kept being supported to
handle existing lzma compressed .deb files.
Issue a warning for now for the -Zlzma option value, the support for
that value will get removed at a later point.
|
|
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
|
|
Doxygen does not seem to handle lex source files nicely, but because the
functions to document are marked in the header anyway, only those should
end up in the final documentation.
|
|
|
|
|
|
|
|
Found by codespell.
|
|
|
|
Those variants do not put triggering packages in triggers-awaited status
and thus do not record the package with the corresponding pending triggers
in the Triggers-Awaited field.
This should be used for triggers which do not provide essential
functionality when we can safely consider that the triggering packages
are able to satisfy dependencies even if the trigger processing
has not yet happened.
|
|
- The list of triggers is in the second parameter and not in the third.
- The --verbose and --query options for dpkg-trigger have never been
implemented.
|
|
Remove trailing spaces. Remove blank lines not separating different code
blocks. Remove blank lines at the end of the file.
|
|
Enable code coverage support with 'configure --enable-coverage'. Use
gcov and lcov for C code coverage, and Devel::Cover and cover for Perl
code coverage.
|
|
|
|
Document in dpkg-source(1) the fact that the fallback to "1.0"
when debian/source/format doesn't exist is deprecated. Explain
the rationale.
Document the long-term deprecation in README.feature-removal-schedule.
|
|
Clarify the status of the API in README.api.
|
|
The exposed API is not yet finished, make the users explicitly
acknowledge this fact by requiring them to define this preprocessor
symbol.
|
|
Stop supporting self backgrounding, remove DPKG_NO_TSTP environment
variable support, as we always spawn a shell now.
This will allow setting useful environment variables for the user to use
with other tools. And is less confusing, as the action to go back to
dpkg does not depend on how dpkg was run.
Closes: #38334
|
|
|
|
|
|
The code should start getting switched to document using JavaDoc
style comments, at least for public declarations.
|
|
|
|
|
|
|
|
|
|
Closes: #17243, #68981, #215374, #217622, #248693, #308285
|