| View previous topic :: View next topic |
| Author |
Message |
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
 Posted: Tue Apr 20, 2021 9:24 pm Post subject: |
 |
|
Not sure if intended or not, but aptx USE flag on pipewire has unstable deps:
| Code: | !!! All ebuilds that could satisfy "media-libs/libopenaptx" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-libs/libopenaptx-9999::gentoo (masked by: missing keyword)
- media-libs/libopenaptx-0.2.0::gentoo (masked by: ~amd64 keyword)
(dependency required by "media-video/pipewire-0.3.25::dantrell-gnome[bluetooth,aptx]" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
|
|
|
| Back to top |
|
 |
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Tue Apr 20, 2021 10:26 pm Post subject: |
|
|
| saboya wrote: | | Not sure if intended or not, but aptx USE flag on pipewire has unstable deps: [...] |
I did slot that version of PipeWire in ~ but I forgot I allow it through for stable regardless.
Looks like it's time for a bit of spring cleaning.
Stay tuned...
Edit: Sync up and you should be good to go.
You may see some downgrades where I opted to take the opportunity to match the revisions in the main tree but if something doesn't look right, just let me know.
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sat Apr 24, 2021 11:08 am Post subject: |
|
|
| dantrell wrote: | | simonvanderveldt wrote: | | Could it be because the dbus call is to NautilusPreviewer2 whereas sushi seems to register as NautilusPreviewer? |
It looks like the interface switch to NautilusPreviewer2 happened in 2019 so I'm not sure this is it.
I'll be clearing a few days to get some work in. My priority (in order) will be:
- Handling the remaining ebuilds using EAPI 5
- Adding support for GNOME 40.0
- Investigating the issue with the Nautilus previewer
Stay tuned. |
You're right, although it seems a bit strange that the names don't match up. Not sure what could be causing it then.
I've got another report, been getting this since I think about 3 of 4 days
| Code: | * Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(gui-libs/libhandy-1.0.3:1.0/0::dantrell-gnome, installed) pulled in by
>=gui-libs/libhandy-0.90.0:1.0/0= required by (media-gfx/gnome-screenshot-3.38.0:0/0::dantrell-gnome-3-38, installed) USE="" ABI_X86="(64)"
>=gui-libs/libhandy-0.90.0:1.0/0= required by (gnome-base/gnome-control-center-3.38.5:2/2::dantrell-gnome-3-38, installed) USE="bluetooth colord cups elogind gnome-online-accounts ibus networkmanager share -doc -flickr -kerberos -libinput (-systemd) -test -thunderbolt -v4l -wayland" ABI_X86="(64)" INPUT_DEVICES="-wacom"
(gui-libs/libhandy-1.0.3:1/1::dantrell-gnome, ebuild scheduled for merge) pulled in by
>=gui-libs/libhandy-0.90.0:1= required by (media-gfx/gnome-screenshot-3.38.0:0/0::dantrell-gnome-3-38, installed) USE="" ABI_X86="(64)"
>=gui-libs/libhandy-0.90.0:1= required by (gnome-base/gnome-control-center-3.38.5:2/2::dantrell-gnome-3-38, installed) USE="bluetooth colord cups elogind gnome-online-accounts ibus networkmanager share -doc -flickr -kerberos -libinput (-systemd) -test -thunderbolt -v4l -wayland" ABI_X86="(64)" INPUT_DEVICES="-wacom"
gui-libs/libhandy:1[introspection] required by (gnome-extra/gnome-tweaks-3.34.1-r200:0/0::dantrell-gnome, ebuild scheduled for merge) USE="" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_8 -python3_7 -python3_9"
|
I don't think this is me, since I don't have anything with regards to libhandy and gnome-tweaks in my portage config (apart from having gnome-tweaks in @world). |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Sat Apr 24, 2021 2:44 pm Post subject: |
|
|
| That's a weird issue with libhandy slots (/0 and /1). There's either something pulling the wrong slot version or portage can't solve this by itself. Did you try unmerging libhandy and trying again? |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sat Apr 24, 2021 10:03 pm Post subject: |
|
|
| saboya wrote: | | That's a weird issue with libhandy slots (/0 and /1). There's either something pulling the wrong slot version or portage can't solve this by itself. Did you try unmerging libhandy and trying again? |
I did not and it worked, thanks for the reminder. A bit strange though, I ran the emerge with backtrack=50, but apparently that still wasn't enough for portage to figure it out. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Sun Apr 25, 2021 2:53 pm Post subject: |
|
|
Excuse the delay, I was away for the day.
| simonvanderveldt wrote: | | I don't think this is me, since I don't have anything with regards to libhandy and gnome-tweaks in my portage config (apart from having gnome-tweaks in @world). |
| saboya wrote: | | That's a weird issue with libhandy slots (/0 and /1). There's either something pulling the wrong slot version or portage can't solve this by itself. Did you try unmerging libhandy and trying again? |
| simonvanderveldt wrote: | | I did not and it worked, thanks for the reminder. A bit strange though, I ran the emerge with backtrack=50, but apparently that still wasn't enough for portage to figure it out. |
It was probably caused by me taking the opportunity to match slots with the main tree (I had 0.0 and 1.0, they had 0.0 and 1).
However, the upgrade should have happened seamlessly, I tested this before I committed my changes but obviously I missed something.
As mentioned, the workaround is to unemerge and then re-emerge the package and obviously new installs are unaffected but I'd love to know what I missed so I'll be seeing if I can reproduce this issue.
Were you on stable or ~?
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sun Apr 25, 2021 6:26 pm Post subject: |
|
|
| dantrell wrote: | It was probably caused by me taking the opportunity to match slots with the main tree (I had 0.0 and 1.0, they had 0.0 and 1).
However, the upgrade should have happened seamlessly, I tested this before I committed my changes but obviously I missed something.
As mentioned, the workaround is to unemerge and then re-emerge the package and obviously new installs are unaffected but I'd love to know what I missed so I'll be seeing if I can reproduce this issue.
Were you on stable or ~? |
Stable, I don't have anything in /etc/portage for libhandy.
I'm on GNOME 3.38, profile "dantrell-gnome-3-38:default/linux/amd64/17.0/desktop/gnome/3.38 (stable)" in case it matters.
| Code: | $ eix libhandy
[I] gui-libs/libhandy
Available versions:
(0.0) 0.0.9(0.0/0)^t[1] 0.0.10(0.0/0)^t[1] [M]0.0.13(0.0/0)^t{tbz2} 0.0.13(0.0/0)^t{tbz2}[1]
(1) 0.82.0^t[1] 0.90.0^t[1] 1.0.0^t[1] 1.0.1^t[1] 1.0.2^t[1] [M]1.0.3^t{tbz2} 1.0.3^t{tbz2}[1] [M]~1.2.0^t [M]~1.2.1^t ~1.2.1^t[1]
{examples glade gtk-doc +introspection test +vala ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32"}
Installed versions: 0.0.13(0.0/0)^t{tbz2}[1](00:23:22 25/04/21)(introspection vala -examples -glade -gtk-doc -test) 1.0.3(1)^t{tbz2}[1](00:05:23 25/04/21)(introspection vala -examples -glade -gtk-doc -test)
Homepage: https://gitlab.gnome.org/GNOME/libhandy
Description: Building blocks for modern adaptive GNOME apps
[1] "dantrell-gnome" /var/db/repos/dantrell-gnome
|
P.S. Another issues popped up recently as well
| Code: | !!! The following installed packages are masked:
- app-misc/tracker-miners-3.0.1::dantrell-gnome (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# Matt Turner <mattst88@gentoo.org> (2021-04-13)
# Masked for testing
- app-misc/tracker-3.0.1::dantrell-gnome (masked by: package.mask)
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook. |
|
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Mon Apr 26, 2021 6:21 pm Post subject: |
|
|
| simonvanderveldt wrote: | | dantrell wrote: | It was probably caused by me taking the opportunity to match slots with the main tree (I had 0.0 and 1.0, they had 0.0 and 1).
However, the upgrade should have happened seamlessly, I tested this before I committed my changes but obviously I missed something. |
Stable, I don't have anything in /etc/portage for libhandy.
I'm on GNOME 3.38, profile "dantrell-gnome-3-38:default/linux/amd64/17.0/desktop/gnome/3.38 (stable)" in case it matters. |
So I was not able to reproduce your exact issue but it turns out I did miss at least one thing for stable:
| Code: | [ebuild NS ] gui-libs/libhandy-1.0.3-r1:1::dantrell-gnome [1.0.3:1.0/0::dantrell-gnome] USE="[...]" 0 KiB
[uninstall ] gui-libs/libhandy-1.0.3:1.0/0::dantrell-gnome USE="[...]"
[blocks b ] gui-libs/libhandy:1.0 ("gui-libs/libhandy:1.0" is blocking gui-libs/libhandy-1.0.3-r1)
[ebuild rR ] gnome-base/gnome-control-center-3.38.5:2::dantrell-gnome-3-38 USE="[...]" 0 KiB
Total: 2 packages (1 in new slot, 1 reinstall, 1 uninstall), Size of downloads: 0 KiB
Conflict: 1 block |
Every ebuild that had a SLOT change should have been bumped.
This problem did not turn up for ~ since I introduced a new version in the same commit.
| simonvanderveldt wrote: | | P.S. Another issues popped up recently as well [...] |
Sync up and you should be good to go.
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Tue Apr 27, 2021 12:22 pm Post subject: |
|
|
| dantrell wrote: | Every ebuild that had a SLOT change should have been bumped.
This problem did not turn up for ~ since I introduced a new version in the same commit. |
That should solve it indeed, just updated and the bump is now there, so should be fine now 
| dantrell wrote: | | simonvanderveldt wrote: | | P.S. Another issues popped up recently as well [...] |
Sync up and you should be good to go. |
Yep, all fixed, thanks again! |
|
| Back to top |
|
|
saboya
Guru
Joined: 28 Nov 2006
Posts: 552
Location: Brazil
|
| Posted: Tue Apr 27, 2021 2:55 pm Post subject: |
|
|
FYI, I got the slot change here and it was resolved as expected:
| Code: |
[ebuild NS ] gui-libs/libhandy-1.0.3-r1:1::dantrell-gnome [1.0.3:1.0/0::dantrell-gnome] USE="introspection vala -examples -glade -gtk-doc -test" 400 KiB
[uninstall ] gui-libs/libhandy-1.0.3:1.0/0::dantrell-gnome USE="introspection vala -examples -glade -gtk-doc -test"
|
|
|
| Back to top |
|
|
Child_of_Sun_24
l33t
Joined: 28 Jul 2004
Posts: 602
|
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Wed Apr 28, 2021 4:59 pm Post subject: |
|
|
| simonvanderveldt wrote: | | That should solve it indeed, just updated and the bump is now there, so should be fine now |
| saboya wrote: | | FYI, I got the slot change here and it was resolved as expected: [...] |
Good to hear.
| Child_of_Sun_24 wrote: | | Since updating gcc to gcc-11.1.0 some packages from your Overlay won't build anymore: [...] |
| Child_of_Sun_24 wrote: | | I hope you can help with this, i tried to use gcc-10.3.0 for building this packages through /etc/portage/env and package.env but it didn't work, so i wanted to tell you this |
To be honest, this is kinda expected.
That's why the overview specifics the GCC release version range that should be used to build GNOME.
I only check on this and resolve build failures roughly every year or so (i.e. if I check GCC 10 this year, GCC 11 probably won't be checked until next year).
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sat May 01, 2021 6:35 pm Post subject: |
|
|
Another small issue to report, xorg-2.eclass is gone https://github.com/gentoo/gentoo/commit/406f2ddec626ca257c5e0f3baba6c1b258d945cd
| Code: | [9] "dantrell-gnome" /var/db/repos/dantrell-gnome (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
Reading category 161|168 ( 95): x11-libs... * ERROR: x11-libs/libXxf86misc-1.0.4::dantrell-gnome failed (depend phase):
* xorg-2.eclass could not be found by inherit()
*
* Call stack:
* ebuild.sh, line 609: Called source '/var/db/repos/dantrell-gnome/x11-libs/libXxf86misc/libXxf86misc-1.0.4.ebuild'
* libXxf86misc-1.0.4.ebuild, line 5: Called inherit 'xorg-2'
* ebuild.sh, line 290: Called die
* The specific snippet of code:
* [[ -z ${location} ]] && die "${1}.eclass could not be found by inherit()"
*
* If you need support, post the output of `emerge --info '=x11-libs/libXxf86misc-1.0.4::dantrell-gnome'`,
* the complete build log and the output of `emerge -pqv '=x11-libs/libXxf86misc-1.0.4::dantrell-gnome'`.
* Working directory: '/usr/lib64/python3.8/site-packages'
* S: '/libXxf86misc-1.0.4'
ebuild failed with status 1
Reading category 161|168 ( 95): x11-libs...
cannot properly execute /var/db/repos/dantrell-gnome/x11-libs/libXxf86misc/libXxf86misc-1.0.4.ebuild
Reading category 168|168 (100) Finished
|
|
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Sat May 01, 2021 9:44 pm Post subject: |
|
|
| simonvanderveldt wrote: | | Another small issue to report, xorg-2.eclass is gone [...] |
I restored the eclass for stable and ported the ebuild to EAPI 7 for ~.
Sync up and you should be good to go.
| dantrell wrote: | GNOME 3.40 was released about a week ago under a new versioning scheme (and should therefore be referred to as GNOME 40 instead).
I haven't updated things on my end for various reasons and if I don't become particularly motivated I will probably continue to sit on things until GNOME 40.1 is released.
No rush right?  |
GNOME 40.1 was released a couple days ago and my TODO list is looking rather hefty. 
I'm going to give it a bit longer to make sure any straggling packages catch up but I'll be tackling this shortly.
Edit: Currently down to 20 EAPI 5 packages awaiting conversion.
I also think I found a way to automate the move from EAPI 6 to 7, especially given that I'm hearing talks of EAPI 8... 
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Thu May 06, 2021 8:59 pm Post subject: |
|
|
| dantrell wrote: | | simonvanderveldt wrote: | | Another small issue to report, xorg-2.eclass is gone [...] |
I restored the eclass for stable and ported the ebuild to EAPI 7 for ~.
Sync up and you should be good to go. |
Just wanted to confirm that this fixed. Thanks again! |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Fri May 07, 2021 9:23 pm Post subject: |
|
|
| dantrell wrote: | | Currently down to 20 EAPI 5 packages awaiting conversion. |
And, done.
I'll be reviewing my changes before they go live and then GNOME 40.1 is next.
_________________
Dantrell B. |
|
| Back to top |
|
|
jserink
Veteran
Joined: 30 Jan 2004
Posts: 1013
|
| Posted: Mon May 10, 2021 7:27 am Post subject: dantrell-gnome-3-38 mask issue |
|
|
Hi All:
About 2 weeks ago, the /var/lib/layman/dantrell-gnome-3-38/profiles/package.mask started throwing these errors:
--- Invalid atom in /var/lib/layman/dantrell-gnome-3-38/profiles/package.mask: x11-wm/mutter::gentoo
Every entry in the file throws this error.
The syntax in the file looks fine, I can't figure out why these errors are coming up.
Any ideas?
Cheers,
John
Merged by Neddyseagoon |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Mon May 10, 2021 5:52 pm Post subject: |
|
|
| jserink wrote: | Every entry in the file throws this error.
The syntax in the file looks fine, I can't figure out why these errors are coming up. |
Looks like this issue which already has a workaround in place.
Either you are not sycned up or you overrode the workaround.
_________________
Dantrell B. |
|
| Back to top |
|
|
jserink
Veteran
Joined: 30 Jan 2004
Posts: 1013
|
| Posted: Tue May 11, 2021 11:12 am Post subject: |
|
|
| dantrell wrote: | | jserink wrote: | Every entry in the file throws this error.
The syntax in the file looks fine, I can't figure out why these errors are coming up. |
Looks like this issue which already has a workaround in place.
Either you are not sycned up or you overrode the workaround. |
Hi:
Thanx for getting back to me.
I do layman -S and emerge --sync every day do Im fairly certain i'm sync'd up.
I've deleted your dantrell-gnome-3-38 overlay and re-added it several times, the issue persists.
I looked at your work around and am not sure how to apply it.
Any hints?
Cheers,
John |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Tue May 11, 2021 7:15 pm Post subject: |
|
|
| jserink wrote: | | I looked at your work around and am not sure how to apply it. |
Reference the Wiki page on /etc/portage/package.mask.
| jserink wrote: | | Any hints? |
However, the workaround (on your part) should not have been necessary.
To triple check, I spun up the latest stage 3 tarball, added the project overlays and saw the same warnings.
I then confirmed that selecting a profile in the project overlays forced a downgrade of Portage and after that the warnings disappeared.
You may want to search /etc/portage to see if something is interfering. You may also want to check your selected profile.
| dantrell wrote: | | Well, I already noticed this yesterday and added a workaround until I figure out how to proceed. |
At the same time, the workaround (on my part) should also not have been necessary.
So I have finally made an inquiry into it.
Edit: I have committed an experimental profile change for GNOME 3.38 that should be backwards and forwards compatible with Portage (at least for the interim).
It'd be nice if anyone (with some free free time) using GNOME 3.38 can sync up, unmask >=sys-apps/portage3.0.18, update Portage and see if emerge tries to do anything funny.
If you see any warnings before, during or after the process, let me know about those too.
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sun May 23, 2021 10:36 am Post subject: |
|
|
| dantrell wrote: | | dantrell wrote: | | Well, I already noticed this yesterday and added a workaround until I figure out how to proceed. |
At the same time, the workaround (on my part) should also not have been necessary.
So I have finally made an inquiry into it.
Edit: I have committed an experimental profile change for GNOME 3.38 that should be backwards and forwards compatible with Portage (at least for the interim).
It'd be nice if anyone (with some free free time) using GNOME 3.38 can sync up, unmask >=sys-apps/portage3.0.18, update Portage and see if emerge tries to do anything funny.
If you see any warnings before, during or after the process, let me know about those too. |
Sorry for the delay, I only check this topic every now and then.
This time I was checking if anyone made progress with the nautilus preview not working. It's been pretty annoying to not have it I've noticed.
Do you think it would be worth it to create an upstream bug for that? Or are we too far off a supported configuration to get a useful answer?
Anyway, just tried portage 3.0.18 after updating @world, nothing strange, it just said nothing to do.
Only issue is there were a bunch of "--- Invalid atom in /var/db/repos/dantrell-gnome-3-36/profiles/package.mask: x11-wm/mutter::gentoo" lines, but these are from the 3.36 overlay, so I guess that's expected (I run 3.38 but still have 3.36 in case I had to roll back, might do that because of the nautilus preview issue). |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Sun May 23, 2021 2:40 pm Post subject: |
|
|
| simonvanderveldt wrote: | | Sorry for the delay, I only check this topic every now and then. |
No problem. 
| simonvanderveldt wrote: | Anyway, just tried portage 3.0.18 after updating @world, nothing strange, it just said nothing to do.
Only issue is there were a bunch of "--- Invalid atom in /var/db/repos/dantrell-gnome-3-36/profiles/package.mask: x11-wm/mutter::gentoo" lines, but these are from the 3.36 overlay, so I guess that's expected (I run 3.38 but still have 3.36 in case I had to roll back, might do that because of the nautilus preview issue). |
I only committed the changes for the generic and GNOME 3.38 overlays so it is expected to see errors for any other overlays you have looped in.
That means it does work though so you can expect me to commit the rest of the changes I'm sitting on for the other overlays when I likewise commit the changes for the 1st pass (of my Nº pass system) for GNOME 40.
I'll remove the mask on my end a bit after that.
Edit: I went ahead and committed the change for the GNOME 3.36 overlay since it was the only change I was sitting on for that overlay.
| simonvanderveldt wrote: | This time I was checking if anyone made progress with the nautilus preview not working. It's been pretty annoying to not have it I've noticed.
Do you think it would be worth it to create an upstream bug for that? Or are we too far off a supported configuration to get a useful answer? |
Let me investigate first.
In fact, since you made time to test (and since I could use a break from my other projects) I'll take the next couple hours to look into this and see if I can resolve this on my end.
Stay tuned.
Edit: Looks like the issue was on my end (an updated dependency somehow slipped through the cracks).
Sync up (for some Sushi) and you should be good to go.
_________________
Dantrell B. |
|
| Back to top |
|
|
simonvanderveldt
Apprentice
Joined: 26 Jan 2016
Posts: 151
|
| Posted: Sun May 23, 2021 9:39 pm Post subject: |
|
|
| dantrell wrote: | I'll remove the mask on my end a bit after that.
Edit: I went ahead and committed the change for the GNOME 3.36 overlay since it was the only change I was sitting on for that overlay. |
Just tested this and I don't see any errors anymore. No updates/packages to install though, so I'll stay on portage 3.0.18 the coming days and report if anything strange pops up.
| dantrell wrote: |
| simonvanderveldt wrote: | This time I was checking if anyone made progress with the nautilus preview not working. It's been pretty annoying to not have it I've noticed.
Do you think it would be worth it to create an upstream bug for that? Or are we too far off a supported configuration to get a useful answer? |
Let me investigate first.
In fact, since you made time to test (and since I could use a break from my other projects) I'll take the next couple hours to look into this and see if I can resolve this on my end.
Stay tuned.
Edit: Looks like the issue was on my end (an updated dependency somehow slipped through the cracks).
Sync up (for some Sushi) and you should be good to go. |
All working again Thanks a lot! Makes daily life a lot easier
P.S Just got this message when updating @world
| Code: | !!! The following update has been skipped due to unsatisfied dependencies:
app-emulation/spice:0
selected: (app-emulation/spice-0.14.0-r2:0/0::dantrell-gnome, installed)
skipped: (app-emulation/spice-0.14.3-r1:0/0::dantrell-gnome, ebuild scheduled for merge) (see unsatisfied dependency below)
!!! All ebuilds that could satisfy ">=app-emulation/spice-protocol-0.14.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-emulation/spice-protocol-9999::gentoo (masked by: package.mask, missing keyword)
- app-emulation/spice-protocol-0.14.3::dantrell-gnome (masked by: missing keyword)
- app-emulation/spice-protocol-0.14.3::gentoo (masked by: package.mask)
- app-emulation/spice-protocol-0.14.1::dantrell-gnome (masked by: missing keyword)
- app-emulation/spice-protocol-0.14.1::gentoo (masked by: package.mask)
- app-emulation/spice-protocol-0.14.0::dantrell-gnome (masked by: missing keyword)
(dependency required by "app-emulation/spice-0.14.3-r1::dantrell-gnome" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
|
|
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Mon May 24, 2021 2:34 pm Post subject: |
|
|
| simonvanderveldt wrote: | | P.S Just got this message when updating @world [...] |
Looks like a couple more packages needed to be stabilized.
Sync up and you should be good to go.
_________________
Dantrell B. |
|
| Back to top |
|
|
dantrell
l33t
Joined: 01 Jun 2007
Posts: 915
Location: Earth
|
| Posted: Thu Jul 01, 2021 4:49 pm Post subject: |
|
|
| dantrell wrote: | | GNOME 40.1 was released a couple days ago and my TODO list is looking rather hefty. |
| dantrell wrote: | That's why the overview specifics the GCC release version range that should be used to build GNOME.
I only check on this and resolve build failures roughly every year or so (i.e. if I check GCC 10 this year, GCC 11 probably won't be checked until next year). |
| dantrell wrote: | | I also think I found a way to automate the move from EAPI 6 to 7, especially given that I'm hearing talks of EAPI 8... |
So it's probably time for a micro-status update.
Real life has been crazy enough (definitely not because of this) lately that I still haven't gotten GNOME 3.40 rolled out yet, however, other updates for the project have continued on schedule.
Given the length of the delay, some may have switched to GNOME as provided by Gentoo and that's okay.
As for my end, I'll (once again be attempting to) clear a few days to get some work in. My priority (in order) will be:
- Adding support for GNOME 40.3
- Building against GCC 10 & 11
- Preparing for EAPI 8
Stay tuned.
_________________
Dantrell B. |
|
| Back to top |
|
|
|
Unsupported Software
