Bug 153943
| Summary: | [MAINTAINER] multimedia/gpodder: update to 2.12 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Charlie Kester <corky1951> | ||||
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
arved 2011-01-14 09:17:56 UTC
FreeBSD ports repository
Modified files:
multimedia/gpodder Makefile distinfo
Log:
Update to 2.12
PR: 153943
Submitted by: maintainer
Feature safe: yes
Revision Changes Path
1.40 +1 -1 ports/multimedia/gpodder/Makefile
1.24 +2 -2 ports/multimedia/gpodder/distinfo
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed committed, thanks |
Update to 2.12 From the author's website: This is a bugfix release on top of the 2.11 release from December. The only code change in this release is a fixed database migration code that avoids problems for users who skip some gPodder releases when upgrading (e.g. gPodder 2.7 to 2.11) and for whom the podcast list appears empty after upgrading. This release addresses this issue in two ways: * Upgrades from gPodder 2.7 or earlier to 2.12 work without problems * Empty databases after a failed upgrade are fixed by gPodder 2.12 The "fix" for empty databases only works if the migration data is still in the database file and if you have not added any new podcasts since due to the way the detection code for a failed upgrade works (it's not possible to distinguish a working DB from a DB with failed migration if you have added podcasts later on). Fix: ============= Files added or deleted: None Minor changes only =============