https://bugzilla.novell.com/show_bug.cgi?id=769693 https://bugzilla.novell.com/show_bug.cgi?id=769693#c2 --- Comment #2 from Justin Yaple <yaplej@gmail.com> 2012-07-03 06:14:12 UTC --- Sorry for being a noob but I only use the web interface for building. Probably not the most efficient method but its been working for me. According to the last statement on that page you referenced. "Changing the packages in linked project The project link does not create new source instances of packages. You need to create them manually in addition for example via the "osc branch" command. Afterward you will be able to change the source in the linking project of that package without affecting the other one." I DO plan on changing the contents of both "network:opennop" and "network:opennop:devel" independant of each other. So now questions: 1. Can I still use a "linked project"? 2. How can I create one via the web interface? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=769693 https://bugzilla.novell.com/show_bug.cgi?id=769693#c4 --- Comment #4 from Justin Yaple <yaplej@gmail.com> 2012-07-03 07:24:21 UTC --- Maybe I am going about this in the wrong way? Should I use CLI and make a "linked project" and keep building against SVN trunk then merge the changes when they have been tested/validated? I thought it might be better for the package to be built directly from a /stable rather than /trunk in my SVN. Another possibly "easier" option would be to just branch the package as "opennop-devel"? Maybe I just dont know enough about this to really be doing it but Im only a one guy show right now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.