From: Leo Famulari <leo@famulari.name>
To: Michael Rohleder <mike@rohleder.de>
Cc: 45405@debbugs.gnu.org
Subject: [bug#45405] [PATCH] gnu: Update Xfce base to 4.16.0.
Date: Thu, 24 Dec 2020 16:51:30 -0500 [thread overview]
Message-ID: <X+UNYt7oqop6ve3e@jasmine.lan> (raw)
In-Reply-To: <20201224132146.25275-1-mike@rohleder.de>
On Thu, Dec 24, 2020 at 02:21:46PM +0100, Michael Rohleder wrote:
> * gnu/packages/xfce.scm (xfdesktop): Update to 4.16.0.
[...]
> Tested with some vm-images and xfce-plugins. As far as I can tell, it looks good ;)
Thanks for the work and for telling us how tested it!
> I couldn't get the test for xfconf run, so I disabled it. If someone(TM) wants
> to take a look... (I'm a bit exhausted)
Okay. When your energy is renewed, can you send a message saying what
goes wrong and what you tried?
> Random Thoughts/Notes:
> Sooner or later we need the xfce-dev-tools packaged, because I tried building
> xfce4-xkb-plugin from upstream master and noticed it needs it.
> (Maybe the xfconf test is also supposed to run with it).
Could it be that xfce-dev-tools is needed when building from VCS, but
not for "real" releases?
> Also, I noticed that debian sid has added a new pkg xfce4-helper yesterday. Maybe
> something like this could be a good idea for us too...
What would that xfce4-helper package do? I couldn't find the new package
on Debian's web site.
next prev parent reply other threads:[~2020-12-24 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 13:21 [bug#45405] [PATCH] gnu: Update Xfce base to 4.16.0 Michael Rohleder
2020-12-24 21:51 ` Leo Famulari [this message]
2020-12-25 13:24 ` Michael Rohleder
2020-12-25 11:02 ` Jonathan Brielmaier
2020-12-25 11:43 ` Michael Rohleder
2021-01-13 15:15 ` Ludovic Courtès
2021-01-13 16:02 ` Michael Rohleder
2021-01-14 16:20 ` bug#45405: " Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X+UNYt7oqop6ve3e@jasmine.lan \
--to=leo@famulari.name \
--cc=45405@debbugs.gnu.org \
--cc=mike@rohleder.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.