Discussion:
Bug#1086807: live-build: weekly live testing images not generated
Add Reply
Leandro Doctors
2024-11-06 10:40:02 UTC
Reply
Permalink
Package: live-build
Version: 2024.11.04
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: ***@gmail.com

Dear Maintainer,

When opening https://cdimage.debian.org/images/weekly-live-builds/amd64/iso-
hybrid/,
instead of finding the weekly live images I find log files.
(Date reported for the logfiles: 2024-11-04 06:02)

For your reference, I copy the contents of the `SHA512SUMS` file, along with
the tail of the `debian-live-testing-amd64-gnome.log` file.


Q1: Shouldn't the `*builds` folders be pointers to the last successful
build of the relevant images?

Q2: Is there a way to access the last successful build of the live images?

Best,
Leandro Doctors

SHA512SUMS:

******************************************
d9bfffb364e1a83cd9b1175f468758ef0b243cd25923567b1d63c6099ac589aa9842ec3e9cb54550a2cd4d6e74a2f8007106213b4ed011ebd8751ef1a51a51a6
debian-live-testing-amd64-cinnamon.iso.log
917b4af2d3a83834664d77657f5fe49a8f66306d01378879c9f710805a2699fedad6f068f498febc6b02e279755d8b201751a8d715b4e3f8a8e47bd765ae0d44
debian-live-testing-amd64-cinnamon.log
954b723003f8c44a18c7717fca2ae3595f5736fbac6bc592e30b87eed35db76c17118c40b10eb4328035c1b3e56ac63b94c5115f2b2e39547b7cecc52c9ed229
debian-live-testing-amd64-gnome.iso.log
c33d303f8006584d50127a244602b1c141183ce8780a0fa0b79e979e028fd46e5a5c103e05632de98777c16b49fe3c8223fb0b1808db4ad9f62d8fccc85fd276
debian-live-testing-amd64-gnome.log
65160e986a70111f56009e88e418ed7a7fde5d1cd6690f2e18a7c0c4c80394a8a15751e83c5826d5c9a0df73e0b3c977bf7fe3dfb6f846ac4d22cb82dd464b08
debian-live-testing-amd64-kde.iso.log
3d01af62a371ab6b2bf4a8db01aa8ad85219e7688c8933b331e008b7f7f74a561b31d4eadafe9373683480862f115ef28ebc698eafce582995635c82d4ffd96d
debian-live-testing-amd64-kde.log
51aac43ad15645bd478787b60d4a29b9bcea9ea4050d22256f7ba439bf9e32494354326da51b35fe1d07f7955a54dc8b4c78cb607975b9255ece6a770979dfd4
debian-live-testing-amd64-lxde.iso.log
004290fb5ab0acf254eccf7c508f5061fb1933def6b63837e5cc23972ef937c9ad091492bbb888de4a489ab6ef73a247acb520fa2728eeeafcdfd91d24a44d04
debian-live-testing-amd64-lxde.log
2e30fdbe50acb28def10c544b4813cd208d4e1a593a4b28ec35c0b9ed3911ad2fa2560a9386b7495fac8a1d6a1865f87186af73914284a79c50c87cf1da3e0bb
debian-live-testing-amd64-lxqt.iso.log
1d1fca755654fc842a58e7e7758de91cbd49c030abaaf8b53d45a45d8d0953db1c5ca2bd874e8d0b9476048d8153bbbf2a34d2449faeb960a1043c04a4a59c3e
debian-live-testing-amd64-lxqt.log
49ffcda6d3fc21a5edbfee0e23c3a502c4f8c03871c89333ae30537fabb37de3b90e1fb34a44e527def4d397370ad03b49a389d93ffad4f9330ea773500a270b
debian-live-testing-amd64-mate.iso.log
5279bdfb52bb42091f14e88787ef8df30d7495294d459bdc062046a7d4da681d732e5f930a03372c9d7b4da13273b6450e9102236c9b2502de723f7f3a945c71
debian-live-testing-amd64-mate.log
d92960d43e799314fa430fa8225e72c94f66ab30530a4c0e7d3aff884f15c49d959ac71363a0ecc0fd5571b0fa3cade76fa0715e59490ac6fc10f408bb157a5d
debian-live-testing-amd64-standard.iso.log
5fa97b8894d9d663eccfaa99213876c3b108953ec10e7fef0877d6fcc6bcda454e6c1a44962d152692f47dc8d2ec12969ed6608580ea1c63f1a979b1de386a58
debian-live-testing-amd64-standard.log
9949b38215f00738557209ab477e3e680b7a3251696f04be7f5e683462f8cf8bffd3ab721aabbc57ad9de115fe229ca1ed7b8ce75d4a7e8973d7c96d41ebbd3f
debian-live-testing-amd64-xfce.iso.log
fb2b948f709b6230c1720b9f8037408f90e716564d82505cd8410e57e60f2d1f27258984e6c116a86048f498dd3d8026f0b1d3f526eb10d514c358b77aac4b0e
debian-live-testing-amd64-xfce.log

*********************************************


debian-live-testing-amd64-gnome.log

*************************************************
[...]


Mon 4 Nov 03:33:09 UTC 2024 - Generating summary.txt

error on first pass; summary.txt says:
Configuration: gnome
Debian version: trixie
Use latest snapshot: yes, from the main Debian archive
Installer origin: git
Snapshot timestamp: 20241104T022108Z
Snapshot epoch: 1730686868
Live-build override: 0
Live-build path: /w/work/amd64-free-gnome/live-build
Build result: 123
Alternative timestamp:
Checksum:
Script commandline: --configuration gnome --debian-version trixie --debian-
version-number testing --timestamp archive --installer-origin git --disk-info
--generate-source
Script hash: 4ef71069b70380206fcd841521228d642dac05ece5ebbaf22ea10031da8a2f28

****************************
Leandro Doctors
2024-11-06 17:30:02 UTC
Reply
Permalink
Post by Leandro Doctors
Q2: Is there a way to access the last successful build of the live images?
Yes, you can ...
* ... use your previously downloaded file, if you still have that
* ... rebuild them using a snapshot, but that is not the easiest way
* ... wait until next Monday, when new images will be generated
I meant an *easy* way :-)
I guess I'll just have to wait until next Monday...
Post by Leandro Doctors
Q1: Shouldn't the `*builds` folders be pointers to the last successful
build of the relevant images?
That depends on your viewpoint...
The logs and the ISO files belong together. If the ISO files were kept,
but the logs were updated, we would not have detected the breakage. If
we didn't update the logs, because the ISOs were not generated, we could
not do diagnosis.
Thanks for the quick response, Roland.

I agree with you in that keeping the logs and ISOs in sync makes sense.
I treat the weekly build as one of the early QA methods. If something
breaks, it's good to know about it.
Note: Even having the ISO files made available, doesn't mean that
everything is guaranteed to work, e.g. for LXDE I've opened #1086075.
Sure. But I think that when they are pointed at from
https://www.debian.org/devel/debian-installer/,
not providing the last successful build (even without any warranty
that it fully works, as you very well noted above, of course)
simply turns all that into a 404...
Anyways, just my opinion.
I'm not sure whether we should keep a backup of the last available
weekly images around, but perhaps the debian-cd team can chime in?
What about keeping two folders?
* one with the last successful build, and
* another one with the last build (no matter whether it is successful or not)
* if the last build is successful, you could even use symlinks to save
up space...


Thanks again,
Leandro

Loading...