Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 619714 - sys-apps/portage-2.3.6: emerge complains about eselect news items version 2.0 (wine item)
Summary: sys-apps/portage-2.3.6: emerge complains about eselect news items version 2.0...
Status: UNCONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-26 02:19 UTC by G.Wolfe Woodbury
Modified: 2017-07-24 12:07 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description G.Wolfe Woodbury 2017-05-26 02:19:25 UTC
emerge complains about /usr/portage/metadata/news/en/.... on a format version 2.0
item for wine (2017-04-??)

This was mentioned in another bug, (#616186) that was closed as resolved in portage 2.3.3

However, portage-2.3.6 (unstable ~amd64) still complains about this item.

I suspect something in 2.3.3 didn't make it into 2.3.6
Comment 1 Todd Walter 2017-05-26 18:03:37 UTC
I'm experiencing the same problem.

Check your emerge --info.

My installed portage (per eix) claims to be 2.3.5 but emerge --info reports 2.2.6. Something went wrong, probably back during the python-exec debacle.
Comment 2 Todd Walter 2017-05-26 18:39:59 UTC
!!! Invalid news item: /usr/portage/metadata/news/2017-04-10-split-and-slotted-wine/2017-04-10-split-and-slotted-wine.en.txt
!!!   line 6: News-Item-Format: 2.0
vader ~ # emerge --info | grep Portage
Portage 2.2.26 (python 3.5.3-final-0, default/linux/amd64/13.0, gcc-6.3.0, glibc-2.23-r3, 4.9.9-gentoo x86_64)
vader ~ # eix sys-apps/portage
[I] sys-apps/portage
     Available versions:  2.2.28 2.3.0 2.3.3 ~2.3.4 2.3.5 ~2.3.6 **9999 {build doc epydoc +ipc +native-extensions selinux xattr LINGUAS="ru" PYTHON_TARGETS="pypy python2_7 python3_4 python3_5 python3_6"}
     Installed versions:  2.3.5(02:40:26 PM 26/05/17)(ipc native-extensions xattr -build -doc -epydoc -selinux LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_4 -pypy -python3_5 -python3_6")


Annoyingly enough, I have a python_targets_python3_5 in package.use but it doesn't seem to pick up on it when I re-emerge the package.
Comment 3 Todd Walter 2017-05-26 19:11:52 UTC
It's the PYTHON_TARGETS that's the issue.  Emerge doesn't update /usr/lib/python-exec/python3.5 even when the variable is set although the earlier version did.

vader python3.5 # ./emerge --version
Portage 2.2.26 (python 3.5.3-final-0, default/linux/amd64/13.0, gcc-6.3.0, glibc-2.23-r3, 4.9.9-gentoo x86_64)
vader python3.5 # ../python3.4/emerge --version
Portage 2.3.5 (python 3.4.5-final-0, default/linux/amd64/13.0, gcc-6.3.0, glibc-2.23-r3, 4.9.9-gentoo x86_64)
vader python3.5 # ../python2.7/emerge --version
Portage 2.3.5 (python 2.7.12-final-0, default/linux/amd64/13.0, gcc-6.3.0, glibc-2.23-r3, 4.9.9-gentoo x86_64)
Comment 4 Todd Walter 2017-05-26 19:14:25 UTC
Those of use with Python 3.5 set as system primary Python (who are probably Blender users) will hit this until 3.5 is out of unstable.
Comment 5 G.Wolfe Woodbury 2017-07-24 12:05:36 UTC
Can we at least get this bug marked as "CONFIRMED" ?

There are now two Version 2.0 news articles that trigger this warning.

Is there a simple workaround ?