is there an OBS RPM archive?
In order to research a problem with an older build of an OBS package (syncthing - https://build.opensuse.org/package/show/network/syncthing) i am looking for older versions of this package? Is there any chance to retrieve older builds?
On Saturday 2021-03-13 18:47, Alex Bihlmaier wrote:
In order to research a problem with an older build of an OBS package (syncthing - https://build.opensuse.org/package/show/network/syncthing) i am looking for older versions of this package?
Is there any chance to retrieve older builds?
No, only source.
Am 13. März 2021 20:37:12 MEZ schrieb Jan Engelhardt <jengelh@inai.de>:
On Saturday 2021-03-13 18:47, Alex Bihlmaier wrote:
In order to research a problem with an older build of an OBS package (syncthing - https://build.opensuse.org/package/show/network/syncthing) i am looking for older versions of this package?
Is there any chance to retrieve older builds?
No, only source.
...from where you could branch and build in your home project Cheers Axel
Hello, [please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ] Am Sonntag, 14. März 2021, 09:49:28 CET schrieb Axel Braun:
Am 13. März 2021 20:37:12 MEZ schrieb Jan Engelhardt:
On Saturday 2021-03-13 18:47, Alex Bihlmaier wrote:
Is there any chance to retrieve older builds?
No, only source.
...from where you could branch and build in your home project
Yes, in theory. In practise you'll build the old source (good) against the current dependencies (libraries, compiler, ...). I'm not sure if I should call this "bad", but I'm quite sure you'll get a different result than building with the original ("old") dependencies, with the difference becoming bigger the older your sources are. You can of course link all the old versions of libraries etc. into your home project so that you indeed build with the old dependencies, but this will probably become a looooong list of packages. Regards, Christian Boltz -- This message was sent using 100 % recycled electrons.
Am Sonntag, 14. März 2021, 15:37:45 CET schrieb Christian Boltz:
Hello,
[please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ]
As long as we rely on manual removal, this fight will be Don Quijoteresque.. Pete
Am 14.03.21 um 21:52 schrieb Hans-Peter Jansen:
Am Sonntag, 14. März 2021, 15:37:45 CET schrieb Christian Boltz:
Hello,
[please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ]
As long as we rely on manual removal, this fight will be Don Quijoteresque..
Pete
When will opensuse-factory@ be dropped? Regards, Frank
On 14/03/2021 22.13, Frank Krüger wrote:
Am 14.03.21 um 21:52 schrieb Hans-Peter Jansen:
Am Sonntag, 14. März 2021, 15:37:45 CET schrieb Christian Boltz:
Hello,
[please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ]
As long as we rely on manual removal, this fight will be Don Quijoteresque..
Pete
When will opensuse-factory@ be dropped?
I understand there is no plan to drop the old addresses in the short or medium time term. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Hello, Am Sonntag, 14. März 2021, 21:52:40 CET schrieb Hans-Peter Jansen:
Am Sonntag, 14. März 2021, 15:37:45 CET schrieb Christian Boltz:
[please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ]
As long as we rely on manual removal, this fight will be Don Quijoteresque..
Not really - it's more a matter of using "reply to list" instead of "reply to all". In worst case, if you use "reply to all" the mail client will additionally drag in factory@lists.o.o from the List-Reply header if the original mail was send to opensuse-factory@o.o - which is exactly what happened here. Needless to say that our mailinglist netiquette [1] also says Do not use Reply-to-all, as that forces duplicate copies of a message upon them. I'm aware that some mail clients don't support "reply to list", but even there, workarounds exist, for example - right-click the list address and pick "reply to this address" - use "reply to all" and remove all superfluous addresses (yes, I know that this is annoying and error-prone) - switch to a better mail client that supports "reply to list" ;-) (Since I already mentioned the netiquette - this discussion is off-topic here, so please only reply reply if you _really_ think you have to ;-) Regards, Christian Boltz [1] https://en.opensuse.org/openSUSE:Mailing_list_netiquette -- Offline ist so ähnlich wie tot, nur langweiliger. [Kristian Köhntopp in http://blog.koehntopp.de/archives/2948-Schoener-Wohnen-im-21.-Jahrhundert.ht...]
Christian Boltz composed on 2021-03-16 00:38 (UTC+0100):
I'm aware that some mail clients don't support "reply to list", but even there, workarounds exist, for example ... - use "reply to all" and remove all superfluous addresses (yes, I know that this is annoying and error-prone)
I don't see how it can constitute much annoyance. It's what I did for many moons before reply-to-all became a SeaMonkey Mail feature. Removing or changing From to to CC or BCC or vice versa is seriously trivial, in SeaMonkey Mail at least. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 3/15/21 1:07 AM, Christian Boltz wrote:
Hello,
[please don't send to factory@lists.o.o _and_ opensuse-factory@o.o - the mail then arrives on the ML twice :-( ]
Am Sonntag, 14. März 2021, 09:49:28 CET schrieb Axel Braun:
Am 13. März 2021 20:37:12 MEZ schrieb Jan Engelhardt:
On Saturday 2021-03-13 18:47, Alex Bihlmaier wrote:
Is there any chance to retrieve older builds?
No, only source.
...from where you could branch and build in your home project
Yes, in theory.
In practise you'll build the old source (good) against the current dependencies (libraries, compiler, ...). I'm not sure if I should call this "bad", but I'm quite sure you'll get a different result than building with the original ("old") dependencies, with the difference becoming bigger the older your sources are.
Lets go with "different" depending on what your goal is, in most cases the software should remain functionally the same if it still builds, but with the advantage it was designed to work with the current state of your system. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 13/03/2021 18.47, Alex Bihlmaier wrote:
In order to research a problem with an older build of an OBS package (syncthing - https://build.opensuse.org/package/show/network/syncthing) i am looking for older versions of this package?
Is there any chance to retrieve older builds?
https://opensuse.zq1.de/history/ keeps Factory binaries since 2020-08-01 and since syncthing is in Factory, you can find older binaries in there. If you need old Leap binaries, you need to rebuild those from source. You can find the git history of our Factory sources in https://code.opensuse.org/package/syncthing/commits/master
On Sat, Mar 13, 2021 at 06:47:20PM +0100, Alex Bihlmaier wrote:
In order to research a problem with an older build of an OBS package (syncthing - https://build.opensuse.org/package/show/network/syncthing) i am looking for older versions of this package?
Is there any chance to retrieve older builds?
Try http://download.opensuse.org/history/ https://forums.opensuse.org/showthread.php/535256-Tumbleweed-snapshots-usage... But in your usecase it may be better option to rebuild and bisec on source changes than binary versions. - Adam
participants (11)
-
Adam Majer -
Alex Bihlmaier -
Axel Braun -
Bernhard M. Wiedemann -
Carlos E. R. -
Christian Boltz -
Felix Miata -
Frank Krüger -
Hans-Peter Jansen -
Jan Engelhardt -
Simon Lees