| View previous topic :: View next topic |
| Author |
Message |
Phleg
n00b
Joined: 17 Oct 2002
Posts: 16
|
 Posted: Fri Jan 17, 2003 10:27 pm Post subject: Portage complaining about man-1.5k-r1 |
 |
|
I'm having trouble updating my system. Whenever I "emerge -u[p] world", I get:
| Code: |
# emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies |
!!! all ebuilds that could satisfy ">=sys-apps/man-1.5k-r1" have been masked. |
I have emerge rsync'd several times to no avail, and most packages I try to update explicitly return to me with this error. I've searched in /usr/portage/profiles/package.mask, but haven't found where this is masked. What can I do to fix it?
Last edited by Phleg on Fri Jan 17, 2003 10:43 pm; edited 1 time in total |
|
| Back to top |
|
 |
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 10:40 pm Post subject: |
|
|
provide the full path to the ebuild:#
| Code: | | emerge -u /usr/portage/sys-apps/man/man-1.5k-r1.ebuild |
the packages are not masked in package.mask but directly in the ebuild via keyword - see also ACCEPT_KEYWORD in your /etc/make.conf
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be.
Last edited by slartibartfasz on Fri Jan 17, 2003 10:42 pm; edited 1 time in total |
|
| Back to top |
|
|
Phleg
n00b
Joined: 17 Oct 2002
Posts: 16
|
| Posted: Fri Jan 17, 2003 10:41 pm Post subject: |
|
|
I'm assuming it's masked for a reason, though =) What might this reason be, before I (potentially) bork my system?
Edit: And, err...it doesn't work anyways.
| Code: | # emerge -pu /usr/portage/sys-apps/man/man-1.5k-r1.ebuild
These are the packages that I would merge, in order:
Calculating dependencies \
!!! all ebuilds that could satisfy ">=sys-apps/man-1.5k-r1" have been masked.
!!! Error calculating dependancies. Please correct. |
It doesn't seem to even finish calculating dependencies, as it goes through that loop for a split second then immediately splurts out the error message.
Last edited by Phleg on Fri Jan 17, 2003 10:44 pm; edited 2 times in total |
|
| Back to top |
|
|
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 10:43 pm Post subject: |
|
|
i dont think man is so crucial to your system - if it doesnt work u can downgrade.... as for the reason - sorry no idea
UPDATE: try it without the -p option ... should work - or u can try to set ACCEPT_KEYWORDS in make.conf
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be. |
|
| Back to top |
|
|
Phleg
n00b
Joined: 17 Oct 2002
Posts: 16
|
| Posted: Fri Jan 17, 2003 10:45 pm Post subject: |
|
|
| slartibartfasz wrote: | | see also ACCEPT_KEYWORD in your /etc/make.conf |
Don't have it there...can you show me a copy of yours? That could be the problem. With the latest version of portage, I believe it updated the contents of make.conf, but I chose to delete the updates (so I could keep my USE settings).
Also, without the -p it still didn't work. |
|
| Back to top |
|
|
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 10:48 pm Post subject: |
|
|
thats very strange - whats your gentoo and portage version?
try:
| Code: | | cat /etc/make.conf | grep KEYWORD |
just to be sure...
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be. |
|
| Back to top |
|
|
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 10:49 pm Post subject: |
|
|
here is the settings section of my make.conf:
| Code: |
# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc', '~sparc64' are the unstable KEYWORDS for their respective
# platforms. DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
ACCEPT_KEYWORDS="~x86"
# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
# temporary storage of data. This can get VERY large depending upon
# the application being installed.
#PORTAGE_TMPDIR=/var/tmp
#
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
# emerges. The source code is maintained here unless you delete
# it. The entire repository of tarballs for gentoo is 9G. This is
# considerably more than any user will ever download. 2-3G is
# a large DISTDIR.
#DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
# with '--buildpkg' or '-b' while emerging a package. This can get
# upto several hundred megs, or even a few gigs.
#PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed.
#PORT_LOGDIR=/var/log/emerge/
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
#PORTDIR_OVERLAY=/usr/local/portage
# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space seperated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror.
#GENTOO_MIRRORS="<your_mirror_here> http://www.ibiblio.org/pub/Linux/distributions/gentoo"
# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
# program is compiled. Presently the only use is for specifying
# the number of parallel makes (-j) to perform. The suggested number
# for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
# packages from the system after every successful merge. This is the
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
# these settings are for developer use, but some are available to non-
# developers as well. 'buildpkg' is an always-on setting for the emerge
# flag of the same name. It causes binary packages to be created of all
# packages that are merged.
#FEATURES="sandbox ccache buildpkg"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
# a current portage tree before it exits with an error. This allows
# for a more successful retrieval without user intervention most times.
#RSYNC_RETRIES="3"
|
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be. |
|
| Back to top |
|
|
Phleg
n00b
Joined: 17 Oct 2002
Posts: 16
|
| Posted: Fri Jan 17, 2003 10:49 pm Post subject: |
|
|
| Code: | # cat /etc/make.conf | grep KEYWORD
# |
I'm using 2.0.46-r4 of Portage.
Edit: FIXED. Adding in the ACCEPT_KEYWORDS option did it! Thanks. |
|
| Back to top |
|
|
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 10:52 pm Post subject: |
|
|
if that still doesnt work u can directly edit the ebuild - at the beginning theres a line KEYWORDS...
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be. |
|
| Back to top |
|
|
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Fri Jan 17, 2003 11:02 pm Post subject: Re: Portage complaining about man-1.5k-r1 |
|
|
| Phleg wrote: | I'm having trouble updating my system. Whenever I "emerge -u[p] world", I get:
| Code: |
# emerge -pu world
These are the packages that I would merge, in order:
Calculating world dependencies |
!!! all ebuilds that could satisfy ">=sys-apps/man-1.5k-r1" have been masked. |
|
Hi,
Emerge doesn't say that man-1.5k-r1 is masked, but it does look like some dependencies has been masked. It might be a deep dependency, so I suggest trying:
| Code: |
emerge -u --deep world -p
|
man-1.5k-r1 is currently installed on my system.
Hope that helps,
--Kutsuya |
|
| Back to top |
|
|
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Fri Jan 17, 2003 11:07 pm Post subject: |
|
|
| slartibartfasz wrote: | here is the settings section of my make.conf:
|
....
Hi,
I like looking at the results of:
It seems shorter, and yet more complete.
regards,
--Kutsuya |
|
| Back to top |
|
|
slartibartfasz
Veteran
Joined: 29 Oct 2002
Posts: 1462
Location: Vienna, Austria
|
| Posted: Fri Jan 17, 2003 11:11 pm Post subject: |
|
|
@Kutsuya
thx for the hint - i learn every time i visit the forums... 
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be. |
|
| Back to top |
|
|
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Fri Jan 17, 2003 11:18 pm Post subject: emerge info |
|
|
| slartibartfasz wrote: | @Kutsuya
thx for the hint - i learn every time i visit the forums... |
You are welcome. It's the same with me. 
--Kutsuya |
|
| Back to top |
|
|
|
Portage & Programming
