Hi Salvatore
I think the repo you posted doesn’t contain any packages matching the pattern.
There are no spacewalk packages in EPEL.
Also drop the ‘-*’
‘+*whatever*’ is enough if you only need selected packages.
Try ‘+*aalib*’, that should give you a match.
Regards,
Javier
Von:
Hi William
I ran into similar issues and decided to build the packages for SLES 15 by
myself.
Yes, newt-python3 should be python3-newt. Not sure, but I guess Red Hat and
Suse have different naming conventions for packages. This is easy to fix in the
.spec file
The spacewalk-usix rpm was
Hi,
Have you already tried deleting the local caches (zypper clean -a) on your
sles11sp4 server?
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von
suhail.siddi...@visitor.upm.com
Gesendet: Mittwoch, 15. August 2018 12:03
An:
Hi
Please check the repository metadata on your spacewalk server in
/var/cache/rhn/repodata/YOURCHANNEL/
You can use spacecmd to regenerate the yumcache:
spacecmd -u USER "softwarechannel_regenerateyumcache YOURCHANNEL"
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
and dirty build. For production use you
should really build the packages by yourself.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Flores, Javier
(D4\INF\IT ID)
Gesendet: Donnerstag, 28. Juni 2018 16:15
An: 'spacewalk-list@redhat.com
list-boun...@redhat.com>
mailto:spacewalk-list-boun...@redhat.com>>
on behalf of Flores, Javier (D4\INF\IT ID)
mailto:javier.flo...@gmz.migros.ch>>
Sent: Thursday, June 28, 2018 3:12:37 AM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewalk-list] Adding SLE_SP3 client
Hi
Which re
Hi
Which repository at opensuse.org are you using?
You can find all the needed packages including python2-newt in this repository:
https://download.opensuse.org/repositories/systemsmanagement:/spacewalk:/2.8/SLE_12_SP3/
Other versions of the spacewalk client can be found here:
Hi Bob
There was a similar issue some months ago.
Maybe this can help:
https://www.redhat.com/archives/spacewalk-list/2018-January/msg00063.html
https://github.com/spacewalkproject/spacewalk/pull/617
I am still on Spacewalk 2.6 so I don’t know if it works, but it seems worth a
try.
Regards,
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>>
on behalf of Flores, Javier (D4\INF\IT ID)
<javier.flo...@gmz.migros.ch<mailto:javier.flo...@gmz.migros.ch>>
Sent: Thursday, December 14, 2017 10:18 AM
To: 'spacewalk-list@redhat.com'
Subject: Re: [Spacewa
Hi Matthias,
I am syncing SLES 12 repos on a daily basis. No problems so far, I get all the
3725 packages.
What I did was to first set up a SLES 12 SP3 VM and register it directly to
Suse. I then used "zypper lr --uri" to get the URI which contains the token and
copied that to the "Repository
Hi
What worked best for me is to just setup a SLES server and register to
scc.suse.com.
After finishing, just use "zypper lr --uri" to show the URL to the repo. Copy
that URL to spacewalk.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im
Hi,
I've had my Spacewalk server registered to itself for almost three years so far
without problems.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Dillon Mills
Gesendet: Dienstag, 1. August 2017 22:04
An:
Hi Ivan,
I just had to configure Spacewalk for Ubuntu last week. Check out this guide
(and the comments):
http://www.devops-blog.net/spacewalk/registering-ubuntu-and-debian-servers-with-spacewalk
It is a bit of work but you’ll get everything working.
Regards,
Javier
Von:
+ '/' + rel_url
-
+return urlparse.urlunsplit((scheme, netloc, path + '/' +
rel_url,query, fragid))
Thank you,
James
On Mon, Feb 20, 2017 at 10:23 AM, Flores, Javier (D4\INF\IT ID)
<javier.flo...@gmz.migros.ch<mailto:javier.flo...@gmz.migros.ch>> wrote:
No need to grab the U
/SUSE/Products/SLE-SERVER/12-SP2/x86_64/product?api_key/repodata/repomd.xml:
[Errno -1] Error importing repomd.xml for
SUSE_Products_SLE-SERVER_12-SP2_x86_64_product_api_key: Damaged repomd.xml file
Thank you,
James
On Fri, Feb 17, 2017 at 10:34 AM, Flores, Javier (D4\INF\IT ID)
<javier.
Hi James,
I have Spacewalk 2.6 running on CentOS since December and syncing SLES 12
channels works.
How did you get the URI with the long key? Did you register a VM directly to
Suse and copied the URL from the zypper repos of that VM?
The only issue I had after upgrading to Spacewalk 2.6 was
ace("&",
"_").replace("=", "_")
Repository sync works but I don't know if this has an impact on other areas of
spacewalk. Use with caution.
Regards,
Javier
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auf
Hello,
I just updated my test server to Spacewalk 2.6 and now I have problems syncing
Suse channels. The problem seems to be that spacewalk-repo-sync changed the way
it is naming the cache directories.
What used to be /var/cache/rhn/reposync/sle-module-adv-systems-management-12 is
now
Hi Matthias,
You can manage the entitlements in the “Spacewalk Default Organization” under
Admin > Subscriptions > “System Entitlements”. Click on “Provisioning (Add-On)”
and then Organizations.
Make sure the organization in which your spacewalk proxy is in, has enough
entitlements.
Regards,
Hi Jineesh,
The URL without rpm/x86_64 should work but maybe there is something wrong with
the credentials.
Please try to sync by using the organization credentials you find in the SUSE
Customer Center. Login to scc.suse.com then click on Organization ->
Organization Credentials.
Regards,
Hi,
It's the same procedure as for CentOS. First create the repositories, then
create a channel and add the repositories to that channel.
SLES11 Repos are hosted by Novell. My "Repository URL" looks something like
https://username:passw...@nu.novell.com/repo/$RCE/SLES11-SP...
Regards,
Javier
fo timezone usbutils xorg-x11-Xvnc
zypp-plugin-spacewalk
Chris Will
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Flores, Javier
(D4\INF\IT ID)
Sent: Wednesday, January 13, 2016 6:40 AM
To: spacewalk-list@redhat.com
Sub
Hi Klaas,
I have been using one base channel for every major release (sles11, sles12) and
child channels per service pack (sles11-sp3-pool, sles11-sp3-updates,
sles11-sp4-pool, sles11-sp4-updates etc.)
To update from SLES 11 SP3 to SLES 11 SP4 I have simply added the SP4 channels
to a SP3
How about
# spacecmd get_serverversion
? Works on my server with 2.2 and 2.3
Regards,
Javier
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Tomas Lestach
Gesendet: Mittwoch, 12. August 2015 11:41
An:
24 matches
Mail list logo
