Re: RFS: akregator - RSS feed aggregator for KDE
Some preliminary comments as I have not yet had time to look at the package proper: - the diff.gz is pretty much empty, it just patches the debian/changelog. I have not been able to verify if the upstream tarballs contain debian/* as the files do not seem to be on the sf.net mirrors yet. From the CVS logs you seem to be part of the development team, so it might be simpler to have the upstream tarballs drop debian/* and just include these files in your diff.gz (which doesn't prevent you from keeping debian/* in the same CVS repository!). - the package versions look dodgy, as there are 2 dashes (1.0-beta4-1). Furthermore you are going to run into problems when the final 1.0 version comes out: [EMAIL PROTECTED]:~$ dpkg --compare-versions 1.0-beta4-1 lt 1.0-1 echo true [EMAIL PROTECTED]:~$ You might consider labeling the beta versions something like 0.99+1.0beta4-1. [EMAIL PROTECTED]:~$ dpkg --compare-versions 0.99+1.0beta4-1 lt 1.0-1 echo true true [EMAIL PROTECTED]:~$ Will try to have a look at the packaging itself later today. Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS: akregator - RSS feed aggregator for KDE
Some preliminary comments as I have not yet had time to look at the package proper: - the diff.gz is pretty much empty, it just patches the debian/changelog. I have not been able to verify if the upstream tarballs contain debian/* as the files do not seem to be on the sf.net mirrors yet. From the CVS logs you seem to be part of the development team, so it might be simpler to have the upstream tarballs drop debian/* and just include these files in your diff.gz (which doesn't prevent you from keeping debian/* in the same CVS repository!). - the package versions look dodgy, as there are 2 dashes (1.0-beta4-1). Furthermore you are going to run into problems when the final 1.0 version comes out: [EMAIL PROTECTED]:~$ dpkg --compare-versions 1.0-beta4-1 lt 1.0-1 echo true [EMAIL PROTECTED]:~$ You might consider labeling the beta versions something like 0.99+1.0beta4-1. [EMAIL PROTECTED]:~$ dpkg --compare-versions 0.99+1.0beta4-1 lt 1.0-1 echo true true [EMAIL PROTECTED]:~$ Will try to have a look at the packaging itself later today. Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS : sailcut - sail design and plotting software
* Does it really have no command-line flags at all? The manpage seems to say so. So far there are no command-line flags, you can just specify the name of a file to open. I still gave the manpage a bit of a polish as it was really dry! * Have a look at http://lists.debian.org/debian-legal/2003/12/msg00188.html, your debian/copyright file should be a tad more detailed. All right, I have fixed that as well. I also added a Closes: #252041 in the changelog, I only intended to do so once the package is actually sponsored :) The corrected version of the package is available from mentors.debian.net: http://mentors.debian.net/debian/pool/main/s/sailcut/ Thanks for your input Rob! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS : sailcut - sail design and plotting software
Hello mentors! I have packaged Sailcut CAD, a sail design and plotting software which my father and I have been writing for several years. Sailcut has a strong userbase (give Google a run) which was traditionally Windows-based, but two years ago we switched to C++/Qt to reach a broader audience the feedback we received shows that this userbase is extending to free OS'es. To the best of my knowledge this is the only sail plotting package that is Free Software so I think it would be an interesting addition to Debian. = Here is the information from the ITP bug I filed: * Package name: sailcut Version : 0.7.0 Upstream Authors: Robert Lainé [EMAIL PROTECTED], Jeremy Lainé [EMAIL PROTECTED] * URL : http://sailcut.sourceforge.net/ * License : GPL Description : A sail design and plotting software Sailcut CAD is a sail design and plotting software which allows you to design and visualise your own sails and compute the accurate development of all panels in flat sheets. You can export the sails you create to DXF, plaintext or Carlson plotter files. Sailcut CAD's user interface is available in English, French, Dutch, German, Italian and Norwegian. = About the package: The package is both Lintian and Linda clean and it is available from mentors.d.o : http://mentors.debian.net/debian/pool/main/s/sailcut/ I am not yet a Debian Developer, but I maintain the package diogenes and I have started the NM process. Thank you for your time and I am looking forward to reading your suggestions on how to improve the package and/or offers for sponsorship! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
RFS : sailcut - sail design and plotting software
Hello mentors! I have packaged Sailcut CAD, a sail design and plotting software which my father and I have been writing for several years. Sailcut has a strong userbase (give Google a run) which was traditionally Windows-based, but two years ago we switched to C++/Qt to reach a broader audience the feedback we received shows that this userbase is extending to free OS'es. To the best of my knowledge this is the only sail plotting package that is Free Software so I think it would be an interesting addition to Debian. = Here is the information from the ITP bug I filed: * Package name: sailcut Version : 0.7.0 Upstream Authors: Robert Lainé [EMAIL PROTECTED], Jeremy Lainé [EMAIL PROTECTED] * URL : http://sailcut.sourceforge.net/ * License : GPL Description : A sail design and plotting software Sailcut CAD is a sail design and plotting software which allows you to design and visualise your own sails and compute the accurate development of all panels in flat sheets. You can export the sails you create to DXF, plaintext or Carlson plotter files. Sailcut CAD's user interface is available in English, French, Dutch, German, Italian and Norwegian. = About the package: The package is both Lintian and Linda clean and it is available from mentors.d.o : http://mentors.debian.net/debian/pool/main/s/sailcut/ I am not yet a Debian Developer, but I maintain the package diogenes and I have started the NM process. Thank you for your time and I am looking forward to reading your suggestions on how to improve the package and/or offers for sponsorship! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: drbd package
Currently, the stable version of drbd is the 0.6.x series. A new version is on the way, the 0.7.x series. I'd like to package the new 0.7.x version in debian, but keep the 0.6.x series in Debian as well. How should I go about this? If the 0.7.x series is going to be the development version for a while, maybe something à-la-Gimp like calling the package drbd0.7 (and having the date in the Debian version) would be appropriate. Otherwise, if the upstream development is pretty fast-moving, you could possibly use drbd-cvs as the package name (and still have the date in the Debian version). That way the ftpmasters wouldn't have to keep making changes to the override file. Jeremy (Disclaimer : I am not a DD) -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: drbd package
Currently, the stable version of drbd is the 0.6.x series. A new version is on the way, the 0.7.x series. I'd like to package the new 0.7.x version in debian, but keep the 0.6.x series in Debian as well. How should I go about this? If the 0.7.x series is going to be the development version for a while, maybe something à-la-Gimp like calling the package drbd0.7 (and having the date in the Debian version) would be appropriate. Otherwise, if the upstream development is pretty fast-moving, you could possibly use drbd-cvs as the package name (and still have the date in the Debian version). That way the ftpmasters wouldn't have to keep making changes to the override file. Jeremy (Disclaimer : I am not a DD) -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS: lis -- SVR4 compatible STREAMS (+help on lintian)
Uploaded to http://mentors.debian.org/ Failed to fetch http://mentors.debian.net/debian/pool/main/l/lis/lis_2.16.16.orig.tar.gz 404 Not Found Looks like you didn't include the original source with your upload. This is because your package version is neither -0 nor -1, so dpkg-genchanges did not include the original source in the list of files. From the dpkg-buildpackage manpage: By default, or if -si is specified, the original source will be included if the version number ends in -0 or -1, ie if the Debian revision part of the version number is 0 or 1. Will try to grab the original source and slap on your diff to have a look at your lintian error. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS: lis -- SVR4 compatible STREAMS (+help on lintian)
Hi again Thomas, I just had a look at your control file.. it's HUGE as you define all the kernel-lis-modules-2.4.26-1-(386|586tsc|etc..) packages! I suggest you take a look at how alsa or pcmcia-cs are packaged and create an lis-source package in your control file. You should not be building all these different flavours from your main control file. What you want to do is build : lis, lis-dev, lis-doc, lis-source. The lis-source package is the one that will be used to build the actual kernel modules. To do so you will provide a template called lis-source.control in your main package which will define the various kernel module packages. Once again, I recommend you take a look at how ALSA or the PCMCIA packages are built! Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS: lis -- SVR4 compatible STREAMS (+help on lintian)
Uploaded to http://mentors.debian.org/ Failed to fetch http://mentors.debian.net/debian/pool/main/l/lis/lis_2.16.16.orig.tar.gz 404 Not Found Looks like you didn't include the original source with your upload. This is because your package version is neither -0 nor -1, so dpkg-genchanges did not include the original source in the list of files. From the dpkg-buildpackage manpage: By default, or if -si is specified, the original source will be included if the version number ends in -0 or -1, ie if the Debian revision part of the version number is 0 or 1. Will try to grab the original source and slap on your diff to have a look at your lintian error. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: lis -- SVR4 compatible STREAMS (+help on lintian)
Hi again Thomas, I just had a look at your control file.. it's HUGE as you define all the kernel-lis-modules-2.4.26-1-(386|586tsc|etc..) packages! I suggest you take a look at how alsa or pcmcia-cs are packaged and create an lis-source package in your control file. You should not be building all these different flavours from your main control file. What you want to do is build : lis, lis-dev, lis-doc, lis-source. The lis-source package is the one that will be used to build the actual kernel modules. To do so you will provide a template called lis-source.control in your main package which will define the various kernel module packages. Once again, I recommend you take a look at how ALSA or the PCMCIA packages are built! Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
removing MySQL data on purge
Upon purging a package, it is expected that all installed data should be removed. The package diogenes installs a MySQL database and a MySQL user by prompting the user via debconf for the admin user/password. I want to give users the possibility to remove that database and user when the package is purged. However, this means knowing the MySQL admin password at removal time. What is the best way to go as it is probably a very bad idea to keep the admin user/password stored in debconf's database? Many thanks in advance! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: removing MySQL data on purge
A better solution would be detecting whether a password is needed (i.e. the debian-sys-maint or whatever the account is called is not available) and if so, prompt the user via debconf at purge. Trying to be guess whether a password is needed seems rather risky as the database could very well be on a different server, don't you think? I also noticed that in horde2, the config script tries to retrieve the local admin password using mysql-localadmpass.get, but it does not check at all if we are indeed installing the database on the local server.. As for prompting at purge, isn't that a big no-no? Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
removing MySQL data on purge
Upon purging a package, it is expected that all installed data should be removed. The package diogenes installs a MySQL database and a MySQL user by prompting the user via debconf for the admin user/password. I want to give users the possibility to remove that database and user when the package is purged. However, this means knowing the MySQL admin password at removal time. What is the best way to go as it is probably a very bad idea to keep the admin user/password stored in debconf's database? Many thanks in advance! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removing MySQL data on purge
A better solution would be detecting whether a password is needed (i.e. the debian-sys-maint or whatever the account is called is not available) and if so, prompt the user via debconf at purge. Trying to be guess whether a password is needed seems rather risky as the database could very well be on a different server, don't you think? I also noticed that in horde2, the config script tries to retrieve the local admin password using mysql-localadmpass.get, but it does not check at all if we are indeed installing the database on the local server.. As for prompting at purge, isn't that a big no-no? Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: One source package and more then 1 deb
Hi Matthijs, When you have a multibinary package, debian/tmp is the default place where files get put. It's then up to you to move those files out of there to put them into the various binary packages' directories, for instance using dh_movefiles (see manpage) if you use debhelper. In your case, there is another thing top take into account : the *first* package listed in debian/control is considered as the main package, that is the one that gets packaged from the contents of debian/tmp. Tot ziens! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: One source package and more then 1 deb
Hi Matthijs, When you have a multibinary package, debian/tmp is the default place where files get put. It's then up to you to move those files out of there to put them into the various binary packages' directories, for instance using dh_movefiles (see manpage) if you use debhelper. In your case, there is another thing top take into account : the *first* package listed in debian/control is considered as the main package, that is the one that gets packaged from the contents of debian/tmp. Tot ziens! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Issues found with diogenes
Hi Matthew, I have gone ahead and made the changes so that you can see them in action. This is done in 0.9.9.3-5 which I have uploaded to your queue. As far as I can tell, that deals with the last item on your initial review of the package, let me know if you find anything else! Have you had a chance to take a look at version Diogenes 0.9.9.3-6 which I sent to your queue on Friday 11 April? I haven't touched the package since as I didn't know if you were satisfied with its current state. Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
Hi Matthew, I have gone ahead and made the changes so that you can see them in action. This is done in 0.9.9.3-5 which I have uploaded to your queue. As far as I can tell, that deals with the last item on your initial review of the package, let me know if you find anything else! Have you had a chance to take a look at version Diogenes 0.9.9.3-6 which I sent to your queue on Friday 11 April? I haven't touched the package since as I didn't know if you were satisfied with its current state. Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Issues found with diogenes
Upload it to my queue (as described at done I'd say that if the problem can be detected at the time the config script runs I've thought about it, and yes, it *can* be done though it requires sucking a wwwconfig-common script into the config script, as we cannot depend on wwwconfig-common being installed at the time it runs. I don't think it's any big deal, the script we're talking about it about 3 lines long. The new behaviour would be: - try to figure out the webgroup at the time the config script runs - if we cannot determine it (for instance if apache is not installed yet or if the user chose Other as the webserver), prompt the user for the appropriate group - in postinst we no longer have a problem, we are sure to have the webgroup Would this be ok? Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
Would this be ok? I have gone ahead and made the changes so that you can see them in action. This is done in 0.9.9.3-5 which I have uploaded to your queue. As far as I can tell, that deals with the last item on your initial review of the package, let me know if you find anything else! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
Would this be ok? I have gone ahead and made the changes so that you can see them in action. This is done in 0.9.9.3-5 which I have uploaded to your queue. As far as I can tell, that deals with the last item on your initial review of the package, let me know if you find anything else! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Issues found with diogenes
Hi Matthew, Thanks for taking the time to look at the package! I have a few questions, especially regarding the database configuration. * No WNPP bug filed. fixed, I have filed an ITP * Communicates with the user via the console. Consider using debconf notes instead if it's vitally important. I suppose you are refering to the postinst script where a message is displayed if it was not possible to determine the group of the webserver process? This was lifted from the horde2 package, but you are right this is not ideal. My problem is that the we only know if we cannot get webgroup variable once we have run the /usr/share/wwwconfig-common/apache-run.get script. Should I call this from the config script and display a message at that time? * If you chose one of the first three options on a question that only has two options in total... oops, fixed! * I never got asked the DB admin questions, so installation failed. I am not sure how this can happen, you should at least have been prompted for the password as this is marked as critical. What level did you select for debconf questions so that I can try to reproduce this? I noticed that in Horde2's scripts, these questions are asked *both* in the config and the postinst scripts, although I was under the impression that there should not be any db_input calls from postinst. contents of/usr/share/doc cannot be relied upon to exist. You'll need to move your installation scripts somewhere else (/usr/share/diogenes/scripts, possibly). done * The permissions setting script is a hack. The gods gave us GRANT for a reason. quite right, I now use wwwconfig-common's createuser script * Automatic installation failed to properly install the apache config. what exactly happened? did /etc/diogenes/apache.conf not get included, or was apache not restarted so that the changes did not take effect? * Due to the problems getting the dbadmin info, no proper cleanup of the database or apache config was done. what do you mean by database cleanup ? I had not intended the database to be dropped, as this could lead to unintented data loss. Maybe I should ask the user upon installation whether he/she wants to get rid of Diogenes data (both database and files in /var/spool/diogenes and /var/lib/diogenes) when Diogenes is removed ? The .dpkg-dist files from ucf weren't cleaned up on purge, either. fixed, I now clean the .dpkg-dist, .dpkg-new and .dpkg-old files Assuming you're intending to become a Debian Developer in the future, I'm happy to sponsor uploads of this package Definitely, the way I see it it would be pointless to upload the packages if I didn't intend to become DD at some point in the future, they would risk becoming unmaintained! On a sidenote, my GPG key was already signed by Andreas Schuldei when we met in Stockholm. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
* Automatic installation failed to properly install the apache config. Ok, got it, /etc/diogenes/apache.conf needed to be created before calling the wwwconfig-common scripts that get it included in httpd.conf! The fixes in my previous email as well as this one are included in the 0.9.9.3-3 package which is available on mentors.debian.net. As far as I can tell, that leaves us with 2 outstanding issues, for which I need your advice: - the problem of communicating via the console - why you did not get prompted for the dbadmin questions Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
* I never got asked the DB admin questions, so installation failed. I think I've got it : diogenes.config tried to figure out the database admin and password by using wwwconfig-common's mysql-localadmpass.get (which reads /etc/mysql/my.cnf /var/lib/mysql/my.cnf ~/.my.cnf) and if it got an answer, it did not ask the corresponding debconf questions. I think this behaviour is not appropriate as it does not guarantee that the said admin/password are for the correct MySQL server (it does no checks on the host). I have dropped this bit of code altogether and simply ask the admin/password questions regardless of the my.cnf files. I am wondering if a bug shouldn't be filed against horde2 as it has the same behaviour. Anyhow, diogenes 0.9.9.3-4 fixes this, can you possibly confirm that the installation works as expected? This still leaves the communicating via console problem if you choose Other as a webserver, I'll wait for your thoughts on the subject. Cheers! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Issues found with diogenes
Hi Matthew, Thanks for taking the time to look at the package! I have a few questions, especially regarding the database configuration. * No WNPP bug filed. fixed, I have filed an ITP * Communicates with the user via the console. Consider using debconf notes instead if it's vitally important. I suppose you are refering to the postinst script where a message is displayed if it was not possible to determine the group of the webserver process? This was lifted from the horde2 package, but you are right this is not ideal. My problem is that the we only know if we cannot get webgroup variable once we have run the /usr/share/wwwconfig-common/apache-run.get script. Should I call this from the config script and display a message at that time? * If you chose one of the first three options on a question that only has two options in total... oops, fixed! * I never got asked the DB admin questions, so installation failed. I am not sure how this can happen, you should at least have been prompted for the password as this is marked as critical. What level did you select for debconf questions so that I can try to reproduce this? I noticed that in Horde2's scripts, these questions are asked *both* in the config and the postinst scripts, although I was under the impression that there should not be any db_input calls from postinst. contents of/usr/share/doc cannot be relied upon to exist. You'll need to move your installation scripts somewhere else (/usr/share/diogenes/scripts, possibly). done * The permissions setting script is a hack. The gods gave us GRANT for a reason. quite right, I now use wwwconfig-common's createuser script * Automatic installation failed to properly install the apache config. what exactly happened? did /etc/diogenes/apache.conf not get included, or was apache not restarted so that the changes did not take effect? * Due to the problems getting the dbadmin info, no proper cleanup of the database or apache config was done. what do you mean by database cleanup ? I had not intended the database to be dropped, as this could lead to unintented data loss. Maybe I should ask the user upon installation whether he/she wants to get rid of Diogenes data (both database and files in /var/spool/diogenes and /var/lib/diogenes) when Diogenes is removed ? The .dpkg-dist files from ucf weren't cleaned up on purge, either. fixed, I now clean the .dpkg-dist, .dpkg-new and .dpkg-old files Assuming you're intending to become a Debian Developer in the future, I'm happy to sponsor uploads of this package Definitely, the way I see it it would be pointless to upload the packages if I didn't intend to become DD at some point in the future, they would risk becoming unmaintained! On a sidenote, my GPG key was already signed by Andreas Schuldei when we met in Stockholm. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Issues found with diogenes
* Automatic installation failed to properly install the apache config. Ok, got it, /etc/diogenes/apache.conf needed to be created before calling the wwwconfig-common scripts that get it included in httpd.conf! The fixes in my previous email as well as this one are included in the 0.9.9.3-3 package which is available on mentors.debian.net. As far as I can tell, that leaves us with 2 outstanding issues, for which I need your advice: - the problem of communicating via the console - why you did not get prompted for the dbadmin questions Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Issues found with diogenes
* I never got asked the DB admin questions, so installation failed. I think I've got it : diogenes.config tried to figure out the database admin and password by using wwwconfig-common's mysql-localadmpass.get (which reads /etc/mysql/my.cnf /var/lib/mysql/my.cnf ~/.my.cnf) and if it got an answer, it did not ask the corresponding debconf questions. I think this behaviour is not appropriate as it does not guarantee that the said admin/password are for the correct MySQL server (it does no checks on the host). I have dropped this bit of code altogether and simply ask the admin/password questions regardless of the my.cnf files. I am wondering if a bug shouldn't be filed against horde2 as it has the same behaviour. Anyhow, diogenes 0.9.9.3-4 fixes this, can you possibly confirm that the installation works as expected? This still leaves the communicating via console problem if you choose Other as a webserver, I'll wait for your thoughts on the subject. Cheers! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS for ITA: xcruise -- Fly about a 3D-formed file system
Hi! After this upload only two wishlist bugs and one important (segfault, unreproducible on my system, being investigated) will be left. I get a segmentation fault on my system, it's pretty strange.. If I just run xcruise, the velocity starts to go negative, and increasingly so (it goes to collosal numbers). After about 5 seconds, the program bails out with a segmentation fault. The only way I can prevent this is by pressing button 1 as soon as I launch xcruise. The strange thing is that I tried to to run valgrind to pinpoint the memory problem and nothing happened (as in xcruise did not start racing away from the galaxies). Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS for ITA: xcruise -- Fly about a 3D-formed file system
Hi! After this upload only two wishlist bugs and one important (segfault, unreproducible on my system, being investigated) will be left. I get a segmentation fault on my system, it's pretty strange.. If I just run xcruise, the velocity starts to go negative, and increasingly so (it goes to collosal numbers). After about 5 seconds, the program bails out with a segmentation fault. The only way I can prevent this is by pressing button 1 as soon as I launch xcruise. The strange thing is that I tried to to run valgrind to pinpoint the memory problem and nothing happened (as in xcruise did not start racing away from the galaxies). Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS : diogenes - web content management system
Hi! I am still looking for a sponsor for Diogenes! I am sure there is someone with some PHP/MySQL/debconf experience out there to look at the packages? Cheers, Jeremy On Mon, 29 Mar 2004 15:02:27 +0200 Jeremy Lainé [EMAIL PROTECTED] wrote: Hello, I am looking for a sponsor for Diogenes, a web content management system. Here is the relevant information: Package : diogenes License : GPL v2 Upstream : Jeremy Lainé [EMAIL PROTECTED] URL : http://opensource.polytechnique.org/diogenes/ Short description : Web content management system Long description : The Diogenes web content management system allows you to create, host and manage web sites through a web interface and/or WebDAV. You can host several independent sites on a single server and even have them run on separate virtualhosts. Diogenes offers fine-grained control of the read and write permissions of the pages making up a site. The packages are lintian and linda clean and have undergone quite a bit of testing. The debconf scripts are adapted from Horde's (cf. messages on this list a few months back) and I made sure to use po-debconf as stated in the latest version of the policy. I would be happy to provide any extra information that might be needed. The packages can be found here: deb http://opensource.polytechnique.org/debian/ ./ deb-src http://opensource.polytechnique.org/debian/ ./ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS : diogenes - web content management system
Experience, probably. Time is the pressing issue. Out of interest, what does diogenes do (apart from WebDAV, which isn't of pressing interest to me personally) that other content management systems, such as MySource, don't do? I have looked through the MySource documentation and I won't claim that Diogenes has all the features of MySource, that just wouldn't be true (for instance there is no plugin mecanism in Diogenes currently). It does however, have some handy features of its own: - WebDAV you already stated - version control (RCS or CVS, your choice), with a built-in diff. viewer - the WYSIWYG editor is a Java applet so it really works on all platforms (http://sourceforge.net/projects/ekit/) - a logging system and a log browser which allow you to keep track of what users have been up to - Diogenes's UI uses GNU gettext, so it is possible to add any number of translations (currently, a French one is included) - import of Word documents using wv for users who really have no clue how to write a web page - if you are sure of what you are doing, you can allow PHP execution, meaning you can write PHP pages - the authentication mecanism is extendable, if you wish you can use a different DB which holds existing user accounts (the documentation for Diogenes lives at http://doc.polytechnique.org/diogenes/) As I said previously, Diogenes is not as complete as something like MySource, but then the approach is different : on one hand, it does allow users with little or no web experience to create sites, but it also catters for the die-hard coders. If you wish, you can tap straight into the RCS/CVS repository or you can even reshape Diogenes quite heavily by subclassing its PHP classes from the config files (/etc/diogenes/diogenes.debian.inc.php is the perfect place to do so). For instance, on diogenes.polytechnique.org, the authentication class has been subclassed to allow 2 different types of login. Hope this gives you a clearer view of what Diogenes does! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS : diogenes - web content management system
Aarrrgh! If you'd happened to package this a couple of months ago, I would have been so incredibly happy. Ah well.. Diogenes *has* been packaged since 2 Dec 2003 but I wanted to make sure the packages were rock solid before looking for a sponsor :) If you can hold off for a couple of days, I'll have a look over the package on Thursday when I get a bit of spare time then. No problem, the packages aren't going to leap off the face of the earth in the meantime, so Thursday is fine! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS : diogenes - web content management system
Hi! I am still looking for a sponsor for Diogenes! I am sure there is someone with some PHP/MySQL/debconf experience out there to look at the packages? Cheers, Jeremy On Mon, 29 Mar 2004 15:02:27 +0200 Jeremy Lainé [EMAIL PROTECTED] wrote: Hello, I am looking for a sponsor for Diogenes, a web content management system. Here is the relevant information: Package : diogenes License : GPL v2 Upstream : Jeremy Lainé [EMAIL PROTECTED] URL : http://opensource.polytechnique.org/diogenes/ Short description : Web content management system Long description : The Diogenes web content management system allows you to create, host and manage web sites through a web interface and/or WebDAV. You can host several independent sites on a single server and even have them run on separate virtualhosts. Diogenes offers fine-grained control of the read and write permissions of the pages making up a site. The packages are lintian and linda clean and have undergone quite a bit of testing. The debconf scripts are adapted from Horde's (cf. messages on this list a few months back) and I made sure to use po-debconf as stated in the latest version of the policy. I would be happy to provide any extra information that might be needed. The packages can be found here: deb http://opensource.polytechnique.org/debian/ ./ deb-src http://opensource.polytechnique.org/debian/ ./ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: RFS : diogenes - web content management system
Experience, probably. Time is the pressing issue. Out of interest, what does diogenes do (apart from WebDAV, which isn't of pressing interest to me personally) that other content management systems, such as MySource, don't do? I have looked through the MySource documentation and I won't claim that Diogenes has all the features of MySource, that just wouldn't be true (for instance there is no plugin mecanism in Diogenes currently). It does however, have some handy features of its own: - WebDAV you already stated - version control (RCS or CVS, your choice), with a built-in diff. viewer - the WYSIWYG editor is a Java applet so it really works on all platforms (http://sourceforge.net/projects/ekit/) - a logging system and a log browser which allow you to keep track of what users have been up to - Diogenes's UI uses GNU gettext, so it is possible to add any number of translations (currently, a French one is included) - import of Word documents using wv for users who really have no clue how to write a web page - if you are sure of what you are doing, you can allow PHP execution, meaning you can write PHP pages - the authentication mecanism is extendable, if you wish you can use a different DB which holds existing user accounts (the documentation for Diogenes lives at http://doc.polytechnique.org/diogenes/) As I said previously, Diogenes is not as complete as something like MySource, but then the approach is different : on one hand, it does allow users with little or no web experience to create sites, but it also catters for the die-hard coders. If you wish, you can tap straight into the RCS/CVS repository or you can even reshape Diogenes quite heavily by subclassing its PHP classes from the config files (/etc/diogenes/diogenes.debian.inc.php is the perfect place to do so). For instance, on diogenes.polytechnique.org, the authentication class has been subclassed to allow 2 different types of login. Hope this gives you a clearer view of what Diogenes does! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS : diogenes - web content management system
Aarrrgh! If you'd happened to package this a couple of months ago, I would have been so incredibly happy. Ah well.. Diogenes *has* been packaged since 2 Dec 2003 but I wanted to make sure the packages were rock solid before looking for a sponsor :) If you can hold off for a couple of days, I'll have a look over the package on Thursday when I get a bit of spare time then. No problem, the packages aren't going to leap off the face of the earth in the meantime, so Thursday is fine! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS : diogenes - web content management system
Hello, I am looking for a sponsor for Diogenes, a web content management system. Here is the relevant information: Package : diogenes License : GPL v2 Upstream : Jeremy Lainé [EMAIL PROTECTED] URL : http://opensource.polytechnique.org/diogenes/ Short description : Web content management system Long description : The Diogenes web content management system allows you to create, host and manage web sites through a web interface and/or WebDAV. You can host several independent sites on a single server and even have them run on separate virtualhosts. Diogenes offers fine-grained control of the read and write permissions of the pages making up a site. The packages are lintian and linda clean and have undergone quite a bit of testing. The debconf scripts are adapted from Horde's (cf. messages on this list a few months back) and I made sure to use po-debconf as stated in the latest version of the policy. I would be happy to provide any extra information that might be needed. The packages can be found here: deb http://opensource.polytechnique.org/debian/ ./ deb-src http://opensource.polytechnique.org/debian/ ./ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
RFS : diogenes - web content management system
Hello, I am looking for a sponsor for Diogenes, a web content management system. Here is the relevant information: Package : diogenes License : GPL v2 Upstream : Jeremy Lainé [EMAIL PROTECTED] URL : http://opensource.polytechnique.org/diogenes/ Short description : Web content management system Long description : The Diogenes web content management system allows you to create, host and manage web sites through a web interface and/or WebDAV. You can host several independent sites on a single server and even have them run on separate virtualhosts. Diogenes offers fine-grained control of the read and write permissions of the pages making up a site. The packages are lintian and linda clean and have undergone quite a bit of testing. The debconf scripts are adapted from Horde's (cf. messages on this list a few months back) and I made sure to use po-debconf as stated in the latest version of the policy. I would be happy to provide any extra information that might be needed. The packages can be found here: deb http://opensource.polytechnique.org/debian/ ./ deb-src http://opensource.polytechnique.org/debian/ ./ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
unofficial sylpheed-claws packages
If someone is interested in working on packages for sylpheed-claws (please, pretty please as Gustavo Noronha Silva is currently unavailable!), you can use the diffs I put online to save a little time. I took Gustavo's patches for 0.9.6 and made the necessary changes to make them work for sylpheed-claws 0.9.7 through 0.9.10. Nothing fancy here, but as sylpheed-claws's code has been changing quite a bit, it'll probably save some time.. The packages and diffs are here: http://dev.jerryweb.org/sylpheed-claws/ Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unofficial sylpheed-claws packages
Cancel my last, I hadn't seen the messages on debian-devel :) Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
unofficial sylpheed-claws packages
If someone is interested in working on packages for sylpheed-claws (please, pretty please as Gustavo Noronha Silva is currently unavailable!), you can use the diffs I put online to save a little time. I took Gustavo's patches for 0.9.6 and made the necessary changes to make them work for sylpheed-claws 0.9.7 through 0.9.10. Nothing fancy here, but as sylpheed-claws's code has been changing quite a bit, it'll probably save some time.. The packages and diffs are here: http://dev.jerryweb.org/sylpheed-claws/ Cheers, Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: unofficial sylpheed-claws packages
Cancel my last, I hadn't seen the messages on debian-devel :) Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: debconf db_input in postinst / horde2
Thanks for all the input! From this discussion I conclude that in my package's case there is no call for db_input in postinst, so I just commented out those calls and lintian/linda are happy :) Maybe it would be useful to summarise the cases where you are pretty forced to use db_input calls in postinst for future reference? The resulting package is available here: http://opensource.polytechnique.org/diogenes/ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debconf db_input in postinst / horde2
Thanks for all the input! From this discussion I conclude that in my package's case there is no call for db_input in postinst, so I just commented out those calls and lintian/linda are happy :) Maybe it would be useful to summarise the cases where you are pretty forced to use db_input calls in postinst for future reference? The resulting package is available here: http://opensource.polytechnique.org/diogenes/ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
debconf db_input in postinst / horde2
Hi! I am trying to put the finishing touches on a package of Diogenes, a web content management system. The package relies on a MySQL database, and this database is created based on some information provided by the user through debconf. I am down to one lintian warning : W: diogenes: postinst-uses-db-input N: It is generally not a good idea for postinst scripts to use debconf N: commands like db_input. Typically, they should restrict themselves to N: db_get to request previously acquired information, and have the config N: script do the actual prompting. My debian/postinst and debian/config are heavily based on those of the horde2 package so I checked, and sure enough the db_input in postinst which is causing the warning came from horde2. It concerns the MySQL admin user and password, which is in fact already asked for in the debian/config file. I can see how it is a Bad Thing to prompt the user for input both in postinst and in config, but the fact still stands that it's the way it's done in horde2, and I'm sure there must be a good reason for it! Any ideas here? Is there any scenario (recovering from a failed install..) which would involve running the postinst without the config, and hence justify the prompt for the admin user/password? In a similar line of thought, the admin password is stored in the debconf database in config and reset in postinst, so I suppose that means that if for some reason the installation fails, we still have the password stored in database. Any pointers to policy reference on dealing with this? Thanks for your time and have a pleasant day! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debconf db_input in postinst / horde2
Hi! I am trying to put the finishing touches on a package of Diogenes, a web content management system. The package relies on a MySQL database, and this database is created based on some information provided by the user through debconf. I am down to one lintian warning : W: diogenes: postinst-uses-db-input N: It is generally not a good idea for postinst scripts to use debconf N: commands like db_input. Typically, they should restrict themselves to N: db_get to request previously acquired information, and have the config N: script do the actual prompting. My debian/postinst and debian/config are heavily based on those of the horde2 package so I checked, and sure enough the db_input in postinst which is causing the warning came from horde2. It concerns the MySQL admin user and password, which is in fact already asked for in the debian/config file. I can see how it is a Bad Thing to prompt the user for input both in postinst and in config, but the fact still stands that it's the way it's done in horde2, and I'm sure there must be a good reason for it! Any ideas here? Is there any scenario (recovering from a failed install..) which would involve running the postinst without the config, and hence justify the prompt for the admin user/password? In a similar line of thought, the admin password is stored in the debconf database in config and reset in postinst, so I suppose that means that if for some reason the installation fails, we still have the password stored in database. Any pointers to policy reference on dealing with this? Thanks for your time and have a pleasant day! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: Sponsor for a bootstrapping Java++ compiler
To achieve this I use the deb-makepkg script below. Thanks a lot, I will look at this. Shouldn't this advertised publicly, and a package made for it? I have rewritten my script in Perl, cleaned it up, removed hard coded values and now both package name and version are extracted from debian/changelog. I put together a Debian package called j-misc which for the moment just contains j-buildpackage (new name of the script) and a template manpage. You can find the package and browse the CVS repository here: http://dev.jerryweb.org/projects/j-misc/ All suggestions are welcome! Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux pgpDgsG5UZARV.pgp Description: PGP signature
Re: Sponsor for a bootstrapping Java++ compiler
AFAIK, this is not OK. Though I used to do it myself too. The
correct way, I believe is to make a tar.gz file, like the one which
is online, and build the Debian package from that.
To achieve this I use the deb-makepkg script below. You need to
adjust the BUILDIR to wherever you build your Debian packages. Next
you cd to your working copy of your package, and type :
deb-makepkg package version
What this does:
* make dist to build the .tar.gz then renames it to
package_version.orig.tar.gz
* extracts the tar.gz
* scans debian/CVS to know what files are actually part of the CVS
module (except .cvsignore files) and copies these files to debian/ in
the directory where the .tar.gz was extracted
* runs dpkg-buildpackage -rfakeroot
That way you have a non-native package with a clean diff!
Jeremy
-
#!/bin/bash
# $Id: deb-makepkg,v 1.4 2003/03/11 17:26:22 sharky Exp $
BUILDIR=~sharky/dev/debian
SRCDIR=`pwd`
BPACKAGE=$1
BVERSION=$2
if [ -z $2 ]; then
echo Usage: deb-makepkg package version
exit 1
fi
if [ ! -f ChangeLog ]; then
echo ChangeLog not found!
exit 2
fi
if [ ! -f debian/CVS/Entries ]; then
echo debian/CVS/Entries not found!
exit 3
fi
rm -f ${BPACKAGE}-${BVERSION}.tar.gz
make dist
if [ ! -f ${BPACKAGE}-${BVERSION}.tar.gz ]; then
echo Cannot find ${BPACKAGE}-${BVERSION}.tar.gz
exit 4
fi
# clean up build directory
if [ ! -d $BUILDIR ]; then
echo Cannot find directory $BUILDIR
exit 5
fi
rm -rf ${BUILDIR}/${BPACKAGE}-${BVERSION}
rm -f ${BUILDIR}/${BPACKAGE}_${BVERSION}-*.diff.gz
# copy and extract archive
cp ${BPACKAGE}-${BVERSION}.tar.gz
${BUILDIR}/${BPACKAGE}_${BVERSION}.orig.tar.gz
cd $BUILDIR
tar zxvf ${BPACKAGE}_${BVERSION}.orig.tar.gz
# enter directory and copy Debian files
mkdir ${BPACKAGE}-${BVERSION}/debian
cd ${BPACKAGE}-${BVERSION}
for debfile in `cat ${SRCDIR}/debian/CVS/Entries | sed -n -e
's/^\/\(.*\)\/1\(\.[0-9]\+\)\+\/.*\/\/$/\1/p'`; do
[ $debfile != .cvsignore ] cp ${SRCDIR}/debian/${debfile} debian
done
# build package
dpkg-buildpackage -rfakeroot
-
--
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
pgp56oxvQCpGF.pgp
Description: PGP signature
Re: (one more attempt at an) RFS: sugarplum
Sweet package, I got it to run on Apache2 in 3 minutes flat. I am unfortunately not a DD so lets hope someone steps up! Thanks for the good work and good luck.. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (one more attempt at an) RFS: sugarplum
Sweet package, I got it to run on Apache2 in 3 minutes flat. I am unfortunately not a DD so lets hope someone steps up! Thanks for the good work and good luck.. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
Re: joining Debian / packaging buildd
You should probably subscribe to buildd-discuss at nocrew.org. done, but no reply so far. In the meantime, I have started work using your package as a base, and have got the buildd package to generate an /etc/default/buildd via debconf. It is structured exactly like the current /etc/buildd/buildd.conf.global. The priorities for the questions are totally arbitrary for the moment as I do not know yet what the correct priorities should be. You can grab my diff from : http://dev.jerryweb.org/projects/buildd/ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux msg08430/pgp0.pgp Description: PGP signature
Re: joining Debian / packaging buildd
You might be interested in http://www.whinlatter.uklinux.net/buildd/ Definitely, I'm looking through it right now. You should probably subscribe to buildd-discuss at nocrew.org. Done, and browsing through the archives I see I'm going pretty much the same way as you as I also rely on autoconf/automake and have moved to debhelper. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux pgp3ubFq6Emso.pgp Description: PGP signature
Re: joining Debian / packaging buildd
You should probably subscribe to buildd-discuss at nocrew.org. done, but no reply so far. In the meantime, I have started work using your package as a base, and have got the buildd package to generate an /etc/default/buildd via debconf. It is structured exactly like the current /etc/buildd/buildd.conf.global. The priorities for the questions are totally arbitrary for the moment as I do not know yet what the correct priorities should be. You can grab my diff from : http://dev.jerryweb.org/projects/buildd/ Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux pgpQ3LDds5caH.pgp Description: PGP signature
joining Debian / packaging buildd
Hi! I am interested in becoming a Debian developer and have already produced a number of Debian packages, but they fall in the pet packages category referred to in another thread on this list. The most recent ones are mpf70-source and mpf70-utils, respectively the source for a kernel module (builds with make-kpkg) and some userspace utilities for the MPman MP-F70 portable MP3 player: deb http://dev.jerryweb.org/debian ./ deb-src http://dev.jerryweb.org/debian ./ As far as I can tell, these packages are pretty much ready, but I am putting them on hold until someone else expresses interest in them, so as not to clutter the Debian archive pointlessly. In the meantime, I think I've found something to sink my teeth in, namely packaging buildd. I realise it's a big bugger, but as packaging it seems to have been on the TODO list for a while I suppose any work I put into it is that much done.. I am looking for a contact from the buildd team to ask whether I can rename some files, or whether this is not a purely Debian package and needs to be handled like a package with an upstream and a Debian diff. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
joining Debian / packaging buildd
Hi! I am interested in becoming a Debian developer and have already produced a number of Debian packages, but they fall in the pet packages category referred to in another thread on this list. The most recent ones are mpf70-source and mpf70-utils, respectively the source for a kernel module (builds with make-kpkg) and some userspace utilities for the MPman MP-F70 portable MP3 player: deb http://dev.jerryweb.org/debian ./ deb-src http://dev.jerryweb.org/debian ./ As far as I can tell, these packages are pretty much ready, but I am putting them on hold until someone else expresses interest in them, so as not to clutter the Debian archive pointlessly. In the meantime, I think I've found something to sink my teeth in, namely packaging buildd. I realise it's a big bugger, but as packaging it seems to have been on the TODO list for a while I suppose any work I put into it is that much done.. I am looking for a contact from the buildd team to ask whether I can rename some files, or whether this is not a purely Debian package and needs to be handled like a package with an upstream and a Debian diff. Jeremy -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://mpf70.sourceforge.net/: MPman MP-F70 support for Linux
