Hello,
I pushed a couple of changes to gdcm [1], in order to address
the important bug #989296, which ended up bumped to serious.
I'm not 100% confident I grasped the problem at play, but with
the window for bringing changes now closing, I'm afraid I can't
afford spending too much more time on
On Thu, Jul 29, 2021 at 10:53:43PM +0530, Nilesh Patra wrote:
> => Now, For unc-fish:
>
> Looks fine, but as you might notice, this package is not in the archive
> yet.
> The reason is the TODO mentioned in d/changelog:
>
> """
> TODO: Find reason for failure:
> $ /usr/lib/unc-fish/fish -b
On 29/07/21 09:40 PM, Shruti Sridhar wrote:
> Hello!
>
> I have written autopkgtests for yanagiba[1] and unc-fish[2].
>
> The yanagiba package seems to fail the ci pipeline. The error seems to be
> from -
>
> dpkg: yanagiba-build-deps: dependency problems, but configuring anyway as
> you
Hello!
I have written autopkgtests for yanagiba[1] and unc-fish[2].
The yanagiba package seems to fail the ci pipeline. The error seems to be
from -
dpkg: yanagiba-build-deps: dependency problems, but configuring anyway as
you requested:
yanagiba-build-deps depends on dh-python; however:
Hi Nilesh,
On 28.07.21 21:19, Nilesh Patra wrote:
[CC'ing Steffen who maintains gprofiler]
Hi,
NOTE: This is for action *after* bullseye release
gprofiler description in CRAN[1] itself states that gprofiler is unmaintained
and new users should use
gprofiler2 instead.
The only reverse(build)
5 matches
Mail list logo