On Sat, 2016-06-04 at 17:59 +0200, Santiago Vila wrote:
> On Sat, Jun 04, 2016 at 04:33:58PM +0100, Ben Hutchings wrote:
> > > You can use the command ischroot from the debianutils package.
> >
> > Why would I want to add a dependency on that? [...]
>
> You really wouldn't, because debianutils is
On Sat, Jun 04, 2016 at 04:33:58PM +0100, Ben Hutchings wrote:
> > You can use the command ischroot from the debianutils package.
>
> Why would I want to add a dependency on that? [...]
You really wouldn't, because debianutils is essential.
On Sat, 2016-06-04 at 11:17 +0200, Aurelien Jarno wrote:
> On 2016-05-26 22:50, Ben Hutchings wrote:
> > I'm inclined to add a check to linux-image prerm scripts that skips the
> > question when DEBIAN_FRONTEND=noninteractive.
> >
> > Aside from that, I might add the check for a chroot or containe
On 2016-05-26 22:50, Ben Hutchings wrote:
> I'm inclined to add a check to linux-image prerm scripts that skips the
> question when DEBIAN_FRONTEND=noninteractive.
>
> Aside from that, I might add the check for a chroot or container, if
> there's a simple way to do that.
You can use the command i
Control: reassign -1 src:linux
Control: severity -1 normal
On Thu, 2016-05-26 at 21:48 +0200, Santiago Vila wrote:
> Package: src:linux,src:supermin,src:sbuild
> Severity: serious
> Justification: Breaks other packages
> X-Debbugs-Cc: sanv...@debian.org
>
> Dear maintainers:
>
> I think this is
* Santiago Vila:
> Package: src:linux,src:supermin,src:sbuild
> Severity: serious
> Justification: Breaks other packages
> X-Debbugs-Cc: sanv...@debian.org
>
> Dear maintainers:
>
> I think this is a bug in linux, but I'm not 100% sure. Please do agree
> with the other maintainers on which package
severity 825423 important
thanks
On Thu, May 26, 2016 at 10:34:12PM +0200, Johannes Schauer wrote:
> this seems to suggest that you are not using a throw-away chroot but
> a persistent one. Could you provide details about your chroot setup?
> Are you not using schroot?
I am using schroot. This i
Hi,
Quoting Santiago Vila (2016-05-26 21:48:49)
> When the package has been built and the build-dependencies are removed
> afterwards, this is what happens:
>
>
> [...]
> Removing linux-image-amd64 (4.5+73) ...
> Removing li
Package: src:linux,src:supermin,src:sbuild
Severity: serious
Justification: Breaks other packages
X-Debbugs-Cc: sanv...@debian.org
Dear maintainers:
I think this is a bug in linux, but I'm not 100% sure.
Please do agree with the other maintainers on which package is to blame.
I'm building packa
9 matches
Mail list logo