On 01/05/2016 01:22 PM, Patrick Shanahan wrote:

* don fisher <hdf3@comcast.net> [01-05-16 15:03]:

...

When I attempt to run zypper up I receive:

File './Essentials/x86_64/libvlccore8-2.2.1-129.1.x86_64.rpm' not found on medium 'http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.2/'

I do not know what interacts with this package, or how to proceed. I realize there were warning about using the packman repository, but any advice would be appreciated.

Warnings? Providing unsubstantiated rumors is very *wrong*. Please provide references or STOP. We don't need "chicken little".

Why are you all up in arms and thumping your chest Patrick? There have always been warnings about packman. To get there from the Opensuse pages you have to go through this page https://en.opensuse.org/Package_repositories#See_also (Read the warning in RED) Click Additional packages: https://en.opensuse.org/Additional_package_repositories More warnings in red Its hard to determine just how opensuse feels about Packman at any given time. There seems to be a love hate relationship going on. I've had bug reports rejected in the past because some packman packages were installed, even though they weren't involve. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/06/2016 12:00 PM, don fisher wrote:

I found additional items I am unsure about. When I examine /lib/modules, or /boot, I find references to at least two kernels. I realize when an update is made the currently executing kernel must be maintained. But where do the references to the old kernel modules etc. get deleted? Does each new install delete all previous kernel references so we always have one backup?

Of course its going to be configurable. There's surely long winded and awkward to read document ion somewhere, but the simplest thing is to look at the configuration files. In this case you want to look at /etc/zypp/zypp.conf In 13.x it says ## Comma separated list of kernel packages to keep installed in ## parallel, if the ## above multiversion variable is set. Packages can be specified as ## 2.6.32.12-0.7 - Exact version to keep ## latest - Keep kernel with the highest version number ## latest-N - Keep kernel with the Nth highest version number ## running - Keep the running kernel ## oldest - Keep kernel with the lowest version number (the GA kernel) ## oldest+N - Keep kernel with the Nth lowest version number ## ## Note: This entry is not evaluated by libzypp, but by the ## purge-kernels service (via /sbin/purge-kernels). I keep the original kernel that came with the distribution and the last 4 kernels. But then I also use the kernel_Stable repository to stay up to date since I use BtrFS, and patches for that come out pretty much every week. As it turns out, I don't reboot after each new kernel comes out. Sometimes there are more than one each week. In a worse case situation I might end up not rebooting for a month and have over a dozen kernels in /boot! They get purged when I reboot. If I get frustrated I might run purge-kernels manually. Its not necessary to keep so many back kernels; its a decision you make for specific reasons. "Paranoia" is an adequate reason. I'll leave it to others to tell how LEAP follows this or not. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org