[manjaro-dev] next pacman

Fri Jan 2 23:10:57 CET 2015

I just pushed the PKGBUILDs of pacman-4.2, package-query-1.5 and 
pamac-2.1 in github.
All need to be pushed together in our repos.
Pacman 4.2 comes with a custom syncfirst patch which now doesn't exit 
pacman after syncfirst and continue with the transaction. Please test.
Pamac is bumped to 2.1 with the support of pacman 4.2 and an enhanced 
preferences menu which permits to edit pacman config and mirrors.
I pushed it now to support pacman 4.2 ASAP but there are some new 
strings to translate.
Regards,
Guillaume.

Le 29/12/2014 08:28, Philip Müller a écrit :
> Arch moved on and released pacman 4.2.0-5 and pyalpm 0.7-1 to their
> stable branch. This means we have to check what changed and what is
> needed to be adopted by us.
>
> For now we are at pacman 4.1.2-8 and pyalpm 0.6.2.2-2
>
> Am 23.12.2014 um 10:55 schrieb Guillaume Benoit:
>> I'm on it. Revert the remove-syncfirst.patch doesn't work anymore so
>> it will takes some time to test a new patch.
>>
>> Guillaume.
>>
>> Le 20/12/2014 08:25, Philip Müller a écrit :
>>> Hi Guillaume,
>>>
>>> pacman 4.2.0 just hit Arch-Testing. Can you take care of it and prepare
>>> some pacman and pamac packages so we can test them. There is no rush in
>>> it, as we can still keep pacman 4.1-series as long as we need to ...
>>>
>>> greez
>>> Phil
>>>
>>> Am 06.12.2014 um 15:56 schrieb Guillaume Benoit:
>>>> Ok, if it's better to have it configurable, we can just keep the
>>>> SyncFirst option.
>>>> Anyway, would you like me to modify the syncfirst patch to permit
>>>> pacman to not exit and continue the transaction or it would be a waste
>>>> of time?
>>>> Guillaume.
>>>>
>>>> Le 06/12/2014 14:59, Rob McCathie a écrit :
>>>>> manjaro-keyring and archlinux-keyring for starters, having them sync
>>>>> first would save some users from issues.
>>>>> Mainly it's for when a keyserver that holds a packager's key is
>>>>> down or
>>>>> is having connections problems for the user - this does happen,
>>>>> there's
>>>>> a number of examples on the forums - the manjaro-system script has no
>>>>> redundancy for this. It can also be problematic when a new signature
>>>>> gets added by Arch and an update for an already installed package is
>>>>> signed with it.
>>>>>
>>>>> Actually, in February this year Phil used manjaro-system to add the
>>>>> keyring packages to SyncFirst[1], but never adjusted the default
>>>>> pacman.conf in the pacman package, so new install medias made after
>>>>> that
>>>>> didn't have the change.
>>>>>
>>>>> Then in September i did it again[2] and this time also updated the
>>>>> stock
>>>>> pacman.conf so it would be permanent[3][4], however, shortly after
>>>>> Phil
>>>>> reverted the change[5]. I did ask why but never got any real
>>>>> explanation. ;-p
>>>>>
>>>>>
>>>>> [1]
>>>>> https://github.com/manjaro/packages-core/commit/614b168d668183c4ff291b967b8a6ddf495e1af7#diff-a7315ea10d82bde98e13fc896f5b8bf9R79
>>>>>
>>>>>
>>>>>
>>>>> [2]
>>>>> https://github.com/manjaro/packages-core/commit/ca7d3d40c47dc127c026239f0c0b4cc0f27c478e
>>>>>
>>>>>
>>>>>
>>>>> [3]
>>>>> https://github.com/manjaro/packages-core/commit/27fcb34afff225a5427594e965b506d0ded1a82c
>>>>>
>>>>>
>>>>>
>>>>> [4]
>>>>> https://github.com/manjaro/packages-core/commit/b5b8ddd357149fed78c94812f57e077f9d14a949
>>>>>
>>>>>
>>>>>
>>>>> [5]
>>>>> https://github.com/manjaro/packages-core/commit/802cb7ede9d376e2276b5f76d030249175752f41
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>
>>>>> Rob McCathie
>>>>>
>>>>> On 07/12/14 00:08, Philip Müller wrote:
>>>>>> Currently it is just manjaro-systems. I rather recommend to make it
>>>>>> configurable. For example with the SyncFirst= line or some extra
>>>>>> config file if needed. If we just create a function for just one
>>>>>> package it would make not much sense. Some people still have added
>>>>>> the
>>>>>> keyring packages in SyncFirst= line. If you can config it it is much
>>>>>> more flexible for later needs.
>>>>>>
>>>>>> Am 06.12.2014 um 14:04 schrieb Guillaume Benoit:
>>>>>>> I'm open to all ideas, I just saw that manjaro-system is the only
>>>>>>> package that to be in SyncFirst.
>>>>>>> What are the other packages we have to take care of?
>>>>>>> Guillaume.
>>>>>>>
>>>>>>> Le 06/12/2014 12:37, Philip Müller a écrit :
>>>>>>>> Hi Guillaume,
>>>>>>>>
>>>>>>>> is manjaro-systems the only package we have to take care of? Is it
>>>>>>>> better to some configuration so we can decide which packages
>>>>>>>> should be
>>>>>>>> installed/checked first? Your patch is fine. I rather would have an
>>>>>>>> additional option to also check for other packages. Maybe we will
>>>>>>>> introduce something which needs the same checkings.
>>>>>>>>
>>>>>>>> ... maybe I'm wrong and we can handle all with manjaro-system.
>>>>>>>>
>>>>>>>> Phil
>>>>>>>>
>>>>>>>> Am 05.12.2014 um 15:50 schrieb Guillaume Benoit:
>>>>>>>>> As some of you already know, pacman 4.2 should be released this
>>>>>>>>> month.
>>>>>>>>> I already worked on porting pamac to this new version because it
>>>>>>>>> comes
>>>>>>>>> with some API changes.
>>>>>>>>> I also worked on an idea I had now I know better pacman an libalpm
>>>>>>>>> concerning SyncFirst option.
>>>>>>>>> Manjaro comes with a custom version a pacman with a revert
>>>>>>>>> patch to
>>>>>>>>> continue to use SyncFirst even if it has been deprecated by pacman
>>>>>>>>> developers. The only reason is to update manjaro-system package
>>>>>>>>> first
>>>>>>>>> to perform some actions before the real update.
>>>>>>>>> I propose a 30 lines patch to replace syncfirst patch which
>>>>>>>>> permits
>>>>>>>>> two things:
>>>>>>>>> -- avoid the usage of syncfirst option in /etc/pacman.conf
>>>>>>>>> -- auto update manjaro-system package first when required and
>>>>>>>>> continue
>>>>>>>>> the transaction with the need to relaunch pacman.
>>>>>>>>> To allow you to have an idea I join a PKGBUILD with the new patch.
>>>>>>>>> This a first version of the patch, I you have some idea to
>>>>>>>>> improve,
>>>>>>>>> tell me.
>>>>>>>>> What do you think about it ?
>>>>>>>>>
>>>>>>>>> Guillaume.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> manjaro-dev mailing list
>>>>>>>>> manjaro-dev at manjaro.org
>>>>>>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> manjaro-dev mailing list
>>>>>>>> manjaro-dev at manjaro.org
>>>>>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> manjaro-dev mailing list
>>>>>>> manjaro-dev at manjaro.org
>>>>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> manjaro-dev mailing list
>>>>>> manjaro-dev at manjaro.org
>>>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>>>
>>>>> _______________________________________________
>>>>> manjaro-dev mailing list
>>>>> manjaro-dev at manjaro.org
>>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>> _______________________________________________
>>>> manjaro-dev mailing list
>>>> manjaro-dev at manjaro.org
>>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>>>
>>> _______________________________________________
>>> manjaro-dev mailing list
>>> manjaro-dev at manjaro.org
>>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>> _______________________________________________
>> manjaro-dev mailing list
>> manjaro-dev at manjaro.org
>> http://lists.manjaro.org/mailman/listinfo/manjaro-dev
>
> _______________________________________________
> manjaro-dev mailing list
> manjaro-dev at manjaro.org
> http://lists.manjaro.org/mailman/listinfo/manjaro-dev