Bug 12353

Summary:	Attempt to install ProFTP/Apache on M4RC Classic Installer results in too many packagers selected
Product:	Mageia	Reporter:	William Kenney <wilcal.int>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	NEEDINFO
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:	4RC
Source RPM:		CVE:
Status comment:
Attachments:	List of packages to be installed along with ProFTP

Description William Kenney 2014-01-18 20:57:18 CET

Once:
Mageia 4 RC - DVD 32 bits
DATE.txt: Fri Jan 17 15:10:03 CET 2014
Mageia-4-RC-i586-DVD.iso
MD5SUM: 8377797be15a187de9154427e09dd1da

is installed properly and the repos set up an attempt to install either Apache
or ProFTP results in over 100 packages being selected. If install is proceeded
with a reboot results in a hung boot. Listing of packages selected is attached.

I'm sure there's a better Summary of this.


Reproducible: 

Steps to Reproduce:

William Kenney 2014-01-18 20:57:58 CET

Whiteboard: (none) => 4RC

Comment 1 William Kenney 2014-01-18 20:59:44 CET

Created attachment 4816 [details]
List of packages to be installed along with ProFTP

Comment 2 William Kenney 2014-01-18 23:51:01 CET

Same problem in:
Mageia 4 RC - DVD 64 bits
Date.txt: Fri Jan 17 15:20:42 CET 2014
Iso name: Mageia-4-RC-x86_64-DVD.iso
MD5SUM: ec1ce42c4b003b5e9bea6911968195c8

Even occurs if you attempt to install Flash or Kompozer

Comment 3 James Kerr 2014-01-19 02:30:46 CET

I did not have that experience.

I made a clean default install of KDE.

Did you execute "urpmi --auto-update" after setting up the repo's. There is a new version of mata-task, which may be relevant.

The packages that are listed in your attachment, were installed on my system as part of the installation of Mageia.

Comment 4 William Kenney 2014-01-19 04:52:28 CET

(In reply to James Kerr from comment #3)

> I did not have that experience.
> 
> I made a clean default install of KDE.
> 
> Did you execute "urpmi --auto-update" after setting up the repo's. There is
> a new version of mata-task, which may be relevant.

Thanks I will try this again tomorrow. I ran the test twice
with the same results. I think there is a serious problem
in how the repo is being handled with the new Classic Installer.
The old ones, not a few days old, worked just fine.

Comment 5 William Kenney 2014-01-19 18:20:30 CET

OK, after a lot of time and repeated installs I come to this conclusion:

There appears to be a very big difference between the way that
the present M4RC Live media vs Classic Install media handle my
local repo. I mirror to mirrors.kernel.org. I do that automatically
every day at 4AM. I also rsync again just before I do any testing.

If I do a Vbox install of lets say M4RC i586 KDE Live-CD and set
the repo such that it is my local repo all goes well. I can install
and update that test install with no problems at all. I can equally
set the repo such that it comes directly from mirrors.kernel.org
and that works just fine too. I believe this is the case for all of
the most recent M4RC Live media.

If I do a Vbox install of the very latest M4RC Classic Installers,
32 or 64 bit, if I use my same local repo it responds as defined
in the Description section of this BUG. If I change the repo
to be direct to mirrors.kernel.org all is well.

So for some reason the latest Classic Installer is not able to
deal with my local repo. I did an install using a one generation
older Classic Installer of just a few days ago and it used my local
repo just fine. So something has changed, and just with the
Classic Installers.

Comment 6 William Kenney 2014-01-19 22:34:59 CET

urpmi.addmedia  core  http://192.168.1.2:8080/~mageia/repo/distrib/4/i586/media/core/release with media_info/hdlist.cz

Works for Live media. Does not work for the most recent Classic Installers


http://mirrors.kernel.org/mageia/distrib/cauldron/i586/media/core/release/

works for both Live media and Classic Installers. Worked for the Classic Installers one generation ago.

Comment 7 Manuel Hiebel 2014-01-21 00:45:55 CET

please run urpmi yourpackage with '--debug' (on a clean environement ie removed of problematic stuff)

Keywords: (none) => NEEDINFO

Comment 8 William Kenney 2014-01-21 01:35:47 CET

(In reply to Manuel Hiebel from comment #7)

> please run urpmi yourpackage with '--debug' (on a clean environement ie
> removed of problematic stuff)

Thanks Manuel. As we "speak" I am rerunning all my testing on this BUG
with the latest ISO's ( dated 19 Jan ). All in Vbox. I am responding
to this message with a Vbox M4 i586 KDE Live-CD. It seems completely
ok with my local repo. All apps are installing from my local repo
with no problems. Give me another 12-hours or so to rerun all this
testing and I will report what I find here. If I run into the problem
again I will use your request and attach it to this BUG.

Comment 9 William Kenney 2014-01-21 01:46:48 CET

FWIW. Computer testing 101 when encountering a bad bug.
Make sure the good parts are still the good parts.

Comment 10 William Kenney 2014-01-21 17:50:44 CET

A retest of this BUG using:

Mageia-4-i586-DVD.iso  ( 01/20/14 )
MD5: 0bb60ecc92df941ceb797fd5edc49004
The retest has included a full range of apps.
All apps installed and updated successfully
using my local repo. On to 64-bit.

Comment 11 William Kenney 2014-01-21 18:58:32 CET

A retest of this BUG using:

Mageia-4-x86_64-DVD.iso  ( 01/20/14 )
MD5: 22614315f8c8aaccfe92d567bf566082
The retest has included a full range of apps.
All apps installed and updated successfully
using my local repo.

This BUG is resolved with the lastest versions
of the Classic Installers.

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