unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: "Yao Wei (魏銘廷)" <mwei@lxde.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 01/11] gnu: lxterminal: Update to 0.3.0.
Date: Mon, 23 Jan 2017 21:06:34 +0000	[thread overview]
Message-ID: <87pojdbi5h.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87bmux5xix.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

Hi,

I have just updated our distributions lxterminal build, and I ran
into the problem described in the below quoted message.

I've seen no recent commit which obviously fixes this issue.
Could you look into it?

Thanks!

Marius Bakke <mbakke@fastmail.com> writes:

> contact.ng0@cryptolab.net writes:
>
>> From: ng0 <ng0@libertad.pw>
>>
>> * gnu/packages/lxde.scm (lxterminal): Update to 0.3.0.
>> [arguments]: Disable tests.
>> [source]: Update to use new '.tar.xz' tarball.
>
> Applied, thanks!
>
>> +    (arguments
>> +     `(; Tests fail for "po" fail with "No rule to make target '../src/encoding.c'
>> +       ;; needed by 'lxterminal.pot'. Stop."
>> +       #:tests? #f))
>
> This is strange. The "po" makefile refer to a file "encoding.c" that is
> missing in the release tarball. Could you report this issue upstream?
>
> The 'check' phase is autotools-generated and does not seem to run any
> actual tests, so I assume this file is not needed. Nothing else refers
> to it.

-- 
♥Ⓐ  ng0 -- https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-01-23 21:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 18:55 Add lxde. (Mixed content: 4 updates, 7 RFCs) contact.ng0
2017-01-23 18:55 ` [PATCH 01/11] gnu: lxterminal: Update to 0.3.0 contact.ng0
2017-01-23 20:31   ` Marius Bakke
2017-01-23 21:06     ` ng0 [this message]
2017-01-23 21:08       ` ng0
2017-01-24  4:26       ` Yao Wei
2017-01-23 18:55 ` [PATCH 02/11] gnu: pcmanfm, libfm: Update to 1.2.5 contact.ng0
2017-01-23 18:55 ` [PATCH 03/11] gnu: menu-cache: Update to 1.0.2 contact.ng0
2017-01-23 18:55 ` [PATCH 04/11] gnu: Add lxmenu-data contact.ng0
2017-01-23 18:55 ` [PATCH 05/11] gnu: Add lxde-icon-theme contact.ng0
2017-01-23 18:55 ` [PATCH 06/11] gnu: Add lxde-common contact.ng0
2017-01-23 22:10   ` Marius Bakke
2017-01-23 23:21     ` ng0
2017-01-23 23:41       ` ng0
2017-01-23 18:55 ` [PATCH 07/11] gnu: Add lxinput contact.ng0
2017-01-23 18:55 ` [PATCH 08/11] gnu: Add lxsession contact.ng0
2017-01-23 18:55 ` [PATCH 09/11] gnu: Add keybinder contact.ng0
2017-01-23 18:55 ` [PATCH 10/11] gnu: Add lxpanel contact.ng0
2017-01-23 18:55 ` [PATCH 11/11] gnu: Add lxde contact.ng0
2017-01-23 19:45   ` Albin
2017-01-23 23:18     ` ng0
2017-01-23 23:29 ` Add lxde. (Mixed content: 4 updates, 7 RFCs) ng0
2017-01-24  0:10   ` ng0
2017-01-24  1:13     ` ng0

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=87pojdbi5h.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=contact.ng0@cryptolab.net \
    --cc=guix-devel@gnu.org \
    --cc=mwei@lxde.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).