On Tue, Aug 25, 2020 at 04:46:36PM -0400, Public mailing list for Arch Linux
development wrote:
> On Tue, 25 Aug 2020 at 15:58:40, Evangelos Foutras via arch-dev-public wrote:
> > I am not sure these serve any purpose. The maintainer line duplicates
> > information available from the archweb or
On Wed, May 13, 2020 at 10:16:38PM +0200, Public mailing list for Arch Linux
development wrote:
> Yo!
>
> After another few lazy weeks I have finished up the new Go packaging
> guidelines.
>
> https://wiki.archlinux.org/index.php/User:Foxboron/Go_packaging_guidelines#Flags_and_build_options
>
On Mon, Apr 20, 2020 at 12:32:18AM +0200, Public mailing list for Arch Linux
development wrote:
> I have also removed `-mod=vendor` from the default listing in `prepare()` as
> Anatol wasn't fond of the idea. I'm still unsure if we really want this as we
> would be willynilly downloading sources
On Sat, Mar 28, 2020 at 02:11:02PM +0100, David Runge wrote:
> On 2019-11-11 09:40:14 (-0300), Giancarlo Razzolini via arch-dev-public wrote:
> > But, we still don't have anyone wanting to become the actual
> > maintainer of archiso to help implement these changes.
>
> I'd be up for it. I have
On Sun, Mar 15, 2020 at 12:09:07PM -0700, Public mailing list for Arch Linux
development wrote:
> Hello Morten
>
> On Sun, Mar 15, 2020 at 5:38 AM Morten Linderud via arch-dev-public
> wrote:
> >
> >
> > # Introduction
> >
> > To enable PIE compilation, we have relied on a patched version of
On Thu, Feb 27, 2020 at 10:11:24AM +0100, Public mailing list for Arch Linux
development wrote:
> PS. If unmaintained orphans in [core] could be moved to [extra], and
> unmaintained orphans in [extra] could be moved to [community], that could
> be a nice "trickle down" effect and would be an
On Sat, Jan 11, 2020 at 09:57:42AM -0500, Dave Reisner wrote:
>On Fri, Jan 10, 2020, 16:43 Christian Rebischke via arch-dev-public
><[1]arch-dev-public@archlinux.org> wrote:
>
> Hi everybody,
> I would like to propose that we create todos for rebuil
Hi everybody,
I would like to propose that we create todos for rebuilds of language
specific packages.
We had two major rebuilds in the last months: python3.8 and ruby2.7.
Can we agree that we create a todo before such rebuilds?
The advantages outweigh the disadvantages. We would gain:
* More
On Thu, Dec 12, 2019 at 01:40:19PM +0100, Public mailing list for Arch Linux
development wrote:
> On 12/12/19 1:21 PM, Christian Rebischke via arch-dev-public wrote:
> > 8.2 I can't find any list about punishments for violations of these
> > rules.
> >
> > Best rega
Hello everybody,
Due to a longer discussion around alpha and beta packages in our
repositories in IRC yesterday, I would like to start a hopefully more
constructive discussion around this topic on the ML.
Short summary for everybody what happened:
I wanted to get caddy2.0.0-beta into
Hi,
I plan to drop the vulnerability management tool "openvas" (Greenbone
Vulnerability Manager).
I stopped using the software and it gets more and more tedious (due to
breaking changes and bad testing at upstream). Moreover I really think
that there are better solutions right now (for example
On Fri, Nov 08, 2019 at 10:22:44AM +0100, Jelle van der Waa wrote:
> Hi all,
>
> Gerardo has stepped down as Arch ISO maintainer, which makes archiso
> unmaintained. I've asked Pierres if he was interested in maintaining
> the project and he is willing to do bug fixes when required but no major
>
On Tue, Jul 30, 2019 at 10:16:17AM +1000, Allan McRae wrote:
> On 30/7/19 8:47 am, Christian Rebischke via arch-dev-public wrote:
> > Hello everybody,
> > I got assigned to this issue here:
> >
> > https://bugs.archlinux.org/task/62823
> >
> > The users
> We already have this feature.
>
> Add the following to the PKGBUILD, and rebuild it:
>
> changelog=NEWS
>
> Now, the user may at any time run the following command for an installed
> package:
>
> $ pacman -Qc pkgname
> Changelog for pkgname:
> [contents of NEWS file]
>
> Changelogs are
On Mon, Jul 29, 2019 at 07:36:31PM -0400, Public mailing list for Arch Linux
development wrote:
> On Mon, 29 Jul 2019 at 18:47:44, Christian Rebischke via arch-dev-public
> wrote:
> > So what can we do here? I am a big fan of Gentoos Newsletter feature[1].
> > It would be s
Hello everybody,
I got assigned to this issue here:
https://bugs.archlinux.org/task/62823
The users would like to have a notice in pre/post install/upgrade
notifications via pacman .install files.
I am not a fan of spamming such news via pacman and I think the
installation/upgrade process
On Thu, Jun 27, 2019 at 03:43:37PM +0800, Public mailing list for Arch Linux
development wrote:
> Hi All,
>
> I have removed dingo the Google DNS-over-HTTPS client from [community].
> The upstream is inactive for years and supports Google only.
>
> I would recommend dns-over-https [1] instead
On Sun, Jun 02, 2019 at 12:38:24AM -0400, Public mailing list for Arch Linux
development wrote:
> Dear Christian,
>
> Thank you for your email.
>
> I do not share your point of view that the organization is chaotic. You
> successfully explained the three roles and each of its duties within two
On Sat, Jun 01, 2019 at 04:10:45PM -1000, Public mailing list for Arch Linux
development wrote:
> Hi Christian,
>
> [2019-06-02 01:08:30 +0200] Christian Rebischke via arch-dev-public:
> > inspired by the last thread about moving proprietary software to
> > community
On Sun, Jun 02, 2019 at 01:07:12PM +1000, Allan McRae wrote:
> On 2/6/19 9:08 am, Christian Rebischke via arch-dev-public wrote:
> > 1. Simplified repositories
> >
> > Currently we have [core], [extra] and [community]. These three
> > repositories are the
Hello everybody,
DISCLAIMER:
Sorry for the huge mail, I didn't thought it would get so long. If you
feel attacked/angry or whatever about it, take a deep breath before you
answer. I hope for a constructive discussion without personal attacks.
On Wed, Mar 27, 2019 at 05:19:34PM +0100, Public mailing list for Arch Linux
development wrote:
> Following up on xyproto's [community] cleanup, here is a list of unrequired
> orphans in [extra] which could be removed (minus the aspell/hunspell dicts).
> Please adopt them if you want to keep them
On Mon, Mar 25, 2019 at 12:46:15AM +0100, Public mailing list for Arch Linux
development wrote:
> On Sun, Mar 24, 2019 at 04:39:54PM -0700, Andrew Gregory via arch-dev-public
> wrote:
> > I don't consider hoping that libarchive doesn't need a rebuild in the
> > near future a great strategy.
On Wed, Mar 20, 2019 at 02:02:08PM +0100, Public mailing list for Arch Linux
development wrote:
> Yo!
>
> As some might be aware, I'm finishing up a master thesis that is due 1st of
> June. Because of this my time is going to be limited closer to the delivery
> date. To try relieve some stress
On Tue, Nov 06, 2018 at 08:37:42PM +1000, Allan McRae wrote:
> On 6/11/18 8:15 pm, Bruno Pagani wrote:
> > Le 06/11/2018 à 11:12, Christian Rebischke via arch-dev-public a écrit :
> >> On Tue, Nov 06, 2018 at 08:09:03PM +1000, Allan McRae wrote:
> >>> On 6/11/18 7:
On Tue, Nov 06, 2018 at 08:09:03PM +1000, Allan McRae wrote:
> On 6/11/18 7:54 pm, Christian Rebischke via arch-dev-public wrote:
> > Hello everybody,
> >
> > First of all, the following mail has nothing to do with the last two TU
> > applications, it's a gen
Hello everybody,
First of all, the following mail has nothing to do with the last two TU
applications, it's a general view on the current TU application process.
I would like to propose a new process for TU applications due to several
reasons:
1. I have the feeling that most sponsors are not
On Thu, Aug 09, 2018 at 06:41:43PM +0200, Public mailing list for Arch Linux
development wrote:
> * Reddit username.
> * What you do.
> * What Monday fits for you?
Reddit username: sh1bumi
What you do: Trusted User, Automated Vagrant image builds, Security Team
work [sadly pretty inactive the
Hello everybody,
Some months ago Bartlomiej had the awesome idea to generate qemu and
virtualbox images as well. Afterwards we had a small discussion about
this topic in #archlinux-projects. I would like to refresh this
discussion and move it to this mail thread.
So, our vagrant boxes are
On Mon, Jan 29, 2018 at 10:00:28PM +0100, Public mailing list for Arch Linux
development wrote:
> So deadline is 2018-02-7
>
>
> -- Chris
Hello everybody,
sorry for the delay. I thought about this a little bit longer and I came
to the conclusion that this project will not work without the full
On Mon, Jan 29, 2018 at 03:09:16PM -0600, Public mailing list for Arch Linux
development wrote:
> On Mon, 29 Jan 2018 22:00:28 +0100
> Christian Rebischke via arch-dev-public <arch-dev-public@archlinux.org> wrote:
>
> > Hello everybody,
> > I would like to start
Hello everybody,
I would like to start a discussion about Windows Subsystem Linux and
Arch linux. You all might know that Microsoft has increased their
participation in open source software a lot since Satya Nadella is CEO
of Microsoft.
They even implemented a subsystem on Windows 10 for
On Fri, Jan 26, 2018 at 04:36:32PM -0800, Public mailing list for Arch Linux
development wrote:
> Hello folks
>
> There been a packaging issue with 'ruby' package that annoyed me for a
> while. The problem comes from the fact that ruby-lang.org source
> tarballs contain ruby sources itself *and*
On Tue, Jan 23, 2018 at 10:58:48AM +0100, Public mailing list for Arch Linux
development wrote:
> On 21.01.2018 20:50, Christian Rebischke via arch-dev-public wrote:
> > I would definitly
> > prefer to have the vagrant boxes around the same date as we release our
> > ISO i
On Sun, Jan 21, 2018 at 07:41:53PM +0100, Public mailing list for Arch Linux
development wrote:
> It would be probably seen as more "official" if it was mentioned on our
> website.
Absolutly! I will see what I can do to bring that on our website.
> > My first goal has been to add some
On Sun, Jan 21, 2018 at 03:23:44PM +0100, Jelle van der Waa wrote:
> I'm all for automatic builds, and the improvement where multiple people
> know how the ISO's are build & released. How would we however sign these
> builds? And is the bootstrap image also generated in the same manner?
Well, we
Hello Everybody,
It's now over a half year ago that I've started working together with
sangy and pierre on our vagrant and docker images. I would like to give
you a short update on this topic.
The Arch Linux Vagrant images are currently be build for libvirt and
virtualbox. We have over 3800
37 matches
Mail list logo
