Hi.
I will put all the bugs that I report about this issue here:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
So far there are one that I reported 19 days ago as a "test report"
and 162 that I reported today. I'm intentionally excluding packages
having
On Tue, Nov 24, 2015 at 00:41:35 +0100, Santiago Vila wrote:
> On Mon, Nov 23, 2015 at 08:42:14PM +0100, Julien Cristau wrote:
> > On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote:
> >
> > > If it's a “severe violation of Debian policy”, the bug is at least
> > > “serious” severity.
> >
Santiago Vila writes:
> On Mon, Nov 23, 2015 at 11:29:19AM +0100, Jakub Wilk wrote:
> > I'd use "severity: serious", just like for a normal FTBFS.
>
> The problem with making them "severity: serious" is that I would be
> deciding on my own that those bugs are RC. Normally, the
On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote:
> If it's a “severe violation of Debian policy”, the bug is at least
> “serious” severity.
>
The release team's RC policy decides which policy violations we consider
"severe" in the sense of "gets a serious severity bug".
Cheers,
Julien
Greetings.
I've noticed that some packages fail to build from source when built
using "dpkg-buildpackage -A".
This is not only a violation of policy, but also prevents the package
from being uploaded in source-only form, as the architecture-independent
packages are generated by a dedicated
* Santiago Vila , 2015-11-23, 10:52:
I've noticed that some packages fail to build from source when built
using "dpkg-buildpackage -A".
[...]
I think those are clearly bugs, and they should be reported. The only
thing that may be unclear is the severity. I would like this to
On Mon, Nov 23, 2015 at 11:29:19AM +0100, Jakub Wilk wrote:
> * Santiago Vila , 2015-11-23, 10:52:
> >I've noticed that some packages fail to build from source when built using
> >"dpkg-buildpackage -A".
> [...]
> >I think those are clearly bugs, and they should be reported. The
On Tue, 2015-11-24 at 08:48 +1100, Ben Finney wrote:
> Julien Cristau writes:
>
> > On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote:
> >
> > > If it's a “severe violation of Debian policy”, the bug is at least
> > > “serious” severity.
>
> This is one way that a
On Mon, Nov 23, 2015 at 08:42:14PM +0100, Julien Cristau wrote:
> On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote:
>
> > If it's a “severe violation of Debian policy”, the bug is at least
> > “serious” severity.
> >
> The release team's RC policy decides which policy violations we
On Mon, Nov 23, 2015 at 05:51:44PM +0100, Thomas Goirand wrote:
> > As the number of bugs is going to be greater than ten
>
> Do you have the exact figures? How many packages are affected?
I don't have exact figures yet, but I estimate about 300, more or less.
I considered the source packages
On 11/23/2015 10:52 AM, Santiago Vila wrote:
> Greetings.
>
> I've noticed that some packages fail to build from source when built
> using "dpkg-buildpackage -A".
>
> This is not only a violation of policy, but also prevents the package
> from being uploaded in source-only form, as the
Santiago Vila wrote:
> I've noticed that some packages fail to build from source when built
> using "dpkg-buildpackage -A".
>
> This is not only a violation of policy, but also prevents the package
> from being uploaded in source-only form, as the architecture-independent
> packages are generated
Julien Cristau writes:
> On Tue, Nov 24, 2015 at 06:14:43 +1100, Ben Finney wrote:
>
> > If it's a “severe violation of Debian policy”, the bug is at least
> > “serious” severity.
This is one way that a bug can be determined “Severity: serious”, by
definition.
In other
13 matches
Mail list logo