On Wed, 9 Mar 2022 00:12:25 +0200, Adrian Bunk
wrote:
>On Tue, Mar 08, 2022 at 05:49:04PM +0100, Marc Haber wrote:
>>...
>> (2)
>> #774046 #520037
>> Which special characters should we allow for account names?
>>
>> People demand being able to use a dot (w
ng.
Adduser can already be configured to allow that via a documented
interface. We're talking about the default here. The only point where
an account might be created before that configuration possibility
becomes available is the Installer.
Greetings
Marc
--
On Tue, 8 Mar 2022 17:02:06 -0600, Richard Laager
wrote:
>On 3/8/22 10:49, Marc Haber wrote:
>> (1)
>> #202943, #202944, #398793, #442627, #782001
>> The bug reporters are requesting the default for DIR_MODE to be changed
>> from 0755 to 0700, making home directories
On Wed, 9 Mar 2022 14:10:04 +0100, Harald Dunkel
wrote:
>On 2022-03-08 17:49:04, Marc Haber wrote:
>> (1a) would it be necessary to handle --system accounts differently? I
>> think yes.
>
>I think it would be helpful to define "system account" and "n
On Tue, 8 Mar 2022 18:40:11 +, Simon McVittie
wrote:
>On Tue, 08 Mar 2022 at 17:49:04 +0100, Marc Haber wrote:
>> (3)
>> #625758
>> --disabled-password just does not set a password for the newly created
>> account (resulting in '*' in shadow) while --dis
at should intentionally be group-readable, not all files created
>anywhere.
Are we using ACLs bei Default already in other places of the Debian
system?
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions
n of a --system user.
Would that help with the issue?
>> How would chown handle the dot case intelligently?
>
>Something along the lines of see if the user exists.
Michael Stone has elaborated on that topic and told us how chown
already behaves.
Greetings
Marc
--
On Thu, 10 Mar 2022 09:28:24 +, Simon McVittie
wrote:
>On Thu, 10 Mar 2022 at 06:37:58 +0100, Marc Haber wrote:
>> Are we using ACLs [by] Default already in other places of the Debian
>> system?
>
>For user-facing purposes I don't think so (although they're av
both configurations are in sync to each other.
Would it make sense that adduser reads login.defs if the respective
setting is not overridden in adduser.conf?
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions ar
On Thu, 10 Mar 2022 13:57:13 +0200, Wouter Verhelst
wrote:
>On Wed, Mar 09, 2022 at 09:00:22PM +0100, Marc Haber wrote:
>> On Tue, 8 Mar 2022 18:40:11 +, Simon McVittie
>> >--disabled-login: the new account has an empty password but is "locked";
>> >so p
uess it's due time. Would we go alone in Debian
or would you prefer that we try convincing upstream to finally go that
way? I am not convinced that Debian should derive from standard
behavior here, but you have the coreutils hat on and I would support
either decision.
And then we'd have
On Wed, 09 Mar 2022 21:34:33 +0100, Pierre-Elliott Bécue
wrote:
>Considering many have replied, I'll stick to that one:
>Marc Haber wrote on 08/03/2022 at 17:49:04+0100:
>> (3)
>> #625758
>> --disabled-password just does not set a password for the newly created
&g
On Thu, 10 Mar 2022 00:01:36 +, Seth Arnold
wrote:
>On Tue, Mar 08, 2022 at 05:49:04PM +0100, Marc Haber wrote:
>> (2)
>> #774046 #520037
>> Which special characters should we allow for account names?
>
>Please consider the leading character separately from
On Thu, 10 Mar 2022 13:17:26 -0800, Steve Langasek
wrote:
>On Thu, Mar 10, 2022 at 06:37:58AM +0100, Marc Haber wrote:
>> On Thu, 10 Mar 2022 00:04:38 +0100, Ansgar wrote:
>> >On Wed, 2022-03-09 at 17:29 -0500, Michael Stone wrote:
>> >> Those are actually unrelate
requiring the package to have one
line in the right place in the script.
Greetings
Marc
P.S.: I got involved with adduser 20 years ago because the then
debhelper maintainer brushed off my suggestion to have a dh call for
creating system users. Back then, this approach was as declar
usly locked
account? I hate the inconsistent terminology that we have here.
Thanks for testing.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany |
would be a nice idea for an MBF. Sadly I do not have the time to
do that. I have filed a wishlist bug for a lintian check.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Maila
by adduser.
Noted. I will post a summary at the beginning of the new week.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom
On Sat, 12 Mar 2022 14:41:35 -0500, Michael Stone
wrote:
>On Fri, Mar 11, 2022 at 10:16:24PM +0100, Marc Haber wrote:
>>[^[:alpha:]]chown[[:space:]][^[:space:]]+\.[^[:space:]] is found 829
>>times in Debian, mostly in docs and comments, but also in a few live
>>scripts. I thi
eeping cron alive
to those systemd-free distributions.
The anti-systemd faction in Debian is cordially invited to step in,
bring cron and cronie up to shape, before asking the rest of the
Distribution to stick with essential system software that has been
unmaintained for years.
Gre
15 year old usergroups decision
>would need to be revalidated by someone who cared.
Wouldnt the umask patch be even more useful if we tightened down the
directory permissions?
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber |
On Sun, 13 Mar 2022 18:02:55 +0100, Christian Kastner
wrote:
>On 2022-03-13 11:06, Marc Haber wrote:
>> The anti-systemd faction in Debian is cordially invited to step in,
>> bring cron and cronie up to shape, before asking the rest of the
>> Distribution to stick with esse
pose the case where certain cron jobs depend on each
other and only work if they're executed in exact order.
>Spending the time to migrate everything.
Yes, that's a point. Would it be an alternative to spend time on cron
and cronie patching and packaging?
Greetings
Marc
-
option chanding deluser's default behavior
to not actually delete a --system account but lock it.
That way, a package can call deluser --lock in postrm for remove, and
straight deluser in postrm for purge, while leaving the final decision
what should happen with system accounts on purg
staller asking whether the user wants a free or a usable system?
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " |
said
nearly the same as Russ said.
>If this is going to be the solution, it has to be WAY easier to do.
Yes, absolutely.
Greetings
Marc
--
------ !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im
t will actually result in less
>non-free software being used overall, as will having the option to
>enable only non-free-firmware without also enabling non-free.
Those are the people who use Ubuntu without even trying Debian because
somebody told them that Debian is SO hard to insta
On Sat, 23 Apr 2022 13:54:59 +0200, Ansgar wrote:
>On Sat, 2022-04-23 at 12:21 +0200, Marc Haber wrote:
>> >Is the presence of shim-signed on the install media enough to make
>> >people feel somehow contaminated?
>>
>> I think so, yes. Personally, I don't car
ld time, the Debian process refrains
from putting a Debian signature on the deb and from uploading? Can the
end user build the shim herself, remove the signature from the signed
shim and compare the binary, preferably in a documented way?
Greetings
Marc
--
--
ackage explicitly.
That sounds nice and it's probably good to avoid accidental mass
removals, but it makes the "manual" mark kind of a misnomer.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions ar
that can boot and install debian without needing the
firmware blob is already one step better than a machine that needs an
install medium with firmware.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions ar
networking to work to get the
>drivers I need for the network card.
PXE boot will work and load a kernel and a doctored initrd that
contains the non-free firmware. Been there, done that, for thousands
of machines.
It would be so nice if Debian would offer such an initrd
/users-and-groups.txt.gz says that no files
should ever be owned by nogroup, making adduser do the right thing in
its current state.
Can you come up with a better default for users created with adduser
--system without requesting a dedicated group?
Gree
ystem user should end up in the
users group automatically even if it has its own group created, making
adduser's behavior regarding the users group independent of whether
usergroups are used or not.
What do you think?
Greetings
Marc
P.S.. If adduser gets changed, I will file a bug against base-pas
Package: wnpp
Severity: wishlist
Owner: Marc Haber
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: journal-brief
Version : 1.1.8
Upstream Author : Tim Waugh
* URL : https://github.com/twaugh/journal-brief
* License : GPL-2+
Programming Lang
On Wed, 06 Jul 2022 15:21:03 -0400, Matt Barry
wrote:
>On Mon, 2022-07-04 at 09:12 +0200, Marc Haber wrote:
>> adduser has been putting newly created 'dynamically allocated system
>> users' (adduser --system) into the nogroup group. It is also
>> documented to
On Thu, 14 Jul 2022 12:54:52 +0100, Steve McIntyre
wrote:
>And I see you uploaded ~immediately - why even bother with an ITP?
Is it proper procedure to upload without an ITP?
--
-- !! No courtesy copies, please !! -----
Marc Haber | " Quest
g default, and is
in line with most other major distributions, the adduser team considers
the matter to be settled; any further discussion should come prepared
with rationale, support, convincing use cases and a signif
vice once we
start shipping needed firmware on official media.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " |
not have a group for all users at all
- --add_extra_groups is now --add-extra-groups for consistency of
option spelling (old spelling still allowed, but deprecated)
- there is now a --firstgid and a --lastgid option to influence the GIDs
chosen for usergr
n this case, an exception might be warranted, but we need to have the
long explanation somewhere in the package for the next round of this
issue that is expected in the 2030ies.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | &qu
On Wed, 27 Jul 2022 16:10:18 +0200, Wouter Verhelst
wrote:
>On Mon, Jul 25, 2022 at 07:06:59PM +0200, Marc Haber wrote:
>> I don't like the idea of messing with old NEWS entries at all.
>
>I'm trying to understand why you feel this way.
It feels like rewriting history.
xtremely confusing to
>users, and an epoch is *hidden* from them.
... because it has been totally confusing to me since I started using
Debian that epochs are not always shown.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc H
s in binNEW to inspect them for bugs in debian/copyright?
Of course, that would just circumvent the decision of the project and
not gain us anything.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the
ing a routine
>update/upgrade cycle on the morning after the upload. I don't think
>everyone running testing/unstable reads debian-devel, so I think it
>would be appropriate to send to -announce at least one (two?) day(s)
>before the upload.
And, is there a solution
On Mon, 28 Nov 2022 15:50:56 +, Benjamin Drung
wrote:
>On Tue, 2022-07-19 at 08:49 +0200, Marc Haber wrote:
>> We implemented that change last week, and promptly a bug report
>> (#1014901) appeared, giving what we consider good arguments to change
>> this back to 0
after all?)
It is. We need to stop having "disable IPv6" as measure 1 if something
doesn't work right. It's the default IP protocol for a decade.
Greetings
Marc
--
------ !! No courtesy copies, please !! -
Marc Haber | " Qu
On Mon, 2 Jan 2023 17:08:25 +0100, Paul Gevers
wrote:
>Hi Marc,
>
>On 02-01-2023 16:58, Marc Haber wrote:
>> On Mon, 2 Jan 2023 16:31:17 +0100, Paul Gevers
>> wrote:
>>> On 02-01-2023 14:21, Alessandro Vesely wrote:
>>>> A user complained that MySQL
2. i just don't think this belongs in the
>installer anymore.
Amen. NIS-based systems usually have professional administrators who
are well able to change the configuration.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Ha
end it
wholeheartedly, but we need more automation for that.
Debian's way to handle conffiles is the best the Linux world has. That
doesn't mean that we don't have room to improve. And sadly, we haven't
moved a single inch here in 15 years.
Greetings
Marc
--
---
t;> even less so when it comes to the year-information.)
Amen.
While I understand that having debian/copyright is vitally important,
we NEED to relax our rules to reduce the effort necessary since it's
demotivating busy work that I feel noone cares about.
Greetings
Marc
--
--
relay side, and then announced EOL for
the server for end of 2022, leaving the world without the reference
implementation.
This is really bad.
Grüße
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mai
be the more natural tool to use for this, but this is a
different tool that needs different knowledge, and it's tooling is way
behind what we have with docker.
So, +1 to be able to run a default systemd-based Debian with systemd
as pid 1 in a docker container.
Greetings
Marc
--
--
en you start your Debian without the "quiet splash"
boot option and shut it down with "sudo shutdown -h now"?
Greetings
Marc
ocal and valid decision of $DAYJOB, which includes accepting
the results. Preseeding could be an option to override the debconf
default for a noninteractive install.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Que
On Sat, 7 Mar 2020 23:02:23 +0100, Marco d'Itri wrote:
>There is:
>
># systemctl mask $DAEMON.service
># apt install $DAEMON
>
>That's it. If the package fails to install then file a bug.
For that you need to know how the $DAEMO
u.com/questions/74061/install-packages-without-starting-background-processes-and-services#
This is indeed bordering between incredibly funny and disturbing.
Alas, it's a golden example for the quality of answers one gets in the
Ubuntu universe.
--
------ !! No
p package (the tool
>for building the base filesystem).
>
>that is to use dpkg-divert to temporarily replace the /sbin/start-stop-
>daemon binary with something that essentially just exits with success
>(i.e. 0).
debootstrap's files don't contain the string "divert". They
h vi to fix a broken system so far that it can again
start an Editor.
I then converted ot be a vim user in 2017.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im
he firmware manually. Doing this will most probably solve
your issue with current Debian as well.
The best idea is to change to a Wifi adapter that has better support.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber
s are handy to have on a "normal" system, but that
>is the point: If I want to look at them, I want to do that 99,9% of the
>time on a normal system, not on a single-purpose minbase(based) one –
>where I don't even have a sane editor available (SCNR).
Amen.
Greeting
d the point-and-drool interface to client
certificates, one needs to manually meddle around with OpenSSL to be
able to log in.
Is this going to stay this way?
Greetings
Marc, who thankfully has still one single machine where the client
cert has not expired yet
--
ing our reputation.
We do provide a rock solid base system where people can install their
software, in the case of those fast moving things in the way upstream
wants them to. This causes a much better result for all those
involved.
Greetings
Marc
--
-- !! No
On Thu, 26 Mar 2020 09:39:56 +1100, Dmitry Smirnov
wrote:
>On Thursday, 26 March 2020 3:45:21 AM AEDT Marc Haber wrote:
>> Software packages like kubernetes, docker, and many of the other "hip
>> tools of the day" are moving way too fast for our release scheme.
>
&
On Thu, 26 Mar 2020 20:22:18 +1100, Dmitry Smirnov
wrote:
>On Thursday, 26 March 2020 7:27:33 PM AEDT Marc Haber wrote:
>> I still wouldn't dare pulling testing or unstable packages to
>> production systems. It's like a worst-of-all-worlds approach.
>
>Not at all.
On Sat, 28 Mar 2020 12:41:46 +1100, Dmitry Smirnov
wrote:
>On Friday, 27 March 2020 7:08:35 PM AEDT Marc Haber wrote:
>> Many upstreams deliver .deb packages of their current releases in
>> noticeably high quality from a Debian point of view. One should look
>> at them b
On Sun, 5 Apr 2020 23:16:51 +0100, Wookey wrote:
>On 2020-04-05 21:15 +0200, Marc Haber wrote:
>> having an obsolete version of the software distributed
>> with/through Debian is (rightfully) seen a liabilty by some upstreams,
>> not as an asset.
>
>I think a more int
On Mon, 23 Mar 2020 08:49:44 +0100, Enrico Zini
wrote:
>On Mon, Mar 23, 2020 at 08:10:18AM +0100, Marc Haber wrote:
>> While we're at thiss, what is the tracker.d.o authenticating against?
>> Since Firefox has removed the point-and-drool interface to client
>> certifica
urself if you believe that you'd get full security
support for a two years old kubernetes release in Debian stable.
The utmost you'd get would be an occasional security fix where an
upstream fix would get _flagged_ as security relevant _AND_
coincidentially backportable to our version.
h that software professionally might probably not
need the level of upstream support that Joe B. Debianuser needs.
Greetings
Marc
--
------ !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannh
ides zero benefit, and they could get the same "stability"
>guarantee by just keeping a copy of a two year old third party .deb and
>never updating it.
What Michael says.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber
, that's not the plan!
A package without upstream support is bound to be a zombie. We don't
have the resources to provide support on the same level like an actice
upstream community does.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
On Fri, 24 Apr 2020 10:53:52 +0200, Jaros?aw K?opotek
wrote:
>Please give me link to BTS.
https://lmgtfy.com/?qtype=search&t=w&q=debian+bts&as=0&s=g&engine=&media_type=
--
-- !! No courtesy copies, please !! -
Marc Haber
dual members directly. That's a telltale sign of a
dysfunctional org.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom &qu
ebian.org/919619
>How to switch to iwd:
>
>apt install iwd
>cat << END > /etc/NetworkManager/conf.d/iwd.conf
>[device]
>wifi.backend=iwd
>END
>systemctl restart NetworkManager
Does iwd have a clickable frontend like for GNOME or KDE?
Greetings
Marc
--
---
Package: wnpp
Severity: wishlist
Owner: Marc Haber
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: gensio
Version : 2.1.5
Upstream Author : Corey Minyard
* URL : https://github.com/cminyard/gensio/releases
* License : GPL2
Programming Lang: C
On Sat, 09 Jul 2016 03:55:31 +0200, german...@ya.ru wrote:
>But if btrfs is so unstable, then what the hell it's doing in Debian Stable's
>kernel?
Because people might want to try it.
Grüße
Marc
--
-- !! No courtesy copies, please !!
stem. The
effect on the system's other seervice is severe up to "sit back and
wait until system becomes responsive again".
That's not what I'd call production ready. It's simply just betafs at
the moment.
Greetings
Marc
--
--
out stating your
name.
You're coming across as a troll otherwise.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning o
nst using
btrfs in productive environments, even if it's from the latest and
greatest kernel.
>>think about stating your name.
>
>My full name is Davidyants Vazgen Samsonovich. Are you happy now?
Happier at least. I think it's polite to introduce oneself.
Greetings
Marc
On Mon, 11 Jul 2016 22:29:20 +0200, Philipp Kern
wrote:
>On Mon, Jul 11, 2016 at 08:07:20PM +0200, Marc Haber wrote:
>> [1] I remember the day when a Debian stable point release introduced a
>> new version of an ethernet driver that broke an entire class of IBM
>> blade se
dvantages of systemd-networkd over ifupdown since it's
friendly to configuration management systems.
Greetings
Marc
--
------ !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Ge
27;t say "every Debian system" to
>> me.
>Sorry, what I actually meant was "every non-toy Debian system".
Please at least try to be not this derogatory.
--
-- !! No courtesy copies, please !! -
Marc Haber | "
nit systems.
And because it's a system-wide decision.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http
s
as "fixed in NMU" get changed to "closed"?
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " |
to do the former nine years ago though. I stopped
caring back then.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom
to do them again when policy finally gets a
move here.
I want a clear TC decision or policy.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany
n I noticed that this puts
downstream distributions that enjoy taking from Debian without
recognizing their ancestor in jeopardy. Part of me actually likes
that.
Greetings
Marc
--
------ !! No courtesy copies, please !! -
Marc Haber | " Questions a
ill uploader for the most prominent package in
Debian using the Debian-foo scheme, and I also remember having written
a document outlining the decision we as a team made thirteen years
ago. I have to admit that I didn't include that document in the
package
On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg
wrote:
> [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day
> migrations)
Does this really mean "once you're out, you'll stay out"?
Greetings
Marc
--
--
On Sun, 06 Nov 2016 09:38:00 +, Niels Thykier
wrote:
>Marc Haber:
>> On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg
>> wrote:
>>> [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day
>>> migrations)
>>
>> Does t
t;people behind it, and the way they acted in the past months.
This is exactly the problem I have with the current policy: I fail to
see why this measure will shorten the freeze.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber
ackage maintainers even more.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by N
to the
responsibilities they have taken voluntarily? Well, _this_ will
clearly motivate people.
Greetings
Ma "not." rc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim,
s the KDE
team doing bug triaging? There are less important packages where the
maintainer has been searching for help to work in a team for years
without success.
And instead of relieving those people, they now get responsible for
their dependencies as well if their mai
red to speak up when
you didn't like what we did, so you're free to take a hike with your
package, have a nice day".
I find that unnecessarily humiliating and will probably not do this
and rather live without my package in stable for this release.
Greetings
Marc
--
when it's ready" to "we'll sacrifice package list completeness
of our release for a timely release", which is a rather radical
change.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions
ls, I am strongly opposed
against the "once you're out, you'll stay out" since I fail to see the
advantages of this approach aside from "giving incentives".
For me, this "incentive" will most likely have the opposite res
ch haven't worked. The approach of "let's freeze and
>then try to fix things" didn't work. Let's not try it again.
I do not think that it is a service to our users to release an
incomplete distribution just for the sake of keeping a date.
Greetings
Marc
--
-
On Sun, 06 Nov 2016 11:51:36 +, Steve McIntyre
wrote:
>Releasing Debian is work for all of us, not just the Release Team...
So you are actually suggesting that people who are neither on the
release team nor maintaining a key package are not working?
Greetings
M
1301 - 1400 of 1914 matches
Mail list logo
