Re: pandoc-filter-diagram_0.2.1-1_amd64.changes REJECTED

[Jonas Smedegaard <dr@jones.dk>]

Hi FTP-masters (cc d-devel list),

A package, that I had initially introduced to Debian some months ago and
had been pending in NEW queue since, was rejected few days ago, like
this:

Quoting Debian FTP Masters (2024-05-14 12:00:12)
> 
> An exception was raised while processing the package:
> Traceback (most recent call last):
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 121, in wrapper
>     function(upload, srcqueue, comments, transaction)
>   File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 248, in comment_accept
>     transaction.copy_binary(
>   File "/srv/ftp-master.debian.org/dak/daklib/archive.py", line 390, in copy_binary
>     self._ensure_extra_source_exists(filename, db_source, archive, extra_archives=extra_archives)
>   File "/srv/ftp-master.debian.org/dak/daklib/archive.py", line 214, in _ensure_extra_source_exists
>     raise ArchiveException('{0}: Built-Using refers to package {1} (= {2}) not in target archive {3}.'.format(filename, source.source, source.version, archive.archive_name))
> daklib.archive.ArchiveException: p/pandoc-filter-diagram/pandoc-filter-diagram_0.2.1-1_amd64.deb: Built-Using refers to package rust-ahash (= 0.8.9-2) not in target archive ftp-master.

I it correct to derive from the above, that packages in NEW queue must
be freshly built, and that I (and we, generally) therefore should
routinely rebuild packages pending in NEW queue to ensure that they are
acceptably?

Just to clarify, the package in question does not directly depend on
rust-ahash 0.8.9-2, that Built-Using information is (as is the general
purpose of that field, I believe) transitive.

Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature