Wrapper script
Hi everyone, I ITP a package that provides a single binary that expects its input file named in a special way, and writes two files with fixed names. One of those is only temporary and not really usefull, so one usually deletes it. I thought of writing a wrapper script, so the user can give the input and output filename, the renaming would be done by the script, as well as taking care of not overriding files if they already exist. Are there any guideline how this is done? I've seen packages using foo.bin for the original binary and foo for the wrapper script, or some using a different location such as /usr/lib/foo/bin for the binary. Or should one leave the binary as foo to provide the know behavior and use foo-wrapper for the script? I'd also be glad if you could point me out to some good source of how to use /tmp in a secure way in scripts; I'd like to run the binary there because I'm not a fan of joking around in the filesystem. (IIRC, tools like pdfjam do so as well.) Any advise would be very welcome! Best regards, Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Removing an obsolete symlink
Hi all, I could use some advice on how to handle the following situation. I adopted a web application package that used to set a symlink under /var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good: we shouldn't touch /var/www and not enable phpmyadmin without asking. So now I have the better way of asking the user which webserver to configure, and drop a symlink under the respective /etc/apache-flavour/conf.d dirs. My question is how to deal with this legacy symlink. I can just rm it on upgrade, but the admin might have put a different symlink there, or depends on the symlink to keep phpmyadmin configured. Shall I just leave the symlink there for upgrades, or do something with it, if so, what? Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
Hi! I am looking for a sponsor for my package avelsieve. I've taken a look at this package. It looks very good in general! I have some comments though: * 01_foldersort_bugfix.patch: the patch does not contain a description, neither in the DP-header nor in the code itself. What does it do? Did you forward it to upstream? * Why don't you disable the plugin on package removal/purge? * Make sure your postrm also works correctly if squirrelmail and/or debconf have already been purged. * It makes sense to install doc/NEWS not as a doc but as the upstream changelog, by changing dh_installchangelogs to dh_installchangelogs doc/NEWS. I'm willing to sponsor it if you could review these items. thanks, Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing an obsolete symlink
On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote: My question is how to deal with this legacy symlink. I can just rm it on upgrade, but the admin might have put a different symlink there, or depends on the symlink to keep phpmyadmin configured. Remove it on upgrade if it still points to the same place (check with readlink) and document the change in NEWS.Debian? Thijs -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Meshlab and Qutemol
Hi all, I was looking for free software to work with STL-files [1] used in rapid prototyping and found Meshlab [2], which is pretty nice, at least for viewing and converting meshes from one format to another (BTW if someone knows of a free software 3D CAD program, please let me know). [1] http://en.wikipedia.org/wiki/STL_(file_format) [2] http://meshlab.sourceforge.net/ AFAIK, there is nothing else in Debian or Ubuntu for viewing these files (apart from converting to something like VRML with e.g. admesh), so packaging Meshlab would be worthwhile. Maybe it could also be used to visualize some types of medical imaging data. Meshlab depends on the VCG library [3], which is also used in a molecular graphics program Qutemol [4], all written by the same group. Qutemol has very impressive graphics output and would be a nice addition to Debian / Ubuntu as well, but needs modern OpenGL hardware which I don't have access to at the moment. [3] http://vcg.sourceforge.net [4] http://qutemol.sourceforge.net/ I could go on and package Meshlab with a static copy of VCG included, but if there's someone with suitable hardware, time and interest to package Qutemol, then maybe VCG should be in a separate package. Anybody interested? Best, Teemu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
Hi Thijs! Thijs Kinkhorst wrote: I've taken a look at this package. It looks very good in general! I have some comments though: Thanks for that! * 01_foldersort_bugfix.patch: the patch does not contain a description, neither in the DP-header nor in the code itself. What does it do? Did you forward it to upstream? Well, I don't know where to describe that. The upstream author works on squirrelmail, too. He said the bug was in squirrelmail itself and he tries to fix it there. If that does not work correctly he will include my patch in the next version of avelsieve. The patch just sorts the mailbox folders when creating new rules. So it's nothing heavy ;) * Why don't you disable the plugin on package removal/purge? Sorry, this was just a mistake. * Make sure your postrm also works correctly if squirrelmail and/or debconf have already been purged. Okay, testing for squirrelmail-configure is no problem, i've done that now. But how do I change the script that it's working correctly without debconf? Testing on db_input and db_go, too? And what could I do with db_purge? That is needed when purging after usage of debconf, isn't it? * It makes sense to install doc/NEWS not as a doc but as the upstream changelog, by changing dh_installchangelogs to dh_installchangelogs doc/NEWS. Changed that. I'm willing to sponsor it if you could review these items. I'm glad! :) Sorry 'cause my beginners questions... Regards, Hauke PS: I built it again, you can find it at the same place... http://downloads.jhr-online.de/avelsieve/ signature.asc Description: OpenPGP digital signature
Re: RFS: avelsieve
On Tue, April 24, 2007 12:40, Jan Hauke Rahm wrote: * 01_foldersort_bugfix.patch: the patch does not contain a description, neither in the DP-header nor in the code itself. What does it do? Did you forward it to upstream? Well, I don't know where to describe that. The upstream author works on squirrelmail, too. He said the bug was in squirrelmail itself and he tries to fix it there. If that does not work correctly he will include my patch in the next version of avelsieve. The patch just sorts the mailbox folders when creating new rules. So it's nothing heavy ;) Yes, Alexandros indeed works on SquirrelMail aswell. You can describe what a patch does in the lines that start with ## DP: in the patch file. That makes sure that if someone else takes a look at your package they'll know what the patch is about. Okay, testing for squirrelmail-configure is no problem, i've done that now. But how do I change the script that it's working correctly without debconf? Testing on db_input and db_go, too? And what could I do with db_purge? That is needed when purging after usage of debconf, isn't it? In the rare case that debconf is purged before your package, your package should make a best effort to purge as much as it can. Try something like this: if [ -f /usr/share/debconf/confmodule ]; then . /usr/share/debconf/confmodule [do debconf stuff] fi or if necessary, do only this for including the debconf confmodule and use || true to make sure db_purge does not fail when the confmodule is missing. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing an obsolete symlink
Am Dienstag, den 24.04.2007, 11:38 +0200 schrieb Thijs Kinkhorst: I could use some advice on how to handle the following situation. I adopted a web application package that used to set a symlink under /var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good: we shouldn't touch /var/www and not enable phpmyadmin without asking. Why? What is so bad with this symlink? Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing an obsolete symlink
On Tue, 24 Apr 2007 13:10:59 +0200, Daniel Leidert wrote: I adopted a web application package that used to set a symlink under /var/www: /var/www/phpmyadmin - /usr/share/phpmyadmin. This was not good: we shouldn't touch /var/www and not enable phpmyadmin without asking. Why? What is so bad with this symlink? E.g. that I don't want to have phpmyadmin publically accessible under DOCUMENT_ROOT/phpmyadmin; and that it's re-created on each and every update of the package. I applaud the idea to remove this annoying symlink from the package. Cheers, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-Hailing frequencies open, Captain. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
Thijs Kinkhorst schrieb: Yes, Alexandros indeed works on SquirrelMail aswell. You can describe what a patch does in the lines that start with ## DP: in the patch file. That makes sure that if someone else takes a look at your package they'll know what the patch is about. I'm still learning... :) thanks! Try something like this: if [ -f /usr/share/debconf/confmodule ]; then . /usr/share/debconf/confmodule [do debconf stuff] fi or if necessary, do only this for including the debconf confmodule and use || true to make sure db_purge does not fail when the confmodule is missing. Okay, I changed that, too. You can find the new package again at http://downloads.jhr-online.de/avelsieve/ Hauke signature.asc Description: OpenPGP digital signature
Re: Removing an obsolete symlink
On Tue, April 24, 2007 13:10, Daniel Leidert wrote: we shouldn't touch /var/www and not enable phpmyadmin without asking. Why? What is so bad with this symlink? - It touches /var/www which is under the administrator's control; - It does not make sense, since the document root might be somewhere else; - The administrator might want to run the webapp on some vhost and specifically not on the host that is served from /var/www; - It enables the webapp automatically with no good way to disable it; - It's not conformant with the Debian webapps policy. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
On Tue, April 24, 2007 13:34, Jan Hauke Rahm wrote: Okay, I changed that, too. You can find the new package again at http://downloads.jhr-online.de/avelsieve/ It looks fine, thanks for the quick response. I have one question remaining: you depend on cyrus being installed. Is it actually necessary to have cyrus on the local host, or can it also be remote? Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
Thijs Kinkhorst schrieb: It looks fine, thanks for the quick response. I have one question remaining: you depend on cyrus being installed. Is it actually necessary to have cyrus on the local host, or can it also be remote? I'm not sure about that. Sieve is connected through port 2000, I guess that's possible remotely, too. I changed that dependency to recommends, you're probably right... Hauke http://downloads.jhr-online.de/avelsieve/ (Sorry for double mail to you, Thijs! I forgot to redirect it to the list.) signature.asc Description: OpenPGP digital signature
Re: Meshlab and Qutemol
On Tue, 24 Apr 2007, Teemu Ikonen wrote: ... I could go on and package Meshlab with a static copy of VCG included, but if there's someone with suitable hardware, time and interest to package Qutemol, then maybe VCG should be in a separate package. Sounds good. I personally would prefer if you would split VCG in any case because I'm a big fan of modularized packaging. Anybody interested? Well, do you want to know whether somebody is interested or whether somebody would like to start real work on it. Interest on my side yes, but these projects would definitely not on top of my todo list. Sponsoring is no problem. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing an obsolete symlink
On Tue, Apr 24, 2007 at 10:10:29AM +, Sam Morris wrote: On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote: My question is how to deal with this legacy symlink. I can just rm it on upgrade, but the admin might have put a different symlink there, or depends on the symlink to keep phpmyadmin configured. Remove it on upgrade if it still points to the same place (check with readlink) and document the change in NEWS.Debian? And echo Removing link: $l = $m 2 in postinst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wrapper script
On Tue, Apr 24, 2007 at 11:33:15AM +0200, Manuel Prinz wrote: Hi everyone, I ITP a package that provides a single binary that expects its input file named in a special way, and writes two files with fixed names. One of those is only temporary and not really usefull, so one usually deletes it. I thought of writing a wrapper script, so the user can give the input and output filename, the renaming would be done by the script, as well as taking care of not overriding files if they already exist. Okay, it would be good to provide an option to inhibit deletion of the file, and it would be good if the renames would be guaranteed to be on the same filesystem and thus atomic. Also be sure to use exec if this is a shells script, so you don't have a needless bash process which is hanging around just going to do wait(); exit(); Are there any guideline how this is done? I've seen packages using foo.bin for the original binary and foo for the wrapper script, or some using a different location such as /usr/lib/foo/bin for the binary. Or should one leave the binary as foo to provide the know behavior and use foo-wrapper for the script? These are all possibilities from which to choose depending on your goals. Another possibility is to make source changes to support --input, --output, --[no-]remove. I'd also be glad if you could point me out to some good source of how to use /tmp in a secure way in scripts; The important thing is that (at a low level) you open files with O_CREAT|O_EXCL. If you do this, it is safe: you won't clobber any existing file. If you don't, it is unsafe. See also this manpages bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368501 I'd like to run the binary there because I'm not a fan of joking around in the filesystem. Check if TMPDIR is set, and use it instead. Any advise would be very welcome! The Debian tools to create tempfiles are tmpfile and mktemp. These will use /tmp by default, and handle TMPDIR. Or, if you put the tempfiles in the same dir as the final pathnames, then you can do mv and it will be atomic. Or, you can use mkdtemp -d to make a directory directly below the final pathname (also guaranteed to be on the same FS). Since it's a new dir, you can assume it's empty. If ther user modifies things in it you can assume they know what they're doing. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: avelsieve
On Tue, April 24, 2007 14:10, Jan Hauke Rahm wrote: Thijs Kinkhorst schrieb: It looks fine, thanks for the quick response. I have one question remaining: you depend on cyrus being installed. Is it actually necessary to have cyrus on the local host, or can it also be remote? I'm not sure about that. Sieve is connected through port 2000, I guess that's possible remotely, too. I changed that dependency to recommends, you're probably right... Uploaded, thanks for your work! Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wrapper script
Am Dienstag, den 24.04.2007, 08:29 -0400 schrieb Justin Pryzby: On Tue, Apr 24, 2007 at 11:33:15AM +0200, Manuel Prinz wrote: [...] Are there any guideline how this is done? I've seen packages using foo.bin for the original binary and foo for the wrapper script, or some using a different location such as /usr/lib/foo/bin for the binary. Or should one leave the binary as foo to provide the know behavior and use foo-wrapper for the script? These are all possibilities from which to choose depending on your goals. Another possibility is to make source changes to support --input, --output, --[no-]remove. Unfortunately, this is not easily possible due to limitations in Fortran. This would require a recent Fortran compiler that supports Fortran2003, which is AFAIK not standard. (I can just say from my own experience.) We have those in Debian, but I'm not sure about other distributions. The program as is compiles fine with F77 compilers, so I thought it may be easier to enhance functionality by a shell script, as suggested by upstream. [...] The Debian tools to create tempfiles are tmpfile and mktemp. These will use /tmp by default, and handle TMPDIR. Or, if you put the tempfiles in the same dir as the final pathnames, then you can do mv and it will be atomic. Or, you can use mkdtemp -d to make a directory directly below the final pathname (also guaranteed to be on the same FS). Since it's a new dir, you can assume it's empty. If ther user modifies things in it you can assume they know what they're doing. Thanks for the pointers, that was what I'm looking for! Best regards, Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: RFS: avelsieve
Thijs Kinkhorst schrieb: Uploaded, thanks for your work! I'm a little bit proud 'cause this is my first package :) Thank YOU for YOUR work - at all and especially at my package! Hauke signature.asc Description: OpenPGP digital signature
Re: staying in stable but compiling for sid
Am 2007-04-13 22:50:23, schrieb Steve Kemp: These two choices suffer in that you can't get a graphical environment within them. So if you build a package for sid which used Xorg you couldn't test it. This is definitivly wrong because thr output of mount of my Devel- Station: --- /dev/sda1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda3 on /tmp type ext3 (rw) /dev/sda4 on /Chroot-Backups type ext3 (rw) /dev/sdb1 on /PostgreSQL type ext3 (rw) /dev/sdb2 on /Chroot-Archive type ext3 (rw) /dev/sdg1 on /usr/src type ext3 (rw) usbfs on /proc/bus/usb type usbfs (rw) samba3.private.tamay-dogan.net:/home on /home type nfs (rw,bg,hard,intr,tcp,vers=3,rsize=8192,wsize=8192,addr=192.168.0.69) /dev/sdc1 on /Chroot-999-sid type ext3 (rw) /dev/sdc3 on /Chroot-999-sid/var type ext3 (rw) /dev/sdc4 on /Chroot-999-sid/var/log type ext3 (rw) /dev on /Chroot-999-sid/dev type none (rw,bind) /proc on /Chroot-999-sid/proc type none (rw,bind) /sys on /Chroot-999-sid/sys type none (rw,bind) /usr/src on /Chroot-999-sid/usr/src type none (rw,bind) /PostgreSQL on /Chroot-999-sid/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-999-sid/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-999-sid/Chroot-Archive type none (rw,bind) /home on /Chroot-999-sid/home type none (rw,bind) /dev/sdd1 on /Chroot-4.0-etch type ext3 (rw) /dev/sdd3 on /Chroot-4.0-etch/var type ext3 (rw) /dev/sdd4 on /Chroot-4.0-etch/var/log type ext3 (rw) /dev on /Chroot-4.0-etch/dev type none (rw,bind) /proc on /Chroot-4.0-etch/proc type none (rw,bind) /sys on /Chroot-4.0-etch/sys type none (rw,bind) /usr/src on /Chroot-4.0-etch/usr/src type none (rw,bind) /PostgreSQL on /Chroot-4.0-etch/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-4.0-etch/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-4.0-etch/Chroot-Archive type none (rw,bind) /home on /Chroot-4.0-etch/home type none (rw,bind) /dev/sde1 on /Chroot-3.1-sarge type ext3 (rw) /dev/sde3 on /Chroot-3.1-sarge/var type ext3 (rw) /dev/sde4 on /Chroot-3.1-sarge/var/log type ext3 (rw) /dev on /Chroot-3.1-sarge/dev type none (rw,bind) /proc on /Chroot-3.1-sarge/proc type none (rw,bind) /sys on /Chroot-3.1-sarge/sys type none (rw,bind) /usr/src on /Chroot-3.1-sarge/usr/src type none (rw,bind) /PostgreSQL on /Chroot-3.1-sarge/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-3.1-sarge/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-3.1-sarge/Chroot-Archive type none (rw,bind) /home on /Chroot-3.1-sarge/home type none (rw,bind) /dev/sdf1 on /Chroot-3.0-woody type ext3 (rw) /dev/sdf3 on /Chroot-3.0-woody/var type ext3 (rw) /dev/sdf4 on /Chroot-3.0-woody/var/log type ext3 (rw) /dev on /Chroot-3.0-woody/dev type none (rw,bind) /proc on /Chroot-3.0-woody/proc type none (rw,bind) /sys on /Chroot-3.0-woody/sys type none (rw,bind) /usr/src on /Chroot-3.0-woody/usr/src type none (rw,bind) /PostgreSQL on /Chroot-3.0-woody/PostgreSQL type none (rw,bind) /Chroot-Backups on /Chroot-3.0-woody/Chroot-Backups type none (rw,bind) /Chroot-Archive on /Chroot-3.0-woody/Chroot-Archive type none (rw,bind) /home on /Chroot-3.0-woody/home type none (rw,bind) --- and now the pstree -pan --- init,1 ??(keventd,2) ??(ksoftirqd_CPU0,3) ??(kswapd,4) ??(bdflush,5) ??(kupdated,6) ??(ahc_dv_0,18) ??(scsi_eh_0,19) ??(kjournald,49) ??(khubd,214) ??(kcopyd,234) ??(kjournald,261) ??(kjournald,262) ??(kjournald,263) ??(kjournald,264) ??(kjournald,265) ??portmap,325 ??syslogd,633 ??klogd,636 ??inetd,648 ??postmaster,707 -D /PostgreSQL/data_7.4 ??? ??postmaster,712 ??? ??postmaster,713 ??pg_autovacuum,718 -D -p 5432 -L /var/log/postgresql/autovacuum_log ??sshd,725 ??? ??sshd,2759 ??? ??sshd,2761 ??? ??bash,2784 ??? ??pstree,3030 -pan ??rpc.statd,730 ??atd,733 ??cron,736 ??rplayd,744 --forward=michelle1.private.tamay-dogan.net ??(rpciod,747) ??(lockd,748) ??(kjournald,756) ??(kjournald,760) ??(kjournald,764) ??(kjournald,778) ??(kjournald,782) ??(kjournald,786) ??(kjournald,800) ??(kjournald,804) ??(kjournald,808) ??(kjournald,821) ??(kjournald,825) ??(kjournald,829) ??wdm,881 ??? ??XFree86,31725 :4 vt12 -nolisten TCP -auth /var/lib/wdm/authdir/authfiles/A:4-VM8TKT ??? ??wdm,31726 ??? ??wdmLogin,31819 -d:4 -wdefault:fvwm2 -l/usr/share/pixmaps/200x130.wdm.woody.oldstable.xpm -bsolid:Gray85 -a ??wdm,1032 ??? ??wdm,1033 ??? ??XFree86,1035 :3 vt11
[RFS] Bug#406168: xbmbrowser -- A light Browser for Pixmaps and Bitmaps
Thanks.
- Forwarded message from Michelle Konzack [EMAIL PROTECTED] -
Date: Fri, 9 Feb 2007 16:21:16 +0100
From: Michelle Konzack [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: [RFS] Bug#406168: xbmbrowser -- A light Browser for Pixmaps and Bitmaps
User-Agent: Mutt/1.5.9i
retitle 406168 Bug#406168: RFS: xbmbrowser -- A light Browser for Pixmaps and
Bitmaps
--
* Package name: xbmbrowser
Version : 5.1-10
Upstream Author : Anthony Thyssen [EMAIL PROTECTED]
(I have tried to contact him without success)
* URL : http://mentors.debian.net/
* License : This program while available in the X windows
Contrib Area, still belongs to the programmers.
Permission is however given for you to freely
copy, distribute and modify it on the condition
that this and all other copyright notices remain
unchanged in all distributions. Modifications
should be forwarded to the Current Programmer
(anthony) for inclusion into the next release.
Programming Lang: C
Description : A light Browser for Pixmaps and Bitmaps
XbmBrowser was already up to Sarge in the Debian GNU/Linux Distribution
and was orpahed on 2005-07-29 by the Debian QA-Team since no one want
to maintain it. For some weeks I have installed a new workststion and
found out, that xbmbrowser is not more availlable...
After searching the BTS I have considered to download the last Debian
version 5.1-8.2 solved three bugs build the package, made the lintian
test (terminated with success) and installed it.
It works like expected.
The last Changelog is:
xbmbrowser (5.1-10) unstable; urgency=low
* Forgotten to change the current maintainer in debian/copyright.
* Converted debian/changelog to utf-8
* Added forgotten Build-Depends
* Correcting two unquoted Strings in xbmbrowser.menu
* Correcting errors in xbmbrowser.{prerm,postrm,postinst}
* Added missing include stdlib.h to xbmbrowser.c
-- Michelle Konzack [EMAIL PROTECTED] Wed, 10 Jan 2007 23:44:08 +0100
xbmbrowser (5.1-9) unstable; urgency=low
* Since it was orphaned in 2005-07-29 I push it back because I and some
other peoples need it.
* Rewrite of debian/rules to use debhelper.
* Correcting (Bug#153147) and changing x-terminal-editor to
x-terminal-emulator in all xbmbrowser menu files
* Moved /usr/share/xbmbrowser/xbmbrowser.menu to /etc/xbmbrowser.menu
and configured it as config file. I can not support the wish to enlarge
the global menu to /usr/lib/tkdesk/... links, since it would mean, that
I have to add another directories too (this can be done by USER configs).
But however, I have included an heavy updated /etc/xbmbrowser.menu with
more security and overwrite protection. (closes: #18005)
* Patch from Andree Leidenfrost [EMAIL PROTECTED] applied.
(closes: #153153)
* Patch from A. Costa [EMAIL PROTECTED] applied. (closes: #306705)
-- Michelle Konzack [EMAIL PROTECTED] Tue, 26 Dec 2006 22:26:06 +0100
I have already uploded the package to http://mentors.debian.net/ and
searching now for a sponsor.
The only thing I have forgotten was to change the debian/copyright file
and the maintainer Info which point currently to Martin Mitchell
[EMAIL PROTECTED]
Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSM LinuxMichi
0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com)
- End forwarded message -
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack Apt. 917 ICQ #328449886
50, rue de Soultz MSN LinuxMichi
0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com)
signature.pgp
Description: Digital signature
RFS: proda
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package proda. * Package name: proda Version : 1.0-1 Upstream Author : Phuong T.M., Do C.B., Edgar R.C., Batzoglou S. * URL : http://proda.stanford.edu * License : public domain [1] Section : science It builds these binary packages: proda - multiple alignment of protein sequences The upload would fix this bug: 408347 The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/p/proda - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/p/proda/proda_1.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards David Paleino [1] it has been published in Multiple alignment of protein sequences with repeats and rearrangements. Nucleic Acids Research 2006 34(20), 5932-5942 - the full text article can be reached at http://nar.oxfordjournals.org/cgi/content/full/34/20/5932 - -- Linux Registered User #334216 Get FireFox! http://snipurl.com/gofoxygo/ Blog http://www.hanskalabs.net/ Staff http://www.debianizzati.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLiXl5qqQFxOSsXQRAm3FAJsGR06KKegkYsDS/J7N2Lmmz1lnBACfZmd/ cK1lc4ErZiM8DP8yCZHb80c= =Rsky -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: proda
Hi, * David Paleino [EMAIL PROTECTED] [2007-04-24 17:46]: I am looking for a sponsor for my package proda. * Package name: proda Version : 1.0-1 Upstream Author : Phuong T.M., Do C.B., Edgar R.C., Batzoglou S. * URL : http://proda.stanford.edu * License : public domain [1] Section : science It builds these binary packages: proda - multiple alignment of protein sequences [...] A few comments: - copyright lacks upstream email, would be good to see it there - watch file seems broken: uscan warning: In debian/watch, no matching hrefs for watch line http://proda.stanford.edu/proda_(_*)\.tar\.gz opts=uversionmangle=s/_/\./ \ http://proda.stanford.edu/proda_(.*)\.tar\.gz should be correct, shouldn't it? - you included manpage.xml but you don't convert it while building? - you have Uploader in control it has to be Uploaders - you directly patched Makefile, why not using dpatch or quilt? (or just do the rm proda and instal from within rules, patching is not really needed here and you never call distclean) Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgppekUfPYZ2D.pgp Description: PGP signature
Re: Symlink conffile?
On Tue, Apr 24, 2007 at 08:26:29PM +0200, Marc Haber wrote: From: Marc Haber [EMAIL PROTECTED] Subject: Symlink conffile? I apologize for hijacking a thread, I forgot to remove the In-Reply-To:-Header from my outgoing message. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Symlink conffile?
Hi, given the case that a conffile was moved from /etc/conffile to /etc/package/conffile. I would now like to include a transition symlink to my package. When I go the easy way, just including the symlink in the package, debhelper does not mark the link a conffile, and every /etc/conffile that might be present on the local system gets unceremoniously overwritten during package installation, causing blatant data loss. When I flag the symlink manually as a conffile, the package in uninstallable: dpkg: error processing $PACKAGE (--install): unable to change ownership of new dist ocnffile '/etc/conffile.dpkg-new': No such file or directory. Policy does not mention any issues with symlinks as conffiles, and I didn't find an appropriate bug filed against dpkg. What to do here? Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 2323190 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Removing an obsolete symlink
On Tue, 24 Apr 2007, Sam Morris wrote: On Tue, 24 Apr 2007 11:38:04 +0200, Thijs Kinkhorst wrote: My question is how to deal with this legacy symlink. I can just rm it on upgrade, but the admin might have put a different symlink there, or depends on the symlink to keep phpmyadmin configured. Remove it on upgrade if it still points to the same place (check with readlink) and document the change in NEWS.Debian? I'd personally suggest just not creating it anymore, and possibly warning once on upgrade that it exists. [If it was in the package itself as opposed to being created with a postinst script, then just don't include it anymore, and warn once that it's been removed.] Don Armstrong -- The game of science is, in principle, without end. He who decides one day that scientific statements do not call for any further test, and that they can be regarded as finally verified, retires from the game. -- Sir Karl Popper _The Logic of Scientific Discovery_ �11 http://www.donarmstrong.com http://rzlab.ucr.edu
RFS: gmailsender
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package gmailsender. * Package name: gmailsender Version : 1.3-1 Upstream Author : Lounis Bellabes [EMAIL PROTECTED] * URL : http://gmailsender.sourceforge.net * License : GPL Section : net It builds this binary package: gmailsender - simple mono-based mail sending application The package is lintian clean. The upload would fix these bugs: 334117 335175 384965 The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/g/gmailsender - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/g/gmailsender/gmailsender_1.3-1.dsc I would be glad if someone uploaded this package for me. Kind regards David Paleino P.S.: how to specify multiple bugs being closed in debian/changelog ? I'll eventually modify it if needed. - -- Linux Registered User #334216 Get FireFox! http://snipurl.com/gofoxygo/ Blog http://www.hanskalabs.net/ Staff http://www.debianizzati.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGLnZM5qqQFxOSsXQRAjsLAJ9o6rHf0tdmoKu9AFh7pAbPhxeMZACdHzrw h11ZEW6Yo/EvRZEUuBp4McA= =b0J6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: proda
Le Tue, Apr 24, 2007 at 06:46:37PM +0200, Nico Golde a écrit : Hi, * David Paleino [EMAIL PROTECTED] [2007-04-24 17:46]: I am looking for a sponsor for my package proda. * Package name: proda Version : 1.0-1 Upstream Author : Phuong T.M., Do C.B., Edgar R.C., Batzoglou S. * URL : http://proda.stanford.edu * License : public domain [1] Section : science It builds these binary packages: proda - multiple alignment of protein sequences [...] A few comments: - copyright lacks upstream email, would be good to see it there - watch file seems broken: uscan warning: In debian/watch, no matching hrefs for watch line http://proda.stanford.edu/proda_(_*)\.tar\.gz opts=uversionmangle=s/_/\./ \ http://proda.stanford.edu/proda_(.*)\.tar\.gz should be correct, shouldn't it? - you included manpage.xml but you don't convert it while building? - you have Uploader in control it has to be Uploaders - you directly patched Makefile, why not using dpatch or quilt? (or just do the rm proda and instal from within rules, patching is not really needed here and you never call distclean) Dear David, it seems that you have adressed most of Nico's points in a revised version uploaded to mentors. It is very clean, I just have a few comments: About debian/rules: - The configure rule is mandatory, but in this case, we do not need it to contain anything. - I would tend to remove the template's comments, but this is up to your taste. - Similarly, you can safely remove lines such as # dh_installmenu, as we can be 99.9 % sure that they will not be useful in the future. - You can give arguments to dh_clean and dh_install, then you do not need the rm -f and the install commands. (This is again up to your taste). - Giving an argument to dh_installdirs, you would not need debian/dirs anymore. About proda.1: - As you built it from an xml source, I think that it is important to provide its sourcce in the package. - You can rebuild it at each package building, it does not take so much CPU. Here is an example of debian/rules file which does this: http://svn.debian.org/wsvn/debian-med/trunk/packages/boxshade/trunk/debian/rules?op=filerev=0sc=0 - You would then need to build-depend on xsltproc, docbook-xsl, docbook-xml. - The manpage says that proda is documented by an info file, but it is not true. - I think that it is not necessary to say in the Description section that the man page was written for Debian. - As proda is in the public domain, I think that the GPL is a bit too much for the manpage. I tend to like to give a permission to use, modify, copy and redistribute as the program itself for my manpages. But it is a matter of taste. Lastly, proda is related to the probcons and amap programs, which failed to build with gcc-4.3. It means that it is likely that you would have a FTBFS bug filed by Martin Michlmayr soon after getting proda in the main archive. Depending on how playful and busy you are, you may be interested to check by yourself before getting sponsored. Have a nice day, -- Charles Plessy http://charles.plessy.org Wako, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
