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

Bug#2188: dpkg-ftp problems


>PACKAGE: dpkg-ftp
>VERSION: 1.3.1
>Thanks for making this workable thru a firewall.  Now, in case you've
>got a lot of time on your hands, here's the feedback from my initial
>usage.  Item (1) below is a trivial problem.  Subsequent items are
>not clear problems.
>1.  In message, "doesn't" is mis-spelt as "dosn't"

Well I can fix that.

>2.  Doesn't recognize "packages" filename with lowercase 'p'
>    (for ms-dos tree).

I call this a feature for now (see below 3).

>3.  (possibly out of scope) Will it work in the ms-dos tree at all?
>    Probably not, as the packages file doesn't have info on ms-dos
>    tree filename to package name mappings.  (I use a 150 MB transfer
>    disk to move packages to non-networked systems.  On some systems,
>    I need to run the disk thru a parallel port adapter and, the parallel
>    port adapter not being supported under Linux, that means that I must
>    use an MS-DOS filesystem on the transfer disk).

You are right, it won't work because the Filename: field in packages
dosn't contain the ms-dos filename.

>4.  (probably out of scope)  What I'd find very useful is to be presented
>    with a list of packages which are update candidates, and to be able to
>    select from those files and download selected ones for later installation
>    via another method direct dpkg install or dselect hard disk).  This could
>    be built into the ftp-dpkg processing which gets done from dselect's
>    [A]ccess choice.  Useful or not, though, whether this is in scope
>    for dpkg-ftp is more easily arguable con than pro.

I not quite sure what you are trying to do.  Currently you should get
the option to select which packages to download during Install.  It
also lists the packages it wants to download.  (It may also help you
to know that the info is in /var/lib/dpkg/methods/ftp/pkgs-to-get.)
The downloaded packages will be left in
/var/lib/dpkg/methods/ftp/binary until you tell the Install script to
delete them.  There is nothing stopping you running the Install script
and telling it to download no packages, you will then get the info you
want, download the packages in any fashion you like put them in the
..../ftp/binary directory and run install again and it should find
them.  I have tried to make all the scripts as bullet proof as
possible (unfortunately we now leave in the age of smart weapons :-)
so stopping and re-running them at any point shouldn't cause any harm
and in fact re-running install until it converges on a solution is in
fact what I often do (ftp gets interrupted or something goes wrong so
I get a few packages at a time).

Version: 2.6.2i


Reply to: