Bug#846002: About the internal and external view of Blends (Was: Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu)

On Mon, Feb 06, 2017 at 06:04:18PM +, Ian Jackson wrote: > > ... > > to Ubuntu). We could do a pretty good service to this type of user to > > make Debian "easy to install". This installation topic comes up in > > every talk I have given (see [1] at 35:20) and since 14 years I can not > >

Bug#846002: About the internal and external view of Blends (Was: Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu)

Andreas Tille writes ("About the internal and external view of Blends (Was: Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu)"): > May be this is the right time to clarify the role of Blends inside > Debian and I'd like to adjust my probably biased

Bug#846002: About the internal and external view of Blends (Was: Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu)

Hi, On Sun, Feb 05, 2017 at 12:38:59AM +0100, Tollef Fog Heen wrote: > > Would it be a sensible compromise to reassign this bug to d-i tagging it > > RC for buster to make sure a Blends menu will exist in the buster > > installer. > > While I think it's important to get it fixed for buster, I

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

On Sat, Feb 04, 2017 at 12:16:01PM +0100, Andreas Tille wrote: > Would it be a sensible compromise to reassign this bug to d-i tagging it > RC for buster to make sure a Blends menu will exist in the buster > installer. besides what Tollef already said about the severity I think a fresh new bug

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

]] Andreas Tille > On Fri, Feb 03, 2017 at 02:10:43PM +0100, Cyril Brulebois wrote: > > > > > > I do have time now, so perhaps while we're reverting those changes > > > Cyril will be open to persuasion that we could also patch the blends > > > back in, and make the menu clearer overall using my

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

On Fri, Feb 03, 2017 at 02:10:43PM +0100, Cyril Brulebois wrote: > > > > I do have time now, so perhaps while we're reverting those changes > > Cyril will be open to persuasion that we could also patch the blends > > back in, and make the menu clearer overall using my early suggestion > > of

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi, first, you've made the point that you were hoping the TC would help the blends team and the d-i team work together. I think that Phil's suggestions for a technical approach are quite good, and I hope that will move forward in the buster cycle. With regard to stretch, I honestly don't think

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Since I've been asked in an IRC query whether I might be willing to consider this suggestion: Philip Hands (2017-02-03): > I think this is in part a symptom of mixing up multiple questions in > one request. > > There seems to be a consensus that the priority change was

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Ole Streicher writes: ... >>> The TC has the power to decide here, and you were asked to do so. If you >>> think that d-i took the right decision, you should decide so (and then >>> you don't need to use your power), but not just let them decide. >> >> That's what the

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi Tollef, On 02.02.2017 21:29, Tollef Fog Heen wrote: > ]] Ole Streicher Am 31.01.2017 um 16:26 schrieb Sam Hartman: > If they don't want to do that for stretch, that's a decision within > their pervue that we clearly don't have the votes to override. >> I have read Sams "vote to

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

]] Ole Streicher Hi > >> Am 31.01.2017 um 16:26 schrieb Sam Hartman: [...] > >>> If they don't want to do that for stretch, that's a decision within > >>> their pervue that we clearly don't have the votes to override. [...] > This makes it a case where one can ask the TC for a decision, if

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi Tollef On 02.02.2017 19:47, Tollef Fog Heen wrote: > ]] Ole Streicher > >> Am 31.01.2017 um 16:26 schrieb Sam Hartman: >>> If you go back one meeting further, my interpretation is that the consensus >>> of >>> the committee seems to be that ultimately this decision belongs to the >>>

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

]] Ole Streicher > Am 31.01.2017 um 16:26 schrieb Sam Hartman: > > If you go back one meeting further, my interpretation is that the consensus > > of > > the committee seems to be that ultimately this decision belongs to the > > installer team. > > That is, in this case, a number of members on

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

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

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

> "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

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

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

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Am 2017-02-01 04:45, schrieb Sam Hartman: What I think several of us did is look at the technical details and decide we believe that the installer team was the right set of people to make this technical decision. So, I think the TC will make its decisions on a technical foundation a lot

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

> "Ole" == Ole Streicher writes: Ole> Hi Sam, Am 31.01.2017 um 16:26 schrieb Sam Hartman: >> If you go back one meeting further, my interpretation is that the >> consensus of the committee seems to be that ultimately this >> decision belongs to the

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi Sam, Am 31.01.2017 um 16:26 schrieb Sam Hartman: > If you go back one meeting further, my interpretation is that the consensus of > the committee seems to be that ultimately this decision belongs to the > installer team. > That is, in this case, a number of members on the TC seem to believe >

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

> "Ole" == Ole Streicher writes: Hi. If you go back one meeting further, my interpretation is that the consensus of the committee seems to be that ultimately this decision belongs to the installer team. That is, in this case, a number of members on the TC seem to believe

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Dear Technical Committee, after reading the CTTE meeting log from 2017-01-26 [1], I feel a bit disappointed. As far as I understand (I am not a long-term DD yet), the Technical Committee has the task to decide items, where a consensus could not be reached. Here, this is obviously the case, as

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

[Samuel Thibault] > This makes me think about a recurring issue: being able to easily > personalize an ISO image. > > It's useful to have an ISO image that "just install this and that on the > whole disk without asking anything" without having to setup PXE. This would be most easy to implement by

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hello, Holger Levsen, on Sun 27 Nov 2016 17:38:27 +0100, wrote: > So how to fix this *and* allow Debian blends be installed easily from > official Debian media? [...] > The idea is, that these images have the *same features* (and packages), the > differences are just which the preselected

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

On Tue, Nov 29, 2016 at 05:52:01PM +, Holger Levsen wrote: > I'm sorry about not being able to reply right now. Gotta catch another > train in 30 or 90min… > > (I peeked into your replies very briefly and saw that I cannot reply quickly…) OK, take your time, have a nice travel - but please

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi Andreas (& Ole), On Tue, Nov 29, 2016 at 05:04:31PM +0100, Andreas Tille wrote: > I wonder what your opinion about the two existing answers might be. You > requested a discussion about your proposed patch but you did not took > part in the last 36 hours. > > I hope you are fine and kind

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi Holger, On Sun, Nov 27, 2016 at 05:38:27PM +0100, Holger Levsen wrote: > I also plan to NMU blends-dev to set blends-tasks back to priority:optional, > probably on Thursday or Friday this week. (To give some time to discussion, > but soon, to not let this slip for to long.) I wonder what

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Hi, On Mon, Nov 28, 2016 at 10:09:56AM +0100, Ole Streicher wrote: > ... > about the blends available during installation, and this makes the > package that provides this information "important". Therefore, it is not > a policy violation, which in turn removes your argument to make this bug >

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Control: reassign -1 blends-tasks Control: tags -1 moreinfo Hi Holger, thank you for your bug report to the "blends" package. I would, however question a few things here and also ask for a little bit more information: The "blends-tasks" package was created as a result of working on bug #758116,

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

Source: blends Version: 0.6.94 Severity: serious Tags: d-i Justification: Policy 2.5 and breaking another package Hi, I'm sorry, but the current implementation of installing Blends from Debian images is simply not acceptable, as in, it completely breaks the UI of debian-installer thus the