[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#434159: marked as done ('ifp upload' not working)

Your message dated Mon, 19 Oct 2020 21:26:40 +0000
with message-id <[🔎] E1kUcfw-000HKZ-0I@fasolo.debian.org>
and subject line Bug#964468: Removed package(s) from unstable
has caused the Debian Bug report #434159,
regarding 'ifp upload' not working
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.)


-- 
434159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434159
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ifp-line-libifp
Version: 1.0.0.2-3
Severity: normal

*** Please type your report below this line ***

Hi,

after upgrading from 'sarge' to 'etch' I found that the 'ifp' command
line program appears not to be working properly. I took a look at the
changelog and README - can't see anything obvious.

I observe that:
  ifp list            works correctly
  ifp rm   foo.mp3    works with warnings
  ifp put  new.mp3    doesn't work
  ifp upload new.mp3  doesn't work

A bit more detail on 'putting'
  $ ifp put new.mp3
  wrn:  [ifp_delta] interesting, there were only 4 bytes.
  Detected: model IFP-795T, firmware 1.24, battery =[#   ], delta 1.0.0.0
  usage: put localfile
         put localdir
  unable to upload file: Bad address
  Operation not permitted

The wrn: line appears on 'rm' operations as well.

'put' worked ok in sarge (1.0.0.1-1) with the same hardware.
The 'ifpgui' program works fine, it is able to upload files.
(ifpgui does print one other warning on startup though:
 libifp.so: cannot open shared object file: No such file or directory )

I've attached straces of ifp doing the 'rm' and 'put' operations.

$ lsusb
Bus 001 Device 004: ID 4102:1007 iRiver, Ltd. iFP-700 series mp3/ogg vorbis player
Bus 001 Device 001: ID 0000:0000

see also lsusb-v.gz attached

One other thing that may be relevant - I'm using 'usbmount' to auto-mount
USB hard drives. But this device does not show up as a hard drive as far
as I can tell.

Cheers
Vince

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages ifp-line-libifp depends on:
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  libifp4                     1.0.0.2-3    communicate with iRiver iFP audio
ii  libusb-0.1-4                2:0.1.12-5   userspace USB programming library

ifp-line-libifp recommends no packages.

-- no debconf information

Attachment: ifp.strace.rm.gz
Description: Binary data

Attachment: ifp.strace.put.gz
Description: Binary data

Attachment: lsusb.-v.gz
Description: Binary data


--- End Message ---
--- Begin Message --- 
Version: 1.0.0.2-5+rm

Dear submitter,

as the package libifp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/964468

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---
Reply to: