firebird-docs — chat stuff about documentation

[Firebird-docs] German langref25 completed

[Köditz, M. <Mar...@it...>]

Good evening,

I've just finished the translation of the last chapter. We have a complete German language reference now. I sent Alexey the pdf. The source code is on Github.

Regards
Martin

[Firebird-docs] FB firebird-3-developer-s-guide-relea

[Nico L. <nl...@mn...>]

Hello all, yesterday i browsed a little bit thru the newly published "FB 3 Developers Guide", 
and i found it very valuable and impressivly well done. NOw my question is, does it make sense to 
provide an additional application example based on  "Python Tkinter"? if so i would be
pleased to take this part and try my best to reach your level. Please let me know your thoughts
Kind Regards

-- 
Nico Latzer <nl...@mn...>

Re: [Firebird-docs] Comments on Firebird 3 Developers's guide

[Helen B. <he...@ii...>]

Mark wrote:

> On 7-3-2018 09:53, Mark Rotteveel wrote:
>> I hadn't noticed yet that the notifications were broken. I wonder if 
>> those are still after-shocks of the issues after the SourceForge 
>> datacenter migration.
>> 
>> I'll check and re-test the configuration.

> Possibly the passwords in mailman were lost during the migration (or at
> least the admin password of the mailing list didn't work for me), so I
> have set them back to their previous values.

> However, GitHub notifications still aren't showing up on the list. I 
> have added myself to the addressee list on GitHub, and the notification
> is showing up on my own address, and it includes the header that should
> let the list accept it. It looks like it might be a problem somewhere 
> within SourceForge...

I don't know how you set that up so I can't test any theory.  One
thought that occurred to me at the time of the big commit of the
fbdevguide files was that I'm fairly sure the SF mailman server has a
size limit on all messages, about 75 KB if I remember rightly.  I
tried to go into the admin interface to see if an over-size message
was waiting for action, but the server itself was down at the time.

It is up at the moment, but the only message there waiting for action
was some of the usual spam.  Your guess about some kind of hitch in
the infrastructure move is probably not far out.

As it happens, a list of files from the initial commit would have been
huge, as there were hundreds of files in the sources for the sample
projects, including dozens for Windows themes in the two .NET frameworks
and the Java app.

The important thing for notifications is to signal when someone has
committed a change or addition to one book or another.

Anyhoo, don't worry yourself about this until you're feeling better.
The users have a super reference book to start experimenting with and
nothing show-stopping has turned up so far.

Helen

Re: [Firebird-docs] Comments on Firebird 3 Developers's guide

[Mark R. <ma...@la...>]

On 7-3-2018 09:53, Mark Rotteveel wrote:
> I hadn't noticed yet that the notifications were broken. I wonder if 
> those are still after-shocks of the issues after the SourceForge 
> datacenter migration.
> 
> I'll check and re-test the configuration.

Possibly the passwords in mailman were lost during the migration (or at 
least the admin password of the mailing list didn't work for me), so I 
have set them back to their previous values.

However, GitHub notifications still aren't showing up on the list. I 
have added myself to the addressee list on GitHub, and the notification 
is showing up on my own address, and it includes the header that should 
let the list accept it. It looks like it might be a problem somewhere 
within SourceForge...

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Comments on Firebird 3 Developers's guide

[Mark R. <ma...@la...>]

On 6-3-2018 22:00, Helen Borrie wrote:
> Sunday, March 4, 2018, 3:02:20 AM, Mark wrote:
<snip>

> You can add it if you like - add a DOC ticket in Tracker.

I'll see what I can do, it may take a while though. I'm currently having 
some health problems that result in low energy and lack of 
concentration. I was already happy I was able to read it to the end and 
make some comments ;)

>> Page 22: SP_ADD_INVOICE_LINE generates an id for invoice_line_id, but
>> there is also a trigger that does this. Removing this would also remove
>> the need for the grant usage to the stored procedure.
> 
> Comment from Denis would be welcome.
> 
>> Page 27: Name of the zip (and the database) is rather generic, can we
>> use a more specific name (eg devguide-example.fdb, and
>> fb_devguide_db_3_0.zip)?
> 
> No, I don't think so.  We seem to have some limits on path lengths in
> the CMS;  plus any updates to links means updates in multiple
> locations.

Interesting. If the files are uploaded using SCP I wouldn't expect there 
to be such issues. Maybe creating an alias higher up the tree in the 
file system might be an option; that would also allow for supporting 
both old and new links.

>> Page 204: How are we going to handle version updates of dependencies?
>> For example Jaybird 3.0.0 has already been superseded with version
>> 3.0.3. And current latest jOOQ version is 3.10.5, latest Spring is
>> 5.0.4, (or 4.3.14 for 4.x), etc.
> 
> My take on this is that it would be something for the driver
> coordinators to keep an eye on.

Ok.

<snip>

> ditto ditto ditto.  Perhaps you and Denis need to confer about such
> things?

Ok

>> Page 211: Add callout that people must update the directory-element in
>> the jOOQ configuration in example.xml
> 
>> I also believe it is possible for jOOQ to have this configuration in the
>> pom.xml, this might make the code more self-contained.
> 
> ditto ditto ditto
> 
>> Page 213: Odd comments in code with a lot of question marks, maybe
>> originally Russian lost in conversion?
> 
> ?

Example:

         // ?????????? ???????????? ???????????
         dataSource.setUrl("jdbc:firebirdsql://localhost:3050/examples");
<snip>

> BTW, I recommended Tracker tickets for changes, etc., as our
> notification setup from github doesn't seem to be working.  Besides,
> the tracker tickets are more accessible to anyone who wants to follow
> changes.  Remember, Tracker isn't just for bugs.

I hadn't noticed yet that the notifications were broken. I wonder if 
those are still after-shocks of the issues after the SourceForge 
datacenter migration.

I'll check and re-test the configuration.

> Notice, too, that there is a Document History chapter.  It would be
> highly useful if you would add a row to that for each batch of changes
> you do, with a link to the Tracker ticket, where applicable.  The
> points you have made concerning the Java section will be more or less
> applicable to the other platforms as well.  Furthermore, we must hope
> that others will come along with sections for other platforms.

Ok, thanks for the feedback. I hope I can do something with it soon.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Comments on Firebird 3 Developers's guide

[Helen B. <he...@ii...>]

Sunday, March 4, 2018, 3:02:20 AM, Mark wrote:

> Great it is now released!

> Some comments on things I noticed when reading (Version 1.000, PDF 
> physical page numbers, not print page numbers). I only read the 
> introduction and the Java part (I'm biased ;):

> Page 9: "About the Author" doesn't say much about the author, add a 
> small biography?

Denis has since provided this - will be in 1.001

> Page 15: Note on use of identity column in Firebird 3 should mention 
> that creating the sequence and trigger is not necessary if using a 
> GENERATED BY DEFAULT AS IDENTITY clause

You can add it if you like - add a DOC ticket in Tracker.

> Page 15: Usage of BLOB SUB_TYPE 1 SEGMENT SIZE 80 is curious: a. 
> SUB_TYPE 1, better would be SUB_TYPE TEXT (more readable/explicit), and
> b. as far as I'm aware SEGMENT SIZE has been deprecated, and doesn't 
> even do anything except maybe for ESQL-usage, which isn't covered in 
> this guide. I think it should be replaced with just BLOB SUB_TYPE TEXT
> to avoid promoting outdated practices.

You can add it if you like - add a DOC ticket in Tracker.

> Page 22: SP_ADD_INVOICE_LINE generates an id for invoice_line_id, but 
> there is also a trigger that does this. Removing this would also remove
> the need for the grant usage to the stored procedure.

Comment from Denis would be welcome.

> Page 27: Name of the zip (and the database) is rather generic, can we 
> use a more specific name (eg devguide-example.fdb, and 
> fb_devguide_db_3_0.zip)?

No, I don't think so.  We seem to have some limits on path lengths in
the CMS;  plus any updates to links means updates in multiple
locations.

> Page 204: How are we going to handle version updates of dependencies? 
> For example Jaybird 3.0.0 has already been superseded with version 
> 3.0.3. And current latest jOOQ version is 3.10.5, latest Spring is 
> 5.0.4, (or 4.3.14 for 4.x), etc.

My take on this is that it would be something for the driver
coordinators to keep an eye on.

> Just updating could break examples, but we may want to add a note that
> people should check if they need to use newer versions.

You can add it if you like - add a DOC ticket in Tracker.

> Page 206: It might be helpful to add the jetty-maven-plugin. This allows
> people to run the example project without having to deploy it (manually)
> to tomcat or another servlet engine.

Same comment as above.

> Just add to the list of plugins:

>              <plugin>
>                  <groupId>org.eclipse.jetty</groupId>
>                  <artifactId>jetty-maven-plugin</artifactId>
>                  <version>9.4.8.v20171121</version>
>              </plugin>

> Then running the example application is just a matter of using

> mvn jetty:run

> from the commandline (or executing this goal from within your IDE), and
> opening http://localhost:8080/ in your browser.

ditto ditto ditto.  Perhaps you and Denis need to confer about such
things?

> Page 211: Add callout that people must update the directory-element in
> the jOOQ configuration in example.xml

> I also believe it is possible for jOOQ to have this configuration in the
> pom.xml, this might make the code more self-contained.

ditto ditto ditto

> Page 213: Odd comments in code with a lot of question marks, maybe 
> originally Russian lost in conversion?

?

> Page 231: Explicit use of a sequence, while the CUSTOMER table has a 
> trigger to do this. Also, the current user may not have usage rights on
> the sequence.

> Page 277: The fbjavaex.zip sources contain Russian comments and the 
> webpage displayed by the project is a mix of Russian and English, it 
> would be helpful if this is replaced with English.

Denis has fixed this.

> The documentation contains sources and screenshots that do have English
> where the example project has Russian, so maybe the wrong example zip 
> was published?

Nope.  It was waaaay more complicated than that. ;-)

BTW, I recommended Tracker tickets for changes, etc., as our
notification setup from github doesn't seem to be working.  Besides,
the tracker tickets are more accessible to anyone who wants to follow
changes.  Remember, Tracker isn't just for bugs.

Notice, too, that there is a Document History chapter.  It would be
highly useful if you would add a row to that for each batch of changes
you do, with a link to the Tracker ticket, where applicable.  The
points you have made concerning the Java section will be more or less
applicable to the other platforms as well.  Furthermore, we must hope
that others will come along with sections for other platforms.

Helen

[Firebird-docs] Comments on Firebird 3 Developers's guide

[Mark R. <ma...@la...>]

Great it is now released!

Some comments on things I noticed when reading (Version 1.000, PDF 
physical page numbers, not print page numbers). I only read the 
introduction and the Java part (I'm biased ;):

Page 9: "About the Author" doesn't say much about the author, add a 
small biography?

Page 15: Note on use of identity column in Firebird 3 should mention 
that creating the sequence and trigger is not necessary if using a 
GENERATED BY DEFAULT AS IDENTITY clause

Page 15: Usage of BLOB SUB_TYPE 1 SEGMENT SIZE 80 is curious: a. 
SUB_TYPE 1, better would be SUB_TYPE TEXT (more readable/explicit), and 
b. as far as I'm aware SEGMENT SIZE has been deprecated, and doesn't 
even do anything except maybe for ESQL-usage, which isn't covered in 
this guide. I think it should be replaced with just BLOB SUB_TYPE TEXT 
to avoid promoting outdated practices.

Page 22: SP_ADD_INVOICE_LINE generates an id for invoice_line_id, but 
there is also a trigger that does this. Removing this would also remove 
the need for the grant usage to the stored procedure.

Page 27: Name of the zip (and the database) is rather generic, can we 
use a more specific name (eg devguide-example.fdb, and 
fb_devguide_db_3_0.zip)?

Page 204: How are we going to handle version updates of dependencies? 
For example Jaybird 3.0.0 has already been superseded with version 
3.0.3. And current latest jOOQ version is 3.10.5, latest Spring is 
5.0.4, (or 4.3.14 for 4.x), etc.

Just updating could break examples, but we may want to add a note that 
people should check if they need to use newer versions.

Page 206: It might be helpful to add the jetty-maven-plugin. This allows 
people to run the example project without having to deploy it (manually) 
to tomcat or another servlet engine.

Just add to the list of plugins:

             <plugin>
                 <groupId>org.eclipse.jetty</groupId>
                 <artifactId>jetty-maven-plugin</artifactId>
                 <version>9.4.8.v20171121</version>
             </plugin>

Then running the example application is just a matter of using

mvn jetty:run

from the commandline (or executing this goal from within your IDE), and 
opening http://localhost:8080/ in your browser.

Page 211: Add callout that people must update the directory-element in 
the jOOQ configuration in example.xml

I also believe it is possible for jOOQ to have this configuration in the 
pom.xml, this might make the code more self-contained.

Page 213: Odd comments in code with a lot of question marks, maybe 
originally Russian lost in conversion?

Page 231: Explicit use of a sequence, while the CUSTOMER table has a 
trigger to do this. Also, the current user may not have usage rights on 
the sequence.

Page 277: The fbjavaex.zip sources contain Russian comments and the 
webpage displayed by the project is a mix of Russian and English, it 
would be helpful if this is replaced with English.

The documentation contains sources and screenshots that do have English 
where the example project has Russian, so maybe the wrong example zip 
was published?

I haven't dug to deep in the actual source code, I might have some more 
comments on that later ;)

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Issue DOC-129 resolved.

[Mark R. <ma...@la...>]

On 20-2-2018 21:25, Norman Dunbar wrote:
> Evening All,
> 
> consider the B_Release branch now up to date as far as gfix is concerned.
> 
> I wasn't aware that I had write privileges on the main repository, hence 
> why I created a fork. I'll know next time.
> 
> Anyone got Sergei's email address as I need to send him my ssh key 
> again. Thanks.

Sergey Mereutsa <se...@dq...>

PS Interesting, it looks like SourceForge still has hickups.. your mail 
(and one of mine) had been stuck for 8-9 days.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Issue DOC-129 resolved.

[Mark R. <ma...@la...>]

On 19-2-2018 00:56, Paul Vinkenoog wrote:
> Hi all,
> 
> [ about committing to B_Release ]
> 
>> Depending on the exact needs, it might take some advanced git-fu, and
>> the simplest solution may turn out to be to just copy the latest state
>> and commit that to B_Release, without merging the specific file-history
>> on the branch.
> 
> And that's exactly how we're supposed to do it, even in the CVS days:
> 
> Once a document reaches a publishable state (again), you copy it to
> B_Release, overwriting the current content (which represents the
> previous publishable state of that document).
> 
> This way, B_Release's head always contains the most recent buildable
> and publishable version of every manual.

Ok, assuming the local master is up-to-date and you are on branch 
B_Release, you can use

git checkout master <path-of-file>

Path of file is relative to your current position in the repository. 
This will copy the file exactly as it is on the HEAD of master, without 
commit history.

As far as I know this would need to be done for each file individually, 
which may not be ideal for larger manuals.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Issue DOC-129 resolved.

[Norman D. <No...@du...>]

Evening All,

consider the B_Release branch now up to date as far as gfix is concerned.

I wasn't aware that I had write privileges on the main repository, hence 
why I created a fork. I'll know next time.

Anyone got Sergei's email address as I need to send him my ssh key 
again. Thanks.


Cheers,
Norm.




-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

[Firebird-docs] [FirebirdSQL/firebird-documentation] c316c3: DOC-129 Resolved. Copied to B_Release.

[Norman D. <no...@du...>]

  Branch: refs/heads/B_Release
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: c316c34134a188258c80715b41507c565f087ec4
      https://github.com/FirebirdSQL/firebird-documentation/commit/c316c34134a188258c80715b41507c565f087ec4
  Author: Norman Dunbar <no...@du...>
  Date:   2018-02-20 (Tue, 20 Feb 2018)

  Changed paths:
    M src/docs/firebirddocs/fbutil_gfix.xml

  Log Message:
  -----------
  DOC-129 Resolved. Copied to B_Release.

[Firebird-docs] [FirebirdSQL/firebird-documentation] 40631d: removed last updated info

[Popa M. A. <ma...@gm...>]

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: 40631d70ea73eeee0f239382ee626fb23407ccf4
      https://github.com/FirebirdSQL/firebird-documentation/commit/40631d70ea73eeee0f239382ee626fb23407ccf4
  Author: Popa Marius Adrian <ma...@gm...>
  Date:   2018-02-21 (Wed, 21 Feb 2018)

  Changed paths:
    M ReadMe

  Log Message:
  -----------
  removed last updated info

removed last updated info

git history is a lot more useful

Re: [Firebird-docs] Issue DOC-129 resolved.

[Paul V. <pa...@vi...>]

Hi Norman,

> I've updated the gfix manual to resolve issue DOC-129 whereby the sweep 
> interval was incorrectly defined.
>
> I've raised a pull request from my specially created branch DOC-129 for 
> the resolution.

I've just merged your commit. But since this is 'your own' doc, you might
just as well have pushed it directly, just like in days of old, when we
were using CVS and ran around in bearskin.

> While I am able to merge this fix into master, I cannot merge it into 
> B_release though. I get the impression that B_Release either didn't come 
> across correctly, or is too far out of date from Master as attempting to 
> merge my DOC-129 branch into B_release gives lots of conflict errors.

Simply copy it over and commit/push it like we decided in 2011:

>> When you're going to publish, you bluntly copy the file(s) in question
>> over their counterparts in the B_Release working copy, and commit there
>> (of course you also commit to HEAD). The advantage of this method is
>> that now you are absolutely sure that the revision in B_Release is
>> identical to the one in HEAD. You can't make subtle mistakes while
>> merging, because there's no merging and tagging involved. You just
>> bulldozer your way into the B_Release branch and drop your stuff there.
>
> I like blunt and I don't care what the cvs gurus think! ;-) This sounds
> by far the method most likely to cause the least errors! I think I'll be
> sticking with this option.


Cheers,
Paul

Re: [Firebird-docs] Issue DOC-129 resolved.

[Paul V. <pa...@vi...>]

Hi all,

[ about committing to B_Release ]

> Depending on the exact needs, it might take some advanced git-fu, and
> the simplest solution may turn out to be to just copy the latest state
> and commit that to B_Release, without merging the specific file-history
> on the branch.

And that's exactly how we're supposed to do it, even in the CVS days:

Once a document reaches a publishable state (again), you copy it to
B_Release, overwriting the current content (which represents the
previous publishable state of that document).

This way, B_Release's head always contains the most recent buildable
and publishable version of every manual.

Cheers,
Paul

[Firebird-docs] [FirebirdSQL/firebird-documentation] 5e4f2f: DOC-129 - Corrected definition of Sweep Interval.

[paulvink <328...@us...>]

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: 5e4f2f96b9d8658749682e30de5f7a20c4841663
      https://github.com/FirebirdSQL/firebird-documentation/commit/5e4f2f96b9d8658749682e30de5f7a20c4841663
  Author: Norman Dunbar <no...@du...>
  Date:   2018-02-17 (Sat, 17 Feb 2018)

  Changed paths:
    M src/docs/firebirddocs/fbutil_gfix.xml

  Log Message:
  -----------
  DOC-129 - Corrected definition of Sweep Interval.
http://tracker.firebirdsql.org/browse/DOC-129

Corrected definition of Sweep Interval to be OST - OIT and not as previously stated.


  Commit: 79eed6ba3e5a765261e744f03e970a2bdbba3044
      https://github.com/FirebirdSQL/firebird-documentation/commit/79eed6ba3e5a765261e744f03e970a2bdbba3044
  Author: paulvink <328...@us...>
  Date:   2018-02-19 (Mon, 19 Feb 2018)

  Changed paths:
    M src/docs/firebirddocs/fbutil_gfix.xml

  Log Message:
  -----------
  Merge pull request #8 from NormanDunbar/DOC-129

DOC-129 - Corrected definition of Sweep Interval.


Compare: https://github.com/FirebirdSQL/firebird-documentation/compare/a2cf3dec26c5...79eed6ba3e5a

Re: [Firebird-docs] Issue DOC-129 resolved.

[Mark R. <ma...@la...>]

On 2018-02-17 11:30, Norman Dunbar wrote:
> it's currently 10:25 UK time. My emails to the list seem to be taking
> a few days to get to the docs list at the moment, so I've no idea if
> or when you will see this!

Specifically, your mail has been stuck for close to 32 hours somewhere 
inside sourceforge, see the received timestamps:

Received: from localhost ([127.0.0.1] 
helo=sfs-ml-4.v29.lw.sourceforge.com)
	by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.89)
	(envelope-from <fir...@li...>)
	id 1enTOv-0000Pk-DP; Sun, 18 Feb 2018 18:09:25 +0000
Received: from siteops-lb-1.v20.lw.sourceforge.com ([172.30.20.11]
  helo=mx.sourceforge.net)
  by sfs-ml-4.v29.lw.sourceforge.com with esmtps
  (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89)
  (envelope-from <No...@du...>) id 1emzkw-00099H-Vd
  for fir...@li...; Sat, 17 Feb 2018 10:30:10 
+0000

Re: [Firebird-docs] Issue DOC-129 resolved.

[Mark R. <ma...@la...>]

On 2018-02-17 11:30, Norman Dunbar wrote:
> Morning All,
> 
> it's currently 10:25 UK time. My emails to the list seem to be taking
> a few days to get to the docs list at the moment, so I've no idea if
> or when you will see this!

At the beginning of the week, SourceForge moved datacenters, and 
something went wrong pretty badly, it should have been fixed Friday (or 
maybe yesterday), as some of my messages I sent during the week were 
delivered, but some of the messages I sent yesterday have only now shown 
up. Chances are there are still some lingering problems, or maybe 
DNS-related issues.

> I've updated the gfix manual to resolve issue DOC-129 whereby the
> sweep interval was incorrectly defined.
> 
> I've raised a pull request from my specially created branch DOC-129
> for the resolution.
> 
> While I am able to merge this fix into master, I cannot merge it into
> B_release though. I get the impression that B_Release either didn't
> come across correctly, or is too far out of date from Master as
> attempting to merge my DOC-129 branch into B_release gives lots of
> conflict errors.
> 
> $git merge DOC-129
> 
[..]
> 
> Git status gives screens and screens of new files to be added, and 9
> modified files, from the 10 files listed above, to have their
> conflicts fixed.
> 
> Listed above is fbutils_gfix.xml but it isn't listed in the git status
> output as a conflicting file. Oh joy!  It also doesn't have any
> conflict markers.
> 
> $git merge --abort cleaned up the mess from the merge.
> 
> The same happens if I experiment with merging master into B_Release
> (in my local copy of my fork - so no damage done!) Another --abort
> cleaned up there too.
> 
> Has anyone else been able to merge new documents or changes into 
> B_Release?

It looks like up to now, changes were cherry picked by manually copying 
them unto the branch, or at least, most commits on B_Release seem to 
copy a specific state onto release, without retaining history from 
master. This probably explains why merging a branch from master onto 
B_Release doesn't work.

I'm not sure if there is an easy way to fix this with git in a way that 
matches with how B_Release is used. Maybe Paul or Helen could describe 
the logical steps how B_Release is supposed to be used, and we can then 
see how we can best do that with git.

Depending on the exact needs, it might take some advanced git-fu, and 
the simplest solution may turn out to be to just copy the latest state 
and commit that to B_Release, without merging the specific file-history 
on the branch.

Mark

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Mark R. <ma...@la...>]

On 2018-02-16 19:13, Norman Dunbar wrote:
> On 14/02/18 08:01, Mark Rotteveel wrote:
> 
>>> Q3. Anyone else seen this? With a clean build? Oracle Java 9?
>> 
>> The build doesn't work with Java 9. In any case, it works OK for me 
>> with Java 8, on Windows.
> 
> Ok, good news there. I've downgraded Java to Java 8, removed the
> fork="true" additions and built the docs again. No problems. So I'll
> stick with Java 8 for now.
> 
> I might even try to learn some Ant stuff! Maybe. Perhaps.
> 
> 
>> A possible workaround is to add dir="${html.dir}" to the java task in 
>> the html task (when fork="true", this will use that as the current 
>> working directory), I haven't tested it though. However, I'm not sure 
>> if forking may cause other issues, so maybe we should tread carefully 
>> here.
> 
> No worries. I didn't try this option as the Java 8 one worked fine.
> I've reverted the build.xml back to how it was and it's fine. As you
> mention, what other issues could have been unleashed!
> 
> 
>> In any case, maybe we should look at updating ant (and maybe some of 
>> the other dependencies).
> 
> We need an Ant guru then! :-)

I have a bit of experience with ant. I was considering to do some 
experiments to either upgrade ant, or maybe try and replace the ant 
build file with a gradle build file, and at the same time remove the 
need for the separate libs.zip and tools.zip download (both Ant and 
Gradle can download dependencies on demand from a remote repository). 
That might also make it easier to upgrade things in the future.

But it is a matter of time and energy, and I'm a bit low on both at the 
moment.

Mark

[Firebird-docs] Issue DOC-129 resolved.

[Norman D. <No...@du...>]

Morning All,

it's currently 10:25 UK time. My emails to the list seem to be taking a 
few days to get to the docs list at the moment, so I've no idea if or 
when you will see this!


I've updated the gfix manual to resolve issue DOC-129 whereby the sweep 
interval was incorrectly defined.

I've raised a pull request from my specially created branch DOC-129 for 
the resolution.

While I am able to merge this fix into master, I cannot merge it into 
B_release though. I get the impression that B_Release either didn't come 
across correctly, or is too far out of date from Master as attempting to 
merge my DOC-129 branch into B_release gives lots of conflict errors.

$git merge DOC-129

Auto-merging src/docs/refdocs/refdocs.xml
CONFLICT (content): Merge conflict in src/docs/refdocs/refdocs.xml

Auto-merging src/docs/refdocs/langref/langrefupd25.xml
CONFLICT (content): Merge conflict in 
src/docs/refdocs/langref/langrefupd25.xml

Auto-merging src/docs/refdocs/langref/langrefupd21.xml
CONFLICT (content): Merge conflict in 
src/docs/refdocs/langref/langrefupd21.xml

Removing src/docs/refdocs/langref/langref25.xml

Auto-merging src/docs/papers/firebird_php_linux.xml
CONFLICT (content): Merge conflict in src/docs/papers/firebird_php_linux.xml

Auto-merging src/docs/papers/firebird_enterprise.xml
CONFLICT (content): Merge conflict in 
src/docs/papers/firebird_enterprise.xml

Auto-merging src/docs/firebirddocs/ubuntu-setup.xml
CONFLICT (content): Merge conflict in src/docs/firebirddocs/ubuntu-setup.xml

Auto-merging src/docs/firebirddocs/quickstartguide-3.xml
CONFLICT (add/add): Merge conflict in 
src/docs/firebirddocs/quickstartguide-3.xml

Auto-merging src/docs/firebirddocs/quickstartguide-2.5.xml

Auto-merging src/docs/firebirddocs/fbutil_isql.xml
CONFLICT (content): Merge conflict in src/docs/firebirddocs/fbutil_isql.xml

Auto-merging src/docs/firebirddocs/fbutil_gfix.xml
CONFLICT (content): Merge conflict in src/docs/firebirddocs/fbutil_gfix.xml

Auto-merging src/docs/firebirddocs/docbuilding-howto.xml
CONFLICT (content): Merge conflict in 
src/docs/firebirddocs/docbuilding-howto.xml

Removing ChangeLog
Automatic merge failed; fix conflicts and then commit the result.


Git status gives screens and screens of new files to be added, and 9 
modified files, from the 10 files listed above, to have their conflicts 
fixed.

Listed above is fbutils_gfix.xml but it isn't listed in the git status 
output as a conflicting file. Oh joy!  It also doesn't have any conflict 
markers.

$git merge --abort cleaned up the mess from the merge.



The same happens if I experiment with merging master into B_Release (in 
my local copy of my fork - so no damage done!) Another --abort cleaned 
up there too.

Has anyone else been able to merge new documents or changes into B_Release?


Cheers,
Norm.

-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Norman D. <No...@du...>]

Testing testing.

Apologies for the noise.

A few emails I sent to the list yesterday have yet to arrive - they are 
not in spam either. Helen's reply to a query in FB-Support yesterday 
arrived here after the OP had responded to Helen.

It can't be a moderation thing - as Helen wouldn't normally have to 
moderate herself!

Sometimes, technology winds me up!


Cheers,
Norm.
-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Norman D. <No...@du...>]

On 14/02/18 08:01, Mark Rotteveel wrote:

>> Q3. Anyone else seen this? With a clean build? Oracle Java 9?
> 
> The build doesn't work with Java 9. In any case, it works OK for me with 
> Java 8, on Windows.

Ok, good news there. I've downgraded Java to Java 8, removed the 
fork="true" additions and built the docs again. No problems. So I'll 
stick with Java 8 for now.

I might even try to learn some Ant stuff! Maybe. Perhaps.


> A possible workaround is to add dir="${html.dir}" to the java task in 
> the html task (when fork="true", this will use that as the current 
> working directory), I haven't tested it though. However, I'm not sure if 
> forking may cause other issues, so maybe we should tread carefully here.

No worries. I didn't try this option as the Java 8 one worked fine. I've 
reverted the build.xml back to how it was and it's fine. As you mention, 
what other issues could have been unleashed!


> In any case, maybe we should look at updating ant (and maybe some of the 
> other dependencies).

We need an Ant guru then! :-)


Thanks for your help.


Cheers,
Norm.


-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Norman D. <No...@du...>]

On 14/02/18 08:11, Mark Rotteveel wrote:

 >> ...
>> I've cleaned out the known_hosts entry, as advised, and reconnected to 
>> add the new one back in, but now I'm asked for a password.
>>
>> Do I need to send Sergey my public key again?
> 
> Possibly, it could also mean you're not offering the (right) SSH key.
> 

Hmm. Unfortunately, it's the only key I've needed to use. I have been 
able in the past to upload documents but I suspect that when the servers 
"changed" or whatever happened to cause my ssh connection to warn me 
about the server having changed, might be the cause. Perhaps.

I shall resent Sergey my public key, just in case. If I can find his 
email address of course!


Cheers,
Norm.


-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Paul V. <pa...@vi...>]

Norman wrote:

> I've done a "./build.sh docs" and everything has built ok, except, the 
> multi-page HTML docs which don't go into dist/html, they just get built 
> into the root folder. This truly messes up a "git status" command as all 
> the files are listed.
>
> Q3. Anyone else seen this? With a clean build? Oracle Java 9?
>
> I did clear everything out again, from the root folder, and did a 
> "./build.sh html" and got exactly the same mess. I can manually move 
> things into dist, but I can't see anything in the build.xml that might 
> be causing this - but I'm not an Ant guru I'm afraid.
>
> Q4. Any clues?

Sorry, no. I'm not an Ant guru either and it's a rather complicated tool,
configuration-wise.

I'd like to look into this but it won't be before Friday.

Cheers,
Paul

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Paul V. <pa...@vi...>]

Hi Norman,

> Q2. Also, as we still copying everything into the B_Release branch?

Once a document is publishable, yes, that's the idea.

Cheers,
Paul

Re: [Firebird-docs] GitHub, Build bugs with Java 9, Assorted Questions!

[Mark R. <ma...@la...>]

On 13-2-2018 22:00, Norman Dunbar wrote:
> On 13/02/18 20:31, Norman Dunbar wrote at great length ....
> 
> Q5. I appear to be no longer allowed to login to 
> www...@cm...:
> 
> The RSA host key for cms.firebirdsql.org has changed,
> and the key for the corresponding IP address 78.47.64.209
> is unknown. This could either mean that
> DNS SPOOFING is happening or the IP address for the host
> and its host key have changed at the same time.
> 
> 
> I've cleaned out the known_hosts entry, as advised, and reconnected to 
> add the new one back in, but now I'm asked for a password.
> 
> Do I need to send Sergey my public key again?

Possibly, it could also mean you're not offering the (right) SSH key.

Mark
-- 
Mark Rotteveel