| Summary: | dev-python/pyzor - pyzord should not run as root | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Benny Pedersen <me> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | me |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
pyzord ebuild
my fix for the non working configs fixed config |
||
|
Description
Benny Pedersen
2008-04-05 19:01:32 UTC
Created attachment 148773 [details]
pyzord ebuild
i have lost if i have made som bugs in here, please just help me make it stable
Created attachment 148775 [details, diff]
my fix for the non working configs
fix is that docs says that : needs space around it, but this does not work here
Comment on attachment 148775 [details, diff] my fix for the non working configs diff -u pyzor/access pyzor-new/access --- pyzor/access 2002-07-02 21:44:12.000000000 +0200 +++ pyzor-new/access 2006-12-17 22:09:44.000000000 +0100 @@ -1,2 +1,2 @@ -ping check : anonymous : allow -ALL : bob : allow +check ping:anonymous:allow +check report ping whitelist:bob:allow diff -u pyzor/config pyzor-new/config --- pyzor/config 2002-06-12 00:00:56.000000000 +0200 +++ pyzor-new/config 2008-04-05 21:20:36.000000000 +0200 @@ -1,8 +1,13 @@ +[client] +ServersFile = /var/lib/pyzord/servers +AccountsFile = /var/lib/pyzord/accounts +# DiscoverServersURL = http://pyzor.sourceforge.net/cgi-bin/inform-servers-0-3-x + [server] -Port = 9999 +Port = 24441 ListenAddress = 127.0.0.1 -AccessFile = access -PasswdFile = passwd - -[client] -ServersFile = servers +LogFile = /var/log/pyzord/pyzord.log +PidFile = /var/run/pyzord/pyzord.pid +DigestDB = /var/lib/pyzord/db +PasswdFile = /var/lib/pyzord/passwd +AccessFile = /var/lib/pyzord/access diff -u pyzor/passwd pyzor-new/passwd --- pyzor/passwd 2002-06-12 03:09:49.000000000 +0200 +++ pyzor-new/passwd 2008-04-05 20:16:44.000000000 +0200 @@ -1 +1 @@ -bob : 8da9f54058c34e383e997f45d6eb74837139f83b +bob:8da9f54058c34e383e997f45d6eb74837139f83b diff -u pyzor/servers pyzor-new/servers --- pyzor/servers 2002-04-22 00:56:30.000000000 +0200 +++ pyzor-new/servers 2006-11-08 03:15:46.000000000 +0100 @@ -1 +1 @@ -127.0.0.1:9999 +127.0.0.1:24441 Comment on attachment 148775 [details, diff]
my fix for the non working configs
not working
Created attachment 148781 [details, diff]
fixed config
missed subdirs
I'm unsure what you are filing a bug about. Could you please tell me the issue you are trying to fix? pyzord is in current ebuild not configured to run as other then root by default as is now, i changed my own to run as non root user since there is no need to have it running as root, thats basicly why i make a bug on it and i found that docs olso have config problems when followed it will not work with the accouncs, i have tested my configs to work, it have take my long time to find that it was just space around : in the config files Hope you guys have enough info to know what Benny is trying to accomplish. Hello Benny,
First, thanks for your report and sorry it took so long to have this bug looked at.
Have you tried to report this to upstream? it seems that what you are trying to accomplish would distort the package a big deal from what upstream has. Please, contact upstream on this issue and then you can reopen the bug.
Best regards,
just posted to pyzor maillist today and waiting see what will happend upstream, i cant make stable ebuilds for something that is not much stable non existing or even working as pyzord pyzor client is stable, but pyzord was never really tested imho dev-python/pyzor-0.5.0-r1 marked stable in portage, but it have depricated calls in python 2.6 pyzord is still in random setup :( https://sourceforge.net/apps/trac/pyzor/ticket/117 this is the bug i have now, why is it stable in portage ? :( @Benny; this seems to fall through the cracks a bit. Looks of it from a few minutes digging about, you're trying to do two things- 1) depriv pyzor 2) update the default configuration that comes with it to compensate for upstream not getting around to actually doing releases anytime recently 3) issues w/ deprecated module access gumming up the spamd integration. #2 in particular is of interest- #3 also. Pretty much, bug fix enabling it to be usable/useful is the core concern- depriving is features on top of that. Can you try splitting patches to the ebuild and source for this, attaching it here please? i will begin work on this one when 0.6 gets released, its to much problem with 0.5 imho to get something stable can we bump versions ? Start by opening a bug for it, shouldn't be a problem. pyzor now has (~)1.0.0 in portage. Declaring this obsolete |
