Re: [Slackbuilds-users] Updates - 20170715.1

>> This is also a good reminder for all maintainers NOT TO USE cp -a >> when trying to copy something from $CWD or else it will have a >> strange owner instead of root. If you want to copy things from the >> directory that the source created, cp -a is fine. > > > Potential downside to *not*

Re: [Slackbuilds-users] Updates - 20170715.1 ownership

On 15/07/17 02:53, Willy Sudiarto Raharjo wrote: We are back to our normal weekend public updates and not so many updates this time, but we do have ownership fixes from Sebastian. This is also a good reminder for all maintainers NOT TO USE cp -a when trying to copy something from $CWD or else it

Re: [Slackbuilds-users] Updates - 20170715.1

On Sat, 15 Jul 2017 07:53:27 +0700 Willy Sudiarto Raharjo wrote: > This is also a good reminder for all maintainers NOT TO USE cp -a > when trying to copy something from $CWD or else it will have a > strange owner instead of root. If you want to copy things from the >

[Slackbuilds-users] Updates - 20170715.1

We are back to our normal weekend public updates and not so many updates this time, but we do have ownership fixes from Sebastian. This is also a good reminder for all maintainers NOT TO USE cp -a when trying to copy something from $CWD or else it will have a strange owner instead of root. If you

Re: [Slackbuilds-users] Installing Python packages

On Fri, 14 Jul 2017, Jeremy Hansen wrote: Just so you know, unless there's binaries created outside of the /usr/lib/python-*/ directories, you can safely compile both the python2 and python3 versions in the same SlackBuild. You can just add a second line to run "python3 setup.py install

Re: [Slackbuilds-users] Installing Python packages

Just so you know, unless there's binaries created outside of the /usr/lib/python-*/ directories, you can safely compile both the python2 and python3 versions in the same SlackBuild. You can just add a second line to run "python3 setup.py install --root=$PKG" and each will be installed into their

Re: [Slackbuilds-users] Installing Python packages

On Fri, 14 Jul 2017, Audrius Kažukauskas wrote: virtualenv is included in Python 3 Standard Library as venv[*] module. The name of executable is pyvenv, but it was deprecated recently, although it's still there and usable: The pyvenv script has been deprecated as of Python 3.6 in favor of

Re: [Slackbuilds-users] slackware-xdg-menu: files with wrong user/group ownerships

Hello, apparently, there are others packages might have the same kind of issue. The command below can be used to identify those package : find . -type f -name "*.SlackBuild" | xargs grep --color -E "^[[:space:]]*cp[[:space:]]+[-][a][[:space:]]+[$][C]" In attachment the list of matches returned

Re: [Slackbuilds-users] Installing Python packages

On Fri, 2017-07-14 at 11:17:31 -0700, Rich Shepard wrote: > On Fri, 14 Jul 2017, Larry Hajali wrote: > > I don't know about all of the packages above but I think virtualenv comes > > with python3. > > Not here. I just upgraded python3 from 3.6.0 to 3.6.1. There's no > virtualenv in

Re: [Slackbuilds-users] Installing Python packages

On Fri, 14 Jul 2017, Larry Hajali wrote: I don't know about all of the packages above but I think virtualenv comes with python3. Larry, Not here. I just upgraded python3 from 3.6.0 to 3.6.1. There's no virtualenv in /usr/lib/python3/site-packages/. Rich

Re: [Slackbuilds-users] Installing Python packages

On Fri, Jul 14, 2017 at 9:14 AM, Rich Shepard wrote: > I installed the Python packages virtualenv, virtualenvwrapper, > virtualenv-clone and their dependencies (e.g., tox, py, pluggy, stevedore) > and they're all in /usr/lib/python2.7/site-packages/. > > I don't know

Re: [Slackbuilds-users] slackware-xdg-menu: files with wrong user/group ownerships

Hello Le 14/07/2017 à 18:10, Sebastien BALLET a écrit : > Hello, > > slackware-xdg-menu.SlackBuild generates package containing files with wrong > ownerships : ... > The attached patch fixes that. Also xdgmenumaker from George Vlahavas works well; https://github.com/gapan/xdgmenumaker it's

[Slackbuilds-users] Installing Python packages

I installed the Python packages virtualenv, virtualenvwrapper, virtualenv-clone and their dependencies (e.g., tox, py, pluggy, stevedore) and they're all in /usr/lib/python2.7/site-packages/. While I keep python2 installed for those applications built against it all my new projects use

[Slackbuilds-users] slackware-xdg-menu: files with wrong user/group ownerships

Hello, slackware-xdg-menu.SlackBuild generates package containing files with wrong ownerships : $ tar tvf /tmp/slackware-xdg-menu-0.7.6.2-noarch-1_SBo.tgz | grep -v "root/root" -rw-r--r-- seb/users 6651 2016-12-10 02:10 usr/share/desktop-directories/Development.directory -rw-r--r--

Re: [Slackbuilds-users] flash plugins

On Sat, 24 Jun 2017 08:13:52 -0700 (PDT), Rich Shepard wrote: > > Adobe was about to kill Flash Player in the past, but now they > > decided to continue developing it so now we have 2 type of flash > > player based on their technology >Does it matter which I have