search for: asr9k

...using two unrelated > and different repo's is beyond me. > > This has always been a problem, even back in the 90's with the RPMs, RH > v say for example Fresh, because package maintainers will package > differently. > > Its like trying to stick a cisco 1800 image on an ASR9K and expecting it > to work perfectly. > > Though we don't use deb or rpm based systems and haven't for about 15 > years, if I was to, I think I'd be using the creators version, and not a > distro's version. >

?? Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. ?I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such

...different repo's is beyond me. > > > > This has always been a problem, even back in the 90's with the RPMs, RH > > v say for example Fresh, because package maintainers will package > > differently. > > > > Its like trying to stick a cisco 1800 image on an ASR9K and expecting it > > to work perfectly. > > > > Though we don't use deb or rpm based systems and haven't for about 15 > > years, if I was to, I think I'd be using the creators version, and not a > > distro's version. > > >

...k you could upgrade versions by using two unrelated and different repo's is beyond me. This has always been a problem, even back in the 90's with the RPMs, RH v say for example Fresh, because package maintainers will package differently. Its like trying to stick a cisco 1800 image on an ASR9K and expecting it to work perfectly. Though we don't use deb or rpm based systems and haven't for about 15 years, if I was to, I think I'd be using the creators version, and not a distro's version. -- Kind Regards, Noel Butler This Email, including any attachments, may con...