Bug 19085 - Update Unetbootin to 1.0.0
Summary: Update Unetbootin to 1.0.0
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Low minor
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-29 05:42 CEST by Kristoffer Grundström
Modified: 2022-05-27 22:06 CEST (History)
2 users (show)

See Also:
Source RPM: unetbootin
CVE:
Status comment:


Attachments

Description Kristoffer Grundström 2016-07-29 05:42:14 CEST
I took the liberty of building the latest upstream version of Unetbootin and I have tested that it works so it's OK to put it in Cauldron at any time.
Kristoffer Grundström 2016-07-29 05:42:34 CEST

Priority: Normal => Low
CC: (none) => hamnisdude
Target Milestone: --- => Mageia 6

Comment 1 Kristoffer Grundström 2016-07-29 06:34:28 CEST
Here's the src.rpm: https://www.dropbox.com/s/0hzx72zbym8p9i2/unetbootin-1.0.0-1.mga5.src.rpm?dl=0
Comment 2 Kristoffer Grundström 2016-07-29 06:35:23 CEST
Had to shorten the source row since it complained about the original line and I didn't know what else to have there.
David GEIGER 2016-07-29 08:22:28 CEST

CC: (none) => geiger.david68210
Assignee: bugsquad => shlomif

Comment 3 Kristoffer Grundström 2016-07-30 12:19:12 CEST
The only thing missing in it is to replace Mandriva with Mageia in the dropdown menu.
Comment 4 Samuel Verschelde 2016-10-10 21:54:25 CEST
Kristoffer, please avoid setting the target milestone, it's used internally to prioritize bug reports. Thanks :)

Target Milestone: Mageia 6 => ---

Comment 5 Kristoffer Grundström 2017-06-25 05:37:08 CEST
I just took the liberty of building a local version of Unetbootin 647 and it both installs and runs just fine.

However there is a libpng error in the terminal when you run it from there.
Comment 6 sturmvogel 2022-05-27 22:06:45 CEST
In MGA8 we have version 700 and in Cauldron the latest 702. Closing as FIXED.

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


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