On 4/5/24 10:30, Pierre-Elliott Bécue wrote:
Pierre-Elliott Bécue wrote on 31/03/2024 at 14:31:37+0200:
Wookey wrote on 31/03/2024 at 04:34:00+0200:
On 2024-03-30 20:52 +0100, Ansgar 🙀 wrote:
Yubikeys, Nitrokeys, GNUK, OpenPGP smartcards and similar devices.
Possibly also TPM modules in com
On 6/3/20 7:30 PM, Gunnar Wolf wrote:
Like Paul said in his reply, I also have a "bash monstrosity" as a
Bash prompt.
For many years, I have taken a different approach; use the default and
add only a few minor changes. Each stable update, I use
/etc/skel/.bashrc and edit/add in my little bits
On 04/09/2018 05:34 PM, Sebastian Andrzej Siewior wrote:
> On 2018-04-09 15:55:14 [-0500], Michael Shuler wrote:
>> It was purely a conservative duplication of existing symlinks. I can
>> drop the old md5 symlinks, if there's a consensus that they are no
>> longer neede
On 04/09/2018 03:21 PM, Sebastian Andrzej Siewior wrote:
> On 2018-04-06 10:05:35 [-0500], Michael Shuler wrote:
>> If you could go ahead and file this bug for ca-certificates, I'd like to
>> include the bug number in the changelog for this commit on the next
>> up
ntly does) but as
> explained above it should not be required to use it.
>
> I am planning to fill bugs against 23 packages which use "c_rehash" to
> use "openssl rehash" instead. Here is the dd-list of packages I
> identified:
<...>
> Michael Shuler
On 11/05/2014 06:51 AM, Noël Köthe wrote:
Hello Debian,;)
wget developers are working on CRL support and raised the following
questions which somebody of you guys have a better answer:
Am Mittwoch, den 05.11.2014, 12:48 +0100 schrieb Tim Ruehsen:
BTW, does Debian meanwhile has a CRL infrastru
On 04/02/2014 04:43 AM, Bas van den Dikkenberg wrote:
The only things states in RDL that user has to be informed about the copyright
I find this, perhaps, the most interesting and on-topic comment in this
thread.
--
Kind regards,
Michael
--
To UNSUBSCRIBE, email to debian-devel-requ...@lis
On 02/08/2014 05:55 AM, Andreas Beckmann wrote:
On 2014-02-08 10:01, Tzafrir Cohen wrote:
On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
Is there a policy on how to package software that does not make releases?
A version
On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
Is there a policy on how to package software that does not make releases?
A version similar to skia_0.0-1~svnr1234 would allow an upstream version
of i.e. 0.1 (if they ever release) to supersede your packaged version.
It should also allow you
as
removed from the archive post-squeeze, and if it may be suitable for
debian in the future.
[0] http://packages.debian.org/search?keywords=mailscanner
[1] http://packages.qa.debian.org/m/mailscanner.html
[2]
http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=mailscanner
--
Kind regards,
On 07/26/2012 08:37 AM, The Fungi wrote:
> On 2012-07-26 14:29:14 +0100 (+0100), Ian Jackson wrote:
> [...]
>> We also need a general word for "someone involved with Debian in a
>> positive way". "Participant" is clumsy; "member of the community"
>> even more so. "Person" might do but word with a m
On 12/13/2011 09:17 AM, Simon Josefsson wrote:
> Possibly DEP5-compliant files could be generated from SPDX files.
This has come up in several DEP5 discussions over the past ~year, as
well as several recent mentions:
https://www.google.com/search?q=spdx+site%3Alists.debian.org
--
Kind regards,
On 08/22/2011 10:56 PM, Russ Allbery wrote:
> Charles Plessy writes:
>
>> as per /usr/share/doc/ca-certificates/README.Debian, I am looking for
>> additional signed recommendations for the addition of the Amazon Elastic
>> Computer Cloud (EC2) public certificate to the ca-certificates packages.
>
On 07/06/2011 08:52 PM, Aaron Toponce wrote:
> I would like to mimic the build process of the chromium-browser as closely
> as possible on a development system, but I am unaware of the process that
> the Debian Chromium Package Maintainers use. I'm not as interested as
> building the .deb, as I am
Package: wnpp
Severity: wishlist
Owner: Michael Shuler
Package name: python-cloudfiles
Version : 1.4.0
Upstream Author : Cloud Files
URL : http://github.com/rackspace/python-cloudfiles/
License : MIT
Programming Lang: Python
Description : Python
Package: wnpp
Severity: wishlist
Owner: Michael Shuler
* Package name: libnet-mosso-cloudfiles-perl
Version : 0.43
Upstream Author : Léon Brocard
* URL : http://search.cpan.org/dist/Net-Mosso-CloudFiles/
* License : Perl (Artistic and GPL)
Programming Lang
On 06/09/2009 02:59 PM, David Claughton wrote:
> Michael Shuler wrote:
>> On 06/09/2009 11:49 AM, Andreas wrote:
>>> Installing it (make), it downloads the binary of the hypervisor!
>>> "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " #
>
On 06/09/2009 11:49 AM, Andreas wrote:
> Installing it (make), it downloads the binary of the hypervisor!
> "Cloning http://xenbits.xensource.com/linux-2.6.18-xen.hg " #
> (downloading)
This is an incorrect understanding of that download step - it is a
*source* download from the upstream merc
to try to recreate
the problem - it's all just 1's and 0's ;)
--
Kind Regards,
Michael Shuler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
night with pbuilder on my SunFire V120.
--
Kind Regards,
Michael Shuler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 11/30/2007 11:51 AM, Milan P. Stanic wrote:
> Are you sure that the complete package is in the public domain?
> Some files are, but not all of them, AFAIK.
There has been some additional discussion on this topic in BTS, as well
as some other places.
http://bugs.debian.org/453680
http://linux.s
21 matches
Mail list logo
