On 2021-01-21 14:08:11 (+0100), Bartłomiej Piotrowski via arch-dev-public wrote:
> Hi everyone,
>
> I'm stepping down as a developer. It's been mostly fantastic ride for
> the last 10 years but it's clear to me now that for better or worse it's
> far from the project I initially joined.
>
> Thank
Hi!
I have just upgraded postfix to 3.5.9.
The package has been split to allow specific installations based on
requirements while not pulling in all of the backends at once:
postfix
postfix-cdb
postfix-ldap
postfix-lmdb
postfix-mysql
postfix-pcre
postfix-pgsql
postfix-sqlite
Please do test the i
On 2021-01-26 22:18:21 (+0100), Levente Polyak via arch-dev-public wrote:
> On 1/26/21 9:53 PM, Morten Linderud via arch-dev-public wrote:
> >
> > It's dissapointing frankly.
> >
>
> Disappointing doesn't really catch it tho. If it would be just about the
> sync functionality: so be it. But crip
On 2021-01-27 08:45:53 (-0300), Giancarlo Razzolini wrote:
> If google drops the api key, yes. They said we can continue using
> them, but we don't know for how long, and they also mentioned
> reviewing quotas, which would render them unusable.
We don't have any specifics, so we will have to wait
Dear staff,
I have begun work on a Request for Comment (RFC) process for Arch Linux
and I am excited to now be able to open the first RFC... to introduce
"Using RFCs" :)
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/1
Please v
Hey all,
it has been roughly two weeks since my first mail and the discussions we
have had via comments on the RFC merge request have concluded. Thank you
all for your improvement suggestions and feedback!
This first RFC is rather special, as it is meant to bootstrap the
process and introduce it
On 2021-02-16 13:38:06 (-0300), Giancarlo Razzolini via arch-dev-public wrote:
> > Gitlab is going to be opened within the next months and we have
> > users on Gitlab today. It's not limited to staff.
True, but as we enforce the access rights to all of our repositories,
we can change that if the n
Hey all,
I'll be away for about a week for holidays.
If anything urgent comes up, feel free to bump or fix my packages.
Best,
David
--
https://sleepmap.de
signature.asc
Description: PGP signature
Dear all,
Jonas and I have been working on changes to our Code of Conduct, which
are represented in the following merge request:
https://gitlab.archlinux.org/archlinux/service-agreements/-/merge_requests/11
While most changes are based on e.g. merging sections or moving topics
to separate docum
On 2021-07-14 13:58:07 (+1000), Allan McRae via arch-dev-public wrote:
> I just read the document as it stands after your proposed changes. My
> conclusion was it is too long, often explained points in too much
> detail, and was too long!
I agree. The current work focusses mainly on splitting out
Hey all,
I made a dodo this morning by accidentally adding a TODO for a
fluidsynth rebuild [1].
The rebuild can only be done after the hdf5 rebuild [2] is done, due to
overlap. I will re-open it once we can proceed.
Sorry for the noise.
Best,
David
[1] https://archlinux.org/todo/fluidsynth-220-
On 2021-07-23 10:48:19 (+0200), Antonio Rojas via arch-dev-public wrote:
> El viernes, 23 de julio de 2021 10:28:42 (CEST), Archange via
> arch-dev-public escribió:
> > Please mind that here is already an (intel-)tbb rebuild waiting for the
> > hdf5 one to finish. As well as a VTK one, but since I
Hi all,
I'll be away for about two weeks and likely not be super active
packaging.
There are a few TODOs for rebuilds [1][2][3] that I have started, which
I may be able to move, but probably not be able to further help rebuild
at the moment.
Feel free to rebuild out-of-date packages. Note, that
On August 21, 2021 9:24:20 PM GMT+02:00, Jelle van der Waa via arch-dev-public
wrote:
>I would love to see someone from our team pick up namcap maintainership,
>take a look at all the pending patches, bugs on the tracker and keep it
>in shape. Is anyone interested in potentially picking up thi
On 2021-08-30 22:35:39 (+0200), Pierre Schmitz via arch-dev-public wrote:
> Thanks for looking into this. It's still weird but let's see if it
> will happen again. I hope it wasn't a memory issue and we can just
> blame Allan. ;-)
Unfortunately this has happened before.
On 2021-04-06 I noticed th
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/6
Please visit the above link for discussion.
Summary:
The adoption of a distribution-wide Code of Conduct (CoC) helps to
describe the social contract by which communication takes p
An RFC has now entered Final Comment Period. In 14 days, discussion will
end and the proposal will either be accepted, rejected or withdrawn:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/6
Please visit the above link for discussion.
Summary:
The adoption of a distribution-wide Co
On 2021-10-08 09:44:56 (+1000), Allan McRae via arch-dev-public wrote:
> On 7/10/21 1:41 am, Sven-Hendrik Haase via arch-dev-public wrote:
> > On 06.10.21 12:47, Allan McRae via arch-dev-public wrote:
> >> On 27/9/21 4:33 am, David Runge via arch-dev-public wrote:
> >&
Hi Pierre,
On 2021-11-01 15:32:51 (+0100), Pierre Schmitz via arch-dev-public wrote:
> I did have some trouble build the current ISO image. As archiso
> requires to be run as root I had to work around some issues with GPG.
> As those did no longer work I thought I manually sign the artifacts.
> Th
On 2021-11-01 18:49:48 (+0100), Pierre Schmitz via arch-dev-public wrote:
> On Mon, Nov 1, 2021 at 5:10 PM David Runge wrote:
> > ... use an ephemeral PGP key (which is fine, as
> > it is not relevant whether it is a specific PGP key, only that the
> > *correct* PGP key is used to validate the roo
On 2021-12-06 16:11:45 (+0100), Pierre Schmitz via arch-dev-public wrote:
> Hi all,
>
> a little heads up as it takes longer than expected. I'll start the PHP
> 8.1 update and the required rebuilds soon. I noticed some unexpected
> incompatibilities and I'd like to look into these first. I'll also
On 2021-12-06 17:58:57 (+0100), Levente Polyak via arch-dev-public wrote:
> On 12/6/21 17:48, David Runge via arch-dev-public wrote:
> > On 2021-12-06 16:11:45 (+0100), Pierre Schmitz via arch-dev-public wrote:
> > > Hi all,
> > >
> > > a little heads up as
On 2021-12-06 18:32:49 (+0100), Pierre Schmitz via arch-dev-public wrote:
> In general we could provide PHP 7 till its end of life in about eleven
> months. But I don't think its worth providing several different minor
> versions at the same time.
I agree.
> This is not how semver is supposed to
Thanks for taking care of this!
It generally looks good, but I would replace
> If you get errors like these
with
"If you get errors such as the following"
Best,
David
--
https://sleepmap.de
signature.asc
Description: PGP signature
Hi all,
in the past days there have been a few releases of our archlinux-keyring
package, which contains the root trust of our distribution.
We have successfully switched to using keyringctl [1] to manage the
keyring. From now on all changes to the keyring are done via merge
requests towards the
On 2022-01-14 16:57:00 (-0800), Brett Cornwall via arch-dev-public wrote:
> On 2022-01-14 21:12, David Runge via arch-dev-public wrote:
> > To all that have added a new @archlinux.org UID or have created a new
> > key, please make sure that all signatures you have received from m
On 2022-01-16 16:40:00 (+0100), Pierre Schmitz via arch-dev-public wrote:
> So far everything looks fine. I am even using PHP 8.1 in production
> for a week now, without any issues. So I'd like to move the packages
> to [extra].
>
> The remaining blocker is nextcloud though. What is the best opti
On 2022-01-16 17:11:44 (+0100), Pierre Schmitz via arch-dev-public wrote:
> Thanks! Let me know if I may support you.
It went quite okay (but I had to remove parts of the patch series as
they apply to files that we do have in our tarball).
nextcloud 23.0.0-2 is now in [community-testing].
As ups
On 2022-01-21 17:51:17 (+0100), Pierre Schmitz via arch-dev-public wrote:
> I just released PHP 8.1 into [extra].
>
> Please also check https://archlinux.org/todo/php-7-retiredment/ so PHP
> 7 can be dropped soon.
>
> have a nice weekend,
Unfortunately, it likely won't be ;_;
https://bugs.archl
Hi Pierre,
On 2022-01-22 20:45:45 (+0100), Pierre Schmitz via arch-dev-public wrote:
> sorry about the hassle. I did not expect much issues here. I would
> consider this one of the smoother PHP updates. Unless people ignored
> warnings by previous PHP versions. I guess that is what mostly happend
On 2021-05-22 00:44:13 (+0200), Andrzej Giniewicz via arch-dev-public wrote:
> my away time got longer than I expected (announced October 2020). Due
> to pandemic I still have no access to my Arch machine. I will get back
> access to it mid July, so this is not a resignation from my TU role!
>
> T
On 2022-01-29 13:11:05 (+0100), Morten Linderud via arch-dev-public wrote:
> * Signing enclave
> * Better rebuilding tools
> * Build automation
> * Git migration
>
> It would make discussions like these completely obsolete. Do we want
> v2, v3, v4, v5, v90001? Enable it in a setting and we'd have
On 2022-01-30 12:13:45 (+0100), Morten Linderud via arch-dev-public wrote:
> ALARM has refused to join the project because of our ancient tooling.
Case in point. :)
--
https://sleepmap.de
signature.asc
Description: PGP signature
Hi all,
given recent topics for build automation and work on internal projects I
would like to announce a code walkthrough for arch-repo-management [1].
I would like to give an overview of the scope of the project, its
current features and which features I would like to see implemented
(some of w
On 2022-01-31 14:23:10 (+0100), David Runge via arch-dev-public wrote:
> The meeting will take place on Jitsi
> https://meet.jit.si/20220202-arch-repo-management
>
> on 2022-02-02 starting around 19:00 CET (UTC+01:00).
>
> Any changes to the date and/or location will be anno
On 2022-01-31 23:55:07 (+1000), Allan McRae via arch-dev-public wrote:
> Any chance this can be recorded? It will be at 4am in my timezone?
I think that can certainly be arranged!
> I am interested in mainly what problem this is solving. From what I
> can tell, our current workflow is package->
On 2022-02-02 12:40:56 (+0100), Morten Linderud via arch-dev-public wrote:
> # Signed SHIM
>
> First of we need to have a signing solution for this. My idea has been to
> piggy-back on the existing work on the signing-enclave. However it's current
> focus is GnuPG and I need something which can su
On 2022-01-31 14:23:10 (+0100), David Runge via arch-dev-public wrote:
> given recent topics for build automation and work on internal projects I
> would like to announce a code walkthrough for arch-repo-management [1].
>
> I would like to give an overview of the scope of the
Hi all,
as announced on arch-dev-public, we would like to do bi-weekly meetings
for arch-repo-management [1].
I misjudged the (current) use-case for the arch-projects mailing list
though and therefore am doing the meeting announcement here.
I will send another mail to discuss the current/future s
Hi all,
while trying to use the arch-projects mailing list for an announcement I
realized, that it is (probably?) not really supposed to be used for
that at the moment.
It explicitly states to be used for development discussion and providing
patches for dbscripts, devtools, mkinitcpio, namcap, ne
On 2022-02-03 22:07:09 (+1000), Allan McRae via arch-dev-public wrote:
> On 3/2/22 21:53, David Runge via arch-dev-public wrote:
> > Unless there are any objections, I propose to
> >
> > * add arch-repo-management and arch-release-promotion to it
> > * change arch-
On 2022-01-31 21:25:41 (+0100), Jelle van der Waa via arch-dev-public wrote:
> We’ve wanted automatic flagging packages out of date for a while and
> currently every packager has to come up with it’s own solution. Let’s
> solve this centralized by integrating nvchecker into archweb.
One thing that
Hi all,
as mentioned mid January [1] we are currently en-route to deprecating
Allan's main signing key [2].
For this purpose I have added 11 rebuild TODOs for packages signed by
packager keys that have been superseded by newer ones (and should then
also be removed). These packages need to be rebu
Hi all,
I'll be away for most of March and beginning of April.
I still have time sporadically over the next week but will likely not be
available for packaging or other things afterwards until the beginning
of April.
Feel free to upgrade packages that are out-of-date while I'm away.
Best,
David
Hi again,
after waiting another couple of weeks, the situation with nextcloud
unfortunately has still not improved.
We see issues with utf-8 compatibility [1] and meanwhile the version
24.0.0 which is supposed to provide native support for php 8.1 is being
delayed until end of April [2].
This all
On 2022-03-16 17:09:59 (+0200), Felix Yan via arch-dev-public wrote:
> certbot
> certbot-apache
> certbot-dns-cloudflare
> certbot-dns-cloudxns
> certbot-dns-digitalocean
> certbot-dns-dnsimple
> certbot-dns-dnsmadeeasy
> certbot-dns-gehirn
> certbot-dns-google
> certbot-dns-linode
> certbot-dns-lu
On 2022-04-06 15:49:54 (+0200), Luna Jernberg wrote:
> Hey!
> Will miss the meeting today, and missed the one 2 weeks ago (if there was
> one?)
> But would gladly read the writeup or see a recording when i have time
Hi!
Yes, see the mail on archlinux-projects [1]. However, I might be a few
minute
Hi all,
with qemu 7.0.0 now in [staging] we have a more extensive split package
setup (see accompanying TODO [1]). Under certain circumstances this will
require manual intervention (or rather a specific upgrade) to regain the
previous functionality:
```
With the update to qemu 7.0.0 the package h
On 2022-04-21 23:20:32 (+0200), David Runge via arch-dev-public wrote:
> with qemu 7.0.0 now in [staging] we have a more extensive split package
> setup (see accompanying TODO [1]). Under certain circumstances this will
> require manual intervention (or rather a specific upgrade) to r
On 2022-04-22 10:52:06 (+0200), Jan Alexander Steffens (heftig) wrote:
> On Fri, Apr 22, 2022 at 10:38 AM David Runge via arch-dev-public <
> arch-dev-public@lists.archlinux.org> wrote:
>
> > The `qemu` package now only carries a few common files and tracks all of
>
On 2022-04-22 11:07:26 (+0200), David Runge via arch-dev-public wrote:
> On 2022-04-22 10:52:06 (+0200), Jan Alexander Steffens (heftig) wrote:
> > I'm still unhappy with `pacman -S qemu` not doing anything useful. Maybe we
> > could name that `qemu-misc` or `qemu-common` inst
On 2022-03-08 13:56:04 (+0100), David Runge via arch-dev-public wrote:
> after waiting another couple of weeks, the situation with nextcloud
> unfortunately has still not improved.
> We see issues with utf-8 compatibility [1] and meanwhile the version
> 24.0.0 which is supposed to pr
On 2022-04-24 19:08:37 (+0200), Pierre Schmitz via arch-dev-public wrote:
> I'd still suggest to provide two different php versions as mentioned
> some time ago: the current "php" and "php-legacy" which will always be
> the oldest supported version. These may provide the versions as you
> suggested
On 2022-04-24 21:13:43 (+0200), David Runge via arch-dev-public wrote:
> On 2022-04-24 19:08:37 (+0200), Pierre Schmitz via arch-dev-public wrote:
> > I'd still suggest to provide two different php versions as mentioned
> > some time ago: the current "php" and &qu
On 2022-04-25 17:25:47 (+0200), David Runge via arch-dev-public wrote:
> And a note on the versioned provides (e.g. `php-apcu=7.4` for the
> current php7-apcu). I believe this should be done, but it would only
> prove useful if packagers then relied on two dependency contraints (I'
55 matches
Mail list logo
