[gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Martin Vaeth
Alan McKinnon alan.mckin...@gmail.com wrote:
 You know what? I'm not convinced.

 What I'm seeing is a rather large towering edifice of complexity to deal
 with a problem that is not the general case.

I find it funny that perhaps you did not realize that you repeated
the main argument *in favour of subslots* on the dev mailing list:

Alan McKinnon alan.mckin...@gmail.com wrote:

[ about emerge -e @world ]

 I've used this once or twice over the years to take care of inexplicable
 instability [...]

In fact, I bet that many gentoo users had the experience several times
over the years that reemerging the same(!) version of some package
mysteriously solves some problem.

 I strongly suspect the actual cause was inconsistencies around plug-in
 modules - the only thing I know of that portage and tools like
 revdep-rebuild can't really detect.

As I have just tried to explain, the cause was more likely the change
of some ABI without a change of the library version: revdep-rebuild can
only detect version changes, and there are some libraries like poppler
or neon (but probably many more I do not know) where upstream regularly
does such tacit ABI changes as a policy.

This was the main reason for introducing subslots!

(That it avoids using revdep-rebuild in many cases or calling things
like @x11-module-rebuild, python-updater, perl-updater, ... is only
a convenient side effect.
Subslots solve the plug-in modules problem, too, of course.)

With subslots emerge -e @world will in the long run never be necessary
anymore to get stability (it might of course still be necessary due to
a major toolchain change; also it does not catch cases where a
tacit ABI change happened by mistake and the developers failed to
see it.)

Note, however, in the long run: The process of transforming all
packages to subslot dependencies is not yet complete.
I guess it will take many years until it is: Up to some corner cases
you can check whether the process is complete for your system when
(
cd -- $(portageq portdir)/metadata/md5-cache
grep -L '^EAPI=\([5-9]\|[1-9][0-9]\)' $(qlist -ICv)
)
does not output anything.



Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Peter Humphrey
On Tuesday 05 Nov 2013 10:52:36 Martin Vaeth wrote:

 Note, however, in the long run: The process of transforming all
 packages to subslot dependencies is not yet complete.
 I guess it will take many years until it is: Up to some corner cases
 you can check whether the process is complete for your system when
 (
   cd -- $(portageq portdir)/metadata/md5-cache
   grep -L '^EAPI=\([5-9]\|[1-9][0-9]\)' $(qlist -ICv)
 )
 does not output anything.

Instructive - here it lists 507 packages!

-- 
Regards,
Peter





Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Alan McKinnon
On 05/11/2013 11:52, Martin Vaeth wrote:
 Alan McKinnon alan.mckin...@gmail.com wrote:
 You know what? I'm not convinced.

 What I'm seeing is a rather large towering edifice of complexity to deal
 with a problem that is not the general case.
 
 I find it funny that perhaps you did not realize that you repeated
 the main argument *in favour of subslots* on the dev mailing list:


It seems to me that you didn't read the whole post fully, and have
cherry-picked a part that you think bolsters your position. It does not.
So I will repeat myself in a different way.

I've run emerge -e world with the result of correcting something perhaps
2 or 3 times in 8 years. Let's assume that in the absence of portage
being able to detect those nasty errors, that this is reasonably
representative of the actual incidence of actual errors I encountered.
Let's then be generous and triple it.

In effect subslots appear to fix something for me about once a year. Is
my logic^Wguess flawed in any way?

So now we have a rather large complex system that deals with what is
essentially a minor problem that occurs say once a year.

I completely understand the problem sub-slots is trying to solve. I'm
just wondering if the methodology you are using to do it is valid, and
if it does not become the cure that is worse than the disease.

Consider for a moment the maintenance burden imposed on ebuild
maintainers, and how sub-slot notation is essentially added by humans
deploying human brains. And remember that humans are notoriously bad at
using mathematically correct solutions (they ... err ... forget to do
stuff).

sub-slots, whilst quite likely mathematically correct, has all the
hallmarks to me of SOMETHING THAT IS GOING TO FAIL DUE TO HUMANS. And
humans seldom do those things that they should do . If this were not so,
php would never have been written (just an arb random example)

I predict once a week fallout from sub-slots induced bugs that was
intended to fix once a year problem.

Do you now see why I'm not convinced this is a real-world solution?




 
 Alan McKinnon alan.mckin...@gmail.com wrote:
 
 [ about emerge -e @world ]
 
 I've used this once or twice over the years to take care of inexplicable
 instability [...]
 
 In fact, I bet that many gentoo users had the experience several times
 over the years that reemerging the same(!) version of some package
 mysteriously solves some problem.
 
 I strongly suspect the actual cause was inconsistencies around plug-in
 modules - the only thing I know of that portage and tools like
 revdep-rebuild can't really detect.
 
 As I have just tried to explain, the cause was more likely the change
 of some ABI without a change of the library version: revdep-rebuild can
 only detect version changes, and there are some libraries like poppler
 or neon (but probably many more I do not know) where upstream regularly
 does such tacit ABI changes as a policy.
 
 This was the main reason for introducing subslots!
 
 (That it avoids using revdep-rebuild in many cases or calling things
 like @x11-module-rebuild, python-updater, perl-updater, ... is only
 a convenient side effect.
 Subslots solve the plug-in modules problem, too, of course.)
 
 With subslots emerge -e @world will in the long run never be necessary
 anymore to get stability (it might of course still be necessary due to
 a major toolchain change; also it does not catch cases where a
 tacit ABI change happened by mistake and the developers failed to
 see it.)
 
 Note, however, in the long run: The process of transforming all
 packages to subslot dependencies is not yet complete.
 I guess it will take many years until it is: Up to some corner cases
 you can check whether the process is complete for your system when
 (
   cd -- $(portageq portdir)/metadata/md5-cache
   grep -L '^EAPI=\([5-9]\|[1-9][0-9]\)' $(qlist -ICv)
 )
 does not output anything.
 


-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Marc Joliet
Am Tue, 05 Nov 2013 12:14:59 +0200
schrieb Alan McKinnon alan.mckin...@gmail.com:

 On 05/11/2013 11:52, Martin Vaeth wrote:
  Alan McKinnon alan.mckin...@gmail.com wrote:
  You know what? I'm not convinced.
 
  What I'm seeing is a rather large towering edifice of complexity to deal
  with a problem that is not the general case.
  
  I find it funny that perhaps you did not realize that you repeated
  the main argument *in favour of subslots* on the dev mailing list:
 
 
 It seems to me that you didn't read the whole post fully, and have
 cherry-picked a part that you think bolsters your position. It does not.
 So I will repeat myself in a different way.
 
 I've run emerge -e world with the result of correcting something perhaps
 2 or 3 times in 8 years. Let's assume that in the absence of portage
 being able to detect those nasty errors, that this is reasonably
 representative of the actual incidence of actual errors I encountered.
 Let's then be generous and triple it.
 
 In effect subslots appear to fix something for me about once a year. Is
 my logic^Wguess flawed in any way?

For *you*! You are not everyone, although I'm sure you already know that ;) .
See my Haskell example below for when subslots fix something more often.

 So now we have a rather large complex system that deals with what is
 essentially a minor problem that occurs say once a year.
 
 I completely understand the problem sub-slots is trying to solve. I'm
 just wondering if the methodology you are using to do it is valid, and
 if it does not become the cure that is worse than the disease.
 
 Consider for a moment the maintenance burden imposed on ebuild
 maintainers, and how sub-slot notation is essentially added by humans
 deploying human brains. And remember that humans are notoriously bad at
 using mathematically correct solutions (they ... err ... forget to do
 stuff).
 
 sub-slots, whilst quite likely mathematically correct, has all the
 hallmarks to me of SOMETHING THAT IS GOING TO FAIL DUE TO HUMANS. And
 humans seldom do those things that they should do . If this were not so,
 php would never have been written (just an arb random example)
 
 I predict once a week fallout from sub-slots induced bugs that was
 intended to fix once a year problem.
 
 Do you now see why I'm not convinced this is a real-world solution?

I think I see your point, but what is the worst that can happen if somebody
gets a subslot wrong? Since too *many* rebuilds aren't all too terrible (a
waste of time for sure, and potentially annoying, but it won't outright break
anything), I suppose the worst case is too *few* automatic rebuilds, right? So
to me it sounds like you want to throw out the feature altogether because it
won't *always* catch everything. Or what potential bugs are you thinking about
that aren't useless rebuilds? I don't remember any from this thread, but of
course I could have missed something.

But what's the alternative? Telling the user to do it instead? That requires
human input, too: *somebody* has to write the elog message, and such that
any Gentoo user can understand it. Or is your point that one can look for
*fully* automatic solutions, as opposed to solutions where humans have to
provide input? I would expect the portage developers to have thought about it
for a while before settling with the subslot idea.

Now an example of my experience with subslots:

I use pandoc (used by IPython Notebook to convert notebooks to html or
whatever), and it -- along with all it's Haskell dependencies -- uses subslots.
That means that, whenever one of the Haskell dependencies updates, it
automatically rebuilds its reverse dependencies. And most of the time, it works
just fine! That's when I like subslots. Especially since the Haskell packages
are moving targets that update fairly often.

When it doesn't work, I'm stuck looking for what I have to rebuild. As a
matter of fact, I ran into such an issue just now: dev-haskell/texmath is
missing a dependency somewhere, so that pandoc would not compile (or run)
anymore after an upgrade to dev-haskell/aeson. Solution: recompile texmath
manually (a bug report will follow). That was simple, however, since the error
message of the Haskell compiler tells you which libraries are the problem. I
don't think I dislike subslots because of this. It's certainly nothing
preserved-rebuild or revdep-rebuild would find.

So, unless there's an at least equally good alternative, *no* subslots would
mean I would have to re-merge *all* dev-haskell packages after every update,
just to be on the safe side (or iteratively recompile according to what the
error message tells me until I finally catch all packages). I think that would
be slightly more terrible than forgotten subslots ;) .



That said, one can certainly improve the user interface to subslots, and I
like the ideas put forth by Martin Väth in
https://bugs.gentoo.org/show_bug.cgi?id=490350. I especially like the idea of
having a dynamic set 

Re: [gentoo-user] do subslots improve user-experience?

2013-11-05 Thread Bruce Hill
On Sat, Nov 02, 2013 at 01:04:52PM +0100, hasufell wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Another round of questioning the users here.
 
 more specifically:
 * how often do you experience useless rebuilds?
 * do you really have a problem with running
 revdep-rebuild/haskell-updater/perl-cleaner etc after every emerge?
 * do you think it's worth the effort to add more stuff to the PM, so
 that you don't have to run revdep-rebuild that often?
 * do you trust the other methods like subslots or preserved-rebuild to
 work reliably? (as in: do you still use revdep-rebuild?)
 
 If you want my opinion on subslots:
 # grep EMERGE_DEFAULT_OPTS /etc/portage/make.conf
 EMERGE_DEFAULT_OPTS=--ignore-built-slot-operator-deps=y

This kind of subslot mess is so irritating:

workstation ~ # emerge -aDjtuv --changed-use @world  dispatch-conf  emerge 
-a --depclean  revdep-rebuild -i  clear  exit

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  rR] dev-qt/qtgui-4.8.5-r1:4  USE=accessibility exceptions glib xv 
(-aqua) -cups -debug -egl -gtkstyle -mng -nas -nis -pch -qt3support -tiff 
-trace -xinerama 0 kB
[ebuild  rR] media-libs/libwebp-0.3.1  USE=jpeg png -experimental -gif 
-opengl -static-libs -swap-16bit-csp -tiff ABI_X86=(64) (-32) (-x32) 0 kB
[ebuild  rR] app-emulation/wine-1.6  USE=X alsa cups fontconfig jpeg mono 
mp3 ncurses nls opengl perl png prelink run-exes ssl threads truetype udisks 
xml -capi -custom-cflags -dos -gecko -gphoto2 -gsm -gstreamer -lcms -ldap -odbc 
-openal -opencl -osmesa -oss -pulseaudio -samba -scanner (-selinux) {-test} 
-v4l -xcomposite -xinerama ABI_X86=32 64 (-x32) LINGUAS=en_US -ar -bg -ca 
-cs -da -de -el -en -eo -es -fa -fi -fr -he -hi -hr -hu -it -ja -ko -lt -ml 
-nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk -sl -sr_RS@cyrillic 
-sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW 0 kB
[ebuild U ~] www-client/firefox-25.0-r1 [24.0-r1] USE=alsa dbus jit 
libnotify startup-notification -bindist -custom-cflags -custom-optimization 
-debug -gstreamer -minimal (-pgo) -pulseaudio (-selinux) -system-cairo 
-system-icu -system-jpeg -system-sqlite -wifi LINGUAS=-af -ak -ar -as -ast 
-be -bg -bn_BD -bn_IN -br -bs -ca -cs -csb -cy -da -de -el -en_GB -en_ZA -eo 
-es_AR -es_CL -es_ES -es_MX -et -eu -fa -fi -fr -fy_NL -ga_IE -gd -gl -gu_IN 
-he -hi_IN -hr -hu -hy_AM -id -is -it -ja -kk -km -kn -ko -ku -lg -lt -lv -mai 
-mk -ml -mr -nb_NO -nl -nn_NO -nso -or -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si 
-sk -sl -son -sq -sr -sv_SE -ta -ta_LK -te -th -tr -uk -vi -zh_CN -zh_TW -zu 
124,545 kB
[ebuild U  ] app-portage/pfl-2.4-r1 [2.3] USE=network-cron 
PYTHON_TARGETS=python2_7%* -python2_6% 7 kB
[ebuild U ~] mail-client/thunderbird-24.1.0-r1 [24.0-r1] USE=alsa dbus jit 
libnotify lightning startup-notification -bindist -crypt -custom-cflags 
-custom-optimization -debug -gstreamer -ldap -minimal -mozdom -pulseaudio 
(-selinux) -system-cairo -system-icu -system-jpeg -system-sqlite -wifi 
LINGUAS=-ar -ast -be -bg -bn_BD -br -ca -cs -da -de -el -en_GB -es_AR -es_ES 
-et -eu -fi -fr -fy_NL -ga_IE -gd -gl -he -hr -hu -hy_AM -id -is -it -ja -ko 
-lt -nb_NO -nl -nn_NO -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si -sk -sl -sq -sr 
-sv_SE -ta_LK -tr -uk -vi -zh_CN -zh_TW 137,057 kB
[ebuild  rR] net-print/cups-filters-1.0.36-r1  USE=jpeg png tiff -perl 
-static-libs -zeroconf 0 kB
[ebuild  rR]  app-text/poppler-0.24.3:0/43  USE=cairo cjk cxx 
introspection jpeg jpeg2k lcms png tiff utils -curl -debug -doc -qt4 0 kB
[ebuild  rR]   media-libs/openjpeg-1.5.1  USE=-doc -static-libs {-test} 0 
kB
[ebuild  rR]   x11-libs/cairo-1.12.14-r4  USE=X glib svg (-aqua) -debug 
-directfb -doc (-drm) (-gallium) (-gles2) -legacy-drivers -opengl -openvg 
(-qt4) -static-libs -valgrind -xcb -xlib-xcb 0 kB
[ebuild  r  U ~]media-libs/libpng-1.6.6:0/16 [1.5.15:0/0] USE=apng (-neon) 
-static-libs ABI_X86=(64%*) -32% (-x32) 860 kB

Total: 11 packages (4 upgrades, 7 reinstalls), Size of downloads: 262,467 kB

The following keyword changes are necessary to proceed:
 (see package.accept_keywords in the portage(5) man page for more details)
# required by @__auto_slot_operator_replace_installed__ (argument)
=media-libs/libpng-1.6.6 ~amd64

Use --autounmask-write to write changes to config files (honoring
CONFIG_PROTECT). Carefully examine the list of proposed changes,
paying special attention to mask or keyword changes that may expose
experimental or unstable packages.

!!! The following installed packages are masked:
- net-analyzer/mtr-0.82::gentoo (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

workstation ~ # grep libpng 
/usr/portage/net-print/cups-filters/cups-filters-1.0.36-r1.ebuild 
png? ( media-libs/libpng:0= )
workstation ~ # grep libpng /usr/portage/app-text/poppler/poppler-0.24.3.ebuild 
png? ( 

Re: [gentoo-user] Qt blocking @world update

2013-11-05 Thread Alex Schuster

Alan McKinnon writes:


Excuse the top-posting; if I try inter-post between all those blockers
you'll never find what I reply :-)


I would, but for everyone else it's a mess. E-mail with line breaks is
not suited for this kind of output.


First I recommend to sync your tree again, just in case you got yours
between two Qt commits and things are not consistent anymore.


Ah, I have this problem for weeks now, but did not care enough. And did
not have the time for this.


You seem to have at least two things happening:

python-exec
qt

To deal with the first, try remove python-exec and re-merge it (but
quickpkg a backup first)

quickpkg python-exec  emerge -avC python-exec  emerge -av1
python-exec

This is untested so I don't know if it will bork. If it does, you have a
quickpkg that you can untar and get things back.


Thanks, a simple upgrade just worked, as I wrote in the reply to Walt.


Onto Qt:

I've had similar things over the years and it always made little sense.
Eventually I removed all references to Qt from world, sets in use and
USE then let portage figure out what to do. Rationale: Qt is a basic
toolkit that stuff uses, so stuff should decide what it needs and not
me. I want the stuff and if that requires Qt then just let portage give
me what is required.

This will show all references to Qt to consider:

grep -ir /qt /etc/portage/ /var/lib/portage/world*


/etc/portage/sets.portage/qt-split:x11-libs/qt-assistant
/etc/portage/sets.portage/qt-split:x11-libs/qt-core
/etc/portage/sets.portage/qt-split:x11-libs/qt-dbus
/etc/portage/sets.portage/qt-split:x11-libs/qt-demo
/etc/portage/sets.portage/qt-split:x11-libs/qt-gui
/etc/portage/sets.portage/qt-split:x11-libs/qt-opengl
/etc/portage/sets.portage/qt-split:x11-libs/qt-phonon
/etc/portage/sets.portage/qt-split:x11-libs/qt-qt3support
/etc/portage/sets.portage/qt-split:x11-libs/qt-script
/etc/portage/sets.portage/qt-split:x11-libs/qt-sql
/etc/portage/sets.portage/qt-split:x11-libs/qt-svg
/etc/portage/sets.portage/qt-split:x11-libs/qt-test
/etc/portage/sets.portage/qt-split:x11-libs/qt-webkit
/etc/portage/sets.portage/qt-split:x11-libs/qt-xmlpatterns
/etc/portage/package.use/misc:dev-qt/qt-creator  doc examples perforce
qtscript
/etc/portage/package.use/misc:dev-qt/qt-meta:3   doc mysql
/etc/portage/package.use/misc:dev-qt/qthelp  doc
/etc/portage/package.use/misc:dev-qt/qtsql   mysql
/etc/portage/package.use/misc:=dev-qt/qtgui-4.8.4-r1 gtkstyle
/etc/portage/package.use/misc:=dev-qt/qtsql-4.8.4mysql
/etc/portage/package.use/misc:=dev-qt/qtgui-4.8.4-r1 gtkstyle
/etc/portage/package.use/misc:=dev-qt/qtgui-4.8.4-r1 gtkstyle
/etc/portage/package.use/misc:=dev-qt/qtsql-4.8.4mysql
/etc/portage/package.use/misc:=dev-qt/qtgui-4.8.4-r1 gtkstyle
/var/lib/portage/world:dev-qt/qt-meta:3


In your case, I see portage wants to downgrade several Qt packages due
to fsrunner, but there's nothing in that ebuild or the kde4-base eclass
it inherits, which leads me to believe you might have a config setting
somewhere that wants to exclude latest Qt somehow.


I commented them all out, I still get the error about multiple Qt
versions.



Portage and the tree by itself isn't doing it, here's my output:

$ emerge -pvt fsrunner

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
[ebuild  N ] kde-misc/fsrunner-0.7.5:4  USE=(-aqua) -debug 18 kB

Total: 1 package (1 new), Size of downloads: 18 kB


Same here, except that it's emerged already.

OK, I have no clue how to further debug this. But what I did is:

for (( i=500; i  0; i-=20 ))
do
  emerge -DautvNj $( head -n $i /var/lib/portage/world )
done

This failed until $i was 260, so I tried a little more, and removed 
media-sound/kid3 from @world. Along with fsrunner of course. Now, it's 
building.


This does not make any sense, does it?

Wonko



Re: [gentoo-user] do subslots improve user-experience?

2013-11-05 Thread Bruce Hill
On Tue, Nov 05, 2013 at 07:29:28AM -0600, Bruce Hill wrote:
 On Sat, Nov 02, 2013 at 01:04:52PM +0100, hasufell wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
  
  Another round of questioning the users here.
  
  more specifically:
  * how often do you experience useless rebuilds?
  * do you really have a problem with running
  revdep-rebuild/haskell-updater/perl-cleaner etc after every emerge?
  * do you think it's worth the effort to add more stuff to the PM, so
  that you don't have to run revdep-rebuild that often?
  * do you trust the other methods like subslots or preserved-rebuild to
  work reliably? (as in: do you still use revdep-rebuild?)
  
  If you want my opinion on subslots:
  # grep EMERGE_DEFAULT_OPTS /etc/portage/make.conf
  EMERGE_DEFAULT_OPTS=--ignore-built-slot-operator-deps=y
 
 This kind of subslot mess is so irritating:
 
 workstation ~ # emerge -aDjtuv --changed-use @world  dispatch-conf  
 emerge -a --depclean  revdep-rebuild -i  clear  exit
 
 These are the packages that would be merged, in reverse order:
 
 Calculating dependencies... done!
 [ebuild  rR] dev-qt/qtgui-4.8.5-r1:4  USE=accessibility exceptions glib 
 xv (-aqua) -cups -debug -egl -gtkstyle -mng -nas -nis -pch -qt3support -tiff 
 -trace -xinerama 0 kB
 [ebuild  rR] media-libs/libwebp-0.3.1  USE=jpeg png -experimental -gif 
 -opengl -static-libs -swap-16bit-csp -tiff ABI_X86=(64) (-32) (-x32) 0 kB
 [ebuild  rR] app-emulation/wine-1.6  USE=X alsa cups fontconfig jpeg 
 mono mp3 ncurses nls opengl perl png prelink run-exes ssl threads truetype 
 udisks xml -capi -custom-cflags -dos -gecko -gphoto2 -gsm -gstreamer -lcms 
 -ldap -odbc -openal -opencl -osmesa -oss -pulseaudio -samba -scanner 
 (-selinux) {-test} -v4l -xcomposite -xinerama ABI_X86=32 64 (-x32) 
 LINGUAS=en_US -ar -bg -ca -cs -da -de -el -en -eo -es -fa -fi -fr -he -hi 
 -hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru 
 -sk -sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW 0 
 kB
 [ebuild U ~] www-client/firefox-25.0-r1 [24.0-r1] USE=alsa dbus jit 
 libnotify startup-notification -bindist -custom-cflags -custom-optimization 
 -debug -gstreamer -minimal (-pgo) -pulseaudio (-selinux) -system-cairo 
 -system-icu -system-jpeg -system-sqlite -wifi LINGUAS=-af -ak -ar -as -ast 
 -be -bg -bn_BD -bn_IN -br -bs -ca -cs -csb -cy -da -de -el -en_GB -en_ZA -eo 
 -es_AR -es_CL -es_ES -es_MX -et -eu -fa -fi -fr -fy_NL -ga_IE -gd -gl -gu_IN 
 -he -hi_IN -hr -hu -hy_AM -id -is -it -ja -kk -km -kn -ko -ku -lg -lt -lv 
 -mai -mk -ml -mr -nb_NO -nl -nn_NO -nso -or -pa_IN -pl -pt_BR -pt_PT -rm -ro 
 -ru -si -sk -sl -son -sq -sr -sv_SE -ta -ta_LK -te -th -tr -uk -vi -zh_CN 
 -zh_TW -zu 124,545 kB
 [ebuild U  ] app-portage/pfl-2.4-r1 [2.3] USE=network-cron 
 PYTHON_TARGETS=python2_7%* -python2_6% 7 kB
 [ebuild U ~] mail-client/thunderbird-24.1.0-r1 [24.0-r1] USE=alsa dbus 
 jit libnotify lightning startup-notification -bindist -crypt -custom-cflags 
 -custom-optimization -debug -gstreamer -ldap -minimal -mozdom -pulseaudio 
 (-selinux) -system-cairo -system-icu -system-jpeg -system-sqlite -wifi 
 LINGUAS=-ar -ast -be -bg -bn_BD -br -ca -cs -da -de -el -en_GB -es_AR -es_ES 
 -et -eu -fi -fr -fy_NL -ga_IE -gd -gl -he -hr -hu -hy_AM -id -is -it -ja -ko 
 -lt -nb_NO -nl -nn_NO -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si -sk -sl -sq 
 -sr -sv_SE -ta_LK -tr -uk -vi -zh_CN -zh_TW 137,057 kB
 [ebuild  rR] net-print/cups-filters-1.0.36-r1  USE=jpeg png tiff -perl 
 -static-libs -zeroconf 0 kB
 [ebuild  rR]  app-text/poppler-0.24.3:0/43  USE=cairo cjk cxx 
 introspection jpeg jpeg2k lcms png tiff utils -curl -debug -doc -qt4 0 kB
 [ebuild  rR]   media-libs/openjpeg-1.5.1  USE=-doc -static-libs {-test} 
 0 kB
 [ebuild  rR]   x11-libs/cairo-1.12.14-r4  USE=X glib svg (-aqua) -debug 
 -directfb -doc (-drm) (-gallium) (-gles2) -legacy-drivers -opengl -openvg 
 (-qt4) -static-libs -valgrind -xcb -xlib-xcb 0 kB
 [ebuild  r  U ~]media-libs/libpng-1.6.6:0/16 [1.5.15:0/0] USE=apng 
 (-neon) -static-libs ABI_X86=(64%*) -32% (-x32) 860 kB
 
 Total: 11 packages (4 upgrades, 7 reinstalls), Size of downloads: 262,467 kB
 
 The following keyword changes are necessary to proceed:
  (see package.accept_keywords in the portage(5) man page for more details)
 # required by @__auto_slot_operator_replace_installed__ (argument)
 =media-libs/libpng-1.6.6 ~amd64
 
 Use --autounmask-write to write changes to config files (honoring
 CONFIG_PROTECT). Carefully examine the list of proposed changes,
 paying special attention to mask or keyword changes that may expose
 experimental or unstable packages.
 
 !!! The following installed packages are masked:
 - net-analyzer/mtr-0.82::gentoo (masked by: package.mask)
 For more information, see the MASKED PACKAGES section in the emerge
 man page or refer to the Gentoo Handbook.
 
 workstation ~ # grep libpng 
 /usr/portage/net-print/cups-filters/cups-filters-1.0.36-r1.ebuild 

Re: [gentoo-user] Re: resolving blocked packages [media-video/ffmpeg-1.2:0]

2013-11-05 Thread Bruce Hill
On Tue, Nov 05, 2013 at 06:15:56AM +, Nuno J. Silva (aka njsg) wrote:
  On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote:
   On 11/03/2013 02:27 AM, Daniel Campbell wrote:
For starters, you should probably merge package.keywords into
package.accept_keywords; the latter is the new standard name, though
Portage will likely support the old names for a while. Just a heads-up
on that.
   
   Thanks for a heads-up. I did as you suggested.
  
  Is there going to be a portage news article on this, or did I miss it?
 
  It wasn't two or three years ago...
 
  mingdao@server ~ $ eselect news read 5
  2012-09-09-make.conf-and-make.profile-move
Title make.conf and make.profile move
AuthorJorge Manuel B. S. Vicetto 
  jmbsvice...@gentoo.org
Posted2012-09-09
Revision  1
 
  Starting next week, new stages will have make.conf and make.profile
  moved from /etc to /etc/portage. This is a change in the installation
  defaults, that will only affect new installs so it doesn't affect
  current systems.
 
  Current users don't need to do anything. But if you want to follow the
  preferred location, you may want to take the chance to move the files
  in your system(s) to the new location.
 
 But that's about make.conf, not about package.keywords.

mingdao blushes
-- 
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting



Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Alan McKinnon
On 05/11/2013 14:11, Marc Joliet wrote:
 Am Tue, 05 Nov 2013 12:14:59 +0200
 schrieb Alan McKinnon alan.mckin...@gmail.com:
 
 On 05/11/2013 11:52, Martin Vaeth wrote:
 Alan McKinnon alan.mckin...@gmail.com wrote:
 You know what? I'm not convinced.

 What I'm seeing is a rather large towering edifice of complexity to deal
 with a problem that is not the general case.

 I find it funny that perhaps you did not realize that you repeated
 the main argument *in favour of subslots* on the dev mailing list:


 It seems to me that you didn't read the whole post fully, and have
 cherry-picked a part that you think bolsters your position. It does not.
 So I will repeat myself in a different way.

 I've run emerge -e world with the result of correcting something perhaps
 2 or 3 times in 8 years. Let's assume that in the absence of portage
 being able to detect those nasty errors, that this is reasonably
 representative of the actual incidence of actual errors I encountered.
 Let's then be generous and triple it.

 In effect subslots appear to fix something for me about once a year. Is
 my logic^Wguess flawed in any way?
 
 For *you*! You are not everyone, although I'm sure you already know that ;) .
 See my Haskell example below for when subslots fix something more often.
 
 So now we have a rather large complex system that deals with what is
 essentially a minor problem that occurs say once a year.

 I completely understand the problem sub-slots is trying to solve. I'm
 just wondering if the methodology you are using to do it is valid, and
 if it does not become the cure that is worse than the disease.

 Consider for a moment the maintenance burden imposed on ebuild
 maintainers, and how sub-slot notation is essentially added by humans
 deploying human brains. And remember that humans are notoriously bad at
 using mathematically correct solutions (they ... err ... forget to do
 stuff).

 sub-slots, whilst quite likely mathematically correct, has all the
 hallmarks to me of SOMETHING THAT IS GOING TO FAIL DUE TO HUMANS. And
 humans seldom do those things that they should do . If this were not so,
 php would never have been written (just an arb random example)

 I predict once a week fallout from sub-slots induced bugs that was
 intended to fix once a year problem.

 Do you now see why I'm not convinced this is a real-world solution?
 
 I think I see your point, but what is the worst that can happen if somebody
 gets a subslot wrong? Since too *many* rebuilds aren't all too terrible (a
 waste of time for sure, and potentially annoying, but it won't outright break
 anything), I suppose the worst case is too *few* automatic rebuilds, right? So
 to me it sounds like you want to throw out the feature altogether because it
 won't *always* catch everything. Or what potential bugs are you thinking about
 that aren't useless rebuilds? I don't remember any from this thread, but of
 course I could have missed something.



I too see your viewpoint, as you see mine. There's nothing wrong with
your logic within the narrow domain of making the code that implements
this specific feature (subslots) work correctly per spec.

Background: I'm a Linux sysadmin by day at an ISP. I constantly have to
contend with Devs and Devops writing bespoke code to implement business
rules. Because I sit three feet back from the problem, I can almost
always see the flaws with the solution. I can't give much details
unfortunately, my employer owns the code. But I get to be very very good
at spotting code that runs per spec, but is very brittle in the real
world. I look for tells like this:

- is the dev trying to get code deployed that is not fully tested?
- is the dev trying to ignore or minimize the real world effect on other
systems?
- can the dev show that someone else (not him) can actually maintain it,
configure it and understand it?
- Can every single person in his team rattle off the primary salient
points of the code without thinking much?
- Did the team who write the code write a doc on how to configure it,
and how to deal with possible failures they anticipate?
- If someone else (like eg me) gets this wrong and I make mistakes while
deploying, how will I know I've made a mistake? Do I get a sane error
message that a) describes the error in simple language and b) does not
make the fatal mistake of exposing the underlying implementation in
error messages?
- Do I need to read the code itself to gain even a high level
understanding of what the code does?

By now you will have guessed that nearby Dev team hate my guts with a
passion. Unlucky for them, I'm root and they ain't. Lucky for them, I'm
quite reasonable and happy to work together to get the questions
answered. With an answer of some kind, we can assess risk and make a
rational choice. Oftentimes it comes down to we write one detailed
technical doc and allay all fears.

I don't see these questions being answered wrt subslots. Maybe they were
answered and I haven't seen the link yet, 

Re: [gentoo-user] Qt blocking @world update

2013-11-05 Thread Alan McKinnon
On 05/11/2013 15:37, Alex Schuster wrote:
 Portage and the tree by itself isn't doing it, here's my output:

 $ emerge -pvt fsrunner

 These are the packages that would be merged, in reverse order:

 Calculating dependencies... done!
 [ebuild  N ] kde-misc/fsrunner-0.7.5:4  USE=(-aqua) -debug 18 kB

 Total: 1 package (1 new), Size of downloads: 18 kB
 
 Same here, except that it's emerged already.
 
 OK, I have no clue how to further debug this. But what I did is:
 
 for (( i=500; i  0; i-=20 ))
 do
   emerge -DautvNj $( head -n $i /var/lib/portage/world )
 done
 
 This failed until $i was 260, so I tried a little more, and removed
 media-sound/kid3 from @world. Along with fsrunner of course. Now, it's
 building.
 
 This does not make any sense, does it?
 


Actually, it does make sense, in a weird kind of way

kid3 and fsrunner are not part of KDE proper (i.e. they are not shipped
in the huge KDE tarballs). So they may be inconsistent with the main
release due to no QA checks beyond what the dev does. And I doubt the
gentoo KDE team checks such packages before updating ebuilds.

I would use this approach:

Remove from world every KDE package that is not in kde-base (quickpkg
first to make restores easier), then update world and do a depclean.
Chances are very good it will complete cleanly.

Then emerge all those KDE packages back in using the -t option to emerge
and see what is causing issues.

I think the odds are very good you will find an out-of-sync package that
directly DEPENDS on some old version of Qt (or something equally silly).
That package might even already be in the emerge output, but buried in
the voluminous output portage gives these days

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Bruce Hill
On Tue, Nov 05, 2013 at 04:44:43PM +0200, Alan McKinnon wrote:
 
 I too see your viewpoint, as you see mine. There's nothing wrong with
 your logic within the narrow domain of making the code that implements
 this specific feature (subslots) work correctly per spec.
 
 Background: I'm a Linux sysadmin by day at an ISP. I constantly have to
 contend with Devs and Devops writing bespoke code to implement business
 rules. Because I sit three feet back from the problem, I can almost
 always see the flaws with the solution. I can't give much details
 unfortunately, my employer owns the code. But I get to be very very good
 at spotting code that runs per spec, but is very brittle in the real
 world. I look for tells like this:
 
 - is the dev trying to get code deployed that is not fully tested?
 - is the dev trying to ignore or minimize the real world effect on other
 systems?
 - can the dev show that someone else (not him) can actually maintain it,
 configure it and understand it?
 - Can every single person in his team rattle off the primary salient
 points of the code without thinking much?
 - Did the team who write the code write a doc on how to configure it,
 and how to deal with possible failures they anticipate?
 - If someone else (like eg me) gets this wrong and I make mistakes while
 deploying, how will I know I've made a mistake? Do I get a sane error
 message that a) describes the error in simple language and b) does not
 make the fatal mistake of exposing the underlying implementation in
 error messages?
 - Do I need to read the code itself to gain even a high level
 understanding of what the code does?

That is good practice, to say the least. Wish it would happen in Gentoo. But
then again, may I ask, do you have as many devs and as many pkgs that must
co-exist on so many differently configured machines?

My take is something like that should be implemented in Gentoo. But then, I
came from to Gentoo after 7+ years in Slackware. It happened your way there,
also, because of a BDFL. We don't have such in Gentoo.

The fact that 16939 packages in Gentoo mostly always work is amazing! Which
requires a lot of hands on deck; and they don't all have the same skills.

 By now you will have guessed that nearby Dev team hate my guts with a
 passion. Unlucky for them, I'm root and they ain't. Lucky for them, I'm
 quite reasonable and happy to work together to get the questions
 answered. With an answer of some kind, we can assess risk and make a
 rational choice. Oftentimes it comes down to we write one detailed
 technical doc and allay all fears.
 
 I don't see these questions being answered wrt subslots. Maybe they were
 answered and I haven't seen the link yet, maybe not. Maybe senior devs
 with clue have thus far successfully modified ebuilds, maybe not. Maybe
 more junior devshave yet to take their first steps, and maybe they will
 royally screw things up by not understanding the syntax, or maybe not.
 
 These questions have not been answered and I certainly don't have
 answers; I also think neither do you. I would like to see this feature
 extensively tested in de and stage before it hits production. Only then
 can I decide for myself if subslots are a good solution to the stated
 problem.

I've asked a very specific question about subslot philosophy as it pertains to
a specific situation on gentoo-dev.
-- 
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting



[gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Martin Vaeth
Alan McKinnon alan.mckin...@gmail.com wrote:

 It seems to me that you didn't read the whole post fully, and have
 cherry-picked a part that you think bolsters your position.

I do not think that I have a position here.
Subslots solve some problem.  If they cause inconveniences
like portage needing too long or frequent reemerges,
these issues should be attacked separately.

 I've run emerge -e world with the result of correcting something perhaps
 2 or 3 times in 8 years.

You *realized* the necessity 2-3 times in 8 years.
For a production system one usually does not want an unrecognized
breakage ever.

 In effect subslots appear to fix something for me about once a year.

Given that on a production system you would have something
seriously broken once a year which is not the case with
subslots, I would say they have reached their goal.

 So now we have a rather large complex system

It is not complex at all: Except taking the dependency string
directly from the metadata it is before modified with information
from /var/db, and during merging the corresponding information
is stored in /var/db. Nothing magic is going on.

I think there is mainly a perception problem:
Whenever there is a problem with dependencies now subslots
are blamed, because they are shown by portage first.
In my experience, all these problems were just usual dependency
problems which just happen from to time and will always happen -
not related with subslots at all.

 Consider for a moment the maintenance burden imposed on ebuild
 maintainers

If your package provides a library and you bump the version
you also bump the subslot except if you happen to know for
sure that the library remains ABI-compatible. If you are short
on time this is a matter of seconds, if you are more careful
and want to do an excellent work you can remember
upstream's policy to save the user from an unnecessary rebuild.

 and how sub-slot notation is essentially added by humans
 deploying human brains. And remember that humans are notoriously bad at
 using mathematically correct solutions (they ... err ... forget to do
 stuff).

Yes, somebody might make a mistake and forget to bump
or do an unnecessary bump. So what? All sort of
mistakes can happen everywhere which can lead to all sort
of problems.

 I predict once a week fallout from sub-slots induced bugs that was
 intended to fix once a year problem.

Let's see: Forgetting to bump a subslot means that the purpose of
subslots for that package fails. A problem, but not worse than
without subslots. Bumping unnecessarily means that perhaps some
packages are rebuilt unnecessarily. Also not something dramatic.
Even if this *should* happen once a week (which I strongly doubt;
more realistic is once in a few months) nothing dramatic happens.




Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Alan McKinnon
On 05/11/2013 17:21, Bruce Hill wrote:
 That is good practice, to say the least. Wish it would happen in Gentoo. But
 then again, may I ask, do you have as many devs and as many pkgs that must
 co-exist on so many differently configured machines?

Not even close :-)

What we lack in package diversity we more than make up for with
business requirements; where in this context business requirements
somehow gets redefined to license to do whatever the blazes you feel
like doing sans oversight.

Gentoo has a strong undercore of people who have all the reasons in the
world to do it right, without bean-counter interference. That alone
probably accounts for the miracle that it all somehow still works.
 
 My take is something like that should be implemented in Gentoo. But then, I
 came from to Gentoo after 7+ years in Slackware. It happened your way there,
 also, because of a BDFL. We don't have such in Gentoo.
 
 The fact that 16939 packages in Gentoo mostly always work is amazing! Which
 requires a lot of hands on deck; and they don't all have the same skills.

Indeed. All the more reason for peer pressure to lean in the direction
of doing it right and closely looking at the full impact on the entire
big picture. I know I'm whinging a bit on this topic right now, but also
feel it's appropriate to metnion that Gentoo does have an admirable
success track record over the years.

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Alan McKinnon
On 05/11/2013 20:06, Martin Vaeth wrote:
 I predict once a week fallout from sub-slots induced bugs that was
  intended to fix once a year problem.
 Let's see: Forgetting to bump a subslot means that the purpose of
 subslots for that package fails. A problem, but not worse than
 without subslots. Bumping unnecessarily means that perhaps some
 packages are rebuilt unnecessarily. Also not something dramatic.
 Even if this *should* happen once a week (which I strongly doubt;
 more realistic is once in a few months) nothing dramatic happens.
 
 

Why am I still feeling that I am not being understood correctly?

You don't have to keep explaining subslots to me, I understand how they
work and what they aim to accomplish:

DEPEND is a forward dependency and cannot deal with reverse
dependencies. Subslots provide the information to portage to be able to
deal with reverse dependencies when generating the dep graph. It does
not do it by interrogating the live filesystem or by discovery, it does
it by using metadata added to the ebuild by a human.

I know that if subslots are correctly defined throughout the tree,
rebuilds will happen during the emerge, and a later @preserved-rebuild
or revdep-rebuild will in all likelihood return null. I have no problem
with any of that, so there's no need to justify those claims further.

What I have maintained all along is that I don't see the solution as
tested to be production-ready and no-one has definitively stated what
can happen when a junior dev gets it spectacularly wrong. This may or
may not turn out to be a real problem in real life , but it is an
anticipated one that deserves an answer.

Keep in mind the real world nature of what a bug usually turns out to
be: something the dev did not anticipate (actual code flaws being
comparatively rare)


-- 
Alan McKinnon
alan.mckin...@gmail.com




[gentoo-user] kernel guys sent me back here

2013-11-05 Thread Grant
I was referred back to my distro supplier for a kernel crash.  Isn't
that a kernel problem?

https://bugzilla.kernel.org/show_bug.cgi?id=62981

- Grant



Re: [gentoo-user] Re: resolving blocked packages [media-video/ffmpeg-1.2:0]

2013-11-05 Thread Mick
On Tuesday 05 Nov 2013 06:15:56 Nuno J. Silva (aka njsg) wrote:
 On 2013-11-05, Bruce Hill da...@happypenguincomputers.com wrote:
  On Mon, Nov 04, 2013 at 10:43:07PM +, Mick wrote:
  On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote:
   On 11/03/2013 02:27 AM, Daniel Campbell wrote:
For starters, you should probably merge package.keywords into
package.accept_keywords; the latter is the new standard name,
though Portage will likely support the old names for a while. Just
a heads-up on that.
   
   Thanks for a heads-up. I did as you suggested.
  
  Is there going to be a portage news article on this, or did I miss it?
  
  It wasn't two or three years ago...
  
  mingdao@server ~ $ eselect news read 5
  2012-09-09-make.conf-and-make.profile-move
  
Title make.conf and make.profile move
AuthorJorge Manuel B. S. Vicetto
jmbsvice...@gentoo.org Posted2012-09-09
Revision  1
  
  Starting next week, new stages will have make.conf and make.profile
  moved from /etc to /etc/portage. This is a change in the installation
  defaults, that will only affect new installs so it doesn't affect
  current systems.
  
  Current users don't need to do anything. But if you want to follow the
  preferred location, you may want to take the chance to move the files
  in your system(s) to the new location.
 
 But that's about make.conf, not about package.keywords.

Right and I created two symlinks to make sure that at least *I* can still find 
these files without having to fight against muscle memory.  I'm just checking 
if I need to create some more.  BTW, I am running mostly stable here, with the 
odd testing version thrown in for cheap thrills.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] do subslots improve user-experience?

2013-11-05 Thread Neil Bothwick
On Tue, 5 Nov 2013 08:29:59 -0600, Bruce Hill wrote:

 I can't understand the *need* for the new slot/subslot philosophy.

The need to it is clear. Previous methods worked by breaking things and
then fixing them, hopefully before the breakage became a problem,
whenever library APIs changed. Subslots are an attempt to deal with this
proactively by fixing the problems as they occur.

Whether subslots are the best way to do it, and whether the
implementation is ideal, as separate questions, but there is no doubt
that any system that relies on the existence of revdep-rebuild is
seriously flawed.

To my mind, the question is not are subslots needed but are they the
best solution to this problem.


-- 
Neil Bothwick

Most software is about as user-friendly as a cornered rat!


signature.asc
Description: PGP signature


Re: [gentoo-user] do subslots improve user-experience?

2013-11-05 Thread Bruce Hill
On Tue, Nov 05, 2013 at 09:28:05PM +, Neil Bothwick wrote:
 On Tue, 5 Nov 2013 08:29:59 -0600, Bruce Hill wrote:
 
  I can't understand the *need* for the new slot/subslot philosophy.
 
 The need to it is clear. Previous methods worked by breaking things and
 then fixing them, hopefully before the breakage became a problem,
 whenever library APIs changed. Subslots are an attempt to deal with this
 proactively by fixing the problems as they occur.
 
 Whether subslots are the best way to do it, and whether the
 implementation is ideal, as separate questions, but there is no doubt
 that any system that relies on the existence of revdep-rebuild is
 seriously flawed.
 
 To my mind, the question is not are subslots needed but are they the
 best solution to this problem.

You misread my statement, also. It is in alignment with your last sentence.
-- 
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting



Re: [gentoo-user] kernel guys sent me back here

2013-11-05 Thread Bruce Hill
On Tue, Nov 05, 2013 at 12:02:00PM -0800, Grant wrote:
 I was referred back to my distro supplier for a kernel crash.  Isn't
 that a kernel problem?
 
 https://bugzilla.kernel.org/show_bug.cgi?id=62981

The first thing for any crash is logs. And btw ... don't go to the Linux
kernel if you're running any Gentoo sys-kernel/* source. Only if you get your
source from kernel.org.
-- 
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting



Re: [gentoo-user] Does Acrobat Reader work for anyone?

2013-11-05 Thread Keith Dart
Re , Nikos Chantziaras said:
 Since quite a while ago (months), acroread stopped working.

Side note, evince works for me on ~amd64 for viewing pdf. It also seems
to work ok with fillable pdf.

https://projects.gnome.org/evince/



-- Keith




-- ~
   Keith Dart ke...@dartworks.biz
   public key: ID: 19017044
   http://www.dartworks.biz/
   =



[gentoo-user] app-text/poppler-0.24.3 fails to build

2013-11-05 Thread Norman Rieß
Hello,

poppler fails to build for me and i don't know why.
Does someone got an idea about this?

[ 97%] Building CXX object
qt4/src/CMakeFiles/poppler-qt4.dir/ArthurOutputDev.cc.o
cd
/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build/qt4/src
 /usr/bin/x86_64-pc-linux-gnu-g++  -DHAVE_CONFIG_H=1
-Dpoppler_qt4_EXPORTS  -DNDEBUG -Wall -Wcast-align -fno-exceptions
-fno-check-new -fno-common -ansi -Wnon-virtual-dtor -Woverloaded-virtual
-O2 -pipe  -fPIC
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3/fofi
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3/goo
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3/poppler
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build/poppler
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3/qt4/src
-I/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build/qt4/src
-I/usr/include/freetype2 -I/usr/include/qt4-o
CMakeFiles/poppler-qt4.dir/ArthurOutputDev.cc.o -c
/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3/qt4/src/ArthurOutputDev.cc
Traceback (most recent call last):
Traceback (most recent call last):
  File /usr/bin/g-ir-scanner, line 46, in module
  File /usr/bin/g-ir-scanner, line 46, in module
sys.exit(scanner_main(sys.argv))
  File /usr/lib64/gobject-introspection/giscanner/scannermain.py, line
404, in scanner_main
sys.exit(scanner_main(sys.argv))
  File /usr/lib64/gobject-introspection/giscanner/scannermain.py, line
404, in scanner_main
transformer = create_transformer(namespace, options)
transformer = create_transformer(namespace, options)
  File /usr/lib64/gobject-introspection/giscanner/scannermain.py, line
297, in create_transformer
  File /usr/lib64/gobject-introspection/giscanner/scannermain.py, line
297, in create_transformer
transformer.register_include(include_obj)
  File /usr/lib64/gobject-introspection/giscanner/transformer.py, line
131, in register_include
transformer.register_include(include_obj)
  File /usr/lib64/gobject-introspection/giscanner/transformer.py, line
131, in register_include
self._parse_include(filename)
self._parse_include(filename)
  File /usr/lib64/gobject-introspection/giscanner/transformer.py, line
203, in _parse_include
  File /usr/lib64/gobject-introspection/giscanner/transformer.py, line
203, in _parse_include
parser.parse(filename)
  File /usr/lib64/gobject-introspection/giscanner/girparser.py, line
60, in parse
parser.parse(filename)
  File /usr/lib64/gobject-introspection/giscanner/girparser.py, line
60, in parse
tree = parse(filename)
  File string, line 62, in parse
tree = parse(filename)
  File string, line 62, in parse
  File string, line 38, in parse
  File string, line 38, in parse
cElementTree.ParseError: syntax error: line 1, column 0
cElementTree.ParseError: syntax error: line 1, column 0
make[2]: *** [glib/Poppler-0.18.gir] Fehler 1
make[2]: Leaving directory
`/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build'
make[1]: *** [glib/CMakeFiles/gir-typelibs.dir/all] Fehler 2
make[1]: *** Warte auf noch nicht beendete Prozesse...
make[2]: *** [glib/Poppler-0.18.gir] Fehler 1
make[2]: Leaving directory
`/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build'
make[1]: *** [glib/CMakeFiles/gir-girs.dir/all] Fehler 2
Linking CXX shared library libpoppler-qt4.so
cd
/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build/qt4/src
 /usr/bin/cmake -E cmake_link_script
CMakeFiles/poppler-qt4.dir/link.txt --verbose=1
/usr/bin/x86_64-pc-linux-gnu-g++  -fPIC -Wall -Wcast-align
-fno-exceptions -fno-check-new -fno-common -ansi -Wnon-virtual-dtor
-Woverloaded-virtual -O2 -pipe   -Wl,-O1 -Wl,--as-needed -Wl,--as-needed
-shared -Wl,-soname,libpoppler-qt4.so.4 -o libpoppler-qt4.so.4.3.0
CMakeFiles/poppler-qt4.dir/poppler-annotation.cc.o
CMakeFiles/poppler-qt4.dir/poppler-document.cc.o
CMakeFiles/poppler-qt4.dir/poppler-embeddedfile.cc.o
CMakeFiles/poppler-qt4.dir/poppler-fontinfo.cc.o
CMakeFiles/poppler-qt4.dir/poppler-form.cc.o
CMakeFiles/poppler-qt4.dir/poppler-link.cc.o
CMakeFiles/poppler-qt4.dir/poppler-link-extractor.cc.o
CMakeFiles/poppler-qt4.dir/poppler-movie.cc.o
CMakeFiles/poppler-qt4.dir/poppler-optcontent.cc.o
CMakeFiles/poppler-qt4.dir/poppler-page.cc.o
CMakeFiles/poppler-qt4.dir/poppler-base-converter.cc.o
CMakeFiles/poppler-qt4.dir/poppler-pdf-converter.cc.o
CMakeFiles/poppler-qt4.dir/poppler-private.cc.o
CMakeFiles/poppler-qt4.dir/poppler-ps-converter.cc.o
CMakeFiles/poppler-qt4.dir/poppler-qiodeviceoutstream.cc.o
CMakeFiles/poppler-qt4.dir/poppler-sound.cc.o
CMakeFiles/poppler-qt4.dir/poppler-textbox.cc.o
CMakeFiles/poppler-qt4.dir/poppler-page-transition.cc.o
CMakeFiles/poppler-qt4.dir/poppler-media.cc.o
CMakeFiles/poppler-qt4.dir/ArthurOutputDev.cc.o
../../libpoppler.so.43.0.0 

[gentoo-user] Re: do subslots improve user-experience?

2013-11-05 Thread Martin Vaeth
Alan McKinnon alan.mckin...@gmail.com wrote:

 You don't have to keep explaining subslots to me

But not every reader knows the details - this is not a private
conversation.

 What I have maintained all along is that I don't see the solution as
 tested to be production-ready

It has been in ~arch for many months, and now it is becoming stable.
This is how testing works in gentoo.
As I tried to explain, even if devs do it wrong, there is not much
harm which can happen except for useless rebuilds or that the
advantage of subslots is missed by mistake.

In practice, it turns out that the portage error messages tend to
confuse users more now: The reason being that, although portage
would be able to resolve subslot dependencies automatically,
it does not show the resolved ones if it breaks before because of
an error, and so users see a lot of errors which actually are none
but occur only as a side effect of a completely different problem.
Although this behavior of portage happens not only for subslots,
the number of false positives has increased due to subslots.
This leads to the wrong perceiption which one can see in the forums.
  But misleading error messages due to non-finished resolving
were a problem which existed also before in portage and which
should be attacked anyway, if it can be.