On Mon, Oct 10, 2005 at 01:47:52PM -0500, Jason Clinton [EMAIL PROTECTED] was
heard to say:
On Monday 10 October 2005 01:37 pm, Alejandro Bonilla wrote:
Hi,
In Sid, apt-get wants to remove hotplug.
Is udev replacing it for good or this is just b0rken?
.Alejandro
Don't do it. See
On Mon, Oct 10, 2005 at 02:37:53PM -0400, Alejandro Bonilla wrote:
Hi,
In Sid, apt-get wants to remove hotplug.
Is udev replacing it for good or this is just b0rken?
From udev's changelog (available online at
http://packages.debian.org/unstable/admin/udev):
* Added support for coldplug
On Monday 10 October 2005 01:54 pm, Daniel Burrows wrote:
Hm, doesn't just manually loading mousedev (and putting it in
/etc/modules) get things working again?
That's not the only problem:
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332905
[2]
On Mon, Oct 10, 2005 at 11:54:11AM -0700, Daniel Burrows wrote:
Hm, doesn't just manually loading mousedev (and putting it in
/etc/modules) get things working again?
Mousedev, evdev and usbmouse here, to have a working setup for X with
a synaptics touchpad and an usb mouse.
--
Francesco
On Mon, 10 Oct 2005 13:47:52 -0500, Jason Clinton wrote
On Monday 10 October 2005 01:37 pm, Alejandro Bonilla wrote:
Hi,
In Sid, apt-get wants to remove hotplug.
Is udev replacing it for good or this is just b0rken?
.Alejandro
Don't do it. See the previous thread titled 'udev
On Monday 10 October 2005 02:27 pm, you wrote:
Also, did anyone try a ipw2100 or ipw2200 with this? Will
/etc/hotplug/firmware agent still work by loading the firmwares with no
additional action from the driver code?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332946
--
I use digital
On Oct 10, Jason Clinton [EMAIL PROTECTED] wrote:
On Monday 10 October 2005 02:27 pm, you wrote:
Also, did anyone try a ipw2100 or ipw2200 with this? Will
/etc/hotplug/firmware agent still work by loading the firmwares with no
additional action from the driver code?
On Monday 10 October 2005 01:54 pm, Daniel Burrows wrote:
Hm, doesn't just manually loading mousedev (and putting it in
/etc/modules) get things working again?
Also note that libgphoto2-2 (upon which much of the desktop metapackages
depend) will conflict with the new udev-0.070-3 until a NMU
On Oct 10, Francesco Paolo Lovergine [EMAIL PROTECTED] wrote:
Mousedev, evdev and usbmouse here, to have a working setup for X with
usbmouse is blacklisted, so it's not supposed to be loaded.
The driver for USB mice is usbhid.
--
ciao,
Marco
signature.asc
Description: Digital signature
A simpler solution could be merging 3) and 5) in a single upload. Then
the Depends in 1) would not be needed.
Yeah, that's one way to ensure the uploads are coordinated. :)
BUT one should have the dependencies (and eventually build dependencies) in
there ANYWAY.
People often do partial
mentioned passwd being Essential because it depends on
passwd. This is actually right. However this dependency is just the
consequence of bash needing the add-shell and remove-shell
utilities...so, in the future, bash shouldn't depend on passwd
anymore.
Other contributors, please continue commenting
[Christian Perrier]
Peter Samuelson mentioned passwd being Essential because it depends
on passwd. This is actually right. However this dependency is just
the consequence of bash needing the add-shell and remove-shell
utilities...so, in the future, bash shouldn't depend on passwd
anymore
The bugs #208514, #268656, #269573, #29317 all finally suggest moving
add-shell and remove-shell out of the passwd package.
These utilities are use to register shells in /etc/shells and they
obviously do no belong to the passwd package.
Having them in passwd enforces shells to depend on it just
[Christian Perrier]
The goal is having a system which always has the two utilities...and
of course avoid the removal of passwd (debianutils is Essential while
passwd isn't).
passwd effectively is Essential because bash depends on it. So I'm
pretty sure you don't have to worry about it being
On Sat, Oct 01, 2005 at 03:05:30PM +0200, Christian Perrier wrote:
The plan we draw is the following:
1) shadow package maintainers upload passwd which
Depends: debianutils (= 2.14.3)
this version *still* includes the utilities
The purpose of 1) is to avoid the removal of passwd
On Sunday 02 October 2005 00:09, Peter Samuelson wrote:
Just coordinate two uploads to happen in the same dinstall cycle:
shadow 1:4.0.12-6 where passwd Depends: debianutils (= 2.15)
debianutils 2.15 Conflicts and Replaces: passwd ( 1:4.0.12-6)
Hmm. That will cover i386 I guess. What
[Frans Pop]
shadow 1:4.0.12-6 where passwd Depends: debianutils (= 2.15)
debianutils 2.15 Conflicts and Replaces: passwd ( 1:4.0.12-6)
Hmm. That will cover i386 I guess. What about other arches that are
autobuilt? (Assuming of course that both maintainers upload for i386.)
Good
[EMAIL PROTECTED] (Bob Proulx) writes:
Should I send you a photocopy of the original cdroms that I used to
install on my system?
Actually, that can be useful, if only to verify just what version was
installed :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Just fix the program that generates our HTML mailing list archives, and
make it output meta name=robots content=noindex for mails which
contain any of the Forbidden Words!
Richard
--
__ _
|_) /| Richard Atterer | GnuPG key:
| \/¯| http://atterer.net | 0x888354F7
¯ '` ¯
On Sep 05, 2005 at 18:33, John Hasler praised the llamas by saying:
David Pashley writes:
No, because that doesn't help the next person that searches on Google.
If these people read the messages they find with their searches they
wouldn't post here. They don't. They just grab the address
On Tue, Sep 06, 2005 at 04:44:41PM +0100, David Pashley wrote:
[...]
Even still, it's worth trying to get
http://lists.debian.org/debian-devel/2005/01/msg01444.html bumped
up to the top of the google search all the same.
[...]
Perhaps I'm missing something, but it seems to me that it would be
David Pashley wrote:
John Hasler praised the llamas by saying:
And helping people get off C4LL W4VE is not our job.
Surely we should do our best to help all computer users, not just Debian
users. :)
It is not practical nor even possible to do so. The noise is
overwhelming!
I have a
David Pashley writes:
I'd hope that people actually clicked on the page in question rather
than just seeing the email address in the summary on the google search.
We don't hear from those ones.
But yes, I agree that some users are occasionally stupid or lazy or both.
Those we do hear from.
The Fungi writes:
Perhaps I'm missing something, but it seems to me that it would be more
effective to try to get http://www.callwave.com/members/cancel/ bumped up
to the top of the google search instead.
Now that sounds sensible.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL
I notified you, electronically a month or more ago to cancel my subscription to CALL WAVE.
This billing has continued on my VISA bill for two or more months.
Will you acknowledge receipt of this current message? I would like a credit memo for the last month or two, but I know this action will
On Monday 05 September 2005 16:34, [EMAIL PROTECTED] wrote:
I notified you, electronically a month or more ago to cancel my
subscription to CALL WAVE.
This billing has continued on my VISA bill for two or more months.
Will you acknowledge receipt of this current message? I would like a
This list is for developers of Debian GNU/Linux (http://www.debian.org)
and are not related to Callwave in any way.
Please view http://lists.debian.org/debian-devel/2005/01/msg01444.html
for information on how to remove yourself from Callwave.
--
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua
Please do not follow up to these messages. These idiots apparently Google
the phrase and then spam all the addresses they find. Posting about the
subject here just creates more hits.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
up to these emails providing
useful information how to remove themselves and in particular link to
the rather informative email from Josh Metzler[0] so that they might
find out how to do it themselves rather than emailing the list.
On a side note, I believe that if you are going to follow up, you
David Pashley writes:
I believe it is far more useful to follow up to these emails providing
useful information how to remove themselves and in particular link to the
rather informative email from Josh Metzler[0] so that they might find out
how to do it themselves rather than emailing the list
On Sep 05, 2005 at 17:13, John Hasler praised the llamas by saying:
David Pashley writes:
I believe it is far more useful to follow up to these emails providing
useful information how to remove themselves and in particular link to the
rather informative email from Josh Metzler[0] so
David Pashley wrote:
Don't follow up. Reply to them privately.
No, because that doesn't help the next person that searches on Google.
That is exactly the point. We DO NOT WANT people to find the Debian
mailing lists in any relation to that search. Every time someone
references it in a
On Sep 05, 2005 at 18:14, Bob Proulx praised the llamas by saying:
David Pashley wrote:
Don't follow up. Reply to them privately.
No, because that doesn't help the next person that searches on Google.
That is exactly the point. We DO NOT WANT people to find the Debian
mailing lists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Proulx wrote:
David Pashley wrote:
Don't follow up. Reply to them privately.
No, because that doesn't help the next person that searches on
Google.
That is exactly the point. We DO NOT WANT people to find the
Debian mailing lists in any
David Pashley writes:
No, because that doesn't help the next person that searches on Google.
If these people read the messages they find with their searches they
wouldn't post here. They don't. They just grab the address and spam us.
And helping people get off C4LL W4VE is not our job.
I
Benjamin Seidenberg wrote:
I wonder if it would be possible to appeal to google to have them
manually edit that search so that l.d.o doesn't appear. (Same for
[replaced with string instrument to avoid another google hit]'s)
What I think I would rather see is targeted moderation of anything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 1 Sep 2005 18:04:35 -0500
Source: libfile-remove-perl
Binary: libfile-remove-perl
Architecture: source all
Version: 0.30-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Gunnar
://contribs.martymac.com/
* License : GPL
Description : Add and remove user and groups stored (using ldap)
Ldapscripts are shell scripts that allow to manage POSIX accounts
(users, groups, machines) on an LDAP directory. They are similar to
smbldap-tools but are written
Quoting Roberto C. Sanchez [EMAIL PROTECTED]:
Because the user is (99% chance) an admin.
We should use debtags for this kind of information, IMHO.
Because the user may not want extraneous or extra Perl modules
installed on his system. If you are building a production box, you may
want to
Author : Ganaël LAPLANCHE [EMAIL PROTECTED]
* URL : http://contribs.martymac.com/
* License : GPL
Description : Add and remove user and groups stored (using ldap)
Ldapscripts are shell scripts that allow to manage POSIX accounts
(users, groups, machines
Package: wnpp
Severity: wishlist
Owner: Pierre Habouzit [EMAIL PROTECTED]
* Package name: ldapscripts
Version : 1.2
Upstream Author : Ganaël LAPLANCHE [EMAIL PROTECTED]
* URL : http://contribs.martymac.com/
* License : GPL
Description : Add and remove
owner 324296 [EMAIL PROTECTED]
submitter 324296 [EMAIL PROTECTED]
thanks
damned, why don't reportbug honour DEBEMAIL ?
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
Package: reportbug
Version: 3.15
Severity: important
Le Dim 21 Août 2005 17:02, Benjamin Seidenberg a écrit :
Pierre Habouzit wrote:
owner 324296 [EMAIL PROTECTED] submitter 324296
[EMAIL PROTECTED] thanks
damned, why don't reportbug honour DEBEMAIL ?
Had same issue, check your
Please remove me from "Call Wave" Ihave signed up for local Comcast
broadband, and no longer need this service.
Thank you,
On Sun, Aug 14, 2005 at 05:35:35AM -0700, Steve Langasek wrote:
libyaml-ruby (*)
Needed by dnsdoctor, zonecheck, and sisu.
libyaml-ruby binary package is a dependency package built from
ruby-defaults source package and depends on libyaml-ruby1.8 (default
Ruby version); libyaml-ruby1.6 binary
On Fri, Aug 12, 2005 at 06:29:58PM +0900, wrote:
Hi,
I think that ruby1.6 should be removed from Debian.
Because Ruby 1.6.x is the old stable version of Ruby.
(current stable version is Ruby 1.8.x.)
I had authored some very simple ruby scripts on a stable machine in 1.6
which are now
ok now how can i get my password from a for callwave, ihave it all install
please as soon as possible.
Hi Akira,
On Fri, Aug 12, 2005 at 10:24:05PM +0900, akira yamada / やまだあきら wrote:
Nico Golde wrote:
Do you have an idea how many of them are packaged with
1.8 too?
The following source packages generate binary packages
for ruby1.6 only:
Thanks for this list. It appears that the following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
On Sun, Aug 14, 2005 at 05:35:35AM -0700, Steve Langasek wrote:
I don't know about aswiki, rsjog, tdiary (tdiary-plugin)
and tictactoe. (I use tDiary on ruby1.8 and I have no problem.)
tictactoe (0.8.1-2) has been uploaded yesterday and now
Hi,
* akira yamada / [EMAIL PROTECTED]$-$i [EMAIL PROTECTED] [2005-08-12 11:49]:
I think that ruby1.6 should be removed from Debian.
Because Ruby 1.6.x is the old stable version of Ruby.
(current stable version is Ruby 1.8.x.)
In unstable, the following packages depend on ruby1.6:
I also
.
And I will request to remove ruby1.6 to ftp.debian.org
at the middle of 2005-09.
Thank you.
--
akira yamada
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Nico Golde wrote:
Do you have an idea how many of them are packaged with
1.8 too?
The following source packages generate binary packages
for ruby1.6 only:
aswiki
drb (*)
erb (*)
gnome-ruby
libhonyaku-damashii-ruby
libiconv-ruby (*)
libmutexm-ruby (*)
libnet-acl-ruby (*)
* Ondrej Sury
| I think that this could be delicate issue, because evolution creates DB
| files in .evolution and it has to be migrated automaticaly for an user.
| So bug is OK, but NMU would not be AFAIK welcomed, since it could broke
| user addressbooks, etc.
|
| Takuo, am I right?
FWIW,
FWIW, this is just about the same response I got from upstream when I
asked them about the issue. The solution is of course to get rid of
libdb and use tdb or something equivalent.
Maybe you should convince bogofilter upstream to keep supporting tdb.
They're dropping it on the grounds that
Please remove me from call wave as I no longer need it. Thomas
Matey
* Ondrej Sury:
I think that this could be delicate issue, because evolution creates DB
files in .evolution and it has to be migrated automaticaly for an user.
Which Berkeley DB feature set is needed by evolution?
The database format itself has not changed since 4.0, so no migration
would be
Hi,
I have thousands of emails in separate maildirs. I would like to
remove header lines from all of them that matches a pattern. AFAICR
I have already used something similar a long time ago, but now I
can not dig up anything. Is there any tool that can do this (C/C++
preferred, but Python/Perl
On Sun, Jul 31, 2005 at 10:19:30AM +0200, Laszlo Boszormenyi wrote:
I have thousands of emails in separate maildirs. I would like to
remove header lines from all of them that matches a pattern. AFAICR
I have already used something similar a long time ago, but now I
can not dig up anything
Hi,
libdb4.1 should be removed from Debian soon. The following packages
still use it (but could move forward to the more recent db4.2 or db4.3
package):
arla
kerberos4kth-servers
vacation
libedataserver1.2-4
libroken16-kerberos4kth
kerberos4kth-kdc
libapache-mod-witch
libotp0-kerberos4kth
On Sun, 2005-07-31 at 15:32 +0200, Andreas Barth wrote:
Hi,
libdb4.1 should be removed from Debian soon. The following packages
still use it (but could move forward to the more recent db4.2 or db4.3
package):
libedataserver1.2-4
evolution-exchange
evolution-data-server1.2
evolution
2005-07-31 (日) の 22:34 +0200 に Ondrej Sury さんは書きました:
On Sun, 2005-07-31 at 15:32 +0200, Andreas Barth wrote:
Hi,
libdb4.1 should be removed from Debian soon. The following packages
still use it (but could move forward to the more recent db4.2 or db4.3
package):
libedataserver1.2-4
Lars Wirzenius [EMAIL PROTECTED] writes:
ma, 2005-07-18 kello 18:51 +0200, Goswin von Brederlow kirjoitti:
The problem is fontconfig / libfontconfig1. No one else is to
blame. Cyclic depends will be broken at random places and will cause
problems.
Ah yes, of course, I should have realized
ti, 2005-07-19 kello 22:04 +0200, Goswin von Brederlow kirjoitti:
Actualy I would prefer if you don't. This is a real bug and should be
noticed by piuparts.
Sure. I'm only ignoring the files fontconfig leaves behind now that I
know there is a problem so that I get rather fewer error logs to
Below is a log of a transaction with apt-get and dpkg to first install
fontconfig and libfontconfig1, and then removing them. Installation goes
nicely, but the removal fails, because dpkg removes libfontconfig1 first
and only after it's done that does it remove fontconfig. Unfortunately
it remove fontconfig. Unfortunately,
fontconfig's maintainer script calls fc-cache (via defoma Perl scripts
that I don't really understand), which is linked against libfontconfig1
and therefore fails in the dynamic linker. fontconfig does depend on
libfontconfig1, so I expected dpkg to remove
ma, 2005-07-18 kello 18:51 +0200, Goswin von Brederlow kirjoitti:
The problem is fontconfig / libfontconfig1. No one else is to
blame. Cyclic depends will be broken at random places and will cause
problems.
Ah yes, of course, I should have realized that. Thanks. It's not a dpkg
problem, and I
this program is not right for me and my
family
thank you for your help
has been for
quite some time.
and
I had planned to 'after stable is out'. I'll try to do a maintenance release
of 2.0.17. If that fails, I can still remove it.
Do you think it should be removed now?
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
* Martin Michlmayr [EMAIL PROTECTED] [2005-06-12 21:13]:
Do you think it should be removed now?
http://lists.debian.org/debian-devel/2005/05/msg00089.html lists some
other octave related packages that should probably be removed.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE,
| on octave2.1 instead -- and octave2.1 is where all development has been for
| quite some time.
| and
| I had planned to 'after stable is out'. I'll try to do a maintenance release
| of 2.0.17. If that fails, I can still remove it.
|
| Do you think it should be removed now?
and
On 12 June 2005
I no longer need the service. Please remove
me immediately.
thank you.
Pls remove me from Call Wave
On Thu, Jun 02, 2005 at 08:09:25PM -0500, Heyer Family wrote:
Please remove me from call wave.
Thanks
Please see http://wiki.debian.net/?DuelingBanjoes for instructions.
Regards,
Paddy
--
Perl 6 will give you the big knob. -- Larry Wall
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
On Thu, Jun 02, 2005 at 08:09:25PM -0500, Heyer Family wrote:
Please remove me from call wave.
What part of the email address debian-devel@lists.debian.org looks
like it screams out we are part of Call Wave?
Please get your facts straight next time.
Yours sincerely,
Andrew Lau
Please remove me from call wave.
Thanks
if it was modified when it is removed in a new
package version?
If by held you mean, not removed, yes, that's what happens, _even
if_ the conffile was not modified.
What does dpkg so with such conffiles they are removed
from one to the next package version?
Ignore them, and don't remove them
Hi,
in an old version of jed-common two conffiles 00site.sl and 99debian.sl
were included. But caused by some reason they aren't removed on upgrade.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266981
Becomes a conffile held if it was modified when it is removed in a new
package version?
* [EMAIL PROTECTED] [2005-03-18 21:36]:
* Jeroen van Wolffelaar [EMAIL PROTECTED] [2005-03-18 21:35]:
Yes, please. raidtools2 is already dropped from testing, which makes
I wonder if there's some kind of upgrade path for people using
raidtools2. I phear to imagine what'll happen to my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 30 Mar 2005 12:35:42 -0600
Source: libfile-remove-perl
Binary: libfile-remove-perl
Architecture: source all
Version: 0.29-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Gunnar
[since my comments are post-sarge, I dropped -release]
On Wednesday 06 April 2005 04:33, Adeodato Simó wrote:
Anyway, that would be a solution local to the KDE metapackages (though
I believe other sets of metapackages are doing it like that), but it's
certainly suboptimal.
I've
* Daniel Burrows [Tue, 05 Apr 2005 22:09:49 -0400]:
[Explanation of how aptitude's smart This pacakge was automatically
installed mechanism breaks badly with metapackages, when removing one
of the dependencies triggers the removal of the metapackage, and then
all the other dependencies
. The package list grows at a far greater rate that our
architecture list, and consumes far greater resources than any single
architecture.
Remove one architecture, and you remove an entire userbase. Remove 10% of
our least used packages and I bet you wont lose but a handful of users
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I noticed the pdp1-unix-v{5,6,7} images - how useful are they really?
popcon suggests that only a few people have installed them.
Since Kevin now orphaned them and they are non-free, can we get rid of
Wouter Verhelst [EMAIL PROTECTED] writes:
On Tue, Mar 01, 2005 at 01:28:58AM +0100, Goswin von Brederlow wrote:
It does? How does that work for packages with only a minimal control
file that generate a full contol file during build?
Such packages need to make sure their initial control file
[Goswin von Brederlow]
Which also avoids that packages will be unavailable on every new
architecture debian introduces because the maintainer has to adjust
the Architecture: line.
I suppose it'd be nice to be able to use !foo in the Architecture: line
for cases where something is known not to
check archives),
It has been brought up before a few times on the m68k mailinglists (and
perhaps others too, but I don't follow those). The answer is pretty
complex. In short: don't remove an architecture from your Architecture:
line unless it
* crashes,
* is something that requires so much CPU time
On Mon, Feb 28, 2005 at 04:42:54AM -0600, Peter Samuelson wrote:
[Goswin von Brederlow]
Which also avoids that packages will be unavailable on every new
architecture debian introduces because the maintainer has to adjust
the Architecture: line.
I suppose it'd be nice to be able to use
Peter Samuelson [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Which also avoids that packages will be unavailable on every new
architecture debian introduces because the maintainer has to adjust
the Architecture: line.
I suppose it'd be nice to be able to use !foo in the Architecture:
On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote:
Peter Samuelson [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Which also avoids that packages will be unavailable on every new
architecture debian introduces because the maintainer has to adjust
the Architecture:
Wouter Verhelst [EMAIL PROTECTED] writes:
On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote:
Peter Samuelson [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Which also avoids that packages will be unavailable on every new
architecture debian introduces because the
On Tue, Mar 01, 2005 at 01:28:58AM +0100, Goswin von Brederlow wrote:
Wouter Verhelst [EMAIL PROTECTED] writes:
On Mon, Feb 28, 2005 at 08:18:56PM +0100, Goswin von Brederlow wrote:
Peter Samuelson [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Which also avoids that packages
On 22/02/2005 at 10:11 Wouter Verhelst wrote...
snip
I agree that we should not continue to provide software for outdated
hardware platforms just for the sake of it; but as it is, there are
still people interested in m68k (some hobbyists, some embedded
developers, some who just use their old
Rudy Godoy [EMAIL PROTECTED] writes:
Regarding this issue I was thinking about it since I've faced in a
situation where a package[0] I maintain does have high hardware
requirements, which led me to think if it is really wise to have it
with arch: any since probably in some arches it would not
Thomas Bushnell BSG [EMAIL PROTECTED] writes:
Rudy Godoy [EMAIL PROTECTED] writes:
Regarding this issue I was thinking about it since I've faced in a
situation where a package[0] I maintain does have high hardware
requirements, which led me to think if it is really wise to have it
with
On Mon, Feb 21, 2005 at 08:54:36PM -0800, Thomas Bushnell BSG wrote:
Dirk Eddelbuettel [EMAIL PROTECTED] writes:
I was quoting a post with actual download numbers that actually demonstrate
that the vast majority of users are on i386: see http://blog.bofh.it/id_66.
But that doesn't show
On Tue, Feb 22, 2005 at 03:09:55PM -0500, Joey Hess wrote:
- security response time (more builds to do)
Which DSAs came out later than they should have because of this
supposed delay? Nor could this possibly slow release.
DSAs are occasionally delayed waiting on builds. The priveliged
On Sat, Feb 26, 2005 at 05:27:48PM -0800, Steve Langasek wrote:
and if we relax this to only require within 10 days of any source upload,
assuming the source isn't buggy, there must be a binary upload for this
security bug, we would be kicking out
alpha arm mips mipsel powerpc sparc
I
, remove
the packages and allow nature to take its course? How much time is
left for Sarge anyway? I've already received more bug reports on
these packages than I had anticipated could arrive pre-sarge. I
suppose it is worth fixing them?
Thanks so much for your great work on supporting cernlib
[Dirk Eddelbuettel]
[1] I removed the entry unknown -- this corresponds to assuming that
unknown as population corresponds to the distribution of all known
dists shown here. Lacking knowledge of what drives unknown, this
appears fair. If someone has a breakdown of unknown,
On Wed, Feb 23, 2005 at 03:08:11AM +, Dirk Eddelbuettel wrote:
stuff and numbers
Just because an arch is fairly unused doesn't mean we should drop
it. We should drop an arch just like we would drop a package - if it
doesn't work, no one wants to maintain it, and if keeping it would
delay
701 - 800 of 1152 matches
Mail list logo
