[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#901578: opa-basic-tools



Hi Brian,

Sorry for not replying sooner.

On 2018-11-09 22:22, Brian Smith wrote:
Hi debian-hpc people,

On Thu, Nov 8, 2018 at 3:18 PM Brian Smith <bsmith@systemfabricworks.com> wrote:

> This is not the case with other Linux flavors, such as RHEL. Perhaps there is a
> rules.d file that is missing?

For clarification, this statement was made regarding the
opa-basic-tools package delivered by Intel's IFS distribution for
RHEL.

RHEL's in-box opa-basic-tools exhibits the same behavior described by this bug.

Does anyone have thoughts on this bug? It blocks opa-ff from migrating
to testing.

Similarly to how other network interfaces are managed, I do not think it is desirable to give regular users ability to manage opa network interfaces. It
is up to the system administrator to fine-tune that if he wishes so.

I agree with your conclusion in the bugreport.

I have a minor remark about handling such bugreports in Debian's BTS (and there is nothing intuitive about this): Since there is no bug in the package and no fix was integrated, the bug should not be marked as fixed in -2. BTS's way to handle
such cases is to:
1) mark this bugreport as "not found" in version opa-ff/10.7.0.0.133+dfsg.1-1
2) tag it "wontfix"
3) close the bugreport, with an explanation.

#901578 is only missing step 1 (modulo removing the annotation about the newer
version, i.e. -2).

Cheers,

--
Mehdi


Reply to: