Hi,
Meeting at Debconf we discussed, how a policy compliant XML core and
package registration system could look like. I'd like to share the
results:
- a package can install one or more catalogs, which go into the package
directory in /usr/share (a catalog written by the package maintainer
can of
Yes, that would be great! --Kris
On Jul 24, 2015 5:35 PM, "Daniel Leidert"
wrote:
> Hi Kris,
>
> Am Samstag, den 30.05.2015, 22:08 -0400 schrieb Kristoffer Rose:
> > I have XML expertise, I am a DD, and I maintain nothing for now (only
> > have a few ITPs out).
> >
> > Any chance you would be at
Hi Kris,
Am Samstag, den 30.05.2015, 22:08 -0400 schrieb Kristoffer Rose:
> I have XML expertise, I am a DD, and I maintain nothing for now (only
> have a few ITPs out).
>
> Any chance you would be at DebCamp and could do a two day intense
> "catchup" on the involved work?
I'll be at DebConf.
Am Samstag, den 30.05.2015, 22:08 -0400 schrieb Kristoffer Rose:
> Dear Daniel and Osamu,
>
>
> I have XML expertise, I am a DD, and I maintain nothing for now (only
> have a few ITPs out).
>
>
> Any chance you would be at DebCamp and could do a two day intense
> "catchup" on the involved work?
Am Samstag, den 30.05.2015, 19:00 +0200 schrieb W. Martin Borgert:
> On 2015-05-28 23:24, Daniel Leidert wrote:
[not using DB toolchain]
> Just out of curiosity: What are you using now?
I haven't done much documentation lately. But I use GROFF for writing
manual pages for Debian packages. Even wi
Dear Daniel and Osamu,
I have XML expertise, I am a DD, and I maintain nothing for now (only have
a few ITPs out).
Any chance you would be at DebCamp and could do a two day intense "catchup"
on the involved work?
Best,
Kris
On Sat, May 30, 2015 at 10:28 AM, Osamu Aoki wrote:
> Hi Daniel,
On 2015-05-28 23:24, Daniel Leidert wrote:
> I was part of the Debian XML/SGML team [1] for quite some time and it
> was fun maintaining the whole DocBook toolchain. Unfortunately I'm not
> using it anymore and thus have lost interest in these packages. Now
> after Jessie has been released, I'm fin
Hi Daniel,
Thanks a lot for maintaining these in good shape.
On Thu, May 28, 2015 at 11:24:17PM +0200, Daniel Leidert wrote:
> x-post
>
> Hi everybody,
>
> I was part of the Debian XML/SGML team [1] for quite some time and it
> was fun maintaining the whole DocBook toolchain. Unfortunately I'm
x-post
Hi everybody,
I was part of the Debian XML/SGML team [1] for quite some time and it
was fun maintaining the whole DocBook toolchain. Unfortunately I'm not
using it anymore and thus have lost interest in these packages. Now
after Jessie has been released, I'm finally stepping back as mainta
oceed? Make a new gpg key, package a new version and look for a
> sponsor to make this last upload? Just fill the wnpp bug for html2ps and
> be done with? Any advices?
You only need to file the orphaning bugs.
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subj
Hello,
I am too busy for working on my debian packages right now. Thus, I need
to orphan my two packages (tcpstat and html2ps). However, I don't have
my gpg key anymore and my sponsor is not available. I have filled a bug
on wnpp regarding tcpstat
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
On Wed, Nov 07, 2012 at 09:26:28AM +0100, Raphael Hertzog wrote:
> (Dropping the bug)
>
> On Tue, 06 Nov 2012, Steve Langasek wrote:
> > Private mails should not be a justification for expedited orphaning of
> > packages. With this bug report you have *now* used
(Dropping the bug)
On Tue, 06 Nov 2012, Steve Langasek wrote:
> Private mails should not be a justification for expedited orphaning of
> packages. With this bug report you have *now* used a proper channel for
> notifying the maintainer that you want to salvage the package; so the clock
son to prioritize responding to it?
>
> Private mails should not be a justification for expedited orphaning of
> packages. With this bug report you have *now* used a proper channel
> for notifying the maintainer that you want to salvage the package; so
> the clock starts now, not when
hould give the maintainer
reason to prioritize responding to it?
Private mails should not be a justification for expedited orphaning of
packages. With this bug report you have *now* used a proper channel for
notifying the maintainer that you want to salvage the package; so the clock
starts now, no
Package: auditd
Severity: serious
Version: 1:1.7.18-1.1
Hi,
I've tried to enter in contact with Philipp Matthias regarding the
status of the audit package. I've sent a first mail a bit more than a
month ago and a second one 15 days later. But I unfortunately didn't
get any answer so far.
The las
Hello,
looking at dbs-using packages, diffmon looks like something that isn't
really maintained:
- last maintainer upload in 2002
- 5 NMUs in a row since then, first in 2006
I'd appreciate being kept in the loop, whatever the outcome is.
Mraw,
KiBi.
signature.asc
Description: Digital signatu
On 05/30/2012 02:49 AM, Thomas Goirand wrote:
> So, if nobody objects within the next following 2 or 3 days, and if Jack
> doesn't show up and oppose to this procedure, we'll do that.
>
> If anyone doesn't agree, please raise your concern *now* (including you,
> Jack).
>
> Cheers,
>
> Thomas Goi
Jonas Smedegaard dijo [Thu, May 31, 2012 at 05:52:47PM +0200]:
> > > You avoided my question, it seems: What does "Maintainer:" mean, then?
> >
> > What does "Uploaders:" field mean?
>
> You still avoid my question: What does "Maintainer:" mean?
This is getting silly. Please stop the word-defini
On Donnerstag, 31. Mai 2012, Jonas Smedegaard wrote:
> You still avoid my question: What does "Maintainer:" mean?
why do you ask rhetoric questions? It's defined in policy and you know it. So
whats the point?
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "uns
On 12-05-31 at 04:43pm, George Danchev wrote:
> On Thursday 31 May 2012 16:15:31 Jonas Smedegaard wrote:
> > [dropping PHP Pear team as cc]
> >
> > On 12-05-31 at 03:16pm, George Danchev wrote:
> > > On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
> > > > > You and a lot of others fail to
On Thursday 31 May 2012 16:15:31 Jonas Smedegaard wrote:
> [dropping PHP Pear team as cc]
>
> On 12-05-31 at 03:16pm, George Danchev wrote:
> > On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
> > > > You and a lot of others fail to realize that the *SPONSOR* is
> > > > responsible for the
[dropping PHP Pear team as cc]
On 12-05-31 at 03:16pm, George Danchev wrote:
> On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
> > > You and a lot of others fail to realize that the *SPONSOR* is
> > > responsible for the package.
> >
> > Huh?!?
> >
> > What does "Maintainer:" mean if no
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
Hi,
> > You and a lot of others fail to realize that the *SPONSOR* is
> > responsible for the package.
>
> Huh?!?
>
> What does "Maintainer:" mean if not the entity being responsible for,
> well, maintaining?!?
Who is responsible for the
Jonas Smedegaard (31/05/2012):
> I have heard before the argument of the sponsor having responsibility,
> but in reality I have *never* heard of sponsors actually being held
> responsible for anything but the concrete upload of a specific
> packaging release.
Suggested reading:
http://bugs.debi
On 12-05-31 at 09:22am, Bernd Zeimetz wrote:
> On 05/30/2012 11:11 AM, Jonas Smedegaard wrote:
> It is better to have a well maintained package than to ait for
> somebody who collected a number of NMUs and doesn't react to bug
> reports for years.
I perfectly agree.
But it is better to have re
On 05/30/2012 11:11 AM, Jonas Smedegaard wrote:
> On 12-05-30 at 11:30am, Thomas Goirand wrote:
>> We aren't kicking him, we want to have the package team maintained.
>> He's fine to come and join!
>
> You want to play by your rules (file), not his. That's kicking to me.
>
>
>> This doesn't rea
On 12-05-30 at 09:41pm, Thomas Goirand wrote:
> On 05/30/2012 05:11 PM, Jonas Smedegaard wrote:
> > you use Debian freeze as argument for swift takeover. I find it not
> > respectful to rush processing like that!
> >
>
> Again, no! That wasn't my point. My point was that it was left
> unmaint
Hi,
On 30.05.2012 18:17, Bart Martens wrote:
> On Wed, May 30, 2012 at 09:41:30PM +0800, Thomas Goirand wrote:
>> By the way, do other think that, even in this case, I should keep the
>> changes
>> as minimum as possible? Or is it ok, considering that all of our
>> toolsets have
>> changed since t
On Wed, May 30, 2012 at 09:41:30PM +0800, Thomas Goirand wrote:
> By the way, do other think that, even in this case, I should keep the
> changes
> as minimum as possible? Or is it ok, considering that all of our
> toolsets have
> changed since the last upload (eg: we now have pkg-php-tools and dh
Thomas Goirand writes:
> By the way, do other think that, even in this case, I should keep the
> changes
> as minimum as possible? Or is it ok, considering that all of our
> toolsets have
> changed since the last upload (eg: we now have pkg-php-tools and dh 8
> sequencer), that we do a bit more c
On 05/30/2012 05:11 PM, Jonas Smedegaard wrote:
> *nothing* qualifies for a hijacking.
>
> With hijacking I mean disrespectful takeover.
>
> Either respect maintainership by only NMUing, or respectfully resolve
> with the Debian community that the current maintainer is unfit for the
> task.
Ok,
On 12-05-30 at 11:30am, Thomas Goirand wrote:
> We aren't kicking him, we want to have the package team maintained.
> He's fine to come and join!
You want to play by your rules (file), not his. That's kicking to me.
> This doesn't really qualify for an NMU, nor does the upgrade to the
> latest
On 05/30/2012 03:51 AM, Jonas Smedegaard wrote:
> I strongly object to this as a general principle: Debian freezing is no
> excuse for hijacking!
>
That's not the reason, the reason is that we've been working on tools to
improve
PHP package quality, and recently noticed that php-codesniffer wa
On 12-05-30 at 02:49am, Thomas Goirand wrote:
> we'd like to see the latest version in Wheezy
OK, this request exists:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599617
> We sent a mail 5 days ago to Jack Bates, and he didn't reply. It's
> currently obvious that there's very few chances th
Hi,
On 29.05.2012 21:51, Jonas Smedegaard wrote:
> Seems you had several years of solving this issue, yet you waited until
Similarly, the maintainer had 4 years to care about his package.
> Did you consider an NMU?
That might be an alternative, but looking at the current bug list people
will a
On 12-05-30 at 02:49am, Thomas Goirand wrote:
> Jack Bates is supposed to maintain php-codesniffer,
[snip]
> this package last upload was from 2008-10-05,
[snip]
> we'd like to see the latest version in Wheezy
[snip]
> We sent a mail 5 days ago to Jack Bates, and he didn't reply. It's
> currently
Hi,
Jack Bates is supposed to maintain php-codesniffer, available from:
http://pear.php.net/package/PHP_CodeSniffer
Unfortunately, the PTS for this package shows that this package last
upload was from 2008-10-05, few months after version 1.1.0 was released
upstream (on the 2008-07-14). Upstream h
Hi,
I intend to adopt these for pkg-perl:
> * libtest-number-delta-perl
> libx11-freedesktop-desktopentry-perl
> libexporter-tidy-perl
> libextutils-depends-perl
> libextutils-pkgconfig-perl
>Misc perl libs. Should probably go to the perl group.
>
and these too:
> * libcairo-perl*
retitle 456924 O: libgstreamer-perl -- Perl interface to the gstreamer
noowner 456924
thanks
Heya,
In my quest to get rid of tasks I don't have the motivation to actually
work on, I want to give up some of my packages. Basically, there are
three groups: Packages that are just fine and need a main
Hi !
I would like to request orphaning of paramiko:
http://packages.qa.debian.org/p/paramiko.html
Only NMU upload have been done since more than one year and its current
maintainer is totally unresponsive (see #460706 for example). It seems
that its email address is now bouncing.
Thanks
(Added debian-gtk-gnome to the lists.)
On Mon, Sep 11, 2006 at 01:24:39PM -0700, Thomas Bushnell BSG wrote:
> Now that the gnome-2 version of gnucash has migrated into testing, I'm
> orphaning them. There are still a tiny number of packages that rely
> on them, so they should not b
x27;m
orphaning them. There are still a tiny number of packages that rely
on them, so they should not be peremptorily removed without
coordinating with or examining those other packages: something I don't
have time to do right now.
The gnome-1 packages concerned are
bonobo, gal0.x, gnome-libs, g
Nathanael Nerode wrote:
> The classic thing to do is to send a note to the bug trail saying one of
> "I sent the fix upstream and will wait for them to fix it"
> "I need help finding out whether this patch works"
> "This patch doesn't work"
> "I don't have time to deal with this, NMUs please"
>
>
Chris Hanson wrote:
> Nathanael Nerode wrote:
>> As discussed in this bug, mhash's maintainer appears to be MIA or out to
>> lunch.
>>
>> Is it OK if we forcibly orphan the package now?
>
> What exactly do you want me to do?
The classic thing to do is to send a note to the bug trail saying one of
Nathanael Nerode <[EMAIL PROTECTED]> writes:
> As discussed in this bug, mhash's maintainer appears to be MIA or
> out to lunch.
>
> Is it OK if we forcibly orphan the package now?
There is no procedure for forcible orphaning the package.
If you have a fix for the bu
Nathanael Nerode wrote:
> As discussed in this bug, mhash's maintainer appears to be MIA or out to
> lunch.
>
> Is it OK if we forcibly orphan the package now?
What exactly do you want me to do? I released a new version recently,
and as far as I can tell there's no consensus on whether the sugg
As discussed in this bug, mhash's maintainer appears to be MIA or out to lunch.
Is it OK if we forcibly orphan the package now?
--
Nathanael Nerode <[EMAIL PROTECTED]>
"It's just a goddamned piece of paper."
-- President Bush, referring to the US Constitution
http://www.capitolhillblue.com/art
Hello QA-Team,
I am interested in keeping goobox current in Etch. The maintainer (who is
in NM) seems MIA (c.f. [1] where Vorlon indicates that orphaning may
be appropriate): Dan Korostelev ([EMAIL PROTECTED] and
[EMAIL PROTECTED]) has 4 packages in Debian:
Name: Last upload
.
Blackbook is dead upstream and needs to undergo the C++ transition.
Screentest is actually usable.
Strongly suggest orphaning his packages.
--
Nathanael Nerode <[EMAIL PROTECTED]>
A thousand reasons. http://www.thousandreasons.org/
Lies, theft, war, kidnapping, torture, rape, murder...
Get me
On Wed, Apr 13, 2005 at 01:22:56PM +0200, Jeremiah Foster wrote:
> I would like Debian to consider aspseek orphaned due to lack of CVS,
> forum, and mail reponse from develpers and maintainers.
There has been a mail exchange with the maintainer already, it's not in
sarge atm so not a urgent issue
I would like Debian to consider aspseek orphaned due to lack of CVS,
forum, and mail reponse from develpers and maintainers.
Jeremiah Foster
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Oct 01, 2004 at 05:56:05PM +1000, Anibal Monsalve Salazar wrote:
> On Fri, Oct 01, 2004 at 09:24:15AM +0200, Matthias Urlichs wrote:
> >For the record: the PTS says that 1.0.8-1 has been uploaded to Unstable,
> >presumably by the maintainer.
>
> It FTBFS on powerpc. See:
>
> http://buildd
* Anibal Monsalve Salazar [Sat, 02 Oct 2004 06:36:18 +1000]:
> On Fri, Oct 01, 2004 at 12:45:07PM -0500, Graham Wilson wrote:
> >libmng 1.0.8-1 builds fine for me on powerpc. I wonder if the build
> >error on voltaire is transient or not. In any case, I can upload a
> >local build if needed.
> Ple
On Fri, Oct 01, 2004 at 12:45:07PM -0500, Graham Wilson wrote:
>libmng 1.0.8-1 builds fine for me on powerpc. I wonder if the build
>error on voltaire is transient or not. In any case, I can upload a
>local build if needed.
Please do so and close #274334 when you upload it.
Anibal Monsalve Salaza
On Fri, Oct 01, 2004 at 05:56:05PM +1000, Anibal Monsalve Salazar wrote:
> On Fri, Oct 01, 2004 at 09:24:15AM +0200, Matthias Urlichs wrote:
> >For the record: the PTS says that 1.0.8-1 has been uploaded to Unstable,
> >presumably by the maintainer.
>
> It FTBFS on powerpc. See:
>
> http://buildd
On Fri, Oct 01, 2004 at 05:56:05PM +1000, Anibal Monsalve Salazar wrote:
> It FTBFS on powerpc. See:
>
> http://buildd.debian.org/fetch.php?&pkg=libmng&ver=1.0.8-1&arch=powerpc&stamp=1096518953&file=log&as=raw
Please file a bug instead. As you've seen in my latest mail in the
thread[1], this issu
On Fri, Oct 01, 2004 at 09:24:15AM +0200, Matthias Urlichs wrote:
>Hi, Jeroen van Wolffelaar wrote:
>>On Sat, Sep 25, 2004 at 02:53:59AM -0700, Steve Langasek wrote:
>>>The libmng package has not seen an upload since April 2003. [...]
>>>It looks like this package is i
On Fri, Oct 01, 2004 at 09:24:15AM +0200, Matthias Urlichs wrote:
> For the record: the PTS says that 1.0.8-1 has been uploaded to Unstable,
> presumably by the maintainer.
Yeah, after a polite reminder, he set himself quite actively to
maintaining his packages again, and actively harrassing (in a
Hi, Jeroen van Wolffelaar wrote:
> On Sat, Sep 25, 2004 at 02:53:59AM -0700, Steve Langasek wrote:
>> The libmng package has not seen an upload since April 2003. [...]
>> It looks like this package is in serious need of orphaning. Can someone
>> in QA confirm this to t
lude various important security fixes.
>
> It looks like this package is in serious need of orphaning. Can someone
> in QA confirm this to their satisfaction and orphan the package?
Will look into it, but pinging & waiting for feedback might take one to
two months until the actual orp
of orphaning. Can someone
in QA confirm this to their satisfaction and orphan the package?
Thanks,
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
On Fri, Jun 25, 2004 at 11:36:50AM +1000, Andrew Pollock wrote:
> On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
> > then do not many orphaned packages (if not most) fit into one of the
> > proposed resons and should be removed from testing?
> >
> > I think many packages coul
On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
> * Matthew Palmer [Mon, 21 Jun 2004 10:12:22 +1000]:
> > On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
>
> > > I wish more people had an attitude like this. Maybe it would make
> > > sense to ask people on d-d-a t
On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
[snip]
>
> then do not many orphaned packages (if not most) fit into one of the
> proposed resons and should be removed from testing?
>
> I think many packages could benefite from this in-the-middle approach:
> instead of co
* Matthew Palmer [Mon, 21 Jun 2004 10:12:22 +1000]:
> On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
> > I wish more people had an attitude like this. Maybe it would make
> > sense to ask people on d-d-a to review their own new packages and
> > consider whether it makes sense t
On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
> * Matthew Palmer <[EMAIL PROTECTED]> [2004-06-20 11:44]:
> > I'll volunteer to check my own packages, with a couple of recommendations:
>
> I wish more people had an attitude like this. Maybe it would make
> sense to ask people o
* Martin Michlmayr ([EMAIL PROTECTED]) [040620 14:25]:
> * Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> > If as maintainer you want your package not to be released but to remain
> > in unstable, then file a serious bug on the package to that effect and
> > tell the release team.
> Is the
* Frank Lichtenheld <[EMAIL PROTECTED]> [2004-06-20 21:20]:
> I played around a bit, my current stuff (nothing serious yet)
> is at http://people.debian.org/~djpig/pkg-invest/
> status.html at least shows the amount of work we're talking about:
> today it were 3350 new source packages when comparin
On Sat, Jun 19, 2004 at 02:20:38PM +0100, Martin Michlmayr wrote:
> In any case, I'd really like volunteers for something else: check
> which packages are going to ship new with sarge (i.e. which have not
> been in woody or another stable release) and take a closer look at
> them to see if we reall
* Matthew Palmer <[EMAIL PROTECTED]> [2004-06-20 11:44]:
> I'll volunteer to check my own packages, with a couple of recommendations:
I wish more people had an attitude like this. Maybe it would make
sense to ask people on d-d-a to review their own new packages and
consider whether it makes sense
On Sun, Jun 20, 2004 at 01:19:28PM +0100, Martin Michlmayr wrote:
> * Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> > If as maintainer you want your package not to be released but to remain
> > in unstable, then file a serious bug on the package to that effect and
> > tell the release team
* Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> If as maintainer you want your package not to be released but to remain
> in unstable, then file a serious bug on the package to that effect and
> tell the release team.
Is there no cleaner solution so those RC bugs don't show up in the RC
b
On Sun, Jun 20, 2004 at 11:44:53AM +1000, Matthew Palmer wrote:
> Do I bug FTPmasters about getting those two removed from testing, or the
> release team?
If as maintainer you want your package not to be released but to remain
in unstable, then file a serious bug on the package to that effect and
On Sat, Jun 19, 2004 at 02:20:38PM +0100, Martin Michlmayr wrote:
> In any case, I'd really like volunteers for something else: check
> which packages are going to ship new with sarge (i.e. which have not
> been in woody or another stable release) and take a closer look at
> them to see if we reall
* Andreas Barth <[EMAIL PROTECTED]> [2004-06-18 18:38]:
> I'm prepared to do the work for it, but would like to pre-warn the
> other developers in time. Therefor, I would e.g. like to send a mail
> like this to d-d-a:
I think it's a good idea in principle to check which stuff should be
removed.
>
es keep on being
> unfit for release, these packages will be removed after release.
>
> Of course, investing the time for reviewing before orphaning / removal
> should be done about release of sarge.
ok, I just misunderstood you.
Gruesse,
--
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/
ies for removal
/ orphaning.
OK, that sounds reasonable.
Mike Stone
elow: Of course, if the maintainer
considers his own package unfit for release because upstream is not
stable enough, than this is ok. But - if the package was removed from
testing because of FTBFS, and just didn't manage to re-enter, because
this bug is still open, than the packa
On Fri, Jun 18, 2004 at 08:27:14PM +0200, Andreas Barth wrote:
Well, I'm not speaking of investing any time now on them, but just to
alert their maintainers and users that if the packages keep on being
unfit for release, these packages will be removed after release.
Why? I'd actually like to se
to
alert their maintainers and users that if the packages keep on being
unfit for release, these packages will be removed after release.
Of course, investing the time for reviewing before orphaning / removal
should be done about release of sarge.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
On Fri, Jun 18, 2004 at 06:38:58PM +0200, Andreas Barth wrote:
> I'd consider it a good idea if we try to get rid of some of the
> packages that are in unstable, but not in the release of sarge
> ("release" as in: stable -> sarge). I'm prepared to do the work for
> it, but would like to pre-warn th
Hi,
I'd consider it a good idea if we try to get rid of some of the
packages that are in unstable, but not in the release of sarge
("release" as in: stable -> sarge). I'm prepared to do the work for
it, but would like to pre-warn the other developers in time. Therefor,
I would e.g. like to send a
r" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Saturday, June 05, 2004 4:25 AM
Subject: Re: Orphaning packages maintained by Scott K. Ellis ([EMAIL PROTECTED])
> On 2004-06-04 Martin Michlmayr <[EMAIL PROTECTED]> wrote:
> > * Andreas Metzler <[EMAIL PROTECTED
On 2004-06-04 Martin Michlmayr <[EMAIL PROTECTED]> wrote:
> * Andreas Metzler <[EMAIL PROTECTED]> [2004-06-03 12:14]:
> > Scott seems to be MIA for quite some time, all his packages
> > (liblogfile-rotate-perl, tree, xpp) have seen multiiple NMUs and
> > However, the packages have not been actuall
* Andreas Metzler <[EMAIL PROTECTED]> [2004-06-03 12:14]:
> Scott seems to be MIA for quite some time, all his packages
> (liblogfile-rotate-perl, tree, xpp) have seen multiiple NMUs and
> However, the packages have not been actually orphaned. Shall I do the
> honors?
See the end of #215551. I d
Hello,
Scott seems to be MIA for quite some time, all his packages
(liblogfile-rotate-perl, tree, xpp) have seen multiiple NMUs and
[EMAIL PROTECTED]:~$ /org/qa.debian.org/mia/mia-history scott
[...]
2003-10-13: Orphaning: liblogfile-rotate-perl
2003-10-13: Orphaning: tree
2003-10-13
Hello,
I sent Jérôme a message asking whether he'd be willing to sponsor
gwenview. In a burst of enthusiasm, he uploaded the (recompiled for
powerpc) package immediately. :)
The maintainer field was set for myself in that upload, so I guess I'm the
maintainer now. I hope that's not a problem.
Hello,
I have a new gwenview package essentially ready. I will contact my current
sponsor, Jérôme Marant, today, and see if he would be willing to sponsor
Gwenview as well. I'll post here once I have his reply.
Cheers,
Christopher Martin
On May 11, 2004 13:20, Martin Michlmayr wrote:
> * Micha
* Michael Spanier <[EMAIL PROTECTED]> [2004-05-11 18:54]:
> I'm the maintainer of gwenview, a kde image viewer.
> As i do not have that much free time to maintain the package, I hereby
> orphan this this package.
>
> Christopher Martin ([EMAIL PROTECTED]) has showed some
> interested in taking t
Hi,
I'm the maintainer of gwenview, a kde image viewer.
As i do not have that much free time to maintain the package, I hereby
orphan this this package.
Christopher Martin ([EMAIL PROTECTED]) has showed some
interested in taking the package over.
gwenview was a sponored upload by colin wats
* Frank Lichtenheld <[EMAIL PROTECTED]> [2004-04-17 13:32]:
> atmelwlandriver, drsync, gloo, gtk-menu, matchbox,
> mmenu, motion, xkbd, xstroke, maintainer Paul Hedderly <[EMAIL PROTECTED]>
> According to the mia db migus contacted him in February. Was there
> any response? I see occasional activi
* Frank Lichtenheld <[EMAIL PROTECTED]> [2004-04-17 13:32]:
> vipec, maintainer Chris Ruffin <[EMAIL PROTECTED]>
> tbm threated to orphan it already, last in his mail three weeks ago.
> Should we proceed?
Well, the told me in private mail that he was really going to do it.
Perhaps someone could he
vipec, maintainer Chris Ruffin <[EMAIL PROTECTED]>
tbm threated to orphan it already, last in his mail three weeks ago.
Should we proceed?
atmelwlandriver, drsync, gloo, gtk-menu, matchbox,
mmenu, motion, xkbd, xstroke, maintainer Paul Hedderly <[EMAIL PROTECTED]>
According to the mia db migus co
(0.9n-1)
>>>> Latest maintainer contribution to the currently open (15+7) bugs:
>>>> But he only seems to maintain gtk-gnutella. The others share ancient
>>>> standard versions and bugs that are not commented on at all.
>>> Well, I'm all for orpha
pen (15+7) bugs:
> >>
> >> But he only seems to maintain gtk-gnutella. The others share ancient
> >> standard versions and bugs that are not commented on at all.
>
> > Well, I'm all for orphaning it.
> [...]
> Ok. How does this continue, what is pro
a. The others share ancient
>> standard versions and bugs that are not commented on at all.
> Well, I'm all for orphaning it.
[...]
Ok. How does this continue, what is proper procedure?
cu andreas
t commented on at all.
Well, I'm all for orphaning it. I've been trying to chase Matthias
for several months, but since he was uploading at least some packages
I never orpaned any packages. At the same time, he never responded to
any of my mails... I don't know why people do that.
--
Martin Michlmayr
[EMAIL PROTECTED]
Hello,
I started checking gtklp:
Last upload: 2003-06-20 (0.9n-1)
Latest maintainer contribution to the currently open (15+7) bugs:
2002-11-21 (#170025).
This looked fishy, so I checked qa.d.o.
Mathias is listed as maintainer of 7 packages:
cd-circleprint
gtk-gnutella
gtklp
newsflas
On 2004-03-23 Andreas Barth <[EMAIL PROTECTED]> wrote:
[lightning]
> Technical speaking you make a QA upload, because as soon as you set
> the maintainer field to QA, bugs will be closed.
> So, I'd say: make a maintainer-upload, and do a -v1.1-2, so that the
> NMUed bug is also closed.
[o] Done.
1 - 100 of 135 matches
Mail list logo
