[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#775180: marked as done (UDD: provide iCalender/ics and/or CalDAV task feeds)

Your message dated Thu, 5 Feb 2015 09:21:22 +0100
with message-id <20150205082122.GA14801@xanadu.blop.info>
and subject line Re: Bug#775180: analysis
has caused the Debian Bug report #775180,
regarding UDD: provide iCalender/ics and/or CalDAV task feeds
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 owner@bugs.debian.org
immediately.)


-- 
775180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775180
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
User: qa.debian.org@packages.debian.org
UserTags: udd
Severity: wishlist


I see there is an RSS feed, e.g.
http://udd.debian.org/dmd/feed/?email1=daniel@pocock.pro

It would be good to have a CalDAV feed too, exporting task items

In case somebody wants to work on this request, could anybody comment on
the way this should be implemented?  In particular,

- does UDD provide a mechanism for detecting when data is stale, so that
GET requests don't always have to run an SQL query?

- how could multiple feeds be supported?  E.g. some developers may want
a single task item in their to-do list that says "Fix RC bugs" while
other developers may want to see each RC bug as a separate to-do item.
Is there any plan to give such options for the RSS feed too?

- it would be good to include in the feeds (both RSS and CalDAV) bugs
that the developer has submitted to some other package and they have the
moreinfo tag

- it may also be useful to filter out bugs that the developer has put
the moreinfo tag on within the last 2 weeks (or maybe 1-2 days if the
bug is RC) so the developer can focus on those bugs that he hasn't
looked at already

--- End Message ---
--- Begin Message --- 
On 04/02/15 at 15:35 -0200, Antonio Terceiro wrote:
> On Wed, Feb 04, 2015 at 02:12:13PM +0100, Daniel Pocock wrote:
> > It has been rejected from wheezy-backports, I've sent a query to the
> > release team about uploading vpim to wheezy-updates instead:
> > 
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777047
> 
> Note that you can workaround the brokennes of the vpim from wheezy by
> symlinks its files into a directory that you then add to the Ruby
> $LOAD_PATH. e.g. on a wheezy box here:
> 
> $ ruby -v
> ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
> $ ls -lh lib/
> total 0
> lrwxrwxrwx 1 vagrant vagrant 22 Feb  4 14:33 vpim -> /usr/lib/ruby/1.8/vpim
> lrwxrwxrwx 1 vagrant vagrant 25 Feb  4 14:33 vpim.rb -> /usr/lib/ruby/1.8/vpim.rb
> $ ruby -I$(pwd)/lib -rvpim -e 'puts Vpim'
> Vpim
> $

Hi,

I've used that work-around (loading the 1.8 load path) to get something
that works. Closing the bug.

Thanks!

Lucas

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: