Sven Joachim wrote:
On 2011-06-08 19:51 +0200, Brian wrote:
On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
Am I the only one still seeing Midnight Commander parse errors when
trying to look inside deb files ? This has been going on , in my case
for two months now. Is there a
On Thu, 09 Jun 2011 17:19:19 +1000
Scott Ferguson wrote:
> On 09/06/11 04:43, Sven Joachim wrote:
> > On 2011-06-08 19:51 +0200, Brian wrote:
> >
> >> On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
> >>
> >>>
> >>> Am I
On 2011-06-09 09:19 +0200, Scott Ferguson wrote:
> As I don't have any problems - does that mean this only affects Wheezy
> builds?
It only affects Wheezy installs, more precisely systems with perl 5.12
or later.
Sven
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a su
On 09/06/11 04:43, Sven Joachim wrote:
> On 2011-06-08 19:51 +0200, Brian wrote:
>
>> On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
>>
>>>
>>> Am I the only one still seeing Midnight Commander parse errors when
>>> trying to look insi
On 09/06/11 01:58, Frank McCormick wrote:
>
> Am I the only one still seeing Midnight Commander parse errors when
> trying to look inside deb files ? This has been going on , in my case
> for two months now. Is there a solution ?
>
>
>
No problems here
Squeeze with
On Wed, 08 Jun 2011 20:43:41 +0200
Sven Joachim wrote:
> On 2011-06-08 19:51 +0200, Brian wrote:
>
> > On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
> >
> >>
> >> Am I the only one still seeing Midnight Commander parse errors when
> >&g
On 2011-06-08 19:51 +0200, Brian wrote:
> On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
>
>>
>> Am I the only one still seeing Midnight Commander parse errors when
>> trying to look inside deb files ? This has been going on , in my case
>> for two m
Am Mittwoch, 8. Juni 2011 schrieb Brian:
> On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
> > Am I the only one still seeing Midnight Commander parse errors when
> > trying to look inside deb files ? This has been going on , in my case
> > for two months now
On Wed 08 Jun 2011 at 11:58:42 -0400, Frank McCormick wrote:
>
> Am I the only one still seeing Midnight Commander parse errors when
> trying to look inside deb files ? This has been going on , in my case
> for two months now. Is there a solution ?
It's the time to use ar
On 2011-06-08 17:58 +0200, Frank McCormick wrote:
> Am I the only one still seeing Midnight Commander parse errors when
> trying to look inside deb files ?
No, you're not alone.
> This has been going on , in my case
> for two months now. Is there a solution ?
See http://bugs.d
Frank McCormick wrote:
Am I the only one still seeing Midnight Commander parse errors when
trying to look inside deb files ? This has been going on , in my case
for two months now. Is there a solution ?
You're certainly not the only one.
I have not found a solution: it does not seem
Am I the only one still seeing Midnight Commander parse errors when
trying to look inside deb files ? This has been going on , in my case
for two months now. Is there a solution ?
--
-- Frank --
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
I just updated Sarge and got the following error:
Preconfiguring packages ...
parse error reading X server string `unknown'
parse error reading X server string `unknown'
What emitted these messages? Is this a problem?
--
Bill Wohler <[EMAIL PROTECTED]> http://www.newt.com/wohler/
On Mon, Apr 30, 2001 at 05:24:37PM +0200, cliff clifferson wrote:
> hi
>
> i have a wired problem with the header files.
> my box has debian 2.2 kernel 2.2.18, and sometimes when i want to
> compile programms gcc gives me errors like that :
>
> /usr/include/sys/socket.h:175: parse error before 's
14 matches
Mail list logo