openshot.developers team mailing list archive
-
openshot.developers team
-
Mailing list archive
-
Message #04533
[Bug 644667] [NEW] Sync openshot 1.2.1-1 (universe) from Debian unstable (main)
Public bug reported:
Binary package hint: openshot
Please sync openshot 1.2.1-1 (universe) from Debian unstable (main).
I am the author of this package, and this new version fixes many
segmentation faults that exist with openshot (1.1.3-1) on maverick.
Myself, along with 2 others have extensively tested the new version on
maverick, and it works much better and more stable that the current
version. This is a Python application, and there are no packages which
depend on the openshot package, and thus there should be very little
risk in syncing this package.
We do not have a CHANGES file, but here is the a link to our LaunchPad milestones, which document all the "changes":
https://launchpad.net/openshot/+milestone/1.2.0
https://launchpad.net/openshot/+milestone/1.2.1
Debian Changelog entries since current maverick version 1.1.3-1:
openshot (1.2.1-1) unstable; urgency=low
* New upstream release to fix some critical bugs with 1.2.0
-- Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx> Sun, 19 Sept 2010 21:00:00 +0100
openshot (1.2.0-1) unstable; urgency=low
* New upstream release
* Bumped standards version to 3.9.1, no changes required
-- Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx> Sun, 19 Sept 2010 20:00:00 +0100
** Affects: openshot (Ubuntu)
Importance: Undecided
Status: New
--
Sync openshot 1.2.1-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/644667
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to openshot in ubuntu.
Status in “openshot” package in Ubuntu: New
Bug description:
Binary package hint: openshot
Please sync openshot 1.2.1-1 (universe) from Debian unstable (main).
I am the author of this package, and this new version fixes many segmentation faults that exist with openshot (1.1.3-1) on maverick. Myself, along with 2 others have extensively tested the new version on maverick, and it works much better and more stable that the current version. This is a Python application, and there are no packages which depend on the openshot package, and thus there should be very little risk in syncing this package.
We do not have a CHANGES file, but here is the a link to our LaunchPad milestones, which document all the "changes":
https://launchpad.net/openshot/+milestone/1.2.0
https://launchpad.net/openshot/+milestone/1.2.1
Debian Changelog entries since current maverick version 1.1.3-1:
openshot (1.2.1-1) unstable; urgency=low
* New upstream release to fix some critical bugs with 1.2.0
-- Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx> Sun, 19 Sept 2010 21:00:00 +0100
openshot (1.2.0-1) unstable; urgency=low
* New upstream release
* Bumped standards version to 3.9.1, no changes required
-- Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx> Sun, 19 Sept 2010 20:00:00 +0100
Follow ups
References