Hey Maxim,
Thank you for all the time and effort you've put into Arch over the years. I'll
pick up kitty.
Best,
Campbell
Original Message
On 5/27/24 9:01 AM, Maxim Baz wrote:
> Hi everyone
>
> Life got busier than ever, and I find myself unable to
Original Message
On 3/25/24 4:10 AM, Robin Candau wrote:
> Hi everyone,
>
> I'm writing this mail as proposal to increase the default
> `vm.max_map_count` [1] value in Arch Linux.
>
> The default `vm.max_map_count` 65530 value is making some Wind
When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43
must be replaced with magpie-wm, which currently depends on mutter. As mutter43
conflicts with mutter, manual intervention is required to complete the upgrade.
First, remove mutter43 via "pacman -Rdd mutter43", then im
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/16
Please visit the above link for discussion.
Best,
Campbell
publickey - arch@serebit.com - 0x35A1812B.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
I'm of the opinion that at least one well-maintained text editor should remain
in core - my vote would be for nano, as vi has been outclassed by its clones
and ed doesn't see much use nowadays. I have no personal issues with the other
suggested cleanup items.
Best,
Campbell
--- Original M
Hi all,
I would like to post the following post-mortem to inform our users about
the recent mishap with wireplumber.
```
Two days ago the `wireplumber` package was made to replace
`pipewire-media-session` as the latter session manager for PipeWire is
considered dead upstream and will see no more
Hi All,
I've tried to reach out to keenerd a couple of times about dropping some
packages of him such as geda-gaf (which lets us drop guile2.0, gtk2 in
the future etc.). But I haven't heard back about these mails.
David has also tried to contact him about his key expiring and being
unable to
Em maio 9, 2022 1:45 Tobias Powalowski via arch-dev-public escreveu:
Hi,
sorry but not getting any answer on IRC makes the impression it is
rather unmaintained.
I just wanted to know when I can expect the release, that was promised
for march also the move to gitlab has not yet happened
arch-dev-public :
>
> On 08.05.2022 21.52, Tobias Powalowski via arch-dev-public wrote:
> > The next 3 weeks later ...
> > any progress on the project release?
> > greetings
> > tpowa
>
> This is really not a topic for arch-dev-public, please discuss it
>
On 08.05.2022 21.52, Tobias Powalowski via arch-dev-public wrote:
The next 3 weeks later ...
any progress on the project release?
greetings
tpowa
This is really not a topic for arch-dev-public, please discuss it
directly with the maintainer, move the discussion to arch-projects or
GitHub[1
The next 3 weeks later ...
any progress on the project release?
greetings
tpowa
Am Di., 19. Apr. 2022 um 11:10 Uhr schrieb Tobias Powalowski
:
>
> Hi folks,
> 6 weeks later, is there a progress to release a new mkinitcpio now soon?
> Thanks.
> greetings
> tpowa
>
> --
&g
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'
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-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. The
On 4/24/22 19:08, 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
de node: PHP 7 is on its way out of support and wont work with
e.g. OpenSSL 3 :-) So we have to update to 8.0 in a few month at
latest.
Greetings,
Pierre
On Sun, Apr 24, 2022 at 6:57 PM David Runge wrote:
>
> On 2022-03-08 13:56:04 (+0100), David Runge via arch-dev-public wrote:
>
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-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-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 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
> its leaf packages as optional dependencies.
>
I'm still unhappy with `pacman -S qemu
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
7.0.0 is replaced by
`qemu-desktop` (**the transition to this package is manual**!)
* The functionality of `qemu-headless` prior to 7.0.0 is replaced by
`qemu-base` (the transition to this package is automatic).
* The functionality of `qemu-arch-extra` and `qemu-headless-arch-extra`
prior to
Hi folks,
6 weeks later, is there a progress to release a new mkinitcpio now soon?
Thanks.
greetings
tpowa
--
Tobias Powalowski
Arch Linux Developer & Package Maintainer (tpowa)
https://www.archlinux.org
tp...@archlinux.org
El martes, 5 de abril de 2022 1:49:27 (CEST), George Rawlinson via
arch-dev-public escribió:
Bit late getting around to this (whoops!), I require some of these
packages. Any chance of moving the following to community:
* libmms
* ttf-dejavu
Moved
* libnet
This is needed by the openjdk
ght be a few
minutes late myself. :)
Best,
David
[1] https://lists.archlinux.org/pipermail/arch-projects/2022-March/005435.html
--
https://sleepmap.de
signature.asc
Description: PGP signature
several incompatibility changes have been resolved which
finally allowed us to upgrade to SQLAlchemy 1.4.
[0] https://lists.archlinux.org/pipermail/aur-general/2022-March/036842.html
[1] https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/11
[2] https://github.com/archlinux/arch-security
On 22-03-30 09:19, Antonio Rojas via arch-dev-public wrote:
> El lunes, 21 de marzo de 2022 19:33:32 (CET), Brett Cornwall via
> arch-dev-public escribió:
> >
> > I'd be interested in:
> >
> > * spice-protocol
> > * libmusicbrainz5
> > * libdiscid
>
Hey,
On 21/03/2022 09:24, Jelle van der Waa wrote:
Hey,
On 20/03/2022 16:51, Nicola Squartini via arch-dev-public wrote:
Sorry for the poorly formatted email. The packages are:
apm
atom
electron9
I'd go for, if no one shows up after a week let's drop it in the AUR so
we ca
El lunes, 21 de marzo de 2022 19:33:32 (CET), Brett Cornwall via
arch-dev-public escribió:
I'd be interested in:
* spice-protocol
* libmusicbrainz5
* libdiscid
* libdvdcss (Not sure if that one should go to community, though)
* dht (same with this one)
* screen
All moved, please adopt
On 11/3/22 09:12, Allan McRae via arch-dev-public 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/11
Please visit the above link
On Thu, Mar 24, 2022 at 09:24:03PM +1000, Allan McRae via arch-dev-public wrote:
> As I said, I'm happy the discussion around this RFC is public and open. But
> if this is a big enough change for an RFC, then it almost certainly needs to
> go through the TU voting procedure.
I
On 24/3/22 18:42, Brett Cornwall via arch-dev-public wrote:
On 2022-03-24 13:23, Allan McRae via arch-dev-public wrote:
On 24/3/22 11:07, Brett Cornwall via arch-dev-public wrote:
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs
On 2022-03-24 13:23, Allan McRae via arch-dev-public wrote:
On 24/3/22 11:07, Brett Cornwall via arch-dev-public wrote:
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/12
Please visit the above link for discussion.
Summary
On 24/3/22 11:07, Brett Cornwall via arch-dev-public wrote:
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/12
Please visit the above link for discussion.
Summary: Reject AUR packages that fulfill package dependencies without
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/12
Please visit the above link for discussion.
Summary: Reject AUR packages that fulfill package dependencies without
providing the files/binaries of the package in question.
si
Am Mon, 21 Mar 2022 18:52:14 +0100
schrieb Pierre Schmitz via arch-dev-public
:
> Hi Christian,
>
> there were some delays due to other rebuilds and lack of time/other
> issues.
>
> So far I did not get any feedback, so I'd like to repeat my request
> for help.
On 2022-03-21 11:33, Brett Cornwall wrote:
On 2022-03-21 11:36, Antonio Rojas via arch-dev-public wrote:
Hello,
Spring (in the northern hemisphere) is here and with it our yearly
orphans cleanup. Please head to
https://archlinux.org/devel/reports/unneeded-orphans/ and adopt
packages that
On 2022-03-21 11:36, Antonio Rojas via arch-dev-public wrote:
Hello,
Spring (in the northern hemisphere) is here and with it our yearly
orphans cleanup. Please head to
https://archlinux.org/devel/reports/unneeded-orphans/ and adopt
packages that you'd like to keep in the repos.
Th
Christian Hesse wrote:
>
> Pierre Schmitz via arch-dev-public on
> Sun, 2022/01/23 12:50:
> > Next steps:
> > 1) Let's agree on a time window where no other rebuild can take place
> > within our staging repos. How about at least the first two weeks in
> > Feb
I've disowned the following packages that I don't use anymore or have
no more interest in:
libisoburn
libisofs
libburn
nx (libxcomp, nx-headers, nx-x11, nxagent, nxproxy)
x2goclient
x2goserver
procmail
xterm
Feel free to adopt the packages.
-Andy
pgppFK2Y2r0AA.pgp
Description: Digitale Sig
Hello,
Spring (in the northern hemisphere) is here and with it our yearly orphans
cleanup. Please head to
https://archlinux.org/devel/reports/unneeded-orphans/ and adopt packages
that you'd like to keep in the repos.
This is also a good oportunity to disown any packages you no longer want to
Hey,
On 20/03/2022 16:51, Nicola Squartini via arch-dev-public wrote:
Sorry for the poorly formatted email. The packages are:
apm
atom
electron9
I'd go for, if no one shows up after a week let's drop it in the AUR so
we can have one electron less :)
Greetings,
Jelle
OpenPGP
Sorry for the poorly formatted email. The packages are:
apm
atom
electron9
On Sun, Mar 20, 2022 at 4:23 PM Nicola Squartini wrote:
> Hi, I'm disowning the following packages: apm atom electron9 Atom is
> basically a rotten project, it gets minimal updates and relies on obsolete
> dependencies,
Hi, I'm disowning the following packages: apm atom electron9 Atom is
basically a rotten project, it gets minimal updates and relies on obsolete
dependencies, so it has become a burden to maintain. Let me know if you
intend to adopt it. Thanks. Regards, Nicola
Hi all,
SDL1 has been deprecated for a while now but we still have some games
and programs which depend on it. Fedora started using SDL's compatbility
library sdl12-compat which implements sdl1 using sdl2 which means you
can run games under wayland, get better controller support and an actual
On 22-03-16 16:23, David Runge via arch-dev-public wrote:
> On 2022-03-16 17:09:59 (+0200), Felix Yan via arch-dev-public wrote:
> > certbot
> > certbot-dns-rfc2136
>
> I can look into co-maintaining those with Jelle (who is at least
> maintaining cerbot) when I'm ba
Hey!
I adopted `dart` simply because I was interested.
Thanks,
Orhun
OpenPGP_0xF83424824B3E4B90.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
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
> ce
Hi,
I am disowning the following packages as an attempt to shorten my TODO
and focus on packages I still use.
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-d
Pierre Schmitz via arch-dev-public on
Sun, 2022/01/23 12:50:
> Next steps:
> 1) Let's agree on a time window where no other rebuild can take place
> within our staging repos. How about at least the first two weeks in
> February?
The todo list has been around for too long alr
versions
>
> The proposed patch to add is located here:
> https://pkgbuild.com/~tpowa/symlink-compression.patch
> Thanks for your feedback.
> greetings
> tpowa
> --
> Tobias Powalowski
> Arch Linux Developer & Package Maintainer (tpowa)
> https://www.archlinux.org
>
patch to add is located here:
https://pkgbuild.com/~tpowa/symlink-compression.patch
Thanks for your feedback.
greetings
tpowa
--
Tobias Powalowski
Arch Linux Developer & Package Maintainer (tpowa)
https://www.archlinux.org
tp...@archlinux.org
St. Martin-Apotheke
Herzog-Georg-Str. 25
89415 Laui
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/11
Please visit the above link for discussion.
Summary:
Store the PGP signing keys listed i
## 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
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 07/03/2022 16:04, Leonidas Spyropoulos via arch-dev-public wrote:
The `keycloak` package prior to version 17.0.0-3 was running with
WildFly server. Since upstream moved to Quarkus, Arch Linux follows
this approach. This means current configurations need to be migrated.
The new config
The `keycloak` package prior to version 17.0.0-3 was running with
WildFly server. Since upstream moved to Quarkus, Arch Linux follows this
approach. This means current configurations need to be migrated.
The new config location needs to be adjusted from the old `.xml` format
to the new `.conf
On 2022-03-04 11:02, Allan McRae via arch-dev-public wrote:
> The tpm2-tss package is co-maintained by Filipe and Jonas. When moved to
> [core], Filipe will lose access to package it (due to only Developers having
> access to [core]). So Jonas will become sole maintainer.
>
> @
On 24/2/22 00:03, Allan McRae via arch-dev-public wrote:
On 23/2/22 22:24, Allan McRae via arch-dev-public wrote:
Hi all,
I notice when using devtools, the following packages from [extra] get
pulled into our clean build root:
extra/gc
extra/guile
extra/libsysprof-capture
extra/libxml2
The
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
A new RFC (request for comment) has been opened here:
https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/11
Please visit the above link for discussion.
Summary:
Store the PGP signing keys listed in a PKGBUILDs `validpgpkeys` array in
the trunk directory of SVN.
Motivation:
The PGP
which means
that the above packager keys can not be used for packaging anymore)
unless other blockers come up.
If you have questions, please reach out via e-mail, or in
#archlinux-staff on libera.chat.
Best,
David
[1]
https://lists.archlinux.org/pipermail/arch-dev-public/2022-January/0
On 23/2/22 22:24, Allan McRae via arch-dev-public wrote:
Hi all,
I notice when using devtools, the following packages from [extra] get
pulled into our clean build root:
extra/gc
extra/guile
extra/libcroco
libcroco is dead and gettext should no longer depend on it. So we can
remove that
Hi all,
I notice when using devtools, the following packages from [extra] get
pulled into our clean build root:
extra/gc
extra/guile
extra/libcroco
extra/libsysprof-capture
extra/libxml2
These are all dependencies of base-devel packages. I'd like to move
them to [core] so they are captured
Hi all,
Recently I have less and less spare time, and keeping packages related to the
AWS ecosystem becomes harder as AWS is a fast moving target. I'm looking
forward to co-maintainers for the following packages:
python-aiobotocore
python-aws-sam-translator
python-aws-xray-sdk
python-cfn-lint
p
On 20/2/22 08:27, Filipe Laíns via arch-dev-public wrote:
I have filled RFC 10 [12] with a formal proposal for this, as it is a fairly big
change. Feel free to give feedback there.
Can you announce the RFC using the template provided in the RFC process.
This will ensure wider viability of
Hi all,
As some of you might know, the Python packaging ecosystem is changing. If you
have noticed a lack of setup.py or its replacement with pyproject.toml then you
already ran into issues I want to discuss today.
I will a bit in-depth when explaining the motivation and current state of
affairs,
On 2022-02-03 12:26, David Runge via arch-dev-public wrote:
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
Hi all,
Just a reminder with the toolchain in [testing] that you need to be
careful when building packages for the stable repos. If you build the
package using the [testing] toolchain and release it to [extra] or
[community] it will fail to run with errors like:
/usr/lib/libc.so.6: version
Hello everybody,
a problem has been found in MariaDB 10.6.6 and upstream decided to withdraw
the release. We do the same, just removed mariadb (and galera) packages from
testing.
https://jira.mariadb.org/browse/MDEV-27789
--
main(a){char*c=/*Schoene Gruesse */"B?IJj;M
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 i
Em janeiro 29, 2022 9:11 Morten Linderud via arch-dev-public escreveu:
Generally my thoughts is that we shouldn't *need* to have a more manhours to
deal with a x86_64_v3. We should instead strenghten our staff and work on the
following:
* Signing enclave
* Better rebuilding tools
*
On 06/02/2022 17:20, Frederik Schwan via arch-dev-public wrote:
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
On Mon, Feb 07, 2022 at 11:28:02AM +0100, Xyne via arch-dev-public wrote:
> Hi,
>
> In the recent discussions about possibly adding support for x86_64-v3 the
> general consensus seemed to be that we need to first work on our packaging
> infrastructure (build pipelines, reproduci
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.
However, I have been having very little time to work on Arch related stuff
lately and the
toolchain is
ready
any tools in development? Aside from some helper tools such as
arch-rebuild-order I didn't find anything in the list of official projects on
our Gitlab.
Regards,
Xyne
## 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
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
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 int
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.
On 2022-02-04 13:49, Jelle van der Waa via arch-dev-public wrote:
Hey all,
On 30/01/2022 12:08, Morten Linderud via arch-dev-public wrote:
I'm very happy to announce that debug packages in Arch Linux has been deployed
:)
This work began after FOSDEM 2020 and was announced in November
On 04/02/2022 12:49, Jelle van der Waa via arch-dev-public wrote:
* How do I verify if the debug package is generated correctly?
After installing the debug package, gdb $binary should reveal:
[jelle@t14s][~]%gdb /usr/bin/cryptsetup
Reading symbols from /usr/bin/cryptsetup...
Reading symbols
On Fri, Feb 04, 2022 at 11:07:29PM +1000, Allan McRae via arch-dev-public wrote:
> On 4/2/22 22:49, Jelle van der Waa via arch-dev-public wrote:
> >
> > * How do I create a debug package?
> >
> > Add 'debug' to the options array in your PKGBUILD, bump pkgre
On 4/2/22 22:49, Jelle van der Waa via arch-dev-public wrote:
* How do I create a debug package?
Add 'debug' to the options array in your PKGBUILD, bump pkgrel and
rebuild. This should result into a debug package based on the 'pkgbase'
of the package/PKGBUILD so for linux
Hey all,
On 30/01/2022 12:08, Morten Linderud via arch-dev-public wrote:
I'm very happy to announce that debug packages in Arch Linux has been deployed
:)
This work began after FOSDEM 2020 and was announced in November 2020. However
because of time constraints it took quite a while befo
On 03.02.22 12:53, David Runge via arch-dev-public wrote:
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
On 31.01.22 21:25, 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.
nvchecker is a program
On 22-02-02 21:03, Felix Yan via arch-dev-public wrote:
> There is a regex plugin and a htmlparser plugin for this.
>
> The htmlparser plugin accepts XPath, but if you want to process it further
> the regex plugin may just work better.
>
> Examples for your packages:
>
> [
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 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-projects to*also* become a general discussion list around
the above mentioned Arch Linux projects
What do you
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
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
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
On 3/2/22 03:42, Leonidas Spyropoulos via arch-dev-public wrote:
On 02/02/2022 17:32, Evangelos Foutras via arch-dev-public wrote:
I'm not fond of the hidden all-caps filename for editable sources
(whereas it's fine for .BUILDINFO and friends). More importantly
though, has integrati
On 2/1/22 22:54, George Rawlinson via arch-dev-public wrote:
On 22-02-01 08:21, Morten Linderud via arch-dev-public wrote:
At this stage, the following [community] packages that I maintain
require massaging of HTML sources:
* html-xml-utils
* oil
* parallel
* libmilter (bundled with sendmail
On 2/2/22 19:59, Anatol Pomozov via arch-dev-public wrote:
And here is one more tool to check if package version is of out-of-date
https://github.com/anatol/pkgoutofdate
It is a pretty simple tool that does not require any modification to Arch
repo. It simply tries to guess what is the next
Hi
On Wed, Feb 2, 2022 at 9:32 AM Evangelos Foutras via arch-dev-public <
arch-dev-public@lists.archlinux.org> 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 .NVCHECKE
On 02/02/2022 17:32, Evangelos Foutras via arch-dev-public wrote:
I'm not fond of the hidden all-caps filename for editable sources
(whereas it's fine for .BUILDINFO and friends). More importantly
though, has integration with [1] been considered? The best way to
implement automat
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 impleme
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 this functionality into archweb in tw
1 - 100 of 546 matches
Mail list logo