On 03/02/15 20:55, Daniel Pocock wrote: > On 03/02/15 19:55, Daniel Pocock wrote: >> On 03/02/15 19:42, Lucas Nussbaum wrote: >>> On 03/02/15 at 18:33 +0100, Daniel Pocock wrote: >>>> On 03/02/15 09:37, Lucas Nussbaum wrote: >>>>> On 03/02/15 at 09:22 +0100, Daniel Pocock wrote: >>>>>> On 03/02/15 08:55, Lucas Nussbaum wrote: >>>>>>> Hi Daniel, >>>>>>> >>>>>>> On 31/01/15 at 11:09 +0100, Daniel Pocock wrote: >>>>>>>> On 30/01/15 16:20, Christophe Siraut wrote: >>>>>>>>> Hi Daniel, >>>>>>>>> >>>>>>>>>> If my proposed solution seems reasonable I'll go ahead and code it >>>>>>>>>> (...) >>>>>>>>> It seems perfectly reasonable to me. I just want to mention that while >>>>>>>>> we started refactoring DMD in order to provide RSS, YAML and JSON, we >>>>>>>>> did not finish isolating the data from the presentation. In >>>>>>>>> consequence >>>>>>>>> you might end up with HTML code in calendar tasks, please fix or fill >>>>>>>>> bugs if it happens. (There should be no HTML in dmd-data.rb nor in >>>>>>>>> dmd.cgi; data should be parsed in dmd-data.rb only; dmd.cgi should be >>>>>>>>> a >>>>>>>>> lot simpler) >>>>>>>>> >>>>>>>> I've done the following: >>>>>>>> >>>>>>>> - initial implementation using the feeditems array >>>>>>>> >>>>>>>> - requested to join collab-qa on alioth so I can push this, otherwise >>>>>>>> somebody else can apply it >>>>>>>> >>>>>>>> - sent an RT request (#5713) to DSA to install the vpim package on >>>>>>>> ullmann >>>>>>> I've reverted the change as it broke bugs.cgi (probably due to the >>>>>>> missing dep). >>>>>>> >>>>>>> Please revert the revert once the change is ready to be deployed. >>>>>> Is there a DSA contact who looks after ullmann.d.o? Or do you have sudo >>>>>> access? I notice nobody replied to the DSA ticket to apt-get install >>>>>> vpim. >>>>> No, a ticket is the correct way to make progress here >>>>> >>>> Thanks Lucas, Peter installed the package and I re-applied the commit in >>>> master, what is the next step to release the change and verify it is >>>> working in production? >>> Crap. vpim is broken in wheezy, it doesn't work with ruby 1.9.x, because >>> it only installs files in /usr/lib/ruby/1.8/ >> I saw the vpim package was almost the same version in jessie and >> wheezy. I actually tested on jessie though >> >>> How much do you depend on this particular implementation of icalendar >>> support in Ruby? You could backport a fixed package and have DSA >>> install it... >> This is the first project where I've tried using Ruby for something and >> this was the first dependency that I found that appeared to be suitable >> as it was in wheezy. If there is another dependency that is easier to >> use I don't mind. >> >> Antonio did an NMU for jessie[1] and I think it is intended to fix the >> issue you described so I could just upload that to wheezy-backports, is >> that what you had in mind? > I uploaded it to wheezy-backports, it is now waiting in NEW
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 > >> I made some fixes upstream[2] but I don't know how keen people would be >> to let that through to jessie and backports while we are in the freeze >> >> Upstream also indicated he would welcome github pull requests, possibly >> making the package easier to support >> >> Regards, >> >> Daniel >> >> >> 1. >> http://metadata.ftp-master.debian.org/changelogs/main/v/vpim/unstable_changelog >> >> 2. https://github.com/sam-github/vpim/commits/master >> >> >> -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d21aad.7030...@pocock.pro
