You are not logged in.
I'm missing systemload, netload and mount plugins... the first 2 were previously in your repo, will they be back?
All your base are belong to us
Offline
hmm gimp is still at 2.3.10? I think 2.3.11 is out.
Offline
Updated xfce-svn stuff.
Added netload plugin
Added mount plugin
Updated xfdesktop (icons work again)
·¬»· i am shadowhand, powered by webfaction
Offline
Quick update:
Over the next week, I will slowly be moving all of my packages into the Unstable repository. Once all packages have been moved over, I will be removing my mousetrap repository (papercut may stay around as a testing ground).
I will also be updating this post as things get added to unstable.
Packages moved so far:
gaim-svn
gimp-devel·¬»· i am shadowhand, powered by webfaction
Offline
Can you remove the replaces=(bmpx) line from the bmpx-svn package in the proccess?
It is not really needed, and not intented to be used that way anyway.
Offline
Can you remove the replaces=(bmpx) line from the bmpx-svn package in the proccess?
It is not really needed, and not intented to be used that way anyway.
Sure. I did it that way for some reason, but I don't remember why now.
·¬»· i am shadowhand, powered by webfaction
Offline
hello, I tried to run bmpx-svn, but I get the following message:
** (beep-media-player-2:3677): CRITICAL **: DBus Error: (org.freedesktop.DBus.Error.Spawn.ChildExited): Process /usr/libexec/beep-media-player-2-bin exited with status 127
Thanks
Offline
you do run a d-bus session daemon, don't you?
if not, or not sure, try running
dbus-launch --exit-with-session beep-media-player-2
and see what happens
Offline
** (beep-media-player-2:7444): CRITICAL **: DBus Error: (org.freedesktop.DBus.Error.Spawn.ChildExited): Process /usr/libexec/beep-media-player-2-bin exited with status 127
that is what I get with
dbus-launch --exit-with-session beep-media-player-2
thanks
Offline
Are you using the testing repo?
Shadowhands stuff is not compiled against testing - probably you are just missing a library.
Cheers,
Blind
Offline
btw, xcompmgr can be removed from makedepends in the xfwm4-svn PKGBUILD, as it is not needed.
Offline
Quick update:
Over the next week, I will slowly be moving all of my packages into the Unstable repository. Once all packages have been moved over, I will be removing my mousetrap repository (papercut may stay around as a testing ground).
Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
Offline
shadowhand wrote:Quick update:
Over the next week, I will slowly be moving all of my packages into the Unstable repository. Once all packages have been moved over, I will be removing my mousetrap repository (papercut may stay around as a testing ground).
Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
you can user ignorepkg in the pacman.conf.
Offline
ralvy wrote:shadowhand wrote:Quick update:
Over the next week, I will slowly be moving all of my packages into the Unstable repository. Once all packages have been moved over, I will be removing my mousetrap repository (papercut may stay around as a testing ground).
Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
you can user ignorepkg in the pacman.conf.
But wouldn't I have to use an ignore line in pacman.conf for each package, one line per package, in unstable? To do that, I would have to anticipate future entries in unstable and create another ignore line for each of them too. I'd like to have pacman ignore everything in unstable except xfce stuff.
Offline
You don't really have to do such thing, since you usually have to explicitly install something from unstable.
They will not just come down and replace the stable versions (where applicable).
Offline
You don't really have to do such thing, since you usually have to explicitly install something from unstable.
They will not just come down and replace the stable versions (where applicable).
Ah, I see. Then, when Shadowhand moves all his xfce files to unstable, will updates happen automatically if I enable that repo? Or will I have to explicitly install each update, one by one?
Offline
just uncomment unstable in /etc/pacman.conf and you can update as usual, as soon as xfce4-svn has been moved to unstable.
Offline
just uncomment unstable in /etc/pacman.conf and you can update as usual, as soon as xfce4-svn has been moved to unstable.
Simple enough. Thanks.
Offline
Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
I think you are a victim of the common misunderstanding of what the [unstable] repo is. It's not like [testing], which may cause a breakage of something, a "playground" for updates to Arch packages. Unstable is a place for packages that aren't a "stable" release, meaning on of the following:
- A package that is a beta, or pre-release of something [gimp-devel falls into this category]
- A package compiled directly from developer repositories (svn, cvs, git, etc) [xfce-svn falls into this group]
Packages in unstable will never have the same names as packages in Current, Extra, or Testing, but may be direct replacements for another package. Examples: gimp-devel replaces gimp, xfce4-svn replaces xfce4, fvwm-devel replaces fvwm.
·¬»· i am shadowhand, powered by webfaction
Offline
ralvy wrote:Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
I think you are a victim of the common misunderstanding of what the [unstable] repo is. It's not like [testing], which may cause a breakage of something, a "playground" for updates to Arch packages. Unstable is a place for packages that aren't a "stable" release, meaning on of the following:
- A package that is a beta, or pre-release of something [gimp-devel falls into this category]
- A package compiled directly from developer repositories (svn, cvs, git, etc) [xfce-svn falls into this group]Packages in unstable will never have the same names as packages in Current, Extra, or Testing, but may be direct replacements for another package. Examples: gimp-devel replaces gimp, xfce4-svn replaces xfce4, fvwm-devel replaces fvwm.
This explains it completely. I was definitely under this misunderstanding.
Offline
Missing dependency of "fam"??
arch ~ 16:42 # thunar
thunar: error while loading shared libraries: libfam.so.0: cannot open shared ob ject file: No such file or directory
arch ~ 16:42 # pacman -Qi thunar-svn
Name : thunar-svn
Version : 23264-1
Groups : xfce4-svn-extra
Packager : Shadowhand <woody>
URL : http://www.xfce.org/
License : None
Architecture : i686
Size : 2612912
Build Date : Thu Oct 5 05:00:31 2006 UTC
Install Date : Mon Oct 16 03:41:34 2006 UTC
Install Script : No
Reason: : installed as a dependency for another package
Provides : None
Depends On : eject exo-svn gtk2 hal hicolor-icon-theme libxfce4util-svn
shared-mime-info
Required By : xfdesktop-svn
Conflicts With : thunar
Description : Thunar is a modern file manager for XfceRegards.
Offline
ralvy wrote:Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
I think you are a victim of the common misunderstanding of what the [unstable] repo is. It's not like [testing], which may cause a breakage of something, a "playground" for updates to Arch packages. Unstable is a place for packages that aren't a "stable" release, meaning on of the following:
- A package that is a beta, or pre-release of something [gimp-devel falls into this category]
- A package compiled directly from developer repositories (svn, cvs, git, etc) [xfce-svn falls into this group]Packages in unstable will never have the same names as packages in Current, Extra, or Testing, but may be direct replacements for another package. Examples: gimp-devel replaces gimp, xfce4-svn replaces xfce4, fvwm-devel replaces fvwm.
So I have a question : what if I have a package in stable which I find good, and if there is a svn version in unstable which I don't want ? Will the package be replaced by the one in unstable ?
Offline
shadowhand wrote:ralvy wrote:Once this happens, is there a way to have pacman avoid things in unstable, other than those related to Xfce?
I think you are a victim of the common misunderstanding of what the [unstable] repo is. It's not like [testing], which may cause a breakage of something, a "playground" for updates to Arch packages. Unstable is a place for packages that aren't a "stable" release, meaning on of the following:
- A package that is a beta, or pre-release of something [gimp-devel falls into this category]
- A package compiled directly from developer repositories (svn, cvs, git, etc) [xfce-svn falls into this group]Packages in unstable will never have the same names as packages in Current, Extra, or Testing, but may be direct replacements for another package. Examples: gimp-devel replaces gimp, xfce4-svn replaces xfce4, fvwm-devel replaces fvwm.
So I have a question : what if I have a package in stable which I find good, and if there is a svn version in unstable which I don't want ? Will the package be replaced by the one in unstable ?
No. The only way to have a package from [unstable] on your system is to explicitely install it with 'pacman -S'.
Offline
Ok, then if I need to install a package, it will firstly be taken in unstable if it exists, otherwise in stable ?
Offline
No. As Shadowhand said, the packages in unstable have different names than the ones in current/extra. You need to specify the correct name to pacman.For example, gimp is in current and gimp-devel is in unstable. If you want to use the stable gimp from current, you do 'pacman -S gimp'. If you want to use the unstable version of gimp (i.e. gimp-devel) from unstable, you do 'pacman -S gimp-devel'. If you choose to install gimp, you don't need to worry about having it replaced without your knowledge by gimp-devel. Because they have different package names, pacman treats them as two entirely different packages. The same goes for all packages in unstable,
Offline