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 inside deb files ? This has been going on , in my case
for two
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
On Thu, 09 Jun 2011 17:19:19 +1000
Scott Ferguson prettyfly.producti...@gmail.com 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 the only one still seeing Midnight Commander
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
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 unsubscribe
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
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.debian.org/cgi-bin
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 -x. Or be patient.
http
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. Is there a solution ?
It's
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 solution ?
It's
On Wed, 08 Jun 2011 20:43:41 +0200
Sven Joachim svenj...@gmx.de 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
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 Iceweasel and Icedove backports
12 matches
Mail list logo
