- User Since
- Feb 12 2017, 5:00 PM (130 w, 6 d)
Nov 3 2018
The Update to upstream freeimage makes the previous patches unnecessary:
Removed the "sanitize encodings / line endings" bit because it isn't needed if no documentation is generated.
Oct 14 2018
Oct 13 2018
Sep 21 2018
have it enabled on my local build
there is a bug in the current release where the plugin interface is not shown so activating involves manually changing settings in dconf .
I would monitor the bug and if it update the commit with a patch/point release when this issue is fixed.
Sep 17 2018
Updated commit to latest release
Sep 16 2018
Aug 11 2018
Aug 4 2018
Jul 21 2018
Jul 20 2018
Jul 15 2018
Installed no issues
- created new VM with Win 10 template
- Created a CentOs 7 Vm deleted the entry (xml definition) did not delete the storage, created a new VM entry with exiting storage
- start a VM created in the previous version of libvirt (switched machines yesterday)
Also ran into this issue yesterday. Tried to create new VM based on an exiting qcow2 image in Virt-Manager. Issue came up when I used the template thing to choose the OS (win 8.1 in my case). Even without the exiting image no media attached the error persists.
Used the generic template to with the exiting image and Virt-manager could create the machine. With other templates like CentOs 7.0 I didn't encounter the issue .
Can't offer a workaround for exiting machines but maybe this can narrow down the issue
Jul 4 2018
Removed patch. The issue was in updateing feedss (T2216) and I tested that again and still updates.
Jul 3 2018
I couldn't figure out how to update the exiting patch properly so I did a rewrite. Is that ok?
Jul 2 2018
bumped release number
Jul 1 2018
Jun 23 2018
Jun 16 2018
Jun 10 2018
Deleted unnecessary patch
Looked at license again thinks both GPLs are '-later'
Sorted the deps correctly
Updated with component
Jun 9 2018
Removed unnecessary sed commands.
Uses original avidemux2.desktop file now.
May 26 2018
forgot some cleanup