[Bug 256885] [NEW PORT] www/py-homeassistant: Open-source home automation platform

2023-01-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256885

xav...@groumpf.org changed:

   What|Removed |Added

 CC||xav...@groumpf.org

--- Comment #20 from xav...@groumpf.org ---
I've compiled the whole stuff, installs flawlessly and runs fine
However homeassistant listen only on 127.0.0.1 instead of 0.0.0.0, which makes
it less useful on a server without a GUI
grep -r 127.0.0.1 returns o a bunch of occurrences, so I don't know how to fix
this
Thanks for the port !
Xavier

-- 
You are receiving this mail because:
You are on the CC list for the bug.


[Bug 256885] [NEW PORT] www/py-homeassistant: Open-source home automation platform

2023-01-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256885

--- Comment #21 from Xavier Humbert  ---
(In reply to Xavier Humbert from comment #20)
Digging in HA docs, II found the variable server_host :

default_config:
  server_host: 0.0.0.0 

Another glitch : PID file cannot be created directly under /var/run, user
homeassistant does not have appropriate rights. 
# mkdir /var/run/homeassistant && chown 570:570 /var/run/homeassistant
and patching rc file accordingly fixes the problem

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Problem reports for python@FreeBSD.org that need special attention

2023-01-29 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
Open|205308 | devel/py-pip and devel/py-virtualenv don't aggree 
Open|240343 | x11-themes/plasma5-breeze-gtk: Fails to build if  
Open|242896 | lang/python*: Fail to package in poudriere (testp 
Open|257362 | lang/python3: Add link for python3-embed.pc where 
Open|258192 | devel/py-pyinstaller: Fails to run on 3.8+. Fix i 
Open|262759 | Python ports that install conflicting files in ge 
Open|257353 | lang/python38: Intermittently fails to build unde 
Open|234981 | graphics/py-wand: Add DOCS option Pass MAINTAINER 
New |268949 | science/py-scipy: Update to 1.10.0
Open|224115 | devel/py-babel directory name != port name
In Progress |258195 | lang/python38: Update to 3.8.12   
In Progress |255025 | textproc/py-chardet: Update to 4.0.0  
New |268594 | math/py-numpy: Update to 1.24.1   
Open|268043 | devel/py-twisted: Consumer ports fail to run: mod 
Open|264426 | www/mitmproxy: Update to 8.0.0 (<=7.0.4 vulnerabl 
Open|264993 | www/mitmproxy: Update to 9.0.1
Open|260448 | [NEW] devel/py-aiosignal: Project to manage callb 

17 problems total for which you should take action.


Re: CHEESESHOP or GH

2023-01-29 Thread Einar Bjarni Halldórsson

Hi Charlie,

On 1/28/23 01:47, Charlie Li wrote:
I commented. This guideline isn't specific to python@ per se, but 
something that applies to all ports: proper release distributions 
(usually source tarballs) are preferred over source code management tags.


For this port, you can go either way, but if you choose to fetch from 
GitHub, make sure to add a comment in the Makefile explaining the 
situation (and maybe reference the upstream issue).


It's unfortunate when individual projects choose to disregard proper 
release engineering practices. Part of our job as port maintainers is to 
serve as that check-and-balance such that if projects want their stuff 
in software repositories, they have to put some consideration as well.




Thank you very much. I saw your comment and learned alot from it. 
Hopefully it'll persuade them to change their mind. If not, I'll switch 
to fetching from github, but I'll make sure to add a comment to the 
Makefile explaining the situation.


.einar