upgrade from hardy to lucid uninstalls samba

Bug #579736 reported by RedScourge
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Expired
High
Unassigned
Nominated for Lucid by RedScourge

Bug Description

Binary package hint: update-manager

I upgraded from 8.04 LTS to 10.04 LTS. This is a fairly standard install because all I need to do on this box is apache, mysql, samba, and sshd.

I had customized the config files of samba, (no errors in the config!) and I guess because of that when I later tried to upgrade, it failed.

Steps to reproduce:

-install hardy
-install samba
-set up a few samba shares
-update all packages to latest
-upgrade from hardy to lucid
-reboot

Before I managed to fix:

dpkg --list | grep samba

rc samba 3.0.28a-1ubuntu4.10 a LanManager-like file and printer server fo
ii samba-common 2:3.4.7~dfsg-1ubuntu3 common files used by both the Samba server a
ii samba-common-bin 2:3.4.7~dfsg-1ubuntu3 common files used by both the Samba server a
ii samba-doc 2:3.4.7~dfsg-1ubuntu3 Samba documentation

After I managed to fix:

ii samba 2:3.4.7~dfsg-1ubuntu3 SMB/CIFS file, print, and login server for U
ii samba-common 2:3.4.7~dfsg-1ubuntu3 common files used by both the Samba server a
ii samba-common-bin 2:3.4.7~dfsg-1ubuntu3 common files used by both the Samba server a
ii samba-doc 2:3.4.7~dfsg-1ubuntu3 Samba documentation

I usually to all package management through aptitude because it's more flexible for someone who does not want to memorize syntax and wants to ensure dependency issues are resolved. When I tried to search for samba in aptitude, it just found a bunch of other crap instead.

How I fixed:

sudo apt-get install samba smbfs

Then it magically worked as it had been working before.

Revision history for this message
RedScourge (redscourge) wrote :
Revision history for this message
RedScourge (redscourge) wrote :

openssh-server was also removed and failed to be re-added in a similar fashion to samba, but I did not think to grab info regarding how i fixed it, etc. The same uploaded zip file should contain info about it. It also broke my iptables somehow but it might be due to my rules and a new version of iptables though, and i had added it as a pre-up on eth0 so just a warning, if someone else were to have done that (i.e. anyone who read the same forum posts as me about how to install iptables into ubuntu on startup) they may want to watch something like that.

In all cases, my config file modifications to any packages have been trivial.

Phillip Susi (psusi)
tags: removed: samba upgrade
affects: update-manager (Ubuntu) → samba (Ubuntu)
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Hello "RedScourge", Thank you for taking the time to file this bug report and help make Ubuntu better!

@psusi - Its not clear why this is being blamed on samba over update-manager when its not even clear what has happened. Please comment on your reasons for reassigning it.

After reading the contents of all of the log files in the attached zip file, I don't see where samba was removed. In fact, it appears it was already removed when apt got involved. There seems to be a missing log that would have been generated when the upgrade is done.

Its non-trivial to reproduce this, as someone will have to install hardy, install samba on it, and then upgrade to lucid.

RedScourge, can you provide any more artifacts before someone has to go through the effort of reproducing? Specifically can you state the exact steps you took to "Upgrade from Hardy to Lucid" ?

Adding work-intensive tag and regression-release tag.

Setting status to Incomplete pending answer on exact upgrade steps.

Setting importance to High, as this would be a serious upgrade regression.

tags: added: regression-release work-intensive
Changed in samba (Ubuntu):
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

Changed in samba (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.