Hi,
My reply on 5/7 got consistently rejected by debian BTS with reason:
550 Blacklisted URL in message. (openzfs . github . io) in [black]. See
http://lookup.uribl.com.
So resending this message to the list.
> 2025年5月7日 02:38，Stefan Bellon 写道：
>
> On Wed, 07 May, Shengqi Chen wrote:
>
>>
Control: tags -1 + moreinfo
Control: severity -1 normal
Control: notfound -1 2.3.2-1
Hi,
> -Original Message-
> From: Pkg-zfsonlinux-devel
> et> On Behalf Of Stefan Bellon
> Sent: Monday, May 5, 2025 5:49 PM
>
> 2025-05-05T10:42:49.790841+02:00 nimbus kernel: PANIC: zroot: blkptr at
> f
Hi,
> -Original Message-
> From: Paul Gevers
> Sent: Thursday, April 24, 2025 9:10 PM>
>
> The changelog says 12 April, not 13 March. Care to fill in the missing
> pieces?
The original version I uploaded to NEW was [1]. However it got rejected due to
extra license in d/copyright [2]. T
Control: tags -1 - moreinfo
Control: fixed -1 1:1.15.0+ds-1~exp1
Control: close -1
I believe this problem has been fixed after the fmtlib and spdlog transition.
Thanks,
Shengqi Chen
Hi Sanvila & Andrius,
> 2025年4月9日 19:53，Santiago Vila 写道：
>
> El 9/4/25 a las 13:42, Andrius Merkys escribió:
>> I would suggest branching off debian/2.6.0+dfsg-5 and applying your patch on
>> that branch. I sometimes do this with packages where git head is unreleased.
2.6.0+dfsg-6 is actually
Hi Dietmar,
> I'm getting the following
>
> error: ‘basic_runtime’ is not a member of ‘fmt’
> 168 | std::is_convertible fmt::basic_string_view>::value || std::is_same,
> fmt::basic_runtime>::value>
This is weird. In in 1.15.1 we have [1]:
template
#if FMT_VERSION >= 90101
Control: affects -1 + src:fmtlib
Control: severity -1 serious
Justification: Stop working with latest mkdocs due to missing dependency
Hi,
As a plugin for mkdocs, now it would not work any more when imported:
This is what I got when I tried to build fmtlib earlier today, I believe there
are more
Hi Simon,
> -Original Message-
> From: Simon Josefsson
>
> Thanks for working on this! It is a bit delicate issue, and I've been
> unable to find the right spell to fix things. Could you propose this as
> a Salsa merge request, or at least a concrete patch? It would indeed be
> nice t
(Resend to BTS only, since my last mail got rejected.)
-Original Message-
To: 1069...@bugs.debian.org; Andrew Bartlett ; Lucas
Nussbaum ; Luca Boccassi ; Simon Josefsson
; Helge Deller
Hi all,
socket-wrapper still fails its tests on armel and armhf, also blocking its
(and all dependen
Control: affects -1 = src:ipxe
Hi all,
I am looping Sergio in, who seems to maintain ipxe in Ubuntu recently
(correct me if wrong), and these changes in Debian are backported
from Ubuntu by Sven.
IIUC, qemu live migration with ipxe enabled cannot be performed during
the upgrade to focal or jammy
Hi Paul and Emilio (again),
> -Original Message-
> From: Shengqi Chen
> Sent: Thursday, February 20, 2025 10:23 PM
>
> > (Emilio)
> > Britney schedules the pytorch tests against rdeps in testing, to ensure they
> > don't break, as pytorch could migrate before and independently of its rde
Hi Paul and Emilio,
> -Original Message-
> From: Paul Gevers
>
> (Paul)
> Will you think about fixing this (eventually)? Having libraries
> co-installable is a common theme, particularly during transitions and
> during upgrades.
I would like to, but I have little idea how to handle it no
Hi,
> -Original Message-
> From: Paul Gevers
> Sent: Thursday, February 20, 2025 3:10 PM>
>
> Yes, but what depends on how bad those failures are for real users that
> would do a partial upgrade. As the test times out without any useful
> output, I can't see what's going on except that
Hi,
I happened to reproduce the problem when working on pytorch-audio.
The root cause is that pytorch is only built for one python version (now 3.13).
The following paragraph is excerpted from its d/rules:
> # [maintainer note on python version]
> # This package is built for a single version (de
Hi,
> -Original Message-
> From: Emilio Pozuelo Monfort
> Sent: Monday, February 17, 2025 10:22 PM
> >
> > For pytorch{,-cuda}:
> >
> > * pytorch-{cluster,scatter,vision,ignite}, baler: builds without issue
> > * pytorch-sparse: failed, in testing, @lumin is looking into it
> > * skorch,
Control: severity -1 important
Hi,
> -Original Message-
> From: Miao Wang
> Sent: Monday, February 3, 2025 10:51 PM
>
> Opt1: Combine the drivers for all the architectures into one ROM like
> before.
>
> Pros:
> - changes are only needed in ipxe and no changes are needed for qemu;
> -
Hi,
The new version of dkms has fixed #1088558, yet not migratable:
Migration status for dkms (3.0.13-1 to 3.1.0-2): BLOCKED: Rejected/violates
migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Not built on buildd: arch all binaries uploaded by pere, a new source-only
up
(Probably) related build logs:
Creating Python 3 environment
Traceback (most recent call last):
File
"/<>/libraries/source/spidermonkey/mozjs-78.6.0/third_party/python/virtualenv/virtualenv.py",
line 46, in
run()
~~~^^
File
"/<>/libraries/source/spidermonkey/mozjs-78.6.0/third_part
Hi,
> * Is libzfs6linux meant to be included in trixie?
Yes.
> * If yes, do you see a risk of rendering a system unbootable if
>libzfs_core.so.3 would go missing?
Yes. libzfs_core is used by many important userspace tools (zfs, zpool, zed,
etc.).
Without them users may not be able to mount
19 matches
Mail list logo
