Your message dated Sat, 28 May 2011 00:46:03 +0930
with message-id <[email protected]>
and subject line Re: Bug#628093: Header files wrongly placed into 
libsofia-sip-ua-dev
has caused the Debian Bug report #628093,
regarding Header files wrongly placed into libsofia-sip-ua-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
628093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628093
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libsofia-sip-ua-dev
Version: 1.12.11+20110422-1
Severity: normal
Tags: patch

The install list for libsofia-sip-ua-dev package collects all installed
header files. However, two of the header files belong to the GLib bindings
and as such should be placed into libsofia-sip-ua-glib-dev. This apparently
was the case before release 1.12.11-1, but the new build rules flattened the
installation. Without a Breaks tag that would accompany a legitimate file
move between packages, an upgrade now fails to replace both of the packages
on e.g. Ubuntu Natty due to file conflicts.
diff -ur sofia-sip-1.12.11+20110422/debian/libsofia-sip-ua-glib-dev.install sofia-sip-1.12.11+20110422.mine/debian/libsofia-sip-ua-glib-dev.install
--- sofia-sip-1.12.11+20110422/debian/libsofia-sip-ua-glib-dev.install	2011-05-27 10:21:09.000000000 +0300
+++ sofia-sip-1.12.11+20110422.mine/debian/libsofia-sip-ua-glib-dev.install	2011-05-26 17:37:37.960345882 +0300
@@ -1,3 +1,5 @@
+usr/include/sofia-sip-*/sofia-sip/su_glib.h
+usr/include/sofia-sip-*/sofia-sip/su_source.h
 usr/lib/libsofia-sip-ua-glib.a
 usr/lib/libsofia-sip-ua-glib.so
 usr/lib/pkgconfig/sofia-sip-ua-glib.pc
diff -ur sofia-sip-1.12.11+20110422/debian/rules sofia-sip-1.12.11+20110422.mine/debian/rules
--- sofia-sip-1.12.11+20110422/debian/rules	2011-05-27 10:21:09.000000000 +0300
+++ sofia-sip-1.12.11+20110422.mine/debian/rules	2011-05-26 18:35:46.957114027 +0300
@@ -81,7 +81,8 @@
 binary-arch: install-arch
 	dh_testdir
 	dh_testroot
-	dh_install --sourcedir=debian/tmp
+	dh_install --sourcedir=debian/tmp --no-package=libsofia-sip-ua-glib-dev -Xsu_glib.h -Xsu_source.h
+	dh_install --sourcedir=debian/tmp --remaining-packages
 	dh_installdocs
 	dh_installchangelogs
 	dh_strip

--- End Message ---
--- Begin Message ---
On Fri, May 27, 2011 at 10:36:49AM +0300, Mikhail Zabaluev wrote:
> Package: libsofia-sip-ua-dev
> Version: 1.12.11+20110422-1
> Severity: normal
> Tags: patch
> 
> The install list for libsofia-sip-ua-dev package collects all installed
> header files. However, two of the header files belong to the GLib bindings
> and as such should be placed into libsofia-sip-ua-glib-dev.

Why?  Nothing about those headers forces any extra dependencies upon the
package they are in, and not making arbitrary special cases greatly
simplifies the packaging, and automatically avoids bugs like #595526.

> This apparently was the case before release 1.12.11-1, but the new build
> rules flattened the installation.

Yes, it did.  And that was not a mistake, and moving these headers was not
an oversight.  It fixed an existing bug with missing headers, and gives us
the best assurance such bugs won't be repeated.

I'm half tempted to get rid of the -glib package altogether, given that it
barely pays for its own overhead in any case.  For now though, I'm happy
enough to still pretend there may be some benefit to some really tight
embedded system, but we'll see.  That only applies to the runtime packages
which are still cleanly separate.

> Without a Breaks tag that would accompany a legitimate file
> move between packages, an upgrade now fails to replace both of the packages
> on e.g. Ubuntu Natty due to file conflicts.

Upgrading squeeze -> wheezy works for me.

  Ron




--- End Message ---

Reply via email to