Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - Unauthorized" for ULN repository

2018-03-26 Thread Sadri, Wafa (BITBW) 
Hi everyone,

SW 2.7 does not support the ULN! I’ve had a support ticket with oracle 
regarding this issue and after 3 weeks they told me that since the new 
repo-sync is now used, ULN sync doesn’t work anymore. So if you want to use ULN 
repos, you have to use SW 2.6 or use the public yum repos form oracle instead 
(which is what we ended up doing).

regards,
Wafa

Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Nicole Beck
Gesendet: Montag, 26. März 2018 21:44
An: 'spacewalk-list@redhat.com' 
Betreff: Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - 
Unauthorized" for ULN repository

Thank you Avi.
Nicole

From: 
spacewalk-list-boun...@redhat.com 
mailto:spacewalk-list-boun...@redhat.com>> 
On Behalf Of Avi Miller
Sent: Monday, March 26, 2018 3:26 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - 
Unauthorized" for ULN repository

Hi,

On 27 Mar 2018, at 5:37 am, Nicole Beck 
mailto:nsky...@syr.edu>> wrote:

I’m trying to setup channels for Oracle Linux on my Spacewalk 2.7 server 
(running  CentOS 7), but the spacewalk-repo-sync is failing with the 
“unauthorized” error below.

Hmm. That’s interesting (because the ULN connection worked sufficiently to get 
the number of packages to download. It’s just when it tries to grab the 
individual package that it breaks.

We’re still in the process of building and testing our 2.7 release, but I’ll 
check with development in case we encountered the same issue.

Thanks,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk and Oracle Linux

2018-03-26 Thread Avi Miller 
Hi,

> On 27 Mar 2018, at 6:58 am, Nicole Beck  wrote:
> 
> We are still doing some R&D of spacewalk and my test server is CentOS. I 
> thought about building on Oracle Linux if we go production with it. Doesn’t 
> the Oracle build of Spacewalk require an Oracle database, vs postgres?

Yes, it does, but we include a limited-use license for Oracle Database 
Enterprise Edition at no cost for use with Spacewalk: 
https://docs.oracle.com/cd/E52668_01/E63013/html/ol7-lic-restricted.html 


Thanks,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk and Oracle Linux

2018-03-26 Thread Nicole Beck 
Hi Avi,
We are still doing some R&D of spacewalk and my test server is CentOS. I 
thought about building on Oracle Linux if we go production with it. Doesn’t the 
Oracle build of Spacewalk require an Oracle database, vs postgres?

I really appreciate your help!
Nicole

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Avi Miller
Sent: Monday, March 26, 2018 3:22 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk and Oracle Linux

Hi,



On 27 Mar 2018, at 12:58 am, Nicole Beck 
mailto:nsky...@syr.edu>> wrote:

Will the ULN clients that get patched with a Spacewalk instance running on 
CentOS still be eligible for Oracle support?

Yes. As long as the packages you’re installing on your Oracle Linux servers are 
signed by Oracle (i.e. are synced from yum.oracle.com or 
ULN), you will get support. However, we will not support your Spacewalk 
instance or any issues you have connecting your Oracle Linux servers to that 
instance.

Frankly, it makes way more sense to deploy the Oracle build of Spacewalk on 
Oracle Linux 7 so that you have a fully supported stack and then you can update 
your CentOS instances from that. You don’t get support for CentOS anyway, so 
there is zero loss here, but you gain support for the Spacewalk infrastructure.

Cheers,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - Unauthorized" for ULN repository

2018-03-26 Thread Nicole Beck 
Thank you Avi.
Nicole

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Avi Miller
Sent: Monday, March 26, 2018 3:26 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - 
Unauthorized" for ULN repository

Hi,


On 27 Mar 2018, at 5:37 am, Nicole Beck 
mailto:nsky...@syr.edu>> wrote:

I’m trying to setup channels for Oracle Linux on my Spacewalk 2.7 server 
(running  CentOS 7), but the spacewalk-repo-sync is failing with the 
“unauthorized” error below.

Hmm. That’s interesting (because the ULN connection worked sufficiently to get 
the number of packages to download. It’s just when it tries to grab the 
individual package that it breaks.

We’re still in the process of building and testing our 2.7 release, but I’ll 
check with development in case we encountered the same issue.

Thanks,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - Unauthorized" for ULN repository

2018-03-26 Thread Avi Miller 
Hi,

> On 27 Mar 2018, at 5:37 am, Nicole Beck  wrote:
> 
> I’m trying to setup channels for Oracle Linux on my Spacewalk 2.7 server 
> (running  CentOS 7), but the spacewalk-repo-sync is failing with the 
> “unauthorized” error below.

Hmm. That’s interesting (because the ULN connection worked sufficiently to get 
the number of packages to download. It’s just when it tries to grab the 
individual package that it breaks.

We’re still in the process of building and testing our 2.7 release, but I’ll 
check with development in case we encountered the same issue.

Thanks,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk and Oracle Linux

2018-03-26 Thread Avi Miller 
Hi,


> On 27 Mar 2018, at 12:58 am, Nicole Beck  wrote:
> 
> Will the ULN clients that get patched with a Spacewalk instance running on 
> CentOS still be eligible for Oracle support?   

Yes. As long as the packages you’re installing on your Oracle Linux servers are 
signed by Oracle (i.e. are synced from yum.oracle.com  
or ULN), you will get support. However, we will not support your Spacewalk 
instance or any issues you have connecting your Oracle Linux servers to that 
instance.

Frankly, it makes way more sense to deploy the Oracle build of Spacewalk on 
Oracle Linux 7 so that you have a fully supported stack and then you can update 
your CentOS instances from that. You don’t get support for CentOS anyway, so 
there is zero loss here, but you gain support for the Spacewalk infrastructure.

Cheers,
Avi

---
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] spacewalk-repo-sync gives "HTTPS Error 401 - Unauthorized" for ULN repository

2018-03-26 Thread Nicole Beck 
Hi,
I'm trying to setup channels for Oracle Linux on my Spacewalk 2.7 server 
(running  CentOS 7), but the spacewalk-repo-sync is failing with the 
"unauthorized" error below.

[root@spacewalk rpm-gpg]# spacewalk-repo-sync --type uln 
--channel=ol6_x86_64_spacewalk26_client 
--url=uln:///ol6_x86_64_spacewalk26_client --verbose
14:03:49 ==
14:03:49 | Channel: ol6_x86_64_spacewalk26_client
14:03:49 ==
14:03:49 Sync of channel started.
14:03:49 Repo URL: uln:///ol6_x86_64_spacewalk26_client
The download URL is: 
https://linux-update.oracle.com/XMLRPC/GET-REQ/ol6_x86_64_spacewalk26_client
14:03:52 Packages in repo:56
14:03:52 Packages already synced:  0
14:03:52 Packages to sync:40
14:03:52 New packages to download:40
14:03:52 Downloading total 40 files from 1 queues.
14:03:52 ERROR: Download failed: 
https://linux-update.oracle.com/XMLRPC/GET-REQ/ol6_x86_64_spacewalk26_client/getPackage/jabberpy-0.5-0.21.el6.noarch.rpm
 - [Errno 14] HTTPS Error 401 - Unauthorized.


I put my ULN username and password in /etc/rhn/spacewalk-repo-sync/uln.conf, 
and the permissions are 0400. I verified that the username and password are 
correct by copying and pasting from this file into the login for 
https://uln.oracle.com.  If I put the wrong password in uln.conf, I get the 
"Fault 60: Invalid username or password" error when running 
spacewalk-repo-sync, so I'm assuming the file is correct.

I tried stopping Spacewalk, removing the appropriate subdirectories in 
/var/cache/rhn/reposync/1/ and restarting Spacewalk, but this did not help.  
Does anyone have suggestions? The directions at 
https://github.com/spacewalkproject/spacewalk/blob/master/backend/README.ULN 
are pretty straightforward, but I'm obviously missing something.
Thanks.
Nicole
Nicole Beck
Information Technology Analyst
Information Technolgy Services - Core Infrustructure Services - Unix

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Using Spacewalk with SLES 12 repositories

2018-03-26 Thread Flores, Javier (D4\INF\IT ID) 
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,
Javier

Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von bdus...@luzerne.edu
Gesendet: Montag, 26. März 2018 17:10
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Using Spacewalk with SLES 12 repositories

I've been encountering a problem configuring SLES 12 repositories with 
Spacewalk.   This problem seems to have been addressed before (i.e. 
https://www.redhat.com/archives/spacewalk-list/2015-February/msg00012.html), 
but this patch doesn't work for me.

The problem appears to be with the repositories themselves.   SUSE requires a 
token to be placed at the end of their repository URLs.  Without the token the 
http server returns a status of 403.

I've placed the URL with associated token in my repository config.   Entering 
this URL into a browser loads the repository perfectly.   When Spacewalk 
attempts to access the repository it needs to access the repomd.xml file which 
it appends to the URL.   This appears to be done incorrectly.

Note the original URL is:
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere

When Spacewalk attempts to access the URL to sync it appends 
/repodata/repomd.xml to the URL as follows:

https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere/repodata/repomd.xml

This is incorrect, it should be:

https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/repodata/repomd.xml?tokenGoesHere

The last URL works fine when placed in a browser.

Note the following from the Spacewalk logs

2018/03/26 10:53:58 -04:00 Repo URL: 
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHerehttps://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere/repodata/repomd.xml:
 [Errno -1] Error importing repomd.xml for SLES12-SP3-Pool x86_64: Damaged 
repomd.xml file

2018/03/26 10:54:01 -04:00 ERROR: failure: repodata/repomd.xml from 
SLES12-SP3-Pool x86_64: [Errno 256] No more mirrors to try.
The damaged repomd.xml file is caused by the 403 status return from the server.

It looks like the initial fix (referenced in the link in my first paragraph) 
was to apply a diff to the Python urlgrabber source.   This diff doesn't work 
for me.   Since it's dated back in 2014 it's possible my source for urlgrabber 
is much newer and not compatible with the diff.

Does anyone have Spacewalk working with the SLES 12 repositories?

I'm using Spacewalk 2.7.

Thanks!
Bob









The contents of this email message and any attachments originating from Luzerne 
County Community College's email system are for the intended recipients only 
and may contain confidential and/or privileged information legally protected 
from disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert the 
sender by replying to the email and then deleting the message and any 
attachments. Also, if you are not the intended recipient, you are hereby 
notified that any use, dissemination, copying, or storage of this message or 
its attachments is strictly prohibited.



Luzerne County Community College

"Northeastern Pennsylvania's Community College"

www.luzerne.edu

800-377-5222
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Using Spacewalk with SLES 12 repositories

2018-03-26 Thread bdushok 
I've been encountering a problem configuring SLES 12 repositories with Spacewalk.   This problem seems to have been addressed before (i.e. https://www.redhat.com/archives/spacewalk-list/2015-February/msg00012.html), but this patch doesn't work for me.
 
The problem appears to be with the repositories themselves.   SUSE requires a token to be placed at the end of their repository URLs.  Without the token the http server returns a status of 403.  
 
I've placed the URL with associated token in my repository config.   Entering this URL into a browser loads the repository perfectly.   When Spacewalk attempts to access the repository it needs to access the repomd.xml file which it appends to the URL.   This appears to be done incorrectly.
 
Note the original URL is:
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere
 
When Spacewalk attempts to access the URL to sync it appends /repodata/repomd.xml to the URL as follows:
 
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere/repodata/repomd.xml
 
This is incorrect, it should be:
 
https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product/repodata/repomd.xml?tokenGoesHere
 
The last URL works fine when placed in a browser.
 
Note the following from the Spacewalk logs
2018/03/26 10:53:58 -04:00 Repo URL: https://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHerehttps://updates.suse.com/SUSE/Products/SLE-SERVER/12-SP3/x86_64/product?tokenGoesHere/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for SLES12-SP3-Pool x86_64: Damaged repomd.xml file
2018/03/26 10:54:01 -04:00 ERROR: failure: repodata/repomd.xml from SLES12-SP3-Pool x86_64: [Errno 256] No more mirrors to try.
The damaged repomd.xml file is caused by the 403 status return from the server.
 
It looks like the initial fix (referenced in the link in my first paragraph) was to apply a diff to the Python urlgrabber source.   This diff doesn't work for me.   Since it's dated back in 2014 it's possible my source for urlgrabber is much newer and not compatible with the diff.
 
Does anyone have Spacewalk working with the SLES 12 repositories?  
 
I'm using Spacewalk 2.7.
 
Thanks!
Bob
 
 
 
 




The contents of this email message and any attachments originating from Luzerne County Community College's email system are for the intended recipients only and may contain confidential and/or privileged information legally protected from disclosure.   If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by replying to the email and then deleting the message and any attachments.   Also, if you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited.



Luzerne County Community College

"Northeastern Pennsylvania's Community College"

www.luzerne.edu

800-377-5222

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk and Oracle Linux

2018-03-26 Thread Nicole Beck 
Hi Avi,
Will the ULN clients that get patched with a Spacewalk instance running on 
CentOS still be eligible for Oracle support?   
Thanks!
Nicole

-Original Message-
From: spacewalk-list-boun...@redhat.com  On 
Behalf Of Avi Miller
Sent: Friday, March 23, 2018 4:56 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk and Oracle Linux

Hi,


> On 24 Mar 2018, at 7:47 am, Nicole Beck  wrote:
> 
> I want to use spacewalk to manage patches for both CentOS and Oracle Linux.  
> Is it possible to do this with my Spacewalk server that is running CentOS? Or 
> does the Spacewalk server have to be running Oracle Linux?

You can use the Spacewalk instance running on CentOS, but it would not be 
eligible for support from Oracle. 

Cheers,
Avi

--
Oracle 
Avi Miller | Product Management Director | +61 (3) 8616 3496 Oracle Linux and 
Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia


___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

2018-03-26 Thread Ananda Arifianto 
Hi Sadri,

Yes, I already synced the repository into the channel.
[cid:image003.png@01D3C52F.E2331650]

Any suggestion?

Best Regards,

Ananda Arifianto

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Sadri, Wafa (BITBW)
Sent: Monday, March 26, 2018 5:57 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

Hi,

have you downloaded any packages into that channel (i.e. did you do a 
repo-sync)?
You need to install the authentication certificates for your RHN registered 
server into spacewalk to do so.

regards,
Wafa

Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Ananda Arifianto
Gesendet: Montag, 26. März 2018 12:08
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

Hi,

I have environment as detail below :


-  Server spacewalk 2.7 using RHEL 7.4

-  2 Clients using RHEL 7.2

I already created channel & 1 repository. Repository sync from 
rhel-7-server-rpms (Redhat subscription).
When I try yum repolist from client, there is no packages available from this 
channel.
[cid:image004.jpg@01D3C52F.E2331650]
I saw certificate verify failed, how to solve this?
FYI, I've configured the repository as detail below
[cid:image005.jpg@01D3C52F.E2331650]

Please advice..

Best Regards,

Ananda Arifianto
The information in this e-mail is confidential and is transmitted strictly for 
the addressee/s. If you receive this e-mail in error, please notify the sender 
and delete it immediately. Copying and/or disseminating the contents are 
prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the 
accuracy or completeness of this email and any views expressed herein do not 
necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
The information in this e-mail is confidential and is transmitted strictly for 
the addressee/s. If you receive this e-mail in error, please notify the sender 
and delete it immediately. Copying and/or disseminating the contents are 
prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the 
accuracy or completeness of this email and any views expressed herein do not 
necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

2018-03-26 Thread Sadri, Wafa (BITBW) 
Hi,

have you downloaded any packages into that channel (i.e. did you do a 
repo-sync)?
You need to install the authentication certificates for your RHN registered 
server into spacewalk to do so.

regards,
Wafa

Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Ananda Arifianto
Gesendet: Montag, 26. März 2018 12:08
An: spacewalk-list@redhat.com
Betreff: [Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

Hi,

I have environment as detail below :


-  Server spacewalk 2.7 using RHEL 7.4

-  2 Clients using RHEL 7.2

I already created channel & 1 repository. Repository sync from 
rhel-7-server-rpms (Redhat subscription).
When I try yum repolist from client, there is no packages available from this 
channel.
[cid:image001.jpg@01D3C501.E2E00E10]
I saw certificate verify failed, how to solve this?
FYI, I've configured the repository as detail below
[cid:image002.jpg@01D3C501.E2E00E10]

Please advice..

Best Regards,

Ananda Arifianto
The information in this e-mail is confidential and is transmitted strictly for 
the addressee/s. If you receive this e-mail in error, please notify the sender 
and delete it immediately. Copying and/or disseminating the contents are 
prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the 
accuracy or completeness of this email and any views expressed herein do not 
necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Client Can't Connect to Spacewalk Repo [Redhat]

2018-03-26 Thread Ananda Arifianto 
Hi,

I have environment as detail below :


-  Server spacewalk 2.7 using RHEL 7.4

-  2 Clients using RHEL 7.2

I already created channel & 1 repository. Repository sync from 
rhel-7-server-rpms (Redhat subscription).
When I try yum repolist from client, there is no packages available from this 
channel.
[cid:image002.jpg@01D3C525.0287C370]
I saw certificate verify failed, how to solve this?
FYI, I've configured the repository as detail below
[cid:image003.jpg@01D3C525.0287C370]

Please advice..

Best Regards,

Ananda Arifianto
The information in this e-mail is confidential and is transmitted strictly for 
the addressee/s. If you receive this e-mail in error, please notify the sender 
and delete it immediately. Copying and/or disseminating the contents are 
prohibited. PT Bank Danamon Indonesia, Tbk. shall not be responsible for the 
accuracy or completeness of this email and any views expressed herein do not 
necessarily reflect the views of PT Bank Danamon Indonesia, Tbk.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list