[opensuse-packaging] How to unlink a package?

newer
[opensuse-packaging] Can someone...

older
Re: [opensuse-packaging] How to...

Johannes Meixner

2 Apr 2014 2 Apr '14

07:35

Hello, what "osc" command can unlink a package? I am looking for the counterpart of "osc linkpac". What I tried: ------------------------------------------------------------------------ $ osc list Printing foomatic-filters _link foomatic-filters-4.0.12.tar.gz foomatic-filters.changes foomatic-filters.spec Link "Printing/foomatic-filters" cannot be expanded: openSUSE:Factory/foomatic-filters: package 'foomatic-filters' does not exist Use "osc repairlink" to fix merge conflicts. $ osc repairlink Printing foomatic-filters using link target of last commit Server returned an error: HTTP Error 400: openSUSE Factory/foomatic-filters package 'foomatic-filters' does not exist openSUSE:Factory/foomatic-filters: package 'foomatic-filters' does not exist $ osc detachbranch Printing foomatic-filters Copying files... package 'Printing/foomatic-filters' is no link ------------------------------------------------------------------------ I did not find documentation how to do it correctly. I only found http://lists.opensuse.org/opensuse-buildservice/2010-05/msg00289.html and http://lists.opensuse.org/opensuse-packaging/2013-09/msg00211.html but both ended in workarounds. I don't know if plain removing of the _link file is the official right solution. It feels more like a low-level hack than a proper counterpart of "osc linkpac". But even if that is the official right solution, I don't find an osc command how to delete one particular file on the server. According to "osc help rdelete" one can at the least delete a whole package. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Show replies by date

Adrian Schröter

2 Apr 2 Apr

07:57

On Mittwoch, 2. April 2014, 09:35:50 wrote Johannes Meixner:

...

Hello,

what "osc" command can unlink a package?

you can checkout unexpanded with either: osc up -u osc co -u PROJECT PACKAGE remove the _link file and commit again..

...

I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package. But I hope you did use "branch" command instead as recommended since years.

...

What I tried: ------------------------------------------------------------------------ $ osc list Printing foomatic-filters _link foomatic-filters-4.0.12.tar.gz foomatic-filters.changes foomatic-filters.spec Link "Printing/foomatic-filters" cannot be expanded: openSUSE:Factory/foomatic-filters: package 'foomatic-filters' does not exist Use "osc repairlink" to fix merge conflicts.

$ osc repairlink Printing foomatic-filters using link target of last commit Server returned an error: HTTP Error 400: openSUSE Factory/foomatic-filters package 'foomatic-filters' does not exist openSUSE:Factory/foomatic-filters: package 'foomatic-filters' does not exist

$ osc detachbranch Printing foomatic-filters Copying files... package 'Printing/foomatic-filters' is no link ------------------------------------------------------------------------

I did not find documentation how to do it correctly.

I only found http://lists.opensuse.org/opensuse-buildservice/2010-05/msg00289.html and http://lists.opensuse.org/opensuse-packaging/2013-09/msg00211.html but both ended in workarounds.

I don't know if plain removing of the _link file is the official right solution. It feels more like a low-level hack than a proper counterpart of "osc linkpac".

But even if that is the official right solution, I don't find an osc command how to delete one particular file on the server. According to "osc help rdelete" one can at the least delete a whole package.

Kind Regards Johannes Meixner

-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Johannes Meixner

08:51

Hello, On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...

...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past. I only try now to clean up mess that OBS/osc has left behind. I could as well recommend you to "just have made" OBS/osc so that no mess could ever happen. By the way: I wonder why "linkpac" still exist and can be used without a warning message when users of it can get lost? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

Adrian Schröter

09:13

On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...

Hello,

On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me. I repeat this at any time on many public mailing lists when someone is mentioning this antic "linkpac" since almost exactly 6 years now. This is our default and if you ever have released a maintenance update you are aware of this command.

...

I only try now to clean up mess that OBS/osc has left behind. I could as well recommend you to "just have made" OBS/osc so that no mess could ever happen.

You can als ask for a text edit which does not allow to do program bugs. Merge conflicts is something what always can happen and all scm tools on this planet need to deal with. And mergeing something with something removed is not even handled at all by others.

...

By the way: I wonder why "linkpac" still exist and can be used without a warning message when users of it can get lost?

there is a usecase for it, but not for what you are doing. And I will not suddenly add a warning there after 6 years. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Johannes Meixner

09:37

Hello, On Apr 2 11:13 Adrian Schröter wrote (excerpt):

...

On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me.

I did not do anything here. I only asked how to clean up OBS' mess. It is inappropriate to now talk to me about mercy. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

Adrian Schröter

09:45

On Mittwoch, 2. April 2014, 11:37:56 wrote Johannes Meixner:

...

Hello,

On Apr 2 11:13 Adrian Schröter wrote (excerpt):

...
On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me.

I did not do anything here. I only asked how to clean up OBS' mess.

It is your messy setup. This is like blaming gcc for not compiling code with syntax errors.

...

It is inappropriate to now talk to me about mercy.

It is also inappropriate to claim that OBS broke your stuff when you created the mess yourself. the reality is that your package do not contain the sources, because you always only follow the other package instance which got removed. In that case you are just lost now. (But I can not verify since there was no hint of your package instance in your mail). You need to re-import them from somewhere, eg. the last src.rpm. Or undelete the package instance again in the target. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Johannes Meixner

11:08

Hello, On Apr 2 11:45 Adrian Schröter wrote (excerpt):

...

On Mittwoch, 2. April 2014, 11:37:56 wrote Johannes Meixner:

...
On Apr 2 11:13 Adrian Schröter wrote (excerpt):

...
On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me.

I did not do anything here. I only asked how to clean up OBS' mess.

It is your messy setup.

I did not do what you call a "messy setup". I am the wrong addressee for such comments. I wonder why you insist to wander from the subject and accuse me of what you think I had done wrong in the past when I had not done it but only asked for the right way how to clean up a current mess in OBS?

...

the reality is that your package do not contain the sources,

The reality is that the package contains sources. Perhaps you may have to re-read more carefully what I wrote? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

Stephan Kulow

11:11

On 02.04.2014 13:08, Johannes Meixner wrote:

...

The reality is that the package contains sources. Perhaps you may have to re-read more carefully what I wrote?

No idea why you guys keep discuss things that didn't happen. Just do what Adrian wrote in his initial reply and forget about the rest:

...

osc co -u PROJECT PACKAGE

remove the _link file and commit again..

Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Adrian Schröter

11:13

On Mittwoch, 2. April 2014, 13:08:57 wrote Johannes Meixner:

...

Hello,

On Apr 2 11:45 Adrian Schröter wrote (excerpt):

...
On Mittwoch, 2. April 2014, 11:37:56 wrote Johannes Meixner:

...
On Apr 2 11:13 Adrian Schröter wrote (excerpt):

...
On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
> I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me.

I did not do anything here. I only asked how to clean up OBS' mess.

It is your messy setup.

I did not do what you call a "messy setup". I am the wrong addressee for such comments.

I wonder why you insist to wander from the subject and accuse me of what you think I had done wrong in the past when I had not done it but only asked for the right way how to clean up a current mess in OBS?

I suggested that already in the very first mail and I did not heard about any results yet.

...

...
the reality is that your package do not contain the sources,

The reality is that the package contains sources. Perhaps you may have to re-read more carefully what I wrote?

and what exactly is not working then what I suggested in my very first mail? Have you tried at all? -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Richard Biener

09:59

On Wed, 2 Apr 2014, Adrian Schröter wrote:

...

On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
Hello,

On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me. I repeat this at any time on many public mailing lists when someone is mentioning this antic "linkpac" since almost exactly 6 years now.

This is our default and if you ever have released a maintenance update you are aware of this command.

Err, but "branch" and "linkpac" do different things! So don't tell people that "branch" is always the correct thing to do. It's not. Richard.

Adam Spiers

10:29

Richard Biener (rguenther@suse.de) wrote:

...

On Wed, 2 Apr 2014, Adrian Schröter wrote:

...
On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me. I repeat this at any time on many public mailing lists when someone is mentioning this antic "linkpac" since almost exactly 6 years now.

This is our default and if you ever have released a maintenance update you are aware of this command.

Err, but "branch" and "linkpac" do different things! So don't tell people that "branch" is always the correct thing to do. It's not.

Right. Last I heard, there were still some perfectly valid use cases for linkpac, and SUSE's Cloud team is still using them IIUC. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Adrian Schröter

10:47

On Mittwoch, 2. April 2014, 11:59:28 wrote Richard Biener:

...

On Wed, 2 Apr 2014, Adrian Schröter wrote:

...
On Mittwoch, 2. April 2014, 10:51:22 wrote Johannes Meixner:

...
Hello,

On Apr 2 09:57 Adrian Schröter wrote (excerpt):

...
...
I am looking for the counterpart of "osc linkpac".

well, if you indeed still use "linkpac" you are lost here, since no files beside the _link is in you package.

But I hope you did use "branch" command instead as recommended since years.

I did not do anything here. It is unfair to now tell me what would have been recommended to be done by others in the past.

You can not get any mercy here from me. I repeat this at any time on many public mailing lists when someone is mentioning this antic "linkpac" since almost exactly 6 years now.

This is our default and if you ever have released a maintenance update you are aware of this command.

Err, but "branch" and "linkpac" do different things! So don't tell people that "branch" is always the correct thing to do. It's not.

and some lines below I wrote exactly this as a reason why I do not suddenly add a warning there. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Andreas Schwab

3 Apr 3 Apr

09:53

New subject: [opensuse-packaging] Re: How to unlink a package?

Richard Biener writes:

...

Err, but "branch" and "linkpac" do different things!

Though the net effect is mostly the same (and you can easily convert the latter into the former). Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Stefan Seyfried

9 Apr 9 Apr

15:35

New subject: [opensuse-packaging] Re: How to unlink a package?

Am 03.04.2014 11:53, schrieb Andreas Schwab:

...

Richard Biener writes:

...
Err, but "branch" and "linkpac" do different things!

Though the net effect is mostly the same (and you can easily convert the latter into the former).

How? (I always use linkpac to link packages into my home to have them availably before factory is built, openssl for example, and then I start messing around with them adding project.diff over time. Now I'll probably add a "sed 's/linkpac/branch/'" to my osc wrapper script :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Adrian Schröter

15:55

New subject: [opensuse-packaging] Re: How to unlink a package?

On Mittwoch, 9. April 2014, 17:35:36 wrote Stefan Seyfried:

...

Am 03.04.2014 11:53, schrieb Andreas Schwab:

...
Richard Biener writes:

...
Err, but "branch" and "linkpac" do different things!

Though the net effect is mostly the same (and you can easily convert the latter into the former).

How?

(I always use linkpac to link packages into my home to have them availably before factory is built, openssl for example, and then I start messing around with them adding project.diff over time. Now I'll probably add a "sed 's/linkpac/branch/'" to my osc wrapper script :-)

and call "osc linktobranch" for your packages. We did this for all factory devel pakcages at least several years ago. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

3669

Age (days ago)

3676

Last active (days ago)

List overview

Download

14 comments

7 participants

participants (7)

Adam Spiers
Adrian Schröter
Andreas Schwab
Johannes Meixner
Richard Biener
Stefan Seyfried
Stephan Kulow

[opensuse-packaging] How to unlink a package?

tags

participants (7)