Searching doc about debian dir in upstream release
Hi! I was ask by a upstream author about the debian-dir in upstream (release) thing where to find documentation about this. I did not find anything on the debian pages or via google by myself. Is there any text, paper, whatever piece of text officially available on this? Thanks for hints. Ciao Max -- Follow the white penguin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Searching doc about debian dir in upstream release
Hi, I was ask by a upstream author about the debian-dir in upstream (release) thing where to find documentation about this. All information about the 'debian'-dir should be linked here: http://www.debian.org/doc/devel-manuals Cheers, Bernd -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#419570: webcalendar: Package dependencies must allow php5 instead of php4
* Stephen Gran [EMAIL PROTECTED] [2007-04-18 01:04]: This one time, at band camp, James Westby said: That's not your job, the php maintainers have to ensure their packages work, you just have to make sure enough php/mysql/apache stuff is installed to work. Well, that's glossing it over a bit - the problem of ORed dependencies is not trivial to deal with, and there is no support in apt for it. Theoretically, these sorts of dependencies could be written with brackets or something to make a complete set soultion possible, but it's not there just yet. Is this feature under development? It would be great to be able to specify dependencies like the following (note the parentheses): Depends: ( ( ( apache | apache-ssl | apache-perl, libapache-mod-php4 ) | ( apache2, libapache2-mod-php4 ), php4-mysql | php4-pgsql ) | ( ( apache | apache-ssl | apache-perl, libapache-mod-php5 ) | ( apache2, libapache2-mod-php5 ), php5-mysql | php5-pgsql ) ) All my problems would then be solved! -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Looking for a maintainer with experience in debconf programming
James Westby [EMAIL PROTECTED] writes: On (17/04/07 22:08), Reinhard Tartler wrote: I intend to take over an existing package not being in debian yet. The original packager seems dead, at least he didn't respond me in two emails, but anyway. He used a lot of debconf in his package. I'm not a debconf pro at all, and I would feel much better if someone could look at the .postinst and the .config file of the boxbackup source package and tell me the biggest mistakes: http://siretart.tauware.de/upload-queue I have taken a very quick glance over the scripts. It appears like his implementation is pretty good, the templates look good, and the config and postinst seem fairly clean. Thank you very much for your review. However there is an option to handle the config files through debconf. It appears as though if this is enabled the config files will be overwritten unconditionally from postinst, which isn't good. I'm not sure whether they are marked as conffiles, so it might not be a policy violation, but it is definately discouraged. You may wish to look in to ucf if you would like to build on his work but avoid this problem. Ok, I'll look into this. thanks for pointer. In fact, I'm considering dropping all the debconf magic, converting the current script with a config-setup helper. I expect this would faciliate upgrades, but I'm still a bit undecided. Could you tell me what config-setup is please? No, I don't now about some software called config-setup. I would have to write a helper script which does the setup of a boxbackup site. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 pgpJxkwAPETNk.pgp Description: PGP signature
Re: Searching doc about debian dir in upstream release
On Wed, 18 Apr 2007 08:40:37 +0200 Maximilian Wilhelm [EMAIL PROTECTED] wrote: Hi! I was ask by a upstream author about the debian-dir in upstream (release) thing where to find documentation about this. Unless your package was written specifically for Debian and Debian alone, the documentation of the debian/ directory upstream reads as: Item 1: Don't package debian/* in the upstream release. Item 2: See 1. You can have it in CVS/svn/whatever, but it should not be part of the tarball release - the Debian maintainer will deal with that separately. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpEpouAhG2HR.pgp Description: PGP signature
Re: Searching doc about debian dir in upstream release
On Wed, 2007-04-18 at 08:40 +0200, Maximilian Wilhelm wrote: Hi! I was ask by a upstream author about the debian-dir in upstream (release) thing where to find documentation about this. I did not find anything on the debian pages or via google by myself. Is there any text, paper, whatever piece of text officially available on this? I'm not really sure what you mean, but I guess that by debian-dir in upstream (release) thing you mean the issue that upstream includes a debian/ dir in released tarballs. That is generally considered a bad idea. I'm not aware of documentation about this in the strict sense of the word, but here's some explanation. You can store the debian/ dir in upstream's VCS, but is is very undesirable to put it into released tarballs. It may seem handy now, but it will create a strange situation when you're no longer part of upstream, or when someone takes over package maintenance, does an NMU or a security update. You will then get a diff.gz that diffs the old and new debian directory. So: keeping it in your upstream version repository is fine, but make sure it's not released. When packaging a new upstream version, combine the tarball with the debian dir at that point. I'll have this added to the Debian Mentors FAQ. Thijs signature.asc Description: This is a digitally signed message part
Re: Bug#393832: Bug#419570: webcalendar: Package dependencies must allow php5 instead of php4
This one time, at band camp, Rafael Laboissiere said: Is this feature under development? It would be great to be able to specify dependencies like the following (note the parentheses): I know people have talked about the problem with an eye towards patching it in. I have not heard that anyone has actually produced any code. Sorry to get your hopes up :) -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: yada generated deb not calling update-menus
On Wed, Apr 18, 2007 at 12:32:25AM +0100, Tim Day wrote: I (novice deb builder) am building a deb with yada Yuck. I don't have any problems getting a sensible /usr/share/menu entry put in place, but it doesn't actually seem to appear in any menus until I do a manual sudo update-menus (or install some other package which triggers a menu update itself). When I look at the postinst file in my yada-generate deb then the only thing of note is: if [ = configure ] [ -x `which update-menus 2/dev/null` ]; then update-menus; fi ...which clearly isn't ever going to do anything! But I can't figure out what's needed to get yada to (presumably) put whatever's needed into those empty quotes so that the configure step will call update-menus. Replacing yada with something non-bletcherous. TTBOMK, the only person willfully using yada for official Debian packages is the yada author. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: yada generated deb not calling update-menus
On Wed, 2007-04-18 at 10:59 +0200, Thijs Kinkhorst wrote: I'm wondering why you, as a 'novice deb builder', chose yada as a packaging helper. I wouldn't recommend it to new packagers (or at all), because it hides large parts of the build process. Ah, but that's exactly why I chose it. I did start off trying dh scripts but thought it seemed like a lot of work for a simple install. I didn't discover yada until I got hold of the Martin Krafft Debian book, liked the look of the apparently cleaner approach and got something which seemed to work well very quickly. You can see that right here: there's code generated that doesn't work, but it's very opaque what does this, why, and how to change it. A look at an old .deb built with yada on sarge (where it worked fine wrt menus) shows it just contains if test -x /usr/bin/update-menus; then update-menus; fi Searching etch's /usr/bin/yada (perl) for update-menus finds \nif [ \$1\ = \configure\ ] ... the $1 is presumably being prematurely substituted when it should go into the postinst script intact. Aha... in fact a few lines later I can see some presumably correctly escaped \nif [ \\$1\ = \configure\ ]; I've just put in a reportbug. My only options for fixing my debs immediately seems to be patching yada or unpacking the debs and patching the affected line. I'm not sure which is more horrible. debhelper might lead to a longer debian/rules file, but it has the advatages that you actually see which steps are taken in what order, and that you can easily control what happens. Hmmm maybe I should give dh another go. Regards Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: Packaging for Debian
Hi, debian-mentors. I sent a message (below) to [EMAIL PROTECTED] about creating a new debian package. And Aníbal Monsalve Salazar [EMAIL PROTECTED] asked me for writing to debian-mentors@lists.debian.org That's what I am doing. Thank you, Anibal. I have searched on internet and seen two how-tos: 1. http://tldp.org/HOWTO/Debian-Binary-Package-Building-HOWTO/ and 2. http://www.debian.org/doc/maint-guide/ May be that's enough, but before begining my job I would like to know your opinion. Thanks, John Paul dos Santos Scott Hood. -- Forwarded message -- From: Aníbal Monsalve Salazar [EMAIL PROTECTED] Date: 17/04/2007 19:09 Subject: Re: Packaging for Debian To: John Hood [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] On Tue, Apr 17, 2007 at 02:58:17PM -0300, John Hood wrote: Hi, all. I don't know if this is the correct list. If not, forgive me. Please write to debian-mentors@lists.debian.org http://lists.debian.org/debian-mentors/ I will package a software (LBAdmin: LoadBalancer.org Appliance Administration System; http://www.loadbalancer.org) for Debian distribution. This is my first .deb package; so, I am looking for some information and orientation. Can anyone help me ? Regards, John. Aníbal Monsalve Salazar -- http://v7w.com/anibal -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGJUV+gY5NIXPNpFURAiF+AJ9Rphc7UVDyCBAID5YI/STVIksZlQCfVMU4 JxiRvo1D8S2kDpc5Qqj04lU= =K1Um -END PGP SIGNATURE-
Re: Fwd: Packaging for Debian
On Wed, Apr 18, 2007 at 09:58:00AM -0300, John Hood wrote:
[...]
1. http://tldp.org/HOWTO/Debian-Binary-Package-Building-HOWTO/
[...]
This is a quick hack for when you have already-compiled software you
want to package for personal use on Debian (commercial applications
or the like).
2. http://www.debian.org/doc/maint-guide/
[...]
This document describes how to properly package software for
inclusion into Debian, or when you want to have packages that are
rebuildable from a source package in an automated fashion.
If the latter is your goal, subscribing to the debian-mentors
mailing list to ask questions (after first searching through the
list archives for your answer) is highly recommended. Also, there's
much fine documentation to this end available from:
http://mentors.debian.net/
Hope that helps!
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP([EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]);
MUD([EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); }
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Could somebody upload rkward 0.4.7?
Hi, I maintain the rkward package, but an not a debian developer. A new upstream release is available, and should be uploaded to unstable as soon as possible. Especially, since the current version in unstable (0.4.2-2) does not work at all with the version of R in unstable (see bug #418686). Usually Roland Marcus Rutschmann sponsors the rkward uploads. However, he seems to be away from e-mail at the moment. Could somebody please upload the new packages (0.4.7-2 available at http://rkward.sourceforge.net/debian/)? Regards Thomas Friedrichsmeier pgp7oTuK4Ih2r.pgp Description: PGP signature
Re: Fwd: Packaging for Debian
Hi, * John Hood [EMAIL PROTECTED] [2007-04-18 15:26]: [...] I have searched on internet and seen two how-tos: 1. [4]http://tldp.org/HOWTO/Debian-Binary-Package-Building-HOWTO/ and 2. [5]http://www.debian.org/doc/maint-guide/ May be that's enough, but before begining my job I would like to know your opinion. Look at http://www.debian.org/doc/devel-manuals that should be enough for the beginning :) Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpopc8nAqW33.pgp Description: PGP signature
RFS: truncate
Dear mentors, I am looking for a sponsor for my package truncate. * Package name: truncate Version : 2007.03.13-1 Upstream Author : Peter Pentchev [EMAIL PROTECTED] (myself) * URL : http://devel.ringlet.net/sysutils/truncate/ * License : Two-clause BSD Section : utils It builds these binary packages: truncate - FreeBSD utility to truncate or extend the size of files The truncate utility adjusts the length of each regular file given on the command-line. This package is simply a redistribution of the utility as found in the FreeBSD base system. . Homepage: http://devel.ringlet.net/sysutils/truncate/ The package is lintian clean. The upload would fix these bugs: 415016 The package can be found on mentors.debian.net: - dget -x http://mentors.debian.net/debian/pool/main/t/truncate/truncate_2007.03.13-1.dsc Just for the record, I know about dd(1)'s seek option :) But still, truncate(1) is a useful utility in its own right, if only for the ease of invoking it and the intuitive command-line interface :) I would be glad if someone uploaded this package for me. G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. pgpamrbxzKEfo.pgp Description: PGP signature
Re: RFS: truncate
On Wed, Apr 18, 2007 at 04:53:38PM +0300, Peter Pentchev wrote: Dear mentors, I am looking for a sponsor for my package truncate. * Package name: truncate Version : 2007.03.13-1 Upstream Author : Peter Pentchev [EMAIL PROTECTED] (myself) * URL : http://devel.ringlet.net/sysutils/truncate/ * License : Two-clause BSD Section : utils [snip] The package is lintian clean. *Sigh*. And 'ere I was, thinking I'd read the template carefully and changed everything :) This one ought to say lintian and linda clean and pbuilder tested :) G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 Nostalgia ain't what it used to be. pgpIR8VerUOJT.pgp Description: PGP signature
Re: RFS: truncate
On Wed, 18 Apr 2007 16:53:38 +0300 Peter Pentchev [EMAIL PROTECTED] wrote: truncate - FreeBSD utility to truncate or extend the size of files The truncate utility adjusts the length of each regular file given on the command-line. This package is simply a redistribution of the utility as found in the FreeBSD base system. That description doesn't help explain why a file would need to be truncated (or extended without allocating space). Why truncate a file (and lose data) rather than split the file? Why extend a file without allocating space? Most (all?) file-open routines will support complete truncation to zero length, what is the advantage of retaining only a portion of the old data in the file and risk losing data integrity (because not all regular files use linear storage). XML/HTML/SGML are just three common regular file types that will react badly to arbitrary truncation and ignore extended file sizes without adding data. Don't assume that users will know anything about the FreeBSD version - you need to explain the what, why and when of using such a program without reference to assumptions based on *BSD. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpgA9ElS69he.pgp Description: PGP signature
Re: RFS: truncate
On Wed, Apr 18, 2007 at 04:53:38PM +0300, Peter Pentchev wrote: Dear mentors, I am looking for a sponsor for my package truncate. * Package name: truncate Version : 2007.03.13-1 Upstream Author : Peter Pentchev [EMAIL PROTECTED] (myself) * URL : http://devel.ringlet.net/sysutils/truncate/ * License : Two-clause BSD Section : utils It builds these binary packages: truncate - FreeBSD utility to truncate or extend the size of files The truncate utility adjusts the length of each regular file given on the command-line. This package is simply a redistribution of the utility as found in the FreeBSD base system. . Homepage: http://devel.ringlet.net/sysutils/truncate/ The package is lintian clean. Very frankly, this should go into coreutils. Having a package alone for an utility that is probably less than 100 lines of C, and that can be replaced by a single line perl script (and i'm not talking about these ugly one-liners) is a bit too much. OTOH, I've always wondered why coreutils didn't have an utility for ftruncate(). If licensing is a problem, it could be reimplemented very easily. Writing a wrapper around ftruncate() is not very difficult. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: Packaging for Debian
Thanks, Fungi and Nico.
At first moment, I just want package for personal/professional use.
I am working in a project that involves localizing/packaging the LBAdmin
software.
In the future, when packaging basics are familiar for me, I would like
properly package software for
inclusion into Debian, a more complicated job. And, may be, adopt other
packages.
Then, I will subscribe to the debian-mentors mailing list.
Helps a lot.
Thank you very much,
John.
2007/4/18, The Fungi [EMAIL PROTECTED]:
On Wed, Apr 18, 2007 at 09:58:00AM -0300, John Hood wrote:
[...]
1. http://tldp.org/HOWTO/Debian-Binary-Package-Building-HOWTO/
[...]
This is a quick hack for when you have already-compiled software you
want to package for personal use on Debian (commercial applications
or the like).
2. http://www.debian.org/doc/maint-guide/
[...]
This document describes how to properly package software for
inclusion into Debian, or when you want to have packages that are
rebuildable from a source package in an automated fashion.
If the latter is your goal, subscribing to the debian-mentors
mailing list to ask questions (after first searching through the
list archives for your answer) is highly recommended. Also, there's
much fine documentation to this end available from:
http://mentors.debian.net/
Hope that helps!
--
{ IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657);
SMTP( [EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511);
AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]);
MUD( [EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); }
Re: yada generated deb not calling update-menus
On (18/04/07 00:32), Tim Day wrote: I (novice deb builder) am building a deb with yada (and pbuilder) on Etch. I don't have any problems getting a sensible /usr/share/menu entry put in place, but it doesn't actually seem to appear in any menus until I do a manual sudo update-menus (or install some other package which triggers a menu update itself). When I look at the postinst file in my yada-generate deb then the only thing of note is: if [ = configure ] [ -x `which update-menus 2/dev/null` ]; then update-menus; fi That should be $1 (or is it $2?) in the first set of quotes. Whatever is writing this out is probably a shell or perl script that isn't escaping it. I don't have internet access to check your script now though. Thanks, James -- James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/ seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: echroot
The diversity is one of the attractiveness of free software, I see very interesting echroot J. M. Bustillo 2007/4/17, Mike Hommey [EMAIL PROTECTED]: On Tue, Apr 17, 2007 at 09:24:42PM +0900, Junichi Uekawa [EMAIL PROTECTED] wrote: Hi, I am looking for a sponsor for my package echroot. echroot extends the basic options that we found in chroot, with echroot we can control many more options than executing chroot. Here I show some of the options that we can happen to echroot. What is the advantage of running a chroot not as root? Personally, I'm touched by this because I'm always forced to use 'su' alongside 'chroot'. Being root inside chrooted environment really is useless. There are dchroot and schroot which can do pretty fancy stuff. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: echroot
Hi, * José Manuel Bustillo [EMAIL PROTECTED] [2007-04-18 21:35]: The diversity is one of the attractiveness of free software, I see very interesting echroot I don't see diversity here apart from the name. Kind regards Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpbCGCBLisr0.pgp Description: PGP signature
Re: RFS: truncate
Mike Hommey wrote: Very frankly, this should go into coreutils. Or bsdmaintutils/bsdutils? -- Chris Lamb, Leamington Spa, UK GPG: 0x634F9A20 signature.asc Description: PGP signature
Re: Bug#393832: Bug#419570: webcalendar: Package dependencies must allow php5 instead of php4
* Stephen Gran [EMAIL PROTECTED] [2007-04-18 11:14]: This one time, at band camp, Rafael Laboissiere said: Is this feature under development? It would be great to be able to specify dependencies like the following (note the parentheses): I know people have talked about the problem with an eye towards patching it in. I have not heard that anyone has actually produced any code. Do you remember where this discussion took place? -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: truncate
On Wed, Apr 18, 2007 at 03:27:09PM +0100, Neil Williams wrote: On Wed, 18 Apr 2007 16:53:38 +0300 Peter Pentchev [EMAIL PROTECTED] wrote: truncate - FreeBSD utility to truncate or extend the size of files The truncate utility adjusts the length of each regular file given on the command-line. This package is simply a redistribution of the utility as found in the FreeBSD base system. That description doesn't help explain why a file would need to be truncated (or extended without allocating space). Why truncate a file (and lose data) rather than split the file? Why extend a file without allocating space? Most (all?) file-open routines will support complete truncation to zero length, what is the advantage of retaining only a portion of the old data in the file and risk losing data integrity (because not all regular files use linear storage). XML/HTML/SGML are just three common regular file types that will react badly to arbitrary truncation and ignore extended file sizes without adding data. Don't assume that users will know anything about the FreeBSD version - you need to explain the what, why and when of using such a program without reference to assumptions based on *BSD. Argh. Yep, come to think of it, this brief description could be kinda misread this way :) Actually, the reference to FreeBSD was more of a recognition of the truncate original authors, not a usage reference or anything - but you're right, in the absence of any usage references at all... Actually, the reason that pushed me to port truncate(1) to Debian was the need to create a large empty file while tracking down a problem with a webserver's large file support. Other than that, I've used it to initialize loopback-mount filesystems, maim lastlog files and news spool indices by only leaving the headers, and sudo truncate -s0 file as an easier-on-the-fingers alias for sudo sh -c ': file' :) So... what do you think about the following description? Or should I file a wishlist bug against bsdmainutils to get truncate(1) included there? The truncate utility adjusts the length of each regular file given on the command-line. It may be used to create sparse files (zero-filled files that do not take up any space on disk) for virtual filesystems, empty data files, or simply large files for testing. It may also empty a file by setting its size to 0 bytes, or remove all but a portion of the data, most useful when the file has a well-known record-based structure like e.g. filesystem images, news spools, utmp or sa(8) accounting files, graphics images, etc. . This package is simply a redistribution of the truncate utility as found in the FreeBSD base system. . Homepage: http://devel.ringlet.net/sysutils/truncate/ Thank you and the others for the prompt replies and comments! G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 because I didn't think of a good beginning of it. pgpjHTGPWzElK.pgp Description: PGP signature
Re: yada generated deb not calling update-menus
On Wed, 2007-04-18 at 17:13 +0100, James Westby wrote: On (18/04/07 00:32), Tim Day wrote: When I look at the postinst file in my yada-generate deb then the only thing of note is: if [ = configure ] [ -x `which update-menus 2/dev/null` ]; then update-menus; fi That should be $1 (or is it $2?) in the first set of quotes. Whatever is writing this out is probably a shell or perl script that isn't escaping it. I don't have internet access to check your script now though. That does seem to be the problem; there's bug #419878 in for it now. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Searching doc about debian dir in upstream release
Bernd Zeimetz [EMAIL PROTECTED] writes: I was ask by a upstream author about the debian-dir in upstream (release) thing where to find documentation about this. All information about the 'debian'-dir should be linked here: http://www.debian.org/doc/devel-manuals I think the OP is asking about the case where the upstream developer has added a 'debian/' directory to the source code, and what the maintainer of the Debian package should do about that. -- \ My interest is in the future, as I am going to spend the rest | `\ of my life there. -- Charles F. Kettering | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
