[ replying Cc bugreport ] Quoting Ayoyimika Ajibade (2022-02-08 13:04:08) > No, you are not missing anything I updated node-node-forge from > version 0.10.0. to 1.2.1 with a draft from upstream repo here > https://github.com/digitalbazaar/forge/pull/945/commits
Ok. Debian package node-node-forge has now been updated to version 1.2.1 in unstable. You need not update your test branch for my sake, just mentioning in case you need to test further, based on up-to-date official Debian packaging. Does your test involve other code changes than cherry-picking the changes done upstream? Also, do I understand it correctly that the changes you and/or upstream did is not backwards-compatible? I.e. that the changes cannot be applied yet for the packaging targeted Debian unstable, but instead need to be done _after_ webpack5 has entered unstable? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
-- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
