Gutenprint packages 'foomatic' and 'ijs' seem to have been obsoleted and are no more present in mirrors, but can not be removed: werewolf:~# rpm -e gutenprint-ijs gutenprint-foomatic error: Failed dependencies: gutenprint-ijs >= 5.0.1 is needed by (installed) task-printing-lexmark-2011-11.mga7.x86_64 gutenprint-ijs >= 5.0.1 is needed by (installed) task-printing-epson-2011-11.mga7.x86_64 gutenprint-ijs >= 5.0.1 is needed by (installed) task-printing-canon-2011-11.mga7.x86_64 gutenprint-foomatic >= 5.0.1 is needed by (installed) task-printing-lexmark-2011-11.mga7.x86_64 gutenprint-foomatic >= 5.0.1 is needed by (installed) task-printing-epson-2011-11.mga7.x86_64 gutenprint-foomatic >= 5.0.1 is needed by (installed) task-printing-canon-2011-11.mga7.x86_64 Some task-printing packages still require them.
Indeed, thanks for the report. The Foomatic data generator and the Ghostscript IJS driver had already been removed in version 5.2.12, that landed in cauldron almost 8 months ago. Both gutenprint-ijs and gutenprint-foomatic are mentioned 5 times as Requires in task-printing-scanning.spec Assigning to all packagers collectively, since there is no registered maintainer for task-printing-scanning
Summary: task-printing still requires ijs => task-printing-* still requires gutenprint-ijs and gutenprint-foomatic, even if gutenprint upstream already urremoved ijs and foomatic in gutenprint-5.2.12Assignee: bugsquad => pkg-bugsCC: (none) => marja11
Summary: task-printing-* still requires gutenprint-ijs and gutenprint-foomatic, even if gutenprint upstream already urremoved ijs and foomatic in gutenprint-5.2.12 => task-printing-* still requires gutenprint-ijs and gutenprint-foomatic, even if gutenprint upstream already removed ijs and foomatic in gutenprint-5.2.12
Would this affect more than just Cauldron then?
(In reply to David Walser from comment #2) > Would this affect more than just Cauldron then? I don't thinks so, I don't find gutenprint-5.2.12 in my local copy of the Mageia 6 repositories [marja@localhost ~]$ find /RedHD2/mageia/distrib/6/SRPMS/core/ | grep gutenprint /RedHD2/mageia/distrib/6/SRPMS/core/release/gutenprint-5.2.11-2.mga6.src.rpm [marja@localhost ~]$ But there is something that I don't understand ==> "mgarepo log 6/gutenprint" shows: ------------------------------------------------------------------------ r1123324 | umeabot | 2017-07-14 15:58:43 +0200 (vr, 14 jul 2017) | 1 line SILENT Branching for Mageia 6 ------------------------------------------------------------------------ r1017383 | luigiwalser | 2016-05-21 18:24:17 +0200 (za, 21 mei 2016) | 1 line SILENT: add missing part of patch ------------------------------------------------------------------------ r1017382 | luigiwalser | 2016-05-21 18:14:27 +0200 (za, 21 mei 2016) | 3 lines - add upstream patch to use pkgconfig instead of ijs-config to find ijs - call autoreconf instead of non-existent autogen.sh ------------------------------------------------------------------------ r1011380 | luigiwalser | 2016-05-09 17:58:20 +0200 (ma, 09 mei 2016) | 1 line 5.2.11 ------------------------------------------------------------------------ ==> It lacks the 5.2.12 entry that "magerepo log gutenprint" does show: ------------------------------------------------------------------------ r1144557 | ovitters | 2017-08-23 23:54:47 +0200 (wo, 23 aug 2017) | 1 line SILENT convert -devel buildrequires into pkgconfig ------------------------------------------------------------------------ r1102216 | luigiwalser | 2017-05-16 23:07:37 +0200 (di, 16 mei 2017) | 4 lines - 5.2.12 - rediff patch 4 - remove patch 6 (ijs driver has been removed) ------------------------------------------------------------------------ r1017383 | luigiwalser | 2016-05-21 18:24:17 +0200 (za, 21 mei 2016) | 1 line SILENT: add missing part of patch ------------------------------------------------------------------------ ==> The 5.2.12 entry has an older time stamp than the "Branching for Mageia 6" time stamp I'm confused :-(
Branching is done after last successful build available in repo, not after latest revision in SVN. 'mgarepo rpmlog 6/gutenprint' shows that mga6's gutenprint was build from r1017383 in SVN. So the branching was done after that revision.
CC: (none) => thomas.bigot
Seem to be OK in mga7 now.
Resolution: (none) => FIXEDStatus: NEW => RESOLVEDCC: (none) => fri