pamac issueshttps://gitlab.manjaro.org/packages/extra/pamac/-/issues2019-07-26T10:43:52Zhttps://gitlab.manjaro.org/packages/extra/pamac/-/issues/1Symbolic links created to enable the timers should not be in /etc/systemd/sys...2019-07-26T10:43:52ZFrog McRibbitSymbolic links created to enable the timers should not be in /etc/systemd/system/multi-user.target.wantsRelevant part of the .install file for `pamac-common`:
```php
post_install() {
# enable systemd timers
ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/multi-user.target.wants
ln -sf /usr/lib/systemd/system...Relevant part of the .install file for `pamac-common`:
```php
post_install() {
# enable systemd timers
ln -sf /usr/lib/systemd/system/pamac-cleancache.timer /etc/systemd/system/multi-user.target.wants
ln -sf /usr/lib/systemd/system/pamac-mirrorlist.timer /etc/systemd/system/multi-user.target.wants
# polkit agent
```
```php
post_remove() {
# disable systemd timers
rm -f /etc/systemd/system/multi-user.target.wants/pamac-cleancache.timer
rm -f /etc/systemd/system/multi-user.target.wants/pamac-mirrorlist.timer
}
```
Link: https://gitlab.manjaro.org/packages/extra/pamac/blob/master/pamac-common.install
Problem: The symbolic links used to enable pamac-cleancache.timer and pamac-mirrorlist.timer should be in /etc/systemd/system/timers.target.wants, not in /etc/systemd/system/multi-user.target.
In general, timer units are supposed to be tied to the timers.target, with WantedBy=timers.target in their configuration. It is also the case for the timer units provided with Pamac: they both are configured with WantedBy=timers.target and therefore, if you would enable those timer units manually with `systemctl enable pamac-blabla.timer`, the symbolic link would be created in /etc/systemd/system/timers.target.wants and not in /etc/systemd/system/multi-users.target.
https://gitlab.manjaro.org/applications/pamac/tree/master/data/systemd
Note: You will also modify the post_remove() in order to remove the symlinks that are in /etc/systemd/system/timers.target.wants, or else they will be left there. You could also keep the current rm commands for backward compatibility for a while, since it won't be retroactive (older system will still have the symlinks in multi-users.target.wants unless they change that manually).
Note2: It doesn't make the units dysfunctional; they are working correctly. It is for the sake of consistency and putting things in the right place.
@schinfohttps://gitlab.manjaro.org/packages/extra/pamac/-/issues/2Using ln -sf overwrite2020-11-20T08:34:44ZGhost UserUsing ln -sf overwriteThe folder **`/etc/systemd/system/timers.target.wants`** is overwritten by installer script
https://gitlab.manjaro.org/packages/extra/pamac/blob/master/pamac-common.install#L23
https://forum.manjaro.org/t/ssd-trim-periodic-with-systemc...The folder **`/etc/systemd/system/timers.target.wants`** is overwritten by installer script
https://gitlab.manjaro.org/packages/extra/pamac/blob/master/pamac-common.install#L23
https://forum.manjaro.org/t/ssd-trim-periodic-with-systemctl/96063/11?u=linux-aarhus
https://gitlab.manjaro.org/applications/pamac/issues/631https://gitlab.manjaro.org/packages/extra/pamac/-/issues/3Weird gnome-shell crash when trying to run Pamac when certain apps are running2020-11-20T08:37:52ZivanWeird gnome-shell crash when trying to run Pamac when certain apps are runningPlease go here, since I explained it in detail with many log reports: https://forum.manjaro.org/t/2nd-time-today-had-pamac-crash-my-desktop/116866
Basically, when system has been running for some time and certain apps are running (firef...Please go here, since I explained it in detail with many log reports: https://forum.manjaro.org/t/2nd-time-today-had-pamac-crash-my-desktop/116866
Basically, when system has been running for some time and certain apps are running (firefox, steam, games, rawtherapee or gimp) if I start Pamac (add/remove manager for Manjaro) and try to refresh the database, gnome-shell crashes.
Before the latest Manjaro update it used to crash almost the entire system (all apps) but luckily, now only gnome-shell crashes and restarts, leaving this log:
```
дец 30 18:59:16 gnome-shell[1121]: toggling down object GInotifyFileMonitor that's already queued to toggle up
дец 30 18:59:18 systemd-coredump[26514]: Process 1121 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 1121:
#0 0x00007faa41feff25 raise (libc.so.6)
#1 0x0000558ddb2aa9e9 n/a (gnome-shell)
#2 0x00007faa41feffb0 __restore_rt (libc.so.6)
#3 0x00007faa41a94166 n/a (libglib-2.0.so.0)
#4 0x00007faa41a88f07 g_log_default_handler (libglib-2.0.so.0)
#5 0x0000558ddb2aa8cc n/a (gnome-shell)
#6 0x00007faa41a9439d g_logv (libglib-2.0.so.0)
#7 0x00007faa41a945a0 g_log (libglib-2.0.so.0)
#8 0x00007faa41249e09 n/a (libgjs.so.0)
#9 0x00007faa41257779 _ZN11ToggleQueue13handle_toggleEPFvP8_GObjectNS_9DirectionEE (libgjs.so.0)
#10 0x00007faa412577f8 _ZN11ToggleQueue18idle_handle_toggleEPv (libgjs.so.0)
#11 0x00007faa41a9a26f g_main_context_dispatch (libglib-2.0.so.0)
#12 0x00007faa41a9c1b1 n/a (libglib-2.0.so.0)
#13 0x00007faa41a9d0c3 g_main_loop_run (libglib-2.0.so.0)
#14 0x00007faa40f9797c meta_run (libmutter-5.so.0)
#15 0x0000558ddb2aa426 n/a (gnome-shell)
#16 0x00007faa41fdb153 __libc_start_main (libc.so.6)
#17 0x0000558ddb2aa61e n/a (gnome-shell)
Stack trace of thread 1126:
#0 0x00007faa420a89ef __poll (libc.so.6)
#1 0x00007faa41a9c120 n/a (libglib-2.0.so.0)
#2 0x00007faa41a9d0c3 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007faa41c0abc8 n/a (libgio-2.0.so.0)
#4 0x00007faa41a78bb1 n/a (libglib-2.0.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1131:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1135:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1127:
#0 0x00007faa420a89ef __poll (libc.so.6)
#1 0x00007faa41a9c120 n/a (libglib-2.0.so.0)
#2 0x00007faa41a9c1f1 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007faa421aae5e n/a (libdconfsettings.so)
#4 0x00007faa41a78bb1 n/a (libglib-2.0.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1124:
#0 0x00007faa420a89ef __poll (libc.so.6)
#1 0x00007faa41a9c120 n/a (libglib-2.0.so.0)
#2 0x00007faa41a9c1f1 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007faa41a9c242 n/a (libglib-2.0.so.0)
#4 0x00007faa41a78bb1 n/a (libglib-2.0.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1137:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1133:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1136:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1138:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 26490:
#0 0x00007faa420ade9d syscall (libc.so.6)
#1 0x00007faa41a4d11b g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007faa41acaf63 n/a (libglib-2.0.so.0)
#3 0x00007faa41acb154 g_async_queue_timeout_pop (libglib-2.0.so.0)
#4 0x00007faa41a7202a n/a (libglib-2.0.so.0)
#5 0x00007faa41a78bb1 n/a (libglib-2.0.so.0)
#6 0x00007faa404c44cf start_thread (libpthread.so.0)
#7 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 17183:
#0 0x00007faa420a89ef __poll (libc.so.6)
#1 0x00007faa20116c14 n/a (libpulse.so.0)
#2 0x00007faa20124059 pa_mainloop_poll (libpulse.so.0)
#3 0x00007faa2012e301 pa_mainloop_iterate (libpulse.so.0)
#4 0x00007faa2012e3b1 pa_mainloop_run (libpulse.so.0)
#5 0x00007faa2011e61e n/a (libpulse.so.0)
#6 0x00007faa200a2d1c n/a (libpulsecommon-13.0.so)
#7 0x00007faa404c44cf start_thread (libpthread.so.0)
#8 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1132:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
Stack trace of thread 1134:
#0 0x00007faa404cac45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007faa3ef120d8 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-60.so.0)
#2 0x00007faa3ef122b9 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-60.so.0)
#3 0x00007faa3ec2dd17 n/a (libmozjs-60.so.0)
#4 0x00007faa3ec28c6b n/a (libmozjs-60.so.0)
#5 0x00007faa404c44cf start_thread (libpthread.so.0)
#6 0x00007faa420b32d3 __clone (libc.so.6)
```https://gitlab.manjaro.org/packages/extra/pamac/-/issues/4pamac is slow2020-11-20T08:37:42ZDanielpamac is slowThe program is very slow in searching (AUR), it was faster in the past. When downloading from the package sources, there is always a break after some downloads. Checking conflicts takes a long time.
I use Archlinux Kernel 5.4.6-arch3-, 1...The program is very slow in searching (AUR), it was faster in the past. When downloading from the package sources, there is always a break after some downloads. Checking conflicts takes a long time.
I use Archlinux Kernel 5.4.6-arch3-, 1 xfce4, pamac 9.2.2-1https://gitlab.manjaro.org/packages/extra/pamac/-/issues/5I wish to downgrade [help request]2021-07-15T05:04:43ZMissLavI wish to downgrade [help request]I do not like the new layout and I really want to know how to downgrade back to the either pamac 10 or even 9 designI do not like the new layout and I really want to know how to downgrade back to the either pamac 10 or even 9 designhttps://gitlab.manjaro.org/packages/extra/pamac/-/issues/6Background updates check damages signatures on public wi-fi2022-07-31T15:44:15ZBitalsBackground updates check damages signatures on public wi-fiHello,
Recently installed Manjaro Gnome, by default Pamac checks for updates in the background.
That's a good functionality, however while using Manjaro on public wi-fi that requires authorization it corrupts all repo signatures in the ...Hello,
Recently installed Manjaro Gnome, by default Pamac checks for updates in the background.
That's a good functionality, however while using Manjaro on public wi-fi that requires authorization it corrupts all repo signatures in the background without the user knowing, because it asks for the .sig files, but gets and saves HTML documents asking to authorize instead.
This is a default behavior and it is very confusing for new users with little experience. You just use your PC, don't explicitly tell it to update and get a bunch of errors preventing you from updating even when you are authorized or inside your private network already.
I suggest using temporary locations for newly downloaded signatures until they are validated and not overwriting existing sigs immediately, or
Discarding sigs when they are corrupted and trying to download them again.
Or maybe you would think of a better solution. But right now the default setup effectively kills its ability to receive updates seemingly by itself.https://gitlab.manjaro.org/packages/extra/pamac/-/issues/7[pkg-upd] 10.42022-04-16T13:55:14ZGeorg Wagner[pkg-upd] 10.4https://gitlab.manjaro.org/applications/pamac/-/releases
https://forum.manjaro.org/t/unstable-update-2022-04-07-gnome-42-mesa-22-0-1-octopi-0-13-0-kde-git-haskell/107784/50
```
PKGBUILD | 13 ++++++-------
1 file changed, 6 insertions...https://gitlab.manjaro.org/applications/pamac/-/releases
https://forum.manjaro.org/t/unstable-update-2022-04-07-gnome-42-mesa-22-0-1-octopi-0-13-0-kde-git-haskell/107784/50
```
PKGBUILD | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/PKGBUILD b/PKGBUILD
index fee27fc..76034aa 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,10 +4,10 @@
pkgbase=pamac
pkgname=('pamac-cli' 'pamac-gtk' 'pamac-gnome-integration')
-_pkgver=10.3.0
-pkgver=10.3.0
-pkgrel=7
-_commit=fe5ebe918439c5ad247bf82226421bb2083431a0
+_pkgver=10.4.0
+pkgver=10.4.0
+pkgrel=1
+_commit=c7db90d14c1c4ea71a5255d974d9b2722402a459
pkgdesc="A Package Manager based on libalpm with AUR and Appstream support"
arch=('x86_64' 'aarch64')
url="https://gitlab.manjaro.org/applications/pamac"
@@ -18,10 +18,9 @@ options=(!emptydirs !strip)
source=("pamac-$pkgver-$pkgrel.tar.gz::$url/-/archive/$_commit/$pkgname-$_commit.tar.gz"
#"pamac-$pkgver-$pkgrel.tar.gz::$url/-/archive/v$pkgver/pamac-v$pkgver.tar.gz"
- 'gnome-shell-extension.patch'
+ #'gnome-shell-extension.patch'
)
-sha256sums=('610d631e8a0e4de408546af776fb7f2cbee4d4f6743b4698e7bea8313c2e1f81'
- '25a4cb7906aeed14c196deeeb6cc6e6bd9f91610bf947ec355944bf09e38aa16')
+sha256sums=('57ea71c69612f8dc7acafe77f2312b2c6728e14bf9c2b6126bc4889be796ae09')
prepare() {
mv "$srcdir/pamac-$_commit" "$srcdir/pamac-v$_pkgver"
```https://gitlab.manjaro.org/packages/extra/pamac/-/issues/8Pamac fails to clear missing dependency errors from memory2023-06-30T17:03:49ZIshatixPamac fails to clear missing dependency errors from memoryPamac has some trouble dealing with missing dependencies in a tidy fashion. It doesn’t provide any way to easily resolve them or simply skip that package to continue with the rest of the installs or updates. Any little issue breaks the e...Pamac has some trouble dealing with missing dependencies in a tidy fashion. It doesn’t provide any way to easily resolve them or simply skip that package to continue with the rest of the installs or updates. Any little issue breaks the entire process. I’ve had this quite a few times, but the latest example was on trying to install SchildiChat which gave the following error:
![Pamac_UnableToClearMissingDependencyEvenWhenPackageDeselected](/uploads/da3cffe1d0cf0e5261b358739ae7f64a/Pamac_UnableToClearMissingDependencyEvenWhenPackageDeselected.png)
- Adding electron24 to the install list doesn’t help.
- Removing SchildiChat from the list of things to be installed/updated doesn’t clear this error from preventing Pamac from proceeding.
- Even after closing Pamac, restarting it, and then going through the entire process to search and select all the packages I wished to install again (without including SchildiChat), the error still appeared blocking further progress.
In the end I had to reboot the system to reset Pamac properly and get the other packages installed/updated including electron24 after which I could then finally install SchildiChat successfully.https://gitlab.manjaro.org/packages/extra/pamac/-/issues/9Prevents incorrect termination due to corrupted package information.2023-08-05T07:02:07ZphoepsilonixPrevents incorrect termination due to corrupted package information.[PATCH] After the update operation, database.refresh().
Prevents incorrect termination due to corrupted package information.
```
diff --git a/src/manager_window.vala b/src/manager_window.vala
index 60ea8b1..ac2a1e6 100644
--- a/src/mana...[PATCH] After the update operation, database.refresh().
Prevents incorrect termination due to corrupted package information.
```
diff --git a/src/manager_window.vala b/src/manager_window.vala
index 60ea8b1..ac2a1e6 100644
--- a/src/manager_window.vala
+++ b/src/manager_window.vala
@@ -3989,6 +3989,7 @@ namespace Pamac {
[GtkCallback]
void on_refresh_button_clicked () {
refresh_updates (false);
+ database.refresh ();
}
void refresh_updates (bool use_timestamp) {
--
```
[0001-After-the-update-operation-database.refresh.patch](/uploads/9867f1dfdf85600dda53cd332943d869/0001-After-the-update-operation-database.refresh.patch)https://gitlab.manjaro.org/packages/extra/pamac/-/issues/10Added missing Name and keywords.2023-08-05T07:04:26ZphoepsilonixAdded missing Name and keywords.Added missing Name and keywords.
```
diff --git a/data/applications/org.gnome.Software.desktop b/data/applications/org.gnome.Software.desktop
index 16a9e83..15b0eb1 100644
--- a/data/applications/org.gnome.Software.desktop
+++ b/data/ap...Added missing Name and keywords.
```
diff --git a/data/applications/org.gnome.Software.desktop b/data/applications/org.gnome.Software.desktop
index 16a9e83..15b0eb1 100644
--- a/data/applications/org.gnome.Software.desktop
+++ b/data/applications/org.gnome.Software.desktop
@@ -1,4 +1,5 @@
[Desktop Entry]
+Name=Add/Remove Software
Exec=gnome-software %U
Terminal=false
Type=Application
diff --git a/data/applications/org.manjaro.pamac.manager.desktop b/data/applications/org.manjaro.pamac.manager.desktop
index 73663da..4d6f500 100644
--- a/data/applications/org.manjaro.pamac.manager.desktop
+++ b/data/applications/org.manjaro.pamac.manager.desktop
@@ -131,6 +131,7 @@ Comment[zh_CN]=添加或删除系统中安装的软件
Comment[zh_HK]=加入或移除系統上安裝的軟件
Comment[zh_TW]=加入或移除系統上安裝的軟體
# Translators: Search terms to find this application. Do NOT translate or localize the semicolons! The list MUST also end with a semicolon!
+Keywords=Updates;Upgrade;Sources;Repositories;Preferences;Install;Uninstall;Program;Software;App;Store;
Keywords[af]=bywerkings;opgradeer;bronne;lêerstoor;voorkeure;installeer;verwyder;program;sagteware;toep;winkel;
Keywords[ar]=تحديثات;ترقيات;مصادر;مستودعات;تفضيلات;تنصيب;إزالة;برنامج;برمجية;تطبيق;سوق;تحديث;ترقية;مصدر;مستودع;
Keywords[as]=আপডেইটসমূহ;উন্নয়ন;উৎসসমূহ;ভঁৰালসমূহ;পছন্দসমূহ;ইনস্টল;আনইনস্টল;প্ৰগ্ৰাম;চফ্টৱেৰ;এপ;সংৰক্ষণ;
--
2.41.0
```
[0001-added-Name-and-Keywords-of-desktop-files.patch](/uploads/6cf4270033164b6c9c6651c4dc0ea52b/0001-added-Name-and-Keywords-of-desktop-files.patch)https://gitlab.manjaro.org/packages/extra/pamac/-/issues/11Interrupted AUR build download fails on subsequent attempts because https://a...2023-09-05T22:51:07ZLawrence R. SteegerInterrupted AUR build download fails on subsequent attempts because https://aur.archlinux.org/ does not support 'byte' restart downloadsAfter interrupting an AUR package build download in pamac, all subsequent builds for the same package fail.
https://aur.archlinux.org/ apparently does not support starting a download at a specific 'byte' offset.
pamac should detect thi...After interrupting an AUR package build download in pamac, all subsequent builds for the same package fail.
https://aur.archlinux.org/ apparently does not support starting a download at a specific 'byte' offset.
pamac should detect this and retry download without 'byte' offset.