Hi,
Roland Clobus wrote:
> The latest gnome image took 3 hours according to the log [2].
> [2]
> https://get.debian.org/images/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-gnome.log
> (from 03:12:32 to 06:04:48)
Interesting log. There are two time zones used in two kinds of
Hi,
Juan Manuel wrote:
> I have downloaded the latest version of debian12. I
> have the GNU4win program with kleopatra but I don't know how to check the
> digital signature.
Do i get it right that you have an MS-Windows system ?
(And that by "GNU4win" you mean "GPG4win" ?)
If so, you need a
Hi,
Tatsu Takamaro wrote:
> I've received my own message to you. But I don't see your answer...
Well, i have't seen that message and the mailing list archive doesn't
show it either:
https://lists.debian.org/debian-cd/2024/03/threads.html
(The one i reply to is your follow-up:
Hi,
Thomas Lange wrote:
> Maybe you can check if there's a problem with DVD17.
What's the exact URL of .jigdo and .template file which was tried ?
For now i tested the offer for amd64 debian-12.4.0 (demonstrating the wget
workaround for a long fixed bug in older jigdo-lite about https):
$
Hi,
i wrote:
> >Does any of the bystanders know from what package this message text stems ?
Steve McIntyre wrote:
> That's cdrom-checker:
So that would be indirectly put into the code at
https://sources.debian.org/src/cdrom-checker/1.62/main.c/?hl=152#L152
by "Template:
Hi,
trying to get our mails in sync again. We seem to have reached consensus
in our understanding of the problem.
i wrote:
> > might possibly be "WPSettings.dat", which causes questions in the
> > internet.
Ram Reddy wrote:
> I think that this could possibly be explained by flaws in my testing.
Hi,
Ram Reddy wrote:
> Thomas Schmitt wrote:
> > FWIW check the BIOS L[123] cache settings [...]
This was posted by Nicholas Geovanis , not by me.
My suspicion is that the Lenovo Legion EFI BIOS intentionally creates
directories and empty file "/efi/Lenovo/BIOS/SelfHealing.fd&
Hi,
Ram Reddy wrote:
> https://drive.google.com/file/d/1Zd6iufVRsfIu-qzC-tJx4FEvCOESOz4_/view?usp=sharing
I downloaded the tarball and compared the original FAT filesystem with the
various modified filesystem images.
--
In
Hi,
Ram Reddy wrote:
> I tested the installer on one of my laptops, and found that its contents
> didn't change.
Good to know that the software in the ISO still works from read-only DVDs.
> On the Lenovo Legion 7i Gen 5*, Lenovo Thinkpad X1 Carbon Gen 2*, Lenovo
> Thinkpad X1 Carbon Gen 5
Hi,
Ram Reddy wrote:
> [...] usb drive [...] debian-12.2.0-amd64-netinst.iso [...]
> [...] Integrity Test section [...]
> ./boot/grub/efi.img failed the MD5 checksum verification. Your installation
> media or this file may have been corrupted.
> [...]
> It was always byte 2303211, line 21165
Hi,
congrats for solving this long standing problem.
A few years ago this would have been great news for Knoppix, which staid
for quite a while with SYSLINUX for EFI. But somewhere between versions
8.6 (2019) and 9.3 (2022) it switched to GRUB.
Although the most recent commit on
Hi,
Philip Hands wrote:
> While looking at the FSF site, I noticed this somewhat amusing method
> for reconciling these two stances:
> https://www.gnu.org/philosophy/install-fest-devil.html
Typically Stallman:
"My new idea is that the install fest could allow the devil to hang
around, off
Hi,
griffin tucker wrote:
> not just useful for debian or linux distros, but any consecutively
> named .iso9660 files
I assume that the script merge_debian_isos is mainly usable with a set of
ISOs made by the debian-cd package. The files of which the content gets
manipulated are probably
Hi,
griffin tucker wrote:
> are there any plans to introduce triple-layer blu-rays for debian?
I guess not:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343
But there is a workaround:
https://wiki.debian.org/MergeDebianIsos
Possibly it is not yet tested with Debian 12. So reports
Hi,
when comparing 12.0.0 with 11.5.0 i see three file trees which have grown
substantially:
du of mounted debian-11.5.0-amd64-netinst.iso :
5 /firmware
126611 /install.amd
308479 /pool
du of mounted debian-12.0.0-amd64-netinst.iso :
221108 /firmware
156509 /install.amd
Hi,
there is already a bug report about a similar problem
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988120
It points to file
jigdo-file-cache.db
and mentions a positive one-time effect, which would match the observation
that the first medium nearly always succeeds.
It works if
Hi,
(Possibly your attachments did not make it to the mailing list.
I got only the mail which was sent directly to me.)
griffin tucker wrote:
> img-debian-12.0.0-source-bd_to_dvd_1_of_2-77429.asc
> ...
> Found 2840 of the 2840 files required by the template
> Successfully created
Hi,
griffin tucker wrote:
> jigdo-lite runs in batch mode, and usually the reconstruction of the
> first .iso is completely reconstructed from a directory of mounted
> .iso's from another format, however, the next few .iso's will
> consistently have 1 file missing that it couldn't find from the
>
Hi,
griffin tucker wrote:
> there's a bug in jigdo that makes it occasionally skip files
In that case the missing files woule be present but filled with zeros
when you mount the incompletely composed ISO.
Can you confirm ?
Not picking a file of a jigdo image may have various reasons.
Temporary
Hi,
(Cc-ing the mailing list debian-cd@lists.debian.org again.)
Muhammad Owais wrote:
> However there is still an issue if I am a windows user how can I use Jigdo.
Steve McIntyre, a Debian Developer who is in charge for debian-cd, offers
binaries for MS-Windows:
Hi,
i'm Cc-ing the mailing list debian-cd@lists.debian.org again.
Please don't expect that i reply to private mails or keep them private,
unless your mail contains a good reason why it shall stay private.
Muhammad Owais wrote directly to my mail address:
> As I found the DVD over here I need
Hi,
Muhammad Owais wrote:
> I couldn't find the
> page from where I can download the Debian 9.7 Complete 3 DVD set.
Choose your CPU type from
https://cdimage.debian.org/mirror/cdimage/archive/9.7.0/
E.g.
https://cdimage.debian.org/mirror/cdimage/archive/9.7.0/amd64/jigdo-dvd/
Have a nice
Hi,
Ricardo Romanach wrote:
> I am currently attempting to create an ISO file from an existing
> Debian 11 installation.
Google found me
https://github.com/pieroproietti/penguins-eggs
"penguins-eggs is a console utility, under continuous development,
that allows you to remaster your
Hi,
Pete Batard wrote:
> Debian does not use an efi.img.
Oh it does with ISOs for i386 and amd64. There is a data file in the ISO
filesystem named
/boot/grub/efi.img
advertised as MBR partition of type 0xEF and as El Torito boot image
for EFI:
$ xorriso -indev
Hi,
James Addison wrote:
> The problem, in both cases, was that I hadn't copied the '.disk' dotfile
> directory from the install media ISO filesystem(s) in each case.
Besides such user pitfalls with the produced ISO and the problem of
symbolic links there are other constraints which an ISO has
Hi,
the use of xorrisofs/genisoimage option -f would convert those links
into shared content data files, too.
Side note:
Differing from my statement in bug #1031696, the current xorriso version
does not complain about dangling symbolic links when -f is given. It
silently includes them as
Hi,
James Addison wrote:
> Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS
> achieve the desired result for both documentation and firmware files,
> without requiring any other changes?
Let's pack up some symbolic links with -f:
$ sudo mount
Hi,
James Addison wrote:
> Please find below a proposed update to the commit message under discussion:
Only one nitpick:
> multiple filenames ("records"). The ISO9660 generation tools
> genisoimage and xorriso can use this to de-duplicate multiple linked
> files from their input,
Hi,
James Addison wrote:
> I've opened a merge request at
> https://salsa.debian.org/images-team/debian-cd/-/merge_requests/30
> [...]
> The commit message contains an effort to explain what's going on; please
> consider that message as reviewable and open to feedback too.
I'm clumsy with web
Hi,
James Addison wrote:
> My interpretation of the commands and output in your comment is that both
> genisoimage and xorriso can translate hardlinks from a source filesystem
> into deduplicated file references in a written ISO filesystem
With genisoimage we only know empirically. With libisofs
Hi,
James Addison wrote:
> it looks like the selection of CD image
> creation tool is configured per-architecture here:
> https://salsa.debian.org/images-team/debian-cd/-/blob/5aebb6794a3b8b2393663fb643e35eb8e510c9a4/Makefile#L24
I wish i would understand the clause
ifneq (,$(filter i386 amd64
Hi,
James Addison wrote:
> Something that symlinks can do is to allow image creators to save space by
> by de-duplicating files. [...]
This could be achieved by a bunch of hard links instead of the symbolic
links. In /firmware of firmware-bookworm-DI-alpha1-amd64-netinst.iso
i see only symbolic
Hi,
just for the records i report what Gerd Mühlenbruch and i found out
off list:
The reason for the bad dowload was that two wget processes were writing
to the same file.
Gerd had started the first wget by letting nautilus executing it. For
this it created a terminal window with a running
Hi,
Gerd Mühlenbruch wrote:
> nautilus is starting a bash terminal.
Do you know which program it runs in there ?
(And with which arguments ?)
> After the break it told me a size of 7.900 Byte.
> ls -l is telling me 150431900 which is huge for the short download time.
I would guess that the
Hi,
Gerd Mühlenbruch wrote:
> So, it seems to be a problem of nautilus on my computer.
wget -c still has a share in this.
But currently i have no ideas how to find out what makes an incomplete
nautilus download so confusing for wget.
> dd if=debian-11.5.0-amd64-netinst.iso bs=1 skip=400556032
Hi,
Gerd Mühlenbruch wrote:
> I started my batch by doubleclicking the file in nautilus.
Being a fvwm user i can only riddle whether this start by nautilus has
something to do with the problem.
But your post of 3 Oct 2022 18:28:08 + says that you started the
original download by wget -c. So
Hi,
Gerd Mühlenbruch wrote:
> While copying the logfile I remembered that I used wget twice with "-c"
> option.
> [...]
> cmp debian-live-11.5.0-amd64-gnome.iso
> Err-debian-live-11.5.0-amd64-gnome.iso
> cmp: EOF on debian-live-11.5.0-amd64-gnome.iso after byte 2910683136,
> [...]
>
Hi,
Gerd Mühlenbruch wrote:
> Pfad="https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid;
> wget $Optionen $Pfad/debian-live-11.5.0-amd64-gnome.iso
> sha512sum --ignore-missing -c SHA512SUMS
> debian-live-11.5.0-amd64-gnome.iso: FEHLSCHLAG
I did
wget
Hi,
i added to merge_debian_isos the capability to burn the resulting
ISO 9660 filesystem directly to optical media and to write it directly
to storage device files. This removes the need for having substantial
free disk space beyond the capacity to store the original ISO images.
While burning
Hi,
Zhang Boyang wrote:
> All OK! Thank you again :)
So as far as we two are concerned, it seems we have a candidate for
release.
Currently it only goes into the GNU xorriso tarball, which is not src of
any Debian package. I could put it into the libisoburn tarball. But as
it is specific to
Hi,
Zhang Boyang wrote:
> Theoretically if both file is already sorted, we can use the `-m' option
I like this idea. Just in case Debian grows to a million packages.
But i understand that i would need two separate files for sorting.
grep ' ./pool/' file1
fgrep -v ' ./pool/' file2
sort -k
Hi,
Zhang Boyang wrote:
> These experiments all succeeded. Thank you very much! Good Job! :)
Thank you for testing and challenging.
I wrote:
> > For now i decided to take the 50 seconds with dash.
> if you really want to reduce runtime I would suggest using
> `sort -s -u -k 2
Hi,
i explored two ways to get a correct and complete md5sum.txt after
merging and sorting:
- Generating the whole md5sum.txt from the emerging ISO's file tree is
possible by help of xorriso, although there is no file tree yet where
all regular files of the ISO can be found for checksumming.
Hi,
i wrote:
> > > md5sum.txt
Zhang Boyang wrote:
> I think maybe we should just create the md5sum from scratch?
Well, not from scratch, because the paths would come from the merged
md5sum.txt.
But indeed the merged file needs polishing:
- Some files are listed multiple times because they
Hi,
Zhang Boyang wrote:
> 2) Create my own version of my-DLBD1.iso and my-DLBD2.iso from my private
> mirror.
This explains why a firmware package was missing which is in the official
DLBD-1 but obviously on your my-DLBD2.
With the new script version which merges /firmware trees:
> This time
Hi,
i tested merging of /firmware directories with barely sufficently
complete
debian-11.0.0-amd64-DLBD-[12].iso.tmp
from aborted jigdo-lite runs.
All files which are reported as being only in CUSTOM(all-in-one) by
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343#115
are listed by
Hi,
Zhang Boyang wrote:
> I will definitely try it
Meanwhile i got some insight into the riddle about diffs between merged.iso
and CUSTOM-1.iso like
Only in /groundtruth/firmware: arm-trusted-firmware-tools_2.4+dfsg-2_amd64.deb
Only in /groundtruth/firmware:
Hi,
i followed David's advise to consider the warnings of shellcheck, to drop
the demand for bash, and to check early whether all needed programs are
available. xorriso gets now checked for being young enough for the job
of replaying the boot related commands as detected with input ISO 1.
(1.3.2
Hi,
i wrote:
> > https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos
Steve McIntyre wrote:
> That might be a useful thing to include in a package. What do you think?
Best would be if debian-cd would take it, so that it can be adapted when
the repository format
Hi,
although it was not the final solution of this bug report, i beefed up
my merger script for Debian ISOs so that it can combine an arbitrary
number of ISOs (within the limits of /dev/loop* and mount(8)).
Maybe it can serve as answer for the next time this wish comes up.
The script is uploaded
Hi,
for now it looks like the merged ISO works as fat DVD-1.
I installed a Debian 11.2.0 system from the merged DVD-1+ DVD-2 ISO
in a qemu VM via option -cdrom. Installation went smoothly.
During reboot i aborted the VM to next deface the El Torito boot sector
of the ISO. I removed the -net
Hi,
i uploaded the first version of my merger script as
https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_2_debian_isos
Please download and give x-permission. The need for sudo can be avoided
by already mounting the two ISOs at the chosen mount points before running
Hi,
i wrote:
> > I began to ponder about a shortcut in libisofs which would trust the
> > checksum file (-checksum-list , -md5-list) enough to omit the reading of
> > all the package files' content.
Steve McIntyre wrote:
> Cute idea (grin!), but it's a non-started - we wouldn't be able to
>
Hi,
Steve McIntyre wrote:
> youre initial guess is correct. We don't generate the .iso files
> at all for the larger images [1]. This means we also don't have
> torrent files for them [2].
I began to ponder about a shortcut in libisofs which would trust the
checksum file (-checksum-list ,
Hi,
Zhang Boyang wrote:
> I guess there is no ready tool can merge two ISOs together.
Not directly. But xorriso can load the meta-data of an ISO, manipulate
that loaded model, and write the result as new ISO with the same boot
equipment as found in the loaded ISO.
As said, that would be no
Hi,
i reply to 1011...@bugs.debian.org and zhangboyang...@gmail.com because
of my question and sketch for a procedure to merge DLBD-1 and -2 after
download into the desired ALL-IN-ONE ISO.
Andrew M.A. Cater wrote to debian-cd@lists.debian.org:
> If the original poster wants one huge .iso as one
Hi,
some technical nitpicking.
Andrew M.A. Cater wrote:
> Also, keeping large files around on disk for a long
> time - there's some likelihood of data corruption.
The .jigdo and .template files of the DLBD ISOs are together smaller than
a netinst CD ISO. (Less than 90 MiB, see
Hi,
J.A. Bezemer wrote:
> When the CD is scanned properly using this process, but the DVD fails, then
> your DVD is bad. Maybe the DVD has bad data on it (corrupted download), or
> the DVD burner is bad, or the DVD reader is bad.
I agree in principle. But the particular reason for the firmware's
Hi,
Gianmarco wrote:
> -> I have tried with: 10.3, 11.1, 11.2 and 11.3.
> [...]
> -> my results (with DVD-1 debian version 11.2):
> 1903144+0 record in
> 1903144+0 record out
> 3897638912 byte (3,9 GB) copied, 260,578 s, 15,0 MB/s
> d1fc0ddc81d980b9eddc9d110344bcf17a6cbd5750e147112ccc23bef4d61a8a
Hi,
i wrote:
> > What ISO exactly did you use ?
Gianmarco wrote:
> i downloaded ISO files from here (i have tried both format):
> https://cdimage.debian.org/debian-cd/current/source/iso-dvd/
That's 11.3.0 meanwhile. But as you report to have used 11.2, i assume that
it is the same ISO as i
Hi,
i wrote:
> > So does the following small (251 MiB) ISO here work better ?
> >
> > https://cdimage.debian.org/mirror/cdimage/archive/8.11.1/amd64/iso-cd/debian-8.11.1-amd64-netinst.iso
Gianmarco wrote:
> i have already installed the jessie version of linux some years ago in one
> of the pc
Hi,
Gianmarco wrote:
> maybe you are telling me that i have to use grub to start the DVD ?
No. GRUB is the bootloader in the ISO which gets started by EFI if it
is not in legacy emulation mode and thus would start the ISOLINUX bootloader
which is in the ISO too.
> - I set the bios with the
Hi,
> in the case of debian 11.2 no computer, not even the most recent one, can
> start with the installation directly from the 1st DVD.
Well, at least for me with a halfways modern EFI it boots to some Debian
software.
- What kind of firmware did you try ? What mainboards or laptop models ?
-
Hi,
Steve McIntyre wrote:
> We don't provide firmware-included
> versions of every media type, just netinst and DVD.
sp...@caiway.net wrote:
> > Perhaps you can give me the link with info how to make my own files
> > *.jigdo & *.template
> For that, you'll need a full local mirror and use
Hi,
Raphael Maria wrote:
> At the moment I need a DVD Image release of Debian 10, for a specific
> project that requires it, but I can't find it on the website.
Those ISOs are in the archive now:
https://cdimage.debian.org/mirror/cdimage/archive/10.11.0/
The first three amd64 DVDs are
Hi,
Christoph Prokop wrote:
> Is it on purpose only DVD1?
Yep. Stated by Andrew M.A. Cater in
https://lists.debian.org/msgid-search/yvwb9cz42+gxr...@einval.com
> > [...] the number of DVDs was [...] reduced for Debian 11. Whereas
> > for Buster we made the first three .iso images, for
Hi,
Steve McIntyre wrote:
> [Dropping CC to Lou as we've wandered, re-adding Thomas for the GPT
> question.]
[Lou and i are subscribed to debian-cd, obviously. :))
It seems you dropped the original poster: The7up
who might indeed not be interested in partitioning.]
> For the
> sake of this
Hi,
Pete Batard wrote:
> Yes, as we've discussed elsewhere, that is pretty much my point.
That's why i summarized the results of our wiggling and fitting with
Ubuntu ISO development.
> symlinks [...] will of course not translate to FAT [...]
Duh. I forgot that aspect in my summary.
So its
Hi,
the advantages of putting an unmodified ISO image plainly onto a USB are:
- The boot and installation process is as near to DVD as possible.
- If anything goes wrong during that process, it is clear that debian-cd
is in charge of diagnosing and hopefully managing the effort to provide
a
Hi,
The7up originally wrote:
> ... > It looks like isorecorder not available since a while ago. May I
> ... > remove it from the list in w.d.o/faq/CD index page?
> ... > At the same time, rufus (https://rufus.ie/ [rufus.ie]) should be
> ... > mentioned as a great app on Windows to make bootable
Hi,
Lou Poppler wrote:
> If you want to recommend rufus, please do so ONLY with a prominent,
> un-ignoreable warning explaining that the user MUST select rufus'
> "DD mode" at the prompt immediately before writing the media.
I understand that manual selection of this mode has been removed in
Hi,
Roland Clobus wrote:
> * xorriso complains about issues with Joliet (symlinks not supported,
> volid too long)
Joliet uses 16-bit characters which halves the field length in the
supplementary volume descriptor of Joliet. So no workaround is possible
other than shortening the volume id.
If
Hi,
Fernando Oliveira wrote:
> When downloading today debian 9.13 i386 netinstall, or debian 9.12 i386
> netinstall, my bitdefender anti-virus gave me an alert they have virus or
> malware. I do not believe it, but telling anyway :-)
The problem is known:
Hi,
> For all they will know, Debian has been pwned :-/
Yeah. I tried hard to keep my previous mail in a civilized tone towards
the intellectual entities who decided to deduce the purity of Debian ISOs
from .exe files on the same server.
(Quotation marks in the air are a warning sign towards
Hi,
the Google problem is getting worse. Firefox only warns because of their
botched malware "detection".
According to statements by Mattias Wadenstein and Steve McIntyre
in the thread around
https://lists.debian.org/debian-cd/2020/11/msg5.html
it is probably about this naive reasoning
Hi,
i wrote:
> > Do i understand right that it is not about the ISO and its content but
> > rather about other files which are offered by the same server ?
Mattias Wadenstein wrote:
> Well, as far as we know, yes.
"Sippenhaft" ... www.dict.cc ... "kin liability".
At least they don't resort to
Hi,
Andrew M.A. Cater wrote:
> If all else fails, find a Linux box and use jigdo-file and the jigdo-lite
> command to assemble a medium from individual Debian packages.
Or follow
https://wiki.debian.org/JigdoOnLive
But the problem is with convenience users who download some netinst or
DVD-1
Hi,
Steve McIntyre wrote:
> > Previously, this seemed to be caused by another (unrelated) download
> > from the same server in Sweden.
Do i understand right that it is not about the ISO and its content but
rather about other files which are offered by the same server ?
Back in july i downloaded
Hi,
Ruud Bos wrote:
> I tried to download two different ISO files via
> https://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/
> Everytime a download has completed, Firefox mentions that the ISO contains
> a virus. I tried downloading both the GNOME and MATE ISO's.
This
Hi,
Steve McIntyre wrote:
> I hope you're keeping ok!
Sufficiently. I'm bored enough for digging out old kernel bugs and trying
to fix them. (I now got a half assembled new Xeon box with the best
Linux 4.19 drivers/scsi/sr.c and drivers/cdrom/cdrom.c ever ...)
But at this occasion i remember
Hi,
ralfs wrote:
> > With buster, only the set of current BD images is available on
> > the servers but not an " debian-update-10.x.x-amd64-DVD-x.iso "
I see
debian-update-10.5.0-amd64-DVD-1.jigdo
debian-update-10.5.0-amd64-DVD-1.template
debian-update-10.5.0-amd64-DVD-2.jigdo
Hi,
i wrote:
> > Quite surely Debian does not put malware into its ISOs.
Steve McIntyre wrote:
> No, *definitely* not.
Well, as upstream programmer i could - intentionally or as victim of
malware myself - be the culprit who sneaks malware into a Debian ISO.
I try hard to keep my machines clean
Hi,
i filed
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966538
"Firefox accuses debian-9.13.0-amd64-netinst.iso of containing malware"
If you are interested in getting possible replies by mail, send a mail to
966538-subscr...@bugs.debian.org
Have a nice day :)
Thomas
Hi,
Deparade Max wrote:
> I tried three times to download the 9.13 version ISO but Firefox keep saying
> that it might conaint a virus or malware. I need a verified answer whats
> going on there.
> I used following site:
> https://cdimage.debian.org/mirror/cdimage/archive/9.13.0/amd64/iso-cd/
>
Hi,
Andrew Cater wrote:
> It does seem that
> we may be able to stop routine production of as many images. Netinst,
> something DVD-ish sized (so smaller than 8G) and some (larger file size ??)
> may do it.
How about being storage-neutral and drop amd64-DVD-2.iso and
amd64-DVD-3.iso in favor of
Hi,
Stefan Monnier wrote:
> I was thinking of a scheme by which the ISO is constructed and streamed
> at the same time, so the complete ISO images aren't ever stored whole
> anywhere on the server.
Although there are no fundamental obstacles for stream production,
the current software
Hi,
(The mail headers indicate that the OP, Andrew Cater, is subscribed to
debian-cd but not to debian-user. So replies to debian-user only might
not get to his attention.)
Stefan Monnier wrote:
> An alternative is to have "virtual ISO images", i.e. images which are
> constructed on the fly
Hi,
Andrew Cater wrote:
> If anybody knows of any [Mac Mini] that they really must keep
> running, speak now or forever hold your peace.
It is possible to create an ISO without EFI boot lures from a normal
i386 or amd64 ISO.
Follow
https://wiki.debian.org/RepackBootableISO
but leave out the
Hi,
Andrew Cater wrote:
> [...] here are
> a couple of architectures that are built but not tested because the testers
> have no hardware.
> One set is an old Mac on Intel media,
Do you mean these ?
https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-mac-10.4.0-i386-netinst.iso
Hi,
I am not aware of a package that is in charge for drive behavior.
libburn or kernel are near the hardware. But i don't see this as libburn
problem and for now not as a kernel problem either.
It is unusual that an empty DVD drive makes noises, except when the tray
was freshly loaded and the
Hi,
do the hybrid ISOs of debian-cd and debian-live depend on blkid properly
detecting the ISO 9660 filesystem on the base device (/dev/srN, /dev/sdX) ?
Does any other Debian software depend on this detection ?
If so, then trouble is at the horizon by
Hi,
wdstud...@protonmail.ch wrote:
> This may come as a shock to you but files without file extensions are not
> very useful. What am I supposed to open them with? Powerpoint? Daemon Tools?
The checksum files like
https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/SHA256SUMS
are plain
Hi,
wdstud...@protonmail.ch wrote:
> Can someone please tell me where [...] I can find the correct sha256
> checksums for the CD/DVD images?
In the same directories as the ISO images.
> The information at www.debian.org/CD/verify was NOT helpful.
Would this article be more helpful ?
Hi,
Steve McIntyre wrote:
> Let's go with "-jigdo-checksum-algorithm" to keep the separation?
The user is king.
Other mail:
I proposed to keep versioning and SONAME at 1
> > LIBJTE1 {
Steve McIntyre wrote:
> Surely that works for upwards compatibility, but won't stop somebody
> from building
Hi,
SONAME comes from libjte/configure.ac. Dunno from where libburn got the
slightly braindamaged way to compose it. From there it spread over the
other libraries. libjte is its youngest victim. Shrug.
The upstream revision "2.0.0" is not necessarily the .so suffix.
The macro values from
Hi,
while exploring the need for adaptions in the build system of libsofs,
i wonder whether it is really necessary to create LIBJTE2 in libjte.ver.
Adding new functions is upward compatible.
In my libraries i add them to the current (and only) SONAME version.
Fine check for compatibility happens
Hi,
i wrote:
> > libjte_set_checksum_algorithm() became necessary
Steve McIntyre wrote:
> ACK. I'd not thought that through fully myself here, but yes.
Here you see why it is good to have a mutually curious user-developer
relation. :))
> I'm open to changing things like option names here,
Hi,
after finding
https://git.einval.com/cgi-bin/gitweb.cgi?p=jigit.git;a=log;h=refs/heads/sha256
https://git.einval.com/cgi-bin/gitweb.cgi?p=jigit.git;a=blob;f=libjte/libjte.h;hb=refs/heads/sha256
i now believe to understand that the new API call
int libjte_set_checksum_algorithm(struct
Hi,
Steve McIntyre wrote:
> the external API for libjte is *very* close to what we had before.
Now i'm curious. I expected no need for a change, assumed that you'd
automagically detect the checksum type from the lines in the -md5-list
file.
> I've got a simple diff right now that I'm
> just
Hi,
Daniel Kahn Gillmor wrote:
> Is the final checksum over the whole image also MD5, or do we use
> something stronger?
Currently, the downloader only checks MD5. But it already now has a wide
range of better checksums to choose from.
A typical .jigdo file contains this header part (after
1 - 100 of 339 matches
Mail list logo
