I have boost 1.68 libs in my tumbleweed snap, and they want the license. The license looks like it should be under oss/noarch
But when I goto:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/
It only has contents up to ant-commons-net
For some reason I am not seeing the rest of the directory which could explain why it didn't download with other boost packages.
Any reason why I might not be seeing it?
Is it there?
tnx!
L A Walsh composed on 2019-04-24 15:43 (UTC-0700):
I have boost 1.68 libs in my tumbleweed snap, and they want the license. The license looks like it should be under oss/noarch
But when I goto:
It only has contents up to ant-commons-net
For some reason I am not seeing the rest of the directory which could explain why it didn't download with other boost packages.
Any reason why I might not be seeing it?
Is it there?
http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-...
* L A Walsh suse@tlinx.org [04-24-19 18:46]:
I have boost 1.68 libs in my tumbleweed snap, and they want the license. The license looks like it should be under oss/noarch
But when I goto:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/
It only has contents up to ant-commons-net
For some reason I am not seeing the rest of the directory which could explain why it didn't download with other boost packages.
Any reason why I might not be seeing it?
Is it there?
impatience, but you are outdated already: http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-... is current.
On 4/24/2019 3:57 PM, Felix Miata wrote:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-...
impatience, but you are outdated already: http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-... is current.
Well thanks, but 1.69 doesn't satisfy rpms that require 1.68, which I found, but this begs the question -- if someone wanted to reproduce a build for an rpm that wants 1.68, but 1.68 isn't in the release directory any more -- it seems that's a bit problematic as pulling in newer versions of everything might pull in unwanted changes.
Does suse keep an archive site of all the rpms that were released in tumbleweed?
It's hard to keep everything cohesive.
How many packages have their version numbers incremented, _on the average_, per release of tumbleweed?
It seems it might save on time and bandwidth to know what packages you need to update to move to a newer version of TW, no?
oi...gotta figure out why my local cache isn't as cohesive as it ought to be. Sigh.
LCP [Stasiek] https://lcp.world
On czw, Apr 25, 2019 at 9:02 AM, L A Walsh suse@tlinx.org wrote:
On 4/24/2019 3:57 PM, Felix Miata wrote:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-...
impatience, but you are outdated already:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_0-... is current.
Well thanks, but 1.69 doesn't satisfy rpms that require 1.68, which I found, but this begs the question -- if someone wanted to reproduce a build for an rpm that wants 1.68, but 1.68 isn't in the release directory any more -- it seems that's a bit problematic as pulling in newer versions of everything might pull in unwanted changes.
Does suse keep an archive site of all the rpms that were released in tumbleweed?
http://download.opensuse.org/history/
It's hard to keep everything cohesive.
How many packages have their version numbers incremented, _on the average_, per release of tumbleweed?
It seems it might save on time and bandwidth to know what packages you need to update to move to a newer version of TW, no?
oi...gotta figure out why my local cache isn't as cohesive as it ought to be. Sigh.
Op donderdag 25 april 2019 09:02:28 CEST schreef L A Walsh:
On 4/24/2019 3:57 PM, Felix Miata wrote:
http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_69_ 0-1.69.0-1.3.noarch.rpm> impatience, but you are outdated already: http://download.opensuse.org/tumbleweed/repo/oss/noarch/boost-license1_6 9_0-1.69.0-1.3.noarch.rpm> is current.
Well thanks, but 1.69 doesn't satisfy rpms that require 1.68, which I found, but this begs the question -- if someone wanted to reproduce a build for an rpm that wants 1.68, but 1.68 isn't in the release directory any more -- it seems that's a bit problematic as pulling in newer versions of everything might pull in unwanted changes.
Does suse keep an archive site of all the rpms that were released in tumbleweed?
You can install tumbleweed-cli, which allows you to move back and forward between TW released snapshots. After install run tumbleweed --help
It's hard to keep everything cohesive.
How many packages have their version numbers incremented, _on the average_, per release of tumbleweed?
It seems it might save on time and bandwidth to know what packages you need to update to move to a newer version of TW, no?
oi...gotta figure out why my local cache isn't as cohesive as it ought to be. Sigh.