Bug#863466: ITP: node-raw-loader -- raw loader module for webpack
Package: wnpp Severity: wishlist Owner: Daniel Ring X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-raw-loader Version : 0.5.1 Upstream Author : Tobias Koppers @sokra * URL : https://github.com/webpack/raw-loader * License : Expat Programming Lang: JavaScript Description : raw loader module for webpack This library is a raw loader module for webpack. This library is a dependency for webpack. Webpack takes code targeted at node.js and adapts it to run in the browser. Node.js comes with an API of its own that is not available in browsers. Webpack exposes this code to programs that are unaware they are running in a browser. Node.js is an event-based server-side JavaScript engine.
Quantic
Hi guys! Is there a "quantic" group or something like that? If any, i'd like to involve in it as a (background, not "former") trainer and industrial engineer. I'm french, in Brittany. Cheers. = == Bien cordialement, *M. Vitrac* mvtec...@gmail.com F-56 VANNES 06-16-62-31-63
Hello! How can I delete Debian from menu before Windows loading?
Hello! I am thinking to use Debian, but later, because I have no time now. How can I delete Debian from menu before Windows loading? Thanks!
Re: Hello! How can I delete Debian from menu before Windows loading?
Le samedi, 27 mai 2017, 21.01:46 h CEST Александр Макаров a écrit : > Hello! > > I am thinking to use Debian, but later, because I have no time now. > > How can I delete Debian from menu before Windows loading? You need to uninstall win32-loader using its' uninstaller, which should be located in `C:\win32-loader\Uninstall.exe` Cheers, OdyX
Re: Hello! How can I delete Debian from menu before Windows loading?
On Sat, May 27, 2017 at 08:35:25PM +0200, Didier 'OdyX' Raboud wrote: > Le samedi, 27 mai 2017, 21.01:46 h CEST Александр Макаров a écrit : > > I am thinking to use Debian, but later, because I have no time now. > > > > How can I delete Debian from menu before Windows loading? > > You need to uninstall win32-loader using its' uninstaller, which should be > located in `C:\win32-loader\Uninstall.exe` I think it's more likely it's about grub. Alexandr: does that menu have a blue background? If so, please google "windows restore mbr" and use one of guides that applies to your version of Windows. It'll be easier as your Windows installation is already bootable so you don't need any rescue media. I can't offer you more detailed assistance, though, as I haven't ran Windows outside a VM for a while. I wish you luck if you ever find the time to try Debian again. Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race.
Bug#863510: ITP: node-readable-stream -- A stream compatibility library for Node.js and browser
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-readable-stream Version : 2.2.9 Upstream Author : FIX_ME upstream author * URL : https://github.com/nodejs/readable-stream#readme * License : Expat Programming Lang: JavaScript Description : A stream compatibility library for Node.js and browser This package is a port to browser context of the well know stream API of Node.js . A stream is an abstract interface for working with streaming data in Node.js. There are many stream objects provided by Node.js. For instance, a request to an HTTP server and process.stdout are both stream instances. . Node.js is an event-based server-side JavaScript engine.
Re: Mitigating the problem of limited security support
Jeremy Bicha schrieb: > understanding is that the Debian Security team has absolutely refused > to extend the "browser exception" (to allow major new versions) to > webkit2gtk, The "browser exception" applies to Chromium and Firefox, which are standalone packages (sans a few addons breaking), but unless webkit provides a long term branch with API stability guarantees, that's not a workable. "Rebase to a new 2.x branch every six months and let's hope that it doesn't break any rdeps" is not a workable solution. Cheers, Moritz
Re: Mitigating the problem of limited security support
On Sat, May 27, 2017 at 5:49 PM, Moritz Mühlenhoff wrote: > The "browser exception" applies to Chromium and Firefox, which are > standalone packages (sans a few addons breaking), but unless webkit > provides a long term branch with API stability guarantees, that's > not a workable. "Rebase to a new 2.x branch every six months and let's > hope that it doesn't break any rdeps" is not a workable solution. webkit2gtk's API has been stable enough for Ubuntu 16.04 LTS. Right now, webkit2gtk 2.16.3 is in experimental with fixes for 3 published CVEs that affect Stretch. What is needed for that version to be allowed in to Stretch now? It is just testing that the rdeps still work? By the way, there are more than twice as many Firefox addons in Debian as there are packages using webkit2gtk. I believe Mozilla has basically committed to breaking several of those addons next year, whereas the webkit2gtk developers try to avoid regressions. Thanks, Jeremy Bicha
Re: Quantic
On Sat, May 27, 2017 at 11:22 PM, Maxime Vitrac wrote: > Is there a "quantic" group or something like that? Could you explain what you mean by quantic? If you are talking about mathematics, the Debian Science team might be interesting to you. https://www.debian.org/blends/ https://wiki.debian.org/DebianScience https://blends.debian.org/science/tasks/mathematics -- bye, pabs https://wiki.debian.org/PaulWise
