On 21/11/2020 18.48, Filipe Laíns via arch-dev-public wrote:
> I understand that. I am not asking to put all releases of Python on the
> repos, only the active ones, which people are using.
I presume you can back it up with numbers how widely 3.7 and 3.6 are
used by Arch users. All I can see is
Hi,
Due to lack of free time, I've orphaned some packages I don't want to
think about:
bash
bash-completion
chrome-gnome-shell
expat
gdbm
libcap
libffi
libunistring
libusb
networkmanager-fortisslvpn
ncurses
openfortivpn
readline
texinfo
wpa_supplicant
I've also disowned some packages I've
On 20/04/2020 00.32, Morten Linderud via arch-dev-public 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 in `build()` and `check()` during
On 13/01/2020 18.28, Christian Rebischke via arch-dev-public wrote:
> [testing] has been used and I wanted to test my packages, but the push
> from [testing] to [community] happened before my scheduled date for
> this.
Have you raised this on the TU or staff channels before the move
happened?
On 05/01/2020 23.04, Morten Linderud via arch-dev-public wrote:
> On Mon, Jan 06, 2020 at 07:53:21AM +1000, Allan McRae via arch-dev-public
> wrote:
>> Following the roll out of the base metapackage, and its poorly written
>> news post, we agreed that all new posts should have a draft posted to
On 14/10/2019 23.11, Levente Polyak via arch-dev-public wrote:
> Q: Why has this been implemented so suddenly?
> A: That's a good question, while we have discussed this topic multiple
>times in the past and also issued a concrete proposal to arch-dev-
>public (plus its follow-up summary)
Damn calendars, how do they even work!?
Yes, I meant 2020.
On 03/09/2019 18.41, Alad Wenter via arch-dev-public wrote:
> ... 2020?
>
> Time flies.
>
> Alad
>
> On 9/3/19 6:36 PM, Bartłomiej Piotrowski via arch-dev-public wrote:
>> Hi all,
>>
>> As I
Hi all,
As I have free time shortage lately, I think it's fair to officially say
I will be in semi-away mode till 2019. I will try my best to keep up
with uncomplicated pkgver bumps for packages I maintain on my own and
make sure all keys are properly signed, but that's all I can promise.
It
I'd go with updating all packages to ship the converted files.
Cluttering /usr with untracked files doesn't sound good.
BP
On 30/07/2019 09.33, Bartłomiej Piotrowski via arch-dev-public wrote:
> On 30/07/2019 02.44, Christian Rebischke via arch-dev-public wrote:
>> One problem I see with the News section is that it's Dev only. I
>> wouldn't even know who I need to ask (and I am TU for sever
On 30/07/2019 02.44, Christian Rebischke via arch-dev-public wrote:
> One problem I see with the News section is that it's Dev only. I
> wouldn't even know who I need to ask (and I am TU for several years
> now).
The list of developers is public. If after few years you don't know a
single person
On 02/06/2019 09.37, Bartłomiej Piotrowski via arch-dev-public wrote:
> On 26/05/2019 22.39, Eli Schwartz via arch-dev-public wrote:
>> Question: are you going to set up an archbuild alias on soyuz/dragon for
>> this, the way you did for gcc8? (Which reminds me, those archbuild
&
On 26/05/2019 22.39, Eli Schwartz via arch-dev-public wrote:
> Question: are you going to set up an archbuild alias on soyuz/dragon for
> this, the way you did for gcc8? (Which reminds me, those archbuild
> aliases still exist and could be deleted).
I can create it, sure.
> Also please bump the
On 26/05/2019 18.51, Bartłomiej Piotrowski via arch-dev-public wrote:
> Hi all,
>
> I just deleted GCC 9 and related packages from [testing] due to the
> filesystem corruption bug when bcache is used[1]. You will have to -Syuu
> your systems.
>
> People hungry for breakag
Hi all,
I just deleted GCC 9 and related packages from [testing] due to the
filesystem corruption bug when bcache is used[1]. You will have to -Syuu
your systems.
People hungry for breakage can install it from [gcc9] repo I uploaded to
pkgbuild.com:
[gcc9]
Server =
Adopted restic and pass-otp.
On 18/03/2019 09.18, Gaetan Bisson via arch-dev-public wrote:
> [2019-03-18 08:39:45 +0100] Bartłomiej Piotrowski via arch-dev-public:
>> I asked Bruno to start another round as previous thread is way too long
>> for people who missed the party to catch up.
>
> So some of u
On 17/03/2019 23.13, Gaetan Bisson via arch-dev-public wrote:
> [2019-03-17 19:07:23 +0100] Bruno Pagani via arch-dev-public:
>> This is a follow-up on the last month discussion about a “minimal base
>> system”.
>
> Creating a new thread removed from the discussion we had a month ago
> just makes
On 18/03/2019 00.35, Gaetan Bisson via arch-dev-public wrote:
> [2019-03-18 00:25:09 +0100] Alad Wenter via arch-dev-public:
>> Assuming we implement this group or meta-package as something of policy,
>> i.e. every repository package is assumed to depend on it. This would then
>> make base
Hi all,
I'm trying to run away from winter so I'll be away starting Wednesday. I
will be partially available via IRC/e-mail but I don't plan to do any
packaging.
Bartłomiej
On 22/01/2019 00.23, Allan McRae via arch-dev-public wrote:
> On 22/1/19 8:03 am, Levente Polyak via arch-dev-public wrote:
>> Everything that won’t be part of base-system needs to be added as a
>> dependency to all requiring packages; alternatively don't omit any first
>> level runtime
On 16/12/2018 21.52, Dave Reisner wrote:
> Hi,
>
> I'm finding myself lacking these days in both time and motivation to
> continue maintenance of both mkinitcpio and arch-install-scripts. Is
> anyone interested in taking these over? Both projects are fairly stable,
> but bugs do crop up as the
Few months ago I asked on arch-dev whether we would like to ask for
access to Cloud Native Computing Foundation cluster, which we could use
to experiment with automated package builds (or anything else really).
Following no response I actually did so anyway[1] and I have been
invited to CNCF
On 06/11/2018 12.13, Bruno Pagani via arch-dev-public wrote:
> Yeah, but [community] used to be something completely separated from
> [extra]. This is less and less the case (numerous packages were moved
> from [extra] to [community] so that TUs could maintain them for
> instance). The line
On 15/09/2018 23.06, Bartłomiej Piotrowski via arch-dev-public wrote:
> On 14/09/2018 18.46, Bartłomiej Piotrowski via arch-dev-public wrote:
>> Hi all,
>>
>> We would like to discuss design, issues and what is left to do about the
>> future dbscripts git migration
On 14/09/2018 18.46, Bartłomiej Piotrowski via arch-dev-public wrote:
> Hi all,
>
> We would like to discuss design, issues and what is left to do about the
> future dbscripts git migration and enabling debug packages by default.
>
> Please fill which time suits you bes
Hi all,
We would like to discuss design, issues and what is left to do about the
future dbscripts git migration and enabling debug packages by default.
Please fill which time suits you best on Monday (17.09) or Tuesday
(18.09) here[1].
The meeting will take place on #archlinux-devops on
On 09/08/2018 18.41, Morten Linderud via arch-dev-public wrote:
> Yo!
>
> The subreddit /r/linux have started organizing AMA threads for relevant
> projects. Gentoo had one of these a few months ago and is an interesting read.
>
>
Hi all,
I want to enable mandatory two-factor authentication in our GitHub
organization. Few of you unfortunately don't use it and will be
effectively removed when I flip the switch, which I plan to do next
week, 6th July.
allanbrokeit
anthraxx
Atsutane
Bluewind
brain0
City-busz
djgera
New draft that includes pam_unix2 deprecation.
Title: glibc 2.27-2 and pam 1.3.0-2 may require manual intervention
The new version of glibc removes support for NIS and NIS+. The default
`/etc/nsswitch.conf` file provided by `filesystem` package already
reflects this change. Please make sure to
On 2018-04-16 13:02, Bartłomiej Piotrowski via arch-dev-public wrote:
Hi team,
During libnsl rebuild heftig pointed out that we are shipping pam_unix2
that has been dead upstream for a long time (to the point that it's
being built from our own mirror now). I'm also unwilling to spend time
What a day!
gksu has been deprecated for years. Applications that require elevated
privileges should use PolicyKit instead - and it seems that everything
in our repositories do. I plan to remove gksu (and libgksu) from
repositories this week.
Bartłomiej
Hi team,
During libnsl rebuild heftig pointed out that we are shipping pam_unix2
that has been dead upstream for a long time (to the point that it's
being built from our own mirror now). I'm also unwilling to spend time
to fix its configure.ac to make it build with libnsl and libtirpc
On 2018-03-20 18:45, Levente Polyak via arch-dev-public wrote:
On March 20, 2018 4:55:16 PM GMT+01:00, Robin Broda via arch-dev-public
<arch-dev-public@archlinux.org> wrote:
On 03/20/2018 02:36 PM, Bartłomiej Piotrowski via arch-dev-public
wrote:
Hi team,
As I'm absolutely the worst
Hi,
I've had too much faith in GCC 8 release schedule. To sweeten the wait
(and catch some possible issues sooner), I'm going to push glibc 2.27
and binutils 2.30 to [staging] in the evening.
The new glibc doesn't ship libnss_nis{,plus} and RPC interface anymore.
Packages that require the last
On 2017-10-22 13:13, Bartłomiej Piotrowski wrote:
> Hi all,
>
> for those of you that are living closer to Asia than Europe, there is
> new build server available, located in Singapore. It is considerably
> less beefy than soyuz, but should be okay for regular builds.
>
> All packagers should be
Hi team,
As I'm absolutely the worst with C++, none of my packages depend on
boost and I've spent enough nights terrified of its build system quirks,
I'll be orphaning it soon. Feel free to adopt it in archweb.
Bartłomiej
On 2018-03-13 15:32, Eli Schwartz via arch-dev-public wrote:
> This wrapper changes depending on which version of meson you have installed.
The wrapper is part of the package that changes.
> The fact that autoconf has weird bugs like needing to set localstatedir
> and sysconfdir to their
On 2018-03-13 14:40, Allan McRae via arch-dev-public wrote:
> On 13/03/18 21:22, Jan Alexander Steffens via arch-dev-public wrote:
>> For that matter, I'm all for putting an arch-configure helper into our
>> autoconf package.
>
> Don't muck around with vanilla packages. Put it in another package
On 2018-03-12 05:33, Pierre Schmitz wrote:
> Thanks for digging this up again. You may use the github issue or
> project system to plan the different steps. Also (and please don't get
> it the wrong way) let's keep the purpose I intended for our Docker
> image intact.
No one has suggested
On 2018-03-10 11:34, Antonio Rojas via arch-dev-public wrote:
> Hi,
> Currently most of our packages which use the cmake build system are built
> with -DCMAKE_BUILD_TYPE=Release. This provides a reasonable (according to
> upstream) set of C(XX)FLAGS defaults which are appended to and override
On 2018-01-29 20:29, Pierre Schmitz wrote:
> * I did not look into the details of how we exactly need to proceed
> with making an "official" image. A few pull requests or some kind of
> setp-by-step plan (wiki or github) would help.
Necrobumping. You actually quoted the message from Santiago that
On 2018-02-13 16:13, Eli Schwartz via arch-dev-public wrote:
> On 02/13/2018 09:29 AM, Bartłomiej Piotrowski via arch-dev-public wrote:
>>>> I have updated gcc in the repository to snapshot from 2018-02-11
>>>> (r257571). Additionally, if you have access to soyuz, the r
On 2018-02-13 15:19, Baptiste Jonglez wrote:
> On 13-02-18, Bartłomiej Piotrowski via arch-dev-public wrote:
>> On 2018-02-04 14:02, Bartłomiej Piotrowski via arch-dev-public wrote:
>>> Hi all,
>>>
>>> I've prepared external repository with GCC 8 built from trun
On 2018-02-04 14:02, Bartłomiej Piotrowski via arch-dev-public wrote:
> Hi all,
>
> I've prepared external repository with GCC 8 built from trunk (as there
> is no stable release yet) that also contains glibc 2.27 and binutils 2.30.
>
> [gcc8]
> Server = http://pkgbuild.
Hi all,
I've prepared external repository with GCC 8 built from trunk (as there
is no stable release yet) that also contains glibc 2.27 and binutils 2.30.
[gcc8]
Server = http://pkgbuild.com/~bpiotrowski/gcc8/
From less obvious packaging changes, glibc no longer ships with obsolete
rpc and nsl,
Whoa, this is so good to bash that I can't decide where to begin.
Microsoft started noticing Linux (or rather stopped to fight it so
valiantly) when they realized where the money is. On this ground alone I
don't see a reason to help some corporation in putting our logo on their
website so they
On 2018-01-20 20:19, Christian Rebischke via arch-dev-public wrote:
> The Arch Linux Vagrant images are currently be build for libvirt and
> virtualbox. We have over 3800 downloads at the moment and slowly
> catching up to the community based arch linux vagrant images.[1]
It would be probably
Hi team,
I've finished moving unneeded orphans to AUR. The only exceptions that
were simply removed are nvidia-304xx family (EOL'ed upstream) and
nautilus-open-terminal (seems to be built into nautilus these days).
You can find the list of (re)moved packages here[1]. Let's try not to
make such a
On 2018-01-04 13:02, Balló György via arch-dev-public wrote:
> Currently the 'xfce4-goodies' package group[1] is in split between [extra]
> and [community]. Most of its packages are in [extra], but 'ristretto' and
> 'xfce4-whiskermenu-plugin' are in [community].
>
> My question is: is it okay, or
On 2018-01-04 12:17, Balló György via arch-dev-public wrote:
> The following packages should be kept too:
> - dvdauthor
> arojas: kdenlive
> fyan: kdenlive
> heftig: brasero
> jgc: brasero
The only two packages that really require it are unneeded orphans, so I
don't see the point.
On 2018-01-04 10:35, Rashif Ray Rahman via arch-dev-public wrote:
> 2018-01-03 21:05 GMT+06:00 Bartłomiej Piotrowski via arch-dev-public
> <arch-dev-public@archlinux.org>:
>>
>> Hi team,
>>
>> This is the final update before I start moving packages to AUR over
On 2018-01-04 00:20, Balló György via arch-dev-public wrote:
> Please move the following packages from [extra] to [community], so I can
> adopt them:
> - gnome-icon-theme-extras
> - libgovirt
> - python2-telepathy
>
> --
> György Balló
> Trusted User
>
Moved, enjoy.
BP
On 2018-01-03 23:31, Balló György via arch-dev-public wrote:
> Please don't remove anything yet. I'll adopt some packages in the next 24
> hours.
>
> You missed some optional and indirect dependencies. We should keep the
> following packages:
I explicitly said that I'm not taking optdepends into
Hi team,
This is the final update before I start moving packages to AUR over this
week.
List of orphans required by maintained packages:
- autoconf-archive:
jgc: dbus, gspell, gnumeric
tomegun: dbus, dbus-docs, libimobiledevice
heftig: gst-plugins-base-libs, gstreamer, libgweather
Hi all,
gdbm 1.14 introduced silent ABI breakage[1] so for now, I removed it
from [testing]. I contacted upstream about the issue and if the time
allows, I will prepare a fix today.
Bartłomiej
signature.asc
Description: OpenPGP digital signature
On 2017-12-18 23:51, Baptiste Jonglez wrote:
> On 18-12-17, Bartłomiej Piotrowski via arch-dev-public wrote:
>> On 2017-12-18 10:54, Bartłomiej Piotrowski via arch-dev-public wrote:
>>> Please look at both lists and adopt what your packages are using or
>>> you're
On 2017-12-18 10:54, Bartłomiej Piotrowski via arch-dev-public wrote:
> Please look at both lists and adopt what your packages are using or
> you're personally interested in. I will drop whatever makes sense in
> January.
And of course, if you are missing some permissions or need someth
Hi team,
Recently I've spent a bit of time on the train so I spent that on
writing a script (of questionable quality) for generating packages
cleanup list. The main difference from the "unneeded orphans" report is
that it also includes orphans that require only other orphans and
additionally
59 matches
Mail list logo
