debian – Ansible package module keeps installing packages

We hava a mixture of CentOS, RedHat, Debian and Ubuntu servers all over the place. I am trying to install generic packages that have the same name for all Distros. The package module seems to work only on CentOS / Redhat boxes, but on Debian boxes it keeps on installing the package. After the script completes the packages are not installed. Rerun the script and same thing. I am running Ansible on the latest Mac OS and the version is 2.9.11

What am I missing to get this to work on Debian systems?

I know that as a workaround I can use when: ansible_distribution and determine what version I am running, but that means I have to make the script longer and type the packages twice.

## Installs Generic OS independent packages ##
- name: "Installs base packages"
    name:  "{{ item }}"
    state: present
    - tcpdump 
    - wget 
    - screen 

For package managers like pip, is it a better practice to install packages with the `–user` flag?

I understand that for most package managers (pip, brew, TeX tlmgr, etc) packages are typically not audited, so there are some inherent security risks in using these package managers. Sometimes the package repositories aren’t trustworthy either.

Would it be a better practice to install all packages with the --user flag? This is in the context of a user who does not normally have root privileges.

I have ubuntu xenial 16.04 how to get new versions of packages?

For example the cmake in my repository appears as 3.5 but my professor’s appears as 3.16 which I need to run doxygen. How can I get this new version in my old ubuntu?

Install packages via pip

Encountered the next error while trying to pip install matplotlib
Don’t know what to do, it managed to install small packages as tqdm or requests, but failed at something like pandas, torch, numpy, etc.Screenshot of the error

HYIP combo packages to start an HYIP Business – HYIPs

Zeligz HYIP comes with HYIP combo packages to create and manage the HYIP website. In this combo, you can get all things that you required for your HYIP business. In their Best HYIP Script, you will get every functionality at an affordable cost. To get the details visit Zeligz Web Store.

Reseller packages created not syncing well

i got a VPS which i made some few reseller cpanel packages… i had a difficult time setting it up with WHMCS…
I somehow got it w… | Read the rest of

Unity Prevent reloading of edited files packages

I had to make a change in the existing Universal Rendering Pipeline’s ShadowCaster2D.cs to suit my needs. But every time I reload the project, the file gets reset. How do I prevent this?

The file that I need to keep is found in the following path:

(Unity Project path)LibraryPackageCachecom.unity.render-pipelines.universal@7.1.7Runtime2DShadowCaster2D.cs

mojave – How can I stop validation of packages hanging for OFXFuse

OSXFuse and Veracrypt were working until I reinstalled Mojave 10.14.6

When I try to reinstall OFXFuse (including option for compatibility layer for legacy MacFUSE file systems) it hangs near the end of the “validation of packages”:

Validating packages hangs

It installs without that option, but on mounting a volume in Veracrypt, I then get the same error I had after reinstalling Mojave, which is why I want to reinstall OFXFuse:

Veracrypt error

Can someone please explain how to avoid OSXFuse installation hanging at “validation of packages”?


can’t install npm package : E: Unable to correct problems, you have held broken packages

I tried to install npm package but it still gave the same output :
check here the screenshot

I even try this solution : npm can't be installed
but still the same error occured !

plz help me !

javascript – Should published npm packages target ES5 syntax?

A bit of background:

I’ve been using Webpack with babel-loader for a while and overall the experience has been hugely positive.

Yesterday, I published an npm package of my own (to a private registry), and installed it into my “main” project that uses Webpack.

What I was surprised to find was that when I built the main project with Webpack, the code from my npm package was not transpiled into ES5 syntax, but retained all the ES6 syntax that was in it.

It appears this is because my webpack.config has this exclude setting, which is strongly recommended by the babel-loader documentation and included in its examples:

   test: /.m?js$/,
   exclude: /(node_modules|bower_components)/,     // <--  here
   use: {
      loader: 'babel-loader',
      options: {
          presets: ('@babel/preset-env')

This much makes perfect sense. What confuses me is that I have never encountered this situation before, across the hundreds of packages and dependencies I’ve consumed in my projects.

This makes me wonder if every one of those packages was transpiled to ES5 syntax before publishing to NPM. Up until now, I had assumed that people just published the code they had, and that Webpack+babel-loader took care of the necessary transpilation.

So my question is:

Is there some unwritten rule that NPM packages that have any possibility of being used in IE should be transpiled to ES5 syntax before npm publishing? Or is there something that I’m missing?