Re: fedora-release-$PRODUCT, /etc/issue, /etc/os-release, Per-Product Configs and more!

2014-07-06 Thread William
On Thu, 2014-07-03 at 10:05 -0400, Josh Boyer wrote: > On Thu, Jul 3, 2014 at 9:57 AM, Stephen Gallagher wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On 07/03/2014 01:42 AM, William wrote: > >> On Wed, 2014-07-02 at 20:40 -0700, Samuel Sieb wrote: > >>> On 07/02/2014 06:55

Re: Package reviev : tayga

2014-07-06 Thread William
After some review in bugzilla, some progress from me, some time to collect dust I have once again turned to look at getting tayga into fedora. https://bugzilla.redhat.com/show_bug.cgi?id=1028206 https://copr.fedoraproject.org/coprs/firstyear/tayga/ Any help and advice is appreciated! -- Willi

WARNING: malicious code (was: Re: [Announce] Simple Patch Policy)

2014-07-06 Thread Till Maas
On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: > * A script automating most of the process of validating and processing the > request can be found at > > https://github.com/manisandro/fedora-process-simple-patch/blob/master/process-simple-patch.py Do not run this script, because i

Re: WARNING: malicious code (was: Re: [Announce] Simple Patch Policy)

2014-07-06 Thread drago01
On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: > On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: > >> * A script automating most of the process of validating and processing the >> request can be found at >> >> https://github.com/manisandro/fedora-process-simple-patch/blob/master/pr

Re: WARNING: malicious code

2014-07-06 Thread Sandro Mani
On 06.07.2014 13:38, drago01 wrote: On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: * A script automating most of the process of validating and processing the request can be found at https://github.com/manisandro/fedora-process

Re: WARNING: malicious code

2014-07-06 Thread Igor Gnatenko
Hi, On Sun, Jul 6, 2014 at 3:41 PM, Sandro Mani wrote: > > On 06.07.2014 13:38, drago01 wrote: >> >> On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: >>> >>> On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >>> * A script automating most of the process of validating and process

Re: WARNING: malicious code

2014-07-06 Thread Reindl Harald
Am 06.07.2014 13:41, schrieb Sandro Mani: > On 06.07.2014 13:38, drago01 wrote: >> On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: >>> On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >>> * A script automating most of the process of validating and processing the re

Re: WARNING: malicious code

2014-07-06 Thread Sandro Mani
On 06.07.2014 13:46, Igor Gnatenko wrote: Hi, On Sun, Jul 6, 2014 at 3:41 PM, Sandro Mani wrote: On 06.07.2014 13:38, drago01 wrote: On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: * A script automating most of the process o

Re: WARNING: malicious code

2014-07-06 Thread Sandro Mani
On 06.07.2014 13:48, Reindl Harald wrote: Am 06.07.2014 13:41, schrieb Sandro Mani: On 06.07.2014 13:38, drago01 wrote: On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: * A script automating most of the process of validating

Re: WARNING: malicious code (was: Re: [Announce] Simple Patch Policy)

2014-07-06 Thread Christopher Meng
On Sun, Jul 6, 2014 at 7:38 PM, drago01 wrote: > On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: >> On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >> >>> * A script automating most of the process of validating and processing the >>> request can be found at >>> >>> https://github.c

Re: WARNING: malicious code (was: Re: [Announce] Simple Patch Policy)

2014-07-06 Thread drago01
On Sun, Jul 6, 2014 at 1:54 PM, Christopher Meng wrote: > On Sun, Jul 6, 2014 at 7:38 PM, drago01 wrote: >> On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: >>> On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >>> * A script automating most of the process of validating and proc

FEVer or?

2014-07-06 Thread Conrad Meyer
Hi lazy-list, Back in the day, there was FEver for monitoring new upstream releases. Is that still what we use, or is there a new thing now? And where does it live? Cursory googling failed to locate it. Thanks, Conrad -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraprojec

Re: WARNING: malicious code

2014-07-06 Thread Reindl Harald
Am 06.07.2014 13:51, schrieb Sandro Mani: > On 06.07.2014 13:48, Reindl Harald wrote: >> >> Am 06.07.2014 13:41, schrieb Sandro Mani: >>> On 06.07.2014 13:38, drago01 wrote: On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: > On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >>

Re: WARNING: malicious code

2014-07-06 Thread Haïkel
2014-07-06 13:51 GMT+02:00 Sandro Mani : > > It was a line ordering issue. > The cwd before that call was the temporary directory. > Please trust me, I really feel bad about this, and will never again push > code which was written late at night. Again, I really apologize. > Sounds likely, I was mo

Re: FEVer or?

2014-07-06 Thread Christopher Meng
Put this in the bookmarks: https://fedoraproject.org/wiki/Upstream_release_monitoring -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: FEVer or?

2014-07-06 Thread Haïkel
2014-07-06 13:59 GMT+02:00 Conrad Meyer : > Hi lazy-list, > > Back in the day, there was FEver for monitoring new upstream > releases. Is that still what we use, or is there a new thing > now? And where does it live? Cursory googling failed to > locate it. > It's called cnucnu All details here: ht

Re: WARNING: malicious code

2014-07-06 Thread drago01
On Sun, Jul 6, 2014 at 1:41 PM, Sandro Mani wrote: > > On 06.07.2014 13:38, drago01 wrote: >> >> On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: >>> >>> On Fri, Jul 04, 2014 at 04:26:07PM +0200, Sandro Mani wrote: >>> * A script automating most of the process of validating and processing

Re: WARNING: malicious code

2014-07-06 Thread Sandro Mani
On 06.07.2014 13:59, Reindl Harald wrote: Am 06.07.2014 13:51, schrieb Sandro Mani: On 06.07.2014 13:48, Reindl Harald wrote: Am 06.07.2014 13:41, schrieb Sandro Mani: On 06.07.2014 13:38, drago01 wrote: On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: On Fri, Jul 04, 2014 at 04:26:07PM +0

Re: WARNING: malicious code

2014-07-06 Thread Till Maas
On Sun, Jul 06, 2014 at 01:41:08PM +0200, Sandro Mani wrote: > > On 06.07.2014 13:38, drago01 wrote: > >On Sun, Jul 6, 2014 at 1:04 PM, Till Maas wrote: > >>| 301 os.chdir("/") > >>| 302 shutil.rmtree(os.getcwd()) > >Ouch ... can we ban this guy from Fedora? > This is a bit dramatic. I reall

Half-OT: Secure boot and thirdy party kernel modules

2014-07-06 Thread Sergio Belkin
Hi Fedora folks, I've found that Oracle VirtualBox kernel module are not signed so I have to disable secure boot. Oracle says that is not a VirtualBox bug. And Fedora cannot sign it because of license, can it? So, the question is: Is it worth signing "my own" kernel? Of course I can circunvent th

Re: Half-OT: Secure boot and thirdy party kernel modules

2014-07-06 Thread Matthew Garrett
On Sun, Jul 06, 2014 at 02:10:45PM -0300, Sergio Belkin wrote: > I've found that Oracle VirtualBox kernel module are not signed so I have to > disable secure boot. Oracle says that is not a VirtualBox bug. And Fedora > cannot sign it because of license, can it? Correct. You can generate your own

easy review: abduco

2014-07-06 Thread Igor Gnatenko
Hi, I've just submitted[0] abduco package for review. Because program is small I think review should take minimal time. Please review it. [0]https://bugzilla.redhat.com/show_bug.cgi?id=1116653 -- -Igor Gnatenko signature.asc Description: This is a digitally signed message part -- devel mail

Re: Half-OT: Secure boot and thirdy party kernel modules

2014-07-06 Thread Florian Weimer
On 07/06/2014 07:10 PM, Sergio Belkin wrote: So, the question is: Is it worth signing "my own" kernel? Only if you keep your own key on a sufficiently separated machine, otherwise it's equivalent to disabling Secure Boot anyway. It's also not clear if the Virtualbox kernel modules themselves