gmane.linux.debian.ports.mips archive

2301 archived articles, newest first (page 4 of 24). Latest articles →

Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Fri, 4 Aug 2023 15:20:08 +0100
Simon McVittie <[email protected]> • #10031
Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Fri, 4 Aug 2023 13:21:51 +0100
Simon McVittie <[email protected]> • #10030
Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Fri, 4 Aug 2023 20:05:20 +0800
YunQiang Su <[email protected]> • #10029
Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Fri, 4 Aug 2023 19:40:57 +0800
YunQiang Su <[email protected]> • #10028
Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Fri, 4 Aug 2023 12:26:37 +0100
Simon McVittie <[email protected]> • #10027
Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
Thu, 3 Aug 2023 17:29:07 +0100
Simon McVittie <[email protected]> • #10026
Re: OOM while building ghc 9.4.5
Sun, 30 Jul 2023 00:02:46 -0400
Jeffrey Walton <[email protected]> • #10025
Re: OOM while building ghc 9.4.5
Sat, 29 Jul 2023 13:35:44 -0400
Jeffrey Walton <[email protected]> • #10024
Re: OOM while building ghc 9.4.5
Sat, 29 Jul 2023 09:44:42 +0300
Ilias Tsitsimpis <[email protected]> • #10023
Re: OOM while building ghc 9.4.5
Fri, 28 Jul 2023 17:09:05 -0400
Jeffrey Walton <[email protected]> • #10022
Re: OOM while building ghc 9.4.5
Fri, 28 Jul 2023 23:27:29 +0300
Ilias Tsitsimpis <[email protected]> • #10021
Re: unbreaking LibreOffices tests on at least release architectures
Fri, 28 Jul 2023 10:25:10 +0200
Andreas Schwab <[email protected]> • #10020
Re: OOM while building ghc 9.4.5
Wed, 26 Jul 2023 13:02:03 -0400
Jeffrey Walton <[email protected]> • #10019
OOM while building ghc 9.4.5
Wed, 26 Jul 2023 19:23:04 +0300
Ilias Tsitsimpis <[email protected]> • #10018
Re: The future of mipsel port
Wed, 26 Jul 2023 18:24:49 +0200
Aurelien Jarno <[email protected]> • #10017
Re: The future of mipsel port
Mon, 24 Jul 2023 23:07:44 +0300
Adrian Bunk <[email protected]> • #10016
Re: The future of mipsel port
Sun, 23 Jul 2023 20:36:53 +0100
Mark Hymers <[email protected]> • #10015
Re: The future of mipsel port
Sun, 23 Jul 2023 20:36:15 +0200
Paul Gevers <[email protected]> • #10014
Getting Bullseye/Bookworm kernel running on Loongson 3A boards
Sun, 23 Jul 2023 18:16:39 +0200
Aurelien Jarno <[email protected]> • #10013
Re: The future of mipsel port
Sun, 23 Jul 2023 16:51:13 +0100
Mark Hymers <[email protected]> • #10012
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 13:08:17 -0400
Jeffrey Walton <[email protected]> • #10011
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 17:26:25 +0200
Rene Engelhard <[email protected]> • #10010
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 16:09:38 +0200
Andreas Schwab <[email protected]> • #10009
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 15:53:48 +0200
Andreas Schwab <[email protected]> • #10008
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 16:04:03 +0200
Rene Engelhard <[email protected]> • #10007
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 15:25:11 +0200
Rene Engelhard <[email protected]> • #10006
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 15:22:43 +0200
Rene Engelhard <[email protected]> • #10005
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 15:07:47 +0200
Andreas Schwab <[email protected]> • #10004
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 15:02:54 +0200
Andreas Schwab <[email protected]> • #10003
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:34:53 +0200
Andreas Schwab <[email protected]> • #10002
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:28:15 +0200
Andreas Schwab <[email protected]> • #10001
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:25:09 +0200
Andreas Schwab <[email protected]> • #10000
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:38:29 +0200
Rene Engelhard <[email protected]> • #9999
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:36:42 +0200
Rene Engelhard <[email protected]> • #9998
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:35:46 +0200
Rene Engelhard <[email protected]> • #9997
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:27:11 +0200
Rene Engelhard <[email protected]> • #9996
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:02:34 +0200
Andreas Schwab <[email protected]> • #9995
Re: unbreaking LibreOffices tests on at least release architectures
Sat, 22 Jul 2023 14:09:38 +0200
Rene Engelhard <[email protected]> • #9994
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 09:10:09 -0400
"Theodore Ts'o" <[email protected]> • #9993
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 18:14:04 +1000 (AEST)
Finn Thain <[email protected]> • #9992
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 02:11:19 +0100
Matthew Wilcox <[email protected]> • #9991
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 11:03:28 +1000 (AEST)
Finn Thain <[email protected]> • #9990
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 15:53:46 -0700
Linus Torvalds <[email protected]> • #9989
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 23:37:32 +0100
Matthew Wilcox <[email protected]> • #9988
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Fri, 21 Jul 2023 08:20:56 +1000
Dave Chinner <[email protected]> • #9987
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 17:38:52 -0400
Jeffrey Walton <[email protected]> • #9986
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 14:27:50 -0400
Jeff Layton <[email protected]> • #9985
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 18:59:50 +0100
Matthew Wilcox <[email protected]> • #9984
Re: [syzbot] [hfs?] WARNING in hfs_write_inode
Thu, 20 Jul 2023 19:50:47 +0200
John Paul Adrian Glaubitz <[email protected]> • #9983
Re: Bug#1041340: RM: libreoffice [mipsel] -- ROM; broken
Wed, 19 Jul 2023 21:06:58 +0200
Rene Engelhard <[email protected]> • #9982
Re: LibreOffice (code) extensions broken on mips64el/riscv64 (was: Re: unbreaking LibreOffices tests on at least release architectures)
Wed, 19 Jul 2023 20:06:25 +0200
Rene Engelhard <[email protected]> • #9981
Re: The future of mipsel port
Wed, 19 Jul 2023 15:06:30 +0800
YunQiang Su <[email protected]> • #9980
Re: The future of mipsel port
Wed, 19 Jul 2023 08:43:21 +0200
Aurelien Jarno <[email protected]> • #9979
Re: The future of mipsel port
Wed, 19 Jul 2023 12:06:41 +0800
YunQiang Su <[email protected]> • #9978
Re: The future of mipsel port
Wed, 19 Jul 2023 11:23:02 +0800
Paul Wise <[email protected]> • #9977
Re: The future of mipsel port
Wed, 19 Jul 2023 05:59:22 +0800
YunQiang Su <[email protected]> • #9976
Re: The future of mipsel port
Tue, 18 Jul 2023 15:26:13 +0200
Mathieu Malaterre <[email protected]> • #9975
Re: The future of mipsel port
Tue, 18 Jul 2023 10:41:21 +0100
Matthew Garrett <[email protected]> • #9974
The future of mipsel port
Tue, 18 Jul 2023 12:45:51 +0800
YunQiang Su <[email protected]> • #9973
Re: Problemas para instalar Debian 11 en Loongson 3A3000D-HP
Tue, 18 Jul 2023 12:25:52 +0800
YunQiang Su <[email protected]> • #9972
Re: Problemas para instalar Debian 11 en Loongson 3A3000D-HP
Tue, 18 Jul 2023 11:30:18 +0800
"chipo" <[email protected]> • #9971
Bug#1041340: RM: libreoffice [mipsel] -- ROM; broken
Mon, 17 Jul 2023 19:38:42 +0200
Rene Engelhard <[email protected]> • #9970
Re: Bug#1040827: RM: firefox [mipsel] -- RoQA; severely outdated, depends on transitional libgdk-pixbuf2.0-0
Wed, 12 Jul 2023 21:38:22 +0100
Simon McVittie <[email protected]> • #9969
Bug#1040827: RM: firefox [mipsel] -- RoQA; severely outdated, depends on transitional libgdk-pixbuf2.0-0
Tue, 11 Jul 2023 10:04:32 +0100
Simon McVittie <[email protected]> • #9968
Re: LibreOffice (code) extensions broken on mips64el/riscv64 (was: Re: unbreaking LibreOffices tests on at least release architectures)
Mon, 10 Jul 2023 18:01:48 +0200
Rene Engelhard <[email protected]> • #9967
Bug#1040663: linux: Please build linux-libc-dev package for loong64
Sat, 08 Jul 2023 20:41:03 +0200
John Paul Adrian Glaubitz <[email protected]> • #9966
LibreOffice (code) extensions broken on mips64el/riscv64 (was: Re: unbreaking LibreOffices tests on at least release architectures)
Tue, 4 Jul 2023 23:56:52 +0200
Rene Engelhard <[email protected]> • #9965
Re: LibreOffice bridges/smoket est on mips(64)el (was: Re: unb reaking LibreOffices tests on at least release architectures)
Tue, 04 Jul 2023 14:23:02 +0200
René Engelhard <[email protected]> • #9964
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]> • #9963
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]> • #9962
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]> • #9961
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 25 Jun 2023 13:37:19 +0200
Rene Engelhard <[email protected]> • #9960
Bug#1037414: gcc-13 ftbfs on mipsel
Thu, 22 Jun 2023 14:50:22 +0200
Matthias Klose <[email protected]> • #9959
Re: unbreaking LibreOffices tests on at least release architectures
Wed, 21 Jun 2023 10:15:14 +0800
Paul Wise <[email protected]> • #9958
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 22:46:42 +0200
Kurt Roeckx <[email protected]> • #9957
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 17:35:55 +0200
Rene Engelhard <[email protected]> • #9956
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 16:52:57 +0200
Kurt Roeckx <[email protected]> • #9955
Re: gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el
Tue, 20 Jun 2023 13:19:17 +0200
Paul Gevers <[email protected]> • #9954
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 09:46:59 +0100
Kirsten Bromilow <[email protected]> • #9953
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 11:25:09 +0300
Adrian Bunk <[email protected]> • #9952
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:07:48 -0400
Jeffrey Walton <[email protected]> • #9951
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:52:44 +0200
Rene Engelhard <[email protected]> • #9950
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 05:50:35 +0200
Rene Engelhard <[email protected]> • #9949
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 02:27:56 +0300
Adrian Bunk <[email protected]> • #9948
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 18:03:42 -0400
Jeffrey Walton <[email protected]> • #9947
Re: unbreaking LibreOffices tests on at least release architectures
Tue, 20 Jun 2023 00:19:46 +0300
Adrian Bunk <[email protected]> • #9946
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 23:29:34 +0200
Rene Engelhard <[email protected]> • #9945
Re: Lemote Fuloong 2F
Mon, 19 Jun 2023 02:48:44 -0400
Jeffrey Walton <[email protected]> • #9944
Re: Lemote Fuloong 2F
Mon, 19 Jun 2023 14:26:07 +0800
YunQiang Su <[email protected]> • #9943
Lemote Fuloong 2F
Mon, 19 Jun 2023 08:53:17 +0300
Efraim Flashner <[email protected]> • #9942
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 02:41:24 +0200 (CEST)
Jan Engelhardt <[email protected]> • #9941
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 17:14:07 -0500
Rob Landley <[email protected]> • #9940
Re: unbreaking LibreOffices tests on at least release architectures
Mon, 19 Jun 2023 00:04:45 +0200
Kurt Roeckx <[email protected]> • #9939
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 16:37:55 -0500
Rob Landley <[email protected]> • #9938
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 22:19:38 +0200
Rene Engelhard <[email protected]> • #9937
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 21:58:14 +0200
Rene Engelhard <[email protected]> • #9936
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:28:15 -0500
Rob Landley <[email protected]> • #9935
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 14:11:20 +0200
Omer Turpault <[email protected]> • #9934
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 12:36:03 +0100
Steve McIntyre <[email protected]> • #9933
Re: unbreaking LibreOffices tests on at least release architectures
Sun, 18 Jun 2023 10:45:57 +0200
Rene Engelhard <[email protected]> • #9932
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.