Bug#709865: transition: libosip2

2013-06-12 Thread Julien Cristau 
On Sat, Jun  1, 2013 at 16:14:43 +0200, Julien Cristau wrote:

 On Sun, May 26, 2013 at 15:39:26 +1000, Mark Purcell wrote:
 
  sipwitch  FTBFS #707450
  linphone  FTBFS #709860
  
 What's the plan for getting these fixed?
 
Ping?

Cheers,
Julien


-- 
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/20130612175923.gc6...@betterave.cristau.org

Bugs in packages meep-*

2013-06-12 Thread Thorsten Alteholz 

Dear release team,

unfortunately the packages meep-* contain bugs that makes it impossible to 
develop own software with libmeep.
As directory names are wrong, especially users of Live CDs might have 
problems using these packages now (actually I got the initial bug report 
from a user of such a CD).
I attached four debdiffs for packages meep-lam4[1], meep-openmpi[2], 
meep-mpich2[3] and meep-mpi-default[4].


Can you please tell me whether these bugs shall be fixed in Wheezy. In 
case they should, as the versions in sid and wheezy are the same, shall I 
upload the new packages to sid now?


Best regards
Thorsten

[1] meep-lam4: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711767
[2] meep-openmpi: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711766
[3] meep-mpich2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711768
[4] meep-mpi-default: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711765
diff -Nru meep-openmpi-1.1.1/debian/changelog 
meep-openmpi-1.1.1/debian/changelog
--- meep-openmpi-1.1.1/debian/changelog 2011-12-13 10:23:17.0 +0100
+++ meep-openmpi-1.1.1/debian/changelog 2013-06-09 19:12:33.0 +0200
@@ -1,3 +1,10 @@
+meep-openmpi (1.1.1-9) unstable; urgency=low
+
+  * debian/rules: mv /usr/include/meep-openmpi to /usr/include/meep
+  (Closes: #711766)
+
+ -- Thorsten Alteholz deb...@alteholz.de  Sun, 09 Jun 2013 11:00:00 +0200
+
 meep-openmpi (1.1.1-8) unstable; urgency=low
 
   * debian/control: depend on debhelper =8
diff -Nru meep-openmpi-1.1.1/debian/rules meep-openmpi-1.1.1/debian/rules
--- meep-openmpi-1.1.1/debian/rules 2011-12-13 19:48:52.0 +0100
+++ meep-openmpi-1.1.1/debian/rules 2013-06-09 19:13:06.0 +0200
@@ -69,6 +69,7 @@
$(MAKE) -C debian/build-openmpi/ install 
prefix=$(CURDIR)/debian/build-openmpi/tmpinst/usr
/usr/bin/chrpath -d 
debian/build-openmpi/tmpinst/usr/lib/libmeep_openmpi.so
/usr/bin/chrpath -d debian/build-openmpi/tmpinst/usr/bin/meep-openmpi
+   mv debian/build-openmpi/tmpinst/usr/include/meep-openmpi 
debian/build-openmpi/tmpinst/usr/include/meep
dh_install -pmeep-openmpi -p$(lm) -p$(lmd) \
 --sourcedir=debian/build-openmpi/tmpinst
 
diff -Nru meep-mpi-default-1.1.1/debian/changelog 
meep-mpi-default-1.1.1/debian/changelog
--- meep-mpi-default-1.1.1/debian/changelog 2012-06-27 21:30:46.0 
+0200
+++ meep-mpi-default-1.1.1/debian/changelog 2013-06-09 19:03:13.0 
+0200
@@ -1,3 +1,10 @@
+meep-mpi-default (1.1.1-10) unstable; urgency=low
+
+  * debian/rules: mv /usr/include/meep-mpi-default to /usr/include/meep
+  (Closes: #711765)
+
+ -- Thorsten Alteholz deb...@alteholz.de  Sun, 09 Jun 2013 11:00:00 +0200
+
 meep-mpi-default (1.1.1-9) unstable; urgency=low
 
   * debian/control: add more Conflicts: (Closes: #677459, #677462)
diff -Nru meep-mpi-default-1.1.1/debian/rules 
meep-mpi-default-1.1.1/debian/rules
--- meep-mpi-default-1.1.1/debian/rules 2012-06-06 14:52:01.0 +0200
+++ meep-mpi-default-1.1.1/debian/rules 2013-06-09 19:04:01.0 +0200
@@ -72,6 +72,7 @@
$(MAKE) -C debian/build-mpi-default/ install 
prefix=$(CURDIR)/debian/build-mpi-default/tmpinst/usr
/usr/bin/chrpath -d 
debian/build-mpi-default/tmpinst/usr/lib/libmeep_mpi-default.so
/usr/bin/chrpath -d 
debian/build-mpi-default/tmpinst/usr/bin/meep-mpi-default
+   mv debian/build-mpi-default/tmpinst/usr/include/meep-mpi-default 
debian/build-mpi-default/tmpinst/usr/include/meep
dh_install -pmeep-mpi-default -p$(lm) -p$(lmd) \
 --sourcedir=debian/build-mpi-default/tmpinst
 
diff -Nru meep-mpich2-1.1.1/debian/changelog meep-mpich2-1.1.1/debian/changelog
--- meep-mpich2-1.1.1/debian/changelog  2012-06-28 21:51:24.0 +0200
+++ meep-mpich2-1.1.1/debian/changelog  2013-06-09 19:05:22.0 +0200
@@ -1,3 +1,10 @@
+meep-mpich2 (1.1.1-10) unstable; urgency=low
+
+  * debian/rules: mv /usr/include/meep-mpich2 to /usr/include/meep
+  (Closes: #711768)
+
+ -- Thorsten Alteholz deb...@alteholz.de  Sun, 09 Jun 2013 11:00:00 +0200
+
 meep-mpich2 (1.1.1-9) unstable; urgency=low
 
   * debian/control: add more Conflicts:
diff -Nru meep-mpich2-1.1.1/debian/rules meep-mpich2-1.1.1/debian/rules
--- meep-mpich2-1.1.1/debian/rules  2012-06-06 13:05:36.0 +0200
+++ meep-mpich2-1.1.1/debian/rules  2013-06-09 19:06:01.0 +0200
@@ -72,6 +72,7 @@
$(MAKE) -C debian/build-mpich2/ install 
prefix=$(CURDIR)/debian/build-mpich2/tmpinst/usr
/usr/bin/chrpath -d 
debian/build-mpich2/tmpinst/usr/lib/libmeep_mpich2.so
/usr/bin/chrpath -d debian/build-mpich2/tmpinst/usr/bin/meep-mpich2
+   mv debian/build-mpich2/tmpinst/usr/include/meep-mpich2 
debian/build-mpich2/tmpinst/usr/include/meep
dh_install -pmeep-mpich2 -p$(lm) -p$(lmd) \
 --sourcedir=debian/build-mpich2/tmpinst
 
diff -Nru meep-lam4-1.1.1/debian/changelog

Bug#661958: transition: apache2 2.4

2013-06-12 Thread Arno Töll 
Hi,

as requested I propose Ben file patterns for the transition.

For modules, it is easy:

affects: build-depends: apache2-threaded-dev|apache2-prefork-dev
bad: build-depends: apache2-threaded-dev|apache2-prefork-dev
good: build-depends: apache2-dev

or, alternatively:

affects: depends apache2.2-common|apache2.2-bin
bad: depends: apache2-mpm-(prefork|worker|event|itk)| apache2.2-common
good: depends: apache2-api-20120211


For web applications it's much harder to tell. It's not easy to tell
whether they are even affected. We are currently working together with
piuparts maintainer to spot problems at runtime.


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature

d-i, point releases and Built-Using

2013-06-12 Thread Adam D. Barratt 
[tl;dr - can we avoid adding and maintaining a wheezy-r0 suite?]

Hi,

For squeeze, we used the squeeze-r0 suite to ensure that a number of
source packages were retained in the archive for licensing reasons, as
they were used in the builds of other packages. In most cases this has
been replaced by Built-Using for wheezy, and there was much rejoicing.

There's a complication for d-i builds, in the shape of the BYHANDed
images. During stable point releases, we often add a new d-i build
whilst keeping older images available but allowing dak to dominate the
older debian-installer source package away.

As far as I can see, this means that dak will not ensure that packages
used to build the older images are retained. Is there an obvious way of
resolving this which I'm missing, other than adding a wheezy-r0 suite
and populating it with the Built-Using data from the 7.0 and 7.1
installer packages (and their Built-Using, etc)?

Regards,

Adam


-- 
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/1371068190.25701.14.ca...@jacala.jungle.funky-badger.org