As long as packages are rebuilt with rpm 4.2-9mdk, there is no issue for the package itself. Chances are, you won't be able to install the -devel (or normal packages that contain files that should be in -devel packages --> QT & KDE packages *HINT*) package. This is because -devel packages built with rpm-4.2-9mdk use a different naming convention, and some packages they require may not be rebuilt with this new naming convention.
If you see that "*.so" or "devel(*)" dependencies are missing / incorrect, then you can probably install the package with --nodeps. Please inform us (on the list) about these missing / incorrect dependencies, we'll see to it ASAP.
We're actually fixing stuff. Really. Beleive me.Please don't get Andi started again ... just wait until the promised
glibc update comes through.
If we need to rebuild glibc then Nanar really shouldn't be rebuilding things with the new rpm just for the hell of it, especially not things that are required to build stuff. And especially not things that are in main.
It's really absurd to be breaking stuff that doesn't need to be broken...
We don't need annother Andi Payn discussion.
Not everybody can upload glibc (among other packages).And if all glibc needs is a rebuild so it provides the new devel stuff why hasn't it been done already and for that matter why didn't Nanar do it when he rebuilt elfutils?
The explanation is simple. A dependency scheme for -devel packages was recently deployed, but we didn't think through the consequences of the naming scheme that was used. This caused conflicts with other naming schemes and made things confusing. I then opted to change the naming scheme so that these conflicts wouldn't exist and it would become clear where the dendency (Provides and Requires) originated from. I urged that this change should be done before a release is made (9.2 or whatever comes next) because after a release mdk will need to support it for a while.This all seems rather haphazard to me. If we're going to be making changes that break things and require rebuilding to fix then either a script should be written to do all the rebuilds so everything gets rebuilt promptly. Or we need to have an explanation of the migration.
Part of the process.Yeah it's cooker, but if we break stuff we need to cook it is rather silly.
And I have no idea who Andi is or what I'd be getting him started about.Just check the archives, 5 or 6 weeks back...
rpmlint is broken?I'm just trying to get some packages updated that I haven't done because I've been busy. I finally find time to do it and someone goes and breaks rpmlint so I can't ensure my packages are good.
The way I see it if you break something then you need to fix it and fix it promptly.Fixing 2 or 3 hundred packages doesn't happen overnight.... We're working on it. It's unfortunat that you've been caught in the middle of it.
regards,
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
