conffile prompt on latest upgrade in hardy

Thats because there has been some changes to smb.conf.

Thanks
chuck

Hi,

I'm marking this back to new as I disagree with your
decision. I will do this only once, as I don't want to
start a fight over it.

I did *not*, as far as I know, modify this file, so I should
not have been prompted, I should just get the new
version.

I am going to attach the new file (I chose to overwrite
with the maintainer's version), and the .ucf-old file,
which I believe is my locally "modified" version.

Thanks,

James

Confirming. Saw this earlier today when I dist-upgraded. I haven't ever modified smb.conf

Where you upgrading from gutsy or from hardy ?

The new version of the samba package introduces ucf to manage the smb.conf file. It should handle an upgrade from the default smb.conf from dapper and gutsy.

On Tue, 2008-03-11 at 19:32 +0000, Mathias Gug wrote:
> Where you upgrading from gutsy or from hardy ?
>
> The new version of the samba package introduces ucf to manage the
> smb.conf file. It should handle an upgrade from the default smb.conf
> from dapper and gutsy.
>

This was an upgrade from Hardy.

Thanks,

James

The issue here is that samba-common has been converted to use ucf for smb.conf management, and this requires a baseline config file to use when first enabling ucf. Templates have been provided for the gutsy and dapper versions of smb.conf, but there have been changes to the smb.conf since gutsy's release which will show up as diffs if you're using an smb.conf that was created from a more recent install of samba.

On the other hand, some bits of the diff (attached) relative to the stock gutsy smb.conf suggest that you might have originally installed a *pre* gutsy version of Samba? Yes, this seems to match the feisty version of the smb.conf file. Unfortunately, while I've tried to provide for the upgrade paths from each of dapper and gutsy, I don't know of a good way to detect that the smb.conf was originally created by an older version of samba than the one being upgraded from.

Hi,

Sorry, yes, I should have been more precise. This was an
upgrade from within Hardy, but the install was originally
feisty, so that is where the file originated I guess.

Thanks,

James

James Westby wrote:
> Hi,
>
> Sorry, yes, I should have been more precise. This was an
> upgrade from within Hardy, but the install was originally
> feisty, so that is where the file originated I guess.
>
> Thanks,
>
> James
>

However I just installed Hardy Alpha 6 (in a VM), and saw this while
dist-upgrading from that.

On Tue, Mar 11, 2008 at 10:45:35PM -0000, Iain Lane wrote:
> However I just installed Hardy Alpha 6 (in a VM), and saw this while
> dist-upgrading from that.

Correct. The latest version of the samba package only knows about the
default smb.conf from dapper and gutsy. All the other configurations will
lead to a prompt when upgrading the samba package to 3.0.28-4ubuntu1.

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

I've attached a debdiff that should fix this issue.

This bug was fixed in the package samba - 3.0.28a-1ubuntu4

---------------
samba (3.0.28a-1ubuntu4) hardy; urgency=low

  [ Mathias Gug ]
  * debian/samba-common.postinst:
    Fix upgrade from a first installation done with feisty, edgy or dapper.
    (LP: #201059).
  * debian/smb.conf.feisty:
    Add default smb.conf shipped in feisty.

  [ Steve Langasek ]
  * When populating the new sambashare group, it's not an error if the
    user simply doesn't exist; test for this case and let the install
    continue instead of aborting. LP: #206036.

 -- Steve Langasek <email address hidden> Wed, 02 Apr 2008 21:07:11 +0000