+1 from me
Doing the `autoreconf -fiv` dance in basically all of my packages for quite a
while. We should standardize this. Every now and then some upstreams can't be
easily regenerated, but imo this is arguably an upstream bug that should be
resolved.
Cheers
Levente
On 2/7/25 4:11 PM, Sven-Hendrik Haase wrote:
Hey,
The git/community-to-extra migration was almost two years ago. Back
then, we left the [community] repository and friends ([community-
staging], [community-testing]) in place (though empty) so that users
would have an easier time migrating.
T
On 10/2/24 6:54 PM, Robin Candau wrote:
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/43
Please visit the above link for discussion.
Sum
On 11/13/24 5:53 AM, Sven-Hendrik Haase wrote:
Hey all,
There's been some discussion about this via chat but no action has been
taken. Some time ago, ollama-gemma2-2b was uploaded to [extra] which has
caused some discussion for various reasons.
Thank you very much for assembling the inform
We are excited to announce that Arch Linux is entering into a direct
collaboration with Valve. Valve is generously providing backing for two
critical projects that will have a huge impact on our distribution: a
build service infrastructure and a secure signing enclave. By supporting
work on a f
## Staff
### Project Leader Election
Recently, we held our [Arch Linux Project Leader][0] election, and the
current Project Leader, Levente "anthraxx" Polyák, was the sole nominee.
As per our election rules, he has been re-elected for another term.
Congratulations to Levente, and we wish him
## Staff
We would like to welcome [Quentin Michaud][0] as part of the Arch Linux
Package Maintainer team.
## RFC
A previously proposed [Distribution Developer Manual RFC][1] has been
accepted with the intention to document how to run the distribution
while leveraging GitLab's collaboration
## Pacman
[Pacman v7.0.0][0] has been released as a major feature version. A new
`DownloadUser` configuration option allows for dropping privileges when
downloading files to a temporary directory. On top of this security
measure, the new Landlock sandbox also prevents writing outside the
rest
## archinstall
The [archinstall v2.8.1][0] update has been released, featuring several
bug fixes and improvements to partitioning and desktop profiles, along
with the introduction of experimental LVM support and the addition of
Finnish translation.
## ArchWeb
[ArchWeb 2024-06-12][1] has bee
## Staff
We would like to welcome [Bert Peters][0] (bertptrs) as well as
[Giovanni Harting][1] (anonfunc) as part of the Arch Linux Package
Maintainer team.
## RFC
An [RFC has been accepted][2] to introduce "Arch Linux Ports" as testbed
for unofficial architectures until they are integrated
## Staff
We would like to welcome [Carl Smedstad][0] as part of the Arch Linux
Package Maintainer team.
Furthermore, we would like to welcome svartkanin as Support Staff for
the archinstall project, assisting with issue tracking and handling of
merge requests.
### Project Leader Election
## Staff
We would like to welcome Vincent Dahmen (wahrwolf) as Arch Linux Support
Staff with their new role as Mirror Admin.
On top we would like to welcome [andreymal and codingkoopa][0] to their
new role as ArchWiki Maintainers.
Additionally, we would like to congratulate Christian Heusel
Sep 1, 2024 11:49:46 Morten Linderud :
> I think it's important to specify how the moderation capabilities are. Public
> paste services are *bounds* to be abused and can distribute malicious files
> and
> illegal files. This needs to be dealt with and should probably not cause too
> much friction
An RFC has now entered its 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/21
Please visit the above link for discussion.
Summary:
This RFC proposes the migration
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/21
Please visit the above link for discussion.
Summary:
This RFC proposes the migration of Arch Linux's operational distro
specifications from existing ArchWiki and other sources
## Staff
We would like to welcome [Vladimir LAVALLADE (Erus Iluvatar)][0] to
their new role as ArchWiki Administrator.
## Infrastructure
The DevOps team has recently provisioned a new EPYC 9454P build server
for Arch Linux packaging. This high-performance server is meant to
streamline the p
## Staff
We would like to welcome [Jakub Klinkovský (lahwaacz)][0] as part of the
Arch Linux Package Maintainer team.
## User meetup
During the [37th Chaos Communication Congress (37C3)][1], we hosted a
user meetup. At this event, we presented our latest achievements and
developments. Addit
## Arch Summit 2023
The Arch Summit took place in Hamburg, Germany, on November 4th and 5th,
bringing together Arch Linux staff and invited guests. The summit
provided an opportunity for the staff to connect, socialize, and delve
into discussions regarding various aspects of our distro.
A ra
## Staff
We would like to welcome [Christian Heusel (gromit)][0] to the Arch
Linux DevOps team, expanding his responsibilities.
## bugbuddy
The initial version of [Bugbuddy][1], our GitLab bug bot, has been
introduced. This tool assigns package maintainers to confirmed GitLab
issues in the
## Scope
Our primary goal is to migrate bugs.archlinux.org to GitLab, focusing on
packaging bugs and our internal projects. In this email, we'll outline
the workflow for packaging bugs and seek your assistance in testing the
migration and the bug bot in the [test migration
group](https://gitl
Hi all,
After resolving all known issues with our tooling and other projects, we
had a version in testing now for an extended period of time. After 15
additional signoffs, I've moved bash 5.2.015-5 to core.
bash 5.2 has arrived, may it create only small havoc.
Cheers,
Levente
OpenPGP_signa
## Staff
We would like to welcome [Fabian Bornschein (fabiscafe)][0] as part of
the Arch Linux Package Maintainer team.
## Bug weekend
During the 1st to 3rd of September, we conducted a [bug weekend][1] with
the aim of resolving old bugs and implementing proposed solutions. This
effort not
On 9/25/23 20:18, Levente Polyak wrote:
Hi all,
this is mostly a notification mail about some inconsistencies with
dbscripts where under specific circumstances some leftover packages
remain in staging or testing. This issue seems to exist since the last
major rollout in June.
There seem to
On 9/10/23 23:10, Jan Alexander Steffens (heftig) wrote:
An RFC has now entered its 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/23
Please visit the above link
Hi all,
this is mostly a notification mail about some inconsistencies with
dbscripts where under specific circumstances some leftover packages
remain in staging or testing. This issue seems to exist since the last
major rollout in June.
There seem to be at least two different bugs involved,
## Staff
We would like to welcome Tomaz Canabrava (tcanabrava) as part of the
Arch Linux Package Maintainer team.
## AURWeb
In [AURWeb v6.2.7][0], we primarily focused on bug fixes while revamping
Prometheus metrics. We introduced new measures like request tracking and
cache-hit/miss ratios
## Staff
We would like to welcome Mario Oenning (moson) as new Arch Linux Support
Staff Member.
## devtools
arch-nspawn is now utilizing a distinct scope name instead of the
previous `--keep-unit` approach. This allows for the creation of a
dedicated scope, placing the container within a sl
## packaging
We have now enabled all packagers to have default access to the multilib
and unstable desktop (GNOME/KDE) repositories. This decision removes
artificial gates and simplifies the process for packagers to contribute
to different aspects of the distro's packaging. By granting wider a
On 6/25/23 19:33, Morten Linderud wrote:
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/16
Please visit the above link for discussion.
Sum
## Staff
We would like to welcome Anton Hvornum (torxed) and Christian Heusel
(gromit) among the Arch Linux Package Maintainers.
On top we would like to welcome Leonidas Spyropoulos (artafinde) to
their new additional duties as Arch Linux Developer
## Git packaging
We are thrilled to annou
Jun 2, 2023 21:21:18 Antonio Rojas :
>> The bot will also set an “unconfirmed” label to new issues so bug
>> wranglers and packagers alike can see and filter whether a bug has
>> already been reproduced.
> > Does this mean bugs are no longer going to be triaged by a human bug
> > wrangler befor
Sounds good, +1 from me.
We used to have this to restrict and "gatekeep" what people add to multilib as
we don't want random lib32 libraries as leaf packages just for the sake of
having the lib32 libraries. But I think that doesn't really need a special
privilege group.
Let's simplify this 👍
We are proud to announce that the migration to Git packaging succeeded! 🥳
Thanks to everyone who has helped during the migration!
Package sources are now available on GitLab[0]. Note that the bugtracker is
still flyspray[1] and that merge requests are not accepted as of now.
We intend to open th
Hi all,
We just wanted to post a small status update:
Everything is going as planned so far. The most thrilling bits have been
finished successfully and we are ahead of schedule. So far only tiny things
popped up that we need to take care of 🥳
The Git packaging ecosystem including updated devt
On 5/19/23 11:36, Jelle van der Waa wrote:
Hi all,
I got my morning coffee ready and will now start disabling ssh/svn
access and stop our rsync endpoint.
For more details of the migration please read the announcement email. [1]
[1]
https://lists.archlinux.org/archives/list/arch-annou...@lis
On 5/12/23 16:59, Morten Linderud wrote:
To make this easy for us doing the migration please ensure that [testing] and
[staging] are empty or cleared before next friday.
Friendly reminder: please check your released packages and clear up
testing/staging repos if possible.
Cheers,
Levente
## project management
We've create a GitLab Board [0] to track all tasks related to project
management and project leadership. This Board allows us to visualize the
exact state of tasks using different lanes and labels, making it easier
to keep track of ongoing progress. Additionally, tasks wi
Hi everyone!
We're excited to announce that the rollout for our Git packaging
implementation is scheduled for Friday, May 19th. Please note that
packaging and mirror sync will not be possible during the rollout as
we'll need to shut down the services. We expect the services to be
available an
On 4/24/23 08:26, Laurent Carlier wrote:
Last week I fell from my bike and was diagnosed with a broken pelvis/ankle.
So for weeks I must stay on a bed for some weeks - and away from my main
computer.
I was not able to build amdvlk with last releases, so if some can fix it,
it'll be awesome.
I
We're excited to share that we're almost there with our Git packaging
implementation, and we need your help to push us over the finish line.
We're asking *every* package maintainer to test our proof of concept [0]
at least once. Your feedback is crucial to ensure that our system works
well bef
## Git packaging sources
We have improved a lot of pieces in `pkgctl` according to the feedback
from the sandbox environment. Most notably it is possible to provide
GitLab tokens via the `DEVTOOLS_GITLAB_TOKEN` environment variable, pass
nocheck to the build command for bootstrap builds, handl
## Git packaging sources
All major workflow and usability requirements for the `pkgctl` tooling
have been finished and a experimental `devtools-git-poc` package has
been put into the repositories. Furthermore the proof of concept sandbox
environment has been set up and rolled out to anyone int
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/17
Please visit the above link for discussion.
Summary:
Adjust packaging CFLAGS from -D_FO
## Git packaging sources
We have announced the state of the art of the Git packaging migration to
`arch-dev-public` [0] including a first item on our distro roadmap to
track the remaining effort [1].
We have prepared most of the necessary settings, configurations and the
corresponding machin
On 2/18/23 15:36, Jelle van der Waa wrote:
On 02/02/2023 01:45, Morten Linderud wrote:
Hi everyone!
Levente and I have been busy preparing a test environment for the new git
package workflow, which is going to replace the svn repository.
To test the new git package setup install `devtools-git-
## The wiki went dark 🌗
Thanks to the effort of Blake Wilson in completing the process [0][1]
previously attempted [2] by killertofus to add Extension:DarkMode [3],
it's lights out for ArchWiki!
All you creatures of the dark can now click on "Dark mode" in the user
menu to experience the soo
Quick addendum as it may not have been clear enough:
while only interacting with `pkgctl` and nothing else, you will operate
against an isolated sandbox environment.
Go nuts, here be dragons!
On 2/2/23 01:45, Morten Linderud wrote:
To test the new git package setup install `devtools-git-poc`
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/17
Please visit the above link for discussion.
Summary:
Adjust packaging CFLAGS from -D_FORTIFY_SOURCE=2 to -D_FORTIFY_SOURCE=3
for better fortification coverage
OpenPGP_signat
Hi all,
I'd like to inform upfront that now would finally be a good time to
implement the `base-devel` meta-package orthogonal to our already
existing `base` meta-package.
We haven't really pushed it for quite some time as nothing in
`base-devel` changed in the past. Now the situation looks
# Introduction
Behold, ~~winter~~ Git is coming. We've been working on and off to get
Git packaging sources ready for a while now. Today I'd like to outline
the final proposal regarding the action plan, workflow, tooling and also
the reason for a couple of decisions. Consider this as a late xm
## Git packaging sources
We made huge progress towards finally being able to
migrate from SVN to Git for package sources. The core
projects responsible for our package build, workflow and
release, namely dbscripts and devtools reached
production grade adjustments to achieve the transition [0][1].
On 11/13/22 19:37, David Runge wrote:
On 2022-11-13 17:42:27 (+0100), Jelle van der Waa wrote:
For packaging we now rely on external parties to keep the source code
hosted which can be a problem and some packagers want to search
through all our packages code. [1]
Currently we already archive so
On 11/10/22 20:05, Andreas 'Segaja' Schleifer wrote:
On 11/9/22 01:13, Levente Polyak wrote >
I have a few questions about the setup:
1. Who can create issues? Anyone or only people registered to the gitlab
or only staff?
Everyone, explicitly inviting the community as well.
I
On 11/9/22 17:34, Antonio Rojas wrote:
Hi,
Qtwebkit has been unmaintained for a long time (last release from annulen's
fork was almost 3 years ago) and is plagued with security issues by now. Most
consumers are either dead upstream, of they use it to provide optional
functionality that can b
Hello everyone,
Several times in the past I was thinking about a better
and more central way to keep track of ideas and
suggestions. We've encountered multiple times that
good ideas got lost because we never properly kept track
of them and only recognized after coming up with the
very same idea m
On 11/6/22 13:53, Andreas 'Segaja' Schleifer wrote:
To reflect these changes I would propose that we update our ruby package
guidelines with the new way that Felix found.
I took the liberty of updating them on my personal space [2]. If there
is no objection, then I would like to push the chang
## mkinitcpio
mkinitcpio v32 has been released [0] which adds support for zst
compressed firmware for future kernel versions as well as various fixes
and adjustments.
## pacman
pacman 6.0.2 has been released [1] which fixes multiple issues with
debug packages. On top pacman-key has been adjust
On 10/25/22 17:49, Evangelos Foutras wrote:
On Tue, 25 Oct 2022 at 12:15, Evangelos Foutras wrote:
If the above approach seems good, please commit the updated PKGBUILD
to svn. We'll then start the rebuilds on [1] and see how they go.
Slight change of plans, Jan is going to push GNOME 43 first
On 10/7/22 13:35, Jelle van der Waa wrote:
...
This all needs some further debugging :)
Thanks a lot for the detailed info. I've done additional rounds of
testing using the latest pacman patches [0]:
There are rumors that the pacman patch "strip: fix unique source paths"
may have side-effect
On 10/11/22 12:05, David Runge wrote:
- preserve base-devel as a group there
I'm actually currently working on moving it to a meta-package as well.
We didn't do it when introducing `base` as we never really changed it.
Now we did with debugedit and face small inconveniences and we are
better of
## RFC
We entered the final discussion period for the RFC [0] to merge the
pacman repository `[community]` into `[extra]` as well as the packaging
VCS location `community` into `packages`. The `[core]` repository
remains limited to Developers. One the RFC is accepted, we will
implement the propos
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/14
Please visit the above link for discussion.
Summary:
Merge the pacman repository `[comm
## devtools
The code and repository has been restructured [0] as it got out of hand
over time. Now it follows a clear distinction and structure with
improvements in the build system.
The incubating tool `diffpkg` received a lot of new features [1] that
will be released shortly. The new tool help
Hi all,
I've had some chats with Giancarlo and he is currently unexpectedly very
busy and stuffed with a lot of work. Thew new MK did not proceed
currently to fill in the missing slot. Together we concluded that
it would be the best to adapt to the current situation, revoke the
newly created key
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/14
Please visit the above link for discussion.
Summary:
Merge the pacman repository [community] into [extra] as well as the
packaging VCS location `community` into `packages`.
Th
## archlinux-keyring
The archlinux-keyring package gained a systemd service and timer unit
which updates existing PGP keys used by pacman on user systems by
default on a weekly basis from Arch Linux's web key directory (WKD)[0].
This service is meant to remove the necessity for most cases of "f
## devtools
The new devtools release brings in several new additions. First and
foremost the `export-pkgbuild-keys` script in combination with
`commitpkg` ensures we export all validpgpkeys into the source tree. The
local keys cache will allow us to operate without remote PGP keyservers
for the m
## Staff
We would like to welcome Slithery [0] among our Forum Admins.
Furthermore fukawi2 has stepping down [1] as Forum Admin. We would like
to express appreciation for all the work through the years.
Last but not least we held our first Mediator election where Andrea
Denisse Gómez-Martínez (
## Keyring
We have started phasing out sha1 keyring signatures and replace some
existing keys with more modern variants.
Furthermore we have started to enforce @archlinux.org UIDs so we can
control the retrieval via wkd in a single place and also allow externals
to just trust one official wkd
## Staff
We would like to welcome sudoforge among the Trusted Users [0].
## RFC
We have ratified a RFC to store upstream signing keys alongside the
packaging sources [1]. This will allow easier successive builds without
the need to continuously rely on remote keyservers to retrieve the
upst
## Staff
sudoforge has applied [0] to become a Trusted User and the vote is
currently in progress.
On top we would like to welcome freswa and Foxboron to their new
additional duties as Arch Linux Developers.
Furthermore we have onboarded the project maintainers Torxed
(archinstall) and kevr (au
## Staff
We have on-boarded wiki maintainers as part of our official staff [0]
and wish a warm welcoming.
We would also like to welcome BrainDamage among the Arch IRC op team.
## Debug packages
The required devtools release is live, which handles debug packages and
makes sure to release the
On 2/6/22 14:25, David Runge via arch-dev-public wrote:
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 b
On 2/2/22 18:32, Evangelos Foutras via arch-dev-public wrote:
On Mon, 31 Jan 2022 at 22:27, Jelle van der Waa via arch-dev-public
wrote:
The question is if anyone object to checking these small .NVCHECKER
files into our svn repository. If there are no real objections, I'll
start implementing t
## Staff
We are happy to welcome Segaja among the Trusted Users [0].
## Monthly Report
We have switched the format of the monthly report to specifically report
the progress of the whole previous month.
## Debug packages
The dbscripts repository handling for debug packages has successfully
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/9
Please visit the above link for discussion.
Summary:
Add an official mediation program to
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/9
Please visit the above link for discussion.
Summary:
Add an official mediation program to our organization consisting of
elected mediators to help settle disputes and provide a
## Report
The pad for the next January 2022 report is available at [0].
## Staff
We are happy to welcome artafinde [1] among the Trusted Users.
Additionally Segaja has applied [2] to become a Trusted User and the
vote is currently in progress.
## mkinitcpio
A new mkinitcpio version v31 has
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 it takes longer than expected. I'll start the PHP
8.1 update and the required rebuilds soon. I noticed some unexpected
incompatibilitie
On 11/18/21 03:19, Allan McRae via arch-dev-public wrote:
On 18/11/21 00:08, Levente Polyak via arch-dev-public wrote:
The idea so far was to release LTO in a second iteration as some
concerns were raised to do both set of changes at the very same time.
My concerns about this are rather
On 11/29/21 14:30, Jelle van der Waa via arch-dev-public wrote:
Hi,
On 14/11/2021 19:40, Jelle van der Waa wrote:
Hi All,
I would like to propose that we start deprecating python2 and only
allowing to exists for:
* Make dependencies where required (js68, grafana-zabbix, etc.)
* Runtime depe
On 11/17/21 13:27, Allan McRae via arch-dev-public wrote:
On 17/11/21 22:03, Jelle van der Waa via arch-dev-public wrote:
## Devtools
* pacman's makepkg.conf is synced with new hardening CFLAGS such as
`-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security
-fstack-clash-protection -fcf-protect
Hi all,
to mitigate different issues with the current status of PGP keyservers
and to simplify the management of our keyring we worked towards
exploring a new way to handle our keyring:
The idea is to have a curated keyring whose source of truth is the
repository itself without relying on ex
On 10/10/21 16:47, Allan McRae via arch-dev-public wrote:
- Overall, I think the current CoC is below the standard that has been
historically set for official contributions to Arch Linux and would be a
poor reflection on the distribution if officially adopted.
- The RFC should not be adopted
On 8/22/21 12:03, Jelle van der Waa via arch-dev-public wrote:
On 17/08/2021 20:36, Morten Linderud via arch-dev-public wrote:
Yo,
I packaged up the new Go release yesterday and moved it over to stable
earlier
today.
Usually new Go minor releases frequently include new compiler
improvements
On 9/5/21 04:38, Allan McRae via arch-dev-public wrote:
Either the CoC was already a formal document and changes were made by a
small number of staff with limited oversight from the governing body -
in this case we need to revert to the last formal version and all
changes need formally agreed on.
I would like to welcome Jonas Witschel (diabonas) among the Arch Linux
Developers.
Jonas has been a Trusted User since 2019 and lately joined the Arch
Linux Security Team.
We wish you good luck and joy with your new responsibilities within Arch
Linux!
cheers,
Levente
OpenPGP_signature
D
We are happy to announce that Arch Linux has partnered with Nitrokey [0]
to equip its staff with free Nitrokey devices. We will use the Nitrokey
devices to store cryptographic keys for signing of git commits, emails
and software packages, GnuPG keys, and SSH accounts.
Thanks to the Nitrokey’s disc
On 3/16/21 6:00 PM, Pierre Schmitz via arch-dev-public wrote:
> Hi, I saw your post; I just did not want to go off-topic right away.
> :-) At least as long as I am the only contributor I hesitate to give
> up on how the infrastructure is set up. It seems to be much more
> complex to do this on "off
On 3/14/21 3:07 PM, Pierre Schmitz via arch-dev-public wrote:
> I just updated the server to also accept x86_64 feature levels, ARM
> and even i686. There is a new version of pkgstats (>= 3.1.0; currently
> in [testing]) which is able to detect feature levels. ARM support is
> pretty early, but x86
Hi Pierre,
I think at this point we should actually convert the "pet project" into
an real official service hosted under the archlinux.org hood :)
cheers,
Levente
OpenPGP_signature
Description: OpenPGP digital signature
On 3/2/21 2:37 AM, Sébastien Luttringer via arch-dev-public wrote:
> On Tue, 2021-03-02 at 00:19 +0100, Levente Polyak via arch-dev-public wrote:
>> I think this is a great step for our distro to get a nicely pre shaped
>> proposals before hitting the final review and presentatio
Thank you all for the RFC idea, healthy discussion around it and the
first RFC about having and RFC :)
I think this is a great step for our distro to get a nicely pre shaped
proposals before hitting the final review and presentation phase as well
as a central point for storing those. I think its p
Hi all,
We were recently made aware by a bug report [1] that when the strip
executable from binutils 2.36-3 in [core] is run within a fakeroot, it
does not keep the correct file ownership during stripping, but
indiscriminately assigns ownership to root:root instead. This causes
issues with executa
help by our long-time developer Allan McRae [3], which -- as
a joint effort of Remi Gacogne (rgacogne) and Levente Polyak (anthraxx)
[4] -- lead to the founding of the structured effort known today as the
Arch Linux Security Team.
Without doubt the work and analysis is challenging and the overall
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 crippling the API usage on a level
that rips out especially things like the safe browsing fu
96 matches
Mail list logo
