| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Closes: #1049427
|
|
|
|
| |
Closes: #1051723
|
|
|
|
| |
Closes: #1051720
|
| |
|
|
|
|
| |
Closes: #1051642
|
|
|
|
|
|
|
|
|
|
| |
As of bookworm, merged-usr is mandatory, and people got caught
in the crosshairs of the dpkg fsys-unmessusr debacle and inadvertently
reverted back to an unmerged configuration and continue to remain
on an unsupported system unknowingly.
Help them by erroring out when they are installing packages on /,
they are not in a chroot, and a usrmerge package is available.
|
| |
|
|
|
|
|
| |
It seems the ubuntu:lunar image has a user with UID 1000 already
which was not the case in previous versions.
|
| |
|
|\
| |
| |
| |
| | |
Try to compare SHA256 to determine same version
See merge request apt-team/apt!305
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we know both SHA256, and they're different, the packages are. This
approach stores the SHA256 only at runtime, avoiding the overhead of
storing it on-disk, because when we update repositories we update all
of them anyhow.
Note that pkgCacheGenerator is hidden, so we can just modify its
ABI, hooray.
Closes: #931175
LP: #2029268
|
| |
| |
| |
| |
| |
| |
| | |
While we are at it fix the mislabeling as (5) in some places and
unfuzzy the translations.
Reported-By: Enrico Zini on IRC
|
| |
| |
| |
| | |
Closes: #1040644
|
| |
| |
| |
| |
| |
| |
| |
| | |
@DonKult: Dropped the explicit %-position change from the referenced
bug through as that will require code (and string) changes to work
correctly.
References: https://bugs.debian.org/1034378
|
| |
| |
| |
| | |
Closes: #1033909
|
| |
| |
| |
| | |
Closes: #1033904
|
|\ \
| |/
|/|
| |
| | |
Add "apt-patterns" reference to "apt list" description in apt(8)
See merge request apt-team/apt!303
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Fix snapshot crashes
See merge request apt-team/apt!301
|
|/
|
|
|
| |
We did not handle multiple components properly, add a contrib
component to the test case.
|
|\
| |
| |
| |
| | |
Do not fail on systems running in FIPSmode.
See merge request apt-team/apt!295
|
| |
| |
| |
| |
| | |
Initialize using gcrypt's GCRYCTL_NO_FIPS_MODE, available since
gcrypt version 1.10.0, otherwise apt aborts on FIPS enabled systems.
|
|\ \
| | |
| | |
| | |
| | | |
dist-upgrade: Revert phased updates using keeps only
See merge request apt-team/apt!299
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes an issue where phased updates gain new dependencies
and cause them to be installed despite themselves not being
installed.
In the cause of investigation, it turned out that we also need
to evaluate the candidate version at those early stage rather
than the install version (which is only valid *after* MarkInstall).
This does not fully resolve the problem: If an update pulls in
a phased update, depends are still being installed. Resolving
this while ensuring that phased updates cannot uninstall packages
requires us to do a minimization of changes by trying to keep
back each new install removal and then seeing if any dependency
is being broken by it. This is more complex and will happen
later.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In the bug, mutter was kept back due to phasing and the new gnome-shell
depended on that, and was therefore kept back as well, however,
gnome-shell-common was not broken, and apt decided to continue upgrading
it by removing gnome-shell and the ubuntu desktop meta packages.
This is potentially a regression of LP#1990586 where we added keep
back calls to the start of the dist-upgrade to ensure that we do not
mark stuff for upgrade in the first place that depends on phasing
updates, however it was generally allowed by the resolver to also
do those removals.
To fix this, we need to resolve the update normally and then use
ResolveByKeepInternal to keep back any changes broken by held back
packages.
However, doing so breaks test-bug-591882-conkeror because ResolveByKeep
keeps back packages for broken Recommends as well, which is not
something we generally want to do in a dist-upgrade after we already
decided to upgrade it.
To circumvent that issue, extend the pkgProblemResolver to allow
a package to be policy broken, and mark all packages that already
were already going to be policy broken to be allowed to be that,
such that we don't try to undo their installs.
LP: #2025462
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
update: Add notice about missing Signed-By in deb822 sources
See merge request apt-team/apt!298
|
| |/
| |
| |
| |
| |
| |
| | |
We want to gently steer users towards having Signed-By for each
source such that we can retire a shared keyring across sources
which improves resilience against configuration issues and
incompetent malicious actors.
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
Seed snapshot servers for well-known hosts
See merge request apt-team/apt!293
|
| |
| |
| |
| |
| |
| | |
Separate the determination of the next level domain into its
own function and split out the "we found a result" into its
own break for improved readability.
|
| | |
|
|/
|
|
|
| |
This will attempt to fallback to a per-server setting if we could
not determine a value from the release file.
|
| |
|
|\
| |
| |
| |
| | |
Add --snapshot and --update support
See merge request apt-team/apt!291
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Provide snapshot support for offical Debian and Ubuntu archives.
There are two ways to enable snapshots for sources:
1. Add Snapshot: yes to your sources file ([snapshot=yes]). This
will allow you to specify a snapshot to use when updating or
installing using the --snapshot,-S option.
2. Add Snapshot: ID to your sources files to request a specific
snapshot for this source.
Snapshots are discovered using Label and Origin fields in the Release
file of the main source, hence you need to have updated the source at
least once before you can use snapshots.
The Release file may also declare a snapshots server to use, similar
to Changelogs, it can contain a Snapshots field with the values:
1. `Snapshots: https://example.com/@SNAPSHOTID@` where `@SNAPSHOTID@`
is a placeholder that is replaced with the requested snapshot id
2. `Snapshots: no` to disable snapshot support for this source.
Requesting snapshots for this source will result in a failure
to load the source.
The implementation adds a SHADOWED option to deb source entries,
and marks the main entry as SHADOWED when a snapshot has been
requested, which will cause it to be updated, but not included
in the generated cache.
The concern here was that we need to keep generating the shadowed
entries because the cleanup in `apt update` deletes any files not
queued for download, so we gotta keep downloading the main source.
This design is not entirely optimal, but avoids the pitfalls of
having to reimplement list cleanup.
Gaps:
- Ubuntu Pro repositories and PPAs are not yet supported.
|
| |
| |
| |
| |
| | |
This runs update before opening the cache and sources.list for
installing/upgrading.
|
|\ \
| |/
|/|
| |
| | |
fix (pkgProblemResolver): Keep "or group" when installing package to satisfy it
See merge request apt-team/apt!292
|
|/ |
|
| |
|
|\
| |
| |
| |
| | |
machine-readable version of COPYING
See merge request apt-team/apt!287
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
The concrete copyright holders listed are not really relevant
for anything, as they are woefully incomplete anyhow. Grouping
by licensing allows us to focus on what matters: Parts that have
a different license from the overall project.
|
| |
| |
| |
| |
| | |
Thanks Petter for chasing down the copyright holders and getting
consent.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The debian/copyright (COPYING) file is missing at least two licenses
(Expat, BSD-3-clause) and some copyright statements. A machine-readable
version of COPYING is attached that fixes these.
Closes: #1019273
|
|/
|
|
|
|
|
| |
lintian-brush only fixed the spare-manual-page ones.
Fixes: lintian: mismatched-override
See-also: https://lintian.debian.org/tags/mismatched-override.html
|