> RESOLUTION
>
> Background
>
> The blends-tasks package was uploaded in April 2016 setting its priority to
> important. The result of this change was that the package started getting
> automatically installed by debootstrap, with the intended effect of causing
> the list of tasks ship
> RESOLUTION
>
> Background
>
> The blends-tasks package was uploaded in April 2016 setting its priority to
> important. The result of this change was that the package started getting
> automatically installed by debootstrap, with the intended effect of causing
> the
> list of tasks s
I call for votes on the following resolution with regards to #846002:
RESOLUTION
Background
The blends-tasks package was uploaded in April 2016 setting its priority to
important. The result of this change was that the package started getting
automatically installed by debootstrap, wit
Sam Hartman writes ("Bug#846002: blends-tasks must be priority:standard and not
make a mess out of tasksel menu"):
> My reading of that is that the consensus of the TC is that the D-I team
> should make this decision.
I can see why Ole is frustrated. I don't think this is a proper
conclusion for
> "Ole" == Ole Streicher writes:
Georg commented that if we're going to delegate to D-I, we should hurry
up and do so unless this turn into another TC failure.
I personally think we've taken long enough this is already a TC failure
and have expressed regret for my actions that contributed to
Hi Sam,
Am 31.01.2017 um 21:45 schrieb Sam Hartman:
> Ole> Hmm, IMO there are two things here: First, in our constitution,
> Ole> the installer team has no specific granted rights, apart from
> Ole> being maintainers of the relevant packages. This makes the Ole>
> conflict primarily a conflict b
6 matches
Mail list logo
