Hi,
I was just wondering what people do to cleanup the local osc packagecache?
Especially for openSUSE:Factory one will end up with quite some versions
of the same package over the years since osc is currently not wiping old
versions.
IMHO osc should do that since it knows best when a newer version has to
be downloaded.
Thanks,
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On Wed, 2008-08-27 at 11:31 +0200, Wolfgang Rosenauer wrote:
> Hi,
>
> I was just wondering what people do to cleanup the local osc packagecache?
> Especially for openSUSE:Factory one will end up with quite some versions
> of the same package over the years since osc is currently not wiping old
> versions.
> IMHO osc should do that since it knows best when a newer version has to
> be downloaded.
I myself clean up that cache once in a while manually... having a 10mbit
line allows me to even wipe files I would still need and redownload them
(anyhow, most likely when I start osc next on a Factory target, have of
the distro is changed).
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I think the following is a bug:
osc build ... mozilla-xulrunner191
Getting buildinfo from server
buildinfo is broken... it says:
expansion error: nothing provides mozilla-xulrunner191
Yeah, nothing provides mozilla-xulrunner191 since I'm just going to
build it?
Probably related to the new PreReq handling since that package contains
a subpackage which PreReqs %{name}?
This also probably only happens as long as there is no built package
available in OBS already since there were no sources committed at that
point.
So I just committed what probably doesn't build at all and within OBS it
starts building at least and doesn't fail with unsatisfied build
requirements.
Thanks,
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
I use _link in one project and would like to ensure, that the package
version+revision of the resulting packes is always at least 1 higher than
the original.
Is there a way for this?
E.G. By adding 100 to the revision automatically in the project
configuration or somethink like this.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
After a long period of inactivity, I have just finally made another release of
Yabsc.
Packages are available at http://software.opensuse.org/search?q=yabsc
Screenshots and source are available at http://www.funktronics.ca/yabsc/
Changes include:
* Restructured models and views to be more efficient
* Added a submit request view (Thanks to Dirk Mueller <dmueller(a)suse.de>)
* Added a scheduled packages tab to the result view
* Resulting package binaries can be viewed and downloaded
* Projects can be added to and removed from the watchlist by right-clicking
them in the project list
* Rebuilds can now be triggered directly in the result view by right-
clicking on the package, or a specific result
* Can now view running build logs in the worker tab
* Worker jobs running for longer than 1 hour are colour-coded like in the
webclient
* Added filter options for worker lists
* Displays number of packages in the wait queue for each arch in the status
bar
Still on the TODO (due to technical limitations or lack of talent on my part):
- Create application icon and desktop file
- Make packagename column persistent when scrolling horizontally
- Show number of watched packages in the wait queue (requires api support)
As always, I am happy to take suggestions, feature requests, and patches.
--
James Oakley
jfunk(a)funktronics.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all!
I would like to announce that we successfully built Xfce 4.6 Alpha
(4.5.80) in openSUSE BuildService. Packages are prepared in
X11:xfce:unstable project[1] and could be downloaded from web
repositories[2].
However, please be aware. These packages haven't been tested, the only
guarantee I could give you is that they can be built :) I also do not
recommend installing these packages over Xfce 4.4 packages (yet). Any
bug reports not related to packaging should be passed to Xfce bugzilla[3].
Thanks you in advance for your testing efforts :)
[1] https://build.opensuse.org/project/show?project=X11:xfce:unstable
(login reqired)
[2] http://download.opensuse.org/repositories/X11:/xfce:/unstable/
[3] http://bugzilla.xfce.org/
--
Best Regards / S pozdravom,
Pavol RUSNAK SUSE LINUX, s.r.o
Package Maintainer Lihovarska 1060/12
PGP 0xA6917144 19000 Praha 9, CR
prusnak[at]suse.cz http://www.suse.cz
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
added ExcludeArch: x86_64 to a package that should not build on x86_64.
OBS starts building and then recognizes that x86_64 is excluded.
OBS shouldn't start building such packages.
Cheers
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I recently got some GNOME:Factory super powers, and while reviewing a
bunch of submission, it appeared to me that most of the time, what's
wrong with them is just some tiny detail in the .changes entry.
It takes quite some time to decline/delete the submission and ask the
submitter to fix this, especially since I could fix things myself really
quickly.
Is there an easy way to handle this kind of case? Ideally, I'd just want
to have an editor being launched with the .changes entry and to fix it
there, then accept the submission.
Thanks,
Vincent
--
Les gens heureux ne sont pas pressés.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello OBS users,
some days before I started with my first project at the OBS
(https://build.opensuse.org/project/show?project=home%3Adaswaldhorn). The
package was build successful, but I get some warnings in the build log. Here
is one:
-----------------------------------------------------
RPMLINT report:
===============
nted.i586: W: dir-or-file-in-usr-local /usr/local/bin/nted
...
[all other files of the package]
...
A file in the package is located in /usr/local. It's not permitted for
packages to install files in this directory.
-----------------------------------------------------
What can I do to avoid this warning? I had a look to
http://en.opensuse.org/Packaging/RpmLint but there I don't find this warning.
Greetings and thanks, Carsten
--
Hier ist mein öffentlicher GPG-Schlüssel:
http://daswaldhorn.funpic.de/gpg.html
=========================================
www.stopptdievorratsdatenspeicherung.de
Hi, currently I am working on upstream integration in BuildService. I
have first patch for OSC. If you want to, you can take a look. If you
have any related ideas, feel free to reply.
For make this totally work, we also need to extend server backend of
buildservice... I am thinking about some special "upstream scheduler"
which have information about all _upstream files and trying "svn co"
(or offcourse similar command for other supported SCM) which are
compared with previous release numbers (stored "somewhere" :-) ) and
if they are different new tarball are created and changes are
commited. Do you have better idea how solve this problem?
Yaloki:
This can be also used for our following OBS migration, because
upstream integration support http downloads too... :-)
--
S pozdravem / Best regards
Marek Stopka
Official openSUSE community member
Kontakty / Contacts
Mobil/Cell phone: 774 59 79 40
E-mail: mstopka(a)opensuse.org
WEB: www.m4r3k.org