Re: [pgadmin-hackers] Release schedule
Dave Page wrote: I can't delay the main release anyway - the balls already rolled too far down the hill (if you get my drift). Regards, Dave. -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: Sat 11/5/2005 7:42 AM To: Dave Page Cc: pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Dave Page wrote: Just for info, I plan to build 1.4.0 tomorrow night (Saturday, GMT), once the PostgreSQL 8.1 docs are available from Marc. I'll upload once done for testing on Saturday/Sunday, and announce on Monday. So, we can builb packages based on: http://bp.pgadmin.org/ftp/release/v1.4.0/src/pgadmin3-1.4.0.tar.gz that's it? Cheers, Raphaël ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [pgadmin-hackers] Release schedule
On 6/11/05 9:01 am, Raphaël Enrici [EMAIL PROTECTED] wrote: Dave Page wrote: I can't delay the main release anyway - the balls already rolled too far down the hill (if you get my drift). Regards, Dave. -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: Sat 11/5/2005 7:42 AM To: Dave Page Cc: pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Dave Page wrote: Just for info, I plan to build 1.4.0 tomorrow night (Saturday, GMT), once the PostgreSQL 8.1 docs are available from Marc. I'll upload once done for testing on Saturday/Sunday, and announce on Monday. So, we can builb packages based on: http://bp.pgadmin.org/ftp/release/v1.4.0/src/pgadmin3-1.4.0.ta r.gz that's it? Yes, that's it - packagers, please go forth and package! There is one minor issue btw - I found that the slony docs weren't included in the source tarball. I added them in, but unfortunately, 3 of the have a name that is too long, which causes the tarball to double in size for some bizarre reason. I dropped the 3 files from the tarball as this is going to be non-trivial to fix - you might prefer to build from svn://svn.pgadmin.org/tags/REL-1_4_0/pgadmin so your distro does include the missing files. Regards, Dave ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Release schedule
Dave Page wrote: On 6/11/05 9:01 am, Raphaël Enrici [EMAIL PROTECTED] wrote: Dave Page wrote: I can't delay the main release anyway - the balls already rolled too far down the hill (if you get my drift). Regards, Dave. -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: Sat 11/5/2005 7:42 AM To: Dave Page Cc: pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Dave Page wrote: Just for info, I plan to build 1.4.0 tomorrow night (Saturday, GMT), once the PostgreSQL 8.1 docs are available from Marc. I'll upload once done for testing on Saturday/Sunday, and announce on Monday. So, we can builb packages based on: http://bp.pgadmin.org/ftp/release/v1.4.0/src/pgadmin3-1.4.0.ta r.gz that's it? Yes, that's it - packagers, please go forth and package! There is one minor issue btw - I found that the slony docs weren't included in the source tarball. I added them in, but unfortunately, 3 of the have a name that is too long, which causes the tarball to double in size for some bizarre reason. I dropped the 3 files from the tarball as this is going to be non-trivial to fix - you might prefer to build from svn://svn.pgadmin.org/tags/REL-1_4_0/pgadmin so your distro does include the missing files. Can you list the missing ones please? For Debian packaging I need to keep the original tarball (that's a mandatory rule). I'll add them as a patch. Regards, Raph ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] SVN Commit by dpage: r4683 - trunk/pgadmin3/pkg/debian
Author: dpage Date: 2005-11-06 10:48:38 + (Sun, 06 Nov 2005) New Revision: 4683 Modified: trunk/pgadmin3/pkg/debian/rules Log: Set executable, per Raph Property changes on: trunk/pgadmin3/pkg/debian/rules ___ Name: svn:executable + * ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[pgadmin-hackers] SVN Commit by dpage: r4684 - branches/REL-1_4_0_PATCHES/pgadmin3/pkg/debian
Author: dpage Date: 2005-11-06 10:56:54 + (Sun, 06 Nov 2005) New Revision: 4684 Modified: branches/REL-1_4_0_PATCHES/pgadmin3/pkg/debian/rules Log: Set executable, per Raph Property changes on: branches/REL-1_4_0_PATCHES/pgadmin3/pkg/debian/rules ___ Name: svn:executable + * ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Release schedule
-Original Message- From: Raphaël Enrici [mailto:[EMAIL PROTECTED] Sent: 06 November 2005 10:37 To: Dave Page Cc: Andreas Pflug; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Can you list the missing ones please? For Debian packaging I need to keep the original tarball (that's a mandatory rule). I'll add them as a patch. docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html Not the shortest names are they? Oddly, it seems to work OK if I build the tarball on OS X, which is fine if it weren't for the fact that developer.pgadmin.org runs Slackware... tardir=pgadmin3-1.5.0 /bin/sh /usr/local/src/pgadmin3/config/missing --run tar chof - $tardir | GZIP=--best gzip -c pgadmin3-1.5.0.tar.gz tar: pgadmin3-1.5.0/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text.html: file name is too long (max 99); not dumped tar: pgadmin3-1.5.0/docs/en_US/slony/function.forwardconfirm-integer-integer-bigint-timestamp-without-time-zone.html: file name is too long (max 99); not dumped tar: pgadmin3-1.5.0/docs/en_US/slony/function.createevent-name-text-text-text-text-text-text-text-text-text.html: file name is too long (max 99); not dumped tar: Error exit delayed from previous errors :-( Regards, Dave ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] SVN Commit by dpage: r4687 - trunk/pgadmin3
Author: dpage Date: 2005-11-06 11:14:33 + (Sun, 06 Nov 2005) New Revision: 4687 Modified: trunk/pgadmin3/configure.ac Log: Fix copyright Modified: trunk/pgadmin3/configure.ac === --- trunk/pgadmin3/configure.ac 2005-11-06 11:14:03 UTC (rev 4686) +++ trunk/pgadmin3/configure.ac 2005-11-06 11:14:33 UTC (rev 4687) @@ -1,6 +1,6 @@ AC_PREREQ(2.57) AC_REVISION($Revision$) -AC_COPYRIGHT(Copyright 2002 - 2004 The pgAdmin Development Team) +AC_COPYRIGHT(Copyright 2002 - 2005 The pgAdmin Development Team) AC_INIT(pgadmin3, 1.5.0, pgadmin-support@postgresql.org) AC_CONFIG_AUX_DIR(config) AC_CONFIG_SRCDIR([src/pgAdmin3.cpp]) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] Release schedule
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page Sent: 06 November 2005 11:07 To: Raphaël Enrici Cc: Andreas Pflug; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule -Original Message- From: Raphaël Enrici [mailto:[EMAIL PROTECTED] Sent: 06 November 2005 10:37 To: Dave Page Cc: Andreas Pflug; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Can you list the missing ones please? For Debian packaging I need to keep the original tarball (that's a mandatory rule). I'll add them as a patch. docs/en_US/slony/function.createevent-name-text-text-text-text -text-text-text-text.html docs/en_US/slony/function.forwardconfirm-integer-integer-bigin t-timestamp-without-time-zone.html docs/en_US/slony/function.createevent-name-text-text-text-text -text-text-text-text-text.html Not the shortest names are they? Oddly, it seems to work OK if I build the tarball on OS X, which is fine if it weren't for the fact that developer.pgadmin.org runs Slackware... tardir=pgadmin3-1.5.0 /bin/sh /usr/local/src/pgadmin3/config/missing --run tar chof - $tardir | GZIP=--best gzip -c pgadmin3-1.5.0.tar.gz tar: pgadmin3-1.5.0/docs/en_US/slony/function.createevent-name-text -text-text-text-text-text-text-text.html: file name is too long (max 99); not dumped tar: pgadmin3-1.5.0/docs/en_US/slony/function.forwardconfirm-intege r-integer-bigint-timestamp-without-time-zone.html: file name is too long (max 99); not dumped tar: pgadmin3-1.5.0/docs/en_US/slony/function.createevent-name-text -text-text-text-text-text-text-text-text.html: file name is too long (max 99); not dumped tar: Error exit delayed from previous errors Having said that - I did just find a fix. Hold on, and I'll re-roll the tarball. /D ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] Release schedule
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page Sent: 06 November 2005 11:16 To: Raphaël Enrici Cc: Andreas Pflug; pgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule Having said that - I did just find a fix. Hold on, and I'll re-roll the tarball. There - re-rolled. Apologies to any of the packagers who were faster than me :-) Now for some sleep... Regards, Dave. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[pgadmin-hackers] OS X src deficiency?
Hi,I checked the RC1 package for DarwinPorts (for OS X). It seems to me, however, that the script 'complete-bundle.sh' is missing in pkg/mac directory. Am I right or am I missing something (at least the build process seems to require it)? Otherwise it builds fine.Another thing I noticed missing was the unix_compilation document that is supposed to be in docs. It is referred to in README.txt, but it does not exist.PS I am sorry that pgAdmin isn't yet in DarwinPorts tree, but that is beyond my control. I'll submit the Portfile for 1.4.0 again and let's hope for the best… !! Jyrki Wahlstedt! Männikkötie 5 D 19 mob. +358-40-502 0164! FI-00630 Helsinki!! Our life is no dream; but it ought to become one and perhaps will.! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
Re: [pgadmin-hackers] Release schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sun, 6 Nov 2005, Dave Page wrote: There is one minor issue btw - I found that the slony docs weren't included in the source tarball. I added them in, but unfortunately, 3 of the have a name that is too long, which causes the tarball to double in size for some bizarre reason. I dropped the 3 files from the tarball as this is going to be non-trivial to fix - you might prefer to build from svn://svn.pgadmin.org/tags/REL-1_4_0/pgadmin so your distro does include the missing files. I think you should rebuild the tarball or directly release 1.4.0-2. The tarball on the FTP site and the tarball I'll use in the RPMs will differ and IMHO it means that what I'll use will not be 1.4.0. Regards, - -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDbfOR4zE8DGqpiZARAlfYAKCFsQODNHuTS2gOVyeFNfEP1L2FpgCeO6dS wvp9aDTy6OP+tVVwk5qSf54= =xv95 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] OS X src deficiency?
-Original Message- From: Jyrki Wahlstedt[EMAIL PROTECTED] Sent: 06/11/05 12:08:11 To: pgadmin-hackerspgadmin-hackers@postgresql.org Subject: [pgadmin-hackers] OS X src deficiency? I checked the RC1 package for DarwinPorts (for OS X). It seems to me, however, that the script 'complete-bundle.sh' is missing in pkg/mac directory. Yes, fixed in the release tarball though. Another thing I noticed missing was the unix_compilation document that is supposed to be in docs. It is referred to in README.txt, but it does not exist. Drat. The file was deprecated a while back. I'll need to remove the reference. Thanks. PS I am sorry that pgAdmin isn't yet in DarwinPorts tree, but that is beyond my control. I'll submit the Portfile for 1.4.0 again and let's hope for the best… Great, thanks. Regards, Dave -Unmodified Original Message- Hi, I checked the RC1 package for DarwinPorts (for OS X). It seems to me, however, that the script 'complete-bundle.sh' is missing in pkg/mac directory. Am I right or am I missing something (at least the build process seems to require it)? Otherwise it builds fine. Another thing I noticed missing was the unix_compilation document that is supposed to be in docs. It is referred to in README.txt, but it does not exist. PS I am sorry that pgAdmin isn't yet in DarwinPorts tree, but that is beyond my control. I'll submit the Portfile for 1.4.0 again and let's hope for the best… ! ! Jyrki Wahlstedt ! Männikkötie 5 D 19mob. +358-40-502 0164 ! FI-00630 Helsinki ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386 ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Release schedule
-Original Message- From: Devrim GUNDUZ[EMAIL PROTECTED] Sent: 06/11/05 12:14:17 To: Dave Pagedpage@vale-housing.co.uk Cc: pgadmin-hackers@postgresql.orgpgadmin-hackers@postgresql.org Subject: Re: [pgadmin-hackers] Release schedule -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sun, 6 Nov 2005, Dave Page wrote: There is one minor issue btw - I found that the slony docs weren't included in the source tarball. I added them in, but unfortunately, 3 of the have a name that is too long, which causes the tarball to double in size for some bizarre reason. I dropped the 3 files from the tarball as this is going to be non-trivial to fix - you might prefer to build from svn://svn.pgadmin.org/tags/REL-1_4_0/pgadmin so your distro does include the missing files. I think you should rebuild the tarball or directly release 1.4.0-2. The tarball on the FTP site and the tarball I'll use in the RPMs will differ and IMHO it means that what I'll use will not be 1.4.0. I stumbled across the fix and rebuilt the tarball, per my earlier email :-) Make sure you get the tarball from developer.pgadmin.org though, as the older one might still be on the mirrors for a day or so. Cheers, Dave -Unmodified Original Message- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sun, 6 Nov 2005, Dave Page wrote: There is one minor issue btw - I found that the slony docs weren't included in the source tarball. I added them in, but unfortunately, 3 of the have a name that is too long, which causes the tarball to double in size for some bizarre reason. I dropped the 3 files from the tarball as this is going to be non-trivial to fix - you might prefer to build from svn://svn.pgadmin.org/tags/REL-1_4_0/pgadmin so your distro does include the missing files. I think you should rebuild the tarball or directly release 1.4.0-2. The tarball on the FTP site and the tarball I'll use in the RPMs will differ and IMHO it means that what I'll use will not be 1.4.0. Regards, - -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDbfOR4zE8DGqpiZARAlfYAKCFsQODNHuTS2gOVyeFNfEP1L2FpgCeO6dS wvp9aDTy6OP+tVVwk5qSf54= =xv95 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[pgadmin-hackers] Manpage writing guidelines?
To be able to upload to official Debian, I need to have a manpage for each program uploaded in the package. I wrote a long time ago a small manpage for pgadmin3 and I am about to write one for pgagent. Here are some questions: - wouldn't it be a good thing that pgadmin3.1 is pushed out of pkg/debian to a more proper place and included in the make install process? - what tools should we use to write our manpages? Something like xml or whatever? I mean, if we are about to do something to automate html help generation and other thing I'm not aware of, maybe it would be a good thing to unify the way we work. Any ideas? Regards, Raph ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Manpage writing guidelines?
Hi Raph, There are obviously no guidelines at the moment, so please write whatever seems appropriate for now. I do plan to work on the docs this cycle, so please raise this again then if I forget. Andreas and I were talking about improving the doc build just last week (it's perhaps the biggest task for me when packing pgInstaller or pgAdmin at the moment). Regards, Dave. -Original Message- From: Raphaël Enrici [mailto:[EMAIL PROTECTED] Sent: Sun 11/6/2005 12:56 PM To: PgAdmin Hackers; Dave Page; Andreas Pflug Subject: Manpage writing guidelines? To be able to upload to official Debian, I need to have a manpage for each program uploaded in the package. I wrote a long time ago a small manpage for pgadmin3 and I am about to write one for pgagent. Here are some questions: - wouldn't it be a good thing that pgadmin3.1 is pushed out of pkg/debian to a more proper place and included in the make install process? - what tools should we use to write our manpages? Something like xml or whatever? I mean, if we are about to do something to automate html help generation and other thing I'm not aware of, maybe it would be a good thing to unify the way we work. Any ideas? Regards, Raph ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] Manpage writing guidelines?
Le Dimanche 06 Novembre 2005 19:24, Dave Page a écrit : There are obviously no guidelines at the moment, so please write whatever seems appropriate for now. I do plan to work on the docs this cycle, so please raise this again then if I forget. Andreas and I were talking about improving the doc build just last week (it's perhaps the biggest task for me when packing pgInstaller or pgAdmin at the moment). Can you explain a bit what is the daunting task for docs ? I think I should include the PostgreSQL french manual in pgAdmin but I don't know if there is an automated way to do the conversion docbook sgml to chm. Can you explain how you did it ? Regards. -- Guillaume. !-- http://abs.traduc.org/ http://lfs.traduc.org/ http://traduc.postgresqlfr.org/ -- ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[pgadmin-hackers] SVN Commit by dpage: r4689 - trunk/pgadmin3
Author: dpage Date: 2005-11-06 22:34:35 + (Sun, 06 Nov 2005) New Revision: 4689 Modified: trunk/pgadmin3/README.txt Log: Update references Modified: trunk/pgadmin3/README.txt === --- trunk/pgadmin3/README.txt 2005-11-06 11:18:07 UTC (rev 4688) +++ trunk/pgadmin3/README.txt 2005-11-06 22:34:35 UTC (rev 4689) @@ -12,8 +12,8 @@ Compilation --- -Unix: Please see docs/en_US/unix_compilation.html for details of building - pgAdmin III on unix platforms. +Unix: Please see http://www.pgadmin.org/download.php#source for details of + building pgAdmin III on unix platforms. Win32: pgAdmin III can be compiled on Windows using MS Visual C++. We use 6.0 with service pack 5. The project workspace file can be found in the @@ -23,4 +23,5 @@ --- Translation into your preferred language is easily possible even for -non-programmers. Please see docs/en_US/translation_*.html for further details. +non-programmers. Please see http://www.pgadmin.org/translation.php for +further details. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Manpage writing guidelines?
On 6/11/05 6:52 pm, Guillaume LELARGE [EMAIL PROTECTED] wrote: Le Dimanche 06 Novembre 2005 19:24, Dave Page a écrit : There are obviously no guidelines at the moment, so please write whatever seems appropriate for now. I do plan to work on the docs this cycle, so please raise this again then if I forget. Andreas and I were talking about improving the doc build just last week (it's perhaps the biggest task for me when packing pgInstaller or pgAdmin at the moment). Can you explain a bit what is the daunting task for docs ? OK, I'll try to remember everything! 1) In a postgresql source tree, run 'make htmlhelp'. This will most likely crash in xsltproc after 10 minutes or so as seen by numerous people on various OS's. 2) Tar up the doc/src/sgml directory and copy it to a Windows machine (fc4 64 bit has also worked for me, but not recently). Re-run the xsltproc step on this box. I do this in 2 steps, because setting up docbook et al. on Windows is non-trivial. 3) Repeat 1 2 for the Slony docs. 4) Manually merge both the PG and Slony help project, index and contents files into the pgAdmin ones. Paths in each file will need to be prefixed with pg/ or slony/ as appropriate. 5) Copy the the PG and Slony docs into the appropriate en_US subdirectory. 5) Load the project into Microsoft HTML Help Workshop. Check the index structure, and move at least 1 item. If necessary, move it, then move it back. This makes the IDE rewrite the index file and fixup an broken markup, or markup it doesn't like for reasons you probably won't ever be able to spot! 6) Repeat 5 for the contents file. 7) Save both files, as well as the project file. 8) Build the HMTL Help File. 9) Generate pgadmin3.hhp.cached file use on *nix, using hhp2cached. If this crashes, try again a couple of times until it works. You might want to prefix the filename with .\ . 10) Commit the updated docs and indexes etc. to SVN. I think I should include the PostgreSQL french manual in pgAdmin but I don't know if there is an automated way to do the conversion docbook sgml to chm. Can you explain how you did it ? The idea always was to get full manuals for each language, but then originally we didn't bundle the pgAdmin and Slony docs. The problem now is that if we do so, the tarball is rapidly going to get huge. I think if we're going to do this, we a) need some serious commitment form the translators that it will be maintained, and b) need to look at packaging translations as 'language packs' that can be downloaded separately from the main package in both the source and binary distributions. Thoughts? Regards, Dave ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] SVN Commit by dpage: r4685 - trunk/pgadmin3
[EMAIL PROTECTED] wrote: Modified: trunk/pgadmin3/configure.ac === --- trunk/pgadmin3/configure.ac 2005-11-06 10:56:54 UTC (rev 4684) +++ trunk/pgadmin3/configure.ac 2005-11-06 11:13:18 UTC (rev 4685) @@ -6,7 +6,7 @@ AC_CONFIG_SRCDIR([src/pgAdmin3.cpp]) AM_CONFIG_HEADER([config.h]) AC_CANONICAL_HOST -AM_INIT_AUTOMAKE +AM_INIT_AUTOMAKE([tar-ustar]) This broke the nightly builds. What version of automake is required for this to work? (And, because I'm curious, what does it do? ;-) ). greetings, Florian Pflug smime.p7s Description: S/MIME Cryptographic Signature
[pgadmin-hackers] SVN Commit by dpage: r4690 - branches/REL-1_4_0_PATCHES/pgadmin3
Author: dpage Date: 2005-11-06 22:37:41 + (Sun, 06 Nov 2005) New Revision: 4690 Modified: branches/REL-1_4_0_PATCHES/pgadmin3/README.txt Log: Update references Modified: branches/REL-1_4_0_PATCHES/pgadmin3/README.txt === --- branches/REL-1_4_0_PATCHES/pgadmin3/README.txt 2005-11-06 22:34:35 UTC (rev 4689) +++ branches/REL-1_4_0_PATCHES/pgadmin3/README.txt 2005-11-06 22:37:41 UTC (rev 4690) @@ -12,8 +12,8 @@ Compilation --- -Unix: Please see docs/en_US/unix_compilation.html for details of building - pgAdmin III on unix platforms. +Unix: Please see http://www.pgadmin.org/download.php#source for details of + building pgAdmin III on unix platforms. Win32: pgAdmin III can be compiled on Windows using MS Visual C++. We use 6.0 with service pack 5. The project workspace file can be found in the @@ -23,4 +23,5 @@ --- Translation into your preferred language is easily possible even for -non-programmers. Please see docs/en_US/translation_*.html for further details. +non-programmers. Please see http://www.pgadmin.org/translation.php for +further details. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] Release schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Sun, 6 Nov 2005, Dave Page wrote: I think you should rebuild the tarball or directly release 1.4.0-2. The tarball on the FTP site and the tarball I'll use in the RPMs will differ and IMHO it means that what I'll use will not be 1.4.0. I stumbled across the fix and rebuilt the tarball, per my earlier email :-) Opps :( Sorry for the noise. Make sure you get the tarball from developer.pgadmin.org though, as the older one might still be on the mirrors for a day or so. Ok, I've built the Fedora Core 4 RPM. It's on developer site atm. More will come later, after PostgreSQL 8.1 will be released. BTW Turkish translation is also ready but I think we are a bit late for it ;) I'll make it happen for 1.4.1. Regards, - -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDbsRb4zE8DGqpiZARAnBvAJ4hT6+RgX345HfGhHjT3rYhmMQlPwCeMGfj 4u5O/XskRKj3jEkfxtwKZek= =3vw6 -END PGP SIGNATURE- ---(end of broadcast)--- TIP 6: explain analyze is your friend
[pgadmin-hackers] The problem in Japanese.
Hi Andreas. situation) 20050914th did not have a problem. However, Problem reproduces the 20050926th edition. Probably, It seems that a change in the meantime has influenced. If you have some hints, please let me know. I am going to try this evening (8 more hours after) again. http://cre-ent.skcapi.co.jp/~saito/pgadmin3/pgAdmin3_crash.png Regards, Hiroshi Saito ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
