Displaying 4 results from an estimated 4 matches for "pts17".
Did you mean:
pts1
2006 Jul 25
2
Problems with config of newhidups
Hi all,
I just downloaded, built and installed nut-2.0.4-pre2. I have an APC
Smart ups 3000 connected via a usb cable. I have compiled and installed
the usb drivers.
I installed the libhidups and libhid.usermap per the README.
I have the following ups.conf:
[APC-3000-ups]
driver = newhidups
port = auto
desc = "APC smart 3000"
When I try to start the driver I get the
2018 Feb 11
3
libsmbclient conflict problem
...eed to keep the samba4 packages?
Yes.
> They do not appear to be co-installable with samba3.
Agreed!!
In looking at this a little more it appears to me that there is a provides
missing from the samba4 packages.
I ran the following on another machine with the samba4 packages installed:
(cg2 pts17) # yum install kdebase
Loaded plugins: changelog, dellsysid, fastestmirror, refresh-packagekit, security
Setting up Install Process
[...]
Resolving Dependencies
--> Running transaction check
---> Package kdebase.x86_64 6:4.3.4-10.el6 will be installed
--> Processing Dependency: kdebase-run...
2018 Feb 06
2
libsmbclient conflict problem
Hi,
I have a c-6 machine that I noticed the following on:
(bugs pts10) # package-cleanup --problems
Loaded plugins: fastestmirror, priorities, refresh-packagekit
Package system-config-printer-libs-1.1.16-26.el6.x86_64 requires libsmbclient.so.0()(64bit)
Package kdebase-runtime-libs-4.3.4-9.el6.x86_64 requires libsmbclient.so.0()(64bit)
So then I ran:
(bugs pts10) # yum install libsmbclient
2018 Feb 11
0
libsmbclient conflict problem
...ror: samba4-winbind-clients conflicts with samba-winbind-clients-3.6.23-46el6_9.x86_64
> Error: samba4-common conflicts with samba-common-3.6.23-46el6_9.x86_64
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
> (cg2 pts17)
> --> Processing Dependency: libwbclient.so.0()(64bit) for package: libsmbclient-3.6.23-46el6_9.x86_64
>
> As you can see above, the the resolver totally ignores the fact that
> the samba4 packages are installed and tries to pull in the samba 3
> packages. This smells like a pack...