Hello,
Sorry for taking this long to respond, I've had quite some stuff
to catch up on, after I was ill for 1 1/2 weeks.
On 20.05.24 02:56, Luca Boccassi wrote:
On Sun, 19 May 2024 at 23:30, Thomas Goirand wrote:
On 5/19/24 17:30, r...@neoquasar.org wrote:
I have an N270 system I can use to c
> I've tried reproducing the daemon-reload bug report, unless I missed
> something
> obvious, daemon-reload works on my T2300, the TM Efficeon, and the
> pre-SSE2
> Pentium 3 (mobile) that I have. I could try running it on an original
> Pentium, but I doubt that debian will run on it at all, even w
Hi Gürkan,
On Fri, Jun 14, 2024 at 12:03 PM Gürkan Myczko wrote:
>
> Have never done mass bug filings, any easy way, preferably something
> copy pastable,
> non-interactive.
Concerning erlang, I've already prepared an upload which builds with
autoconf 1.72, so you may skip it when reporting bugs
Package: wnpp
Severity: wishlist
Owner: Alan M Varghese
X-Debbugs-Cc: debian-devel@lists.debian.org, a...@digistorm.in
* Package name: hyprwayland-scanner
Version : 0.3.10
Upstream Contact: vaxerski
* URL : https://github.com/hyprwm/hyprwayland-scanner
* License
Am Thu, Jun 06, 2024 at 08:14:18PM +0200 schrieb Étienne Mollier:
> > 100% agreed. The care and excellence that you've brought to this work has
> > been exceptional.
>
> Very much seconded, you have my thanks added on the stack! :)
Seconded as well. You deserve a $DRINK / some sweets once we m
Then it's not a problem in the first place. If you can't reproduce a bug with a
reasonable effort, then it is unconfirmed and you can stop worrying about it. A
bug that can't be reproduced, effectively doesn't exist.
That's not a reason to stop supporting an entire architecture. That's a
troub
On Fri, Jun 14, 2024 at 05:53:42AM -0500, r...@neoquasar.org wrote:
> A bug that can't be reproduced, effectively doesn't exist.
Wow.
--
WBR, wRAR
signature.asc
Description: PGP signature
Hello,
On 14.06.24 12:53, r...@neoquasar.org wrote:
Then it's not a problem in the first place. If you can't reproduce a
bug with a reasonable effort, then it is unconfirmed and you can stop
worrying about it. A bug that can't be reproduced, effectively doesn't
exist.
That's not a reason to
On Fri, 14 Jun 2024 at 11:54, wrote:
>
> Then it's not a problem in the first place. If you can't reproduce a bug with
> a reasonable effort, then it is unconfirmed and you can stop worrying about
> it. A bug that can't be reproduced, effectively doesn't exist.
>
> That's not a reason to stop su
Hello,
On 09.06.24 16:21, Ansgar 🙀 wrote:
Hi,
On Sun, 2024-06-09 at 08:58 -0500, r...@neoquasar.org wrote:
What it is is functional, and paid for. And likely, already installed
and in use somewhere (like all of my 32-bit systems).
It's not just a matter of "buy something better." That's easy.
PSA: as of systemd/256~rc3-3 the open file descriptors hard limit is
bumped early at boot from 1048576 to the max value that the kernel
allows, which on amd64 is currently 1073741816.
Hi,
It seems some proprietary software (the JetBrains IDEs) has some
problems with this change.
See for inst
On Fri, 14 Jun 2024 at 13:21, Mourad De Clerck wrote:
>
> > PSA: as of systemd/256~rc3-3 the open file descriptors hard limit is
> > bumped early at boot from 1048576 to the max value that the kernel
> > allows, which on amd64 is currently 1073741816.
>
> Hi,
>
> It seems some proprietary software
Am 14.06.24 um 14:13 schrieb Mourad De Clerck:
PSA: as of systemd/256~rc3-3 the open file descriptors hard limit is
bumped early at boot from 1048576 to the max value that the kernel
allows, which on amd64 is currently 1073741816.
Hi,
It seems some proprietary software (the JetBrains IDEs) has
On 2024-06-14 Gürkan Myczko wrote:
[...]
> Have never done mass bug filings, any easy way, preferably something copy
> pastable,
> non-interactive.
Hej,
How about mass-bug(1) in devscripts?
cu Andreas
r...@neoquasar.org writes:
> Then it's not a problem in the first place. If you can't reproduce a bug
> with a reasonable effort, then it is unconfirmed and you can stop
> worrying about it.
I think you're confusing two different types of reproduction.
Architecture porting bugs are often hardwar
> On Jun 14, 2024, at 11:46, Russ Allbery wrote:
>
> r...@neoquasar.org writes:
>
>> Then it's not a problem in the first place. If you can't reproduce a bug
>> with a reasonable effort, then it is unconfirmed and you can stop
>> worrying about it.
>
> I think you're confusing two different t
rhys dijo [Fri, Jun 14, 2024 at 01:09:18PM -0500]:
> My response remains the same. If it only affects a small slice of
> systems that already represent a small slice of systems, it becomes
> untenably difficult to chase that one bug that affects that one
> case.
>
> But that does not translate in
Hi
On 14-06-2024 8:09 p.m., rhys wrote:
Even under the bookworm "Intel 686-only" rules, it still works, so I still use
it. It's built, it runs, it serves a purpose, and it costs very little.
And you can keep trying that until it doesn't work for you anymore,
we're not saying we'll hold you
On Fri, 2024-06-14 at 14:07 +0200, Maite Gamper wrote:
> Hello,
>
> On 09.06.24 16:21, Ansgar 🙀 wrote:
[...]
> >
> > As I said before
> > (https://lists.debian.org/debian-devel/2024/05/msg00302.html):
> >
> > If you look at https://release.debian.org/testing/arch_qualify.html
> > there is at lea
Package: wnpp
Severity: wishlist
Owner: Maytham Alsudany
X-Debbugs-CC: debian-devel@lists.debian.org
Control: block 1073140 by -1
* Package name: xcur2png
Version : 0.7.1
Upstream Contact: https://github.com/eworm-de/xcur2png/issues
* URL : https://github.com/eworm-de/
Package: wnpp
Severity: wishlist
Owner: Maytham Alsudany
X-Debbugs-CC: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: azote
Version : 1.12.9
Upstream Contact: https://github.com/nwg-piotr/azote/issues
* URL : https://github.com/nwg-piotr/
On Fri, 14 Jun 2024 21:04:23 +0200, Ben Hutchings
wrote:
>But we definitely should
>discourage users from using i386 kernel packages on 64-bit-capable
>hardware, if we don't drop them entirely. I keep meaning to implement
>a boot-time warning about that...
We could build that into the update-gru
22 matches
Mail list logo
