Bug#980217: ipp-usb: should this be Multi-Arch: foreign?

2021-02-19 Thread Alexander Pevzner

Hi Didier,

I don't know how to correctly explain it in terms of Debian packaging 
rules, but conceptually, yes, ipp-usb:i386 should be satisfied by 
ipp-usb:amd64 and visa versa.


I'll Cc: this conversation to Zdenek, because the same idea may be 
applied to Fedora packaging too.


And probably, the same is true for the ARM32/ARM64 combination.

On 2/19/21 8:39 PM, Didier 'OdyX' Raboud wrote:

Hello Alexander,

As ipp-usb author; do you have an opinion/advice about this?

Many thanks in advance, cheers,

OdyX

Le samedi, 16 janvier 2021, 12.19:15 h CET Simon McVittie a écrit :

Package: ipp-usb
Version: 0.9.16-1
Severity: minor

A recent update to wine32:i386 on my amd64 system pulled in libsane1:i386,
which Recommends ipp-usb. Because ipp-usb is Multi-Arch: no, apt
interprets this as wanting to install ipp-usb:i386, which conflicts
with ipp-usb:amd64.

ipp-usb seems to be a daemon (systemd service) that is contacted via
IPC, conceptually similar to avahi-daemon, dbus-daemon or cups - which
hopefully means that it doesn't matter which architecture's ipp-usb
you have, because libsane1:amd64, libsane1:i386 and libsane1:mipsel
all speak the same architecture-independent IPC protocol to communicate
with ipp-usb?

If that's the case, then ipp-usb should be marked Multi-Arch: foreign,
which means that libsane1:i386 Recommends: ipp-usb would be satisfied
by ipp-usb:amd64.





--

Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#982742: solved

2021-02-15 Thread Alexander Pevzner

On 2/16/21 4:31 AM, mh wrote:

comparing avahi settings was much less pain then I expected.


Congratulations!


had an active (non commented out) line:

allow-interfaces=eth9


Which effectively protected Avahi from being working on all another 
interfaces, including the loopback interface.


Nice that this problem has been finally solved.

--

Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

2021-02-15 Thread Alexander Pevzner

Hi,

with a help of Michael, I've investigated this problem down to its root 
cause, which appeared to be a misbehabing Avahi daemon.


If in one console the following command is being running:
avahi-publish -s test _test._tcp 0

The following command running in another console prints nothing:
avahi-browse -rt _test._tcp

As I'm not very familiar with Avahi troubleshooting, any help or ideas 
are welcome.


--

    Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#982742: cups: config of usb printer now impossible due to usblp and libusb conficting (used to work!)

2021-02-15 Thread Alexander Pevzner

Michael,

On 2/15/21 2:01 PM, Till Kamppeter wrote:
Michael Hatzold (CCed) reports a problem with ipp-usb. The printer 
provides a 7/1/4 interface on USB, meaning that it supports IPP-over-USB 
and with this, according to the standards, driverless printing (and 
scanning if it is a MFP).


I'm the author of ipp-usb, and I want to investigate this problem.

May I ask you to gather ipp-usb logs? To do so, please do the following:
1. Remove all old ipp-usb logs (rm /var/log/ipp-usb/*)
2. Restart ipp-usb and reproduce a problem
3. Send me all files from the /var/log/ipp-usb/ directory

--

Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#973951: ipp-usb: Fails to restart

2020-11-08 Thread Alexander Pevzner

Hi Tollef,

I'm the author of ipp-usb

Please, send me logs, all files under the /var/log/ipp-usb/*

--

Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#964446: sane-airscan stuck in NEW

2020-08-05 Thread Alexander Pevzner

Hi Till, OdyX, Zdenek,

I've just created the new 0.99.12 release, and I highly recommend to 
upgrade existent packaging.


All technical details were posted to the 
sane-de...@alioth-lists.debian.net mailing list.


On 8/4/20 9:17 PM, Till Kamppeter wrote:

Great, so I will base my Ubuntu package also on the new version.

OdyX, could you update the Debian packaging appropriately, too? Thanks.

    Till

On 04/08/2020 20:10, Alexander Pevzner wrote:
I think I will merge -unstable in few hours and will release result as 
0.99.12. It would be nice, if Debian will synchronize with .12, not 
.11 (otherwise we will wait a couple of month before next chance to 
synchronize).


As .12 drops dependency on libsoup and libglib, and adds dependency on 
gnutls, it will require packaging to be tweaked a little bit.



--

Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#961218: ipp-usb Packaging some more remarks

2020-07-16 Thread Alexander Pevzner

Hi Didier,


No you didn't. I just had this mail in my outbox (but not sent) for a week; it
just went out now as I logged back on my laptop.

It's just some time-warping :-)


I have a similar problem on OBS, and as a dirty workaround I simply 
unpack on a build machine an archive that contains go cache of all 
downloaded dependencies. Not very convenient, but it works.


If problem still exist, after a week of labtop being not used :-), I can 
put release tag on goipp. As go dependencies are versioned, I will have 
to update and re-release the ipp-usb too.


Note, the goipp library is not expected to be updated very often.

--

    Wishes, Alexander Pevzner (p...@apevzner.com)



Bug#964446: RFP: sane-airscan - SANE backend for AirScan (eSCL) and WSD document scanners

2020-07-07 Thread Alexander Pevzner

Hi OdyX,


For the record, I am primarily concerned about the printing support in Debian,
which packaging I carry mostly alone (I get great help from Brian Potkin for
bug triaging, and Till Kamppeter for upstream and Ubuntu support). I don't
really intend to also start carrying the scanning stack on my shoulders too.


I already provide Debian packages, build on OpenSUSE Build Services, so 
this software proven to build and work on Debian.


Technically, the question is in integration it with the official Debian 
packaging process.


Actually, sane-airscan is not capricious in building and packaging.

Regarding technical support, I can provide it for Debian users as well 
as I already provide it for users of my own packages, assuming I will be 
somehow notified if user files bug to Debian bug tracking system.


--

Wishes, Alexander Pevzner (p...@apevzner.com)