<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>197799</bug_id>
          
          <creation_ts>2007-11-01 18:42 0000</creation_ts>
          <short_desc>Please stabilize =gnome-extra/libgda-1.2.4</short_desc>
          <delta_ts>2007-11-10 12:14:28 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>2007.0</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <keywords>STABLEREQ</keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>183465</dependson>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>mike@nerone.org</reporter>
          <assigned_to>gnome@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>mike@nerone.org</who>
            <bug_when>2007-11-01 18:42:15 0000</bug_when>
            <thetext>The current stable, libgd-1.2.3, deps on postgresql, when all it needs is libpq. This has been fixed in the unstable libgd-1.2.4 since January. Can we either get libgd-1.2.4 stablized or at least get the dep fixed in a revbump to libgd-1.2.3?

It&apos;s not critical, of course, but it&apos;s a trivially-fixed annoyance that&apos;s been around for a while now.

Thanks much!</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jakub@gentoo.org</who>
            <bug_when>2007-11-01 19:26:25 0000</bug_when>
            <thetext>There&apos;s no libgd anywhere. If you mean media-libs/gd then it doesn&apos;t depend on postgresql at all. If you mean something else, then you&apos;ll have to tell us what ebuild is this about.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>mike@nerone.org</who>
            <bug_when>2007-11-01 19:29:14 0000</bug_when>
            <thetext>Cripes - sorry, s/libgd/libgda/

Summary updated, too.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>eva@gentoo.org</who>
            <bug_when>2007-11-01 21:57:38 0000</bug_when>
            <thetext>no bugs since at least 2007-08-01.
I&apos;d vote for stabilizing 1.2.4</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dang@gentoo.org</who>
            <bug_when>2007-11-03 14:21:07 0000</bug_when>
            <thetext>I agree.

Arches: target keywords are:
alpha amd64 hppa ia64 ppc ppc64 sparc x86

x86-fbsd: It&apos;s up you you; you don&apos;t have the old version stable.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>armin76@gentoo.org</who>
            <bug_when>2007-11-04 11:04:43 0000</bug_when>
            <thetext>test fails, stable doesn&apos;t:

make[1]: Leaving directory `/var/tmp/portage/gnome-extra/libgda-1.2.4/work/libgda-1.2.4/data&apos;
Making check in po
make[1]: Entering directory `/var/tmp/portage/gnome-extra/libgda-1.2.4/work/libgda-1.2.4/po&apos;
INTLTOOL_EXTRACT=../intltool-extract srcdir=. ../intltool-update --gettext-package libgda-2 --pot
rm -f missing notexist
srcdir=. ../intltool-update -m
The following files contain translations and are currently not in use. Please
consider adding these to the POTFILES.in file, located in the po/ directory.

libsql/parser.c

If some of these files are left out on purpose then please add them to
POTFILES.skip instead of POTFILES.in. A file &apos;missing&apos; containing this list
of left out files has been written in the current directory.
if [ -r missing -o -r notexist ]; then \
          exit 1; \
        fi
make[1]: *** [check] Error 1
make[1]: Leaving directory `/var/tmp/portage/gnome-extra/libgda-1.2.4/work/libgda-1.2.4/po&apos;
make: *** [check-recursive] Error 1
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>eva@gentoo.org</who>
            <bug_when>2007-11-04 19:28:24 0000</bug_when>
            <thetext>actually I forgot bug #183465 was still open.
otherwise, the test is now fixed in cvs</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lavajoe@gentoo.org</who>
            <bug_when>2007-11-04 20:00:17 0000</bug_when>
            <thetext>BSD has no stable keyword yet...  we&apos;re keyworded in 1.2.4 though.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>armin76@gentoo.org</who>
            <bug_when>2007-11-05 10:25:26 0000</bug_when>
            <thetext>alpha/ia64/sparc stable</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2007-11-06 17:23:35 0000</bug_when>
            <thetext>Stable for HPPA.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>corsair@gentoo.org</who>
            <bug_when>2007-11-06 19:17:51 0000</bug_when>
            <thetext>ppc64 stable</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>wltjr@gentoo.org</who>
            <bug_when>2007-11-06 21:57:17 0000</bug_when>
            <thetext>Really need to unmask and see about getting 3.0.1 stabilized. Current upstream release is 3.0 and development is 3.1.3. So 1.2.x is quite old and outdated. Doesn&apos;t compile against newer versions of Firebird in tree, etc and so on.

I would imagine not many users using this. Or there would be requests to get this ebuild current or etc. 3.0.1 has been masked for most of this year. No open bugs, so I say, unmask see if it causes any problems. If not then look to stabilize that version ASAP and clean out 1.2.x cruft. IMHO :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>fauli@gentoo.org</who>
            <bug_when>2007-11-08 08:59:52 0000</bug_when>
            <thetext>x86 stable</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dang@gentoo.org</who>
            <bug_when>2007-11-08 21:58:43 0000</bug_when>
            <thetext>amd64 done.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nixnut@gentoo.org</who>
            <bug_when>2007-11-10 12:14:28 0000</bug_when>
            <thetext>ppc stable, closing since we&apos;re last</thetext>
          </long_desc>
      
    </bug>

</bugzilla>