Re: Bug#732282: stop building java for sparc, sparc64, s390, kfreebsd-any
Am 16.12.2013 11:34, schrieb Matthias Klose: Package: java-common Version: 0.50 Severity: serious Tags: jessie, sid openjdk-7 currently ftbfs on sparc, sparc64, s390, kfreebsd-any. So please either remove the default-* packages on these archs, or fall back to gcj. - the hotspot port for linux sparc isn't maintained anymore by upstream. If a porter is interested, maybe investigate how to build the zero vm on these architectures. - s390 needs an update of the s390 debian specific patch. Not working on this myself. - the debian kfreebsd patches need an update. I don't think it's feasible to burden the openjdk maintainers or the security team with patch maintenance. I understand that the bsd support is found upstream in openjdk-8, so maybe try that again for the next upstream version. ia64, sparc, sparc64, kfreebsd-i386 and kfreebsd-amd64 are now demoted to gcj on the VCS. Had to demote ia64 too, and don't want to investigate anymore. I'll upload java-common later this week. The good news is that arm64, mips, mipsel, powerpcspe, ppc64el and x32 are now promoted to use openjdk-7. Matthias -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d24e65.5000...@debian.org
Re: How to get a new palo source package into unstable?
Hello Helge! On Sat, Jan 11, 2014 at 10:37:52PM +0100, Helge Deller wrote: as you might have noticed, we did huge progress on the HPPA (PA-RISC) port: http://buildd.debian-ports.org/stats/ Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). In order to be able to boot parisc machines, the hppa port needs the palo debian package. PALO is the PA-RISC boot loader and a boot-loader-image generator, similar to lilo on i386 or silo on sparc. Or aboot on the Alpha machines. I've continued to maintain and further develop palo. The new palo git repository is now at: git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git and the source should compile and run on all plattforms. A simple checkout and dpkg-buildpackage should work. Thank you very much for doing this (and the hard work of bringing the buildds back to life). Even though I currently don't own a PA-RISC machine, I'm very glad that someone took care of it, such that owners of these machines can still use it with a current Debian release. Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. What is the usual process to get a new/old package back into debian unstable? Maybe someone of you who has a debian developer rights is willing to upload the source package? I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? Cheers, Adrian [1] http://mentors.debian.net/ [2] http://buildd.debian-ports.org/status/package.php?p=radeontopsuite=sid -- .''`. 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 -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140112163248.ga10...@physik.fu-berlin.de
Re: gcc-4.9 uploaded to experimental
On Fri, Jan 10, 2014 at 7:23 PM, Matthias Klose d...@debian.org wrote: gcc-4.9 is uploaded to experimental, asking the porters to watch for build failures and corresponding patches. See https://buildd.debian.org/status/package.php?p=gcc-4.9suite=experimental These are already fixed in the vcs. - fixed the gospec.c ftbfs on archs without ld.gold - fixed the g++ b-d on armel/armhf The build log on mips64el can be found from: http://mips64el.debian.net/attempted/gcc-4.9-mips64el.log.xz Matthias -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52cfd843.1010...@debian.org -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKcpw6VzmezVP+6LFsb7Afs=xmhs9e295ybriksp0sn7aa0...@mail.gmail.com
Re: How to get a new palo source package into unstable?
Hi Adrian, On 01/12/2014 05:32 PM, John Paul Adrian Glaubitz wrote: On Sat, Jan 11, 2014 at 10:37:52PM +0100, Helge Deller wrote: as you might have noticed, we did huge progress on the HPPA (PA-RISC) port: http://buildd.debian-ports.org/stats/ Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). Good thing is, that those machines got pretty cheap now. A Dualcore-C8000 workstation is available on ebay for 100 EUR. In order to be able to boot parisc machines, the hppa port needs the palo debian package. PALO is the PA-RISC boot loader and a boot-loader-image generator, similar to lilo on i386 or silo on sparc. Or aboot on the Alpha machines. I've continued to maintain and further develop palo. The new palo git repository is now at: git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git and the source should compile and run on all plattforms. A simple checkout and dpkg-buildpackage should work. Thank you very much for doing this (and the hard work of bringing the buildds back to life). Even though I currently don't own a PA-RISC machine, I'm very glad that someone took care of it, such that owners of these machines can still use it with a current Debian release. Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. What is the usual process to get a new/old package back into debian unstable? Maybe someone of you who has a debian developer rights is willing to upload the source package? I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. Thanks! AFAIK the bootloader is the only package which is parisc specific. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. I uploaded it, and CC'ed you on the request. http://mentors.debian.net/package/palo The info at top of the website is the latest package with most warnings fixed. It would be nice if you could help me (off-list) further on that. Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? Sure, I'll send you login details off-list. If other people here on the list want access, please let me know. PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. I can reschedule a rebuild of radeontop for you, or you can just build it yourself on the machine for which I send you a login. Just let me know. Thanks! Helge -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d30ad2.8030...@gmx.de
Re: How to get a new palo source package into unstable?
Hi Helge! On 01/12/2014 10:36 PM, Helge Deller wrote: Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). Good thing is, that those machines got pretty cheap now. A Dualcore-C8000 workstation is available on ebay for 100 EUR. If just had enough room. There are already too many Amigas taking up my space :). Still, I like to support the port as much as I can. I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. Thanks! AFAIK the bootloader is the only package which is parisc specific. Ok, good to know. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. I uploaded it, and CC'ed you on the request. http://mentors.debian.net/package/palo The info at top of the website is the latest package with most warnings fixed. It would be nice if you could help me (off-list) further on that. Will do! I'll answer your separate mail later! Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? Sure, I'll send you login details off-list. If other people here on the list want access, please let me know. Thanks, got them. Will change the password and install my SSH key ASAP. We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. Ah, glad to hear it has been fixed. Then there's nothing I am worrying about. Are you working together with Ingo Juergensmann to update the buildd status information on buildd.net? I can reschedule a rebuild of radeontop for you, or you can just build it yourself on the machine for which I send you a login. Just let me know. Don't worry about radeontop. I just picked that package as an example to check whether the build logs are still missing or not. This is one of my own packages and the last upload was just done a few weeks ago, so I thought I might check this one to see whether the problem has already been addressed. But when you say the logs are properly uploaded now, I'm happy. So, please don't reschedule the package, it will updated in the very near future anyway. 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 -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d33683.2020...@physik.fu-berlin.de