From: Nicol TAO <nicol_tao@126.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] How to fully mask gnome-3.18 upgrade
Date: Wed, 2 Mar 2016 14:58:26 +0800 [thread overview]
Message-ID: <56D68F12.60404@126.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello, all.
Several days before, I upgrade my gnome-3.16 to version gnome-3.18,
and the desktop crash frequently. Then I downgrade my gnome to version
3.16 and everything goes fine.
I want to ask how to mask the upgrades of gnome-3.18. I really want to
find gnome 3.16 profile as kde4 and kde5 case, but none.
I followed and add the mask items copied from
https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/package.mask?id=
caaec004d31dee515d64cd310f1e38fd55bab43f
But when I run emerge -auDN world, the gnome upgrades comes again!
- --
Nicol TAO (taozhijiang)
http://freesign.net
GPG: A251 3E22 BE65 E709 B1DD 5BE5 D2D3 FB76 C0CC 5261
Thanks & Best Regards!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCAAGBQJW1o8SAAoJENLT+3bAzFJhDfsIAI1xDClhy6MI6+WeWocCg36q
NpZsF0oIH42JhwnjfgDE+/V+E8EaA7JPyV96UJz3/7uJu7JpKTY6vsPwQIvcMDZW
rms8TAQdFP4sYKsmwvnc9RCCtchqq7g/N5KHpQMncQ2sBXL7CVZqa6JvmtssQw/T
R0nwJ0qePUURB3CV+z9hxuddCivANvoYLcpZUrVLIpi2i5cYT/qoIA9xN+beE7eH
fcfZLvqPK94TFvo0KJDBkwFMymht4fAXVr0Hl1esTg8yKJcWtKHRfBBjcvep1Lfh
ZmeS1DCBApWEaA97MFZsN0mpYT1zGwLdHhl1p/qH6gNeZiiiiPNbMAShXOfzqk4=
=VgAb
-----END PGP SIGNATURE-----
[-- Attachment #2: 0xC0CC5261.asc --]
[-- Type: application/pgp-keys, Size: 1727 bytes --]
[-- Attachment #3: 0xC0CC5261.asc.sig --]
[-- Type: application/pgp-signature, Size: 287 bytes --]
next reply other threads:[~2016-03-02 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 6:58 Nicol TAO [this message]
2016-03-03 5:35 ` [gentoo-user] How to fully mask gnome-3.18 upgrade Stroller
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=56D68F12.60404@126.com \
--to=nicol_tao@126.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