Bug 177786 - net/samba36 net/samba-nmblookup multimedia/xbmc conflics
Summary: net/samba36 net/samba-nmblookup multimedia/xbmc conflics
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: VK
URL:
Keywords:
: 194318 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-04-11 20:40 UTC by Chris Dukes
Modified: 2016-10-17 23:57 UTC (History)
6 users (show)

See Also:


Attachments
Avoid all samba deps when WITHOUT_SMB is specified (919 bytes, patch)
2014-08-09 09:06 UTC, Ulrich Spörlein
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dukes 2013-04-11 20:40:00 UTC
Using pkgng.
Have multimedia/xbmc configured with Samba support which causes dependency of net/samba-nmblookup.
Wish to run samba36 on same machine as xbmc.  Due to xbmc's dependency on samba-nmblookup, samba36 conflicts.

Fix: 

I believe the best option within the current limits of ports and pkgng would be for samba to follow the model used by postgresql and NOT include the nmblookup pieces in the samba36 package, and instead have samba36-nmblookup be a dependency for samba36.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-04-11 20:40:08 UTC
Responsible Changed
From-To: freebsd-ports-bugs->timur

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Ulrich Spörlein freebsd_committer freebsd_triage 2014-08-09 09:05:01 UTC
That fix would actually be preferred. For now I just want to run both XBMC and Samba on the same host and have a patch that avoids *all* samba dependencies in XBMC so they can co-exist.

Chances are, that if your HTPC is both running XBMC and Samba, that you don't actually need XBMC to talk SMB with some other hosts.
Comment 3 Ulrich Spörlein freebsd_committer freebsd_triage 2014-08-09 09:06:09 UTC
Created attachment 145548 [details]
Avoid all samba deps when WITHOUT_SMB is specified
Comment 4 Chris Dukes 2014-08-09 14:14:55 UTC
(In reply to Ulrich Spörlein from comment #2)
> That fix would actually be preferred. For now I just want to run both XBMC
> and Samba on the same host and have a patch that avoids *all* samba
> dependencies in XBMC so they can co-exist.
> 
> Chances are, that if your HTPC is both running XBMC and Samba, that you
> don't actually need XBMC to talk SMB with some other hosts.

I have an odd use case.
Two media PCs, one with one flavor of content, the other with the rest.  They see the other's content via NFS.  The wrinkle, the kids like to watch content from their laptops, which means smb/cifs.  They also occasionally have content.  The current work around, a second HDMI cable and the occasional tutorial on sftp.

I have a little more time now, so I'll look into providing a patch to samba such that the server has a dependency on the client package.
Comment 5 David Chisnall freebsd_committer freebsd_triage 2014-12-23 21:07:46 UTC
*** Bug 194318 has been marked as a duplicate of this bug. ***
Comment 6 David Chisnall freebsd_committer freebsd_triage 2015-03-21 16:53:42 UTC
This bug has been open for almost two years and we still can't install XBMC (or Kodi, as it's now known) from packages with samba.  Please will the samba maintainer make the samba36 package depend on the samba-nmblookup package, rather than conflicting with it and remove the duplicate files?
Comment 7 Timur I. Bakeyev freebsd_committer freebsd_triage 2015-05-26 18:31:19 UTC
I'm more willing to drop samba36-nmblookup and let everything depend on samba36. 

Well, if anyone wants to send a patch that removes nmblookup from the samba36 package gracefully - then we can solve this issue now.

Personally, since stagedir I'd expect ability to package several packages from one port. After build process we have just a set of files, which can be packaged in any combination we like.
Comment 8 Andriy Gapon freebsd_committer freebsd_triage 2015-05-27 11:32:57 UTC
(In reply to Timur I. Bakeyev from comment #7)
I support removing samba36-nmblookup, its usefulness seems to be very limited.
Comment 9 Slawomir Wojciech Wojtczak 2015-06-05 00:12:51 UTC
Please drop net/samba-nmblookup already, its more then two years for a single bug ...

Reported: 2013-04-11
Modified: 2015-05-27
Comment 10 Slawomir Wojciech Wojtczak 2015-06-05 00:26:07 UTC
BINARY WORKAROUND:



# pkg info | grep samba
samba36-3.6.25                 Free SMB and CIFS client and server for Unix
samba36-libsmbclient-3.6.25_2  Shared lib from the samba package
1:13|BLACKBOX|vermaden ~ % sudo pkg delete samba36-3.6.25
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        samba36-3.6.25

The operation will free 110 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling samba36-3.6.25...
[1/1] Deleting files for samba36-3.6.25: 100%



# pkg install kodi
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 2 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        kodi: 14.0
        samba36-nmblookup: 3.6.25

The process will require 79 MiB more space.

Proceed with this action? [y/N]: y
[1/2] Installing samba36-nmblookup-3.6.25...
[1/2] Extracting samba36-nmblookup-3.6.25: 100%
[2/2] Installing kodi-14.0...
[2/2] Extracting kodi-14.0: 100%



# pkg delete -f samba36-nmblookup-3.6.25
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        samba36-nmblookup-3.6.25

The operation will free 2 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling samba36-nmblookup-3.6.25...
[1/1] Deleting files for samba36-nmblookup-3.6.25: 100%



# pkg install samba36
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (1 conflicting)
pkg: Cannot solve problem using SAT solver:
conflict rule: The following packages conflict with each other: samba36-3.6.25(r), samba36-nmblookup-3.6.25(r)
conflict rule: The following packages conflict with each other: samba36-3.6.25(r), samba36-3.6.25(r)
cannot install package samba36, remove it from request? [Y/n]: n
pkg: cannot solve job using SAT solver
Checking integrity... done (0 conflicting)
The most recent version of packages are already installed



# sqlite3 -header -column /var/db/pkg/local.sqlite "select * from deps where name='samba36-nmblookup';"
origin               name               version     package_id
-------------------  -----------------  ----------  ----------
net/samba-nmblookup  samba36-nmblookup  3.6.25      545   



# sqlite3 /var/db/pkg/local.sqlite "update deps set name='net/samba36' where origin='net/samba36';"



# pkg install samba36
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 1 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        samba36: 3.6.25

The process will require 110 MiB more space.

Proceed with this action? [y/N]: y
[1/1] Installing samba36-3.6.25...
[1/1] Extracting samba36-3.6.25: 100%
Message for samba36-3.6.25:
 ===============================================================================
Samba3 *package* now doesn't include ADS support due the portability problems
with Kerberos5 libraries on different installations. You need to compile the
port yourself to get this functionality.

For additional hints and directions, please, look into the README.FreeBSD file.
===============================================================================
Comment 11 brent 2016-01-08 03:56:15 UTC
January 2016; on a completely up to date system; just hit this. If everyone is agreed can this get pushed through already?
Comment 12 David Chisnall freebsd_committer freebsd_triage 2016-01-08 09:46:31 UTC
I believe that the short-term fix that should be pushed forward is dropping the samba-nmblookup dependency from the packaged version of kodi.  People needing it are welcome to build the port.  A longer-term solution, to allow a single port to produce multiple packages, is currently under development and that will allow the dependency to be reintroduced and net/samba-nmblookup to become a sub-package (and dependency) of net/samba36.  That said, given that net/samba-nmblookup already exists, it should be a simple patch to remove the files from samba-nmblookup from the samba36 plist and add a dependency on samba-nmblookup.
Comment 13 Slawomir Wojciech Wojtczak 2016-01-08 14:32:28 UTC
This bug is present for so long that even XBMC project managed to change its name into KODI ...
Comment 14 Slawomir Wojciech Wojtczak 2016-02-17 07:09:05 UTC
Can we manage to fix that for 10.3-RELEASE?
Comment 15 Andriy Gapon freebsd_committer freebsd_triage 2016-03-24 11:47:40 UTC
Timur, so could you please kill net/samba-nmblookup?
The main samba port is not really heavy-weight and does not cause any system overhead unless its daemons are explicitly enabled.
Comment 16 Slawomir Wojciech Wojtczak 2016-03-24 12:42:59 UTC
@Andriy Gapon

+1
Comment 17 VK 2016-10-17 23:57:17 UTC
Closing, as net/samba36 expired and is removed from the tree:

https://svnweb.freebsd.org/ports?view=revision&revision=415323

I'm considering this FIXED per given revision because the requests here were to remove the net/samba-nmblookup, which was deleted as well with that revision.

Please reopen if you think this was a mistake.