On Tue, Apr 06, 2021 at 08:43:27PM +0200, Martin Jansa via 
lists.openembedded.org wrote:
> * 8459235919f592b1bc099ecf9a947cb6344b6fa5 doesn't exist in current repo:
>   libyui$ git branch -a --contains 8459235919f592b1bc099ecf9a947cb6344b6fa5
>   error: no such commit 8459235919f592b1bc099ecf9a947cb6344b6fa5
> 
> * there are no common commits in the new libyui repo, but luckily old
>   repo is kept as
>   https://github.com/libyui/libyui-old
>   similarly libyui-ncurses now contains only README about being obsolete in:
>   https://github.com/libyui/libyui-ncurses
>   but at least it wasn't rewritten to have the new content
> 
> Signed-off-by: Martin Jansa <[email protected]>
> ---
>  meta-oe/recipes-graphics/libyui/libyui_3.6.0.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-oe/recipes-graphics/libyui/libyui_3.6.0.bb 
> b/meta-oe/recipes-graphics/libyui/libyui_3.6.0.bb
> index 7c6f4c13d2..f3c112c3b8 100644
> --- a/meta-oe/recipes-graphics/libyui/libyui_3.6.0.bb
> +++ b/meta-oe/recipes-graphics/libyui/libyui_3.6.0.bb
> @@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = 
> "file://COPYING.gpl-3;md5=d32239bcb673463ab874e80d47fae504 \
>                      
> file://COPYING.lgpl-3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
>                     "
>  
> -SRC_URI = "git://github.com/libyui/libyui.git \
> +SRC_URI = "git://github.com/libyui/libyui-old.git \
>             file://0001-Fix-build-with-clang.patch \
>             file://0001-Use-relative-install-paths-for-CMake.patch \
>             "

Gentle ping for these 3 (and 3 hostapd fixes currently in
stable/dunfell-nut).

Attachment: signature.asc
Description: PGP signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#90947): 
https://lists.openembedded.org/g/openembedded-devel/message/90947
Mute This Topic: https://lists.openembedded.org/mt/82231569/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to