Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Working Great #1

Closed
scoobyd00 opened this issue Oct 12, 2015 · 1 comment
Closed

Working Great #1

scoobyd00 opened this issue Oct 12, 2015 · 1 comment

Comments

@scoobyd00
Copy link

Sorry but couldnt find anywhere else to leave this message.
Downloaded and installed on my raspberry pi 2. Ive had a RTSP network camera and so ive been using a standard fork (mr dave) of motion and running it manually.
Your interface is excellent, its working great with my rtsp camera.
Great work.
@ccrisan
Copy link
Collaborator

ccrisan commented Oct 12, 2015

Thanks for your feedback :)

@caveflyer caveflyer mentioned this issue Oct 30, 2015
Closed
@olliraa olliraa mentioned this issue Jan 12, 2016
Closed
@onejay09 onejay09 mentioned this issue Jan 28, 2016
Closed
@Gordon-1 Gordon-1 mentioned this issue Mar 15, 2016
Closed
@jagd1000 jagd1000 mentioned this issue Apr 23, 2016
Closed
@elstimate elstimate mentioned this issue Jan 4, 2017
Closed
ccrisan added a commit that referenced this issue Jun 2, 2017
@ccrisan
Merge pull request #1 from ccrisan/pine64
bf37f78 
Pine64 Support
@Frankthedoc Frankthedoc mentioned this issue Jun 20, 2017
Open
@adrian0 adrian0 mentioned this issue Sep 6, 2017
Closed
@dshults dshults mentioned this issue Sep 13, 2017
Closed
ccrisan pushed a commit that referenced this issue Oct 3, 2017
@nisargap
Merge pull request #1 from nisargap/S50date-mod
051e5df 
Modified S50date to explicitly specify the date file path
@crw crw mentioned this issue Oct 3, 2017
Closed
@s-moon s-moon mentioned this issue Dec 17, 2017
Closed
@yoshibatora yoshibatora mentioned this issue Dec 7, 2018
Open
ccrisan pushed a commit that referenced this issue Jan 12, 2019
@baruchsiach @jacmet
iperf: bump to version 2.0.12
ad8f435 
Drop patch #1; not needed anymore.

Drop patch #2; fixed upstream in a slightly different way.

Cc: Matt Weber <matthew.weber@rockwellcollins.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
ccrisan pushed a commit that referenced this issue Jan 12, 2019
@gportay @tpetazzoni
qt5virtualkeyboard: fix patch applied to 2.0 version
945a836 
The patch 0001-remove-weird-install-path-for-example.patch using
patch: does not apply properly and needs to be fixed.

The patch was backported from 5.7 [1] with path adaptation in commit
(cb97d94 qt5virtualkeyboard: allow to build with qt5.6), but the
submitted patch did not reflect that said adaptation.

Apply the said patch adaptation (i.e. add missing basic subdirectory) to
apply properly the patch.

Fixes:

   >>> qt5virtualkeyboard 2.0 Patching

   Applying 0001-remove-weird-install-path-for-example.patch using patch:
   patching file examples/virtualkeyboard/basic/basic.pro
   Hunk #1 FAILED at 7.
   1 out of 1 hunk FAILED -- saving rejects to file examples/virtualkeyboard/basic/basic.pro.rej
   make: ***[/home/test/autobuild/run/instance-2/output/build/qt5virtualkeyboard-2.0/.stamp_patched] Error 1

[1]: qt/qtvirtualkeyboard@aef55eb

Signed-off-by: Gaël PORTAY <gael.portay@savoirfairelinux.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
@8OND007 8OND007 mentioned this issue Jan 12, 2019
Closed
ccrisan pushed a commit that referenced this issue Feb 22, 2019
@baruchsiach @ccrisan
openssh: bump to version 7.9p1
8db68e8 
Drop patch #1. uClibc no longer includes pthreads.h indirectly.

Drop patch #2. The sys/param.h header is included indirectly through the
local includes.h header since version 6.8p1.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
@jasaw jasaw mentioned this issue Aug 5, 2019
Closed
@usbrit usbrit mentioned this issue Aug 6, 2019
Open
ccrisan pushed a commit that referenced this issue Sep 29, 2019
@jacmet
package/wolfssl: security bump to version 3.5.17
4e1b3c6 
From the release notes:

This release of wolfSSL includes a fix for 1 security vulnerability.

Medium level fix for potential cache attack with a variant of
Bleichenbacher’s attack.  Earlier versions of wolfSSL leaked PKCS #1 v1.5
padding information during private key decryption that could lead to a
potential padding oracle attack.  It is recommended that users update to the
latest version of wolfSSL if they have RSA cipher suites enabled and have
the potential for malicious software to be ran on the same system that is
performing RSA operations.  Users that have only ECC cipher suites enabled
and are not performing RSA PKCS #1 v1.5 Decryption operations are not
vulnerable.  Also users with TLS 1.3 only connections are not vulnerable to
this attack.  Thanks to Eyal Ronen (Weizmann Institute), Robert Gillham
(University of Adelaide), Daniel Genkin (University of Michigan), Adi Shamir
(Weizmann Institute), David Wong (NCC Group), and Yuval Yarom (University of
Adelaide and Data61) for the report.

The paper for further reading on the attack details can be found at
http://cat.eyalro.net/cat.pdf

Drop now upstreamed patch.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
ccrisan pushed a commit that referenced this issue Sep 29, 2019
@baruchsiach @jacmet
libssh: fix some -Werror=strict-overflow build failures
9952e3b 
Add fixes for some of the build failures caused by strict-overflow
warnings. Patches #1, #2, and #4 are upstream. Patch #3 is pending
upstream.

Fixes:
http://autobuild.buildroot.net/results/923/9239f230629ca4e381af5e8f43989997d9bfde99/
http://autobuild.buildroot.net/results/618/6187b92bcdfd9281683c37906ae74f2e0c5e6d0e/
http://autobuild.buildroot.net/results/9eb/9eb5ed92a923f0c038e3d913289eddc1cda1b62f/

Cc: Scott Fan <fancp2007@gmail.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
@GrueMaster GrueMaster mentioned this issue Nov 29, 2019
Open
@starbasessd starbasessd mentioned this issue Feb 29, 2020
Closed
@starbasessd starbasessd mentioned this issue May 2, 2020
Closed
@starbasessd starbasessd mentioned this issue Jul 20, 2020
Open
popoviciri pushed a commit to popoviciri/motioneyeos that referenced this issue Aug 18, 2020
@ffontaine @yann-morin-1998
package/libusb-compat: set LIBUSB_1_0_SONAME
3a9261d 
LIBUSB_1_0_SONAME is detected since version 0.1.6 and
libusb/libusb-compat-0.1@b6f5a2f

The detection mechanism is based on sed, here are the more relevant
parts:

 shrext_regexp=`echo "$shrext_cmds" | sed 's/\./\\\\./'`
[...]
 [AS_VAR_SET([ac_Lib_SONAME], [`ldd conftest$ac_exeext | grep 'lib[$2]'$shrext_regexp | sed 's/^@<:@ \t@:>@*lib[$2]'$shrext_regexp'/lib[$2]'$shrext_regexp'/;s/@<:@ \t@:>@.*$//'`])])

However, this mechanism is broken with sed 4.7 and will return the
following 'silent' error:

checking for SONAME of libusb-1.0... sed: -e expression motioneye-project#1, char 40: Invalid back reference
unknown

Moreover, it also raises the following build failure on one of the
autobuilder because an empty line is added to LIBUSB_1_0_SONAME:

checking for SONAME of libusb-1.0... checking
libusb-1.0.so.0
checking for GNU extensions of errno.h... no
configure: WARNING: cache variable au_cv_lib_soname_LIBUSB_1_0 contains a newline
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating libusb.pc
config.status: creating libusb-config
config.status: creating Makefile
config.status: creating libusb/Makefile
config.status: creating examples/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default commands
configure: WARNING: unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html, --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6, --disable-nls
configure: WARNING: cache variable au_cv_lib_soname_LIBUSB_1_0 contains a newline
[7m>>> libusb-compat 0.1.7 Building[27m
PATH="/usr/lfs/hdd_v1/rc-buildroot-test/scripts/instance-0/output-1/host/bin:/usr/lfs/hdd_v1/rc-buildroot-test/scripts/instance-0/output-1/host/sbin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1/usr/local/bin:/accts/mlweber1/bin:/accts/mlweber1/libexec/git-core:/accts/mlweber1/usr/bin:/accts/mlweber1
 /usr/local/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin"  /usr/bin/make -j8  -C /usr/lfs/hdd_v1/rc-buildroot-test/scripts/instance-0/output-1/build/libusb-compat-0.1.7/
make[1]: Entering directory `/usr/lfs/hdd_v1/rc-buildroot-test/scripts/instance-0/output-1/build/libusb-compat-0.1.7'
Makefile:284: *** missing separator.  Stop.

We could patch patch m4/au_check_lib_soname.m4 to fix the mechanism
however this is difficult without reproducing the autobuilder failure
and upstream seems dead so just set LIBUSB_1_0_SONAME

Fixes:
 - http://autobuild.buildroot.org/results/12d771d85d30594929cfe3e1c783fc70857e7f5f

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
[yann.morin.1998@free.fr: extract the actual SONAME from the library]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
@lonewolph lonewolph mentioned this issue Aug 29, 2020
Open
@mrmichaelhallett mrmichaelhallett mentioned this issue Oct 28, 2020
Closed
@starbasessd starbasessd mentioned this issue Mar 11, 2021
Closed
@Matthew1471 Matthew1471 mentioned this issue May 23, 2021
Open
@ayrfield2 ayrfield2 mentioned this issue Sep 14, 2021
Open
@starbasessd starbasessd mentioned this issue Sep 22, 2021
Closed
@starbasessd starbasessd mentioned this issue Nov 9, 2021
Closed
@starbasessd starbasessd mentioned this issue Jun 10, 2022
Open
@Gladyww Gladyww mentioned this issue Oct 7, 2022
Open
@starbasessd starbasessd mentioned this issue Oct 29, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ccrisan @scoobyd00