Your message dated Tue, 20 Jun 2017 17:34:02 +0200
with message-id <[email protected]>
and subject line Closing resolved bug
has caused the Debian Bug report #832187,
regarding astropy-utils: Section should not be “python”
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 [email protected]
immediately.)
--
832187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: astropy-utils
Version: 1.2.1-1
Severity: minor
Dear Maintainer,
The section “python” is for packages that install the Python
programming language or libraries. Its packages are primarily of
interest only to Python programmers.
The package ‘astropy-utils’ installs primarily some applications, of
interest regardless of the programming language. It should not be in
the “python” section.
By the section descriptions, this package may belong in section
“science”.
Please set the field “Section” appropriately on this package.
Since the package is already in Debian with a different section, you
will also need to submit a request to override the existing section
<URL:https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#override-file>.
Then mark this bug report as blocked by that new one, and be sure not
to close this one until that new one is completed.
--
\ “Firmness in decision is often merely a form of stupidity. It |
`\ indicates an inability to think the same thing out twice.” |
_o__) —Henry L. Mencken |
Ben Finney <[email protected]>
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Since the override bug is done since a few months, I am closing this one
as well.
@Ben: I am however wondering why you did not issue the override bug
yourself (and put the maintainer into Cc:)? It was already changed in
d/control since ages.
Writing a bug "please write another bug, wait until it is closed, and
then close this bug" seems to me a quite useless overhead.
Best regards
Ole
--- End Message ---
