(In reply to Bit Twister from comment #0)
> Description of problem: mga7
> 
> Picked a package and popup gives
> Sorry, the following package cannot be selected:
> 
> Without any other information.
> Tried others with same results.
> 

This report is about drakrpm not explaining why the package cannot be selected, correct?

Did it use to tell why a package couldn't be selected?

(If it never did, then this'll become an enhancement request)

Keywords: (none) => NEEDINFO
Assignee: bugsquad => mageiatools
CC: (none) => marja11

(In reply to Marja van Waes from comment #1)
> (In reply to Bit Twister from comment #0)

> 
> This report is about drakrpm not explaining why the package cannot be
> selected, correct?

Correct.

> 
> Did it use to tell why a package couldn't be selected?

I never tried the test before.  :)

Since it will create a core if core dumps are enabled, and it is a mga6.rpm I just assumed it was a bug, and hopefully would not happen when the mga7 rpm is installed.


In my opinion applications should not go around creating core files if core dump is enabled.

> (If it never did, then this'll become an enhancement request)

Hmmm, if the code is there to show the reason, but has not been working, I suggest to you it is a bug. Seems like the Dev will have to decide if it is a bug or enhancement.

Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Status of this is unclear.

New installation M7 and Cauldron with above command:

(In reply to Bit Twister from comment #0)
> Description of problem: mga7
> 
> Picked a package and popup gives
> Sorry, the following package cannot be selected:
> 
> Without any other information.
> Tried others with same results.
> 
> Running urpmi --replacefiles --auto-update --auto --download-all from the
> command line shows
> 
> While some packages may have been installed, there were failures.
> The following packages can't be installed because they depend on packages
> that are older than the installed ones:
> systemd-devel-230-12.mga6
> lib64dbus-devel-1.10.16-1.mga6
> lib64atk-bridge-devel-2.26.0-1.mga7
> lib64gtk+3.0-devel-3.22.24-1.mga7
> lib64edataserver1.2-devel-3.26.1-1.mga7
> lib64gweather-devel-3.26.0-1.mga7
> evolution-data-server-tests-3.26.1-1.mga7
> lib64ebook1.2_19-3.26.1-1.mga7
> lib64camel1.2_60-3.26.1-1.mga7
> lib64evolution-data-server-gir1.2-3.26.1-1.mga7
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible: always
> 
> 
> Steps to Reproduce:
> 1. run drakrpm-update
> 2. pick any un-selected package
> 3.

See mga6 packages and mga7 ones. This is not recommended.

Does this still apply?

CC: (none) => ouaurelien
Keywords: NEEDINFO => (none)

(In reply to Aurelien Oudelet from comment #4)
> Status of this is unclear.

I would say status is clear. :)
but it is unclear if the problem still exists.

> New installation M7 and Cauldron with above command:

I concur because currently there are no packages that fail to install.
Big round of Thank You to the Devs, QA, Packagers, and everyone else.


> > systemd-devel-230-12.mga6
> > lib64dbus-devel-1.10.16-1.mga6
> > lib64atk-bridge-devel-2.26.0-1.mga7

> 
> See mga6 packages and mga7 ones. This is not recommended.

What can I say, I do a clean install, install all my add on rpms
and yet there they are.

> Does this still apply?

I can not say. The fail to install problem has not shown up so I can
not perform the test.

As for mga6 rpms in cauldron there is cookcc, cookcc-javadoc, hub, hub-doc
and js-sizzle, and 255 mga7 rpms in cauldron.

This bug was filed against Mageia 6 which is EOL since Sep 2019.

Closing as OLD.

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