Re: Bug#678979: request freeze exception for slony1-2

On Sat, 2013-03-16 at 11:38 +, Adam D. Barratt wrote: > On Sun, 2012-10-07 at 14:30 +0200, Mehdi Dogguy wrote: > > On 21/09/2012 04:58, Peter Eisentraut wrote: > > > According to bug #678979 [0], which was submitted by the lead > > > upstream developer, slony

request freeze exception for slony1-2

According to bug #678979 [0], which was submitted by the lead upstream developer, slony 2.0 does not work well with postgresql 9.1. Therefore, we had to resolve to making an upgrade to slony version 2.1, and I request that that be allowed into wheezy now. To be precise: The source package name is

Re: please remove slony1 from testing

On mån, 2011-12-05 at 19:58 +, Adam D. Barratt wrote: > On Mon, 2011-12-05 at 20:15 +0200, Peter Eisentraut wrote: > > Please remove the slony1 source package (not to be confused with the > > slony1-2 source package) from testing, as it's obsolete and at the end > >

please remove slony1 from testing

Please remove the slony1 source package (not to be confused with the slony1-2 source package) from testing, as it's obsolete and at the end of its transition period. A marginally related bug is #639477, which I've set to serious, to keep the package out of testing. -- To UNSUBSCRIBE, email to

Re: [Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

On sön, 2010-01-03 at 18:10 +0100, Markus Wanner wrote: > Peter Eisentraut wrote: > > I guess the Python-packaging-like solution to that would be to always > > support two PostgreSQL releases per stable Debian release. > > I suspect that means one of them overlapping with o

Re: [Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

On ons, 2009-12-30 at 20:02 +0100, Martin Pitt wrote: > Dimitri Fontaine [2009-12-30 10:52 +0100]: > > That's why I proposed having a single binary package for any extension, > > embedding support for more than one major version of PostgreSQL. That > > would match how the code is maintained. > > T

Re: architecture wildcards, type-handling, etc.

On Wednesday 13 May 2009 21:55:00 Guillem Jover wrote: > So, there's missing support in sbuild (#501230), which arguably is > a pretty recent bug report, but AFAIR I sent a mail to Ryan long time > ago when drafting the wildcard support and never heard back, but then > I never insisted again, so th

dirmngr 1.0.2

The upstream maintainer of dirmngr (Werner Koch) has asked me to propose dirmngr 1.0.2 for inclusion into lenny: """ The last release is close to a year old but we have always worked on the package and made it more stable and added new features. Most work has been done as part of the Windows por

Consider unblocking mawk

(1.3.3-11.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/postinst: fix bashism. Closes: #308134 + + -- Peter Eisentraut <[EMAIL PROTECTED]> Sat, 05 Apr 2008 17:11:11 +0200 + mawk (1.3.3-11) unstable; urgency=low * 08_fix-for-gcc3.3.dpatch: grossly hack configure t

lenny NFS 4 release goal

You are listed as the advocate of a lenny release goal: # NFS version 4 support Advocate: Steinar H. Gunderson Description: Support version 4 of the NFS protocol everywhere. Bug-Tag: nfs-v4 State: confirmed (inherited from etch) There is no discernible bug list and the tag doesn't appear

Missing bug URLs for some release goals

In the list of release goals at , the goals NFS version 4 support I18n support for package descriptions don't show a bug URL. They also don't show a user email address, so I couldn't come up with a working usertag-based URL myself. Could the missing

Re: kolab-webadmin for etch

ned between the subversion repository and the ftp archive. -- Peter Eisentraut http://developer.postgresql.org/~petere/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kolab-webadmin for etch

This contains a small configuration update so that the installation interacts properly with the kolab-resource-manager package. kolab-webadmin (0.4.0-20060810-4) unstable; urgency=medium * Install the apache.conf file into the kolab directory to make sure we can enable it by default if t

Re: egroupware for etch

Steve Langasek wrote: > Yes, I'm afraid I can't view this as a routine "maintenance release" > with changes of this scope, and don't believe it's appropriate to > allow this update into etch at this point of the freeze. > > > Prehaps just the patches for php5.2 could be applied. > > I would accept

kolab-cyrus-imapd for etch

Please approve kolab-cyrus-imapd 2.2.13-2 for etch. This release only pulls in the changes of cyrus-imapd-2.2 2.2.13-10, which someone in the release team previously found worthwhile. kolab-cyrus-imapd (2.2.13-2) unstable; urgency=high * Synced against cyrus-imapd package -- Peter

egroupware for etch

Please approve egroupware 1.2.106-2.dfsg-1 for etch. This is a maintenance release over what is currently in etch, and it is required to be able to use PHP 5 and/or PostgreSQL 8.1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED

Re: How to get rid of db2latex-xsl in etch

Marc 'HE' Brockschmidt wrote: > Yes, I think this would be a good idea. Peter, could you do this or > do you of a reason to postpone this change? It's on its way. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#375077: udevd: nss_ldap: failed to bind to LDAP server -> boot fails

: #390926) + * When upgrading from earlier versions, remove rc.d symlinks and install +again in the new location (closes: #375077) + + -- Peter Eisentraut <[EMAIL PROTECTED]> Mon, 16 Oct 2006 12:37:56 +0200 + libnss-ldap (251-5.2) unstable; urgency=high * Non-maintainer upload. diff

Re: [Build-common-hackers] Re: cdbs update

Pierre Habouzit wrote: > Le sam 30 septembre 2006 10:16, Peter Eisentraut a écrit : > > * Move dh_installinit to binary-fixup to make sure its postinst > > fragment is the last (debhelper.mk) (closes: 386970) > > AIUI that would break deamons using dh_pysupport. This is e

cdbs update

+- Support patches ending in .diff (closes: #389508) +- Ensure exit status 0 in case of success (closes: #389929) + * Added XS-X-Vcs-Svn field + * Move dh_installinit to binary-fixup to make sure its postinst fragment + is the last (debhelper.mk) (closes: 386970) + + -- Peter Eisentrau

postgresql transition/upgrade strategy

Because of the transition to the multi-version postgresql packaging, we will have the situation in etch that someone who just does "apt-get install postgresql" (as has been the custom for many years) will always end up with the old version 7.4 instead of the newer 8.1. (The reason that postgres

licq on arm

I've been maintaining the licq package for over two years now, and it seems that the arm build gets lost at every single upload. I have regularly sent reminders to the buildd maintainers, but there was no consistent reaction. It almost appears as though this package is blacklisted in same fas

Help ntp into testing

Could you help 1:4.2.0a+stable-9 into testing? There are three outstanding RC bugs, but they're all in stable anyway, and the new package contains a number of improvements over testing. pgpLlOTUKqqW4.pgp Description: PGP signature

xmms-kde

I don't know what this means http://bjorn.haxx.se/debian/testing.pl?package=xmms-kde * xmms-kde has no old version in testing (trying to add, not update) * Adding xmms-kde makes 1 non-depending packages uninstallable on hppa: xmms-kde (recur was tried but failed) Could you please apply one of

Triggering rebuilds on all architectures

Someone NMU'ed one of my packages with a changelog entry of something like "trigger rebuild on all architectures". It was my understanding that this was frowned upon, and that one should contact buildds or the release team to do binary-only re-uploads. What would have been the preferred way t

egroupware 1.0.0.007-2.dfsg-3 for sarge

I have another one-line fix in egroupware that I want to propose for sarge: egroupware (1.0.0.007-2.dfsg-3) unstable; urgency=medium * Fixed PAM authentication (closes: #306729) -- Peter Eisentraut <[EMAIL PROTECTED]> Tue, 24 May 2005 11:11:11 +0200 The actual fix is

Re: egroupware 1.0.0.007-2.dfsg-2 for sarge

Steve Langasek wrote: > > Please allow egroupware 1.0.0.007-2.dfsg-2 into sarge. This is a > > one-line change to repair the calendar display in konqueror, which > > is unusable without this. > Approved. (Are you certain that this isn't a konqueror bug?) I am leaning in that direction, but who

egroupware 1.0.0.007-2.dfsg-2 for sarge

Please allow egroupware 1.0.0.007-2.dfsg-2 into sarge. This is a one-line change to repair the calendar display in konqueror, which is unusable without this. egroupware (1.0.0.007-2.dfsg-2) unstable; urgency=medium * Fix calendar month display in Konqueror -- Peter Eisentraut <[EM

Re: kdirstat 2.4.4-1 for sarge

Frank Lichtenheld wrote: > On Fri, May 06, 2005 at 09:27:06AM +0200, Peter Eisentraut wrote: > > In the alternative, would you accept an upload to t-p-u that fixes > > only #303809 in the current sarge version 2.4.0-2? > > I would definetly accept a upload to t-p-u for that

kdirstat 2.4.4-1 for sarge

implemented them are removed. * Changed to debhelper 4 [Peter Eisentraut] * Corrected use of configure --build and --host options [Peter Eisentraut] * Do not compress .docbook files (closes: #303809) [Peter Eisentraut] -- Mike Schacht <[EMAIL PROTECTED]> Fri, 15 Apr 2005 06:59:26

Please fix cdbs version 0.4.26-4

I just spent some hours battling against cdbs. I think the changes in 0.4.26-4 were a total desaster, leading to bugs #294694, #295250, #296763, #299010, #300465 and a few other ones that I might have to file after these ones are fixed. This potentially introduces build regressions in hundreds

Please consider lzo 1.08-2 for sarge

* Converted to dpatch * Updated libtool (closes: #261313) * Added minilzo to installation -- Peter Eisentraut <[EMAIL PROTECTED]> Thu, 11 Nov 2004 12:33:51 +0100

contrib packages with missing dependencies

Is there anything the release managers are able and willing to do in order to help some contrib packages with missing dependencies into sarge? There are several packages that have java dependencies that seemingly cannot be resolved without some sort of hammer. A sizeable list of possible candi

Re: Why is licq scheduled for removal?

Am Freitag, 22. Oktober 2004 14:17 schrieb Andreas Barth: > The current RC-bug that you just set to pending now - but I guess that > was just 10 hours too late. I uncommented the hint now, but AFAICS, it > will still be executed tonight. I understand. But two comments on that: 1. I'm all for agg

Why is licq scheduled for removal?

I happened to read that licq is scheduled for removal today: http://bjorn.haxx.se/debian/testing.pl?package=licq Does someone know why that is? The same questions goes for http://bjorn.haxx.se/debian/testing.pl?package=licq-plugin-osd

Remove postgresql-plruby on ia64 from sarge?

The latest postgresql-plruby package does not build on ia64 because the configuration script hangs indefinitely until the buildd kills it. I have asked around for help, but so far without success. Assuming that no fix for this problem appears very soon, can the previous build on ia64 be remov

Re: Upgrading stable postgresql to 7.2.4

Martin Pitt wrote: > > I don't know what the actual policy they apply regarding what kinds > > of bugfixes can go in such an update looks like; however, if it is > > (more or less) the same as the one Debian applies to stable updates > > (i.e., only patches to fix security holes, bugs that make the