Whether I set in xpdfrc psPaperSize A4 or letter, the header of the postscript generated by pdftops always says: %%DocumentMedia: plain 612 792 0 () () %%BoundingBox: 0 0 612 792 (matching the settings in the PDF file). Contrary to that, pdftops from the original xpdf sources (not xpdf-toppler) works fine. I guess people don't pay attention since many printers are tolerant about media mismatch, but mine (Phaser 8400) is paranoidally picky. Reproducible: Always Steps to Reproduce:
Please try to set the papersize using libpaper and /etc/papersize
(In reply to comment #1) > Please try to set the papersize using libpaper and /etc/papersize It's set to a4. But I don't think xpdf ever uses it: $ ldd /usr/bin/xpdf | grep paper || echo "nada" nada $
Please complain upstream to the poppler devs about this
Pardon me, but isn't this what Gentoo package maintainer is supposed to do?! Instead of each user keeping track of every possible upstream contact/mailing list/whatnot??
well, I do not really care about it. I just think you care more about it and can get it moving faster upstream. Bug reports are better when the reporter cares about getting it solved :) The poppler upstream can be found here: https://bugs.freedesktop.org/enter_bug.cgi?product=poppler
(In reply to comment #5) > well, I do not really care about it. <rant> Then perhaps you should step off as the package maintainer? Sorry to sound rude, but what are then your motivations to maintain this package? Cooking up an ebuild in an overlay tree and keeping it in sync with upstream version incrementing is usually rather trivial task. If this is now the official Gentoo stance ("we don't care about upstream bugs"), maybe it should be stated clearly atop of the bugzilla entry page. </rant>
the reason for bugs to be first filed here is that they could result from gentoo provided patches and thus not fit into upstream bugzilla. On this one I can be sure that it does not result from gentoo provided patches, thus it is an upstream issue, not a gentoo one. It does not make sense to track issues multiple times and from an upstream tracking also other distributions can take advantage. I could step down as a package maintainer maybe but it certainly would not help you. It also will not help to not look at such issues (because that is the alternative ..)
(In reply to comment #7) > It does not make sense to track issues multiple times and from an upstream > tracking also other distributions can take advantage. Absolutely. However, I believe it's the distribution-package maintainer's job to do the forwarding of such bug reports. Ideally, I'd like to see a reply along the lines "the bug is believed to exist in the upstream version, the bug report #XYZ has been filed <http://the/url/to/the/upstream/tracker>". Then, I could follow the tracker, send updates/comments etc if needed. Every Gentoo user knows how to file a report in the Gentoo bugzilla, while finding out the relevant info for a specific upstream takes time (plus the registration hassles, studying the project's FAQ first etc). Don't you agree that on average, chances that a user files a bug upstream are lower? > It also will not help to not look at such issues (because that is the > alternative ..) Hmm, not sure I understood this...
(In reply to comment #8) > Absolutely. However, I believe it's the distribution-package maintainer's job > to do the forwarding of such bug reports. Ideally, I'd like to see a reply > along the lines "the bug is believed to exist in the upstream version, the bug > report #XYZ has been filed <http://the/url/to/the/upstream/tracker>". Then, I > could follow the tracker, send updates/comments etc if needed. I do not believe that is part of my job as package maintainer. And I do not think it is usefull for me to report something that i dont care about. > Every Gentoo user knows how to file a report in the Gentoo bugzilla, while > finding out the relevant info for a specific upstream takes time (plus the > registration hassles, studying the project's FAQ first etc). Don't you agree > that on average, chances that a user files a bug upstream are lower? The chances of a Gentoo developer filing an upstream bug are even lower than that.. so better ask the the user to file it instead of letting the bug rot > > It also will not help to not look at such issues (because that is the > > alternative ..) > > Hmm, not sure I understood this... Well, I do not want to report it upstream, so either you do it or no one does it. It would have just stayed open here for people to look at and for you to be happy. If you dont want to report it we can just reopen this and leave the bug open until someone likes to report it upstream or writes a patch :) BTW: I do believe it is my duty to get patches upstream as a Gentoo developer.
(In reply to comment #9) > I do not believe that is part of my job as package maintainer. Well, that's the problem. > And I do not think it is usefull for me to report something that i dont care about. Useful for you?! It would be useful for _users_! If all you care is your own satisfaction, you shouldn't probably be a maintainer. IMVHO, this position implies some responsibility. > The chances of a Gentoo developer filing an upstream bug are even lower than > that.. so better ask the the user to file it instead of letting the bug rot Again, this is because of your attitude. > BTW: I do believe it is my duty to get patches upstream as a Gentoo developer. What's the difference? In terms of time, it's the same - posting upstream a link to the Gentoo bugzilla entry.
(In reply to comment #10) > > I do not believe that is part of my job as package maintainer. > > Well, that's the problem. You seem to forget one thing. As you're not paying for Gentoo and the support for it, all the work you're benefiting from is thanks to volunteers. And it's no surprise that volunteers decide themselves what responsibilities they volunteer for or not. If you want to decide what Stefan's responsibilities are, feel free to spend your time working for Gentoo, become a developer, and then play a role in all the decision processes that decide what his responsibilities are. We are always happy to welcome new active developers. > > And I do not think it is usefull for me to report something that i dont care about. > > Useful for you?! It would be useful for _users_! If all you care is your own > satisfaction, you shouldn't probably be a maintainer. IMVHO, this position > implies some responsibility. Please let Gentoo officials decide whether Stefan should be maintaining anything or not. > Again, this is because of your attitude. If you want to talk about attitude issues, we could start with yours. You seem content enough to complain about something that's not working the way you want it, even rant about the way we work, but what have you really done to help us or upstream fix this for you ? Denis.
(In reply to comment #11) > You seem to forget one thing. As you're not paying for Gentoo and the support > for it, all the work you're benefiting from is thanks to volunteers. And it's > no surprise that volunteers decide themselves what responsibilities they > volunteer for or not. You are wrong. Whether somebody's get paid for a job or not is irrelevant. E.g., here in Israel many ambulance drivers (and medics) are volunteers. However, if one such a volunteer decides in the middle of an urgent call to drink a cup of coffee around the corner, would you say it's OK? > Please let Gentoo officials decide whether Stefan should be maintaining > anything or not. ?? I haven't noticed I unticked any checkbox in his profile. > If you want to talk about attitude issues, we could start with yours. You seem > content enough to complain about something that's not working the way you want > it, even rant about the way we work, but what have you really done to help us > or upstream fix this for you ? I reported the bug and explained how to reproduce it. Do you believe I was asked for any other help? No, instead I got a reply "I don't care". Again, if this is the expected behavior on part of a Gentoo package maintainer - fine, but (as I said in an earlier comment) it would be nice to have it officially stated/documented. Obviously, I wouldn't bother reporting the bug in the first place.
ok, explaining more: for some ebuilds, like eix I track bugs in Gentoos bugzilla. I dont care there too but I just reassign it to the maintainer then and mark the bug as fixed as soon as I get a version bump. Unfortunately poppler maintainers dont monitor bugzilla so you need to file the bug upstream there. Thanks for asking us beforehand if it is a gentoo bug - and no it is not a bug in the gentoo packaging, it is one in the poppler software. And if you think I am not a good maintainer because I do not do this for you you can certainly do that. It is not like it will cost any lives in this case. And in my opinion it is better to tell you to have no hopes that someone files this upstream for you than to let this bug get old here with you waiting for a reaction eternally.
(In reply to comment #13) > Unfortunately poppler maintainers dont monitor bugzilla Is it at all possible, BTW? Say, in Debian bug tracking system one can subscribe to a package and get every communication forwarded. > no it is not a bug in the gentoo packaging, it is one in the poppler software. Of course, I was quite certain from day one. > And if you think I am not a good maintainer because I do not do this for you > you can certainly do that. It is not like it will cost any lives in this case. No, but it leaves a bad taste for the whole Gentoo (since, apparently, you are not alone). I repeat my point: nobody forced you to take the job of maintaining this package; however, once you _volunteered_ to do it, you should live up to the expectations. Now the only moot point (at least to me) is whether this is the official Gentoo motto today ("we don't bother with upstream bugs") - and then it would be honest to get it written clearly on the wall, or it's your own one - and then you should resign as not satisfying the job requirements. (Note that when I say "you should" I mean it's just logical - why _voluntarily_ take a job you dislike?; not that I'm going in any way to force you, of course.) Is there a third option? > And in my opinion it is better to tell you to have no hopes that someone files > this upstream for you than to let this bug get old here with you waiting for a > reaction eternally. Maybe, like worse is better than worst. Why don't you consider a good-case scenario?
(In reply to comment #14) > one - and then you should resign as not satisfying the job requirements. (Note that would help no one, not you and not me. Besides I can set the job requirements myself because I am the maintainer. And as long as there is no one else looking at the bugs I can handle them as I like to. Feel free to do a better job by looking at the poppler bugs yourself. You can do that by putting a watch on printing@gentoo.org in your settings for example. > that when I say "you should" I mean it's just logical - why _voluntarily_ take > a job you dislike?; not that I'm going in any way to force you, of course.) Is > there a third option? I am just doing what I like to do. And why should I not do a job I like to do? I like to try out new versions of poppler and write ebuilds for them. I do not like to report a bug for you. > > And in my opinion it is better to tell you to have no hopes that someone files > > this upstream for you than to let this bug get old here with you waiting for a > > reaction eternally. > > Maybe, like worse is better than worst. Why don't you consider a good-case > scenario? I am monitoring the printing bugs for some time. I have never seen a "good-case" scenario like some misterious maintainer stepping out of thin air and doing the work. So really you cant start dreaming here. It is as it is now.
(In reply to comment #15) > I am just doing what I like to do. And why should I not do a job I like to do? > I like to try out new versions of poppler and write ebuilds for them. Well, this doesn't need a Gentoo dev status, does it? Everyone can submit a new ebuild/patch via bugzilla. Many users do it (I did it on a couple of occasions, too). So how's your status of an @gentoo.org email owner makes any difference here? (BTW, you're for the n-th time in a row avoid answering my question - is the "I don't care" slogan an accepted Gentoo dev. attitude nowadays?) > So really you cant start dreaming here. It is as it is now. Be it as you like.
