On Sun Jun 26, 2022 at 04:33:24PM +0000, Dimitri Karamazov wrote:
> On Tue, May 31, 2022 at 10:10:59AM +0200, Pascal Stumpf wrote:
> > Here's an update to I2P 1.8.0. Working fine on my router so far.
> >
> > ok?
> I appreciate the help and the update works well.
Committed, thanks!
>
> Regards,
> Dimitri
> >
> > Index: Makefile
> > ===================================================================
> > RCS file: /data/cvs/ports/net/i2p/Makefile,v
> > retrieving revision 1.15
> > diff -u -p -r1.15 Makefile
> > --- Makefile 21 May 2022 11:38:03 -0000 1.15
> > +++ Makefile 25 May 2022 18:52:59 -0000
> > @@ -2,9 +2,8 @@ COMMENT= i2p routing protocol
> >
> > GH_ACCOUNT= i2p
> > GH_PROJECT= i2p.i2p
> > -GH_TAGNAME= i2p-1.7.0
> > +GH_TAGNAME= i2p-1.8.0
> > DISTNAME= ${GH_TAGNAME}
> > -REVISION= 1
> >
> > CATEGORIES= net
> >
> > Index: distinfo
> > ===================================================================
> > RCS file: /data/cvs/ports/net/i2p/distinfo,v
> > retrieving revision 1.6
> > diff -u -p -r1.6 distinfo
> > --- distinfo 8 Mar 2022 00:56:24 -0000 1.6
> > +++ distinfo 25 May 2022 18:53:07 -0000
> > @@ -1,2 +1,2 @@
> > -SHA256 (i2p-1.7.0.tar.gz) = KTGe388o9ed/u1yyH7Gij7hG0iQr4sZ5z8WmEyxfYb4=
> > -SIZE (i2p-1.7.0.tar.gz) = 37867228
> > +SHA256 (i2p-1.8.0.tar.gz) = AYQyEGkD8KqdzJ9q0wKFbaPhlfcwumHO3ek/nkW0OtQ=
> > +SIZE (i2p-1.8.0.tar.gz) = 38024343
> > Index: pkg/PLIST
> > ===================================================================
> > RCS file: /data/cvs/ports/net/i2p/pkg/PLIST,v
> > retrieving revision 1.6
> > diff -u -p -r1.6 PLIST
> > --- pkg/PLIST 8 Mar 2022 00:56:24 -0000 1.6
> > +++ pkg/PLIST 25 May 2022 19:01:02 -0000
> > @@ -18,9 +18,14 @@ share/i2p/LICENSE.txt
> > share/i2p/blocklist.txt
> > share/i2p/certificates/
> > share/i2p/certificates/family/
> > +share/i2p/certificates/family/SUNYSB.crt
> > +share/i2p/certificates/family/bandura.crt
> > share/i2p/certificates/family/gostcoin.crt
> > share/i2p/certificates/family/i2p-dev.crt
> > share/i2p/certificates/family/i2pd-dev.crt
> > +share/i2p/certificates/family/memcpy.crt
> > +share/i2p/certificates/family/mibhq.crt
> > +share/i2p/certificates/family/stormycloud.crt
> > share/i2p/certificates/family/volatile.crt
> > share/i2p/certificates/news/
> > share/i2p/certificates/news/ampernand_at_gmail.com.crt
> > @@ -39,8 +44,10 @@ share/i2p/certificates/reseed/creativeco
> > share/i2p/certificates/reseed/echelon3_at_mail.i2p.crt
> > share/i2p/certificates/reseed/hankhill19580_at_gmail.com.crt
> > share/i2p/certificates/reseed/hottuna_at_mail.i2p.crt
> > +share/i2p/certificates/reseed/i2p-reseed_at_mk16.de.crt
> > share/i2p/certificates/reseed/igor_at_novg.net.crt
> > share/i2p/certificates/reseed/lazygravy_at_mail.i2p.crt
> > +share/i2p/certificates/reseed/r4sas-reseed_at_mail.i2p.crt
> > share/i2p/certificates/reseed/rambler_at_mail.i2p.crt
> > share/i2p/certificates/reseed/reseed_at_diva.exchange.crt
> > share/i2p/certificates/router/
>
Thursday, June 30, 2022
Re: USB audio garbled over time
On Thu, Jun 30, 2022 at 03:11:18PM -0700, Courtney wrote:
> Hello everyone,
>
> I am running OpenBSD -current branch right now. I have a FiiO E10k plugged
> into my board. Here is the part of the dmesg when it is connected
>
> Jun 30 15:02:48 towerDefense /bsd: uaudio0 at uhub0 port 14 configuration 1
> interface 2 "FiiO DigiHug USB Audio" rev 1.10/0.01 addr 6
> Jun 30 15:02:48 towerDefense /bsd: uaudio0: class v1, full-speed, sync,
> channels: 2 play, 2 rec, 3 ctls
> Jun 30 15:02:48 towerDefense /bsd: audio1 at uaudio0
>
> I have been trying to pinpoint an issue where after a time of being away
> from my computer,
> when I come back my audio isn't behaving. I'm not an audio guy so I will
> probably mess
> up some terms, sorry. The pitch sounds right but the audio has a lot of
> static in it. Normally
> this happens after I walk away from my computer and come back maybe an hour
> later. It
> doesn't go into any sleep state, only power efficiency mode that the
> monitors handle on their
> own. An rcctl restart sndiod doesn't solve the issue, I have to physically
> unplug and plug it,
> then run rcctl restart sndiod and all is back to normal. Nothing appears in
> the logs for me
> to report. What can I look at when I encounter this again to see what is
> being changed
> (if anything)? Or, maybe my hardware is just progressively giving up the
> ghost? This has been
> happening for a while now.
When you walk away is it playing? you can run:
audioctl -f /dev/audioctl1
to check device state before and after the walk (empty "mode" means
it's closed, "pause=0" means it's playing or recording)
> Hello everyone,
>
> I am running OpenBSD -current branch right now. I have a FiiO E10k plugged
> into my board. Here is the part of the dmesg when it is connected
>
> Jun 30 15:02:48 towerDefense /bsd: uaudio0 at uhub0 port 14 configuration 1
> interface 2 "FiiO DigiHug USB Audio" rev 1.10/0.01 addr 6
> Jun 30 15:02:48 towerDefense /bsd: uaudio0: class v1, full-speed, sync,
> channels: 2 play, 2 rec, 3 ctls
> Jun 30 15:02:48 towerDefense /bsd: audio1 at uaudio0
>
> I have been trying to pinpoint an issue where after a time of being away
> from my computer,
> when I come back my audio isn't behaving. I'm not an audio guy so I will
> probably mess
> up some terms, sorry. The pitch sounds right but the audio has a lot of
> static in it. Normally
> this happens after I walk away from my computer and come back maybe an hour
> later. It
> doesn't go into any sleep state, only power efficiency mode that the
> monitors handle on their
> own. An rcctl restart sndiod doesn't solve the issue, I have to physically
> unplug and plug it,
> then run rcctl restart sndiod and all is back to normal. Nothing appears in
> the logs for me
> to report. What can I look at when I encounter this again to see what is
> being changed
> (if anything)? Or, maybe my hardware is just progressively giving up the
> ghost? This has been
> happening for a while now.
When you walk away is it playing? you can run:
audioctl -f /dev/audioctl1
to check device state before and after the walk (empty "mode" means
it's closed, "pause=0" means it's playing or recording)
USB audio garbled over time
Hello everyone,
I am running OpenBSD -current branch right now. I have a FiiO E10k plugged
into my board. Here is the part of the dmesg when it is connected
Jun 30 15:02:48 towerDefense /bsd: uaudio0 at uhub0 port 14
configuration 1 interface 2 "FiiO DigiHug USB Audio" rev 1.10/0.01 addr 6
Jun 30 15:02:48 towerDefense /bsd: uaudio0: class v1, full-speed, sync,
channels: 2 play, 2 rec, 3 ctls
Jun 30 15:02:48 towerDefense /bsd: audio1 at uaudio0
I have been trying to pinpoint an issue where after a time of being away
from my computer,
when I come back my audio isn't behaving. I'm not an audio guy so I will
probably mess
up some terms, sorry. The pitch sounds right but the audio has a lot of
static in it. Normally
this happens after I walk away from my computer and come back maybe an
hour later. It
doesn't go into any sleep state, only power efficiency mode that the
monitors handle on their
own. An rcctl restart sndiod doesn't solve the issue, I have to
physically unplug and plug it,
then run rcctl restart sndiod and all is back to normal. Nothing appears
in the logs for me
to report. What can I look at when I encounter this again to see what is
being changed
(if anything)? Or, maybe my hardware is just progressively giving up the
ghost? This has been
happening for a while now.
Courtney
I am running OpenBSD -current branch right now. I have a FiiO E10k plugged
into my board. Here is the part of the dmesg when it is connected
Jun 30 15:02:48 towerDefense /bsd: uaudio0 at uhub0 port 14
configuration 1 interface 2 "FiiO DigiHug USB Audio" rev 1.10/0.01 addr 6
Jun 30 15:02:48 towerDefense /bsd: uaudio0: class v1, full-speed, sync,
channels: 2 play, 2 rec, 3 ctls
Jun 30 15:02:48 towerDefense /bsd: audio1 at uaudio0
I have been trying to pinpoint an issue where after a time of being away
from my computer,
when I come back my audio isn't behaving. I'm not an audio guy so I will
probably mess
up some terms, sorry. The pitch sounds right but the audio has a lot of
static in it. Normally
this happens after I walk away from my computer and come back maybe an
hour later. It
doesn't go into any sleep state, only power efficiency mode that the
monitors handle on their
own. An rcctl restart sndiod doesn't solve the issue, I have to
physically unplug and plug it,
then run rcctl restart sndiod and all is back to normal. Nothing appears
in the logs for me
to report. What can I look at when I encounter this again to see what is
being changed
(if anything)? Or, maybe my hardware is just progressively giving up the
ghost? This has been
happening for a while now.
Courtney
Re: [update] samba-4.15.8
On Thu 30/06/2022 01:12, Jeremie Courreges-Anglas wrote:
>
> Here's an update to the latest samba bugfix release.
> https://www.samba.org/samba/history/samba-4.15.8.html
Builds, and run tested on amd64 at home.
OK bket@
>
> Here's an update to the latest samba bugfix release.
> https://www.samba.org/samba/history/samba-4.15.8.html
Builds, and run tested on amd64 at home.
OK bket@
Upcoming HSE Inspector workshops
| Training built around current real-world expertise and fully aligned with the regulator |
|
Health and Safety Executive - 5N1 Redgrave Court, Merton Road, Bootle, Merseyside L20 7HS
Re: NEW: textproc/py-dict2xml
On Thu, Jun 30, 2022 at 04:34:57PM +0200, Stuart Henderson wrote:
> ok?
ok
>
>
> Information for inst:py3-dict2xml-1.7.1
>
> Comment:
> small utility to convert a Python dictionary into an XML
>
> Description:
> Super Simple utility to convert a python dictionary into an xml string.
>
> from dict2xml import dict2xml
>
> data = {
> 'a': 1,
> 'b': [2, 3],
> 'c': {
> 'd': [
> {'p': 9},
> {'o': 10}
> ],
> 'e': 7
> }
> }
>
> print (dict2xml(data, wrap="all", indent=" "))
>
> Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
>
> WWW: https://github.com/delfick/python-dict2xml
>
--
Tracey Emery
> ok?
ok
>
>
> Information for inst:py3-dict2xml-1.7.1
>
> Comment:
> small utility to convert a Python dictionary into an XML
>
> Description:
> Super Simple utility to convert a python dictionary into an xml string.
>
> from dict2xml import dict2xml
>
> data = {
> 'a': 1,
> 'b': [2, 3],
> 'c': {
> 'd': [
> {'p': 9},
> {'o': 10}
> ],
> 'e': 7
> }
> }
>
> print (dict2xml(data, wrap="all", indent=" "))
>
> Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
>
> WWW: https://github.com/delfick/python-dict2xml
>
--
Tracey Emery
NEW: textproc/py-dict2xml
ok?
Information for inst:py3-dict2xml-1.7.1
Comment:
small utility to convert a Python dictionary into an XML
Description:
Super Simple utility to convert a python dictionary into an xml string.
from dict2xml import dict2xml
data = {
'a': 1,
'b': [2, 3],
'c': {
'd': [
{'p': 9},
{'o': 10}
],
'e': 7
}
}
print (dict2xml(data, wrap="all", indent=" "))
Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
WWW: https://github.com/delfick/python-dict2xml
Information for inst:py3-dict2xml-1.7.1
Comment:
small utility to convert a Python dictionary into an XML
Description:
Super Simple utility to convert a python dictionary into an xml string.
from dict2xml import dict2xml
data = {
'a': 1,
'b': [2, 3],
'c': {
'd': [
{'p': 9},
{'o': 10}
],
'e': 7
}
}
print (dict2xml(data, wrap="all", indent=" "))
Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
WWW: https://github.com/delfick/python-dict2xml
Re: NEW: geo/py-google-i18n-address
On Thu, Jun 30, 2022 at 03:58:47PM +0200, Stuart Henderson wrote:
> ok to import? (needed to update xml2rfc)
>
>
> Comment:
> validation helpers for Google's i18n address database
>
> Description:
> This package contains a copy of Google's i18n address metadata
> repository that contains great data but comes with no uptime guarantees.
>
> Contents of this package will allow you to programatically build address
> forms that adhere to rules of a particular region or country, validate
> local addresses and format them to produce a valid address label for
> delivery.
>
> The package also contains a Python interface for address validation,
> normalization, latinization and formatting.
>
> Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
>
> WWW: https://github.com/mirumee/google-i18n-address
>
ok!
--
Tracey Emery
> ok to import? (needed to update xml2rfc)
>
>
> Comment:
> validation helpers for Google's i18n address database
>
> Description:
> This package contains a copy of Google's i18n address metadata
> repository that contains great data but comes with no uptime guarantees.
>
> Contents of this package will allow you to programatically build address
> forms that adhere to rules of a particular region or country, validate
> local addresses and format them to produce a valid address label for
> delivery.
>
> The package also contains a Python interface for address validation,
> normalization, latinization and formatting.
>
> Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
>
> WWW: https://github.com/mirumee/google-i18n-address
>
ok!
--
Tracey Emery
NEW: geo/py-google-i18n-address
ok to import? (needed to update xml2rfc)
Comment:
validation helpers for Google's i18n address database
Description:
This package contains a copy of Google's i18n address metadata
repository that contains great data but comes with no uptime guarantees.
Contents of this package will allow you to programatically build address
forms that adhere to rules of a particular region or country, validate
local addresses and format them to produce a valid address label for
delivery.
The package also contains a Python interface for address validation,
normalization, latinization and formatting.
Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
WWW: https://github.com/mirumee/google-i18n-address
Comment:
validation helpers for Google's i18n address database
Description:
This package contains a copy of Google's i18n address metadata
repository that contains great data but comes with no uptime guarantees.
Contents of this package will allow you to programatically build address
forms that adhere to rules of a particular region or country, validate
local addresses and format them to produce a valid address label for
delivery.
The package also contains a Python interface for address validation,
normalization, latinization and formatting.
Maintainer: The OpenBSD ports mailing-list <ports@openbsd.org>
WWW: https://github.com/mirumee/google-i18n-address
Re: graphics/openimageio: actually disable dcmtk
Looks like you got really unlucky to hit that!
OK
On 2022/06/30 15:21, Jeremie Courreges-Anglas wrote:
>
> Hi,
>
> (summoning Rafael's cmake-fu)
>
> I spotted an openimageio build error in the current riscv64 bulk:
>
> ninja: error: '/usr/local/lib/libdcmimage.so.0.0', needed by 'lib/libOpenImageIO.so.11.1', missing and no known rule to make it
>
> Setting DCMTK_FOUND=OFF is ineffective (it's not a cached variable /
> user setting). With the following diff I can do the follwing dance
> without hitting an error.
>
> russell /usr/ports/graphics/openimageio$ make clean; doas pkg_add -a dcmtk; make configure; doas pkg_delete dcmtk; make fake package MAKE_JOBS=2
>
> Since it's possible that a package with an unregistered dep on dcmtk
> landed on some user machine, the diff includes a REVISION bump.
>
> ok?
>
> PS: it would be good to audit all the deps and forcefully disable (or
> explicitely enable) them if needed.
>
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/graphics/openimageio/Makefile,v
> retrieving revision 1.62
> diff -u -p -r1.62 Makefile
> --- Makefile 18 Mar 2022 21:10:59 -0000 1.62
> +++ Makefile 30 Jun 2022 13:14:58 -0000
> @@ -8,7 +8,7 @@ GH_PROJECT = oiio
> GH_TAGNAME = Release-$V
> V = 2.2.20.0
> DISTNAME = openimageio-${V}
> -REVISION = 0
> +REVISION = 1
>
> SHARED_LIBS += OpenImageIO 11.1 # 2.2.20
> SHARED_LIBS += OpenImageIO_Util 7.0 # 2.2.20
> @@ -59,7 +59,7 @@ CONFIGURE_ARGS += -DCMAKE_INSTALL_MANDIR
> -DCMAKE_LIBRARY_PATH="${WRKBUILD}/lib:${CMAKE_LIBRARY_PATH}" \
> -DSTOP_ON_WARNING=OFF \
> -DUSE_CCACHE=OFF \
> - -DDCMTK_FOUND=OFF \
> + -DCMAKE_DISABLE_FIND_PACKAGE_DCMTK=TRUE \
> -DUSE_EXTERNAL_PUGIXML=ON \
> -DUSE_OPENCV=OFF \
> -DUSE_OPENVDB=OFF \
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
>
OK
On 2022/06/30 15:21, Jeremie Courreges-Anglas wrote:
>
> Hi,
>
> (summoning Rafael's cmake-fu)
>
> I spotted an openimageio build error in the current riscv64 bulk:
>
> ninja: error: '/usr/local/lib/libdcmimage.so.0.0', needed by 'lib/libOpenImageIO.so.11.1', missing and no known rule to make it
>
> Setting DCMTK_FOUND=OFF is ineffective (it's not a cached variable /
> user setting). With the following diff I can do the follwing dance
> without hitting an error.
>
> russell /usr/ports/graphics/openimageio$ make clean; doas pkg_add -a dcmtk; make configure; doas pkg_delete dcmtk; make fake package MAKE_JOBS=2
>
> Since it's possible that a package with an unregistered dep on dcmtk
> landed on some user machine, the diff includes a REVISION bump.
>
> ok?
>
> PS: it would be good to audit all the deps and forcefully disable (or
> explicitely enable) them if needed.
>
>
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/graphics/openimageio/Makefile,v
> retrieving revision 1.62
> diff -u -p -r1.62 Makefile
> --- Makefile 18 Mar 2022 21:10:59 -0000 1.62
> +++ Makefile 30 Jun 2022 13:14:58 -0000
> @@ -8,7 +8,7 @@ GH_PROJECT = oiio
> GH_TAGNAME = Release-$V
> V = 2.2.20.0
> DISTNAME = openimageio-${V}
> -REVISION = 0
> +REVISION = 1
>
> SHARED_LIBS += OpenImageIO 11.1 # 2.2.20
> SHARED_LIBS += OpenImageIO_Util 7.0 # 2.2.20
> @@ -59,7 +59,7 @@ CONFIGURE_ARGS += -DCMAKE_INSTALL_MANDIR
> -DCMAKE_LIBRARY_PATH="${WRKBUILD}/lib:${CMAKE_LIBRARY_PATH}" \
> -DSTOP_ON_WARNING=OFF \
> -DUSE_CCACHE=OFF \
> - -DDCMTK_FOUND=OFF \
> + -DCMAKE_DISABLE_FIND_PACKAGE_DCMTK=TRUE \
> -DUSE_EXTERNAL_PUGIXML=ON \
> -DUSE_OPENCV=OFF \
> -DUSE_OPENVDB=OFF \
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
>
graphics/openimageio: actually disable dcmtk
Hi,
(summoning Rafael's cmake-fu)
I spotted an openimageio build error in the current riscv64 bulk:
ninja: error: '/usr/local/lib/libdcmimage.so.0.0', needed by 'lib/libOpenImageIO.so.11.1', missing and no known rule to make it
Setting DCMTK_FOUND=OFF is ineffective (it's not a cached variable /
user setting). With the following diff I can do the follwing dance
without hitting an error.
russell /usr/ports/graphics/openimageio$ make clean; doas pkg_add -a dcmtk; make configure; doas pkg_delete dcmtk; make fake package MAKE_JOBS=2
Since it's possible that a package with an unregistered dep on dcmtk
landed on some user machine, the diff includes a REVISION bump.
ok?
PS: it would be good to audit all the deps and forcefully disable (or
explicitely enable) them if needed.
Index: Makefile
===================================================================
RCS file: /cvs/ports/graphics/openimageio/Makefile,v
retrieving revision 1.62
diff -u -p -r1.62 Makefile
--- Makefile 18 Mar 2022 21:10:59 -0000 1.62
+++ Makefile 30 Jun 2022 13:14:58 -0000
@@ -8,7 +8,7 @@ GH_PROJECT = oiio
GH_TAGNAME = Release-$V
V = 2.2.20.0
DISTNAME = openimageio-${V}
-REVISION = 0
+REVISION = 1
SHARED_LIBS += OpenImageIO 11.1 # 2.2.20
SHARED_LIBS += OpenImageIO_Util 7.0 # 2.2.20
@@ -59,7 +59,7 @@ CONFIGURE_ARGS += -DCMAKE_INSTALL_MANDIR
-DCMAKE_LIBRARY_PATH="${WRKBUILD}/lib:${CMAKE_LIBRARY_PATH}" \
-DSTOP_ON_WARNING=OFF \
-DUSE_CCACHE=OFF \
- -DDCMTK_FOUND=OFF \
+ -DCMAKE_DISABLE_FIND_PACKAGE_DCMTK=TRUE \
-DUSE_EXTERNAL_PUGIXML=ON \
-DUSE_OPENCV=OFF \
-DUSE_OPENVDB=OFF \
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
(summoning Rafael's cmake-fu)
I spotted an openimageio build error in the current riscv64 bulk:
ninja: error: '/usr/local/lib/libdcmimage.so.0.0', needed by 'lib/libOpenImageIO.so.11.1', missing and no known rule to make it
Setting DCMTK_FOUND=OFF is ineffective (it's not a cached variable /
user setting). With the following diff I can do the follwing dance
without hitting an error.
russell /usr/ports/graphics/openimageio$ make clean; doas pkg_add -a dcmtk; make configure; doas pkg_delete dcmtk; make fake package MAKE_JOBS=2
Since it's possible that a package with an unregistered dep on dcmtk
landed on some user machine, the diff includes a REVISION bump.
ok?
PS: it would be good to audit all the deps and forcefully disable (or
explicitely enable) them if needed.
Index: Makefile
===================================================================
RCS file: /cvs/ports/graphics/openimageio/Makefile,v
retrieving revision 1.62
diff -u -p -r1.62 Makefile
--- Makefile 18 Mar 2022 21:10:59 -0000 1.62
+++ Makefile 30 Jun 2022 13:14:58 -0000
@@ -8,7 +8,7 @@ GH_PROJECT = oiio
GH_TAGNAME = Release-$V
V = 2.2.20.0
DISTNAME = openimageio-${V}
-REVISION = 0
+REVISION = 1
SHARED_LIBS += OpenImageIO 11.1 # 2.2.20
SHARED_LIBS += OpenImageIO_Util 7.0 # 2.2.20
@@ -59,7 +59,7 @@ CONFIGURE_ARGS += -DCMAKE_INSTALL_MANDIR
-DCMAKE_LIBRARY_PATH="${WRKBUILD}/lib:${CMAKE_LIBRARY_PATH}" \
-DSTOP_ON_WARNING=OFF \
-DUSE_CCACHE=OFF \
- -DDCMTK_FOUND=OFF \
+ -DCMAKE_DISABLE_FIND_PACKAGE_DCMTK=TRUE \
-DUSE_EXTERNAL_PUGIXML=ON \
-DUSE_OPENCV=OFF \
-DUSE_OPENVDB=OFF \
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Fix for xfce4-xsettings with upcoming libX11 update
Hi,
I've been preparing various X libraries updates during r2k22. Among
them is an update to libX11 1.8.1, which add an unconditional
XInitThreads() call during libX11 initialisation.
This is causing a (known) regression in xfce4-settings, causing
xfsettingsd to abort.
This adds a patch to fix the issue.
https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/369
PS: xfsettingd is multi-threaded, and I've no way to be sure that only
one thread will do X calls. So it should have been using XInitThreads
from the start.
diff --git a/x11/xfce4/xfce4-settings/Makefile b/x11/xfce4/xfce4-settings/Makefile
index 19532c9036f..28a71cb0eb4 100644
--- a/x11/xfce4/xfce4-settings/Makefile
+++ b/x11/xfce4/xfce4-settings/Makefile
@@ -2,7 +2,7 @@ COMMENT= Xfce4 settings helpers
XFCE_PROJECT= xfce4-settings
XFCE_VERSION= 4.16.2
-REVISION= 2
+REVISION= 3
# GPLv2
PERMIT_PACKAGE= Yes
diff --git a/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c b/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c
new file mode 100644
index 00000000000..7a47a5aaf56
--- /dev/null
+++ b/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c
@@ -0,0 +1,57 @@
+Fix recursive lock in libX11
+
+Index: xfsettingsd/xsettings.c
+--- xfsettingsd/xsettings.c.orig
++++ xfsettingsd/xsettings.c
+@@ -144,6 +144,12 @@ struct _XfceXSettingsScreen
+ gint screen_num;
+ };
+
++struct _XfceTimestamp
++{
++ Window window;
++ Atom atom;
++};
++
+
+
+ G_DEFINE_TYPE (XfceXSettingsHelper, xfce_xsettings_helper, G_TYPE_OBJECT);
+@@ -1033,11 +1039,11 @@ xfce_xsettings_helper_timestamp_predicate (Display *x
+ XEvent *xevent,
+ XPointer arg)
+ {
+- Window window = GPOINTER_TO_UINT (arg);
++ struct _XfceTimestamp *ts = (struct _XfceTimestamp *)arg;
+
+ return (xevent->type == PropertyNotify
+- && xevent->xproperty.window == window
+- && xevent->xproperty.atom == XInternAtom (xdisplay, "_TIMESTAMP_PROP", False));
++ && xevent->xproperty.window == ts->window
++ && xevent->xproperty.atom == ts->atom);
+ }
+
+
+@@ -1046,17 +1052,18 @@ Time
+ xfce_xsettings_get_server_time (Display *xdisplay,
+ Window window)
+ {
+- Atom timestamp_atom;
++ struct _XfceTimestamp *ts = g_malloc(sizeof(struct _XfceTimestamp));
+ guchar c = 'a';
+ XEvent xevent;
+
+ /* get the current xserver timestamp */
+- timestamp_atom = XInternAtom (xdisplay, "_TIMESTAMP_PROP", False);
+- XChangeProperty (xdisplay, window, timestamp_atom, timestamp_atom,
++ ts->atom = XInternAtom (xdisplay, "_TIMESTAMP_PROP", False);
++ ts->window = window;
++ XChangeProperty (xdisplay, window, ts->atom, ts->atom,
+ 8, PropModeReplace, &c, 1);
+ XIfEvent (xdisplay, &xevent, xfce_xsettings_helper_timestamp_predicate,
+- GUINT_TO_POINTER (window));
+-
++ (XPointer)ts);
++ g_free(ts);
+ return xevent.xproperty.time;
+ }
+
--
2.36.1
--
Matthieu Herrb
I've been preparing various X libraries updates during r2k22. Among
them is an update to libX11 1.8.1, which add an unconditional
XInitThreads() call during libX11 initialisation.
This is causing a (known) regression in xfce4-settings, causing
xfsettingsd to abort.
This adds a patch to fix the issue.
https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/369
PS: xfsettingd is multi-threaded, and I've no way to be sure that only
one thread will do X calls. So it should have been using XInitThreads
from the start.
diff --git a/x11/xfce4/xfce4-settings/Makefile b/x11/xfce4/xfce4-settings/Makefile
index 19532c9036f..28a71cb0eb4 100644
--- a/x11/xfce4/xfce4-settings/Makefile
+++ b/x11/xfce4/xfce4-settings/Makefile
@@ -2,7 +2,7 @@ COMMENT= Xfce4 settings helpers
XFCE_PROJECT= xfce4-settings
XFCE_VERSION= 4.16.2
-REVISION= 2
+REVISION= 3
# GPLv2
PERMIT_PACKAGE= Yes
diff --git a/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c b/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c
new file mode 100644
index 00000000000..7a47a5aaf56
--- /dev/null
+++ b/x11/xfce4/xfce4-settings/patches/patch-xfsettingsd_xsettings_c
@@ -0,0 +1,57 @@
+Fix recursive lock in libX11
+
+Index: xfsettingsd/xsettings.c
+--- xfsettingsd/xsettings.c.orig
++++ xfsettingsd/xsettings.c
+@@ -144,6 +144,12 @@ struct _XfceXSettingsScreen
+ gint screen_num;
+ };
+
++struct _XfceTimestamp
++{
++ Window window;
++ Atom atom;
++};
++
+
+
+ G_DEFINE_TYPE (XfceXSettingsHelper, xfce_xsettings_helper, G_TYPE_OBJECT);
+@@ -1033,11 +1039,11 @@ xfce_xsettings_helper_timestamp_predicate (Display *x
+ XEvent *xevent,
+ XPointer arg)
+ {
+- Window window = GPOINTER_TO_UINT (arg);
++ struct _XfceTimestamp *ts = (struct _XfceTimestamp *)arg;
+
+ return (xevent->type == PropertyNotify
+- && xevent->xproperty.window == window
+- && xevent->xproperty.atom == XInternAtom (xdisplay, "_TIMESTAMP_PROP", False));
++ && xevent->xproperty.window == ts->window
++ && xevent->xproperty.atom == ts->atom);
+ }
+
+
+@@ -1046,17 +1052,18 @@ Time
+ xfce_xsettings_get_server_time (Display *xdisplay,
+ Window window)
+ {
+- Atom timestamp_atom;
++ struct _XfceTimestamp *ts = g_malloc(sizeof(struct _XfceTimestamp));
+ guchar c = 'a';
+ XEvent xevent;
+
+ /* get the current xserver timestamp */
+- timestamp_atom = XInternAtom (xdisplay, "_TIMESTAMP_PROP", False);
+- XChangeProperty (xdisplay, window, timestamp_atom, timestamp_atom,
++ ts->atom = XInternAtom (xdisplay, "_TIMESTAMP_PROP", False);
++ ts->window = window;
++ XChangeProperty (xdisplay, window, ts->atom, ts->atom,
+ 8, PropModeReplace, &c, 1);
+ XIfEvent (xdisplay, &xevent, xfce_xsettings_helper_timestamp_predicate,
+- GUINT_TO_POINTER (window));
+-
++ (XPointer)ts);
++ g_free(ts);
+ return xevent.xproperty.time;
+ }
+
--
2.36.1
--
Matthieu Herrb
Re: USB ethernet adapter?
> Hi,
>
> My PCEngines APU died and I need to rebuild my router.
>
> I'm throwing together an old desktop, but ultimately I'd like to use a
> Raspberry Pi that I bought to play with.
>
> My network configuration needs 2 wired interfaces. I don't have a switch
> that will do vlans, and I don't want to have to configure all of that.
>
> This is only for a 20 Meg (bi directional) connection, so not stressing
> things too much.
>
> What would be a good USB to ethernet (RJ45) adapter that is supported by
> OpenBSD?
>
> Thanks,
> Steve W.
Hi Steve,
this bandwidth will be fine even on a RPI3 (tried here on old link, it was
fine up to 50Mbps without queuing).
I have now a RPI4 4GB and an USB Trendnet usb3 adapter:
rpi4_obsd /bsd: axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX
Elec. Corp. AX88179" rev 3.00/1.00 addr 3
rpi4_obsd /bsd: axen0: AX88179, address xxxxxxxxxx
rpi4_obsd /bsd: rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
that despite some messages like this:
rpi4_obsd /bsd: axen0: checksum err (pkt#1)
will do fine. Nowadays the link is 200/80 Mbps and I use queuing fine. For
20Mbps even the usb2 Linksys 100Mbps ethernet will do for you.
att,
matheus
>
> My PCEngines APU died and I need to rebuild my router.
>
> I'm throwing together an old desktop, but ultimately I'd like to use a
> Raspberry Pi that I bought to play with.
>
> My network configuration needs 2 wired interfaces. I don't have a switch
> that will do vlans, and I don't want to have to configure all of that.
>
> This is only for a 20 Meg (bi directional) connection, so not stressing
> things too much.
>
> What would be a good USB to ethernet (RJ45) adapter that is supported by
> OpenBSD?
>
> Thanks,
> Steve W.
Hi Steve,
this bandwidth will be fine even on a RPI3 (tried here on old link, it was
fine up to 50Mbps without queuing).
I have now a RPI4 4GB and an USB Trendnet usb3 adapter:
rpi4_obsd /bsd: axen0 at uhub0 port 3 configuration 1 interface 0 "ASIX
Elec. Corp. AX88179" rev 3.00/1.00 addr 3
rpi4_obsd /bsd: axen0: AX88179, address xxxxxxxxxx
rpi4_obsd /bsd: rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
that despite some messages like this:
rpi4_obsd /bsd: axen0: checksum err (pkt#1)
will do fine. Nowadays the link is 200/80 Mbps and I use queuing fine. For
20Mbps even the usb2 Linksys 100Mbps ethernet will do for you.
att,
matheus
Re: VMWare / Backup / OpenBSD 7.1 / Quiesce
For anyone interested.
After enabling some debugging on the vmt driver, I discovered that the
message being sent for the quiesce is "vmbackup.startWithOpts ". This
message is not supported by the driver.
Thanks,
Mike
On Mon, 27 Jun 2022 at 15:15, Mike Mercier <mmercier@gmail.com> wrote:
> Hello,
>
> I am testing backups of an OpenBSD 7.1 guest on VMWare 6.7 with a DELL
> Avamar appliance, using the vmimage functionality of the device. The
> OpenBSD backups complete with 'exceptions', the error code being 10020.
> What I see in the Avamar logs is the following:
> --
> vSphere Task failed (application quiesce): 'An error occurred while
> quiescing the virtual machine. See the vitual machine's event log for
> details.'.
> Application consistent snapshot quiesce failure.
> The VM could not be quiesced prior to snapshot creation and this backup
> may not be used as a base for subsequest CBT backup if successful.
> --
>
> Does the OpenBSD VMware tools driver VMT(4) support the VMWare quiesce
> command? Looking through the vmt.c code I believe it does. During my
> testing of the backup and doing ad-hoc snapshots, I did see the following
> message on the OpenBSD guest console once - 'vmt0: aborting quiesce'.
>
> Thanks,
> Mike
>
After enabling some debugging on the vmt driver, I discovered that the
message being sent for the quiesce is "vmbackup.startWithOpts ". This
message is not supported by the driver.
Thanks,
Mike
On Mon, 27 Jun 2022 at 15:15, Mike Mercier <mmercier@gmail.com> wrote:
> Hello,
>
> I am testing backups of an OpenBSD 7.1 guest on VMWare 6.7 with a DELL
> Avamar appliance, using the vmimage functionality of the device. The
> OpenBSD backups complete with 'exceptions', the error code being 10020.
> What I see in the Avamar logs is the following:
> --
> vSphere Task failed (application quiesce): 'An error occurred while
> quiescing the virtual machine. See the vitual machine's event log for
> details.'.
> Application consistent snapshot quiesce failure.
> The VM could not be quiesced prior to snapshot creation and this backup
> may not be used as a base for subsequest CBT backup if successful.
> --
>
> Does the OpenBSD VMware tools driver VMT(4) support the VMWare quiesce
> command? Looking through the vmt.c code I believe it does. During my
> testing of the backup and doing ad-hoc snapshots, I did see the following
> message on the OpenBSD guest console once - 'vmt0: aborting quiesce'.
>
> Thanks,
> Mike
>
Weekly Digest Newsletter: 30 June 2022
| This week's news and updates about health and safety at work |
|
Health and Safety Executive - 5N1 Redgrave Court, Merton Road, Bootle, Merseyside L20 7HS
Subscribe to:
Posts (Atom)