feature freeze?

2010-08-05 Thread Peter Czanik
Hello,

According to schedule, there is now a feature freeze in effect. I read
http://fedoraproject.org/wiki/ReleaseEngineering/FeatureFreezePolicy but
it's not clear for me if I'm too late to ask a minor version update.

Syslog-ng 3.1.2 was released yesterday (for details, check
https://lists.balabit.hu/pipermail/syslog-ng/2010-August/014606.html ).
This is a minor version update with many bugfixes. Syslog-ng is a leaf
package, AFAIK, nothing depends on it. Can I still add a version update
request to bugzilla, or it is too late to be included in Fedora 14?

BTW: once upon a time, syslog-ng was rejected as default syslog because
of its license:
https://www.redhat.com/archives/fedora-devel-list/2007-June/msg02385.html While
I guess, it's too late now to make a switch now, here is some good news:
http://bazsi.blogs.balabit.com/2010/07/syslog-ng-contributions-redefined.html
Dual licensing will be gone with the upcoming syslog-ng v3.2.

Bye,
CzP / from syslog-ng upstream...
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: feature freeze?

2010-08-09 Thread Peter Czanik
Hello,

On 08/06/2010 01:42 AM, Kevin Kofler wrote:
> Peter Czanik wrote:
>> While I guess, it's too late now to make a switch now, here is some good
>> news:
>> http://bazsi.blogs.balabit.com/2010/07/syslog-ng-contributions-
> redefined.html
>> Dual licensing will be gone with the upcoming syslog-ng v3.2.
>
> Nothing has really changed for practical purposes. There's still a
> non-Free
> "Premium Edition" with added features and a crippleware "Open Source
> Edition". The only thing which has changed is the way the non-Free
> features
> are delivered (as plugins instead of relicensing the whole thing). This
> doesn't resolve the complaint that upstream will be unwilling to add
> features which are specific to the non-Free edition.
>
> Crippleware "OSE"s suck. Fedora should not encourage this practice.
OSE is nothing near to being a crippleware. Most features arrive
simultaneously to OSE and PE (like support for the new syslog spec,
etc.) or appear in PE first and then migrated quickly to OSE (like SSL
and database support). Automatic testing of PE also helped to fix more
bugs in OSE than the community ever did. So the time and energy spent on
PE automagically helps to improve the OSE too.

A more detailed blog entry about the OSE vs. PE question is available at
http://bazsi.blogs.balabit.com/2010/08/lwn-syslog-ng-rotten-to-open-core.html

And for those, who are more interested in technical details than
licensing, here is a list of what's new in syslog-ng OSE v3.2 alpha2:
http://bazsi.blogs.balabit.com/2010/08/lwn-syslog-ng-rotten-to-open-core.html

Bye,
CzP / from syslog-ng upstream...

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


syslog-ng

2010-04-08 Thread Peter Czanik
Hello,

I'm helping to upgrade syslog-ng to current version in major Linux
distributions. I would like to ask, if you could update syslog-ng to
version 3.1. I'm working on the openSUSE version of syslog-ng 3.1 (
http://download.opensuse.org/repositories/home:/czanik:/branches:/Base:/System/openSUSE_Factory/src/
), and it is also being upgraded in Debian (
http://packages.qa.debian.org/s/syslog-ng.html ) and Gentoo (
http://gentoo.linuxhowtos.org/portage/app-admin/syslog-ng ) and Mandriva
( http://sophie.zarb.org/viewrpm/b8182fa1eee109cc655a020a2cb62f5f ).

For a complete list of changes, please see:
http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.5/changelog-en.txt
http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/changelog-en.txt

Major changes from the packaging point of view:

- addition of new utilities:
/usr/bin/pdbtool
/usr/sbin/syslog-ng-ctl

- apparmor (or SElinux in case of Fedora) needs some extra permissions:
/var/run/syslog-ng.ctl rw,
/var/run/syslog-ng/additional-log-sockets.conf r,
capability sys_tty_config,

Version 3.0 also added SSL support among many other changes, but that
can't be enabled on openSUSE (configure arg: --disable-ssl): syslog-ng
is in /sbin, openssl libs are in /usr/lib, linking from /usr is not
allowed in /, and SSL is not available statically for security reasons.
As far as I can see (I have a Fedora 13 snapshot installed in vmware),
Fedora has the same problem.

Please let me know, if you need any additional help/information to get
syslog-ng updated for Fedora.

Best regards,
Peter Czanik

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-04-08 Thread Peter Czanik
Hello,

2010-04-08 21:06 keltezéssel, Daniel J Walsh írta:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/08/2010 10:02 AM, Peter Czanik wrote:
>   
>> Hello,
>>
>> I'm helping to upgrade syslog-ng to current version in major Linux
>> distributions. I would like to ask, if you could update syslog-ng to
>> version 3.1. I'm working on the openSUSE version of syslog-ng 3.1 (
>> http://download.opensuse.org/repositories/home:/czanik:/branches:/Base:/System/openSUSE_Factory/src/
>> ), and it is also being upgraded in Debian (
>> http://packages.qa.debian.org/s/syslog-ng.html ) and Gentoo (
>> http://gentoo.linuxhowtos.org/portage/app-admin/syslog-ng ) and Mandriva
>> ( http://sophie.zarb.org/viewrpm/b8182fa1eee109cc655a020a2cb62f5f ).
>>
>> For a complete list of changes, please see:
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.5/changelog-en.txt
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/changelog-en.txt
>>
>> Major changes from the packaging point of view:
>>
>> - addition of new utilities:
>> /usr/bin/pdbtool
>> /usr/sbin/syslog-ng-ctl
>>
>> 
> Are these tools executed by init scripts or just by administrators?
>   
Just by administrators. The first manages the pattern database (patterns
are not included), the second gives stats and controls debugging:

bigone112:~ # pdbtool
Syntax: pdbtool  [options]
Possible commands are:
matchMatch a message against the pattern database
dump Dump pattern datebase tree
mergeMerge pattern databases
bigone112:~ # syslog-ng-ctl
Syntax: syslog-ng-ctl  [options]
Possible commands are:
statsDump syslog-ng statistics
verbose  Enable/query verbose messages
debugEnable/query debug messages
traceEnable/query trace messages


>> - apparmor (or SElinux in case of Fedora) needs some extra permissions:
>> /var/run/syslog-ng.ctl rw,
>> 
> Is this a sock_file?
>   
Yes, it is.

>> /var/run/syslog-ng/additional-log-sockets.conf r,
>> 
Ooops, sorry, this is a SuSE related config file, where additional log
sockects from chroots are added on start by the init script.

> Why not put syslog-ng.ctl in /var/run/syslog-ng?
>   
It is controlled by configure parameter: --with-pidfile-dir=/var/run
which also affects pid file location (see src/syslog-ng.h):
#define PATH_PIDFILEPATH_PIDFILEDIR "/syslog-ng.pid"
#define PATH_CONTROL_SOCKET PATH_PIDFILEDIR "/syslog-ng.ctl"
Fedora seems to be a bit more flexible here, than SuSE, so one could
easily set to use /var/run/syslog-ng/ for both of these files.

>> capability sys_tty_config,
>> 
> What other processes need to read/write in these directories or sock_files?
>   
Only syslog-ng and syslog-ng-ctl.

Bye,
CzP

>> Version 3.0 also added SSL support among many other changes, but that
>> can't be enabled on openSUSE (configure arg: --disable-ssl): syslog-ng
>> is in /sbin, openssl libs are in /usr/lib, linking from /usr is not
>> allowed in /, and SSL is not available statically for security reasons.
>> As far as I can see (I have a Fedora 13 snapshot installed in vmware),
>> Fedora has the same problem.
>>
>> Please let me know, if you need any additional help/information to get
>> syslog-ng updated for Fedora.
>>
>> Best regards,
>> Peter Czanik
>>
>> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAku+KUsACgkQrlYvE4MpobNBeQCfRvP3ykhSY8xaAMCL6PlOY+18
> fY8AoIo2TyUSPXEYDiUWs5ts/U6IMh8B
> =G3LL
> -END PGP SIGNATURE-
>   

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-04-13 Thread Peter Czanik
Hello,

Quick heads up: version 3.1.1 of syslog-ng is now available, which among
other things fixes a problem with pipe(). In 3.X, pipe used 100% CPU,
when a file parameter was used instead of a pipe (as was in the default
openSUSE syslog-ng.conf).

Bye,
CzP

2010-04-08 21:06 keltezéssel, Daniel J Walsh írta:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/08/2010 10:02 AM, Peter Czanik wrote:
>   
>> Hello,
>>
>> I'm helping to upgrade syslog-ng to current version in major Linux
>> distributions. I would like to ask, if you could update syslog-ng to
>> version 3.1. I'm working on the openSUSE version of syslog-ng 3.1 (
>> http://download.opensuse.org/repositories/home:/czanik:/branches:/Base:/System/openSUSE_Factory/src/
>> ), and it is also being upgraded in Debian (
>> http://packages.qa.debian.org/s/syslog-ng.html ) and Gentoo (
>> http://gentoo.linuxhowtos.org/portage/app-admin/syslog-ng ) and Mandriva
>> ( http://sophie.zarb.org/viewrpm/b8182fa1eee109cc655a020a2cb62f5f ).
>>
>> For a complete list of changes, please see:
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.5/changelog-en.txt
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/changelog-en.txt
>>
>> Major changes from the packaging point of view:
>>
>> - addition of new utilities:
>> /usr/bin/pdbtool
>> /usr/sbin/syslog-ng-ctl
>>
>> 
> Are these tools executed by init scripts or just by administrators?
>   
>> - apparmor (or SElinux in case of Fedora) needs some extra permissions:
>> /var/run/syslog-ng.ctl rw,
>> 
> Is this a sock_file?
>   
>> /var/run/syslog-ng/additional-log-sockets.conf r,
>> 
> Why not put syslog-ng.ctl in /var/run/syslog-ng?
>   
>> capability sys_tty_config,
>> 
> What other processes need to read/write in these directories or sock_files?
>   
>> Version 3.0 also added SSL support among many other changes, but that
>> can't be enabled on openSUSE (configure arg: --disable-ssl): syslog-ng
>> is in /sbin, openssl libs are in /usr/lib, linking from /usr is not
>> allowed in /, and SSL is not available statically for security reasons.
>> As far as I can see (I have a Fedora 13 snapshot installed in vmware),
>> Fedora has the same problem.
>>
>> Please let me know, if you need any additional help/information to get
>> syslog-ng updated for Fedora.
>>
>> Best regards,
>> Peter Czanik
>> 

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: Seeking co-maintainers for syslog-ng

2011-02-02 Thread Peter Czanik
Hello,

On 02/02/2011 03:24 PM, Doug Warner wrote:
> syslog-ng is an alternative syslog daemon that provides high
> flexibility and a
> great configuration syntax.  I've done a lot of work to make sure this is
> parallel-installable with the other syslog daemons, but lately I
> haven't had
> the time to keep up with new releases.
>
> I'm looking for help maintaining the syslog-ng package and especially
> getting
> 3.2 tested [1]
>
> I have a personal repository that I've been testing 3.1 in [2] [3] but I
> haven't been able to test out 3.2 yet.
>
> Feel free to shoot me an email if you're interested in helping and
> I'll get
> you approved in pkgdb!
I'll be at FOSDEM this weekend. If you happen to be there and also
interested in the syslog-ng port, I'd be happy to meet you there. I
helped in creating the v3.2 package for openSUSE and FreeBSD and I could
share my experiences, patches, etc. there.

Bye,

-- 

Peter Czanik (CzP) 
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-05-12 Thread Peter Czanik
Hello,

2010-04-08 21:06 keltezéssel, Daniel J Walsh írta:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/08/2010 10:02 AM, Peter Czanik wrote:
>   
>> Hello,
>>
>> I'm helping to upgrade syslog-ng to current version in major Linux
>> distributions. I would like to ask, if you could update syslog-ng to
>> version 3.1. I'm working on the openSUSE version of syslog-ng 3.1 (
>> http://download.opensuse.org/repositories/home:/czanik:/branches:/Base:/System/openSUSE_Factory/src/
>> ), and it is also being upgraded in Debian (
>> http://packages.qa.debian.org/s/syslog-ng.html ) and Gentoo (
>> http://gentoo.linuxhowtos.org/portage/app-admin/syslog-ng ) and Mandriva
>> ( http://sophie.zarb.org/viewrpm/b8182fa1eee109cc655a020a2cb62f5f ).
>>
>> For a complete list of changes, please see:
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.5/changelog-en.txt
>> http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/changelog-en.txt
>>
>> Major changes from the packaging point of view:
>>
>> - addition of new utilities:
>> /usr/bin/pdbtool
>> /usr/sbin/syslog-ng-ctl
>>
>> 
> Are these tools executed by init scripts or just by administrators?
>   
>> - apparmor (or SElinux in case of Fedora) needs some extra permissions:
>> /var/run/syslog-ng.ctl rw,
>> 
> Is this a sock_file?
>   
>> /var/run/syslog-ng/additional-log-sockets.conf r,
>> 
> Why not put syslog-ng.ctl in /var/run/syslog-ng?
>   
>> capability sys_tty_config,
>> 
> What other processes need to read/write in these directories or sock_files?
>   
>> Version 3.0 also added SSL support among many other changes, but that
>> can't be enabled on openSUSE (configure arg: --disable-ssl): syslog-ng
>> is in /sbin, openssl libs are in /usr/lib, linking from /usr is not
>> allowed in /, and SSL is not available statically for security reasons.
>> As far as I can see (I have a Fedora 13 snapshot installed in vmware),
>> Fedora has the same problem.
>>
>> Please let me know, if you need any additional help/information to get
>> syslog-ng updated for Fedora.
>> 
I'm looking for information, how to get a package (in my case:
syslog-ng) updated to the latest available version. First I tried to
contact the original syslog-ng packagers directly, but I got no response
at all. Here on the list I got some questions about the new syslog-ng
version, but while I update my rawhide installation quite often, I still
did not see an update for syslog-ng.

Now I looked around on the Fedora wiki, how I could to the packaging
work myself. I found a page with many interesting details:
http://fedoraproject.org/wiki/PackageMaintainers/Join , but this seems
to be for packagers joining to add a new package. How could I get an
existing package upgraded?

Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-02 Thread Peter Czanik
Hello,

2010-05-12 17:07 keltezéssel, Daniel J Walsh írta:
>> I'm looking for information, how to get a package (in my case:
>> syslog-ng) updated to the latest available version. First I tried to
>> contact the original syslog-ng packagers directly, but I got no response
>> at all. Here on the list I got some questions about the new syslog-ng
>> version, but while I update my rawhide installation quite often, I still
>> did not see an update for syslog-ng.
>>
>> Now I looked around on the Fedora wiki, how I could to the packaging
>> work myself. I found a page with many interesting details:
>> http://fedoraproject.org/wiki/PackageMaintainers/Join , but this seems
>> to be for packagers joining to add a new package. How could I get an
>> existing package upgraded?
>>
>> Bye,
>> CzP
>> 
> Have you opened a bugzilla requesting the update?
>
> I think you need to sign up and work to become a provenpackager.
>   
I did not open a bugzilla request yet, but it does not seem to be
appropriate any more, as syslog-ng and related libraries seem to be
dropped from Fedora (it is the same on FC13 and rawhide):

[r...@fedora13 ~]# yum install syslog-ng
Loaded plugins: presto, refresh-packagekit
Setting up Install Process   
Resolving Dependencies   
--> Running transaction check
---> Package syslog-ng.i686 0:2.1.4-6.fc12 set to be updated
--> Processing Dependency: libevtlog.so.0 for package:
syslog-ng-2.1.4-6.fc12.i686
--> Processing Dependency: libnet.so.1 for package:
syslog-ng-2.1.4-6.fc12.i686  
--> Running transaction
check
---> Package eventlog.i686 0:0.2.7-4.fc12 set to be
updated  
---> Package libnet.i686 0:1.1.4-3.fc12 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved


 Package Arch   Version 
RepositorySize

Installing:
 syslog-ng   i686   2.1.4-6.fc12
fedora   138 k
Installing for dependencies:
 eventlogi686   0.2.7-4.fc12
fedora16 k
 libnet  i686   1.1.4-3.fc12
fedora49 k

Transaction Summary

Install   3 Package(s)
Upgrade   0 Package(s)

Total download size: 204 k
Installed size: 638 k
Is this ok [y/N]:
Exiting on user Command
Complete!
[r...@fedora13 ~]#

So the question is modified: how can I get it (and the supporting
packages) back into Fedora. I have now updated the syslog-ng spec file
from Fedora 12 to syslog-ng version 3.1.1 and compiled with mock on FC12
FC13 and Rawhide. These packages work fine, except for SElinux, as there
is an additional control socket now and some rlimit settings. I'll have
a separate e-mail about it.

And a bonus question, as I work now for the upstream developer of
syslog-ng: what was the reason for dropping syslog-ng from the distribution?

Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-02 Thread Peter Czanik
Hello,

2010-06-02 12:56 keltezéssel, Peter Czanik írta:
>
> So the question is modified: how can I get it (and the supporting
> packages) back into Fedora. I have now updated the syslog-ng spec file
> from Fedora 12 to syslog-ng version 3.1.1 and compiled with mock on FC12
> FC13 and Rawhide.
Almost forgot, the sources are available at
http://peter.czanik.hu/syslog-ng3.tgz
"rpmbuild -bs syslog-ng.spec" is your friend, if you want a source rpm,
I did not want to upload that for three releases...
Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-02 Thread Peter Czanik
2010-06-02 14:02 keltezéssel, Petr Lautrbach írta:
> On 06/02/2010 12:56 PM, Peter Czanik wrote:
>   
>> Hello,
>>
>> 2010-05-12 17:07 keltezéssel, Daniel J Walsh írta:
>> 
>>>> I'm looking for information, how to get a package (in my case:
>>>> syslog-ng) updated to the latest available version. First I tried to
>>>> contact the original syslog-ng packagers directly, but I got no response
>>>> at all. Here on the list I got some questions about the new syslog-ng
>>>> version, but while I update my rawhide installation quite often, I still
>>>> did not see an update for syslog-ng.
>>>>
>>>> Now I looked around on the Fedora wiki, how I could to the packaging
>>>> work myself. I found a page with many interesting details:
>>>> http://fedoraproject.org/wiki/PackageMaintainers/Join , but this seems
>>>> to be for packagers joining to add a new package. How could I get an
>>>> existing package upgraded?
>>>>
>>>> Bye,
>>>> CzP
>>>>
>>>> 
>>> Have you opened a bugzilla requesting the update?
>>>
>>> I think you need to sign up and work to become a provenpackager.
>>>
>>>   
>> I did not open a bugzilla request yet, but it does not seem to be
>> appropriate any more, as syslog-ng and related libraries seem to be
>> dropped from Fedora (it is the same on FC13 and rawhide):
>>
>> 
> You really should open bugzilla request.
>   
Done: https://bugzilla.redhat.com/show_bug.cgi?id=598961

>> [r...@fedora13 ~]# yum install syslog-ng
>> 
> ...
>   
>> Installing:
>>   syslog-ng   i686   2.1.4-6.fc12
>> fedora   138 k
>> Installing for dependencies:
>>   eventlogi686   0.2.7-4.fc12
>> fedora16 k
>>   libnet  i686   1.1.4-3.fc12
>> fedora49 k
>>
>> 
> So syslog-ng is still there. It wasn't just rebuilt since fc12 as there was no
> mass rebuild for fc13 and no update by package maintainer.
Ah, good to know. I just teach sometimes Fedora/RHEL/CentOS, I never
developed for it :-) I package for openSUSE and FreeBSD, where each
little change triggers a rebuild of all dependent packages.

>  Last changelog
> entry is from f12(-rawhide) times:
>
> * Tue Sep 15 2009 Ray Van Dolson  - 2.1.4-8
> - Adjust eventlog build requirement
>
>   
>> And a bonus question, as I work now for the upstream developer of
>> syslog-ng: what was the reason for dropping syslog-ng from the distribution?
>> 
> It's still there, see 
> https://admin.fedoraproject.org/pkgdb/acls/name/syslog-ng
>   
Which is very good news :)
Thanks, bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-10 Thread Peter Czanik
2010-06-02 14:02 keltezéssel, Petr Lautrbach írta:
> On 06/02/2010 12:56 PM, Peter Czanik wrote:
>   
>> Hello,
>>
>> 2010-05-12 17:07 keltezéssel, Daniel J Walsh írta:
>> 
>>>> I'm looking for information, how to get a package (in my case:
>>>> syslog-ng) updated to the latest available version. First I tried to
>>>> contact the original syslog-ng packagers directly, but I got no response
>>>> at all. Here on the list I got some questions about the new syslog-ng
>>>> version, but while I update my rawhide installation quite often, I still
>>>> did not see an update for syslog-ng.
>>>>
>>>> Now I looked around on the Fedora wiki, how I could to the packaging
>>>> work myself. I found a page with many interesting details:
>>>> http://fedoraproject.org/wiki/PackageMaintainers/Join , but this seems
>>>> to be for packagers joining to add a new package. How could I get an
>>>> existing package upgraded?
>>>>
>>>> Bye,
>>>> CzP
>>>>
>>>> 
>>> Have you opened a bugzilla requesting the update?
>>>
>>> I think you need to sign up and work to become a provenpackager.
>>>
>>>   
>> I did not open a bugzilla request yet, but it does not seem to be
>> appropriate any more, as syslog-ng and related libraries seem to be
>> dropped from Fedora (it is the same on FC13 and rawhide):
>>
>> 
> You really should open bugzilla request.
>   

Done: https://bugzilla.redhat.com/show_bug.cgi?id=598961
What is the procedure, if there is no response to such a bugzilla request? Is 
there maintainer a timeout, like with FreeBSD? Or I have to wait patiently 
until something happens? I was suggested, that as "provenpackager" I could do 
this, but as I don't have any Fedora packages, it is a no-go. Or could an other 
"provenpackager" do it for me? Updated sources, prepared by me, are also in 
bugzilla...
Bye,
CzP

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-11 Thread Peter Czanik
2010-06-10 15:10 keltezéssel, Rahul Sundaram írta:
> On 06/10/2010 04:45 PM, Peter Czanik wrote:
>   
>> Done: https://bugzilla.redhat.com/show_bug.cgi?id=598961
>> What is the procedure, if there is no response to such a bugzilla request? 
>> Is there maintainer a timeout, like with FreeBSD? Or I have to wait 
>> patiently until something happens? I was suggested, that as "provenpackager" 
>> I could do this, but as I don't have any Fedora packages, it is a no-go. Or 
>> could an other "provenpackager" do it for me? Updated sources, prepared by 
>> me, are also in bugzilla...
>> Bye,
>>   
>> 
> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
>   
OK, created a 'non-responsive maintainer' bug:
https://bugzilla.redhat.com/show_bug.cgi?id=603012

> Yes,  a proven packager could also do it for you.
>   
Could, but I start to have some doubts, as this thread is over a month
old, and contains URL to updated package, which was never downloaded...
So, the three weeks countdown just started, and I hope, that either the
maintainer will respond or I can take the package over. Well, actuall
I'd be more happy with the original maintainer or a proven packager, as
I have some packaging experience, but no Fedora infrastructure experience...
Bye,
CzP
Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-14 Thread Peter Czanik
Hello,

2010-06-11 18:44 keltezéssel, Doug Warner írta:
> On 06/11/2010 05:32 AM, Peter Czanik wrote:
>   
>> 2010-06-10 15:10 keltezéssel, Rahul Sundaram írta:
>> 
>>> On 06/10/2010 04:45 PM, Peter Czanik wrote:
>>>   
>>>   
>>>> Done: https://bugzilla.redhat.com/show_bug.cgi?id=598961
>>>> What is the procedure, if there is no response to such a bugzilla request? 
>>>> Is there maintainer a timeout, like with FreeBSD? Or I have to wait 
>>>> patiently until something happens? I was suggested, that as 
>>>> "provenpackager" I could do this, but as I don't have any Fedora packages, 
>>>> it is a no-go. Or could an other "provenpackager" do it for me? Updated 
>>>> sources, prepared by me, are also in bugzilla...
>>>> Bye,
>>>>   
>>>> 
>>>> 
>>> https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
>>>   
>>>   
>> OK, created a 'non-responsive maintainer' bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=603012
>>
>> 
>>> Yes,  a proven packager could also do it for you.
>>>   
>>>   
>> Could, but I start to have some doubts, as this thread is over a month
>> old, and contains URL to updated package, which was never downloaded...
>> So, the three weeks countdown just started, and I hope, that either the
>> maintainer will respond or I can take the package over. Well, actuall
>> I'd be more happy with the original maintainer or a proven packager, as
>> I have some packaging experience, but no Fedora infrastructure experience...
>> 
> I responded to the original bug and closed the non-responsive maintainer bug.
>
> The updated package was published as a tgz file which made it difficult to see
> what was being changed in the spec file; a link to the new spec file or patch
> would be much easier to see what's going on.
>   
Sorry, I just wanted to help by providing it. I don't really now the
Fedora development process yet, so I looked at other bugzilla entries,
and found that people provide spec files or srpm-s for new or updated
packages.

> To be honest, maintaining syslog-ng (while I use it all the time) is a very
> tiring process; there isn't much "support" for multiple sysloggers in Fedora
> and it was a real pain to get everyone cooperating to make them not have to
> conflict with each other.  I can see why the previous maintainers left the
> syslog-ng package go unmaintained now as well.
>
> I'll try to work on getting this package updated as I do still prefer
> syslog-ng's syntax over rsyslog even if it has other problems.
>   
Thank you. Please let me know, if you need any help or information from
syslong-ng upstream.
Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: syslog-ng

2010-06-22 Thread Peter Czanik
Hello,

2010-06-11 18:44 keltezéssel, Doug Warner írta:
> To be honest, maintaining syslog-ng (while I use it all the time) is a
> very
> tiring process; there isn't much "support" for multiple sysloggers in Fedora
> and it was a real pain to get everyone cooperating to make them not have to
> conflict with each other.  I can see why the previous maintainers left the
> syslog-ng package go unmaintained now as well.
>
> I'll try to work on getting this package updated as I do still prefer
> syslog-ng's syntax over rsyslog even if it has other problems.
>   
I checked http://cvs.fedoraproject.org/viewvc/rpms/syslog-ng/devel/ but
I don't see any changes. Is there anything more I could help in getting
syslog-ng updated to the latest stable version?
Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: concept of package "ownership"

2010-07-02 Thread Peter Czanik
2010-07-02 03:18 keltezéssel, Kevin Kofler írta:
> Dave Airlie wrote:
>   
>> So I've noticed maintainers of packages in Fedora seem to have a concept
>> of ownership, and I'm wondering if we could remove that word from usage
>> about maintainership.
>> 
> +1
>
> IMHO any sponsored packager should be free to do changes which benefit the 
> Fedora Project to any package, no matter who officially maintains the 
> package. And such changes include things like upgrading the package to the 
> current upstream release in Rawhide, especially when that release is needed 
> for other packages. Even a provenpackager can't always make such changes 
> without getting yelled at.
>
> I think we need to get rid of the concept of ownership entirely, that'd also 
> make orphaned or de-facto orphaned packages less of a problem. You see a 
> problem, you fix it. Who cares whether the package has an active maintainer 
> or not?
>   
+1
I'd like to get syslog-ng updated to the latest version in Rawhide (I
work part time for the upstream developer and I'm also an occasional
Fedora user). I contacted the package owner, no response. Created a
bugreport to get it updated (
https://bugzilla.redhat.com/show_bug.cgi?id=598961 ), and also provided
an updated package, which compiles and works fine on Fedora 12, 13 and
Rawhide. After waiting for weeks, I started a maintainer time out. It
was closed within an hour. I got some comments on bugzilla, but nothing
happened ever since. The updated package was never downloaded from my
website.

What can I do in this situation? Obviously I'm not a proven packager to
update the package myself, as I'm not a Fedora developer. I worked a lot
to update and test the package, but still I'm stuck. And as you can see,
the maintainer timeout procedure does not help either...

Bye,
CzP

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: concept of package "ownership"

2010-07-02 Thread Peter Czanik
Hello,

2010-07-02 14:48 keltezéssel, Thomas Janssen írta:
> +1
>> I'd like to get syslog-ng updated to the latest version in Rawhide (I
>> work part time for the upstream developer and I'm also an occasional
>> Fedora user). I contacted the package owner, no response. Created a
>> bugreport to get it updated (
>> https://bugzilla.redhat.com/show_bug.cgi?id=598961 ), and also provided
>> an updated package, which compiles and works fine on Fedora 12, 13 and
>> Rawhide. After waiting for weeks, I started a maintainer time out. It
>> was closed within an hour. I got some comments on bugzilla, but nothing
>> happened ever since. The updated package was never downloaded from my
>> website.
>>
>> What can I do in this situation? Obviously I'm not a proven packager to
>> update the package myself, as I'm not a Fedora developer. I worked a lot
>> to update and test the package, but still I'm stuck. And as you can see,
>> the maintainer timeout procedure does not help either...
>> 
> You have to accept the maintainers decision to not update it yet? What
> do you think will happen if everyone builds the wishes he has and
> breaks a lot of stuff with it? Anarchy? We have processes for that in
> Fedora: https://fedoraproject.org/wiki/MikeKnox/AWOL_Maintainers
>   
Well, syslog-ng is a leaf package. AFAIK, there are no others depending
on it, so it can't really break a lot of stuff. Also, I tested the
package heavily, not just updated, and no problems came up during testing.
Version 2.X of syslog-ng, which is currently included in Fedora, is now
obsolate. The current release is 3.1.1, this is the version I prepared
for Fedora.
And it is not just a random wish: I did the update for openSUSE and
FreeBSD, where they are accepted already and in use. Gentoo, Arch,
Mandriva, Debian, Ubuntu, NetBSD, Solaris, etc. all did the switch at
least in their devel versions for the above reasons. Only Fedora is
missing from the list...
Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Reminder: Fedora 14 Feature Freeze is Next Week (2010-07-27)

2010-07-20 Thread Peter Czanik
Hello,

2010-07-21 06:18 keltezéssel, John Poelstra írta:
> Feature Freeze means that all accepted feature for the release are 
> *significantly* "feature complete", ready for testing, and have a 
> current status.
>   
What does it from the software version point of view? I'm asking because
of the pending syslog-ng update, which I coordinate for all major Linux
distributions where only Fedora did not make the switch from syslog-ng
2.X to 3.X. I started the process well before the feature freeze, in
April, by contacting the maintainer and also this mailing list. I also
filed a bugzilla request beginning June (
https://bugzilla.redhat.com/show_bug.cgi?id=598961 ). It has spec and
config diffs and also a source rpm attached, which I tested on Fedora
12, 13 and rawhide.

I had no response to personal e-mails, mailing list or to the bugzilla
entry, so I started the "non-responsive maintainer" process, which had a
response within a few hours (
https://bugzilla.redhat.com/show_bug.cgi?id=603012 ). Nothing seems to
have happened ever since.

What can I do in this situation?

Bye,
CzP
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel