Greg Freemyer
2014-08-27 19:33:59 UTC
All,
I've been using OBS for a couple years. I maintain numerous packages
and in one case I have about 50 packages that form a dependency tree
(no cycles, just a tree).
One of the frustrations I've had not having an easy way to know if the
top packages "Requires:" statements are met without actually
installing it.
I find that hard because on my development PC I may have the
dependencies installed but that doesn't mean they are in OBS for other
users.
I just realized I can tell at least some extent by looking at the WebUI.
In particular my last "mistake" related to plaso which I submitted to
factory without having all the dependencies in factory first.
I just created a dedicated sub-project in my home project for plaso
(python-plaso). The plaso package is at:
https://build.opensuse.org/package/show/home:gregfreemyer:libyal-plaso/python-plaso
If I click on openSUSE_Factory in the build results area I can see the
factory RPMs for plaso. I already knew that:
https://build.opensuse.org/package/binaries/home:gregfreemyer:libyal-plaso/python-plaso?repository=openSUSE_Factory
If I then click on one of the noarch RPMs, I can see the provides and
requires columns. I even knew that.
https://build.opensuse.org/package/binary/home:gregfreemyer:libyal-plaso/python-plaso?arch=i586&filename=python-plaso-1.1.0-8.1.noarch.rpm&repository=openSUSE_Factory
What I didn't know is that if I do the same thing in the devel project
(security this time), then the requires columns that have a blank in
the "provided by" column mean factory can't provide the required
package:
https://build.opensuse.org/package/binary/security/python-plaso?arch=x86_64&filename=python-plaso-1.1.0-7.1.noarch.rpm&repository=openSUSE_Factory
I submitted all 6 of the missing dependencies to factory a few hours
ago, so if there are no blanks in the provided by column you know my
SRs got accepted!
Hope that helps someone.
Greg
--
Greg Freemyer
I've been using OBS for a couple years. I maintain numerous packages
and in one case I have about 50 packages that form a dependency tree
(no cycles, just a tree).
One of the frustrations I've had not having an easy way to know if the
top packages "Requires:" statements are met without actually
installing it.
I find that hard because on my development PC I may have the
dependencies installed but that doesn't mean they are in OBS for other
users.
I just realized I can tell at least some extent by looking at the WebUI.
In particular my last "mistake" related to plaso which I submitted to
factory without having all the dependencies in factory first.
I just created a dedicated sub-project in my home project for plaso
(python-plaso). The plaso package is at:
https://build.opensuse.org/package/show/home:gregfreemyer:libyal-plaso/python-plaso
If I click on openSUSE_Factory in the build results area I can see the
factory RPMs for plaso. I already knew that:
https://build.opensuse.org/package/binaries/home:gregfreemyer:libyal-plaso/python-plaso?repository=openSUSE_Factory
If I then click on one of the noarch RPMs, I can see the provides and
requires columns. I even knew that.
https://build.opensuse.org/package/binary/home:gregfreemyer:libyal-plaso/python-plaso?arch=i586&filename=python-plaso-1.1.0-8.1.noarch.rpm&repository=openSUSE_Factory
What I didn't know is that if I do the same thing in the devel project
(security this time), then the requires columns that have a blank in
the "provided by" column mean factory can't provide the required
package:
https://build.opensuse.org/package/binary/security/python-plaso?arch=x86_64&filename=python-plaso-1.1.0-7.1.noarch.rpm&repository=openSUSE_Factory
I submitted all 6 of the missing dependencies to factory a few hours
ago, so if there are no blanks in the provided by column you know my
SRs got accepted!
Hope that helps someone.
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org
To unsubscribe, e-mail: opensuse-packaging+***@opensuse.org
To contact the owner, e-mail: opensuse-packaging+***@opensuse.org