On Fri, 2008-07-04 at 08:33 +0200, Tollef Fog Heen wrote:
> * Neil Williams
>
> | Just a thought - why use /usr/lib/$ARCH and /usr/include/$ARCH at all
> | when it would (IMHO) be simpler to use /usr/$TRIPLET/ and put the entire
> | package under that, as we do with dpkg-cross currently:
>
> How
On Fri, 04 Jul 2008, Ben Finney wrote:
> [Followup on debian-devel, instead of debian-devel-announce. Raphael,
> did you intentionally set Mail-Followup-To to debian-devel-announce or
> was that an oversight?]
Well, mutt adds it automatically as I have it configured to recognize all
debian-* as ma
* Neil Williams
| Just a thought - why use /usr/lib/$ARCH and /usr/include/$ARCH at all
| when it would (IMHO) be simpler to use /usr/$TRIPLET/ and put the entire
| package under that, as we do with dpkg-cross currently:
How would you then handle libraries that go in /lib? (Apart from the
fact
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 497 (new: 4)
Total number of packages offered up for adoption: 110 (new: 2)
Total number of packages request
On Tue, 2008-07-01 at 18:44 +0200, Goswin von Brederlow wrote:
> James Vega <[EMAIL PROTECTED]> writes:
>
> > On Sat, Jun 28, 2008 at 02:03:05AM -0700, Steve Langasek wrote:
> >> So if we allow multiple packages to be installed at the same time which
> >> divert the same file, then I think we have
On Fri, Jul 4, 2008 at 11:05 AM, Ryan Kavanagh <[EMAIL PROTECTED]> wrote:
> * Package name: password
> Description : Compact ruby random password generator
>
> Little random password generator which generates a random
> password which is strong, safe and secure.
pwgen already exists.
Al
[Followup on debian-devel, instead of debian-devel-announce. Raphael,
did you intentionally set Mail-Followup-To to debian-devel-announce or
was that an oversight?]
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> Advice on quilt usage and compatibility with new source format
Thanks very much for t
Ryan Kavanagh <[EMAIL PROTECTED]> writes:
> Package: wnpp
> Severity: wishlist
> Owner: Ryan Kavanagh <[EMAIL PROTECTED]>
>
> * Package name: password
That's a very generic package name and should probably say *something*
about how it's a random password generator.
> Version : 2007
Package: wnpp
Severity: wishlist
Owner: Ryan Kavanagh <[EMAIL PROTECTED]>
* Package name: password
Version : 2007.12.30
Upstream Author : Joakim Olsson <[EMAIL PROTECTED]>
* URL : http://lirhost.net/~jocke/password/
* License : GPL
Programming Lang: Ruby
De
El Jueves, 3 de Julio de 2008, Raphael Hertzog escribió:
> I'm reluctant to change the default behaviour of start-stop-daemon at this
> point. What do other people think of making --oknodo the default behaviour
> and adding a new option to force the current default behaviour (exit with
> failure i
On Fri, Jul 4, 2008 at 6:17 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> This is why I suggested to integrate liblocale-gettext-perl in perl-base
> itself. This would be the simplest/nicest solution IMO. It would always be
> synchronized with the current perl.
>
> See http://bugs.debian.org/cgi
Hola,
Somos un grupo de ingenieros que hemos puesto en marcha el primer
buscador libre de boletines oficiales.
Simplemente por si pensais que puede ser de interés y quereis colaborar
poniendo un link a www.iboof.com en vuestra página.
Saludos cordiales,
Ana Gil Barrenechea
Ingenier
Andreas Tille dijo [Thu, Jul 03, 2008 at 09:24:32AM +0200]:
> >I haven't been following trigger adoption very much, so I'm ignorant:
> >what harm have triggers done?
>
> It slows down apt-get / aptitude by calling update-menus / update-mandb
> for every package that drops a file into this director
Raphael Hertzog wrote:
> On Thu, 03 Jul 2008, Bryan Donlan wrote:
>> On Thu, Jul 3, 2008 at 6:25 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
>>> Package: release-notes
>>> Severity: important
>>>
>>> To work-around a problem that can happen in the perl 5.10 upgrade (see
>>> #479711), the perl sc
On Thu, 03 Jul 2008, Ian Jackson wrote:
> Here is a summary of the problem:
FWIW, the summary is right according to my understanding.
> * This problem is clearly release critical. I don't think documenting
> a release critical bug of this severity in the release notes is
> acceptable. Furth
On Thu, 03 Jul 2008, Bryan Donlan wrote:
> On Thu, Jul 3, 2008 at 6:25 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> > Package: release-notes
> > Severity: important
> >
> > To work-around a problem that can happen in the perl 5.10 upgrade (see
> > #479711), the perl scripts contained in dpkg (u
(Cc -devel to seek input)
On Thu, 31 May 2007, Iñaki Baz Castillo wrote:
> Acording to the LSB specifications for init scripts [1]:
>
> "For all other init-script actions, the init script shall return an exit
> status of zero if the action was successful. Otherwise, the exit status
> shall be non
* Bernd Eckenfels <[EMAIL PROTECTED]> [080703 09:57]:
> In article <[EMAIL PROTECTED]> you wrote:
> > The Debian maintainer for a specific VPN decides it does not need
> > special shutdown handling
>
> Nono, thats not my point. My point is, that a maintainer of any package
> cannot easyly forsee w
On Thu, 03 Jul 2008, Ian Jackson wrote:
> * Suppressing lazy symbol resolution may work in this case, but it
> is not correct.
Lazy symbol resolution should be supressed while in eval regardless of
the method which we use to resolve this problem. Non-recoverable
failures from code in eval should
Raphael Hertzog writes ("Bug#489132: lenny release notes, upgrade dpkg first"):
> To work-around a problem that can happen in the perl 5.10 upgrade (see
> #479711), the perl scripts contained in dpkg (update-alternatives,
> dpkg-divert) have been modified... but for the work-around to be used, the
Hi,
On Thursday 03 July 2008 12:25, Raphael Hertzog wrote:
> Given that the new dpkg also supports triggers, we should probably also
> recommend to upgrade apt/aptitude at the same time otherwise those tools
> might be confused by the new package status...
#464559 (in apt) is also a problem for e
Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: bzr-git
Version : 0.0.1
Upstream Author : David Allouche <[EMAIL PROTECTED]>
Aaron Bentley <[EMAIL PROT
Hello,
I found this when trying to solve #369386. There seems to be a problem
when trying to go from two conflicting packages to a dummy package and
the prefered one:
Before:
Package: lynx
Version: 2.8.6-2.1
Conflicts: lynx-cur
Package: lynx-cur
Version: 2.8.7dev9-1
Conflicts: lynx
After:
Packa
Package: wnpp
Severity: wishlist
Owner: Florian Grandel <[EMAIL PROTECTED]>
* Package name: jaranalyzer
Version : 1.2
Upstream Author : Kirk Knoernschild <[EMAIL PROTECTED]> (remove the _filter)
* URL : http://www.kirkk.com/main/Main/JarAnalyzer
* License : non
Ben Finney writes:
> I'd advise the name "mnemosyne-weblog" which is slightly less
> jargonny.
Hmm. While I don't want to dismiss this out of hand, I feel much more
natural saying "blog" myself. As a crude approximation of current usage,
here are the current numbers of google hits for:
"weblog
In article <[EMAIL PROTECTED]> you wrote:
> The Debian maintainer for a specific VPN decides it does not need
> special shutdown handling
Nono, thats not my point. My point is, that a maintainer of any package
cannot easyly forsee which part of the system he is using (resolver, pam,
proxy, ..) mig
Package: wnpp
Severity: wishlist
Owner: Edi Stojicevic <[EMAIL PROTECTED]>
* Package name: libgit-fastexport-perl
Version : 0.01
Upstream Author : Philippe 'Book' Bruat <[EMAIL PROTECTED]>
* URL :
http://search.cpan.org/dist/Git-FastExport-0.01/lib/Git/FastExport.pm
* Simon Josefsson:
>> Suppose that a package wants to create a UNIX domain socket as part of
>> its test suite. If the socket is created within the package build
>> directory, this might fail because of the quite low path name length
>> limit. What is the correct way of dealing with this? "mkte
Florian Weimer <[EMAIL PROTECTED]> writes:
> Suppose that a package wants to create a UNIX domain socket as part of
> its test suite. If the socket is created within the package build
> directory, this might fail because of the quite low path name length
> limit. What is the correct way of deali
Suppose that a package wants to create a UNIX domain socket as part of
its test suite. If the socket is created within the package build
directory, this might fail because of the quite low path name length
limit. What is the correct way of dealing with this? "mktemp -d" uses
TMPDIR, which is pot
Package: release-notes
Severity: important
To work-around a problem that can happen in the perl 5.10 upgrade (see
#479711), the perl scripts contained in dpkg (update-alternatives,
dpkg-divert) have been modified... but for the work-around to be used, the
new dpkg must obviously be installed first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2008-07-03 08:58, Lars Wirzenius wrote:
> For unarchiving and un-closing, use the control bot
> ([EMAIL PROTECTED]).
I didn't know about the 'unarchive' command.
Thanks, everything is fine now!
Johannes
-BEGIN PGP SIGNATURE-
Version: GnuP
On Thu, 3 Jul 2008, Lars Wirzenius wrote:
to, 2008-07-03 kello 08:24 +0200, Andreas Tille kirjoitti:
/me as a completely uneducated apt / aptitude user thinks: Triggers have
done more harm than good.
I haven't been following trigger adoption very much, so I'm ignorant:
what harm have triggers
On Wed, Jul 02, 2008 at 04:36:56PM -0400, Joe Smith wrote:
>> Either I don't understand the usage scenario you are talking about, or I
>> misunderstand what is being proposed in this thread, or you
>> misunderstand what is being proposed in this thread. Here is a more
>> concrete example of a sit
34 matches
Mail list logo
