| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Seems like the interaction between wildcards and exemptions has changed
slightly, so be positively more explicit about our ignoring of en.
Git-Dch: Ignore
|
| |
|
|
| |
Git-Dch: Ignore
|
| | |
|
| |
|
|
|
|
| |
It can be useful to have a whole makefile available for vendor setup,
but by providing a basic one we can deal with the simple cases more
easily (and changes to the system are presumably easier).
|
| |
|
|
|
|
|
|
| |
There is a new "apt full-upgrade" that performs a apt-get dist-upgrade.
"apt dist-upgrade" is still supported as a alias. The "apt upgrade" code
is changed so that it mirrors the behavior of
"apt-get upgrade --with-new-pkgs" and also honors
"apt uprade --no-new-pkgs".
|
| |
|
|
|
|
|
| |
The apt-key script uses quiet a few keyring files for operation which
are specific to the distribution it is build on and is hence one of the
most patched parts – even if it is not that often used anymore now that
a fragment directory for trusted.gpg exists.
|
| |
|
|
|
|
|
| |
manpages sometimes refer to distro-specific things like the name of the
package providing the achive-keyring. Having a central place to
configure this helps in having it consistent in the manpages and allows
to load this info from other places in the buildsystem as well later.
|
| |
|
|
|
|
|
|
| |
Many derivatives make quiet a few simple changes to apt introducing
silly diffs just to change examples and co making it harder for
them to update apt and harder for us to merge real changes back.
First stop: doc/examples/sources.list
|
| |
|
|
|
| |
Building manpages becames more consistent this way and
it is simpler to ignore build artefacts, too.
|
| |
|
|
|
|
|
| |
adding some comments, regrouping files and use some patterns to avoid
updating the ignore file for new translations or abi changes
Git-Dch: Ignore
|
| | |
|
| |
|
