From: owner@bugs.debian.org (Debian Bug Tracking System)
To: Benjamin Drung <benjamin.drung@profitbricks.com>
Cc: pkg-ofed-devel@lists.alioth.debian.org, linux-rdma@vger.kernel.org
Subject: Processed: Re: Processed: libibverbs-dev no longer ships infiniband/driver.h
Date: Thu, 16 Nov 2017 12:45:09 +0000 [thread overview]
Message-ID: <handler.s.C.151083616125033.transcript@bugs.debian.org> (raw)
In-Reply-To: 1510836156.4026.96.camel@profitbricks.com
Processing commands for control@bugs.debian.org:
> reassign 881814 src:libfabric 1.4.0-1
Bug #881814 [src:rdma-core] libibverbs-dev no longer ships infiniband/driver.h
Bug reassigned from package 'src:rdma-core' to 'src:libfabric'.
No longer marked as found in versions rdma-core/15-1.
Ignoring request to alter fixed versions of bug #881814 to the same values previously set
Bug #881814 [src:libfabric] libibverbs-dev no longer ships infiniband/driver.h
Marked as found in versions libfabric/1.4.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
881814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881814
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
prev parent reply other threads:[~2017-11-16 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151075140461.17370.2844187627354872362.reportbug@localhost>
2017-11-15 13:12 ` Processed: libibverbs-dev no longer ships infiniband/driver.h Debian Bug Tracking System
[not found] ` <handler.s.B.15107514116787.transcript-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org>
2017-11-15 17:16 ` Jason Gunthorpe
[not found] ` <20171115171657.GQ25894-uk2M96/98Pc@public.gmane.org>
2017-11-16 12:42 ` Bug#881814: " Benjamin Drung
2017-11-16 12:45 ` Debian Bug Tracking System [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=handler.s.C.151083616125033.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=benjamin.drung@profitbricks.com \
--cc=linux-rdma@vger.kernel.org \
--cc=pkg-ofed-devel@lists.alioth.debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.