Your message dated Thu, 23 Apr 2020 22:06:13 +0200 with message-id <ffb969c6-69c5-a356-e1e7-48079751de8a@debian.org> and subject line Re: nmu: eye_20.0411.2226~ds-2 has caused the Debian Bug report #958561, regarding nmu: eye_20.0411.2226~ds-2 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.) -- 958561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958561 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: eye_20.0411.2226~ds-2
- From: Jonas Smedegaard <dr@jones.dk>
- Date: Thu, 23 Apr 2020 19:45:53 +0200
- Message-id: <[🔎] 158766395368.1253352.11509714704922779875.reportbug@auryn.jones.dk>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: binnmu -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 eye needs same runtime version as used at build-time. A new release of swi-prolog-nox therefore needs a rebuild of eye. nmu eye_20.0411.2226~ds-2 . ANY . unstable . -m "rebuild to pick up swi-prolog-nox" - -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-rc5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6h1FEACgkQLHwxRsGg ASG2tw//TDQe/eSZy028TjF99xMUyLa/thgOlEIP+Rnjvr8lbVI56ihftlPgXA04 m6aJgEtc5fAE/OUWrUel7WJk1VAP/OrCLzA90ZCTKM7WR2ayfLu9jqqxejoP3CfN 64VR8jdyl9A1+5JNpzXwzvcImPDHnn+0/w4A2k83JN4y0aulIQzsic8LskoedwSq l3W9S7aSy9WjhF+al4J5pxPbpKaWZDm7mPpOi1UaCDrZ/X0izcloF3U1CYg36L8O HjeWi0xhSrJTFl+V+7rC5swx+MtvCs5Zm63VLOaeMQY/gSbsxIWrWMHYVbZyjopK xJcufpZb7r3HLZpzAeCOpPQ+W4S+jy1Pa+yvxdHYuSN0v5fcm5fW3BX996yNJGVp nSyG81xhNvWgrkyDQKMxojAjr4ZbUNtP4WoTyA5AZZqzImEWw7M1ScM8zGJInpng asLp6Mm6qbKP8TgrDCt6OwGCu4vYMs2G9X/NBIpOnK2mzRvYn5O65tzpq2S762Nk 0c3vj4XsGbVl4xX1PquX+4tN10LOokXWkzcmPPo+usDTLvfwbUYt+M8WLEniPbjF +iQgQbt0TgK/X9QK+v9M6yM9CEYQLb+QZidN7UfjAVTeSgnbbwrW4e8Za9nlRRUQ wR6j+ttmU5z+Uir6BGzMFWbRnAyrmLsowfvxKkr5XK4ZelFi6Bg= =UBYJ -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: 958561-done@bugs.debian.org, Jonas Smedegaard <dr@jones.dk>
- Subject: Re: nmu: eye_20.0411.2226~ds-2
- From: Andreas Beckmann <anbe@debian.org>
- Date: Thu, 23 Apr 2020 22:06:13 +0200
- Message-id: <ffb969c6-69c5-a356-e1e7-48079751de8a@debian.org>
- In-reply-to: <[🔎] 158766395368.1253352.11509714704922779875.reportbug@auryn.jones.dk>
- References: <[🔎] 158766395368.1253352.11509714704922779875.reportbug@auryn.jones.dk> <[🔎] 158766395368.1253352.11509714704922779875.reportbug@auryn.jones.dk>
On Thu, 23 Apr 2020 19:45:53 +0200 Jonas Smedegaard <dr@jones.dk> wrote: > eye needs same runtime version as used at build-time. > A new release of swi-prolog-nox therefore needs a rebuild of eye. > > nmu eye_20.0411.2226~ds-2 . ANY . unstable . -m "rebuild to pick up swi-prolog-nox" eye is an arch:all package and thus cannot be binNMUed. You'll have to do a no-change source upload to trigger a rebuild. Can you relax the strict (= ${used-for-build}) dependency by a range (>= ${used-for-build}), (<< ${next-upstream-version}) to avoid rebuilding for each new Debian revision (or even each binNMU) of swi-prolog-nox? Andreas PS: for next-upstream-version something like "${current-upstream-version}+~" can be used
--- End Message ---