[Cooker] Re: [BUG] squid-2.5.STABLE3-1

2003-07-17 Thread Norman Zhang
Hi,

 [EMAIL PROTECTED] nzhang]# rpm -Uvh squid-2.5.STABLE2-2mdk.i586.rpm
 Preparing...
 ### [100%]
1:squid
 ### [100%]
 [EMAIL PROTECTED] nzhang]# rpm -Uvh squid-2.5.STABLE3-1mdk.i586.rpm
 error: failed dependencies:
 perl(Authen::Smb::Smb)   is needed by squid-2.5.STABLE3-1mdk

 I have noticed that ... how come we didn't have this message before
 ... or maybe this package has just gone from the distro ...

I does sound funny. I checked CPAN perl-Auth-Smb has been changed since June
7, 1999. Why would someone take that out of the distro?

 Maybe I should add the perl-Auth-Smb package ...

Please do. I will go test it out.

Regards,
Norman






Re: [Cooker] Re: [BUG] squid-2.5.STABLE3-1

2003-07-17 Thread Duncan
On Thu 17 Jul 2003 15:05, Norman Zhang posted as excerpted below:
 Hi,

  [EMAIL PROTECTED] nzhang]# rpm -Uvh squid-2.5.STABLE2-2mdk.i586.rpm
  Preparing...
  ### [100%]
 1:squid
  ### [100%]
  [EMAIL PROTECTED] nzhang]# rpm -Uvh squid-2.5.STABLE3-1mdk.i586.rpm
  error: failed dependencies:
  perl(Authen::Smb::Smb)   is needed by squid-2.5.STABLE3-1mdk
 
  I have noticed that ... how come we didn't have this message before
  ... or maybe this package has just gone from the distro ...

 I does sound funny. I checked CPAN perl-Auth-Smb has been changed since
 June 7, 1999. Why would someone take that out of the distro?

  Maybe I should add the perl-Auth-Smb package ...

 Please do. I will go test it out.

Are you sure it isn't included in one of the other Mdk packages?  The perl 
dependencies have been being reworked since the new RPM, to take advantage of 
some of the new features available and make automation of dependencies on the 
developer side far easier.  Most such new unsatisfied dependencies, then, 
have been due to folks updating what they have access to to require the new 
dependencies, before the core packages they may NOT have write access to have 
been updated to provide them.  This is just part of the growing pains of 
Cooker, to be expected in an alpha state distrib program, so nothing to worry 
about at this point.

There are two ways to proceed with the install and test to see if that's the 
situation.  If it's not something you use often, you can just urpmi 
--allow-force and force the install (or do the equivalent rpm call directly), 
then see if it works.  Otherwise, you can check the dependency files manually 
one by one to see if they exist and are in a location where they can be 
found.  I've done both.

What I'm thinking is that if this just appeared, it isn't likely to be that 
the dependency files aren't there in reality, because as you noted, it 
doesn't make sense.  It's far more likely that this is a dependency update 
thing, particularly since we already know there ARE and have been such issues 
going on with perl and Cooker in this round.

-- 
Duncan - List replies preferred.
They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety.
Benjamin Franklin