On 05/01/17 10:08, Roger Leigh wrote:
On 05/01/17 09:23, Brian May wrote:
Peter Palfrader writes:
It's a serious bug that makes it break in many cases, requiring the
sysadmin to clean up and/or reboot the system. Whether or not it's RC
in the end is the decision of the release team, but th
On 05/01/17 09:23, Brian May wrote:
Peter Palfrader writes:
It's a serious bug that makes it break in many cases, requiring the
sysadmin to clean up and/or reboot the system. Whether or not it's RC
in the end is the decision of the release team, but this severity was
set after discussing th
Peter Palfrader writes:
> It's a serious bug that makes it break in many cases, requiring the
> sysadmin to clean up and/or reboot the system. Whether or not it's RC
> in the end is the decision of the release team, but this severity was
> set after discussing this on #debian-release.
Is anythi
On Mon, 05 Dec 2016, Brian May wrote:
> On Wed, Nov 30, 2016 at 02:57:07PM +, Peter Palfrader wrote:
> > severity 786566 serious
> > thanks
> >
> > This schroot issue is affecting our debian.org porterboxes, and it
> > affects other users (e.g. torproject.org build environment) where more
> >
On Wed, Nov 30, 2016 at 02:57:07PM +, Peter Palfrader wrote:
> severity 786566 serious
> thanks
>
> This schroot issue is affecting our debian.org porterboxes, and it
> affects other users (e.g. torproject.org build environment) where more
> than one chroot is being used at a time.
>
> We rea
severity 786566 serious
thanks
This schroot issue is affecting our debian.org porterboxes, and it
affects other users (e.g. torproject.org build environment) where more
than one chroot is being used at a time.
We really should fix this for stretch.
--
| .''`. *
6 matches
Mail list logo
