Hello,
With help from upstream we've got versions of llvmlite and numba that
build with dependencies currently in Debian.
Numba built and passed tests for amd64 and arm64. It build but the
build time tests failed for mips64el, ppc64el, and s390x. Numba
couldn't build on armel, armhf, i386, and r
Hi Santiago,
On Sun, Apr 13, 2025 at 01:22:21PM +0200, Santiago Vila wrote:
> After building all the archive (trixie/sid) with nocheck, I only found 33 new
> packages which fail to build with nocheck that were not reported before.
> Admittedly
> a little bit more than I expected, but certainly no
Hi,
On 13-04-2025 17:12, Helmut Grohne wrote:
That said, Emilio explicitly asked them not to be filed as rc on irc.
That feels like RT is not internally consistent here. How about filing
them as rc now and tagging them trixie-ignore later if we deem the
effort too big?
What I think he means,
Hello,
Thanks for the links. The checklist in itself seems like it would fix a
lot of problems. Here are some comments:
- The item "A verbatim copy of the package’s copyright information is
often required to be present in /usr/share/doc/PACKAGE/copyright, too;
see Copyright considerations."
On 2025-04-13 Chris Hofstaedtler wrote:
> brian m. carlson (one of the git upstream copyright holders) claims
> in Bug #1094969 that git cannot be distributed when linked with
> OpenSSL. IIRC the Debian position is to use the system library
> exception.
> Indeed our /usr/lib/git-core/git-remot
Hello fellow developers,
On Thu, Apr 10, 2025 at 07:37:32AM +0200, Helmut Grohne wrote:
> how about libc6-dev stops depending on libcrypt-dev?
with minor disagreement in details, I have received much positive
feedback and therefore moved forward.
> So far so good. That's 1 + 95 + 11 + 1 = 108 so
brian m. carlson (one of the git upstream copyright holders) claims
in Bug #1094969 that git cannot be distributed when linked with
OpenSSL. IIRC the Debian position is to use the system library
exception.
Indeed our /usr/lib/git-core/git-remote-https links against
libssl.so.3, probably via li
I belive debian wants to provide its documentation as packages in stable
releases.
But currently debian-reference is scheduled for auto removal on 2025-04-15
(which this mail bumps a bit into the future).
Maybe "nobody" is aware of this?
Anyone up to taking a look at this?
On Mon, 17 Mar 2025 0
Hello.
After building all the archive (trixie/sid) with nocheck, I only found 33 new
packages which fail to build with nocheck that were not reported before.
Admittedly
a little bit more than I expected, but certainly not "hundreds" as some people
feared.
(The main reason there are not so many
On Sun, 13 Apr 2025 at 13:22:21 +0200, Santiago Vila wrote:
After building all the archive (trixie/sid) with nocheck, I only found 33 new
packages which fail to build with nocheck that were not reported before.
Admittedly
a little bit more than I expected, but certainly not "hundreds" as some pe
El 13/4/25 a las 15:22, Simon McVittie escribió:
On a personal note, I consider those bugs interesting to fix because I think
there
should be a safe procedure to build all packages in the archive in a way which
minimizes
build failures as much as possible.
If that's what you want, I think sce
11 matches
Mail list logo
