#422878 cycle: Cycle failed to export to iCal

Package:
cycle
Source:
cycle
Submitter:
Petr Gajdusek
Date:
2023-01-16 06:09:02 UTC
Severity:
normal
Tags:
#422878#5
Date:
2007-05-08 15:36:06 UTC
From:
To:
Hi, I cannot export anything to iCal. Exported iCal file is always empty.
Cycle output:

Traceback (most recent call last):
  File "/usr/bin/cycle", line 150, in Export
    report_year_ical(self.cal.year, fileobj)
  File "/usr/share/cycle/cal_year.py", line 677, in report_year_ical
    print >>fileobj, "\n".join(s)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xed' in
positio

#422878#10
Date:
2007-05-29 14:05:32 UTC
From:
To:
Hi Petr,

I think this is because you have added a comment using non ascci characters.
Can you check if this is the problem?

Ana

#422878#15
Date:
2007-05-29 16:46:47 UTC
From:
To:
Hi Ana,

my system locale setting is cs_CZ.UTF-8. When I run cycle under this
locale export always fails. I haven't added any comment. Cycle is
translated into czech language including all calendar notices such as
"Beginning of cycle", "1-st tablet" etc., could this be problem?

When I run "LC_ALL=POSIX cycle" export works good without any output to
standard error.

Btw. all comments seem to be ignored when exporting (even pure ascii
comments).

Petr

#422878#20
Date:
2018-02-20 07:28:17 UTC
From:
To:
Ahoj dobré ráno,
Som Katie! ako sa máš! Dúfam, že ste v poriadku av dokonalom zdraví. Našiel som svoj e-mail prostredníctvom spoločnosti Google a mám pocit, že vás môžem kontaktovať, ak vám to nevadí, chcel by som mi napísať, čakám na vašu poštu, pretože s tebou mám niečo veľmi dôležité. Pozdravy.

#422878#25
Date:
2018-05-07 20:13:25 UTC
From:
To:

#422878#30
Date:
2018-07-29 12:15:17 UTC
From:
To:
Hi Dear, my name is Jack and i am seeking for a relationship in which i will feel loved after a series of failed relationships.

I am hoping that you would be interested and we could possibly get to know each other more if you do not mind. I am open to answering questions from you as i think my approach is a little inappropriate. Hope to hear back from you.

Jack.

#422878#35
Date:
2018-12-22 08:10:03 UTC
From:
To:
Hi Oleg,

you might know that cycle is packaged for Debian.  Over time it gathered
some bug reports which are open for a long time without proper
attention.  Here you can find a summary over all those bugs:

https://bugs.debian.org/src:cycle

I'm not sure whether you keep on working on cycle but I simply want to
make sure that those issues are not escaping your attention.

Kind regards and thanks for maintaining cycle as free software

      Andreas.

#422878#44
Date:
2020-02-16 00:19:44 UTC
From:
To:
Dear submitter,

as the package cycle has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/939181

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

#422878#57
Date:
2023-01-16 06:03:51 UTC
From:
To:
cycle 0.3.2-2 has been reintroduced into Debian unstable.

Please try it and see if the issue has been fixed.

If the issue has been fixed, please let us know on this bug.

If the issue has not been fixed, please search the upstream bug
databases to see if the issue is already reported and if it is not
reported, then report a new issue upstream. Please let us know about
any new or existing upstream bugs you file or find.

https://github.com/metlov/cycle/issues
https://sourceforge.net/p/cycle/bugs/
https://sourceforge.net/p/cycle/feature-requests/