| Summary: | 6_rc0: unable to install flightgear due to unsatisfied flightgear-data | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Rémi Verschelde <rverschelde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lists.jjorge |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | flightgear-2016.4.2-1.mga6.x86_64 | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2016-12-04 06:52:48 CET
flightgear needs a rebuild with fixed version number in the requires. Assignee:
bugsquad =>
lists.jjorge Any chance that flightgear requires could be modified to want flightgear-data equal to same version or accept greater than current version?
If so maybe yaflight might could use the same feature.
installing flightgear-data-2016.4.2-1.mga6.noarch.rpm from /var/cache/urpmi/rpms
Preparing... ####################
1/1: flightgear-data ######################
removing package yaflight-0.99.29-6.mga6.x86_64
1/3: removing yaflight-0.99.29-6.mga6.x86_64
######################
removing package flightgear-2016.4.2-1.mga6.x86_64
2/3: removing flightgear-2016.4.2-1.mga6.x86_64
#######################
3/3: removing flightgear-data-2016.4.1-1.mga6.noarch
Yes, the requires should be:
Requires: flightgear-data >= %{version}
Here upstream had not released data 2016.4.2 when they released the .2 version of the engine, so I guess zezinho had to hardcode the min necessary version - but at any rate it should be a minimum, not an exact requires.
|