> > is Martin Schulze; [...]
>
> Yes, but he prefers to be called Joey.
But has "Martin" in his From line, which is pretty confusing for
people who are not hardcore Debianers since the origins of
computing...:-)
signature.asc
Description: Digital signature
Quoting Kevin B. McCarty ([EMAIL PROTECTED]):
> Hi all,
>
> Does anyone know whether the default sbuild environment includes the
> file /etc/shadow? I am sponsoring a package ("root", cf. #325306) whose
> configure script tests the existence of /etc/shadow to decide whether or
> not to support sh
On 25 Apr 2006, Bernhard R. Link outgrape:
> * Manoj Srivastava <[EMAIL PROTECTED]> [060425 18:09]:
>> On what basis are you making this decision? I explained that it is
>> important, for debugging and development reasons for the free
>> software community, to be able to easily build upstream vers
Package: wnpp
Severity: wishlist
Owner: Jamie Wilkinson <[EMAIL PROTECTED]>
* Package name: facter
Version : 1.1.4
Upstream Author : Luke Kanies <[EMAIL PROTECTED]>
* URL : http://reductivelabs.com/projects/facter
* License : GPL
Programming Lang: Ruby
Descr
On Wed, Apr 26, 2006 at 08:08:50PM -0400, Stefano Zacchiroli wrote:
> On Thu, Apr 27, 2006 at 01:28:09AM +0200, Wouter Verhelst wrote:
> > That's why we have FTBFS bugs.
>
> The efficiency of that is far lower. FTBFS bugs are manually submitted,
> more then once I experienced a gap of weeks betwee
On Thu, Apr 27, 2006 at 01:28:09AM +0200, Wouter Verhelst wrote:
> That's why we have FTBFS bugs.
The efficiency of that is far lower. FTBFS bugs are manually submitted,
more then once I experienced a gap of weeks between the actual FTBFS and
the bug report.
Having the possibility of subscribing
On Wed, Apr 26, 2006 at 06:07:37PM -0400, Kevin B. McCarty wrote:
> Hi all,
>
> Does anyone know whether the default sbuild environment includes the
> file /etc/shadow?
It might, if the admin set it up inside the chroot. It's not guaranteed,
though, as sbuild functions without it, too (though it
On Wed, Apr 26, 2006 at 03:07:58PM -0400, Stefano Zacchiroli wrote:
> On Mon, Apr 24, 2006 at 07:31:13PM +0200, Wouter Verhelst wrote:
> > > Those cases can be treated differently than failures due to other
> > > reasons, though.
> > Uh, yes; and they are. But that's not the point.
> >
> > The poi
On Mon, Apr 24, 2006 at 05:32:00PM +0200, Michelle Konzack wrote:
> Am 2006-04-21 11:54:47, schrieb Wouter Verhelst:
> > On Fri, Apr 21, 2006 at 08:14:10AM +0200, Wolfgang Lonien wrote:
> > > Adrian von Bidder wrote:
> > > > How do I bind a computer to an NIS server?
> > > > Use a rope?
> > > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 26/apr/06, alle ore 15:25, Joerg Jaspert ha scritto:
experimental is autobuild, thats no reason to not use it.
And you dont break the existing squid package in unstable/testing with
an upload to exp.
I think I wasn't clear when I explain
Il giorno 26/apr/06, alle ore 12:35, Eduard Bloch ha scritto:
How would that interact with running squid installations? Please
tell us
what the actuall constraints are instead of repeating "needs to stay
here, needs to stay there". I assume you want to:
- make a package name more clear to sh
Hi all,
Does anyone know whether the default sbuild environment includes the
file /etc/shadow? I am sponsoring a package ("root", cf. #325306) whose
configure script tests the existence of /etc/shadow to decide whether or
not to support shadow passwords. This is a compile-time setting, so I'd
li
On Wed, 26 Apr 2006, Robert Collins wrote:
> Wearing my upstream hat, I'd like to see squid3 packages that *do not*
> conflict or replace squid packages in a release.
>
> Squid3 has many features that are simply not available to squid 2.5, and
> I think parallel installs are really quite reasonabl
Hi,
I've redone the packaging for ndiswrapper, starting with 1.8-2. My goal
is to allow utils packages to be installed in parallel, and to allow a
smooth upgrade from both 1.1-4 (the version that's in sarge) and 1.8-1
(the version that's in sid).
If you are running ndiswrapper 1.8-1, please upgr
Package: wnpp
Severity: wishlist
Owner: "Jaldhar H. Vyas" <[EMAIL PROTECTED]>
* Package name: libkwiki-plugins-perl
Version : 0.01
Upstream Author : Various. Compiled by Jaldhar H. Vyas <[EMAIL PROTECTED]>
* URL : N/A
* License : GPL+Artistic
Description
On Apr 26, Mike Bird <[EMAIL PROTECTED]> wrote:
> > FYI, this will probably horribly break the udev configuration.
> There may well be situations where Udev breaks but I haven't seen
There are, I am sure about this. You MUST purge and reinstall udev to
have a chance for it to work.
If you do not i
On Mon, Apr 24, 2006 at 07:31:13PM +0200, Wouter Verhelst wrote:
> > Those cases can be treated differently than failures due to other
> > reasons, though.
> Uh, yes; and they are. But that's not the point.
>
> The point really is that build failures rarely need maintainer
> intervention. Botheri
On Wed, Apr 26, 2006 at 11:56:36AM -0700, Mike Bird wrote:
> On Wed, 2006-04-26 at 11:31, Marco d'Itri wrote:
> > On Apr 26, Mike Bird <[EMAIL PROTECTED]> wrote:
> > > In working on (unsupported) dist-upgrades from Ubuntu/Breezy
> > > to Debian/Etch I ran into a lot of failures due to missing
> > F
On Wed, 2006-04-26 at 11:31, Marco d'Itri wrote:
> On Apr 26, Mike Bird <[EMAIL PROTECTED]> wrote:
> > In working on (unsupported) dist-upgrades from Ubuntu/Breezy
> > to Debian/Etch I ran into a lot of failures due to missing
> FYI, this will probably horribly break the udev configuration.
There
On Apr 26, Mike Bird <[EMAIL PROTECTED]> wrote:
> In working on (unsupported) dist-upgrades from Ubuntu/Breezy
> to Debian/Etch I ran into a lot of failures due to missing
FYI, this will probably horribly break the udev configuration.
--
ciao,
Marco
signature.asc
Description: Digital signature
Em Qua, 2006-04-26 às 18:49 +0200, Gonéri Le Bouder escreveu:
> On graphic software websites, in general the most visited page is the one
> with
> the screenshots because it give a good overview of the software.
> In general a screenshot is better that the limited description provided by
> the
Hello,
On graphic software websites, in general the most visited page is the one with
the screenshots because it give a good overview of the software.
In general a screenshot is better that the limited description provided by the
Debian control file.
I think that tools like synaptic or Debian I
On Wed, Apr 26, 2006 at 09:14:40AM -0700, Mike Bird wrote:
> How else should I report this, if at all?
>
> In working on (unsupported) dist-upgrades from Ubuntu/Breezy
> to Debian/Etch I ran into a lot of failures due to missing
> gconf-schemas. A lot of gnome software uses gconf-schemas
> in pos
How else should I report this, if at all?
In working on (unsupported) dist-upgrades from Ubuntu/Breezy
to Debian/Etch I ran into a lot of failures due to missing
gconf-schemas. A lot of gnome software uses gconf-schemas
in postinst but depends on gconf2 >= 2.10.1-2. gconf-schemas
seems to have a
On 10636 March 1977, Luigi Gangitano wrote:
>> Upload to experimental, not as new source.
> Why not?
Just from what i read in the thread...
> Since I'd like to make squid3 easily available to all those that want
> to try the new features, without braking the existing squid package,
> unstable is
Steve Langasek wrote:
> In that case, you probably want to open a RFA bug rather than an O bug.
Yep. I got #364606 now.
Really, people, nobody wants a beautiful lirc package?
--
.''`. I may not have gone where I intended to go, but I think
: :' : I have ended up where I needed to be -- D
Dear Steinar,
I'm not an expert on NFS/SunRPC so I cannot say it would be good or bad to
assign fixed port numbers on debian BY DEFAULT.
Regards,
David
- Original Message -
> On Wed, Apr 26, 2006 at 06:36:59AM -0500, David McGiven wrote:
> > The newer 2.6 series kernels support configu
This one time, at band camp, David McGiven said:
>
> Dear Debian Developers,
>
> The newer 2.6 series kernels support configuring the TCP/UDP port number
> of the kernel lockd via the files /proc/sys/fs/nfs/nlm_tcpport and
> /proc/sys/fs/nfs/nlm_udpport.
[EMAIL PROTECTED]:~$ cat /etc/sysctl.conf
Marco,
Most probably you're right, but take a look to this scenario :
You want to change the lockd ports. For this you have to stop->start the
nfs-common service, echo "port" > /proc/sys/fs/nfs/nlm_tcpport and start
again.
When you're sure you want those ports, and if you want to preserve this
Re: To debian-devel@lists.debian.org 2006-04-26 <[EMAIL PROTECTED]>
> [*] Though I don't think "we" ever said Manoj's wish to rename the
> package was unethical - "we" just think that it confuses users more
> than it serves them. But as said, that's up to the maintainer to
> decide.
Hrm, I missed
Am 2006-04-22 01:27:18, schrieb Henning Makholm:
> Scripsit Wolfgang Lonien <[EMAIL PROTECTED]>
>
> > And for those who still are complaining about the installer not being
> > graphical: please, guys, there's more than your x86 machines. Keep that
> > in mind. And where is the difference between a
Am 2006-04-21 11:54:47, schrieb Wouter Verhelst:
> On Fri, Apr 21, 2006 at 08:14:10AM +0200, Wolfgang Lonien wrote:
> > Adrian von Bidder wrote:
> > > How do I bind a computer to an NIS server?
> > > Use a rope?
> > > -- Seen on #Debian
> >
> > That was a good one! Was it Joey H. or Joey S.? A
Am 2006-04-21 07:07:56, schrieb Andrew Donnellan:
> Babelfish says the other email was complaining that the resolution
> should be higher and criticising the installer for being 90s-era. If
> he wanted help he could have actually asked...at least some people
> like Barry appreciate how easy it act
Re: Russ Allbery 2006-04-26 <[EMAIL PROTECTED]>
> > Must we decide on a policy? Can't Manoj just package gnus-dfsg and
> > be done with it? Is that really such a big problem?
>
> > I think not.
>
> Amen.
>
> I can understand people disagreeing with Manoj's choice, but am completely
> mystified b
On Wed, Apr 26, 2006 at 06:36:59AM -0500, David McGiven wrote:
> The newer 2.6 series kernels support configuring the TCP/UDP port number
> of the kernel lockd via the files /proc/sys/fs/nfs/nlm_tcpport and
> /proc/sys/fs/nfs/nlm_udpport.
Actually, I've been considering locking both lockd, mountd
On Apr 26, David McGiven <[EMAIL PROTECTED]> wrote:
> Having a look on /etc/init.d/nfs-common and /etc/default/nfs-common (On
> Debian Sarge) I don't find any smart way to specify those ports. It would
> be great if we had an option to specify the ports on the file :
> /etc/default/nfs-common
No,
Dear Debian Developers,
The newer 2.6 series kernels support configuring the TCP/UDP port number
of the kernel lockd via the files /proc/sys/fs/nfs/nlm_tcpport and
/proc/sys/fs/nfs/nlm_udpport.
Having a look on /etc/init.d/nfs-common and /etc/default/nfs-common (On
Debian Sarge) I don't find any
On Wed, 2006-04-26 at 12:42 +0200, Wouter Verhelst wrote:
> On Wed, Apr 26, 2006 at 11:13:32AM +0200, Luigi Gangitano wrote:
> > Squid 3 is not release ready. And with current plans should not
> > release with etch. So squid 2.5 needs to stay in unstable/testing at
> > least until etch is relea
#include
* Luigi Gangitano [Wed, Apr 26 2006, 12:21:52PM]:
> >>Squid 3 is not release ready. And with current plans should not
> >>release
> >>with etch.
> >
> >Upload to experimental, not as new source.
>
> Why not? Since I'd like to make squid3 easily available to all those
> that want to
On Wed, Apr 26, 2006 at 11:13:32AM +0200, Luigi Gangitano wrote:
> Squid 3 is not release ready. And with current plans should not
> release with etch. So squid 2.5 needs to stay in unstable/testing at
> least until etch is released and can be installed on production
> machines.
Well, then t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joerg,
Il giorno 26/apr/06, alle ore 12:06, Joerg Jaspert ha scritto:
On 10636 March 1977, Luigi Gangitano wrote:
I don't think people will install unstable on production
machines, so
don't see how that would be a problem.
Squid 3 is not relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 26/apr/06, alle ore 11:13, Christian Perrier ha scritto:
I don't think people will install unstable on production machines, so
don't see how that would be a problem.
Unstable, maybe not. Testing, well, I can bet a few beers (preferrably
On 10636 March 1977, Luigi Gangitano wrote:
>> I don't think people will install unstable on production machines, so
>> don't see how that would be a problem.
> Squid 3 is not release ready. And with current plans should not release
> with etch.
Upload to experimental, not as new source.
--
bye
> You're about to upload a separate squid3 package (to unstable) because
> you think people should continue to use squid 2.5 on production
> machines.
>
> I don't think people will install unstable on production machines, so
> don't see how that would be a problem.
Unstable, maybe not. Testing,
Il giorno 26/apr/06, alle ore 08:06, Wouter Verhelst ha scritto:
Would you really install unstable on your production machine?
No, and this is exactly my point.
Then I'm afraid I don't get your point.
You're about to upload a separate squid3 package (to unstable) because
you think people sh
* Henrique de Moraes Holschuh <[EMAIL PROTECTED]> [060425 20:45]:
> > For me a changed .orig.tar.gz means I no longer can easily verify what
> > exactly is changed. So I have to not only to download the original
>
> This is a bug. debian/copyright might be in the diff, but it still needs to
> des
On Sat, Apr 22, 2006 at 03:17:41PM +0200, Martijn van Oosterhout wrote:
> On 4/19/06, Daniel Hermann <[EMAIL PROTECTED]> wrote:
> > At the very least, could you please reopen bug #325971 so that people
> > can find out what's wrong with their server.
>
> AIUI, anybody can reopen a bug report.
>
T
Package: wnpp
Severity: wishlist
Owner: Pierre Chifflier <[EMAIL PROTECTED]>
* Package name: newpki-php
Version : 2.0.0+rc1
Upstream Author : Frederic Giudicelli <[EMAIL PROTECTED]>
* URL : http://www.newpki.org/
* License : GPL with openssl exception
Program
48 matches
Mail list logo
