Re: gtk-doc-1.22 change wrt to tmpl builds

[Milan Crha]

On Sun, 2015-04-26 at 21:38 +0200, Stefan Sauer wrote:
> The upcoming gtk-doc-1.22 release will switch the default makefile
> flavour from "legacy" to "no-tmpl".

Hi,
I'm trying to build evolution-data-server 3.16.2 against gtk-doc-1.22
and it fails [1]. It has its configure.ac with this line:
   GTK_DOC_CHECK([1.14],[--flavour no-tmpl])
thus should not be affected by the change. Trying to build against
gtk-doc 1.21 works flawlessly.

I'm wondering, could there be a regression in the gtk-doc 1.22, or is
there anything I should fix in evolution-data-server? The thing is that
if I understand the errors properly, then it's in the generated files,
which are mostly out of my hands.
Thanks and bye,
Milan

[1] The actual build errors with gtk-doc 1.22:

  DOC   Building HTML
../xml/e-source-webdav.xml:125: parser error :
Opening and ending tag mismatch: note line 125 and para

   ^
../xml/e-source
-webdav.xml:131: parser error : Opening and ending tag mismatch:
para line 131 and note

 ^
../xml/e-source-webdav.xml:157: parser error : Opening and ending tag 
mismatch: note line 157 and para

   ^
../xml/e-source-webdav.xml:163: parser error : Opening and ending tag 
mismatch: para line 163 and note

 ^
../eds-docs.sgml:118: element include: XInclude error : could not load 
../xml/e-source-webdav.xml, and no fallback was found
../xml/e-book-client-cursor.xml:244: parser error : Opening and ending tag 
mismatch: programlisting line 242 and para
gdouble percent;
   ^
../xml/e-book-client-cursor.xml:245: parser error : xmlParseEntityRef: no 
name
// Fetch the position & total
 ^
../xml/e-book-client-cursor.xml:256: parser error : Sequence ']]>' not 
allowed in content
// Let the user know the percentage of contacts in the list
  ^
../xml/e-book-client-cursor.xml:256: parser error : Sequence ']]>' not 
allowed in content
update_percentage_of_list_browsed (user_interface, 
percent);]]>
   ^
../xml/e-data-book-cursor.xml:160: parser error : StartTag: invalid element 
name
 for (i = 0; i < cursor->n_sort_fields; i++) {
^
../xml/e-data-book-cursor.xml:174: parser error : Sequence ']]>' not 
allowed in content
 state->last_uid = e_contact_get (contact, E_CONTACT_UID);
  ^
../xml/e-data-book-cursor.xml:174: parser error : Sequence ']]>' not 
allowed in content
]]>
^
../xml/e-data-book-cursor.xml:174: parser error : internal error: detected 
an error in element content
]]>
^
../xml/e-data-book-cursor.xml:174: parser error : Extra content at the end 
of the document
]]>
^
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Network switch for irc.gnome.org: Thursday, 14th May, 2015, 22 - 23 CET+1

[Andrea Veri]

Dear GNOME Community,

after testing the new IRCD and its integration with services 
(ChanServ, NickServ) [1] we are delighted to announce we will be 
moving the testing servers to production this upcoming thursday from 
22 to 23 CET+1.

The downtime should not take more than a few minutes: old ircds will 
be shutdown and the new ones will be restarted for properly binding 
to the default ports. (being 6667 for non-ssl connections and 6697 for 
ssl-enabled connections)

The new network will come with new features:

 - SSL (reachable by connecting to port 6697 on each of the servers 
   hosted within the network)
 - IRC services (ChanServ, NickServ), that will allow you to register 
   your nickname and channel in a safe and straightforward way. 
   Instructions on how to interact with services are available at [1], 
   [2] will receive a revamp in the next couple of days including all 
   the details and support contacts
 - Improved IPv6 support now available on both irc.acc.umu.se and 
   irc.poop.nl

As a side note the GNOME Bot known as 'Services' will be removed from 
channels that previously requested it unless a specific team requires 
its MeetBot capability. I'll give [3] a look and see which teams made 
use of it in the past years and leave it connected on those channels. 
If you want the bot to join a new channel as you would be willing to 
manage a meeting through it opening a bug at [4] should be the ideal way for 
having it added to the requested channel.

The Operators Team will be available on the #opers channel during and 
after the migration, questions and support requests should be 
redirected to that channel.

This is the list of servers that will populate the network:

 - irc.acc.umu.se: IPv4: 130.239.18.215, IPv6: 2001:6b0:e:2018::215
 - irc.eagle.y.se, IPv4: 82.99.16.155
 - irc.gimp.ca, IPv4: 142.4.222.129
 - irc.poop.nl, IPv4: 83.98.201.42 - IPv6: 2001:16f8:4::42

The irc.gimp.org (the record irc.gnome.org points to) round robin will 
be updated with the new IPs on the same day, it might take a few hours
for all the DNS resolvers to get in sync, in case make use of the IPs of
the machines to connect as listed above.

As usual keep an eye at [5].


[1] https://mail.gnome.org/archives/gnome-announce-list/2015-April/msg00010.html
[2] https://wiki.gnome.org/Sysadmin/IRC
[3] https://meetbot.gnome.org/
[4] https://bugzilla.gnome.org/enter_bug.cgi?product=sysadmin&component=IRC
[5] https://status.gnome.org


-- 

Cheers,

Andrea

Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin Team Coordinator,
GNOME Foundation Membership & Elections Committee Chairman

Homepage: http://www.gnome.org/~av


signature.asc
Description: Digital signature
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list