amd64 package.mask

[plice]

Hello,

I haven't updated my pc for a long time. now i did emerge --sync, and then i'm trying to run emerge --update world and i get constantly that most of the packages are masked.
the file package.mask has:

=app-misc/lirc-0.8*
>=x11-base/xorg-server-1.7
>=x11-proto/xcmiscproto-1.2.0
>=x11-proto/bigreqsproto-1.1.0
>=x11-proto/xf86driproto-2.1.0
>=x11-proto/xf86bigfontproto-1.2.0
>=x11-base/xorg-drivers-1.7
>=x11-proto/xextproto-7.1.1
>=x11-proto/fixesproto-4.1.1
>=x11-proto/inputproto-2.0
>=x11-libs/libX11-1.4
>=x11-libs/libX11-1.3.2
>=x11-libs/libXext-1.1.1
>=x11-libs/libXi-1.4
>=x11-apps/xinput-1.5.0
>=x11-proto/xf86vidmodeproto-2.3
>=x11-libs/libXxf86vm-1.1.0
>=x11-proto/recordproto-1.14
>=x11-libs/libXtst-1.1.0
>=x11-proto/scrnsaverproto-1.2.0
>=x11-libs/libXScrnSaver-1.2.0
>=x11-proto/xineramaproto-1.2
>=x11-libs/libXinerama-1.1
>=x11-proto/xf86dgaproto-2.1
>=x11-libs/libXxf86dga-1.1.1


(i need to keep lirc the same version, that's why i keep that package, otherwise there is lots of problems)

e.g.
!!! All ebuilds that could satisfy ">=x11-proto/inputproto-2.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-proto/inputproto-2.0.1 (masked by: package.mask)
- x11-proto/inputproto-2.0 (masked by: package.mask)

(dependency required by "x11-libs/libXi-1.3.1" [ebuild])
(dependency required by "xfce-base/xfce4-settings-4.7.4" [ebuild])
(dependency required by "@selected")
(dependency required by "@world" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

each time i unmask one package higher, i get other one blocked.

I have emerged new portage, as it was available. Does portage keep the package.mask updated automatically?

i have also added allow ~amd64, otherwise it wouldn't even start . . .

Pls advise.

thank you

Polish

[Veldrin]

Your package mask worries me...
I there a particular reason, why you do not want to upgrade to xorg-server-1.7? xorg-1.6 is no longer in portage...

as an intermediate step, you could just upgrade system, and then world (i.e emerge -aDu system && emerge -aDu world)

[floppymaster]

Why do you have so many masked packages?

Also, the latest version of lirc in the tree is 0.8.7, so =app-misc/lirc-0.8* has absolutely no effect at the moment.

[Veldrin]

sure it does.... I basically tells portage, to not install any version.
_________________
read the portage output!
If my answer is too concise, ask for an explanation.

[floppymaster]

Ah, yes, I suppose it does.

In that case: Don't upgrade your system if you don't want new software!

[Veldrin]

[plice]

Hi guys,

I had lots of problems with the masking when i tried to set up the gentoo from beginning. Somehow the masking packaged stayed there.

Funny thing is that i have not put any(except lircd) packages to mask it.

I only need to keep the lircd original package (i actually played with it for a long time, partially getting modules form another lircd, otherwise i had issues with seg faults. There was bug in lircd, that was carried continuously for many packages)

Anyways, I guess it's safe then to remove content of the package.mask ? I only need lircd to stay the same.



Also, does portage creates automatically package.mask, or is it just a co incidence?

big thanks

[Veldrin]

[plice]

hey guys,
cleaned the blocked packages. Updating all now and got stuck on the python 3.1 link bug (the python-updater didn't work) so i've just changed elselect python to the 3.1 and it's working.
Now i'm stuck with :

* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
>>> Unpacking source...
>>> Unpacking zope.fixers-1.0.tar.gz to /var/tmp/portage/net-zope/zope-fixers-1.0/work
>>> Source unpacked in /var/tmp/portage/net-zope/zope-fixers-1.0/work
>>> Preparing source in /var/tmp/portage/net-zope/zope-fixers-1.0/work/zope.fixers-1.0 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/net-zope/zope-fixers-1.0/work/zope.fixers-1.0 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/net-zope/zope-fixers-1.0/work/zope.fixers-1.0 ...
* Building of net-zope/zope-fixers-1.0 with CPython 3.1...
python3.1 setup.py build -b build-3.1
Traceback (most recent call last):
File "setup.py", line 19, in <module>
from setuptools import setup, find_packages
ImportError: No module named setuptools
* ERROR: net-zope/zope-fixers-1.0 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3265: Called distutils_src_compile
* environment, line 928: Called python_execute_function 'distutils_building'
* environment, line 2053: Called die
* The specific snippet of code:
* die "${failure_message}";
*
* If you need support, post the output of 'emerge --info =net-zope/zope-fixers-1.0',
* the complete build log and the output of 'emerge -pqv =net-zope/zope-fixers-1.0'.
* The complete build log is located at '/var/tmp/portage/net-zope/zope-fixers-1.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/net-zope/zope-fixers-1.0/temp/environment'.
* S: '/var/tmp/portage/net-zope/zope-fixers-1.0/work/zope.fixers-1.0'

>>> Failed to emerge net-zope/zope-fixers-1.0, Log file:

>>> '/var/tmp/portage/net-zope/zope-fixers-1.0/temp/build.log'

* Messages for package net-zope/zope-fixers-1.0:

* ERROR: net-zope/zope-fixers-1.0 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 3265: Called distutils_src_compile
* environment, line 928: Called python_execute_function 'distutils_building'
* environment, line 2053: Called die
* The specific snippet of code:
* die "${failure_m


haven't seen any bugs online for this one etc :/

got amd 64

thank you

[bpoint]

I just had this exact same problem happen to me earlier today.

[Hu]

[plice]

cool,
got the package fixed. emeged the package and then run python-updater.

Fingers crossed, will update the full box soon . . . haven't done it in a v.long time.

thanks guys!
EDIT:
didn't get far . . .


make[2]: Leaving directory `/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55/tests'
make[2]: Entering directory `/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55'
make[1]: Leaving directory `/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55'
/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55/ext/python /var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55
python3.1 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.1
copying ypath.py -> build/lib.linux-x86_64-3.1
copying ydump.py -> build/lib.linux-x86_64-3.1
copying yaml2xml.py -> build/lib.linux-x86_64-3.1
warning: build_py: byte-compiling is disabled, skipping.

running build_ext
building 'syck' extension
creating build/temp.linux-x86_64-3.1
x86_64-pc-linux-gnu-gcc -pthread -O2 -pipe -march=native -fomit-frame-pointer -fPIC -fPIC -I/usr/local/include -I../../lib -I/usr/include/python3.1 -c pyext.c -o build/temp.linux-x86_64-3.1/pyext.o
pyext.c:12: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'PyTypeObject'
pyext.c: In function 'syck_PyIntMaker':
pyext.c:33: warning: return makes pointer from integer without a cast
pyext.c: At top level:
pyext.c:47: warning: initialization from incompatible pointer type
pyext.c: In function 'py_syck_node_alloc':
pyext.c:56: error: 'SyckNodeType' undeclared (first use in this function)
pyext.c:56: error: (Each undeclared identifier is reported only once
pyext.c:56: error: for each function it appears in.)
pyext.c: In function 'py_syck_node_getattr':
pyext.c:118: warning: return makes pointer from integer without a cast
pyext.c:122: warning: return makes pointer from integer without a cast
pyext.c:128: warning: return makes pointer from integer without a cast
pyext.c: In function 'py_syck_node_setattr':
pyext.c:137: warning: initialization makes pointer from integer without a cast
pyext.c:155: warning: assignment makes pointer from integer without a cast
pyext.c: In function 'py_syck_node_repr':
pyext.c:180: warning: return makes pointer from integer without a cast
pyext.c: At top level:
pyext.c:186: warning: initialization makes integer from pointer without a cast
pyext.c:190: warning: initialization from incompatible pointer type
pyext.c:191: warning: initialization from incompatible pointer type
pyext.c:192: warning: initialization from incompatible pointer type
pyext.c:194: error: 'cmpfunc' undeclared here (not in a function)
pyext.c:194: error: expected '}' before numeric constant
pyext.c: In function 'yaml_org_handler':
pyext.c:228: warning: assignment makes pointer from integer without a cast
pyext.c:237: warning: initialization makes pointer from integer without a cast
pyext.c:240: warning: passing argument 2 of 'PyObject_GetAttr' makes pointer from integer without a cast
pyext.c:290: warning: assignment makes pointer from integer without a cast
pyext.c:295: warning: assignment makes pointer from integer without a cast
pyext.c:300: warning: assignment makes pointer from integer without a cast
pyext.c:305: warning: assignment makes pointer from integer without a cast
pyext.c:310: warning: assignment makes pointer from integer without a cast
pyext.c:316: warning: assignment makes pointer from integer without a cast
pyext.c: In function 'py_syck_parse_handler':
pyext.c:423: warning: assignment makes pointer from integer without a cast
pyext.c: In function 'initsyck':
pyext.c:500: error: 'PyTypeObject' has no member named 'ob_type'
pyext.c:501: warning: assignment makes pointer from integer without a cast
error: command 'x86_64-pc-linux-gnu-gcc' failed with exit status 1
* ERROR: dev-libs/syck-0.55-r4 failed:
* Building failed
*
* Call stack:
* ebuild.sh, line 56: Called src_compile
* environment, line 4987: Called distutils_src_compile
* environment, line 1345: Called die
* The specific snippet of code:
* "$(PYTHON)" "${setup_file}" "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed";
*
* If you need support, post the output of 'emerge --info =dev-libs/syck-0.55-r4',
* the complete build log and the output of 'emerge -pqv =dev-libs/syck-0.55-r4'.
* The complete build log is located at '/var/tmp/portage/dev-libs/syck-0.55-r4/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/syck-0.55-r4/temp/environment'.
* S: '/var/tmp/portage/dev-libs/syck-0.55-r4/work/syck-0.55'

>>> Failed to emerge dev-libs/syck-0.55-r4, Log file:

>>> '/var/tmp/portage/dev-libs/syck-0.55-r4/temp/build.log'


i've run python-updater again, and still nothing.

How do I start looking for errors like that? Is there a how-to or something?

thank you