On 7/28/24 16:19, Adam D. Barratt wrote:
On Wed, 2024-02-14 at 20:03 +, OVHcloud wrote:
Submission-Type: new
Site: debian.mirrors.ovh.net
Apologies for the long delay in getting back to this.
Our automated checks noticed an issue with your setup, which is
hopefully easy to resolve:
o The
On 3/22/24 17:42, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
On Wed, 2024-02-14 at 20:03 +, OVHcloud wrote:
Site: debian.mirrors.ovh.net
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-
amd64 i386 mips mips64el mipsel powerpc ppc64el riscv64 s390x
Archive-http: /deb
Package: ipmiutil
Version: 3.1.8-4
Hi,
In some cases (Intel S2600STB boards), ipmiutil fails to install the
first time:
Setting up ipmiutil (3.1.8-4) ...
SDR record 61 is malformed, length 12 is less than minimum 12
0061 GetSDR error -25, rlen = 10
dpkg: error processing package ipmiutil (--co
Package: grub-pc
Version: 2.06-13
Hi,
When ZFS is used for the / or /boot partitions on legacy boot servers
(with vdevs using more than one disk/partition), grub-pc's postinst
shows this during the configure phase:
┌──┤ Configuring grub-pc ├──┐
│ GRUB i
On 28/12/2020 00:24, Markus Koschany wrote:
Hello,
I have prepared a new security update of pacemaker, the latest version in the
1.1.x series. The update will fix CVE-2018-16877, CVE-2018-16878 and CVE-2020-
25654. I would appreciate it if you could test this version before it is
uploaded to str
Package: pacemaker
Version: 1.1.16-1+deb9u1
Severity: grave
X-Debbugs-CC: a...@debian.org
Hi,
I am running corosync 2.4.2-3+deb9u1 with pacemaker and the last run of
unattended-upgrades broke the cluster (downgrading pacemaker to 1.1.16-1
fixed it immediately).
The logs contain a lot of warnings t
On 13/11/2020 12:23, Alejandro Taboada wrote:
> Maybe Corocync is not using peer communication? Could you check someway the
> packet source address .. if it’s form localhost just allow, other check
> permissions
> I know is not ideal but will solve a tot of production issues in the
> meanwhile.
On 17/11/2020 18:41, Alejandro Taboada wrote:
> Thank you Markus,
>
> I just updated deb9u2 and works fine. Let me know when you have new updates
> and I can test this thing.
>
> Regards,
> Alejandro
>
>> On 17 Nov 2020, at 05:16, Markus Koschany wrote:
>>
>> Control: severity -1 normal
>>
>>
Package: zfsutils-linux
Version: 2.0.3-9
|Severity: important|
Hi,
Currently, creating a ZFS dataset with mountpoint=legacy and adding it to
/etc/fstab as auto causes the system to hang at boot because the mount is
attempted before the pool has been imported or the ZFS module loaded.
How to rep
On 29/01/2025 08:04, Ritesh Raj Sarraf wrote:
It is preferred to have the point of view from upstream as well. Let's
wait and see. 🙏
s3nt fr0m a $martph0ne, excuse typ0s
On Tue, 28 Jan 2025, 16:17 Louis Sautier, wrote:
On 28/01/2025 09:22, Ritesh Raj Sarraf wrote:
Opening an
On 10/02/2025 09:59, Ritesh Raj Sarraf wrote:
On Mon, 2025-02-10 at 04:27 +0100, Louis Sautier wrote:
It has now been ~2 weeks since I opened the issue on GitHub and
almost a
month since I emailed the author.
Could you or another maintainer check my merge request at
https://salsa.debian.org
Package: smp-utils
Version: 0.99-1
Hi,
smp_discover 1.62 20190124 from smp-utils 0.99-1 has a bug when the
-p/--phy options is used; -n/--num is also broken.
The main problem is that the -p option is handled incorrectly, e.g.
smp_discover -p 5
not only starts at phy 5 but also skips the last 5
On 28/01/2025 06:44, Ritesh Raj Sarraf wrote:
Have you reported it upstream ? That'd be the very first thing to do
s3nt fr0m a $martph0ne, excuse typ0s
On Tue, 28 Jan 2025, 02:21 Louis Sautier, wrote:
Package: smp-utils
Version: 0.99-1
Hi,
smp_discover 1.62 20190124 fro
On 28/01/2025 09:22, Ritesh Raj Sarraf wrote:
Opening an issue is worthwhile. The reason is because emails may fall
under spam classification while opening an issue guarantees that it is
reported.
s3nt fr0m a $martph0ne, excuse typ0s
On Tue, 28 Jan 2025, 12:30 Louis Sautier, wrote:
On
14 matches
Mail list logo
