Your message dated Sat, 06 Apr 2024 13:05:15 +0000
with message-id <e1rt5jp-002ckq...@fasolo.debian.org>
and subject line Bug#1066469: fixed in tack 1.09+20230201-1
has caused the Debian Bug report #1066469,
regarding tack: FTBFS: configure: error: No curses header-files found
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 ow...@bugs.debian.org
immediately.)


-- 
1066469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tack
Version: 1.08-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> configure: WARNING: pkg-config is not installed
> checking for specific curses-directory... no
> checking for specified curses library type... curses
> checking for extra include directories... no
> checking if we have identified curses headers... none
> configure: error: No curses header-files found
>       tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/tack_1.08-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: tack
Source-Version: 1.09+20230201-1
Done: Sven Joachim <svenj...@gmx.de>

We believe that the bug you reported is fixed in the latest version of
tack, 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 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sven Joachim <svenj...@gmx.de> (supplier of updated tack 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 06 Apr 2024 10:03:12 +0200
Source: tack
Architecture: source
Version: 1.09+20230201-1
Distribution: unstable
Urgency: medium
Maintainer: Sven Joachim <svenj...@gmx.de>
Changed-By: Sven Joachim <svenj...@gmx.de>
Closes: 1066469
Changes:
 tack (1.09+20230201-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Bump debhelper from old 10 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Fix field name case in debian/copyright (Upstream-name => Upstream-Name).
   * Use canonical URL in Vcs-Browser.
   * Fix field name case in debian/copyright (Upstream-contact ⇒
     Upstream-Contact).
 .
   [ Sven Joachim ]
   * New upstream snapshot.
     - Fixes FTBFS with -Werror=implicit-function-declaration
       (Closes: #1066469).
   * Update debian/watch to version 4, and look for tarballs on
     https://invisible-mirror.net.
   * Add a debian/watch.snapshot file for checking/downloading snapshots
     with uscan.
   * Update debian/upstream/signing-key.asc.
     - Add new key 19882D92DDA4C400C22C0D56CC2AF4472167BE03.
     - Drop old SHA1 key C52048C0C0748FEE.
   * Build-depend on libncurses-dev rather than on libncurses5-dev.
   * Bump Standards-Version to 4.6.2, no changes needed.
   * Update debian/copyright.
   * Add a debian/salsa-ci.yml file for the Salsa CI pipeline.
     - Disable the arm64 crossbuild job, not supported.
Checksums-Sha1:
 d028b64b5cd326be164bb183e7f93018cd9af659 1998 tack_1.09+20230201-1.dsc
 4373862e3280a90f817498ddcd84ee66c000f6d9 256410 tack_1.09+20230201.orig.tar.gz
 6cc2a703764162214014a8fab8d359d6dcfc3f60 729 tack_1.09+20230201.orig.tar.gz.asc
 69e63664e092bde2f0684b28b5edf9a067896886 6344 
tack_1.09+20230201-1.debian.tar.xz
 896a885e99d3f1392d519bca963846ddc2ea9801 5538 
tack_1.09+20230201-1_source.buildinfo
Checksums-Sha256:
 376ed629089337d8fd2b233e955f84722c8bd7e43f04aa1671196d9cf609c25a 1998 
tack_1.09+20230201-1.dsc
 db68142ccd260f47930c7f5577fad466f0aac7461c183087e9fe364664548081 256410 
tack_1.09+20230201.orig.tar.gz
 70a2993052c5a231a8d6f347bd401f6d3fc761e19ba524ed2eeb3efbe3cf7730 729 
tack_1.09+20230201.orig.tar.gz.asc
 767a496abc886cac187fe329704f40aad83e32df705428356bb9c8e03ae585fa 6344 
tack_1.09+20230201-1.debian.tar.xz
 4fe0d897b09ad90d6799d38344a89680d3fc68c82b7372de2a2f04ff69122ffb 5538 
tack_1.09+20230201-1_source.buildinfo
Files:
 4edf16ad30767d619dd31e3c440a3c63 1998 misc optional tack_1.09+20230201-1.dsc
 060820b6151e8fe9288d9d6ce1927a70 256410 misc optional 
tack_1.09+20230201.orig.tar.gz
 c3ac6d663aec2ffe4a5fd30067108080 729 misc optional 
tack_1.09+20230201.orig.tar.gz.asc
 9c4f8389cde4a1f715f8a6ba3800edc1 6344 misc optional 
tack_1.09+20230201-1.debian.tar.xz
 5efc59e520ba66475d2a0f6c76bfe369 5538 misc optional 
tack_1.09+20230201-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYRQtoQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFC12C/4i9V9/fu1weEOljXYrL9rBM07m3FBvNRUr
7ToUeWwBduOZhBWyF8nQrGo4sU7cSnhEuX63rvhJlY2om1dKBNDEp/KsUScFBOW7
i1NdsdVMGggn+yZ+CuF+5Qkt5j325INcwLRF4qqudMSdht0xSW0AicA+Yadc2zV9
Pk1m3rJmwQBTe7idMrk/vTsu5hiMt1gOmlXOUorR7cUwPysYmMPVEz1P6wLXLMLA
T6WdwFsLT3ykR40zI+ISLE+ESbPDfmUg7sbwGNfRLu/KEtZstY2u7vX+qxtLPw3v
yCqppXAxGgWwccD5ZmRzgJ9K5E96v8UxJpBx8EzYvnW7wQLHXfp+2WsF7OJ6fTVE
ikPFruyU3No7qysvxTcdG7JzNCMKig+RO30+Sg3H7BfwudUMvOaO5u/4nRkr158G
5zImKwBmI9L+/Mg4qMtASMMwmY6FvTD5ZHBdXQBIFL4jK8zKbAwr+YWdCa8IUku9
zbbfhzjPNYpS/CJ9bgFY8z+ceqObPzM=
=TZZk
-----END PGP SIGNATURE-----

Attachment: pgpJ1JGQ1f6Sf.pgp
Description: PGP signature


--- End Message ---

Reply via email to