Github messages for voidlinux
 help / color / mirror / Atom feed
From: heindsight <heindsight@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hplip: Update to 3.21.10
Date: Tue, 09 Nov 2021 20:30:10 +0100	[thread overview]
Message-ID: <20211109193010.HDXRU6igD9N3YAKTmXqhrLgZjIjrKLSPQ6pdmoQs1yA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33832@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

New comment by heindsight on void-packages repository

https://github.com/void-linux/void-packages/pull/33832#issuecomment-964467812

Comment:
@biopsin That's rather strange. Could you rebuild with ` -UNDEBUG -DHPMUD_DEBUG -DESCL_DEBUG` added to the `CFLAGS` set in the template?

Then run:
```
scanimage -T -d hpaio:/net/HP_Neverstop_Laser_MFP_120x?ip=192.168.1.201 --verbose
```
while tailing syslog? That might give some more insight into where things are going wrong.

  parent reply	other threads:[~2021-11-09 19:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 18:07 [PR PATCH] hplip: Update to 3.21.8 heindsight
2021-10-31  8:40 ` biopsin
2021-11-04 13:38 ` biopsin
2021-11-05 10:26 ` biopsin
2021-11-05 17:55 ` heindsight
2021-11-05 18:43 ` [PR PATCH] [Updated] " heindsight
2021-11-05 20:16 ` [PR PATCH] [Updated] hplip: Update to 3.21.10 heindsight
2021-11-09 13:20 ` biopsin
2021-11-09 19:30 ` heindsight [this message]
2021-11-23 10:01 ` biopsin
2021-11-28 11:46 ` [PR PATCH] [Updated] " heindsight
2021-12-06 21:42 ` ahesford
2021-12-07 20:27 ` biopsin
2021-12-08  1:05 ` [PR PATCH] [Merged]: " ahesford
2021-12-30 11:25 ` biopsin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211109193010.HDXRU6igD9N3YAKTmXqhrLgZjIjrKLSPQ6pdmoQs1yA@z \
    --to=heindsight@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).