• New pacman.conf issue?


    Hi,
    just updated my system with new /etc/pacman.conf. I think it has a problem (or am I missing something?): it seems to be missing lines

    [antergos]
    SigLevel = PackageRequired
    Include = /etc/pacman.d/antergos-mirrorlist
    

    since without those lines pacman seems to use only Arch mirrors, and e.g. dropbox and a few AUR packages are not updating correctly.

    Could someone comment on this?

  • this is what mine says

    #
    # /etc/pacman.conf
    #
    # See the pacman.conf(5) manpage for option and repository directives
    
    #
    # GENERAL OPTIONS
    #
    [options]
    # The following paths are commented out with their default values listed.
    # If you wish to use different paths, uncomment and update the paths.
    #RootDir     = /
    #DBPath      = /var/lib/pacman/
    #CacheDir    = /var/cache/pacman/pkg/
    #LogFile     = /var/log/pacman.log
    #GPGDir      = /etc/pacman.d/gnupg/
    #HookDir     = /etc/pacman.d/hooks/
    HoldPkg     = pacman glibc
    #XferCommand = /usr/bin/curl -C - -f %u > %o
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #CleanMethod = KeepInstalled
    #UseDelta    = 0.7
    Architecture = auto
    
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    #IgnorePkg   =
    #IgnoreGroup =
    
    #NoUpgrade   =
    #NoExtract   =
    
    # Misc options
    #UseSyslog
    #Color
    #TotalDownload
    CheckSpace
    #VerbosePkgLists
    
    # By default, pacman accepts packages signed by keys that its local keyring
    # trusts (see pacman-key and its man page), as well as unsigned packages.
    SigLevel    = Required DatabaseOptional
    LocalFileSigLevel = Optional
    #RemoteFileSigLevel = Required
    
    # NOTE: You must run `pacman-key --init` before first using pacman; the local
    # keyring can then be populated with the keys of all official Arch Linux
    # packagers with `pacman-key --populate archlinux`.
    
    #
    # REPOSITORIES
    #   - can be defined here or included from another file
    #   - pacman will search repositories in the order defined here
    #   - local/custom mirrors can be added here or in separate files
    #   - repositories listed first will take precedence when packages
    #     have identical names, regardless of version number
    #   - URLs will have $repo replaced by the name of the current repo
    #   - URLs will have $arch replaced by the name of the architecture
    #
    # Repository entries are of the format:
    #       [repo-name]
    #       Server = ServerName
    #       Include = IncludePath
    #
    # The header [repo-name] is crucial - it must be present and
    # uncommented to enable the repo.
    #
    
    # The testing repositories are disabled by default. To enable, uncomment the
    # repo name header and Include lines. You can add preferred servers immediately
    # after the header, and they will be used before the default mirrors.
    
    
    #[antergos-staging]
    #SigLevel = PackageRequired
    #Server = http://mirrors.antergos.com/$repo/$arch/
    
    [antergos]
    SigLevel = PackageRequired
    Include = /etc/pacman.d/antergos-mirrorlist
    
    #[testing]
    #Include = /etc/pacman.d/mirrorlist
    
    [core]
    Include = /etc/pacman.d/mirrorlist
    
    [extra]
    Include = /etc/pacman.d/mirrorlist
    
    #[community-testing]
    #Include = /etc/pacman.d/mirrorlist
    
    [community]
    Include = /etc/pacman.d/mirrorlist
    
    # If you want to run 32 bit applications on your x86_64 system,
    # enable the multilib repositories as required here.
    
    #[multilib-testing]
    #Include = /etc/pacman.d/mirrorlist
    
    [multilib]
    Include = /etc/pacman.d/mirrorlist
    
    # An example of a custom package repository.  See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #SigLevel = Optional TrustAll
    #Server = file:///home/custompkgs
    

    You can try to copy/paste mine and use the diff command. The q option might help to briefly list if the files differ or not.
    And then determine if and where.
    Or you could use diff -y for side to side comparison

  • @modisc
    Yes, your version is about the same as my previous one before update.

    So, the new pacman.conf (that came with the latest update) really is missing sections [antergos] and [multilib] if I understand it correctly.

    I think @developers should take a look at this.

  • OK, file /etc/pacman.conf is owned by package pacman. So it comes from upstream, and that may make fixing this a bit trickier. Today the problem was actually file /etc/pacman.conf.pacnew that did not have the required sections (antergos and multilib).

    Could it be possible to create an antergos-pacman package that adds the missing sections into /etc/pacman.conf.pacnew? Or is there another external way to add missing sections for /etc/pacman.conf, maybe using another file?

  • @manuel said in New pacman.conf issue?:

    the new pacman.conf (that came with the latest update) really is missing sections [antergos] and [multilib] if I understand it correctly.

    Hi @manuel ,

    Maybe I don’t understand your problem exactly, but what you suggest it’s not a good idea.

    You always have to update manually your conf files checking the new .pacnew files that are created. This is a rule for all packages that have some sort of file configuration. That’s why a new .pacnew conf file is created without overwriting your modified .conf file when you update them.

    Antergos cannot modify .conf files automatically, it’s your work as admin to check that .pacnew files and mix them with your old modified .conf files

    Cheers!

  • @karasu
    Thanks for the reply. As a general rule I understand that for conf files.
    But this particular file, pacman.conf, is a bit trickier for an average user like me.

    I’d like to take the new (or even required sometimes) features from conf files, and usually I manage to do so quite easily. But since some conf files are not that much documented, I don’t always know which features to take, which not. So basically it seems to be a documentation problem for me.

    And this file in particular, I don’t really understand why the [antergos] section is missing from the .pacnew file. Wondering the same about the [multilib] section, but I guess that’s just for 32 bit libs, so it is not always required.

    The only reason I can think of for not having [antergos] section is that people that want to use only Arch but install Antergos because it is easier will want this. But even that doesn’t sound right in my mind, since (I believe, maybe a poll is needed? :) ) most of us want to use Antergos instead of Arch.

    But I may be wrong here, and I’m not asking for any change for this. Now I understand better why this way has been selected, thanks for that! :)

  • This post is deleted!
  • @manuel said in New pacman.conf issue?:

    OK, file /etc/pacman.conf is owned by package pacman. So it comes from upstream, and that may make fixing this a bit trickier.

    The only reason I can think of for not having [antergos] section is that people that want to use only Arch but install Antergos because it is easier will want this.

    I guess some pacman update generated the new file (which comes from archlinux so uses only arch repositories, right?

    Also did you install pacman using --force or --overwrite by any chance?

  • @fernandomaroto No, I didn’t force the update, just manually copied new pacman.conf.pacnew onto pacman.conf. I should have checked the diffs more thoroughly, then I’d have noticed the missing sections. And I simply assumed pacman.conf.pacnew includes the antergos section, which it didn’t…

    But that’s resolved now and the system is working well again. :)

pacman.conf3 Posts 9Views 502
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.