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://www.midnight-commander.org/ticket/2552


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110608175159.GJ19914@desktop">http://lists.debian.org/20110608175159.GJ19914@desktop

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 the time to use ar -x. Or be patient.
>
> http://www.midnight-commander.org/ticket/2552

You are not the only one. I am missing this option, too.
It was quite comforttable for a quick look into a package.

Hope, it will be fixed soon.

Cheers

Hans


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201106082013.33231.hans.ullrich@loop.de">http://lists.debian.org/201106082013.33231.hans.ullrich@loop.de

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 the time to use ar -x. Or be patient.

Nah, neither. This is free software after all…

> http://www.midnight-commander.org/ticket/2552

…and there's even a patch available! The bug is in a perl script
(/usr/lib/mc/extfs.d/deb) that you can edit directly if you don't care
about debsums complaining:

--8<---------------cut here---------------start------------->8---
--- deb.orig 2010-09-08 00:00:00.000000000 +0200
+++ deb 2011-05-10 15:46:07.000000000 +0200
@@ -46,7 +46,7 @@
{
while(<PIPEIN>)
{
- split;
+ @_ = split;

$perm=$_[0]; $owgr=$_[1]; $size=$_[2];
if($_[3] =~ /^dddd-/) { # New tar format
@@ -100,7 +100,7 @@
{
while(<PIPEIN>)
{
- split;
+ @_ = split;
$size=$_[0];
last if $size =~ /:/;
next if $size !~ /d+/;
--8<---------------cut here---------------end--------------->8---

Rebuilding the package is of course cleaner, but I was too lazy to
do that.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87pqmop3j6.fsf@turtle.gmx.de">http://lists.debian.org/87pqmop3j6.fsf@turtle.gmx.de

On Wed, 08 Jun 2011 20:43:41 +0200
Sven Joachim <svenjoac@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 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.
>
> Nah, neither. This is free software after all…
>
> > http://www.midnight-commander.org/ticket/2552
>
> …and there's even a patch available! The bug is in a perl script
> (/usr/lib/mc/extfs.d/deb) that you can edit directly if you don't care
> about debsums complaining:
>
> --8<---------------cut here---------------start------------->8---
> --- deb.orig 2010-09-08 00:00:00.000000000 +0200
> +++ deb 2011-05-10 15:46:07.000000000 +0200
> @@ -46,7 +46,7 @@
> {
> while(<PIPEIN>)
> {
> - split;
> + @_ = split;
>
> $perm=$_[0]; $owgr=$_[1]; $size=$_[2];
> if($_[3] =~ /^dddd-/) { # New tar format
> @@ -100,7 +100,7 @@
> {
> while(<PIPEIN>)
> {
> - split;
> + @_ = split;
> $size=$_[0];
> last if $size =~ /:/;
> next if $size !~ /d+/;
> --8<---------------cut here---------------end--------------->8---
>
> Rebuilding the package is of course cleaner, but I was too lazy to
> do that.

I was too lazy even to use patch. I edited the file directly. It
works! Thanks


--
-- Frank --


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110608172921.a5b9ab01.debianlist@videotron.ca">h ttp://lists.debian.org/20110608172921.a5b9ab01.debianlist@videotron.ca

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, i386, KDE.
dpkg --get-selections | grep zip
bzip2 install
gzip install
libzip1 install
p7zip-full install
unzip install
zip install

tiny image attached:-
In left pane I've opened a .deb file
and menu is open showing installed compression formats.

Cheers

--
Tuttle? His name's Buttle.
There must be some mistake.
Mistake? [Chuckles]
We don't make mistakes.

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 months now. Is there a solution ?
>>
>> It's the time to use ar -x. Or be patient.
>
> Nah, neither. This is free software after all…
>
>> http://www.midnight-commander.org/ticket/2552
>
> …and there's even a patch available! The bug is in a perl script
> (/usr/lib/mc/extfs.d/deb) that you can edit directly if you don't care
> about debsums complaining:
>
<snipped>

As I don't have any problems - does that mean this only affects Wheezy
builds?

NOTE: I'm running ext4


Cheers


--
Tuttle? His name's Buttle.
There must be some mistake.
Mistake? [Chuckles]
We don't make mistakes.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DF073F7.1010405@gmail.com">http://lists.debian.org/4DF073F7.1010405@gmail.com

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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87r573zb34.fsf@turtle.gmx.de">http://lists.debian.org/87r573zb34.fsf@turtle.gmx.de

On Thu, 09 Jun 2011 17:19:19 +1000
Scott Ferguson <prettyfly.productions@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 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.
> >
> > Nah, neither. This is free software after all…
> >
> >> http://www.midnight-commander.org/ticket/2552
> >
> > …and there's even a patch available! The bug is in a perl script
> > (/usr/lib/mc/extfs.d/deb) that you can edit directly if you don't care
> > about debsums complaining:
> >
> <snipped>
>
> As I don't have any problems - does that mean this only affects Wheezy
> builds?
>
> NOTE: I'm running ext4

I'm running Sid (up to date) - it's now fixed thanks to a patch.
But I don't understand why it doesn't affect Wheezy ??


--
-- Frank --


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110609094422.8dc35c85.debianlist@videotron.ca">h ttp://lists.debian.org/20110609094422.8dc35c85.debianlist@videotron.ca

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 solution ?

It's the time to use ar -x. Or be patient.


Nah, neither. This is free software after all…


http://www.midnight-commander.org/ticket/2552


…and there's even a patch available! The bug is in a perl script
(/usr/lib/mc/extfs.d/deb) that you can edit directly if you don't care
about debsums complaining:

--8<---------------cut here---------------start------------->8---
--- deb.orig 2010-09-08 00:00:00.000000000 +0200
+++ deb 2011-05-10 15:46:07.000000000 +0200
@@ -46,7 +46,7 @@
{
while(<PIPEIN>)
{
- split;
+ @_ = split;

$perm=$_[0]; $owgr=$_[1]; $size=$_[2];

if($_[3] =~ /^dddd-/) { # New tar format
@@ -100,7 +100,7 @@
{
while(<PIPEIN>)
{
- split;
+ @_ = split;
$size=$_[0];
last if $size =~ /:/;
next if $size !~ /d+/;
--8<---------------cut here---------------end--------------->8---

Rebuilding the package is of course cleaner, but I was too lazy to
do that.



Thanks. I missed that patch.
Still running mc 2:4.6.2~git20080311-4 and for that the deb script is in


/usr/share/mc/extfs.
Works great.

Hugo







--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: isr3qc$ni7$1@dough.gmane.org">http://lists.debian.org/isr3qc$ni7$1@dough.gmane.org