Hi
On Wed, Jun 19, 2024 at 11:18:36AM -0700, Russ Allbery wrote:
> > Other ideas like waldi's 3.0 (gitarchive) also go in that direction.
>
> Similarly, I'm not sure a source package based on Git avoids the need for
> a source package build system. There are a ton of ways that maintainers
> stor
Hi
On Sat, Jun 15, 2024 at 11:03:17AM +0200, Philip Hands wrote:
> If Ian were to offer a hosting service for such personal tag2upload
> instances, in a way that he assured me could not be used to sign
> packages unless I had signed a matching git-tag, I would be willing to
> trust his assurances,
On Wed, Jun 12, 2024 at 04:23:29PM +0100, Simon McVittie wrote:
> On Wed, 12 Jun 2024 at 15:20:45 +0100, Ian Jackson wrote:
> > tag2upload, like dgit, ensures and insists that the git tree you are
> > uploading corresponds precisely [1] to the generated source package.
> >
> > If you base your Deb
On Wed, Jun 12, 2024 at 08:59:46AM +0200, Holger Levsen wrote:
> Am Tue, Jun 11, 2024 at 10:27:56PM -0700 schrieb Russ Allbery:
> > > As I said several times before: the implementation has known security
> > > bugs (unless you fixed them). But I guess this is going to get ignored
> > > again anyway
On Tue, Aug 30, 2022 at 05:05:35PM -0400, Antoine Beaupré wrote:
> Didn't we have buster/updates for a while? Is breakage related to that
> the reason why we're not doing this here?
We didn't have "buster" and "buster/updates" in the same place. And
less "buster/updates" being a subset of "buster
Hi
On Tue, Aug 30, 2022 at 03:11:25PM -0500, Richard Laager wrote:
> DSC 1 says we will never "require the use of a non-free component". To me,
> this is the major relevant issue.
Nothing in Debian requires any non-free component. Require would be:
can't be used without, which clearly is not tru
Moin
On Wed, Aug 24, 2022 at 11:05:21AM +0200, Thomas Goirand wrote:
> My recent experience with servers (10 and 25 Gbits/s dual port SFP+) is that
> you need firmware for network cards when running with:
> - Broadcom (bnx2 / bnx2x)
> - Qlogic
> - Intel (they partially work without the firmware-mi
On Tue, Aug 23, 2022 at 11:20:09PM +0200, Bart Martens wrote:
> It would be nice to have both installers presented on the front page, so users
> can choose. I have no strong opinion on whether the "plus" installer would be
> called official or not.
While we are at it, can you please propose a word
On Thu, Nov 11, 2021 at 02:23:58PM -0500, Daniel Kahn Gillmor wrote:
> I'm legitimately surprised to hear that anyone in the Debian project
> believes that the term "FTP master" is *not* confused and outdated.
I'm really surprised that ftp master is more important than the weird
definition of DD a
On Sat, Sep 11, 2021 at 06:18:16AM +, Paul Wise wrote:
> On Fri, Sep 10, 2021 at 2:44 PM Felix Lechner wrote:
> > A fellow developer and I have reached an impasse over the appropriate
> > level of privacy guarantees in Debian. [1]
> I think that lintian privacy tags currently represent several
Hi Brian
On Fri, Nov 15, 2019 at 01:10:58AM -0500, Brian Gupta wrote:
> Do you think it's ok in any case to remove init scripts. Let's say an
> upstream stops maintaining init scripts,
I would like to know if this is a real world problem. Please provide an
example of a package where the init scr
On Wed, Aug 06, 2014 at 03:53:09AM +0200, Jan Sechser wrote:
> can you plz remove me from the list thanks
Please do that yourself. For more information read the footer on
_every_ mail; I'll quote one for you:
> To UNSUBSCRIBE, email to debian-vote-requ...@lists.debian.org
> with a subject of "un
On Sun, Dec 28, 2008 at 08:45:16PM -0500, Theodore Tso wrote:
> If there was a GR which chainged the Debian Social contract which
> relaxed the first clause to only include __software__ running on the
> Host CPU, I would enthusiastically vote for such a measure.
I doubt that this a usable definiti
On Mon, Oct 27, 2008 at 10:35:23AM +, Neil McGovern wrote:
> --
> - Following the announcement of the 22nd of October on the
> debian-devel-announce
>mailing list (Message-id: <[EMAIL PROTECTED]>) about "Developer
>Status
On Fri, Oct 24, 2008 at 09:15:43PM +0900, Charles Plessy wrote:
> The Debian Project, by the way of a general resolution of its developpers,
> decides:
>
> - The changes announced the 22nd of October on the debian-devel-announce
>mailing list (Message-id: <[EMAIL PROTECTED]>) are suspended.
I second the following proposal.
> === START OF PROPOSAL ===
> Definition: For the purpose of this resolution, the "firmware" mentioned below
> designates binary data included in some of the linux kernel drivers, usually
> as
> hex-encoded variables and whose purpose is to be loaded into a given
On Wed, Sep 27, 2006 at 12:36:56PM -0500, Manoj Srivastava wrote:
> ,
> | 1. We affirm that our Priorities are our users and the free software
> | community (Social Contract #4);
> | 2. We acknowledge that there is a lot of progress in the kernel
> | firmware issue; however, it is not
On Fri, Sep 22, 2006 at 09:11:02PM +0200, Frederik Schueler wrote:
> On Fri, Sep 22, 2006 at 10:45:34AM -0500, Manoj Srivastava wrote:
> > come to an agreement about what exactly in that email
> > constitutes the actual general resolution?
I second the following GR.
-BEGIN PGP SIGNE
Seconded.
On Wed, Aug 30, 2006 at 11:06:54PM +0200, Frederik Schueler wrote:
> Overview:
>
> The Linux kernel source contains device drivers that ship with firmware
> files provided by the hardware manufacturer. They are uploaded during
> the driver initialization to the corresponding hardware d
19 matches
Mail list logo
