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

Bug#829286: RFS: newlisp/10.7.0-2



On Sunday, July 03 2016, Gianfranco Costamagna wrote:

>>Thanks for the review, Gianfranco.  If I may, I'd like to propose that
>
>>you upload the package as-is by the end of tomorrow (Sunday) even if
>>Andrey doesn't reply.  I'd really like to get these fixes uploaded ASAP.
>
>
> fine for me, you already did a nice bug triaging, and almost fixed
> all the bugs you got (+1 unreproducible/possibly fixed)
>
> dput -e 1 ftp-master newlisp_10.7.0-2_source.changes
>
> BTW, I put it on deferred/1, and I have a question for you :)

Thanks, Gianfranco.

> as a DM, I'm pretty sure (but I can't check this anymore since I moved to DD),
> that you can reschedule stuff for other people too.
> Can you please try this command?
> dcut ftp-master reschedule -d 0 -f newlisp_10.7.0-2_source.changes
>
> this should move the newlisp in incoming queue

Hm, here's what I see when I try it:

  D: dcut 0.2.1
  D: trying to get maintainer email from environment
  D: Uploader from env: Sergio Durigan Junior <sergiodj@sergiodj.net>
  D: first argument "ftp-master" treated as host
  D: loading dput
  D: calling dput.read_configs
  D: Parsing Configuration File /etc/dput.cf
  D: Parsing Configuration File /home/sergio/.dput.cf
  D: Successfully parsed command "reschedule -d 0 -f newlisp_10.7.0-2_source.changes"
  D: calling debsign: ['debsign', '-mSergio Durigan Junior <sergiodj@sergiodj.net>',
  '/tmp/dcut.RMMfsD/dcut.Sergio_Durigan_Junior__sergiodj_sergiodj_net_.1467570258.1694.commands']
  .commands file has invalid Commands line: reschedule -d 0 -f newlisp_10.7.0-2_source.changes
  debsign: .commands file appears to be invalid. see:
  ftp://ftp.upload.debian.org/pub/UploadQueue/README
  for valid format
  Error: debsign failed.

Is this my fault?

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Attachment: signature.asc
Description: PGP signature


Reply to: