Bug 32341

Summary:	yarnpkg wasn't moved to updates along with nodejs
Product:	Mageia	Reporter:	Marja Van Waes <marja11>
Component:	RPM Packages	Assignee:	QA Team <qa-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	Normal	CC:	chb0, davidwhodgins, fri, herman.viaene, qa-bugs, security, sysadmin-bugs
Version:	9	Keywords:	validated_update
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA9-64-OK
Source RPM:	yarnpkg-1.22.19-11.mga9.src.rpm	CVE:
Status comment:
Bug Depends on:	32176
Bug Blocks:	28809, 32309

Description Marja Van Waes 2023-09-28 18:47:28 CEST

+++ This bug was initially created as a clone of Bug #32176 +++


When nodejs was pushed for bug 32176, yarnpkg was left behind in testing.

In bug32176,comment25 Christian Barranco says:

As the advisory might have not been clear enough for yarnpkg, here is an update:

ADVISORY NOTICE PROPOSAL (UPDATE)
========================
yarnpkg package rebuilt with npm 9.6.7


Description
yarpnkg package rebuilt with npm 9.6.7, after updating to nodejs 18.17.1

           
References
https://bugs.mageia.org/show_bug.cgi?id=32176


SRPMS
9/core
yarnpkg-1.22.19-13.mga9.src.rpm



PROVIDED PACKAGES:
yarnpkg-1.22.19-13.mga9

    
PACKAGES FOR QA TESTING
=======================
MGA9
yarnpkg-1.22.19-13.mga9.noarch.rpm

==========================================================

As this package has already been well tested along with nodejs, I leave the validated_update keyword.

Comment 1 David Walser 2023-09-28 18:58:34 CEST

Bug 32176 was reopened so that a sysadmin can move that package.

*** This bug has been marked as a duplicate of bug 32176 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED

Comment 2 Marja Van Waes 2023-09-28 19:14:58 CEST

(In reply to David Walser from comment #1)
> Bug 32176 was reopened so that a sysadmin can move that package.
> 
> *** This bug has been marked as a duplicate of bug 32176 ***


I uploaded a new advisory for this report and won't try to fix the advisory for 32176

Feel free to remove 32341.adv and adjust 32176.adv

Keywords: (none) => advisory
Whiteboard: (none) => MGA8TOO MGA8-64-OK MGA9-64-OK

Comment 3 Marja Van Waes 2023-10-01 14:46:17 CEST

If this report needs to be reopened, then the advisory will need to be uploaded to svn again. I removed it after this report was closed as invalid

Keywords: advisory => (none)

Comment 4 christian barranco 2023-10-01 15:09:24 CEST

Hi. Not sure what to do anymore. 
Previous nodejs bug report https://bugs.mageia.org/show_bug.cgi?id=32176 has not been enough to get yarnpkg-1.22.19-13.mga9.noarch.rpm pushed to updates, despite it was listed on the advisory.

It is still in updates_testing.
What should I do?

Thanks

Comment 5 christian barranco 2023-10-01 15:12:39 CEST

Apologies Marja; just saw https://bugs.mageia.org/show_bug.cgi?id=32176#c30
It is being sorted out there.

Comment 6 Marja Van Waes 2023-10-01 15:33:32 CEST

Thanks Christian, I'll wait to see what happens

Comment 7 christian barranco 2023-11-27 12:34:40 CET

MGA8 doesn’t have yarnpkg. 
What should still be done to move this report to Resolved?

Whiteboard: MGA8TOO MGA8-64-OK MGA9-64-OK => MGA9-64-OK

Comment 8 Marja Van Waes 2023-11-27 12:58:04 CET

(In reply to christian barranco from comment #7)
> MGA8 doesn’t have yarnpkg. 
> What should still be done to move this report to Resolved?

Did you have this page in an old cache?

David Walser set this report to RESOLVED-DUPLICATE on 2023-09-28 18:58:34 CEST

Comment 9 christian barranco 2023-11-27 13:02:34 CET

Hi Marja. My bad indeed. The thing is I thought this report was blocking mga#28809 , but no then.

Comment 10 christian barranco 2023-11-27 13:03:50 CET

And I am on my phone, which is not easy (at least for me) to get a good overview…

Comment 11 Marja Van Waes 2023-11-27 14:37:24 CET

It's no problem at all. You do a lot of great work and I'm sure I err more often than you do.