Re: [pacman-dev] [PATCH v2] Extend download callback interface with start/complete events

On 6/5/20 12:50 pm, Anatol Pomozov wrote: > With the previous download interface the callback uses the first progress > event as 'download has started' signal. Unfortunately it does not work with > up-to-date files that never receive 'download progress' events. > Up-to-date database messages are cu

Re: [pacman-dev] [PATCH] doc: remove vim modelines from BUILDINFO(5)

On 6/5/20 12:09 pm, Eli Schwartz wrote: > We (thought we) removed all modelines from the project in commit > 860e4c4943ad062bd0eff99f28e7d64804b3c08e, but apparently this one > sneaked in by virtue of this manpage being added to the project after > the "remove all the modelines" patch was submitted

[pacman-dev] [GIT] The official pacman repository branch, master, updated. v5.2.1-66-g411b12d0

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The official pacman repository". The branch, master has been updated via 411b12d09ddb47722acf6d354c17ee9ee5228964 (commit) vi

[pacman-dev] [PATCH v2] Extend download callback interface with start/complete events

With the previous download interface the callback uses the first progress event as 'download has started' signal. Unfortunately it does not work with up-to-date files that never receive 'download progress' events. Up-to-date database messages are currently handled in sync_syncdbs() after the sequen

[pacman-dev] [PATCH] doc: remove vim modelines from BUILDINFO(5)

We (thought we) removed all modelines from the project in commit 860e4c4943ad062bd0eff99f28e7d64804b3c08e, but apparently this one sneaked in by virtue of this manpage being added to the project after the "remove all the modelines" patch was submitted, but before it was applied. I must have failed

Re: [pacman-dev] [PATCH v2] Introduce event types for start/end database list download

On 6/5/20 11:28 am, Anatol Pomozov wrote: > Multiplexed database/files downloads will use multiple progress bars. > The UI logic is quite complicated and printing error messages while > handling multiple progress bars is going to be challenging. > > Instead we are going to save all ALPM error mess

Re: [pacman-dev] [PATCH] Introduce event types for start/end database list download

On 6/5/20 11:28 am, Anatol Pomozov wrote: >>> Multiplexed database/files downloads will use multiple progress bars. >>> The UI logic is quite complicated and printing error messages while >>> handling multiple progress bars is going to be challenging. >>> >>> Instead we are going to save all ALPM e

[pacman-dev] [PATCH v2] Introduce event types for start/end database list download

Multiplexed database/files downloads will use multiple progress bars. The UI logic is quite complicated and printing error messages while handling multiple progress bars is going to be challenging. Instead we are going to save all ALPM error messages to a list and flush it at the end of the downlo

Re: [pacman-dev] [PATCH] Introduce event types for start/end database list download

Hello On Tue, Apr 28, 2020 at 6:31 PM Allan McRae wrote: > > On 17/4/20 12:31 pm, Anatol Pomozov wrote: > > Multiplexed database/files downloads will use multiple progress bars. > > The UI logic is quite complicated and printing error messages while > > handling multiple progress bars is going to

Re: [pacman-dev] [PATCH] Add a helper macro to free() dload_payload structure

Hi On Tue, Apr 28, 2020 at 5:56 PM Allan McRae wrote: > > On 27/4/20 12:24 pm, Anatol Pomozov wrote: > > Hi > > > > On Sun, Apr 26, 2020 at 7:18 PM Allan McRae wrote: > >> > >> On 27/4/20 11:54 am, Anatol Pomozov wrote: > >>> Hi > >>> > >>> On Sun, Apr 26, 2020 at 4:54 PM Allan McRae wrote: > >

Re: [pacman-dev] [PATCH] Add str_endswith() utility function

Hi On Tue, Apr 28, 2020 at 8:43 PM Allan McRae wrote: > > On 22/4/20 4:42 am, Anatol Pomozov wrote: > > It provides an easy way to check whether a string ends with a given > > suffix. > > > > Note: "pkg.sig" is a valid package name with signature file > "pkg.sig.sig" But *.pkg.sig.sig could

Re: [pacman-dev] Setting HOME in build() breaks package signing

On 5/5/20 4:11 PM, brainpower wrote: [...] > This made me wonder: > Is this something makepkg should take care of (e.g.by restoring $HOME after > build() or ensuring gpg will use $OLDHOME/.gnupg) > or should such a PKGBUILD be considered broken / invalid? [...] > $ cat PKGBUILD > pkgname=broken

[pacman-dev] Setting HOME in build() breaks package signing

Hi, a while back I came across a PKGBUILD which changed $HOME in build() as a workaround for a bad installer [1]. For some reason this failed to build with `makepkg --sign`, claiming it could not find my gpg key, see snippet below. After some time debugging this, I found changing $HOME broke the

Re: [pacman-dev] Planning the move to the Arch Linux Gitlab instance

On Sun May 3, 2020 at 7:20 PM EDT, Anatol Pomozov wrote: > Hi > > On Sat, May 2, 2020 at 1:29 AM Allan McRae wrote: > > So how would we proceed? > > > > Bugs: > > Do we pick a date where we disable new bug submissions on the current > > tracker and point towards gitlab? Are old bug transferred a