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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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
On Thu, Apr 08, 2010 at 04:02:54PM +0200, Peter Czanik wrote:
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.
OpenSSL being in /usr/lib instead of /lib is a regression that was introduced in Fedora 11 afaics and partly broke pam_mount: https://bugzilla.redhat.com/show_bug.cgi?id=559953 https://bugzilla.redhat.com/show_bug.cgi?id=239375
Hopefully it will be moved back to /lib eventually and then syslog-ng could use SSL support, too.
Regards Till
-----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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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
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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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 <command> [options] Possible commands are: match Match a message against the pattern database dump Dump pattern datebase tree merge Merge pattern databases bigone112:~ # syslog-ng-ctl Syntax: syslog-ng-ctl <command> [options] Possible commands are: stats Dump syslog-ng statistics verbose Enable/query verbose messages debug Enable/query debug messages trace Enable/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_PIDFILE PATH_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-----
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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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
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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/12/2010 08:28 AM, Peter Czanik wrote:
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:/Syst... ), 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/c... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.1.0/c...
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
Have you opened a bugzilla requesting the update?
I think you need to sign up and work to become a provenpackager.
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):
[root@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 Repository Size ==================================================================================================== Installing: syslog-ng i686 2.1.4-6.fc12 fedora 138 k Installing for dependencies: eventlog i686 0.2.7-4.fc12 fedora 16 k libnet i686 1.1.4-3.fc12 fedora 49 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! [root@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
On 02/06/10 11:56, Peter Czanik wrote: --snip--
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
No idea but this is when rsyslog was mooted.
http://www.redhat.com/archives/fedora-devel-list/2007-July/msg00941.html
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
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.
[root@fedora13 ~]# yum install syslog-ng
...
Installing: syslog-ng i686 2.1.4-6.fc12 fedora 138 k Installing for dependencies: eventlog i686 0.2.7-4.fc12 fedora 16 k libnet i686 1.1.4-3.fc12 fedora 49 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. Last changelog entry is from f12(-rawhide) times:
* Tue Sep 15 2009 Ray Van Dolson rayvd@fedoraproject.org - 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
Regards,
Petr
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
[root@fedora13 ~]# yum install syslog-ng
...
Installing: syslog-ng i686 2.1.4-6.fc12 fedora 138 k Installing for dependencies: eventlog i686 0.2.7-4.fc12 fedora 16 k libnet i686 1.1.4-3.fc12 fedora 49 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 rayvd@fedoraproject.org - 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
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
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
Yes, a proven packager could also do it for you.
Rahul
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@lists.stg.fedoraproject.org