Re: [frankie@debian.org: Status of kernel-patches in sarge]

[Steve Langasek]

On Sat, May 21, 2005 at 10:04:02AM +0200, Francesco Paolo Lovergine wrote:
> The check shown below is almost complete (but for a couple of 2.2 patches
> and per-arch patches).
> I'm asking if mass bug report filing is opportune at this stage.
> IMHO patches which cannot be applied to debian kernel-sources are almost
> unuseful and should be removed from sarge...

I think this is a reasonable thing to do, and the sooner, the better.  I
would suggest filing the bugs as grave ("package is unusable or mostly so").
If a maintainer disagrees and believes the patch is still useful in sarge,
he can downgrade (hopefully with an explanation, so we know how to tell in
the future that the package is still fulfilling its purpose).  Any of these
patches whose maintainers don't speak up for them can then be pulled before
we release.

Thanks,
-- 
Steve Langasek
postmodern programmer

> - Forwarded message from Francesco Paolo Lovergine <[EMAIL PROTECTED]> 
> -
> 
> Old-Return-Path: <[EMAIL PROTECTED]>
> From: Francesco Paolo Lovergine <[EMAIL PROTECTED]>
> To: debian-kernel@lists.debian.org
> Subject: Status of kernel-patches in sarge
> Mail-Followup-To: debian-kernel@lists.debian.org
> 
> I'm performing an ongoing activity to check the applicability of current
> kernel-patches against sarge kernel-sources for 2.4.27 and 2.6.8.
> 
> An almost complete summary is available at 
> 
> http://people.debian.org/~frankie/kernel-patches-checks.txt
> 
> As you can see, there are a few patches which cannot be used
> with neither 2.4.27 nor 2.6.8. Marked patches should be simply RC bugged
> and hinted for remove if not aligned properly.
> 
> I would also point that too often patch names differes from their 
> kernel-patch names,
> without justification. I'm working on a little script to do this kind of
> light check automatically, too.
> 
> -- 
> Francesco P. Lovergine
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> - End forwarded message -


signature.asc
Description: Digital signature

Bug#310165: ITP: bkchem -- Python based free chemical drawing program

[Li Daobing]

Package: wnpp
Severity: wishlist
Owner: Li Daobing <[EMAIL PROTECTED]>


* Package name: bkchem
  Version : 0.9.0
  Upstream Author : Beda Kosata <[EMAIL PROTECTED]>
* URL : http://bkchem.zirael.org/
* License : GPL & LGPL
  Description : Python based free chemical drawing program

 BKchem is a free (as in free software) chemical drawing program, which is
 written in python.
 .
 Some of the features, you can expect:
  * Drawing (bond-by-bond drawing; templates for common rings; expanding of
common-groups; draws radicals, charges, arrows; color support ...)
  * Editing (unlimited undo and redo capabilities; aligning; scaling;
rotation (2D, 3D) ...)
  * Export/Import (fully supported SVG-, OpenOffice.org-Draw-, EPS-export;
basic support for CML1 and CML2 import and export)

You can find debian source package at:
http://debian.wgdd.de/debian/dists/sid/contrib/source/science/
  
-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: unrar version confusion

[Adrian Bunk]

On Sat, May 21, 2005 at 08:33:20PM -0700, Steve Langasek wrote:
> On Sun, May 22, 2005 at 12:20:47AM +0200, Adrian Bunk wrote:
>...
> > Repairing this issue by simply renaming the non-free package back to 
> > unrar and giving the free program a different name should be pretty 
> > straightforward and doable for sarge.
> 
>...
> $ grep-excuses unrar-nonfree
> unrar-nonfree (- to 3.4.3-1)
> Maintainer: Chris Anderson 
> Section: non-free/utils
> 171 days old (needed 10 days)
> Not touching package, as requested by freeze (contact debian-release if 
> update is needed)
> out of date on alpha: unrar-nonfree (from 3.3.6-2)
> out of date on mips: unrar-nonfree (from 3.3.6-2)
> out of date on mipsel: unrar-nonfree (from 3.3.6-2)
> unrar-nonfree (source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, 
> powerpc, s390, sparc) is buggy! (1 > 0)
> Not considered
> $
> 
> Not really an issue for sarge anyway...

The RC bug in unrar-nonfree is only a small licence clarification issue 
that is already resolved in the latest upstream version of 
unrar-nonfree.

> Steve Langasek

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mdadm+udev needs testing!

[Andreas Gredler]

On Sat, May 21, 2005 at 05:51:44PM +0200, martin f krafft wrote:
> [Bcc: [EMAIL PROTECTED]
> 
> mdadm has three udev-related RC bugs (#294404, #273182 and #301560),
> which I seem to have been able to fix using previous work by Steve
> Langasek and Marco d'Itri. Since mdadm is a critical piece of
> software, I herewith call to those of you with the ability to test
> it in a udev environment to do so!

Ok, done :-)
I was testing on my unstable box with 2.6.9.
I had mdadm-1.9.0-2.1 installed and a RAID1, which I had to create with
-auto=yes.
I removed the raid (with mkfs.ext3 on the partitions) and rebooted the
machine to make sure that there are no /dev/md* nodes left.
Then "apt-get install mdadm -t madduck-nmu"
Now I was able to create my RAID without the -auto=yes option.

reptile:~$ ls -al /dev/md*
brw-rw  1 root disk 9,  0 May 22 10:31 /dev/md0
brw-rw  1 root disk 9,  1 May 22 10:31 /dev/md1
brw-rw  1 root disk 9, 10 May 22 10:31 /dev/md10
brw-rw  1 root disk 9, 11 May 22 10:31 /dev/md11
brw-rw  1 root disk 9, 12 May 22 10:31 /dev/md12
brw-rw  1 root disk 9, 13 May 22 10:31 /dev/md13
brw-rw  1 root disk 9, 14 May 22 10:31 /dev/md14
brw-rw  1 root disk 9, 15 May 22 10:31 /dev/md15
brw-r--r--  1 root root 9, 16 May 22 10:31 /dev/md16
brw-r--r--  1 root root 9, 17 May 22 10:31 /dev/md17
brw-r--r--  1 root root 9, 18 May 22 10:31 /dev/md18
brw-r--r--  1 root root 9, 19 May 22 10:31 /dev/md19
brw-rw  1 root disk 9,  2 May 22 10:31 /dev/md2
brw-r--r--  1 root root 9, 20 May 22 10:31 /dev/md20
brw-r--r--  1 root root 9, 21 May 22 10:31 /dev/md21
brw-r--r--  1 root root 9, 22 May 22 10:31 /dev/md22
brw-r--r--  1 root root 9, 23 May 22 10:31 /dev/md23
brw-r--r--  1 root root 9, 24 May 22 10:31 /dev/md24
brw-rw  1 root disk 9,  3 May 22 10:31 /dev/md3
brw-rw  1 root disk 9,  4 May 22 10:31 /dev/md4
brw-rw  1 root disk 9,  5 May 22 10:31 /dev/md5
brw-rw  1 root disk 9,  6 May 22 10:31 /dev/md6
brw-rw  1 root disk 9,  7 May 22 10:31 /dev/md7
brw-rw  1 root disk 9,  8 May 22 10:31 /dev/md8
brw-rw  1 root disk 9,  9 May 22 10:31 /dev/md9

I'm not sure why some devices are group root.

> You can get mdadm 1.9.0-2.2 for i386 as well as the source package
> from
> 
>   deb http://debian.madduck.net ~madduck/packages/nmu/mdadm/
>   deb-src http://debian.madduck.net ~madduck/packages/nmu/mdadm/

mdadm_1.9.0.orig.tar.gz is missing

HTH
greets Jimmy

-- 
 Andreas "Jimmy" Gredler 
   ,'"`. http://www.g-tec.co.at/ | [EMAIL PROTECTED]
  (  grml.org -» Linux for texttool-users and sysadmins
   `._,  http://www.grml.org/| [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: unrar version confusion

[Wouter Verhelst]

On Fri, May 20, 2005 at 05:59:36PM -0700, Russ Allbery wrote:
> Wouter Verhelst <[EMAIL PROTECTED]> writes:
> > Then the new program should still have a higher version number, to allow
> > people who currently use the non-free program to upgrade to the free
> > program.
> 
> That's why there's the 1: there to increase the epoch.

Oh, indeed, sorry. I misread and thought the original, non-free, rar had
an epoch of 3.

-- 
The amount of time between slipping on the peel and landing on the
pavement is precisely one bananosecond


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: big usermem kernel patch

[Russell Coker]

On Thursday 19 May 2005 12:26, Camm Maguire <[EMAIL PROTECTED]> wrote:
> Greetings!  It seems that we are in need of a 'big usermem' kernel
> patch in Debian, so I am considering contributing such a package.  It
> appears there are two approaches on the net, both in various
> incarnations of redhat:
>
> 1) user-tunable /proc/self/mapped_base -- this allows setuid processes
>to move the base address at which shared libs are mapped from the
>default (on x86) of 0x4000, allowing for much larger contiguous
>brk *or* mmaped space (up to 2.7 GB -- the oracle docs appear to
>refer to this.  See also WOLK).

What about the 4/4 kernel patch?  That should allow something > 3.5G of 
address space to be mapped contiguously.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mdadm+udev needs testing!

[martin f krafft]

also sprach Andreas Gredler <[EMAIL PROTECTED]> [2005.05.22.1052 +0200]:
> Now I was able to create my RAID without the -auto=yes option.

Good.

> brw-rw  1 root disk 9,  2 May 22 10:31 /dev/md2
> brw-r--r--  1 root root 9, 20 May 22 10:31 /dev/md20
> 
> I'm not sure why some devices are group root.

Only devices with minors up to and including 15 are created by
MAKEDEV. I have no idea where your other devices are coming from.
This should not be a problem though.

Nevertheless, are you using udev? If yes, then this *is* weird. If
not, then you can probably delete the device nodes /dev/md16 and up,
or chown/chmod them, depending on how many software RAID devices you
need.

> >   deb http://debian.madduck.net ~madduck/packages/nmu/mdadm/
> >   deb-src http://debian.madduck.net ~madduck/packages/nmu/mdadm/
> 
> mdadm_1.9.0.orig.tar.gz is missing

fixed.

Thanks for your time!

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
 
the security, stability and reliability of a computer system
is reciprocally proportional to
the amount of vacuity between the ears of the admin.


signature.asc
Description: Digital signature

Re: mdadm+udev needs testing!

[Andreas Gredler]

On Sun, May 22, 2005 at 11:47:07AM +0200, martin f krafft wrote:
> also sprach Andreas Gredler <[EMAIL PROTECTED]> [2005.05.22.1052 +0200]:
 
> > brw-rw  1 root disk 9,  2 May 22 10:31 /dev/md2
> > brw-r--r--  1 root root 9, 20 May 22 10:31 /dev/md20
> > 
> > I'm not sure why some devices are group root.
> 
> Only devices with minors up to and including 15 are created by
> MAKEDEV. I have no idea where your other devices are coming from.
> This should not be a problem though.

ACK.

> Nevertheless, are you using udev? If yes, then this *is* weird. If
> not, then you can probably delete the device nodes /dev/md16 and up,
> or chown/chmod them, depending on how many software RAID devices you
> need.

Yes, of course udev, because the bugs are udev-related, too :-)
In debian/mdrun you are creating devices with mdrun. There's one sed
script, which parses partitions but there's also a for loop for mknod:
0-24. I thinks that's the reason for 24 md devices :-) 

> Thanks for your time!

No problem, I need a good mdadm package ;-)

greets Jimmy

-- 
 Andreas "Jimmy" Gredler 
   ,'"`. http://www.g-tec.co.at/ | [EMAIL PROTECTED]
  (  grml.org -» Linux for texttool-users and sysadmins
   `._,  http://www.grml.org/| [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Inconsistent handling of sourceless packages in main

[Eduard Bloch]

Moin Goswin!
Goswin von Brederlow schrieb am Donnerstag, den 19. Mai 2005:

> IMHO debian-installer in unacceptable as it causes GPL violations.
> Interlocking the debian-installer builds with the exact source
...
> Any ideas? Comments? Solutions?

Relax, there is no problem. (The same was as there is no problem with
boot-floppies, beeing in Woody without the correct source. Nobody did
care in the last 3 years).

Regards,
Eduard.
-- 
In the beginning was the word, and the word was content-type: text/plain


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310194: ITP: schism -- Impulse Tracker clone

[Simon Richter]

Package: wnpp
Severity: wishlist
Owner: Simon Richter <[EMAIL PROTECTED]>

* Package name: schism
  Version : 0.2a
  Upstream Author : chisel <[EMAIL PROTECTED]>
* URL : http://rigelseven.com/schism/
* License : GPL
  Description : Impulse Tracker clone

Source: schism
Section: sound
Priority: optional
Maintainer: Simon Richter <[EMAIL PROTECTED]>
Build-Depends: debhelper (>= 4.0.0), libsdl1.2-dev, libmodplug-dev, 
autotools-dev
Standards-Version: 3.6.1

Package: schism
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: ImpulseTracker clone aiming at providing the same look&feel
 This is an editor for "tracked" music, i.e. audio samples of instruments
 pitch shifted according to the note data.
 .
 The Impulse Tracker is one of the most popular "tracker" programs at
 present, and Schism Tracker attempts to follow their UI layout wherever
 possible in order to make it easy for existing users to switch.

(Note: the upstream author's real name is not published on the website.
I've already contacted him about that).

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#310194: ITP: schism -- Impulse Tracker clone

[Jérôme Marant]

Simon Richter <[EMAIL PROTECTED]> writes:

> Package: wnpp
> Severity: wishlist
> Owner: Simon Richter <[EMAIL PROTECTED]>
>
> * Package name: schism
>   Version : 0.2a
>   Upstream Author : chisel <[EMAIL PROTECTED]>
> * URL : http://rigelseven.com/schism/
> * License : GPL
>   Description : Impulse Tracker clone

Wow. It reminds me the old days of Demo parties :-)

-- 
Jérôme Marant

Re: Bug#310194: ITP: schism -- Impulse Tracker clone

[Steinar H. Gunderson]

On Sun, May 22, 2005 at 02:12:27PM +0200, Jérôme Marant wrote:
> Wow. It reminds me the old days of Demo parties :-)

The old days? Those still exist :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: unrar version confusion

[Jeroen van Wolffelaar]

On Sun, May 22, 2005 at 12:41:11AM +0200, Adrian Bunk wrote:
> - rename the unrar-nonfree package back to unrar
> - rename the free unnrar package to unrar-free (it can even be left out 
>   of sarge (version 0.0.1 that is the one year old latest upstream 
>   version...))
> - get the non-free package that is again named unrar back into sarge

I've done the first point, neglecting the second point for now, and the
third point is an RM decision.

My rationale to do this, is:

- woody shipped with a non-free unrar named 'unrar', and it worked
- the free version is not functionally equivalent yet, of the .rar files
  in the wild, I couldn't actually find a single one that was
  unpackeable with the free unrar.
- So, it's too late now to have sarge ship with a free alternative,
  because development of that one simply hasn't reached a functionally
  (nearly-?) equivalent version. For etch, let's see, but for sarge,
  let's just maintain the situation as it was in woody: a non-free
  'unrar' for people not objecting to non-free who want to unrar files.

Once the free unrar matured enough, it can probably ultimately replace
unrar (again), but until that time, I really do believe the free unrar
should be named differently until that point is reached. I offer my
assistance to get this happening again because of what I've done to
unstable at the moment.

RMs, please review unrar-nonfree 1:3.5.2-0.1, restoring a new version of
the unrar that was in woody to sarge.

Thanks,
--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Debian Sarge

[Eddy Veenstra]

 
Dear 
Debian team,
 
For 
several years I used Debian 2.2R5 'potato' and was a happy user. In the meantime 
I've tried on that system Xfree 4.2 (download version), but it wasn't an 
easy task to get it properly installed. So I went back to my 'good-old' 2.2R5 
and decided to wait until Debian would come with a distribution that 
had XFree 4.2.
I've 
tested Mandrake 10.1 community and Suze 9.2 on my new PC ( AMD 3500+). On both 
distribution almost all hardware was detected and the proper drivers installed, 
except for my wireless network card (RT2500) which had to be done manually. Even 
my TV-card was recognized and installed.
What I 
don't like about Mandrake and Suze is that they decide which packages are to be 
installed; they do a lot behind my back and that's what I don't 
like.
Now I've 
downloaded Debian Sarge DVD-version with jigdo and that was a big 
improvement for downloading. The installation was in the old fashioned Debian 
way, so that was not a problem.
The 
installation asked for my video-card (Nvidia GeForce 5700LE)and my monitor ( CTX 
S962 19” LCD ). I selected the correct driver (NV) and gave the horizontal and 
vertical frequencies ( 30-80 hor, 59-75 vert ) for my monitor. When the 
installation was finished, X was started in 800x600 mode. No higher resolutions 
were possible. In the GNome environment I 
couldn't find a way to tell the system about my graphics card, my 
monitor, or the 
resolutions I prefer.
So I ran 
xf86config to solve the problem. No success. Apparently GNome doesn't react to 
the changes I made with xf86config. But how can I tell GNome what card and 
monitor I have? I've tried all the items in the menu to find a way, but I had no 
success. I've done six installations now, and every time the same problems 
occur. The problems on all occasion are listed below.

All kind of hardware wasn't 
detected:
Printer: HP PSC 2355 on USB
on-board sound card Realtek AC '97
Pinnacle TV card Pro
Wireless networkcard RT2500
Modem Intel 536EP

Other thing I've found:
Error message 'No CUPS-Server running'. 
Adding a printer gave no solution. 
I Prefer KDE over GNome. But GNome is 
always installed. In 2.2R5 you could choose the Desktop manager(s). How can it 
be done in 3.1?

My system:
Mainboard: Asus A8V de luxe, AMD 
3500+
Graphic card NVidia GeForce 5700 LE
Monitor CTX S962A
hda: Quantum Fireball 6.2 Gb; Fat 32 
Windows 98
hdb: Seagate 20 Gb; hdb1: Ext3 root 
filesystem;   hdb2: Ext2;   hdb3: linux swap
sda: Maxtor 200Gb. Sda1 ntsf 
WinXP;   sda2 ntsf;   sda3 Linux swap
 
I hope you can solve some things for 
me.
Regards,
Eddy 
Veenstra

mdadm+udev needs MORE testing!

[martin f krafft]

We have revamped the mdadm fix in a much cleaner way, using a patch
by Erik van Konijnenburg to fix the --auto command line option.
Also, some fixes to mdrun (which is deprecated but must still work)
and device node permissions have been committed. Lastly,
a README.udev file is now provided.

If you get a chance, please test the latest package:

> You can get mdadm 1.9.0-2.2 for i386 as well as the source package
> from
> 
>   deb http://debian.madduck.net ~madduck/packages/nmu/mdadm/
>   deb-src http://debian.madduck.net ~madduck/packages/nmu/mdadm/
> 
> or
> 
>   http://debian.madduck.net/~madduck/packages/nmu/mdadm/

Thanks a lot.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
 
whatever you do will be insignificant,
but it is very important that you do it.
 -- mahatma gandhi


signature.asc
Description: Digital signature

Re: Debian Sarge

[Andrew M.A. Cater]

On Sun, May 22, 2005 at 02:26:59PM +0200, Eddy Veenstra wrote:
>  
> Dear Debian team,
> 
For the future: this question and others like it would be better asked
on debian-user. Debian-devel is essentially a list for Debian developers
and others to discuss the development of Debian - including off-topic
flamewars as well, of course :)
> 
> 
> For several years I used Debian 2.2R5 'potato' and was a happy user. In the 
> meantime I've tried on that system Xfree 4.2 (download version), but it 
> wasn't an easy task to get it properly installed. So I went back to my 
> 'good-old' 2.2R5 and decided to wait until Debian would come with a 
> distribution that had XFree 4.2.
> 
> I've tested Mandrake 10.1 community and Suze 9.2 on my new PC ( AMD 3500+). 
> On both distribution almost all hardware was detected and the proper drivers 
> installed, except for my wireless network card (RT2500) which had to be done 
> manually. Even my TV-card was recognized and installed.
> 
> What I don't like about Mandrake and Suze is that they decide which packages 
> are to be installed; they do a lot behind my back and that's what I don't 
> like.
> 
> Now I've downloaded Debian Sarge DVD-version with jigdo and that was a big 
> improvement for downloading. The installation was in the old fashioned Debian 
> way, so that was not a problem.
> 

That's good to hear. The new Debian installer is at least more
straightforward than the 2.2 installer. One suggestion to everyone:
if things aren't detected initially, try restarting the installation
and using 

expert26

which will ask you all the questions in the install - which may allow
you to pass parameters for modules and other things.

> The installation asked for my video-card (Nvidia GeForce 5700LE)and my 
> monitor ( CTX S962 19" LCD ). I selected the correct driver (NV) and gave the 
> horizontal and vertical frequencies ( 30-80 hor, 59-75 vert ) for my monitor. 
> When the installation was finished, X was started in 800x600 mode. No higher 
> resolutions were possible. In the GNome environment I couldn't find a way to 
> tell the system about my graphics card, my monitor, or the resolutions I 
> prefer.
>
Try 

apt-get install x-window-system kde

as a start. If you have both GNOME and KDE installed, it seems to me
that GNOME is always started by default.  Use the session selector on
either GDM or KDM such that the first session you start up is KDE and
you'll start KDE afterwards, since the default is always to start the 
last session used.

dpkg-reconfigure -plow xserver-xfree86

will re-ask the questions for XFree86 configuration.
> 
> So I ran xf86config to solve the problem. No success. Apparently GNome 
> doesn't react to the changes I made with xf86config. But how can I tell GNome 
> what card and monitor I have? I've tried all the items in the menu to find a 
> way, but I had no success. I've done six installations now, and every time 
> the same problems occur. The problems on all occasion are listed below.
> 
Try the above.
> 
> All kind of hardware wasn't detected:
> 
> Printer: HP PSC 2355 on USB
> 
Apt-get install hp-ijs ?? : what happens if you plug in / unplug the
printer - do you get any message on the screen?

> on-board sound card Realtek AC '97

You probably need various sound modules including ac97 included. KDE
uses alsa by default.
> 
> Pinnacle TV card Pro
> 
bt848 / bt878 modules, perhaps??

> Wireless networkcard RT2500
> 

Not sure whether this is included by default but the driver is at least
open source.

> Modem Intel 536EP

No idea - is this actually a modem or a Windows HCF soft modem??
> 
> Other thing I've found:
> 
> Error message 'No CUPS-Server running'. Adding a printer gave no solution. 
> 
apt-get install hplip cupsys and the other dependencies.

> I Prefer KDE over GNome. But GNome is always installed. In 2.2R5 you could 
> choose the Desktop manager(s). How can it be done in 3.1?
> 
> My system:
> 
> Mainboard: Asus A8V de luxe, AMD 3500+
> 
> Graphic card NVidia GeForce 5700 LE
> 
> Monitor CTX S962A
> 
> hda: Quantum Fireball 6.2 Gb; Fat 32 Windows 98
> 
> hdb: Seagate 20 Gb; hdb1: Ext3 root filesystem;   hdb2: Ext2;   hdb3: linux 
> swap
> 
> sda: Maxtor 200Gb. Sda1 ntsf WinXP;   sda2 ntsf;   sda3 Linux swap
> 
> 
> 
> I hope you can solve some things for me.
> 
> Regards,
Hope this helps,

Andy
> 
> Eddy Veenstra


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Changes to the weekly WNPP posting

[Martin Michlmayr]

* Tollef Fog Heen <[EMAIL PROTECTED]> [2005-05-20 09:55]:
> Throw in a link to the full list for RFA/O/RFH too?  Apart from that,
> I'd love to see it on d-d-a.

OK, I'll add links.  Note sure about d-d-a or d-d yet.  Someone also
suggested an RSS feed.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Changes to the weekly WNPP posting

[Martin Michlmayr]

* Jeroen van Wolffelaar <[EMAIL PROTECTED]> [2005-05-20 11:48]:
> One could decide to let RM: bugs on ftp.d.o always linger a certain
> amount of time before processing, for complete removals, in any case.

That's someone I wanted to suggest anyway.  While I'm happy to see
removals happening much more frequently and quickly these days, the
downside is that it doesn't give people a chance to complain when
someone is removed within minutes of it being requested.
-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#310194: ITP: schism -- Impulse Tracker clone

[Jérôme Marant]

"Steinar H. Gunderson" <[EMAIL PROTECTED]> writes:

> On Sun, May 22, 2005 at 02:12:27PM +0200, Jérôme Marant wrote:
>> Wow. It reminds me the old days of Demo parties :-)
>
> The old days? Those still exist :-)

Yes, but the original spirit has gone.

-- 
Jérôme Marant

Re: Bug#310194: ITP: schism -- Impulse Tracker clone

[Steinar H. Gunderson]

On Sun, May 22, 2005 at 06:36:01PM +0200, Jérôme Marant wrote:
>> The old days? Those still exist :-)
> Yes, but the original spirit has gone.

Tsk. :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

depending on shared libbfd from binutils-dev

[Micah Anderson]

The package description for binutils-dev says the following:

>Description: The GNU binary utilities (BFD development files) This
> package includes header files and static libraries necessary to build
> programs which use the GNU BFD library, which is part of binutils.
> Note that building Debian packages which depend on the shared libbfd
> is Not Allowed.
 
I see this in the binutils-dev package description, however I dont see
it anywhere else, not in the policy, not in lintian/linda checks, not
on any mailing lists I see a couple of people on debian-devel
asking (a couple years ago) what the deal is with this, but no
informative responses. Does anyone know *why* this is and why this
isn't documented somewhere more visible?

Thanks,
micah



signature.asc
Description: Digital signature

Re: depending on shared libbfd from binutils-dev

[Steve Langasek]

On Sun, May 22, 2005 at 12:24:28PM -0500, Micah Anderson wrote:
> The package description for binutils-dev says the following:

> >Description: The GNU binary utilities (BFD development files) This
> > package includes header files and static libraries necessary to build
> > programs which use the GNU BFD library, which is part of binutils.
> > Note that building Debian packages which depend on the shared libbfd
> > is Not Allowed.

> I see this in the binutils-dev package description, however I dont see
> it anywhere else, not in the policy, not in lintian/linda checks, not
> on any mailing lists I see a couple of people on debian-devel
> asking (a couple years ago) what the deal is with this, but no
> informative responses. Does anyone know *why* this is and why this
> isn't documented somewhere more visible?

Because libbfd does not have a stable ABI suitable for public use, nor is
there currently a way to express a dependency on this library without
things breaking (you can't depend on "binutils" and have any guarantee of
getting the correct lib).

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: unrar version confusion

[Niklas Vainio]

I'm the (previous) maintainer of unrar. Jose Carlos Medeiros has offered to
adopt it.

On Sun, May 22, 2005 at 02:36:50PM +0200, Jeroen van Wolffelaar wrote:
> On Sun, May 22, 2005 at 12:41:11AM +0200, Adrian Bunk wrote:
> > - rename the unrar-nonfree package back to unrar
> > - rename the free unnrar package to unrar-free (it can even be left out 
> >   of sarge (version 0.0.1 that is the one year old latest upstream 
> >   version...))
> > - get the non-free package that is again named unrar back into sarge

I support your suggestions of renaming. I also think there should be an
unrar implementation in the next Debian stable. Currently there is none.
(The Debian project distributes a non-free unrar from its servers, but it's
not part of Debian.)

I've kept unrar intentionally out of sarge because of incompability
problems. Changing the package name and fixing rest of the bugs (I've sent
some patches) would allow it go in.

> Once the free unrar matured enough, it can probably ultimately replace
> unrar (again), but until that time, I really do believe the free unrar
> should be named differently until that point is reached. I offer my
> assistance to get this happening again because of what I've done to
> unstable at the moment.

Jose, have you got any comments? Have you got a sponsor? Jeroen, could you
sponsor Jose if needed?

-- 
Niklas Vainio <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [frankie@debian.org: Status of kernel-patches in sarge]

[Francesco Paolo Lovergine]

On Sun, May 22, 2005 at 12:40:26AM -0700, Steve Langasek wrote:
> On Sat, May 21, 2005 at 10:04:02AM +0200, Francesco Paolo Lovergine wrote:
> > The check shown below is almost complete (but for a couple of 2.2 patches
> > and per-arch patches).
> > I'm asking if mass bug report filing is opportune at this stage.
> > IMHO patches which cannot be applied to debian kernel-sources are almost
> > unuseful and should be removed from sarge...
> 
> I think this is a reasonable thing to do, and the sooner, the better.  I
> would suggest filing the bugs as grave ("package is unusable or mostly so").
> If a maintainer disagrees and believes the patch is still useful in sarge,
> he can downgrade (hopefully with an explanation, so we know how to tell in
> the future that the package is still fulfilling its purpose).  Any of these
> patches whose maintainers don't speak up for them can then be pulled before
> we release.
> 

Yes, this appears reasonable to me.

-- 
Francesco P. Lovergine


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [frankie@debian.org: Status of kernel-patches in sarge]

[Francesco Paolo Lovergine]

On Sun, May 22, 2005 at 12:35:59AM +0200, Adrian Bunk wrote:
> On Sat, May 21, 2005 at 10:04:02AM +0200, Francesco Paolo Lovergine wrote:
> 
> > The check shown below is almost complete (but for a couple of 2.2 patches
> > and per-arch patches).
> > I'm asking if mass bug report filing is opportune at this stage.
> > IMHO patches which cannot be applied to debian kernel-sources are almost
> > unuseful and should be removed from sarge...
> >...
> 
> I'd even ask whether all these patches are _really_ required for sarge.
> 

Eh eh, maybe that could be ask for quite a lot of packages around in sarge :-)

> Each of the patches might be broken by a security update for the 
> kernel and each of them requires security support.
> 

I'd expect maintainers drop patches which are orphaned by the upstream
or whose maintainance would be a problem... 

-- 
Francesco P. Lovergine


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310258: ITP: nautilus-open-terminal -- open terminal in any folder from Nautilus

[Dan Korostelev]

Package: wnpp
Severity: wishlist
Owner: Dan Korostelev <[EMAIL PROTECTED]>

* Package name: nautilus-open-terminal
  Version : 0.2
  Upstream Author : Christian Neumair <[EMAIL PROTECTED]>
* URL : http://manny.cluecoder.org/packages/nautilus-open-terminal/
* License : GPL
  Description : open terminal in any folder from Nautilus

 This is an extension for Nautilus (file manager for
 GNOME desktop) that provides a menu option for any
 local folder object to open a terminal in that folder.

-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-9-amd64-k8
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

FW: Processing of tla-load-dirs_1.0.21ubuntu1_source.changes

[John Goerzen]

Can anyone tell me what this means, and who is trying to upload this to
Debian without even sending me a patch first?


- Forwarded message from Archive Administrator <[EMAIL PROTECTED]> -

From: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 22 May 2005 14:30:38 -0400
To: [EMAIL PROTECTED]
Subject: Processing of tla-load-dirs_1.0.21ubuntu1_source.changes

PGP/GnuPG signature check failed on tla-load-dirs_1.0.21ubuntu1_source.changes
gpg: Signature made Sun May 22 14:24:08 2005 EDT using DSA key ID C5AA2301
gpg: Can't check signature: public key not found
(Exit status 2)
tla-load-dirs_1.0.21ubuntu1_source.changes has bad PGP/GnuPG signature!
Removing tla-load-dirs_1.0.21ubuntu1_source.changes, but keeping its associated 
files for now.

Greetings,

Your Debian queue daemon


- End forwarded message -

-- 
John Goerzen
Author, Foundations of Python Network Programming
http://www.amazon.com/exec/obidos/tg/detail/-/1590593715


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: FW: Processing of tla-load-dirs_1.0.21ubuntu1_source.changes

[Adrian Bunk]

On Sun, May 22, 2005 at 03:56:35PM -0500, John Goerzen wrote:

> Can anyone tell me what this means, and who is trying to upload this to
> Debian without even sending me a patch first?

This gpg key belongs to Jani Monoses (Cc'ed).

Perhaps he can tell what happened (looks like an accidental upload to 
Debian instead of Ubuntu).

> - Forwarded message from Archive Administrator <[EMAIL PROTECTED]> -
> 
> From: Archive Administrator <[EMAIL PROTECTED]>
> Date: Sun, 22 May 2005 14:30:38 -0400
> To: [EMAIL PROTECTED]
> Subject: Processing of tla-load-dirs_1.0.21ubuntu1_source.changes
> 
> PGP/GnuPG signature check failed on tla-load-dirs_1.0.21ubuntu1_source.changes
> gpg: Signature made Sun May 22 14:24:08 2005 EDT using DSA key ID C5AA2301
> gpg: Can't check signature: public key not found
> (Exit status 2)
> tla-load-dirs_1.0.21ubuntu1_source.changes has bad PGP/GnuPG signature!
> Removing tla-load-dirs_1.0.21ubuntu1_source.changes, but keeping its 
> associated files for now.
> 
> Greetings,
> 
>   Your Debian queue daemon
> 
> 
> - End forwarded message -

> John Goerzen

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310290: ITP: libccl0 -- Interface to configuration files containing key/value pairs

[Juergen Salk]

Package: wnpp
Severity: wishlist
Owner: Juergen Salk <[EMAIL PROTECTED]>


* Package name: libccl0
  Version : 0.1.1
  Upstream Author : Stephen F. Booth <[EMAIL PROTECTED]>
* URL : http://sbooth.org/ccl
* License : GPL
  Description : Interface to configuration files containing key/value pairs

Customizable configuration library, a collection of functions
for application programmers wishing to interface with
user-editable configuration files containing key/value pairs.

ccl is customizable because it allows the comment, key/value, and
string literal delimiters to be programatically specified at
runtime.  
ccl is designed to be simple and portable; it has a small
interface consisting of five functions and is written in ANSI/ISO
C. ccl uses avl's implemenation of binary search trees for
backend storage.

Regards, 

Juergen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mdadm+udev needs MORE testing!

[martin f krafft]

also sprach Jan Dittmer <[EMAIL PROTECTED]> [2005.05.22.2305 +0200]:
> Works for me.  assembled by the kernel. udev nodes are created correctly.

Thanks. a newer version, -2.3, will make it into sarge. Thanks to
everyone who helped.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
 
"you don't sew with a fork, so i see no reason
 to eat with knitting needles."
   -- miss piggy, on eating chinese food


signature.asc
Description: Digital signature

Re: mdadm+udev needs MORE testing!

[Jan Dittmer]

martin f krafft wrote:

>>You can get mdadm 1.9.0-2.2 for i386 as well as the source package
>>from

Works for me. 

$ ls -l /dev/md*
lrwxrwxrwx  1 root root   4 May 22 22:56 /dev/md0 -> md/0
lrwxrwxrwx  1 root root   4 May 22 22:56 /dev/md1 -> md/1
lrwxrwxrwx  1 root root   4 May 22 22:56 /dev/md2 -> md/2
lrwxrwxrwx  1 root root   4 May 22 22:56 /dev/md3 -> md/3

/dev/md:
total 0
brw-rw  1 root disk 9, 0 May 22 22:56 0
brw-rw  1 root disk 9, 1 May 22 22:56 1
brw-rw  1 root disk 9, 2 May 22 22:56 2
brw-rw  1 root disk 9, 3 May 22 22:56 3

-- 
Jan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#72140: Much more better than usual, believe me.

[Deanna]

Guys keep it real hard.
http://VOSIeawbXRgqmby.t6i.net/pharm/sevy/rustic.php

Deanna

Re: Example where testing-security was used?

[Steve Langasek]

On Sun, May 22, 2005 at 12:46:09AM +0200, Adrian Bunk wrote:
> As far as I understood it, the missing infrastructure for 
> testing-security was the reason why the release of sarge was delayed by 
> more than half a year.

> As far as I have seen, it seems most security updates go either through 
> unstable or through testing-proposed-updates.

> Can anyone point me to an example where testing-security has actually 
> been used?

At present, unfortunately not.

This does not obviate the need for testing-security to be brought on-line
and tested prior to the freeze; the woody release was delayed for about a
month because of the lack of usable autobuilder infrastructure for security
updates, and if we had tried to freeze sarge before the same infrastructure
was available, we would have had the same problem again (except compounded
with others this time, like ftp-master not scaling to handle the added
load).

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Bug#53121: When you get it you don't regret.

[Young]

Much more better than usual, believe me.
http://GVGdfcfTWtwx.mfek.com/ph/sevy/procrustean.htm

Young

why so much spam on the devel list?

[Kamaraju Kusumanchi]

Hi
   I am subscribed to debian-user, debian-mentors and debian-devel 
lists. I am finding that typically debian-devel and debian-mentors is 
way more spammed than debian-user. Why is it so? Am I just day dreaming 
or is there any reason? Is there anything we forgot to implement on d-d 
lists that has already been implemented on d-u?


thanks
raju


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#78782: No way back once you try it.

[Fern]

Actually she takes much more time to have pleaseure.
http://VWBoasUZrcvo.yi4.net/pharm/sevy/bumptious.html

Fern

Re: why so much spam on the devel list?

[Adam Heath]

On Sun, 22 May 2005, Kamaraju Kusumanchi wrote:

> Hi
> I am subscribed to debian-user, debian-mentors and debian-devel
> lists. I am finding that typically debian-devel and debian-mentors is
> way more spammed than debian-user. Why is it so? Am I just day dreaming
> or is there any reason? Is there anything we forgot to implement on d-d
> lists that has already been implemented on d-u?

Few obvious things come to mind.

Bugs filed against Package: general are sent to -devel.

Mails from the bug system sent to -devel are whitelisted, and don't go thru
the spam filters on murphy.

The bug system has it's own set of filters, including spamassassin and
crossassin.

Bugs themselves are an additional source of spam targets; so them plus the
list will generally cause an increase of spam on debian-devel.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Regarding unresponsive Debian maintainers (was: Re: Open-Source environments for Java)

[Rogério Brito]

On May 22 2005, Roberto C. Sanchez wrote:
> Rogério Brito wrote:
> > In my very humble and uninformed opinion, some maintainers should
> > really give up maintaining their packages or should try to get other
> > people as co-maintainers, if they lack the time to fix their
> > packages. :-(
> > 
> > If they applied to the project, then, they committed themselves to some
> > responsibilities and even though the project is mostly driven by
> > volunteers, if they can't keep up with their committments, then they
> > should politely be asked to give space to other people. And I can tell
> > you that there are other people interested in *working* for the
> > project.
> 
> By my count, there are already many maintainers that have done so with
> their packages:
> 
> http://www.nl.debian.org/devel/wnpp/rfa_bypackage
> http://www.nl.debian.org/devel/wnpp/orphaned
> http://www.nl.debian.org/devel/wnpp/being_adopted
> 
> I understand that not all are represented however.

*That* was my point. The fact that a given package is being orphaned or
adopted actually seems to indicate that some attention is being given to
it: the maintainer recognizes that he has no time or interest in the
package anymore and won't be stalling the project (or, at least, the users
of such packages).

And the fact that a package is adopted shows that it is important to, at
least, someone (the person adopting the package, of course -- but probably
many other users also).

> I have seen cases of maintainers that have packages with may bug reports,
> without any indication of an intent to fix them.

Exactly. It is a frustration to have a bug filed for, say, almost one year
(Lack of time during one year? Better drop the position of being a Debian
developer, then).

I have filed some bugs (sometimes *with* patches included) and not received
any response from the maintainer. Not only me, but many other users. Want
an example? See the maintainer of the vrms package.

I merged some bugs there. I sent the maintainer a simplified patch (after
another user had already sent a better patch, but possibly more
"intrusive"). I'm still waiting for a response. And the package could
easily be fixed (say, a hot fix) and then refactored to include a proper
fix and some quite useful features (like listing contrib packages).

I think that Martin-Éric Racine has expressed this quite well in his
message on the BTS: .

And this is not the only case. Want to see other examples? See, for
instance, the bugs for grip (I have at least two filed there, both with
more than 200 days).

And there are many other examples of unresponsive maintainers. Would it be
the case of the project taking a drastic change and dropping such
developers (and some of the buggy, obsolete packages) more often than what
is currently done?

Perhaps this would be a good movement to get "the cruft" out of Debian and
get it to a manageable size. Perhaps that could lead to slightly faster
release cycles.

> They don't respond to pings from other developers or users.

Yes, I have suffered from that, as expressed above. :-(

And I think that the Project Leaders (say, Project Scud) could take some
actions regarding this. It would only benefit the project, as far as I can
see.

> Then when someone NMUs their package to fix a bug or something like that,
> they immediately revert the changes.

Which means that they actually had time to revert the changes and upload a
new package. Why couldn't they fix the package in the first place? Or
simply marking a bug with "wontfix".

That's enough for the user to know the status of the package s/he is using
(and to know if a locally compiled version should be made).


Just my 2 cents, Rogério Brito.

-- 
Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lxdoom: help wanted

[Joe Drew]

For some time I've been more or less MIA, but in the past month or so  
it became impossible for me to do debian work: the processor in my  
desktop, my only Debian machine (the only other machine I own has a  
proprietary, non-Linux compatible (Airport Extreme) wifi card)  
released its magic smoke.


For that reason, could interested developers please NMU lxdoom? It  
has a couple of patches in the bts that should be applied.


Thanks very much to any who can help.

Joe

PS: Not subscribed to -devel, please CC me.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Changes to the weekly WNPP posting

[Thomas Bushnell BSG]

Martin Michlmayr <[EMAIL PROTECTED]> writes:

> * Jeroen van Wolffelaar <[EMAIL PROTECTED]> [2005-05-20 11:48]:
>> One could decide to let RM: bugs on ftp.d.o always linger a certain
>> amount of time before processing, for complete removals, in any case.
>
> That's someone I wanted to suggest anyway.  While I'm happy to see
> removals happening much more frequently and quickly these days, the
> downside is that it doesn't give people a chance to complain when
> someone is removed within minutes of it being requested.

Someone or something?

It's surely possible to put it back if the removal was bad, right?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Regarding unresponsive Debian maintainers (was: Re: Open-Source environments for Java)

[Andrew Suffield]

On Mon, May 23, 2005 at 12:55:30AM -0300, Rog?rio Brito wrote:
> > I have seen cases of maintainers that have packages with may bug reports,
> > without any indication of an intent to fix them.
> 
> Exactly. It is a frustration to have a bug filed for, say, almost one year
> (Lack of time during one year? Better drop the position of being a Debian
> developer, then).

Admittedly there are probably a fair number of cases where developers
are waiting for sarge to stop this damned *looming* over the project
and get out the way, before making changes which are neither critical
nor trivial.

-- 
  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' :  http://www.debian.org/ |
 `. `'  |
   `- -><-  |


signature.asc
Description: Digital signature