Bug 10365 - urpmi --no-install installs when called second time
Summary: urpmi --no-install installs when called second time
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-30 11:40 CEST by Hartmut Goebel
Modified: 2013-11-23 16:15 CET (History)
1 user (show)

See Also:
Source RPM: urpmi-6.48.5-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Hartmut Goebel 2013-05-30 11:40:03 CEST
I try upgrading from Mageia2 to Mageia3.

Running
urpmi --replacefiles --auto-update --auto --no-install --noclean
downloades the files quite fine.

When running a second time this happens:
[root@server]# LC_ALL=C urpmi --replacefiles --auto-update --auto --no-install --noclean
medium "Core Release" is up-to-date
[...]
Freeing read locks for locker 0xc: 20563/139983559288576
[...]

restarting urpmi
The following packages have to be removed for others to be upgraded:
lib64avfilter2-0.10.7-1.mga2.tainted.x86_64
 (due to missing libopencv_imgproc.so.2.3()(64bit),
  due to missing libavformat.so.53()(64bit))
[... a few more oth this ...]
[... approx. 600 or 700 blank lines ...]
[root@server]#

This looks as if
a) urpmi get restarted even if no new package has been installed.
b) --no-install is not passed to the restarted urpmi
Comment 1 Samuel Verschelde 2013-08-29 16:56:19 CEST
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => thierry.vignaud

Comment 2 Manuel Hiebel 2013-10-22 12:19:01 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Thierry Vignaud 2013-10-22 21:38:08 CEST
Are you sure it actually installed anything?
Might be an issue between --no-install & priority updates
Comment 4 Hartmut Goebel 2013-10-27 17:23:40 CET
(In reply to Thierry Vignaud from comment #3)
> Are you sure it actually installed anything?

I can not tell whether it actually installed anything. Sorry, but this is 6 month ago now. Looking at my transscript, I would say it did not install anything. But if not, why does this "The following packages have to be removed for others to be upgraded:" appear then?
Thierry Vignaud 2013-10-27 18:49:01 CET

Summary: urpmi --no-install installes when called second time => urpmi --no-install installs when called second time

Comment 5 Manuel Hiebel 2013-11-23 16:15:41 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


Note You need to log in before you can comment on or make changes to this bug.