From: Naga Malleswari <nagamalli@riseup.net>
To: 40485@debbugs.gnu.org, Danny Milosavljevic <dannym@scratchpost.org>
Subject: [bug#40485] Acknowledgement (gnu: Update libxfce4ui to 4.15.2.)
Date: Tue, 7 Apr 2020 19:10:23 +0530 [thread overview]
Message-ID: <aa0f4995-3613-4115-07dc-3eac1a99214b@riseup.net> (raw)
In-Reply-To: <handler.40485.B.158626413323635.ack@debbugs.gnu.org>
Hi Danny
(inputs `(("libsm" ,libsm)
("libice" ,libice)
;; FIXME: required by libxfce4ui-1.pc, so should be
propagated,
;; but will lead to a conflict with gtk+.
("gtk+-2" ,gtk+-2)
I understand that xfce4-embed-plugin failed after libxfce4ui is updated
because of the conflict with the inputs. What is suggested to do.
On 07/04/20 6:26 pm, GNU bug Tracking System wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> guix-patches@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 40485@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
--
Regards
NagaMalli
next prev parent reply other threads:[~2020-04-07 13:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 12:55 [bug#40485] gnu: Update libxfce4ui to 4.15.2 Naga Malleswari
[not found] ` <handler.40485.B.158626413323635.ack@debbugs.gnu.org>
2020-04-07 13:40 ` Naga Malleswari [this message]
2020-04-07 13:57 ` [bug#40485] Acknowledgement (gnu: Update libxfce4ui to 4.15.2.) Danny Milosavljevic
2020-04-07 14:01 ` Danny Milosavljevic
2020-04-07 14:07 ` Danny Milosavljevic
2020-04-07 14:17 ` Naga Malleswari
2020-04-07 14:23 ` Danny Milosavljevic
2020-04-07 19:17 ` Naga Malleswari
2020-04-07 19:24 ` Danny Milosavljevic
2020-04-07 19:48 ` Danny Milosavljevic
2020-04-08 19:43 ` Naga Malleswari
2020-04-08 22:19 ` Danny Milosavljevic
2020-04-08 22:31 ` Danny Milosavljevic
2020-04-08 22:44 ` Danny Milosavljevic
2020-04-09 20:42 ` Naga Malleswari
2020-04-09 22:11 ` Danny Milosavljevic
2020-04-12 21:09 ` Naga Malleswari
2020-04-13 19:27 ` Danny Milosavljevic
2020-04-14 15:43 ` [bug#40485] [PATCH v3] : " Naga Malleswari
2020-04-14 17:07 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-19 15:59 ` bug#40485: " Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aa0f4995-3613-4115-07dc-3eac1a99214b@riseup.net \
--to=nagamalli@riseup.net \
--cc=40485@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).