On 2021-01-23 19:00 -0500, Olek Wojnar wrote:
>Hello Debian Science (and Deep Learning) Tensorflow packagers,
>I see that there have been a couple commits recently to the Tensorflow
>package.[1] I wanted to reach out and make sure you know that our team is
>available and happy to
Hello Debian Science (and Deep Learning) Tensorflow packagers,
I see that there have been a couple commits recently to the Tensorflow
package.[1] I wanted to reach out and make sure you know that our team is
available and happy to help you with any Bazel-related build issues you may
have. As you
Hi Stephen,
I have disabled i386 build [1] and reduced the size of salsa-build binaries [2].
Now it builds fine in pipeline and I have uploaded the package.
[1]
https://salsa.debian.org/science-team/siconos/-/commit/8aca640c2743655e87aa181ddfd153f51e6f58e7
[2]
Andrius Merkys writes:
> On 2021-01-23 12:01, Gard Spreemann wrote:
>> I took a stab at it for one package. Does this seem sane?
>>
>> https://salsa.debian.org/gspr/hera/-/blob/2749a47cad5b1b25f4c5cd219db2db907bd4ddc7/debian/upstream/metadata
>
> Seems OK to me. I am not aware of any
Hi Gard,
On 2021-01-23 12:01, Gard Spreemann wrote:
> I took a stab at it for one package. Does this seem sane?
>
> https://salsa.debian.org/gspr/hera/-/blob/2749a47cad5b1b25f4c5cd219db2db907bd4ddc7/debian/upstream/metadata
Seems OK to me. I am not aware of any validation tool for d/u/metadata,
Hi Anton,
Thanks, last time I tried to use the salsa pipeline for this package,
it was not possible because the build produced too much log output and
failed for that reason.
It seems that in your attempt, it actually makes it all the way to the
end; I'm actually not clear on what "fails", it
Gard Spreemann writes:
> I've been meaning to add upstream's bibliography data to some of my
> packages. My understanding [1] is that this should be done through
> d/upstream files, but it is also my impression that DEP-12 has stalled a
> bit.
>
> What is the current preferred way to do this?
7 matches
Mail list logo
