Hi Jonas,
On Mon, Feb 20, 2023 at 06:44:23PM +0100, Jonas Smedegaard wrote:
> I don't see a need for such general rule for all librust-*-dev packages.
This definitely is a trade-off. Hence I asked about what we should do
about it.
> E.g. librust-futures-timer-dev and librust-event-listener-dev h
Quoting Helmut Grohne (2023-02-20 18:12:14)
> On Wed, Feb 15, 2023 at 08:14:17PM +0100, Fabian Grünbichler wrote:
> > > TL;DR: Is the switch to arch:all one that should be reverted in the face
> > > of it apparently breaking cross builds? Or is there another alternative
> > > (nowadays) that make
Hi Fabian,
On Wed, Feb 15, 2023 at 08:14:17PM +0100, Fabian Grünbichler wrote:
> > // This is the best but not ideal option for us.
> > //
> > // Currently Debian M-A spec has a deficiency where a package X
> > that
> > // build-depends on a (M-A:fo
Shengjing Zhu 于 2023年2月16日周四 09:16写道：
> Sam Hartman 于 2023年2月16日周四 06:37写道：
>
>> However, adding a question to the mix, why does arch all work for go
>> packages?
>> Do they not care about cross compilation, or are concerns somehow
>> different there?
>
>
> Go doesn't work. I guess we started fr
Sam Hartman 于 2023年2月16日周四 06:37写道：
> However, adding a question to the mix, why does arch all work for go
> packages?
> Do they not care about cross compilation, or are concerns somehow
> different there?
Go doesn't work. I guess we started from the common sense that
arch-indepent files should
On 2023-02-15 15:37 -0700, Sam Hartman wrote:
> > "Fabian" == Fabian Grünbichler
> > writes:
> Fabian> All in all it seems to me like the problem currently is more
> Fabian> a theoretical one - it doesn't seem to cause (much, if at
> Fabian> all) additional breakage on top of
Hi!
On Wed, Feb 15, 2023, at 7:51 PM, Fabian Grünbichler wrote:
> debcargo, the tool used by the Debian rust team to streamline the work
> of transforming upstream crates into Debian source packages generates
> d/control entries for librust-* binary packages qualified as arch:any
> and M-A:same, i
> "Fabian" == Fabian Grünbichler writes:
Fabian> All in all it seems to me like the problem currently is more
Fabian> a theoretical one - it doesn't seem to cause (much, if at
Fabian> all) additional breakage on top of stuff that is already not
Fabian> cross compilable at the m
On February 15, 2023 8:57:12 PM GMT+01:00, Sam Hartman
wrote:
>> "Fabian" == Fabian Grünbichler writes:
>
>Fabian> On Wed, Feb 15, 2023, at 7:51 PM, Fabian Grünbichler wrote:
>>> Hi,
>>>
>>> I'm writing this mail in order to get further input from
>>> knowledgeable, b
> "Fabian" == Fabian Grünbichler writes:
Fabian> On Wed, Feb 15, 2023, at 7:51 PM, Fabian Grünbichler wrote:
>> Hi,
>>
>> I'm writing this mail in order to get further input from
>> knowledgeable, but not directly involved DDs - mostly those
>> involved with cross-bui
On Wed, Feb 15, 2023, at 7:51 PM, Fabian Grünbichler wrote:
> Hi,
>
> I'm writing this mail in order to get further input from knowledgeable, but
> not directly involved DDs - mostly those involved with cross-building and
> multi-arch matters.
sorry for the noise - now with correct CC of debian
Hi,
I'm writing this mail in order to get further input from knowledgeable, but not
directly involved DDs - mostly those involved with cross-building and
multi-arch matters.
Some background for those not familiar with rust packaging in Debian, skip
below for the actual examples and question.
12 matches
Mail list logo
