requires write access to the repository error

:pserver: protocol allows two types of authorization and access
control.
1. UNIX rights
This is by default. You login as specific user and will have the same
rights for repository as this user. To make possible several users
work with this repository they included into specific group (for
example "cvsusers"), and this group used as owner group for
repository. Your admin should be able to setup this easily.
2. build in pserver support
In this case system account is used to access repository (root). You
can define "virtual" users and password. Check the info below for
details:
--------------------------------------------------------------------
Because the client stores and transmits passwords in cleartext (almost--see
Password authentication security, for details), a separate CVS password
file may be used, so people don't compromise their regular passwords when
they access the repository. This file is $CVSROOT/CVSROOT/passwd (see
Intro administrative files). Its format is similar to /etc/passwd, except
that it only has two or three fields, username, password, and optional
username for the server to use. For example:
bach:ULtgRLXo7NRxs
cwang:1sOp854gDF3DY
The password is encrypted according to the standard Unix crypt() function,
so it is possible to paste in passwords directly from regular Unix passwd
files.
When authenticating a password, the server first checks for the user in the
CVS passwd file. If it finds the user, it compares against that password.
If it does not find the user, or if the CVS passwd file does not exist,
then the server tries to match the password using the system's user-lookup
routine (using the system's user-lookup routine can be disabled by setting
SystemAuth=no in the config file, see config). When using the CVS passwd
file, the server runs as the username specified in the third argument in
the entry, or as the first argument if there is no third argument (in this
way CVS allows imaginary usernames provided the CVS passwd file indicates
corresponding valid system usernames). In any case, CVS will have no
privileges which the (valid) user would not have.

The answer depends on protocol you use to access CVS server. Which
protocol you use (:local: :pserver: :ssh:).