On Sat, Feb 11, 2023 at 08:48:55AM +0100, Paul Gevers wrote:
> Hi,
>
> Disclaimer, I may be misunderstanding how things work, because I only judge
> it on observations and some comments in threads here and there.
>
> On 11-02-2023 00:43, Adrian Bunk wrote:
> > I would be curious whether there is
Hi,
Disclaimer, I may be misunderstanding how things work, because I only
judge it on observations and some comments in threads here and there.
On 11-02-2023 00:43, Adrian Bunk wrote:
I would be curious whether there is any technical reason why most
Go libraries are binary-all but most Rust
On Fri, Feb 10, 2023 at 11:32:21AM +0100, Jonas Smedegaard wrote:
>...
> Reduced size in the archive: Avoids multiple identical copies of library
> source code
>...
I remember the 1990s when archive size was a problem, but a few
years ago we had the first file > 2 GB in the archive (AFAIR an
On Fri, Feb 10, 2023 at 03:10:03PM -0700, Sam Hartman wrote:
> > "Jonas" == Jonas Smedegaard writes:
>
>
> Jonas> Yes, I am aware that the Rust team packages arch-all code as
> Jonas> arch-any packages, but I am unaware that their reasoning is
> Jonas> well documented anywhere.
Quoting Paul Gevers (2023-02-10 21:14:52)
> On 09-02-2023 23:59, Jonas Smedegaard wrote:
> > I can only interpret that as the test environment on thos arches being
> > broken. Please don't punish the package for that :-(
>
> I think your interpretation it wrong. librust-rustls-dev Depends on
>
Quoting Sam Hartman (2023-02-10 23:10:03)
[concerns over binNMUing due to static linking snipped: irrelevant!]
> If on the other hand your packages aren't going to need to be rebuilt
> when their dependencies change, it may not be a big deal.
librust-*-dev packages contain no static linking. I
> "Jonas" == Jonas Smedegaard writes:
Jonas> Yes, I am aware that the Rust team packages arch-all code as
Jonas> arch-any packages, but I am unaware that their reasoning is
Jonas> well documented anywhere. The only reason I was aware of
Jonas> when I did the switch was that
Hi Jonas,
On 09-02-2023 23:59, Jonas Smedegaard wrote:
I can only interpret that as the test environment on thos arches being
broken. Please don't punish the package for that :-(
I think your interpretation it wrong. librust-rustls-dev Depends on
librust-ring-0.16+default-dev which is only
Quoting Sebastian Ramacher (2023-02-10 10:30:53)
> Control: tags -1 moreinfo
> Control: severity -1 normal
>
> On 2023-02-09 23:59:25 +0100, Jonas Smedegaard wrote:
> > Package: release.debian.org
> > Severity: important
> >
> > ckage src:rust-rustls is not migrating to testing because tests
Control: tags -1 moreinfo
Control: severity -1 normal
On 2023-02-09 23:59:25 +0100, Jonas Smedegaard wrote:
> Package: release.debian.org
> Severity: important
>
> ckage src:rust-rustls is not migrating to testing because tests fail for
> s390x and ppc64el. On both arches the failure is that
Processing control commands:
> tags -1 moreinfo
Bug #1030957 [release.debian.org] release.debian.org: please have rust-rustls
ignore CI tests for s390x and ppc64el
Added tag(s) moreinfo.
> severity -1 normal
Bug #1030957 [release.debian.org] release.debian.org: please have rust-rustls
ignore CI
Package: release.debian.org
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
ckage src:rust-rustls is not migrating to testing because tests fail for
s390x and ppc64el. On both arches the failure is that the test
environment thinks it needs to install an arch-specific
12 matches
Mail list logo
