Le 19-11-17 à 08 h 09, Xavier a écrit :
>
> I fixed copyright years
>
Thanks!
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hello team,
Le 19-11-16 à 18 h 00, Thorsten Alteholz a écrit :
>
> please also mention at least
> i18next-17.0.18/test/backward/v1.11.1.compat.js
> in your debian/copyright.
>
I've updated the file d/copyright in the salsa repository [1].
I've looked for other source files with a copyright
Le 17/11/2019 à 13:58, Nicolas Mora a écrit :
> Hello team,
>
> Le 19-11-16 à 18 h 00, Thorsten Alteholz a écrit :
>>
>> please also mention at least
>> i18next-17.0.18/test/backward/v1.11.1.compat.js
>> in your debian/copyright.
>>
>
> I've updated the file d/copyright in the salsa repository
Hi fellow team members,
I was wandering what is the best approach for d/changelog when releasing a
package to unstable after it has been though a few iterations to experimental.
It would seem that the right thing to do is to keep all experimental changelog
entries, and add a new one for
node-yarnpkg_1.19.1-1~bpo10+1_amd64.changes uploaded successfully to localhost
along with the files:
node-yarnpkg_1.19.1-1~bpo10+1.dsc
node-yarnpkg_1.19.1.orig-babel-plugin-transform-inline-imports-commonjs.tar.gz
node-yarnpkg_1.19.1.orig-decode-uri-component.tar.gz
node-js-yaml_3.13.1+dfsg-2~bpo10+1_amd64.changes uploaded successfully to
localhost
along with the files:
node-js-yaml_3.13.1+dfsg-2~bpo10+1.dsc
node-js-yaml_3.13.1+dfsg.orig.tar.xz
node-js-yaml_3.13.1+dfsg-2~bpo10+1.debian.tar.xz
node-js-yaml_3.13.1+dfsg-2~bpo10+1_all.deb
binary:node-js-yaml is NEW.
binary:node-js-yaml is NEW.
source:node-js-yaml 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
binary:yarnpkg is NEW.
binary:yarnpkg is NEW.
source:node-yarnpkg 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.
FYI: The status of the pkg-js-tools source package
in Debian's testing distribution has changed.
Previous version: 0.9.17
Current version: 0.9.18
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
Le 18/11/2019 à 06:35, Xavier a écrit :
> Le 18/11/2019 à 01:23, Nicolas Mora a écrit :
>> Hello,
>>
>> Le 19-11-17 à 16 h 20, Xavier a écrit :
>>>
>>> Take a look at my changes. I think you should provide a browserified
>>> file in /usr/share/javascript (in a separate package).
>>>
>> I added a
pkg-js-tools_0.9.19_sourceonly.changes uploaded successfully to localhost
along with the files:
pkg-js-tools_0.9.19.dsc
pkg-js-tools_0.9.19.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Le 18/11/2019 à 01:23, Nicolas Mora a écrit :
> Hello,
>
> Le 19-11-17 à 16 h 20, Xavier a écrit :
>>
>> Take a look at my changes. I think you should provide a browserified
>> file in /usr/share/javascript (in a separate package).
>>
> I added a separate package called libjs-i18next, but for
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Nov 2019 06:54:44 +0100
Source: node-mocha
Architecture: source
Version: 6.2.0+ds1-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Nov 2019 06:51:08 +0100
Source: pkg-js-tools
Architecture: source
Version: 0.9.19
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes:
Le 17/11/2019 à 14:59, Nicolas Mora a écrit :
> Le 19-11-17 à 08 h 09, Xavier a écrit :
>>
>> I fixed copyright years
>>
> Thanks!
Take a look at my changes. I think you should provide a browserified
file in /usr/share/javascript (in a separate package).
Cheers,
Xavier
--
Pkg-javascript-devel
Hello,
Le 19-11-17 à 16 h 20, Xavier a écrit :
>
> Take a look at my changes. I think you should provide a browserified
> file in /usr/share/javascript (in a separate package).
>
I added a separate package called libjs-i18next, but for some reason, if
I add a file
16 matches
Mail list logo
