Hello All,
I'm running a private instance and I'd like to enable networking on my
workers so they can build some java apps, via maven, which need to
download pom's/war's from the net. I ask google but he wasn't much
help so I'm hoping someone here can help;-)
How can I go about doing this?
--
Later,
Darin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Not sure what the correct list is to report mirror issues, but
http://tux.rainside.sk/opensuse/ is empty.
laf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi.
There is a ghost package in my OBS home project. I'm using the web interface,
not the command line one. If you go to
https://build.opensuse.org/project/show/home:jcsl:LXDE
you can see the real 10 packages in the Packages box on left side, but if you
look in the Build Results box, on the right side, you see 11 next to the
"succeeded" text. If you then click the succeeded link you find the
pcmanfm-1.2.0-beta1 package, and if you click on its link you get a Package
"pcmanfm-1.2.0-beta1" not found in project "home:jcsl:LXDE", as expected. It
even appears in the scheduled and building states when something I'm building
triggers its build (I don't know how can this be).
Any hints?
Greetings.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On openSUSE 13.1 with repo tools [1]
There's a problem with
nothing provide python-packaging can't install obs-service-set_version-0.5.0-44.1-noarch
A missing link or aggregate for 13.1 ?
[1] repositories/openSUSE:/Tools/openSUSE_13.1
An idea how to fix it?
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member & Board, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hej hej!
Sometime between July 19 and today, July 23, the building of deb
packages for Debian and Ubuntu broke in the public instance of OBS, at
least for the generated / munged Debian control files.
Here's a log of a new, broken build:
<https://build.opensuse.org/build/home:DrMcCoy:xoreos/Debian_8.0/x86_64/xore…>
and a log of an old, working build:
<https://build.opensuse.org/build/home:DrMcCoy:xoreos/Debian_8.0/i586/xoreos…>
The broken build worked previously, but after hitting "Trigger
rebuild", it fails. Nothing was changed in that package.
The relevant error message is this:
| dpkg-genchanges -v~0 >../xoreos_0.0.1_amd64.changes
| parsechangelog/debian: warning: 'since' option specifies non-existing version
| parsechangelog/debian: warning: use newest entry that is earlier than the one specified
| parsechangelog/debian: error: parsechangelog/debian: error: ~0 is not a valid version
|
| dpkg-genchanges: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255
| dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255
while previously, the dpkg-genchanges call was this:
| dpkg-genchanges >../xoreos_0.0.1_i386.changes
I.e. something now sets -v ($since in dpkg-buildpackage) to "~0". I
can't see in the logs where that's coming from, so I guess that's the
OBS scripts doing that? Or am I missing or forgetting something in the
source files, that now somehow shows?
Thanks,
Sven
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Debian builds are failing due to a missing DEBVERSION environment
variable, which was introduced by openSUSE/obs-build#175 [1]. This
patch should have included some sort of backwards compatibility via a
conditional check for DEBVERSION being nonempty. I would gladly
submit a patch for this if I had some sort of easy way to test the
patch, which I do not.
Also, how does one go about setting the DEBVERSION variable for OBS?
Is this even possible?
Relevant log output:
[ 40s] dpkg-deb: building package `bitlbee-facebook' in
`../bitlbee-facebook_17~f55536c_i386.deb'.
[ 40s] dpkg-genchanges -v~0 >../bitlbee-facebook_17~f55536c_i386.changes
[ 40s] parsechangelog/debian: warning: 'since' option specifies
non-existing version
[ 40s] parsechangelog/debian: warning: use newest entry that is
earlier than the one specified
[ 40s] parsechangelog/debian: error: parsechangelog/debian: error:
~0 is not a valid version
[ 40s]
[ 40s] dpkg-genchanges: error: changelog parser
/usr/lib/dpkg/parsechangelog/debian gave error exit status 255
[ 40s] dpkg-buildpackage: error: dpkg-genchanges gave error exit status 255
James
[1] https://github.com/openSUSE/obs-build/pull/175
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
By accident I did a commit with 'Release: <largenumber>' in a rpm spec
file. The prjconf has 'Release: <CI_CNT>.string.<B_CNT>', but that does
most likely not matter.
What happens now is that CI_CNT is now based on <largenumber> instead of
the single digit checkin count of the pkg.
How does one reset CI_CNT? Doing a new checkin with "Release: 1' does
not help.
Olaf
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
