Why has fedpkg suddenly grown a dependency on MySQL-python?

[Tom Lane]

I was rather surprised to find a routine "yum update" on my F14 system
suddenly wanting to pull in a lot of mysql stuff that I'd not had
installed at the moment.  Investigation showed that if I try to remove
MySQL-python again, yum wants to take all this stuff with it:

Removing:
 MySQL-python         x86_64  1.2.3-1.fc14                      @updates  228 k
Removing for dependencies:
 TurboGears           noarch  1.0.9-8.fc14                      @updates  7.6 M
 bodhi-client         noarch  0.8.0-1.fc14                      @updates   25 k
 fedora-easy-karma    noarch  0-0.15.20110825git36efb338.fc14   @updates   75 k
 fedora-packager      noarch  0.5.9.2-2.fc14                    @updates   72 k
 fedpkg               noarch  0.5.9.2-2.fc14                    @updates  248 k
 python-fedora        noarch  0.3.25.1-1.fc14.1                 @updates  1.7 M
 python-sqlobject     noarch  0.10.2-6.fc14                     @fedora   1.6 M

Needless to say, that would put rather a crimp in my ability to do any
Fedora packaging work on this machine.

AFAIK, there is no legitimate reason for fedpkg or fedora-packager to
need to talk to a mysql database, so I'd really like to see this
dependency go away again.  I have routine occasion to shuffle mysql
packages in and out, and I don't want entirely-unnecessary dependencies
getting in the way.

			regards, tom lane

[Mathieu Bridon]

On Tue, 2011-11-22 at 01:16 -0500, Tom Lane wrote:
>  I was rather surprised to find a routine "yum update" on my
> F14 system
>  suddenly wanting to pull in a lot of mysql stuff that I'd not had
>  installed at the moment.  Investigation showed that if I try to remove
>  MySQL-python again, yum wants to take all this stuff with it: 
You forgot to paste the most important:
# yum remove MySQL-python
[... snip ...]
---> Package MySQL-python.x86_64 0:1.2.3-1.fc14 set to be erased
--> Processing Dependency: MySQL-python for package:
python-sqlobject-0.10.2-6.fc14.noarch
--> Running transaction check
---> Package python-sqlobject.noarch 0:0.10.2-6.fc14 set to be erased
--> Processing Dependency: python-sqlobject >= 0.8 for package:
TurboGears-1.0.9-8.fc14.noarch
--> Running transaction check
---> Package TurboGears.noarch 0:1.0.9-8.fc14 set to be erased
--> Processing Dependency: TurboGears for package:
python-fedora-0.3.25.1-1.fc14.1.noarch
--> Running transaction check
---> Package python-fedora.noarch 0:0.3.25.1-1.fc14.1 set to be erased
--> Processing Dependency: python-fedora for package:
fedpkg-1.3.0.1-1.fc14.noarch
[... snip ...]
>  Removing:
>   MySQL-python         x86_64  1.2.3-1.fc14                      @updates  228 k
>  Removing for dependencies:
>   TurboGears           noarch  1.0.9-8.fc14                      @updates  7.6 M
>   bodhi-client         noarch  0.8.0-1.fc14                      @updates   25 k
>   fedora-easy-karma    noarch  0-0.15.20110825git36efb338.fc14   @updates   75 k
>   fedora-packager      noarch  0.5.9.2-2.fc14                    @updates   72 k
>   fedpkg               noarch  0.5.9.2-2.fc14                    @updates  248 k
>   python-fedora        noarch  0.3.25.1-1.fc14.1                 @updates  1.7 M
>   python-sqlobject     noarch  0.10.2-6.fc14                     @fedora   1.6 M
>  
>  Needless to say, that would put rather a crimp in my ability to do any
>  Fedora packaging work on this machine.
>  
>  AFAIK, there is no legitimate reason for fedpkg or fedora-packager to
>  need to talk to a mysql database, 
They don't.

They require python-fedora, which provides a client library (used by
fedpkg iirc) as well as the necessary integration with FAS for
TurboGears, TurboGears2, Django, etc...

Perhaps python-fedora would need to be splitted then? That would have
the added benefit to remove those web stacks, rather than just the mere
228kB taken by MySQL-python.

I guess it just takes someone to do it. ;)


-- 
Mathieu

[Toshio Kuratomi]

On Tue, Nov 22, 2011 at 01:16:01AM -0500, Tom Lane wrote:
>  I was rather surprised to find a routine "yum update" on my
> F14 system
>  suddenly wanting to pull in a lot of mysql stuff that I'd not had
>  installed at the moment.  Investigation showed that if I try to remove
>  MySQL-python again, yum wants to take all this stuff with it:
>  
>  Removing:
>   MySQL-python         x86_64  1.2.3-1.fc14                      @updates  228 k
>  Removing for dependencies:
>   TurboGears           noarch  1.0.9-8.fc14                      @updates  7.6 M
>   bodhi-client         noarch  0.8.0-1.fc14                      @updates   25 k
>   fedora-easy-karma    noarch  0-0.15.20110825git36efb338.fc14   @updates   75 k
>   fedora-packager      noarch  0.5.9.2-2.fc14                    @updates   72 k
>   fedpkg               noarch  0.5.9.2-2.fc14                    @updates  248 k
>   python-fedora        noarch  0.3.25.1-1.fc14.1                 @updates  1.7 M
>   python-sqlobject     noarch  0.10.2-6.fc14                     @fedora   1.6 M
>  
>  Needless to say, that would put rather a crimp in my ability to do any
>  Fedora packaging work on this machine.
>  
>  AFAIK, there is no legitimate reason for fedpkg or fedora-packager to
>  need to talk to a mysql database, so I'd really like to see this
>  dependency go away again.  I have routine occasion to shuffle mysql
>  packages in and out, and I don't want entirely-unnecessary dependencies
>  getting in the way.
>   
Are you able to upgrade to a later Fedora?  I think you're seeing this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=754538

which is a confluence of the update policy and conflicting use cases wanting
a bug to either be fixed or not.  In Fedora > 14, this shouldn't be an
issue.

Note that for your use case, this dep chain might also be breakable in
python-sqlobject.  For python-sqlalchemy we decide that we only explicitly
rely on sqlite (which is provided by python itself these days).  We treat
MySQL and postgres backends as optional deps that users or applications must
explicitly install if they want to use them.

-Toshio

[Tom Lane]

Toshio Kuratomi <a.badger(a)gmail.com&gt; writes:
>  On Tue, Nov 22, 2011 at 01:16:01AM -0500, Tom Lane wrote:
> > I was rather surprised to find a routine "yum update" on my F14 system
> > suddenly wanting to pull in a lot of mysql stuff that I'd not had
> > installed at the moment. 
>  Are you able to upgrade to a later Fedora?  I think you're seeing
> this bug:
>  https://bugzilla.redhat.com/show_bug.cgi?id=754538 
Yes, that's the same issue, thanks for the reference.

Obviously, I won't be using F14 for very much longer.  What I was
mainly worried about was the possibility that this growth in deps was a
reflection of a new fedpkg version, so that I could expect to have to
contend with the issue even in F15 and beyond.  If the dependencies have
been cleaned up in more recent branches then my concern is minimal.

I do agree with the complainers in the BZ that this was something
inappropriate to do in F14, but what's done is done.  Even if you undid
it, anyone who's done "yum update" recently on an F14 box will have all
those unnecessary deps installed.  Personally, I always do a fresh
install not an upgrade when going to a new Fedora, so the extra deps
won't be permanent baggage for me, but they will be for other people.

			regards, tom lane

[Rahul Sundaram]

On 11/22/2011 09:02 PM, Tom Lane wrote:

>  I do agree with the complainers in the BZ that this was something
>  inappropriate to do in F14, but what's done is done.  Even if you undid
>  it, anyone who's done "yum update" recently on an F14 box will have all
>  those unnecessary deps installed. 
Not necessarily.  man yum.conf and read up on
clean_requirements_on_remove

Rahul