Re: Debian acronymns
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
Re: A policy on use of AI-generated content in Debian
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 Policy asks for. There is a popular old opinion unrelated to AI that there is not. -- WBR, wRAR signature.asc Description: PGP signature
Re: Looking for SHA256SUMS for Debian 12
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 "27DE B156 44C6 > B3CF 3BD7 D291 300F 846B A25B AE09" > or. > gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-key A25BAE09 > gpg --list-key --with-fingerprint A25BAE09 > > How can I get the signing key for "debian-12.5.0-amd64-netinst.iso"? This is answered on https://www.debian.org/CD/verify , linked from the same page you were given. -- WBR, wRAR signature.asc Description: PGP signature
Re: Have we considered a codename 'rolling' for testing before?
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/ReleaseProposals, are about making some actual workflow changes. But if your proposal implies telling end users to use testing that's mostly https://wiki.debian.org/DropStableJustUseTesting. > They do have a point, consider it a canary in the coal mine for other > projects not recommending Debian. If the perception of the wording > 'testing' is scaring away many that would be open to a rolling version of > Debian. It's by design. Testing has several quite specific problems, at least some of which directly impact end users. While the Debian release process requires that at least some people use testing, it also implies that end users shouldn't use testing and it requires that testing behaves differently from a rolling distro. There were proposals in the past, some even doing some actual work, to make testing more useful for end users, and that's quite different from simply renaming it. > 3. Motivation Behind the Proposal: > * Enhanced Clarity and Appeal: The codename/label “Debian Rolling” is > intended to provide clearer insight into the nature of the Testing branch > for those unfamiliar with Debian's development cycle, potentially > attracting users interested in a blend of stability and freshness in > software. That reduces clarity because that's not the nature of the Testing branch. Are you maybe also unfamiliar with Debian's development cycle? > 4. Alternative: Maybe just clearly stating that debian testing is used as a > 'rolling release' It is not.
Re: Lack of replies
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 a complete crap-shot > > whether I'll even receive a comment on any code contribution (including > > debian-devel RFS, salsa MR, or BTS patch). > > For salsa and BTS, one reason for lack of reply can be that the maintainer is > never notified. I get surprised sometimes that salsa has merge requests > waiting for me. I suspect that either the email notification is broken or > off > by default and I never saw instructions to enable it. It is off by default unless that was changed recently-ish. > In the case of the BTS: it used to email me but that broke a couple years ago > and apparently it is hard to fix. So currently a class of us don't get email > from any bug reports. What is that class?
Re: Community renewal and project obsolescence
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 I'll even receive a > comment on > any code contribution (including debian-devel RFS, salsa MR, or BTS patch). There are multiple reasons for that, some common to all of these, some specific to some contribution types, but all ultimately boil down to other people being volunteers. There is no direct way to improve this beyond magically increasing the total amount of time spent by maintainers on Debian work. Some processes or tools could be improved but I'm not sure how much would that help. > If there were a single thing that could be done, in my mind it would be to > have someone > make sure that contributions do not go entirely ignored. Even just telling > someone "hey, > none of the stuff you're submitting is really good enough for Debian" would > be helpful > because they could either work on improving, or stop trying to contribute. There is no polite way to tell that, but also it's not a big problem for the project if somebody who submits very bad RFSes gets those RFSes ignored instead of being told to stop waiting for feedback on them. Giving constructive feedback, on the other hand, can be very time-draining, especially to first-time contributors submitting poor quality things. This is not even specific to Debian but applies to any open source maintainer work.
Re: Community renewal and project obsolescence
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 debian-devel RFS, salsa MR, or BTS patch). > > This is also my experience. > > A related question I've been pondering: did salsa make this worse for new > contributors because some maintainers (seem to) ignore issues/MRs there? Maybe, but also salsa MRs being ignored by default was an intentional decision AFAIK, both a technical decision of not notifying maintainers about created MRs and a policy decision of the BTS being the only officially promoted way to contact maintainers and submit patches. I have no idea if people are actually told that before they submit MRs. > I figure for the many people coming from GH style platforms nowerdays being > ignored on salsa would be a major discouragment to contributing. Well, salsa didn't make this worse, it just added something that can be ignored. > > If there were a single thing that could be done, in my mind it would be > > to have someone make sure that contributions do not go entirely ignored. > > I've been thinking along those lines too. Perhaps we just need an > aggregator that flags mails/comments/other contributions by new people that > are being ignored. You'll still need people to provide feedback.
Re: Aw: Debian 12 vs MySql WOrkbench
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 depends on is > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040290 > and it is already fixed for several months, just apparently the maintainers > did not get around to reupload a fixed version. (the user asked about Debian 12 which is stable)
Re: [Confirmation request] Regarding EOS/EOL of Debian OS (as of October 2023)
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/Linux 9(64bit) > > In addition, in accordance with our internal regulations, we will continue to > periodically update EOS/EOL information. > We need to take inventory. > If there is any information posted on the official website that you can refer > to at that time. > In the future, we will refer to them instead of making inquiries. > We apologize for the inconvenience, but if you know of such a site, could you > please introduce it to us? Please read https://wiki.debian.org/LTS and https://wiki.debian.org/LTS/Extended
Re: Don`t upgrade pip
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 they release a version with a conforming version number. Discussion > can be found at https://github.com/pypa/pip/issues/12063 > WARNING: There was an error checking the latest version of pip. Does this message cause any actual problems?
Re: Will nala be in software soon?
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
Re: Become Debian Contributor
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.debian.org/intro/help
Re: Libc6 Usage Question
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.
Re: Libc6 Usage Question
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 project fails to > run, due to Debian not having a libc6 version as low as GLibC 2.32. If you want to support running on stable consider building on stable. You may want to consult Github actions documentation to see if it's possible and how to do that. Please also note that the user support list is debian-user@. > I've > tried to compile my project to musl, statically, and even just embedding > the correct version of libc6 in the lib folder that I set my rpath to. I've > either had segfaults or failed builds. I would like to ask how I can either > support an older version of libc6 or upgrade any customers' systems to the > correct version. I'd also happily accept not requiring libc6 at all. Out of all of these options building on an older system sounds the best and the easiest.
