Hi, I set up a space on our server bound to the name packages.tei-c.org on 193.170.113.222 so currently the packages should be available at: #sources.list deb http://packages.tei-c.org/deb/binary ./ given the right DNS entry or /etc/hosts file The signing key fingerprint is 4C1AAD67: https://pgp.mit.edu/pks/lookup?op=get&search=0xC77BEA304C1AAD67 What I am currently struggling with is the stylesheets build, which tends to yield varying results. It does not build the documentation, because I have not oxygen on this machine. Nevertheless, I think it could be good to try whether the repo works at all. cheers, Stefan
Stefan, great work! (haven’t tested, though ;) But why are you trying to build the Stylesheets yourself and not simply fetch them from the Jenkins? Best Peter
Am 26.04.2016 um 15:38 schrieb Stefan Majewski
: Hi,
I set up a space on our server bound to the name packages.tei-c.org on 193.170.113.222
so currently the packages should be available at:
#sources.list deb http://packages.tei-c.org/deb/binary ./
given the right DNS entry or /etc/hosts file
The signing key fingerprint is 4C1AAD67: https://pgp.mit.edu/pks/lookup?op=get&search=0xC77BEA304C1AAD67
What I am currently struggling with is the stylesheets build, which tends to yield varying results. It does not build the documentation, because I have not oxygen on this machine. Nevertheless, I think it could be good to try whether the repo works at all.
cheers, Stefan -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
Hi,
wow, I just assumed that the debs would not build there, as the debs in the
main Guidelines build are not created (apart from the database). That's
useful, then I can at least see where the differences are and possibly
either take the package from jenkins.
http://jenkins.tei-c.org/job/Stylesheets-release-7.41.0/ws/
Thanks for the hint.
cheers,
Stefan
2016-04-26 21:49 GMT+02:00 Peter Stadler
Stefan,
great work! (haven’t tested, though ;)
But why are you trying to build the Stylesheets yourself and not simply fetch them from the Jenkins?
Best Peter
Am 26.04.2016 um 15:38 schrieb Stefan Majewski
: Hi,
I set up a space on our server bound to the name packages.tei-c.org on 193.170.113.222
so currently the packages should be available at:
#sources.list deb http://packages.tei-c.org/deb/binary ./
given the right DNS entry or /etc/hosts file
The signing key fingerprint is 4C1AAD67: https://pgp.mit.edu/pks/lookup?op=get&search=0xC77BEA304C1AAD67
What I am currently struggling with is the stylesheets build, which tends to yield varying results. It does not build the documentation, because I have not oxygen on this machine. Nevertheless, I think it could be good to try whether the repo works at all.
cheers, Stefan -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
2016-04-26 22:19 GMT+02:00 Stefan Majewski
Ok put in the packages from there now, as I don't have oxygen and think that some people like the documentation. In fact, the Stylesheets, links and scripts have all been in place. Building the other debs on Jenkins is probably too slow, right? Otherwise that would be the smoothest from a release-tech perspective. cheers, Stefan
participants (2)
-
Peter Stadler
-
Stefan Majewski