Please push "ocaml-rdf-0.4-3.mga3"
the docs was not provided in the previous mkrel
--
Hi,
is there a package providing the command 'pandoc' ?
it seems to be something supposed to produce .pdf from .md files:
pandoc somedoc.md -o somedoc.pdf
--
Cheers
Hi D.
I would suggest providing SFML 2.0 for Mageia 3.
SFML 2.0 is not "officially" released yet, but it's only because the
upstream want to polish the web site before it. There is a very high
probability that the current git version will be the 2.0 release. And
anyway it's been a while that the S
2013/3/10, AL13N :
>> If you don't know just don't delete anything, just provide what the
>> install script did installed.
>> Anyway if there is something installed (by error) it won't have bad
>> effects on the real parts of the lib.
>
> in any case, i'm asking because we do have a policy of remov
> > ocaml-xen should be split in ocaml-xen and ocaml-xen-devel, (2013-03-04)
[...]
> what kind of filenames should be in -devel and which in regular package?
main package:
- .cma .cmi .cmo .cmxs .so META .so.owner
(and README, LICENSE, etc...)
devel package:
- .a .cmxa .cmx .o .mli .ml
(and docum
2012/11/28, Thierry Vignaud :
> On 28 November 2012 21:35, Florent Monnier
> wrote:
>> but maybe rpm is my friend and I'm just not aware of it.
>>
>> Is there an rpm command line option to get the list of the dependents
>> of a given lib?
>
> eg for gl
>> In case that's bad, I'm wondering how I should handle this.
>> - I can just icrem the mkrel of all ocaml libs.
>> (I can write the script to do this in 5 minutes.)
>>
>
> That's normally what happends when deps are updated (for example several
> libs has this effect)
>
> The dependent packages s
2012/11/28, Thomas Backlund :
> Florent Monnier skrev 28.11.2012 20:39:
>> 2012/11/28, Thierry Vignaud :
>>> On 28 November 2012 15:44, blue_prawn
>>> wrote:
>>>> blue_prawn 0.3-5.mga3:
>>>> + Revision: 322631
>>>> - no change, only
2012/11/28, Thierry Vignaud :
> On 28 November 2012 15:44, blue_prawn
> wrote:
>> blue_prawn 0.3-5.mga3:
>> + Revision: 322631
>> - no change, only a rebuild
>
> Please tell why you rebuild
> eg: "rebuild for new ocaml" or whatever instead of "no change..."
malo (other ocaml packager) suggests m
2012/11/26, Joseph Wang :
[...]
> I suppose it would help if someone tries to "sell" me Mageia. What is
> Mageia, and why should I volunteer to work on it?
[...]
Hello,
I won't tell you that you should be a volunteer to Mageia. You should
volunteer to the project that you like, that matches your
2012/11/26, Joseph Wang :
[...]
> So what do you want me to do?
I just discovered your problem while reading your email and its answers.
I'm also a volunteer just like you.
Not for Mageia but in other project I also did some work that have
never been accepted upstream. So I do understand that this
thank you!
2012/10/1, nicolas vigier :
> On Mon, 01 Oct 2012, Florent Monnier wrote:
>
>> 2012/10/1, nicolas vigier :
>> > On Mon, 01 Oct 2012, Florent Monnier wrote:
>> [...]
>> >> I probably not used the correct scheme to add the "beta" part.
&g
2012/10/1, nicolas vigier :
> On Mon, 01 Oct 2012, Florent Monnier wrote:
[...]
>> I probably not used the correct scheme to add the "beta" part.
>> But now how can I fix this ?
>
> If the beta package was only available in cauldron and not part of a
> stabl
Hi,
I have this error message with 'mgarepo submit' :
Submission errors, aborting:
- mascot-1.0-5.mga3:
- Current or newer revision(s) already exists in core/release for
cauldron: 1.0beta-4.mga3
the previous version was 1.0beta, now is 1.0.
I probably not used the correct scheme to add the "be
Hello,
We have updated the ocaml compiler to its last version, but an error
made that some ocaml libraries don't pass the build system, here is an
example:
http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20121001102816.blue_prawn.valstar.13592/
I see in this log that it uses th
Maybe we could make possible to put a package in two different groups.
So in the .spec file we could have more than one Group: field.
In .desktop files it is already possible to put a software in several
categories.
2012/9/30, Olav Vitters :
> On Wed, Sep 26, 2012 at 10:00:04PM +0100, Pierre-Malo
2012/9/29, Thierry Vignaud :
>> It seems there is a problem on the build system.
>
> There's not
[...]
>> RPM build errors:
>> File not found by glob:
>> /home/iurt/rpm/BUILDROOT/ocaml-findlib-1.3.3-4.mga3.x86_64/usr/bin/*
>
> Hint: compare _paths_ ...
Indeed, I was not thinking at this kind
The problem was not at all from the build system, but from the .spec file.
Sorry for the noise.
--
Le vendredi 28 septembre 2012 21:03:10, vous avez écrit :
> Hello,
>
> It seems there is a problem on the build system.
>
> This package should produce /usr/bin/ocamlfind
> but it seems that a tool
Le mercredi 06 juin 2012 11:09:48, Thierry Vignaud a écrit :
> On 2 June 2012 18:42, blue_prawn wrote:
> > blue_prawn 5.2.0-1.mga3:
> > + Revision: 253448
> > - sync tarball lua-5.2.0.tar.gz
> > - update to last version lua-5.2.0
>
> Please introduce back lua-5.1 as lua51 (the same way we have l
Le samedi 02 juin 2012 15:53:16, vous avez écrit :
> Le samedi 02 juin 2012 15:18:07, Sander Lepik a écrit :
> > 02.06.2012 15:57, Florent Monnier kirjutas:
> > > What is the equivalent with mgarepo ?
> >
> > I think you should read the full policy first:
Le samedi 02 juin 2012 15:18:07, Sander Lepik a écrit :
> 02.06.2012 15:57, Florent Monnier kirjutas:
> > What is the equivalent with mgarepo ?
>
> I think you should read the full policy first:
> https://wiki.mageia.org/en/Updates_policy
Yes, I've read this yet but it
Hi,
I've found and fixed a bug in one package.
With mdvsys the process to provide a bugfix to the users was:
mdvsys co --distribution 2010.1 $PKG
# work on the package & add/update the subrel
# add a line "%define subrel 1" before %mkrel (the first one is 1, not 0)
mdvsys ci -m "description of t
Le mercredi 02 mai 2012 00:21:06, nicolas vigier a écrit :
> Hello,
>
> The following list of packages are on the svn in the cauldron directory,
> but are not in the packages repository. This should be packages that
> have been renamed, obsoleted, or imported but never submitted. I plan
> to move
Le mercredi 02 mai 2012 00:21:06, nicolas vigier a écrit :
> Hello,
>
> The following list of packages are on the svn in the cauldron directory,
> but are not in the packages repository. This should be packages that
> have been renamed, obsoleted, or imported but never submitted. I plan
> to move
Hi,
I have a package that installs a file /usr/share/texmf/ls-R
This file exists yet, so what should I do with this file ?
--
Thanks
Le samedi 07 janvier 2012 14:53:59, vous avez écrit :
> Le samedi 07 janvier 2012 13:58:05, Luc Menut a écrit :
> > Le 07/01/2012 13:23, Florent Monnier a écrit :
> > > Hi,
> > >
> > > In Mandriva I was using this command to make proper attri
Hi,
I have a package with 2 patches, each modifying one line that is in the
context of the other patch. So the second one that is applied is rejected.
I would like to know what is the correct way to handle this?
Should the context of the second one correspond to the modified version by the
fir
Le samedi 07 janvier 2012 13:58:05, Luc Menut a écrit :
> Le 07/01/2012 13:23, Florent Monnier a écrit :
> > Hi,
> >
> > In Mandriva I was using this command to make proper attribution of
> > imported .spec files:
> >
> > $ mdvsys import foo.src.rpm --m
Hi,
In Mandriva I was using this command to make proper attribution of imported
.spec files:
$ mdvsys import foo.src.rpm --message 'this spec file is imported from Fedora
where it was written by X'
I'm trying to make the equivalent with this command:
$ mgarepo putsrpm -m "this spec file is im
Le vendredi 04 février 2011 17:49:39, Maarten Vanraes a écrit :
> Op vrijdag 04 februari 2011 17:16:09 schreef Florent Monnier:
> > Hi,
> > I was (or I still am?) maintainer for these packages:
> > http://maint.mandriva.com/listpkgs.php?owner=105
> > I have not read the
Hi,
I was (or I still am?) maintainer for these packages:
http://maint.mandriva.com/listpkgs.php?owner=105
I have not read the 5000 mails of the lists yet,
but I have seen the occurrence of "buildsystem",
so my question is should I join the team now to
provide the equivalent packages, or should I w
31 matches
Mail list logo
