All of lore.kernel.org
 help / color / mirror / Atom feed
* Github tracker for PowerPC issues
@ 2026-01-21 20:43 John Paul Adrian Glaubitz
  2026-01-22  6:46 ` Trupti
  0 siblings, 1 reply; 5+ messages in thread
From: John Paul Adrian Glaubitz @ 2026-01-21 20:43 UTC (permalink / raw)
  To: debian-powerpc; +Cc: linuxppc-dev, gentoo-powerpc

Hi,

I just noticed that similar to the issue tracker I created for SPARC [1], there is an
issue tracker for PowerPC [2].

The idea is to track any issues specific to a certain architecture in a central, prominent
location so these become visible to any distribution maintainer and PowerPC upstream developer.

Thus, if you spot a bug affecting PowerPC, please report it in [2].

Thanks,
Adrian

> [1] https://github.com/sparclinux/issues/issues
> [2] https://github.com/linuxppc/issues/issues

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Github tracker for PowerPC issues
  2026-01-21 20:43 Github tracker for PowerPC issues John Paul Adrian Glaubitz
@ 2026-01-22  6:46 ` Trupti
  2026-01-22  6:55   ` John Paul Adrian Glaubitz
  0 siblings, 1 reply; 5+ messages in thread
From: Trupti @ 2026-01-22  6:46 UTC (permalink / raw)
  To: John Paul Adrian Glaubitz; +Cc: debian-powerpc, linuxppc-dev, gentoo-powerpc


Hello Adrian,


On 2026-01-22 02:13, John Paul Adrian Glaubitz wrote:
> Hi,
> 
> I just noticed that similar to the issue tracker I created for SPARC
> [1], there is an
> issue tracker for PowerPC [2].
> 
> The idea is to track any issues specific to a certain architecture in
> a central, prominent
> location so these become visible to any distribution maintainer and
> PowerPC upstream developer.
> 
> Thus, if you spot a bug affecting PowerPC, please report it in [2].
> 
> Thanks,
> Adrian
> 
>> [1] https://github.com/sparclinux/issues/issues
>> [2] https://github.com/linuxppc/issues/issues

Thanks for sharing this information. However, the issues at 
https://github.com/linuxppc/issues/issues are mostly related to the core 
Linux kernel and toolchain.

For Debian-specific work, we need a separate issue tracker: 
https://github.com/linuxppc/Debian/issues, where Debian-related issues 
can be reported.

I will share the link to this issue tracker shortly.


Thanks,
Trupti


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Github tracker for PowerPC issues
  2026-01-22  6:46 ` Trupti
@ 2026-01-22  6:55   ` John Paul Adrian Glaubitz
  2026-01-22  7:14     ` Trupti
  0 siblings, 1 reply; 5+ messages in thread
From: John Paul Adrian Glaubitz @ 2026-01-22  6:55 UTC (permalink / raw)
  To: Trupti; +Cc: debian-powerpc, linuxppc-dev, gentoo-powerpc



> On Jan 22, 2026, at 7:47 AM, Trupti <trupti@linux.ibm.com> wrote:
> 
> Thanks for sharing this information. However, the issues at https://github.com/linuxppc/issues/issues are mostly related to the core Linux kernel and toolchain.
> 
> For Debian-specific work, we need a separate issue tracker: https://github.com/linuxppc/Debian/issues, where Debian-related issues can be reported.

But I’m not talking about Debian-specific issues. Tracking Debian-specific issues happens in Debian.

When I report an issue in the GHC Haskell compiler on PowerPC, it belongs in the existing tracker. Doesn’t it?

Adrian


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Github tracker for PowerPC issues
  2026-01-22  6:55   ` John Paul Adrian Glaubitz
@ 2026-01-22  7:14     ` Trupti
  2026-01-22  7:41       ` John Paul Adrian Glaubitz
  0 siblings, 1 reply; 5+ messages in thread
From: Trupti @ 2026-01-22  7:14 UTC (permalink / raw)
  To: John Paul Adrian Glaubitz; +Cc: debian-powerpc, linuxppc-dev, gentoo-powerpc

On 2026-01-22 12:25, John Paul Adrian Glaubitz wrote:
> But I’m not talking about Debian-specific issues. Tracking
> Debian-specific issues happens in Debian.
> 
> When I report an issue in the GHC Haskell compiler on PowerPC, it
> belongs in the existing tracker. Doesn’t it?
> 
> Adrian

That makes sense, thanks for clarifying. I agree, we can use the 
existing issue tracker for this.


Thanks,
Trupti


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Github tracker for PowerPC issues
  2026-01-22  7:14     ` Trupti
@ 2026-01-22  7:41       ` John Paul Adrian Glaubitz
  0 siblings, 0 replies; 5+ messages in thread
From: John Paul Adrian Glaubitz @ 2026-01-22  7:41 UTC (permalink / raw)
  To: Trupti; +Cc: debian-powerpc, linuxppc-dev, gentoo-powerpc

Hi Trupti,

On Thu, 2026-01-22 at 12:44 +0530, Trupti wrote:
> On 2026-01-22 12:25, John Paul Adrian Glaubitz wrote:
> > But I’m not talking about Debian-specific issues. Tracking
> > Debian-specific issues happens in Debian.
> > 
> > When I report an issue in the GHC Haskell compiler on PowerPC, it
> > belongs in the existing tracker. Doesn’t it?
> > 
> > Adrian
> 
> That makes sense, thanks for clarifying. I agree, we can use the 
> existing issue tracker for this.

Thank you! Debian-specific issue will be reported in Debian.

I'm just tracking issues there that affect PowerPC in general.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-01-22 21:50 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-21 20:43 Github tracker for PowerPC issues John Paul Adrian Glaubitz
2026-01-22  6:46 ` Trupti
2026-01-22  6:55   ` John Paul Adrian Glaubitz
2026-01-22  7:14     ` Trupti
2026-01-22  7:41       ` John Paul Adrian Glaubitz

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.