Hi,

[email protected] wrote:

URL:http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
[...] [898812/898812] -> "./debian-12.8.0-amd64-BD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb [...]"
[1]Could not open `./debian-12.8.0-amd64-BD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
[...]' for input - excluded (Input/output error)

Somehow this looks like a problem with the local storage representation
of the downloaded file python3-impacket_0.10.0-4_all.deb .

The lack of this file in the resulting debian-12.8.0-amd64-BD-1.iso
will prevent the ISO from being verified by its published checksums
and it will prevent installation of python3-impacket_0.10.0-4_all.deb,
if that is desired.
The ISO is supposed to be bootable and all others of its packages to be installable from it.

----------------------------------------------------------------------
Now for the problematic file:

The messages look like it might have been successfully downloaded.
What do you get from

md5sum ./debian-12.8.0-amd64-BD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb

I get

60351904c1c37ea9167dba5131f3fac5 .../python3-impacket_0.10.0-4_all.deb

after
wget http://ftp.debian.org/debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
or
wget http://us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
alike.

This MD5 checksum matches the base64 encoded checksum in the file
debian-12.8.0-amd64-BD-1.jigdo
which i obtained by

wget https://cdimage.debian.org/debian-cd/current/amd64/jigdo-bd/debian-12.8.0-amd64-BD-1.jigdo

To get the checksum i did:

gunzip < debian-12.8.0-amd64-BD-1.jigdo | \
grep python3-impacket_0.10.0-4_all.deb

This yielded:
YDUZBMHDfqkWfbpRMfP6xQ=Debian:pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
of which i used the part before "=", padded up by "==" to 24 bytes, for

echo -n YDUZBMHDfqkWfbpRMfP6xQ== | base64 -d | od -t x1 | \
sed -e 's/^.......//' -e 's/ //g'

which yielded

60351904c1c37ea9167dba5131f3fac5

(The base64 encoding in .jigdo is peculiar. One has to replace "-"
characters by "+" and "_" by "/", to convert from RFC3548 "URL and
Filename Safe Alphabet" to RFC3548 "Base 64 Alphabet".
But in this case it works well without such a conversion.)

----------------------------------------------------------------------
Remedy proposal:

If the file python3-impacket_0.10.0-4_all.deb is missing or if its
MD5 sum is not 60351904c1c37ea9167dba5131f3fac5 , then you could try to download the file manually, verify it by md5sum, and put it where
jigdo-lite attempted to put it:
./debian-12.8.0-amd64-BD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian/pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb

Then run jigdo-lite again, so that it can find the file and insert it
into the resulting .iso image.

(If the jigdo-lite run does not work, then i guess that you could use the jigdo-lite input prompt "Files to scan:" to tell it to scan the directory
which contains
pool/main/i/impacket/python3-impacket_0.10.0-4_all.deb
In my wget example this would be
./debian-12.8.0-amd64-BD-1.iso.tmpdir/us.cdimage.debian.org/cdimage/snapshot/Debian
I guess because i never entered anything to "Files to scan:".
)


Have a nice day :)

Thomas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)