Re: New [community] additions for 2018

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

 



On Sat, 27 Jan 2018 19:19:10 +0100, Ralf Mardorf wrote:
>On Sat, 27 Jan 2018 19:01:29 +0100, David Runge wrote:
>>On 2018-01-27 18:39:16 (+0100), Ralf Mardorf wrote:  
>>> On Sat, 27 Jan 2018 18:32:56 +0100, David Runge wrote:    
>>> >Please note: If you now do a `pacman -Syu` (with the
>>> >[community-testing] repo still enabled in /etc/pacman.conf), you'll
>>> >update your system with everything that's newer in
>>> >[community-testing] in comparison to [community] (the first has
>>> >precedence)!    
>>> 
>>> Better do not enable testing, buts simply install the package you
>>> wish to test by
>>> 
>>>   pacman -S URL_of_the_package_location
>>>     
>>Ralf, that's not really a helpful suggestion.
>>
>>However, if you activate the [community-testing] repository, pacman
>>will properly install all dependencies of a package and be able to
>>keep track of it in a reasonable way.
>>Some of the new additions have dependencies (also in
>>[community-testing]).
>>
>>So please, refrain from doing it the way Ralf described.  
>
>My apologoes for the typo "S" should read "U", "S" doesn't work at all,
>but "U" would install all dependencies, too.
>
>
>
>[root@archlinux rocketmouse]# pacman -Q yoshimi 
>yoshimi 1.5.6-1
>[root@archlinux rocketmouse]# pacman -U
>https://mex.mirror.pkgbuild.com/community-testing/os/x86_64/yoshimi-1.5.6-2-x86_64.pkg.tar.xz
> yoshimi-1.5.6-2-x86_64
> 6.2 MiB   686K/s 00:09
> [--------------------------------------------------------------------]
> 100%
> yoshimi-1.5.6-2-x86_64.sig
> 566.0   B  0.00B/s 00:00
> [--------------------------------------------------------------------]
> 100%
>loading packages...
>resolving dependencies...
>looking for conflicting packages...
>
>Packages (1) yoshimi-1.5.6-2
>
>Total Installed Size:  10.95 MiB
>Net Upgrade Size:      -1.78 MiB
>
>:: Proceed with installation? [Y/n] 
>(1/1) checking keys in
>keyring
>[--------------------------------------------------------------------]
>100% (1/1) checking package
>integrity
>[--------------------------------------------------------------------]
>100% (1/1) loading package
>files
>[--------------------------------------------------------------------]
>100% (1/1) checking for file
>conflicts
>[--------------------------------------------------------------------]
>100% (1/1) checking available disk
>space
>[--------------------------------------------------------------------]
>100% :: Processing package changes... (1/1) upgrading
>yoshimi
>[--------------------------------------------------------------------]
>100% :: Running post-transaction hooks... (1/3) Updating icon theme
>caches... (2/3) Arming ConditionNeedsUpdate... (3/3) Updating the
>desktop file MIME type cache... [root@archlinux rocketmouse]# pacman
>-Q yoshimi yoshimi 1.5.6-2 [root@archlinux rocketmouse]# ls
>-hl /var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz*
>-rw-r--r-- 1 root root 6.3M Jan 25
>15:01 /var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz
>-rw-r--r-- 1 root root  566 Jan 25
>15:01 /var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz.sig
>
>
>
>The only drawaback still is the sig file.
>
>Once you install the next upgrade and run "pacman -Sc" the *sig file
>will not be removed, you need to remove it using
>
>rm -i /var/cache/pacman/pkg/*sig
>
>
>
>[root@archlinux rocketmouse]# rm -i /var/cache/pacman/pkg/*sig
>rm: remove regular file
>'/var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz.sig'? y
>[root@archlinux rocketmouse]# ls
>-hl /var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz*
>-rw-r--r-- 1 root root 6.3M Jan 25
>15:01 /var/cache/pacman/pkg/yoshimi-1.5.6-2-x86_64.pkg.tar.xz
>[root@archlinux rocketmouse]#
>
> 
>
>That's it.
>
>Yes, all dependncies already were installed on my system, if not pacman
>would have installed them.

My bad :D

indeed, assuming a package should depend on additional packages from
any testing repository, it doesn't work ;), but then we are on the
"partial" upgrade issue, so it anyway would be required to enable _all_
testing repositories, not just the community testing repository.

IOW the OP needs to upgarde everything using all testing
repositories ;). Actually this usually isn't required ;).
-- 
https://www.schneier.com/blog/archives/2018/01/spectre_and_mel_1.html



[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux