Your message dated Tue, 22 Nov 2016 21:05:03 +
with message-id
and subject line Bug#798043: fixed in lives 2.8.1-1
has caused the Debian Bug report #798043,
regarding lives: creates (and uses) world-writeable directory
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> tag 798043 pending
Bug #798043 [lives] lives: creates (and uses) world-writeable directory
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
798043: http://bugs.debian.org/c
This bug can be closed with the release of LiVES 2.8.1
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
3 more patches - implementing the permissions change as discussed and also
ensuring that umask is employed correctly throughout.
I think these will be the final patches for this issue, assuming there are
no bugs found during testing.
https://sourceforge.net/p/lives/code/2587/
https://sourceforge.
Hi,
On 01/10/16 07:23, salsaman wrote:
> James, I was wondering what action should be taken regarding
> directory/subdirectory permissions for existing users. The options I can
> think of (from simplest to most complex): a) do nothing, only new users
> get the benefit. b) add a note in Release Not
James, I was wondering what action should be taken regarding
directory/subdirectory permissions for existing users. The options I can
think of (from simplest to most complex): a) do nothing, only new users get
the benefit. b) add a note in Release Notes informing users how to update
the directory p
Relevant patches:
https://sourceforge.net/p/lives/code/2574/
https://sourceforge.net/p/lives/code/2576/
https://sourceforge.net/p/lives/code/2578/
https://sourceforge.net/p/lives/code/2579/
https://sourceforge.net/p/lives/code/2580/
___
pkg-multimedia-ma
This has now been fixed. The problem was that the backend (smogrify) needs
to communicate some information to the front end (LiVES) at startup, and to
do so it was creating ~/livestmp (the default working directory on first
time startup) to write some temporary files in.
The default is now set to
Hi,
first of all, I am the main developer of LiVES. Please cc the address
salsaman+li...@gmail.com to all future bugs related to LiVES. You are also
welcome to report bugs on the mailing list or via the issue tracker (
https://sourceforge.net/p/lives/bugs/).
I will look into the issues that you me
Package: lives
Version: 2.4.0~ds0-1+b1
Severity: important
Dear Maintainer,
simply starting `lives` will create a new directory `~/livestmp` (in my home),
which is world read and writeable.
i think this is an absolte no-go.
$ cd ~
$ rm -rf .lives* livestmp
$ lives
[...]
$ ls -lhan livestmp/
tota
10 matches
Mail list logo