On 5/17/25 5:21 AM, Ralf Mardorf wrote:
On Sat, 2025-05-17 at 08:03 +, Edward Toroshchyn wrote:
Without knowing more about the problem you're solving it's hard to
give a more specific advice.
Good point! I guess dependencies such as bash or systemd might be a
concern.
If you're want a
On 5/17/25 4:03 AM, Edward Toroshchyn wrote:
pacman is open source, so of course you can change it however you want.
Without knowing more about the problem you're solving it's hard to give
a more specific advice.
If you're want a minimalistic OS and/or package manager, have you looked
at
Is it possible to build a neutered version of pacman?
A pacman lite if you will
I need to cut down on the dependencies pacman requires.
Without key signing and package signing.
I would like to only have package building and package management and
pull from an http respository.
This is
On 5/6/25 6:17 AM, Markus Schaaf wrote:
Am 04.05.25 um 19:13 schrieb Pocket:
gpg —full-gen-key
gpg —export —armor —output public-key.asc pocket
gpg —export-secret-keys —armor —output private-key.asc pocket
The key id is pocket.
For each key/attempt I imported each key into Pacman-key
On 5/4/25 9:33 PM, u...@net9.cf wrote:
Pocket wrote:
On 5/4/25 3:12 PM, Doug Newgard wrote:
On 5/4/25 8:20 AM, Pocket wrote:
I am getting this error when running is there a way to fix this?
We aren't the ones to be asking. Arch is x86_64 only, ArchLinuxARM is a
separate distro
On 5/4/25 3:12 PM, Doug Newgard wrote:
On 5/4/25 8:20 AM, Pocket wrote:
I am getting this error when running is there a way to fix this?
We aren't the ones to be asking. Arch is x86_64 only, ArchLinuxARM is a
separate distro with it's own repositories.
This is what I
On 5/4/25 3:12 PM, Doug Newgard wrote:
On 5/4/25 8:20 AM, Pocket wrote:
I am getting this error when running is there a way to fix this?
We aren't the ones to be asking. Arch is x86_64 only, ArchLinuxARM is a
separate distro with it's own repositories.
I heard you the first t
pacman -Syy refreshes all db for all repositories
Is there a way to have pacman only refresh a single repository db?
Ie pacman -Syy custom only refreshes custom withou refreshing core extra etc
--
Hindi madali ang maging ako
On 5/4/25 3:12 PM, Doug Newgard wrote:
On 5/4/25 8:20 AM, Pocket wrote:
I am getting this error when running is there a way to fix this?
We aren't the ones to be asking. Arch is x86_64 only, ArchLinuxARM is a
separate distro with it's own repositories.
I found something i
Sent from my iPhone
> On May 4, 2025, at 11:50 AM, u...@net9.cf wrote:
>
> Pocket wrote:
>
>>
>> Sent from my iPhone
>>
>>>> On May 4, 2025, at 9:21 AM, u...@net9.cf wrote:
>>>
>>> Pocket wrote:
>>>
>>&g
Sent from my iPhone
> On May 4, 2025, at 9:21 AM, u...@net9.cf wrote:
>
> Pocket wrote:
>
>>
>> I am building packages using makepkg for the raspberry pi 4 platform
>>
>> I changed the CFLAGS adding -march=armv8-a -mtune=cortex-a72 (makepkg.conf
I am getting this error when running is there a way to fix this?
Using makechrootpkg -c -r "$CHROOT" -- --ignorearch --skippgpcheck works
fine
$ arch-nspawn $CHROOT/root pacman -Syy
:: Synchronizing package databases...
custom 11.5 KiB 261
KiB/
I am building packages using makepkg for the raspberry pi 4 platform
I changed the CFLAGS adding -march=armv8-a -mtune=cortex-a72 (makepkg.conf).
I started to build all the packages that make up the "Building in a
clean chroot" following the building in a claen chroot on the wiki.
All when w
On 4/21/25 2:41 AM, Robin Candau wrote:
On 4/21/25 4:15 AM, Pocket wrote:
I am building packages following DeveloperWiki:Building in a clean chroot
When building packages that are associated with gnome I get the
following error:
CMake Error at wsrep-lib/CMakeLists.txt:5
I am building packages following DeveloperWiki:Building in a clean chroot
When building packages that are associated with gnome I get the
following error:
CMake Error at wsrep-lib/CMakeLists.txt:5 (cmake_minimum_required):
Compatibility with CMake < 3.5 has been removed from CMake.
Updat
I have read the information previous supplied and found some useful
tidbits/information.
This is to better explain what I am trying to accomplish
server alarm.home.org <-- fetchmail<-- 1...@example.org
Dovecot/SMTP<-- 2...@example.org
On 11/5/24 04:31, Uwe Koloska wrote:
I just need help setting up multiple accounts (smarthost) to
www.twc.com. One of the following, opensmtpd | postfix | exim.
This is easy with postfix and well documented:
http://www.postfix.org/SASL_README.html#client_sasl_sender
Hope this helps
Uwe
On 11/4/24 17:44, David C. Rankin wrote:
On 11/4/24 11:09 AM, Pocket wrote:
I am looking to setup an email server for home use.
I want to replace a debian server on a RPI 4 to an archlinux arm on
RPI 4.
I have dovecot and postifix on the debian rpi presently. It is not
working as needed
On 11/4/24 15:50, Polarian wrote:
Just a note,
If this is being done on residential broadband then good luck, its very
unlikely to work.
A large number of ISPs block/filter port 25 (which is used to relay
emails) to "protect against spam". Not to mention the horrific IP
reputations which mos
I am looking to setup an email server for home use.
I want to replace a debian server on a RPI 4 to an archlinux arm on RPI 4.
I have dovecot and postifix on the debian rpi presently. It is not
working as needed.
I have looked at the relative wiki pages for postfix, exim, opensmtpd
and dovec
On 4/17/24 18:44, Doug Newgard wrote:
On Wed, 17 Apr 2024 13:01:11 -0400
Pocket wrote:
I am trying to build nodejs in a chroot using
pkgctl repo clone --protocol=https nodejs
pushd nodejs
makechrootpkg -c -u -r "$CHROOT" -- --skippgpcheck
popd
It fails at this point
==
I am trying to build nodejs in a chroot using
pkgctl repo clone --protocol=https nodejs
pushd nodejs
makechrootpkg -c -u -r "$CHROOT" -- --skippgpcheck
popd
It fails at this point
==> Entering fakeroot environment...
chmod: cannot access '/startdir/pkg': No such file or directory
I don't h
Trying to build plasma-wayland-protocols
This is the error I am getting
What executable is it looking for?
I have built the entire qt5/qt6 stack except for qt5-ukui-platformtheme
plasma-wayland-protocols is a dependency of qt5-ukui-platformtheme
So I am stuck here
Can anyone shed light on t
I have a project where I am building arch packages for raspberry pi's
4/5. Building the base and devtools with all there dependencies I have
2477 completed with some packages being complete failures.
In the qt5-* PKGBUILD most fail due to the wrong directory
For example in qt5-tools:
Build
24 matches
Mail list logo
