From: Nick H. <nic...@ho...> - 2013-03-15 18:31:50
|
I have started to look at this bug. When family trees are listed two tables are opened. The Gramps database version is obtained from the metadata table and the number of people from the person table. If a table created using bsddb is opened using bsddb3 it is upgraded. Attempting to open a table in bsddb3 format using bsddb will give an error. The same thing happens of you open a bsddb database using bsddb3 in the Gramps GUI. At present we don't warn the user that the format of their database will be changed. Is there a way we can determine the bsddb version before opening a table? If not, should we create a text file containing a version, so we can warn the user before an upgrade? Nick. |
From: Paul F. <pf....@gm...> - 2013-03-15 20:51:31
|
On 3/15/13, Nick Hall <nic...@ho...> wrote: > Is there a way we can determine the bsddb version before opening a > table? If not, should we create a text file containing a version, so > we can warn the user before an upgrade? If an additional file is created, why not put everything into it which a "gramps -L" types out (number of people, locked, etc.)? Just a thought. |
From: Nick H. <nic...@ho...> - 2013-03-15 21:14:05
|
On 15/03/13 20:51, Paul Franklin wrote: > On 3/15/13, Nick Hall <nic...@ho...> wrote: >> Is there a way we can determine the bsddb version before opening a >> table? If not, should we create a text file containing a version, so >> we can warn the user before an upgrade? > If an additional file is created, why not put everything into it > which a "gramps -L" types out (number of people, locked, etc.)? > > Just a thought. > > We could create an extra file. My question is, do we want to? Is there a neat way of detecting that Gramps is about to upgrade the database? How do we want to fix this? It applies not only to CLI, but also to the GUI. Nick. |
From: Benny M. <ben...@gm...> - 2013-03-15 22:43:14
|
We already have a bdbversion.txt file. I would just use that, or is it not sufficient? I don't think it's a problem to only fix this in gramps 4.0 This is on the roadmap of 3.4 because we use 3.4 and 4.0, but users will not do that. So it should be sufficient if 4.0 gives warning if 1/no bdbversion.txt present 2/present but older version. If user upgrades with 4.0, he should not expect it to open with 3.4 (it will work in 3.4 anyway if the python version is the same though!). Anyway, from the mailing correspondence, I was thinking Tim fixed this already.... Backporting bdbversion.txt writeout to gramps 3.4 is off course allowed :-) Benny 2013/3/15 Nick Hall <nic...@ho...> > On 15/03/13 20:51, Paul Franklin wrote: > > On 3/15/13, Nick Hall <nic...@ho...> wrote: > >> Is there a way we can determine the bsddb version before opening a > >> table? If not, should we create a text file containing a version, so > >> we can warn the user before an upgrade? > > If an additional file is created, why not put everything into it > > which a "gramps -L" types out (number of people, locked, etc.)? > > > > Just a thought. > > > > > We could create an extra file. My question is, do we want to? > > Is there a neat way of detecting that Gramps is about to upgrade the > database? > > How do we want to fix this? It applies not only to CLI, but also to > the GUI. > > Nick. > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2013-03-16 01:10:58
|
On 15/03/13 22:43, Benny Malengier wrote: > Anyway, from the mailing correspondence, I was thinking Tim fixed this > already.... I am happy to let Tim fix it. I was just trying to help out fixing something for the next release. The bug was not assigned. When someone starts work on a fix, if they assign the bug to themselves then it will let others know to move onto another one. Nick. |
From: Tim L. <guy...@gm...> - 2013-03-15 23:09:35
|
bdbversion.txt is already written in gramps34, it is just that it is not used in the right way. (I have looked at this myself, and done some prototype work, but not the full fix). I believe this needs to be fixed in gramps34 as well as 40 and trunk, because there will still be people upgrading from even earlier versions of Gramps to gramps34, and also, it will apply if the bsddb version is upgraded underneath any version of Gramps (by some upgrade to the platform). I have now raised http://www.gramps-project.org/bugs/view.php?id=6483 Listing the Family Trees can corrupt them http://www.gramps-project.org/bugs/view.php?id=6529 Cancelling database upgrade can corrupt the database I suggest the following changes to gramps34, gramps40 and trunk: (1) Change src/cli/clidbman.py get_dbdir_summary() (a) return (count, bsdbdversion, schemaversion) (b) On entry open bdbversion.txt. If the file is absent or not the current version of bsddb return ("Unknown", "Unknown", "Unknown") without touching the database. (2) Change src/cli/clidbman.py family_tree_summary() to output both bsddb version and schema version (note that at present, "db version" means the schema version, not the [bsd]db version). (3) Change src/gen/db/write.py __check_db_version() (a) Open bdbversion.txt (b) If bsddbversion is the current version, return. (c) If the file is absent, run a Question dialogue explaining that the version of the database could not be determined and asking whether you want to try to open the database. (d) If the bsddb is going to be upgraded run a question dialogue explaining that the database will be upgraded. (e) If the user answers yes to the dialogues, create a zip file in .gramps, named <path_name from NAME_FILE>_<date>_<time> containing all the database files. Then return. (f) if the user answers no to the dialogue, raise an exception. (g) If the bsddb is going to be a downgrade, raise the exception as at present. I suggest the output to a zip file, because at least that way, if there are problems, the user has some chance of having a 'backup' file that could be used to recover the data. Note, I think some of the errors in dbloader.py read_file may no longer be raised. I have not checked things like import and open in cli to see whether there may be other places that need to be fixed. I think these are all bugs (rather than feature requests) except for changing the family tree summary, but I hope you will agree that this is a necessary change so that users can understand what is happening. -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659380.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Tim L. <guy...@gm...> - 2013-03-16 11:22:51
|
I missed a change: Tim Lyons wrote > bdbversion.txt is already written in gramps34, it is just that it is not > used in the right way. > > (I have looked at this myself, and done some prototype work, but not the > full fix). > > I believe this needs to be fixed in gramps34 as well as 40 and trunk, > because there will still be people upgrading from even earlier versions of > Gramps to gramps34, and also, it will apply if the bsddb version is > upgraded underneath any version of Gramps (by some upgrade to the > platform). > > I have now raised > > http://www.gramps-project.org/bugs/view.php?id=6483 Listing the Family > Trees can corrupt them > http://www.gramps-project.org/bugs/view.php?id=6529 Cancelling database > upgrade can corrupt the database > > I suggest the following changes to gramps34, gramps40 and trunk: > > (1) Change src/cli/clidbman.py get_dbdir_summary() > (a) return (count, bsdbdversion, schemaversion) > (b) On entry open bdbversion.txt. If the file is absent or not the > current version of bsddb return ("Unknown", "Unknown", "Unknown") without > touching the database. > > (2) Change src/cli/clidbman.py family_tree_summary() to output both bsddb > version and schema version (note that at present, "db version" means the > schema version, not the [bsd]db version). > > (3) Change src/gen/db/write.py __check_db_version() > (a) Open bdbversion.txt > (b) If bsddbversion is the current version, return. > (c) If the file is absent, run a Question dialogue explaining that the > version of the database could not be determined and asking whether you > want to try to open the database. > (d) If the bsddb is going to be upgraded run a question dialogue > explaining that the database will be upgraded. > (e) If the user answers yes to the dialogues, create a zip file in > .gramps, named > <path_name from NAME_FILE> > _ > <date> > _ > <time> > containing all the database files. Then return. > (f) if the user answers no to the dialogue, raise an exception. > (g) If the bsddb is going to be a downgrade, raise the exception as at > present. (4) Change src/cli/clidbman.py create_new_db() or create_new_db_cli() so that when the a new database is created the bdbversion.txt file is written Tim Lyons wrote > I suggest the output to a zip file, because at least that way, if there > are problems, the user has some chance of having a 'backup' file that > could be used to recover the data. > > Note, I think some of the errors in dbloader.py read_file may no longer be > raised. I have not checked things like import and open in cli to see > whether there may be other places that need to be fixed. > > > I think these are all bugs (rather than feature requests) except for > changing the family tree summary, but I hope you will agree that this is a > necessary change so that users can understand what is happening. -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659391.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Benny M. <ben...@gm...> - 2013-03-16 09:39:29
|
2013/3/16 Tim Lyons <guy...@gm...> > bdbversion.txt is already written in gramps34, it is just that it is not > used > in the right way. > > (I have looked at this myself, and done some prototype work, but not the > full fix). > > I believe this needs to be fixed in gramps34 as well as 40 and trunk, > because there will still be people upgrading from even earlier versions of > Gramps to gramps34, and also, it will apply if the bsddb version is > upgraded > underneath any version of Gramps (by some upgrade to the platform). > > I have now raised > > http://www.gramps-project.org/bugs/view.php?id=6483 Listing the Family > Trees > can corrupt them > http://www.gramps-project.org/bugs/view.php?id=6529 Cancelling database > upgrade can corrupt the database > > I suggest the following changes to gramps34, gramps40 and trunk: > > (1) Change src/cli/clidbman.py get_dbdir_summary() > (a) return (count, bsdbdversion, schemaversion) > (b) On entry open bdbversion.txt. If the file is absent or not the > current version of bsddb return ("Unknown", "Unknown", "Unknown") without > touching the database. > > (2) Change src/cli/clidbman.py family_tree_summary() to output both bsddb > version and schema version (note that at present, "db version" means the > schema version, not the [bsd]db version). > > (3) Change src/gen/db/write.py __check_db_version() > (a) Open bdbversion.txt > (b) If bsddbversion is the current version, return. > (c) If the file is absent, run a Question dialogue explaining that the > version of the database could not be determined and asking whether you want > to try to open the database. > (d) If the bsddb is going to be upgraded run a question dialogue > explaining that the database will be upgraded. > (e) If the user answers yes to the dialogues, create a zip file in > .gramps, named <path_name from NAME_FILE>_<date>_<time> containing all the > database files. Then return. > (f) if the user answers no to the dialogue, raise an exception. > (g) If the bsddb is going to be a downgrade, raise the exception as at > present. > > I suggest the output to a zip file, because at least that way, if there are > problems, the user has some chance of having a 'backup' file that could be > used to recover the data. > > Note, I think some of the errors in dbloader.py read_file may no longer be > raised. I have not checked things like import and open in cli to see > whether > there may be other places that need to be fixed. > > > I think these are all bugs (rather than feature requests) except for > changing the family tree summary, but I hope you will agree that this is a > necessary change so that users can understand what is happening. > > I agree to this, although too many dialogs is not very nice. Probably3 c and d above can be rolled in one dialog. I don't think the bug should hold up release. Also,, changes like this need some testing, so if we do before release, release must be postponed. So I suggest to put it on next release, and that we do that release together with 4.0.0. Now we need a release to have plugins working again. Tim, do you have time to do these fixes the coming month? Benny > > > -- > View this message in context: > http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659380.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Tim L. <guy...@gm...> - 2013-03-16 11:52:07
|
Benny Malengier wrote > I agree to this, although too many dialogs is not very nice. Probably3 c > and d above can be rolled in one dialog. > I don't think the bug should hold up release. Also,, changes like this > need > some testing, so if we do before release, release must be postponed. So I > suggest to put it on next release, and that we do that release together > with 4.0.0. > Now we need a release to have plugins working again. > > Tim, do you have time to do these fixes the coming month? Yes, I should be able to do that. Are you saying that I should put off any commits for this till after 3.4.3 has been released? Tim. -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659393.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Benny M. <ben...@gm...> - 2013-03-16 12:17:56
|
2013/3/16 Tim Lyons <guy...@gm...> > Benny Malengier wrote > > I agree to this, although too many dialogs is not very nice. Probably3 c > > and d above can be rolled in one dialog. > > I don't think the bug should hold up release. Also,, changes like this > > need > > some testing, so if we do before release, release must be postponed. So I > > suggest to put it on next release, and that we do that release together > > with 4.0.0. > > Now we need a release to have plugins working again. > > > > Tim, do you have time to do these fixes the coming month? > > Yes, I should be able to do that. > > Are you saying that I should put off any commits for this till after 3.4.3 > has been released? > Yes, Jerome plans for 19 March, so that is not long :-) Quick changes only lead to too little testing. Benny > > Tim. > > > > -- > View this message in context: > http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659393.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: jerome <rom...@ya...> - 2013-03-16 15:30:22
|
> Yes, Jerome plans for 19 March, so that is not long :-) Quick changes only lead to too little testing. If need we can release 3.4.3 on April? --- En date de : Sam 16.3.13, Benny Malengier <ben...@gm...> a écrit : De: Benny Malengier <ben...@gm...> Objet: Re: [Gramps-devel] 6483: Listing the Family Trees can corrupt them À: "Tim Lyons" <guy...@gm...> Cc: "Gramps Development List" <gra...@li...> Date: Samedi 16 mars 2013, 13h17 2013/3/16 Tim Lyons <guy...@gm...> Benny Malengier wrote > I agree to this, although too many dialogs is not very nice. Probably3 c > and d above can be rolled in one dialog. > I don't think the bug should hold up release. Also,, changes like this > need > some testing, so if we do before release, release must be postponed. So I > suggest to put it on next release, and that we do that release together > with 4.0.0. > Now we need a release to have plugins working again. > > Tim, do you have time to do these fixes the coming month? Yes, I should be able to do that. Are you saying that I should put off any commits for this till after 3.4.3 has been released? Yes, Jerome plans for 19 March, so that is not long :-) Quick changes only lead to too little testing. Benny Tim. -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659393.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel -----La pièce jointe associée suit----- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar -----La pièce jointe associée suit----- _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Tim L. <guy...@gm...> - 2013-03-17 11:15:10
|
Jérôme wrote >> Yes, Jerome plans for 19 March, so that is not long :-) > Quick changes only lead to too little testing. > > If need we can release 3.4.3 on April? As we need 3.4.3 to allow add-on updates, I don't think it is worth postponing the release for fixing the database problems. Lets aim the database problems for 3.4.4 in the not too distant future, and try to fix some more bugs for 3.4.4. Regards, Tim. -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659410.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Jérôme <rom...@ya...> - 2013-03-18 09:54:41
|
There was an alternate release name (proposed for 3.4.2)[1]: "Whenever life gets you down, Mrs. Brown" Is it OK to use it for 3.4.3 release? I should be able to patch two minor issues before this release: * 4687: global name 'warn' is not defined 'logging' or 'warning' module? * 6512: Header columns on Event Compare tool should not use event_name from table_titles but they can also wait for 3.4.4! Also, I am not certain of current status for some bug reports[2]: * 6336: Delayed update of bottom bar in Person View after merge * 6493: crash during Calculate Preview of a filtered XML export * 6526: crashes when entering or leaving person view * 3968: [NarWeb] Save/Restore settings for Narrated Website Generation [1] http://www.gramps-project.org/wiki/index.php?title=Previous_releases [2] http://www.gramps-project.org/bugs/roadmap_page.php?version_id=35 Le 17/03/2013 12:14, Tim Lyons a écrit : > Jérôme wrote >>> Yes, Jerome plans for 19 March, so that is not long :-) >> Quick changes only lead to too little testing. >> >> If need we can release 3.4.3 on April? > > As we need 3.4.3 to allow add-on updates, I don't think it is worth > postponing the release for fixing the database problems. Lets aim the > database problems for 3.4.4 in the not too distant future, and try to fix > some more bugs for 3.4.4. > > Regards, > Tim. > > > > -- > View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659410.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Alain A. <ala...@wa...> - 2013-03-18 10:18:16
|
<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Le 18/03/2013 10:54, Jérôme a écrit :<br> </div> <blockquote cite="mid:514...@ya..." type="cite"> <pre wrap="">There was an alternate release name (proposed for 3.4.2)[1]: "Whenever life gets you down, Mrs. Brown" Is it OK to use it for 3.4.3 release?</pre> </blockquote> I'm just sorry about the non choice of 'For Rob ...' or something like that as we purpose there is a few time.<br> <br> A+<br> <div class="moz-signature">-- <br> <hr> Alain Aupeix<br> <a class="moz-txt-link-freetext" href="http://jujuland.pagesperso-orange.fr/">http://jujuland.pagesperso-orange.fr/</a><br> <a class="moz-txt-link-freetext" href="http://pissobi-lacassagne.pagesperso-orange.fr/">http://pissobi-lacassagne.pagesperso-orange.fr/</a> <hr> U.buntu 12.04 | G.ramps 3.5.0-0.SVN20055 | H.arbour 3.2.0dev (Rev 18920) | HbIDE (Rev.189) <hr></div> </body> </html> |
From: Jérôme <rom...@ya...> - 2013-03-18 12:51:39
|
'3.4.1' was 'in Memory of Rob G. Healey'. http://www.gramps-project.org/wiki/index.php?title=Template:Releases/3.4.1 http://gramps-project.org/2012/07/in-memory-of-rob-g-healey/ Le 18/03/2013 11:18, Alain Aupeix a écrit : > Le 18/03/2013 10:54, Jérôme a écrit : >> There was an alternate release name (proposed for 3.4.2)[1]: >> "Whenever life gets you down, Mrs. Brown" >> >> Is it OK to use it for 3.4.3 release? > I'm just sorry about the non choice of 'For Rob ...' or something like > that as we purpose there is a few time. > > A+ > -- > ------------------------------------------------------------------------ > Alain Aupeix > http://jujuland.pagesperso-orange.fr/ > http://pissobi-lacassagne.pagesperso-orange.fr/ > ------------------------------------------------------------------------ > U.buntu 12.04 | G.ramps 3.5.0-0.SVN20055 | H.arbour 3.2.0dev (Rev 18920) > | HbIDE (Rev.189) > ------------------------------------------------------------------------ |
From: Alain A. <ala...@wa...> - 2013-03-18 13:05:27
|
<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Le 18/03/2013 13:51, Jérôme a écrit :<br> </div> <blockquote cite="mid:514...@ya..." type="cite">'3.4.1' was 'in Memory of Rob G. Healey'. <br> </blockquote> Sorry, I miss it ...<br> <br> A+<br> <div class="moz-signature">-- <br> <hr> Alain Aupeix<br> <a class="moz-txt-link-freetext" href="http://jujuland.pagesperso-orange.fr/">http://jujuland.pagesperso-orange.fr/</a><br> <a class="moz-txt-link-freetext" href="http://pissobi-lacassagne.pagesperso-orange.fr/">http://pissobi-lacassagne.pagesperso-orange.fr/</a> <hr> U.buntu 12.04 | G.ramps 3.5.0-0.SVN20055 | H.arbour 3.2.0dev (Rev 18920) | HbIDE (Rev.189) <hr></div> </body> </html> |
From: Nick H. <nic...@ho...> - 2013-03-18 14:07:45
|
On 18/03/13 09:54, Jérôme wrote: > Also, I am not certain of current status for some bug reports[2]: > > * 6336: Delayed update of bottom bar in Person View after merge > > * 6493: crash during Calculate Preview of a filtered XML export > > * 6526: crashes when entering or leaving person view > > * 3968: [NarWeb] Save/Restore settings for Narrated Website Generation I fixed the Citation gramplet as part of bug #6336. The reporter needs check to see if this solves the problem. The Set Tag tool has now been marked as UNSTABLE. Bug #6526 has been left open, due to another related error that I don't quite understand. Both of these bugs are probably fixed though. Nick. |
From: Jérôme <rom...@ya...> - 2013-03-18 17:38:13
|
OK, thank you! Also, I looked at changelog for last changes since 3.4.2. I started a draft section for NEWS page[1]. I am not certain to know what all these changes mean for user. ie. should be include into a generic line like 'various bug fix' or we should be more descriptive? This page could be available after 3.4.3 release (will be included into NEWS page), but if someone knows what type of changes should have its own line or find a group of changes, feel free to improve current page[1]. [1] http://www.gramps-project.org/wiki/index.php?title=Template:Releases/3.4.3 Jérôme Le 18/03/2013 15:07, Nick Hall a écrit : > On 18/03/13 09:54, Jérôme wrote: >> Also, I am not certain of current status for some bug reports[2]: >> >> * 6336: Delayed update of bottom bar in Person View after merge >> >> * 6493: crash during Calculate Preview of a filtered XML export >> >> * 6526: crashes when entering or leaving person view >> >> * 3968: [NarWeb] Save/Restore settings for Narrated Website Generation > > I fixed the Citation gramplet as part of bug #6336. The reporter needs > check to see if this solves the problem. > > The Set Tag tool has now been marked as UNSTABLE. Bug #6526 has been > left open, due to another related error that I don't quite understand. > > Both of these bugs are probably fixed though. > > Nick. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Nick H. <nic...@ho...> - 2013-03-18 18:14:58
|
Jérôme, Out of my commits the following would be of interest to the user: r21654 6336: Fix update problems with citation bottombar gramplet r21632 Make availability of GraphViz settings depend on output format r21631 Improve the descriptions and tooltip for GraphViz aspect ratio option r21605 6237: Suppress Gramps ID in Narrative Web report r21575 6457: Fix Open Document Text output in Book report The commit message for r21575 referred to the bug fix I reverted. Nick. On 18/03/13 17:37, Jérôme wrote: > OK, thank you! > > > Also, I looked at changelog for last changes since 3.4.2. > I started a draft section for NEWS page[1]. > > I am not certain to know what all these changes mean for user. > ie. should be include into a generic line like 'various bug fix' or we > should be more descriptive? > > This page could be available after 3.4.3 release (will be included into > NEWS page), but if someone knows what type of changes should have its > own line or find a group of changes, feel free to improve current page[1]. > > > [1] > http://www.gramps-project.org/wiki/index.php?title=Template:Releases/3.4.3 > > > Jérôme > > Le 18/03/2013 15:07, Nick Hall a écrit : >> On 18/03/13 09:54, Jérôme wrote: >>> Also, I am not certain of current status for some bug reports[2]: >>> >>> * 6336: Delayed update of bottom bar in Person View after merge >>> >>> * 6493: crash during Calculate Preview of a filtered XML export >>> >>> * 6526: crashes when entering or leaving person view >>> >>> * 3968: [NarWeb] Save/Restore settings for Narrated Website Generation >> I fixed the Citation gramplet as part of bug #6336. The reporter needs >> check to see if this solves the problem. >> >> The Set Tag tool has now been marked as UNSTABLE. Bug #6526 has been >> left open, due to another related error that I don't quite understand. >> >> Both of these bugs are probably fixed though. >> >> Nick. >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_mar >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel |
From: Benny M. <ben...@gm...> - 2013-03-18 19:13:21
|
Jerome, In stead of: New URL for gramps-addons Write: "Plugins now need to be downloaded from a different location. Only with 3.4.3 will you be able to dowload updates to the downloadable plugins." And put that as first item. Then perhaps as second: "Large cleanup in the narrative web plugin" and then group the narweb commits with that. Note that it is nice to add the username of the person who did the commit, see eg http://www.piware.de/2013/03/pygobject-3-7-92-released/. Don't know if that is easy to add :-) Benny 2013/3/18 Jérôme <rom...@ya...> > OK, thank you! > > > Also, I looked at changelog for last changes since 3.4.2. > I started a draft section for NEWS page[1]. > > I am not certain to know what all these changes mean for user. > ie. should be include into a generic line like 'various bug fix' or we > should be more descriptive? > > This page could be available after 3.4.3 release (will be included into > NEWS page), but if someone knows what type of changes should have its > own line or find a group of changes, feel free to improve current page[1]. > > > [1] > http://www.gramps-project.org/wiki/index.php?title=Template:Releases/3.4.3 > > > Jérôme > > Le 18/03/2013 15:07, Nick Hall a écrit : > > On 18/03/13 09:54, Jérôme wrote: > >> Also, I am not certain of current status for some bug reports[2]: > >> > >> * 6336: Delayed update of bottom bar in Person View after merge > >> > >> * 6493: crash during Calculate Preview of a filtered XML export > >> > >> * 6526: crashes when entering or leaving person view > >> > >> * 3968: [NarWeb] Save/Restore settings for Narrated Website Generation > > > > I fixed the Citation gramplet as part of bug #6336. The reporter needs > > check to see if this solves the problem. > > > > The Set Tag tool has now been marked as UNSTABLE. Bug #6526 has been > > left open, due to another related error that I don't quite understand. > > > > Both of these bugs are probably fixed though. > > > > Nick. > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_d2d_mar > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: John R. <jr...@ce...> - 2013-03-18 19:37:42
|
On Mar 18, 2013, at 12:13 PM, Benny Malengier <ben...@gm...> wrote: > Jerome, > > In stead of: > > New URL for gramps-addons > > Write: > > "Plugins now need to be downloaded from a different location. Only with 3.4.3 will you be able to dowload updates to the downloadable plugins." > > And put that as first item. > Then perhaps as second: > > "Large cleanup in the narrative web plugin" and then group the narweb commits with that. > > Note that it is nice to add the username of the person who did the commit, see eg http://www.piware.de/2013/03/pygobject-3-7-92-released/. Don't know if that is easy to add :-) > One more: New optional dependency, PyICU, corrects sorting in non-English locales especially on Microsoft Windows. Regards, John Ralls |
From: Nick H. <nic...@ho...> - 2013-03-18 19:50:11
|
On 18/03/13 19:13, Benny Malengier wrote: > "Plugins now need to be downloaded from a different location. Only > with 3.4.3 will you be able to dowload updates to the downloadable > plugins." > or perhaps: "Plugins now need to be downloaded from a different location. Only with 3.4.3 will you be able to receive automatic notification of new and updated plugins." or "Plugins now need to be downloaded from a different location. Only with 3.4.3 will you be able to use Gramps to check for new and updated plugins." Nick. |
From: Tim L. <guy...@gm...> - 2013-03-18 20:58:45
|
I have just been updating the page, to include PyICY, Narrative Web (summary and details). For Addon, have changed it to The automatic [[3.4_Addons#Installing_Addons_in_Gramps|Addon checking and download]] now works once again (the location used in Gramps 3.4.2 and before had been changed, so the the automatic process was no longer working). (In order to be positive first, and to explain why after - hope that is OK). -- View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659456.html Sent from the GRAMPS - Dev mailing list archive at Nabble.com. |
From: Nick H. <nic...@ho...> - 2013-03-18 21:34:52
|
Tim, Yes, that looks Ok to me. I've added my commits to the page. Nick. On 18/03/13 20:58, Tim Lyons wrote: > I have just been updating the page, to include PyICY, Narrative Web (summary > and details). > > For Addon, have changed it to > > The automatic [[3.4_Addons#Installing_Addons_in_Gramps|Addon checking and > download]] now works once again (the location used in Gramps 3.4.2 and > before had been changed, so the the automatic process was no longer > working). > > (In order to be positive first, and to explain why after - hope that is OK). > > > > -- > View this message in context: http://gramps.1791082.n4.nabble.com/6483-Listing-the-Family-Trees-can-corrupt-them-tp4659372p4659456.html > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > |