Hi! The yast2-gtk package is at version 2.21.58 in the project openSUSE:11.3. However, a few bugs [1] were detected and the developer upgraded the version to 2.21.64 to fix them. Now, I have created the patch for the fixes against the older version, in a branched project [2]. To address the version updates, I renamed the source binary from yast2-gtk-2.21.58.tar.bz2 to yast2-gtk-2.21.64.tar.bz2, and the directory in that source also to yast2-gtk-2.21.64. In other words, the source in the branched project is identical to the one in the original project, with only the name changed. Then I apply the patch via the usual patch macro in the spec file: %patch -p1. Everything works, package builds without complains and installs fine. Solves the problems. Eventually, I want to submit this for maintenance release, and I wanted to know if the procedure I followed is an acceptable way of doing it or is there a better way to do this? Is it okay if the package being submitted for a maintenance release has a source with a different version number compared to the original package in the distribution? Would be much grateful for any help. [1] Critical: https://bugzilla.novell.com/show_bug.cgi?id=620513 Medium: https://bugzilla.novell.com/show_bug.cgi?id=609778 [2] https://build.opensuse.org/project/show?project=home%3Abadshah400% 3Abranches%3AopenSUSE%3A11.3 Bye -- Atri -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org