Midnight commander has the ability to read into many file formats, I find it very useful for inspecting rpms, but each time I open one of these a red box appears with the following (two times in the same box): error: incorrect format: unknown tag error: incorrect format: unknown tag After the error message mc reads the file correctly It seems the problematic tags are COPYRIGHT and SERIAL, the following diff applied to /usr/share/mc/extfs/rpm provides the desired behavior. aemaeth extfs # diff -u rpm_gentoo rpm --- rpm_gentoo 2008-08-10 13:16:02.000000000 +0200 +++ rpm 2008-06-28 11:54:00.000000000 +0200 @@ -95,10 +95,6 @@ echo "$FILEPREF 0 $DATE INFO/PACKAGER" test "`$RPM -qp --qf \"%{URL}\" \"$f\"`" = "(none)" || echo "$FILEPREF 0 $DATE INFO/URL" - test "`$RPM -qp --qf \"%{SERIAL}\" \"$f\"`" = "(none)" || - echo "$FILEPREF 0 $DATE INFO/SERIAL" - test "`$RPM -qp --qf \"%{COPYRIGHT}\" \"$f\"`" = "(none)" || - echo "$FILEPREF 0 $DATE INFO/COPYRIGHT" test "`$RPM -qp --qf \"%{EPOCH}\" \"$f\"`" = "(none)" || echo "$FILEPREF 0 $DATE INFO/EPOCH" test "`$RPM -qp --qf \"%{LICENSE}\" \"$f\"`" = "(none)" || @@ -106,8 +102,6 @@ else echo "$FILEPREF 0 $DATE INFO/PACKAGER" echo "$FILEPREF 0 $DATE INFO/URL" - echo "$FILEPREF 0 $DATE INFO/SERIAL" - echo "$FILEPREF 0 $DATE INFO/COPYRIGHT" echo "$FILEPREF 0 $DATE INFO/EPOCH" echo "$FILEPREF 0 $DATE INFO/LICENSE" fi @@ -156,8 +150,6 @@ INFO/PACKAGER) $RPM -qp --qf "%{PACKAGER}\n" "$f" > "$3"; exit 0;; INFO/URL) $RPM -qp --qf "%{URL}\n" "$f" >"$3"; exit 0;; INFO/BUILDTIME) $RPM -qp --qf "%{BUILDTIME:date}\n" "$f" >"$3"; exit 0;; - INFO/SERIAL) $RPM -qp --qf "%{SERIAL}\n" "$f" >"$3"; exit 0;; - INFO/COPYRIGHT) $RPM -qp --qf "%{COPYRIGHT}\n" "$f" >"$3"; exit 0;; INFO/EPOCH) $RPM -qp --qf "%{EPOCH}\n" "$f" >"$3"; exit 0;; INFO/LICENSE) $RPM -qp --qf "%{LICENSE}\n" "$f" >"$3"; exit 0;; INFO/RPMVERSION) $RPM -qp --qf "%{RPMVERSION}\n" "$f" >"$3"; exit 0;;
Use the "Create a New Attachment" button to attach your patch as an file, not going to copy'n'paste it from here.
Try 4.7.0_pre1, reopen if this is still a issue.
Reopen for correct resolution.
I've checked this one; seems to be fixed with 4.7.0_pre1.