Hi Robin,
On Fri, Apr 03, 2020 at 09:46:34AM +0200, Robin Gustafsson wrote:
> Hi Elías,
>
> > -Under build system it's fine [2] but with salsa-ci pipeline[3] it fails.
> > Do you know why?
>
> The error in the build output [1] implies that GPICK_BUILD_DATE is
> expected, but not found, among the
Dear Thibaut,
On Fri, Apr 03, 2020 at 09:08:00AM +0200, Thibaut Paumard wrote:
> Dear Elias,
>
> You can (and probably should) build your package using sbuild and
> configure it to run autopkgtest after build.
>
> when sbuild is set-up, you can also run autopkgtest manually in its schroot.
>
> Y
Hi Elías,
> -Under build system it's fine [2] but with salsa-ci pipeline[3] it fails.
> Do you know why?
The error in the build output [1] implies that GPICK_BUILD_DATE is
expected, but not found, among the environment variables. You probably
have it set in your local environment, but it's not b
Dear Elias,
Le 03/04/2020 à 02:50, Elías Alejandro a écrit :
> Hello all
> I have a question about a package which have a delayed transition
> to testing. Gpick package has fixed under unstable a bug related with
> python3 migration but it's blocked because of regression.[1]
> -Do you know how to
Hello all
I have a question about a package which have a delayed transition
to testing. Gpick package has fixed under unstable a bug related with
python3 migration but it's blocked because of regression.[1]
-Do you know how to fix this regression block? How can I test
under a local environment?
-S
5 matches
Mail list logo