New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF link missing? #747

Open
Vangelis66 opened this Issue Apr 24, 2017 · 16 comments

Comments

Projects
None yet
10 participants
@Vangelis66
Copy link

Vangelis66 commented Apr 24, 2017

The easiest way is simply to let us do it. A robot is standing by to look for new work on the main branch
and automatically build it for everyone.

You can find the current builds on http://git-scm.com/book.

... Apologies for being ...thick (!), but once I visit referenced link I fail to spot "current builds";
I distinctly remember a pdf link being available there, last time I visited I fetched file "progit-en.1067.pdf" with a PDF modification timestamp of 20160309 (still on disk today). Is this link not available anymore?
FWIW, https://github.com/progit/progit2/releases only provide progit-2.0.0.pdf with a PDF modification timestamp of 20141021.

EDIT: Thanks to the Internet Archive, it appears the download links were removed after 20170309 (last capture with the links showing up; PDF link points to file progit-en.1084.pdf with a 20160323 PDF timestamp) ; so, if this was intentional, references on README.asc should be removed now...

@jnavila

This comment has been minimized.

Copy link
Member

jnavila commented Apr 24, 2017

True, true. Much of the work took place in the git-scm repo, but we forgot to update the README here.

@Vangelis66

This comment has been minimized.

Copy link

Vangelis66 commented Apr 24, 2017

Much of the work took place in the git-scm repo

So I've searched and indeed found git/git-scm.com#983 that was merged on 20170311;
is that a permanent removal and if not, any speculation as to when the PDF link'll be restored?
Have always been a fan of the PDF format of the Git Book ...
Thanks.

@jnavila

This comment has been minimized.

Copy link
Member

jnavila commented Apr 25, 2017

Unfortunately, the building robot is no longer available. We replaced it with a direct publishing to the git-scm website, but all ebooks are missing. I didn't find a simple way to generate the pdf. What you can do is build the PDF from the repo, the scripts for this are quite accessible.

@pavel-mironchik

This comment has been minimized.

Copy link

pavel-mironchik commented Apr 30, 2017

Here are ebooks builded at 2017/05/01: https://drive.google.com/drive/folders/0BzAMsjLtoLg-NFFHdGdBb3Qyd1E?usp=sharing

@Vangelis66

This comment has been minimized.

Copy link

Vangelis66 commented Apr 30, 2017

@brunen9

Many thanks for those 👍
Being on Windows (Vista), it's quite cumbersome to generate the PDF version locally
from the repo scripts ;-( ; so your offerings are highly appreciated!

Cheers

@MichaelTiernan

This comment has been minimized.

Copy link

MichaelTiernan commented May 17, 2017

Thanks to brunen9 for providing the prebuilt books.
May I point out that the README file in the source doesn't specify the tools the building the books requires.

I've added asciidoctor to my system and have yet to find the "bundle" command.

It would be nice/important to have a prerequisite section.

@jnavila

This comment has been minimized.

Copy link
Member

jnavila commented May 17, 2017

@MichaelTiernan You don't need bundle in fact. That's some reminiscence of the "Ruby everywhere" Motto that was hitting at the time of starting the book.

Just type:

asciidoctor-pdf progit.asc

And enjoy !

@sivaraam

This comment has been minimized.

Copy link
Contributor

sivaraam commented May 18, 2017

Should the README be updated to reflect the current state ?

@justinclift

This comment has been minimized.

Copy link
Contributor

justinclift commented May 19, 2017

@jnavila Awesome, that's good info. Would it be feasible to update the README.md with that (and any other similar bits), as per @sivaraam's question above?

Asking because I tried building on FreeBSD earlier today, which barfed as one of the Ruby gems needed for the ebook generation refused to build. "Host OS not supported" or some similar message (it was a few hours ago).

Having that info instead of the single bundle exec command would have helped in my situation. 😄

@tyrann0us

This comment has been minimized.

Copy link

tyrann0us commented Jul 28, 2017

progit2.zip @ c337c6a.

Contains:
progit.epub
progit.html
progit.mobi
progit.pdf

@jtcmedia

This comment has been minimized.

Copy link

jtcmedia commented Aug 18, 2017

In case this is of use to someone, I made a quick and dirty YAML CI file that runs on GitLab https://gitlab.com/jc-camosun/pro-git-book-pdf-generator that generates the PDF. The generator generates a new PDF daily.

@Vangelis66

This comment has been minimized.

Copy link

Vangelis66 commented Aug 18, 2017

This is awfully nice Jason 👍

Downloads -> Artifacts -> Download 'pdf' and unzipping yields a fine progit.pdf file...

@TimoSolo

This comment has been minimized.

Copy link

TimoSolo commented Aug 30, 2017

Unfortunately, the building robot is no longer available. We replaced it with a direct publishing to the git-scm website, but all ebooks are missing.
~ @jnavila

Is someone working on a bot to build the ebooks automatically? It would be a great contribution to humanity! :D I've scoured the web but can't find any that use the latest version.

If I get >10 👍 I will attempt to build it..

@clfsoft

This comment has been minimized.

Copy link

clfsoft commented Sep 9, 2017

the generated pdf book missing the index part

@sivaraam

This comment has been minimized.

Copy link
Contributor

sivaraam commented Sep 12, 2017

In case this is of use to someone, I made a quick and dirty YAML CI file that runs on GitLab https://gitlab.com/jc-camosun/pro-git-book-pdf-generator that generates the PDF.

Thanks for the great work! I just made a 'Merge request' to fix a small regression as a consequence of d2152ec

Anyone should be able to run the Pipeline to re-generate it if needed.

@jtcmedia Only part of this statement seems to be true. I could access the Pipeline but I could run it only in my fork of your repository. Am I missing something?

@jtcmedia

This comment has been minimized.

Copy link

jtcmedia commented Sep 13, 2017

@sivaraam thanks for the merge request. My bad, that's right, you can't run the Pipeline. I've scheduled it to run daily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment