Le 22/05/2020 à 09:56, Viktor Csiky a écrit :
> Hello
> This fix still didn't surface in backports.
> Please add it to backports, otherwise (I guess unlike testing) there is
> no feasible means for anyone using backports to fix the whole npm bunch,
> except disabling backports, purging and reinstalling (the older one).


I pushed node-dot-prop in backports. Since this package is new in
backports, wait 2-3 days to get it


---- Forwarder mail ----
From: Debian FTP Masters <ftpmas...@ftp-master.debian.org>
Subject: node-dot-prop_5.2.0-1~bpo10+1_amd64.changes is NEW

binary:node-dot-prop is NEW.
binary:node-dot-prop is NEW.
source:node-dot-prop is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
     or https://ftp-master.debian.org/backports-new.html for *-backports

Reply via email to