Hi,
something I constantly run into when using webui is the fact that
there is no warning / message that there is an older SR pending for a
package with the option to superseed the previous one (as osc does).
This typically leaves to 2 SRs against one package where in worst case
the target project might end up accepting the wrong one (in case the
submitter forgets to retract the old request).
Are there any plans to implement this on webui as well?
Dominique
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
What is the difference between Support and Keep?
Like, let's say I have a package FOO that I'd like to always be
installed in the build environment, *if* it is available. If it is not
available, block all other builds until it *is* available, but do not
block FOO itself. How do I do that?
Is there a way to configure a project with more than one repository
with different configurations (such as, when using repo A, substitute
foo for bar)?
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi y'all,
as it occured several times already, there seem to be some misconceptions
about source services for the Build Service. Recently, it seemed to became
fashionable to replace each and every package tarball with a download service
pointing to some URL. As by most commit messages, people seem to be believe
that some magic update logic will happen once upstream releases a new tarball.
Just to make this clear, this won't happen!
The only thing that changes is that the source tarball is not stored alongside
your spec but downloaded on-demand instead (speak, with every rebuild). And it
is not (yet) cached and you still have to update stuff (by changing that URL).
As a packager, you have to download the tarball anyways because you want to
look at new documentation files or update your local patches.
However, this may make sense if you use it together with some more source
services (like re-packaging or checksum checks), but I consider it unfriendly
to change someone else's packages to use source services without asking.
Please don't do that.
--
Mit freundlichen Grüßen,
Sascha Peilicke
http://saschpe.wordpress.com
Hi, I have this branch of the pgadmin3 project:
https://build.opensuse.org/package/show?package=pgadmin3&project=home%3Akla…
It was ok, until recently there seems to have been a conflicting
change in the parent project since the status changed to broken:
conflict in pgadmin3.spec
I have no access to the osc tool currently, only the web ui - how can
I resolve the conflict from there? I can't even get a description of
the conflicting changes.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi guys.
Someone changed something between 2011-03-02 17:11:55 and 2011-02-23 19:38:19
that broke all my deb builds for one package.
Package in question: security:OpenVAS:UNSTABLE:v4/libopenvas
Why it wasn't me who fucked it up:
1. As you can see the latest version (4.0.2) is on d.o.o so it must have been
build properly at one point in time.
2. Now it is broken albeight I didn't change a thing (config or source).
3. If you check out an older revision - that built fine - you'll notice that
it is broken too now (I tried with r11-9).
Please have a look at this.
regards,
Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Will someone create it?
--
Adam "etamPL" Mizerski
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I know it's been mentioned before, but I seem to have lost the email about it...
Can anyone post the patch for it/how to use it again?
--
later, Robert Xu
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I have a couple of questions on local-obs sync from remote obs (I
have a project on local obs linked to a project on remote obs).
First: sometimes the scheduler gets stuck for quite a while, and from
the logs it seems that it is downloading from the remote obs. If
there's a lot to download this can take > 20 minutes. During this
time, all job processing seems to halt. Is that the case and if so, is
there a way to avoid it? All of the local-only projects get stuck
along, when they don't depend at all on what's being downloaded.
2nd: I see the same 'getting data for project' logs in the different
schedulers (from remote obs) - is it cached locally on the 1st
download, or does each sched re-download the same version of the same
pkgs?
The only way I see right now to avoid this problem is to setup 2 local
obs, with one acting effectively as a cache for the remote downloads.
I'm hoping there's a less draconian solution...
Thanks,
Christian.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Tuesday 15 March 2011
Hello.
In package > Users linked icon "Inherited from project" is missing.
Link to icon is
https://static.opensuse.org/hosts/build2.o.o/images/icons/project.png
Not Found
The requested URL /hosts/build2.o.o/images/icons/project.png was not
found on this server.
--
WBR
Kyrill
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
please comment on this. I personally run often into a osc CLI inconsitency
that the list/ls comand is using -R for revision listings, while other
commands like diff, rdiff, submitrequest are using -r for revision.
-r for list command is "repository" which is usually ignored on source listings.
I like to proposed change switch -r and -R in list command to have this consistent.
In addition to that we could maybe do a backward compatibly check that when
-r and -b is used for binary listings that -r is still used as repository parameter.
any comments on this ?
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org