Your message dated Sun, 13 May 2012 10:30:27 +0000
with message-id <[email protected]>
and subject line Bug#670138: fixed in libical 0.48-2
has caused the Debian Bug report #670138,
regarding libical FTBFS on ARM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
670138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libical
Version: 0.48-1
User: [email protected]
Usertags: origin-ubuntu precise
Tags: patch

We are now carrying this in Ubuntu. The fix is committed upstream; you
may want to carry this until an upstream update.

debian/patches/fix_arm_ftbfs.patch:

From: Robie Basak <[email protected]>
Subject: Fix libicalss parser for non-Intel architectures

The test suite fails on ARM and PowerPC because the libicalss lexer
performs unput(EOF) which is not permitted. On these architectures, this
gets interpreted as unput(255), creating an extra token which then
causes the parser to return a syntax error.

Instead, the lexer should just ignore EOF and not attempt to unput it.
The input stream will remain at EOF and the lexer will return an EOF as
the next token as needed.

Forwarded: 
https://sourceforge.net/tracker/?func=detail&aid=3517199&group_id=16077&atid=316077
Bug-Ubuntu: https://bugs.launchpad.net/bugs/979846
Last-Update: 2012-04-12

--- a/src/libicalss/icalsslexer.c
+++ b/src/libicalss/icalsslexer.c
@@ -936,7 +936,9 @@
 YY_RULE_SETUP
 {
        int c = input();
-       unput(c);
+       if (c != EOF) {
+               unput(c);
+       }
        if(c!='\''){
                sslval.v_string= icalmemory_tmp_copy(sstext);
                return STRING;
--- a/src/libicalss/icalsslexer.l
+++ b/src/libicalss/icalsslexer.l
@@ -111,7 +111,9 @@
 
 \'[\@\*A-Za-z0-9\-\.\:\ ]+\' {
        int c = input();
-       unput(c);
+       if (c != EOF) {
+               unput(c);
+       }
        if(c!='\''){
                sslval.v_string= icalmemory_tmp_copy(yytext);
                return STRING;

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: libical
Source-Version: 0.48-2

We believe that the bug you reported is fixed in the latest version of
libical, which is due to be installed in the Debian FTP archive:

libical-dbg_0.48-2_amd64.deb
  to main/libi/libical/libical-dbg_0.48-2_amd64.deb
libical-dev_0.48-2_amd64.deb
  to main/libi/libical/libical-dev_0.48-2_amd64.deb
libical0_0.48-2_amd64.deb
  to main/libi/libical/libical0_0.48-2_amd64.deb
libical_0.48-2.debian.tar.gz
  to main/libi/libical/libical_0.48-2.debian.tar.gz
libical_0.48-2.dsc
  to main/libi/libical/libical_0.48-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fathi Boudra <[email protected]> (supplier of updated libical package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 13 May 2012 12:52:58 +0300
Source: libical
Binary: libical-dev libical0 libical-dbg
Architecture: source amd64
Version: 0.48-2
Distribution: unstable
Urgency: low
Maintainer: Fathi Boudra <[email protected]>
Changed-By: Fathi Boudra <[email protected]>
Description: 
 libical-dbg - debugging symbols for libical
 libical-dev - iCalendar library implementation in C (development)
 libical0   - iCalendar library implementation in C (runtime)
Closes: 663624 670138 670139 670140
Changes: 
 libical (0.48-2) unstable; urgency=low
 .
   * Add patches (Thanks to Robie Basak):
     - fix_arm_ftbfs.patch: fix FTBFS on ARM: do not unput when input returns
       EOF. (Closes: #663624, #670138)
     - fix_ftbfs_dependencies.patch: fix CMakeLists.txt dependencies.
       (Closes: #670139)
     - fix_timezone_crash.patch: workaround to avoid heap corruption until
       upstream have a complete fix. (Closes: #670140)
Checksums-Sha1: 
 e55a0f087fbd2ac79e34ed094cba049f469d0246 1280 libical_0.48-2.dsc
 33f0d518d7132442460bf9d6276708ae2b766e73 21227 libical_0.48-2.debian.tar.gz
 6d45e1d0e53d06f12256d6fa863eef1844ea2ef0 307032 libical-dev_0.48-2_amd64.deb
 7cd46fa0590651de8a6741e402a1e15ff9d7ab53 237578 libical0_0.48-2_amd64.deb
 c6f266f91dbde4190932b4ea7432e2ca72fdb1e5 442378 libical-dbg_0.48-2_amd64.deb
Checksums-Sha256: 
 3c09c3a07ae15e4bdf87990ae04947d0be791762af97e6caf6b87e3b3296f6c2 1280 
libical_0.48-2.dsc
 6656124654539ee10277f4461cb6ac953ccc876d0d3a3812b4b84471ae0a68f9 21227 
libical_0.48-2.debian.tar.gz
 d1e96f2cb3943ced01a38035ccf5613485bada10b6bdf21da0af6a6d52a25b4a 307032 
libical-dev_0.48-2_amd64.deb
 1b6a7a7011907d5887f5e7350ecdb3ed43662ff34b24101e2eb3b3c4aa201b4e 237578 
libical0_0.48-2_amd64.deb
 28692d6eb6b5b913de680b9a2f1346b5a664eb97a31c6129b152aae273908b81 442378 
libical-dbg_0.48-2_amd64.deb
Files: 
 02e7e8f530a1c0ce646e015e47dd55d3 1280 libs optional libical_0.48-2.dsc
 d089d753fa24e3865aeb51f0714a4c9b 21227 libs optional 
libical_0.48-2.debian.tar.gz
 cc78b42956ccd15142ab43189ce15cbf 307032 libdevel optional 
libical-dev_0.48-2_amd64.deb
 5641d6e0508badc796f2d423b48321dd 237578 libs optional libical0_0.48-2_amd64.deb
 22caed679c4ccbfbbc7415bab1f2a3b3 442378 debug extra 
libical-dbg_0.48-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAk+viCUACgkQjPU19mqlcvdKuwQAmWzMdfmkizEvVaKx0jM8bZbd
vbeyZcFG8nTCxy6RfRhgwCU5zVP+wpLHb/OyGZPJE/Zr6XRwTPssBvXWLCAU+sSh
wIbGJsfIomzLd+vxdFpjtmWBaQq64SrzB1DFqcDulkjjlpDIFbkiy8D78/PVkVl2
7bfLF2UX+3P53hKv9Ao=
=XYME
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to