On Thu, Aug 08, 2024 at 05:27:30PM +, kent.t.pine...@lmco.com wrote:
> I found this license referenced on the License information at
> https://www.debian.org/legal/licenses/
This list doesn't seem relevant for anything. The page as a whole doesn't
either, at least in the current state (it say
On Mon, May 06, 2024 at 04:52:05PM -0300, Jack Warkentin wrote:
> That's great. But how is anyone going to find it?
Google.
E.g. "Debian acronyms" points to it.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Fri, May 03, 2024 at 01:04:29PM +0900, Charles Plessy wrote:
> If I would hear that other Debian developers use them in that context, I
> would seriously question whether there is any value to spend my
> volunteer time in keeping debian/copyright files accurate to the level
> of details our Poli
On Tue, Apr 16, 2024 at 11:35:11AM +0200, Jens Hermann wrote:
> Dear Sir or Madam,
>
> Thank you very for your answers.
>
> I have another question about verification.
> On Linux there is the following command to import the signing key:
> gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-key "
On Sun, Feb 11, 2024 at 04:39:50PM +, Martin Stadtler wrote:
> Hi All,
>
> I am certain this has come up in the past, but have we considered adding
> the codename/label rolling to testing?
Hard to say, as things that are usually proposed, like ones listed on
https://wiki.debian.org/ReleaseProp
On Fri, Dec 29, 2023 at 02:18:41PM -0600, Steven Robbins wrote:
> Antonio Russo wrote:
>
> > As someone who would like to participate more in the development of Debian,
> > my personal experience is that making contributions is like dropping a
> > message in a bottle into the sea. It feels like
On Fri, Dec 29, 2023 at 08:48:28AM -0800, Antonio Russo wrote:
> As someone who would like to participate more in the development of Debian,
> my personal
> experience is that making contributions is like dropping a message in a
> bottle into
> the sea. It feels like a complete crap-shot whether
On Fri, Dec 29, 2023 at 06:49:47PM +0100, Daniel Gröber wrote:
> > [...] my personal experience is that making contributions is like
> > dropping a message in a bottle into the sea. It feels like a complete
> > crap-shot whether I'll even receive a comment on any code contribution
> > (including d
On Tue, Nov 21, 2023 at 11:35:46AM +0100, Steffen Möller wrote:
> Hi Allan,
>
> The status of the package is described on
> https://tracker.debian.org/pkg/mysql-workbench
>
> and you see it is waiting for another package to transition to testing, so it
> can migrate itself.
>
> The bug it depen
On Wed, Oct 18, 2023 at 01:00:00PM +, endo.hirofumi wrote:
> This is the main topic, but please check the EOS and EOL of the following
> products provided by your project.
> Could you please give me some guidance?
> *If it has not been published, please reply to that effect.
>
>
> Debian GNU
On Mon, Oct 16, 2023 at 12:16:24PM +0400, Леонид Сергеевич wrote:
> DEPRECATION: reportbug 7.5.3-deb10u1 has a non-standard version number. pip
> 24.0 will enforce this behaviour change. A possible replacement is to
> upgrade to a newer version of reportbug or contact the author to suggest
> that t
On Thu, Oct 12, 2023 at 07:09:00AM -0400, Steven Friedrich wrote:
> Nala is a github project that is a new front-end for apt. I am hoping it
> will soon be available in debian12 stable tree.
Debian 12 includes nala: https://packages.debian.org/stable/nala
On Fri, Jul 14, 2023 at 01:27:12PM +0330, Zareh K wrote:
> Hi
> Dears I'm a Linux user with around 12 years of experience in using Dbian
> based OS.
> I'm not a developer but I'm keen to help debian project by anyway.
> Is there anyone could help me to join any team.
Please look at https://www.deb
On Tue, Apr 25, 2023 at 10:24:35PM -0400, Alexis E wrote:
> I discovered there are more lists than just this one, so I'll be forwarding
> the email to the appropriate list (which I believe to be
> debian-gl...@lists.debian.org).
Definitely not that one.
On Tue, Apr 25, 2023 at 06:29:11PM -0400, Alexis E wrote:
> Dear Debian Mailing List,
> I am working on a project which requires libc6. When I build this
> project on my laptop, the project works fine as it builds for the libc6 on
> my laptop, however, when I build it in Github actions, the pro
15 matches
Mail list logo