On 01/20/17 10:11, Rick Stevens wrote:
> The code was probably written with UTF-8 locale characters and you may
> not be using the UTF-8 locale. You may need to do something similar to
>
> export LANG=en_US.UTF-8
> export LC_ALL=en_US.UTF-8
>
> in your spec file so things get built un
On 01/19/2017 04:21 PM, JD wrote:
> Ditto with fc25 src: mkvtoolnix-9.5.0-1.fc25.src.rpm
>
>
> On 01/19/2017 05:19 PM, JD wrote:
>> $ rpmbuild -v -bb mkvtoolnix.spec 2>&1 | tee mkvtoolnix.build.out
>>
>> .
>> .
>> .
>> WARNING: unable to read lib/avilib-0.6.10/avilib.c: invalid byte
>> sequence i
On 01/20/17 09:29, Ed Greshko wrote:
> works fine here
Even with the same WARNINGS
[egreshko@meimei ~]$ grep ^WARN mkvtoolnix.build.out
WARNING: unable to read lib/avilib-0.6.10/avilib.c: invalid byte sequence in
US-ASCII
WARNING: unable to read lib/avilib-0.6.10/avimisc.c: invalid byt
On 01/20/17 08:21, JD wrote:
> Ditto with fc25 src: mkvtoolnix-9.5.0-1.fc25.src.rpm
F25 is currently at mkvtoolnix-9.6.0-1
rpmbuild -v -bb rpm/SPECS/mkvtoolnix.spec 2>&1 | tee mkvtoolnix.build.out
.
.
.
[egreshko@meimei ~]$ tail mkvtoolnix.build.out
Checking for unpackaged file(s): /usr/lib/rpm
Ditto with fc25 src: mkvtoolnix-9.5.0-1.fc25.src.rpm
On 01/19/2017 05:19 PM, JD wrote:
$ rpmbuild -v -bb mkvtoolnix.spec 2>&1 | tee mkvtoolnix.build.out
.
.
.
WARNING: unable to read lib/avilib-0.6.10/avilib.c: invalid byte
sequence in US-ASCII
WARNING: unable to read lib/avilib-0.6.10/avimis
$ rpmbuild -v -bb mkvtoolnix.spec 2>&1 | tee mkvtoolnix.build.out
.
.
.
WARNING: unable to read lib/avilib-0.6.10/avilib.c: invalid byte
sequence in US-ASCII
WARNING: unable to read lib/avilib-0.6.10/avimisc.c: invalid byte
sequence in US-ASCII
WARNING: unable to read src/common/checksums/adler
Tom Horsley writes:
On Thu, 19 Jan 2017 10:41:41 -0500
Matthew Miller wrote:
> I don't think that's really a better question, because actually most of
> the complex other stuff _does_ happen in other processes. Take a look
> at /usr/lib/systemd for a variety of discrete parts.
>
> There are ple
On 01/19/2017 12:40 PM, Stephen Morris wrote:
> On 19/1/17 6:15 pm, Joe Zeff wrote:
>> On 01/18/2017 11:53 PM, Stephen Morris wrote:
>>> I've checked the KEY_MGMT value and it matches the entry in the
>>> associated keys file.
>>> I've also added the two WPA_ALLOW keys but they have made no differe
As some of you may know, every year Google hosts the Google Summer of
Code (GSoC), last year we participated with some decent results for a
few projects. I was just sending this heads up to those whom may be
interested in partaking as a mentor or student (even if you are already
a fedora contribut
On 19/1/17 6:15 pm, Joe Zeff wrote:
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys but they have made no difference
to NM acknowledging that the device can be connected to.
On 19/1/17 10:58 pm, Matthew Miller wrote:
On Thu, Jan 19, 2017 at 06:13:11PM +1100, Stephen Morris wrote:
Stephen, are you using NetworkManager?
I am still using NetworkManager, but I am having problems with it at
the moment with it not connecting to my usb wireless device, which
I'm still try
On 19/1/17 8:08 am, Samuel Sieb wrote:
On 01/18/2017 01:39 PM, Stephen Morris wrote:
What I don't understand is when there is a problem why it is always the
CIFS mount that is the one that fails, I would have expected it to be
random as to which one is the one that fails.
Is it possible that th
On Thu, Jan 19, 2017 at 12:48:33PM -0500, Tom Horsley wrote:
> An old system:
>
> root@ubuntu8d04x:~# ldd /sbin/init
> linux-vdso.so.1 => (0x7fff8b3ff000)
> libc.so.6 => /lib/libc.so.6 (0x7ff582d2a000)
> /lib64/ld-linux-x86-64.so.2 (0x7ff58308c000)
>
> A new s
Hi
I'm testing Electrum on Fedora 25 and I'm missing the support for
hardware wallet that Electrum is supposed to have. Do I need to install
some additional package or has this feature been omitted?
Cheers
Mark
___
users mailing list -- users@lists.fedo
On Thu, 19 Jan 2017 10:41:41 -0500
Matthew Miller wrote:
> I don't think that's really a better question, because actually most of
> the complex other stuff _does_ happen in other processes. Take a look
> at /usr/lib/systemd for a variety of discrete parts.
>
> There are plenty of things which co
On Thu, Jan 19, 2017 at 10:16:13AM -0500, Tom Horsley wrote:
> > Since it was in D state, it probably issued a blocking system call that
> > didn't return as expected and hung the application.
>
> Better question: Why is PID 1 the monolithic insanely complex "systemd"
> program? Why isn't PID 1 j
On Thu, 19 Jan 2017 07:06:23 -0800
Gordon Messmer wrote:
> > Good question. Why is systemd not reaping zombies, as PID 1 should be
> > doing?
>
>
> Since it was in D state, it probably issued a blocking system call that
> didn't return as expected and hung the application.
Better question:
On Thu, Jan 19, 2017 at 09:57:15AM -0500, Robert P. J. Day wrote:
> > You could probably use mod_session (maybe with mod_auth_form) to
> > provide similar functionality.
>
> i was starting to suspect something like that, i just didn't see it
> explicitly written down anywhere.
>
> has anyone
On 01/19/2017 04:02 AM, Sam Varshavchik wrote:
Good question. Why is systemd not reaping zombies, as PID 1 should be
doing?
Since it was in D state, it probably issued a blocking system call that
didn't return as expected and hung the application. Unless that
condition is reproducible, it'l
On Thu, 19 Jan 2017, Matthew Miller wrote:
> On Thu, Jan 19, 2017 at 08:44:57AM -0500, Robert P. J. Day wrote:
> > where does one find the mod_auth_tkt module for apache in current
> > fedora? or has it been subsumed into something else?
>
> AFAIK this was never updated upstream for Apache httpd
On Thu, Jan 19, 2017 at 08:44:57AM -0500, Robert P. J. Day wrote:
> where does one find the mod_auth_tkt module for apache in current
> fedora? or has it been subsumed into something else?
AFAIK this was never updated upstream for Apache httpd 2.4.
You could probably use mod_session (maybe with
where does one find the mod_auth_tkt module for apache in current
fedora? or has it been subsumed into something else?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
On Thu, Jan 19, 2017 at 11:06:35AM +, Patrick O'Callaghan wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1119787
> Just as a matter of interest, why does "After=network.target" even
> exist? In what circumstance would this ever be the right thing to do?
It exists for _shutdown_ orderin
On Wed, Jan 18, 2017 at 09:25:31PM -0600, Chris Adams wrote:
> Any service that can be configured to bind to a specific IP should have
> "After=network-online.target" rather than "After=network.target". This
> can be servers for web, mail, FTP, SSH, DNS, logging, and more.
>
> This is a long-stan
On Thu, Jan 19, 2017 at 06:13:11PM +1100, Stephen Morris wrote:
> >Stephen, are you using NetworkManager?
> I am still using NetworkManager, but I am having problems with it at
> the moment with it not connecting to my usb wireless device, which
> I'm still trying to sort out.
Is that the same net
Joe Zeff writes:
On 01/18/2017 10:18 AM, Rick Stevens wrote:
On 01/18/2017 09:33 AM, Joe Zeff wrote:
On 01/18/2017 09:20 AM, Rick Stevens wrote:
And yes, I agree...systemd is a spectacular failure.
This March, systemd will celebrate its 7th birthday. Complaints like
this are about as usefu
Joe Zeff writes:
On 01/18/2017 03:41 AM, Sam Varshavchik wrote:
top - 06:31:36 up 3 days, 21:37, 2 users, load average: 6.00, 6.00, 6.00
Tasks: 294 total, 1 running, 277 sleeping, 0 stopped, 16 zombie
Why do you have 16 zombies after just under 4 days?
Good question. Why is systemd
On Wed, 2017-01-18 at 21:25 -0600, Chris Adams wrote:
> Once upon a time, Rick Stevens said:
> > So, it launches
> > the network, says the network is up and moves along even though the
> > network isn't actually up. Your mount is sometimes attempted with a
> > functioning network and sometimes not
On 01/18/2017 11:53 PM, Stephen Morris wrote:
I've checked the KEY_MGMT value and it matches the entry in the
associated keys file.
I've also added the two WPA_ALLOW keys but they have made no difference
to NM acknowledging that the device can be connected to.
Do you have any way of testing the
On 19/1/17 10:22 am, Rick Stevens wrote:
On 01/18/2017 01:21 PM, Stephen Morris wrote:
On 19/1/17 3:43 am, Rick Stevens wrote:
On 01/18/2017 01:54 AM, Stephen Morris wrote:
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if yo
30 matches
Mail list logo
