Re: [CentOS] CentOS ISO contents

2016-10-07 Thread Johnny Hughes
On 10/03/2016 05:56 AM, Harry Mallon wrote:
> On the download page https://wiki.centos.org/Download it lists: DVD, Minimal, 
> Everything, LiveGNOME, LiveKDE.
> 
> Where can I find the lists of packages contained in each one without 
> downloading and extracting them? Is there a repo with the scripts that make 
> them maybe?
> 

Well, lists of packages are not really important wrt Everything (it has
everything listed in the /os/ directory on mirror.centos.org) .. or DVD,
as DVD has everything that can be installed via the GUI installer on
that DVD.

It does happen that the files used to create those ISOs are here
(minimal, dvd):

http://bit.ly/2dSMP4A

The LiveGNOME nad LiveKDE create scripts are here:

http://bit.ly/2dZFMqk

Thanks,
Johnny Hughes






signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Kerberized NFS client and slow user write performance

2016-10-07 Thread Matt Garman
We seem to be increasingly hit by this bug:

https://access.redhat.com/solutions/2040223
"On RHEL 6 NFS client usring kerberos (krb5), one user experiences
slow write performance, another does not"

You need a RH subscription to see that in its entirety.  But the
subject basically says it all: randomly, one or more users will be
subjected to *terrible* NFS write performance that persists until
reboot.

There is a root cause shown, but that is cryptic to non-kernel devs;
it doesn't explain from a user perspective what triggers this state.
(That's why it appears to be random to me.)

There is no solution or workaround given.  This appears to be on a
per-user + per-server basis, so a crude workaround is to migrate the
user to a different server.  And we do regular reboots, which somewhat
hides the problem.

My question to the list: has anyone else dealt with this?  The link
says "Solution in Progress", but that was last updated nearly a year
ago.  We don't have any support contracts with upstream, just the
website access subscription, so I doubt RH will offer any help.
Appreciate any suggestions!

Thanks,
Matt
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS-announce Digest, Vol 140, Issue 4

2016-10-07 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. [Infra] - CentOS Bug tracker migration /  maintenance window
  (Fabian Arrotin)


--

Message: 1
Date: Fri, 7 Oct 2016 08:03:37 +0200
From: Fabian Arrotin <arr...@centos.org>
To: "The CentOS developers mailing list." <centos-de...@centos.org>,
centos-annou...@centos.org
Subject: [CentOS-announce] [Infra] - CentOS Bug tracker migration /
maintenance window
Message-ID: <d9892bbc-f65b-ca04-a824-154c1e2b2...@centos.org>
Content-Type: text/plain; charset="utf-8"

We have to upgrade our current MantisBT instance for the CentOS bug
tracker service (aka https://bugs.centos.org)

Migration is scheduled for """"Friday october 7th, 12:15 pm UTC time"""".
You can convert to local time with $(date -d '2016-10-7 12:15 UTC'')

The expected "downtime" is estimated to ~15 minutes , time needed to
update MantisBT code, run the mysql schema update, and then put the node
back in production mode.

Thanks for your comprehending and patience.

on behalf of the Infra team,
-- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab

-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: 
<http://lists.centos.org/pipermail/centos-announce/attachments/20161007/26595c7e/attachment-0001.sig>

--

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce


End of CentOS-announce Digest, Vol 140, Issue 4
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] porting spec files

2016-10-07 Thread Ned Slider

On 07/10/16 10:17, Alice Wonder wrote:



On 10/07/2016 01:44 AM, Ned Slider wrote:

On 06/10/16 22:50, Alice Wonder wrote:

An rpm intended for a bleeding edge Fedora builds perfectly for me when
I comment two macros apparently not in CentOS 7 -

%transfiletriggerin

and

%transfiletriggerun

Looks like they operate similar to %post and %postun but are different.

Is a simple way to do what they do in CentOS 7 or do I have to change
the packaging logic to build in CentOS 7 and have things work properly?



These are file triggers, they trigger scripts to run when specific files
are added or removed from the system when packages are (un)installed.
See here:

http://www.rpm.org/wiki/FileTriggers


Whilst RHEL's version of RPM doesn't support file triggers, it does
support package triggers, so maybe you could devise a workaround with
those:

http://rpm.org/api/4.4.2.2/triggers.html




Okay it looks like what is happening is the triggers are used when
plugins are installed, and the CentOS 7 way is to run those triggers in
the post/pre scriptlets of the packages that have the plugins.



Yes, that is the preferred method and is OK as long as you also have 
packaging control over the packages that provide the plugins. The point 
of the file triggers is for when that is not the case.


Generally, triggers should be used sparingly (as a last resort) as they 
have a tendency to complicate matters rather than simplify, and thus 
make troubleshooting issues much harder.


For example, you package some software that needs to do something every 
time the kernel is updated. You don't have control over the kernel 
package, so you use a trigger in your own package - either a package 
trigger if the action needs to be performed every time the kernel 
package is (un)installed/updated, or a file trigger if it's when a 
specific file is (un)installed/updated.


The reason it makes things hard to troubleshoot is that, using the 
example above, the kernel is updated and that triggers your script in 
package Foo and something goes wrong. You've narrowed it down to 
happening every time you update the kernel package so naturally you now 
spend an age going through the kernel SPEC file trying to find the cause 
but of course you are looking in the wrong place and will never find it.



Probably better to have the file trigger conceptually, less chance for
scriptlet bugs, but CentOS 8 will come soon enough I suppose ;)



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] porting spec files

2016-10-07 Thread Alice Wonder



On 10/07/2016 01:44 AM, Ned Slider wrote:

On 06/10/16 22:50, Alice Wonder wrote:

An rpm intended for a bleeding edge Fedora builds perfectly for me when
I comment two macros apparently not in CentOS 7 -

%transfiletriggerin

and

%transfiletriggerun

Looks like they operate similar to %post and %postun but are different.

Is a simple way to do what they do in CentOS 7 or do I have to change
the packaging logic to build in CentOS 7 and have things work properly?



These are file triggers, they trigger scripts to run when specific files
are added or removed from the system when packages are (un)installed.
See here:

http://www.rpm.org/wiki/FileTriggers


Whilst RHEL's version of RPM doesn't support file triggers, it does
support package triggers, so maybe you could devise a workaround with
those:

http://rpm.org/api/4.4.2.2/triggers.html




Okay it looks like what is happening is the triggers are used when 
plugins are installed, and the CentOS 7 way is to run those triggers in 
the post/pre scriptlets of the packages that have the plugins.


Probably better to have the file trigger conceptually, less chance for 
scriptlet bugs, but CentOS 8 will come soon enough I suppose ;)


--
-=-
Sent my from my laptop, may not be able to respond timely
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] porting spec files

2016-10-07 Thread Ned Slider

On 06/10/16 22:50, Alice Wonder wrote:

An rpm intended for a bleeding edge Fedora builds perfectly for me when
I comment two macros apparently not in CentOS 7 -

%transfiletriggerin

and

%transfiletriggerun

Looks like they operate similar to %post and %postun but are different.

Is a simple way to do what they do in CentOS 7 or do I have to change
the packaging logic to build in CentOS 7 and have things work properly?



These are file triggers, they trigger scripts to run when specific files 
are added or removed from the system when packages are (un)installed. 
See here:


http://www.rpm.org/wiki/FileTriggers


Whilst RHEL's version of RPM doesn't support file triggers, it does 
support package triggers, so maybe you could devise a workaround with those:


http://rpm.org/api/4.4.2.2/triggers.html


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS-announce] [Infra] - CentOS Bug tracker migration / maintenance window

2016-10-07 Thread Fabian Arrotin
We have to upgrade our current MantisBT instance for the CentOS bug
tracker service (aka https://bugs.centos.org)

Migration is scheduled for Friday october 7th, 12:15 pm UTC time.
You can convert to local time with $(date -d '2016-10-7 12:15 UTC'')

The expected "downtime" is estimated to ~15 minutes , time needed to
update MantisBT code, run the mysql schema update, and then put the node
back in production mode.

Thanks for your comprehending and patience.

on behalf of the Infra team,
-- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab



signature.asc
Description: OpenPGP digital signature
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce