[Bug 2247350] Review Request: bcachefs-tools - Userspace tools for bcachefs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=2247350



--- Comment #37 from Kent Overstreet <kent.overstreet@xxxxxxxxx> ---
> I'm sorry, but I really don't understand this argument. I assume we don't even use the same C / Rust compilers (or the same versions) - I really hope you don't want us to ship and use the same version of the C / Rust compilers and the linker that you used to build and test, too?

No. What I want is, if you're going to enable LTO, do it by submitting a patch
to bcachefs-tools so it can be properly tested.

> To the contrary - Fedora packages *MUST* be built with the default compiler flags set by the distribution - calling this "monkey-patching" is not accurate.
Unless there are actual problems that are caused by some flags, just disabling
them is not OK.

I seriously doubt you change the compiler flags for the kernel to something
unsupported.

> This is not the first project that's written in Rust that now makes up some kind of critical component in Fedora - even RPM itself now has dependencies that are written in Rust. The way we package components like these has never caused any "subtle" issues like the ones you're thinking of here.

I'm sorry, but RPM won't cause the system to fail to boot, or corrupt user
data, if it has bugs.

Us filesystem people are _considerably_ touchier than most about having a
proper QA process.

> This is also out of your hands, given how packaging works, be it Rust or C or whatever - you just *cannot* guarantee (or expect) that we will ship the exact versions of dependencies that you tested with - or the same version of the C / Rust compiler that you compiled your tests with, for what it's worth.

> Making sure that the packages that *we* ship actually work is also not *your* responsibility, but that of the *packager*.

No, this attitude right here is a total non starter.

I'm the one who's primarily going to be on the hook for bcachefs bug reports; I
have not seen any of you involved in bcachefs, nor have I seen any kind of a QA
process from you guys.

Given that, this "we know best, and you will have no involvement" attitude
isn't going to fly. I haven't gotten this working with any other distributions;
NixOS, Debian and Arch people have been totally fine to work with, and have
been in active communication when necessary and contribute changes back.

Let's just put a pause on this whole process, shall we?


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2247350

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202247350%23c37
--
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux