Re: Debian 11.10 release date enquiry
On Fri, 2024-04-26 at 00:07 +, Devidas Shanbhag, Amrutha wrote: > Thanks for your response. My bad, I should have mentioned that I did > look at the releases page and found that the next point release 11.10 > isn’t planned yet. Hence the query. > > Historically, minor versions have been released roughly once every > month. You're miscounting. Updates to stable (currently Debian 12) are approximately once every two months. For oldstable (currently Debian 11) they're about once every four months, until it moves to being handled by the LTS team. Regards, Adam
Re: Upcoming stable point release (12.6)
On Fri, 2024-02-16 at 17:35 +, Jonathan Wiltshire wrote: > The next point release for "bookworm" (12.6) is scheduled for > Saturday, April 6th. Processing of new uploads into bookworm- > proposed-updates will be frozen during the preceeding weekend. Due to recent events, the point release has been postponed. A new date will be announced when possible. Regards, Adam
Upcoming oldstable point release (11.9)
Hi, The next point release for "bullseye" (11.9) is scheduled for Saturday, February 10th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (12.5)
Hi, The next point release for "bookworm" (12.5) is scheduled for Saturday, February 10th. Processing of new uploads into bookworm-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (12.3)
Hi, The next point release for "bookworm" (12.3) is scheduled for Saturday, December 9th. Processing of new uploads into bookworm-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Bug#1043539: project: Forwarding of @debian.org mails to gmail broken
On Sun, 2023-08-13 at 10:57 +0100, Adam D. Barratt wrote: > On Sat, 2023-08-12 at 23:13 +0200, Mattia Rizzolo wrote: > > On Sat, Aug 12, 2023 at 01:41:46PM -0700, Russ Allbery wrote: > > > The problem I suspect is with email forwarding, and specifically > > > email > > > forwarding to Gmail, which has recently ramped up the amount of > > > verification it does on messages. Because of email forwarding, > > > Gmail sees > > > a message purportedly from helgefjell.de but actually delivered > > > by > > > debian.org mail servers, and has now decided to be suspicious of > > > that. > > > > This is the exact use case that SRS was developer for, however > > gmail's documentation does not recommend that (but the situation, > > as > > you noted, worsened, so I tried it in some other similar setups and > > everything is great, so...). > > They sort of recommend it now. But also not. It's complicated. [tm] > > > My understanding is that several DSA members were opposed to using > > SRS for @debian.org forwarding, but maybe it's now time? > > > > That's essentially what's being worked on. But life, and free time, > and > other priorities, keep getting in the way. An initial version, rewriting mails to Google-hosted domains from "external" e-mail addresses (those for which debian.org's mail relays don't consider themselves authoritative, so mostly not *.debian.org and *.debconf.org) is now live. Please let DSA know if you encounter any issues. Regards, Adam
Bug#1043539: project: Forwarding of @debian.org mails to gmail broken
On Sat, 2023-08-12 at 23:13 +0200, Mattia Rizzolo wrote: > On Sat, Aug 12, 2023 at 01:41:46PM -0700, Russ Allbery wrote: > > The problem I suspect is with email forwarding, and specifically > > email > > forwarding to Gmail, which has recently ramped up the amount of > > verification it does on messages. Because of email forwarding, > > Gmail sees > > a message purportedly from helgefjell.de but actually delivered by > > debian.org mail servers, and has now decided to be suspicious of > > that. > > This is the exact use case that SRS was developer for, however > gmail's documentation does not recommend that (but the situation, as > you noted, worsened, so I tried it in some other similar setups and > everything is great, so...). They sort of recommend it now. But also not. It's complicated. [tm] > My understanding is that several DSA members were opposed to using > SRS for @debian.org forwarding, but maybe it's now time? > That's essentially what's being worked on. But life, and free time, and other priorities, keep getting in the way. Regards, Adam
Bug#1043539: project: Forwarding of @debian.org mails to gmail broken
On Sat, 2023-08-12 at 17:08 +, Helge Kreutzmann wrote: > Hello Adam, > Am Sat, Aug 12, 2023 at 05:35:52PM +0100 schrieb Adam D. Barratt: > > On Sat, 2023-08-12 at 15:54 +, Helge Kreutzmann wrote: [...] > > > 550-5.7.26 This mail is unauthenticated, which poses a > > > security > > > risk to the > > > 550-5.7.26 sender and Gmail users, and has been blocked. The > > > sender must > > > 550-5.7.26 authenticate with at least one of SPF or DKIM. For > > > this message, > > > 550-5.7.26 DKIM checks did not pass and SPF check for > > > [helgefjell.de] did not > > > [...] > > > 550-5.7.26 > > > https://support.google.com/mail/answer/81126#authentication for > > > 550 5.7.26 instructions on setting up authentication. v26- > > > 20020aa7d65a00b005231f55294dsi4996663edr.385 - gsmtp > > > > > > The IP 82.195.75.114 resolves to > > > 114.75.195.82.in-addr.arpa is an alias for 114.64- > > > 26.75.195.82.in- > > > addr.arpa. > > > 114.64-26.75.195.82.in-addr.arpa domain name pointer > > > mailly.debian.org. > > > > > > And of course, SPF/DKIM checks for my domain (helgefjell.de) fail > > > for this IP, which is @debian.org. > > > > > > > The DKIM signature warning has nothing to do with the forwarding, > > or the involvement of debian.org at all. The reason that check > > fails is that your mail has no DKIM signature, so obviously can't > > have a valid one. Signing your mail would probably make gmail a lot > > happier with it in general. (As a side note, the BTS breaks many > > common DKIM signature strategies, but that's a different issue.) > > Sigh. > > Directly gmail accepts it. > I'm not sure why the sigh, but in any case your direct mail presumably succeeds because it passes the SPF check. I was simply clarifying that the DKIM check would fail in both cases. Regards, Adam
Bug#1043539: project: Forwarding of @debian.org mails to gmail broken
Hi, On Sat, 2023-08-12 at 15:54 +, Helge Kreutzmann wrote: > If I try to mail e.g. Marcos Fouces , this no > longer works. I get the following error message: > Contacting DSA is generally a better way to ask about infrastructure things than filing bugs on high-level pseudo-packages. > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) > failed: > > marcos.fou...@gmail.com > host gmail-smtp-in.l.google.com [173.194.79.26] > SMTP error from remote mail server after pipelined end of data: > 550-5.7.26 This mail is unauthenticated, which poses a security > risk to the > 550-5.7.26 sender and Gmail users, and has been blocked. The > sender must > 550-5.7.26 authenticate with at least one of SPF or DKIM. For > this message, > 550-5.7.26 DKIM checks did not pass and SPF check for > [helgefjell.de] did not > 550-5.7.26 pass with ip: [82.195.75.114]. The sender should visit > 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for > 550 5.7.26 instructions on setting up authentication. v26- > 20020aa7d65a00b005231f55294dsi4996663edr.385 - gsmtp > > The IP 82.195.75.114 resolves to > 114.75.195.82.in-addr.arpa is an alias for 114.64-26.75.195.82.in- > addr.arpa. > 114.64-26.75.195.82.in-addr.arpa domain name pointer > mailly.debian.org. > > And of course, SPF/DKIM checks for my domain (helgefjell.de) fail for > this IP, which is @debian.org. > The DKIM signature warning has nothing to do with the forwarding, or the involvement of debian.org at all. The reason that check fails is that your mail has no DKIM signature, so obviously can't have a valid one. Signing your mail would probably make gmail a lot happier with it in general. (As a side note, the BTS breaks many common DKIM signature strategies, but that's a different issue.) The general issue is being worked on, as time and resources allow. Regards, Adam (part of, but not on behalf of, DSA)
Upcoming stable point release (11.7)
Hi, The next point release for "bullseye" (11.7) is scheduled for Saturday, April 29th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.6)
Hi, The next point release for "bullseye" (11.6) is scheduled for Saturday, December 17th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: master.d.o bullseye upgrade
Hi, On Wed, 2022-08-17 at 17:39 +0100, Adam D. Barratt wrote: > I'll be upgrading master to bullseye later this evening, aiming to > begin around 18:30UTC. The upgrade is now complete. Please let DSA know if you notice any issues. Regards, Adam signature.asc Description: This is a digitally signed message part
Upcoming oldstable point release (10.13)
Hi, The next - and final - point release for "buster" (10.13) is scheduled for Saturday, September 10th. Processing of new uploads into buster- proposed-updates will be frozen during the weekend of August 27th. Regards, Adam
Upcoming stable point release (11.5)
Hi, The next point release for "bullseye" (11.5) is scheduled for Saturday, September 10th. Processing of new uploads into bullseye-proposed- updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.4)
Hi, The next point release for "bullseye" (11.4) is scheduled for Saturday, July 9th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.12)
Hi, The next point release for "buster" (10.12) is scheduled for Saturday, March 26th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.3)
Hi, The next point release for "bullseye" (11.3) is scheduled for Saturday, March 26th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.2)
Hi, The next point release for "bullseye" (11.2) is scheduled for Saturday, December 18th. Processing of new uploads into bullseye-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (10.11)
Hi, The next point release for "buster" (10.11) is scheduled for Saturday, October 9th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (11.1)`
Hi, The first point release for "bullseye" (11.1) is scheduled for Saturday, October 9th. Processing of new uploads into bullseye- proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.10)
Hi, The next point release for "buster" (10.10) is scheduled for Saturday June 19th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: salsa.debian.org currently down
On Thu, 2021-03-18 at 10:11 -0700, Jacob Lifshay wrote: > I didn't see any recent announcements and couldn't find any salsa- > specific mailing lists, so I'm posting here. Which location would I > find status announcements for salsa? They're generally on the debian-infrastructure-announce list. In this specific case, it's https://lists.debian.org/msgid-search/YFMXgikaGq9doSmV@chou Regards, Adam
Upcoming stable point release (10.9)
Hi, The next point release for "buster" (10.9) is scheduled for Saturday March 27th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.8)
Hi, The next point release for "buster" (10.8) is scheduled for Saturday February 6th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.7)
Hi, The next point release for "buster" (10.7) is scheduled for Saturday December 5th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: Q: When dnsZoneEntry is freed after DD retired
On Wed, 2020-09-30 at 12:57 +0200, Mattia Rizzolo wrote: > On Tue, Sep 29, 2020 at 05:10:23PM +0900, Kentaro Hayashi wrote: > > How should I ask to remove them in this case? > > This being debian-project@ I'm sure there are several DSA members who > follow the list, so I'd say to try and wait some time to see if any > of them follow up. As noted in the original mail, as soon as an account is locked any corresponding debian.net DNS entries stop being published. The only question under consideration is thus whether those entries should become available for re-use and, if so, when. My (anecdotal) experience is that debian.net entries tend to fall into two categories - those that only have any relevance or usefulness to an individual, and those that are of wider use, where there may be surprise at their disappearance. It's not entirely clear in either case how soon after retirement the record should become available, and we don't have tooling to support any answer other than "immediately". If there's a need / desire for a particular DNS name previously owned by an ex-DD to be made available, then we'd be happy to discuss that on a per-case basis. As a side-note, please bear in mind that -project is publicly archived when considering whether to post data from LDAP to it (even publicly- visible data). Regards, Adam [as a member of, but not on behalf of, DSA]
Upcoming stable point release (10.6)
Hi, The next point release for "buster" (10.6) is scheduled for Saturday September 26th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: Upcoming stable point release (10.5)
Hi, On Sun, 2020-07-12 at 15:37 +0100, Adam D. Barratt wrote: > On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote: > > The next point release for "buster" (10.5) is scheduled for > > Saturday July 18th. Processing of new uploads into buster-proposed- > > updates will be frozen during the preceding weekend. > > Unfortunately this has had to be delayed slightly. > > A new date will be announced soon. This will now be Saturday August 1st. Regards, Adam
Re: Upcoming stable point release (10.5)
Hi, On Sat, 2020-06-27 at 14:35 +0100, Adam D. Barratt wrote: > The next point release for "buster" (10.5) is scheduled for Saturday > July 18th. Processing of new uploads into buster-proposed-updates > will be frozen during the preceding weekend. Unfortunately this has had to be delayed slightly. A new date will be announced soon. Regards, Adam
Upcoming oldstable point release (9.13)
Hi, The next - and final - point release for "stretch" (9.13) is scheduled for Saturday, July 18th. Processing of new uploads into stretch- proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.5)
Hi, The next point release for "buster" (10.5) is scheduled for Saturday July 18th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.4)
Hi, The next point release for "buster" (10.4) is scheduled for Saturday, May 9th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: master.d.o buster upgrade
On Thu, 2020-02-13 at 18:08 +, Adam D. Barratt wrote: > I'll be upgrading master to buster later this evening, aiming to > begin around 20:00UTC. The upgrade is now complete. Please let DSA know if you notice any issues. Regards, Adam signature.asc Description: This is a digitally signed message part
Re: Unscheduled UBC service outage
On 2020-02-12 08:58, Adam D. Barratt wrote: Due to an issue with the MSA, a number of services hosted at UBC are currently offline pending further investigation. Everything should be back up now, please let DSA know if you notice any remaining issues. Regards, Adam
Upcoming oldstable point release (9.12)
Hi, The next point release for "stretch" (9.12) is scheduled for Saturday, February 8th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.3)
Hi, The next point release for "buster" (10.3) is scheduled for Saturday, February 8th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: Some thoughts about Diversity and the CoC
On 2019-12-12 10:22, Gerardo Ballabio wrote: And indeed, in the last decades, redefining language has been a major part of the political debate at large, with every group trying to "hijack words for their own ends". [...] So when I refuse ... to abuse the English language by calling an individual "they" I don't have anything to add to Steve's response to the rest of your mail, but if you insist on flogging this particular expired equine then you should be aware that you're approximately six centuries too late to stop the use of singular they being acceptable in English. Regards, Adam
Upcoming stable point release (10.2)
Hi, The next point release for "buster" (10.2) is scheduled for Saturday, November 16th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (9.10)
Hi, The next point release for "stretch" (9.10) is scheduled for Saturday, September 7th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (10.1)
Hi, The first point release for "buster" (10.1) is scheduled for Saturday, September 7th. Processing of new uploads into buster-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.9)
Hi, The next point release for "stretch" (9.9) is scheduled for Saturday, April 27th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.8)
Hi, The next point release for "stretch" (9.8) is scheduled for Saturday, February 16th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.6)
Hi, The next point release for "stretch" (9.6) is scheduled for Saturday, November 10th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.5)
Hi, The next point release for "stretch" (9.5) is scheduled for Saturday, July 14th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.4)
Hi, The next point release for "stretch" (9.4) is scheduled for Saturday, March 10th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release
Hi, The next point release for "jessie" (8.10) is scheduled for Saturday, December 9th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release
Hi, The next point release for "stretch" (9.3) is scheduled for Saturday, December 9th. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.1)
Hi, The first point release for "stretch" (9.1) is scheduled for Saturday, July 22nd. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (8.9)
Hi, The next point release for "jessie" (8.9) is scheduled for Saturday, July 22nd. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.8)
Hi, The next point release for "jessie" (8.8) is scheduled for Saturday, May 6th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.7)
Hi, The next point release for "jessie" (8.7) is scheduled for Saturday, January 14th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.6)
Hi, The next point release for "jessie" (8.6) is scheduled for Saturday, September 17th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Re: third-party packages adding apt sources
On 2016-05-19 17:39, Bas Wijnen wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, May 19, 2016 at 11:46:53AM -0400, Paul Tagliamonte wrote: [cc'ing devel, since this is a rant that involves technical topics, and god knows I only go on so many rants a year these days] You didn't actually do this. https://lists.debian.org/debian-devel/2016/05/msg00277.html disagrees (modulo quibbles on naming). Regards, Adam
Upcoming stable point release (8.4)
Hi, The next point release for "jessie" (8.4) is scheduled for Saturday, April 2nd. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (7.10)
Hi, The next point release for "wheezy" (7.10) is scheduled for Saturday, April 2nd. Processing of new uploads into wheezy-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (8.3)
Hi, The next point release for "jessie" (8.3) is scheduled for Saturday, January 23rd. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (7.9)
Hi, The next point release for wheezy (7.9) is scheduled for Saturday, September 5th. Processing of new uploads into wheezy-proposed-updates will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Upcoming stable point release (8.2)
Hi, The next point release for jessie (8.2) is scheduled for Saturday, September 5th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Upcoming stable point release (8.1)
Hi, The first point release for jessie (8.1) is scheduled for Saturday, June 6th. Stable NEW will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Re: CD Images
On Wed, 2015-03-04 at 13:16 -0800, Dave Turner wrote: I guess if it works, it works, but it doesn’t work for me. Seems there may be configuration issues with the name servers, but that resolution is happening anyway. I use unbound for my internal resolvers, and I’ve never seen this before. So, just a heads-up I guess. http://dnscheck.pingdom.com/?domain=cdimage.debian.orgtimestamp=1425503610view=2 I'm somewhat confused at this point. That page says that it can't find the nameservers for the *zone* cdimage.debian.org. That's correct and expected - it's a hostname, not a domain name. There aren't any nameservers for cdimage.debian.org, rather for debian.org. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1425505829.2596.13.ca...@adam-barratt.org.uk
Upcoming stable point release (7.8)
Hi, The next point release for wheezy (7.8) is scheduled for Saturday, January 10th. Stable NEW will be frozen during the preceding weekend. Regards, Adam signature.asc Description: This is a digitally signed message part
Re: Can I still depend on Debian?
On Mon, 2014-11-17 at 14:10 -0800, Rhy Thornton wrote: More concerning than that is that systemd won't be producing human readable log files. As a full time sysadmin, I'm reading log files all day, and I have to wonder what the reasoning behind this is (to be fair, I haven't really looked into it yet. I'm busy with real work). To be fair, it would be helpful if you _did_ look in to things, before making incorrect statements with such certainty. If you don't get logs as usual via syslog, that's a bug and should be fixed. $ ls -ltr /sbin/init lrwxrwxrwx 1 root root 20 Sep 28 20:33 /sbin/init - /lib/systemd/systemd $ ls -l /var/log/syslog -rw-r- 1 root adm 769029 Nov 17 22:50 /var/log/syslog ii systemd 215-5+b1 amd64system and service manager Regards, Adam (also a sysadmin, reading log files much of the day and busy with real work, including trying to get a release out...) -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1416264978.19889.36.ca...@adam-barratt.org.uk
Upcoming stable point release (7.7)
Hi, The next point release for wheezy (7.7) is scheduled for Saturday, October 18th. Stable NEW will be frozen during the preceding weekend. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411585956.15708.2.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.6)
Hi, The next point release for wheezy (7.6) is scheduled for Saturday, July 12th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402513678.4620.13.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.10)
Hi, The next (and final) point release for squeeze (6.0.10) is scheduled for Saturday, July 19th. Oldstable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1402513777.4620.15.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.5)
Hi, The next point release for wheezy (7.5) is scheduled for Saturday, April 26th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395609622.12119.11.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.4)
Hi, The next point release for wheezy (7.4) is scheduled for Saturday February 8th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390507736.6444.23.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.9)
Hi, The next point release for squeeze (6.0.9) is scheduled for Saturday February 15th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390507759.6444.24.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.3)
Hi, The next point release for wheezy (7.3) is scheduled for Saturday December 14th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386102648.3844.14.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.2)
Hi, The next point release for wheezy (7.2) is scheduled for Saturday October 12th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1379877070.4765.26.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release (6.0.8)
Hi, The next point release for squeeze (6.0.8) is scheduled for Saturday October 19th. Oldstable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1379877103.4765.27.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (7.1)
Hi, The first point release for wheezy (7.1) is scheduled for Saturday June 15th. Stable NEW will be frozen during the preceding weekend. As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1368681625.6290.20.ca...@jacala.jungle.funky-badger.org
Re: [all candidates] Removing or limiting DD rights?
On 03.04.2013 06:09, Chris Knadle wrote: On Tuesday, April 02, 2013 20:34:28, Russ Allbery wrote: Note that we already did do something about it by deprecating close in the BTS in favor of sending a real email message to -done that is copied to the submitter. The Debian BTS now nags the maintainer about telling the submitter something if they use the close command. That's interesting. That sounds like an improvement in this area. If you happen to know when that was implemented, I'd be interested. June of last year I saw a bug closed (marked as done, without explanation) where I didn't see any email sent to the BTS control@ address in the bug, so I was confused as to how the bug was closed. Would emailing -done do that? Closing the bug is exactly what -done is for. Using control@ to close bugs should be the exception, not the rule. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/93853dd7c74239d3941ce5762...@mail.adsl.funky-badger.org
Re: Kernel Header?
On Sat, 2013-03-16 at 09:33 -0400, Nathaniel Biser wrote: Thanks, everybody! First, I think that Kali linux is debian derived, though it isn't debian per-say. Apt-get install didn't work, it couldn't find the package that I need anywhere. And I checked the link that you gave me to look at, and I still couldn't find anything. I sure hope that I will be able to run VMware on this PCanymore ideas? The problem is that a Debian derivative may have different packages or at least different versions of packages, with different dependencies than those in Debian proper which means that solutions that apply to Debian itself don't always apply to derivatives, and vice-versa. In a related note, debian-project's stated purpose is Discussion about non-technical topics related to the Debian Project, which looking for packages doesn't really fit. You might find one of the more user-oriented lists more appropriate. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1363442854.2662.25.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (6.0.7)
Hi, The next point release for squeeze (6.0.7) is scheduled for Saturday February 23rd. Stable NEW will be frozen during the preceding Monday (18th). As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1360783944.9953.3.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release (6.0.5)
Hi, The next point release for squeeze (6.0.5) is scheduled for Saturday May 12th. Stable NEW will be frozen during the preceding weekend (5/6th). As usual, base-files can be uploaded at any point before the freeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335820791.6289.20.ca...@jacala.jungle.funky-badger.org
Upcoming oldstable point release
Hi, The next - and final - point release for lenny (5.0.10) is scheduled for Saturday March 10th. Oldstable NEW will be frozen during the coming weekend (3rd/4th). As this will be the last point release for lenny, it will be moved to archive.debian.org in the near future (most likely on or after March 24th). Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1330499137.12939.49.ca...@jacala.jungle.funky-badger.org
Upcoming stable point release
Hi, The next point release for squeeze (6.0.4) is scheduled for Saturday January 28th. Stable NEW will be frozen during the preceeding weekend (21st/22nd). As usual, base-files can be uploaded at any point before the freeze. If there is a further kernel update planned for inclusion in the point release, it would be ideal if that could be uploaded over the coming weekend so that we can look at finalising the installer later next week. Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b0343660143780d37f8c02ff126c5...@mail.adsl.funky-badger.org
Re: 1 year release good enough.
On Sun, 2012-01-01 at 11:51 +0530, dE . wrote: I was wondering about the 2 year release cycle of Debian and it's adaptability on the Desktops. You have to admit that Debian is not used used much on the Desktops -- Really? Of the five systems in my household which could count as desktops (assuming one includes laptops - they're certainly not servers), three of them run Debian (and one of the others doesn't belong to me). Since there's a new branch, there'll be additional loads on the developers (backports and all that), You seem to be assuming that everyone will be happy to take on these additional loads. With both my maintainer and release hats on, I believe you're mistaken in that (and in the need for the proposal in general). However, as has been done more than once in the past, you're free to set up and maintain such a branch and prove to people that it's workable and worthwhile. I suggest the unstable branch be demolished (I'm not clear about it's role though) I'm concerned that someone who doesn't know what the purpose of unstable is should be trying to make far-reaching changes to the way the project works. and increase the migration time from experimental to testing. Right now, there's no migration of packages from experimental to testing. So you certainly couldn't decrease the time... Regards, Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1325428498.2980.11.ca...@jacala.jungle.funky-badger.org
Re: DAM and NEW queues processing
On Thu, 2009-06-25 at 18:11 +0200, Lucas Nussbaum wrote: On 25/06/09 at 17:45 +0200, Michael Banck wrote: On Thu, Jun 25, 2009 at 02:43:53PM +0200, Lucas Nussbaum wrote: I said that I considered some people ready to start NM, because I was sure that they would be perfectly ready to be a DD by the end of the NM process (i.e a year and a half later, basically), and that they would be good NM applicants (modulo the usual delays and motivation problems). You considered people ready to start NM while the project did not (i.e. they were not ready by the time they applied, as required by the project). Let's look at what the documentation says. on nmadvocate.php, it is said: Please advocate an applicant only if you are sure that he or she is prepared and capable to become a Debian Developer. it's become, not be. I've always read that as using a different sense of become - to assume the role of being a DD, rather than to develop over time in to a DD. YMM - and apparently does - V. Adam -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [SUMMARY] About terminology for stable/testing/unstable and related issues
On Sat, 2006-05-13 at 09:54 +0200, Florian Weimer wrote: * Adam D. Barratt: On Tuesday, May 09, 2006 6:26 AM, Florian Weimer [EMAIL PROTECTED] wrote: [...] Suite has already been used informally. For completeness, you should also mention section (main, contrib, non-free) Those are components in Debian's nomenclature. Sections are the next level down. Policy 2.2 calls them sections or categories (depending on whether you go with the headline or the main text). One place the term component is used is APT, but I don't think this is an authoritative reference (cf. the use of distribution). dak calls them components, as ime do the ftp-masters (presumably because apt and dak do); likewise suites. Unofficial tools such as madison-lite and rmadison unsurprisingly also follow the convention. Policy 2.2 is a confusing use of sections imho, especially as 2.4 is also headed Sections and describes sections as I did previously, i.e. as a level below main, etc. Just to add to the fun, 2.4 also says: The `Section' field should be of the form: * _section_ if the package is in the _main_ category, * _segment/section_ if the package is in the _contrib_ or _non-free_ distribution areas. using three different terms for the same thing within one paragraph. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SUMMARY] About terminology for stable/testing/unstable and related issues
On Tuesday, May 09, 2006 6:26 AM, Florian Weimer [EMAIL PROTECTED] wrote: * Christian Perrier: Most concerns have been raised about my proposed use of branch for talking about stable/testing/unstable. Suite seems better...suited, indeed. Suite has already been used informally. For completeness, you should also mention section (main, contrib, non-free) Those are components in Debian's nomenclature. Sections are the next level down. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Information abount packages.d.o and experimental
On Sat, 2006-01-07 at 11:20 +0100, Florian Weimer wrote: * Noèl Köthe: is it possible to get information about the problem with packages.d.o and the experimental problem? Isn't experimental being pulled from the archive or something like that? Given that a member of the ftpmaster team has commented on this thread without suggesting any such thing (and I haven't heard any reference elsewhere to such a plan), I'd say it's unlikely. Regards, Adam
Re: Induction of new members to the technical committee
On Thursday, December 22, 2005 7:22 AM, Martin Zobel-Helas [EMAIL PROTECTED] wrote: Hi Manoj, On Tuesday, 20 Dec 2005, you wrote: [...] So I hereby propose that this committee recommend to the the Debian project leader the following individuals to be candidates for induction into the technical committee (as per section 6.2.2 of the constitution) [...] actually, i would like to know how this persons have been appointed/selected? Will this work like any other vote, so anyone can be recommented? Or does the CTTE need to assign this person by it's own? As noted in Manoj's message, section 6 of the constituion covers the Technical Committee. Section 6.2 specifies that appointments are made by the Committee and/or DPL subject to the conditions of that section. Cheers, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Complaint about #debian operator
On Mon, 2005-12-12 at 21:42 +0100, martin f krafft wrote: also sprach Joey Hess [EMAIL PROTECTED] [2005.12.12.2121 +0100]: So when was the last time you tried installing Debian with this task whose name you are not even sure of? I don't think I ever installed the task myself, but surely I installed GNOME and/or KDE, and the task doesn't really do anything else, or does it? [...] The desktop task installs KDE and GNOME [EMAIL PROTECTED]:~$ grep-dctrl -sPackage -FTask -r ^desktop $ /var/lib/apt/lists/*_Packages \ | egrep -ci (gnome|kde) 0 [...] Why did you bring up d-i in this context anyway? I'm assuming that tasksel's recentish changelog was being alluded to (2.30, for instance). Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-DDs as official Debian package maintainers
On Thursday, September 22, 2005 8:36 AM, MJ Ray [EMAIL PROTECTED] wrote: Jonas Smedegaard [EMAIL PROTECTED] wrote: MJ Ray [EMAIL PROTECTED] wrote: [...] Tools like qa.debian.org tracks maintainers, not signers. So for each package I believe I must find the package in packages.qa.debian.org, pick the upload message, decipher the GPG signature... Right? No, you find the package's control file and look at the Uploader. packages.qa.debian.org shows this in Co-maintainers at present, for some reason. Erm... because that's how policy defines the field. Section 5.6.3 - http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Uploaders - to be precise. Uploaders lists addresses which are not the address listed in Maintainer: but from which uploads should not be considered NMUs. That effectively makes those addressess co-maintainers (admittedly it may require a small leap to extend that to maintainer is a mailing list with named developers as co-maintainers, but it's really not that difficult and more of a hop than a leap). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-DDs as official Debian package maintainers
[resent with correct From:] On Thursday, September 22, 2005 8:36 AM, MJ Ray [EMAIL PROTECTED] wrote: Jonas Smedegaard [EMAIL PROTECTED] wrote: MJ Ray [EMAIL PROTECTED] wrote: [...] Tools like qa.debian.org tracks maintainers, not signers. So for each package I believe I must find the package in packages.qa.debian.org, pick the upload message, decipher the GPG signature... Right? No, you find the package's control file and look at the Uploader. packages.qa.debian.org shows this in Co-maintainers at present, for some reason. Erm... because that's how policy defines the field. Section 5.6.3 - http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Uploaders - to be precise. Uploaders lists addresses which are not the address listed in Maintainer: but from which uploads should not be considered NMUs. That effectively makes those addressess co-maintainers (admittedly it may require a small leap to extend that to maintainer is a mailing list with named developers as co-maintainers, but it's really not that difficult and more of a hop than a leap). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
