| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
to force upgrades in launchpad buildd chroots
Gbp-Dch: full
|
|
|
|
| |
This reverts commit 9bb953fddae0246a4dcedddb769d75d3521e1f2f.
|
|
|
|
|
|
|
| |
The TagFile parser will have already parsed further and can't go
back so it needs to reopen the file if compressed.
Closes: #1067440
|
|\
| |
| |
| |
| | |
Update documentation for apt-get upgrade with pkg arg
See merge request apt-team/apt!334
|
| |
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |
| |
| |
| |
| |
| | |
Closes: #1065831
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |
| |
| |
| |
| |
| | |
Closes: #1065831
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
|\ \
| | |
| | |
| | |
| | | |
Update URI in documentation
See merge request apt-team/apt!335
|
| | |
| | |
| | |
| | | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |/
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
|\ \
| |/
|/|
| |
| | |
pkgTagFile::Jump: Use lookback buffer to rejump to current position
See merge request apt-team/apt!336
|
|/
|
|
|
|
|
|
|
| |
If we get called twice with the same offset, our d->Start and d->iOffset
will already point at the offset for the next section. But since we have
the start of the last parsed section still in the buffer, just make sure
to always go back to the start first.
Closes: #1067440
|
|
|
|
| |
Closes: #1065517
|
|
|
|
| |
Closes: #1065513
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libapt has a NotEquals relation for version constraints in
dependencies, which is used internally e.g. in the MultiArch
implementation, but this relation is not supported by Debian
policy and as such can not be used in packages.
Our parser here is extremely accepting, even unknown relations are
parsed as Equals relation – but the version that must match will be a
rather strange one…
For our own testcases and e.g. on the command line with 'satisfy' it
can make sense to have != available… and what strange things apt does
parsing unsupported relations is not really much of a concern. Real
packages will not have such relations anyhow as we are (mostly) just
a consumer, not a producer of packages and index files.
|
|
|
|
|
|
|
|
|
| |
The option was removed in 2016 along with the code surrounding it, as
the special build-deps specific solver was replaced with reusing our
generic solver(s). As such, the normal debug options for these apply
here nowadays instead of requiring another one to be set as well.
References: a249b3e6fd798935a02b769149c9791a6fa6ef16
|
|
|
|
|
|
|
|
|
|
| |
While the code claims to handle it by just continuing the loop, the
looping condition will actually cause a break from the loop failing the
interrupted writing. The non-static FileFd::Write (and ::Read) deal with
this by setting acceptable values for the loop condition as well – but
for more simplicity and consistency we can instead remove this extra loop
condition and perform the continue/break due to error handling more
explicitly.
|
|\
| |
| |
| |
| | |
Support building without gnutls
See merge request apt-team/apt!333
|
|/
|
|
|
|
|
|
|
| |
Once in a generation, it may be necessary to bootstrap apt in an
environment where gnutls is not yet available. This makes gnutls
support in apt optional.
You may also want a configure flag to force gnutls to be required from
outside the buildsystem (e.g. debian/rules).
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Assert >=2048-bit RSA keys, Ed25519, Ed448, and some improvements to diagnostic reporting
See merge request apt-team/apt!322
|
| |
| |
| |
| |
| | |
This will only issue warnings instead of errors while we continue
cleaning up our repositories.
|
| |
| |
| |
| | |
This allows us to render public key algorithms as weak as well.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The assertion can be overriden using apt::key::assert-pubkey-algo,
the default is the most opinionated one.
This will inform the user during apt-cdrom add as we do not
pass --quiet to user, so adjust test case.
Add a simple test case for it to test-method-gpgv.
LP: #2055193
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Do not require versioned dpkg-dev on CI
See merge request apt-team/apt!332
|
|/ /
| |
| |
| |
| | |
Annotate the Build-Depends with a <!pkg.apt.ci> profile and use
that in prepare-release when doing build-dep.
|
|\ \
| | |
| | |
| | | |
Import 2.7.12+nmu1
|
| |/
| |
| |
| |
| |
| |
| | |
apt (2.7.12+nmu1) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1061896
|
|\ \
| | |
| | |
| | |
| | | |
Show correct location of configure-index in man page
See merge request apt-team/apt!330
|
| |/
| |
| |
| |
| |
| |
| |
| | |
The man page uses examples/configure-index.gz for the configure-index
file, but this isn't a .gz file. Remove the .gz so users can find the
correct file.
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
|\ \
| |/
|/|
| |
| | |
Fix spelling mistake in zh_CN.po
See merge request apt-team/apt!331
|
|/ |
|
|
|
|
|
| |
I also unfuzzied the translation strings for the 23.10->24.04
apt-key deprecation change.
|
| |
|
|\
| |
| |
| |
| | |
Automatically enable snapshots where supported
See merge request apt-team/apt!328
|
| |
| |
| |
| |
| |
| | |
1. repository not supporting snapshots, implicit Enabled
2. repository not supporting snapshots, Enabled: yes
3. URL-based lookup, implicit Enabled
|
| |
| |
| |
| |
| |
| | |
This was accidentally using testfailure instead of
testfailureequal, hence trying to run the output string
as a command :(
|
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a bit more code but avoids any surprises later on by
having both the shadowed and non-shadowed meta index in the
list.
Gbp-Dch: ignore
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Convert sources.list Snapshot option from opt-in to automatic. If
we can find a snapshot server, Snapshot: yes is assumed if a snapshot
is specified.
On the implementation side, we record automatic snapshot enablement
by adding a '?' suffix to the snapshot timestamp, if any is specified,
this avoids introducing bugs into the code where we could end up with
an empty snapshot.
This has an annoying internal implementation caveat: Since we call
GetDebReleaseIndexBy() with the SHADOWED option emplaced, if we do
not find a server, we need to remove the SHADOWED option again, but
we already have inserted a shadowed release index into the list.
This will simply insert the release index a second time without the
SHADOWED option which in preliminary testing works fine, but it would
arguably be more correct to also remove the release index again if
we have created it.
FIXME: This only has one test case: A source with supported snapshot
server is auto-discovered. We should also add a test case where we
cannot detect a server and then don't fail in automatic mode.
|
|/
|
|
| |
Closes: #1054137
|
|\
| |
| |
| |
| | |
Modernize standard library includes
See merge request apt-team/apt!329
|
|/
|
|
|
|
| |
This was automated with sed and git-clang-format, and then I had to
fix up the top of policy.cc by hand as git-clang-format accidentally
indented it by two spaces.
|
|
|
|
|
| |
While it was initially on the road map for 24.04 it got replaced
with the disable 1024R keys feature.
|
|\
| |
| |
| |
| | |
apt.8: summarise remaining verbs (Closes: #827785)
See merge request apt-team/apt!315
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following were undocumented
// package stuff
{"auto-remove", &DoInstall, nullptr},
{"autopurge",&DoInstall, nullptr},
// system wide stuff
// misc
{"moo", &DoMoo, nullptr},
// for compat with muscle memory
{"dist-upgrade", &DoDistUpgrade, nullptr},
{"showsrc",&ShowSrcPackage, nullptr},
{"depends",&Depends, nullptr},
{"rdepends",&RDepends, nullptr},
{"policy",&Policy, nullptr},
{"build-dep", &DoBuildDep,nullptr},
{"clean", &DoClean, nullptr},
{"distclean", &DoDistClean, nullptr},
{"dist-clean", &DoDistClean, nullptr},
{"autoclean", &DoAutoClean, nullptr},
{"auto-clean", &DoAutoClean, nullptr},
{"source", &DoSource, nullptr},
{"download", &DoDownload, nullptr},
{"changelog", &DoChangelog, nullptr},
{"info", &ShowPackage, nullptr},
And there's good reason for some of it, but I unironically didn't know
where apt changelog lived. It's unsearchable.
So the following are now simple links with no paragraphs:
// query
// package stuff
// system wide stuff
// misc
// for compat with muscle memory
{"showsrc",&ShowSrcPackage, nullptr},
{"depends",&Depends, nullptr},
{"rdepends",&RDepends, nullptr},
{"policy",&Policy, nullptr},
{"build-dep", &DoBuildDep,nullptr},
{"clean", &DoClean, nullptr},
{"distclean", &DoDistClean, nullptr},
{"autoclean", &DoAutoClean, nullptr},
{"source", &DoSource, nullptr},
{"download", &DoDownload, nullptr},
{"changelog", &DoChangelog, nullptr},
|