Hi,
the webclient can now delete packages for real. We decided to delete the
remove links from the project overview page, as it is an action that is not
usually done often. The remove link can be found on the package detail page,
beneath the edit link on top of the page.
Have fun,
--
Andreas Bauer - Novell - SUSE Internal Tools
Could I request the admins to please remove the following packages
from Project Compiz-Quinn:
XglXorg7
gcompizthemer-themes
wncktest
gcompizthemer
libwncktest
Compiz-Quinn (with capital C and Q, not compiz-quinn)
And all the packages from home:cyberorg
Thanks
-J
Hi all
I am trying to build Xgl with Xinerama patch. I have been successful
in creating a package built against Xorg7 repository (standard/Xorg7).
The package is available here:
http://software.opensuse.org/download/Compiz-Quinn/standard/i586/
However building for 10.1 and Factory fails as I have to remove
xorg-x11-compat70-devel from Buildrequires.
How do I specify buildrequires per repository? I dont know what goes
in place of ifrepository.
something like
%ifrepository standard
Buildrequires: xyz
%endif
%ifrepository 10.1
Buildrequires: xorg-x11-compat70-devel
%endif
Thanks
Jigish
Hi
Could the buildservice team please delete the following removed
packages (which are now blocking other new packages, which should be
built) from project "home:sndirsch"?
FreeNX
NX
avrdude
freeglut
glest
glest-data
joy2key
numlockx
sisctrl
x11-input-synaptics
xsnow
knx
nvtv
selectio
tiny-nvidia-installer
tuxpaint
xorg-x11-6_8_1
xorg-x11-6_8_2
qfix
torcs
I can't delete them. Neither via the frontend nor with osc.
Best regards,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
------------------------------------------------------
Hi builders,
we changed the code so that a package exists in a project iff
there is a meta file (i.e. package.xml exists). The former
implementation was that a package existed iff it was in the
package list in the project's meta file.
Because of this you may experience that some packages that
you thought deleted show up again. Just delete them again.
Sorry for the inconvenience,
Michael.
--
Michael Schroeder mls(a)suse.de
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
Hi,
we will update the backend/database server to SLES10 today, which will resolve
the problems I had with the API update yesterday. The buildservice will be
unavailable from 15:00 CEST (13:00 UTC) until it's done.
--
Andreas Bauer - Novell - SUSE Internal Tools
Hi
I wonder what has happened to the Build monitor for the projects?
Could we have this feature again? I consider it being pretty helpful.
I tried "Add packages/repositories to enable the build monitor", but
this didn't help. :-(
Best regards,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
------------------------------------------------------
Am Tuesday 08 August 2006 08:45 schrieb Jigish Gohil:
> On 8/8/06, Adrian Schröter <adrian(a)suse.de> wrote:
> > Am Tuesday 08 August 2006 08:10 schrieb Jigish Gohil:
> >
> >
> > %if %suse_version = 1001
> > Buildrequires: xorg-x11-compat70-devel
> > %else
> > Buildrequires: xyz
> > %endif
>
> Thanks Adrian
>
> How do we find out what is suse_version for any repository? For
> example what would be the suse_version of Factory and Xorg7
> repositories?
There is no easy interface for that yet. You can't destinguish between Factory
and xorg7 for Factory in that way. Except the xorg7 project defines a macro
(which would be possible to setup).
The url to get the build information would be
api.opensuse.org/rpm/<project>/<repository>/<arch>/<package>/buildinfo
--
Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian(a)suse.de
Hi,
the opensuse API will get an update today at 16:00 UTC (18:00 CEST).
The main reason for the update is the setup of a SQL database for storing the
metadata of projects and packages. Estimated downtime is 1-2 hours.
--
Andreas Bauer - Novell - SUSE Internal Tools