On Wed, Mar 19, 2014 at 10:28:25AM +0100, Malthe Borch wrote:
> On 18 March 2014 17:29, Julian Andres Klode wrote:
>
> > On Tue, Mar 18, 2014 at 01:48:27PM +0100, Malthe Borch wrote:
> > > The local computer time is encoded in the GPG signature:
> > >
> > > If you verify using ``gpg --verify``.
>
On 18 March 2014 17:29, Julian Andres Klode wrote:
> On Tue, Mar 18, 2014 at 01:48:27PM +0100, Malthe Borch wrote:
> > The local computer time is encoded in the GPG signature:
> >
> > If you verify using ``gpg --verify``.
> >
> > gpg: Signature made Fri 14 Feb 2014 09:30:32 PM CET using RSA k
On Tue, Mar 18, 2014 at 01:48:27PM +0100, Malthe Borch wrote:
> The local computer time is encoded in the GPG signature:
>
> If you verify using ``gpg --verify``.
>
> gpg: Signature made Fri 14 Feb 2014 09:30:32 PM CET using RSA key ID
> B35FEC3C
>
> This was taken from the latest release of
The local computer time is encoded in the GPG signature:
If you verify using ``gpg --verify``.
gpg: Signature made Fri 14 Feb 2014 09:30:32 PM CET using RSA key ID
B35FEC3C
This was taken from the latest release of apt-cacher-ng [1].
It's contingent on the release system's local time being
On Tue, Mar 18, 2014 at 1:30 PM, Malthe Borch wrote:
> How difficult would it be to implement a pinning policy that only allowed
> packages released up until some timestamp:
>
> -- /etc/apt/preferences --
>
> Explanation: I want a system current as of some date.
> Package: *
> Pin: release a=stabl
How difficult would it be to implement a pinning policy that only
allowed packages released up until some timestamp:
-- /etc/apt/preferences --
Explanation: I want a system current as of some date.
Package: *
Pin: release a=stable <= 2014-03-18T12:00:00Z
This would be very useful in situations
I'd like to propose an algorithm that, if I'm not mistaken, results in above
policy.
Presuppositions
---
A general form rule or stanza is one that has "Package: *" AND "Pin:
".
A specific form rule or stanza is one that has "Package: " OR
"Pin: version" where is a space-separated lis
I'd like to propose a new policy view.
This is the current output of "apt-cache policy" (modified from [22]):
-- apt-cache policy --
:
Installed:
Candidate:
Package-Pin:
Version table:
***
-- end apt-cache policy package-name --
The
Namely, what I, as a user, would like only is that pinning per package
(wildcarded) name or version works, and that those more specific pins are
propagated to EDSP/CUDF dumps, i.e. in the EDSP dump, the APT-Pin field for
"package=chromium,version=whatever-is-available-in-unstable" stanza says
505 (
Since I opened this new bug, I'd like to add my specific use case as well:
Naturally, I want my system stable. Perhaps some time into the release
cycle, I want my user apps updated for the sake of new features, so I pull
them from testing. Chromium and Iceweasel, perhaps with more stable
(supposed
Package: apt
Version: 0.9.7.4
Severity: important
Tags: confirmed
I took liberty to mark this as confirmed, as it very well is and will as
such hopefully jump at the willing contributors from the top of the
outstanding bugs list. Maintainers' sympathy kindly appreciated.
I know this is kind of TL
11 matches
Mail list logo
