Package libsmbclient needs to be rebuild against new samba4-common

Stephen Gallagher sgallagh at redhat.com
Mon Apr 23 11:25:17 UTC 2012


On Mon, 2012-04-23 at 13:57 +0300, Kalev Lember wrote:
> On 04/23/2012 06:22 AM, Simo Sorce wrote:
> > On Sun, 2012-04-22 at 20:53 +0300, Kalev Lember wrote:
> >> libsmbclient has been now removed from samba4 package (see bug #814451),
> >> but what you have installed is a leftover from the earlier packaging
> >> error. Incrementing the epoch number in the samba 3 package would fix
> >> the upgrade paths again, making sure everybody gets back the samba 3
> >> libsmbclient.
> > 
> > As far as I know that package never reached the stable repository, can
> > you confirm you use updates-testing ?
> > If that's the case I do not think we are going to up the epoch.
> 
> Yes, the samba4 updates was only in updates-testing. However,
> updates-testing is turned on by default in F17 and because of that,
> every F17 user still got the libsmbclient update.
> 
> It's your call to make, but I wouldn't base the decision on whether it
> was in stable updates or updates-testing. Both are currently enabled by
> default in F17.


There is a reasonable expectation that when using a Fedora Beta you may
end up in a situation that requires manual effort to get out of. I agree
with Simo that no epoch bump is needed here.

I do maintain that we should stop leaving updates-testing enabled once
we hit Beta. (Alpha is fine). This would also help with getting testing
for the bits that will ultimately be the final release.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120423/7081e7b7/attachment.sig>


More information about the devel mailing list