close 385191 1.8-17 thanks On Wed, Sep 06, 2006 at 11:29:51PM +0200, Ludovic Rousseau wrote: > severity 385191 normal > thanks > > Le 29.08.2006, à 19:22:26, Florian Schlichting a écrit: > > Package: plucker-desktop > > Version: 1.8-16+b1 > > Severity: grave > > Justification: renders package unusable > > > > since the last update of plucker (1.8-16+b1, a binary NMU by "the buildd" > > to rebuild plucker against python2.4), it won't update my channel any > > more. Without any error messages, it merely reports success, albeit > > without the usual progress messages (retrieving http://.... etc). After > > finishing, there is no file in the output location, or if a file is > > still cached in ~/.plucker, it will be copied without being updated. > > > > since updating channels is the whole point of plucker-desktop, I believe > > the severity is justified > > I can't reproduce the bug. I am using plucker-desktop 1.8-17 and the > channels are updated. > > Did you had a look in ~/.plucker/channels/ to see if you find a > directory named after your channels and with a *.pdb file inside? > You can use the "plucker" command to view the .pdb file.
Yes I did and there was a file, which I got unchanged in the output location even days later, so eventually I deleted it and it wasn't replaced, that was when I filed the bug. The error messages I referred to I only got before the switch of the default python version. The channel update now runs without displaying any error messages. But the good news: upgrading from 1.8-16+b1 to 1.8-17 actually fixes the problem, in some magic way. When I saw the update coming up in aptitude, and after reading your mail, I tested again to be sure the problem still persists, which it did. After the upgrade everything worked, so to be absolutely sure, I downgraded again to 1.8-16+b1 (which is now in testing) and again I had the same problems. So I'd say 1.8-16+b1 is in some way broken, and 1.8-17 fixes that. BTW thanks for a lot of good work in getting the plucker package in shape! Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
