"{0,100}?". No change same failures.
"*?" Lots more failures.
Not done any tests with bigger than 100, the request is too open ended!
Is it time to reassess this approach? I suggest we ensure that the DRV
file is correct at package build time and push the required changes
upstream. Running a script at install time to try to correct the file
seems like asking for trouble to me. Is their any way to use
UIConstraints to ensure that any printer that requires special duplex
page sizes does not allow the option to be set without a duplex page
size being selected. I we have to run a script then do it at package
build time and error the build process if this results in an invalid DRV
file.
My procedure for running these tests is as follows.
Starting with the source package installed.
1. Run configure to generate the DRV file from the templates.
2. Copy the generated file to my testing directory.
3. For each test I do.
4. Make another temporary copy of the file I copied from the source.
5. Run ppdc -t tempfile | grep " FAIL" > fails.orig to get a baseline.
6. Run the script or a modified version of the script.
7. Run ppdc -t tempfile | grep " FAIL" >fails.new
This should ensure that I am testing the in the states before and after
the script had modified the file at install time.
The space in front of the FAIL in the grep is to filter out all the individual
fails and leave the ones that just contain the printer model name. It should be
removed to catch all fails.
Cheers,
Roger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly for HP printers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
