Getting a package in with an expired key

Hello all, This has come up before but I was unsuccessful following the suggestions (changing the expiry date of the key) Some time ago I decided to create a new key since my first one was created when I didn't know enough about GPG and did a few silly things. Since then I have been unable to ge

Getting a package in with an expired key

Hello all, This has come up before but I was unsuccessful following the suggestions (changing the expiry date of the key) Some time ago I decided to create a new key since my first one was created when I didn't know enough about GPG and did a few silly things. Since then I have been unable to g

how many users is too few

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I've got a package (gtkgo) that has been discontinued upstream. So far I've been ignoring this and continuing to apply fixes, etc. But I'm beginning to wonder if I should ITA it since maintained packages are starting to incorporate its fun

how many users is too few

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I've got a package (gtkgo) that has been discontinued upstream. So far I've been ignoring this and continuing to apply fixes, etc. But I'm beginning to wonder if I should ITA it since maintained packages are starting to incorporate its fu

Re: Where to place images?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I like this idea. /usr/share/doc is really not the right place for images, > and placing them there simply because it happens to be web-accessible is an > unnecessary kludge. Slightly less unappetizing is to place the images in > /usr/share/ and sy

Re: Where to place images?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I like this idea. /usr/share/doc is really not the right place for images, > and placing them there simply because it happens to be web-accessible is an > unnecessary kludge. Slightly less unappetizing is to place the images in > /usr/share/ and s

choosing a package name

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm packaging gnubg (gnu backgammon program). I'm a bit worried that this name is too short and I should call it gnubackgammon or something. I asked upstream and they said: > Personally I have a slight preference for gnubg for consistency, but I >

Re: packages with binary 'source' files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Why should the debian.diff contain this binary file, that is not part > of your port to Debian, but a result of compiling the package? True > As the diff is generated at the very beginning of dpkg-buildpackage, > this means that it was left over fr

choosing a package name

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm packaging gnubg (gnu backgammon program). I'm a bit worried that this name is too short and I should call it gnubackgammon or something. I asked upstream and they said: > Personally I have a slight preference for gnubg for consistency, but I >

Re: packages with binary 'source' files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Why should the debian.diff contain this binary file, that is not part > of your port to Debian, but a result of compiling the package? True > As the diff is generated at the very beginning of dpkg-buildpackage, > this means that it was left over f

packages with binary 'source' files

-BEGIN PGP SIGNED MESSAGE- I'm trying to package a program (gnubg) that generates a binary file during compilation. However this upsets dpkg-buildpackage which can't diff between the current version and the .orig Personally I think this is a bug in diff (you should be able to diff binary

packages with binary 'source' files

-BEGIN PGP SIGNED MESSAGE- I'm trying to package a program (gnubg) that generates a binary file during compilation. However this upsets dpkg-buildpackage which can't diff between the current version and the .orig Personally I think this is a bug in diff (you should be able to diff binar