Martin Steigerwald <Martin@lichtvoll.de> > Am Samstag, 16. März 2013 schrieb José Manuel Santamaría Lema: > > Martin Steigerwald <Martin@lichtvoll.de> > > > > > Hi! > > > > > > Thanks for packaging digikam 3.0. > > > > > > Is there any way to resolve the following without messing my system up? > > > > > > I read: > > > * digikam 3.0.0 uses features from unreleased kdegraphics >=4.10 & > > > ships a private version of the kdegraphics libs - this is not the > > > Debian way > > > : > > > :-( * Unsatisfactory Conflicts: libkipi8, libkexiv2-10, libkdcraw20, > > > > > > libksane0 > > > > > > from the changelog. And can put the package on hold since my self built > > > digikam 2.9.0 packages still work. > > > [snip] > > > > It's a bit late to do this, but I have uploaded yesterday a fixed digikam > > 2.9.0 to qt-kde.debian.net. > > I already replaced my self built 2.9 packages (see some earlier thread > here) with those. Worked nicely. I have to keep those packages on hold to > avoid having apt/aptitude try to update them to the 3.0 ones. > > Thanks, I guess you had to put them on hold to upgrade from your custom packages to the qt-kde.d.n ones, afaik that's unavoidable unless you comment out the experimental line in your sources.list first. But what about once you have upgraded to the qt-kde.d.n? Keeping the experimental lines in sources.list: do you still need to have the packages on hold to prevent an undesired upgrade to the 3.0.0 packages in experimental?
Attachment:
signature.asc
Description: This is a digitally signed message part.