J?rgen H?gg wrote:
>
> I'm curious about how the auto-builders work, somehow
> I didn't find enough info about them, except for buildd
> (http://buildd.debian.org/).
>
> My question is: how do I make my packages available for
> all architectures?
> (Or at least, as many as possible. :-)
>
> Shou
J?rgen H?gg wrote:
>
> I'm curious about how the auto-builders work, somehow
> I didn't find enough info about them, except for buildd
> (http://buildd.debian.org/).
>
> My question is: how do I make my packages available for
> all architectures?
> (Or at least, as many as possible. :-)
>
> Sho
Duncan Findlay wrote:
>
> The NM process is full of waiting. Consider it more of a test of
> devotion rather than a nuisance. It'll happen eventually, I believe
> most of this stuff has to be done manually, and usually by some of the
> busiest people Debian has.
>
> --
> Duncan Findlay, who had
Duncan Findlay wrote:
>
> The NM process is full of waiting. Consider it more of a test of
> devotion rather than a nuisance. It'll happen eventually, I believe
> most of this stuff has to be done manually, and usually by some of the
> busiest people Debian has.
>
> --
> Duncan Findlay, who had
retitle 129924 O: tk707 - a drum sequencer
thanks
Anyone care to adopt tk707? It's a nice drum sequencer based
on the Roland TR-707 Rhythm Composer.
http://www-lmc.imag.fr/lmc-edp/Pierre.Saramito/tk707
I noodle along to mp3s rather than a drum track now and haven't
used it in months. Bug-free
Gergely Nagy wrote:
> >
> > I'd rather not have either a conffile. Currently the user has to
> > 'N' on installing a new sbuild.local.conf but it's a nobrainer -
> > no diff or thinking required as everything in the new file is
> > commented out.
> >
>
> Only if the file was changed. And if it
Gergely Nagy wrote:
> >
> > I'd rather not have either a conffile. Currently the user has to
> > 'N' on installing a new sbuild.local.conf but it's a nobrainer -
> > no diff or thinking required as everything in the new file is
> > commented out.
> >
>
> Only if the file was changed. And if it
Cc to mentors for input
summary: the sbuild package has three configurations files, each
overriding the previous one: /etc/sbuild.conf, /etc/sbuild.conf.local,
~/.sbuildrc.
sbuild.conf is for upstream changes, sbuild.conf.local (a
conffile currently) for local system-wide changes, .sbuildrc for
u
Cc to mentors for input
summary: the sbuild package has three configurations files, each
overriding the previous one: /etc/sbuild.conf, /etc/sbuild.conf.local,
~/.sbuildrc.
sbuild.conf is for upstream changes, sbuild.conf.local (a
conffile currently) for local system-wide changes, .sbuildrc for
Roland Mas wrote:
> Josselin Mouette (2002-02-25 14:00:29 +0100) :
>
>> I have a problem with the frozen-bubble-lib package : due to a debhelper
>> bug, it has been built as an empty package on two arches (sparc and
>> powerpc), and marked as successfully built by buildd.
>> Is there a good way to
Roland Mas wrote:
> Josselin Mouette (2002-02-25 14:00:29 +0100) :
>
>> I have a problem with the frozen-bubble-lib package : due to a debhelper
>> bug, it has been built as an empty package on two arches (sparc and
>> powerpc), and marked as successfully built by buildd.
>> Is there a good way t
Alwyn Schoeman wrote:
>
> Recently a newer version of the package that I maintain has
> been uploaded into unstable. When I look at the excuses file
> it should have been in testing 10 days ago, but there seems
> to be a problem with the m68k build.
>
> Upon further investigation it appears that
Alwyn Schoeman wrote:
>
> Recently a newer version of the package that I maintain has
> been uploaded into unstable. When I look at the excuses file
> it should have been in testing 10 days ago, but there seems
> to be a problem with the m68k build.
>
> Upon further investigation it appears tha
Stephan A Suerken wrote:
>
> Hi,
>
> I would like anyone to comment if I am right on these points.
>
> o There's currently no standard way (for developers) to test
> the building of packages on public (alien arch) machines.
In general, if your package builds ok in a chroot environment
with just
Stephan A Suerken wrote:
>
> Hi,
>
> I would like anyone to comment if I am right on these points.
>
> o There's currently no standard way (for developers) to test
> the building of packages on public (alien arch) machines.
In general, if your package builds ok in a chroot environment
with jus
Javier Viñuales Gutiérrez wrote:
> [-- text/plain, encoding quoted-printable, 17 lines --]
>
> On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
>> No, you are right: all you need is docbook-to-man. See policy,
>> section 2.4.2 where this is explained in detail.
>
> Ok, I just readed
Javier Viñuales Gutiérrez wrote:
> [-- text/plain, encoding quoted-printable, 17 lines --]
>
> On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
>> No, you are right: all you need is docbook-to-man. See policy,
>> section 2.4.2 where this is explained in detail.
>
> Ok, I just readed
Stefano Zacchiroli wrote:
>
> I know a little about buildd, but I guess that it try to build a package
> and it if fail someone take its logs and submit a bug report.
> At the end of the build process I guess that the build environment is
> totally cleaned and that survive only a build log.
Most
Stefano Zacchiroli wrote:
>
> I know a little about buildd, but I guess that it try to build a package
> and it if fail someone take its logs and submit a bug report.
> At the end of the build process I guess that the build environment is
> totally cleaned and that survive only a build log.
Most
Matt Zimmerman wrote:
> On Fri, Jan 26, 2001 at 10:18:19PM -0800, Rick Younie wrote:
>
>> I'm playing with a script and need a push. Why doesn't this
>> work?
>>
>> telnet lists.debian.org 80
>> GET /debian-mentors-0101/msg00033.html HTTP/1.0
&
I'm playing with a script and need a push. Why doesn't this
work?
telnet lists.debian.org 80
GET /debian-mentors-0101/msg00033.html HTTP/1.0
Accept: */*
The following works but why is the full url is required?
telnet lists.debian.org 80
GET http://lists.debian.org/debian-mentors-0101/ms
Matt Zimmerman wrote:
> On Fri, Jan 26, 2001 at 10:18:19PM -0800, Rick Younie wrote:
>
>> I'm playing with a script and need a push. Why doesn't this
>> work?
>>
>> telnet lists.debian.org 80
>> GET /debian-mentors-0101/msg00033.html HTTP/1.0
&
I'm playing with a script and need a push. Why doesn't this
work?
telnet lists.debian.org 80
GET /debian-mentors-0101/msg00033.html HTTP/1.0
Accept: */*
The following works but why is the full url is required?
telnet lists.debian.org 80
GET http://lists.debian.org/debian-mentors-0101/m
Henrique M Holschuh wrote:
> On Fri, 26 Jan 2001, Junichi Uekawa wrote:
>>
>> AFAIK a sponsored upload means all the email is received by the sponser,
>> and not the sponsored.
>
> Not really. If the sponsor does not change the changelog entry, email
> goes to whomever is listed there (at least th
Henrique M Holschuh wrote:
> On Fri, 26 Jan 2001, Junichi Uekawa wrote:
>>
>> AFAIK a sponsored upload means all the email is received by the sponser,
>> and not the sponsored.
>
> Not really. If the sponsor does not change the changelog entry, email
> goes to whomever is listed there (at least t
Chris Ruffin wrote:
>
> electric is the package I'm really concerned about. I uploaded it to
> the old woody tree, and it was accecpted. But the package won't go
> into testing, and gives the following in update_excuses:
>
> electric 6.00-1 (new) (low) Maintainer: Chris Ruffin
> <[EMAIL PROTECT
Chris Ruffin wrote:
>
> electric is the package I'm really concerned about. I uploaded it to
> the old woody tree, and it was accecpted. But the package won't go
> into testing, and gives the following in update_excuses:
>
> electric 6.00-1 (new) (low) Maintainer: Chris Ruffin
> <[EMAIL PROTEC
Drew Parsons wrote:
>
> As for editing nroff source, that's what I meant with my first question. Is
> there no editor for this sort of thing? For handling all the fiddly things
> like section breaks and bold text, etc, so I don't have to learn nroff itself.
If you use dh_make, the manpage examp
Drew Parsons wrote:
>
> As for editing nroff source, that's what I meant with my first question. Is
> there no editor for this sort of thing? For handling all the fiddly things
> like section breaks and bold text, etc, so I don't have to learn nroff itself.
If you use dh_make, the manpage exam
Simon Richter wrote:
> On Tue, 3 Oct 2000, Sean 'Shaleh' Perry wrote:
>
>> rpath hardcodes an item's location. If this item later moves,
>> everything using it gets confused. rpath is generally frowned
>> upon.
>
> rpath adds additional path elements to the search list. Libraries are
> still fou
Simon Richter wrote:
> On Tue, 3 Oct 2000, Sean 'Shaleh' Perry wrote:
>
>> rpath hardcodes an item's location. If this item later moves,
>> everything using it gets confused. rpath is generally frowned
>> upon.
>
> rpath adds additional path elements to the search list. Libraries are
> still fo
Christian Kurz wrote:
>
>> > The person who signs the changes file gets mailed
>> > My sponsor when I was in the queue would forward me the mails from
>> > dinstall/ftp-master, yours probably did this as well
>
>> Hmm. Nope, Shorty did the signing and upload, however this mail went
>> directly to
Christian Kurz wrote:
>
>> > The person who signs the changes file gets mailed
>> > My sponsor when I was in the queue would forward me the mails from
>> > dinstall/ftp-master, yours probably did this as well
>
>> Hmm. Nope, Shorty did the signing and upload, however this mail went
>> directly t
Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> traini
Peter Palfrader wrote:
>
>> I think a point could be made for including a bogus bug in a
>> guy's first package so he can learn the changelog procedure for
>> closing it while he's still in close contact with his sponsor.
>
> Since ITPs are now reported as bugs against wnpp you have your
> train
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck
Antti-Juhani Kaijanaho wrote:
> On 2914T102042-0700, Rick Younie wrote:
>> Anyhow, ignore this specific example. I just mean in the general
>> case. Get it close or flog the package until it squeaks?
>
> Well, in the final analysis, it's the sponsor's neck
How exacting should a sponsor be?
A sponsor was reamed on a list a while back because he duploaded
a package with a fairly minor error. He'd identified the problem
and told the packager to fix it in the next version and said that
this was his impression of what a sponsor should do. That is,
get
How exacting should a sponsor be?
A sponsor was reamed on a list a while back because he duploaded
a package with a fairly minor error. He'd identified the problem
and told the packager to fix it in the next version and said that
this was his impression of what a sponsor should do. That is,
get
This was in -devel a couple days ago:
Craig Small wrote:
> ...
> I have a reasonably good working relationship with the upstream
> maintainer Patrick Powell and he does actively maintain LPRng. Actually
> he's probably my best upstream maintainer, even including packages where
> I am that upstream
This was in -devel a couple days ago:
Craig Small wrote:
> ...
> I have a reasonably good working relationship with the upstream
> maintainer Patrick Powell and he does actively maintain LPRng. Actually
> he's probably my best upstream maintainer, even including packages where
> I am that upstrea
Michael Beattie wrote:
>
> Would those posting 'Re: .*NM.*' *PLEASE* go and reread the description of
> this mailing list.
>
Whoops.
nm-discuss seems to be fubared. Is there another list to talk
about the nm process until it gets fixed or moved to d.o?
Rick
Colin Watson wrote:
> Julian Gilbey <[EMAIL PROTECTED]> wrote:
>>
>>I get all my nm-admin mail through the gated nm-discuss list, and it
>>has *not* been quiet. Please check your subscription details if you
>>are not receiving anything!
>
> I see the web archives
> (http://cipsa.physik.uni-freibu
Michael Beattie wrote:
>
> Would those posting 'Re: .*NM.*' *PLEASE* go and reread the description of
> this mailing list.
>
Whoops.
nm-discuss seems to be fubared. Is there another list to talk
about the nm process until it gets fixed or moved to d.o?
Rick
--
To UNSUBSCRIBE, email to [
Colin Watson wrote:
> Julian Gilbey <[EMAIL PROTECTED]> wrote:
>>
>>I get all my nm-admin mail through the gated nm-discuss list, and it
>>has *not* been quiet. Please check your subscription details if you
>>are not receiving anything!
>
> I see the web archives
> (http://cipsa.physik.uni-freib
Could I get advice on whether this is a suitable package?
The programs are written in the interpreted language rexx. Three
are to query search engines -- Debian, Geocrawler, Dejanews. They
run from the command line and show the hits in Lynx, sorted by
date. The other is nodeps which shows packa
Could I get advice on whether this is a suitable package?
The programs are written in the interpreted language rexx. Three
are to query search engines -- Debian, Geocrawler, Dejanews. They
run from the command line and show the hits in Lynx, sorted by
date. The other is nodeps which shows pack
>> http://lists.debian.org - everything you need :)
>> So, for example if you want to package 'helloworld2000',
>> you'd search for it in the bottom of the page, and find out
>> if its ITP'd already.
>
> The search engine on the lists page has been broken for quite some time.
geocrawler.com also
>> http://lists.debian.org - everything you need :)
>> So, for example if you want to package 'helloworld2000',
>> you'd search for it in the bottom of the page, and find out
>> if its ITP'd already.
>
> The search engine on the lists page has been broken for quite some time.
geocrawler.com als
I'm looking for a sponsor. I've done three packages. They can be
downloaded at
http://loki.dhs.org/~rick/debian/
and with apt
deb http://loki.dhs.org/~rick/debian unstable rexx
deb-src http://loki.dhs.org/~rick/debian unstable rexx
Package: tkheadlines
Description: Headline clicker
Hamish Moffatt wrote:
>
> On Tue, Feb 08, 2000 at 08:39:00PVM -0800, Rick Younie wrote:
>> ..
>> The only problem lintian has with the two function packages is
>> 'useless call to ldconfig' after install/remove but regina
>> needs this to find the libs
This is a followup to a request for sponsorship a week ago with
some more details.
I've packaged a couple function libraries for the regina-rexx
interpreter and a headlines viewer/clicker that I've written that
uses these.
I got Joey Hess's opinion before I started that since general
programs did
I've packaged a couple functions libraries for the existing
Debian package regina-rexx and an app that uses these to test
them out - rxsock, rexxtk and tkheadlines. These lines in
sources.list will pick them up if I've done it right,
deb http://loki.dhs.org/~rick/downloads/debian unstable rexx
de
53 matches
Mail list logo
