Control: reassign -1 bart-cuda 0.8.00-1
Control: fixed -1 0.8.00-2
Control: close -1
On Thu, Nov 17, 2022 at 05:34:05PM +0200, Adrian Bunk wrote:
> The situation around gcc-11 is less obvious,
> and gcc-11 usage in nvidia-cuda-toolkit is a separate bug.
OK then, re-assigning and closing.
--
Be
On Thu, Nov 17, 2022 at 08:50:39PM +0530, Nilesh Patra wrote:
> On Thu, Nov 17, 2022 at 03:58:42PM +0100, Andreas Beckmann wrote:
> > On 17/11/2022 15.34, Nilesh Patra wrote:
> > > In that case, I am re-assigning this to nvidia-cuda-toolkit since nvcc
> > > needs to
> > > support gcc-12.
> >
> >
On 17/11/2022 16.20, Nilesh Patra wrote:
$ apt show nvidia-cuda-toolkit-gcc 2>/dev/null | grep 'Depends'
Depends: g++-11, gcc-11, nvidia-cuda-toolkit (= 11.6.2-2)
So this bug is still kind of valid. Please let me know if that's not the case.
Even 11.8 (unpackaged) does only support gcc-11 ...
On Thu, Nov 17, 2022 at 03:58:42PM +0100, Andreas Beckmann wrote:
> On 17/11/2022 15.34, Nilesh Patra wrote:
> > In that case, I am re-assigning this to nvidia-cuda-toolkit since nvcc
> > needs to
> > support gcc-12.
>
> Please tell this $VENDOR.
>
> > There is absolutely nothing that can be don
On 17/11/2022 15.34, Nilesh Patra wrote:
In that case, I am re-assigning this to nvidia-cuda-toolkit since nvcc needs to
support gcc-12.
Please tell this $VENDOR.
There is absolutely nothing that can be done at bart-cuda's end to fix this if
only gcc-12 is being released.
Every B-D user of
Control: reassign -1 nvidia-cuda-toolkit 11.6.2-3
On Tue, 08 Nov 2022 20:16:33 +0200 Adrian Bunk wrote:
> Source: bart-cuda
> Version: 0.8.00-1
> Severity: serious
> Control: block 1023666 by -1
>
> According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016625#65
> gcc-11 might be a tem
Source: bart-cuda
Version: 0.8.00-1
Severity: serious
Control: block 1023666 by -1
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016625#65
gcc-11 might be a temporary workaround (but it might be only gcc-12 that
will be in bookworm).
7 matches
Mail list logo