Help Needed: Missing Obsoletes cause upgrade trouble

[Warren Togami]

http://togami.com/~warren/archive/2004/fc1-fc2-conflicts.txt

I decided to test a FC1 "Everything" apt-get dist-upgrade to FC2 using 
rawhide from April 21st.  It found two cases where removed subpackages 
were not Obsoleted by FC2 packages, causing a file conflict.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121415
boost
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121414
tcl & tk

These packages have been fixed and will be in tomorrow's rawhide push, 
but I have copied them manually to fedora.us RPMS.updates.  It is good 
that the files conflicted because they can be fixed quickly, but what 
scares me is possible cases where files did NOT conflict.  Please be on 
the look out for any missing Obsoletes that  resulted in package or 
sub-package removal.

We would really appreciate your help with "Everything" upgrade tests 
from RH9 to FC2, and perhaps RH8 or RH7.x should be done too.  I highly 
suspect more conflicts or missing package removals are present in FC2. 
Please do "Everything" installs, then attempt an upgrade with apt-get or 
yum, then report any problems you encounter here.

http://togami.com/~warren/archive/2004/fc1-fc2pretest3-matching.txt
Below is a list of packages that remained unchanged from FC1 
"Everything" to FC2 apt-get dist-upgrade.  Please read the instructions 
at the top and comment here.

Warren Togami
[e-mail]

[Michael Schwendt]

Extra packages from fedora.us for Fedora Core 1 with higher versions
in Fedora Core Development (rpmdb-fedora-1.92-0.20040421):

xrestop
  k3b
  gimp2-1.3* -> gimp-2.0*  (upgrade removes gimp2*)
  libexif, libexif-devel
  iptstate
 (perl-DateManip)
 (perl-RPM-Specfile)
  flac, flac-devel, (flac-libs is obsoleted)
  xmms-flac
  libdv, libdv-devel, libdv-tools
  speex, speex-devel
  libgpg-error, libgpg-error-devel

Conflicts (FC1 extras not touched by upgrade):

juk ./. kmultimedia
  sylpheed-claws (not upgraded with sylpheed)
  alsa-driver ./. dev, MAKEDEV
  alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
  leafnode ./. cyrus-imapd (bug filed)
  kgpg ./. kdeutils, kde-i18 (several i18n packages!)

[Michael Schwendt]

On Fri, 23 Apr 2004 02:22:56 +0200, Michael Schwendt wrote:
> Conflicts (FC1 extras not touched by upgrade):
>
> juk ./. kdemultimedia
>   kgpg ./. kdeutils, kde-i18 (several i18n packages!)

"juk" and "kgpg" are included with KDE >= 3.2
> sylpheed-claws (not upgraded with sylpheed)

Not a problem. Mass-rebuild of Extras will make available sylpheed-claws
for fc2, too.
> leafnode ./. cyrus-imapd (bug filed)

Only a manual page, which can be renamed.
> alsa-driver ./. dev, MAKEDEV
>   alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!

Dangerous. In particular "alsa-driver", which contains many /dev files.

[Thorsten Leemhuis]

Am Fr, den 23.04.2004 schrieb Michael Schwendt um 16:13:
> On Fri, 23 Apr 2004 02:22:56 +0200, Michael Schwendt wrote:

[...]
> > alsa-driver ./. dev, MAKEDEV
> >   alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
>
> Dangerous. In particular "alsa-driver", which contains many /dev files.

What can I (as alsa-packager for fedora.us) do to solve this problem?
Any hints?

CU
thl

[Michael Schwendt]

On Fri, 23 Apr 2004 20:37:53 +0200, Thorsten Leemhuis wrote:
> [...]
> > > alsa-driver ./. dev, MAKEDEV
> > >   alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
> >
> > Dangerous. In particular "alsa-driver", which contains many /dev files.
>
> What can I (as alsa-packager for fedora.us) do to solve this problem?
> Any hints?

Nothing I know of. I don't know about any ways to specify that a package
obsoletes itself during an upgrade. Any packages which are not listed as
"Obsoletes:" in a new package are not removed.

[Warren Togami]

Michael Schwendt wrote:
> On Fri, 23 Apr 2004 20:37:53 +0200, Thorsten Leemhuis wrote:
> > [...]
> > > > alsa-driver ./. dev, MAKEDEV
> > > >  alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
> > >
> > > Dangerous. In particular "alsa-driver", which contains many /dev files.
> >
> > What can I (as alsa-packager for fedora.us) do to solve this problem?
> > Any hints?
>
> Nothing I know of. I don't know about any ways to specify that a package
> obsoletes itself during an upgrade. Any packages which are not listed as
> "Obsoletes:" in a new package are not removed.

Has the ABI/API changed from 1.0.3a to 1.0.4?

Warren

[Michael Schwendt]

On Sat, 24 Apr 2004 08:03:07 -1000, Warren Togami wrote:
> Michael Schwendt wrote:
> > On Fri, 23 Apr 2004 20:37:53 +0200, Thorsten Leemhuis wrote:
> > > [...]
> > > > > alsa-driver ./. dev, MAKEDEV
> > > > >  alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
> > > >
> > > > Dangerous. In particular "alsa-driver", which contains many /dev files.
> > >
> > > What can I (as alsa-packager for fedora.us) do to solve this problem?
> > > Any hints?
> >
> > Nothing I know of. I don't know about any ways to specify that a package
> > obsoletes itself during an upgrade. Any packages which are not listed as
> > "Obsoletes:" in a new package are not removed.
>
> Has the ABI/API changed from 1.0.3a to 1.0.4?

No.

"alsa-driver" is the problem, because it contains ALSA device files
found in "dev" package and scripts found in "MAKEDEV" package.

[Alexandre Oliva]

On Apr 23, 2004, Thorsten Leemhuis  wrote:
> Am Fr, den 23.04.2004 schrieb Michael Schwendt um 16:13:
> > On Fri, 23 Apr 2004 02:22:56 +0200, Michael Schwendt wrote:
>
> [...]
> > > alsa-driver ./. dev, MAKEDEV
> > >   alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
> >
> > Dangerous. In particular "alsa-driver", which contains many /dev files.
> What can I (as alsa-packager for fedora.us) do to solve this problem?
> Any hints?

IIRC the only conflict is with MAKEDEV.  How about getting your
alsa-driver to Require: the file provided by MAKEDEV, and split that
file out into a separate package, say alsa-driver-MAKEDEV?

MySQL on FC1 and AMD64

[Mark Page]

Hi,

has anyone successfully installed the MySQL AMD64 rpms from
www.mysql.com on Core1, specifically for version 4.0.18 or 4.1.1.?

Regards, -Mark.

I get the following errors;

[root@prod1 mark]# rpm -i MySQL-server-4.1.1-1.x86_64.rpm
warning: MySQL-server-4.1.1-1.x86_64.rpm: V3 DSA signature: NOKEY, key
ID 5072e1f5
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this
binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.

key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
...
...

[Michael Schwendt]

On 01 May 2004 02:50:14 -0300, Alexandre Oliva wrote:
> On Apr 23, 2004, Thorsten Leemhuis  wrote:
> > Am Fr, den 23.04.2004 schrieb Michael Schwendt um 16:13:
> > > On Fri, 23 Apr 2004 02:22:56 +0200, Michael Schwendt wrote:
> >
> > [...]
> > > > alsa-driver ./. dev, MAKEDEV
> > > >   alsa-lib, alsa-utils, all of alsa* because 1.0.4 > 1.0.3a!
> > >
> > > Dangerous. In particular "alsa-driver", which contains many /dev files.
> > What can I (as alsa-packager for fedora.us) do to solve this problem?
> > Any hints?
>
> IIRC the only conflict is with MAKEDEV.  How about getting your
> alsa-driver to Require: the file provided by MAKEDEV, and split that
> file out into a separate package, say alsa-driver-MAKEDEV?

After analyzing the conflict in detail, an obvious suggestion [posted
off-list] has been to simply copy the conflicting file from MAKEDEV and
include it in the alsa-driver package, too. That would get rid of the
conflict.