Bug#698632: rstatd: Patch 03-627217-netio.patch breaks RPC protocol compatibility for rstatd
On Tue, Feb 05, 2013 at 03:43:56PM +0100, Salvatore Bonaccorso wrote: At this stage of the freeze this option (droping the patch for 627217) looks the best to me, what do you think Anibal? Hello Salvatore, I'll prepare a new package without it. Cheers, Aníbal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698632: rstatd: Patch 03-627217-netio.patch breaks RPC protocol compatibility for rstatd
627217 found rstatd/4.0.1-8 stop On Mon, Jan 21, 2013 at 02:50:43PM +0100, Salvatore Bonaccorso wrote: Source: rstatd Version: 4.0.1-7 Severity: serious Justification: Regression, mixed environments Squeeze and Wheezy -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Anibal At our workplace we found that the patch 03-627217-netio.patch introduced in version 4.0.1-5 breaks the compatibility of rstatd in a inhomogeneous setup, where wheezy, squeeze and even solaris hosts interact. I have set the severity to serious as it introduces a 'regression' for Squeeze - - Wheezy, where one has mixed Squeeze and Wheezy setups, but can be downgraded to important if you don't agree. But IMHO should get version working in mixed environment. Here is a small example to reproduce the problem: sid 192.168.122.53 (rstatd and rstat-client 4.0.1-7) squeeze 192.168.122.54 (rstatd and rstat-client 4.0.1-4+squeeze1) - cut-cut-cut-cut-cut-cut- root@sid:~# rup 192.168.122.53 sid 12:50 up 3:58,1 user, load 0.00 0.01 0.04 root@sid:~# rup 192.168.122.54 rup: RPC: Success root@sid:~# - cut-cut-cut-cut-cut-cut- - cut-cut-cut-cut-cut-cut- root@squeeze:~# rup 192.168.122.53 192.168.122.53 1:00 up , 1358769030 load 0.00 0.01 0.04 root@squeeze:~# rup 192.168.122.54 squeeze 12:50 up 2 days,3:39,1 user, load 0.00 0.00 0.00 root@squeeze:~# - cut-cut-cut-cut-cut-cut- (Note that rup also shows wrong information on 192.168.122.53). Reverting the patch 03-627217-netio.patch let it work in a mixed squeeze, wheezy environment. If 627217 can be fixed, it should probably without breaking the protocol. After reverting the patch the requests give again correct results. - cut-cut-cut-cut-cut-cut- root@sid:~# rup 192.168.122.53 sid 14:13 up 5:22,1 user, load 0.00 0.01 0.05 root@sid:~# rup 192.168.122.54 192.168.122.5414:13 up 2 days,5:02,0 user, load 0.00 0.00 0.00 - cut-cut-cut-cut-cut-cut- - cut-cut-cut-cut-cut-cut- root@squeeze:~# rup 192.168.122.53 192.168.122.5314:14 up 5:22,0 user, load 0.00 0.01 0.05 root@squeeze:~# rup 192.168.122.54 squeeze 14:14 up 2 days,5:02,1 user, load 0.00 0.00 0.00 root@squeeze:~# - cut-cut-cut-cut-cut-cut- Could you please revert at least 03-627217-netio.patch (if fixing #627217 without creating the compatibility issue cannot be fixed)? Regards, Salvatore -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ/UeuAAoJEHidbwV/2GP+SmsP/ivgYb8Usx1/t4L3kt1Rn6L8 Qc2wvdq92n76axAJ8XYDEyhvZH1AQHLa3SQihNbfQEtDp0Br7OP4uaqrSB+zPhE/ +VIv4iffUmKTCimAeBdQnSyrzoY2OgzKxExga0ESaK7Eld/UtrPDJdrz4DSPlcS2 XpIg6HzwNImkVjkAzOb0rWo/CP2JsQvO8yJ4I8W0Ojh+GczXFugkJ8PMh3siesxw jm2tI6Sd1uLu7dtFmb+EScLCdZy7PB8g8MoyxmXZDOAXQ+D+n+BL+T+jYC6Mentg KgJb0/URM2FO6blGYNgAEfptYP6TGK6IODlpe2217S/HUDFo3X2KUHU3mIWk0udJ JGxHZhhONaMXnjZSl4+beynl/hs1KD0PxP560A6EvkfRoeakOVaHbpCBly/88WaQ zY1+TSy/oDumcG7Tf2MBbo3NiAY9WYzni2Z6/J2P5wI3VVadIzQtbZFcZDq5nUp2 pzF/glRw1ZLc2bK6c/D8xRiMceAlTL/LnLUUkoNGcfmEjQ/I4BJGosQr4UFUmUT4 7q7za/9xhqoqxYpsayKRcCo577tOVibEn55QnIElBv0zm/9YdsgxdX0w4i4A8LXF x0Rnzy4tUitA4/8Id8rpbhixLohXrpYVvYsbfP3nixbx9KdeA4MV48AsMZcgiXjX psYM7kFTjZcA2osZ/tqd =qt2D -END PGP SIGNATURE- Hello Thomas, Christian Oetzel's patch introduced a regression and I would be great if he could have look at this bug report: http://bugs.debian.org/698632 The original patches are at: http://bugs.debian.org/627217 Please pass this message on to Christian Oetzel. Cheers, Anibal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698632: rstatd: Patch 03-627217-netio.patch breaks RPC protocol compatibility for rstatd
Hi Anibal On Mon, Jan 21, 2013 at 02:50:43PM +0100, Salvatore Bonaccorso wrote: Reverting the patch 03-627217-netio.patch let it work in a mixed squeeze, wheezy environment. If 627217 can be fixed, it should probably without breaking the protocol. After reverting the patch the requests give again correct results. [...] Could you please revert at least 03-627217-netio.patch (if fixing #627217 without creating the compatibility issue cannot be fixed)? At this stage of the freeze this option (droping the patch for 627217) looks the best to me, what do you think Anibal? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698632: rstatd: Patch 03-627217-netio.patch breaks RPC protocol compatibility for rstatd
Source: rstatd Version: 4.0.1-7 Severity: serious Justification: Regression, mixed environments Squeeze and Wheezy -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Anibal At our workplace we found that the patch 03-627217-netio.patch introduced in version 4.0.1-5 breaks the compatibility of rstatd in a inhomogeneous setup, where wheezy, squeeze and even solaris hosts interact. I have set the severity to serious as it introduces a 'regression' for Squeeze - - Wheezy, where one has mixed Squeeze and Wheezy setups, but can be downgraded to important if you don't agree. But IMHO should get version working in mixed environment. Here is a small example to reproduce the problem: sid 192.168.122.53 (rstatd and rstat-client 4.0.1-7) squeeze 192.168.122.54 (rstatd and rstat-client 4.0.1-4+squeeze1) - cut-cut-cut-cut-cut-cut- root@sid:~# rup 192.168.122.53 sid 12:50 up 3:58,1 user, load 0.00 0.01 0.04 root@sid:~# rup 192.168.122.54 rup: RPC: Success root@sid:~# - cut-cut-cut-cut-cut-cut- - cut-cut-cut-cut-cut-cut- root@squeeze:~# rup 192.168.122.53 192.168.122.53 1:00 up , 1358769030 load 0.00 0.01 0.04 root@squeeze:~# rup 192.168.122.54 squeeze 12:50 up 2 days,3:39,1 user, load 0.00 0.00 0.00 root@squeeze:~# - cut-cut-cut-cut-cut-cut- (Note that rup also shows wrong information on 192.168.122.53). Reverting the patch 03-627217-netio.patch let it work in a mixed squeeze, wheezy environment. If 627217 can be fixed, it should probably without breaking the protocol. After reverting the patch the requests give again correct results. - cut-cut-cut-cut-cut-cut- root@sid:~# rup 192.168.122.53 sid 14:13 up 5:22,1 user, load 0.00 0.01 0.05 root@sid:~# rup 192.168.122.54 192.168.122.5414:13 up 2 days,5:02,0 user, load 0.00 0.00 0.00 - cut-cut-cut-cut-cut-cut- - cut-cut-cut-cut-cut-cut- root@squeeze:~# rup 192.168.122.53 192.168.122.5314:14 up 5:22,0 user, load 0.00 0.01 0.05 root@squeeze:~# rup 192.168.122.54 squeeze 14:14 up 2 days,5:02,1 user, load 0.00 0.00 0.00 root@squeeze:~# - cut-cut-cut-cut-cut-cut- Could you please revert at least 03-627217-netio.patch (if fixing #627217 without creating the compatibility issue cannot be fixed)? Regards, Salvatore -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ/UeuAAoJEHidbwV/2GP+SmsP/ivgYb8Usx1/t4L3kt1Rn6L8 Qc2wvdq92n76axAJ8XYDEyhvZH1AQHLa3SQihNbfQEtDp0Br7OP4uaqrSB+zPhE/ +VIv4iffUmKTCimAeBdQnSyrzoY2OgzKxExga0ESaK7Eld/UtrPDJdrz4DSPlcS2 XpIg6HzwNImkVjkAzOb0rWo/CP2JsQvO8yJ4I8W0Ojh+GczXFugkJ8PMh3siesxw jm2tI6Sd1uLu7dtFmb+EScLCdZy7PB8g8MoyxmXZDOAXQ+D+n+BL+T+jYC6Mentg KgJb0/URM2FO6blGYNgAEfptYP6TGK6IODlpe2217S/HUDFo3X2KUHU3mIWk0udJ JGxHZhhONaMXnjZSl4+beynl/hs1KD0PxP560A6EvkfRoeakOVaHbpCBly/88WaQ zY1+TSy/oDumcG7Tf2MBbo3NiAY9WYzni2Z6/J2P5wI3VVadIzQtbZFcZDq5nUp2 pzF/glRw1ZLc2bK6c/D8xRiMceAlTL/LnLUUkoNGcfmEjQ/I4BJGosQr4UFUmUT4 7q7za/9xhqoqxYpsayKRcCo577tOVibEn55QnIElBv0zm/9YdsgxdX0w4i4A8LXF x0Rnzy4tUitA4/8Id8rpbhixLohXrpYVvYsbfP3nixbx9KdeA4MV48AsMZcgiXjX psYM7kFTjZcA2osZ/tqd =qt2D -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
