Some questions regarding packaging of bolt

Hello debian-mentors, i'm in the process of packaging 'bolt', the thunderbolt 3 device manager. I've pushed the current state of the package to salsa [0]. There are still some lintian warnings about missing copyright informations, but those are about manpage files, dockerfiles, systemd-servic

Re: I have some questions about alioth repository

On Fri, 21 Apr 2017 10:58:30 +0100 Ghislain Vaillant wrote: > If the corresponding Vcs-* fields in d/control are missing for these > packages, then the packaging work is not stored in a VCS. You may > generate one by calling `gbp import-dscs $PACKAGE` which will download > all previous uploads an

Re: I have some questions about alioth repository

On Fri, Apr 21, 2017 at 05:37:19PM +0900, JungHwan Kang wrote: > 4. Some packages don't have repository(No repository found by debcheckout > tool) > >     like acpi, alsamixergui, apg, aspell-en, autoconf. > >     Are there repositories for source code of those packages ? > % dgit clone ac

Re: I have some questions about alioth repository

Hi, >> 3. In case of darcs package, debcheckout tried to download source code from >> Darcs repository. >> (anonscm.debian.org/cgi-bin/darcsweb.cgi) >> But, that failed. Because, the project doesn’t exist in the repository. Is >> this working well? > >If it failed, probably the answer is

Re: I have some questions about alioth repository

On Fri, 2017-04-21 at 17:37 +0900, JungHwan Kang wrote: > Hi, > I was analyzing repositories of debian packages by debcheckout tool. > I've known there are 7 types of version control system. > (Arch, Bazzar, CVS, Darcs, Git, Mercurial, Subversion) > My questions are below... >   > 1 All version c

I have some questions about alioth repository

Hi, I was analyzing repositories of debian packages by debcheckout tool. I've known there are 7 types of version control system. (Arch, Bazzar, CVS, Darcs, Git, Mercurial, Subversion) My questions are below... 1 All version control systems are using actively? or moving to git progressively

Re: Some questions about copyrights

OK, Paul has talked about embedded copies which I agree with (leaving aside the whole jquery thing) in general. Use the already packaged libraries for that, your life will be better for it! Turning to copyright files, the preferred format is the old DEP-5 format, found at [1] The files stanzas, t

Re: Some questions about copyrights

On Sat, Jun 13, 2015 at 10:30 AM, wrote: > https://code.google.com/p/uftt/source/browse/trunk/src/linux/libnetlink.c?r=1041 It looks like this code has several copies already in Debian. The proper upstream for this file seems to be iproute2 but that only builds a static library that isn't insta

Re: Some questions about copyrights

On Sat, Jun 13, 2015 at 10:30 AM, wrote: > Hello, this is my first time publishing a program i have made ... > Also at the debian/copyright file. The lines should be something like that? > Code was taken from here: > https://github.com/seanmiddleditch/libtelnet > https://code.google.com/p/uftt/s

Some questions about copyrights

Hello, this is my first time publishing a program i have made, i would like you to explain me some things about copyrights, i was reading about copyright for packaging a program i made at Debian and i could not understand/fill some parts. From all the source code files, i have used 4 that are not

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Paul Gevers wrote: > > It is done by `make distclean'. > > I hate to disagree, but for me it doesn't. Of course, sorry about that :(. Make does not recurse into the Tests directory by default. Fixed, and I explicitly delete them before the build too. > E.g. it seems that you removed libtool fo

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

On 15-07-14 18:52, Yavor Doganov wrote: > Paul Gevers wrote: >> Whatever you do, to prevent accidental usage of a pre-build object >> file it is very common to at least clean them. > > It is done by `make distclean'. I hate to disagree, but for me it doesn't. After `make distclean` the files are

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Paul Gevers wrote: > On 15-07-14 16:05, Yavor Doganov wrote: > > I don't understand. It is quite common for a package not to build > > some part of the source; this is not a problem at all as long as > > everything is DFSG-compliant. Which is the case here. > > This is true if you mean that not

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

On 15-07-14 16:05, Yavor Doganov wrote: >> Well, the source has to be DFSG-free. How we guarantee that usually is >> by building everything from source during the build. If you don't want >> to build it, you have to remove them from source and repack > > I don't understand. It is quite common for

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Paul Gevers wrote: > On 15-07-14 14:54, Yavor Doganov wrote: > > Hmm, but I have not overridden them, I don't feel I should. I have > > informed upstream and I hope it won't happen in subsequent releases. > > Well, to document this fact is exactly why an override would be nice. OK, I added the o

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Paul Gevers wrote: > Before I upload this package to the new queue, could you please > comment on the lintian errors about missing source? The reason for these is gnustep-make's incapable dist rule, combined with not so careful upstream. > I am looking for a statement like: "I added lintian overr

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

On 15-07-14 14:54, Yavor Doganov wrote: > Paul Gevers wrote: >> Before I upload this package to the new queue, could you please >> comment on the lintian errors about missing source? > > The reason for these is gnustep-make's incapable dist rule, combined > with not so careful upstream. > >> I am

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Hi Yavor, And an additional remark: the COPYING file and the headers in several (all?) source files don't match. The COPYING file says LGPL-2.1+ while the headers say LGPL-2+. Please update your d/copyright file to match the situation. Paul signature.asc Description: OpenPGP digital signature

Bug#752339: Some questions about RFS: dbuskit/0.1.1-1 [ITP]

Control: owner -1 ! Control: tags -1 moreinfo Hi Yavor, Before I upload this package to the new queue, could you please comment on the lintian errors about missing source? I am looking for a statement like: "I added lintian overrides for these files as the source is available several directories

Re: Some questions related to signing

Le 24/04/12 04:25, Paul Wise a écrit : > On Tue, Apr 24, 2012 at 10:13 AM, Christopher Howard wrote: > >> * I make binary deb packages available for my projects from my Web site, >> but I also wanted to make the deb source files available, so that people >> can wrap their own binary debs for other

Re: Some questions related to signing

On Tue, Apr 24, 2012 at 10:13 AM, Christopher Howard wrote: > * I make binary deb packages available for my projects from my Web site, > but I also wanted to make the deb source files available, so that people > can wrap their own binary debs for other architectures. I know that they > need the *.

Some questions related to signing

A few humble questions related to packaging signing: * I make binary deb packages available for my projects from my Web site, but I also wanted to make the deb source files available, so that people can wrap their own binary debs for other architectures. I know that they need the *.orig.tar.gz fil

Re: Request for substitute sponsor (vim-vimoutliner) and some questions

Adam D. Barratt wrote: > http://people.debian.org/~joey/3.1r1/, given that woody isn't stable any > more. ;-) Thanks a lot. Matěj -- Matej Cepl, http://www.ceplovi.cz/matej/blog/ GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC I went to a Grateful Dead Concert and they played f

Re: Request for substitute sponsor (vim-vimoutliner) and some questions

On Tuesday, October 11, 2005 5:38 AM, Justin Pryzby <[EMAIL PROTECTED]> wrote: > On Mon, Oct 10, 2005 at 11:26:55PM -0400, Matej Cepl wrote: [...] >> Or what should I do with persistent user claiming that he wants to >> have it fixed in stable? On the other hand, 0.3.3-6 (which is what >> is in sa

Re: Request for substitute sponsor (vim-vimoutliner) and some questions

On Mon, Oct 10, 2005 at 11:26:55PM -0400, Matej Cepl wrote: > 2) Bug# 216626 -- I have tried to close > (because it was already fixed in 0.3.4-1), but then the reporter reopened > it claiming that it was not fixed in sarge, so it should stay opened. That > IMHO isn't

Request for substitute sponsor (vim-vimoutliner) and some questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, my sponsor (Martin F. Krafft) got tendonitis, so I need somebody to help me with vim-vimoutliner. Is there any nice DD willing to sponsor next upload of vim-vimoutliner package? Version 0.3.4-2 is available at

Re: Some questions

On Tue, Mar 01, 2005 at 04:34:44PM +0100, Lars Roland wrote: > 2) When you update the database software from, say, version 1.0 to 1.1 > then it would be preferable to NOT generate all the tables again (that > is, mysoftware-db 1.1 should just alter or extend the tables that > mysoftware-db 1.0 crea

Re: Some questions

On Tue, Mar 01, 2005 at 06:15:15PM +0100, Lars Roland wrote: > On Tue, 1 Mar 2005 16:51:02 +0100, Romain Beauxis <[EMAIL PROTECTED]> wrote: > > Le Mardi 1 Mars 2005 16:34, Lars Roland a écrit : > > > 2) When you update the database software from, say, version 1.0 to 1.1 > > > then it would be prefe

Re: Some questions

On Tue, 1 Mar 2005 16:51:02 +0100, Romain Beauxis <[EMAIL PROTECTED]> wrote: > Le Mardi 1 Mars 2005 16:34, Lars Roland a écrit : > > 2) When you update the database software from, say, version 1.0 to 1.1 > > then it would be preferable to NOT generate all the tables again (that > > is, mysoftware-d

Re: Some questions

On Tuesday 01 March 2005 16:34, Lars Roland wrote: > 1) How do I create a deb package that just drops the documentation in > a given directory (eg. it is pure html doc so no man pages are > created). easy, just call dh_install in your debian/rules file (if it's a long list of files you might

Re: Some questions

On Tue, Mar 01, 2005 at 04:34:44PM +0100, Lars Roland wrote: > Hi > > This may be newbie questions, but anyway here goes: We have a > commercial system, that we are planing to make available open source > (GPL) - right now the plan is to have deb packages and tgz files for > the installation. The

Some questions

Hi This may be newbie questions, but anyway here goes: We have a commercial system, that we are planing to make available open source (GPL) - right now the plan is to have deb packages and tgz files for the installation. The tgz installation can be broken into a) Executable files b) Database f

Re: some questions on multiple binaries per source

On Thu, Dec 02, 2004 at 06:53:07PM +0100, Eric Lavarde wrote: > OK, two answers, two contradictory ones, I'm helped... :-) > > So, conclusion is that the policy is not conclusive on this point, and > I'm free to do like I feel better (anyway my sponsor will decide). Well, there is always the pos

Re: some questions on multiple binaries per source

OK, two answers, two contradictory ones, I'm helped... :-) So, conclusion is that the policy is not conclusive on this point, and I'm free to do like I feel better (anyway my sponsor will decide). Thanks, Eric Colin Watson wrote: On Wed, Dec 01, 2004 at 03:38:40PM -0500, Justin Pryzby wrote: On W

Re: some questions on multiple binaries per source

On Wed, Dec 01, 2004 at 03:38:40PM -0500, Justin Pryzby wrote: > On Wed, Dec 01, 2004 at 09:06:24PM +0100, Eric Lavarde wrote: > > - more specific question: one of the additional packages is a plugin, > > FreeMind itself "requires" Java, the plugin "requires" Java and > > FreeMind. Am I supposed

Re: some questions on multiple binaries per source

On Wed, Dec 01, 2004 at 09:06:24PM +0100, Eric Lavarde wrote: > I'm packaging FreeMind (old version somewhere on the upload path), and > the new version is requesting multiple packages. So here two questions: > - is there somewhere a specific description of multi-packaging? the new > maintainer t

some questions on multiple binaries per source

Hi, I'm packaging FreeMind (old version somewhere on the upload path), and the new version is requesting multiple packages. So here two questions: - is there somewhere a specific description of multi-packaging? the new maintainer tutorial isn't really explaining much and I couldn't find anythi

Re: some questions on multiple binaries per source

On Wed, Dec 01, 2004 at 09:06:24PM +0100, Eric Lavarde wrote: > I'm packaging FreeMind (old version somewhere on the upload path), and > the new version is requesting multiple packages. So here two questions: > - is there somewhere a specific description of multi-packaging? the new > maintainer t

some questions on multiple binaries per source

Hi, I'm packaging FreeMind (old version somewhere on the upload path), and the new version is requesting multiple packages. So here two questions: - is there somewhere a specific description of multi-packaging? the new maintainer tutorial isn't really explaining much and I couldn't find anything

Re: Some questions

* Dan Korostelev [Thu, 05 Aug 2004 23:48:22 +0400]: > I'm a (newbie) maintainer of gnome-ppp package and i'm somehow confused. please send this kind of questions to [EMAIL PROTECTED] [m-f-t set] > package overview page (http://packages.qa.debian.org/g/gnome-ppp.html) > says that new version of

Re: Some questions

* Dan Korostelev [Thu, 05 Aug 2004 23:48:22 +0400]: > I'm a (newbie) maintainer of gnome-ppp package and i'm somehow confused. please send this kind of questions to [EMAIL PROTECTED] [m-f-t set] > package overview page (http://packages.qa.debian.org/g/gnome-ppp.html) > says that new version of

Re: Some questions about patching source

Stephen, On Thu, Nov 07, 2002 at 04:43:37PM -0500, Stephen Gran wrote: > > > Define "other things". As long as it is headers, the best solution would > > > be to ask the xscreensaver maintainer whether he could make a -dev > > > package with the headers that you can build-depend on. Hrm, what abo

Re: Some questions about patching source

Stephen, On Thu, Nov 07, 2002 at 04:43:37PM -0500, Stephen Gran wrote: > > > Define "other things". As long as it is headers, the best solution would > > > be to ask the xscreensaver maintainer whether he could make a -dev > > > package with the headers that you can build-depend on. Hrm, what abo

Re: Some questions about patching source

This one time, at band camp, Stephen Gran said: > This one time, at band camp, Simon Richter said: > > Stephen, > > > > On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > > > I am putting together a .deb of cosmos (the xscreensaver module) for > > > personal consumption - I don't thin

Re: Some questions about patching source

This one time, at band camp, Stephen Gran said: > This one time, at band camp, Simon Richter said: > > Stephen, > > > > On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > > > I am putting together a .deb of cosmos (the xscreensaver module) for > > > personal consumption - I don't thin

Re: Some questions about patching source

This one time, at band camp, Junichi Uekawa said: > > The plan I have come up with is to put all the files it needs into a > > debian/patches directory, and alter the Makefile accordingly. This > > works just fine, although it makes the resulting .diff about twice the > > size of the original sour

Re: Some questions about patching source

This one time, at band camp, Simon Richter said: > Stephen, > > On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > > I am putting together a .deb of cosmos (the xscreensaver module) for > > personal consumption - I don't think it's suitable to go into Debian > > proper, as upstream se

Re: Some questions about patching source

> The plan I have come up with is to put all the files it needs into a > debian/patches directory, and alter the Makefile accordingly. This > works just fine, although it makes the resulting .diff about twice the > size of the original source code, and it means it need to be redone > every time th

Re: Some questions about patching source

Stephen, On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > I am putting together a .deb of cosmos (the xscreensaver module) for > personal consumption - I don't think it's suitable to go into Debian > proper, as upstream seems to have disappeared (at any rate, the site > where I orig

Re: Some questions about patching source

On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > The problem I am having with putting it together is that in order for it > to build from source, it needs a compiled xscreensaver source tree to pull > some headers and other things from. You may want to look into apt-src; there is s

Some questions about patching source

Hello all, I am putting together a .deb of cosmos (the xscreensaver module) for personal consumption - I don't think it's suitable to go into Debian proper, as upstream seems to have disappeared (at any rate, the site where I originally downloaded the source is gone, and google returns only old hi

Re: Some questions about patching source

This one time, at band camp, Junichi Uekawa said: > > The plan I have come up with is to put all the files it needs into a > > debian/patches directory, and alter the Makefile accordingly. This > > works just fine, although it makes the resulting .diff about twice the > > size of the original sour

Re: Some questions about patching source

This one time, at band camp, Simon Richter said: > Stephen, > > On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > > I am putting together a .deb of cosmos (the xscreensaver module) for > > personal consumption - I don't think it's suitable to go into Debian > > proper, as upstream se

Re: Some questions about patching source

> The plan I have come up with is to put all the files it needs into a > debian/patches directory, and alter the Makefile accordingly. This > works just fine, although it makes the resulting .diff about twice the > size of the original source code, and it means it need to be redone > every time th

Re: Some questions about patching source

Stephen, On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > I am putting together a .deb of cosmos (the xscreensaver module) for > personal consumption - I don't think it's suitable to go into Debian > proper, as upstream seems to have disappeared (at any rate, the site > where I orig

Re: Some questions about patching source

On Wed, Nov 06, 2002 at 02:21:07PM -0500, Stephen Gran wrote: > The problem I am having with putting it together is that in order for it > to build from source, it needs a compiled xscreensaver source tree to pull > some headers and other things from. You may want to look into apt-src; there is s

Some questions about patching source

Hello all, I am putting together a .deb of cosmos (the xscreensaver module) for personal consumption - I don't think it's suitable to go into Debian proper, as upstream seems to have disappeared (at any rate, the site where I originally downloaded the source is gone, and google returns only old hi

Re: some questions about DBS

On Sun, Jan 27, 2002 at 03:06:38PM +0100, Tollef Fog Heen wrote: > It doesn't. There are absolutely no docs, IIRC. Doogie promised to document it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52351&archive=yes&repeatmerged=yes Unfortunately, the next maintainer for that package closed it.

Re: some questions about DBS

On Sun, Jan 27, 2002 at 03:06:38PM +0100, Tollef Fog Heen wrote: > It doesn't. There are absolutely no docs, IIRC. Doogie promised to document it in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52351&archive=yes&repeatmerged=yes Unfortunately, the next maintainer for that package closed it.

Re: some questions about DBS

Tollef Fog Heen <[EMAIL PROTECTED]> writes: > * Robert Bihlmeyer > > | Michael Moerz <[EMAIL PROTECTED]> writes: > | > | > Well is there any documentation out there that would line out > | > the usage of the DBS (doogie build system)? > | [...] > | > Is there any url where I could fetch a debia

Re: some questions about DBS

* Robert Bihlmeyer | Michael Moerz <[EMAIL PROTECTED]> writes: | | > Well is there any documentation out there that would line out | > the usage of the DBS (doogie build system)? | [...] | > Is there any url where I could fetch a debian/scripts tarball | > from? (or should I stick to the mention

Re: some questions about DBS

Michael Moerz <[EMAIL PROTECTED]> writes: > Well is there any documentation out there that would line out > the usage of the DBS (doogie build system)? [...] > Is there any url where I could fetch a debian/scripts tarball > from? (or should I stick to the mentioned packages?) I think you want to

Re: some questions about DBS

Tollef Fog Heen <[EMAIL PROTECTED]> writes: > * Robert Bihlmeyer > > | Michael Moerz <[EMAIL PROTECTED]> writes: > | > | > Well is there any documentation out there that would line out > | > the usage of the DBS (doogie build system)? > | [...] > | > Is there any url where I could fetch a debi

Re: some questions about DBS

* Robert Bihlmeyer | Michael Moerz <[EMAIL PROTECTED]> writes: | | > Well is there any documentation out there that would line out | > the usage of the DBS (doogie build system)? | [...] | > Is there any url where I could fetch a debian/scripts tarball | > from? (or should I stick to the mentio

Re: some questions about DBS

Michael Moerz <[EMAIL PROTECTED]> writes: > Well is there any documentation out there that would line out > the usage of the DBS (doogie build system)? [...] > Is there any url where I could fetch a debian/scripts tarball > from? (or should I stick to the mentioned packages?) I think you want to

some questions about DBS

Hi! Well is there any documentation out there that would line out the usage of the DBS (doogie build system)? Currently I am browsing packages that make use of it, but that's rather time consuming (like alsa, shadow). And what's better (or the real difference) between the native DBS and the one p

some questions about DBS

Hi! Well is there any documentation out there that would line out the usage of the DBS (doogie build system)? Currently I am browsing packages that make use of it, but that's rather time consuming (like alsa, shadow). And what's better (or the real difference) between the native DBS and the one

Re: some questions about packing

[Very new DD, so take what I say with a grain of salt.] On Wed, Dec 06, 2000 at 04:58:34PM -0800, Sean 'Shaleh' Perry wrote: > On 07-Dec-2000 Manuel Estrada wrote: > > Is there some automated way to keep the .ex files and not include > > them in the source package? > > leave them in the debi

Re: some questions about packing

MoiN Just some additional thoughts... On Thu, Dec 07, 2000 at 01:32:04AM +0100, Manuel Estrada wrote: > Is there some automated way to keep the .ex files and not include > them in the source package? Yes. Don't remove the dh-make package, as it keeps the .ex files in the directory /usr/share/de

Re: some questions about packing

* Sean 'Shaleh' Perry <[EMAIL PROTECTED]> [20001206 16:58]: > On 07-Dec-2000 Manuel Estrada wrote: > > > > First, where should I send the ITP message? debian-devel > > debian-mentors or both. > > should go to debian-devel and the package wnpp in the debian bug tracking > system. Your first uplo

RE: some questions about packing

On 07-Dec-2000 Manuel Estrada wrote: > > Hello all, > > I am packing visualos, dhid and jslaunch as part of my aplication to > become a debian member and I have some cuestions: > > First, where should I send the ITP message? debian-devel > debian-mentors or both. > should go to debian-deve

some questions about packing

Hello all, I am packing visualos, dhid and jslaunch as part of my aplication to become a debian member and I have some cuestions: First, where should I send the ITP message? debian-devel debian-mentors or both. Is there some automated way to keep the .ex files and not include them in the so

Re: some questions about packing

[Very new DD, so take what I say with a grain of salt.] On Wed, Dec 06, 2000 at 04:58:34PM -0800, Sean 'Shaleh' Perry wrote: > On 07-Dec-2000 Manuel Estrada wrote: > > Is there some automated way to keep the .ex files and not include > > them in the source package? > > leave them in the deb

Re: some questions about packing

MoiN Just some additional thoughts... On Thu, Dec 07, 2000 at 01:32:04AM +0100, Manuel Estrada wrote: > Is there some automated way to keep the .ex files and not include > them in the source package? Yes. Don't remove the dh-make package, as it keeps the .ex files in the directory /usr/share/d

Re: some questions about packing

* Sean 'Shaleh' Perry <[EMAIL PROTECTED]> [20001206 16:58]: > On 07-Dec-2000 Manuel Estrada wrote: > > > > First, where should I send the ITP message? debian-devel > > debian-mentors or both. > > should go to debian-devel and the package wnpp in the debian bug tracking > system. Your first upl

RE: some questions about packing

On 07-Dec-2000 Manuel Estrada wrote: > > Hello all, > > I am packing visualos, dhid and jslaunch as part of my aplication to > become a debian member and I have some cuestions: > > First, where should I send the ITP message? debian-devel > debian-mentors or both. > should go to debian-dev

some questions about packing

Hello all, I am packing visualos, dhid and jslaunch as part of my aplication to become a debian member and I have some cuestions: First, where should I send the ITP message? debian-devel debian-mentors or both. Is there some automated way to keep the .ex files and not include them in the s

Re: Some questions about packaging

On Wed, Nov 29, 2000 at 07:54:22PM +, Colin Watson wrote: > Bas Zoetekouw <[EMAIL PROTECTED]> wrote: > >Hi Frederico! > > > >You wrote: > > > >> The program has 'less' harcoded into it, and uses it has a pager to > >> display the help, so I made the package depend on less... butt a better > >>

Re: Some questions about packaging

On Wed, Nov 29, 2000 at 08:16:12PM +0100, Bas Zoetekouw wrote: > Hi Frederico! > > You wrote: > > > I'm packaging sel (I did an ITP on it yesterday); I've gotten to the > > point were the package correctly builds, goes trough lintian with no > > warnings, installs ok and deinstalls ok. > > Great

Re: Some questions about packaging

On Wed, Nov 29, 2000 at 07:54:22PM +, Colin Watson wrote: > Bas Zoetekouw <[EMAIL PROTECTED]> wrote: > >Hi Frederico! > > > >You wrote: > > > >> The program has 'less' harcoded into it, and uses it has a pager to > >> display the help, so I made the package depend on less... butt a better > >>

Re: Some questions about packaging

On Wed, Nov 29, 2000 at 08:16:12PM +0100, Bas Zoetekouw wrote: > Hi Frederico! > > You wrote: > > > I'm packaging sel (I did an ITP on it yesterday); I've gotten to the > > point were the package correctly builds, goes trough lintian with no > > warnings, installs ok and deinstalls ok. > > Grea

Re: Some questions about packaging

Bas Zoetekouw <[EMAIL PROTECTED]> wrote: >Hi Frederico! > >You wrote: > >> The program has 'less' harcoded into it, and uses it has a pager to >> display the help, so I made the package depend on less... butt a better >> aproach would be to change the code so it would get the PAGER env var >> and g

Re: Some questions about packaging

Hi Frederico! You wrote: > I'm packaging sel (I did an ITP on it yesterday); I've gotten to the > point were the package correctly builds, goes trough lintian with no > warnings, installs ok and deinstalls ok. Great. > The package is relatively simple (well, only one bin, and actually just > tw

Some questions about packaging

Hello all! I'm packaging sel (I did an ITP on it yesterday); I've gotten to the point were the package correctly builds, goes trough lintian with no warnings, installs ok and deinstalls ok. The package is relatively simple (well, only one bin, and actually just two or three code files)... my only

Re: Some questions about packaging

Bas Zoetekouw <[EMAIL PROTECTED]> wrote: >Hi Frederico! > >You wrote: > >> The program has 'less' harcoded into it, and uses it has a pager to >> display the help, so I made the package depend on less... butt a better >> aproach would be to change the code so it would get the PAGER env var >> and

Re: Some questions about packaging

Hi Frederico! You wrote: > I'm packaging sel (I did an ITP on it yesterday); I've gotten to the > point were the package correctly builds, goes trough lintian with no > warnings, installs ok and deinstalls ok. Great. > The package is relatively simple (well, only one bin, and actually just > t

Some questions about packaging

Hello all! I'm packaging sel (I did an ITP on it yesterday); I've gotten to the point were the package correctly builds, goes trough lintian with no warnings, installs ok and deinstalls ok. The package is relatively simple (well, only one bin, and actually just two or three code files)... my onl

Re: newbie problems and some questions

Fernando Sanchez <[EMAIL PROTECTED]> writes: > - I got an automatically-generated mail confirming my account/password on > master, etc, which also mentioned that I should use [EMAIL PROTECTED] > address > for signing packages, so I had to add this identificator to my pgp key and > send the

Re: newbie problems and some questions

On Sun, 14 Feb 1999, Fernando Sanchez wrote: > Hello, > I'm having some problems uploading a package, but I also think I > must have done something wrong in the process, so please tell me if there is > some big mistake in my procedures: > > - I got an automatically-generated mail confirming

newbie problems and some questions

Hello, I'm having some problems uploading a package, but I also think I must have done something wrong in the process, so please tell me if there is some big mistake in my procedures: - I got an automatically-generated mail confirming my account/password on master, etc, which also mentio

Re: My first packages -- some questions.

Hi Guys! I've put my packages back together without debmake helper scripts, and I feel much more confidant now that I know what is going on. A big help was Igor Grobman's unfinished work, the "Debian Programmers Manual" http://www.pics.com/~igor/debian/programmer.html/index.html which contain

Re: My first packages -- some questions.

> I think that I will be able to manage the rules file (doing by > example, as Manoj said), but what I am missing is a feeling of what > utilities get run in what order. For instance, is dpkg-buildpackage > just another helper script, or is it something that all but the most > ardent do-it-your-se

Re: My first packages -- some questions.

Hi, >>"Kirk" == Kirk Hilliard <[EMAIL PROTECTED]> writes: Kirk> Thanks Manoj, Scott, and Igor for answering my questions. Manoj, Kirk> if you have that "Working set of rules files as a learning Kirk> example" available, then yes, I would like a copy. You Kirk> mentioning mailing it. That would b

Re: My first packages -- some questions.

Thanks Manoj, Scott, and Igor for answering my questions. Manoj, if you have that "Working set of rules files as a learning example" available, then yes, I would like a copy. You mentioning mailing it. That would be fine, or I could grab it off you web site if you made it available there. I h

Re: My first packages -- some questions.

Hi, >>"Kirk" == Kirk Hilliard <[EMAIL PROTECTED]> writes: Kirk> 0. BTW, I built my packages in what I assume is the standard Kirk> way. I ran deb-make, edited the files in debian/ and ran build. Kirk> Should I be doing something differently? I am not quite Kirk> comfortable with this level of au

Re: My first packages -- some questions.

On 2 Feb 1998, Kirk Hilliard wrote: > OK, here is my first bunch of question. > > 0. BTW, I built my packages in what I assume is the standard way. I >ran deb-make, edited the files in debian/ and ran build. Should I >be doing something differently? I am not quite comfortable with >

Re: My first packages -- some questions.

> I would also appreciate it if someone could give my packages a quick > look before I upload them to Incoming. I could either put them in my > home directory on master or in an obscure corner of my web page. Were > I to do that and then decide that I wanted to change something, would > I have t

My first packages -- some questions.

Hi Mentors! I am putting together my first two packages: elisp-manual and emacs-lisp-intro. These are orphaned packages that I adopted and am converting over from old source format as well as updating with new upstream versions. I have several minor question, the first bunch of which I will ask