[opensuse-buildservice] How do I unmark packages as a devel project?
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either. The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity. Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Feb 26, 2012 at 08:43:12AM +0200, Dave Plater wrote:
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either.
Which package and which direction?
The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity.
I do not think this kind of locking is good... Most package work in my mind is short timed and should be transfered to the devel project quite fast. There are always merging issue possible, but this should be seldom? ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Sun, Feb 26, 2012 at 08:43:12AM +0200, Dave Plater wrote:
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either. Which package and which direction? One example is "home:plater libkate" is the devel project for "multimedia:libs libkate", I'm not quilte sure of which packages I also did
On 02/26/2012 01:26 PM, Marcus Meissner wrote: this to before I realised that there wasn't an undevel command. I'm sure I've done it to a few more packages as well.
The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity. I do not think this kind of locking is good...
Most package work in my mind is short timed and should be transfered to the devel project quite fast.
There are always merging issue possible, but this should be seldom?
ciao, Marcus
I have a few packages that need a lot of work to update: lilypond and blender are difficult to maintain, I can't remember ever having a lilypond release that didn't have issues, lilypond is large and to have to re checkout the whole package again because somebody with good intentions cleaned up the spec file and a maintainer has innocently accepted it, this has happened before. I also work on other packages while waiting for one to build and publish for testing, I like to install from the online repository to make sure that everything installs smoothly. All said I always copy my local copy into a .backup directory and have needed to use it often. I'm internet bandwidth disadvantaged and every megabyte counts atm due to only having a shared 384K down 64K up connection. Lastly being a community maintainer I need to work for money sometimes and if that happens to be in the middle of ie. "getting lilypond back into factory along with guile1 because I wasn't around to complain when guile was updated to 2.0" it gets extremely frustrating. Luckily another user came to my rescue. If it's only a quick version update, locking is maybe not necessary, I haven't had the situation where I've wasted time updating only to find that somebody else has already done it but multimedia is a high interest area and there are quite a few outside submissions. Maybe a flag that can be set to show in a submit request that another maintainer is already working on the package and redirects the submission the the maintainers home project. Making a package in my home project the devel package of the multimedia satisfies my requirements if I could only undevel it afterwards. Maybe there's already something in place, I haven't even been able to follow the packaging list since January. Thanks Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Feb 28, 2012 at 07:28:56PM +0200, Dave Plater wrote:
On Sun, Feb 26, 2012 at 08:43:12AM +0200, Dave Plater wrote:
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either. Which package and which direction? One example is "home:plater libkate" is the devel project for "multimedia:libs libkate", I'm not quilte sure of which packages I also did
On 02/26/2012 01:26 PM, Marcus Meissner wrote: this to before I realised that there wasn't an undevel command. I'm sure I've done it to a few more packages as well.
Run: osc meta pkg -e multimedia:libs libkate and remove this line: <devel project="home:plater" package="libkate"/> (so basically the devel project is in the one where it points from.) I am leaving the locking part to others ;) Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 02/29/2012 01:05 AM, Marcus Meissner wrote:
Run: osc meta pkg -e multimedia:libs libkate
and remove this line: <devel project="home:plater" package="libkate"/>
(so basically the devel project is in the one where it points from.)
I am leaving the locking part to others;)
Ciao, Marcus Thanks, now all I need to do is make a script to turn it on and off then I have my lock :-) , if needed. Now which other packages did I do this to :-( At least I know what to do when I find them, thanks again.
Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 02/26/2012 07:43 AM, Dave Plater wrote:
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either.
The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity.
The key here is communication and not ignorance, which you showed here: https://build.opensuse.org/stage/package/rdiff?linkrev=base&package=libconfig&project=multimedia%3Alibs&rev=3 where you simply chopped a previous submission (by yours truly): https://build.opensuse.org/stage/package/rdiff?linkrev=base&package=libconfig&project=multimedia%3Alibs&rev=2 The key concept here would have been called 'merging' and isn't really specific to OBS. But lets go on a bit, after 'working' on that package, you reopened a request to Factory (https://build.opensuse.org/request/show/106980) that was reasonably declined (see our packaging policies). It's rather funny that I wanted to do you a favor with just the above submission and fix your issues ;-) Long story short, I would really appreciate if you could stop pretending to be the one true source of wisdom and try to collaborate with others (like me). And don't try to make your home project the devel project for any other project (please revert if you already did), otherwise I'll make mine a devel project of yours! -- Viele Grüße, Sascha Peilicke
On 02/26/2012 07:43 AM, Dave Plater wrote:
After continually getting multimedia packages that I was working on in home:plater, messed up by other submissions I had the bright idea to make the package the devel project of the multimedia:libs package. Unfortunately I can't delete or "undevel" the package and with my current situation I'm not on line enough to manage this either.
The problem I attempted to address is a real problem though, there should be a way for a maintainer to lock the package that he's working on, especially before release when there's a lot of activity.
The key here is communication and not ignorance, which you showed here:
where you simply chopped a previous submission (by yours truly):
The key concept here would have been called 'merging' and isn't really specific to OBS. But lets go on a bit, after 'working' on that package, you reopened a request to Factory (https://build.opensuse.org/request/show/106980) that was reasonably declined (see our packaging policies). It's rather funny that I wanted to do you a favor with just the above submission and fix your issues ;-)
Long story short, I would really appreciate if you could stop pretending to be the one true source of wisdom This comment really baffles me. and try to collaborate with others (like me).
And don't try to make your home project the devel project for any other project (please revert if you already did), otherwise I'll make mine a devel project of yours! I find your language offensive, especially after having a forced absence and still managing to work on bugs using a mobile phone during the
On 03/06/2012 02:14 PM, Sascha Peilicke wrote: period. As I politely pointed out that I was unfamiliar with the new reopen feature and the supersedeing. The correct response would be to enlighten me, I still don't understand what the reopen button is, I have been unable to read any list emails apart from bugzilla and the messages I received from users concerning rosegarden, blender and lilypond. I realise there are differences in communication between english and germans, I have worked with Germans and I have both German and Austrian friends, I try very hard to prevent misunderstanding but in this case I think I failed. I'm still under very difficult circumstances, please understand that my time spent replying to this email is precious but I'm not sure if you could understand poverty and hardship like I do. Dave -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Dave Plater -
Dave Plater -
Marcus Meissner -
Sascha Peilicke