Hi, please fix the dependency of the gimp-2.2.0 ebuild to accept gimp-print >= 4.2 and not only =4.2.*.I have tested it with gimp-print-5.0-beta2 and it works quite fine. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: gimpprint? ( =media-gfx/gimp-print-4.2* ) Expected Results: gimpprint? ( >=media-gfx/gimp-print-4.2 )
Doesn't work here. Gimp-2.2 wont build after installing the 5.0-beta2, claims it can't find libgimpprint nor gimpprint's config file.
i still don't know what this flag is good for, gimp-print-5.0.0-beta3 installs the printing plugin for gimp, but why this dependency inside gimp?
Changing the dependency to >=gimp-print-4.2 causes the emerge of gimp to fail with the following error: checking for gimpprint-config... no checking for GIMP-PRINT - version >= 4.2.0... no *** The gimpprint-config script installed by GIMP-PRINT could not be found *** If GIMP-PRINT was installed in PREFIX, make sure PREFIX/bin is in *** your path, or set the GIMPPRINT_CONFIG environment variable to the *** full path to gimpprint-config. configure: error: *** Check for libgimpprint failed. You can download it from *** http://gimp-print.sourceforge.net/ or you can build without it by passing *** --disable-print to configure (but you won't be able to print then). !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/gimp-2.2.3/work/gimp-2.2.3/config.log Could emerge gimp with USE="-gimpprint" emerge gimp but would then not be able to print from gimp.
I've got gimp 2.2.3 installed and gimp-print 5.0.0_beta3, and the print option in Gimp appears to work. Before, I had gimp installed using the gimpprint USE flag, and it was in a constant upgrade/downgrade cycle between gimp-print 5.0.0_beta3 and 4.2.7. The fix was to just not use the gimpprint USE flag.
I had the same problem here. Changing the ebuild dependency to: gimpprint? ( >=media-gfx/gimp-print-4.2 ) didn't help, as the gimp configure script couldn't find gimpprint-config (there isn't none included in gimpprint-5.0.0) I copied the gimpprint-config from gimp-print-4.2.7 and changed it so that the version returned 5.0.0. Then the gimp configure script complained that the gimpprint version was too new. I manually removed this verification (editing the gimp configure script) and it is compiling now. I don't know if the gimp-print plugin will work though, will post as soon as I can print something.
*** Bug 87928 has been marked as a duplicate of this bug. ***
*** Bug 92354 has been marked as a duplicate of this bug. ***
According to configure.in: m4_define([gimpprint_required_version], [4.2.0]) m4_define([gimpprint_suggested_version], [4.2.6]) m4_define([gimpprint_toonew_version], [4.3.0]) Therefore, if you use >=4.2.*, gimp maintainers don't support it. The ebuilds will stay how they are until the maintainers say that its okay to use a later ( probably non-beta ) version of gimp-print. Thanks for reporting!
*** Bug 92476 has been marked as a duplicate of this bug. ***
*** Bug 93222 has been marked as a duplicate of this bug. ***
*** Bug 95330 has been marked as a duplicate of this bug. ***
*** Bug 100047 has been marked as a duplicate of this bug. ***
*** Bug 103469 has been marked as a duplicate of this bug. ***
well, somebody please fix it so updating world doesn't constantly flip between 5.0 and 4.2 please. it's frustrating to have a crontab script that keeps running constantly because there gimp print always needs "updated".
*** Bug 109247 has been marked as a duplicate of this bug. ***
(In reply to comment #15) > well, somebody please fix it so updating world doesn't constantly flip between > 5.0 and 4.2 please. it's frustrating to have a crontab script that keeps > running constantly because there gimp print always needs "updated". man portage - /etc/portage/package.mask
the point is to fix the problem, not cover up the symptoms. my package.[un]mask files grow and grow. this isn't the only package that does this. as for cyclic dependancies, the only dependancy parent showing up is gimp.
to bug 'maintainers': you keep dropping all 'cyclic rebuilds on gimp-print' under this topic, which is pointless. The pople who are complaining (i guess) don't want to have gimp-print > 4.2, they just don't want to have gimp-print constantly flipping form one version to another. Because of what you do, this 'flipping' BUG (because it is a bug!) cannot reach people who maintain ebuilds because you keep it as resolved/invalid (which is not true). Please sort it out.
I see that rc1 is out on SF, is there any way to get this package to play with gimp2.xx ? I really need these drivers for my Cannon i965 , the gimp-print-4x just dont work. I did at one stage get beta2 to work with some voersion of gimp-2 but with all this up/downing and ebuilds getting pulled I just cant get anything to print anymore. I can get a lovely test page of CUPS but no joy at all were it counts: gimp. Any suggestions ? TIA
There must be a way for this to run with gimp it has got through 4 beta releases , why cant it install on gentoo ?
this is a closed invalid bug. The GNOME herd does not support anything upstream doesn't. We also do not support unstable builds ( which means RC builds as well ). Please see comment #8 if you want a reason why we will not support it. Stop using --deep and you will stop having upgrade/downgrade cycles. Thanks
OK, so where is "upstream"? Last time I tried to get direct support I found rapids, barrages and waterfalls had to be traversed to get "upstream". I am not a salmon and I dont have a helicopter, so if the 'herd' wants to pass responsability on this and you know a short-cut arround the rapids, let's have it ;) gimp seems to be _the_ must-have image processing package for Linux and I cant even use it. I do not intend to start rebooting to windows installation every time I need a printer. TIA
*** Bug 110691 has been marked as a duplicate of this bug. ***
(In reply to comment #19) > The pople who are complaining (i guess) > don't want to have gimp-print > 4.2, they just don't want to have gimp-print > constantly flipping form one version to another. Maybe you might review man portage - /etc/portage/package.mask, as already noted in comment #17. > Because of what you do, this 'flipping' BUG (because it is a bug!) cannot reach > people who maintain ebuilds because you keep it as resolved/invalid (which is > not true). Please sort it out. Maybe you might review the bugzilla instructions on the front page, especially the bold letter "Note: When searching for duplicate bugs, prefix search with 'ALL'" (In reply to comment #23) > OK, so where is "upstream"? Last time I tried to get direct support I found > rapids, barrages and waterfalls had to be traversed to get "upstream". http://www.gimp.org/ Everyone here, stop posting useless rants to a CLOSED INVALID bug.
Well, last one note from me: I was a huge gentoo hype .. 2 years ago. Several servers and desktops with this distro. Now i have just one last installation. Two main reasons are baselayout upgrades that completely screw up installation (especially diskless). And approach to bugs (aka 'its not a bug, since you can patch it yourself', 'it works for me' or 'its not our problem, go upstream'). And a few of my colegues had the same experience. I can tell you this: its a best way to loose users. But maybe you we'll be better of without them - you won't be getting any complaints then. I think a new slogan is in order: Please forward it with my best wishes to the team: "Gentoo - we don't care if it works"
(In reply to comment #26) > "Gentoo - we don't care if it works" Ah, sure; which part of the following have you missed? m4_define([gimpprint_required_version], [4.2.0]) m4_define([gimpprint_suggested_version], [4.2.6]) m4_define([gimpprint_toonew_version], [4.3.0]) We won't be supporting >gimp-print-4.2 until upstream supports it and upstream apparently won't support alpha/beta releases of gimp-print either - what a surprise. ;p So put one line into your package.mask and stop buspamming others. TIA.
How about the part that you miss where 5.0 is working? It's entirely obvious that some versions of software work for some people and other versions don't based on their system. Heck, look at auto* packages where you pretty much need every friggen version installed. Users shouldn't have to manually package.mask something for something like version flipping. Obviously version X was acceptable at one point in time and the very next emerge action wants to flip the version to Y with NO OTHER software changing in the system. THAT is a bug. In this case it happens to be associated with gimp-print. But there are other software packages that do this too. Glossing over bugs by package.mask'ing the symptoms isn't a fix. You might even get a lot more help and happy users simply by acknowledging that users don't like this BUG and that it IS a bug -- regardless of the fact that it is or isn't fixed. Telling people off, marking things invalid, won't fix, upstream, etc, basically avoiding or rudely ignoring users does exactly one thing, it irritates users and drives them away. If you crap your pants and walk through public, even though you go wipe, people are still going to remember you and avoid you. And they'll talk about you. It'll take a lot of effort to win those people back again plus the hundreds of people they passed the word on to. So please stop being a bug buck-passer, and just do the simple and courteous thing of acknowledging bug reporters. It's no wonder why a growing number of people thumb their noses at Gentoo, refuse to post bugs, or plain jump ship. If you want Gentoo to be a developer's only distribution having lost all it's users, fine. Be that way. You'll be alone in your libsandbox without any users and your distro will die. But the pride and glory of ANYTHING, isn't the product, it's the customer service. And it's customer service that decides whether your and your product live or die. Always.
Very nicely put. I think this is becoming a critical issue for Gentoo. I wont distract by adding more than a "me too" since I think you sum it up very well. me too!
*** Bug 117667 has been marked as a duplicate of this bug. ***
*** Bug 118370 has been marked as a duplicate of this bug. ***
*** Bug 118649 has been marked as a duplicate of this bug. ***
>>Telling people off, marking things invalid, won't fix, upstream, etc, >>basically avoiding or rudely ignoring users does exactly one thing, it >>irritates users and drives them away. the other disadvantage if INVALID is when it does get fixed no-one is any the wiser because the bug is already closed. I'd had to mess around putting masks and stuff in place to stop the flip-flop on gimp-print. It seems a better policy would be LATER, rather than INVALID which is was not. So I suppose this could finally changed to resolved FIXED, since it has been and anyone watching the bug will get a ping. ;)
*** Bug 185337 has been marked as a duplicate of this bug. ***
