Bug 262591 – [gnome overlay] Patch for gnome-base/gdm-2.5.92 is missing/misnamed in tree

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Kobboi 2009-03-15 19:22:03 UTC]

I don't mean to sound disrespectful, but how do errors like this one get in to the tree? Isn't there a basic/automatic test for this?

>>> Emerging (2 of 3) gnome-base/gdm-2.25.92 from gnome
 * gdm-2.20.5-gentoo-files.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                          [ ok ]
 * gdm-2.25.92.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                                      [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                        [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                       [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                      [ ok ]
>>> Unpacking source...
>>> Unpacking gdm-2.20.5-gentoo-files.tar.bz2 to /var/tmp/portage/gnome-base/gdm-2.25.92/work
>>> Unpacking gdm-2.25.92.tar.bz2 to /var/tmp/portage/gnome-base/gdm-2.25.92/work
>>> Source unpacked in /var/tmp/portage/gnome-base/gdm-2.25.92/work
>>> Preparing source in /var/tmp/portage/gnome-base/gdm-2.25.92/work/gdm-2.25.92 ...

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/local/layman/gnome/gnome-base/gdm/files/gdm-2.25.92-selinux-remove-attr.patch
 *   ( gdm-2.25.92-selinux-remove-attr.patch )

 * 
 * ERROR: gnome-base/gdm-2.25.92 failed.
 * Call stack:
 *               ebuild.sh, line   48:  Called src_prepare
 *             environment, line 2858:  Called epatch '/usr/portage/local/layman/gnome/gnome-base/gdm/files/gdm-2.25.92-selinux-remove-attr.patch'
 *             environment, line 1383:  Called die
 * The specific snippet of code:
 *                   die "Cannot find $EPATCH_SOURCE!";
 *  The die message:
 *   Cannot find $EPATCH_SOURCE!
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/gnome-base/gdm-2.25.92/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/gnome-base/gdm-2.25.92/temp/environment'.
 * This ebuild is from a repository named 'gnome'
 * 


Reproducible: Always

[Comment 1 Rémi Cardona (RETIRED) 2009-03-15 19:30:55 UTC]

(In reply to comment #0)
> I don't mean to sound disrespectful, but how do errors like this one get in to
> the tree? Isn't there a basic/automatic test for this?

Automatic testing for an overlay? No. It's probably just an oversight.

Please do remember that the Gnome overlay is a testing ground where things may break.

Thanks

[Comment 2 Serkan Kaba (RETIRED) 2009-03-15 19:35:55 UTC]

*** This bug has been marked as a duplicate of bug 262581 ***