From: owner@bugs.debian.org (Debian Bug Tracking System)
To: Michael Biebl <biebl@debian.org>
Cc: linux-xfs@vger.kernel.org
Subject: Processed: forcibly merging 766811 857932 854961
Date: Thu, 16 Mar 2017 16:06:14 +0000 [thread overview]
Message-ID: <handler.s.C.148968027111476.transcript@bugs.debian.org> (raw)
In-Reply-To: 1489680268-1682-bts-biebl@debian.org
Processing commands for control@bugs.debian.org:
> forcemerge 766811 857932 854961
Bug #766811 [xfslibs-dev] spurious library links
Bug #766811 [xfslibs-dev] spurious library links
Marked as found in versions xfsprogs/4.9.0.
Added tag(s) sid and stretch.
Bug #854961 [xfslibs-dev] xfslibs-dev won't install in Docker image (where /lib -> /usr/lib)
Severity set to 'normal' from 'important'
Marked as fixed in versions xfsprogs/4.3.0+nmu1.
Marked as found in versions xfsprogs/4.3.0 and xfsprogs/3.2.1.
Added tag(s) sid and stretch.
Bug #857932 [xfslibs-dev] xfslibs-dev:ppc64el Fails to install on multi-arch setup with merged /usr
Marked as fixed in versions xfsprogs/4.3.0+nmu1.
Marked as found in versions xfsprogs/4.3.0, xfsprogs/4.9.0, and xfsprogs/3.2.1.
Merged 766811 854961 857932
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
766811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766811
854961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854961
857932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857932
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
parent reply other threads:[~2017-03-16 16:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1489680268-1682-bts-biebl@debian.org>]
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.148968027111476.transcript@bugs.debian.org \
--to=owner@bugs.debian.org \
--cc=biebl@debian.org \
--cc=linux-xfs@vger.kernel.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.