On Fri, 2011-05-27 at 11:51 +0530, Ankur Sinha wrote:
> Hi Gunter,
>
> I've built the package and submitted it for review here[1]
>
> I had one small query: Should I version the package as 2.6 (is it a
> stable release?), or should I use the svn checkout time stamp for the
> version?
>
> Thanks,
> Ankur
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=707613
Another *tiny* query: Folks suggested I first find out how upstream
(you) generate the test images, and then proceed to package it. We need
to be as close to upstream as possible :)
Thanks
Ankur
On Tue, 2011-05-24 at 09:06 +0200, Gunter Zeilinger wrote:
> Hello Ankur
>
> You will find the images at the svn at
> https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4che2-test/tags/dcm4…
>
> Kind Regards,
>
> gunter
Hi Gunter,
I've built the package and submitted it for review here[1]
I had one small query: Should I version the package as 2.6 (is it a
stable release?), or should I use the svn checkout time stamp for the
version?
Thanks,
Ankur
[1] https://bugzilla.redhat.com/show_bug.cgi?id=707613
Hi folks,
I just submitted the dcm4che-test-images package for review[1]. Could
someone please begin to review it? dcm4che is dependent on this package,
and therefore, so is mayan.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=707613
Thanks,
Ankur
Hello Gunter,
I'm trying to package dcm4che to make it available in the Fedora
repositories as part of the fedora medical initiative[1]. Could you
please point me to the sources used to build the dcm4che-test-image
jar.
It appears that the jar is required to build dcm4che. As per our
packaging guidelines, all build dependencies of a package must be
packaged first. For this, I require the sources of the jar file. I've
looked at the svn etc. but have failed to find them. I'd be grateful if
you could please point me to the correct location.
Once dcm4che is packaged, I will proceed to package mayam.
Thank you,
Regards,
Ankur
[1]https://fedoraproject.org/wiki/SIGs/FedoraMedical
Hi folks,
For those involved in packaging for the Medical sig, please do have a
look at the opensuse src rpms[1]. I think just changing the macros to
fit fedora's build system should be enough.
Thanks,
Ankur
[1] http://download.opensuse.org/repositories/medical/openSUSE_11.4/src/
Came across this bug again.
https://bugzilla.redhat.com/show_bug.cgi?id=669146
Comments below.
>Review:
>[+] OK
>[-] NA
>[X] issue
>X Package is a GUI app and has a .desktop file
? Since when :-) If there is a desktop file we can remove it. This is not a gui app
>X Package owns all the directories it creates.
>The directories here are not owned by the package:
>%doc %{_defaultdocdir}/%{name}/*
>%{_sharedstatedir}/%{name}/*
>You'll either have to use %dir %{_defaultdocdir}/%{name}
>or simply
>%doc %{_defaultdocdir}/%{name}
So I guess this can be fixed ?
>gnumed-server.noarch: W: no-manual-page-for-binary gm-restore_database
>gnumed-server.noarch: W: no-manual-page-for-binary gm-zip+sign_backups
>gnumed-server.noarch: W: no-manual-page-for-binary gm-move_backups_offsite
>gnumed-server.noarch: W: no-manual-page-for-binary gm-restore_data
True.
>/home/ankur/rpmbuild/SPECS/gnumed-server.spec: W: invalid-url Source0:
>http://www.gnumed.de/downloads/server/v14/gnumed-server.14.7.tgz HTTP Error
>404: Not Found
Maybe the server was down. Anyway I would like you to try version 15.4 of gnumed-server.
>gnumed-server.src: W: invalid-url Source0:
>http://www.gnumed.de/downloads/server/v14/gnumed-server.14.7.tgz HTTP Error
>404: Not Found
>2 packages and 1 specfiles checked; 0 errors, 6 warnings.
Same here.
>SHOULD Items:
Issues:
>1. Some of the files show a GPL license (not a v2). This needs to be added to
>the spec. A copy of the v1 license should also be included in the package.
@ Karsten. We could make this go away by licensing these files as GPL2, right ?
>3. The package is a GUI tool right? In that case a desktop file must be added
>to the package as described here
no it is not
>4. Doesn't the package require Python? I don't see it in the Requires. Please
>check on this.
It actually depends on
python-psycopg2 (>= 2.0.8)
Python-Module for PostgreSQL
which should nicely pull in python
>5. I haven't been able to check the functioning (yet).
you should :-)
>6. Please check the other issues outlined above too (ownership etc.)
see comments
I would appreciate if the issues could be checked and if the bug could be
updated.
Please let us (GNUmed) know if there are any issues you want us to fix
upstream.
Sebastian
Hi all,
http://ginkgo-cadx.com/en/
It might be worth exploring packaging of this LGPL application. The GNUmed
team would be highly interested in this (I will do some usability tests)
as it is the only application (I know of) on all operating systems (important
for us) which supports viewing fluouroscopy and echo studies.
Here is the list of dependecies
WxWidgets: MultiPlatform Graphical User Interface (GUI).
VTK: Kitware's Visualization ToolKit.
ITK: Kitware's Insight Segmentation and Registration Toolkit.
DCMTK: Offis' DICOM ToolKit.
OpenSSL: Open Source SSL/TLS Framework .
SQLite: The in-process SQL DataBase Engine.
Best regards,
Sebastian