gmane.linux.debian.ports.s390 archive

1130 archived articles, newest first (page 11 of 12). Latest articles →

Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:28:15 +0200
Andreas Schwab <[email protected]> • #4561
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:25:09 +0200
Andreas Schwab <[email protected]> • #4560
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:38:29 +0200
Rene Engelhard <[email protected]> • #4559
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:36:42 +0200
Rene Engelhard <[email protected]> • #4558
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:35:46 +0200
Rene Engelhard <[email protected]> • #4557
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:27:11 +0200
Rene Engelhard <[email protected]> • #4556
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:02:34 +0200
Andreas Schwab <[email protected]> • #4555
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:09:38 +0200
Rene Engelhard <[email protected]> • #4554
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 09:10:09 -0400
"Theodore Ts'o" <[email protected]> • #4553
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 18:14:04 +1000 (AEST)
Finn Thain <[email protected]> • #4552
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 02:11:19 +0100
Matthew Wilcox <[email protected]> • #4551
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 11:03:28 +1000 (AEST)
Finn Thain <[email protected]> • #4550
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 15:53:46 -0700
Linus Torvalds <[email protected]> • #4549
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 23:37:32 +0100
Matthew Wilcox <[email protected]> • #4548
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 08:20:56 +1000
Dave Chinner <[email protected]> • #4547
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 17:38:52 -0400
Jeffrey Walton <[email protected]> • #4546
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 14:27:50 -0400
Jeff Layton <[email protected]> • #4545
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 18:59:50 +0100
Matthew Wilcox <[email protected]> • #4544
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 19:50:47 +0200
John Paul Adrian Glaubitz <[email protected]> • #4543
Re: Adduser/logger problems in s390x autopkgtest
Mon, 10 Jul 2023 14:23:41 +0800
Paul Wise <[email protected]> • #4542
Adduser/logger problems in s390x autopkgtest
Sun, 9 Jul 2023 18:32:26 +0200
Marc Haber <[email protected]> • #4541
Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)
Tue, 04 Jul 2023 15:58:18 +0200
Laurent Siksous <[email protected]> • #4540
Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)
Tue, 4 Jul 2023 14:29:48 +0300
Adrian Bunk <[email protected]> • #4539
Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)
Mon, 3 Jul 2023 21:55:29 +0200
Rene Engelhard <[email protected]> • #4538
LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures)
Mon, 3 Jul 2023 21:31:29 +0200
Rene Engelhard <[email protected]> • #4537
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 25 Jun 2023 13:37:19 +0200
Rene Engelhard <[email protected]> • #4536
Bug#1038827: libwebm: Failed tests in big-endian architectures
Wed, 21 Jun 2023 16:51:46 -0400
Boyuan Yang <[email protected]> • #4535
Re: unbreaking LibreOffices tests on at least release architectures
Wed, 21 Jun 2023 10:15:14 +0800
Paul Wise <[email protected]> • #4534
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 22:46:42 +0200
Kurt Roeckx <[email protected]> • #4533
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 17:35:55 +0200
Rene Engelhard <[email protected]> • #4532
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 16:52:57 +0200
Kurt Roeckx <[email protected]> • #4531
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 09:46:59 +0100
Kirsten Bromilow <[email protected]> • #4530
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 11:25:09 +0300
Adrian Bunk <[email protected]> • #4529
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:07:48 -0400
Jeffrey Walton <[email protected]> • #4528
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:52:44 +0200
Rene Engelhard <[email protected]> • #4527
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:50:35 +0200
Rene Engelhard <[email protected]> • #4526
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 02:27:56 +0300
Adrian Bunk <[email protected]> • #4525
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 18:03:42 -0400
Jeffrey Walton <[email protected]> • #4524
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:19:46 +0300
Adrian Bunk <[email protected]> • #4523
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 23:29:34 +0200
Rene Engelhard <[email protected]> • #4522
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 02:41:24 +0200 (CEST)
Jan Engelhardt <[email protected]> • #4521
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 17:14:07 -0500
Rob Landley <[email protected]> • #4520
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 00:04:45 +0200
Kurt Roeckx <[email protected]> • #4519
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 16:37:55 -0500
Rob Landley <[email protected]> • #4518
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 22:19:38 +0200
Rene Engelhard <[email protected]> • #4517
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 21:58:14 +0200
Rene Engelhard <[email protected]> • #4516
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:28:15 -0500
Rob Landley <[email protected]> • #4515
Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Sun, 18 Jun 2023 15:58:10 +0200
John Paul Adrian Glaubitz <[email protected]> • #4514
Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Sun, 18 Jun 2023 14:52:18 +0100
Simon McVittie <[email protected]> • #4513
Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Sun, 18 Jun 2023 14:46:58 +0100
Simon McVittie <[email protected]> • #4512
Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022
Sun, 18 Jun 2023 13:40:09 +0100
Simon McVittie <[email protected]> • #4511
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:11:20 +0200
Omer Turpault <[email protected]> • #4510
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 12:36:03 +0100
Steve McIntyre <[email protected]> • #4509
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:45:57 +0200
Rene Engelhard <[email protected]> • #4508
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:32:55 +0200
Rene Engelhard <[email protected]> • #4507
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:19:28 +0200
John Paul Adrian Glaubitz <[email protected]> • #4506
unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 09:31:05 +0200
Rene Engelhard <[email protected]> • #4505
Re: help needed to manage s390x host for ci.debian.net
Wed, 10 May 2023 11:27:42 +0530
Dipak Zope <[email protected]> • #4504
Re: help needed to manage s390x host for ci.debian.net
Thu, 20 Apr 2023 08:21:40 +0200
Paul Gevers <[email protected]> • #4503
Re: help needed to manage s390x host for ci.debian.net
Tue, 18 Apr 2023 13:46:32 -0700
"Elizabeth K. Joseph" <[email protected]> • #4502
Re: Help needed with tomopy/s390x
Wed, 15 Mar 2023 06:21:56 +0000
Dipak Zope1 <[email protected]> • #4501
Help needed with tomopy/s390x
Tue, 14 Mar 2023 17:56:02 +0100
Roland Mas <[email protected]> • #4500
Re: help needed to manage s390x host for ci.debian.net
Tue, 28 Feb 2023 21:04:45 +0100
Paul Gevers <[email protected]> • #4499
Re: help needed to manage s390x host for ci.debian.net
Tue, 28 Feb 2023 00:39:02 +0000
James Addison <[email protected]> • #4498
RE: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Fri, 24 Feb 2023 18:21:00 +0000
Dipak Zope1 <[email protected]> • #4497
Re: help needed to manage s390x host for ci.debian.net
Tue, 21 Feb 2023 20:44:38 +0100
Paul Gevers <[email protected]> • #4496
RE: help needed to manage s390x host for ci.debian.net
Tue, 21 Feb 2023 16:46:56 +0000
Dipak Zope1 <[email protected]> • #4495
Re: help needed to manage s390x host for ci.debian.net
Mon, 20 Feb 2023 21:45:36 +0100
Philipp Kern <[email protected]> • #4494
Re: help needed to manage s390x host for ci.debian.net
Sat, 18 Feb 2023 16:26:22 +0100
Philipp Kern <[email protected]> • #4493
Re: help needed to manage s390x host for ci.debian.net
Sat, 18 Feb 2023 14:23:02 +0000
James Addison <[email protected]> • #4492
Re: help needed to manage s390x host for ci.debian.net
Fri, 17 Feb 2023 13:04:09 -0300
Antonio Terceiro <[email protected]> • #4491
Patch "[PATCH v2 1/1] s390/signal: fix endless loop in do_signal" has been added to the 5.10-stable tree
Fri, 17 Feb 2023 15:15:14 +0100
<[email protected]> • #4490
Re: [PATCH v2 1/1] s390/signal: fix endless loop in do_signal
Fri, 17 Feb 2023 15:04:54 +0100
Greg KH <[email protected]> • #4489
Re: help needed to manage s390x host for ci.debian.net
Thu, 16 Feb 2023 17:49:56 +0100
Paul Gevers <[email protected]> • #4488
[PATCH v3] s390/signal: fix endless loop in do_signal
Wed, 15 Feb 2023 16:13:35 +0100
Sumanth Korikkar <[email protected]> • #4487
[PATCH v2 1/1] s390/signal: fix endless loop in do_signal
Wed, 15 Feb 2023 15:13:24 +0100
Sumanth Korikkar <[email protected]> • #4486
Re: [PATCH 0/1] s390: fix endless loop in do_signal
Wed, 15 Feb 2023 14:49:22 +0100
Greg KH <[email protected]> • #4485
Re: [PATCH 0/1] s390: fix endless loop in do_signal
Wed, 15 Feb 2023 14:35:24 +0100
Heiko Carstens <[email protected]> • #4484
Re: [PATCH 0/1] s390: fix endless loop in do_signal
Wed, 15 Feb 2023 14:23:20 +0100
Greg KH <[email protected]> • #4483
Re: [PATCH 1/1] s390/signal: fix endless loop in do_signal
Wed, 15 Feb 2023 14:22:24 +0100
Greg KH <[email protected]> • #4482
[PATCH 1/1] s390/signal: fix endless loop in do_signal
Wed, 15 Feb 2023 13:04:13 +0100
Sumanth Korikkar <[email protected]> • #4481
[PATCH 0/1] s390: fix endless loop in do_signal
Wed, 15 Feb 2023 13:04:12 +0100
Sumanth Korikkar <[email protected]> • #4480
Re: help needed to manage s390x host for ci.debian.net
Tue, 14 Feb 2023 21:42:09 +0100
Paul Gevers <[email protected]> • #4479
Mary Hasan
Tue, 14 Feb 2023 11:52:26 +0000
dhruv balodia <[email protected]> • #4478
RE: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Mon, 13 Feb 2023 15:49:26 +0000
Dipak Zope1 <[email protected]> • #4477
RE: suspecting 5.10.0-21 kernel breaking something with futexes on s390x
Mon, 13 Feb 2023 15:05:40 +0000
Dipak Zope1 <[email protected]> • #4476
RE: help needed to manage s390x host for ci.debian.net
Mon, 13 Feb 2023 14:59:50 +0000
Dipak Zope1 <[email protected]> • #4475
Re: help needed to manage s390x host for ci.debian.net
Mon, 13 Feb 2023 08:57:33 +0100
Philipp Kern <[email protected]> • #4474
RE: help needed to manage s390x host for ci.debian.net
Mon, 13 Feb 2023 06:33:08 +0000
Dipak Zope1 <[email protected]> • #4473
Re: help needed to manage s390x host for ci.debian.net
Sun, 12 Feb 2023 22:38:46 +0100
Paul Gevers <[email protected]> • #4472
Re: help needed to manage s390x host for ci.debian.net
Sun, 12 Feb 2023 20:32:27 +0100
Philipp Kern <[email protected]> • #4471
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Sat, 11 Feb 2023 14:20:50 -0800
Otto Kekäläinen <[email protected]> • #4470
help needed to manage s390x host for ci.debian.net
Sat, 11 Feb 2023 18:18:12 +0100
Paul Gevers <[email protected]> • #4469
Bug#1031022: Does not work on big endian machines
Fri, 10 Feb 2023 15:41:07 +0100
Enrico Zini <[email protected]> • #4468
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Wed, 8 Feb 2023 11:42:10 +0000
Andrew Hutchings <[email protected]> • #4467
Re: Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Wed, 8 Feb 2023 08:51:24 +0100
Sebastian Ramacher <[email protected]> • #4466
Bug#1030510: Info received (Bug#1030510: Info received (Bug#1030510: Info received (mariadb: FTBFS on s390x: timeout)))
Tue, 7 Feb 2023 08:36:11 -0800
Otto Kekäläinen <[email protected]> • #4465
Re: suspecting 5.10.0-21 kernel breaking something with futexes on s390x
Mon, 6 Feb 2023 13:32:48 +0000
Dipak Zope1 <[email protected]> • #4464
Re: suspecting 5.10.0-21 kernel breaking something with futexes on s390x
Mon, 6 Feb 2023 13:34:10 +0000
Dipak Zope1 <[email protected]> • #4463
suspecting 5.10.0-21 kernel breaking something with futexes on s390x
Mon, 6 Feb 2023 16:20:04 +0300
Michael Tokarev <[email protected]> • #4462
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.