Re: Debian 10 "buster" moved to archive.debian.org

2024-05-27 Thread Leandro Cunha
Hi, On Fri, May 24, 2024 at 10:28 PM Otto Kekäläinen wrote: > > Hi! > > So just to clarify, are you saying that a copy of > https://security.debian.org/debian-security/dists/buster/ will never > be archived at https://archive.debian.org/debian-security/dists/ like > previous releases have been

Re: Debian 10 "buster" moved to archive.debian.org

2024-05-24 Thread Otto Kekäläinen
Hi! So just to clarify, are you saying that a copy of https://security.debian.org/debian-security/dists/buster/ will never be archived at https://archive.debian.org/debian-security/dists/ like previous releases have been so far? This is not about getting *new security updates*, but purely a

Re: Debian 10 "buster" moved to archive.debian.org

2024-05-20 Thread Leandro Cunha
Hi Otto, In Buster's case, it would be becoming an ELTS soon and would have to use Freexian's repositories. It would no longer be the security team with DLAs that would take care of CVEs for ELTS, but the Frexian team. So much so that if I look at the links below I didn't find anything (about

Re: Debian 10 "buster" moved to archive.debian.org

2024-05-20 Thread Otto Kekäläinen
On Sat, 23 Mar 2024 at 01:32, Ansgar  wrote: > > Hi, > > Debian 10 "buster" has moved to archive.debian.org in order to free > space on the main mirror network. We plan to start removing files for > non-LTS architectures in about two weeks; the existing Release files > will then refer to no

Re: debian-policy: clarify requirement for use of Static-Built-Using

2024-04-23 Thread Fabian Grünbichler
On Fri, Apr 19, 2024 at 07:59:19AM +0100, Sean Whitton wrote: > Hello Go and Rust packagers, > > On Thu 18 Apr 2024 at 11:29pm +03, Maytham Alsudany wrote: > > > With the increasing amount of programs in Debian that Build-Depend and > > statically link with Golang and Rust libraries, it's

Re: Debian

2024-04-19 Thread José Luis González González
On Fri, 19 Apr 2024 10:09:26 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:59:57 +0200 > José Luis González González wrote: > > > On Fri, 19 Apr 2024 09:39:02 +0200 > > José Luis González González wrote: > > > > > Good day, > > > > > > There's an issue with the dash

Re: Debian

2024-04-19 Thread Steve McIntyre
You've written a lot of text here in a few mails, replying to yourself several times. This is not a positive pattern. On Fri, Apr 19, 2024 at 11:58:18AM +0200, José Luis González González wrote: >> There are similar issues with boa and dhttpd, and it seems Apache is going >> that way. > >nvi

Re: Debian

2024-04-19 Thread José Luis González González
On Fri, 19 Apr 2024 10:09:26 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:59:57 +0200 > José Luis González González wrote: > > > On Fri, 19 Apr 2024 09:39:02 +0200 > > José Luis González González wrote: > > > > > Good day, > > > > > > There's an issue with the dash

Re: Debian

2024-04-19 Thread José Luis González González
On Fri, 19 Apr 2024 09:59:57 +0200 José Luis González González wrote: > On Fri, 19 Apr 2024 09:39:02 +0200 > José Luis González González wrote: > > > Good day, > > > > There's an issue with the dash package and maintainer, and mutt as well. > > > > I even tried to reach dash maintainer

Re: debian-policy: clarify requirement for use of Static-Built-Using

2024-04-19 Thread Sean Whitton
Hello Go and Rust packagers, On Thu 18 Apr 2024 at 11:29pm +03, Maytham Alsudany wrote: > With the increasing amount of programs in Debian that Build-Depend and > statically link with Golang and Rust libraries, it's important that > the Debian Policy clearly sets out the requirements for

Re: Debian Policy 4.7.0.0 released

2024-04-12 Thread Pierre-Elliott Bécue
Please do it yourself by following the instructions here: https://lists.debian.org/debian-devel/ Maycon Antônio wrote on 08/04/2024 at 17:44:20+0200: > Please cancel my name from this list, thank you. > > On Sun, 7 Apr 2024 at 12:32, Sean Whitton wrote: >> >> Hello everyone, >> >> I just

Re: Debian Policy 4.7.0.0 released

2024-04-08 Thread Maycon Antônio
Please cancel my name from this list, thank you. On Sun, 7 Apr 2024 at 12:32, Sean Whitton wrote: > > Hello everyone, > > I just pushed version 4.7.0.0 of the Debian Policy Manual and related > documents to sid. Below you will find the significant normative changes > from the

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-07 Thread Marco d'Itri
On Apr 07, Bernd Zeimetz wrote: > There are more than enough ways to keep the entries based on dns > records in your l3 firewalls uptodate, I can't see how this should > warrant to keep yet another patch Jan^WMarco. Not for the form *.domain.tld. -- ciao, Marco signature.asc Description: PGP

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-07 Thread Bernd Zeimetz
On Tue, 2024-04-02 at 12:04 +0200, Marco d'Itri wrote: > On Apr 02, Colin Watson wrote: > > > At the time, denyhosts was popular, but it was removed from Debian > > several years ago.  I remember that, when I dealt with that on my > > own > > systems, fail2ban seemed like the obvious

Re: [sylpheed:37255] Re: Debian 12 released with two RC bugs in Sylpheed

2024-04-07 Thread Paul
On Sun, 7 Apr 2024 15:18:57 +0200 José Luis González wrote: > I found the report now. It's #1036799. Yes, it looks like a temporary server issue. And you're sending via gmail now. But again, what do you expect a package maintainer to do? It's upstream where bugs get fixed. Your subject is

Re: Debian 12 released with two RC bugs in Sylpheed

2024-04-07 Thread José Luis González
On Sun, 7 Apr 2024 13:26:49 +0200 José Luis González wrote: > The maintainer accumulates a lot of bugs for the package, doesn't take > care about almost all, and when I filed a RC bug because the package > became unusable to me he downgraded severity to important claiming it > was just a Gmail

Re: Debian 12 released with two RC bugs in Sylpheed

2024-04-07 Thread Sirius
In days of yore (Sun, 07 Apr 2024), José Luis González thus quoth: > Hi, > > Debian 12 was released with two Release Critical bugs I filed on May > 20th 2023 (#1036424 and #1036388) on Sylpheed about issues that I > found on stable, and remain, with Debian 12 released later on June 10th > 2023.

Re: Debian 12 released with two RC bugs in Sylpheed

2024-04-07 Thread Marco d'Itri
On Apr 07, José Luis González wrote: > I want to know why Debian 12 was released with those two Sylpheed RC > bags, report the incident to you all, know what to do with the > maintainer and kindly request that someone better at the job takes over > Sylpheed maintainance, or otherwise I will

Re: Debian Project Leader election 2024: First call for votes

2024-04-06 Thread 陳昌倬
On Sat, Apr 06, 2024 at 01:46:28AM +0200, Debian Project Secretary - Kurt Roeckx wrote: > - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=- > 9c605edd-40a5-469c-9489-cbf80ac05970 > [1] Choice 1: Andreas Tille > [2] Choice 2: Sruthi Chandran > [ ] Choice 3: None Of The

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Colin Watson
On Thu, Apr 04, 2024 at 06:42:08PM -0300, Henrique de Moraes Holschuh wrote: > If libwrap is bringing in complex libs, maybe we could reduce the > attack surface on libwrap itself? It would be nice to have a variant > that only links to the libc and that's it... Yeah, that's

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Henrique de Moraes Holschuh
On Tue, Apr 2, 2024, at 07:04, Marco d'Itri wrote: > On Apr 02, Colin Watson wrote: > >> At the time, denyhosts was popular, but it was removed from Debian >> several years ago. I remember that, when I dealt with that on my own >> systems, fail2ban seemed like the obvious replacement, and my

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Marc Haber
On Thu, 4 Apr 2024 13:25:04 +0200, Stephan Seitz wrote: >Am Di, Apr 02, 2024 at 13:30:43 +0200 schrieb Marc Haber: >>from being vulnerable to the current xz-based attack. Just having to >>dump an ALL: ALL into /etc/hosts.deny is vastly easier than having to >>maintain a packet filter. > >Stupid

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Russ Allbery
Florian Lohoff writes: > These times have long gone and tcp wrapper as a security mechanism has > lost its reliability, this is why people started moving away from tcp > wrapper (which i think is a shame) > I personally moved to nftables which is nearly as simple once you get > your muscle

ufw (was Re: Debian openssh option review: considering splitting out GSS-API key exchange)

2024-04-04 Thread Holger Levsen
On Thu, Apr 04, 2024 at 01:32:11PM +0200, Marc Haber wrote: > So you have dedicated packet filters on every machine you run, even if > sshd is the only network-facing service? on most machines and it was as simple as doing: apt install ufw ufw allow ssh ufw enable voila, done. rules configured

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Marc Haber
On Thu, 4 Apr 2024 13:03:50 +0200, Florian Lohoff wrote: >I personally moved to nftables which is nearly as simple once you get >your muscle memory set. So you have dedicated packet filters on every machine you run, even if sshd is the only network-facing service? Greetings Marc --

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Stephan Seitz
Am Di, Apr 02, 2024 at 13:30:43 +0200 schrieb Marc Haber: from being vulnerable to the current xz-based attack. Just having to dump an ALL: ALL into /etc/hosts.deny is vastly easier than having to maintain a packet filter. Stupid question, but if you put „ALL: ALL” into hosts.deny, couldn’t

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-04 Thread Florian Lohoff
On Tue, Apr 02, 2024 at 01:30:43PM +0200, Marc Haber wrote: > On Tue, 2 Apr 2024 01:30:10 +0100, Colin Watson > wrote: > >We carry a patch to restore support for TCP wrappers, which was dropped > >in OpenSSH 6.7 (October 2014); see >

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-03 Thread Colin Watson
On Wed, Apr 03, 2024 at 04:01:34PM -0400, Michael Stone wrote: > To speed things up for those who really want it, perhaps make > openssh-client/server dependency-only packages on > openssh-client/server-nogss? People can choose the less-compatible version > for this release if they want to, and

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-03 Thread Michael Stone
On Tue, Apr 02, 2024 at 01:30:10AM +0100, Colin Watson wrote: * add dependency-only packages called something like openssh-client-gsskex and openssh-server-gsskex, depending on their non-gsskex alternatives * add NEWS.Debian entry saying that people need to install these packages

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-03 Thread Colin Watson
On Wed, Apr 03, 2024 at 04:38:19PM +0200, Marc Haber wrote: > On Wed, 03 Apr 2024 14:10:37 +0100, "Jonathan Dowland" > wrote: > >For you and fellow greybeards, perhaps: I'd be surprised if many people > >younger than us have even heard of tcp wrappers. I don't think the > >muscle memory of a

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-03 Thread Marc Haber
On Wed, 03 Apr 2024 14:10:37 +0100, "Jonathan Dowland" wrote: >On Tue Apr 2, 2024 at 12:30 PM BST, Marc Haber wrote: >> Please don't drop the mechanism that saved my¹ unstable installations >> from being vulnerable to the current xz-based attack. Just having to >> dump an ALL: ALL into

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-03 Thread Jonathan Dowland
On Tue Apr 2, 2024 at 12:30 PM BST, Marc Haber wrote: > Please don't drop the mechanism that saved my¹ unstable installations > from being vulnerable to the current xz-based attack. Just having to > dump an ALL: ALL into /etc/hosts.deny is vastly easier than having to > maintain a packet filter.

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread RL
Colin Watson writes: > GSS-API key exchange > > However, OpenSSH upstream has long rejected it > All the same, I'm aware that some people now depend on having this > facility in Debian's main openssh package > How does this rough plan sound? > > * for Debian trixie

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Marc Haber
On Tue, 2 Apr 2024 01:30:10 +0100, Colin Watson wrote: >We carry a patch to restore support for TCP wrappers, which was dropped >in OpenSSH 6.7 (October 2014); see >https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-April/032497.html >and thread. That wasn't long before the Debian 8

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Colin Watson
On Tue, Apr 02, 2024 at 12:04:26PM +0200, Marco d'Itri wrote: > Yes, people. I object to removing TCP wrappers support since the patch > is tiny and it supports use cases like DNS-based ACLs which cannot be > supported by L3 firewalls. I suspect OpenSSH upstream would also want me to point out

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Marco d'Itri
On Apr 02, Colin Watson wrote: > You could use a drop-in unit to wrap sshd in tcpd, as suggested by the > Fedora wiki page? This would avoid exposing sshd's process space to > libwrap and all the stuff it links to by default. This would require to switch to socket activation of sshd, which is

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Colin Watson
On Tue, Apr 02, 2024 at 12:04:26PM +0200, Marco d'Itri wrote: > On Apr 02, Colin Watson wrote: > > At the time, denyhosts was popular, but it was removed from Debian > > several years ago. I remember that, when I dealt with that on my own > > systems, fail2ban seemed like the obvious

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Christian Göttsche
On Tue, 2 Apr 2024 at 02:30, Colin Watson wrote: > > [I've CCed openssh-unix-dev for awareness, but set Mail-Followup-To to > just debian-devel and debian-ssh to avoid potentially spamming them with > a long discussion. If you choose to override this then that's your > call, but please be

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Marco d'Itri
On Apr 02, Colin Watson wrote: > At the time, denyhosts was popular, but it was removed from Debian > several years ago. I remember that, when I dealt with that on my own > systems, fail2ban seemed like the obvious replacement, and my impression > is that it's pretty widely used nowadays; it's

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-02 Thread Colin Watson
On Tue, Apr 02, 2024 at 03:27:30AM +0200, Christoph Anton Mitterer wrote: > Do you think it will be possible to have still only one `ssh`, `scp`, > etc. command and that will just use extra GSSAPI stuff if installed and > needed by a certain connection? It would be technically possible to retain

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-01 Thread Howard Chu
Damien Miller wrote: > Another thing we're considering in OpenSSH is changing how we integrate > with PAM. PAM's API demands loading modules into the authenticating > process' address space, but obviously we've just been reminded that this > is risky. This was a long-standing problem with

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-01 Thread Sirius
In days of yore (Tue, 02 Apr 2024), Colin Watson thus quoth: > TCP wrappers > Not used hosts.{allow,deny} for the last 17 years (since I started my current employment) so I am biased. Honest opinion is that firewall and fail2ban have pretty much obsoleted TCP wrappers. > SELinux >

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-01 Thread Russ Allbery
Christoph Anton Mitterer writes: > Actually I think that most sites where I "need"/use GSSAPI... only > require the ticket for AFS, and do actually allow pubkey auth (but > right now, one doesn't have AFS access then). In past discussions of this patch, this has not been the case. One of the

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-01 Thread Christoph Anton Mitterer
Hey. On Tue, 2024-04-02 at 01:30 +0100, Colin Watson wrote: > All the same, I'm aware that some people now depend on having this > facility in Debian's main openssh package: I get enough occasional > bug > reports to convince me that it's still in use. Being one of those people, and having even

Re: Debian openssh option review: considering splitting out GSS-API key exchange

2024-04-01 Thread Damien Miller
On Tue, 2 Apr 2024, Colin Watson wrote: [I'm not subscribed to the debian-* lists, please Cc me in replies if you want me to see them] > [I've CCed openssh-unix-dev for awareness, but set Mail-Followup-To to > just debian-devel and debian-ssh to avoid potentially spamming them > with a long

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-26 Thread Andreas Metzler
On 2024-03-24 Samuel Henrique wrote: > Hello everyone, > Given our current time_t transition happening, which means packages > are blocked from migrating to testing for weeks, and that unstable > updates have become harder to apply, two critical CVE fixes for > Firefox became impossible to get

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-25 Thread Samuel Henrique
> On 24-03-2024 11:45 p.m., Samuel Henrique wrote: > > In a recent case, the issue was addressed by performing a > > testing-proposed-update of the package. This would allow firefox-esr to be > > fixed on testing before the transition is over, but it would not work for > > those > > installing

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-25 Thread Paul Gevers
Hi Samuel, On 24-03-2024 11:45 p.m., Samuel Henrique wrote: In a recent case, the issue was addressed by performing a testing-proposed-update of the package. This would allow firefox-esr to be fixed on testing before the transition is over, but it would not work for those installing the firefox

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-25 Thread Hakan Bayındır
I moved to Mozilla's official packages for the time being since I didn't want to downgrade to ESR for now. Will resume with Debian's packages when the dust settles down. On 25.03.2024 ÖÖ 8:26, Leandro Cunha wrote: Hi, On Mon, Mar 25, 2024 at 2:18 AM Paul Wise wrote: On Sun, 2024-03-24 at

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-24 Thread Leandro Cunha
Hi, On Mon, Mar 25, 2024 at 2:18 AM Paul Wise wrote: > > On Sun, 2024-03-24 at 22:45 +, Samuel Henrique wrote: > > > I'm sending this to d-devel because there should be a lot of testing and > > unstable users on this list. If you're not running firefox 124.0.1 or > > firefox-esr

Re: Debian testing/unstable users: beware of Firefox critical CVEs

2024-03-24 Thread Paul Wise
On Sun, 2024-03-24 at 22:45 +, Samuel Henrique wrote: > I'm sending this to d-devel because there should be a lot of testing and > unstable users on this list. If you're not running firefox 124.0.1 or > firefox-esr 115.9.1esr-1, you should find a way of upgrading to those > versions.

Re: [Debian-iot-maintainers] Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition

2024-02-02 Thread Carsten Schoenert
Am 01.02.24 um 09:30 schrieb Steve Langasek: What is the rationale behind rising a bug report at 9:51pm my time and firing a *direct* NMU upload just 11min later (according to the time stamps from the emails)? There are 1200+ source packages that require NMUing and the Debian archive is a

Re: [Debian-iot-maintainers] Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition

2024-02-01 Thread Steve Langasek
On Thu, Feb 01, 2024 at 07:45:57AM +0100, Carsten Schoenert wrote: > Hello Steve, > Am 31.01.24 um 21:59 schrieb Steve Langasek: > ... > > Please find the patch for this NMU attached. > > If you have any concerns about this patch, please reach out ASAP. >

Re: [Debian-iot-maintainers] Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition

2024-02-01 Thread Sune Vuorela
On 2024-02-01, Carsten Schoenert wrote: > What is the rationale behind rising a bug report at 9:51pm my time and > firing a *direct* NMU upload just 11min later (according to the time > stamps from the emails)? > I as the uploader for libcoap have no chance to do any action on this > bug

Re: [Debian-iot-maintainers] Bug#1062257: libcoap3: NMU diff for 64-bit time_t transition

2024-01-31 Thread Carsten Schoenert
Hello Steve, Am 31.01.24 um 21:59 schrieb Steve Langasek: ... Please find the patch for this NMU attached. If you have any concerns about this patch, please reach out ASAP. ^^ Although this package will be uploaded to

Re: Debian-devel

2023-11-17 Thread Kimberly Lane
Debian-devel, it's my new email.

Re: debian/copyright format and SPDX

2023-09-25 Thread Stephan Lachnit
On Mon, Sep 25, 2023 at 7:15 AM Steve Langasek wrote: > > So can you tell me where in that specification this "flat text file" format > is actually described? The specification is not on the page that includes > this quote. The text does not link to the place in the spec where this > format is

Re: debian/copyright format and SPDX

2023-09-24 Thread Steve Langasek
On Fri, Sep 22, 2023 at 12:58:10PM +0200, Stephan Lachnit wrote: > On Fri, Sep 22, 2023 at 11:11 AM Steve Langasek wrote: > > SPDX defines an xml format only. They lost before they'd even started. > > debian/copyright is supposed to be human-readable first and foremost. XML > > need not

Re: debian/copyright format and SPDX

2023-09-22 Thread Russ Allbery
Sune Vuorela writes: > I do think that this is another point of "we should kill our babies if > they don't take off". And preferably faster if/when "we lost" the race. > We carried around the debian menu for a decade or so after we failed to > gain traction and people centered on desktop files.

Re: debian/copyright format and SPDX

2023-09-22 Thread Stephan Lachnit
On Fri, Sep 22, 2023 at 11:11 AM Steve Langasek wrote: > > > SPDX defines an xml format only. They lost before they'd even started. > > debian/copyright is supposed to be human-readable first and foremost. XML > need not apply. Not true. From [1]: > Shall be in a human readable form. > [...]

Re: debian/copyright format and SPDX

2023-09-22 Thread G. Branden Robinson
At 2023-09-22T02:11:15-0700, Steve Langasek wrote: > SPDX defines an xml format only. They lost before they'd even > started. > > debian/copyright is supposed to be human-readable first and foremost. > XML need not apply. Very much +1 on everything quoted. That said, SPDX's license list and

Re: debian/copyright format and SPDX

2023-09-22 Thread Steve Langasek
On Fri, Sep 22, 2023 at 08:43:25AM -, Sune Vuorela wrote: > On 2023-09-08, Jeremy Stanley wrote: > > Since Debian's machine-readable format has been around longer than > > either of the newer formats you mentioned, it seems like it would > > make more sense for the tools to incorporate a

+1 (Re: debian/copyright format and SPDX)

2023-09-22 Thread Holger Levsen
On Fri, Sep 22, 2023 at 08:43:25AM -, Sune Vuorela wrote: > I do think that this is another point of "we should kill our babies if > they don't take off". And preferably faster if/when "we lost" the race. > > We carried around the debian menu for a decade or so after we failed to > gain

Re: debian/copyright format and SPDX

2023-09-22 Thread Sune Vuorela
On 2023-09-08, Jeremy Stanley wrote: > Since Debian's machine-readable format has been around longer than > either of the newer formats you mentioned, it seems like it would > make more sense for the tools to incorporate a parser for it rather I do think that this is another point of "we should

RE: debian testing daily build: installing GRUB/Bootloader and initramfs failing!!

2023-09-17 Thread André Verwijs
thank you Gioele, yes i did got this bug to. but with https://bugs.debian.org/1040899 is trying to install Debian 13, with is VERY unstable and alpha stage, i hope debian 12 can be fixed... thank you André

Re: debian testing daily build: installing GRUB/Bootloader and initramfs failing!!

2023-09-17 Thread Gioele Barabucci
On 17/09/23 09:46, André Verwijs wrote: debian testing daily build:  installing GRUB/Bootloader and initramfs failing!! Probably you stumbled upon this problem: https://bugs.debian.org/1040899 The root cause has (hopefully) been fixed by the Debian Installer team and will be released soon:

Re: debian/copyright format and SPDX

2023-09-09 Thread Jonas Smedegaard
Quoting Paul Wise (2023-09-09 09:18:59) > On Fri, 2023-09-08 at 12:09 +0530, Hideki Yamane wrote: > > > Making appropriate debian/copyright file is hard and boring task, IMHO > > Using scancode-toolkit/etc can probably automate most of that work. > > https://wiki.debian.org/CopyrightReviewTools

Re: debian/copyright format and SPDX

2023-09-09 Thread Paul Wise
On Fri, 2023-09-08 at 12:09 +0530, Hideki Yamane wrote: > Making appropriate debian/copyright file is hard and boring task, IMHO Using scancode-toolkit/etc can probably automate most of that work. https://wiki.debian.org/CopyrightReviewTools -- bye, pabs https://wiki.debian.org/PaulWise

Re: debian/copyright format and SPDX

2023-09-08 Thread Hideki Yamane
Hi, On Fri, 08 Sep 2023 07:34:43 -0700 Russ Allbery wrote: > The really interesting part of SPDX is the license list and the canonical > name assignment, which is *way* more active and *way* more mature at this > point than the equivalent in Debian. They have a much larger license > list, which

Re: debian/copyright format and SPDX

2023-09-08 Thread Jeremy Stanley
On 2023-09-08 13:31:43 + (+), Jeremy Stanley wrote: > On 2023-09-08 12:09:09 +0530 (+0530), Hideki Yamane wrote: > [...] > > SPDX is led by the Linux foundation project, OpenChain for license > > compliance. > [...] > > Unless I'm misreading, OpenChain follows the REUSE specification >

Re: debian/copyright format and SPDX

2023-09-08 Thread Mattia Rizzolo
On Fri, Sep 08, 2023 at 07:34:43AM -0700, Russ Allbery wrote: > I don't think the file format is the most interesting part of SPDX. They > don't really have a competing format equivalent to the functionality of > our copyright files (at least that I've seen; I vaguely follow their > lists). Last

Re: debian/copyright format and SPDX

2023-09-08 Thread Russ Allbery
Jonas Smedegaard writes: > Only issue I am aware of is that SPDX shortname "MIT" equals Debian > shortname "Expat". There was also some sort of weirdly ideological argument with the FSF about what identifiers to use for the GPL and related licenses, which resulted in SPDX using an "-only" and

Re: debian/copyright format and SPDX

2023-09-08 Thread Russ Allbery
Jeremy Stanley writes: > Since Debian's machine-readable format has been around longer than > either of the newer formats you mentioned, it seems like it would make > more sense for the tools to incorporate a parser for it rather than > create needless churn in the package archive just to

Re: debian/copyright format and SPDX

2023-09-08 Thread Jeremy Stanley
On 2023-09-08 12:09:09 +0530 (+0530), Hideki Yamane wrote: [...] > SPDX is led by the Linux foundation project, OpenChain for license > compliance. [...] Unless I'm misreading, OpenChain follows the REUSE specification which acknowledges the sufficiency of "DEP5" formatted license info:

Re: debian/copyright format and SPDX

2023-09-08 Thread Jonas Smedegaard
Hi Hideki, Quoting Hideki Yamane (2023-09-08 08:39:09) ½> > tl;dr: How about considering updating debian/copyright format to have > more compatibility with SPDX format > > > SBOM is expected to be used widely and several tools support it as a trend > now, since US government asks to

Re: Debian Day 2023 em Belo Horizonte (12/08)

2023-08-08 Thread Paulo Henrique de Lima Santana
Olá pessoal. Lembrando que neste sábado (12) teremos o nosso encontro para celebrar o aniversário do Debian. Inicialmente o encontro está previso para ir até às 17h, mas como temos apenas 2 palestras, não tenho certeza se teremos tanto assunto pra ir até às 17h. Então pode ser que termine

Re: Debian 5.19.11-1 (2022-10-03) x86_64 GNU/Linux: NFSv3 Input/output error while cat , 5.14 or below ok

2023-08-01 Thread Konstantin Demin
Hello! Despite I'm not maintainer nor developer I'd suggest to install latest Linux image package from "bullseye-backports" channel - "6.1.27" for now. вт, 1 авг. 2023 г. в 16:43, Chenguang Zhang : > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where

Re: debian-devel-digest Digest V2023 #271

2023-07-19 Thread James Damour
Unsubscribe On Tue, Jul 18, 2023 at 1:33 PM < debian-devel-digest-requ...@lists.debian.org> wrote: > Content-Type: text/plain > > debian-devel-digest Digest Volume 2023 : > Issue 271 > > Today's Topics: > Re: Proposed MBF: Removal of libfree [ Hugh McMaster >

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Daniel S.
|| |We would also like to reveal the codename of Debian 15, which will be "Buttercup". This name follows the tradition of naming Debian releases after characters from the Toy Story movies. We hope you like it and look forward to your contributions to make Debian 15 another great release. |

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Andrey Rakhmatullin
On Wed, Jul 05, 2023 at 11:05:05PM +0200, Joaquín Rufo Gutierrez wrote: > No, Debian 13 will be released on 2024 occasionally. Who are you, sorry?

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Samuel Henrique
The person who sent this "announcement" doesn't seem to be part of the Debian Project, they're also not listed as a member of the release team at https://www.debian.org/intro/organization Someone from the release team might confirm my assumption, but for now please assume this is a fake/troll

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Fabio Fantoni
Il 05/07/2023 22:50, Joaquín Rufo Gutierrez ha scritto: |Hello Debian users, We are happy to announce that Debian 13, codenamed "Trixie", is expected to be released sometime in 2024, following the usual 2-year release cycle.| | | |Hi, sorry but if it were |||2-year release cycle | shouldn't

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Joaquín Rufo Gutierrez
No, Debian 13 will be released on 2024 occasionally. El mié, 5 jul 2023 a las 23:04, Mike Hommey () escribió: > On Wed, Jul 05, 2023 at 10:50:34PM +0200, Joaquín Rufo Gutierrez wrote: > > Hello Debian users, > > > > We are happy to announce that Debian 13, codenamed "Trixie", is > > expected to

Re: Debian 13 release schedule and Debian 15 codename announcement

2023-07-05 Thread Mike Hommey
On Wed, Jul 05, 2023 at 10:50:34PM +0200, Joaquín Rufo Gutierrez wrote: > Hello Debian users, > > We are happy to announce that Debian 13, codenamed "Trixie", is > expected to be released sometime in 2024, following the usual 2-year > release cycle. Bookworm was released in 2023. The usual

Re: Debian 9/stretch moved to archive.debian.org

2023-04-24 Thread Thomas Kähn

Re: Debian 9/stretch moved to archive.debian.org

2023-04-23 Thread Xiyue Deng
xiao sheng wen(肖盛文) writes: > [[PGP Signed Part:Undecided]] > Hi, > > 在 2023/4/24 04:39, Ansgar 写道: >> This has happened now, just according to 計画[1]. It might take a moment >> to reach mirrors. >> >> Ansgar >> >>[1]: Translator's note: 計画 means plan. > > In chinese word, plan means "计划",

Re: Debian 9/stretch moved to archive.debian.org

2023-04-23 Thread 肖盛文
Hi, 在 2023/4/24 04:39, Ansgar 写道: This has happened now, just according to 計画[1]. It might take a moment to reach mirrors. Ansgar [1]: Translator's note: 計画 means plan. In chinese word, plan means "计划", it's not "計画". :-) Thanks! -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆

Re: Debian 9/stretch moved to archive.debian.org

2023-04-23 Thread Ansgar
On Mon, 2023-03-27 at 00:40 +0200, Ansgar wrote: > the stretch, stretch-debug and stretch-proposed-updates suites have now > also been imported on archive.debian.org. People still interested in > these should update their sources.list. > > I plan to remove the suites from the main archive in

Re: Debian Installer Bookworm RC 1 release

2023-04-03 Thread Cyril Brulebois
Charles Curley (2023-04-03): > Hmm. On https://www.debian.org/devel/debian-installer, there are two > news items at the top. Both are dated 19 Feb 2023. Is that correct? > > The RC1 release > (https://www.debian.org/devel/debian-installer/News/2023/20230403) is > also dated February 19th, 2023.

Re: Debian Installer Bookworm RC 1 release

2023-04-03 Thread Charles Curley
On Mon, 3 Apr 2023 23:31:42 +0200 Cyril Brulebois wrote: > The Debian Installer team[1] is pleased to announce the first release > candidate of the installer for Debian 12 "Bookworm". Hmm. On https://www.debian.org/devel/debian-installer, there are two news items at the top. Both are dated 19

Re: Debian Project Leader election 2023: First call for votes

2023-04-02 Thread Micha Lenk
Hi Luna, Am 1. April 2023 16:24:51 MESZ schrieb Luna Jernberg : >Not really any point to vote as highvoltage is the only one to vote on I beg to disagree. There is still a point in voting with just one ballot option available. By following the rules set by our constitution, we ensure we

Re: Debian Project Leader election 2023: First call for votes

2023-04-01 Thread Luna Jernberg
Hey! Not really any point to vote as highvoltage is the only one to vote on congrats to being the Debian Project Leader for another year On 4/1/23, Debian Project Secretary - Kurt Roeckx wrote: > Hi, > > > > This is the first call for votes on the DPL election of 2023. > > > Voting period

Re: Debian 9/stretch moved to archive.debian.org

2023-03-30 Thread Ansgar
On Tue, 2023-03-28 at 16:24 +, Thorsten Glaser wrote: > Ansgar dixit: > > I plan to remove the suites from the main archive in about a month > > (2023-04-23 or later). > > > > The stretch-backports, stretch-backports-sloppy and related debug suites > > will likely move soon as well and might

Re: Debian 9/stretch moved to archive.debian.org

2023-03-28 Thread Thorsten Glaser
Ansgar dixit: >the stretch, stretch-debug and stretch-proposed-updates suites have now >also been imported on archive.debian.org. People still interested in >these should update their sources.list. Might be useful to note that stretch-updates should be dropped from sources.list but has been

Re: debian support veeam

2023-02-22 Thread Paul Wise
On Wed, 2023-02-22 at 12:16 +0300, Nijam Deen wrote: > debain os will support for veeam backup using network storage Since Veeam is proprietary software, please ask their support team: https://www.veeam.com/support.html -- bye, pabs https://wiki.debian.org/PaulWise signature.asc

Re: debian stretch: disable running gvfsd by default

2023-02-19 Thread Andrew M.A. Cater
On Sat, Feb 18, 2023 at 06:28:45AM +0200, ijaaskelai...@outlook.com wrote: > The old version breaks online filesystems! > YOu may want to note that stretch has very recently been moved to archive.debian.org. It may be appropriate to move to a newer supported version of Debian, perhaps to

Re: Debian versão gamer

2022-12-29 Thread Diego Santos
Olá! Quero saber se tem curso de Debian completo básico ao avançado a Sou fã vejo única versão estabilidade segurança,mas vejo Linux não tem sido olhares da Inteltem bugs kernel questão dual boot , wi-fi quero ser Harry Potter garoto propaganda do Debian no Brasil...sendo foguete comercial e

Re: Debian Med video conference tomorrow, third Sunday of December 2022-12-18 18:00 UTC

2022-12-17 Thread Andreas Tille
Hi, this is the call for the next video conference of the Debian Med team that are an established means to organise the tasks inside our team. In last conference we decided about a new scheme to find a date: First Friday of a month Third Sunday of a month The rationale is that several

Re: debian/watch: Ignoring pre-release on GittHub

2022-12-13 Thread Kentaro Hayashi
Hi, 2022年12月8日(木) 20:40 Andrius Merkys : > > On 2022-12-08 12:59, Kentaro Hayashi wrote: > > 2022年12月5日(月) 16:41 Stephan Lachnit : > >> > >> You can try to take a look at the GitHub API, e.g. [1]. > >> > >> Inside is an `prerelease` entry. Not sure how easy this is to > >> implement in uscan

Re: debian/watch: Ignoring pre-release on GittHub

2022-12-08 Thread Andrius Merkys
On 2022-12-08 12:59, Kentaro Hayashi wrote: 2022年12月5日(月) 16:41 Stephan Lachnit : You can try to take a look at the GitHub API, e.g. [1]. Inside is an `prerelease` entry. Not sure how easy this is to implement in uscan though. Cheers, Stephan [1]:

  1   2   3   4   5   6   7   8   9   10   >