If anyone is interested, I'd like to offer my perspective here as
someone who was, and still is, really quite enthusiastic about helping
Debian, but hasn't really found a way to do so yet.
Sorry, but it turned into a bit of an essay when I wasn't looking.
Let me just disclaim, too: I'm trying to
Dear friends,
I have been reading your postings to this mailing list. I have really enjoyed
reading about your perspectives on the Free/Open Source Software phenomenon.
My name is Tiebing Shi and I am a Ph.D. student at Queen's University in
Canada. I am very interested in learning more about
Hi folks,
With the upload of pam 1.0.1-11 to unstable, we've fixed a long-standing bug
in the /etc/pam.d/common-* abstractions: namely, that there was no way to
set separate system-wide policies for interactive vs. non-interactive
sessions (bug #169930).
The PAM MiniPolicy (/usr/share/doc/libpam
On lördagen den 22 augusti 2009, Aaron M. Ucko wrote:
> Magnus Holmgren writes:
> > * Self-contained, no dependencies (except libc), thanks to code
> > included from the PolarSSL project.
> >
> From a Debian perspective, that's a policy violation, not a feature!
>
> Please arrange for it to us
Hello,
(Adding debian-devel for additional comments, and previous contributors to
the topic)
As mentioned in #533265, the advice to update apt and aptitude at the
beginning of an upgrade may fail.
With a standard Etch install (i.e. only "standard" is selected in tasksel),
apt-utils and aptitude
Package: wnpp
Severity: wishlist
Owner: gregor herrmann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: libpoex-types-perl
Version : 0.091420
Upstream Author : Nicholas Perez
* URL : http://search.cpan.org/dist/POEx-Types/
* License : GPL-3
P
Package: wnpp
Severity: wishlist
Owner: Penny Leach
* Package name: dwoo
Version : 1.1.0
Upstream Author : Jordi Boggiano
* URL : http://dwoo.org
* License : Modified BSD
Programming Lang: PHP
Description : PHP5 template engine
Dwoo is a PHP5 templat
* Julien BLACHE (jbla...@debian.org) [090823 11:53]:
> Andreas Barth wrote:
> > send a mail to d-d-a with "how to do it" and a list of affected
> > packages, and then step-by-step file the appropriate bug reports
> > (only for packages which can dump their la-file).
>
> Please go ahead with that.
Andreas Barth wrote:
Hi Aba,
> send a mail to d-d-a with "how to do it" and a list of affected
> packages, and then step-by-step file the appropriate bug reports
> (only for packages which can dump their la-file).
Please go ahead with that. It's going to be much much easier to remove
the .la fi
(followup from -release, text from there is reused, so if you read
-release things are not too new for you)
Hi,
from time to time we have "funny" RC bugs thanks to dependencies
hidden in .la-files. Also these files lead to unneeded dependencies
between packages (in the case package A needs lib B
10 matches
Mail list logo
