Re: abiword
On 04/11/2016 07:02 AM, Yasha Karant wrote: Is there any EL7 rpm or other successful build of a recent stable release of abiword? If so, what is URL to download the build including whatever other rpms are required (or a large static image that does not require any .so components that are not part of the standard SL 7 repo)? Yasha Karant Several of abiword's buildrequires are not in the various EL7 repos. There aren't very many of them; in attempting to rebuild the FC22 Abiword and attempting to install the buildreqs I get: No package aiksaurus-devel available. No package aiksaurus-gtk-devel available. No package gtkmathview-devel available. No package link-grammar-devel available. No package loudmouth-devel available. No package ots-devel available. No package wv-devel available. Not sure how difficult that will be to get those packages (and the packages the -devel packages depend upon) built. I have a client who is waiting on a CentOS 7-compatible Abiword to migrate to CentOS 7 from CentOS 6, and Abiword is a blocker.
Samba update killed my servers
Greetings, I am running SL6 on my Samba servers. I am in an environment where I am required to apply security patches daily. Yum auto updates nearly all security patches for me every morning (only a few things like the kernel are excluded). This morning we went from 3.6.23-25 to 3.6.23-30. Every thing broke. Not a single server works. Short recap that proves it is the update. $ # restore everything from backup server $ service nmb start; service smb start $ # everything works. $ service nmb stop; service smb stop $ yum update -y --security --exclude=kernel* # updates just 5 packages: samba, samba-client, # samba-common, samba-winbind, and samba-winbind-clients $ service nmb start; service smb start # Nothing works. $ service nmb stop; service smb stop $ yum history undo $lastversion $ service nmb start; service smb start # Everything works again. There is really not much in the logs at all from smb/nmb as to what is going wrong. The client just gets a strange error about permissions denied. However, in the log file for the client, we see things like "Domain password server not available". There are occasional messages in nmb logs about "current master browser = UNKNOWN" and "find_domain_master_name_query_fail" but they are not easily reproducible. 1) It is amazing how many questions on the samba list don't get responses... 2) The vast majority of the responses I found on line didn't seem to work. At one point, I scrapped my entire smb.conf file, wiped samba, and restarted with the smb.conf file the new RPM provided. I still couldn't get clients to connect. Here is my smb.conf file that I restored from last night. It has been working since May of 2014. [global] workgroup = MYWORKGROUP server string = hostname netbios name = hostname log file = /var/log/samba/log.%m max log size = 50 security = domain password server = my.primary.domain.server preferred master = no wins support = no wins server = my.primary.domain.server wins proxy = yes dns proxy = yes load printers = yes cups option = raw restrict anonymous = 1 smb ports = 139 [homes] comment = Home Directories browsable = no writeable = yes valid users = %S [ yes I know I am not supposed to use security=domain with password server, but it works. Modifying either seems to make it not work] Anyone else have horrific issues with this update?? Thanks! ~Stack~ signature.asc Description: OpenPGP digital signature
Re: Security ERRATA Critical: samba and samba4 on SL6.x, SL7.x i386/x86_64
Thanks, it works fine now.
Re: Security ERRATA Critical: samba and samba4 on SL6.x, SL7.x i386/x86_64
On 04/13/2016 10:36 AM, Glenn Morris wrote: Hi, Pat Riehecky wrote: SL7 x86_64 [...] openchange-2.0-10.el7_2.i686.rpm openchange-2.0-10.el7_2.x86_64.rpm openchange-debuginfo-2.0-10.el7_2.i686.rpm openchange-debuginfo-2.0-10.el7_2.x86_64.rpm These ones don't seem to appear in ftp://ftp.scientificlinux.org/linux/scientific/7.2/x86_64/updates/security/ which causes updates to fail with: Error: Package: openchange-2.0-9.el7.x86_64 (@sl) Requires: libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Removing: samba-client-libs-4.2.3-12.el7_2.x86_64 (@sl-security) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Updated By: samba-client-libs-4.2.10-6.el7_2.x86_64 (sl-security) ~libsamba-debug-samba4.so(SAMBA_4.2.10)(64bit) Available: samba-client-libs-4.2.3-10.el7.x86_64 (sl) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Available: samba-client-libs-4.2.3-11.el7_2.x86_64 (sl-security) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) You could try using --skip-broken to work around the problem Weird, I'll republish the repo and watch it for unexpected behavior. Pat
Re: Security ERRATA Critical: samba and samba4 on SL6.x, SL7.x i386/x86_64
Hi, Pat Riehecky wrote: > SL7 > x86_64 [...] > openchange-2.0-10.el7_2.i686.rpm > openchange-2.0-10.el7_2.x86_64.rpm > openchange-debuginfo-2.0-10.el7_2.i686.rpm > openchange-debuginfo-2.0-10.el7_2.x86_64.rpm These ones don't seem to appear in ftp://ftp.scientificlinux.org/linux/scientific/7.2/x86_64/updates/security/ which causes updates to fail with: Error: Package: openchange-2.0-9.el7.x86_64 (@sl) Requires: libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Removing: samba-client-libs-4.2.3-12.el7_2.x86_64 (@sl-security) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Updated By: samba-client-libs-4.2.10-6.el7_2.x86_64 (sl-security) ~libsamba-debug-samba4.so(SAMBA_4.2.10)(64bit) Available: samba-client-libs-4.2.3-10.el7.x86_64 (sl) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) Available: samba-client-libs-4.2.3-11.el7_2.x86_64 (sl-security) libsamba-debug-samba4.so(SAMBA_4.2.3)(64bit) You could try using --skip-broken to work around the problem
Re: darktable
On 04/13/2016 01:30 AM, Yasha Karant wrote: Is there any port of: Grab the latest source tarball (recent version: darktable 2.0.3) – make sure to use the .tar.xz file to SL 7x? Yasha Karant There is a Fedora package, I would start there. You can always grab the source rpm and try recompiling. They list the deps on their install page in the Fedora section.
