Hello.
I just noticed some glitches while using urpmc:
libsmbclient0-3.0-0.alpha21.3mdk -> libsmbclient0-2.2.8a-7mdk
* Tue Jul 15 2003 Buchan Milne <[EMAIL PROTECTED]> 2.2.8a-7mdk
- reduce optimisations (from -O2 to -O1) until we find the real problem.
smbmount and smbpasswd should work now (please test)
- specify CFLAGS in one place to reduce confusion ...
[...a lot of log entries...]
* Sat Jan 24 1998 John H Terpstra <[EMAIL PROTECTED]>
- Many optimisations (some suggested by Manoj Kasichainula <[EMAIL PROTECTED]>
- Use of chkconfig in place of individual symlinks to /etc/rc.d/init/smb
- Compounded make line
- Updated smb.init restart mechanism
- Use compound mkdir -p line instead of individual calls to mkdir
- Fixed smb.conf file path for log files
- Fixed smb.conf file path for incoming smb print spool directory
- Added a number of options to smb.conf file
- Added smbadduser command (missed from all previous RPMs) - Doooh!
- Added smbuser file and smb.conf file updates for username map
!!! CHANGELOG TRUNCATED OR CURRENT ENTRY MISSING !!!
Hm. Let's see. The versions are correct (i.e. I have
libsmbclient0-3.0-0.alpha21.3mdk installed; libsmbclient0-2.2.8a-7mdk
and libsmbclient0-3.0-0.alpha21.3mdk are available on my medium).
libsmbclient0-3.0-0.alpha21.3mdk is from contrib and
libsmbclient0-2.2.8a-7mdk is from cooker. Does this make a difference?
Neither urpmi nor rpmdrake want to upgrade this package ("urpmi
libsmbclient" -> "Everything already installed"). Do you need any
further info?
libgdbm2-1.8.0-22mdk -> libgdbm2-1.8.0-23mdk
* Mon Jul 28 2003 Gwenole Beauchesne <[EMAIL PROTECTED]> 1.8.0 -23mdk
- mkbliname
* Thu Jul 10 2003 Laurent MONTEL <[EMAIL PROTECTED]> 1.8.0 -22mdk
- Rebuild
* Wed Jun 04 2003 Stefan van der Eijk <[EMAIL PROTECTED]> 1.8.0-21mdk
- rebuild for deps
[...a lot of log entries...]
!!! CHANGELOG TRUNCATED OR CURRENT ENTRY MISSING !!!
I guess the problem is with the space in the version numbers of the
last two log entries. So this is more a problem of the package, not of
urpmc. But maybe urpmc could stop displaying the log, as soon as it
found the first version which it positively identifies as being lower
than the current one? Here that would be 1.8.0-21.
Ah, and is it possible to print the line
!!! PACKAGE NOT CURRENTLY INSTALLED FULL CHANGELOG SHOWN !!!
at the start of the belonging changelog, not at the end?
Aside from that, did I already mention that I love this tool? :-)
And some glitches in packages, which urpmc showed:
GConf-1.0.9-8mdk -> GConf-1.0.9-9mdk
libGConf1-1.0.9-8mdk -> libGConf1-1.0.9-9mdk
!!! NO CHANGELOG ENTRIES NEWER THAN INSTALLED PACKAGE !!!
urpmc is right. Verified with rpm -q --changlog by hand. The last log
entry is labeled as 1.0.9-8mdk.
Bye,
Benjamin.
