On Sat, Dec 31, 2016 at 12:30:12AM +1100, Stuart Prescott wrote:
>
>Dear -boot & -cd,
>
>In re-reading #758234, I noticed a request that -boot and -cd be kept up to
>speed with priority changes that might have an impact on the installer.
ACK, thanks!
>In the thread starting at
>
> https://
On Mon 2017-01-02 19:47:00 -0500, Ansgar Burchardt wrote:
> There was an open bug about changing the overrides (#849903) and I just
> set all packages built from gpgme1.0 to "Priority: optional".
>
> I don't think there is any reason for the lib*-dev packages to be at
> Priority: extra?
I read:
h
Daniel Kahn Gillmor writes:
> On Thu 2016-12-29 23:41:39 -0500, Stuart Prescott wrote:
>> one of the objectives for stretch was to reduce the number of Python 2
>> packages that are installed in common scenarios, instead having the
>> Python 3 stack take over. The "standard task" within tasksel is
On Thu 2016-12-29 23:41:39 -0500, Stuart Prescott wrote:
> one of the objectives for stretch was to reduce the number of Python 2
> packages that are installed in common scenarios, instead having the
> Python 3 stack take over. The "standard task" within tasksel is a
> reasonable place to look.¹
[
Dear -boot & -cd,
In re-reading #758234, I noticed a request that -boot and -cd be kept up to
speed with priority changes that might have an impact on the installer.
In the thread starting at
https://lists.debian.org/debian-python/2016/12/msg00070.html
we have been looking at whether
On Fri, 30 Dec 2016 10:14:20 Julian Andres Klode wrote:
> On Fri, Dec 30, 2016 at 06:52:37AM +0100, Matthias Klose wrote:
> > I don't know the rationale for having the apt and gpg bindings as Priority
> > standard, but if these can be made optional, then the depending packages
> > can be made optio
On Fri, Dec 30, 2016 at 06:52:37AM +0100, Matthias Klose wrote:
> I don't know the rationale for having the apt and gpg bindings as Priority
> standard, but if these can be made optional, then the depending packages can
> be
> made optional as well.
python-apt is standard because it was used by a
On 30.12.2016 05:41, Stuart Prescott wrote:
>
> Hi everyone,
>
> one of the objectives for stretch was to reduce the number of Python 2
> packages that are installed in common scenarios, instead having the Python 3
> stack take over. The "standard task" within tasksel is a reasonable place to
Hi everyone,
one of the objectives for stretch was to reduce the number of Python 2
packages that are installed in common scenarios, instead having the Python 3
stack take over. The "standard task" within tasksel is a reasonable place to
look.¹
Thanks to the recent work on reportbug and debia
9 matches
Mail list logo
