Comment 65 for bug 192310

Ok Duncan, first is not my text - it's the proposal that bug report tool
offer me.

I think was OK on his way.

Second - It's about a Metabug ( yes " ...which is also in package
***..." is a metabug which require a final resolution, I'll speak about
that later on this mail), so I'm not reporting about my problem. I'm not
asking for help ...regarding your solution, I can do that without fill
in bug reports - but this is not the proper solution. Imagine mr. Duncan
  you tell that to a beginner - he will ask you beck probably what is
...kernel.

So my report is there in hope is be useful for something.

Now about the metabug -> is present from first Ubuntu.

Maybe a packager does something wrong.

But is not OK for peoples to see this bug too often.

And this is happening almost each week for a package or 2. Is not an
Open Office error.

Is a decision to take => so if the same package is there = we should
interrupt the upgrade process ? - what if our program take count on the
library presence and continue upgrade process ( if is THE SAME library
what's the real problem ? - do not copy the file but give to installer
option TRUE when he check paths and libraries - so the upgrade process
can continue). OR if is the same file -> OVERWRITE THE FILE and GO ON (
you can check the file version using checksum, numbering system, file
length, etc ) - BUT NOT BROKE A PROCESS BECAUSE ONE OF THE NECESSARY
FILES IS ALREADY THERE.

This is my message and please take count on that.

About the specific part of the bug - I can delete the file from it's
location and from dpkg index so after that Upgrade will work OK - no
necessary to upgrade my kernel ( which may work or not ...).

Regards,
Sorin

Duncan Lithgow wrote:
> Please trim your text before posting.
> I saw a similar problem, I booted with an older kernel, ran upgrade again and it works fine now.
>