Bug#827964: marked as done (nmu: vim-command-t_4.0-1)
Your message dated Fri, 24 Jun 2016 11:50:39 +0200
with message-id <b6e7b472-d02d-4fad-6205-e1af0636ed37@debian.org>
and subject line Re: Bug#827964: nmu: vim-command-t_4.0-1
has caused the Debian Bug report #827964,
regarding nmu: vim-command-t_4.0-1
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 owner@bugs.debian.org
immediately.)
--
827964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827964
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
vim-command-t has stricter dependency requirements on the version of
ruby under which it runs than specified in libruby2.3's shlibs/symbols
files. As a result the package does not function when used with vim in
unstable.
Please rebuild vim-command-t against the latest ruby2.3-dev.
nmu vim-command-t_4.0-1 . ANY . unstable . -m "Rebuild against current ruby2.3-dev"
- -- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (555, 'testing'), (520, 'unstable'), (510, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJXa8SGAAoJENILQgJc2ie5y3EQAKQVTTHiWPVomzokYDbH0aXN
YhXxh4IUsdOuJNbjcIVC01INLo16E1Glc4y5aIF7uQ1W2WqZkoVlH+2kcdNhnKfm
HINg2een7nEDtSHTPEyoZnWtvQZVmGI2G22k1meL70h5P0YkCt7rRd3A7t0mXYmX
fzT21lNDytbP8qIW108ciMgcWALWojxLSwhOuR9IuyJoZby7ITl1QCVDDO4P4cRB
t0YZlc0dQ2SEl3F9CLTDdNB1muDY3Nb/91O8CLuem2Hxv3n32w6/MMH9Ek3PtYAS
Rza5bgN15wGESrBP79JwIU38tKb03NqQ99oLLSZ2uTjKpDPYFl+fGpCfAAcXkY46
a3S1Z0/DH0HshwYrMWHx35lZE13rqoUzoW6vpxtA1p7PX/g8rhZeHhcch72PT58U
5Hw3MK2AqmyEyZSzGDuatgW9SKUydHeJFK63yfDskg8VXwCXIbmdAG85OFlZiQ5f
KmqCaRQOcw1W5ix/YpcmB2qi+egckRhT1Yl4x93wgkClQypBJEd8NspAA6elHZbR
f3lRYlt7caGqzmutJItiJvBp21IIlkufqtWELzeDBwFn0976YmUDT1AZWDBLvFu9
rf+8Dqy2N0llmd6EThLDuOQcLk/GYppLP5SsuxYcsdXHXAP/LrQewAnCEx9CuTke
ZSMwso3Able1bmYwXB1t
=VgfY
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 23/06/16 17:44, Sam Morris wrote:
> On Thu, 2016-06-23 at 16:50 +0200, Emilio Pozuelo Monfort wrote:
>> On 23/06/16 13:14, Sam Morris wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: binnmu
>>>
>>> Hello,
>>>
>>> vim-command-t has stricter dependency requirements on the version
>>> of
>>> ruby under which it runs than specified in libruby2.3's
>>> shlibs/symbols
>>> files. As a result the package does not function when used with vim
>>> in
>>> unstable.
>>
>> Maybe it should have a stricter dependency? This sounds like a bug in
>> the
>> package (dependencies).
>>
>> Cheers,
>> Emilio
>
> Yes, in the next version I upload I have tightened the dependency on
> libruby2.3. But I'm waiting for a sponsor to upload that; in the
> meantime, a rebuild will fix the package in unstable.
Let's not workaround this with a binNMU.
Cheers,
Emilio
--- End Message ---
Reply to: