Package: jigdo-file
Version: 0.8.1-1+b1
Severity: normal
Tags: upstream
X-Debbugs-Cc: [email protected]
The man page has:
manpg> NAME
manpg> jigdo-lite - Download jigdo files using wget
manpg>
manpg> SYNOPSIS
manpg> jigdo-lite [ URL ]
The help page has:
help> Usage: /usr/bin/jigdo-lite [OPTIONS] [FILES or URLS...]
Man page problems:
The man page incorrectly implies that local files cannot be supplied
with a simple filename -- that they must be in an URL format. The
short description in the first section incorrectly implies that this
“lite” tool is only used to fetch the *.jigdo files and nothing
else. It would be better to write something like:
“Downloads jigdo metadata (if needed) and the payload data specified by it
(as needed).”
Help page problems:
The BNF is incorrect but probably understandable enough to most. The
flaw is that -h and -v are mutually exclusive to everything
else. This would be more accurate:
Usage: /usr/bin/jigdo-lite [-h|-v|[OPTIONS] [files|URLS...]]
Judging from this line in the config: “jigdoOpts='--cache
jigdo-file-cache.db'”,
--cache is also an option. It is missing in both the help page and man page.
mini how-to problems from
file:///usr/share/doc/jigdo-file/debian-jigdo-mini-howto.html:
> 2.3 …
>
> “jigdo-lite uses wget which, by default, uses http to transfer
> files. Unlike rsync, http is never blocked by firewalls (except the
> ones behind which you shouldn't be using jigdo to begin with).”
This might have been accurate in 2005 but these days HTTP is the
*worst* as far as being encumbered by blockades and countless
varieties of enshitification. I’m surprised rsync is said to have such
issues, but I find FTP to be less prone to nannying obstacles.
Considering jigdo is not limited to large Debian images, it seems a
bit off to tell users what networks they should not be using jigdo
on. Although it is a Debian how-to, jigdo could be used to do a small
update.
> 4.1 …
>
> “Jigdo is under aggressive development. Bug fixes and enhancements
> are constant, so if you're using stable or testing, download
> jigdo-file from unstable at
> http://packages.debian.org/unstable/utils/jigdo-file.html.
> As of 28 Nov 2005 it's at version 0.7.2-2.”
That statement is 20 yrs old; probably should be removed.
> 6.12. For image updates, I want jigdo-lite to scan 14 loop-mounted images in
> one go. How can I do this?
It would be good to mention xorriso in this section. Perhaps reference
https://wiki.debian.org/MergeDebianIsos
> 6.18. Can I run multiple instances of jigdo-lite to download images in
> parallel?
>
> Absolutely. However, to avoid filename clashing, you should run each
> jigdo-lite instance in its own separate directory.
That’s inconvenient. I can only imagine name clashing in $CWD with
jigdo-file-cache.db. Is that the issue? Is the DB unable to handle
concurrency? If true, then --cache should be documented because it
would enable multiple instances to share the same $CWD.
The current answer ignores the fact that the config file is
hard-coded. It’s surprising that that is not a problem. Isn’t there a
race condition with the config file whereby concurrent instances would
be affected by each other’s settings?
It’s worth noting that it would be very useful for each concurrent
jigdo instance to pull from a different mirror. The hard-coded config
file complicates that for non-interactive launches. IIUC, each
instance would need a TCL/Expect wrapper script to supply a different
mirror. Correct? Maybe this should be mentioned in the mini how-to.
> Be aware that jigdo-lite is bandwidth and CPU intensive, so you
> won't want to use your computer with multiple instances running in
> tandem.
I would change that to: “Be aware that jigdo-lite is bandwidth and CPU
intensive, so you will want to use nice and ionice commands when
simultaneously using your computer’s UI.”
-- System Information:
Debian Release: 12.12
APT prefers oldstable-updates
APT policy: (990, 'oldstable-updates'), (990, 'oldstable-security'), (990,
'stable'), (990, 'oldstable'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-28-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages jigdo-file depends on:
ii libbz2-1.0 1.0.8-5+b1
ii libc6 2.36-9+deb12u13
ii libdb5.3 5.3.28+dfsg2-1
ii libgcc-s1 12.2.0-14+deb12u1
ii libstdc++6 12.2.0-14+deb12u1
ii wget 1.21.3-1+deb12u1
ii zlib1g 1:1.2.13.dfsg-1
jigdo-file recommends no packages.
jigdo-file suggests no packages.
-- no debconf information
