| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Introduced in commit f96f650bffaeb949a96107fcb188f9927be42171.
|
|
|
|
|
|
|
|
|
|
Update to 1608t.
|
|
|
|
|
|
On parse mark not-installed leftover packages for automatic removal from
the database on next dump. The states we consider for removal are
want_purge, want_deinstall and want_hold. The latter being the ancient
default for not-installed packages.
This makes the --forget-old-unavail option not useful anymore, so switch
it to be a no-op, and target it for future removal as obsolescent.
Closes: #33394, #429262
|
|
Update to 1664t0u0f.
|
|
In order to properly transition to GNU's install-info, dpkg's install-info
is modified to be a simple wrapper around /usr/bin/install-info. That
wrapper warns when the user explicitely calls /usr/sbin/install-info since
the new install-info is in /usr/bin/.
This wrapper is meant to be removed at some point when all references
to /usr/sbin/install-info have gone (most probably in squeeze+1).
Also remove the manual page since there's nothing to document any more
and add a lintian override until the wrapper is removed.
Reference: http://wiki.debian.org/Transitions/DpkgToGnuInstallInfo
|
|
Update to 1662t0u2f.
|
|
|
|
|
|
This seems to be obsolete and now the field has the form “#. type: ”.
Which gets duplicated with the old form.
|
|
|
|
Closes: #534551
|
|
|
|
|
|
Add new tag "ignore-blacklist" to force-include symbols which are
normally blacklisted. This can be useful for libgcc to include symbols
that the toolchain allows to be shared but that are often static
(and hence are blacklisted for this reason). Closes: #533642
|
|
|
|
Symbols might be tagged with arbitary number of tags which are separated by '|'
(aka pipe) character. Tags (only if there are any) must be enclosed in the ()
brackets right before a symbol name. Each tag can appear only once in the tag
specification for each symbol. A tag can optionally have a value. The tag value
is separated from the tag name by character '='. Tag names and values can be
arbitrary strings except they cannot contain any of the special ()|=
characters. A name of the tagged symbol can optionally be quoted with either '
or " characters (e.g. to allow whitespaces in the symbol name). If there are no
tags specified, symbol name cannot be quoted and symbol name continues up until
the first whitespace.
Example of the quoted symbol with 2 tags (the first tag has a value while the
second does not):
(tag1=value of the first tag|tag2)"Foo::Bar::foobar()"@Base 1.0 1
Tags serve two purposes:
* they can be used for symbol marking (e.g. when a symbol must be treated
specially under certain circumstances);
* they tell the parser that the specified symbol name must be processed in
certain way to become a raw symbol name as found in the object files.
Such tags are processed in the order they are specified.
Symbol files with tags are not backwards compatible, so a new parameter
'template_mode' has been added to SymbolFile::dump(). If template_mode is not
set (default), dump() emits a fully post-processed symbol specifications as
directed by their tags. Tags themselves are ommited from output and unknown
tags are ignored. If template_mode is set, dump() keeps tags in the output and
emits symbol specifications as they were read from the symbol file.
As a result, a new parameter -t was added to dpkg-gensymbols to support writing
the symbol file in template mode. Default is to write in non-template mode.
(tag|...|tagN)#include "file_to_include"
All symbols in the "file_to_include" will be tagged with #include tags by
default. A symbol in "file_to_include" can specify additional tags in its tag
specification or even override the tag value inherited from #include tags by
specifying another one in its own tag specifaction. There is no way for the
symbol to untag itself, even if the tag was inherited from #include. #include
tags are assumed to go always before (in tagorder) symbol specific tags even if
the symbol overrides the tag. Recursive tagged #includes are supported.
The patch also adds support for 2 tags:
* optional - a symbol marked as optional can disappear from the object file at
any time and that will never cause dpkg-gensymbols to fail (just emit the
diff). If optional symbol disappears, it is dumped as MISSING with
deprecated string set to the current package version (hence it always appears
in the dpkg-gensymbols diff). If optional symbol reappears, it gets
undeprecated but its minver is kept unchanged (contrary to reappearing
MISSING symbols).
Example: C++ template instantiation which disappearance is not ABI breaking
(i.e. basically it is a private symbol).
(optional)_ZN6Phonon22ObjectDescriptionModelILNS_21ObjectDescriptionTypeE0EE11qt_metacastEPKc@Base 4:4.2.0
* arch=<list of architectures as in Build-Depend dep> - allows to
mark a symbol as arch-specific. When dumping in non-templace mode, only
symbols concerned for the current host architecture are dumped. When dumping
in template mode, all arch-specific symbols are always dumped (including
proper tags). If arch-specific symbol appears on the arch that it is not
supposed to appear, it is made arch neutral (hence it appears in the
dpkg-gensymbols diff). If arch-specific symbol disappears from its arch, it
gets declared as MISSING.
Example: armel specific symbol due to qreal mangling as float on arm(el)
and double on other arches.
(arch=arm armel)_ZN6Phonon11AudioOutput13volumeChangedEd@Base 4:4.2.0
(arch=!armel !arm)_ZN6Phonon11AudioOutput13volumeChangedEf@Base 4:4.2.0
|
|
Update to 1663t.
|
|
Updated po/sv.po to 1012t0f0u.
Updated man/po/sv.po to 1661t0f0u.
Updated scripts/po/sv.po to 479t0f0u.
|
|
Reported-by: Per Andersson <avtobiff@gmail.com>
|
|
|
|
Update to 1661t.
|
|
|
|
Even if there's no use at all for substvars or they are (currently)
undesirable making the source not easily reproducible for Debian and
most derivatives using the same build processesor, it might be
interesting for uses like templated source package generation and
similar, or other interesting ideas we might not have thought about.
Also the same logic we applied for the removal of the substvar support
could be applied to most of the “Build options” as well, as those do not
make sense in the normal build for official packages (like -U, or -D).
Changed the code to stop producing warnings, and remove deprecated notes
from man page.
|
|
Update dpkg-parsechangelog's documentation to make it clearer that spaces
are not allowed between single characters options and their values.
For example, "-v1.14" works but "-v 1.14" doesn't. However "--since 1.14"
works. Long options can have values as the next command line argument but
not short ones.
|
|
Packages should use the new dpkg-vendor interface and not rely
on this environment variable.
|
|
This combination is generally not recommended as you want to ensure
that a source package contains only source and not any intermediary files
left-over by the previous build. Nevertheless it can be useful from time
to time and instead of bluntly refusing, we now simply warn the user
and let the build proceed.
-nc still implies -b if nothing else has been specified as it's routinely
used to test if a fix is working by restarting a previously interrupted
build where it failed.
|
|
It has long been superseeded by ‘date -R’.
|
|
This tool is meant to be used in debian/rules files to have common source
packages across multiple distributions and yet still have slightly
different binary packages.
To automatically conserve customizations across derivatives of a given
distribution, one can use “dpkg-vendor --derives-from vendor” so that all
derivatives keep the same customizations when they rebuild the source
package even if the current vendor is no more the same.
|
|
When configuring with --without-dselect or --without-start-stop-daemon,
do not install the man pages related to those programs.
|
|
The backticks are treated like text, until the shell expands them, thus
making this solution portable.
|
|
Update to 1659t.
|
|
Add "keyrings" vendor hook, used by dpkg-source to allow vendors to
supply additional keyrings against which source package signatures will
be verified. Implement this for Ubuntu.
|
|
The regular expression used to identify additional tarballs (used in
formats "2.0" and "3.0 (quilt)") was too strict and refused dashes. This
commit fixes that and documents the set of allowed characters in the
dpkg-source manual page.
|
|
Update man/po/sv.po to 1659t0f0u.
Update scripts/po/sv.po to 477t0f0u.
|
|
Add a missing paragraph with heading tag.
Replace reference to ‘link’ with ‘name’ in --auto.
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
|
|
|
|
Update to 1654t3u.
|
|
Reported-by: Jonathan Gibert <jokot3@gmail.com>
|
|
Reported-by: Modestas Vainius <modestas@vainius.eu>
|
|
|
|
Update to 1635t6f16u.
|
|
|
|
|
