Bug 754018 – =dev-php/composer-2.0.13 stabilization

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Tomáš Mózes 2020-11-11 12:31:53 UTC]

With composer-2 being out (and soon in portage), please let's stabilize composer-1 and it's deps. Thanks

[addCollapseLink(1, 1, 'Toggle comment display'); Comment 1 NATTkA bot 2021-03-01 18:08:59 UTC Comment hidden (obsolete)]

Unable to check for sanity:

> no match for package: dev-php/composer-1.10.15

[Comment 2 Joonas Niilola 2021-03-02 06:33:19 UTC]

1.10.20 then?

[Comment 3 Tomáš Mózes 2021-03-02 07:59:28 UTC]

(In reply to Joonas Niilola from comment #2)
> 1.10.20 then?

Sure, but seems like there is not much interest in it and I cannot call stabilization.

[Comment 4 Joonas Niilola 2021-03-02 08:39:54 UTC]

TBF I don't know why proxy-maint is still CCd for composer, doesn't look like we've done anything in 2+ years. Pinging whissi directly.

[Comment 5 Thomas Deutschmann (RETIRED) 2021-03-02 11:55:49 UTC]

I personally don't care much about stable but we can do that. However, most PHP packages should get marked for ALLARCHES first. I'll do that this week...

[Comment 6 Tomáš Mózes 2021-03-02 17:56:48 UTC]

(In reply to Thomas Deutschmann from comment #5)
> I personally don't care much about stable but we can do that. However, most
> PHP packages should get marked for ALLARCHES first. I'll do that this week...

Me neither for leaf packages, but this duplicates work since everybody wanting to install composer on stable arch needs to unmask these specific versions.

I don't run ~arch on my servers.

[addCollapseLink(7, 1, 'Toggle comment display'); Comment 7 NATTkA bot 2021-03-20 08:29:02 UTC Comment hidden (obsolete)]

Unable to check for sanity:

> no match for package: dev-php/composer-1.10.20

[addCollapseLink(8, 1, 'Toggle comment display'); Comment 8 NATTkA bot 2021-03-20 10:49:02 UTC Comment hidden (obsolete)]

Unable to check for sanity:

> no match for package: dev-php/semver-1.7.1

[Comment 9 Joonas Niilola 2021-03-20 10:56:21 UTC]

So during spring cleaning I've apparently dropped bunch of packages required to be stabilized in this bug. Now I'm pondering between reverting bunch of those commits, or stabilizing composer-2 instead. What do you think? Either way I can do the "cleanup work". 

I personally vote for stabilizing composer-2.

[Comment 10 Joonas Niilola 2021-03-20 13:18:40 UTC]

Well semver was reverted and everything else seems to be present. No idea how to re-trigger nattkas' sanity check, but this stable request should be good to go again.

[addCollapseLink(11, 1, 'Toggle comment display'); Comment 11 NATTkA bot 2021-04-27 14:32:30 UTC Comment hidden (obsolete)]

Unable to check for sanity:

> no match for package: dev-php/composer-1.10.20

[Comment 12 Thomas Deutschmann (RETIRED) 2021-05-04 19:42:59 UTC]

Let's go with =dev-php/composer-2.0.13!

[Comment 13 Agostino Sarubbo 2021-05-06 06:55:20 UTC]

amd64 stable

[Comment 14 Agostino Sarubbo 2021-05-10 06:59:18 UTC]

x86 stable. Closing.