Hey, > Probably I will send git commits via email, I am not inclined to clone > to my salsa account a few hundred packages manually. I hope you > understand. Checking out the pkg-kde git is easily automatized, though.
well you can use the gitlab API to do this for you, the API isn't that hard to use. See my salsa.py to get the buildlog/lintian from salsa: https://salsa.debian.org/hefee/pkg-kde-dev-scripts/-/blob/hefee/pim-management/function_collection/salsa.py#L45 if you want to use the SalsaPackage class you need a Project, that you get here: https://salsa.debian.org/hefee/pkg-kde-dev-scripts/-/blob/hefee/pim-management/function_collection/functions.py#L1506 Sure it should be much easier to use, that's why I havn't merged it yet. > I have checked the experimental version right now, and a few questions > remain open after checking which packages I couldn't update on my > installation to the frameworks version in experimental. what are the issues? what state you had before? > - why was the > Provides: libkf5contacts5-5.69 > dropped from libkf5contacts5? Up to the last version these provides > were always present. well on kdepim the ABI is not stable, so we came up with this virtual package approach, to bundle things correctly. Because kcontacts and kcalcore moved to frameworks, the ABI is now stable and we can ship symbols files and do tracking via symbols file. We need to do a transition in order to build the rdepends correctly. > - what are you planning to do with calendarcore that has moved to the > frameworks? kcalcore is currently also in NEW queue, because of a new -doc package.I shipped 4:19.08.3+really5.69.0-1~ to experimental, so other packages can depend on the new kcalcore. The version in NEW is 5:5.69.0-1. hefee
signature.asc
Description: This is a digitally signed message part.
-- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
