From: "Tomáš Chvátal" <scarabeus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [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:46:16 +0200 [thread overview]
Message-ID: <CA+Nrkpe6_6_V-+MSsDsoS6P4m6Q93RqQO+5cCrOOv9kMynJ_zg@mail.gmail.com> (raw)
In-Reply-To: <4E6F1778.2090506@gentoo.org>
2011/9/13 Markos Chandras <hwoarang@gentoo.org>:
> On 12/09/2011 09:55 μμ, Peter Volkov (pva) wrote:
>> pva 11/09/12 18:55:52
>>
>> Modified: ChangeLog Added:
>> wireshark-1.6.2.ebuild wireshark-1.4.9.ebuild Removed:
>> wireshark-1.4.7.ebuild wireshark-1.6.0_rc1.ebuild
>> wireshark-1.4.4.ebuild wireshark-1.4.6-r1.ebuild Log: Version bump.
>> Fixes security bug #381551, thank GLSAMaker/CVETool Bot. Added
>> 1.6.2, bug #370683. 1.6.2 also fixes bug 373545 wrt Francesco
>> Lamonica. Drop old.
>>
>> ... !!<net-analyzer/wireshark-1.6.0_rc1"
>
> 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
>
> - --
> Regards,
> Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
Actually this s**t happens a lot,
due to broken build system the package links to the already in-system
packages and use headers from system.
So one has to block the major versions to avoid the breakages during the build
Cheers
Tom
prev parent reply other threads:[~2011-09-13 9:47 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ò
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 ` Tomáš Chvátal [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=CA+Nrkpe6_6_V-+MSsDsoS6P4m6Q93RqQO+5cCrOOv9kMynJ_zg@mail.gmail.com \
--to=scarabeus@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