Not a single package manager GUI?

There is not a single package manager GUI for archlinux. The one provided in community repo jacman is quite unstable and the gtkpacman in aur can even search packages.
How about porting http://www.packagekit.org/index.html to archlinux.

Phrodo_00 wrote:yes I was thinking about you and the couple of packagekit topics that have appeared... and not thinking as seroius intentions from arch, but from, you know, some guy, you seemed pretty decided in that post, looks like I was wrong then... anyway, now that I know you aren't really interested and I'm starting vacation at university (and starting to work in a job if I can find one) I might aswell start taking a look at libalpm (why is it called like that?) and packagekit and see if I come out with something.
From http://www.archlinux.org/pacman/ :
As of version 3.0, pacman has been lib-ified, with a backend library named 'libalpm' (Arch Linux Package Management). Speed in some cases has been improved, and this should allow us in the future to speed development of alternative front ends.
EDIT: however, some other guy nicknamed tradiaz said he was going to do it, not a lot about him has been heard though.
There are two recent commits from him, you can see them in gitweb for example :
http://gitweb.freedesktop.org/?p=packagekit.git
(look for alpm and the date of today)
But it looks far from complete if the table on the faq is uptodate:
http://www.packagekit.org/pk-faq.html

Similar Messages

Package Manager GUI permissions

I have a fresh install of Solaris 11, using LDAP to authenticate against a Windows 2008 R2 Active Directory server for login. This server is used for VNC desktop access for users, so I have all the desktop tools installed and working. I also have a second, bare-bones Solaris 11 server that is hosting the IPS repository. This is all working just peachy.
However, I seem to have a problem with the Package Manager GUI and LDAP users. I have an LDAP account I use for development and a separate, local account for doing admin stuff. I can install software with the Package Manager GUI using the admin account, but I can't seem to do this with my LDAP account. When i try and launch the GUI using the links on the desktop, I get nothing. If I try and use the "packagemanager" command from a terminal, I get an error pop-up that says "Could not operate on /var/pkg/lock because of insufficient permissions. Please try the command again as a privileged user." My LDAP account does have the "Software Installation" profile applied, and I can install packages using "pfexec" from a terminal, but I would really like to use the GUI (and let some of the other power users have access to install stuff too).
Oh and "pfexec packagemanager" does not work either (get a "Can't open display" error).
Any ideas what I am doing wrong?

Here is what I get when I run /'usr/lib/pm-launch /usr/bin/packagemanager'
No protocol specified
No protocol specified
/usr/lib/python2.6/vendor-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display
warnings.warn(str(e), _gtk.Warning)
No protocol specified
No protocol specified/
Unable to initialize gtk
could not open display
No errors in .xsession-errors. Also, if I run just /usr/bin/packagemanager I get the GUI, but it gives me the permission error, so I can definitely bring up X apps.

Managing JAVA JDK and JRE with Package Management in Solaris 11.1

I want to manage Java JDK & JRE in an Solaris environment using Package Management I'm currently running Solaris 11.1 in a VMWare host. My current latest Java release is JDK1.7.0_07 and JRE1.7.0_07. I want to upgrade to JDK1.7.0_17 & JRE1.7.0_17 using Package Management. I've tried on several occasions to upgrade to latest release of Java but I have not been successful. Each time I try using the Package Management GUI or use command line they appear to be successful but the new release does not show.
What could I be doing wrong?
Thanks

I also learned that the READMEs for the following patches in My Oracle Support also describe the downgrave process:
Patch 18362676: JAVA 6 DOWNGRADE INCORPORATION FOR ORACLE SOLARIS 11.1.15.4.0 AND 11.1.16.5.0
Patch 18362686: JAVA 7 DOWNGRADE INCORPORATION FOR ORACLE SOLARIS 11.1.15.4.0 AND 11.1.16.5.0
-- Alan

Package Manager OEL5R3 not working like it does in RHEL5R3

In Red Hat after you register with RHN, the Package Manager (Add/Remove Programs in the menu) will show a list of package groups that can be pulled from the installation media on the Browse tab. I have found this to be very helpful during initial setup of a system and it does not seem to work at all with OEL5R3.
I have been able to populate the List tab by setting up a yum repository, but was really hoping to see the package groups (which contain many pre-selected packages) in this tool.
I have done a lot of searching and there seems to be very limited information about this tool. When attempting to view the setup on a RHL box through the GUI the app dumps with a python error. The config files themselves do not appear to be straight up yum config files.
Anyone have this working? Does it work properly on R1 or R2?
Thank you...
-Andy

Time for me to clarify, again :)
1) RPM package groups are a supported feature for OEL, including the RPM tools.
2) The availability of package groups, along with their presentation offering
on the pirut, system-config-packages, or GNOME menu, depends on whether or
not a particular repository provides the necessary "comps.xml" definition
files. Without these files, pirut doesn't know anything about package
groups.
3) OEL installation media provides these "comps.xml" files, so RPM package
groups are available during initial installation.
4) The ULN Network has the files available for download, depending on the
channel subscriptions, but does not utilize them for the ability to download
or update on a package group basis.
5) Oracle offers a public YUM repository, where package groups may be used.
More details on this are on the http://public-yum.oracle.com web site,
including a "public-yum-{el4,el5,ovm2}.repo" definition file that can be
installed into "/etc/yum.repos.d/" for yum(8) access.
6) Once you have the public YUM repository setup from #5, you can use pirut,
system-config-packages, et. al., to install an RPM package group.
The catch is the packages will be from the original distribution media, so
after that you must "yum update" or "up2date --update" to get the latest
versions.
Hope this clarifies my earlier too-succinct response.

Data Guard Manager GUI does not respond

Hello,
I configured a standby datase environment using the Data Guard(9.0.1). Both, the primary and standby are 9.0.1
Few days ago, the standby crashed and i was getting an Ora-12500 error. To solve that error i had to recreate the oracle instance. After that, the primary established connection to the standby and shipped the logs which were applied by the stand. But when i connect to the Data Guard Manager GUI and click on my data guard configuration, the cursor shows up and keep running on the screen indicating that the DGMGUI is working on the background. I left DGMGUI running overnigth but it did not finished. I don't know what is the problem. Any hint ?
Thanks a lot.
Hardy.

You probably want to post this in the General Database forum.
Thanks.

[SOLVED] node package manager: command not found

I installed nodejs, and it was working fine. I updated a couple of days ago, and now npm install and npm lead to
zsh: command not found
Node has some naming conflicts, from what I have read. I am confused as to how the namespace for packages works, but hopefully someone can point me in the right direction with this because, while confusing, I don't think it is causing the problem. I usually execute the application as node, but it is in the repositories as nodejs. I found node in /usr/bin. I can execute npm there, but it advises that npm should be run in a normal shell with a different directory, not in /usr/bin. There was no nodejs or npm.
I removed nodejs using
pacman -Rdd nodejs
since adom has dependencies, but when I tried to reinstall using
pacman -S nodejs
, it said it was up to date and reinstalled. I updated my system and rebooted. I still can execute node but not the npm-it still returns
zsh: command not found: npm
I have no idea why the node package manager disappearred. I also have no idea why it would not have reinstalled with nodejs from the repo.
➜ ~ sudo pacman -Rdd node
[sudo] password for user:
error: target not found: node
➜ ~ nodejs npm
zsh: command not found: nodejs
➜ ~ node npm
module.js:338
throw err;
^
Error: Cannot find module '/home/user/npm'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:278:25)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
Last edited by 01010101 (2015-06-17 17:40:33)

➜ ~ pkgfile npm
zsh: command not found: pkgfile
➜ ~ sudo pacman -S pkgfile
resolving dependencies...
looking for inter-conflicts...
Packages (1): pkgfile-15-1
Total Download Size: 0.02 MiB
Total Installed Size: 0.05 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
pkgfile-15-1-x86_64 21.6 KiB 323K/s 00:00 [######################] 100%
(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%
(1/1) installing pkgfile [######################] 100%
==> Run 'pkgfile --update' to initialize the database
➜ ~ pkgfile npm
error: No repo files found. Please run `pkgfile --update'.
➜ ~ pkgfile --update
error: unable to write to /var/cache/pkgfile: Permission denied
➜ ~ sudo pkgfile --update
:: Updating 4 repos...
download complete: multilib [ 224.2 KiB 372K/s 3 remaining]
download complete: core [ 608.8 KiB 536K/s 2 remaining]
download complete: extra [ 6.9 MiB 2038K/s 1 remaining]
download complete: community [ 10.9 MiB 2.55M/s 0 remaining]
:: download complete in 4.26s < 18.6 MiB 4.37M/s 4 files >
:: waiting for 1 process to finish repacking repos...
➜ ~ pkgfile npm
community/npm
➜ ~ cd development/anj
➜ anj ls
app.js bin bower.json package.json public routes views
➜ anj npm install
zsh: command not found: npm

How to deploy EAR on CE server using Java Support Package Manager

Hello,
I am using CE server where I want to deploy EAR file by using JSPM. I run this program in Drive:\usr\sap\CE1\J00\j2ee\JSPM\go.bat
I have also put the EAR file into the inbox folder Drive:\usr\sap\CE1\SYS\EPS\in but still It does not show me any file to proceed further for deployment.
Does any one has idea?
Regards,
NK

Hi,
The Java Support Package Manager is not able to deploy a single .ear file.
If the *.EAR file is placed inside an SCA (Software Component Archive) then JSPM is able to deploy it.
You have to create a .SCA from an .EAR file
SAP note 1223957 contains an attachment (nwpacktool.zip) which can be used to create a .SCA file from the .EAR file.
Gerd

Suggestion for new package management scheme

As was talked about in the INCOMING thread, Arch is growing and the devs are having trouble keeping up with maintaining packages. Arch is becoming disorganized and messy.
Well, Xentac and I were discussing this for a while, and we both seem to like a voting system. Arch shouldn't try to maintain every package out there, it's simply a waste of effort. If only one or two people want a package, they can build it themselves, it's not hard with ABS.
Arch devs should focus on keeping packages high quality, up to date, etc. They can't do this if there's 10,000 packages. So the solution would be that a package won't be included in the official repos (current, extra, unstable) unless it gets a certain number of votes, showing that lots of people really want the package, and it's "essential".
I don't know how many votes a package would need, but that's a little thing. I would suggest all packages in Extra/Unstable initially go up for this voting (once we implement it) and we make the vote quota be a little lower for this initial slimming, and that'll cut down the repos right there. All those packages that no one uses (that wont even get one vote) can be cut away. People can always vote them back if they become popular.
I don't want to have to do things like KDE, GNOME, etc myself, but I really don't mind maintaining my own little customizations, like Rhythmbox w/ XINE support (instead of Gstreamer). This vote system simply makes sure that a package is worth the developers time.
This goes with my idea of Arch as the perfect "Base" distro. People can build what they want on top of it.
This idea would also remove STAGING, as Arch wouldn't be accepting outside packages (though you're free to run your own repo or post PKGBUILDs on the forum). TESTING would be still used of course.
Suggestions?

beniro wrote:
I haven't really seen a single post in this thread that is without some merit, or at least an attempt at input.
The great thing about not being a larger distro is that the situation isn't as pressurized. Still, though, we (meaning the community AND developers) still obviously want Arch to be the best it can be and that's what this thread is about.
So...are any of the ideas mentioned here feasible? What do you think would be the best solution to creating a package release system that can handle Arch's current growth?
What about implementing a vote-based system for everything not in current? Would this be done with a web-based interface by using "submitrequest/vote" or something...obviously only registered users should be voting, right?
Anyway, I think a great job is being done and this thread is simply a positive indication of the vitality of the community. I think most of us fully recognize the resources of our developers and are simply wanting to find a way for them to bring us the best possible product. Arch rules!
I agree. I think what we should do is just take this time that we have while Arch is still young and not as well known among the Linux community, and try to make it great, relieving the pressures that we'd get a lot of later (not to say that we wouldn't get any, just less, hopefully).
As for the package setup, isn't there some way that we could write some system to do this? I had mentioned it before. And, I just came up with a small system. It would work like this:
We get one main server, whose "job" would be to create and store packages, and users could download from that server to install, etc. Now, whenever someone on the package management team finds an updated version of a package, they could log in to a special area of the site meant specifically for those developers. Then, using the special program on the website/server, they could link to the .tar or .bz2 that contains the source and submit it, along with the file's information that would be included with the package when you install it (file name, version, etc.) into the web-based form. Then, they click submit, and the server processes that file after downloading it, runs a makepkg-type thing on it, and stores the produced package in a "Fresh" repository. Then, the developer can download the file and opt to test it. If they're sure that it's okay, then they can replace the new file over the old one.
Just an idea, tell me what you think... :?

ABS as an universal package manager

I've just had a rather interesting thought. I'm lately entertaining (and discussing) the idea of universal package management, self contained packages etc. As I've recently switched to Arch again, I thought about ABS as a system which actually reduces dependence on a single repository, a single rule-set so to speak and adds a great amount of flexibility. It may very well be the best way of utilizing the one universal packaging format that there currently is: source tarballs.
What if other distros started packaging and maybe even pre-installing ABS, or something similar? Any user of any other distro would only need a tool like yaourt to check up a mirror of all PKGBUILD's available in the whole GNU/Linux universe and initiate an install where the system would just follow the instructions laid down in the PKGBUILD.
Now, considering the flexibility of PKGBUILD's, you don't even need to have them all compile a given program on the user's computer. Instead of fetching a source tarball it could just fetch a binary tarball. The dependencies are still all pretty much the same (and stated and taken care of by the PKGBUILD instructions), the biggest difference is just that instead of compiling the user gets a pre-compiled package and the whole process is done much faster.
Anyway, I wonder what you think and if anyone has discussed this before. I think the PKGBUILD's may very well contain one possible solution to coming up with universal package management system, at least as an add-on to a given distro's base packaging system. And even as an add on, and especially with the ability to install binary and not just source tarballs (much like pacman in fact) may add a great amount of flexibility to a given distro's user that they may currently be missing.
Cheers
Last edited by libervisco (2008-07-04 02:25:39)

Stythys wrote:what's the point of having different distros if they all start trying to be the same?
There's no point at all there because that's not my point. The idea of universal package management is merely meant to increase compatibility, to provide a way to easily install the same piece of software using the same process on any distro. Imagine the benefits this could have for newbie users once such an option was further developed and polished. You could tell someone how to install a given program and it would work no matter what distro you run. As it is right now you have specific instructions per distro, not to mention that one distro has some software which another just doesn't.
It is not meant to replace the existing package management in these distros, just add a way to easily install software even without it, when it doesn't have what you need or when it's simply simpler for you to do it this way.
Stythys wrote:Anyways I seriously doubt other distros are just gonna start using ABS if asked. If you want pacman/ABS on a different system, just compile it yourself
Well, I agree they wont just adopt it. It would all be gradual. Someone starts compiling it for other distros and distributing it through a web site or where possible through community contributed repositories. If people like what they see they start using it more and more until some distros decide to include it by default. Depending on its success the extreme end result would be for it to be a common feature of *every* GNU/Linux system.
But yes, it does start with someone compiling it.
Stythys wrote:but then why not just use arch
Why aren't all GNU/Linux users the users of Arch?
ABS is by far not the only thing which differentiates Arch from others so it's not like putting ABS on other distros would result in them becoming exactly like Arch. That said, people have different preferences. Not everyone wants nor is knowledgeable enough to go through Arch's install process, for example.
Cheers

Pcurses - a curses package management tool

pcurses features package browsing and management in a curses frontend written in C++
Features:
* regexp filtering and searching any package property
* customizable colorcoding
* customizable sorting
* external command execution with package list string replacements
* user defined macros and hotkeys
Package management is done through external command execution: for example, '!sudo pacman -S %p' will install all currently queued packages.
For more information, read the README file at github and take a look at some of the defined macros in /etc/pcurses.conf.
Default hotkey mappings:
1 - filter packages with updates available
2 - filter installed packages
5 - run pacman -Syu
6 - run pacman -S on the current contents of the queue
7 - run pacman -Rs on the current contents of the queue
These macros are entirely customizable and are defined in /etc/pcurses.conf.
The default view optimized for 80x24 terminals:
And a 3 pane view for larger terminals:
Get it here: http://aur.archlinux.org/packages.php?ID=42685
Or, if you are using pacman-git: http://aur.archlinux.org/packages.php?ID=50804
Github: https://github.com/schuay/pcurses
Old thread from Nov 2010: https://bbs.archlinux.org/viewtopic.php?id=108585
For now, documentation is located mostly in the README file.
Keyboard commands are displayed by pressing the 'h' key in pcurses.
Last edited by schuay (2011-07-18 13:54:05)

Reposting the full tutorial from the README file:
QUICK TUTORIAL
Navigation and queue management
The package list and queue can be navigated using the up/down arrows, page
up/down, and the home and end keys. The tab key switches focus between the
package and queue lists.
Adding packages to the queue is done by pressing the right arrow key while the
package list is focused. Left arrow removes the selected package from the
queue.
Filtering
Keybindings are displayed by pressing the 'h' (Help) key in pcurses.
Filtering takes the following syntax:
nd:game 1 23
1 is a list of field specifiers. These tell pcurses which fields to search.
Field specifiers are the highlighted characters in the field names in the info
pane. In this example, this means that the Name and Description are searched
for the phrase 'game'.
2 the character ':' separates the field specifier list from the search phrase.
If this character is not present, the entire string is interpreted as the
search phrase.
3 is the actual search phrase. If it contains only alphanumeric characters, a
simple and quick string search is used. Otherwise, it is treated as a regular
expression (which is a bit slower). The search is case INSENSITIVE.
1 and 2 are OPTIONAL.
These searches can be chained. This means that a search for 'n:^a', followed by
'b:2010' will show all packages beginning with the letter 'a' and having a
build date in the year 2010.
Previous filters are cleared by pressing the 'c' key.
Pressing the up and down keys while in input mode will scroll through all
previous history.
Sorting and colorcoding
Colorcoding and sorting use the same syntax as filtering, but only accept a
single field specifier.
Command execution
Command execution can be entered by pressing the '!' key. The token '%p' will
be replaced by the current contents of the package queue. For example, with a
current package selection of pcurses and pacman,
!sudo pacman -S '%p'
will be expanded to
echo 'sudo pacman -S pcurses pacman'
A few useful commands could be
!pacman -Sy
!sudo pacman -S %p
!sudo pacman -Rs %p
Macros
Macros are defined in /etc/pcurses.conf using the syntax 'macroname=command'.
Macros can be chained by separating them with a comma. A few examples:
sortbyname=.n
colorbyrepo=;r
filterupdates=/d:update available
chainedmacro=@sortbyname,colorbyrepo,filterupdates
If defined, the macro named 'startup' will be executed on each application
start. Hotkeys can be defined by creating macros named '1', '2', [...], and are
triggered by pressing the corresponding key in pcurses.
All macros can be executed in pcurses by pressing the '@' key and entering the
macro name.
Last edited by schuay (2011-07-18 13:50:37)

[ABANDONED][Project] Wakka: A Gtk-Based Package Management Tool

==Summary==
Wakka is a loosely-GtkPacman based package manager, designed to cleanup the design of GtkPacman as well as the user interface, and update it to the latest and greatest releases of Python and pyGtk. It was originally developed as a project to make GtkPacman more stable on my own system, but I realized that many other users had the same problems that I did, thus the public release.
==History==
I found GtkPacman when I first came to Arch in 2009, being the GUI loving Ubuntu convert that I was, and I noticed that the last release had been in February of 2008, with no updates since, and no indication that the project was ongoing. Being a budding (and overconfident) Computer Science student I decided to take on the task of forking and maintaining this wonderful piece of software for the community. Yes, I could finally give back! Little did I realize that the task was far beyond my skills to accomplish.
I quickly found that cleaning this thing up enough for my own use was hard enough, and getting a decent realease out and dealing with bug reports and such would be neigh on impossible. It also didn't help that I had no idea what the heck pacman was doing in the backend, since apt and Synaptic were my only prior experience with package managers.
So there I lost steam, but from time to time I would open the code up and peck away at it, modifying bits here and there to work the way I wanted, but I eventually just took to the command line and lost sight of old Wakka. Well, just this last week I stumbled back upon it, and with my newfound pacman-fu and python-jitsu (not to mention free time) I decided to tackle this beast once and for all. I may not keep it up to date when I'm finished, and I may not even use the thing, but I'm going to clean this monster up and make it faster, more stable, and most of all more elegant (have you looked at the code for gtkPacman? It's not very elegant).
==Installation and Use==
You can now install Wakka from the AUR, but if you still wish to download and try other versions, you can grab a source tarball of any release from the project page on google code or get the newest stable release from the link below. You can also grab the bleeding edge (sometimes broken) svn code as well, but it's not useful for much other than development purposes.
Basically, unless you're going to dig through the code, use the AUR version, it's the safest.
==Files==
Pkgbuild: http://aur.archlinux.org/packages.php?ID=47037
Project: http://code.google.com/p/wakka-package-manager/
Source: http://wakka-package-manager.googlecode … .4.tar.bz2
==TODO==
- Speeeeed it up!
- Streamlining
- Bugfixes
Not particularly in that order, depending on the circumstances.
Last edited by minasmorath (2012-04-12 18:22:08)

swanson wrote:Just did a daily update/upgrade and it worked very nicely indeed! All events present themselves clearly during the process. For me, as new Arch user, it is very nice to get a list of all available packages in the repos. The overview and search capabilties are handy, much more so than doing pacman -Ss "xxxxx" in terminal.
I'm glad you like it!
pablokal wrote:when you install something the sizes are not given of the packages to be installed (also the sizes of the dependencies); would be nice if these sizes were given, just like in pacman.
I didn't even notice that, I'll add it asap.
pablokal wrote:Second when installing by default the terminal is closed.
I don't know about opening it up, but you're right, hiding things is bad practice, so at least a summary and a more clear indication that stuff is going on.
tomd123 wrote:can you provide a PKGBUILD in the aur?
Hopefully I can get the PKGBUILD up in the AUR within the next week, but I won't post it until everything is ported to Python 3 and I've done thorough testing. I also have a couple minor changes to make along the way, I don't like the way the update all button works right now, I'm changing it so that it just marks all changes in the install queue and alerts you of the packages to be updated, and I need to fix the 'required by' section of the package summary, since it uses an old method, and dependency size display.
All in all as soon as it's cleaned up I'll post it. I'll be going on spring break here in a week as well so I'll have plenty of time to work on it this week and next.
Thanks for the input, I'm on it!
Mitch

Package Manager Loop

I backed up my previous Solaris 10 install and then installed snv_86 i86pc (from a CD). There are several things I am trying to get back running (print server is a big issue) and have been trying to use Package Manager to upgrade the system. It informed me that SUNWipkg and SUNWipkg-gui must be upgraded first but then gets in a continuous loop upgrading SUNWipkg and SUNWipkg-gui. The first time it downloaded the files and restarted the application, but after that nothing is done (it takes time but the details window shows no activity and it indicates that 0 files were done). It still indicates that it is going to restart Package Manager (It no longer restarts). I thought that I might be able to solve it from the command line, but smpatch does not seem to be installed. Is there a command line tool that might work so that I can upgrade my system? What should I try?
Thanks,
wor

wroseland wrote:
I backed up my previous Solaris 10 install and then installed snv_86 i86pc (from a CD). It informed me that SUNWipkg and SUNWipkg-gui must be upgraded first but then gets in a continuous loop upgrading SUNWipkg and SUNWipkg-gui. Are you on Solaris or are you using the OpenSolaris Live CD?
Please cat /etc/release and post.
alan

Visual Studio 2013 Nuget Package Manager error

Hello everyone,
I tried to add and use OpenCV library in my Visual Studio javascript windows application project, but I still get the same error.
This is my Package manager console:
PM> Install-Package OpenCV
Installing 'OpenCV 2.4.8'.
Successfully installed 'OpenCV 2.4.8'.
Adding 'OpenCV 2.4.8' to BlankSharedApp1.Windows.
Uninstalling 'OpenCV 2.4.8'.
Successfully uninstalled 'OpenCV 2.4.8'.
Install failed. Rolling back...
Install-Package : Could not install package 'OpenCV 2.4.8'. You are trying to install this package into a project that targets 'Windows,Version=v8.1', but the
package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1
+ Install-Package OpenCV
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException
+ FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
Thanks for answers.

Hi Fačko,
Normally, we won't get any errors if we create a new project. Since you get this error when using OpenCV library and it is a third-party product, I think you need to ask in
OpenCV forum for better response.
Thank you for your understanding!
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Database Studio 7.9.08.09 - Could not access to user management; Deleting old settings and reinstallation did not bring a change -- database studio deinstallation cannot be performed anymore

Hi Community,
for a few months I have been struggling with a SAP Max DB database Studio issue and finally, I had to give up the idea of being able to fix this on my own. I am desperately seeking for help and I hope that you may be able to give me a hint, advice or even a solution.
This is what happened:
I used to run Windows 7 on 32bit. I also had Database Studio installed - which was running fine then.
After a harware upgrade, I am running now Windows 7 on a 64 bit System. All my files from my local disk (C:\) have been restored and copied onto my new system.
I reinstalled Database Studio Version 7.9.08.09 onto my new System. But on the first try to start the program I received the error that said "Could not Access to user Management.See Window -> Show View-> Event Log Viewer for more Details."
However the Event Log Viewer was empty.
After searching the web for a solution, I followed the advice given in this community and deinstalled Database Studio and deleted the C.\Users\MyAccount\sdb folder manually.
I reinstalled Database Studio and started it as Administrator.
However, the error is still appearing.
And, what makes it even worse is : now I am not able to uninstall Database Studio anymore.
When I run SAP MaxDB Installation Manager and select the instance of database Studio to be uninstallled I am receiving the error:
"ERR: Unhandled Exception: Can't call method: "GenPackageList" on an undefined value at SDB/Install/Gui/Dialogs/SelectInstance.pm line 328"
Any advice is highly appreciated.
Thanks,
Agnieszka

Hello Yashwanth,
thank you for your quick Response.
Yes, I downloaded and installed the 64 bit Version of dbstudio.
I downloaded and ran the following .exe file: maxdb-studio-win-64bit-x86_64-7_9_08_09.exe
I am running the following Java-Version:
Java Plug-in 1.6.0_45
Using JRE version 1.6.0_45-b06 Java HotSpot(TM) Client VM
I myself am not a SAP customer. However, the Company I am working for is a SAP customer.
Can you explain in Detail, how to create a ticket with SAP?
Thanks,
Agnieszka

How to delete a single entry from GUI History

All,
I want to delete a single line of GUI history.
This is my scenario. During the installation of SAPGui in the user system , we usually send the preconfigured MDB files also along with distribution. But by mistake i tyoed the administrator password in the user name of the login screen it gotupdated in the master MDB file . Now i wanted to delete the only that particular entry from GUI History.
PS I donot want to delete the entire MDB file and recreate again.
Any Info?
a®s
Edited by: a®s on Jul 7, 2009 10:56 AM

Hi,
It is very simple....
Here is how you can delete a particular entry from GUI History
1. Open the login screen.
2. Place cursor in "User Name" input field
3. Press spacebar on your keyboard. - This will show all entries from history
4. Scroll & highlight the entry you wish to delete using arrow keys on keyboard (Do not hit enter, just scroll....leave all entries visible)
5. Hit "Delete" button on your keyboard.
Hope this helps.
Regards,
-Abhijit

Not a single package manager GUI?

Similar Messages

Maybe you are looking for