On Thu, May 10, 2018 at 11:24:35AM +0200, Laurent Bigonville wrote:
Debian seems to contains to version of rng-tool packaged in two
different src package (rng-tool, last upload in 2011 and rng-tool5,
last upload yesterday).
This might be confusing for our users.
Shouldn't rng-tools package be
On Wed, Jun 27, 2007 at 11:38:19AM +0200, Thijs Kinkhorst wrote:
On Tuesday 26 June 2007 01:07, Jérémy Bobbio wrote:
* Have a new release policy of not releasing orphaned packages in
stable. Interested maintainers would then have to adopt them or
let them be removed by the Q&A team.
I
On Mon, Nov 27, 2006 at 05:33:25PM +0100, Michelle Konzack wrote:
And HOW can I get UID's >=65536 to work?
I have already tried it in my /etc/passwd and
/etc/group but it gives tonns of errors.
Any hints?
Hint: you need to be more specific about the problems you're having.
Mike Stone
--
T
On Fri, Jun 16, 2006 at 10:01:37AM -0700, Thomas Bushnell BSG wrote:
Whose archives? Ours?
Yes. Perhaps you're aware of archive.debian.org, which has releases back
to bo?
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROT
On Wed, Jun 14, 2006 at 05:18:13PM -0700, Thomas Bushnell BSG wrote:
Yes. Deleting information is a big step.
Luckily we aren't doing that, since the information itself is still
available in archives.
I was myself bit by this, when the gnome maintainers decided that
gnome-1 was obsolete, a
On Mon, Jun 12, 2006 at 10:03:42PM -0700, Thomas Bushnell BSG wrote:
Michael Stone <[EMAIL PROTECTED]> writes:
On Mon, Jun 12, 2006 at 10:55:32AM -0700, Thomas Bushnell BSG wrote:
But a bulk "anything that is orphaned and has a low popcon number must
be useless" is incorrec
On Mon, Jun 12, 2006 at 10:55:32AM -0700, Thomas Bushnell BSG wrote:
But a bulk "anything that is orphaned and has a low popcon number must
be useless" is incorrect.
You've made this assertion several times, it's still unsubstantiated.
The process of identifying potentially problematic package
On Mon, Jun 12, 2006 at 09:51:28AM +0200, Thomas Viehmann wrote:
Basically, this amounts to perpetually keeping obsolete packages. Is a
good choice?
Well, at least you've learned why debian has so much obsolete junk--the
"every package is sacred crowd" comes along every time this topic comes
On Fri, Sep 16, 2005 at 08:17:16AM -0400, Robert Main wrote:
I am receiving spam from you and your lists, I want this stopped, NOW
You're kidding, RIGHT?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Jul 20, 2005 at 04:14:38PM +0200, Raphael Hertzog wrote:
It's possible that we over-estimate the "pros" but doing this can't harm
us, so there's no reason for you to stop us.
Who's stopping you? I'm not allowed to have the opinion that it's an
oversold idea? I already said that if you t
On Wed, Jul 20, 2005 at 01:49:15PM +0200, Benjamin BAYART wrote:
Recently (a few months ago) the debian-qa team did an update of dvidvi,
applying the patches that were in the BTS. Before that, bugs have been
in open state, some with patches attached, for more than 5 years.
But they're applied n
On Wed, Jul 20, 2005 at 12:43:55PM +0200, Santiago Vila wrote:
No, just because there is an Ubuntu patch does not mean the patch
should be in the BTS
That's obvious. What is desired is that if there is a useful patch that
someone submit it to the BTS (perhaps with a wishlist tag) rather than
g
On Tue, Jul 19, 2005 at 01:52:07PM +0200, Benjamin BAYART wrote:
No. They would submit patches, or via the bug tracking system, or via an
rcs. The main difference is the result produced:
- with the bug tracking system, you have a patch which sleeps there for
years, waiting for someone to care
On Tue, Jul 19, 2005 at 09:14:19AM +0200, Alexis Sukrieh wrote:
This proposal aims to fill the blank in such situations.
What blank? I checked--there are *no* patches in the BTS for dvidvi.
Maybe if there were some patches out there and the argument was about
making the process easier or somesu
On Tue, Jul 19, 2005 at 10:34:05AM +0200, Benjamin BAYART wrote:
If a package is orphaned in Debian, but still have users and people
willing to maintain the software, this proposition can help.
I'm still just not getting it. So you've got an external developer
community that will be active in
On Mon, Jul 18, 2005 at 05:44:09PM +0200, Raphaël Hertzog wrote:
to improve integration of Ubuntu patches into Debian we need to make
maintainers aware of their existence. So they need to be mentionned in
the PTS.
Why wouldn't there just be a bug filed pointing to the patch?
Mike Stone
--
To
On Mon, Jul 18, 2005 at 06:13:53PM +0200, Alexis Sukrieh wrote:
IMHO, when we drop packages from our archive just because they are
orphaned (I have the jpeg2ps example in mind) we definitely loose a
point (just think to the end-user point of view).
IMO, we lose far more points when people insta
On Fri, Jul 15, 2005 at 05:00:21PM +0200, Benjamin BAYART wrote:
When you say that, or you're wrong, or "nobody" is to be understood as
"nobody in the Debian developpers" in which case you're right. But the
fact that a package is of no interest to a Debian developper does not
prove the package to
I don't get it. If a maintainer still needs to review the patch and
upload it, how is this different than the current situation?
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Jul 14, 2005 at 07:46:36PM +0200, Raphael Hertzog wrote:
The whole discussion is about defining what is reasonable, what are the
limits and how can it be made working.
No, you're looking to set up a special infrastructure to support some
wacky corner cases. Why don't you just accept the
On Wed, Jul 13, 2005 at 07:27:58PM +0200, Benjamin Bayart wrote:
If you think it is satisfactory, then, well, perhaps there is nothing to
change and I'm wrong on that. But if you think it have to be improved,
my proposition is just to accept more-or-less automaticaly the
contributions from the ou
On Mon, Nov 15, 2004 at 09:06:22PM +0100, Thomas Schorpp wrote:
yes, i've mailed to this list to find out whats missing, beating me up
for it wont surely help ;)
You're not being beaten up. If you were looking for a different reaction
you should try another forum. This list is basically focused
On Fri, Nov 12, 2004 at 02:11:46PM +1100, Anibal Monsalve Salazar wrote:
The changelog is misleading.
Please see above.
You explained why you did what you did, but that doesn't change the fact
that it's misleading. Perhaps you could consider a different method?
Mike Stone
On Thu, Nov 04, 2004 at 09:46:38PM +0100, Andreas Tille wrote:
Please explain your understanding of the relation of the words
a) help - as I wroteand
b) insult - as you interpreted my mail
Have you checked the thread title lately?
Mike Stone
On Tue, Jun 22, 2004 at 04:04:37PM +0200, Helmut Wollmersdorfer wrote:
Sorry, I thought, that stable is important.
What does that have to do with anything?
Mike Stone
On Fri, Jun 18, 2004 at 11:57:24PM +0200, Andreas Barth wrote:
1. I really hope that we are able to release more often in future.
Releasing only every four years is a dead end.
People have been saying that since I joined the project, if not earlier. :)
2. Please see "exception" below: Of cour
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
On Wed, May 05, 2004 at 01:25:10AM +0200, Bluefuture wrote:
In all this cases, is it so hard for Mantainers to fill watch file in
their own packages for Qa pourposes?
We've had this argument before and the problem remains that many
devlopers don't see a point to putting one in. It's not that it
On Wed, Mar 10, 2004 at 12:23:23PM +0100, Thomas Hood wrote:
Upgrades are handled properly if and only if rc symlink farms are
fully populated.
No, they *aren't* handled properly, since they can't cope with manually
started services. It's broken either way. And if you think about it,
we already
On Tue, Mar 09, 2004 at 11:25:03PM +0100, Thomas Hood wrote:
The first problem (as has already been mentioned) is that in the absence
of symlinks the service will be started on upgrade even if it wasn't
running before the upgrade.
Well, there are long-standing bugs in debian's handling of servi
On Tue, Mar 09, 2004 at 09:40:22AM -0300, Henrique de Moraes Holschuh wrote:
rcconf should just be fixed to put kill links. "floating" instead of "off"
is a bad idea to begin with IMHO, unless you have the three states.
You haven't given an actual rationale for that but I'll explain why I
think
On Mon, Mar 08, 2004 at 09:28:05AM +0100, Thomas Hood wrote:
The configuration is not interpreted to mean "no-op". As I said
before,
you said it, but it's wrong.
There is evidently a lot of confusion surrounding this issue.
Something should be added to the Debian Reference about it.
Luckil
On Sun, Mar 07, 2004 at 10:14:11PM +0100, Thomas Hood wrote:
Argh! You're not supposed to delete _any_ links -- just rename
them from Sn to K(100-n) and back.
No, deleting them would be fine.
If there is neither an S nor a K symlink for a service in a
runlevel it does not mean that the serv
On Sun, Mar 07, 2004 at 03:05:42PM -0500, Joe Nahmias wrote:
No, you're only supposed to delete the start links (S??service), not all
the links.
Ah, yes. Deleting *all* the links would be a pretty severe bug.
Mike Stone
On Sun, Mar 07, 2004 at 06:46:55PM +0100, Thomas Hood wrote:
has let it be known that there will be a new release RSN. The
big issue (deleting symlinks to disable a service) apparently
will remain unfixed in this release but I'll take that up with
Why is that a problem? It's how you're *suppos
On Sat, Mar 06, 2004 at 02:50:15PM -0500, R. Wood wrote:
On Sat, Mar 06, 2004 at 09:31:59AM +0100, Thomas Hood imagined:
Rcconf checks 'defaults' links in /etc/rc?.d/ directories
for choice as unset, whether the package has the start
file with the same number in /etc/rc?.d/(?:=2345)
On Mon, Feb 09, 2004 at 08:37:30AM -0800, you wrote:
The description lies; kernel-patch-evms was updated for 2.6.0 some time ago.
Of course, 2.6.0 has known security problems, and 2.6.1 isn't in Debian yet.
Which is fine, since 2.6.2 is out :)
Mike Stone
On Fri, Jan 16, 2004 at 03:31:14PM +0100, you wrote:
would you like wishlist bugs more if every bug had a working watch file
attached?
No, what would make you think that would be a good idea?
Mike Stone
On Fri, Jan 16, 2004 at 10:30:22AM +0100, you wrote:
and it takes a maximum of two minutes per package to create a watch
file, so why not?
Because I don't see a point. Because I've seen a lot of clever little
ideas for things to add to packages come and go. If a developer decides
he wants this,
On Thu, Jan 15, 2004 at 04:30:38PM +0100, you wrote:
automated way to check for new releases so thes know that the package is
up to date. apart from that it makes a good indication of an inactive
maintainer.
It shows no such thing. It indicates that the maintainer doesn't want to
package the ne
On Wed, Jan 14, 2004 at 05:15:14PM +0100, Filippo Giunchedi wrote:
up-to-dated. OTOH having the PTS stating "new upstream version available blah
blah" can reduce BRs like "hey, a new release is out! could you please update
this package?"
I seriously doubt that. I see zero value in having a wat
On Mon, Oct 13, 2003 at 10:19:13PM -0700, Marc Singer wrote:
I found this recipe. Yet, I feel like I'm missing something. How can
I perform dselect on a machine where I am not root?
If you're not root than chroot isn't what you're looking for. Take a
look at UML (user mode linux) instead.
Mi
I propose that we remove this package. There's no source code, upstream
has disappeared, and ethereal is a free package that provides pretty
much the same functionality but better (or at least that's my
impression). Any comments?
kill it.
Mike Stone
Please don't crosspost to so many lists. Follow-ups set to the bug
report. You should most definately have more than the ramdisk driver in
/proc/devices. I also run devfs & lvm and have this in /proc/devices:
Block devices:
1 ramdisk
3 ide0
7 loop
8 sd
9 md
11 sr
22 ide1
58 lvm
65 sd
On Mon, Apr 08, 2002 at 01:08:10AM +0100, Mark Brown wrote:
> I have this sneaking suspicion that we need a tool more appropriate than
> the BTS to handle the WNPP. The BTS seems rather fragile for this
> purpose - the format for bug titles and to a greater extent the way
> followups for bug repor
On Tue, Jul 24, 2001 at 12:59:57PM +0200, Raphael Hertzog wrote:
> Le Tue, Jul 24, 2001 at 06:24:07AM -0400, Michael Stone écrivait:
> > On Tue, Jul 24, 2001 at 05:00:36AM -0400, Nathanael Nerode wrote:
> > > Who has the authority to remove a package in this state, and fore
On Tue, Jul 24, 2001 at 05:00:36AM -0400, Nathanael Nerode wrote:
> Who has the authority to remove a package in this state, and forestall
> angry complaints should the maintainer come back some years in the
> future? Well, the QA committee clearly does.
Not really. The QA committee was never g
On Sun, Jul 22, 2001 at 01:21:55PM -0400, Adam Di Carlo wrote:
> If these can't get fixed, we may need to eliminate dhcp-client and
> move back to pump, which I wouldn't be all that happy about.
I've always had much better luck with pump than the alternatives. There
isn't a perfect solution.
--
Package: lockvc
Version: 3.9-1
Severity: grave
The default for lockvc seems to have changed, so that it now logs the
user out after 15 mins. It does that by killing *all* of the user's
processes. If no one else jumps in, I'll NMU in the next few days.
--
Mike Stone
On Sat, Dec 09, 2000 at 10:13:53AM +0100, Christian Kurz wrote:
> On 00-12-09 Gordon Sadler wrote:
> > Pardon my ignorance, but the libpam-pwdb that this bug refers to not
> > being available seems to be in an odd position. It IS available,
> > however only on auric, testing. I track quite a few mi
On Fri, Mar 31, 2000 at 08:25:32AM -0500, Michael Alan Dorman wrote:
> Raphael Hertzog <[EMAIL PROTECTED]> writes:
> > could someone with a good knowledge of perl have a look at this
> > problem ?
>
> Well, I would, if there appeared to be a problem.
>
> I get success. I would suggest this is ei
On Wed, Jan 12, 2000 at 10:27:44PM +, Julian Gilbey wrote:
> What?! Two *different* wnpp pages? Is there any chance of merging
> them?
I lost the response I got on the last one. I think the answer was that
someone just needs to port the stuff on the old page to the new page.
(Someone correct
On Wed, Jan 12, 2000 at 02:59:08PM -0800, Sean 'Shaleh' Perry wrote:
> you can do a few things:
>
> scour freshmeat or the net for something not in Debian
> find something in Debian that has not been updated lately and update it
> read the BTS, fix a bug or three on something you use or know about
On Wed, Jan 12, 2000 at 08:26:01PM +, Julian Gilbey wrote:
> On Wed, Jan 12, 2000 at 04:31:50PM +0100, Thierry Laronde wrote:
> > I'm not a developer yet, but I'm looking for a package to adopt in order to
> > learn, with an actual example, how the work has to be done.
>
> Have a look at the w
On Mon, Dec 13, 1999 at 11:16:22PM +0100, Josip Rodin wrote:
> On Mon, Dec 13, 1999 at 09:59:23PM +, M.C. Vernon wrote:
> > I think it should say "Debian Quality Assurance" instead of "the
> > Debian Quality Assurance".
>
> That is gramatically correct or just better style?
I think the origin
The wnpp lists hwtools as orphaned by debian-qa. But the BTS lists it
under Siggy Brentrup <[EMAIL PROTECTED]>. I can't find any reference to
that name in the changelog for hwtools--so what's the deal?
Mike Stone
On Sun, Oct 10, 1999 at 04:50:22PM +1000, Herbert Xu wrote:
> Because I'm yet to reach bootparamd while splitting netstd. It will
> be fixed when it leaves netstd.
Why can't the included patch be included before then? Are you willing to
accept an NMU?
Mike Stone
pgpOKWWvFtdDO.pgp
Description:
Why doesn't the wnpp list at http://qa.debian.org/wnpp.html match the
one at http://www.debian.org/doc/prospective-packages.html? Why not just
link to the latter list rather than generating a new one?
Mike Stone
For the long term, it might be nice to divide tasks by difficulty. E.g.,
there could be a section for bugs that are fixed by a provided patch or
simple dependency rules, and another section for difficult debugging
work. (The intent of this being to make it easier for a beginner to sit
down and knoc
On Sat, Sep 18, 1999 at 12:15:14PM +0200, Raphael Hertzog wrote:
> Le Sat, Sep 18, 1999 at 01:25:06AM -0400, Johnie Ingram écrivait:
> > * Suggested motto: "all free, all good"
>
> :) It's not really QA related.
Sure it is. QA is trying to make free software good. Despite ESR's
boosting, that's n
On Sat, Aug 28, 1999 at 02:10:01PM +1000, Anthony Towns wrote:
> Note that the first maintainer script after "remove /bin/sh" is the
> postinst -- adding the link in the preinst doesn't do us any good on
> upgrades.
Ok. I stand corrected. How's this for a nasty hack: what if the preinst
diverts /b
On Fri, Aug 27, 1999 at 11:28:30PM +0200, Raphael Hertzog wrote:
> Which is also not so logical since in the preinst bash is not yet unpacked
> and there may be no /bin/bash ... it may be installed in the
> preinst when the package is upgraded ($1 = upgrade) only (in which
> case the link should al
On Sat, Aug 28, 1999 at 05:13:55AM +1000, Anthony Towns wrote:
> * postinst is a /bin/bash script instead of a /bin/sh script -- this
>means it won't fail if for some reason there isn't a /bin/sh symlink
>already. If there isn't a symlink (or or an actual file) it makes
>
On Thu, May 06, 1999 at 06:43:52PM +0200, Josip Rodin wrote:
> The M4 is almost ready. Please wait a few more days (when you've waited
> this long, it'll be nothing ;).
How 'bout M5? ;)
Mike Stone
[snipping a lot about wm selection]
Is it possible that this is being overanalyzed? What if we just choose a
default by fiat (falling back to whatever happens to be installed, in no
particular order) and print a message about how to change it? Then
recommend gdm or wdm or some other display manage
All right, here's the revised list (removing anything that someone confirmed
as almost done.)
Quoting Michael Stone ([EMAIL PROTECTED]):
> > apache32204 user directories allow symlinks to other files [0]
> > (Johnie Ingram <[EMAIL PROTECTED]>)
>
> T
Well, let's see what's holding up slink. :)
> apache32204 user directories allow symlinks to other files [0]
> (Johnie Ingram <[EMAIL PROTECTED]>)
There's a suggested fix in the bug report. Is it problematic?
> autoconf 32391 Autoconf patches for slink [0] (Ben Pfaff <[
67 matches
Mail list logo
