On Thu, Jul 21, 2022 at 08:54:20AM -0700, Brett Cornwall wrote:
> On 2022-07-21 10:15, David Runge wrote:
> > Hi all,
> >
> > I'm currently partly moderating mailing lists for Arch Linux.
> > Since we've switched to mailman3 I receive *a lot* of info from the
> > system, that mails are being held
On Tue, Sep 20, 2022 at 08:14:47PM +0200, Pierre Schmitz wrote:
> Hi all,
>
> I have been thinking about refocusing my contributions on Arch. As
> Andreas rightfully asked about openssl it's probably best to go ahead.
> I have been maintaining a couple of packages simply because they where
> orpha
On Sun, Dec 11, 2022 at 08:46:07PM +0100, Andreas Radke wrote:
> I have noticed freswa has bumped BerkeleyDB to
> v6 (again) and started pushing rebuilds to staging repo.
I've checked every affected package for it's license:
389-ds-base:
GPLv3+
https://github.com/389ds/389-ds-base/blob/main/
On Mon, Dec 12, 2022 at 07:14:42PM +0100, Balló György wrote:
> 2022. 12. 12, hétfő keltezéssel 17.16-kor Frederik Schwan ezt írta:
> > As far as I understand, the main concern is linking GPLv2 against
> > AGPLv3.
> > Thus I'd propose to create db5.3 f
On Wed, Dec 14, 2022 at 10:56:30AM +0100, Pierre Schmitz wrote:
> What is the latest news on this? I noticed PHP was patched for db-6
> and later on db support was removed completely. Will the db/db5
> package be dropped entirely?
I removed db support where it seemed like a proper solution. For PH
Glibc 2.37 is about to be released to [testing].
Please be aware that any package that links against the 2.37 libc has to stay in
testing for as long as glibc stays there. Otherwise breakage will be imminent.
Best regards,
Frederik
signature.asc
Description: PGP signature
Hi everyone,
As you might have heard by now redis got a new license and *some* forks were
created [1].
Valkey as one of them is developed by the Linux Foundation, and adopted by
Fedora already [2].
So we think it's a good step to follow that path and replace redis by valkey.
--
# Valkey to
Hi everyone,
as discussed in the Matrix packaging channel, the upcoming glibc move from
testing to stable
will break audio connectivity for Discord clients. Discord has fixed the issue
in their canary build
and has communicated an eta for the fix in stable for 2025-02-10. As the glibc
update ho
I just pushed glibc 2.41 to testing. Do not move packages linked against 2.41
to extra or core until glibc itself moves around Sunday/Monday.
Otherwise the package will probably break.
Best regards,
Frederik
signature.asc
Description: PGP signature
On Sun, Feb 02, 2025 at 02:43:25PM +0100, Frederik Schwan wrote:
> Hi everyone,
>
> as discussed in the Matrix packaging channel, the upcoming glibc move from
> testing to stable
> will break audio connectivity for Discord clients. Discord has fixed the
> issue in their cana
On Sun, Feb 02, 2025 at 11:22:20PM +0100, gromit wrote:
> On 25/02/02 02:43PM, Frederik Schwan wrote:
> > # Glibc 2.41 corrupting Discord installation
> >
> > Glibc and it's friends will move from testing to stable on approx.
> > 2025-02-03. After installing the
m the [extra] repo.
> or
> 2. from the moving to the [extra] repo, the AUR redis package will also
> not
> receive updates in the future, and should be considered deprecated until
> it
> is removed from AUR in the future.
>
> Which explanation is this
On Fri, May 02, 2025 at 05:04:51PM +0200, Bert Peters wrote:
> Hi all,
>
> A while ago we as a distro decided to stop supporting Redis, due to
> their licence change [1], and move to Valkey. Through a combined
> effort, we removed all direct dependencies on redis, replacing them
> with vault and p
On Wed, Feb 26, 2025 at 09:53:50PM +0100, Jelle van der Waa wrote:
> Hi All,
>
> After all the recent RISC-V news I went ahead and checked out the existing
> effort to get Arch Linux supported on RISC-V. Felix maintains an overlay of
> PKGBUILDs which require customization to be be able to build o
Hey all,
below is the news item I would like to post. We had to change some
mailing list ids which used to be @archlinux.org to @lists.archlinux.org
to mitigate anti spam issues. Sending to @archlinux.org still works
as usual though.
```
Due to issues with our anti spam measures, we had to migrat
On Fri, Jan 21, 2022 at 11:32:59AM +0100, Jelle van der Waa via arch-dev-public
wrote:
> Hello,
>
> Noticing that I don't really have time and energy to maintain a part of my
> packages. I think it's better to disown them and let others take care of
> them, the list is:
>
> chromium-bsu
> guetzl
On Mon, Jan 31, 2022 at 09:25:41PM +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.
>
>
On Mon, Feb 07, 2022 at 12:26:54PM -0300, Giancarlo Razzolini via
arch-dev-public wrote:
> Hi All,
>
> Most of you are aware that our toolchain is currently outdated. We always had
> very few people
> working on it through the years and I took over once Barth left, because it
> was needed.
>
>
18 matches
Mail list logo
