Your message dated Tue, 4 Oct 2016 09:28:29 +0200
with message-id <[email protected]>
and subject line Re: Bug#839240: saga: Should have a stricter dependency
between saga and libsaga
has caused the Debian Bug report #839240,
regarding saga: Should have a stricter dependency between saga and libsaga
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.)
--
839240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839240
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: saga
Version: 2.3.1+dfsg-2
Severity: normal
Hi!
About https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838915#25 I saw
that I had saga at version 2.3.1+dfsg-2 and libsaga-* at version
2.3.1+dfsg-1+b1
The dependency was properly satisfied when saga was pulled from unstable
(it depends on libsaga-api-2.3.1 only, for example, instead on a
possibly stricter libsaga-api-2.3.1 (= 2.3.1+dfsg-2))
Shouldn't we have this dependency versioned?
Thank you very much!
Best regards,
Nelson
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (200, 'unstable'),
(100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--- End Message ---
--- Begin Message ---
notfound 839240 saga/2.3.1+dfsg-2
thanks
On 09/30/2016 06:35 PM, Nelson A. de Oliveira wrote:
> Em 30 de set de 2016 12:13 PM, "Sebastiaan Couwenberg" escreveu:
>>
>> Why weren't the libsaga-* packages upgraded along with saga? You have
>> gotten version 2.3.1+dfsg-2 for all of the saga packages.
>
> It was a simple "apt -t unstable install saga"
>
> I usually trust that all the necessary dependencies will be updated
> together (ie, I don't manually verify that every library was also updated)
You cannot rely on inter-package dependencies to pull in the new
revision of the shared libraries it uses. Most packages use symbols
files for their shared libraries which only depend on the upstream
version of the library package.
When you upgrade a package by installing a binary packages instead of
using `apt-get upgrade` you need to ensure that you install all affected
binary packages.
I'm closing this issue since it's not a bug in saga.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
