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
Marc Haber wrote:
> On Tue, 14 Feb 2023 11:23:55 -0800, Russ Allbery wrote:
> >I think the right answer (which as is often the case involves a lot more
> >work) is to break the configuration file into separate parts, one of which
> >is a true configuration file in the Policy definition and the oth
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
Marc Haber wrote...
> The "split it" approach is something that comes naturally to someone
> who has been heavily socialized in the Debian Universe because we
> handle conffiles on a file level. It feels unnatural and clumsy for
> someone who is not familiar with the deep historic reasons for us t
On Wed, Feb 15, 2023 at 11:29:25AM +, Alastair McKinstry wrote:
The counterpoint is if someone does a high-core-count 32-bit arch for
HPC; x32 could (have been) such an architecture, but its development
looks stalled.
That may have been a possibility 15-20 years ago, but today anything
ca
> "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.
On Wed, Feb 15, 2023 at 07:50:10AM -0800, Russ Allbery wrote:
> Well, I adore this way of configuring things and think it's way better
> than how Debian has been doing it and I haven't used Red Hat since the
> late 1990s, so *shrug*. :)
>
> But the point wasn't to advocate for that approach spec
Marc Haber writes:
> The issue is, however, a lot more complicated than one would might
> think, imagine a structured configuration file like a systemd unit or an
> icinga or bind or ISC DHCP config file which would need multiple
> "managed sections", and the special case of a setting moving from
Package: wnpp
Severity: wishlist
Owner: KevinDuan
X-Debbugs-Cc: debian-devel@lists.debian.org, duankai...@ubuntukylin.com
* Package name: libkysdk-system
Version : 1.0.1-1
Upstream Author : KevinDuan
* URL : https://gitee.com/openkylin/libkysdk-system
* License
Package: wnpp
Severity: wishlist
Owner: KevinDuan
X-Debbugs-Cc: debian-devel@lists.debian.org, duankai...@ubuntukylin.com
* Package name: libkysdk-system
Version : 2.0.0-1
Upstream Author : KevinDuan
* URL : https://gitee.com/openkylin/libkysdk-system
* License
On Tue, 14 Feb 2023 at 19:24, Russ Allbery wrote:
>
> Christoph Biedl writes:
>
> > these days, I found a package in Debian (four-digit popcon count) that
> > in an upgrade happily removed some some changes I had made to a
> > configuration file of that package, in /etc/.
>
> > My immediate react
Package: wnpp
Severity: wishlist
Owner: KevinDuan
X-Debbugs-Cc: debian-devel@lists.debian.org, duankai...@ubuntukylin.com
* Package name: libkysdk-base
Version : 1.0.1-1
Upstream Author : KevinDuan
* URL : https://gitee.com/openkylin/libkysdk-base
* License :
On 15/02/2023 00:16, Steve Langasek wrote:
On Mon, Feb 13, 2023 at 02:18:06PM +, Alastair McKinstry wrote:
On 13/02/2023 12:51, Adrian Bunk wrote:
There are a significant number of science libraries dependent on MPI.
We would need to do MPI-free builds of these libraries; I'm not sure how
On Tue, Feb 14, 2023 at 04:16:33PM -0800, Steve Langasek wrote:
>...
> working out which of those reverse-dependencies are
> *not* scientific applications that should drop the build-dependency rather
> than being removed, and so forth.
>
> So it's a tradeoff between the maintenance work of keeping
Package: wnpp
Severity: wishlist
Owner: KevinDuan
X-Debbugs-Cc: debian-devel@lists.debian.org, duankai...@ubuntukylin.com
* Package name: libkysdk-system
Version : 2.0.0-1
Upstream Author : KevinDuan
* URL : https://gitee.com/openkylin/libkysdk-system
* License
On Tue, 14 Feb 2023 11:23:55 -0800, Russ Allbery
wrote:
>I think the right answer (which as is often the case involves a lot more
>work) is to break the configuration file into separate parts, one of which
>is a true configuration file in the Policy definition and the other of
>which is the settin
22 matches
Mail list logo
