[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#787609: marked as done (tucnak: fails to install: update-alternatives: <link> and <path> can't be the same)

Your message dated Fri, 12 Jun 2015 10:27:07 +0000
with message-id <E1Z3MB1-0006Uh-PA@franck.debian.org>
and subject line Bug#787609: fixed in tucnak 4.03-2
has caused the Debian Bug report #787609,
regarding tucnak: fails to install: update-alternatives: <link> and <path> can't be the same
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.)


-- 
787609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787609
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tucnak
Version: 4.03-1
Severity: serious
User: debian-qa@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up tucnak (4.03-1) ...
  update-alternatives: <link> and <path> can't be the same
  
  Use 'update-alternatives --help' for program usage information.
  dpkg: error processing package tucnak (--configure):
   subprocess installed post-installation script returned error exit status 2
  Processing triggers for libc-bin (2.19-18) ...
  Processing triggers for systemd (215-18) ...
  Errors were encountered while processing:
   tucnak


cheers,

Andreas

Attachment: tucnak_4.03-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message --- 
Source: tucnak
Source-Version: 4.03-2

We believe that the bug you reported is fixed in the latest version of
tucnak, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 787609@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Tuckley <colint@debian.org> (supplier of updated tucnak package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 12 Jun 2015 09:22:50 +0100
Source: tucnak
Binary: tucnak
Architecture: source amd64
Version: 4.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Colin Tuckley <colint@debian.org>
Description:
 tucnak     - VHF/UHF/SHF Hamradio contest logging program
Closes: 787609
Changes:
 tucnak (4.03-2) unstable; urgency=medium
 .
   * Remove use of 'update-alternatives' (Closes: #787609)
Checksums-Sha1:
 a6388b1b24bf0ff1965debb75a207b466caec4ac 1937 tucnak_4.03-2.dsc
 4d55b75fbaeabdfb2e0a4a138095a67f52a35240 13152 tucnak_4.03-2.debian.tar.xz
 24c2a954392206de6d91c0eb78d84436245571cc 1256446 tucnak_4.03-2_amd64.deb
Checksums-Sha256:
 9fe5a69d7bc3fc29281f1acabe0df2a743b7aee0be0131594e2bc64a3446c6f7 1937 tucnak_4.03-2.dsc
 b2125c7355a12f050f29525fc8cce40a4b7f2f56ea77ae45e6146b1d7eade220 13152 tucnak_4.03-2.debian.tar.xz
 53ffb8d57cbb21763a08fab3c94a4acdccbb47f873b4474825d6a9d1058c5857 1256446 tucnak_4.03-2_amd64.deb
Files:
 56cdc7668d5ef9f483c74f3561000d09 1937 hamradio optional tucnak_4.03-2.dsc
 de4fa6dff38e8973ed62e9688b4b3a13 13152 hamradio optional tucnak_4.03-2.debian.tar.xz
 7559ae28ee3c2ca7cd5ee8dbad4a7a34 1256446 hamradio optional tucnak_4.03-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVepnbAAoJEPoMQQc4ydkDVRsQAKKbZvytmP5uaP8yG+2GZL2W
gfUPMUbqtsX1cjKYmJFyyluTHMgh1wSmfMAH5bsmdkaqF6H/dljMACpmxESfim6M
EinsGDdwN5grd44UhTTcmzVXOPmHj4XwSgk/ENTtvk+sajczH38BKpbddHPhFlDz
y/iMrXiRjcdGnaAQzEKEqM2E9Y9lKQNoRTg6CPY6zrPo6WMwExbvpVwvvco/9SgF
Og0zqM75838F6/XbMLetgXlF8qxj/kc30ILwDuxF+ip6rxllwYTJ+JjpxYpZbxIb
WDYRswOAI/asS3FlC6CWdUtNUkUqp/xEyC+I7TfDeo94XfIepZlNTN5QVIeWwYOS
jcXh3rkxc1wSc+tg085qDMTqOlSCMFoquTnd8iGW43S6m9SAwWXwB5tZcom34moN
FqYbruFRhNRz5nBr1K13+2TeyW4FWkczgnakiq0EAkHFOnWLr8w8Tm4LjGXU4Vgn
XOdaQhJFWMciB/XKicx+mxnvZPBn546c3rxR2kHBvSCqwx/s07h8hCU6+ewAew6t
aY1Y9VyIQ8yAPCP3Oai317tiKCkLJ5D9M/AeDGEeqthxXqLz5rNwqfd3SzV+nLTe
ZOiPUeCYq8hfmVowUtPuF3CieOtkph8cg9s4P6SpdwE5OEryeeA8wO1CL9Xf47MS
7tSgUPmj9O4j3sYcmO2D
=MzXb
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: