; -DPACKAGE_STRING=\"LiVES\ 3.0.2\"
> -DPACKAGE_BUGREPORT=\"https://github.com/salsaman/LiVES/issues\";
> -DPACKAGE_URL=\"http://lives-video.com\"; -DPACKAGE=\"lives\"
> -DVERSION=\"3.0.2\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
All plugins should be placed inside/lib/lives This is where "make
install" will place them.
If the plugins are installed to a non-standard location then you still need
to edit the config file by hand,
the config file is now in ~/.config/lives/settings
If this is an issue then please feel free to c
Sorry, my bad: I forgot to update the constants in the .h files. I was
looking in the .c files by mistake.
Also, I think it should be AV_CODEC_ID_* in the headers (although
AV_CODEC_* seemed to work too).
Please check that you are compiling with the current versions of those
files. There are no instances of CODEC_* any more in those files.
I believe all the issues noted should be fixed now. You will need to
replace the follwoing files:
configure.ac
libweed/weed-compat.h
libweed/weed-compat.pc
plugins/decoders/*
(the weed-compat changes are unrelated, but you will need to update them to
compile the current decoder plugins).
If you have a moment, perhaps you could pull the newly updated files from
lives/lives-plugins/plugins/decoders in subversion (
http://svn.code.sf.net/p/lives/code/trunk) and recompile. It should fix the
FTBFS.
Gabriel.
This bug can be closed with the release of LiVES 2.8.1
This bug can be closed with the release of LiVES 2.8.1
This bug can be closed with the release of LiVES 2.8.1
Thankyou for your detailed investigation Lionel. This issue has now been
addressed in version 2.8.1 of LiVES which should be in the debian
repositiries shortly.
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.
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/
All issues noted above have been fixed. In addition:
- the terminology has been changed throughout to try to be less confusing.
The directory is now referred to as the "LiVES working directory"
everywhere.
For example prefs->tmpdir is now prefs->workdir in the C code, and $tmpdir
is now $workdir i
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
On Thu, Sep 22, 2016 at 7:56 PM, James Cowgill wrote:
>
> Thinking about this some more, there is a slight race condition here if
> the user deletes the file after the checks, but before it's written. I
> think the best fix would break the smogrify API unfortunately. One
> alternative is to use
ents to this bug by sending email and of course I would need to add a
topic to the email. Hopefully just replying will leave it alone then
> On 20/09/16 15:51, salsaman wrote:
> > I would prefer to keep $tmpdir as it is, I dont see any reason to change
> > it to $XDG_CACHE_
I would prefer to keep $tmpdir as it is, I dont see any reason to change it
to $XDG_CACHE_HOME as this variable is only used internally to smogrify.
Also using /lives would be confusing as there is already a .lives file and
lives-dir which are both created in $HOME. Also the user can select the
loc
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
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.
Secondly, there is incorrect information in this bug report.
>>
You'll see that $curtmpdir is set to /tmp/smogrify, via code such as:
$han
LiVES.
Index: libweed/weed-compat.h
===
--- libweed/weed-compat.h (revision 2352)
+++ libweed/weed-compat.h (working copy)
@@ -42,7 +42,7 @@
*/
-/* (C) Gabriel "Salsaman" Finch, 2005 - 2012 */
+/* (C) Gabriel
needed to identify this change.
On Tue, Mar 8, 2016 at 11:15 AM, salsaman wrote:
> Is there a compile time check for this version (e.g.
> LIBAVCODEC_VERSION_MAJOR) or even #ifdef AV_PIX_FMT_RGB24 ?
>
>
>
>
Is there a compile time check for this version (e.g.
LIBAVCODEC_VERSION_MAJOR) or even #ifdef AV_PIX_FMT_RGB24 ?
in libweed/*.pc
A warning about the second change is printed at configure time, the first
is not documented, but it quite likely should be.
Please test and let me know if this fixes the problem for you.
http://lives.sourceforge.net
https://www.openhub.net/accounts/salsaman
On Thu, Oct 23
g (which I hope will work in
all cases):
- #ifndef AV_OPT_TYPE_INT
+ #if FF_API_OLD_AVOPTIONS
leaving the lines in the same place as the original.
Regards
Salsaman.
http://lives.sourceforge.net
https://www.ohloh.net/accounts/salsaman
I am no the packager, I am the upstream developer. Better to ask
Alessio, Current .debs do not have the patch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Yes, as I stated earlier in the comments, you will need the patch
which I indicated.
Salsaman.
main developer, LiVES
http://lives.sourceforge.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
Can we try to get 1.6.2 with this patch into testing ? I understand
there was a freeze very recently for the next stable release.
1.6.2 with this patch would be much better than the existing 1.6.1 version.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
http://lives.svn.sourceforge.net/viewvc/lives/trunk/src/startup.c?r1=1446&r2=1509
Regards,
Salsaman.
http://lives.sourceforge.net
https://www.ohloh.net/accounts/salsaman
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
This is fixed in 1.2.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Please apply the following patches and see if it fixes the problem:
http://lives.svn.sourceforge.net/viewvc/lives/trunk/configure.in?r1=316&r2=306&view=patch
http://lives.svn.sourceforge.net/viewvc/lives/trunk/src/Makefile.am?r1=316&r2=151&view=patch
Gabriel.
http://lives.sf.net
On Sun, September 13, 2009 15:14, Harry Rickards wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/13/09 14:04, Bastian Blank wrote:
>> On Sun, Sep 13, 2009 at 01:20:57PM +0100, Harry Rickards wrote:
>>> On 09/13/09 12:30, Bastian Blank wrote:
I don't see a reason for this exc
il
> 1.0.0-5 is released, or apply the new files in debian/ from SVN. To do
> that download the source of 1.0.0-4 with 'apt-get source lives', and rm
> - -rf the debian/ directory. Then download the new debian/ from SVN with
> 'svn checkout
> http://svn.debian.or
il
> 1.0.0-5 is released, or apply the new files in debian/ from SVN. To do
> that download the source of 1.0.0-4 with 'apt-get source lives', and rm
> - -rf the debian/ directory. Then download the new debian/ from SVN with
> 'svn checkout
> http://svn.debian.or
On Fri, August 21, 2009 19:22, Harry Rickards wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Russ Allbery wrote:
>> Harry Rickards writes:
>>> Russ Allbery wrote:
>>
I'm afraid those dictionaries are wrong, at least as dictionaries are
normally judged. The word is converte
On Tue, July 28, 2009 12:14, Harry Rickards wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Christian Marillat wrote:
>> Harry Rickards writes:
>>
>>> Christian Marillat wrote:
Harry Rickards writes:
>>
>> [...]
>>
The diff in this link doesn't provides packages for the sha
On Tue, July 28, 2009 12:14, Harry Rickards wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Christian Marillat wrote:
>> Harry Rickards writes:
>>
>>> Christian Marillat wrote:
Harry Rickards writes:
>>
>> [...]
>>
The diff in this link doesn't provides packages for the sha
Robert,
it appears that your email is no longer functioning. Please update me with
your new email address.
Gabriel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
OK. How long does approval normally take ?
Also, you should have checked the file list with me first. Libraries like:
./usr/lib/lives/plugins/playback/video/lives2lives_stream.a
./usr/lib/lives/plugins/playback/video/SDL.a
./usr/lib/lives/plugins/effects/realtime/weed/*.a
are redundant, beca
an. could you make
> a tarball release of all this stuff of CVS?
>
> regards,
> guerkan senguen
>
>> Regards,
>> Gabriel "salsaman",
>> http://lives.sourceforge.net
>>
>
>
LiVES 0.9.9.6 has been released today. This version should
On Wed, December 17, 2008 22:50, Robert Millan wrote:
> On Tue, Apr 29, 2008 at 04:01:59PM +0200, Gürkan Sengün wrote:
>> On Tue, April 29, 2008 09:29, Gürkan Sengün wrote:
>> >Dear Salsaman,
>> >
>> >Could you relicense all of your software parts of liv
On Fri, December 19, 2008 19:28, Robert Millan wrote:
> On Thu, Dec 18, 2008 at 01:14:49AM +0100, salsa...@xs4all.nl wrote:
>> >
>> > Additionally your debian/copyright file is incomplete and misses
>> > (C)holders/license data. You have to include all such differences.
>> > Like all of libOSC/*,
On Wed, December 17, 2008 22:50, Robert Millan wrote:
> On Tue, Apr 29, 2008 at 04:01:59PM +0200, Gürkan Sengün wrote:
>> On Tue, April 29, 2008 09:29, Gürkan Sengün wrote:
>> >Dear Salsaman,
>> >
>> >Could you relicense all of your software parts of liv
On Tue, April 29, 2008 11:57, Christian Marillat wrote:
> Gürkan Sengün <[EMAIL PROTECTED]> writes:
>
>>> I still don't understand the necessity to upload Lives in Debian.
>>>
>>> Without mjpegtools you can't encode in mpeg2. Same for transcode or
>>> mencoder who doesn't exist in Debian even if
On Tue, April 29, 2008 11:55, Gürkan Sengün wrote:
>> I still don't understand the necessity to upload Lives in Debian.
>>
>> Without mjpegtools you can't encode in mpeg2. Same for transcode or
>> mencoder who doesn't exist in Debian even if you add a note saying
>> "Lives doesn't work, you need
There are LiVES .debs now at debian-multimedia.org.
All that is required is for somebody to copy these packages into the
main debian repositories.
Salsaman.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
LiVES is now at version 0.9.8, and still there is no full-time debian
maintainer for this package !
How come nobody has picked this up yet ?
Salsaman.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
47 matches
Mail list logo
