Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Update to 2842t3f1u.
|
|
The architecture specifications and the restriction formulas apply also
to the dependency fields in the binary package stanzas in debian/control.
|
|
Mention that these fields are really udeb-specific.
|
|
|
|
|
|
|
|
First we list source, then binary, then changes.
|
|
The dpkg-cross program and its package have been obsolete for some time,
it is also unmaintained and bug-ridden with Debian policy violations.
|
|
This man page does not describe a file format, move it to the
conventions section.
|
|
We should use the binary (instead of the source) version for the
.buildinfo filename, otherwise on binNMUs the filename will be wrong.
Reported-by: Raphaël Hertzog <hertzog@debian.org>
|
|
Closes: #862924
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Update to 2843t1f.
|
|
|
|
Update to 2843t1f.
|
|
Using the same name as the name in the SYNOPSIS, or the COMMANDS section
seems confusing as it can be understood as the program accepting -c
argument values without the -c command option.
Reported-by: Johannes Schauer <josch@debian.org>
|
|
Closes: #857852
|
|
|
|
The current implementation supports several comment lines, VCS and
editor variable settings which get ignored. In addition, to be able
to handle ancient changelog entries, the parser will detect those and
ignore while preserving them for output.
Closes: #858579
Reviewed-by: G. Branden Robinson <g.branden.robinson@gmail.com>
|
|
|
|
|
|
Update to 2841t1f.
|
|
Make the existing octal parser more robust, by checking for the expected
format of leading zeros or spaces, followed by any ASCII octal characters
(0-7), followed by zero or more space or NULs. Even though POSIX specifies
that numerical fields should end with at least one space or NUL, we still
support this extension which has been present in other implementations
for a long time.
Add support for base-256 encoded numeric fields, to support large
values, for UID/GID, device number, size and even negative timestamps.
This is necessary not only to be able to store larger values, but to
cover packages that can already be generated by dpkg-deb, given that it
uses the system GNU tar when building.
Closes: #850834
|
|
Using libdir is wrong, and doubly so when being referred from
architecture independent files such as perl modules. This affects
non-Debian based systems, which might by default use an arch varying
libdir per architecture, for example when using the obsolete multilib
layout.
|
|
Closes: #857449
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
This makes detecting them more difficult, as they become a bunch of
false-positives to wade through.
|
|
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
|
|
Closes: #856325, #856326
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Update to 2841t1f.
|
|
Delegate the setting to gcc builtin or an explicit request by a user.
This is needed to cope with the general PIE brokenness situation in
Debian, and the current specific brokenness of a Debian gcc patch
mangling the dpkg build flags.
This is wrong in so many levels, as we'll have discrepancies between
architectures, the interface towards maintainers is inconsistent, and
updating the PIE support needs touching and coordinating two places. But
it's certainly the current lesser evil.
Closes: #848129, #845550
|
|
Specifically kfreebsd-amd64, kfreebsd-i386, sparc and sparc64.
|
|
All the currently planned changes have been done, let's bump the format
version to denote a stable format, which will not change in incomatible
changes any more without bumping the major version component.
|
|
Closes: #854417
Proposed-by: Dieter Adriaenssens <dieter.adriaenssens@gmail.com>
|
|
Noted by looking at lintian warning
|
|
|
|
|
|
restrictions"
This reverts commit 9899bdcf9bde76d969b124abf0a898fcbb202c70.
This change is contentious and should have been discussed more widely.
Given that this has been live only for a couple of days, the impact
should be minimal, but still something to take into account once and
if this gets reintroduced, in the same or different form and shape.
Closes: #852820
|
|
|
|
Update to 2843t1f.
|
|
|
|
Missed in commit 7662e0937bb064a0754d12605d80a96a17e2aadf.
|
|
There was no option to disable signing globally, so many users and
tools rely on the two existing options to disable it. But with the
introduction of signed .buildinfo files, there is no way for old tools
to request the right thing.
Abuse --unsigned-changes to mean not signing .buildinfo either.
Closes: #852822
|
|
This option disables signing any file. This makes this option
a future-proof way to disable all signing, in case we add yet more
files to sign, so that programs do not have to keep learning what
options to pass.
|
|
Update to 2839t1f.
|
|
|
|
Add new options -ui and --unsigned-buildinfo.
Closes: #843925
|
|
This will make it possible to enable or disable specific features that
should be recorded in the .buildinfo file. For now only “all” and “path”
are supported.
Closes: #848705
|
|
Closes: #851889, #851891
Signed-off-by: Guillem Jover <guillem@debian.org>
|