home  bbs  files  messages ]

      ZZLI4427             linux.debian.maint.boot             505 messages      

[ previous | next | reply ]

[ list messages | list forums ]

  Msg # 47 of 505 on ZZLI4427, Friday 8-21-25, 1:00  
  From: CYRIL BRULEBOIS  
  To: ALL  
  Subj: Re: local udeb package building for Trix  
 [continued from previous message] 
  
 > http:///deb.debian.org/debian/dists/ 
 ldstable/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/d 
 ebian/dists/stable/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/d 
 ebian/dists/testing/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/debian/dists/ 
 nstable/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: INFO: mirror does not have any 
 > suite symlinks 
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/d 
 ebian/dists/trixie/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/d 
 ebian/dists/stable/Release 
 > -O - | grep -E '^(Suite|Codename|Architectures):' 
 > Aug 11 22:50:46 choose-mirror[3120]: INFO: suite/codename set to: 
 trixie/trixie 
  
 That's what we'd expect at this point, again. 
  
 > Aug 11 22:50:46 choose-mirror[3120]: DEBUG: command: wget --no-verbose 
 > http:///deb.debian.org/debian/dists/ 
 rixie/main/binary-amd64/Release 
 > -O - | grep ^Architecture: 
 > Aug 11 22:50:46 anna-install: Queueing udeb trixie-support for later 
 > installation 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 
 > http:///deb.debian.org/debian/dists/ 
 ldstable/Release: 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > ERROR 404: Not Found. 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 
 > http:///deb.debian.org/d 
 ebian/dists/stable/Release: 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > ERROR 404: Not Found. 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 
 > http:///deb.debian.org/debian/dists/ 
 esting/Release: 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > ERROR 404: Not Found. 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 
 > http:///deb.debian.org/debian/dists/ 
 nstable/Release: 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > ERROR 404: Not Found. 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > URL:http:///deb.debian.org/debian/di 
 ts/trixie/Release 
 > [135869/135869] -> "-" [1] 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 
 > http:///deb.debian.org/d 
 ebian/dists/stable/Release: 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > ERROR 404: Not Found. 
 > Aug 11 22:50:46 main-menu[690]: (process:3113): 2025-08-11 22:50:46 
 > URL:http:///deb.debian.org/debian/di 
 ts/trixie/main/binary-amd64/Release 
 > [116/116] -> "-" [1] 
 > Aug 11 22:50:46 main-menu[690]: INFO: Falling back to the package 
 > description for bzpartrep 
 > Aug 11 22:50:46 main-menu[690]: INFO: Menu item 'download-installer' 
 selected 
 > Aug 11 22:50:46 net-retriever: regular: dists/unstable/Release 
 > /tmp/net-retriever-3171-Release 
  
 And that part seems very strange to me. I don't recall changes in that 
 area, that would mean switching to a different suite. But then, I've 
 never getting such 404s, so I'm not actively testing any kind of 
 possible fallback. 
  
 > Aug 11 22:50:46 anna[3169]: 
 > http:///deb.debian.org/debian/dists/ 
 nstable/Release: 
 > Aug 11 22:50:46 anna[3169]: 2025-08-11 22:50:46 ERROR 404: Not Found. 
 > Aug 11 22:58:23 init: starting pid 670, tty '/dev/tty2': '-/bin/sh' 
 > Aug 11 22:59:11 anna[3169]: WARNING **: bad d-i Packages file 
 > Aug 11 22:59:11 main-menu[690]: INFO: Menu item 'download-installer' 
 > succeeded but requested to be left unconfigured. 
 > Aug 11 22:59:11 main-menu[690]: INFO: Falling back to the package 
 > description for bzpartrep 
 > Aug 11 22:59:23 main-menu[690]: INFO: Falling back to the package 
 > description for bzpartrep 
 > Aug 11 22:59:23 main-menu[690]: INFO: Menu item 'save-logs' selected 
  
 > We are using an apt-mirror populated internal mirror server, and as 
 > part of that we do _not_ mirror unstable releases. It seems like the 
 > Trixie install is still trying to pull unstable, while older versions 
 > will attempt to pull their own release. I have tried both with the 
 > debian/changelog file listing its release as "unstable", as well as 
 > listing its release as "trixie". 
  
 Which debian/changelog? 
  
 If you're building a custom debian-installer package, you should be 
 aware of the heuristics in debian/rules (see test on ${SUITE}) but those 
 are the same as usual (except the obvious codename update). At runtime 
 you can check /etc/udebs-source. 
  
 > So my question is, has anything changed between Bookworm and Trixie 
 > for how udebs pick their release? And, how do I make the udeb pick the 
 > correct release? 
  
 That doesn't ring a bell. I'm not sure what €€€the udeb€€€ you mean this 
 time. If you're talking about bzpartrep, its debian/changelog is totally 
 irrelevant. That's the primary source of information for the usual 
 tooling to get a target written to a .changes (and even that can be 
 overridden), which is then processed by uploading/merging tools to 
 create/update repositories. 
  
 If €€€the udeb€€€ means net-retriever, then we definitely need to hear back 
 about the (possible) custom debian-installer build and the resulting 
 /etc/udebs-source. 
  
 FWIW there was no changes to the net-retriever script since 2021, and 
 even then those were for things that aren't used in official releases. 
  
 For reference, codename/suite selection is done this way, hence the 
 question regarding a possible custom debian-installer build, and the 
 suggestion to check /etc/udebs-source if that's what happening: 
  
         # Setting codename to a suite is not very nice, but can do no harm 
         if ! db_get mirror/udeb/suite || [ -z "$RET" ]; then 
                 if [ -f /etc/udebs-source ]; then 
                         RET=$(cat /etc/udebs-source) 
                 else 
                         db_get mirror/codename 
                 fi 
         fi 
         codename="$RET" 
  
  
 Cheers, 
 -- 
 Cyril Brulebois (kibi@debian.org)             
 D-I release manager -- Release team member -- Freelance Consultant 
  
 -----BEGIN PGP SIGNATURE----- 
  
 iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmimdHgACgkQ/5FK8MKz 
 VSBlTQ//drcAz1bx/2vCf0mOQ7QwIY1T8KuLNcSWGuhtn2io4VVi4FJUep1D5d7d 
 oS73DXixFkNoFD7X7ZyKkB2nUYVi9iqfam+miCj9jc0Bceeg8f0sQZz3LTIT9ugr 
 nN1jGqjrbLcFnC/L543bjTDIX53MnmVy7IPhfAMvl9ABi2QRQJ2YFUZTkwoHVMNa 
 XfPtMTpDiu+nxubOm9h+BRnto5oNTyS3IAZ/SAFbgbJNIML1aMqZt2NwXDZvc94Z 
 npZWuD1nkxpvaTiIA+YMA39sWDbZbQxrf27jvS4u7ff5cetNQJdgZorRuis8X1DC 
 Mx9uowJDEFs5/CM+nHl7YImGgtlipGYqnMoH4J0up4f44/Py41dRvjqVYnzqb8p5 
 3iCmPq98TGF4SiHLFoN3i5WtCy3VPod1mHMNIXpBsZuXgUUKbTcKSDXcRLViy5vC 
 NbyYFh3GgCv4C3AHDK+QZkcw6wnqYkhQF2+jGZaEPThRZgG7IHgo8xEJ3x2XDk5I 
 QrvIw+CpGWubCUOszv9nQvcuwz4TC0b/egIhe/ejVdcDl/hm7mH1JrGzkPrUHLiV 
 gCJO9CSQY9mfSrK//ODWB3L8FL2Xkpo/tI/oSxo0G6aCpLXEJLM/tAY/pFaRrieB 
  
 [continued in next message] 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2) 

[ list messages | list forums | previous | next | reply ]

search for:

328,100 visits
(c) 1994,  bbs@darkrealms.ca