Re: [arch-general] File conflict between official packages
On 20/08/2021 16:21, 山田ハヤオ via arch-general wrote: > I tried to install cups-filters and pantheon-default-settings. > As a result, Pacman reported a "/usr/share/cups/data/default-testpage.pdf" > conflict. > This issue should be fixed. > > PS > Since I used the mailing list for the first time, I apologize for sending > it to some wrong places. > Hi, Could you open a bug report against both packages on bugs.archlinux.org? That will help get the right people on it. -- Regards, Konstantin OpenPGP_signature Description: OpenPGP digital signature
Re: [arch-general] Is it possible to download only one single update from community-testing?
On 03/09/2021 13:22, Björn Fries via arch-general wrote:
> Hello,
>
> On 9/3/21 12:15 PM, Peter Nabbefeld via arch-general wrote:
>> Is it possible to download this single package,
>> without downloading full repository index and probably even updating
>> everything to community-update?
>
> manually download package from mirror, install with
> pacman -U filename.pkg.tar.zst
Your mileage may vary, but you could add [community-testing] to
/etc/pacman.conf but at the bottom of the file. Or at least below
[community]. Then you can install things with
`pacman -S community-testing/${pkgname}`.
However, this and your general idea are not great advice and will put
your system in an unsupported state. Meaning, what you want to do is
equivalent to a partial upgrade (like pacman -Sy & pacman -S something)
and if you have issues later, Arch Linux support options will probably
just refuse to help you. Hence, why it's called an unsupported state.
--
Regards,
Konstantin
OpenPGP_signature
Description: OpenPGP digital signature
Re: [arch-general] Possible to rebuild a standard package?
On 04/09/2021 15:12, Peter Nabbefeld via arch-general wrote: > > Hello, > > I'd like to re-build (not just re-install) pyside2 and python-shiboken2 > locally. As PKGBUILD (at least for shiboken2) contains cmake > instructions, I'd guess this should be easy, but I cannot figure out, how. > > Kind regards, > Peter > > One thing you could also try locally is to install the devtools package and then run the `extra-x86_64-build` command in the folder containing the PKGBUILD file. This will create a clean chroot under /var and will build the package exactly they way we build most packages in the official repos. One thing to remember is that this way is much more taxing in computing resources, specifically disk space and time. But it is safer as your system is separated from the build environment. -- Regards, Konstantin OpenPGP_signature Description: OpenPGP digital signature
Re: [arch-general] Difficulty installing UEFI
On 11/16/21 00:06, Paul M. Foster via arch-general wrote: > On 11/15/21 4:52 PM, Bjoern Franke via arch-general wrote: >> Hi, >>> >>> I have a 2017 Lenovo ThinkCentre M800 that I'm using to try to install >>> Arch on a hard drive. I've formatted the drive (under Arch, using fdisk, >>> with gpt partition, etc.), gone through the installation up to the point >>> where I run grub-install with this command: >>> >>> grub-install --target=x86_64-efi --bootloader-id=grub_uefi --recheck >>> >> >> what device did you use for installing? Did you select "Boot UEFI"? Is >> "BIOS Legacy"-mode enabled in BIOS? >> >> Regards >> Bjoern > > Not sure I understand what you mean. I used a thumb drive with the Arch > ISO on it, and tweaked the BIOS to boot that drive first. > > Paul > > There are two places where this is important. First, when creating a USB stick with an Arch ISO, you need to create it as a UEFI bootable USB stick. Then you also need to boot that USB stick in UEFI mode when trying to install to a machine. If you do not create a UEFI compatible USB in the first place, you won't be able to boot it in UEFI mode later. However, even if you have a UEFI USB, you can still boot it in legacy support mode (BIOS) and that will not install/enable UEFI support on your new installation. -- Regards, Konstantin OpenPGP_signature Description: OpenPGP digital signature
