gnumed-client license

[Ankur Sinha]

Hi Sebastian,

I'm in the middle of packaging gnumed-client[1]. I wanted to confirm the
license that it's distributed under. It holds a gplv2 file, but the spec
I referenced specified GPLv1 iirc. Can you please clarify what license I
should use in the spec for fedora?

[1] https://bugzilla.redhat.com/show_bug.cgi?id=728757

[Sebastian Hilbert]

On Dienstag, 9. August 2011 18:34:51 Ankur Sinha wrote:
> Hi Sebastian,
>
> I'm in the middle of packaging gnumed-client[1]. I wanted to confirm the
> license that it's distributed under. It holds a gplv2 file, but the spec
> I referenced specified GPLv1 iirc. Can you please clarify what license I
> should use in the spec for fedora?
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=728757

GPLv2

if you need us to clean up any references upstream let us know.

Sebastian

[Ankur Sinha]

On Tue, 2011-08-09 at 20:35 +0200, Sebastian Hilbert wrote:
> GPLv2
>
> if you need us to clean up any references upstream let us know.
>
> Sebastian

Hi Sebastian,

I just needed to confirm for the review :)

Another query: I've referenced the spec that the website contains. This
spec uses quite a few explicit requires. Are these necessary?
> Requires:  aspell
> Requires:  file
> Requires:  python >= 2.3
> Requires:  python-psycopg2 >= 2.0.10
> Requires:  java
> Requires:  xsane
> Requires:  wxPython >= 2.6.3
> Requires:  mx
> Requires:  kdepim
> Requires:  texlive

Specially aspell, file, texlive, xsane etc?

[Sebastian Hilbert]

On Dienstag, 9. August 2011 18:34:51 Ankur Sinha wrote:
> Hi Sebastian,
>
> I'm in the middle of packaging gnumed-client[1]. I wanted to confirm the
> license that it's distributed under. It holds a gplv2 file, but the spec
> I referenced specified GPLv1 iirc. Can you please clarify what license I
> should use in the spec for fedora?
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=728757

Thanks for the effort.

Sebastian

gnumed-client update

[Sebastian Hilbert]

Hi all,

It would be great if someone finds some time to update gnumed to the latest 
stable realease in Fedora.

GNUmed oldstable (current in Fedora) is 1.1.18 over the included 1.1.14

and server v16.18

http://www.gnumed.de/downloads/client/1.1/

GNUmed newstable is 1.2.2. if someone has time to work on it.

and server v17.2

If you want I can find you the changelog for each version.

Let me know what we can do as upstream to make this as easy as possible for 
you.

Regards,
Sebastianedorahosted.org/mailman/listinfo/medical-sig

gnumed-client update

[Michel Alexandre Salim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sebastian,

On 08/04/2012 05:50 PM, Sebastian Hilbert wrote:
> Hi all,
>
> It would be great if someone finds some time to update gnumed to
> the latest stable realease in Fedora.
>
> GNUmed oldstable (current in Fedora) is 1.1.18 over the included
> 1.1.14
>
> and server v16.18

Thanks for the heads-up. I'll get 1.1.18 pushed a.s.a.p. and then work
on 1.2.2 for Rawhide (to be Fedora 18). Do you think the changes are
ground-breaking enough that stable distribution releases should stick
to 1.1.x?

I meant to sign GNUmed up to our automatic release tracker when I
started co-maintaining but somehow that didn't happen -- will do that
so we don't fall behind on future releases.

Thanks,

- -- 
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/

Email:  [e-mail]  | GPG key ID: A36A937A
Jabber: [e-mail]       | IRC: [e-mail]

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJQHQ7xAAoJEEr1VKujapN6X58IAJpE/jaIzGxqm8Oo3U0xtbSo
> Sj4fjgU18PtFrncuxLovB+A/+AAXlF3kOQsh7DcT/P76pjy4AnXzH1bG5Er3zjgu
> coh70ByaSuCOQ4+gdHp/NLk/gvvmlNhNFIlbRdxFkI3zSnB81V3rXESgR9r3h1DH
> vU2+4zy9KIp/a8Aouu4fyPtG99vzgEM6oFrO334c5ISXGcA9xamF+ci1E3o2LP/Q
> qVN7/A5HbKOw7teOYGoHxahJoddf1ON5w9EW8wPZTWMnPrhNf4cANG36GBQVnNVu
> xPCAnULq5s3BziwwRttrfyBJC8VCEHGyLM/QXI5IUaNUp5seBQ3y+2ZxV8KEuuo=
> =16iW
> -----END PGP SIGNATURE-----