search

APN-Pucky / pkg-testing-tools

Set of tools to simplify package testing for arch stabilizations and package bumps in Gentoo
BSD 3-Clause "New" or "Revised" License
2 stars 0 forks source link

New release #17

Closed juippis closed 8 months ago

juippis commented 8 months ago

Hey,

for some reason 0.2.1 is really bad at calculating multiple use flag combinations. It can take hours to finish simple calculation before anything happens. -9999 (git-version) seems to work instantly, so could you tag a new release? :)

APN-Pucky commented 8 months ago

Sure, I don't know why I did not get a email for this issue tho ... (EDIT: lets see if Star+Watch helps)

APN-Pucky commented 8 months ago

BTW. what do you think about forcefully removing each package before testing/installing it (again) using sth. like emerge --unmerge. I do not see any drawback, just a cleaner install env. Just to make sure there are no old files are still around and picked up wrongly by tests (cf. https://github.com/gentoo/gentoo/pull/35746#discussion_r1526393529)

APN-Pucky commented 8 months ago

https://github.com/gentoo/gentoo/pull/35769

juippis commented 8 months ago

Thanks for the release!

BTW. what do you think about forcefully removing each package before testing/installing it (again) using sth. like emerge --unmerge. I do not see any drawback, just a cleaner install env. Just to make sure there are no old files are still around and picked up wrongly by tests (cf. gentoo/gentoo#35746 (comment))

Personally not a huge fan, this issue hasn't come up to me nearly ever. And it most likely wouldn't prevent the problem happening while upgrading either. But I see you added a new -C option so as it's optional it's totally fine.