Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Dantrell's GNOME Without Systemd Project (Part 3)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Sun Apr 14, 2019 11:52 pm    Post subject: Reply with quote

Elleni wrote:
ok, I removed gles2 useflag and tried to continue emerge, but soon stopped here:
http://dpaste.com/18GXGTB

Sync up and rebuild:

Code:
emerge --ask --oneshot --nodeps x11-libs/vte gnome-extra/gnome-boxes

Elleni wrote:
emerge @preserved-rebuild
http://dpaste.com/3J71B8Y

Oh boy, libsoup again.

What's the output of the following commands:

Code:
emerge --pretend --verbose net-libs/libsoup
or ls -l /usr/lib*/pkgconfig/libsoup-*.pc
pkg-config --modversion libsoup-2.4

Also, please share the full build output of libsoup as well so I can compare:

Code:
emerge --ask --oneshot --nodeps net-libs/libsoup

_________________
Dantrell B.
Back to top
View user's profile Send private message
runningnak3d
n00b
n00b


Joined: 05 Sep 2018
Posts: 39

PostPosted: Mon Apr 15, 2019 1:31 pm    Post subject: Reply with quote

Finally got around to testing, and the only problem that I ran into was a slotting problem with:

x11-libs/libwnck-2.31.0::dantrell-gnome which is needed by lxpanel.

It has a file collision with:

x11-libs/libwnck-3.31.4:3::dantrell-gnome-3-32

Code:

 * Detected file collision(s):
 *
 *    /usr/bin/wnckprop
 *    /usr/bin/wnck-urgency-monitor


For now I unmerged lxpanel, and everything else went fine.

I use nvidia-xrun and use lxpanel with openbox for a minimal DE to use with Steam. That way I don't have to deal with Bumblebee.

-- Brian
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Mon Apr 15, 2019 8:35 pm    Post subject: Reply with quote

dantrell wrote:

Sync up and rebuild:

Code:
emerge --ask --oneshot --nodeps x11-libs/vte gnome-extra/gnome-boxes

Oh boy, libsoup again.

What's the output of the following commands:

Code:
emerge --pretend --verbose net-libs/libsoup
or ls -l /usr/lib*/pkgconfig/libsoup-*.pc
pkg-config --modversion libsoup-2.4

Also, please share the full build output of libsoup as well so I can compare:

Code:
emerge --ask --oneshot --nodeps net-libs/libsoup


vte and gnome-boxes successfully built.

emerge --pretend --verbose net-libs/libsoup
Code:

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

Calculating dependencies                           ... done!
[ebuild   R    ] net-libs/libsoup-2.66.1-r1:2.4::dantrell-gnome-3-32  USE="gnome introspection ssl vala -doc -gssapi -samba -test" ABI_X86="32 (64) (-x32)" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

ls -l /usr/lib*/pkgconfig/libsoup-*.pc
Code:

-rw-r--r-- 1 root root 345 14. Apr 09:46 /usr/lib64/pkgconfig/libsoup-2.4.pc
-rw-r--r-- 1 root root 370 14. Apr 09:46 /usr/lib64/pkgconfig/libsoup-gnome-2.4.pc
-rw-r--r-- 1 root root 345 14. Apr 09:46 /usr/lib/pkgconfig/libsoup-2.4.pc
-rw-r--r-- 1 root root 370 14. Apr 09:46 /usr/lib/pkgconfig/libsoup-gnome-2.4.pc

pkg-config --modversion libsoup-2.4
Code:
2.66.1



libsoup build output.

I then proceeded with world update, and it went well quite far, but fails @geary
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 12:30 am    Post subject: Reply with quote

runningnak3d wrote:
Finally got around to testing, and the only problem that I ran into was a slotting problem with:

x11-libs/libwnck-2.31.0::dantrell-gnome which is needed by lxpanel.

It has a file collision with:

x11-libs/libwnck-3.31.4:3::dantrell-gnome-3-32

As per upstream, they can be installed in parallel but the latter must have the tools USE flag disabled.

I don't turn it on so maybe check your end?

Elleni wrote:
libsoup build output.

Thanks, a quick look shows (yours):

Code:
Native C compiler: x86_64-pc-linux-gnu-gcc (gcc 8.2.0 "x86_64-pc-linux-gnu-gcc (Gentoo 8.2.0-r6 p1.7) 8.2.0")
Found pkg-config: /usr/bin/x86_64-pc-linux-gnu-pkg-config (0.29.2)
Dependency libpsl found: YES 0.20.1
Found ninja-1.8.2 at /usr/bin/ninja
>>> needed    sym /usr/lib32/libsoup-2.4.so.1
>>> needed    obj /usr/lib32/libsoup-2.4.so.1.8.0

vs (mine):

Code:
Native C compiler: x86_64-pc-linux-gnu-gcc (gcc 8.3.0 "x86_64-pc-linux-gnu-gcc (Gentoo 8.3.0-r1 p1.1) 8.3.0")
Found pkg-config: /usr/bin/x86_64-pc-linux-gnu-pkg-config (1.5.4)
Dependency libpsl found: YES 0.20.2
Found ninja-1.9.0.git.kitware.dyndep-1.jobserver-1 at /usr/bin/ninja

Still not sure if this confirms my current guess that your issue is lib32 related, investigating further as we speak.

Elleni wrote:
I then proceeded with world update, and it went well quite far, but fails @geary

This looks like upstream needs to raise their libgee dependency requirement.

Please confirm with:

Code:
ACCEPT_KEYWORDS="~amd64" emerge --ask --nodeps dev-libs/libgee mail-client/geary

_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Tue Apr 16, 2019 4:35 am    Post subject: Reply with quote

dantrell wrote:

This looks like upstream needs to raise their libgee dependency requirement.

Please confirm with:

Code:
ACCEPT_KEYWORDS="~amd64" emerge --ask --nodeps dev-libs/libgee mail-client/geary


confirmed as this builds successfully.

The remaining files of emerge world -uDN did build successfully.

I proceeded with emerge --depclean, revdep-rebuild and emerge @preserved-rebuild.

The resulting/remaining fails are the following:
gssdp:
http://dpaste.com/2F3XY53
rest:
http://dpaste.com/0YEED0J
gupnp:
http://dpaste.com/1S78WXH
california - where the emerge does not stop failed but I stopped it with Ctrl+C as it seems to hang in a loop as console repeatingly showing
Code:

Goa-1.0.gir:20967.1-20967.0: warning: expected end element of `type'


Goa-1.0.gir:20967.1-20967.0: error: unexpected end of file


Goa-1.0.gir:20967.1-20967.0: warning: expected end element of `type'


Goa-1.0.gir:20967.1-20967.0: error: unexpected end of file


Goa-1.0.gir:20967.1-20967.0: warning: expected end element of `type'


Goa-1.0.gir:20967.1-20967.0: error: unexpected end of file


Last edited by Elleni on Tue Apr 16, 2019 5:06 am; edited 2 times in total
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 5:01 am    Post subject: Reply with quote

Elleni wrote:
confirmed as this builds successfully

Thanks for confirming.

I have made this live on my end.

dantrell wrote:
Still not sure if this confirms my current guess that your issue is lib32 related, investigating further as we speak.

I'm pretty sure it is lib32 related and I think I have a fix in place. Sync up and try:

Code:
emerge --ask --oneshot --nodeps net-libs/libsoup net-libs/gssdp net-libs/rest

_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Tue Apr 16, 2019 5:22 am    Post subject: Reply with quote

result:
http://dpaste.com/339YZSF
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 5:35 am    Post subject: Reply with quote

Elleni wrote:
result:
http://dpaste.com/339YZSF

Sync up once more:

Code:
emerge --ask --oneshot --nodeps net-libs/libsoup net-libs/gssdp net-libs/rest

:twisted:
_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Tue Apr 16, 2019 6:26 am    Post subject: Reply with quote

This time those three package built successfully. 8)

Emerge california (only remaining package that emerge @preserved-rebuild wants to build) still has this loop as posted above.
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 6:51 am    Post subject: Reply with quote

Elleni wrote:
This time those three package built successfully. 8)

Nice, I wasn't worried at all. :lol:

Elleni wrote:
Emerge california (only remaining package that emerge @preserved-rebuild wants to build) still has this loop as posted above.

This one seems related to GNOME Online Accounts.

Please share the full build output of both packages if the following fails:

Code:
emerge --ask --oneshot --nodeps --verbose net-libs/gnome-online-accounts gnome-extra/california

_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Tue Apr 16, 2019 10:55 am    Post subject: Reply with quote

I could emerge gnome-onlineaccounts successfully, but I dont know how to present a build log of california as the file gets immediatelly too large so partially following build log by opening it with nano and copy/pasting:

Code:
^[[32;01m * ^[[39;49;00mPackage:    gnome-extra/california-0.4.0-r2
^[[32;01m * ^[[39;49;00mRepository: dantrell-gnome
^[[32;01m * ^[[39;49;00mUSE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
^[[32;01m * ^[[39;49;00mFEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking california-0.4.0.tar.xz to /var/tmp/portage/gnome-extra/california-0.4.0-r2/work
>>> Source unpacked in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work
>>> Preparing source in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0 ...
 ^[[32;01m*^[[0m Applying california-0.4.0-fix-build-with-evolution-data-server-3.13.90.patch ...
^[[A^[[110C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m Applying california-0.4.0-fix-build-with-libical-3.0.patch ...
^[[A^[[110C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m Disabling deprecation warnings ...
^[[A^[[110C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 * Running elibtoolize in: california-0.4.0/
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0 ...
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/do$
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking for valac... /usr/bin/valac-0.32
checking for valac... (cached) /usr/bin/valac-0.32
checking whether /usr/bin/valac-0.32 is at least version 0.24.0... yes
checking for glib-compile-resources... /usr/bin/glib-compile-resources
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.51.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/gmsgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.26.2
checking for XML::Parser... ok
checking for x86_64-pc-linux-gnu-pkg-config... /usr/bin/x86_64-pc-linux-gnu-pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CALIFORNIA... yes
checking for x86_64-pc-linux-gnu-pkg-config... (cached) /usr/bin/x86_64-pc-linux-gnu-pkg-config
checking pkg-config is at least version 0.16... yes
checking whether ln -s works... yes
checking for itstool... itstool
checking for xmllint... xmllint
checking for _NL_TIME_FIRST_WEEKDAY... yes
checking for xdg-email... yes
checking Unity support... no
checking fatal Vala warnings... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating po/Makefile.in
config.status: creating help/Makefile
config.status: creating data/california.desktop.in
config.status: creating config/config.h
config.status: executing depfiles commands
config.status: executing po/stamp-it commands

Options:
        Unity support:          no
        Fatal Vala warnings:    yes

>>> Source configured.
>>> Compiling source in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0 ...
make -j13
Building local GSettings schema...
make  all-recursive
make[1]: Verzeichnis „/var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0“ wird betreten
Making all in src
rm -f california_vala.stamp && echo stamp > california_vala.stamp-t
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac-0.32 --debug --enable-checking --vapidir ../vapi --target-glib=2.38 --enable-deprecated --gresources=california-resources.xml  --define HAVE__NL_TIME_FIRST_WEEKDAY --fatal-warnings --pkg gtk+-3.0 --pkg gio-2.0 --pkg p$
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../config  -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cair$
^[[001mGoa-1.0.gir:26.7-26.42:^[[0m ^[[001;31merror:^[[0m unknown child element ^[[001m`source-position'^[[0m in ^[[001m`interface'^[[0m
      <source-position filename="goa-generated.h" line="85"/>
      ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:32.9-32.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <source-position filename="goa-generated.h" line="89"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:33.9-33.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:46.9-46.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <source-position filename="goa-generated.h" line="90"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:47.9-47.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:53.9-53.8:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <parameters>
        ^[[001;32m^[[0m
^[[001mGoa-1.0.gir:618.9-618.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m
        <source-position filename="goa-generated.h" line="33"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:619.9-619.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:622.9-622.8:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m

(...)

rm -f california_vala.stamp && echo stamp > california_vala.stamp-t
CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac-0.32 --debug --enable-checking --vapidir ../vapi --target-glib=2.38 --enable-deprecated --gresources=california-resources.xml  --define HAVE__NL_TIME_FIRST_WEEKDAY --fatal-warnings --pkg gtk+-3.0 --pkg gio-2.0 --pkg p$
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../config  -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cair$
^[[001mGoa-1.0.gir:26.7-26.42:^[[0m ^[[001;31merror:^[[0m unknown child element ^[[001m`source-position'^[[0m in ^[[001m`interface'^[[0m
      <source-position filename="goa-generated.h" line="85"/>
      ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:32.9-32.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <source-position filename="goa-generated.h" line="89"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:33.9-33.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:46.9-46.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <source-position filename="goa-generated.h" line="90"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:47.9-47.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:53.9-53.8:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`function'^[[0m
        <parameters>
        ^[[001;32m^[[0m
^[[001mGoa-1.0.gir:618.9-618.44:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m
        <source-position filename="goa-generated.h" line="33"/>
        ^[[001;32m^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:619.9-619.17:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m
        <return-value transfer-ownership="none">
        ^[[001;32m^^^^^^^^^^[[0m
^[[001mGoa-1.0.gir:622.9-622.8:^[[0m ^[[001;35mwarning:^[[0m expected end element of ^[[001m`virtual-method'^[[0m
Back to top
View user's profile Send private message
runningnak3d
n00b
n00b


Joined: 05 Sep 2018
Posts: 39

PostPosted: Tue Apr 16, 2019 1:00 pm    Post subject: Reply with quote

runningnak3d wrote:
Finally got around to testing, and the only problem that I ran into was a slotting problem with:

x11-libs/libwnck-2.31.0::dantrell-gnome which is needed by lxpanel.

It has a file collision with:

x11-libs/libwnck-3.31.4:3::dantrell-gnome-3-32


dantrell wrote:

As per upstream, they can be installed in parallel but the latter must have the tools USE flag disabled.

I don't turn it on so maybe check your end?



You were absolutely correct sir. Thank you very much for pointing out the problem. I have several other packages that need the tools USE flag, so I removed it for libwnck and they slot together nicely now. What is strange is that I added the tools flag back when I built my system, and didn't run into this in 3.28 or the upgrade to 3.30, and I had lxpanel installed the whole time. Did you perhaps explicitly remove the flag from the older libs needed by 3.28 and 3.30?

EDIT: actually after some quick digging, it looks like in 3.30 you renamed the libwnck-3 tools so that they didn't collide with libwnck-2. This is a very minor issue, but just thought you might be interested in how you were doing it.

Thank you VERY much for you prompt replies. You are a mad man ;)

-- Brian
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 7:47 pm    Post subject: Reply with quote

Elleni wrote:
I could emerge gnome-onlineaccounts successfully, but I dont know how to present a build log of california as the file gets immediatelly too large so partially following build log by opening it with nano and copy/pasting: [...]

This is fine.

I would like the full build output for the successful net-libs/gnome-online-accounts emerge too.

runningnak3d wrote:
EDIT: actually after some quick digging, it looks like in 3.30 you renamed the libwnck-3 tools so that they didn't collide with libwnck-2. This is a very minor issue, but just thought you might be interested in how you were doing it.

Before libwnck moved to the Meson build system, there was a --program-suffix= configure option in place. I could mimic the behaviour but I'm not sure that's the best option.

For instance, Arch Linux removes the libwnck-2 tools in favor of the the libwnck-3 tools but if I do that here then libwnck-3 needs to become a dependency of libwnck-2 to ensure tools are pulled in.

On the other hand, I checked lxpanel and it looks like it can build with both series of libwnck but there are still ~12 packages in the main tree that want the older version.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Tue Apr 16, 2019 8:02 pm    Post subject: Reply with quote

dantrell wrote:

I would like the full build output for the successful net-libs/gnome-online-accounts emerge too.


https://bpaste.net/show/4e9e6451c470
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Tue Apr 16, 2019 8:05 pm    Post subject: Reply with quote

dantrell wrote:
Shibotto wrote:
Also there are... "things" :lol:

Oh no.

I'm yet to sort everything out (time flies when your hardware is obsolete :lol: ), but I guess it's about time I report something.

dantrell wrote:
If one of them was about the invisible GNOME Terminal icon, it's back now.[/size]

This actually never were a problem for me using default Adwaita, so I made a comparison screenshot. I don't love or hate either of them, so I guess it's up to personal preference¯\_(ツ)_/¯



Now, the first problem I noticed was about some GTK applications not getting focus when launched. Contrary to what the issue says, gnome-terminal works as expected for me, but Nautilus and some other things I can't remember (sorry :oops:) don't.
This has been addressed upstream, but the fix will be included in mutter 3.32.1, which is not out yet. So here's the patch out of the merge request; I've been using it for a couple of days and it seems fine.



The next one was about sci-geosciences/geoclue-glib-3.26.0 crashing badly when geocoding certain locations, of course including my home :lol:.
Upgrading to 3.26.1 (currently ~*) fixed the crash for me. It still have problems getting some locations (of course including my home, again :lol:), but at least it stops segfaulting applications using it. I'll keep an eye on this.

This was particularly tricky to find, because the initial symptom was gnome-calendar crashing. It took me a while and casually messing with gnome-weather to realize that gnome-calendar also gives you 3 days weather forecasts and the two things might be related.
Back to top
View user's profile Send private message
runningnak3d
n00b
n00b


Joined: 05 Sep 2018
Posts: 39

PostPosted: Tue Apr 16, 2019 8:45 pm    Post subject: Reply with quote

dantrell wrote:

runningnak3d wrote:
EDIT: actually after some quick digging, it looks like in 3.30 you renamed the libwnck-3 tools so that they didn't collide with libwnck-2. This is a very minor issue, but just thought you might be interested in how you were doing it.

Before libwnck moved to the Meson build system, there was a --program-suffix= configure option in place. I could mimic the behaviour but I'm not sure that's the best option.

For instance, Arch Linux removes the libwnck-2 tools in favor of the the libwnck-3 tools but if I do that here then libwnck-3 needs to become a dependency of libwnck-2 to ensure tools are pulled in.

On the other hand, I checked lxpanel and it looks like it can build with both series of libwnck but there are still ~12 packages in the main tree that want the older version.

[/quote]

I am sure the number of people that would ever run into this are -- well -- probably just me. I mean how many people have Gnome installed and use lxpanel? ;) Granted, I don't use lxpanel WITH Gnome, just have it installed for use in a secondary X display.

On a different note, since the upgrade to 3.32, if I suspend my laptop, it won't wake up -- can't even switch to another TTY. However, it isn't completely frozen because I can ssh in and restart gdm.

I haven't had a chance to roll back to 3.30 and then ONLY upgrade Gnome to see if the problem is with 3.32, or maybe there was something else that got pulled in when I did the upgrade to 3.32. I shouldn't have upgraded world for the switch -- that was my bad.

I will try to roll back in the next day or two and see.

-- Brian
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Tue Apr 16, 2019 11:22 pm    Post subject: Reply with quote

Elleni wrote:
https://bpaste.net/show/4e9e6451c470

Thanks, currently investigating.

Shibotto wrote:
This actually never were a problem for me using default Adwaita, so I made a comparison screenshot. I don't love or hate either of them, so I guess it's up to personal preference¯\_(ツ)_/¯

I tested it like 15+ times and I swear it was invisible but I just tested it again and now it shows up. ¯\_(ツ)_/¯

For now, I put the change behind the vanilla-icon USE flag and turned it on by default.

Shibotto wrote:
Now, the first problem I noticed was about some GTK applications not getting focus when launched. Contrary to what the issue says, gnome-terminal works as expected for me, but Nautilus and some other things I can't remember (sorry :oops:) don't.
This has been addressed upstream, but the fix will be included in mutter 3.32.1, which is not out yet. So here's the patch out of the merge request; I've been using it for a couple of days and it seems fine.

Patched.

Shibotto wrote:
The next one was about sci-geosciences/geoclue-glib-3.26.0 crashing badly when geocoding certain locations, of course including my home :lol:.
Upgrading to 3.26.1 (currently ~*) fixed the crash for me. It still have problems getting some locations (of course including my home, again :lol:), but at least it stops segfaulting applications using it. I'll keep an eye on this.

Stabilized.

Shibotto wrote:
This was particularly tricky to find, because the initial symptom was gnome-calendar crashing. It took me a while and casually messing with gnome-weather to realize that gnome-calendar also gives you 3 days weather forecasts and the two things might be related.

Consulting a meteorologist.

runningnak3d wrote:
On a different note, since the upgrade to 3.32, if I suspend my laptop, it won't wake up -- can't even switch to another TTY. However, it isn't completely frozen because I can ssh in and restart gdm.

This one I'm not sure about so I'll review things on my end and wait to see how your rollback goes.
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 434
Location: Brazil

PostPosted: Tue Apr 16, 2019 11:57 pm    Post subject: Reply with quote

I won't be a part of the early bird task force this time, too many things on my plate to risk breakage right now. But, once again, thanks for you hard work dantrell.
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Thu Apr 18, 2019 8:32 am    Post subject: Reply with quote

Quick fix for gnome-builder: I think this line should be removed, since the clang plugin is controlled by a meson_use a few lines above.

EDIT: also media-video/pipewire seems to depend on many more things, including media-libs/libv4l (which I didn't have). I found it in this meson.build, which I'm not sure whether it's optional plugins or mandatory. Sorry I'm vague and inaccurate, I'm doing this in a hurry :P
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Thu Apr 18, 2019 4:17 pm    Post subject: Reply with quote

The problem with california is the old (obsolete) vala-0.32 not handling some newer gir properties, in this case "source-position". This property gets ignored in recent vala versions, but california seems to be half dead and doesn't compile with recent vala.

Anyway, here's a patch for the converted C code used in vala release tarballs, which can be applied to dev-lang/vala-0.32.1 and fixes california compilation.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Thu Apr 18, 2019 8:11 pm    Post subject: Reply with quote

Hi Shibotto and thanks for helping.

I don't know if this is the correct way to apply your provided patch. I created /etc/patches/gnome-extra/california folder and added a file california-0.4.0-r2 with the content of your patch.

Portage tried to apply it but failed with:
Code:
>>> Emerging (1 of 1) gnome-extra/california-0.4.0-r2::dantrell-gnome
 * california-0.4.0.tar.xz BLAKE2B SHA512 size ;-) ...                                                         [ ok ]
>>> Unpacking source...
>>> Unpacking california-0.4.0.tar.xz to /var/tmp/portage/gnome-extra/california-0.4.0-r2/work
>>> Source unpacked in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work
>>> Preparing source in /var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0 ...
 * Applying california-0.4.0-fix-build-with-evolution-data-server-3.13.90.patch ...                            [ ok ]
 * Applying california-0.4.0-fix-build-with-libical-3.0.patch ...                                              [ ok ]
 * Applying california-0.4.0-r2.patch ...
The text leading up to this was:
--------------------------
|diff -Nuar a/vala/valagirparser.c b/vala/valagirparser.c
|--- a/vala/valagirparser.c     2016-06-20 20:26:53.000000000 +0200
|+++ b/vala/valagirparser.c     2019-04-18 13:07:10.582783799 +0200
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored                                                                                       [ !! ]
 * ERROR: gnome-extra/california-0.4.0-r2::dantrell-gnome failed (prepare phase):
 *   patch -p1  failed with /etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch
 *
 * Call stack:
 *               ebuild.sh, line  124:  Called src_prepare
 *             environment, line 2660:  Called gnome2_src_prepare
 *             environment, line 1881:  Called xdg_src_prepare
 *             environment, line 3788:  Called default
 *      phase-functions.sh, line  868:  Called default_src_prepare
 *      phase-functions.sh, line  933:  Called __eapi6_src_prepare
 *             environment, line  249:  Called eapply_user
 *             environment, line  631:  Called eapply '/etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *             environment, line  601:  Called _eapply_patch '/etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *             environment, line  539:  Called __helpers_die 'patch -p1  failed with /etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *   isolated-functions.sh, line  119:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=gnome-extra/california-0.4.0-r2::dantrell-gnome'`,
 * the complete build log and the output of `emerge -pqv '=gnome-extra/california-0.4.0-r2::dantrell-gnome'`.
 * The complete build log is located at '/var/tmp/portage/gnome-extra/california-0.4.0-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-extra/california-0.4.0-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0'
 * S: '/var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0'

>>> Failed to emerge gnome-extra/california-0.4.0-r2, Log file:

>>>  '/var/tmp/portage/gnome-extra/california-0.4.0-r2/temp/build.log'

 * Messages for package gnome-extra/california-0.4.0-r2:

 * ERROR: gnome-extra/california-0.4.0-r2::dantrell-gnome failed (prepare phase):
 *   patch -p1  failed with /etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch
 *
 * Call stack:
 *               ebuild.sh, line  124:  Called src_prepare
 *             environment, line 2660:  Called gnome2_src_prepare
 *             environment, line 1881:  Called xdg_src_prepare
 *             environment, line 3788:  Called default
 *      phase-functions.sh, line  868:  Called default_src_prepare
 *      phase-functions.sh, line  933:  Called __eapi6_src_prepare
 *             environment, line  249:  Called eapply_user
 *             environment, line  631:  Called eapply '/etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *             environment, line  601:  Called _eapply_patch '/etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *             environment, line  539:  Called __helpers_die 'patch -p1  failed with /etc/portage/patches/gnome-extra/california/california-0.4.0-r2.patch'
 *   isolated-functions.sh, line  119:  Called die
 * The specific snippet of code:
 *              die "$@"
 *
 * If you need support, post the output of `emerge --info '=gnome-extra/california-0.4.0-r2::dantrell-gnome'`,
 * the complete build log and the output of `emerge -pqv '=gnome-extra/california-0.4.0-r2::dantrell-gnome'`.
 * The complete build log is located at '/var/tmp/portage/gnome-extra/california-0.4.0-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-extra/california-0.4.0-r2/temp/environment'.
 * Working directory: '/var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0'
 * S: '/var/tmp/portage/gnome-extra/california-0.4.0-r2/work/california-0.4.0'


What am I doing wrongly?
Back to top
View user's profile Send private message
Shibotto
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2015
Posts: 109
Location: Italy

PostPosted: Thu Apr 18, 2019 8:40 pm    Post subject: Reply with quote

Elleni wrote:
What am I doing wrongly?

This solves an issue in the vala compiler, so you should put it in /etc/patches/dev-lang/vala-0.32.1
Next rebuild dev-lang/vala:0.32, then california should compile :D
Back to top
View user's profile Send private message
dantrell
Guru
Guru


Joined: 01 Jun 2007
Posts: 529
Location: Earth

PostPosted: Thu Apr 18, 2019 9:00 pm    Post subject: Reply with quote

saboya wrote:
I won't be a part of the early bird task force this time, too many things on my plate to risk breakage right now. But, once again, thanks for you hard work dantrell.

Completely understandable and thanks for the support.

Shibotto wrote:
Quick fix for gnome-builder: I think this line should be removed, since the clang plugin is controlled by a meson_use a few lines above.

Done.

Shibotto wrote:
EDIT: also media-video/pipewire seems to depend on many more things, including media-libs/libv4l (which I didn't have). I found it in this meson.build, which I'm not sure whether it's optional plugins or mandatory. Sorry I'm vague and inaccurate, I'm doing this in a hurry :P

I cross checked the list of dependencies against Arch Linux and only added media-libs/libv4l for now.

Shibotto wrote:
The problem with california is the old (obsolete) vala-0.32 not handling some newer gir properties, in this case "source-position". This property gets ignored in recent vala versions, but california seems to be half dead and doesn't compile with recent vala.

Nice work. :o

I would say I was madly investigating but since things slowed down so I took a couple days off.

Shibotto wrote:
Anyway, here's a patch for the converted C code used in vala release tarballs, which can be applied to dev-lang/vala-0.32.1 and fixes california compilation.

I reviewed this and it can be backported all the way to the 0.26 series but I only applied it to 0.32 for now.

Elleni wrote:
What am I doing wrongly?

Shibotto wrote:
This solves an issue in the vala compiler, so you should put it in /etc/patches/dev-lang/vala-0.32.1

This is live on my end now though. :P

Sync up and yada yada:

Code:
emerge --ask --oneshot --nodeps dev-lang/vala:0.32 gnome-extra/california

_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Thu Apr 18, 2019 9:15 pm    Post subject: Reply with quote

I parallelly did what Shibotto explained and can confirm success - thanks guys, you rock :D
Back to top
View user's profile Send private message
Elleni
l33t
l33t


Joined: 23 May 2006
Posts: 753

PostPosted: Sat Apr 20, 2019 2:11 pm    Post subject: Reply with quote

Now that everything compiled fine, I am looking at gnome 3.32 and here's my first problem :twisted:

How can I correct this, and what would be the default font for shell?
https://pasteboard.co/Ib1bKHa.jpg

Edit - found out: Had to go in terminal settings and activate userdefined font, that did the trick :)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum