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.
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?
On 16-05-2024 10:35 a.m., Jonas Smedegaard wrote:
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.
Built-Using is used for license compliance so we HAVE TO have the exact version in the archive. If the version mentioned in the Built-Using
field is no longer in the archive, the package can't be accepted.
On Thu, May 16, 2024 at 4:35 PM Jonas Smedegaard <dr@jones.dk> wrote:
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?
Not a ftp-master, but if you see such a message, it means that your
package has already been accepted, and you can continue uploading
without going through the NEW queue again.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:10:42 |
Calls: | 7,466 |
Calls today: | 2 |
Files: | 12,691 |
Messages: | 5,627,862 |