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 ... 18, 19, 20  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
Ultimator
n00b
n00b


Joined: 23 Jun 2018
Posts: 24

PostPosted: Thu May 21, 2020 8:06 pm    Post subject: Reply with quote

Build fails for net-print/cups-filters-1.25.13 (probably other versions too) with gcc 10.
This upstream patch fixes it
https://github.com/OpenPrinting/cups-filters/commit/e6c5025df307d3e8c79c3cd801780e4570f8607e
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Thu May 21, 2020 9:05 pm    Post subject: Reply with quote

Ultimator wrote:
Build fails for net-print/cups-filters-1.25.13 (probably other versions too) with gcc 10.
This upstream patch fixes it
[...]

Thanks for the heads up.

Patched the latest stable version (and did some updating / spring cleaning while I was at it).

Did I mention how much I'm not liking how many packages need to be patched for GCC 10? :?

Quote:
media-fonts/symbola: Remove last-rited pkg

In other news, Symbola has been removed from the main tree. You can find Gentoo's thoughts on the matter here and Fedora's thoughts on the matter here.

Here's the footer of Symbola 9.17's homepage on 20170811:

Code:
In lieu of a licence; fonts and documents in this site are free for any use; George Douros.

Here are the contents of the Symbola.pdf:

Code:
Symbola, version 9.17, July 2017
SYMBOLA IS FREE FOR ANY USE

Unicode Fonts for Ancient Scripts
George Douros

Here's the footer of Symbola 10.24's homepage on 20180212:

Code:
In lieu of a licence; fonts and documents in this site are free for any use; George Douros

And once again, here are the contents of the Symbola.pdf:

Code:
Symbola, version 10.24, January 2018
SYMBOLA IS FREE FOR ANY USE

Unicode Fonts for Ancient Scripts
George Douros

Contrast this with the current License Agreement and the new contents of Symbola.pdf where it applies:

Code:
Symbola, version 13.00, march 2020
free strictly for personal, non-commercial use
available under the general ufas licence
Unicode Fonts for Ancient Scripts
George Douros

The facts show that:

1. The old license agreement, such as it was, does not contain any termination clauses and is therefore valid forever.

2. The new license agreement, such as it is, cannot be applied retroactively and therefore only applies to the versions of Symbola which include the new wording.

As such, Symbola versions 9.17 and 10.24 are provided by the project overlays. If you have an issue with this, let me know and I'll introduce a restrictive USE flag that specifically allows for excluding Symbola.
_________________
Dantrell B.
Back to top
View user's profile Send private message
vozhyk
n00b
n00b


Joined: 18 Nov 2018
Posts: 8
Location: Warsaw, Poland

PostPosted: Sun May 31, 2020 5:05 pm    Post subject: Reply with quote

I tried running Waybar, and it ends up invisible, which is reportedly fixed by gtk!1633.

I'm running a not-recently-upgraded 3.34 branch (with gtk+-3.24.17):
Code:
 * Last emerge --sync was 44d 1h 54m 26s ago.
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Mon Jun 01, 2020 12:47 am    Post subject: Reply with quote

vozhyk wrote:
I tried running Waybar, and it ends up invisible, which is reportedly fixed by gtk!1633.

Thanks for the heads up.

I stabilized GTK version 3.24.18 which includes this fix.
_________________
Dantrell B.
Back to top
View user's profile Send private message
simonvanderveldt
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2016
Posts: 118

PostPosted: Sun Jun 07, 2020 9:17 am    Post subject: Reply with quote

Hi dantrell,

media-gfx/gimp-2.10.18-r1 was stabilized in the gentoo tree recently. It requires a newer gegl (>=media-libs/gegl-0.4.22:0.4[cairo]) which seems to be masked in your overlay.
Can media-libs/gegl-0.4.22::dantrell-gnome be stabilized or is there an issue with this newer version?

Code:
~ ❯ sudo emerge -1av gimp

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

Calculating dependencies... done!
[binary   R    ] media-gfx/gimp-2.10.14-r1:2::gentoo  USE="gnome -aalib -alsa (-altivec) (-aqua) -debug -doc -heif -jpeg2k -mng -openexr -postscript -python -test -udev -unwind -vector-icons -webp -wmf -xpm" CPU_FLAGS_X86="mmx sse" PYTHON_SINGLE_TARGET="python2_7" 28,057 KiB

Total: 1 package (1 reinstall, 1 binary), Size of downloads: 28,057 KiB

!!! The following update has been skipped due to unsatisfied dependencies:

media-gfx/gimp:2

  selected: (media-gfx/gimp-2.10.14-r1:2/2::gentoo, binary scheduled for merge)
  skipped: (media-gfx/gimp-2.10.18-r1:2/2::gentoo, ebuild scheduled for merge) (see unsatisfied dependency below)

!!! All ebuilds that could satisfy ">=media-libs/gegl-0.4.22:0.4[cairo]" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-libs/gegl-9999::gentoo (masked by: package.mask, missing keyword)
- media-libs/gegl-0.4.22::dantrell-gnome (masked by: missing keyword)
- media-libs/gegl-0.4.22::gentoo (masked by: package.mask)

(dependency required by "media-gfx/gimp-2.10.18-r1::gentoo" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Would you like to merge these packages? [Yes/No]


Related to this I also have a question about keywords for the packages from your overlays.
Looking at gegl with equery I currently get this:
Code:
~ ❯ eq y -O gegl
Keywords for media-libs/gegl:
             |                             |   u     | 
             | a   a       p s       a r   |   n     | 
             | m   r h i   p p   m s l i m | e u s   | r
             | d a m p a p c a x 6 3 p s i | a s l   | e
             | 6 r 6 p 6 p 6 r 8 8 9 h c p | p e o   | p
             | 4 m 4 a 4 c 4 c 6 k 0 a v s | i d t   | o
-------------+-----------------------------+---------+---------------
    0.2.0-r6 | + + ~ ~ ~ + + o + o o ~ o ~ | 6 o 0   | gentoo       
    0.2.0-r6 | o o o o o o o o o o o o o o | 6 o     | dantrell-gnome
-------------+-----------------------------+---------+---------------
   0.3.14    | o o o o o o o o o o o o o o | 6 # 0.3 | dantrell-gnome
   0.3.20    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.3.26    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.3.28    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.3.30    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.3.34    | + + + ~ ~ + + o + o o ~ o ~ | 6 o     | gentoo       
   0.3.34    | o o o o o o o o o o o o o o | 6 o     | dantrell-gnome
-------------+-----------------------------+---------+---------------
    0.4.0-r1 | o o o o o o o o o o o o o o | 6 # 0.4 | dantrell-gnome
    0.4.2    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
    0.4.4    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
    0.4.6    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
    0.4.8-r1 | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.4.12    | o o o o o o o o o o o o o o | 6 #     | dantrell-gnome
   0.4.14    | o o o o o o o o o o o o o o | 7 #     | dantrell-gnome
   0.4.16    | + + + ~ ~ ~ ~ o + o o ~ o ~ | 7 o     | gentoo       
   0.4.16    | o o o o o o o o o o o o o o | 7 #     | dantrell-gnome
   0.4.18    | + ~ + ~ ~ ~ ~ o + o o o o ~ | 7 o     | gentoo       
[I]0.4.18    | o o o o o o o o o o o o o o | 7 o     | dantrell-gnome
   0.4.20    | o o o o o o o o o o o o o o | 7 #     | dantrell-gnome
   0.4.22    | + ~ + ~ ~ ~ + o ~ o o ~ o ~ | 7 o     | gentoo       
   0.4.22    | o o o o o o o o o o o o o o | 7 o     | dantrell-gnome
  [M]9999    | o o o o o o o o o o o o o o | 7 o     | gentoo       


I'd have expected the installed 0.4.18::dantrell-gnome to be marked stable and others from ::dantrell-gnome to be either testing or unkeyworded, but it seems everything is unkeyworded. The ebuilds themselves contain "special" keywords (i.e. * or ~*) though. Is this simply an issue with equery showing the information incorrectly?

[edit] I also have a question about this note
dantrell wrote:
dantrell wrote:
[...] I might just follow through with hiding the 13.0 & 17.0 profiles instead¹ and introducing desktop/gnome+plasma/mainline (or latest or something).

I followed through with this and an update of app-admin/eselect will show the full benefits (which can be disabled through the vanilla-profile USE flag).

Running "eselect profile" at that point should be pretty self explanatory:

Code:
eselect profile

In short, "eselect profile list" will show your current profile (which could be hidden as long as it's valid) + the latest non-hidden profiles.

To get the full list use "eselect profile --hidden" instead.

Do note, however, that this change is only in effect for GNOME 3.34 and greater because I'm stacking up changes for the older release versions.

The known issues section in the repo's readme mentions "17.0 Enforces PIE Hidden¹ for amd64; Visible for x86".
I was wondering what the actual issue is. Is it that PIE is enabled and thus one must make sure to rebuild @world? Or is it something else?
And just to be sure PIE is also enabled for your 17.0 profiles? Asking because I'm currently on dantrell-gnome-3-32:default/linux/amd64/17.0/desktop/gnome/3.32 and wanted to upgrade to 3.36 and I'm unsure if I can just use the hidden dantrell-gnome-3-36:default/linux/amd64/17.0/desktop/gnome/3.36 profile.
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Sun Jun 07, 2020 3:23 pm    Post subject: Reply with quote

simonvanderveldt wrote:
media-gfx/gimp-2.10.18-r1 was stabilized in the gentoo tree recently. It requires a newer gegl (>=media-libs/gegl-0.4.22:0.4[cairo]) which seems to be masked in your overlay.
Can media-libs/gegl-0.4.22::dantrell-gnome be stabilized [...]

Stabilized but it'll be another hour or so before it's live (currently updating a test install).

Edit: It's live.

simonvanderveldt wrote:
[...] or is there an issue with this newer version?

The only issue is that I check stable when someone reminds me it exists. :oops:

simonvanderveldt wrote:
I'd have expected the installed 0.4.18::dantrell-gnome to be marked stable and others from ::dantrell-gnome to be either testing or unkeyworded, but it seems everything is unkeyworded. The ebuilds themselves contain "special" keywords (i.e. * or ~*) though. Is this simply an issue with equery showing the information incorrectly?

It's an issue with equery but I don't know if upstream would correct it.

There's at least 3 other packages I know of (pkgcheck, repoman and smart-live-rebuild) that have issues with the techniques used by the project overlays (even though they are perfectly valid uses which have worked since 2011). :evil:

simonvanderveldt wrote:
I was wondering what the actual issue is. Is it that PIE is enabled and thus one must make sure to rebuild @world? Or is it something else?
And just to be sure PIE is also enabled for your 17.0 profiles? Asking because I'm currently on dantrell-gnome-3-32:default/linux/amd64/17.0/desktop/gnome/3.32 and wanted to upgrade to 3.36 and I'm unsure if I can just use the hidden dantrell-gnome-3-36:default/linux/amd64/17.0/desktop/gnome/3.36 profile.

There isn't an issue. Instead, that block of text should just be moved out from under Known Issues and into its own section.

Rest assured, PIE is enabled for the 17.0 profiles (and for the 17.1 profiles which inherit it).
_________________
Dantrell B.
Back to top
View user's profile Send private message
saboya
Guru
Guru


Joined: 28 Nov 2006
Posts: 516
Location: Brazil

PostPosted: Mon Jun 08, 2020 3:20 pm    Post subject: Reply with quote

saboya wrote:
And now, a little funny case: Apparently, multilib rust ebuilds are broken if you use rust-bin. Turns out rust-bin does not pull the 32-bit version of the std crate.


FYI, since =dev-lang/rust-bin-1.43.0 this is no longer an issue and the ebuild pulls in all the necessary files for working rust compilers / std libs for mutilib configs.

Relevant issue: https://bugs.gentoo.org/701362
Back to top
View user's profile Send private message
Elleni
Veteran
Veteran


Joined: 23 May 2006
Posts: 1075

PostPosted: Fri Jun 12, 2020 11:31 am    Post subject: Reply with quote

Hi Dantrell,
Upgrading my system gnome-boxes failed to build. Thanks for checking. :)
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Sat Jun 13, 2020 3:27 am    Post subject: Reply with quote

Elleni wrote:
Upgrading my system gnome-boxes failed to build.

I wasn't immediately able to reproduce this build failure but it looks like you might need to rebuild sys-apps/usbredir:

Code:
emerge --ask --oneshot --nodeps --verbose sys-apps/usbredir

It's possible a more recent version of dev-libs/libgusb needs to be stabilized too but I was able to build against the last 5 versions. :o
_________________
Dantrell B.
Back to top
View user's profile Send private message
Elleni
Veteran
Veteran


Joined: 23 May 2006
Posts: 1075

PostPosted: Sat Jun 13, 2020 3:21 pm    Post subject: Reply with quote

Thanks re-emerging usbredir solved it.
Back to top
View user's profile Send private message
vozhyk
n00b
n00b


Joined: 18 Nov 2018
Posts: 8
Location: Warsaw, Poland

PostPosted: Sat Jun 13, 2020 9:04 pm    Post subject: Reply with quote

I'm trying to upgrade world after not upgrading it for a few months. One of the problems reported by emerge is:
Code:
!!! All ebuilds that could satisfy ">=app-text/poppler-0.87.0:=" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-text/poppler-9999::gentoo (masked by: package.mask, missing keyword)
- app-text/poppler-0.89.0::dantrell-gnome (masked by: missing keyword)
- app-text/poppler-0.89.0::gentoo (masked by: package.mask, ~amd64 keyword)
- app-text/poppler-0.88.0-r1::dantrell-gnome (masked by: missing keyword)
- app-text/poppler-0.88.0-r1::gentoo (masked by: package.mask)
- app-text/poppler-0.87.0::dantrell-gnome (masked by: missing keyword)

(dependency required by "app-text/texlive-core-2020-r5::gentoo" [ebuild])
(dependency required by "dev-texlive/texlive-plaingeneric-2020::gentoo" [ebuild])
(dependency required by "dev-texlive/texlive-pstricks-2020::gentoo" [ebuild])
(dependency required by "dev-texlive/texlive-mathscience-2020::gentoo" [ebuild])
(dependency required by "dev-texlive/texlive-xetex-2020::gentoo" [ebuild])
(dependency required by "app-text/texlive-2020::gentoo[xetex]" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

I'm using the gnome+plasma 17.0 profile. This seems related to dantrell-gnome, as it masks poppler::gentoo, but doesn't unmask any version from ::dantrell-gnome.

Edit: after I did
Code:
echo "=app-text/poppler-0.89.0::dantrell-gnome **" >> /etc/portage/package.accept_keywords/temp
, I get a similar one about libgit2:
Code:
!!! The following update has been skipped due to unsatisfied dependencies:

dev-lang/rust:stable

  selected: (dev-lang/rust-1.41.1:stable/1.41::gentoo, installed)
  skipped: (dev-lang/rust-1.43.1:stable/1.43::gentoo, ebuild scheduled for merge) (see unsatisfied dependency below)

!!! All ebuilds that could satisfy ">=dev-libs/libgit2-0.99:=" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-libs/libgit2-1.0.1::dantrell-gnome (masked by: missing keyword)
- dev-libs/libgit2-1.0.1::gentoo (masked by: package.mask, ~amd64 keyword)
- dev-libs/libgit2-1.0.0-r1::gentoo (masked by: package.mask)

(dependency required by "dev-lang/rust-1.43.1::gentoo" [ebuild])
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Sun Jun 14, 2020 4:48 am    Post subject: Reply with quote

dantrell wrote:
There isn't an issue. Instead, that block of text should just be moved out from under Known Issues and into its own section.

That block of text was moved.

vozhyk wrote:
This seems related to dantrell-gnome, as it masks poppler::gentoo, but doesn't unmask any version from ::dantrell-gnome.

It is related but you misinterpreted the emerge error.

The issue here was that a more recent of version of Poppler needed to be stabilized (which I did).

vozhyk wrote:
Edit: after I did [...]

The most recent versions of Poppler are always keyword masked until I review them.

Feel free to reverse this mask if you have security concerns and/or are capable of dealing with any build failures that prop up.

vozhyk wrote:
I get a similar one about libgit2: [...]

Sync up and you should be good to go.

dantrell wrote:
For what it's worth, GNOME 3.34 is scheduled to keep rolling out bugfix releases until 3.34.9 (August of this year).

In other news, GNOME 3.34.7 (bugfixes) and GNOME 3.36.3 (bugfixes) are now available.

Technically it already was but upstream still distributed the core package tarballs on a staggered release schedule which was just finalized.

Nothing significant has changed since the initial announcement post or the previous updates.

Enjoy.
_________________
Dantrell B.
Back to top
View user's profile Send private message
simonvanderveldt
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2016
Posts: 118

PostPosted: Thu Jun 18, 2020 6:41 pm    Post subject: Reply with quote

dantrell wrote:
simonvanderveldt wrote:
media-gfx/gimp-2.10.18-r1 was stabilized in the gentoo tree recently. It requires a newer gegl (>=media-libs/gegl-0.4.22:0.4[cairo]) which seems to be masked in your overlay.
Can media-libs/gegl-0.4.22::dantrell-gnome be stabilized [...]

Stabilized but it'll be another hour or so before it's live (currently updating a test install).

Edit: It's live.

Thanks, it's working fine after this change, sorry for the delay on the feedback.

dantrell wrote:
simonvanderveldt wrote:
[...] or is there an issue with this newer version?

The only issue is that I check stable when someone reminds me it exists. :oops:

:) That's good to know though.

My upgrade to 3.36 with the 17.0 profile worked flawlessly (thanks!).
I just checked if there were still some older versions of packages installed and there are still a couple of packages that have a 3.32 version installed
Code:
$ eix-installed -a | grep 3.32
app-arch/file-roller-3.32.3
app-text/yelp-tools-3.32.2
gnome-extra/gnome-color-manager-3.32.0
gnome-extra/gnome-system-monitor-3.32.1
gnome-extra/zenity-3.32.0
x11-libs/libwnck-3.32.0

gnome-extra/gnome-system-monitor has a 3.36.1 available, which seems to be keyworded for testing. Is that correct?

For the other packages I don't see a 3.36 (or 3.34) version available in your repos, although some of them do seem to have a git tag for 3.36, these are
- https://gitlab.gnome.org/GNOME/file-roller/-/tree/3.36.2
- https://gitlab.gnome.org/GNOME/gnome-color-manager/-/tree/GNOME_COLOR_MANAGER_3_36_0
- https://gitlab.gnome.org/GNOME/libwnck/-/tree/3.36.0

I assume this means these projects didn't release any tarballs yet?

dantrell wrote:
simonvanderveldt wrote:
I'd have expected the installed 0.4.18::dantrell-gnome to be marked stable and others from ::dantrell-gnome to be either testing or unkeyworded, but it seems everything is unkeyworded. The ebuilds themselves contain "special" keywords (i.e. * or ~*) though. Is this simply an issue with equery showing the information incorrectly?

It's an issue with equery but I don't know if upstream would correct it.

There's at least 3 other packages I know of (pkgcheck, repoman and smart-live-rebuild) that have issues with the techniques used by the project overlays (even though they are perfectly valid uses which have worked since 2011). :evil:

OK, that's good to know, quiet annoying though :( I'm pretty swamped with stuff at the moment but maybe I can find a moment to look into at least trying to fix equery.
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Thu Jun 18, 2020 11:59 pm    Post subject: Reply with quote

simonvanderveldt wrote:
I just checked if there were still some older versions of packages installed and there are still a couple of packages that have a 3.32 version installed
Code:
$ eix-installed -a | grep 3.32
app-arch/file-roller-3.32.3
app-text/yelp-tools-3.32.2
gnome-extra/gnome-color-manager-3.32.0
gnome-extra/gnome-system-monitor-3.32.1
gnome-extra/zenity-3.32.0
x11-libs/libwnck-3.32.0

simonvanderveldt wrote:
For the other packages I don't see a 3.36 (or 3.34) version available in your repos, although some of them do seem to have a git tag for 3.36, these are
- https://gitlab.gnome.org/GNOME/file-roller/-/tree/3.36.2
- https://gitlab.gnome.org/GNOME/gnome-color-manager/-/tree/GNOME_COLOR_MANAGER_3_36_0
- https://gitlab.gnome.org/GNOME/libwnck/-/tree/3.36.0

I assume this means these projects didn't release any tarballs yet?

It's actually perfectly normal that there might be some older packages sitting around since they probably don't have any tarballs available.

But like you said, some of them do.

For those packages what happened is that they really didn't have any tarballs available during the initial x.y.0 release and therefore they slipped through the cracks (on my end) during subsequent updates since my secret overlay tools don't automatically point to the latest upstream listings.

I just accounted for this and will be merging the results.

Edit: Merged (and live).

simonvanderveldt wrote:
gnome-extra/gnome-system-monitor has a 3.36.1 available, which seems to be keyworded for testing. Is that correct?

Sometimes when a package is updated out of schedule (like a 3.36.0 release dropping after months on 3.32.z), I slot the update in ~ for a bit.
_________________
Dantrell B.
Back to top
View user's profile Send private message
Child_of_Sun_24
Guru
Guru


Joined: 28 Jul 2004
Posts: 499

PostPosted: Tue Jun 23, 2020 7:20 am    Post subject: Reply with quote

Hi there :-)

I have a problem building net-libs/gupnp-1.2.3, it looks like a patch can't be applied.
Code:
 * Package:    net-libs/gupnp-1.2.3
 * Repository: dantrell-gnome
 * Maintainer: gnome@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc introspection kernel_linux python_single_target_python3_8 userland_GNU vala
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Using python3.8 to build
>>> Unpacking source...
>>> Unpacking gupnp-1.2.3.tar.xz to /var/tmp/portage/net-libs/gupnp-1.2.3/work
>>> Source unpacked in /var/tmp/portage/net-libs/gupnp-1.2.3/work
>>> Preparing source in /var/tmp/portage/net-libs/gupnp-1.2.3/work/gupnp-1.2.3 ...
 * Applying gupnp-1.2.2-build-manpage.patch ...
patching file doc/meson.build
Hunk #1 FAILED at 4.
Hunk #2 FAILED at 26.
2 out of 2 hunks FAILED -- saving rejects to file doc/meson.build.rej
patching file meson.build
Hunk #1 FAILED at 31.
1 out of 1 hunk FAILED -- saving rejects to file meson.build.rej
 [ !! ]
 * ERROR: net-libs/gupnp-1.2.3::dantrell-gnome failed (prepare phase):
 *   patch -p1  failed with /var/tmp/portage/net-libs/gupnp-1.2.3/files/gupnp-1.2.2-build-manpage.patch
 *
 * Call stack:
 *               ebuild.sh, line  125:  Called src_prepare
 *             environment, line 2948:  Called xdg_src_prepare
 *             environment, line 3944:  Called default
 *      phase-functions.sh, line  855:  Called default_src_prepare
 *      phase-functions.sh, line  920:  Called __eapi6_src_prepare
 *             environment, line  310:  Called eapply '/var/tmp/portage/net-libs/gupnp-1.2.3/files/gupnp-1.2.2-build-manpage.patch'
 *             environment, line 1056:  Called _eapply_patch '/var/tmp/portage/net-libs/gupnp-1.2.3/files/gupnp-1.2.2-build-manpage.patch'
 *             environment, line  994:  Called __helpers_die 'patch -p1  failed with /var/tmp/portage/net-libs/gupnp-1.2.3/files/gupnp-1.2.2-build-manpage.patch'
 *   isolated-functions.sh, line  112:  Called die
 * The specific snippet of code:
 *         die "$@"
 *
 * If you need support, post the output of `emerge --info '=net-libs/gupnp-1.2.3::dantrell-gnome'`,
 * the complete build log and the output of `emerge -pqv '=net-libs/gupnp-1.2.3::dantrell-gnome'`.
 * The complete build log is located at '/var/log/portage/net-libs:gupnp-1.2.3:20200623-071059.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/net-libs/gupnp-1.2.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-libs/gupnp-1.2.3/temp/environment'.
 * Working directory: '/var/tmp/portage/net-libs/gupnp-1.2.3/work/gupnp-1.2.3'
 * S: '/var/tmp/portage/net-libs/gupnp-1.2.3/work/gupnp-1.2.3'


I hope you can help me :-)
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 24218
Location: here

PostPosted: Tue Jun 23, 2020 7:26 am    Post subject: Reply with quote

In gupnp-1.2.3 patch gupnp-1.2.2-build-manpage.patch is no longer required because is fixed upstream
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Cuong Nguyen
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2018
Posts: 146

PostPosted: Tue Jun 23, 2020 11:54 am    Post subject: Reply with quote

fedeliallalinea wrote:
In gupnp-1.2.3 patch gupnp-1.2.2-build-manpage.patch is no longer required because is fixed upstream


Just have fixed manually :D
Code:

--- /var/lib/layman/dantrell-gnome/net-libs/gupnp/gupnp-1.2.3.ebuild    2020-06-23 18:48:10.863439023 +0700
+++ /var/db/pkg/net-libs/gupnp-1.2.3/gupnp-1.2.3.ebuild 2020-06-23 18:45:46.704444346 +0700
@@ -43,9 +43,9 @@
        )
 "
 
-PATCHES=(
-       "${FILESDIR}"/${PN}-1.2.2-build-manpage.patch # https://gitlab.gnome.org/GNOME/gupnp/merge_requests/5
-)
+#PATCHES=(
+#      "${FILESDIR}"/${PN}-1.2.2-build-manpage.patch # https://gitlab.gnome.org/GNOME/gupnp/merge_requests/5
+#)
 
 src_prepare() {
        use introspection && vala_src_prepare
Back to top
View user's profile Send private message
dantrell
l33t
l33t


Joined: 01 Jun 2007
Posts: 717
Location: Earth

PostPosted: Tue Jun 23, 2020 7:31 pm    Post subject: Reply with quote

Child_of_Sun_24 wrote:
I have a problem building net-libs/gupnp-1.2.3, it looks like a patch can't be applied.

fedeliallalinea wrote:
In gupnp-1.2.3 patch gupnp-1.2.2-build-manpage.patch is no longer required because is fixed upstream

Cuong Nguyen wrote:
Just have fixed manually :D

I could have sworn I built all the new packages but I guess I was mistaken. :?

I'll be correcting this shortly.

Edit: Corrected.
_________________
Dantrell B.
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 ... 18, 19, 20
Page 20 of 20

 
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