If we move or copy a package from one project to another, what happens
to the release number?
I suppose, it starts to count from the beginning. Is that correct?
This is a problem if I adjust the installation source for a moved
package, and the package might then never be updated until the release
number is higher again.
Here is such a case:
Installed Packages
zsh.i586 4.3.2-10.1 installed
Available Packages
zsh.i586 4.3.2-3.1 shells
I would like to see a way to keep this intact over the move (or
respectively, copy the starting release tag).
Regards,
Peter
--
SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo:
Research & Development A malevolent monster (not true?);
Some mischief microbic;
What makes someone phobic;
The work one does not want to do.
From: Chris Young (The Omnificent English Dictionary In Limerick Form)
Hello,
I'm using SLED 10 (Novell has recently offered me a one-year
subscription activation), openSUSE 10.1, openSUSE 10.2 beta and openSUSE
Factory. I'm a huge fan of SUSE Linux distributions (I write a lof of
SUSE howtos on my french blog) and I'm used to build my own packages for
my own needs and friends.
Well, I've made some packages for SLED 10 (F-Spot 0.2.2, banshee 0.11
plugins, some Python libraries and Jokosher) but as my hosting provider
is really unstable (my hosting provider is my Internet provider, aka
free.fr, it's a free hosting with often server troubles), it's a pain to
maintain and share my packages. So, I recently remove my personal
repository and I was waiting for a better solution. I think Build
Service would be the best one.
Well, if it's possible, I would be glad to have a Build Service account.
But if it's not possible (for any reasons), I will find another solution
to maintain and share my packages.
I post this message on this mailing list because I already sent a
request on http://build.opensuse.org but I didn't receive any answer, so
I don't know if it's the correct process to request an account. Excuse
me if this is not :/
In the positive case, I would like to use the name "gfabio" for my
repository project, so home:gfabio.
Thanks in advance for your answer.
Regards,
Gilles
--
Gilles Fabio aka "Play"
Weblog : http://gilles.fabio.free.fr/blog
OpenPGP : 320F31F8 (pgp.mit.edu)
Sent from : SUSE Linux Enterprise Desktop 10
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Am Wednesday 08 November 2006 16:03 schrieb Dominique Leuenberger:
> >>> Reply on 08-11-2006 17:02:11 <<<> Am Thursday 19 October 2006 13:06
>
> schrieb Dominique Leuenberger:
> > We discussed to extend yum repos to support links to other repos as
> > well.
> > This means you add the amarok4 repo for example and this implicit
>
> adds
>
> > also
> > the KDE4 repo. When you remove amarok4 repo, the KDE4 repo disappears
>
> as
>
> > well.
> > But this would be an extension to the current yum/rpm-md format
>
> which
>
> > needs
> > to be discussed (and proposed in a valid way) on the yum ml.
> >
> > I would be happy if someone could spend some time on this issue :)
> >
> > > don't misunderstand me: I like the split in this cattegory, and I
> >
> > think
> >
> > > it's important, but it would also be very interesting to have the
> > > possibility to subscribe only to one Repository (technically, it
>
> IS
>
> > > possible... remains just the question, if it can be implemented on
> >
> > the
> >
> > > Build Service).
>
> Adrian, do you know if there is already something going on in this
> direction?
I do not think so.
> If not, I could try to work out something on the yum ml, trying to feel
> if such a thing would be completely new idea or how far something alike
> is already developed there.
That would be great :)
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
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
Hi,
We are having problems getting a package to build - looks like dependncy
problems. It is a java based plugin in tomcat for AppArmor. The package
tomcat_apparmor is in factory but we would like to make a development version
available via the build service. Does the buildservice expand
java2-devel-packages to fill the required dependencies?
Here is the link showing the build problems:
http://build.opensuse.org/package/show?package=tomcat_apparmor&project=home…
Thanks,
dominic
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On Thu, Nov 09, 2006 at 08:13:28AM +0100, Dominique Leuenberger wrote:
> >>> Reply on 09-11-2006 9:11:55 <<<> On Wed, Nov 08, 2006 at 02:45:10PM
> +0100, Dominique Leuenberger wrote:
> > > Hi everybody,
> > >
> > > I just wanted to tell you that in games:strategy:turn-based I
> started
> > > to maintain the game
> > > 'Mars, Land of no Mercy'.
> > >
> > > The game is in very early development stage but progress is being
> > made.
> > > If you think it's to early to put it in this prominent place, I
> can
> > > remove it again and currenlty only maintain it in my home.
> > >
> > > Give it a try, and post some feedback.
> >
> > # mars
> > [ERROR] Image [ERROR]
> > Couldn't open data/img/mars1_800.png
> >
> > Sometimes you get a Sig11 instead. It seems to work when you chdir
> to
> > /usr/share/games/mars first.
> >
>
> Stefan,
>
> that's a knwon 'feature' for 0.2.0 (I wrote it in the changelog. Is
> there a more prominent place?)
> Discussion with the upstream team revealed, that the next version
> (probably 0.3.0) should have this fixed so I can do a start menu item
> without problem.
>
> For the time being, I could step around this by creating a shell
> script, that starts Mars.
Yes, this would be ok.
Thanks,
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
------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Stefan,
>>> Reply on 09-11-2006 9:11:55 <<<> On Wed, Nov 08, 2006 at 02:45:10PM
+0100, Dominique Leuenberger wrote:
> > Hi everybody,
> >
> > I just wanted to tell you that in games:strategy:turn-based I
started
> > to maintain the game
> > 'Mars, Land of no Mercy'.
> >
> > The game is in very early development stage but progress is being
> made.
> > If you think it's to early to put it in this prominent place, I
can
> > remove it again and currenlty only maintain it in my home.
> >
> > Give it a try, and post some feedback.
>
> # mars
> [ERROR] Image [ERROR]
> Couldn't open data/img/mars1_800.png
>
> Sometimes you get a Sig11 instead. It seems to work when you chdir
to
> /usr/share/games/mars first.
>
Stefan,
that's a knwon 'feature' for 0.2.0 (I wrote it in the changelog. Is
there a more prominent place?)
Discussion with the upstream team revealed, that the next version
(probably 0.3.0) should have this fixed so I can do a start menu item
without problem.
For the time being, I could step around this by creating a shell
script, that starts Mars.
What do you think about?
Dominique
Hi everybody,
I just wanted to tell you that in games:strategy:turn-based I started
to maintain the game
'Mars, Land of no Mercy'.
The game is in very early development stage but progress is being made.
If you think it's to early to put it in this prominent place, I can
remove it again and currenlty only maintain it in my home.
Give it a try, and post some feedback.
Regards,
Dominique
>>> Reply on 08-11-2006 17:02:11 <<<> Am Thursday 19 October 2006 13:06
schrieb Dominique Leuenberger:
> We discussed to extend yum repos to support links to other repos as
> well.
> This means you add the amarok4 repo for example and this implicit
adds
> also
> the KDE4 repo. When you remove amarok4 repo, the KDE4 repo disappears
as
>
> well.
> But this would be an extension to the current yum/rpm-md format
which
> needs
> to be discussed (and proposed in a valid way) on the yum ml.
>
> I would be happy if someone could spend some time on this issue :)
>
> > don't misunderstand me: I like the split in this cattegory, and I
> think
> > it's important, but it would also be very interesting to have the
> > possibility to subscribe only to one Repository (technically, it
IS
> > possible... remains just the question, if it can be implemented on
> the
> > Build Service).
Adrian, do you know if there is already something going on in this
direction?
If not, I could try to work out something on the yum ml, trying to feel
if such a thing would be completely new idea or how far something alike
is already developed there.
Regards,
Dominique
Hi everybody,
I just tried to add Mandriva 2005 and Fedora 5 Extra as available
repositories to my home:dimstar repository.
For Mandriva, it seems almost all packages fail with the same error
message:
installing bootloader-utils-1.9-3mdk
installing kernel-i586-up-1GB-2.4.28.0.rc1.5mdk-1-1mdk
Cannot find a boot loader installed
error: %post(kernel-i586-up-1GB-2.4.28.0.rc1.5mdk-1-1mdk.i586)
scriptlet failed, exit status 21
Is this a known bug/'feature' ? Or worth a bug entry? Or are other
platforms than SuSE Linux not supported at all?
If they are: Can we also get support for later versions inside? Like
Madriva 2007 and Fedora 6? At the moment we can only build against old
distros in this case.
Regards,
Dominique
Hey,
I've noticed this a few times now: I'll commit an update to a package
(via osc if that matters) and then go to the website to watch the build
progress for that package. If it happens to be a point where the
buildservice is relatively idle, the package will usually have started
rebuilding against all of the repositories I've assigned.
On multiple occasions I've gone to view a build log for the package,
catching it in progress. I'll watch it continue building to completion,
only to discover at the end that it just rebuilt the *previous* version
of the package, If I then go back to the package status page, the package
will have had a new build kicked off for the same repository target;
returning to the log, it will indeed be a build for the newly committed
version of this package.
Is this known behavior? Expected behavior? Please let me know if there's
anything in the above that I need to clarify.
Thanks.
--
Steve Beattie
SUSE Labs, Novell Inc.
<sbeattie(a)suse.de>
http://NxNW.org/~steve/