Re: News about Firefox for PowerPC
On 3/7/19 8:21 AM, Dennis Clarke wrote: > Ha. Let's not drag the SPARC world into this. In my opinion, based on > some twenty years of observational data, the only problem with SPARC > based systems is that they are horribly slow and run horribly hot while > costing horrible amounts of money. Other than that it is a fantastic > architecture. :-) Slow? The SPARC T5 we have in Debian Ports is eight or nine years old and is still one of the fastest machines we have in the whole of Debian. But that was not my point: My point is to ask users to fix bugs upstream so everyone profits from the fixes and don't keep your fixes local. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: News about Firefox for PowerPC
On 3/6/19 12:34 PM, John Paul Adrian Glaubitz wrote: > On 3/6/19 5:52 AM, Dennis Clarke wrote: >> So would it be of value for me to fire up Debian buster or sid on a >> PowerMac G5 here and do some testing? Not sure where you are getting >> your Firefox from. Also is that the nightly builds? > > We're building stock Debian packages from unstable. Debian has a "firefox" > and a "firefox-esr" package, both maintained by Mike Hommey who is also > an engineer working at Mozilla. > >> I currently am >> running 67.0a1 where about:buildconfig claims : >> >> https://hg.mozilla.org/mozilla-central/rev/78601cacfe69dc8659c3fe7cd3eb94366aa3d680 >> >> Is this similar to Firefox for PowerPC ? > > There is no "Firefox for PowerPC". Again, I'm not building packages manually > for powerpc/ppc64. All packages you are getting for powerpc and ppc64 are > automatically built from what's in the Debian archive for Debian unstable. > > Any bug fixes should therefore either go to the corresponding Debian package, > or even better, forwarded upstream. Keeping fixes in local repositories > specifically > for powerpc or ppc64 is a very bad idea because those fixes will have to be > carried > around indefinitely. You will always want to upstream everything to make sure > everyone gets those fixes. > > And if something crashes on SPARC, for example, there is a chance the bug also > affects x86, just in a more subtle way. Ha. Let's not drag the SPARC world into this. In my opinion, based on some twenty years of observational data, the only problem with SPARC based systems is that they are horribly slow and run horribly hot while costing horrible amounts of money. Other than that it is a fantastic architecture. :-) -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional
Re: PPC64 Illegal Instruction
I do not have a contact, but I think they are the same people behind the PowerPC Notebook project [1]. Maybe you can contact them here [2]. [1] https://www.powerpc-notebook.org/about/ [2] https://www.powerpc-notebook.org/contacts/ F. Il 06/03/19 18:55, John Paul Adrian Glaubitz ha scritto: > On 3/5/19 3:57 PM, aggaz wrote: >> I understand your frustration, but I want you to know that I found a way >> to use my PowerMac G5 in these last two days. >> >> Basically I am using Debian Sid PPC64 with this extra repository: >> >> http://repo.powerprogress.org/ > It would be much better if the maintainers of this repository would > upstream their PowerPC-specific patches, either to Debian or directly > towards upstream. > > Most upstream bugs can be reported using Bugzilla (in case for Firefox) > or github issues. If someone has a patch, they just attach it to the > bug report. > > Do you have contact to the maintainers of the repository above? > > Adrian >
Re: PPC64 Illegal Instruction
On 3/5/19 3:57 PM, aggaz wrote: > I understand your frustration, but I want you to know that I found a way > to use my PowerMac G5 in these last two days. > > Basically I am using Debian Sid PPC64 with this extra repository: > > http://repo.powerprogress.org/ It would be much better if the maintainers of this repository would upstream their PowerPC-specific patches, either to Debian or directly towards upstream. Most upstream bugs can be reported using Bugzilla (in case for Firefox) or github issues. If someone has a patch, they just attach it to the bug report. Do you have contact to the maintainers of the repository above? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: PPC64 Illegal Instruction
Hi Noah! On 3/6/19 2:06 AM, Noah Wolfe wrote: > I fully understand that. I've got another PPC64 install now, so when I > have time, I can start trying to bug test everything and at least find > some leads as to why some packages do not want to function. Thanks. Best would be to report bugs: > https://www.debian.org/Bugs/Reporting > https://wiki.debian.org/reportbug For 32-bit PowerPC, use these tags: User: debian-powerpc@lists.debian.org Usertags: powerpc X-Debbugs-CC: debian-powerpclists.debian.org For 64-bit PowerPC, use: User: debian-powerpc@lists.debian.org Usertags: ppc64 X-Debbugs-CC: debian-powerpclists.debian.org (The mail addresses for ppc64 are correct, no typo). > Perhaps I can also get around to dealing with that Arctic Fox problem, > as can others, I hope... Well, at least one ppc64 you should be able to use the latest vanilla Firefox. For 32-bit PowerPC (powerpc), someone needs to work on the WASM-Support which is missing. We have Rust for 32-bit PowerPC, so that's not a problem. FWIW, I would be careful running forks of Firefox. Firefox is software which subject to a lot of security issues, so it needs a strong upstream which will fix vulnerabilities within a short time frame. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: News about Firefox for PowerPC
On 3/6/19 5:52 AM, Dennis Clarke wrote: > So would it be of value for me to fire up Debian buster or sid on a > PowerMac G5 here and do some testing? Not sure where you are getting > your Firefox from. Also is that the nightly builds? We're building stock Debian packages from unstable. Debian has a "firefox" and a "firefox-esr" package, both maintained by Mike Hommey who is also an engineer working at Mozilla. > I currently am > running 67.0a1 where about:buildconfig claims : > > https://hg.mozilla.org/mozilla-central/rev/78601cacfe69dc8659c3fe7cd3eb94366aa3d680 > > Is this similar to Firefox for PowerPC ? There is no "Firefox for PowerPC". Again, I'm not building packages manually for powerpc/ppc64. All packages you are getting for powerpc and ppc64 are automatically built from what's in the Debian archive for Debian unstable. Any bug fixes should therefore either go to the corresponding Debian package, or even better, forwarded upstream. Keeping fixes in local repositories specifically for powerpc or ppc64 is a very bad idea because those fixes will have to be carried around indefinitely. You will always want to upstream everything to make sure everyone gets those fixes. And if something crashes on SPARC, for example, there is a chance the bug also affects x86, just in a more subtle way. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: old OpenServers able to use Debian?
On Thu, Feb 14, 2019 at 07:28:08AM -0500, IT1 Stuart Blake Tener, USNR wrote: > I have some P710 or P720 (they are 4U rack mount) OpenServers from a number > of years ago that I believe are Power5. Is there a current (or older) > version of Debian that works for them? P7xx should be power7 or power7+ machines. The power5 and power6 machines were P5xx. They should certainly run ppc64 port. -- Len Sorensen
