From: "Diego Elio Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/wireshark: wireshark-1.6.2.ebuild ChangeLog wireshark-1.4.9.ebuild wireshark-1.4.7.ebuild wireshark-1.6.0_rc1.ebuild wireshark-1.4.4.ebuild wireshark-1.4.6-r1.ebuild
Date: Tue, 13 Sep 2011 11:23:18 +0200 [thread overview]
Message-ID: <1315905798.4408.7.camel@raven.home.flameeyes.eu> (raw)
In-Reply-To: <4E6F1778.2090506@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Il giorno mar, 13/09/2011 alle 11.42 +0300, Markos Chandras ha scritto:
>
> Why is wireshark blocking itself on DEPEND? is this a known bug that
> prevents normal update from old to new version? It is a bit odd to
> have to remove the existing installation in order to update to a new
> one
AFAICT it might be related to the fact that wireshark tends to link to
its own installed libraries when being rebuilt. Yes that means that its
build system is tfu.
--
Diego Elio Pettenò — Flameeyes
http://blog.flameeyes.eu/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-09-13 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110912185552.543242004C@flycatcher.gentoo.org>
2011-09-13 8:42 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/wireshark: wireshark-1.6.2.ebuild ChangeLog wireshark-1.4.9.ebuild wireshark-1.4.7.ebuild wireshark-1.6.0_rc1.ebuild wireshark-1.4.4.ebuild wireshark-1.4.6-r1.ebuild Markos Chandras
2011-09-13 9:23 ` Diego Elio Pettenò [this message]
2011-09-13 9:28 ` Ciaran McCreesh
2011-09-13 9:53 ` [gentoo-dev] " Diego Elio Pettenò
2011-09-13 10:24 ` Ciaran McCreesh
2011-09-13 13:58 ` Mike Frysinger
2011-09-14 5:17 ` Ciaran McCreesh
2011-09-13 13:59 ` Mike Frysinger
2011-10-11 5:31 ` Peter Volkov
2011-09-13 9:46 ` [gentoo-dev] " Tomáš Chvátal
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=1315905798.4408.7.camel@raven.home.flameeyes.eu \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox