[Pkg-javascript-devel] node-resolve 1.5.0-1 MIGRATED to testing
FYI: The status of the node-resolve source package in Debian's testing distribution has changed. Previous version: 1.4.0-1 Current version: 1.5.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-rollup-plugin-json 3.1.0-1 MIGRATED to testing
FYI: The status of the node-rollup-plugin-json source package in Debian's testing distribution has changed. Previous version: 3.0.0-1 Current version: 3.1.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-rollup-plugin-commonjs 9.1.8-1 MIGRATED to testing
FYI: The status of the node-rollup-plugin-commonjs source package in Debian's testing distribution has changed. Previous version: 9.1.3-1 Current version: 9.1.8-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-rollup-plugin-node-resolve 3.4.0-1 MIGRATED to testing
FYI: The status of the node-rollup-plugin-node-resolve source package in Debian's testing distribution has changed. Previous version: 3.3.0-1 Current version: 3.4.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#836744: marked as done (npm: bash completion script breaks $IFS)
Your message dated Tue, 25 Sep 2018 00:01:30 +0530 with message-id <8c363b98-da3c-7e4e-a12f-0fe9361d0...@onenetbeyond.org> and subject line closing old bug has caused the Debian Bug report #836744, regarding npm: bash completion script breaks $IFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 836744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: npm Version: 1.4.21+ds-2 Severity: important If the `npm` bash completion is interrupted, the IFS variable in the shell becomes corrupted so that now basically very little works, including aliases with spaces in. For example: $ alias ls alias ls='ls $LS_OPTIONS' $ ls [currently works] Now cause a completion that gets interrupted, by hitting and then $ npm install l At this point the alias is now broken $ ls ls: invalid argument ‘auto -h’ for ‘--color’ Valid arguments are: - ‘always’, ‘yes’, ‘force’ - ‘never’, ‘no’, ‘none’ - ‘auto’, ‘tty’, ‘if-tty’ Try 'ls --help' for more information. This bug comes from the completion script trying to save and restore changes to IFS by its own local variable of $si, rather than simply doing local IFS -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages npm depends on: ii node-abbrev 1.0.9-1 ii node-ansi 0.3.0-2 ii node-ansi-color-table 1.0.0-1 ii node-archy0.0.2-1 ii node-block-stream 0.0.7-1 ii node-fstream 0.1.24-1 ii node-fstream-ignore 0.0.6-2 ii node-github-url-from-git 1.4.0-1 ii node-glob 4.0.5-1 ii node-graceful-fs 3.0.2-1 ii node-gyp 3.4.0-1 ii node-inherits 2.0.1-3 ii node-ini 1.1.0-1 ii node-lockfile 0.4.1-1 ii node-lru-cache2.3.1-1 ii node-minimatch1.0.0-1 ii node-mkdirp 0.5.0-1 ii node-nopt 3.0.1-1 ii node-npmlog 0.0.4-1 ii node-once 1.1.1-1 ii node-osenv0.1.0-1 ii node-read 1.0.5-1 ii node-read-package-json1.2.4-1 ii node-request 2.26.1-1 ii node-retry0.6.0-1 ii node-rimraf 2.2.8-1 ii node-semver 2.1.0-2 ii node-sha 1.2.3-1 ii node-slide1.1.4-1 ii node-tar 1.0.3-2 ii node-underscore 1.7.0~dfsg-1 ii node-which1.0.5-2 ii nodejs4.3.1~dfsg-3 npm recommends no packages. npm suggests no packages. -- no debconf information -- Paul "LeoNerd" Evans leon...@leonerd.org.uk | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/ pgpsDwC0W7glz.pgp Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Most likely fixed in a recent upload. Reopen if still relevant. signature.asc Description: OpenPGP digital signature --- End Message --- -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-webpack-stats-plugin_0.2.1-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Sep 2018 19:28:10 +0530 Source: node-webpack-stats-plugin Binary: node-webpack-stats-plugin Architecture: source Version: 0.2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: node-webpack-stats-plugin - Webpack stats plugin Changes: node-webpack-stats-plugin (0.2.1-1) unstable; urgency=medium . * New upstream version 0.2.1 * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) Checksums-Sha1: cba1bcc131629a9bfe5a1fe7fdc592c8bdfb7889 2156 node-webpack-stats-plugin_0.2.1-1.dsc 893c921160c94b5c195f024fe445a51d39058797 62119 node-webpack-stats-plugin_0.2.1.orig.tar.gz d0b30998d0526902c79e079a804fb5315d84f496 2216 node-webpack-stats-plugin_0.2.1-1.debian.tar.xz 49c76b67732b5ec6abeab1b791ed71920abb5345 6116 node-webpack-stats-plugin_0.2.1-1_source.buildinfo Checksums-Sha256: b00d3427c1906e107f7d886be9a035b500851233ac88e6b51ef26ec8f2b5b8a8 2156 node-webpack-stats-plugin_0.2.1-1.dsc c01229a6c566fbae3e55f44f15fcae802c8616e2ec94709aef4a56766aea7a66 62119 node-webpack-stats-plugin_0.2.1.orig.tar.gz c6fc2adf205ed861cff77ed3e13992603a103acddefb61f48aa52d5201356e47 2216 node-webpack-stats-plugin_0.2.1-1.debian.tar.xz 0b03cd423fc61606936bea39cabb46a55cf88047bb2bb4f4e85a9a1f841d2faf 6116 node-webpack-stats-plugin_0.2.1-1_source.buildinfo Files: 572ca5436c0ad3d4b1645fc661b6b6d7 2156 javascript optional node-webpack-stats-plugin_0.2.1-1.dsc db8da7325052ca1c8fdcc9179f03a6aa 62119 javascript optional node-webpack-stats-plugin_0.2.1.orig.tar.gz 88477361098f04fe2d0a8d1454aac7e6 2216 javascript optional node-webpack-stats-plugin_0.2.1-1.debian.tar.xz 5544c56b5346f83b90a0337e7169a5f8 6116 javascript optional node-webpack-stats-plugin_0.2.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAluo7jYACgkQzh+cZ0US wipZEw//ZH3rRu+vcHeOUqvpNPm3eoWki98MQdlZfgESovJ8lw+zTLuJhiXiIZDw 2N4+80+mqGlC1ndRRuZIEg8HgOC9fPC9PDyAAAKwpMdOjGeFFX79uaYqA1JcNzwv PtaGH5S8stLj99K6iMgYd3D6/j7NvuwXPgkY4v7SDjbRGKhV0lKlhgYkK7NhqD7d am02gC9ITh7rOtUUqNX+1qx8DeLafJaRxderWkrb6AhZliyrO4mLfb1Pn9QxE7bH 1x5T8ACdRaUj5qs+KwmAVNVYZk02ni3mlqIpNHnXbHWsA7mqPj/TRuCaTBNW4o2d 1PSqE6/bvNMlcgSNGYO6rjZ7Pz53Tb8dnPagMmdWzpRmMdCkQ1uRdNRhX6cOTqlg zocnToIWWlXNVNaIG8WtPvHkbW8j5QTAMy3mP+E6EfJ63olF4BmiHO/q/stNW1Qe xraWXZMepejpYI8Wcx/iLkEkThq+pijKIH0i0oJce+/Mhz/zH4XrvIm+U93LWwWJ JNJfZ5vXI4g7owsEF5cY+7BlEySJYBCevHW7gX6sx6ZCDLse1k/d00RbMo7FBC+t wVquhZ43MtBLI3OWABWocyP4/o3g2R3yV0ubc93s8bUEq4XV/FSnghZmd4LeBxCd pqQQAIuB1V3xX96XGut6VdJl+t+MWlR34veaTFTn8BGIs1f7DjY= =02gx -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-webpack-stats-plugin_0.2.1-1_source.changes
node-webpack-stats-plugin_0.2.1-1_source.changes uploaded successfully to localhost along with the files: node-webpack-stats-plugin_0.2.1-1.dsc node-webpack-stats-plugin_0.2.1.orig.tar.gz node-webpack-stats-plugin_0.2.1-1.debian.tar.xz node-webpack-stats-plugin_0.2.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-worker-loader_2.0.0-1_amd64.changes
node-worker-loader_2.0.0-1_amd64.changes uploaded successfully to localhost along with the files: node-worker-loader_2.0.0-1.dsc node-worker-loader_2.0.0.orig.tar.gz node-worker-loader_2.0.0-1.debian.tar.xz node-worker-loader_2.0.0-1_all.deb node-worker-loader_2.0.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] status of acorn git repo - build is failing
On 9/23/18 8:28 PM, Bastien ROUCARIES wrote: > On Fri, Sep 21, 2018 at 4:53 PM Pirate Praveen > wrote: >> >> Hi, >> >> Can someone confirm if you can build acorn from git repo? I tried master >> and debian/5.5.3+ds3-1 both failed. > > Did you see it is a multiple tar ? No. It did not have any README.Source and watch file had only a single entry. signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On 9/24/18 4:05 PM, Bastien ROUCARIES wrote: > No it is quite easy with newer fakeupstream support. It a joy, Did you try ? 1. Well, we don't always use the fakeupstream. Most of the time it is github tarballs. 2. It still involve manual effort in multiple packages rather than do it once for all (and manual work only when necessary). signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On Mon, Sep 24, 2018 at 12:24 PM Pirate Praveen wrote: > > > > On 2018, സെപ്റ്റംബർ 24 2:28:00 PM IST, Bastien ROUCARIES > wrote: > >On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen > > wrote: > >> > >> On 9/24/18 2:09 PM, Bastien ROUCARIES wrote: > >> >> I think it is over engineering and making things unnecessarily > >complex. This can be a fallback option if a separate version of type > >definition is required instead of the centrally shipped version. > >> > And how to you keep version in sync ? > >> > >> You always ship the latest in node-typescript-types package and ship > >> separate definitions only in case something don't work. I don't think > >we > >> have to keep it strictly in sync with the node modules. For example, > >we > >> have nodejs 8.11.2 but @types/node only has 8.10.x. > > > >I believe it is quite fragile compared to > >https://wiki.debian.org/Javascript/GroupSourcesTutorial > > I think the type definitions don't change for every js code change so its not > as fragile. If it really change to breaking builds, then only we need to do > the extra work of adding it to corresponding node package. Adding multiple > tarballs is real pain and that has to be the last resort I think. No it is quite easy with newer fakeupstream support. It a joy, Did you try ? Bastien > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On 2018, സെപ്റ്റംബർ 24 2:28:00 PM IST, Bastien ROUCARIES wrote: >On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen > wrote: >> >> On 9/24/18 2:09 PM, Bastien ROUCARIES wrote: >> >> I think it is over engineering and making things unnecessarily >complex. This can be a fallback option if a separate version of type >definition is required instead of the centrally shipped version. >> > And how to you keep version in sync ? >> >> You always ship the latest in node-typescript-types package and ship >> separate definitions only in case something don't work. I don't think >we >> have to keep it strictly in sync with the node modules. For example, >we >> have nodejs 8.11.2 but @types/node only has 8.10.x. > >I believe it is quite fragile compared to >https://wiki.debian.org/Javascript/GroupSourcesTutorial I think the type definitions don't change for every js code change so its not as fragile. If it really change to breaking builds, then only we need to do the extra work of adding it to corresponding node package. Adding multiple tarballs is real pain and that has to be the last resort I think. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#903336: marked as done (node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md"))
Your message dated Mon, 24 Sep 2018 10:05:39 + with message-id and subject line Bug#903336: fixed in node-babel-plugin-add-module-exports 0.2.1-3 has caused the Debian Bug report #903336, regarding node-babel-plugin-add-module-exports: FTBFS in buster/sid (dh_installdocs: Cannot find "README.md") to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-babel-plugin-add-module-exports Version: 0.2.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i fakeroot debian/rules binary-indep dh binary-indep dh_testroot -i dh_prep -i dh_install -i dh_installdocs -i dh_installdocs: Cannot find (any matches for) "README.md" (tried in .) debian/rules:8: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-babel-plugin-add-module-exports.html [ Note: There has been a recent change in debhelper behaviour, the current behaviour is the intended one. See Bug #903133 for details ]. Thanks. --- End Message --- --- Begin Message --- Source: node-babel-plugin-add-module-exports Source-Version: 0.2.1-3 We believe that the bug you reported is fixed in the latest version of node-babel-plugin-add-module-exports, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-babel-plugin-add-module-exports package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Sep 2018 15:17:23 +0530 Source: node-babel-plugin-add-module-exports Binary: node-babel-plugin-add-module-exports Architecture: source Version: 0.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Description: node-babel-plugin-add-module-exports - Babel plugin for default module.exports like babel version 5 Closes: 903336 Changes: node-babel-plugin-add-module-exports (0.2.1-3) unstable; urgency=medium . * Stop trying to install a not shipped README.md. (Closes: #903336) (Thanks to Adrian Bunk) * Use salsa.debian.org in Vcs-* fields * Bump debhelper compatibility level to 11 * Bump Standards-Version to 4.2.1 (no changes needed) Checksums-Sha1: 0eff0230233ef7bfcc2588009d550ac1964ed46d 2277 node-babel-plugin-add-module-exports_0.2.1-3.dsc be3cb72fcf574580f867732bd89a9064368b5587 2452 node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz b71b73b534c31741b699adc3e160d69a751f96fe 6171 node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo Checksums-Sha256: 17235238dce4e3419ce0a6c9a205c046dce3f03a8af8116e52001c178bfdab35 2277 node-babel-plugin-add-module-exports_0.2.1-3.dsc bde264adb2d479c4ffe0daa95901ec2700b2a9ffa30ccac20b96819e8d916dbb 2452 node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz 320ec7481260ae35c9a4201f9de762ca4a0ca8c28c2ffb2a49c3e39455133402 6171 node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo Files: 67034960b6b3be4372a372b6052b94cf 2277 javascript optional node-babel-plugin-add-module-exports_0.2.1-3.dsc 99783f1e4e520dc2f0bec287978bc7b8 2452 javascript optional node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz bff61cd94a5eab866989c1c26e68f111 6171 javascript optional node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAluotGIACgkQzh+cZ0US
[Pkg-javascript-devel] Processing of node-babel-plugin-add-module-exports_0.2.1-3_source.changes
node-babel-plugin-add-module-exports_0.2.1-3_source.changes uploaded successfully to localhost along with the files: node-babel-plugin-add-module-exports_0.2.1-3.dsc node-babel-plugin-add-module-exports_0.2.1-3.debian.tar.xz node-babel-plugin-add-module-exports_0.2.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen wrote: > > On 9/24/18 2:09 PM, Bastien ROUCARIES wrote: > >> I think it is over engineering and making things unnecessarily complex. > >> This can be a fallback option if a separate version of type definition is > >> required instead of the centrally shipped version. > > And how to you keep version in sync ? > > You always ship the latest in node-typescript-types package and ship > separate definitions only in case something don't work. I don't think we > have to keep it strictly in sync with the node modules. For example, we > have nodejs 8.11.2 but @types/node only has 8.10.x. I believe it is quite fragile compared to https://wiki.debian.org/Javascript/GroupSourcesTutorial -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On 9/24/18 2:09 PM, Bastien ROUCARIES wrote: >> I think it is over engineering and making things unnecessarily complex. This >> can be a fallback option if a separate version of type definition is >> required instead of the centrally shipped version. > And how to you keep version in sync ? You always ship the latest in node-typescript-types package and ship separate definitions only in case something don't work. I don't think we have to keep it strictly in sync with the node modules. For example, we have nodejs 8.11.2 but @types/node only has 8.10.x. signature.asc Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On Mon, Sep 24, 2018 at 9:25 AM Pirate Praveen wrote: > > > > On 2018, സെപ്റ്റംബർ 23 8:26:25 PM IST, Bastien ROUCARIES > wrote: > >types node should go to parent package. i means node-types-acorn > >should go to package node-acorn using fakeuptstream multiple tar > >improvement if needed > > > > I think it is over engineering and making things unnecessarily complex. This > can be a fallback option if a separate version of type definition is required > instead of the centrally shipped version. And how to you keep version in sync ? Bastien > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review
Le 13/09/2018 à 11:16, Xavier a écrit : > Le 11/09/2018 à 19:48, Pirate Praveen a écrit : >> >> On 9/11/18 10:45 PM, Jérémy Lal wrote: >>> Hi Xavier, >>> >>> The example in Provides section should be written >>> Provides: node-ta, node-tb >>> ? >> >> I think there should not be Provides as it implies sharing, which will >> negate the reason why we are embedding in the first place. > > Hello, > > I updated https://wiki.debian.org/Javascript/GroupSourcesTutorial to > write a ~policy to choose to embed or not and to export or not. Please > review it > > Cheers, > Xavier Hi all, I rewrote uscan and my work has been accepted by devscripts team (no behavior change for now but OO rewrite will help a lot). If you agree, I can add the same embedding system in uscan than I've done for fakeupstream.cgi Cheers, Xavier -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On 2018, സെപ്റ്റംബർ 23 8:26:25 PM IST, Bastien ROUCARIES wrote: >types node should go to parent package. i means node-types-acorn >should go to package node-acorn using fakeuptstream multiple tar >improvement if needed > I think it is over engineering and making things unnecessarily complex. This can be a fallback option if a separate version of type definition is required instead of the centrally shipped version. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On 2018, സെപ്റ്റംബർ 24 6:24:50 AM IST, Julien Puydt wrote: >Hi, > >Le 23/09/2018 à 16:44, Pirate Praveen a écrit : >> On 9/23/18 5:13 PM, Julien Puydt wrote: >>> What do you think of the attached script? It assumes the upstream >>> DefinitelyTyped tree is in "DefinitelyTyped.upstream" as it's the >layout >>> I use for my experiment, and generates a "control" file and a bunch >of >>> "node-types-*.install" files. >> >> Did you check node-typescript-types source? It just downloads the >> tarballs from npm registry. I think that is a better approach (only >ship >> the definitions we want instead of all) and instead of creating many >> more binary packages, a provides should be sufficient (if at all >required). >> > >Did you see the script was detecting which packages are in Debian, and >only then shipped them? Here I have: > >jpuydt@nox:~/Debian/DefinitelyTyped$ python3 build_control.py >Reading package lists... Done >Building dependency tree >Reading state information... Done >490 node-types-* generated and 4266 not considered It'd add 490 new binary packages, which I don't think will make ftp masters happy. Even this much is unnecessary I think. Instead of looking at a node package being in Debian as a criteria, I think we can add them only if a package actually build depend on it. >so yes, the source tree has everything, but it's only packaging as >binary the necessary files... > >In my first mail I think proposed to ship what is really often a >*single >file* within each package separately ; that sounds the least complex >(no >need for fancy features in a fakeupstream, no need for a complex script > >to build thousands of packages...). -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-sourcemap-codec_1.4.3-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 24 Sep 2018 07:41:02 +0200 Source: node-sourcemap-codec Binary: node-sourcemap-codec Architecture: source all Version: 1.4.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Julien Puydt Description: node-sourcemap-codec - Encode/decode sourcemap mappings Changes: node-sourcemap-codec (1.4.3-1) unstable; urgency=medium . * New upstream release. * Refresh packaging: - Use my debian.org mail address. - Use salsa in Vcs-* fields. - Bump dh compat to 11. - Bump std-ver to 4.2.1. Checksums-Sha1: 488d61e1c14bc393df1f64906d36134d0ad3bf0a 2180 node-sourcemap-codec_1.4.3-1.dsc 229101165aeb449c12964f5837dd37780ece4234 6313 node-sourcemap-codec_1.4.3.orig.tar.gz 3b51b5aef266fd9a115ed21f742e9470370fab05 2352 node-sourcemap-codec_1.4.3-1.debian.tar.xz a3bee8acc1134f78f5de4eb113f3f9f560db8f72 5480 node-sourcemap-codec_1.4.3-1_all.deb a9ed5d09e6ff0c8f04f7ee43cc2b753bc473ce04 6462 node-sourcemap-codec_1.4.3-1_amd64.buildinfo Checksums-Sha256: 694f246706de51e3b3db520b5bbc12f5958d9522419d4d4755572e01f90dd04b 2180 node-sourcemap-codec_1.4.3-1.dsc 8a543776ba04275f5d49c918b9737a0787fcb254f32907c1703a6224e4a119f3 6313 node-sourcemap-codec_1.4.3.orig.tar.gz 05186d261191238407878cbf2b881711599ef8d5612af0705117e9e32ea256af 2352 node-sourcemap-codec_1.4.3-1.debian.tar.xz 38ee20bd43ed4a37c39363c182603aa133b4def5a21dd0046e0c0f241af19e90 5480 node-sourcemap-codec_1.4.3-1_all.deb c06b4c520d76622474072d9a7c07f77f1efa0ef8ff47791010723303dfd3955d 6462 node-sourcemap-codec_1.4.3-1_amd64.buildinfo Files: 9dfe1cc49e90ce63ea04ebef7dd045ed 2180 javascript optional node-sourcemap-codec_1.4.3-1.dsc e76aaadf8bb9be898c8087c1c4714595 6313 javascript optional node-sourcemap-codec_1.4.3.orig.tar.gz c5b7df27461ef7cea830194581c6a07c 2352 javascript optional node-sourcemap-codec_1.4.3-1.debian.tar.xz 2ea4397a94d7553692cc164daec017d3 5480 javascript optional node-sourcemap-codec_1.4.3-1_all.deb 4507efc691f9ea0523058d257907de79 6462 javascript optional node-sourcemap-codec_1.4.3-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJNBAEBCgA3FiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAluoeTsZHGp1bGllbi5w dXlkdEBsYXBvc3RlLm5ldAAKCRAExTvX/gMFUSPzD/0Sn+LptDT5IwOeJsKxZ5yB Q904MD2Zc2mIWlC+GPfL5DYXB5eEqjdfw2pK7XAIzLsfNR7PyEvRozJKpPQN++0Y LCEoRfyTHcoKg+5sUCCe12xkQXfM3Flgh/dGfWdEOMGSYisTMnr39FvwylbKFBqS 1Im5gWbfSqWcagkZp33voqsC2+/6/3bPiN+P9uPeuih9O+52EfH47lCIo+jdQg8e SqwPNdub71ATsosbGu5sNXevnecUm2r+ua2KYVw4X/Rz8aV1AvvSahb/tPwFZx31 SXDgujjIFYZ6vF9UDQGIwafaAuXxWl9Q5dyqYZxppOiHd4V+ZfnINbVz9TUcC1kx ZL8IuJv7W47gINPM3DCKE6VhcNHPmEu86hg08oC5jFet6c0vY08GfrP5Q1hjTx0d iwPYsRL2Q32sTYmPcINQAupGQFtoBdJTAzSNt9Afuky+pGBT1Le/N0zbuHeY9cmT K20Ia95A2MdBdcaBdr7xqVDhL5YcvpO6VBDq7m9o+hcBIe7UTTvXHR+yVP9Z794b QyLrxG3rLnh1sH4A5Aj5izY8BjtdJdkQfVVfkwiXeRN+z70vMQJgYHwyL+sssMZS Rv0WSh2hwNu1lg7yLrBypz/bxWHZ59NoiDnNMDo28/uKCWKxvVzAM4C//QlvLijr yUamQReIpuomQNsUqbhB8Q== =+uwZ -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-sourcemap-codec_1.4.3-1_amd64.changes
node-sourcemap-codec_1.4.3-1_amd64.changes uploaded successfully to localhost along with the files: node-sourcemap-codec_1.4.3-1.dsc node-sourcemap-codec_1.4.3.orig.tar.gz node-sourcemap-codec_1.4.3-1.debian.tar.xz node-sourcemap-codec_1.4.3-1_all.deb node-sourcemap-codec_1.4.3-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
