Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts - sarge security update finished

2006-05-29 Thread Martin Pitt
Hi Joey, Martin Schulze [2006-05-28 19:37 +0200]: [1] http://people.debian.org/~mpitt/psql-sarge/ [2] http://people.debian.org/~mpitt/psql-sarge/postgresql_7.4.7-6sarge2.debdiff Thanks a lot. However, could you redo the (source) package without the arch crap inside? There is no arch

Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts - sarge security update finished

2006-05-29 Thread Martin Schulze
Martin Pitt wrote: Hi Joey, Martin Schulze [2006-05-28 19:37 +0200]: [1] http://people.debian.org/~mpitt/psql-sarge/ [2] http://people.debian.org/~mpitt/psql-sarge/postgresql_7.4.7-6sarge2.debdiff Thanks a lot. However, could you redo the (source) package without the arch

Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts - sarge security update finished

2006-05-29 Thread Martin Pitt
Hi, Martin Schulze [2006-05-29 15:25 +0200]: Martin Pitt wrote: Hi Joey, Martin Schulze [2006-05-28 19:37 +0200]: [1] http://people.debian.org/~mpitt/psql-sarge/ [2] http://people.debian.org/~mpitt/psql-sarge/postgresql_7.4.7-6sarge2.debdiff Thanks a lot. However,

Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts - sarge security update finished

2006-05-28 Thread Martin Pitt
Hi security team, I backported the relevant changes from 7.4.13 and put the sarge security update to [1]. This time, just putting 7.4.13 into sarge-security would even have been safer IMHO, and that's what users would want anyway, but we already had this discussion several times, so I only ported

Bug#368645: CVE-2006-2313, CVE-2006-2314: encoding conflicts - sarge security update finished

2006-05-28 Thread Martin Schulze
Martin Pitt wrote: Hi security team, I backported the relevant changes from 7.4.13 and put the sarge security update to [1]. This time, just putting 7.4.13 into sarge-security would even have been safer IMHO, and that's what users would want anyway, but we already had this discussion