[ This is a repost of the following article: ]
[ From: [EMAIL PROTECTED] (Bruno Rodrigues)]
[ Subject: Re: More Assignments]
[ Newsgroups: gmane.linux.debian.devel.mentors,gmane.linux.debian.devel.rele
On Fri, Aug 29, 2003 at 12:44:02PM +0300, Fabian Fagerholm wrote:
>
> * Check out the trunk you just created into a directory called
> project- (svn co).
I was with you up to this point. I don't normally name my working copy
in the form project- as that form is needed for actually m
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize everything in this
reply to myself.
Managing Debian packages wi
El Jueves, 28 de Agosto de 2003 23:04, Juan Manuel García Molina escribió:
> Hi.
>
> I'd like to seek an sponsor to upload pose package.
I forgot the URL [1] to the package:
[1] http://www.superiodico.net/debian/upload/pose/
Yours,
--
Juan Manuel García Molina
[EMAIL PROTECTED]
Jamin W. Collins wrote:
> I prefer an alternate structure where you start with the project as a
> top level. This keeps all project (package) related files under one
> directory in the project:
>
>project/
> trunk/
> branches/
> tags/
> vendor/
The only problem wit
On Thu, Aug 28, 2003 at 09:56:29PM -0400, Joey Hess wrote:
> Jamin W. Collins wrote:
> > I prefer an alternate structure where you start with the project as
> > a top level. This keeps all project (package) related files under
> > one directory in the project:
> >
> >project/
> > tru
Joey Hess <[EMAIL PROTECTED]> wrote:
> [-- text/plain, encoding quoted-printable, charset: us-ascii, 143 lines --]
>
> Here are 15 to remove. FWIW I looked at a total of ~50 packages to find
> these. All bugs have been chosschecked against the NMU claims page which
> is why mindi and mondo are not
Does anyone care to upload my new php4-imagick package ?
This package closes #206960: php4-imagick: This package doesn't work
with the newer imagemagick.
Package is available at http://litux.org/debian/unstable
#include
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
> On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> > How do I manage a new Debian package with Subversion?
>
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everythin
Fabian Fagerholm wrote:
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everything in this
> reply to myself.
Nice job writing this up, here are some corrections.
> The repository will have the following structure:
>
> trun
Jamin W. Collins wrote:
> I was with you up to this point. I don't normally name my working copy
> in the form project- as that form is needed for actually making
> hte package and for that we need an exported copy of the working copy.
Actually, dpkg-buildpackage does not care what you name the b
On Fri, Aug 29, 2003 at 12:30:46PM -0400, Joey Hess wrote:
> Fabian Fagerholm wrote:
> > * B.B. svn_load_dirs -t tags/projectX/upstream/
> >url://host/repos/ branches/projectX/upstream
> >/path/to/new/version
>
> I've only ever had to do this once, and
Hi, mentors.
I have a package ready for upload, facturalux. This revision corrects an
important funcionality bug.
You can find the updated package here [1]:
[1] http://www.superiodico.net/debian/upload/facturalux/
The changelog says:
Changes:
facturalux (0.4-2) unstable; urgency=low
.
*
On Thu, Aug 28, 2003 at 10:24:57PM +0300, Fabian Fagerholm wrote:
>
> How do I manage a new Debian package with Subversion?
>
> The things I've found only scratch the surface a bit, assume a level
> of knowledge beyond mine, or assume you're migrating from CVS and
> already have made several init
Hello,
I have a package that installs a xemacs specific .el file, which
naturally don't build with the emacs20 package i have installed.
Is there a way of specifying that only xemacs installs should build a
given .el or something such ?
Friendly,
Sven Luther
Quoting Sven Luther <[EMAIL PROTECTED]>:
> Hello,
Hello,
> I have a package that installs a xemacs specific .el file, which
> naturally don't build with the emacs20 package i have installed.
>
> Is there a way of specifying that only xemacs installs should build a
> given .el or something such
Hi.
I'd like to seek an sponsor to upload pose packages. The package is in Debian
repository and it's quite important because it contains the migration to gcc
3.3.
The changelog:
Changes:
pose (3.5-4) unstable; urgency=low
.
* Use fltk 1.1 instead of fltk 1:
+ Few ideas 'stolen' fro
Ky Vinh Tran Luu wrote:
> that mentors are not too busy preparing for the sid release.
There won't be a sid release ever
SCNR,
Grüße/Regards,
René
--
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL PROTECTE
[EMAIL PROTECTED] (Geert Stappers) writes:
> On Thu, Aug 28, 2003 at 11:54:58AM +0200, Goswin von Brederlow wrote:
> > Fabio Massimo Di Nitto <[EMAIL PROTECTED]> writes:
> >
> > > On Wed, 27 Aug 2003, Eric Winger wrote:
> > >
> > > > In putting my packages to my local repository, I've encountere
On Fri, Aug 29, 2003 at 10:30:46PM +0200, Eduard Bloch wrote:
>
> Question: how do you manage upstream and Debian branches? I encounter
> this problem while trying to find the best concept for svn-uupdate.
>
> The first idea was:
>
> branches/upstream/a.b ---> branches/ups
#include
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
> Actually, dpkg-buildpackage does not care what you name the build
> directory of a package.
>
> Persaonally, I use just packagename for the directory names and build
> directly from them, using a collection of ugly hacks to ignore the .svn
>
On Sat, Aug 30, 2003 at 12:33:29AM +0200, Eduard Bloch wrote:
> #include
> * Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
>
> > What _stupidness_ are you refering to? I've always just used something
> > like:
> >
> >svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
>
#include
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
> What _stupidness_ are you refering to? I've always just used something
> like:
>
>svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
change
Eduard Bloch wrote:
> However, a possible implementation failed completely because of
> stupideness of "svn merge". So we have to find an alternative solution
> with diff&patch&cp. OTOH it is not possible to keep the version history of
> every file.
I think you're looking for svn_load_dirs.
--
s
Where can I get versions of packages that are not in any distribution?
E.g., I want a copy of the package opensp-1.5release-0.1, which appeared
between the stable version (opensp-1.5pre5-5) and the testing version
(opensp-1.5release-3). The source (.dsc and .diff.gz) is fine, I don't need
the bina
On Aug 29, Sven Luther ([EMAIL PROTECTED]) wrote:
> I have a package that installs a xemacs specific .el file, which
> naturally don't build with the emacs20 package i have installed.
>
> Is there a way of specifying that only xemacs installs should build a
> given .el or something such ?
Ye
On Fri, Aug 29, 2003 at 08:34:41PM -0400, Neil Roeth wrote:
> Where can I get versions of packages that are not in any distribution?
> E.g., I want a copy of the package opensp-1.5release-0.1, which appeared
> between the stable version (opensp-1.5pre5-5) and the testing version
> (opensp-1.5releas
Jamin W. Collins wrote:
> I prefer an alternate structure where you start with the project as a
> top level. This keeps all project (package) related files under one
> directory in the project:
>
>project/
> trunk/
> branches/
> tags/
> vendor/
The only problem wit
On Thu, Aug 28, 2003 at 09:56:29PM -0400, Joey Hess wrote:
> Jamin W. Collins wrote:
> > I prefer an alternate structure where you start with the project as
> > a top level. This keeps all project (package) related files under
> > one directory in the project:
> >
> >project/
> > tru
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize everything in this
reply to myself.
Managing Debian packages wi
On Fri, Aug 29, 2003 at 12:44:02PM +0300, Fabian Fagerholm wrote:
>
> * Check out the trunk you just created into a directory called
> project- (svn co).
I was with you up to this point. I don't normally name my working copy
in the form project- as that form is needed for actually m
#include
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
> On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
> > How do I manage a new Debian package with Subversion?
>
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everythin
Joey Hess <[EMAIL PROTECTED]> wrote:
> [-- text/plain, encoding quoted-printable, charset: us-ascii, 143 lines --]
>
> Here are 15 to remove. FWIW I looked at a total of ~50 packages to find
> these. All bugs have been chosschecked against the NMU claims page which
> is why mindi and mondo are not
[ This is a repost of the following article: ]
[ From: [EMAIL PROTECTED] (Bruno Rodrigues)]
[ Subject: Re: More Assignments]
[ Newsgroups: gmane.linux.debian.devel.mentors,gmane.linux.debian.devel.rele
Does anyone care to upload my new php4-imagick package ?
This package closes #206960: php4-imagick: This package doesn't work
with the newer imagemagick.
Package is available at http://litux.org/debian/unstable
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tro
Fabian Fagerholm wrote:
> Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
> insight into this issue. I will try to summarize everything in this
> reply to myself.
Nice job writing this up, here are some corrections.
> The repository will have the following structure:
>
> trun
Jamin W. Collins wrote:
> I was with you up to this point. I don't normally name my working copy
> in the form project- as that form is needed for actually making
> hte package and for that we need an exported copy of the working copy.
Actually, dpkg-buildpackage does not care what you name the b
On Fri, Aug 29, 2003 at 12:30:46PM -0400, Joey Hess wrote:
> Fabian Fagerholm wrote:
> > * B.B. svn_load_dirs -t tags/projectX/upstream/
> >url://host/repos/ branches/projectX/upstream
> >/path/to/new/version
>
> I've only ever had to do this once, and
Hello,
I have a package that installs a xemacs specific .el file, which
naturally don't build with the emacs20 package i have installed.
Is there a way of specifying that only xemacs installs should build a
given .el or something such ?
Friendly,
Sven Luther
--
To UNSUBSCRIBE, email to [EMAI
Quoting Sven Luther <[EMAIL PROTECTED]>:
> Hello,
Hello,
> I have a package that installs a xemacs specific .el file, which
> naturally don't build with the emacs20 package i have installed.
>
> Is there a way of specifying that only xemacs installs should build a
> given .el or something such
[EMAIL PROTECTED] (Geert Stappers) writes:
> On Thu, Aug 28, 2003 at 11:54:58AM +0200, Goswin von Brederlow wrote:
> > Fabio Massimo Di Nitto <[EMAIL PROTECTED]> writes:
> >
> > > On Wed, 27 Aug 2003, Eric Winger wrote:
> > >
> > > > In putting my packages to my local repository, I've encountere
#include
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
> Actually, dpkg-buildpackage does not care what you name the build
> directory of a package.
>
> Persaonally, I use just packagename for the directory names and build
> directly from them, using a collection of ugly hacks to ignore the .svn
>
On Fri, Aug 29, 2003 at 10:30:46PM +0200, Eduard Bloch wrote:
>
> Question: how do you manage upstream and Debian branches? I encounter
> this problem while trying to find the best concept for svn-uupdate.
>
> The first idea was:
>
> branches/upstream/a.b ---> branches/ups
#include
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
> What _stupidness_ are you refering to? I've always just used something
> like:
>
>svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
change
Eduard Bloch wrote:
> However, a possible implementation failed completely because of
> stupideness of "svn merge". So we have to find an alternative solution
> with diff&patch&cp. OTOH it is not possible to keep the version history of
> every file.
I think you're looking for svn_load_dirs.
--
s
45 matches
Mail list logo
