https://sourceforge.net/p/live-raizo/tickets/2018-04-08T16:26:11.097000ZRecent changes to tickets2018-04-08T16:26:11.097000Z2018-04-08T16:26:11.097000ZRaizo62https://sourceforge.net/u/raizo62/https://sourceforge.net58abb40d53b495d743a6504e072893d717e49386

<div class="markdown_content"><ul> <li><strong>status</strong>: open --&gt; closed</li> </ul></div>

2018-04-04T15:30:10.063000Z2018-04-04T15:30:10.063000ZJesse Smithhttps://sourceforge.net/u/slicer69/https://sourceforge.net6e5a36ef7410bcfb3a8c0aebced19cfe5f15158f

<div class="markdown_content"><p>Great, thank you very much.</p></div>

2018-04-04T15:00:26.362000Z2018-04-04T15:00:26.362000ZRaizo62https://sourceforge.net/u/raizo62/https://sourceforge.netadcc61b3ac587572d9ede14ba2aafce184504716

<div class="markdown_content"><p>Ok. For the next releases, i will put the file pkglist (example "live-raizo-v9.18.04.02-amd64.iso.pkglist") with the dump of "dpkg -l"</p></div>

2018-04-04T13:47:49.489000Z2018-04-04T13:47:49.489000ZJesse Smithhttps://sourceforge.net/u/slicer69/https://sourceforge.netb0eb6c03b6f6ecf1344aad45c861379c331c9e36

<div class="markdown_content"><p>Thanks very much.</p> <p>Ideally, I just need a file which contains a dump of the "dpkg -l" command as run from the live ISO. The manifest/package file can have just about any name. Other projects which do this usually take the name of the ISO file and just add a suffix like ".manifest" or ".pkglist".</p> <p>For example, if you release a new ISO called "live-raizo-v9.18.04.02-amd64.iso", then an ideal manifest file would have the name "live-raizo-v9.18.04.02-amd64.iso.pkglist". That lets me know which version of the ISO these packages are associated with.</p></div>

2018-04-04T06:54:15.129000Z2018-04-04T06:54:15.129000ZRaizo62https://sourceforge.net/u/raizo62/https://sourceforge.net4d8bfd22dd3a3f65592270c135b4abfee229ac5b

<div class="markdown_content"><p>Yes, i can do it.<br/> What files do you exactly needed ? and what is the name of the separate download that i must use on sourceforge (and can i have a version number to identify the iso ) ?</p></div>

2018-04-03T22:45:34.625000Z2018-04-03T22:45:34.625000ZJesse Smithhttps://sourceforge.net/u/slicer69/https://sourceforge.net2c29c2bea69b1c9522c5f40fc3457e3a8f647bea

<div class="markdown_content"><p>I'm one of the DistroWatch maintainers and having the manifest file either on the ISO or as a separate download makes it a lot easier to find out what technologies are included in a distro and to update our package table.</p> <p>If you don't want to include the manifest file in the ISO, would you please consider making it a separate download that is available on SourceForge? That would be even better as I wouldn't need to download the entire ISO to get the relevant information.</p></div>

2018-04-03T21:09:59.888000Z2018-04-03T21:09:59.888000ZRaizo62https://sourceforge.net/u/raizo62/https://sourceforge.net4a05e06e9de1e40bdd83f84490a048f4aa92e2cb

<div class="markdown_content"><p>Yes, I emptied these files to decrease the size of the iso file (no small gain).<br/> Why do you need it ?</p></div>

2018-04-03T18:50:51.522000Z2018-04-03T18:50:51.522000ZJesse Smithhttps://sourceforge.net/u/slicer69/https://sourceforge.net3211a1e8e372224cef69b31540d2e274df78260e

<div class="markdown_content"><p>In the latest snapshot of Live Raizo (version 9.18.04.02) the files on the ISO which contain package manifests are empty. In previous versions the iso/live/filesystem.packages file would contain a list of software included on the system. That file, and its related files, are empty in the new snapshot.</p></div>

2018-04-03T18:50:51.522000Z2018-04-03T18:50:51.522000ZJesse Smithhttps://sourceforge.net/u/slicer69/https://sourceforge.netf851471e77283f87b8ad043af1f06ab40b443589

<div class="markdown_content"><p>Ticket 1 has been modified: Live ISO missing package manifest data<br/> Edited By: Raizo62 (raizo62)<br/> Status updated: u'open' =&gt; u'closed'</p></div>