-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/17/13 00:38, Vincent W. Chen wrote: > > When you say "rebuilding fvwm without deprecated.patch", what steps did you > take? Since the patches are the same, it means that when you tested the new > patch with the previous version (1:2.6.5.ds-1), the bug wasn't fixed. I'd > like to know how you go about rebuilding fvwm. >
Using your new patch I had created a new source package (I edited patch/series to kick out "deprecated.patch" and to append "deprecated.new.patch"). Looking at "quilt push -a" I verified that the new patch is in. The binary package was built using pbuilder. I still have the source and binary packages of the test build. If I install the test binary today, then the problem is still in, so I would guess I had made a mistake at install time. Please accept my apologies. Of course I still would be glad if I could help to get this problem fixed. Regards Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEg8egACgkQUTlbRTxpHjcDqQCfTCJZQ/KHJ97BrWVe/xK2iRlU BF8Aniv1oEfaR/kgchNDiBpnwn6xpLTk =xh9a -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
