Debian Patches
Status for perlnavigator/0.6.3+ds-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 020240807~5027701.patch | fix warnings via namespace::autoclean On Perl 5.40 a new warning is introduced when the import method of an unknown package is called. . https://perldoc.perl.org/perldelta#Calling-the-import-method-of-an-unknown-package-produces-a-warning . This is seen via PerlNavigator because Inquisitor.pm removes namespace::clean and namespace::autoclean from %INC. The solution is to add stub import subs for these packages so that the Perl interpreter no longer believes that they do not exist. |
Olaf Alders <olaf@wundersolutions.com> | yes | debian upstream | upstream, https://github.com/bscan/PerlNavigator/commit/5027701 | 2026-05-18 |
| 020231022~9b87dad.patch | fix for namespace clean and autoclean | bscan <10503608+bscan@users.noreply.github.com> | no | upstream, https://github.com/bscan/PerlNavigator/commit/9b87dad | 2026-05-18 | |
| 020231023~ab444e4.patch | fix for namespace clean/autoclean minimum versions | bscan <10503608+bscan@users.noreply.github.com> | no | upstream, https://github.com/bscan/PerlNavigator/commit/ab444e4 | 2026-05-18 | |
| 020260226~ca603a2.patch | fix namespace::clean stub missing get_functions and clean_subroutines The namespace::clean stub only provided import() and VERSION, but not get_functions() or clean_subroutines(). Any module that calls namespace::clean->get_functions($package) at file scope (not inside a BEGIN block) would fail with: . Can't locate object method "get_functions" via package "namespace::clean" . This causes a cascade of BEGIN failed errors through the dependency chain, surfacing as dozens of false Syntax diagnostics in the editor. . Fix: add a get_functions stub that reads CODE symbols from the package stash directly, matching the real implementation's return value, and a no-op clean_subroutines stub. |
Dan Wright <dan.wright@grantstreet.com> | no | upstream, https://github.com/bscan/PerlNavigator/commit/ca603a2 | 2026-05-18 | |
| 1001_lru-cache.patch | adapt to newer NodeJS module lru-cache v7 | Jonas Smedegaard <dr@jones.dk> | no | 2023-05-28 | ||
| 2001_URI.patch | use NodeJS-internal module url (not vscode-uri) | Jonas Smedegaard <dr@jones.dk> | not-needed | 2023-05-28 | ||
| 2002_shebang.patch | add shebang to main executable | Jonas Smedegaard <dr@jones.dk> | not-needed | 2023-05-28 | ||
| 2003_privacy.patch | avoid privacy breach in documentation | Jonas Smedegaard <dr@jones.dk> | not-needed | 2023-05-28 | ||
| 2004_silence_test_skew.patch | work around failing perl test t/01_MyClass.t The issue might be an off by one error fixed in upstream git commit 980a742, which is however uncomfortably large to cherry-pick. |
Jonas Smedegaard <dr@jones.dk> | not-needed | 2026-05-18 | ||
| ts6-tsconfig.patch | build with TypeScript 6 tsc 6 rejects the node10 module resolution (TS5107). With "module": "commonjs" the default resolution is the same thing, except that it now honours the package.json "exports" of the modules copied into node_modules -- which point at bundles carrying no typings. "resolvePackageJsonExports": false restores the classic types/main lookup. . tsc 6 also stopped picking up node_modules/@types on its own, so the Node typings used by the server and by vscode-jsonrpc have to be asked for explicitly (TS2591, TS2503). . Finally, vscode-jsonrpc ships a LinkedMap declaration that the stricter Map/Iterator definitions of the tsc 6 libraries reject (TS2416). That is a problem for its own maintainers, not for this build, hence "skipLibCheck". |
Xavier Guimard <yadd@debian.org> | not-needed | 2026-08-17 | ||
| fix-for-recent-lru.patch | fix for recent node-lru-cache lru-cache >= 7 no longer exports the constructor directly, so `new LRU()` failed with "LRU is not a constructor" and the server did not start at all. . Two further incompatibilities show up once the server runs: . * `del()` was deprecated in v7 and removed in v10: use `delete()` instead, otherwise closing any document throws "navSymbols.del is not a function". * `sizeCalculation` must return a strictly positive integer since v7. A Perl document with no symbol (empty file, or a file that fails to compile) has `elems.size == 0`, which made `navSymbols.set()` throw. Report 1 for those documents so they are still cached. |
Yadd <yadd@debian.org> | not-needed | debian | 2026-08-17 |
All known versions for source package 'perlnavigator'
- 0.6.3+ds-3 (sid)
- 0.6.3+ds-1 (forky)
- 0.6.0~dfsg-3 (trixie)
