Santiago Vila writes:
> Single-CPU systems are ubiquitous in the cloud. I was a system admin in
> a small startup some time ago. Everything was in the cloud, and one of my
> duties was naturally to reduce the IT bill if possible, so I used single-cpu
> systems extensively, as they are almost alwa
El 14/5/25 a las 19:27, Adrian Bunk escribió:
On Wed, May 14, 2025 at 06:58:22PM +0200, Santiago Vila wrote:
El 14/5/25 a las 12:50, Adrian Bunk escribió:
...
How many of the packages that break with "make --shuffle" are currently
doing parallel building?
I am asking since these might be RC bug
On Wed, May 14, 2025 at 06:58:22PM +0200, Santiago Vila wrote:
> El 14/5/25 a las 12:50, Adrian Bunk escribió:
>...
> > How many of the packages that break with "make --shuffle" are currently
> > doing parallel building?
> > I am asking since these might be RC bugs for trixie.
>
> I believed (rega
El 14/5/25 a las 12:50, Adrian Bunk escribió:
What is a maintainer supposed to do when the package already does
"dh --no-parallel" and the upstream Makefiles are basically unfixable?
Whether a Makefile is unfixable or not is subjective. Everything depends
on the amount of time that one is willi
Hi,
On 14/05/25 at 13:50 +0300, Adrian Bunk wrote:
> On Tue, May 06, 2025 at 08:48:29AM +0200, Lucas Nussbaum wrote:
> > On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> > > In some cases, the bug is already known, because debian/rules
> > > has --max-parallel=1. Example: The alpine package.
> >
On Tue, May 06, 2025 at 08:48:29AM +0200, Lucas Nussbaum wrote:
> On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> > In some cases, the bug is already known, because debian/rules
> > has --max-parallel=1. Example: The alpine package.
> >
> > (I wonder how much feasible would be to skip those pac
On 05/05/25 at 22:14 +0200, Santiago Vila wrote:
> In some cases, the bug is already known, because debian/rules
> has --max-parallel=1. Example: The alpine package.
>
> (I wonder how much feasible would be to skip those packages)
The alpine package is indeed a good example of a package that make
In some cases, the bug is already known, because debian/rules
has --max-parallel=1. Example: The alpine package.
(I wonder how much feasible would be to skip those packages)
Thanks.
Hi,
On 05/05/25 at 21:53 +0200, Santiago Vila wrote:
> El 5/5/25 a las 21:26, Lucas Nussbaum escribió:
> > [...]
>
> Thanks a lot for this. I was never brave enough to go ahead
> and announce a MBF.
>
> May I know what kind of machines did you use to found those bugs?
> Machines with 8 CPUs only
El 5/5/25 a las 21:26, Lucas Nussbaum escribió:
[...]
Thanks a lot for this. I was never brave enough to go ahead
and announce a MBF.
May I know what kind of machines did you use to found those bugs?
Machines with 8 CPUs only? (I ask because I found more than 800
packages with makefile issues
On Monday, May 5, 2025 12:26:00 PM Mountain Standard Time Lucas Nussbaum
wrote:
> Hi,
>
> GNU Make now has a --shuffle option that simulates non-deterministic
> ordering of target prerequisites. See
> https://trofi.github.io/posts/238-new-make-shuffle-mode.html and also
> previous work in Debian
Hi,
GNU Make now has a --shuffle option that simulates non-deterministic
ordering of target prerequisites. See
https://trofi.github.io/posts/238-new-make-shuffle-mode.html and also
previous work in Debian by Santiago Vila:
https://people.debian.org/~sanvila/make-shuffle/
While make always process
12 matches
Mail list logo
