Hi,
I wonder if what I saw is an known bug. I tried vpim-0.12
and I was going to call dtend, dtstamp, dtstart and duration
method in Vpim::Icalendar::Vevent class which I got from
Vpim::Icalendar#events method. but I encountered a problem
here like,
ArgumentError: wrong number of arguments (1 for 0)
from /usr/lib/ruby/1.8/vpim/vevent.rb:289:in `to_time''
from /usr/lib/ruby/1.8/vpim/vevent.rb:289:in `dtend''
Though Vevent#dtend is going to call to_time method with
''date-time'' argument, Vpim::DirectoryInfo::Field#to_time
seems not allowing any arguments. What''s wrong then? maybe
I could just remove this argument, but I''m not sure what
does it mean.
BTW I''ve made a Debian package for vpim and uploaded
it. hopefully it will be available soon.
Thanks,
--
Akira TAGOH : tagoh@gnome.gr.jp / Japan GNOME Users Group
at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project
: tagoh@redhat.com / Red Hat, Inc.
: tagoh@debian.org / Debian Project
Wrote Akira TAGOH <at@gclab.org>, on Fri, Jan 21, 2005 at 03:22:10AM +0900:> I wonder if what I saw is an known bug. I tried vpim-0.12 > and I was going to call dtend, dtstamp, dtstart and duration > method in Vpim::Icalendar::Vevent class which I got from > Vpim::Icalendar#events method. but I encountered a problem > here like, > > ArgumentError: wrong number of arguments (1 for 0) > from /usr/lib/ruby/1.8/vpim/vevent.rb:289:in `to_time'' > from /usr/lib/ruby/1.8/vpim/vevent.rb:289:in `dtend''I am pretty sure this is an error in my code, I''ll check tonight.> Though Vevent#dtend is going to call to_time method with > ''date-time'' argument, Vpim::DirectoryInfo::Field#to_time > seems not allowing any arguments. What''s wrong then? maybe > I could just remove this argument, but I''m not sure what > does it mean. > > BTW I''ve made a Debian package for vpim and uploaded > it. hopefully it will be available soon.That''s cool, thank you very much, Akira! I would like to include the dpkg config in the vpim release, would you like that? Also, maybe you already have a way of distributing .dpkgs, if you would like to tell me where it is, I can add a note to the readme. Or, if you would like, you can upload the pkg to rubyforge. Thanks, Sam -- Sam Roberts <sroberts@certicom.com>
Hi Sam,>>>>> On Thu, 20 Jan 2005 14:56:26 -0500, >>>>> "SR" == Sam Roberts <sroberts@uniserve.com> wrote:SR> I am pretty sure this is an error in my code, I''ll check tonight. Thank you :) SR> That''s cool, thank you very much, Akira! SR> I would like to include the dpkg config in the vpim release, would you SR> like that? SR> Also, maybe you already have a way of distributing .dpkgs, if you would SR> like to tell me where it is, I can add a note to the readme. SR> Or, if you would like, you can upload the pkg to rubyforge. Well, you mean .deb? well, I''m waiting for the approval which is required for the new package. people who uses Debian will be able to get vpim package for Debian via apt-get after that. the package name is libvpim-ruby1.8. I don''t know when it''s accepted. if anyone wants to install it before accepting, I can upload it somewhere. Thanks, -- Akira TAGOH : tagoh@gnome.gr.jp / Japan GNOME Users Group at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project : tagoh@redhat.com / Red Hat, Inc. : tagoh@debian.org / Debian Project
Quoteing at@gclab.org, on Fri, Jan 21, 2005 at 05:50:36AM +0900:> Hi Sam, > > >>>>> On Thu, 20 Jan 2005 14:56:26 -0500, > >>>>> "SR" == Sam Roberts <sroberts@uniserve.com> wrote: > > SR> I am pretty sure this is an error in my code, I''ll check tonight. > > Thank you :)Sorry, I''d fixed it locally and not uploaded it. 0.13 was uploaded and should fix this problem.> SR> I would like to include the dpkg config in the vpim release, would you > SR> like that? > > SR> Also, maybe you already have a way of distributing .dpkgs, if you would > SR> like to tell me where it is, I can add a note to the readme. > > SR> Or, if you would like, you can upload the pkg to rubyforge. > > Well, you mean .deb? well, I''m waiting for the approval > which is required for the new package. people who uses > Debian will be able to get vpim package for Debian via > apt-get after that. the package name is libvpim-ruby1.8.I don''t know how to make .deb files, even though I develop on debian at work, but I assume there is some kind of config file that you wrote, and you can use it to create .deb files. Is that how it works? I''d like to add whatever it is that you use to make the packages to the standard vpim release. That way, when there is a new vpim release you (or anybody) could just untar it, type "make debian", and have a .deb file for the latest release. Is that even possible? Then I could install development packages on my machine at work easily, and if you ever get tired of uploading the packages to debian, somebody else could take over, and wouldn''t have to repeat the work you''ve done.> I don''t know when it''s accepted. if anyone wants to install > it before accepting, I can upload it somewhere.I don''t know, maybe its not useful, but if it takes a long time to be accepted, you can upload the .deb files to the rubyforge project. Anyhow, I''m not trying to make more work for you! Thanks for trying to get vPim packaged, and if you want to add the package config files or the .deb files to the project, you are welcome to do so. Cheers, Sam
>>>>> On Thu, 20 Jan 2005 23:35:21 -0500, >>>>> "SR" == Sam Roberts <sroberts@uniserve.com> wrote:SR> Sorry, I''d fixed it locally and not uploaded it. SR> 0.13 was uploaded and should fix this problem. Cool. thanks! SR> I don''t know how to make .deb files, even though I develop on debian at SR> work, but I assume there is some kind of config file that you wrote, and SR> you can use it to create .deb files. Is that how it works? Yes, you need some files under debian/ directory to make .deb file. SR> I''d like to add whatever it is that you use to make the packages to the SR> standard vpim release. That way, when there is a new vpim release you SR> (or anybody) could just untar it, type "make debian", and have a .deb SR> file for the latest release. Is that even possible? Yes, it''s possible. but please don''t include debian/ directory into the tarball, please. if debian/ directory is maintained in upstream as well, it becomes the native package so that probably there is no changes I should make separately. but vpim isn''t the debian-specific. However just including it into the repository for testing may be a good idea. SR> Then I could install development packages on my machine at work easily, SR> and if you ever get tired of uploading the packages to debian, somebody SR> else could take over, and wouldn''t have to repeat the work you''ve done. Well, don''t worry. we have the procedure for that. and if I get tired of, I''ll do so according to. then, someone else can take over without the lacking of something so that everyone can get the debian source packages from the debian mirror site. SR> I don''t know, maybe its not useful, but if it takes a long time to be SR> accepted, you can upload the .deb files to the rubyforge project. Sure. I''ll let you know when it''s needed. SR> Anyhow, I''m not trying to make more work for you! Thanks for trying to SR> get vPim packaged, and if you want to add the package config files or SR> the .deb files to the project, you are welcome to do so. Thanks, -- Akira TAGOH : tagoh@gnome.gr.jp / Japan GNOME Users Group at@gclab.org : tagoh@gnome-db.org / GNOME-DB Project : tagoh@redhat.com / Red Hat, Inc. : tagoh@debian.org / Debian Project
Quoteing at@gclab.org, on Fri, Jan 21, 2005 at 02:23:25PM +0900:> >>>>> On Thu, 20 Jan 2005 23:35:21 -0500, > >>>>> "SR" == Sam Roberts <sroberts@uniserve.com> wrote: > SR> I''d like to add whatever it is that you use to make the packages to the > SR> standard vpim release. That way, when there is a new vpim release you > SR> (or anybody) could just untar it, type "make debian", and have a .deb > SR> file for the latest release. Is that even possible? > > Yes, it''s possible. but please don''t include debian/ > directory into the tarball, please. if debian/ directory is > maintained in upstream as well, it becomes the native > package so that probably there is no changes I should make > separately. but vpim isn''t the debian-specific. However > just including it into the repository for testing may be a > good idea.As you wish. I just thought it might be convenient for some people, I''ve downloaded packages before with the files needed to make various patches. By the way, anybody else who is listening, if you want to make a package for <insert your favorite OS distribution> I''m happy to include your work/packages in vPim, too. Cheers, Sam