Bug#649508: marked as done (hplip on ppc)
Your message dated Fri, 10 Nov 2017 14:23:56 +0000
with message-id <10112017104103.6f360b98c538@desktop.copernicus.org.uk>
and subject line Re: Bug#649508: hplip on ppc
has caused the Debian Bug report #649508,
regarding hplip on ppc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
649508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649508
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: hplip on ppc
- From: christian <dubyda@gmail.com>
- Date: Mon, 21 Nov 2011 18:52:44 +0100
- Message-id: <20111121175244.22665.6132.reportbug@ZOUK>
Package: hplip
Version: 3.10.6-2
Severity: important
Tags: d-i
While installing hplip on ppc, I must install the binary plugin manually. This is OK but later in the
install process of my "HP laserjet m1212nf MFP", I get the following error message :
"OSError: /usr/share/hplip/fax/plugins/fax_marvell.so: l'encodage des donn?es du fichier ELF n'est pas big-endian"
I notice this :
lrwxrwxrwx 1 root root 50 21 nov. 17:38 fax_marvell.so -> /usr/share/hplip/fax/plugins/fax_marvell-x86_32.so
-- System Information:
Debian Release: 6.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.32-5-powerpc
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages hplip depends on:
ii adduser 3.112+nmu2 add and remove users and groups
ii coreutils 8.5-1 GNU core utilities
ii cups 1.4.4-7 Common UNIX Printing System(tm) -
ii cups-client 1.4.4-7 Common UNIX Printing System(tm) -
ii hplip-cups 3.10.6-2 HP Linux Printing and Imaging - CU
ii hplip-data 3.10.6-2 HP Linux Printing and Imaging - da
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libcups2 1.4.4-7 Common UNIX Printing System(tm) -
ii libdbus-1-3 1.2.24-4+squeeze1 simple interprocess messaging syst
ii libhpmud0 3.10.6-2 HP Multi-Point Transport Driver (h
ii libsane 1.0.21-9 API library for scanners
ii libsane-hpaio 3.10.6-2 HP SANE backend for multi-function
ii libssl0.9.8 0.9.8o-4squeeze4 SSL shared libraries
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii policykit-1 0.96-4+squeeze1 framework for managing administrat
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-dbus 0.83.1-1 simple interprocess messaging syst
ii python-imaging 1.1.7-2 Python Imaging Library
ii python-pexpect 2.3-1 Python module for automating inter
ii python-support 1.0.10 automated rebuilding support for P
Versions of packages hplip recommends:
ii avahi-daemon 0.6.27-2+squeeze1 Avahi mDNS/DNS-SD daemon
ii sane-utils 1.0.21-9 API library for scanners -- utilit
Versions of packages hplip suggests:
pn hplip-doc <none> (no description available)
ii hplip-gui 3.10.6-2 HP Linux Printing and Imaging - GU
pn kdeprint | gtklp | xpp <none> (no description available)
ii python-notify 0.1.1-2+b2 Python bindings for libnotify
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: 649508-done@bugs.debian.org
- Subject: Re: Bug#649508: hplip on ppc
- From: Brian Potkin <claremont102@gmail.com>
- Date: Fri, 10 Nov 2017 14:23:56 +0000
- Message-id: <10112017104103.6f360b98c538@desktop.copernicus.org.uk>
- In-reply-to: <20111121175244.22665.6132.reportbug@ZOUK>
- References: <20111121175244.22665.6132.reportbug@ZOUK>
Dear Debian User,
Futher information on your issue was asked for a few months ago but
there has been no response to the rquest. Use of our limited, volunteer
supported resources is best served by not keeping around inactive bugs
for longer than desirable, so the report is now being closed.
You may, of course, wish to review the reported problem. It would be
appreciated if any future investigation could be conducted using the
testing or unstable distributions. If considered necessary, a new bug
report, possibly referencing this one, would be submitted.
Thank you for your report and understanding.
Regards,
Brian.
--- End Message ---
Reply to: