Hi,
On 05/11/21 at 21:22 +0100, Lucas Nussbaum wrote:
> Hi,
>
> I'd like to propose a MBF with severity:serious for the above issue.
> build-arch and build-indep are required targets according to Debian
> Policy section 4.9. This rule was introduced in Policy version 3.9.4,
> released in 2012.
>
On Sun, Nov 7, 2021 at 5:36 AM Ole Streicher wrote:
> One solution here could be to recognize multiple teams: the "primary
> one" (by the maintainer's selection) goes into the "Maintainer:" field
> in d/control, and all secondary would go into the "Uploaders:"
> field. This would imply that the pa
On Tue, Nov 09, 2021 at 08:44:52PM +, Simon McVittie wrote:
> On Tue, 09 Nov 2021 at 19:01:18 +0100, David Kalnischkies wrote:
> > On Tue, Nov 09, 2021 at 03:21:25PM +, Simon McVittie wrote:
> > (Minus that for 12 it is technically still supported as long as it
> > remains 12
>
> No, it d
On Tue, 09 Nov 2021 at 19:01:18 +0100, David Kalnischkies wrote:
> On Tue, Nov 09, 2021 at 03:21:25PM +, Simon McVittie wrote:
> > > As I see it the CTTE decision effectively allows the transition to be
> > > deferred until the moment you want to upgrade to 13.
> >
> > I think you mean: until
On Tue, 09 Nov 2021 at 20:27:24 +0100, Bastian Blank wrote:
> On Tue, Nov 09, 2021 at 08:19:40PM +0100, Michael Biebl wrote:
> > I'm worried that by saying that unmerged is still supported in 12, we open a
> > can of worms and just punt this down to yet another release cycle.
>
> No, unmerged will
On Tue, Nov 09, 2021 at 08:19:40PM +0100, Michael Biebl wrote:
> I'm worried that by saying that unmerged is still supported in 12, we open a
> can of worms and just punt this down to yet another release cycle.
No, unmerged will not be supported in 12. Having the ability to create
something does
On 09.11.21 19:01, David Kalnischkies wrote:
(Minus that for 12 it is technically still supported as long as it
remains 12, but those who have to know will know that and everyone else
is better of following the default anyhow)
I'm worried that by saying that unmerged is still supported in 1
Package: wnpp
Severity: wishlist
Owner: Emmanuel Arias
X-Debbugs-Cc: debian-devel@lists.debian.org, eam...@yaerobi.com
* Package name: mdit-py-plugins
Version : 0.2.8
Upstream Author : Chris Sewell
* URL : https://github.com/executablebooks/mdit-py-plugins
* License
Package: wnpp
Severity: wishlist
Owner: Diane Trout
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: scikit-misc
Version : 0.1.4
Upstream Author : Hassan Kibirige
* URL : https://github.com/has2k1/scikit-misc
* License : BSD with non-endorsement cla
On Tue, Nov 09, 2021 at 03:21:25PM +, Simon McVittie wrote:
> > As I see it the CTTE decision effectively allows the transition to be
> > deferred until the moment you want to upgrade to 13.
>
> I think you mean: until the moment you want to upgrade to testing after
> Debian 12 release day. Th
(Speaking only for myself, not the TC as a whole - but I wrote the first
draft of what became the TC resolution we're discussing.)
On Tue, 09 Nov 2021 at 15:19:53 +0100, David Kalnischkies wrote:
> On Mon, Nov 08, 2021 at 12:56:49PM +0100, Marco d'Itri wrote:
> > On Nov 08, Simon Richter wrote:
>
On Mon, Nov 08, 2021 at 12:56:49PM +0100, Marco d'Itri wrote:
> On Nov 08, Simon Richter wrote:
> > Right now, it is sufficient to preseed debconf to disallow the usrmerge
> > package messing with the filesystem tree outside dpkg. Managed installations
> > usually have a ready-made method to do so
Package: wnpp
Severity: wishlist
Owner: Daniel Gröber
* Package name: zsh-histdb
Version : git HEAD
Upstream Author : Tom Hinton
* URL : https://github.com/larkery/zsh-histdb
* License : MIT
Programming Lang: ZSH
Description : scalable command history
13 matches
Mail list logo
