Bug 393811 – Please stabilize =x11-terms/aterm-1.0.1-r2

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Paweł Hajdan, Jr. (RETIRED) 2011-12-08 23:51:38 UTC]

Is it OK to stabilize =x11-terms/aterm-1.0.1-r2 ?

If so, please CC arches and add STABLEREQ keyword.

Stabilization of this package has been repoman-checked on the following arches: x86, amd64

[Comment 1 Paweł Hajdan, Jr. (RETIRED) 2011-12-16 10:20:04 UTC]

Maintainer timeout, arches go ahead.

[Comment 2 Agostino Sarubbo 2011-12-16 14:01:01 UTC]

This package seems dead upstream. I'll mark stable anyway, but keep in mind.

amd64 stable

[Comment 3 Myckel Habets 2011-12-17 16:08:19 UTC]

Builds and runs fine on x86. Please mark stable for x86.

[Comment 4 Paweł Hajdan, Jr. (RETIRED) 2011-12-18 20:09:20 UTC]

x86 stable, closing

[Comment 5 Michael Palimaka (kensington) 2012-07-11 15:00:36 UTC]

Missing archs, reopening.

[Comment 6 Anthony Basile 2012-07-22 17:14:44 UTC]

ppc is fine and I will mark it stable in a sec.

ppc64 fails to start with the following error message:

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  20 (X_GetProperty)
  Resource id in failed request:  0x0
  Serial number of failed request:  26
  Current serial number in output stream:  26

I don't know aterm well enough to interpret that.

[Comment 7 Pacho Ramos 2012-07-22 17:22:40 UTC]

(In reply to comment #6)
> ppc is fine and I will mark it stable in a sec.
> 
> ppc64 fails to start with the following error message:
> 
> X Error of failed request:  BadWindow (invalid Window parameter)
>   Major opcode of failed request:  20 (X_GetProperty)
>   Resource id in failed request:  0x0
>   Serial number of failed request:  26
>   Current serial number in output stream:  26
> 
> I don't know aterm well enough to interpret that.

I would simply drop ppc64 keywords for all aterm versions then

[Comment 8 Anthony Basile 2012-07-22 19:08:21 UTC]

(In reply to comment #7)
> (In reply to comment #6)
> > ppc is fine and I will mark it stable in a sec.
> > 
> > ppc64 fails to start with the following error message:
> > 
> > X Error of failed request:  BadWindow (invalid Window parameter)
> >   Major opcode of failed request:  20 (X_GetProperty)
> >   Resource id in failed request:  0x0
> >   Serial number of failed request:  26
> >   Current serial number in output stream:  26
> > 
> > I don't know aterm well enough to interpret that.
> 
> I would simply drop ppc64 keywords for all aterm versions then

Not sure, -r1 was marked stable and yet I get the same for it as -r2.  Lets see if anyone else with a ppc64 reproduced this error.

[Comment 9 Jeroen Roovers (RETIRED) 2012-08-01 23:40:08 UTC]

Stable for HPPA.

[Comment 10 Brent Baude (RETIRED) 2012-08-06 21:11:01 UTC]

ppc64 done

[Comment 11 Raúl Porcel (RETIRED) 2012-08-26 18:36:38 UTC]

alpha/ia64/sparc stable