Re: [DNG] Why is spamassasin compiling here?

2019-11-07 Thread hal



On 11/6/19 7:53 AM, Dimitris via Dng wrote:

On 11/6/19 3:45 PM, hal wrote:


I've installed the libc6-dev-i386 package to see if it solves it but then I 
wondered what is spamassasin doing compiling things anyway?




https://packages.debian.org/stretch/sa-compile



Thanks. I reinstalled the package (was already installed) and similar 
error. sys/types.h does exist so it's confusing.



# find /usr/ -name 'types.h' -ls
   133512  4 -rw-r--r--   1 root root 3233 Feb  6  2019 
/usr/include/rpc/types.h
   133825  8 -rw-r--r--   1 root root 7563 Feb  6  2019 
/usr/include/x86_64-linux-gnu/bits/types.h
   133630  4 -rw-r--r--   1 root root  113 Sep 20 06:03 
/usr/include/x86_64-linux-gnu/asm/types.h
   172609  0 lrwxrwxrwx   1 root root   31 Feb  6  2019 
/usr/include/sys/types.h -> ../x86_64-linux-gnu/sys/types.h
   132607  4 -rw-r--r--   1 root root  170 Sep 20 06:03 
/usr/include/asm-generic/types.h
   133259  4 -rw-r--r--   1 root root 1844 Sep 20 06:03 
/usr/include/linux/iio/types.h
   133181  4 -rw-r--r--   1 root root 1430 Sep 20 06:03 
/usr/include/linux/types.h


# dir /usr/lib/x86_64-linux-gnu/perl/5.24/CORE/perl.h
-rw-r--r-- 1 root root 235054 Nov 29  2018 
/usr/lib/x86_64-linux-gnu/perl/5.24/CORE/perl.h




# aptitude reinstall sa-compile
The following packages will be REINSTALLED:
  sa-compile
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 
not upgraded.

Need to get 47.5 kB of archives. After unpacking 0 B will be used.
Get: 1 http://deb.devuan.org//merged ascii/main amd64 sa-compile all 
3.4.2-1~deb9u1 [47.5 kB]

Fetched 47.5 kB in 3s (12.5 kB/s)
(Reading database ... 65673 files and directories currently installed.)
Preparing to unpack .../sa-compile_3.4.2-1~deb9u1_all.deb ...
Unpacking sa-compile (3.4.2-1~deb9u1) over (3.4.2-1~deb9u1) ...
Setting up sa-compile (3.4.2-1~deb9u1) ...
Running sa-compile (may take a long time)
In file included from body_0.xs:2:0:
/usr/lib/x86_64-linux-gnu/perl/5.24/CORE/perl.h:689:23: fatal error: 
sys/types.h: No such file or directory

 #include 
   ^
compilation terminated.
make: *** [body_0.o] Error 1
command 'make PREFIX=/tmp/.spamassassin7174sFN7hktmp/ignored 
INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.024/3.004002 
>>/tmp/.spamassassin7174sFN7hktmp/log' failed: exit 2

dpkg: error processing package sa-compile (--configure):
 subprocess installed post-installation script returned error exit 
status 25

Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 sa-compile
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up sa-compile (3.4.2-1~deb9u1) ...
Running sa-compile (may take a long time)
In file included from body_0.xs:2:0:
/usr/lib/x86_64-linux-gnu/perl/5.24/CORE/perl.h:689:23: fatal error: 
sys/types.h: No such file or directory

 #include 
   ^
compilation terminated.
make: *** [body_0.o] Error 1
command 'make PREFIX=/tmp/.spamassassin81455TCZBXtmp/ignored 
INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.024/3.004002 
>>/tmp/.spamassassin81455TCZBXtmp/log' failed: exit 2

dpkg: error processing package sa-compile (--configure):
 subprocess installed post-installation script returned error exit 
status 25

Errors were encountered while processing:
 sa-compile

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] How stable Is beowulf? How to upgrade from ascii?

2019-11-07 Thread Bernard Rosset via Dng

How stable is beowulf? Is there people using it in production?


It is stated on https://devuan.org/os/releases:

Beowulf -> In development
I suppose it is equivalent to "testing".

"testing is where the next stable suite is developed. Software is 
usually more up-to-date but there may still be issues. testing becomes 
stable “when it is ready”."


It is thus technically "not ready" - yet. The dev team released Ascii 
2.1 recently, which concurs with the table in page linked above.

Follow announces for when that will change.

I suggest you read the changes: 
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.html


-

On a personal note, I switched from Ascii to Beowulf almost exactly a 
month ago. Hard to get proper feedback with such a small hindsight, but 
here a couple points:

- So far, no major problem
- A myriad of package default configuration having changed (hence a lot 
of diff to do to cook modified configuration files on top of the new 
formats) -- nothing unusual here, though
- AppArmor! 
(https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.html#apparmor)
If you run a nameserver daemon, the corresponding AppArmor configuration 
will most probably not be activated: none of mine was.
It seems also to be a pain with namespaces (containers) requiring 
elevated privileges ie for debootstrap (cf. 
https://stackoverflow.com/questions/26406048/debootstrap-inside-a-docker-container/45661089#45661089)
- Even though I use scripts to automatically save/restore ip(6)tables 
rules on up/down, I ended up having my rules cleared through initial 
reboots. No precise idea on why.

I suggest you always keep a manual save of them somewhere.


How to I upgrade from ascii to beowulf?


As usual with APT.
If you are unsure, you can follow Debian's guide 
(https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.html).


The tutorial uses apt. Some feel more confident with the lower-level, 
original interface apt-get.


HTH,
Bernard Rosset
https://rosset.net/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Why is spamassasin compiling here?

2019-11-07 Thread Dimitris via Dng
On 11/7/19 2:01 PM, hal wrote:
>    172609  0 lrwxrwxrwx   1 root root   31 Feb  6  2019
> /usr/include/sys/types.h -> ../x86_64-linux-gnu/sys/types.h


i think the problem is there.. symlink(?) to non-existent file..

in a debian stretch system (got no ascii with spamassassin available),
this is a regular file, and /usr/include/sys/types.h doesn't exist..

# dpkg -S sys/types.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/types.h


maybe reinstall libc6-dev ??



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] How stable Is beowulf? How to upgrade from ascii?

2019-11-07 Thread Haines Brown
I installed Beowulf over Ascii several months ago and want to report 
general success. 

However, there was a glitch I do not understand. I could not get SMTP 
authentication (I'm running exim4 and mutt). Turned out that exim 
could not read my etc/eximr4/passwd.client file. Its ownership and 
permissinons were

  -rw-r- 1 root saned 653 Oct 29 12:17 passwd.client

which is the same as they were on Ascii. User was in the saned group. 

I recovered an ability to send e-mal by changing the permission to  

  -rw-r--r--  

If user is in saned group, shouldn't the user running exim be able to 
get SMTP authentication by reading passwd.client?

Haines Brown




 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] How stable Is beowulf? How to upgrade from ascii?

2019-11-07 Thread fraser kendall
On Thu, 7 Nov 2019 13:13:38 +0100
Bernard Rosset via Dng  wrote:


> - Even though I use scripts to automatically save/restore ip(6)tables 
> rules on up/down, I ended up having my rules cleared through initial 
> reboots. No precise idea on why.
> I suggest you always keep a manual save of them somewhere.

Beowulf/Buster has moved from iptables to nftables.  You can still use
iptables* with iptables-legacy*, but you'll need to edit your scripts
to reflect this. The option to save existing rules is part of the
upgrade but assumes that the existing rules haven't already been
overwritten with the default 'allow anything and everything'.  I use a
second root terminal to check the current ruleset before making the
decision to accept; I also check that the correct ruleset has been
applied after the first few reboots and any updates just to be sure.

Regards

fraser

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] How stable Is beowulf? How to upgrade from ascii?

2019-11-07 Thread Mike Tubby


On 07/11/2019 12:13, Bernard Rosset via Dng wrote:

How stable is beowulf? Is there people using it in production?




I have 20+ hosts all running Beowulf, including production DNS servers, 
email servers, MySQL (MariaDB) servers, web servers, firewalls, routers 
and Asterisk PBXes on mainly Dell R210 and R720 hardware and it is very 
stable and very reliable.


I am free of systemd and happy ;-)

Mike


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Why is spamassasin compiling here?

2019-11-07 Thread hal



On 11/7/19 6:39 AM, Dimitris wrote:

On 11/7/19 2:01 PM, hal wrote:

    172609  0 lrwxrwxrwx   1 root root   31 Feb  6  2019
/usr/include/sys/types.h -> ../x86_64-linux-gnu/sys/types.h



i think the problem is there.. symlink(?) to non-existent file..

in a debian stretch system (got no ascii with spamassassin available),
this is a regular file, and /usr/include/sys/types.h doesn't exist..

# dpkg -S sys/types.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/sys/types.h


maybe reinstall libc6-dev ??



Aha.. good catch.

# cd /usr/include/sys && file types.h
types.h: broken symbolic link to ../x86_64-linux-gnu/sys/types.h

# aptitude reinstall libc6-dev
The following packages will be REINSTALLED:
  libc6-dev
The following partially installed packages will be configured:
  sa-compile
...

# cd /usr/include/sys && file types.h
types.h: symbolic link to ../x86_64-linux-gnu/sys/types.h



Looks better now. Thank you for taking the time to help!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] How stable Is beowulf? How to upgrade from ascii?

2019-11-07 Thread Bernard Rosset via Dng

Beowulf/Buster has moved from iptables to nftables.  You can still use
iptables* with iptables-legacy*, but you'll need to edit your scripts
to reflect this. The option to save existing rules is part of the
upgrade but assumes that the existing rules haven't already been
overwritten with the default 'allow anything and everything'.


Thanks for that catch. I forgot about the move, which was publicized 
years ago already IIRC.


Are you implying the upgrade process (ie no reboot) already replaced the 
rules? Well... That is not surprising in the usual Debian's way (and why 
loads of people hate it ;o) ), but still damaging if that was the case...
That is something I definitely did not check for, and might explain 
while all of the sudden rulesets were empty (noticed only after reboot).


My scripts, using ip(6)tables-save binaries and then loading through 
ip(6)tables, are still working.
I am not used to the nftables interface (yet). Time to learn at last, I 
guess. :o)



I use a second root terminal to check the current ruleset before making the
decision to accept; I also check that the correct ruleset has been
applied after the first few reboots and any updates just to be sure.


Whatever way it is done: it means manual backup & restoration whenever 
needed.


Bernard Rosset
https://rosset.net/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng