gmane.linux.debian.ports.alpha archive

400 archived articles, newest first (page 3 of 4). Latest articles →

Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:25:09 +0200
Andreas Schwab <[email protected]> • #10349
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:38:29 +0200
Rene Engelhard <[email protected]> • #10348
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:36:42 +0200
Rene Engelhard <[email protected]> • #10347
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:35:46 +0200
Rene Engelhard <[email protected]> • #10346
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:27:11 +0200
Rene Engelhard <[email protected]> • #10345
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:02:34 +0200
Andreas Schwab <[email protected]> • #10344
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:09:38 +0200
Rene Engelhard <[email protected]> • #10343
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 09:10:09 -0400
"Theodore Ts'o" <[email protected]> • #10342
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 18:14:04 +1000 (AEST)
Finn Thain <[email protected]> • #10341
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 02:11:19 +0100
Matthew Wilcox <[email protected]> • #10340
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 11:03:28 +1000 (AEST)
Finn Thain <[email protected]> • #10339
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 15:53:46 -0700
Linus Torvalds <[email protected]> • #10338
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 23:37:32 +0100
Matthew Wilcox <[email protected]> • #10337
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 08:20:56 +1000
Dave Chinner <[email protected]> • #10336
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 17:38:52 -0400
Jeffrey Walton <[email protected]> • #10335
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 14:27:50 -0400
Jeff Layton <[email protected]> • #10334
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 18:59:50 +0100
Matthew Wilcox <[email protected]> • #10333
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 19:50:47 +0200
John Paul Adrian Glaubitz <[email protected]> • #10332
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]> • #10331
Bug#1040062: dpkg-dev: Please drop pie-{compile,link}.spec
Tue, 4 Jul 2023 13:12:48 +0300
Adrian Bunk <[email protected]> • #10330
Re: Bug#1040062: dpkg-dev: Please drop pie-{compile,link}.spec
Tue, 4 Jul 2023 09:23:43 +0200
Guillem Jover <[email protected]> • #10329
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]> • #10328
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]> • #10327
Bug#1040062: dpkg-dev: Please drop pie-{compile,link}.spec
Sun, 02 Jul 2023 00:02:46 +0300
Adrian Bunk <[email protected]> • #10326
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 25 Jun 2023 13:37:19 +0200
Rene Engelhard <[email protected]> • #10325
Re: unbreaking LibreOffices tests on at least release architectures
Wed, 21 Jun 2023 10:15:14 +0800
Paul Wise <[email protected]> • #10324
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 22:46:42 +0200
Kurt Roeckx <[email protected]> • #10323
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 17:35:55 +0200
Rene Engelhard <[email protected]> • #10322
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 16:52:57 +0200
Kurt Roeckx <[email protected]> • #10321
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 09:46:59 +0100
Kirsten Bromilow <[email protected]> • #10320
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 11:25:09 +0300
Adrian Bunk <[email protected]> • #10319
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:07:48 -0400
Jeffrey Walton <[email protected]> • #10318
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:52:44 +0200
Rene Engelhard <[email protected]> • #10317
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:50:35 +0200
Rene Engelhard <[email protected]> • #10316
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 02:27:56 +0300
Adrian Bunk <[email protected]> • #10315
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 18:03:42 -0400
Jeffrey Walton <[email protected]> • #10314
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:19:46 +0300
Adrian Bunk <[email protected]> • #10313
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 23:29:34 +0200
Rene Engelhard <[email protected]> • #10312
Re: Linux 6.1.27, cgroup: Instruction fault 4 with systemd
Mon, 19 Jun 2023 14:01:36 +0200
Frank Scheiner <[email protected]> • #10311
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 02:41:24 +0200 (CEST)
Jan Engelhardt <[email protected]> • #10310
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 17:14:07 -0500
Rob Landley <[email protected]> • #10309
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 00:04:45 +0200
Kurt Roeckx <[email protected]> • #10308
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 16:37:55 -0500
Rob Landley <[email protected]> • #10307
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 22:19:38 +0200
Rene Engelhard <[email protected]> • #10306
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 21:58:14 +0200
Rene Engelhard <[email protected]> • #10305
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:28:15 -0500
Rob Landley <[email protected]> • #10304
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:11:20 +0200
Omer Turpault <[email protected]> • #10303
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 12:36:03 +0100
Steve McIntyre <[email protected]> • #10302
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:45:57 +0200
Rene Engelhard <[email protected]> • #10301
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:32:55 +0200
Rene Engelhard <[email protected]> • #10300
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:19:28 +0200
John Paul Adrian Glaubitz <[email protected]> • #10299
unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 09:31:05 +0200
Rene Engelhard <[email protected]> • #10298
Updated installation images for Debian Ports
Wed, 14 Jun 2023 15:06:55 +0200
John Paul Adrian Glaubitz <[email protected]> • #10297
Re: Updated installation images for Debian Ports 2023-06-06
Tue, 6 Jun 2023 16:11:46 +0200
Rafael Ruiz <[email protected]> • #10296
Updated installation images for Debian Ports 2023-06-06
Tue, 06 Jun 2023 15:52:10 +0200
John Paul Adrian Glaubitz <[email protected]> • #10295
Re: [PATCH] module: fix module load for ia64
Sun, 4 Jun 2023 14:34:08 -0700
Song Liu <[email protected]> • #10294
Re: [PATCH] module: fix module load for ia64
Sat, 3 Jun 2023 15:30:13 +0200
Frank Scheiner <[email protected]> • #10293
Re: systemd 252.6-1 produces an Instruction fault, sysvinit works
Mon, 22 May 2023 11:48:35 +0200
Frank Scheiner <[email protected]> • #10292
Re: Linux 6.1.27, cgroup: Instruction fault 4 with systemd
Mon, 22 May 2023 11:37:38 +0200
John Paul Adrian Glaubitz <[email protected]> • #10291
Linux 6.1.27, cgroup: Instruction fault 4 with systemd
Mon, 22 May 2023 11:34:47 +0200
Frank Scheiner <[email protected]> • #10290
Re: systemd 252.6-1 produces an Instruction fault, sysvinit works
Sun, 21 May 2023 09:48:43 +0200
John Paul Adrian Glaubitz <[email protected]> • #10289
Re: systemd 252.6-1 produces an Instruction fault, sysvinit works
Sun, 21 May 2023 12:11:20 +1200
Michael Cree <[email protected]> • #10288
Re: future of the libc6.1-alphaev67 package
Sat, 20 May 2023 09:25:09 +1200
Michael Cree <[email protected]> • #10287
Bug#1036158: gcc-13: Please raise baseline for alpha to EV56
Sat, 20 May 2023 09:19:46 +1200
Michael Cree <[email protected]> • #10286
systemd 252.6-1 produces an Instruction fault, sysvinit works
Thu, 18 May 2023 13:01:25 +0200
Frank Scheiner <[email protected]> • #10285
Re: Bug#1036158: gcc-13: Please raise baseline for alpha to EV56
Wed, 17 May 2023 21:17:23 +0200
Frank Scheiner <[email protected]> • #10284
Re: Bug#1036158: gcc-13: Please raise baseline for alpha to EV56
Wed, 17 May 2023 11:27:43 +0200
John Paul Adrian Glaubitz <[email protected]> • #10283
Bug#1036158: gcc-13: Please raise baseline for alpha to EV56
Tue, 16 May 2023 09:38:56 +0200
John Paul Adrian Glaubitz <[email protected]> • #10282
Re: future of the libc6.1-alphaev67 package
Mon, 15 May 2023 12:13:04 +0200
John Paul Adrian Glaubitz <[email protected]> • #10281
Re: future of the libc6.1-alphaev67 package
Sun, 14 May 2023 22:47:44 +0200
Aurelien Jarno <[email protected]> • #10280
Re: future of the libc6.1-alphaev67 package
Sun, 14 May 2023 22:06:06 +0200
John Paul Adrian Glaubitz <[email protected]> • #10279
Re: future of the libc6.1-alphaev67 package
Sun, 14 May 2023 21:53:56 +0200
Aurelien Jarno <[email protected]> • #10278
I desperately need help
Wed, 19 Apr 2023 18:17:33 +0000
Ethan Burns <[email protected]> • #10277
New energy drinks on offer
Wed, 22 Feb 2023 08:30:32 GMT
"Bernardo Lecerda" <[email protected]> • #10276
Bug#1028624: libdeflate: Please build with -O1 on alpha to fix FTBFS
Fri, 13 Jan 2023 20:05:43 +0100
John Paul Adrian Glaubitz <[email protected]> • #10275
Re: Bug#963109: libreoffice: Please drop clang from build-dependencies for alpha and ia64
Wed, 11 Jan 2023 20:03:49 +0100
John Paul Adrian Glaubitz <[email protected]> • #10274
Re: Bug#963109: libreoffice: Please drop clang from build-dependencies for alpha and ia64
Wed, 11 Jan 2023 19:45:42 +0100
John Paul Adrian Glaubitz <[email protected]> • #10273
Re: [PATCH] elf: Fix GL(dl_phdr) and GL(dl_phnum) for static builds [BZ #29864]
Wed, 11 Jan 2023 14:49:59 -0300
Adhemerval Zanella Netto via Libc-alpha <[email protected]> • #10272
Re: [PATCH] elf: Fix GL(dl_phdr) and GL(dl_phnum) for static builds [BZ #29864]
Wed, 11 Jan 2023 15:27:53 +0100
Florian Weimer via Libc-alpha <[email protected]> • #10271
LibreOffice architecture support (was: Fwd: Plan to remove dead C++ UNO bridge implementations (bridges/source/cpp_uno/*))
Tue, 10 Jan 2023 19:25:53 +0100
Rene Engelhard <[email protected]> • #10270
Bug#1028200: glibc: FTBFS on alpha due to buggy GL(dl_phdr) and GL(dl_phnum) [BZ #29864]
Sun, 08 Jan 2023 13:39:59 +0100
John Paul Adrian Glaubitz <[email protected]> • #10269
Re: Unversioned symbols when building kernel package
Fri, 6 Jan 2023 09:05:17 +0100
John Paul Adrian Glaubitz <[email protected]> • #10268
Re: Unversioned symbols when building kernel package
Thu, 05 Jan 2023 17:15:05 +0100
Ben Hutchings <[email protected]> • #10267
Re: Unversioned symbols when building kernel package
Thu, 5 Jan 2023 17:39:12 +0100
John Paul Adrian Glaubitz <[email protected]> • #10266
Re: Unversioned symbols when building kernel package
Thu, 5 Jan 2023 13:24:54 +0100
John Paul Adrian Glaubitz <[email protected]> • #10265
Bug#1027974: linux: FTBFS on alpha due to unversioned symbols
Thu, 05 Jan 2023 13:03:05 +0100
John Paul Adrian Glaubitz <[email protected]> • #10264
Re: Update on the glibc segfault issue on Alpha
Thu, 5 Jan 2023 12:25:02 +0100
John Paul Adrian Glaubitz <[email protected]> • #10263
Re: Unversioned symbols when building kernel package
Wed, 4 Jan 2023 23:31:07 +0100
John Paul Adrian Glaubitz <[email protected]> • #10262
Re: Unversioned symbols when building kernel package
Wed, 4 Jan 2023 23:00:03 +0100
Frank Scheiner <[email protected]> • #10261
Unversioned symbols when building kernel package
Wed, 4 Jan 2023 22:15:31 +0100
John Paul Adrian Glaubitz <[email protected]> • #10260
Re: Update on the glibc segfault issue on Alpha
Wed, 4 Jan 2023 09:00:16 -0300
Adhemerval Zanella Netto via Libc-alpha <[email protected]> • #10259
Re: Update on the glibc segfault issue on Alpha
Wed, 4 Jan 2023 10:25:57 +0100
John Paul Adrian Glaubitz <[email protected]> • #10258
[PATCH] elf: Fix GL(dl_phdr) and GL(dl_phnum) for static builds [BZ #29864]
Tue, 3 Jan 2023 11:30:11 -0300
Adhemerval Zanella via Libc-alpha <[email protected]> • #10257
Re: Update on the glibc segfault issue on Alpha
Tue, 3 Jan 2023 10:47:02 -0300
Adhemerval Zanella Netto via Libc-alpha <[email protected]> • #10256
Re: Update on the glibc segfault issue on Alpha
Tue, 03 Jan 2023 14:29:56 +0100
Florian Weimer via Libc-alpha <[email protected]> • #10255
Re: Update on the glibc segfault issue on Alpha
Tue, 3 Jan 2023 09:09:04 -0300
Adhemerval Zanella Netto via Libc-alpha <[email protected]> • #10254
Re: Update on the glibc segfault issue on Alpha
Mon, 2 Jan 2023 18:37:54 +0100
John Paul Adrian Glaubitz <[email protected]> • #10253
Update on the glibc segfault issue on Alpha
Mon, 2 Jan 2023 12:44:40 +0100
John Paul Adrian Glaubitz <[email protected]> • #10252
Re: glibc regression on alpha with 2.34+
Wed, 21 Dec 2022 17:54:48 +0100
John Paul Adrian Glaubitz <[email protected]> • #10251
Re: glibc regression on alpha with 2.34+
Wed, 21 Dec 2022 01:58:13 +0100
John Paul Adrian Glaubitz <[email protected]> • #10250
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.