Your message dated Tue, 23 May 2023 15:47:07 +0200 with message-id <7502d771-b071-5fe4-f74b-de7c08916f6f@debian.org> and subject line Re: Bug#1036047: unblock: nlopt/2.7.1-5 has caused the Debian Bug report #1036047, regarding unblock: nlopt/2.7.1-5 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.) -- 1036047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036047 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: nlopt/2.7.1-5
- From: Nilesh Patra <nilesh@debian.org>
- Date: Sun, 14 May 2023 16:29:55 +0530
- Message-id: <[🔎] 168406199532.69662.13062189625251203715.reportbug@debian>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock X-Debbugs-Cc: nlopt@packages.debian.org Control: affects -1 + src:nlopt Please unblock package nlopt [ Reason ] This upload was done due to address a piuparts error while upgrading nlopt from bullseye -> bookworm, see #1035629. [ Impact ] Loss of files in usr/share/doc/libnlopt0 maybe observed, and over-writing files too, which is not desired. [ Tests ] Manual tests done locally by upgrading from version in bullseye to bookworm, and then removing packages individually, and inspected the contents of the doc directories -- did not see any surprises. [ Risks ] As the upload touches only the doc section only, the package is un-affected in terms of it's core (library) functionality. No big risks. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock nlopt/2.7.1-5diff -Nru nlopt-2.7.1/debian/changelog nlopt-2.7.1/debian/changelog --- nlopt-2.7.1/debian/changelog 2022-04-14 15:10:53.000000000 +0000 +++ nlopt-2.7.1/debian/changelog 2023-05-14 09:35:20.000000000 +0000 @@ -1,3 +1,13 @@ +nlopt (2.7.1-5) unstable; urgency=medium + + * Team Upload. + * Add maintscript to convert libnlopt-dev doc + symlink to directory (Closes: #1035629) + * Add a preinst to remove examples directory in libnlopt0 + which should be present in -dev only + + -- Nilesh Patra <nilesh@debian.org> Sun, 14 May 2023 09:35:20 +0000 + nlopt (2.7.1-4) unstable; urgency=medium * Team upload diff -Nru nlopt-2.7.1/debian/libnlopt0.preinst nlopt-2.7.1/debian/libnlopt0.preinst --- nlopt-2.7.1/debian/libnlopt0.preinst 1970-01-01 00:00:00.000000000 +0000 +++ nlopt-2.7.1/debian/libnlopt0.preinst 2023-05-14 09:35:20.000000000 +0000 @@ -0,0 +1,6 @@ +#!/bin/sh -e +# directory moved to -dev package, the symlink from past upgrade should be removed +if [ -d /usr/share/doc/libnlopt0/examples ]; then + rm -rf /usr/share/doc/libnlopt0/examples +fi +#DEBHELPER# diff -Nru nlopt-2.7.1/debian/libnlopt-dev.maintscript nlopt-2.7.1/debian/libnlopt-dev.maintscript --- nlopt-2.7.1/debian/libnlopt-dev.maintscript 1970-01-01 00:00:00.000000000 +0000 +++ nlopt-2.7.1/debian/libnlopt-dev.maintscript 2023-05-14 09:35:20.000000000 +0000 @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/libnlopt-dev libnlopt0 2.7.1-5~
--- End Message ---
--- Begin Message ---
- To: Nilesh Patra <nilesh@debian.org>, 1036047-done@bugs.debian.org
- Subject: Re: Bug#1036047: unblock: nlopt/2.7.1-5
- From: Paul Gevers <elbrus@debian.org>
- Date: Tue, 23 May 2023 15:47:07 +0200
- Message-id: <7502d771-b071-5fe4-f74b-de7c08916f6f@debian.org>
- In-reply-to: <[🔎] 168406199532.69662.13062189625251203715.reportbug@debian>
- References: <[🔎] 168406199532.69662.13062189625251203715.reportbug@debian>
Hi, On 14-05-2023 12:59, Nilesh Patra wrote:unblock nlopt/2.7.1-5done and aged. PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---