Hi,
I'm mailing you as maintainers of various cups* related ports, as I would like to see the problems described in this PRs fixed and the recent upgrade generated far more problems for the users that we all would have liked. Currently there are the following PRs against CUPS: ( http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports&text=cups ) f 2006/06/25 ports/99460 itetcu print/cups: CUPS 1.2.0_x: Unable to open USB device "usb:/dev/ulpt0": Permission denied f 2006/06/29 ports/99602 itetcu CUPS relaying fails f 2006/06/30 ports/99624 itetcu [PATCH] print/cups: update to 1.2.1 f 2006/07/02 ports/99707 itetcu CUPS in ports can't print raw data using application/octet-stream f 2006/07/03 ports/99745 itetcu print/cups: CUPS 1.2.0_x: Unable to open parallel port device file "/dev/lpt0": Permission denied f 2006/07/04 ports/99786 itetcu cups-base OPTIONS don't work and 1.2.1 has been released f 2006/07/04 ports/99791 itetcu cups-base clobbers LPRng f 2006/07/05 ports/99798 itetcu print/cups-base makes symbolic links without entity Plus 2 others against cups-pstoraster (ports/98199, ports/98843) which is unmaintained. - you'll notice that one of the PRs above is an update for cups-base to 1.2.1 - since the rest of the ports that you maintain depend on cups-base, it would be nice I think, to have the dependent ports tested at run time with the new version before the update to cups-base is commited (provided that the maintainer approves the update, of course); while I'm a cups user, I'm not a "heavy " one, so I can't do all this testing. - I would also like to do one or two commits for the above PRs since there's no reason to force users to update cups ports each next day :-) (what I'm saying is that it's better to wait a few days until we can sort all problems out rather that commit incomplete fixes) - I also know there are some open cups-related kde bugs; I don't know if/how they are related to above PRs. In conclusion, before commiting an other update to cups-base, I'd like to know it has been tested with the other ports and have the respective patches for them if necessary. Thanks, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #400: We are Microsoft. What you are experiencing is not a problem; it is an undocumented feature.
signature.asc
Description: PGP signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
