ebuild --force <pkgname-ver.ebuild> manifest = broken manifest without DIST entry Reproducible: Always Steps to Reproduce: 1.generate manifest for soe ebuild with distfile 2. change distfile somehow 3. regenerate manifest with command ebuild --force <pkgname-ver.ebuild> manifest since repoman manifest will not work and thet is bad Actual Results: we will get manifest without DIST entry Expected Results: Normal Manifest with DIST entry
The way that ebuild --force <ebuild> manifest is currently implemented, it temporarily rewrites the Manifest with the DIST entries for the corresponding ebuild missing, and then it regenerates those entries and writes the Manifest a second time. If it gets interrupted after it writes the Manifest the first time, then the corresponding DIST entries will be missing. However, generally this isn't a problem since you can simply run the command again (without interruption). It always works correctly for me, so I'm not sure how to reproduce the supposed problem that you're reporting.
I'm still wondering what the problem is. Doesn't it regenerate the DIST entries for you like it does for me? Maybe I should try a specific ebuild to reproduce the result you got?
(In reply to comment #2) > I'm still wondering what the problem is. Doesn't it regenerate the DIST entries > for you like it does for me? Maybe I should try a specific ebuild to reproduce > the result you got? > well it was with kde-testing overlay's ebuilds in kde-base/
