Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 35 |
Nodes: | 6 (1 / 5) |
Uptime: | 19:08:59 |
Calls: | 321 |
Calls today: | 1 |
Files: | 957 |
Messages: | 82,383 |
Hello,
* Debian testing on a i5-8265U, 32GB RAM, 1TB NVME laptop.
* RHEL 9.x on a Ultra 7 155H, 32GB RAM, 1TB NVME laptop. This has a 100GB Debian testing builder VM. Many other test VMs.
That is certainly more than what I have at home. I hope it can handle it. Otherwise you are completely free to revert of course.
The biggest thing I have is time, the one thing others have a distinct lack of. A previous career has taken its toll on my spine with damage at the base and sever damage at the top (neck). Surgeons will not operate as it could make my condition worse or paralyse me, so we are left managing my pain and lack of mobility (cannot walk more than 10m at a time).
I'm really sorry to hear this.
I'm disabled myself, though of course completely different circumstances and situation than you.
As you say, exceptions. ratt is not for all packages, the test is certainly none blocking, but I hope any issues raised having the test will make for good bug reports, communication and avoid unnecessary breakage.
It seems I have no objections then.
On Thursday, January 23, 2025 3:47:56 AM MST Phil Wyett wrote:
The biggest thing I have is time, the one thing others have a distinct lack of. A previous career has taken its toll on my spine with damage at the base
and sever damage at the top (neck). Surgeons will not operate as it could make my condition worse or paralyse me, so we are left managing my pain and lack of mobility (cannot walk more than 10m at a time).
I’m very sorry to hear that, but I am glad you are doing positive things with
your time even though you have to deal with significant pain.
As you say, exceptions. ratt is not for all packages, the test is certainly none blocking, but I hope any issues raised having the test will make for good
bug reports, communication and avoid unnecessary breakage.
I applaud your efforts.
--
Soren Stoutner
soren@debian.org
ratt (“Rebuild All The Things!”) operates on a Debian .changes file of
a just-
built package, identifies all reverse-build-dependencies and rebuilds
them with
the .debs from the .changes file.
The intended use-case is, for example, to package a new snapshot of a
Go
library and verify that the new version does not break any other Go libraries/binaries.
ratt need not be run against architecture 'all' packages, so for these
it will
be a 'N/A' result.
Hello,
let me start thanking you for your work weeding the RFS bugs, it has been really really useful.
I've become a DD in the end of 2023 so it's still fresh in my mind the frustration of getting something sponsored :D
The description of ratt only mentions go, does it work/is it useful for other languages as well?
And can your infrastructure support it?
In the python team it has happened to me that an upload breaks other stuff, and
then I have to find out after the fact what got broken and also fix the other things. In general breaking other stuff isn't an argument against uploading per
se, but indicates that more uploads become needed, so while a good test in general, I think there might be exceptions to the rule.
The biggest thing I have is time, the one thing others have a distinct lack of. A previous career has taken its toll on my spine with damage at the base and sever damage at the top (neck). Surgeons will not operate as it could make my condition worse or paralyse me, so we are left managing my pain and lack of mobility (cannot walk more than 10m at a time).
As you say, exceptions. ratt is not for all packages, the test is certainly none blocking, but I hope any issues raised having the test will make for good
bug reports, communication and avoid unnecessary breakage.
* Debian testing on a i5-8265U, 32GB RAM, 1TB NVME laptop.
* RHEL 9.x on a Ultra 7 155H, 32GB RAM, 1TB NVME laptop. This has a 100GB
Debian testing builder VM. Many other test VMs.
The biggest thing I have is time, the one thing others have a distinct lack of. A previous career has taken its toll on my spine with damage at the
base and sever damage at the top (neck). Surgeons will not operate as it could make my condition worse or paralyse me, so we are left managing my
pain and lack of mobility (cannot walk more than 10m at a time).
As you say, exceptions. ratt is not for all packages, the test is certainly none blocking, but I hope any issues raised having the test will make for good bug reports, communication and avoid unnecessary breakage.
ratt (“Rebuild All The Things!”) operates on a Debian .changes file of a just-
built package, identifies all reverse-build-dependencies and rebuilds them with
the .debs from the .changes file.
The intended use-case is, for example, to package a new snapshot of a Go library and verify that the new version does not break any other Go libraries/binaries.
ratt need not be run against architecture 'all' packages, so for these it will
be a 'N/A' result.
Your thoughts?
Le 2025-01-22 21:15, Phil Wyett a Θcritá:
ratt need not be run against architecture 'all' packages, so for theseJava libraries are architecture:all, and some updates are breaking builds (typical causes are that some artifact got renamed, that a deprecated API
it will
be a 'N/A' result.
got finally removed, or sometimes plain old API/ABI incompatibilities). Why should they not need this?