[Pkg-javascript-devel] Processed: Upgrade severity due to upload.

2024-04-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # OpenSSL 3.2 has been uploaded to unstable, raise the severity > severity 1061458 serious Bug #1061458 [src:gdm3] gdm3: Testsuite breaks with openssl 3.2 Severity set to 'serious' from 'important' > severity 1061869 serious Bug #1061869

[Pkg-javascript-devel] Bug#1046929: marked as done (node-graphql: Fails to build source after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:04:09 + with message-id and subject line Bug#1046929: fixed in node-graphql 16.8.1-2 has caused the Debian Bug report #1046929, regarding node-graphql: Fails to build source after successful build to be marked as done. This means that you claim that the

[Pkg-javascript-devel] Bug#1049548: marked as done (node-graphql: Fails to build binary packages again after successful build)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 04:04:10 + with message-id and subject line Bug#1049548: fixed in node-graphql 16.8.1-2 has caused the Debian Bug report #1049548, regarding node-graphql: Fails to build binary packages again after successful build to be marked as done. This means that

[Pkg-javascript-devel] Processing of node-graphql_16.8.1-2_sourceonly.changes

2024-04-04 Thread Debian FTP Masters
node-graphql_16.8.1-2_sourceonly.changes uploaded successfully to localhost along with the files: node-graphql_16.8.1-2.dsc node-graphql_16.8.1-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list

[Pkg-javascript-devel] node-tar 6.1.13+~cs7.0.5-3 MIGRATED to testing

2024-04-04 Thread Debian testing watch
FYI: The status of the node-tar source package in Debian's testing distribution has changed. Previous version: 6.1.13+~cs7.0.5-1 Current version: 6.1.13+~cs7.0.5-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times

[Pkg-javascript-devel] Processed: Bug#1049548 marked as pending in node-graphql

2024-04-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1049548 [src:node-graphql] node-graphql: Fails to build binary packages again after successful build Added tag(s) pending. -- 1049548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049548 Debian Bug Tracking System Contact

[Pkg-javascript-devel] Processed: Bug#1046929 marked as pending in node-graphql

2024-04-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1046929 [src:node-graphql] node-graphql: Fails to build source after successful build Added tag(s) pending. -- 1046929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046929 Debian Bug Tracking System Contact ow...@bugs.debian.org with

[Pkg-javascript-devel] node-graphql_16.8.1-2_sourceonly.changes ACCEPTED into unstable

2024-04-04 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Apr 2024 02:58:21 +0530 Source: node-graphql Architecture: source Version: 16.8.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers

[Pkg-javascript-devel] Bug#1058552: Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

2024-04-04 Thread Jonas Smedegaard
Quoting James Valleroy (2024-04-04 16:13:07) > On 3/28/24 4:08 AM, Petter Reinholdtsen wrote: > > [James Valleroy 2024-02-12] > >> Here is a patch that fixes the build: > > > > Thank you. Can you explain why changing the output from package.json to > > mktemp and then moving the result to

[Pkg-javascript-devel] Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

2024-04-04 Thread James Valleroy
On 3/28/24 4:08 AM, Petter Reinholdtsen wrote: [James Valleroy 2024-02-12] Here is a patch that fixes the build: Thank you. Can you explain why changing the output from package.json to mktemp and then moving the result to package.json will solve the build problem? I fail to understand how