search

draek / galaxium

Automatically exported from code.google.com/p/galaxium
0 stars 0 forks source link

Fedora repository doesn't work #58

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Fedora repo doesn't work,yum doesn't find galaxium package

Original issue reported on code.google.com by kheli...@gmail.com on 8 Apr 2008 at 1:55

GoogleCodeExporter commented 9 years ago 
that's because the package doesn't exist yet

galaxium is still beta, galaxium 0.7 isn't officially released yet
for now, the only way to use galaxium on fedora is building the complete 
package from
source

(fedora packages will probably be online in 2-4 weeks)

Original comment by ben.motm...@gmail.com on 8 Apr 2008 at 3:54

GoogleCodeExporter commented 9 years ago 
This isnt supposed to be for 0.7, it has nothing to do with a release. The 
repos and
packages we make are a whole other thing.

Original comment by dra...@gmail.com on 26 Apr 2008 at 10:02

GoogleCodeExporter commented 9 years ago 
None packages from ben.motmans are built... He must be blind to omit rpmbuild 
error
about missing .desktop file, he probably forgot to attach...

Original comment by jakub.ru...@gmail.com on 10 May 2008 at 9:39

GoogleCodeExporter commented 9 years ago 
have a look 2 comments up in this thread, the reason why there are no
fedora/opensuse/mandriva packages, is that I didn't upload a tarball to the 
build service

anticipating the next question, "why didn't you upload a tarball to the build
service?" ==> Galaxium 0.7 isn't released yet, I cannot package what doesn't 
exist

I am going to work on a BETA release next week, but I'm seriously considering to
remove the link from the wiki because I doubt we will receive useful bug 
reports at
this point from people using a precompiled package

Original comment by ben.motm...@gmail.com on 10 May 2008 at 10:18

GoogleCodeExporter commented 9 years ago 
I created packages based on today's svn checkout, i586 packages are building
correctly, but for some reason the mono compiler craps out on the x86_64 
packages

just to be clear, this package hasn't been tested yet, and it packages a SVN
checkout, so it is not some kind of official release

Original comment by ben.motm...@gmail.com on 25 May 2008 at 11:54

GoogleCodeExporter commented 9 years ago 
I tried your packages @ openSUSE. Galaxium works like charm but I don't have 
time to
investigate on your packages quality.

Original comment by jakub.ru...@gmail.com on 27 May 2008 at 7:26

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by dra...@gmail.com on 14 Jun 2008 at 12:27

GoogleCodeExporter commented 9 years ago 
Again, these packaging issues aren't going to be delt with for a bit still 
until the
team is all back and we get the ball rolling on OBS and PPA.

Original comment by dra...@gmail.com on 23 May 2009 at 3:03

GoogleCodeExporter commented 9 years ago 
Please, don't use "invalid". This issue (as well as the one with Hardy) is very 
valid
and was even worked on.

Original comment by Zarevucky.Jiri on 23 May 2009 at 8:37

GoogleCodeExporter commented 9 years ago 
Its not a software issue which is what I'm using the issues list for. If there 
needs
to be discussion about packages etc, it should go to the groups.

I want to keep this issues list organized with software related issues.

Original comment by dra...@gmail.com on 23 May 2009 at 1:44

GoogleCodeExporter commented 9 years ago 
Hmm... I think issues list is for all the problems that are on our side. Groups 
is
for user-side problems, questions, etc. Am I wrong? I believe it generally 
works that
way in most projects.

Original comment by Zarevucky.Jiri on 23 May 2009 at 5:18

GoogleCodeExporter commented 9 years ago 
I dont think its a matter of our side/their side, its just a matter of 
organization.
I would rather keep the issues list 100% application/code related, thats really 
all
it boils down to for me.

Any other issues that are not application/code specific, can go to the groups 
for
discussion.

Original comment by dra...@gmail.com on 23 May 2009 at 6:39

GoogleCodeExporter commented 9 years ago 
Maybe, but users will keep posting repository problem to the issue list, 
regardless
of what your organization is.. :-P

Original comment by Zarevucky.Jiri on 23 May 2009 at 6:42

GoogleCodeExporter commented 9 years ago 
yeah you are right :P

Original comment by dra...@gmail.com on 24 May 2009 at 2:21