February 2018 - Tei-council

TEI Council @ DH?
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Feb '18

11 Feb '18

Dear all, taking up James' suggestion to promote the TEI by doing more workshops e.g. at the main DH conference, I want to ask if anyone would be interested to submit a TEI-related workshop proposal for the DH 2018 conference in Mexico? Deadline is February 16, I know, not much time... It thought of an ODD workshop, a Hackathon, an introductory training, TEI and LOD, etc. Best wishes, Martina Martina Scholger Centre for Information Modelling - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz AUSTRIA

9 10

Re: [tei-council] TEI SIG Newspapers and Periodicals
by James Cummings 08 Feb '18

08 Feb '18

Hi Martina, Getting them to at least give a couple short paragraphs of description (like many of the other SIGs have on their pages (c.f. Computer-Mediated Communciation, Correspondence, East Asian/Japanese) would be good since they have to get that kind of thing together anyway to put on that page. I can't imagine that we'd turn them down though. ;-) Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 06 February 2018 18:27:27 To: tei-council(a)lists.tei-c.org Subject: [tei-council] WG: TEI SIG Newspapers and Periodicals Dear all, I received an email from Dario Kampkaspar who is asking for the official approval of the SIG on Newspapers and Periodicals. The minutes from their meeting in Victoria contain the main interests of the SIG, see https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…. I read through the SIG rules and wonder if the minutes are enough for a decision or if I should ask him for a summarized proposal / mission statement? I tend towards the latter. What do you think about it and what is the standard procedure? Best, Martina Von: Kampkaspar, Dario [mailto:Dario.Kampkaspar@oeaw.ac.at] Gesendet: Donnerstag, 1. Februar 2018 10:56 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Betreff: TEI SIG Newspapers and Periodicals Liebe Martina, wie ich gerade über Ingo Börner hörte, ist wohl die Meldung der SIG damals "untergegangen". Damit Du hierzu auch etwas vorliegen hast, hier meine damalige Mail: this is to officially let you and Council know that the SIG on newspapers and periodicals asks to be formally recognized by the TEI. As I was the one to bring the topic back up, I was chosen as convener. We have met yesterday and discussed our work for the next year. The minutes of our meeting, which include our key interests, can be found under https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1… [https://lh5.googleusercontent.com/aJaB9OCaX6iwuk_qFT-tSmzCr0uMQBl1iBFc4K6is…]<https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…> notes2017-11-14 - Google Docs<https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…> docs.google.com Newspapers SIG Present Dario Kampkaspar (DK) Sarah Stanley (SS) Alison Chapman (AC) Paul Schaffner (PS) Martin Holmes (MH) Syd Bauman (SB) Ingo Boerner (IB) Minutes How to encode periodicity? How to name different constituents of a newspaper? Interests of the group Periodical Victorian poe... If you need any additional information, please contact me at any time. Wenn Du weitere Info brauchst, kannst Du mich natürlich kontaktieren, per Mail oder Telefon. Herzlichen Dank und beste Grüße aus Wien, Dario -- tei-council mailing list tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

3 2

[romajs] macroSpec[@type='dt'] vs dataSpec
by Raffaele Viglianti 08 Feb '18

08 Feb '18

Hi all, I'm facing a bit of a conundrum related to datatypes and RomaJS and need your input. I'll try my best to explain it. 1. Currently, there are two ways of defining datatypes in ODD: macroSpec[@type='dt'] and dataSpec. Is macroSpec[@type='dt'] going to be deprecated, or are both systems going to be viable? 2. The TEI source, and therefore p5subset.xml currently defines datatypes BOTH with macroSpec[@type='dt'] (e.g. data.certainty) and dataSpec (e.g. teidata.certainty). Why? Is one going to go away eventually? 3. What should Roma do? This is a multifaceted problem, but let's focus on elementSpec/content for now since this is what I'm dealing with at the moment. 3a: when creating/editing a macroRef, Roma will list all macroSpecs for the @key value, including those with @type='dt'. I'm inclined to keep this, because likely people who created new datatypes (which does happen) have done so with macroSpec[@type='dt'] for a while before dataSpec (and after). 3b: a p5subset specific issue: unless the macroSpec/dataSpec duplicates are not fixed, users will see them both show up. I don't think this is good: new ODDs should use dataSpec/dataRef, right? But at the same time I don't want Roma to not be able to handle existing ODDs with macroRefs to datatypes. Help. Raff

2 2

Re: [tei-council] [romajs] macroSpec[@type='dt'] vs dataSpec
by James Cummings 08 Feb '18

08 Feb '18

I think agree with Syd on these issues. Also 3a I would not list datatypes created with macroSpec, and with 3b agree that RomaJS should only handle new pure ODD and thus dataSpec/dataRef. I'd be perfectly happy for when I try to load an ODD into RomaJS that it complain and say the ODD uses old ways of doing things (such as RelaxNG, macroSpec for datatypes, etc.) and say those need to be fixed first or something. There have got to only be a limited number of things that are fairly straightforward to test for, right? Best wishes, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: tei-council-bounces(a)lists.tei-c.org <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 08 February 2018 00:04:16 To: tei-council(a)lists.tei-c.org Subject: Re: [tei-council] [romajs] macroSpec[@type='dt'] vs dataSpec Fast thoughts: 1. Yup. 2. Partially: <dataSpec> is (correctly) used for 'teidata.*' datatypes <macroSpec> is used (under depricatoin) for 'data.*' datatypes -- they expire in October <macroSpec> is used for 'macro.*' macros. (Should that be done w/ <dataSpec>? Idunno off top of head.) 3a. I disagree. When dealing w/ <macroRef>, I say consider only <macroSpec>s with type="pe". 3b. Yes, new Roma should not be able to handle existing ODDs that use <macroRef> to point to 'data.*' datatypes, thus forcing users to switch. (Which is good, as they will *have* to switch in 8 months, anyway.) > I'm facing a bit of a conundrum related to datatypes and RomaJS and need > your input. I'll try my best to explain it. > > 1. Currently, there are two ways of defining datatypes in ODD: > macroSpec[@type='dt'] and dataSpec. Is macroSpec[@type='dt'] going to be > deprecated, or are both systems going to be viable? > > 2. The TEI source, and therefore p5subset.xml currently defines datatypes > BOTH with macroSpec[@type='dt'] (e.g. data.certainty) and dataSpec (e.g. > teidata.certainty). Why? Is one going to go away eventually? > > 3. What should Roma do? This is a multifaceted problem, but let's focus on > elementSpec/content for now since this is what I'm dealing with at the > moment. > > 3a: when creating/editing a macroRef, Roma will list all macroSpecs for the > @key value, including those with @type='dt'. I'm inclined to keep this, > because likely people who created new datatypes (which does happen) have > done so with macroSpec[@type='dt'] for a while before dataSpec (and after). > > 3b: a p5subset specific issue: unless the macroSpec/dataSpec duplicates are > not fixed, users will see them both show up. I don't think this is good: > new ODDs should use dataSpec/dataRef, right? But at the same time I don't > want Roma to not be able to handle existing ODDs with macroRefs to > datatypes. -- tei-council mailing list tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived

1 0

https access to Guidelines
by Lou Burnard 07 Feb '18

07 Feb '18

Is there any good reason why the TEI stylesheets and TEI releases in general should not be served using https rather than http? It would make it easier to integrate links (e.g. to the TEI provided CSS) into a document which is going to be served from a server that requires use https, such as for example github pages.

1 0

WG: TEI SIG Newspapers and Periodicals
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Feb '18

06 Feb '18

Dear all, I received an email from Dario Kampkaspar who is asking for the official approval of the SIG on Newspapers and Periodicals. The minutes from their meeting in Victoria contain the main interests of the SIG, see https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…. I read through the SIG rules and wonder if the minutes are enough for a decision or if I should ask him for a summarized proposal / mission statement? I tend towards the latter. What do you think about it and what is the standard procedure? Best, Martina Von: Kampkaspar, Dario [mailto:Dario.Kampkaspar@oeaw.ac.at] Gesendet: Donnerstag, 1. Februar 2018 10:56 An: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Betreff: TEI SIG Newspapers and Periodicals Liebe Martina, wie ich gerade über Ingo Börner hörte, ist wohl die Meldung der SIG damals "untergegangen". Damit Du hierzu auch etwas vorliegen hast, hier meine damalige Mail: this is to officially let you and Council know that the SIG on newspapers and periodicals asks to be formally recognized by the TEI. As I was the one to bring the topic back up, I was chosen as convener. We have met yesterday and discussed our work for the next year. The minutes of our meeting, which include our key interests, can be found under https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1… [https://lh5.googleusercontent.com/aJaB9OCaX6iwuk_qFT-tSmzCr0uMQBl1iBFc4K6is…]<https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…> notes2017-11-14 - Google Docs<https://docs.google.com/document/d/1i0ow7-rfjg2OLwuyzXlk-u7P0nWLN5MP9VWUed1…> docs.google.com Newspapers SIG Present Dario Kampkaspar (DK) Sarah Stanley (SS) Alison Chapman (AC) Paul Schaffner (PS) Martin Holmes (MH) Syd Bauman (SB) Ingo Boerner (IB) Minutes How to encode periodicity? How to name different constituents of a newspaper? Interests of the group Periodical Victorian poe... If you need any additional information, please contact me at any time. Wenn Du weitere Info brauchst, kannst Du mich natürlich kontaktieren, per Mail oder Telefon. Herzlichen Dank und beste Grüße aus Wien, Dario

2 1

Cologne F2F: invited expert Susanne Haaf
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Feb '18

05 Feb '18

Dear Board, I would like to submit a request on behalf of the Council. Since our next F2F meeting in Cologne will take place just before the annual German-speaking Digital Humanities conference, we would like to take the opportunity to invite an external expert - Susanne Haaf - to work with us on a number of issues raised by the LingSIG. I would therefor ask you if the TEI could cover one overnight stay for her. Best wishes, Martina Martina Scholger Centre for Information Modelling - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz AUSTRIA

1 0

Cologne f2f, invited expert Susanne Haaf
by Peter Stadler 05 Feb '18

05 Feb '18

Dear all, as you might know/remember we have a bunch of pending linSIG issues and we invited Susanne Haaf as "(external) expert" to work with us on those. During the last config call we decided on Sunday afternoon as a slot for these issues; Susanne could make it on Sunday (hurray) but would need reimbursement for that one overnight stay. Otherwise she’d be available on Monday afternoon for free. I remember that some people need to leave on Monday noon(?) and miss the afternoon session – is that correct? Next question: would there be funding for one night for Susanne if we’d stick with the Sunday? Have there be any „invited experts“ before and are there any rules of procedure? Best Peter

2 1

Build failed in Jenkins: TEIP5-dev #3017
by Victoria TEI Jenkins 02 Feb '18

02 Feb '18

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/3017/display/redirect?page=cha…> Changes: [s.bauman] tei_customization fixes: Eeek! It's not showing up in the oXygen ------------------------------------------ [...truncated 10.43 KB...] fakeroot debian/rules binary dh_testdir dh_testroot dh_installdirs install -d <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/debian-tei-p5-doc/debian…> (cd ..; make VCS=git INJENKINS=true XSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> PREFIX=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/debian-tei-p5-doc/debian…> install-doc) make[1]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> BUILD: Make distribution directory for doc rm -rf release/tei-p5-doc* mkdir -p release/tei-p5-doc/share/doc/tei-p5-doc/en cp VERSION release/tei-p5-doc/share/doc/tei-p5-doc BUILD: Make web pages for release notes for i in ReleaseNotes/readme*xml; do \ ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -f <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> -lib Utilities/lib/saxon9he.jar -Dprofiledir=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> -Dprofile=readme \ -DinputFile=`pwd`/$i -DoutputFile=`pwd`/release/tei-p5-doc/share/doc/tei-p5-doc/`basename $i .xml`.html; \ done [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 8 seconds [echo] XSLT generate HTML files (language ${lang}) Warning: XML resolver not found; external catalogs will be ignored BUILD SUCCESSFUL Total time: 9 seconds BUILD: Make web guidelines in all supported languages make html-web ALLLANGUAGES="en es de ja ko fr it zh-TW" make[2]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> BUILD: Making HTML Guidelines for language en rm -rf Guidelines-web perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…;"> \ Utilities/guidelines.xsl.model > Utilities/guidelines.xsl if [ -n ] ; then curl -s http://www.tei-c.org/index.xml | sed 's/content="text\/html"/content="text\/html; charset=utf-8"/' | xmllint --html --noent --dropdtd --xmlout - > Utilities/teic-index.xml;fi for i in en es de ja ko fr it zh-TW ;do \ mkdir -p Guidelines-web/$i/html; \ cp odd.css guidelines.css guidelines-print.css Guidelines-web/$i/html; \ (cd Source/Guidelines/en; tar --exclude .svn -c -f - Images) | (cd Guidelines-web/$i/html; tar xf - );\ (cd webnav; tar --exclude .svn -c -f - .) | (cd Guidelines-web/$i/html; tar xf - ); \ done echo '<project basedir="." default="html" name="buildweb"><import file="antbuildweb.xml"/><target name="html">' \ > buildweb.xml for i in en es de ja ko fr it zh-TW ;do \ echo "<buildweb lang=\"$i\"/>" >> buildweb.xml; \ done echo '</target></project>' >> buildweb.xml ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/jing.jar:Utilities/lib/saxon9he.jar -f buildweb.xml -DgoogleAnalytics= [echo] Make Guidelines web pages for language en [echo] Make Guidelines web pages for language es [echo] Make Guidelines web pages for language de [echo] Make Guidelines web pages for language ja [echo] Make Guidelines web pages for language ko [echo] Make Guidelines web pages for language fr [echo] Make Guidelines web pages for language it [echo] Make Guidelines web pages for language zh-TW BUILD SUCCESSFUL Total time: 16 minutes 26 seconds # commented out for DEBUGing: rm -f buildweb.xml Utilities/teic-index.xml touch html-web.stamp make[2]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> (cd Guidelines-web; tar --exclude .svn -c -f - . ) | (cd release/tei-p5-doc/share/doc/tei-p5-doc; tar xf - ) BUILD: make PDF version of Guidelines make pdf make[2]: Entering directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> check if XeLaTeX exist /usr/bin/xelatex perl -p -e \ "s+http://www.tei-c.org/release/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…;> \ s+/usr/share/xml/tei/stylesheet+<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…;"> \ Utilities/guidelines-latex.xsl > Utilities/guidelines.xsl BUILD: build Lite version of Guidelines, then LaTeX version of Guidelines from Lite, then run to PDF using XeLaTeX Make sure you have Junicode, Arphic and Mincho fonts installed ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/../../../Stylesheets-dev…> -DXELATEX=xelatex pdfonce [echo] make LaTeX and PDF BUILD FAILED <http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5/antbuilder.xml>:158: exec returned: 1 Total time: 1 minute 56 seconds make[2]: *** [Guidelines.pdf] Error 1 make[2]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> make[1]: *** [dist-doc.stamp] Error 2 make[1]: Leaving directory `<http://teijenkins.hcmc.uvic.ca/job/TEIP5-dev/ws/P5'> make: *** [install] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1364: dpkg-buildpackage -rfakeroot -D -us -uc -nc -b -i.svn -I.svn failed make: *** [deb] Error 29 Build step 'Execute shell' marked build as failure Archiving artifacts Not sending mail to unregistered user s.bauman(a)neu.edu

1 1

Stand-Off conf call
by Peter Stadler 01 Feb '18

01 Feb '18

Dear all, just a friendly reminder that we’ll be meeting in less than an hour … I will send around the connection details soon. Best Peter

5 11