|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
FreeDiamsHi all, Hi Andreas,
I've released sources of FreeDiams v0.1.2 (which is mainly a debug release). I've compiled it with my old rules/control because I've had a lot of errors when trying to use the new ones. Can you try a compilation with the "three package" method please ? Thanks a lot Eric http://www.freemedforms.com/ -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: FreeDiamsHi Eric,
there is no need to CC me in your mails, I'm reading the list carefully. ;-) On Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote: > I've released sources of FreeDiams v0.1.2 (which is mainly a debug > release). Fine. Build is just running on my box. I'll check the results and will upload to ftp.debian.org in case I see no problems. > I've compiled it with my old rules/control because I've had a lot of > errors when trying to use the new ones. Could you send a build log file? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: FreeDiamsOn Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote:
> I've released sources of FreeDiams v0.1.2 (which is mainly a debug > release). I have seen you even released v0.1.4 - at least guessing from your commit to the packaging SVN. I would like to clarify something and I hope you don't mind if I do this in public. But there might be other beginners and I would like to keep a record of this explanation. As I realised you are using the file debian/changelog to describe what you have changed in FreeDiams. But this is not the intention of the __debian__/changelog file. This file just describes the changes in the *Debian* *packaging*. So if there is a new version of FreeDiams the debian/changelog file would say something like this. freediams (0.1.4-1) UNRELEASED; urgency=low ^^^ mind this Debian version!!! * New upstream version * Additional Build-Depends ... * Bumped Standards-Version ... * Changes in debian/rules -- Eric Maeker <eric.maeker@...> Fri, 23 Oct 2009 00:00:00 +0200 What you wrote in this file rather belongs to a so called "upstream changelog" file which if for instance called "ChangeLog" or ChangeLog.txt or whatever. Here you can document the changes inside actual upstream (=FreeDiams) code. If you are mixing this up people which are not using Debian will probably miss your changelog and from a packaging point of view it might confuse other packagers. Feel free to ask here or in private if something remains unclear. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: FreeDiamsLe 23 oct. 09 à 19:28, Andreas Tille a écrit : > On Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote: >> I've released sources of FreeDiams v0.1.2 (which is mainly a debug >> release). > > I have seen you even released v0.1.4 - at least guessing from your > commit to the packaging SVN. I've sent a mail to debian-med too... It is not arrived... Whatever here is its content : > Hi all, > > This version (0.1.4) of FreeDiams corrects a fatal bug at application closing (seg fault). Update is _highly_ recommanded. > Some other bugs are corrected : > - Linux : Documentation access restored > - Win32 : MedinTux configuration corrected > > http://www.freemedforms.com/ > Sources available tomorrow. > Eric > I would like to clarify something and I > hope you don't mind if I do this in public. But there might be other > beginners and I would like to keep a record of this explanation. Ok no problem. As I already say : I'm just a C++ coder, not a linux guru, even not a debian guru ;) > As I realised you are using the file debian/changelog to describe what > you have changed in FreeDiams. But this is not the intention of the > __debian__/changelog file. This file just describes the changes in > the *Debian* *packaging*. Ok so the changelog in debian dir must only inform new uploads (and changes done to the other debian files). > So if there is a new version of FreeDiams > the debian/changelog file would say something like this. > > freediams (0.1.4-1) UNRELEASED; urgency=low > ^^^ > mind this Debian version!!! Ah ok, so the '-1' stands for debian version of the upstream 0.1.4 (no changes in the source package). I understand. > What you wrote in this file rather belongs to a so called "upstream > changelog" file which if for instance called "ChangeLog" or > ChangeLog.txt or whatever. Here you can document the changes inside > actual upstream (=FreeDiams) code. If you are mixing this up people > which are not using Debian will probably miss your changelog and from > a packaging point of view it might confuse other packagers. Yes yes, I thought this changelog was presented to users (eg synaptic when updating the package), I have therefore included all changes FreeDiams interesting. If the informations in 'debian/changelog' only refers to the file debian changes, is there a way to present application's update informations to users ? > Feel free to ask here or in private if something remains unclear. > > Kind regards > > Andreas. Thank you for your explanations. Eric -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: FreeDiamsOn Fri, Oct 23, 2009 at 08:56:05PM +0200, Eric MAEKER wrote:
>> As I realised you are using the file debian/changelog to describe what >> you have changed in FreeDiams. But this is not the intention of the >> __debian__/changelog file. This file just describes the changes in >> the *Debian* *packaging*. > Ok so the changelog in debian dir must only inform new uploads (and > changes done to the other debian files). Yes. >> freediams (0.1.4-1) UNRELEASED; urgency=low >> ^^^ >> mind this Debian version!!! > Ah ok, so the '-1' stands for debian version of the upstream 0.1.4 (no > changes in the source package). I understand. Exactly. > Yes yes, I thought this changelog was presented to users (eg synaptic > when updating the package), Well, this is correct if you have installed apt-listchanges (perhaps synaptic does on it's own - I don't know because I'm using plain apt-get mostly. > I have therefore included all changes > FreeDiams interesting. If the informations in 'debian/changelog' only > refers to the file debian changes, is there a way to present > application's update informations to users ? Hmm, not really. If there are *really* important things users really must know then you can use NEWS.Debian which is formatted like a changelog file. But it is widely considered as missuse if you just put any changes there. IMHO the best way to inform users is to maintain a proper upstream changelog and install this to /usr/share/doc/freediams/changelog using dh_installchangelogs. Debian users should be trained to have a look into /usr/share/doc/<packagename> and will find the relevant information there. Trusting that users are carefully browsing the Debian changelog in Synaptic or apt-listchanges is probably not rectifyed. There might be to many changes at one update and so it will not really get much notice anyway. > Thank you for your explanations. That's what this list is for. ;-) Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: FreeDiamsHi Eric,
I had another look into FreeDiams and I would like to propose some changes for your upstream tarball which will turn out to be very helpful for every Linux user and specifically for clean Debian packaging. 1. Please make only those files executable which really are intended to be executed. I only found one single file which should be executable: updatetranslations.sh So I would suggest to do find . -type f -exec chmod 644 \{\} \; which makes all files readable for everybody and writable for the user. After this reset executable flag for the script chmod 755 updatetranslations.sh This change in your tarball makes sure we will not have to fix permissions of files while building the Debireadable for everybody and writable for the user. After this reset executable flag for the script chmod 755 updatetranslations.sh This change in your tarball makes sure we will not have to fix permissions of files while building the Debiareadable for everybody and writable for the user. After this reset executable flag for the script chmod 755 updatetranslations.sh This change in your tarball makes sure we will not have to fix permissions of files while building the Debian package. 2. Use an upstream changelog: On Fri, Oct 23, 2009 at 08:56:05PM +0200, Eric MAEKER wrote: > > Ok so the changelog in debian dir must only inform new uploads (and > changes done to the other debian files). So if I would be in your shoes I would just move the debian/changelog to ChangeLog. Once this is done we can use a quite simple changelog saying something like freediams (0.1.5-1) unstable; urgency=low * Initial upload (Closes #<ITPbug>) -- Uploader / Date This makes things much easier and transparent for Debian users and your fellow developers 3. Please fix the clean target of your makefile. I had to use the following tweak in the debian/rules file: override_dh_auto_clean: rm -rf bin/plugins/* bin/freediams find build -type d -name "\.*" -exec rm -rf \{\} \; 2> /dev/null || true rm -rf global_resources/doc/FreeDiams It would be great, if you would add these three lines to your clean target. Please let me know if you agree with these suggestions and if yes, when you might release a new tarball addressing these items. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |