t; What is the typical way one would go about adopting a package?
> If you mean an orphaned one, just upload it with you as the
> maintainer, in
> addition to the O bug management described at
> https://www.debian.org/devel/wnpp/#l3
>
> > I've heard that writing a patch and
On Tue, Jun 15, 2021 at 03:30:41AM -0500, Brian Thompson wrote:
> What is the typical way one would go about adopting a package?
If you mean an orphaned one, just upload it with you as the maintainer, in
addition to the O bug management described at
https://www.debian.org/devel/wnpp/#l3
>
Hi Brian,
thanks for offering to take over an important package.
On Tue, Jun 15, 2021 at 03:30:41AM -0500, Brian Thompson wrote:
> What is the typical way one would go about adopting a package? I've
> heard that writing a patch and proposing it might be a good starting
> point. S
What is the typical way one would go about adopting a package? I've
heard that writing a patch and proposing it might be a good starting
point. Specifically, I am looking at apt-listchanges.
Best regards,
Brian
On Fri, Aug 16, 2013 at 08:46:49PM +0200, Mario Trangoni wrote:
> Can someone help me on the steps to follow for adopting a package at
> debian?
http://www.debian.org/devel/wnpp/
http://www.debian.org/doc/manuals/developers-reference/pkgs.html#adopting
--
WBR, wRAR
signature.asc
Descr
Can someone help me on the steps to follow for adopting a package at
debian?
Thanks and best regards,
Mario Trangoni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Shaun,
thanks for your interest to help Debian.
On 07.09.2011 12:37, Shaun Silk wrote:
> Do I have to find a sponsor for this package? How do I proceed?
Yes, you need a sponsor. Please read [1][2] to get the idea. You may
also find the New Mainta
I am adopting an orphaned package (ircii), I have changed the title to ITA, and
I have
also changed the owner using cont...@bugs.debian.org. As the last package built
was from 2008, I have started
work on building the 2011 version, patching the build system etc. I also have
an account
on mentor
On Fri, Apr 25, 2008 at 11:42:41AM +0200, Vincent Bernat wrote:
> It seems that you have awaken the previous maintainer who have stolen your
> ITA. I hope that this won't bug you.
Yes, I have already noticed. That is perfectly ok with me.
To Alan Bain:
-
If you are reding this list, c
On Fri, 25 Apr 2008 00:05:26 +0400, Stanislav Maslovski
<[EMAIL PROTECTED]> wrote:
>> > === 8<
>> > package wnpp
>> > retitle 465910 ITA: nec -- NEC2 Antenna Modelling System
>> > owner 465910 !
>> > quit
>> > === >8 ===
Amaya <[EMAIL PROTECTED]> writes:
> Luis Rodrigo Gallardo Cruz wrote:
> > You don't actually need the 'quit', but it hurts noone.
>
> There actuatually seems to be a trend to use 'kthxbye' nowadays, which
> is not documented, but seems to work, and a lot cooler and lolcatter
On Thu, 24 Apr 2008, Amaya wrote:
> Luis Rodrigo Gallardo Cruz wrote:
> > You don't actually need the 'quit', but it hurts noone.
>
> There actuatually seems to be a trend to use 'kthxbye' nowadays,
> which is not documented, but seems to work, and a lot cooler and
> lolcatter
It is "documnted" o
Luis Rodrigo Gallardo Cruz wrote:
> You don't actually need the 'quit', but it hurts noone.
There actuatually seems to be a trend to use 'kthxbye' nowadays, which
is not documented, but seems to work, and a lot cooler and lolcatter
From http://www.debian.org/Bugs/server-control
quit
On Thu, Apr 24, 2008 at 02:36:37PM -0500, Luis Rodrigo Gallardo Cruz wrote:
> On Thu, Apr 24, 2008 at 11:25:11PM +0400, Stanislav Maslovski wrote:
> > Shall this mail sent from my own address to
> > [EMAIL PROTECTED] suffice for setting an ITA?
> >
> > === 8< ==
On Thu, Apr 24, 2008 at 11:25:11PM +0400, Stanislav Maslovski wrote:
> As I have never worked with the BTS control bot, I am asking for
> directions. Shall this mail sent from my own address to
> [EMAIL PROTECTED] suffice for setting an ITA?
>
> === 8< =
Hello mentors,
Reading the list of orphaned packages I have noticed that package "nec"
has been orphaned [1]. Because I use NEC2 in antenna related research
I think that I can adopt this package.
At the moment I am not a maintainer of any package in Debian nor a DD,
however I have been packaging
Székelyi Szabolcs wrote:
> when adopting a package, sould I first contact the original maintainer
> and the the retitle the 'O:' bug to 'ITA:' or retitle it first and
> contact the maintainer afterwards?
depends.
when there is a O:, retitle it to ITA:, get a pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Mentors,
when adopting a package, sould I first contact the original maintainer
and the the retitle the 'O:' bug to 'ITA:' or retitle it first and
contact the maintainer afterwards?
As I remember, a non-dd is allowed to a
On Sun, 2006-07-02 at 22:53 +0200, Bartosz Fenski aka fEnIo wrote:
> Please don't feel offended. I tried to contact you several times and
> I hijacked this packaged because I couldn't do that.
In the future, an NMU might be a better start for improving a package
that lacks care, rather than hijac
George Danchev wrote:
On Sunday 02 July 2006 23:53, Bartosz Fenski aka fEnIo wrote:
--cut--
From the bug reports you've filed against calcurse it's clear to me that
you probably are the perfect person to maintain it, so in the final
analysis I have no issue with you becoming the maintainer.
On Sunday 02 July 2006 23:53, Bartosz Fenski aka fEnIo wrote:
--cut--
> > From the bug reports you've filed against calcurse it's clear to me that
> > you probably are the perfect person to maintain it, so in the final
> > analysis I have no issue with you becoming the maintainer. But like I
> > s
On Sun, Jul 02, 2006 at 12:11:36PM -0400, Ryan Coyner wrote:
> Hello Mr. Fenski
Hi.
> As the maintainer of the package calcurse (at least until yesterday) I
> was surprised, both good and bad, this morning to check my email and
> find that a new version of calcurse has been uploaded to Debian.
>
* Ryan Coyner [Sun, 02 Jul 2006 12:11:36 -0400]:
> However I must admit that I'll think twice about packaging software in
> the future if there is indeed a policy where a DD can simply take over
> maintainence of a package without even sending me a courtesy email.
No, there isn't such policy. To
Hello Mr. Fenski
As the maintainer of the package calcurse (at least until yesterday) I
was surprised, both good and bad, this morning to check my email and
find that a new version of calcurse has been uploaded to Debian.
I was surprised in a good way because the upload of version 1.4 was
overdu
On Sat, Mar 27, 2004 at 01:24:48PM +1100, Anibal Monsalve Salazar may have
written:
> On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote:
> >deb http://cvs.delink.net/debian/ delink contrib
> >deb-src http://cvs.delink.net/debian/ delink contrib
>
> I couldn't get relay-ctrl_3.1.1.orig
On Sat, Mar 27, 2004 at 01:24:48PM +1100, Anibal Monsalve Salazar may have written:
> On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote:
> >deb http://cvs.delink.net/debian/ delink contrib
> >deb-src http://cvs.delink.net/debian/ delink contrib
>
> I couldn't get relay-ctrl_3.1.1.orig.
On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote:
>deb http://cvs.delink.net/debian/ delink contrib
>deb-src http://cvs.delink.net/debian/ delink contrib
I couldn't get relay-ctrl_3.1.1.orig.tar.gz.
$ apt-get source relay-ctrl
Reading Package Lists... Done
Building Dependency Tree...
On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote:
>deb http://cvs.delink.net/debian/ delink contrib
>deb-src http://cvs.delink.net/debian/ delink contrib
I couldn't get relay-ctrl_3.1.1.orig.tar.gz.
$ apt-get source relay-ctrl
Reading Package Lists... Done
Building Dependency Tree...
On Fri, Mar 26, 2004 at 01:39:24PM +1100, Anibal Monsalve Salazar may have
written:
>
> Yes. You put in one directory the files with the following suffixes:
> .diff.gz, .dsc, .changes, .deb and .orig.tar.gz. For example, look at
> [2] or any other debian package for that matter. Note that you hav
On Fri, Mar 26, 2004 at 01:39:24PM +1100, Anibal Monsalve Salazar may have written:
>
> Yes. You put in one directory the files with the following suffixes:
> .diff.gz, .dsc, .changes, .deb and .orig.tar.gz. For example, look at
> [2] or any other debian package for that matter. Note that you have
On Thu, Mar 25, 2004 at 08:24:54PM -0500, Brian T Glenn wrote:
>On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have
>written:
>>On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
>>>I have submitted an ITA (Bug#238972), but the original RFA is
>>>Bug#238972.
>>
On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have
written:
> On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
> >I have submitted an ITA (Bug#238972), but the original RFA is
> >Bug#238972.
>
> The original RFA is 237446.
>
> There was no need for a new bu
On Thu, Mar 25, 2004 at 08:24:54PM -0500, Brian T Glenn wrote:
>On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have written:
>>On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
>>>I have submitted an ITA (Bug#238972), but the original RFA is
>>>Bug#238972.
>>
>>
On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have written:
> On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
> >I have submitted an ITA (Bug#238972), but the original RFA is
> >Bug#238972.
>
> The original RFA is 237446.
>
> There was no need for a new bug
On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
>I have submitted an ITA (Bug#238972), but the original RFA is
>Bug#238972.
The original RFA is 237446.
There was no need for a new bug report (238972). You have already retitled
bug report 237446. Now, you need to merge 237446 and 2
On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote:
>I have submitted an ITA (Bug#238972), but the original RFA is
>Bug#238972.
The original RFA is 237446.
There was no need for a new bug report (238972). You have already retitled
bug report 237446. Now, you need to merge 237446 and 2
I have submitted an ITA (Bug#238972), but the original RFA is
Bug#238972. I have new packages created for relay-ctrl at the current
version per the RFA. I attempted to contact the current maintainer,
but i have received no response after a few days.
What else should I be doing in order to execute
I have submitted an ITA (Bug#238972), but the original RFA is
Bug#238972. I have new packages created for relay-ctrl at the current
version per the RFA. I attempted to contact the current maintainer,
but i have received no response after a few days.
What else should I be doing in order to execute
hello dariush...
Received at 2003-01-14 / 22:24 by Dariush Pietrzak:
> I'd like to adopt qiv (bug #176329), but I am not a DD yet.
> I am using this package and don't want to see it removed. Should I file
> ITA?
> Or maybe - how long should I wait for some real DD to take care of this
> package
Hello,
I'd like to adopt qiv (bug #176329), but I am not a DD yet.
I am using this package and don't want to see it removed. Should I file
ITA?
Or maybe - how long should I wait for some real DD to take care of this
package before filing ITA myself?
--
Dariush Pietrzak,
"Who are we helping? - t
hello dariush...
Received at 2003-01-14 / 22:24 by Dariush Pietrzak:
> I'd like to adopt qiv (bug #176329), but I am not a DD yet.
> I am using this package and don't want to see it removed. Should I file
> ITA?
> Or maybe - how long should I wait for some real DD to take care of this
> package
Hello,
I'd like to adopt qiv (bug #176329), but I am not a DD yet.
I am using this package and don't want to see it removed. Should I file
ITA?
Or maybe - how long should I wait for some real DD to take care of this
package before filing ITA myself?
--
Dariush Pietrzak,
"Who are we helping? - t
Andreas Klein <[EMAIL PROTECTED]> writes:
> 1. Where can I find the old-version of the package. (Since I want to
> adopt an existing package I think I can skip the steps descriped in the
> sections 3-6 in the "Debian New Maintainers' Guide" and start with section
> 9.)
apt-get source PACKAGE
Or l
Thanks for your hints. But I have still two questions:
1. Where can I find the old-version of the package. (Since I want to
adopt an existing package I think I can skip the steps descriped in the
sections 3-6 in the "Debian New Maintainers' Guide" and start with section
9.)
2. I can not use the p
Andreas Klein <[EMAIL PROTECTED]> writes:
> 1. Where can I find the old-version of the package. (Since I want to
> adopt an existing package I think I can skip the steps descriped in the
> sections 3-6 in the "Debian New Maintainers' Guide" and start with section
> 9.)
apt-get source PACKAGE
Or l
Thanks for your hints. But I have still two questions:
1. Where can I find the old-version of the package. (Since I want to
adopt an existing package I think I can skip the steps descriped in the
sections 3-6 in the "Debian New Maintainers' Guide" and start with section
9.)
2. I can not use the p
On Tue, Oct 22, 2002 at 09:03:58AM +0200, Andreas Klein wrote:
> I want do adopt the package **larswm**.
>
> I have several years Linux experience but I'm a newbi to debian. So I need
> a quick introdution in "Howto maintain a debian package".
Read practically all the links in http://www.debian.o
On Tue, Oct 22, 2002 at 09:03:58AM +0200, Andreas Klein wrote:
> I want do adopt the package **larswm**.
>
> I have several years Linux experience but I'm a newbi to debian. So I need
> a quick introdution in "Howto maintain a debian package".
Read practically all the links in http://www.debian.o
Andreas Klein <[EMAIL PROTECTED]> writes:
> I want do adopt the package **larswm**.
>
> I have several years Linux experience but I'm a newbi to debian. So I need
> a quick introdution in "Howto maintain a debian package".
http://www.debian.org/doc/maint-guide/
--
People said I was dumb, but I
I want do adopt the package **larswm**.
I have several years Linux experience but I'm a newbi to debian. So I need
a quick introdution in "Howto maintain a debian package".
Thanks for your help.
Andreas Klein
Andreas Klein <[EMAIL PROTECTED]> writes:
> I want do adopt the package **larswm**.
>
> I have several years Linux experience but I'm a newbi to debian. So I need
> a quick introdution in "Howto maintain a debian package".
http://www.debian.org/doc/maint-guide/
--
People said I was dumb, but I
I want do adopt the package **larswm**.
I have several years Linux experience but I'm a newbi to debian. So I need
a quick introdution in "Howto maintain a debian package".
Thanks for your help.
Andreas Klein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscrib
On Fri, 2 Mar 2001 00:48:57 +0100, Javier Viñuales Gutiérrez
<[EMAIL PROTECTED]> wrote:
>I know to make a _new_ debian package from its sources but now, I need to
>package a _orphaned_ package from its diff, dsc, orig and changes files.
>What do I have to do?.
You probably only have to dpkg-source
On Fri, 2 Mar 2001 00:48:57 +0100, Javier Viñuales Gutiérrez
<[EMAIL PROTECTED]> wrote:
>I know to make a _new_ debian package from its sources but now, I need to
>package a _orphaned_ package from its diff, dsc, orig and changes files.
>What do I have to do?.
You probably only have to dpkg-sourc
On Fri, Mar 02, 2001 at 12:48:57AM +0100, Javier Vi?uales Guti?rrez wrote:
> I know to make a _new_ debian package from its sources but now, I need to
> package a _orphaned_ package from its diff, dsc, orig and changes files.
> What do I have to do?.
First, apt-get source . This will download the
Hello,
I know to make a _new_ debian package from its sources but now, I need to
package a _orphaned_ package from its diff, dsc, orig and changes files.
What do I have to do?.
Thank you.
--
Javier Viñuales Gutiérrez <[EMAIL PROTECTED]>
GnuPG public information: pub 1024D/4EB82468
1C2A 024
On Fri, Mar 02, 2001 at 12:48:57AM +0100, Javier Vi?uales Guti?rrez wrote:
> I know to make a _new_ debian package from its sources but now, I need to
> package a _orphaned_ package from its diff, dsc, orig and changes files.
> What do I have to do?.
First, apt-get source . This will download the
Hello,
I know to make a _new_ debian package from its sources but now, I need to
package a _orphaned_ package from its diff, dsc, orig and changes files.
What do I have to do?.
Thank you.
--
Javier Viñuales Gutiérrez <[EMAIL PROTECTED]>
GnuPG public information: pub 1024D/4EB82468
1C2A 02
On 26-Feb-2001 Sean Preston wrote:
> Hi
>
> I am a little new at this and confused by the documentation on the bug
> track page. How do I go about adopting a package that is up for adoption?
>
> I believe I have to send a message to [EMAIL PROTECTED] but what do I use
Hi
I am a little new at this and confused by the documentation on the bug
track page. How do I go about adopting a package that is up for adoption?
I believe I have to send a message to [EMAIL PROTECTED] but what do I use
in the subject?
Just a little confused by these options.
OIf you
On 26-Feb-2001 Sean Preston wrote:
> Hi
>
> I am a little new at this and confused by the documentation on the bug
> track page. How do I go about adopting a package that is up for adoption?
>
> I believe I have to send a message to [EMAIL PROTECTED] but what do I use
Hi
I am a little new at this and confused by the documentation on the bug
track page. How do I go about adopting a package that is up for adoption?
I believe I have to send a message to [EMAIL PROTECTED] but what do I use
in the subject?
Just a little confused by these options.
OIf you
On Tue, Aug 15, 2000 at 01:00:46AM -0400, Steven R . Baker wrote:
> I changed the control files, did a dch -i, and stuff, and did
> dpkg-buildpackage and it didn't generate a new .changes file, just a
> .diff and a .dsc???
Do you have a gpg key with the exact ID in your Maintainer: field?
Send the
On Tue, Aug 15, 2000 at 01:00:46AM -0400, Steven R . Baker wrote:
> I changed the control files, did a dch -i, and stuff, and did
> dpkg-buildpackage and it didn't generate a new .changes file, just a
> .diff and a .dsc???
Do you have a gpg key with the exact ID in your Maintainer: field?
Send th
Thanks. That's basically what I was thinking, only it never occurred
to me at all until after the package was installed. I'll fix it.
Which leads me to my next question. What's the proper way to do
another release of my package?
I changed the control files, did a dch -i, and stuff, and did
dpk
On Mon, Aug 14, 2000 at 11:58:38PM -0400, Steven R . Baker wrote:
> Hi everyone,
> I just adopted AfterStep, but ran into some problems with the
> adoption process. The previous AfterStep package packaged version
> 1.6.10, and the current (stable) version is 1.8.3. So, after speaking
> with the
> So, I just created a new package. Should I have merged the
> changelogs into one, and made the packages look similar?
Yes. If the package name is the same, you should have.
The package should as cleanly as possible replace the old one.
History is important, even if it's just "new version up
Hi everyone,
I just adopted AfterStep, but ran into some problems with the
adoption process. The previous AfterStep package packaged version
1.6.10, and the current (stable) version is 1.8.3. So, after speaking
with the previous maintainer (a while ago) I packaged 1.8.3.
When packaging 1.8.3,
Thanks. That's basically what I was thinking, only it never occurred
to me at all until after the package was installed. I'll fix it.
Which leads me to my next question. What's the proper way to do
another release of my package?
I changed the control files, did a dch -i, and stuff, and did
dp
On Mon, Aug 14, 2000 at 11:58:38PM -0400, Steven R . Baker wrote:
> Hi everyone,
> I just adopted AfterStep, but ran into some problems with the
> adoption process. The previous AfterStep package packaged version
> 1.6.10, and the current (stable) version is 1.8.3. So, after speaking
> with th
> So, I just created a new package. Should I have merged the
> changelogs into one, and made the packages look similar?
Yes. If the package name is the same, you should have.
The package should as cleanly as possible replace the old one.
History is important, even if it's just "new version u
Hi everyone,
I just adopted AfterStep, but ran into some problems with the
adoption process. The previous AfterStep package packaged version
1.6.10, and the current (stable) version is 1.8.3. So, after speaking
with the previous maintainer (a while ago) I packaged 1.8.3.
When packaging 1.8.3
*-Mark Brown <[EMAIL PROTECTED]>
|
| I've got a feeling I'm missing something really obvious here. I'd like
| to adopt the orphaned mpich package, so I mailed the wnpp. I first
| mailed them a bit over a week ago, but I was a bit confused (I hadn't
| properly read the documentation at the top of
On Fri, 4 Dec 1998, Mark Brown wrote:
> I've got a feeling I'm missing something really obvious here. I'd like
> to adopt the orphaned mpich package, so I mailed the wnpp. I first
> mailed them a bit over a week ago, but I was a bit confused (I hadn't
> properly read the documentation at the top
I've got a feeling I'm missing something really obvious here. I'd like
to adopt the orphaned mpich package, so I mailed the wnpp. I first
mailed them a bit over a week ago, but I was a bit confused (I hadn't
properly read the documentation at the top of the page) so I sent
another message earlier
75 matches
Mail list logo
