Your message dated Fri, 18 Nov 2016 14:22:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#844725: libproj12 should conflict with libproj9
has caused the Debian Bug report #844725,
regarding libproj12 should conflict with libproj9
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.)
--
844725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844725
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: proj
Version 4.9.3-1
Severity: Serious
Justification: breaks unrelated software when both libraries are installed.
Hi, as said, it took me two days to debug to understand this failure
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/m/mipp/20161118_053933_5e50e@/log.gz
the python binding fails and segfaults when both libproj9 and libproj12 are
installed
(Reading database ... 65663 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [05:39:15]: test python2: [-----------------------
=== python2.7 ===
test_tsx (test_xsar.Test) ... Segmentation fault (core dumped)
autopkgtest [05:39:23]: test python2: -----------------------]
autopkgtest [05:39:23]: test python2: - - - - - - - - - - results - - - - - -
- - - -
python2 FAIL non-zero exit status 139
autopkgtest [05:39:23]: @@@@@@@@@@@@@@@@@@@@ summary
python2 FAIL non-zero exit status 139
a no-change rebuild of mipp with both runtime libraries installed triggers the
failure.
Since you can't force people from autoremoving the old libraries, I think this
is an RC bug, and some sort
of conflict with previous version should be added to prevent such segfaults
from happening.
thanks for understanding,
Gianfranco
--- End Message ---
--- Begin Message ---
severity 844725 wishlist
tags 844725 wontfix
thanks
Hi Gianfranco,
Sorry to hear you wasted your time. Thank for caring about packages in
universe though, too few people in Ubuntu do.
On 11/18/2016 01:59 PM, Gianfranco Costamagna wrote:
> Hi, as said, it took me two days to debug to understand this failure
> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/m/mipp/20161118_053933_5e50e@/log.gz
>
> the python binding fails and segfaults when both libproj9 and libproj12 are
> installed
>
> [...]
>
> a no-change rebuild of mipp with both runtime libraries installed triggers
> the failure.
>
> Since you can't force people from autoremoving the old libraries, I think
> this is an RC bug, and some sort
> of conflict with previous version should be added to prevent such segfaults
> from happening.
Transitions ensure that all reverse dependencies are updated for the new
library thereby making it obsolete and easy to remove with `apt-get
autoremove`. By having all rdeps depend on the new library package, the
old one should no longer be installed via (build) dependencies.
The failure in Ubuntu to do a proj transition does not warrant an RC bug
in Debian. Conflicts are not appropriate because libproj9 and libproj12
do not contain the same files.
The fix for this issue is to do a proj transition in Ubuntu as we've
done in Debian. If Ubuntu does not have the manpower to do transitions
for packages in universe, they should consider removing those packages
to acknowledge their lack of maintenance in Ubuntu. Removal of packages
Ubuntu users rely on should motivate them to become involved in their
maintenance in a similar fashion as removal from testing in Debian.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
