removing and adding dynamically assigned system users

hi, i am currently building a package which needs a system user. so i use dynamically assigend system users (range 100-999). i install it with adduser --system etc. now, when a package is deinstalled, when is the user removed from the database ? when postrm remove is called or is it postrm purge?

uploading to proposed-updates

hi, i have a bugreport for a package which is solved in a new version. and the bug report told me that it is fixed in the new package. it's a woody package but compiled for potato but shouldn't be a problem because it only depends on libc6. so, know this would be a reason to be included into propo

Re: Adoption

hi, On Fri, Nov 17, 2000 at 12:19:44PM -0800, Ian Eure wrote: > hi. when i adopt a package, should i keep the changelog from the previous > maintainer? yes, just note that you adapted the package and continue with the changelog. so long Othmar

shlibs control file when there aren't actual shared libs

hi, my package, modlogan, uses .so files, like actual libs, but not aimed at someone else but just for the program (modlogan). well, since it also doesn't have version numbers or something else, and it also doesn't need this, but lintian complains that there isn't a shlibs control file. i simply d

Re: creating man pages

hi, On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote: > What's the "best" way of maintaining or creating a man page? > I'll be needing to do that with some of my packages, but it just occurred to > me I don't actually know how, apart from cutting and pasting in a text > editor. My gue

Re: creating man pages

Hi, On Wed, Dec 13, 2000 at 09:35:09AM +0100, Adrian Bunk wrote: > If you are are writing nroff I'd suggest using gmanedit: well, vi{,m}/emacs/any other editor is also good enough for it :). depends what you like. so long Othmar

handling patches

hi, how should one treat patches which aren't upstream, like backports of a later release to the stable version? is there a recommended way? or how are people treating it? or people tell me how they do it and i can try the solutions and use the one i feel comfortable with. so long and thanks Othm

handling configfiles

hi, i have to deal myself with replacing/etc. config files since they are generated in the postinst script. is there a package which is suitable for taking this as an example? the formal description in debian-policy is a bit too formal so that it is possible that i misunderstand things. so looking

Re: handling configfiles

hi, On Sat, Mar 03, 2001 at 02:56:58AM -1000, Brian Russo wrote: > You lost me I'm afraid, what exactly is it you're trying to do? ok, from the beginning. i build a config file from the postinst script. since i do this, i can't use conffile. therefore i have to deal with certain installation situ

Re: Creating man pages (upstream does not have one)

hi, On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote: > What programs should I use to create one? the normal groff and the an macro (on the commandline that's the -man ;)) ... read the manpage howto as a start and also read man 7 man ... so long Othmar

Re: Creating man pages (upstream does not have one)

hi, On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote: > I would recommend to write them in the POD (Plain Old Documentation) > format which makes it very seasy to write/update a man page. > (see http://qa.debian.org/man-pages.html for pointers to documentations). haven't dealt

dpkg tries to remove a config file twice ...

hi, i generate a config file in my postinst, hence it's not marked as a conffile. so if the package is purged i have to remove it by hand in the postinst: # purge the config file which is created in the postinst script if [ "$1" = purge ] ; then rm /etc/modlogan/modlogan.conf fi ok, i've

Re: dpkg tries to remove a config file twice ...

hi, On Mon, May 21, 2001 at 08:10:59PM +0200, Robert Bihlmeyer wrote: > > Change it to "rm -f ...". That way, you wont get an error. You should do > > it this way anyway, else your package becomes uninstallable if the user > > removes the file before removing the package. > It's not only a good id

removing and adding dynamically assigned system users

hi, i am currently building a package which needs a system user. so i use dynamically assigend system users (range 100-999). i install it with adduser --system etc. now, when a package is deinstalled, when is the user removed from the database ? when postrm remove is called or is it postrm purge?

uploading to proposed-updates

hi, i have a bugreport for a package which is solved in a new version. and the bug report told me that it is fixed in the new package. it's a woody package but compiled for potato but shouldn't be a problem because it only depends on libc6. so, know this would be a reason to be included into prop

Re: Adoption

hi, On Fri, Nov 17, 2000 at 12:19:44PM -0800, Ian Eure wrote: > hi. when i adopt a package, should i keep the changelog from the previous > maintainer? yes, just note that you adapted the package and continue with the changelog. so long Othmar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] w

shlibs control file when there aren't actual shared libs

hi, my package, modlogan, uses .so files, like actual libs, but not aimed at someone else but just for the program (modlogan). well, since it also doesn't have version numbers or something else, and it also doesn't need this, but lintian complains that there isn't a shlibs control file. i simply

Re: creating man pages

hi, On Wed, Dec 13, 2000 at 08:35:45AM +1100, Drew Parsons wrote: > What's the "best" way of maintaining or creating a man page? > I'll be needing to do that with some of my packages, but it just occurred to > me I don't actually know how, apart from cutting and pasting in a text > editor. My gu

Re: creating man pages

Hi, On Wed, Dec 13, 2000 at 09:35:09AM +0100, Adrian Bunk wrote: > If you are are writing nroff I'd suggest using gmanedit: well, vi{,m}/emacs/any other editor is also good enough for it :). depends what you like. so long Othmar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject o

handling patches

hi, how should one treat patches which aren't upstream, like backports of a later release to the stable version? is there a recommended way? or how are people treating it? or people tell me how they do it and i can try the solutions and use the one i feel comfortable with. so long and thanks Oth

handling configfiles

hi, i have to deal myself with replacing/etc. config files since they are generated in the postinst script. is there a package which is suitable for taking this as an example? the formal description in debian-policy is a bit too formal so that it is possible that i misunderstand things. so lookin

Re: handling configfiles

hi, On Sat, Mar 03, 2001 at 02:56:58AM -1000, Brian Russo wrote: > You lost me I'm afraid, what exactly is it you're trying to do? ok, from the beginning. i build a config file from the postinst script. since i do this, i can't use conffile. therefore i have to deal with certain installation sit

Re: Creating man pages (upstream does not have one)

hi, On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote: > What programs should I use to create one? the normal groff and the an macro (on the commandline that's the -man ;)) ... read the manpage howto as a start and also read man 7 man ... so long Othmar -- To UNSUBSCRIBE, ema

Re: Creating man pages (upstream does not have one)

hi, On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote: > I would recommend to write them in the POD (Plain Old Documentation) > format which makes it very seasy to write/update a man page. > (see http://qa.debian.org/man-pages.html for pointers to documentations). haven't dealt

dpkg tries to remove a config file twice ...

hi, i generate a config file in my postinst, hence it's not marked as a conffile. so if the package is purged i have to remove it by hand in the postinst: # purge the config file which is created in the postinst script if [ "$1" = purge ] ; then rm /etc/modlogan/modlogan.conf fi ok, i've

Re: dpkg tries to remove a config file twice ...

hi, On Mon, May 21, 2001 at 08:10:59PM +0200, Robert Bihlmeyer wrote: > > Change it to "rm -f ...". That way, you wont get an error. You should do > > it this way anyway, else your package becomes uninstallable if the user > > removes the file before removing the package. > It's not only a good i

dpkg-shlibdeps strange messages and lintian error (rpath)

hi, first, dpkg-shlibdeps checks a few shared objects files which resides in the packages own subdir in /usr/lib, since they are just some sort of plugins, but shlibdeps complains: dpkg-shlibdeps: warning: format of libmla_mdata_netmask.so not recognized and this without about a dozen of files.

Re: dpkg-shlibdeps strange messages and lintian error (rpath)

hi, On Mon, Sep 17, 2001 at 01:49:03PM +0200, Robert Bihlmeyer wrote: > > first, dpkg-shlibdeps checks a few shared objects files which > > resides in the packages own subdir in /usr/lib, since they are > > just some sort of plugins, but shlibdeps complains: > > dpkg-shlibdeps: warning: format of

Re: gcc-3.0 problem on ARM

Hi, On Thu, May 09, 2002 at 04:51:43PM +0100, Phil Brooke wrote: > > > Assuming that an uploaded gcc-3.0 can compile searchandrescue on the arm > > > okay, would the buildd eventually revisit it? > > I think they do ... but if you are desperate, and don't have a new > > upload scheduled soon, you

dpkg-shlibdeps strange messages and lintian error (rpath)

hi, first, dpkg-shlibdeps checks a few shared objects files which resides in the packages own subdir in /usr/lib, since they are just some sort of plugins, but shlibdeps complains: dpkg-shlibdeps: warning: format of libmla_mdata_netmask.so not recognized and this without about a dozen of files. w

Re: dpkg-shlibdeps strange messages and lintian error (rpath)

hi, On Mon, Sep 17, 2001 at 01:49:03PM +0200, Robert Bihlmeyer wrote: > > first, dpkg-shlibdeps checks a few shared objects files which > > resides in the packages own subdir in /usr/lib, since they are > > just some sort of plugins, but shlibdeps complains: > > dpkg-shlibdeps: warning: format of