Re: Abotu setting 'PermitRootLogin=no' in sshd_config

[Andrew Haley]

On 27/11/14 14:52, Nico Kadel-Garcia wrote:
On Thu, Nov 27, 2014 at 8:06 AM, P J P  wrote:
>> > Overall this feature adds more value to Fedora, than its perceived short 
>> > term cost.
> I agree, from a basic security standpoint, that it's the simplest
> change with the largest return on investment.

At some loss of usability.  To often we hear "This is better for
security, therefore we should do it" without considering the usability
trade-off.

Andrew.
-- 
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: How to take ownership of orphaned package: ddclient

[Michael Schwendt]

On Tue, 23 Dec 2014 10:57:14 -0700, Kevin Fenzi wrote:

> You will need to convince a sponsor to sponsor you. 
> 
> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group?rd=Extras/HowToGetSponsored
> 
> Many sponsors like to see you put together a package for review or
> 'pre' review existing packages in the review queue to show that you
> know what you are doing. 

Btw, several sponsors have been burnt by someone new wanting to take over
a single orphaned (or even deprecated) package, only to give up shortly
afterwards without any notification. :(  So, a positive attitude in
general and not getting upset too easily by other changes in the dist is
a plus if you are serious about becoming a contributor.
-- 
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: Where should a package place facter facts?

[Michael Schwendt]

On Tue, 23 Dec 2014 20:10:08 +0100, Reindl Harald wrote:

> > Are packages really supposed to put files in "/local/"?
> 
> no - /usr/local/ is admin area - period

True - ignoring the 'period' ;)
-- 
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: Incorrect FSF Address error from rpmlint

[Matěj Cepl]

On 2014-12-23, 21:06 GMT, Gerald B. Cox wrote:
> Upstream had a few files that had the old address.  I've 
> noticed the GPLv3 doesn't have an address in it's notice.  Is 
> it sufficient to instruct upstream to just remove the address 
> for GPLv2.  Not that they're going to move again, but seems to 
> be alot of work for everybody if the address is actually 
> required.

Yes, with GPLv3 FSF finally acknowledged the existence of 
Internet :) and it mentions the copy of the license being 
available on the Internet.

GPLv2 is from 1991 and we have to admit that the Internet was 
not widely available or even known most of the time, so the 
preferred method for obtaining the license was the snail mail.

However, I don't think that the “How to use GNU license for your 
own software” has any contractual significance whatsoever in 
using, so I don’t see anything bad in upgrading even the 
instructions for GPLv2 to the Internet age (of course, you have 
to fix the name of the program, and decide about "or any later 
version" clause).


Copyright (C)   

This program is free software; you can redistribute it 
and/or modify it under the terms of the GNU General Public 
License as published by the Free Software Foundation; either 
version 2 of the License, or (at your option) any later 
version.

This program is distributed in the hope that it will be 
useful, but WITHOUT ANY WARRANTY; without even the implied 
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.  See the GNU General Public License for more 
details.

You should have received a copy of the GNU General Public 
License along with Foobar.  If not, see 
.

Whatever way you decide to resolve the conflict (just fix the 
address, or use this modified license information), I believe 
your best bet is to make a patch (and adding it via normal 
Patch: clause) and send the whole patch upstream for the 
inclusion in the project.

Best,

Matěj

-- 
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: Why isn't F2FS support in the Kernel?

[Matěj Cepl]

On 2014-12-22, 17:20 GMT, Gerald B. Cox wrote:
> It isn't about a single module... you're a smart guy... you 
> know better.

I think you are a smart guy so you know better as well than ask 
somebody else to work for you on your pet project.

https://fedoraproject.org/wiki/Building_a_custom_kernel

*PLONK

Matěj

-- 
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: Why isn't F2FS support in the Kernel?

[drago01]

On Wed, Dec 24, 2014 at 12:00 PM, Matěj Cepl  wrote:
> On 2014-12-22, 17:20 GMT, Gerald B. Cox wrote:
>> It isn't about a single module... you're a smart guy... you
>> know better.
>
> I think you are a smart guy so you know better as well than ask
> somebody else to work for you on your pet project.

He already apologized ... no need to dig out the old mails ... let the
thread die.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

rawhide report: 20141224 changes

[Fedora Rawhide Report]

Compose started at Wed Dec 24 05:15:05 UTC 2014
Broken deps for i386
--
[3Depict]
3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[aeskulap]
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires liboflog.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg8.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg16.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg12.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmnet.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmjpeg.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimgle.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimage.so.3.6
aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmdata.so.3.6
[boswars]
boswars-2.7-5.fc22.i686 requires libtolua++-5.1.so
[cab]
cab-0.1.9-12.fc22.i686 requires cabal-dev
[dnssec-check]
dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14
dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14
[ember]
ember-0.7.2-2.fc22.i686 requires libtolua++-5.1.so
[fawkes]
fawkes-lua-0.5.0-19.fc22.i686 requires libtolua++-5.1.so
fawkes-plugin-katana-0.5.0-19.fc22.i686 requires libtolua++-5.1.so
fawkes-plugin-pantilt-0.5.0-19.fc22.i686 requires libtolua++-5.1.so
fawkes-plugin-roomba-0.5.0-19.fc22.i686 requires libtolua++-5.1.so
fawkes-plugin-skiller-0.5.0-19.fc22.i686 requires libtolua++-5.1.so
[gcc-python-plugin]
gcc-python2-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22
gcc-python2-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22
gcc-python3-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22
gcc-python3-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22
[glances]
glances-2.1.2-2.fc22.noarch requires python-psutil >= 0:2.0.0
[gtatool]
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libofstd.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires liboflog.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libijg8.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libijg16.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libijg12.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libdcmjpeg.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libdcmimgle.so.3.6
gtatool-dcmtk-1.5.2-14.fc22.i686 requires libdcmdata.so.3.6
[guacamole-server]
libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-utils.so.1.2
libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-core.so.1.2
libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-codec.so.1.2
libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-cache.so.1.2
[libreoffice]
1:libreoffice-core-4.4.0.0-5.beta2.fc22.i686 requires libcmis-0.4.so.4
[nodejs-got]
nodejs-got-2.2.0-1.fc22.noarch requires npm(duplexify) < 0:4
nodejs-got-2.2.0-1.fc22.noarch requires npm(duplexify) >= 0:3.2.0
[nwchem]
nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1
[pam_mapi]
pam_mapi-0.2.0-3.fc22.i686 requires libmapi.so.0
[python-selenium]
python3-selenium-2.43.0-1.fc22.noarch requires python3-rdflib
[shogun]
shogun-doc-3.2.0.1-0.27.git20140804.96f3cf3.fc22.noarch requires 
shogun-data = 0:0.8.1-0.18.git20140804.48a1abb.fc22
[stratagus]
stratagus-2.2.7-4.fc22.i686 requires libtolua++-5.1.so
[uwsgi]
uwsgi-plugin-gridfs-2.0.7-2.fc22.i686 requires libmongoclient.so
uwsgi-stats-pusher-mongodb-2.0.7-2.fc22.i686 requires libmongoclient.so
[vfrnav]
vfrnav-20140510-2.fc22.i686 requires libpolyclipping.so.16
vfrnav-utils-20140510-2.fc22.i686 requires libpolyclipping.so.16



Broken deps for x86_64
--
[3Depict]
3Depict-0.0.16-3.fc22.x86_64 requires libmgl.so.7.2.0()(64bit)
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[aeskulap]
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libofstd.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires liboflog.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libijg8.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libijg16.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libijg12.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libdcmnet.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires libdcmjpeg.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires 
libdcmimgle.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.x86_64 requires 
libdcmimage.so.3.6()(64bit)
aeskulap-0.2.2-0.19beta1.fc22.

Re: How to take ownership of orphaned package: ddclient

[Christopher Meng]

On Wed, Dec 24, 2014 at 6:26 PM, Michael Schwendt  wrote:
> On Tue, 23 Dec 2014 10:57:14 -0700, Kevin Fenzi wrote:
>
>> You will need to convince a sponsor to sponsor you.
>>
>> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group?rd=Extras/HowToGetSponsored
>>
>> Many sponsors like to see you put together a package for review or
>> 'pre' review existing packages in the review queue to show that you
>> know what you are doing.
>
> Btw, several sponsors have been burnt by someone new wanting to take over
> a single orphaned (or even deprecated) package, only to give up shortly
> afterwards without any notification. :(  So, a positive attitude in
> general and not getting upset too easily by other changes in the dist is
> a plus if you are serious about becoming a contributor.

I will take it back as I was an admin of this package. Incidentally,
should I go through the review process again?

Thanks.
-- 
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: Abotu setting 'PermitRootLogin=no' in sshd_config

[P J P]

> On Wednesday, 24 December 2014 3:07 PM, Andrew Haley wrote:
> At some loss of usability.  To often we hear "This is better for
> security, therefore we should do it" without considering the usability
> trade-off.


  It'll help if you could define this some loss of usability. If it is about 
remotely installed VM images, it's also discussed

  here -> 
https://lists.fedoraproject.org/pipermail/security/2014-December/002061.html

---
Regards
   -Prasad
http://feedmug.com
-- 
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: Incorrect FSF Address error from rpmlint

[Gerald B. Cox]

On Wed, Dec 24, 2014 at 2:53 AM, Matěj Cepl  wrote:

> However, I don't think that the “How to use GNU license for your
> own software” has any contractual significance whatsoever in
> using, so I don’t see anything bad in upgrading even the
> instructions for GPLv2 to the Internet age (of course, you have
> to fix the name of the program, and decide about "or any later
> version" clause).
>

Thanks... I reviewed the FSF website and thought that they implied that
also, but wanted to
get some feedback to somewhat validate my assumption.  I also went ahead
and made
the changes and submitted a git pull request; in addition to sending an
email explaining
why I made the change.
-- 
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: Why isn't F2FS support in the Kernel?

[Gerald B. Cox]

On Wed, Dec 24, 2014 at 3:00 AM, Matěj Cepl  wrote:

> I think you are a smart guy so you know better as well than ask
> somebody else to work for you on your pet project.
>
> https://fedoraproject.org/wiki/Building_a_custom_kernel
>
>
>
Thanks for the link, I'll take a look at it.  I don't really have much
experience with custom kernels,
but always willing to learn new things.

Just for the record, my intent was simply to comment on the Phoronix
article and the fact
that F2FS is being used and we don't have it.  It isn't a personal pet
project.
>From what I read it has the possibility of getting rid of FAT / NTFS on
flash devices;
which would be a good thing - and I thought that would be something the
Fedora community
would be interested with participating.

People contribute in many different ways, and I didn't think I needed to
possess a kernel skill-set
to broach this topic.

That is pretty much it.  No anger, no malice, no passive aggressive hidden
messages.
I appreciate the fact the issue is currently being considered.
-- 
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: Abotu setting 'PermitRootLogin=no' in sshd_config

[Mike Pinkerton]

On 24 Dec 2014, at 09:29, P J P wrote:


On Wednesday, 24 December 2014 3:07 PM, Andrew Haley wrote:
At some loss of usability.  To often we hear "This is better for
security, therefore we should do it" without considering the  
usability

trade-off.



  It'll help if you could define this some loss of usability. If it  
is about remotely installed VM images, it's also discussed


  here -> https://lists.fedoraproject.org/pipermail/security/2014- 
December/002061.html



Remotely installed on bare metal.

--
Mike Pinkerton


--
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: [Test-Announce] New Fedora 22 Nightly compose test event: 20141222 (Adam Williamson)

[Robert Knight]

On Mon, 22 Dec 2014 17:43:39 -0800, Adam Williamson 
 said:

Once again I noticed a new nightly test event was 'needed' while
testing relval changes! So the new testing nightly is 20141222.


I've tested the x86_64 network install image on real hardware for the 
Server.  It did work.


We use a 1998 vintage DHCP server that's been heavily modified.  As a 
consequence, I have to specify enough networking specifications so that 
a network installer can see the, um, network as Fedora 21 and later 
doesn't want to send the hardware id as the defaul any longer.  There's 
some discussion of this in this closed BZ 
(https://bugzilla.redhat.com/show_bug.cgi?id=1142889).


In the past, I've been able to switch to one of the text consoles once 
the first panel is up, provide enough DHCP config to satisfy my vintage 
server, and then return.  It appears that this most recent 
nightly-to-be-tested tries to reach back home and refresh the repos 
before / during the display of that first panel.  And it crashes 
horribly at that point (usual panel with a Report this bug button). I'll 
find some way to get the network up in the crashed system and submit a 
problem next week, but didn't want to leave this unremarked until then.


I can specify enough information as kernel parameters to avoid this, but 
that also raised an interesting question: on a new piece of hardware, if 
one has to specify networking on the kernel parameter line, how does one 
know what the name of the (or at least a) network device is?


Regards,
Robert
--
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: Abotu setting 'PermitRootLogin=no' in sshd_config

[P J P]

> On Wednesday, 24 December 2014 11:01 PM, Mike Pinkerton wrote:
> Remotely installed on bare metal.


  I see. Is there a provision that you could edit the kick-start file? Or 
supply parameters to it?? If so, it could be possible to enable remote root 
login post install. If not, let's see how we could address that.

Which tool is it? 
---
Regards
   -Prasad
http://feedmug.com
-- 
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: Why isn't F2FS support in the Kernel?

[Matěj Cepl]

On 2014-12-24, 11:10 GMT, drago01 wrote:
>> I think you are a smart guy so you know better as well than ask
>> somebody else to work for you on your pet project.
>
> He already apologized ... no need to dig out the old mails ... let the
> thread die.

Yes, my point was mainly to post the URL of building customized 
kernel. He can use it.

Matěj

-- 
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: Why isn't F2FS support in the Kernel?

[Reindl Harald]

Am 24.12.2014 um 21:20 schrieb Matěj Cepl:

On 2014-12-24, 11:10 GMT, drago01 wrote:

I think you are a smart guy so you know better as well than ask
somebody else to work for you on your pet project.


He already apologized ... no need to dig out the old mails ... let the
thread die.


Yes, my point was mainly to post the URL of building customized
kernel. He can use it


then why did you write the angry "*PLONK"?
just curious because my intention is also way too often misinterpreted



signature.asc
Description: OpenPGP digital signature
-- 
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: Why isn't F2FS support in the Kernel?

[Matěj Cepl]

On 2014-12-24, 20:59 GMT, Reindl Harald wrote:
> then why did you write the angry "*PLONK"?

PLONK is not angry. http://www.catb.org/jargon/html/P/plonk.html 
defines it in this way:

plonk: excl.,vt.

[Usenet: possibly influenced by British slang ‘plonk’ for 
cheap booze, or ‘plonker’ for someone behaving stupidly 
(latter is lit. equivalent to Yiddish schmuck)] The sound 
a newbie makes as he falls to the bottom of a kill file.  
While it originated in the newsgroup talk.bizarre, this term 
(usually written “*plonk*”) is now (1994) widespread on 
Usenet as a form of public ridicule.

For me it is just a sign that for the purposes of my mental 
hygiene I put author of the email into the killlist. No anger 
needs to be involved.

Matěj

-- 
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: Why isn't F2FS support in the Kernel?

[Chris Murphy]

On Wed, Dec 24, 2014 at 10:04 AM, Gerald B. Cox  wrote:

> From what I read it has the possibility of getting rid of FAT / NTFS on
> flash devices;
> which would be a good thing - and I thought that would be something the
> Fedora community
> would be interested with participating.

UDF has been in the best position to do this for ~ 20 years, seeing as
it has had Windows, OS X, and linux distro support for most of that
time frame. And yet it didn't supplant FAT or NTFS on flash media on
any platform or distribution.

F2FS's main benefit is its tunablity. Meanwhile manufacturers aren't
going to make the internal geometry or FTL scheme their using
discoverable. Therefore a default format won't result in tuned
storage. It'll require the initiator of the format command to have
product specific knowledge so that the right format options are used.
This suggests a manufacturer specific formatting utility, assuming the
idea is to make F2FS general purpose across Windows, OS X and Linux.
But since there are no Windows or OS X drivers that's a premature
conclusion.

I think more likely it's a way to supplant all other file systems,
including Linux file systems, for tablets, phones, IVI, and other
embedded products. The manufacturers of those systems can use F2FS
across the board, and get the optimum formatting command from their
flash vendor of choice; and as they find out, probably as Samsung
hopes, that this will show Samsung flash outperforms everyone else
when optimized, that more embedded product developers will choose
Samsung flash.


-- 
Chris Murphy
-- 
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: Incorrect FSF Address error from rpmlint

[Kevin Kofler]

Matěj Cepl wrote:
> You should have received a copy of the GNU General Public
> License along with Foobar.  If not, see
> .

I just use the standard GPLv3+ template for my new GPLv2+ projects (with 
only the version changed to 2), including the  
link. It's OK to point to the current version of the GPL for projects using 
"or (at your option) any later version" licensing, and the links to the old 
versions can also be found there anyway.

Kevin Kofler

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct