Re: mkarchroot and Manual intervention for pacman 7.0.0 and local repositories required

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Lone_Wolf <lone_wolf@xxxxxxxxxxxxxxx> wrote:

> 
> On 22-09-2024 21:55, u34@xxxxxxx wrote:
> >      $ pacman -Qo mkarchroot
> >      /usr/bin/mkarchroot is owned by devtools 1:1.2.1-1
> >
> > Referring to
> > https://archlinux.org/news/manual-intervention-for-pacman-700-and-local-repositories-required/
> > and to
> > https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot#Setting_up_a_chroot
> > with a modified pacman.conf:
> >
> >      error: could not open file /home/user/chroot/root/var/lib/pacman/sync/download-o6cp5z/core.db.part: Permission denied
> >      error: failed to setup a download payload for core.db
> >      error: failed to synchronize all databases (failed to retrieve some files)
> >      ==> ERROR: Failed to install packages to new root
> >      ==> ERROR: Failed to install all packages
> >
> > The modified pacman.conf is using links created with
> >      ln -s /var/lib/pacman/sync/*.db /var/cache/pacman/pkg/
> > I have also tried the naive approach of
> >      --- a/usr/bin/mkarchroot	2024-06-23 21:00:54.158267054 +0000
> >      +++ b/usr/bin/mkarchroot	2024-09-22 19:31:52.984269364 +0000
> >      @@ -73,6 +73,7 @@
> >       [[ -e $working_dir ]] && die "Working directory '%s' already exists" "$working_dir"
> >       
> >       mkdir -p "$working_dir"
> >      +chown :alpm "$working_dir"
> >       
> >       lock 9 "${working_dir}.lock" "Locking chroot"
> >
> > In addition, the most basic suggestion of
> > https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot#Setting_up_a_chroot
> > , namely
> >      # mkarchroot /home/user/chroot/root base-devel
> > also fails. Though it could be due to a usually working XferCommand in
> > pacman.conf.
> > Does mkarchroot broken?
> >       
> > --
> > u34
> 
> 
> Try disabling the sandbox / download user in pacman .conf .
> 
>  >#DownloadUser = alpm
> DisableSandbox

I do not understand why 

    #DownloadUser = alpm

Disables Sandbox when there is a specific configuration option to 
DisableSandbox. Was that a too quick blind typing mistake? In any case, I 
have tried the 4 pairs of {,#}DownloadUser = alpm and {,#}DisableSandbox.

My command line was 
    # mkarchroot -C /home/user/pacman.conf /home/user/chroot/root base-devel

1. With
    #DownloadUser = alpm
    #DisableSandbox
   mkarchroot succeeds with an exit code of 0.
2. With
    DownloadUser = alpm
    #DisableSandbox
   which is the default configuration of /etc/pacman.conf, mkarchroot failed 
   with an exit code of 255.
3. 
    DownloadUser = alpm
    DisableSandbox
   mkarchroot failed with an exit code of 255.
4. 
    #DownloadUser = alpm
    DisableSandbox
   mkarchroot succeeds with an exit code of 0.

As an aside, my /etc/pacman.conf has

    DownloadUser = alpm
    #DisableSandbox

and does seems to work. Such a setting is the default configuration of 
/etc/pacman.conf. Doesn't it?

--
34

> 
> 
> That should make downloads/ everything related to the sandbox act 
> exactly the same as pacman 6.x .
> 
> Lone_Wolf
> 



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux