From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] what's going on with updates ?
Date: Mon, 13 Sep 2010 14:02:01 -0500 [thread overview]
Message-ID: <AANLkTinQaT51ZU5QhLGRFacuqRz0UUj1vOigDHuEBXgW@mail.gmail.com> (raw)
In-Reply-To: <201009130815.23751.stephane@22decembre.eu>
On Mon, Sep 13, 2010 at 1:15 AM, Stéphane Guedon <stephane@22decembre.eu> wrote:
> Since few days ( two or three ?), every time I launch emerge, it's saying me
> it needs an update of portage itself.
> In plus, I have upgraded udev at least two times (160>161>162 today)...
>
> Plus, I have had two warning message concerning updates : sudo and an other...
>
> what's going on ? Is somebody founding security holes "à la pelle" (french
> expression).
From Changelog you can see, lots of bugs fixed in portage 2.1 in the
last few days:
*portage-2.1.9.1 (06 Sep 2010)
06 Sep 2010; Zac Medico <zmedico@gentoo.org> +portage-2.1.9.1.ebuild:
2.1.9.1 version bump. This fixes bug #336019 (show ebuild maintainer in
build log), bug #336085 (AttributeError triggered by slot conflict), and
bug #336285 (add unpack() workaround for interactive unzip). Bug #335925
tracks all bugs fixed since 2.1.8.x.
*portage-2.1.9.2 (08 Sep 2010)
08 Sep 2010; Zac Medico <zmedico@gentoo.org> +portage-2.1.9.2.ebuild:
2.1.9.2 version bump. This fixes bug #332719 (depclean removes newly
installed packages), bug #336338 (document FEATURES=candy), bug #336349
(warn about dos-style line endings in make.conf), bug #336350
(AttributeError for selinux), and bug #336356 (AttributeError when
running test phase with ebuild command). Bug #335925 tracks all bugs
fixed since 2.1.8.x.
*portage-2.1.9.3 (10 Sep 2010)
10 Sep 2010; Zac Medico <zmedico@gentoo.org> +portage-2.1.9.3.ebuild:
2.1.9.3 version bump. This fixes bug #267103 (warn about unapplied config
updates in /etc/portage), bug #273282 (QA warning about install in
deprecated directories), bug #336499 (call pkg_nofetch for misc fetch
failures), bug #336503 (FEATURES=usersync tempdir permission issues),
bug #336595 (--quiet support for "global updates"), bug #336644 (IOError
[Errno 11] issues with tmpfs), and bug #336651 (fix resume after portage
update to work with --exclude). Bug #335925 tracks all bugs fixed since
2.1.8.x.
*portage-2.1.9.4 (11 Sep 2010)
11 Sep 2010; Zac Medico <zmedico@gentoo.org> +portage-2.1.9.4.ebuild:
2.1.9.4 version bump. This fixes bug #336692 (make package.mask negation
in profiles PMS compliant and issue warnings) and also fixes subtle bugs
in pkg_nofetch support. Bug #335925 tracks all bugs fixed since 2.1.8.x.
*portage-2.1.9.5 (13 Sep 2010)
13 Sep 2010; Zac Medico <zmedico@gentoo.org> +portage-2.1.9.5.ebuild:
2.1.9.5 version bump. This fixes bug #336142 (ebuild-ipc timeout is
too short), bug #336875 (ETIME ImportError on FreeBSD), and bug #337031
(make "always overflow destination buffers" gcc warnings non-fatal).
Bug #335925 tracks all bugs fixed since 2.1.8.x.
next prev parent reply other threads:[~2010-09-13 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 6:15 [gentoo-user] what's going on with updates ? Stéphane Guedon
2010-09-13 11:07 ` Albert Hopkins
2010-09-13 18:00 ` Dale
2010-09-13 18:06 ` [gentoo-user] " Nikos Chantziaras
2010-09-13 19:02 ` Paul Hartman [this message]
2010-09-14 17:46 ` [gentoo-user] " Matthias Schwarzott
-- strict thread matches above, loose matches on Subject: below --
2010-09-14 6:00 Stéphane Guedon
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=AANLkTinQaT51ZU5QhLGRFacuqRz0UUj1vOigDHuEBXgW@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@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