Bug#630044: transition: poppler 0.16

Am 29.06.2011 19:11, schrieb Philipp Kern: > Hi, > > the only issue I see at the moment is this: > > On Fri, Jun 10, 2011 at 05:03:47PM +0200, Pino Toscano wrote: >> * python-poppler (poppler-glib) >> The (small) patch needed to compile with poppler 0.16 is not >> compatible with poppler

NEW changes in oldproposedupdates

Processing changes file: php5_5.2.6.dfsg.1-1+lenny11_amd64.changes ACCEPT Processing changes file: php5_5.2.6.dfsg.1-1+lenny11_alpha.changes ACCEPT Processing changes file: php5_5.2.6.dfsg.1-1+lenny11_arm.changes ACCEPT Processing changes file: php5_5.2.6.dfsg.1-1+lenny11_armel.changes ACCE

NEW changes in proposedupdates

Processing changes file: postgresql-8.4_8.4.8-0squeeze2_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qc6sd-xs...@franck.debian.org

Re: Bug#632028: postgresql 8.4.8 regression - failure to handle char(4) = bpchar

Hello Josip, Josip Rodin [2011-06-29 10:32 +0200]: > Unfortunately this "stable" upgrade of PostgreSQL 8.4.7-0squeeze2 to > 8.4.8-0squeeze1 introduced a bug apparently from the 9.0 branch that is > now consistently breaking queries on our production "stable" machines. I uploaded 8.4.8-0squeeze2 w

Bug#630044: transition: poppler 0.16

Hi, the only issue I see at the moment is this: On Fri, Jun 10, 2011 at 05:03:47PM +0200, Pino Toscano wrote: > * python-poppler (poppler-glib) > The (small) patch needed to compile with poppler 0.16 is not > compatible with poppler 0.12, so it cannot be uploaded right now. > Asked to

Bug#623999: transition: libuim6

On Wed, May 18, 2011 at 02:24:46PM +0200, Mehdi Dogguy wrote: > On 25/04/2011 09:59, Kiwamu Okabe wrote: > > I'd like to upload > > http://mentors.debian.net/debian/pool/main/u/uim/uim_1.6.1-3.dsc, > > which has changed SONAME (libuim6 => libuim7), to unstable. > > > > There is reverse-dependencie

Re: SAT based britney - handling conflicts

Hi, On Thu, Jun 23, 2011 at 10:25:55AM +0200, Raphael Hertzog wrote: > You're suggesting that one way to legitimately ignore the problem of > Conflicts would be to have the Debian policy only allow usage of Conflicts > for cases that cannot create problems during testing migration. Is that > righ

Re: SAT based britney - formalisation of the problem

Hi again, On Thu, Jun 23, 2011 at 01:06:44PM +0200, Joachim Breitner wrote: > > But according to our experience, for it to happen > > the problem should not be underestimated and, more importantly, should > > be properly formalized in a way which is independent of some specific > > encoding techn

Re: Updates question

On Wed, Jun 29, 2011 at 03:48:49PM +0200, Pontus Andersson wrote: >Hi. > >I have previously downloaded all Debian 6.0.1 DVD's to be used on >non-internet access computers. > >Question 1: To get updates 6.0.2 is it enough to download: > >debian-update-6.0.2.1-i386-DVD-1.iso >

Updates question

Hi. I have previously downloaded all Debian 6.0.1 DVD's to be used on non-internet access computers. Question 1: To get updates 6.0.2 is it enough to download: debian-update-6.0.2.1-i386-DVD-1.iso and

Re: Updates for dokuwiki

On Wed, 29 Jun 2011 01:59:28 +0200, Tanguy Ortolo wrote: Adam D. Barratt, 2011-06-27 19:48 UTC+0100: The security patches themselves look fine, however a Standards-Version change isn't really appropriate for a stable update, even when it requires no modification to the package other than changi

Processed: unblock 622279 with 624975 625027 614619 621829

Processing commands for cont...@bugs.debian.org: > # packages not in testing, they do not block anything > unblock 622279 with 624975 625027 614619 621829 Bug #622279 [release.debian.org] transition: python-defaults (switching default: 2.6 -> 2.7) Was blocked by: 628860 629085 628243 625676 62358

Re: Bug#632028: postgresql 8.4.8 regression - failure to handle char(4) = bpchar

On Wed, Jun 29, 2011 at 10:32:27AM +0200, Josip Rodin wrote: > Unfortunately this "stable" upgrade of PostgreSQL 8.4.7-0squeeze2 to > 8.4.8-0squeeze1 introduced a bug apparently from the 9.0 branch that is > now consistently breaking queries on our production "stable" machines. I propose the attac

NEW changes in oldproposedupdates

Processing changes file: dokuwiki_0.0.20080505-4+lenny3_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qbpzo-0005bh...@franck.debian.org

NEW changes in proposedupdates

Processing changes file: dokuwiki_0.0.20091225c-10+squeeze2_amd64.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qbpzn-0005b2...@franck.debian.or