Hi!

 Forgot to Cc this mail to the bugreports so that all involved parties
are informed about my plans. Here it goes:

----- Forwarded message from Gerfried Fuchs <[EMAIL PROTECTED]> -----

Date: Tue, 20 May 2008 13:25:43 +0200
From: Gerfried Fuchs <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: pgadmin3 for experimental

        Hi!

 As I haven't seen any further reply to my last ping about the status
of the package I plan to do an NMU for pgadmin3 to experimental. I am
currently so far that the building works. I will of course send the
changes on to the according bugreports.

 Things I noticed: The content of the svn repository isn't based on the
NMU that was done in may 2007 but on the version from before that. It
thus revertes the binNMU-safetyness. Not getting rid of that changes is
a must here, especially since they were in there for so long already.
The changelog entries in the svn though never seem to have found any
light, or I was unable to find the place where they were uploaded with
that.

 That's the main reasons why my NMU will be based on what's in the pool
instead of what's in the svn repository. This is the changelog entries
so far:

#v+
  * Non-Maintainer Upload of new upstream version to experimental.
  * New upstream release:
    - Build-Depends on libwxgtk2.8-dev instead of libwxgtk2.6-dev.
    - Versioned-Depends on libpq-dev bumped to >= 8.1.
    - New Build-Depends on libxml2-dev and libxslt1-dev.
  * Build-Depend on autotools-dev and pull in config.{guess,sub} on build time
    instead of copying over on clean target if existing, to make it more 
    relyable and not have it in the .diff.gz.
  * Don't ignore errors on make clean anymore.
  * Remove unneccessary patches from all Makefile.in files.
  * Bump Standards-Version to 3.7.3.
  * Fixed filenames in debian/pgadmin3.docs, got rid of the additionally
    generated TODO.txt.
#v-

 As version I've chosen to use 1.8.2-0.1 so it won't clutter with any
maintainer upload that might be worked on in silence.

 So long,
Rhonda

----- End forwarded message -----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to