Re: Bug#730258: please add arch-specific BTS tags
On 23/11/2013 22:53, Don Armstrong wrote: > kfreebsd-amd64 > kfreebsd-i386 Most of the bugs affecting one of these also affect the other. I think it makes sense to add a single tag to cover both. -- Robert Millan -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52915a2a.8010...@debian.org
Re: Bug#730258: please add arch-specific BTS tags
On 11/23/13 4:35 PM, John Paul Adrian Glaubitz wrote: On 11/24/2013 12:22 AM, Helge Deller wrote: On 11/24/2013 12:21 AM, John Paul Adrian Glaubitz wrote: On 11/23/2013 11:51 PM, Helge Deller wrote: Please add "hppa" Assuming that you are one of the hppa guys, how is the port doing? Any chance that the buildds will be up and running again anytime soon? Yes, think so. I'm working on that just right now... Very cool! Hope you guys will soon be where we already are with the m68k port :). Crossing my fingers! It's been sad to see the number of up-to-date packages in hppa dropping over the time. Keep us updated! Adrian [Sorry, meant to cc. this to the list] I'm currently working with Helge Deller and John David Anglin on kernel testing with one of my machines (64 Bit SMP - HP Visualize J6750 workstation). I'm not one of the official developers, but willing to donate time and machine resources to keep the port going. We've had some pretty interesting breakthroughs recently, regarding the 64 bit SMP kernel. Dave L. -- -- Dave Land Land Computer Service xmecha...@landcomp.net -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52915037.3020...@landcomp.net
Re: Bug#730258: please add arch-specific BTS tags
On Sun, 24 Nov 2013, Paul Wise wrote: > On Sun, Nov 24, 2013 at 5:53 AM, Don Armstrong wrote: > > > These are the list of ports that I see: > > I would strongly suggest not hardcoding this list and instead > harvesting the Architecture fields of the Release files for oldstable > -> experimental on ftp.d.o, ftp.d-p.o and maybe archive.d.o. > > We have made this mistake and similar ones (usually hardcoding release > codenames) in the QA infrastructure and it has bitten us hard in the > past. Lets not make that mistake here. The list will be hardcoded, because it has to live in the Debbugs configuration file, and tags shouldn't disappear just because debian-ports or debian has dropped an architecture. That said, I was planning on setting it up so that I at least was notified when the set from cannonical location changed. > The release files are the closest to a canonical list of ports. There > are other ports out there not maintained on d-p.o (like the Interix or > Solaris ones for example) but I don't think we need to bother about > those until they move closer to Debian. OK. -- Don Armstrong http://www.donarmstrong.com "There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." -- Jeremy S. Anderson -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131124004708.gc7...@teltox.donarmstrong.com
Re: Bug#730258: please add arch-specific BTS tags
On 11/24/2013 01:20 AM, Thorsten Glaser wrote: > John Paul Adrian Glaubitz dixit: >> So, the buildds are already up and running? Shouldn't they be showing >> up on buildd.debian-ports.org [1]? > > I think I saw buildd uploads for hppa on incoming.d.o this week. Indeed: > http://incoming.debian-ports.org/buildd/packages/unstable/main/ Very cool! 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-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/529148de.8070...@physik.fu-berlin.de
Re: Bug#730258: please add arch-specific BTS tags
John Paul Adrian Glaubitz dixit: >On 11/24/2013 12:47 AM, John David Anglin wrote: >> It should be going up now. > >So, the buildds are already up and running? Shouldn't they be showing >up on buildd.debian-ports.org [1]? I think I saw buildd uploads for hppa on incoming.d.o this week. Paul Wise dixit: >are other ports out there not maintained on d-p.o (like the Interix or Huh, the Interix port is not vaporware? Interesting… bye, //mirabilos -- cool ein Ada Lovelace Google-Doodle. aber zum 197. Geburtstag? Hätten die nicht noch 3 Jahre warten können? bis dahin gibts google nicht mehr ja, könnte man meinen. wahrscheinlich ist der angekündigte welt- untergang aus dem maya-kalender die globale abschaltung von google ☺ und darum müssen die die doodles vorher noch raushauen -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1311240019570.12...@herc.mirbsd.org
Re: Bug#730258: please add arch-specific BTS tags
On Sun, Nov 24, 2013 at 5:53 AM, Don Armstrong wrote: > These are the list of ports that I see: I would strongly suggest not hardcoding this list and instead harvesting the Architecture fields of the Release files for oldstable -> experimental on ftp.d.o, ftp.d-p.o and maybe archive.d.o. We have made this mistake and similar ones (usually hardcoding release codenames) in the QA infrastructure and it has bitten us hard in the past. Lets not make that mistake here. The release files are the closest to a canonical list of ports. There are other ports out there not maintained on d-p.o (like the Interix or Solaris ones for example) but I don't think we need to bother about those until they move closer to Debian. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6evh+_xumxvgd5w8a8kd1laxgggylnmuxstbllu4ou...@mail.gmail.com
Re: Bug#730258: please add arch-specific BTS tags
On 23-Nov-13, at 6:35 PM, John Paul Adrian Glaubitz wrote: Crossing my fingers! It's been sad to see the number of up-to-date packages in hppa dropping over the time. It should be going up now. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp50b10a8a25fb6dfae41df297...@phx.gbl
Re: Bug#730258: please add arch-specific BTS tags
On 11/24/2013 12:47 AM, John David Anglin wrote: > On 23-Nov-13, at 6:35 PM, John Paul Adrian Glaubitz wrote: > >> Crossing my fingers! It's been sad to see the number of up-to-date >> packages in hppa dropping over the time. > > It should be going up now. So, the buildds are already up and running? Shouldn't they be showing up on buildd.debian-ports.org [1]? Adrian > [1] http://buildd.debian-ports.org/status/architecture.php?a=hppa&suite=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-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52913f09.6080...@physik.fu-berlin.de
Re: Bug#730258: please add arch-specific BTS tags
On 11/24/2013 12:22 AM, Helge Deller wrote: > On 11/24/2013 12:21 AM, John Paul Adrian Glaubitz wrote: >> On 11/23/2013 11:51 PM, Helge Deller wrote: >>> Please add "hppa" >> >> Assuming that you are one of the hppa guys, how is the port doing? Any >> chance that the buildds will be up and running again anytime soon? > > Yes, think so. > I'm working on that just right now... Very cool! Hope you guys will soon be where we already are with the m68k port :). Crossing my fingers! It's been sad to see the number of up-to-date packages in hppa dropping over the time. Keep us updated! 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-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52913bad.9000...@physik.fu-berlin.de
Re: Bug#730258: please add arch-specific BTS tags
On 11/24/2013 12:21 AM, John Paul Adrian Glaubitz wrote: > On 11/23/2013 11:51 PM, Helge Deller wrote: >> Please add "hppa" > > Assuming that you are one of the hppa guys, how is the port doing? Any > chance that the buildds will be up and running again anytime soon? Yes, think so. I'm working on that just right now... Helge -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/529138b5.5050...@gmx.de
Re: Bug#730258: please add arch-specific BTS tags
On 11/23/2013 11:51 PM, Helge Deller wrote: >> What else am I missing? > > Please add "hppa" Assuming that you are one of the hppa guys, how is the port doing? Any chance that the buildds will be up and running again anytime soon? Cheers, 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-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52913875.3080...@physik.fu-berlin.de
Re: Bug#730258: please add arch-specific BTS tags
On 11/23/2013 10:53 PM, Don Armstrong wrote: > On Sat, 23 Nov 2013, Ivo De Decker wrote: >> During a discussion about architecture qualification, the release team >> concluded that it would be interesting to have a better way to track >> architecture-specific bugs. It would be nice to have BTS tags for each >> architecture that is currently in the archive. It might also make >> sense to have tags for the architectures on debian-ports, to be able >> to filter issues about these easily. > > This sounds reasonable; are only tags required, or do we need more > infrastructure than that? > > These are the list of ports that I see: > > amd64 > armel > armhf > hurd-i386 > i386 > ia64 > kfreebsd-amd64 > kfreebsd-i386 > mips > mipsel > powerpc > s390x > sparc > avr32 > sh > > What else am I missing? Please add "hppa" Helge -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5291317e.3020...@gmx.de
Re: Bug#730258: please add arch-specific BTS tags
Don Armstrong dixit: >These are the list of ports that I see: Question is, where do you see them? >avr32 This one got removed even from debian-ports for several reasons. >sh I think there's sh4 but not just sh. Looking at the buildd pages is probably the best idea. Combining https://buildd.debian.org/status/package.php?p=mksh and http://buildd.debian-ports.org/status/package.php?p=mksh (and ignoring s390 removal) gives us this list: alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc powerpcspe ppc64 s390x sh4 sparc sparc64 x32 This keeps hppa, which I’ve seen have some activity recently. >has another; I'd like to reference a canonical location for ports >(perhaps maintained by debian-ports or similar) so I don't have to Even the list on debian-ports is out of date wrt. debian-ports architectures – it misses x32 and arm64, for example. Sorry about that. There seems to be nobody keeping this list up to date so looking at the buildds seems best. Another option is of course to look at what dpkg supports, unearthing things like armeb, arm, avr32, sh3, etc. bye, //mirabilos -- „Also irgendwie hast du IMMER recht. Hier zuckelte gerade ein Triebwagen mit der Aufschrift "Ostdeutsche Eisenbahn" durch Wuppertal. Ich glaubs machmal nicht…“ -- Natureshadow, per SMS „Hilf mir mal grad beim Denken“ -- Natureshadow, IRL, 2x -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1311232243030.12...@herc.mirbsd.org
Re: Bug#730258: please add arch-specific BTS tags
On 23 November 2013 21:53, Don Armstrong wrote: > On Sat, 23 Nov 2013, Ivo De Decker wrote: >> During a discussion about architecture qualification, the release team >> concluded that it would be interesting to have a better way to track >> architecture-specific bugs. It would be nice to have BTS tags for each >> architecture that is currently in the archive. It might also make >> sense to have tags for the architectures on debian-ports, to be able >> to filter issues about these easily. > > This sounds reasonable; are only tags required, or do we need more > infrastructure than that? > > These are the list of ports that I see: > > amd64 > armel > armhf > hurd-i386 > i386 > ia64 > kfreebsd-amd64 > kfreebsd-i386 > mips > mipsel > powerpc > s390x > sparc > avr32 > sh > > What else am I missing? [I note that > http://www.debian.org/ports/#portlist-released seems to have a > reasonable list of ports, and > http://anonscm.debian.org/viewvc/webwml/webwml/english/releases/sid/archive.data?view=markup > has another; I'd like to reference a canonical location for ports > (perhaps maintained by debian-ports or similar) so I don't have to > figure out for myself which ports need a tag and what that tag should > be, and which ports are just duplicates of other ports, and therefore > don't need a tag. > There are 484 reports usertagged "debian-...@lists.debian.org arm64". Please consider including "arm64" tag. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUg0yh60VEh50NCbYK+nfs65F5x3jU6MFL+WEdqT=qz...@mail.gmail.com
Re: Bug#730258: please add arch-specific BTS tags
On Sat, 23 Nov 2013, Ivo De Decker wrote: > During a discussion about architecture qualification, the release team > concluded that it would be interesting to have a better way to track > architecture-specific bugs. It would be nice to have BTS tags for each > architecture that is currently in the archive. It might also make > sense to have tags for the architectures on debian-ports, to be able > to filter issues about these easily. This sounds reasonable; are only tags required, or do we need more infrastructure than that? These are the list of ports that I see: amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc avr32 sh What else am I missing? [I note that http://www.debian.org/ports/#portlist-released seems to have a reasonable list of ports, and http://anonscm.debian.org/viewvc/webwml/webwml/english/releases/sid/archive.data?view=markup has another; I'd like to reference a canonical location for ports (perhaps maintained by debian-ports or similar) so I don't have to figure out for myself which ports need a tag and what that tag should be, and which ports are just duplicates of other ports, and therefore don't need a tag. -- Don Armstrong http://www.donarmstrong.com "There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." -- Jeremy S. Anderson -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131123215315.gb7...@teltox.donarmstrong.com
Re: Switch default GCC to 4.8 on s390x
On Sat, Nov 23, 2013 at 03:39:52PM +0100, Matthias Klose wrote: > Am 23.11.2013 13:52, schrieb Aurelien Jarno: > > On Sat, Nov 23, 2013 at 10:44:04AM +0100, Matthias Klose wrote: > >> Am 23.11.2013 03:33, schrieb Aurelien Jarno: > >>> On Mon, Nov 18, 2013 at 09:09:18AM +0100, Matthias Klose wrote: > Am 12.11.2013 15:40, schrieb Aurelien Jarno: > > Hi all, > > > > The s390x architecture is still using GCC 4.6 as the default > > compiler, while most other architectures have already switched to > > GCC 4.8. It starts to cause problem for building packages: some > > packages need C11 features to be compiled, while some others assume > > the default compiler is already GCC 4.8 (in that case they are > > actually buggy). It would also help having the same default version > > of GCC than for GCJ, GDC or GFORTRAN. > > > > I therefore propose to switch the default compiler on s390x to GCC > > 4.8 by default. It is already used to build the kernel without any > > known issue. > > > > Any comments or opinion on that? > > Is this a commitment from Philipp, Bastian or your side to monitor > for s390x specific toolchain issues, forward these upstream and feed > these back into Debian? > > >>> > >>> It is a commitment from my side, although s390x is well tested upstream > >>> and there is therefore not a lot to do. > >> > >> please update debian/README.Debian in gcc-4.8. > >> > > > > Done. That said I still don't understand why only a limited list of > > architectures have to do that. I do not believe that architectures not > > listed there are actually better supported in Debian. > > It's the other way around. Every architecture should have an entry. But maybe > it is easier to mention which architectures currently don't have such entries, > namely sparc, s390, ia64, powerpc, ppc64. s390 is dead and is still only available for squeeze and wheezy, so it doesn't matter for jessie and sid. > x86 should be waived. we do have active contributors for kfreebsd, the hurd, > m68k, alpha, powerpcspe, mips64, hppa at least. If they have active contributors, I think they should also be noted there, otherwise this file is more than useless. Or we should remove mips and s390x entries. > arm* is missing here, but it > is usually taken care of by myself. Well then why you don't add yourself there? Note that they are a few worrying bugs on armel like #628063, #697521, #727621 that have not been forwarded upstream yet. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131123145825.gc20...@hall.aurel32.net
Re: Switch default GCC to 4.8 on s390x
Am 23.11.2013 13:52, schrieb Aurelien Jarno: > On Sat, Nov 23, 2013 at 10:44:04AM +0100, Matthias Klose wrote: >> Am 23.11.2013 03:33, schrieb Aurelien Jarno: >>> On Mon, Nov 18, 2013 at 09:09:18AM +0100, Matthias Klose wrote: Am 12.11.2013 15:40, schrieb Aurelien Jarno: > Hi all, > > The s390x architecture is still using GCC 4.6 as the default > compiler, while most other architectures have already switched to > GCC 4.8. It starts to cause problem for building packages: some > packages need C11 features to be compiled, while some others assume > the default compiler is already GCC 4.8 (in that case they are > actually buggy). It would also help having the same default version > of GCC than for GCJ, GDC or GFORTRAN. > > I therefore propose to switch the default compiler on s390x to GCC > 4.8 by default. It is already used to build the kernel without any > known issue. > > Any comments or opinion on that? Is this a commitment from Philipp, Bastian or your side to monitor for s390x specific toolchain issues, forward these upstream and feed these back into Debian? >>> >>> It is a commitment from my side, although s390x is well tested upstream >>> and there is therefore not a lot to do. >> >> please update debian/README.Debian in gcc-4.8. >> > > Done. That said I still don't understand why only a limited list of > architectures have to do that. I do not believe that architectures not > listed there are actually better supported in Debian. It's the other way around. Every architecture should have an entry. But maybe it is easier to mention which architectures currently don't have such entries, namely sparc, s390, ia64, powerpc, ppc64. x86 should be waived. we do have active contributors for kfreebsd, the hurd, m68k, alpha, powerpcspe, mips64, hppa at least. arm* is missing here, but it is usually taken care of by myself. Matthias -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5290be38.8000...@debian.org
Re: Switch default GCC to 4.8 on s390x
On Sat, Nov 23, 2013 at 10:44:04AM +0100, Matthias Klose wrote: > Am 23.11.2013 03:33, schrieb Aurelien Jarno: > > On Mon, Nov 18, 2013 at 09:09:18AM +0100, Matthias Klose wrote: > >> Am 12.11.2013 15:40, schrieb Aurelien Jarno: > >>> Hi all, > >>> > >>> The s390x architecture is still using GCC 4.6 as the default compiler, > >>> while most other architectures have already switched to GCC 4.8. It > >>> starts to cause problem for building packages: some packages need C11 > >>> features to be compiled, while some others assume the default compiler > >>> is already GCC 4.8 (in that case they are actually buggy). It would > >>> also help having the same default version of GCC than for GCJ, GDC or > >>> GFORTRAN. > >>> > >>> I therefore propose to switch the default compiler on s390x to GCC 4.8 > >>> by default. It is already used to build the kernel without any known > >>> issue. > >>> > >>> Any comments or opinion on that? > >> > >> Is this a commitment from Philipp, Bastian or your side to monitor for > >> s390x specific toolchain issues, forward these upstream and feed these > >> back into Debian? > >> > > > > It is a commitment from my side, although s390x is well tested upstream and > > there is therefore not a lot to do. > > please update debian/README.Debian in gcc-4.8. > Done. That said I still don't understand why only a limited list of architectures have to do that. I do not believe that architectures not listed there are actually better supported in Debian. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net signature.asc Description: Digital signature
Re: Switch default GCC to 4.8 on s390x
Am 23.11.2013 03:33, schrieb Aurelien Jarno: > On Mon, Nov 18, 2013 at 09:09:18AM +0100, Matthias Klose wrote: >> Am 12.11.2013 15:40, schrieb Aurelien Jarno: >>> Hi all, >>> >>> The s390x architecture is still using GCC 4.6 as the default compiler, >>> while most other architectures have already switched to GCC 4.8. It >>> starts to cause problem for building packages: some packages need C11 >>> features to be compiled, while some others assume the default compiler >>> is already GCC 4.8 (in that case they are actually buggy). It would >>> also help having the same default version of GCC than for GCJ, GDC or >>> GFORTRAN. >>> >>> I therefore propose to switch the default compiler on s390x to GCC 4.8 >>> by default. It is already used to build the kernel without any known >>> issue. >>> >>> Any comments or opinion on that? >> >> Is this a commitment from Philipp, Bastian or your side to monitor for >> s390x specific toolchain issues, forward these upstream and feed these >> back into Debian? >> > > It is a commitment from my side, although s390x is well tested upstream and > there is therefore not a lot to do. please update debian/README.Debian in gcc-4.8. -- To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/529078e4.2010...@debian.org