Bug 25571

Summary:	urpmi @ new version, do not forget to base on 8.110
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	MGA7TOO
Source RPM:	urpmi	CVE:
Status comment:

Description Morgan Leijström 2019-10-15 12:09:15 CEST

From Bug 24438 - urpmi.addmedia --distrib adds repositories with "Core 32bit Release" and "Core 32bit Updates" disabled while Nonfree/Tainted 32bit are enabled, causing problems when updating 32bit packages


Thomas Backlund from comment #15:
> (In reply to Martin Whitaker from comment #13)
> > For testing on a mga6 system., you'll first need to apply the two
> > cherry-picked patches I've just attached.
> > 
> > There's an inconsistency in the mga6 urpmi version. On a mga6 system I have
> > urpmi-8.110-2, but in subversion the spec file in updates/6 is for 8.110-1.
> 
> Looks like a screwup at Mga 6 release time.
> 
> I pushed translation updates as 8.110-1 but forgot to tag git, so remi
> tagged it with here:
> http://gitweb.mageia.org/software/rpm/urpmi/commit/
> ?id=47be347d65e30c8f0b80d1d1ed66295fd9a4dbe3
> 
> in order to add the:
> workaround a segfault in gurpmi (mga#21167) in mga 6 
> 
> But for some reason it failed to get picked up at svn branching.
> 
> So if someone do a new urpmi release, it  must be ensured that it's based of
> the real tagged 8.110 to not loose that fix

Morgan Leijström 2019-10-15 12:10:08 CEST

Whiteboard: (none) => MGA7TOO
Version: 7 => Cauldron
Assignee: bugsquad => mageiatools

Comment 1 Lewis Smith 2019-10-15 21:37:15 CEST

I do not see the point of this reminder bug, because the original bug 24438 has very recent posts even from you; and tv (for 'urpmi') is already CC'd there.
I suggest closing this one as a duplicate of the original - unless you have good reason not to do so.

Comment 2 Morgan Leijström 2019-10-15 21:52:41 CEST

OK you are more experienced on the customs here.

I was thinking one issue, one bug if possible; was thinking the upter bug could be solved and mark fixed asynchronously with an update of urpmi.

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

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