Your message dated Fri, 18 Sep 2026 11:46:11 +0000 with message-id <[email protected]> and subject line Bug#1137258: Removed package(s) from unstable has caused the Debian Bug report #832699, regarding support for a more structured mirror cache to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 832699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832699 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: live-build Version: 5.0~a1-1 Severity: wishlist A possible improvement for the future, submitting now ahead of time. (Can be ignored for the time being). Taking a que from the current installer_debian-installer cache, which uses URLs (with forward slashes replaced with underscores) in the filenames, to separate out files from different locations, such as daily builds of installer image files from normal, my new almost complete bug #718225 solution caches files in a similar way, using the URL to build sub directories that closely mirror the URL path. There are advantages to this, making the cache more suitable for building images of different distributions, and when building for a derivative distribution, it ensures that files from parent and derivative mirrors are separated. Also, should a user mix up the parent and derivative config parameters, and then correct them without flushing the cache, there's no problem, the correct files are retrieved from the cache. I actually don't particularly like the base of the URL being used in this way because although it works, it looks really messy. Furthermore, simply switching from say one debian mirror to another means perfectly good cached files are ignored, which isn't desirable. So I'm considering alternatives for how this could be improved in the future (LB v5.x). One would be simply sub-directories of 'parent' and 'derivative' or 'parent{-|.}mirror' and 'derivative{-|.}mirror'. This obviously breaks the latter advantage of the user specifying the URLs the wrong way around and fixing without a cache flush though (not a big deal, but good to allow if possible). It also requires ensuring that 'parent' attributes are used throughout the code when not doing a derivative build, if this is not the case already, but such consistency is desirable anyhow. An alternative could be to have a simple label to go alongside each of parent and derivative mirrors, i.e. 'debian', 'ubuntu', 'progress-linux', etc., which can be used for sub-directory names (e.g. cache/packages.bootstrap/debian). How such labels are supplied is a tricky question however. It would be over the top I think for new config params to be added. Hard coding a grep against the url to determine which of progress-linux/ubuntu/debian might work, but further works against opening up use of LB on more derivative distributions (something I personally am supportive of improving, I don't know about maintainer). The best approach might be to completely revise the config format in the planned switch to python in v5.x+. Instead of taking the user's config as a set of parameters, read them from a file (as is done with the full config files in config/ after processing auto/config and other params). This would provide a more simple opportunity for the user to supply labels. Furthermore, much more of the 'mode' customisations could possibly be captured in such a config file, making the code neater, simpler, and more open to other debian derivatives.
--- End Message ---
--- Begin Message ---Version: 20190301-lts1-5+rm Dear submitter, as the package open-infrastructure-system-tools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1137258 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
