Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-08-15 Thread Max Kanat-Alexander

Christoph Maser wrote:

Am Donnerstag, den 06.08.2009, 07:55 +0200 schrieb Max Kanat-Alexander:


  BTW, is Template-Toolkit 2.22 packaged? I'm only seeing 2.21.

  -Max


Not yet, but very soon ;)


	Hey CHristoph. Is very soon very soon? I still don't see 2.22 in 
rpmforge.


-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-08-06 Thread Max Kanat-Alexander
Christoph Maser wrote:
 I know I use it to. But point was to provide everything needed for
 Bugzilla so you don't have to use this solution.

Yeah, I think the only solution is to convince Red Hat to have a
perl-CGI module for RHEL6 that's separate from perl-core.

-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-31 Thread Christoph Maser
Am Freitag, den 17.07.2009, 21:22 +0200 schrieb Max Kanat-Alexander:
   Bugzilla 3.4 will be coming out soon, and it uses the following Perl
 packages as requirements or optionally:

   Template-Toolkit 2.22 (not out yet, but will be soon).
   TheSchwartz
   Daemon-Generic

   Could we get packages for these in rpmforge? (Particularly the last two
 would be nice, because they have a lot of prereqs.)

   -Max

We figured it wants CGI = v3.21, but perl-core ships 3.15  that is much
mor of a problem. Actually all the issues in the original posting are
fixed or fixed after next rebuilds (got it working locally).

So what do we do with the CGI-dependency?


financial.com AG

Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | 
Germany
Frankfurt branch office/Niederlassung Frankfurt: Messeturm | 
Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany
Management board/Vorstand: Dr. Steffen Boehnert (CEO/Vorsitzender) | Dr. Alexis 
Eisenhofer | Dr. Yann Samson | Matthias Wiederwach
Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender)
Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID 
number/St.Nr.: DE205 370 553
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-28 Thread Christoph Maser
Am Samstag, den 25.07.2009, 13:31 +0200 schrieb Christoph Maser:
   I will fix that.
 
  Is that the unnecessary dependencies in Data-ObjectDriver, or the
 tool
  that is adding these incorrect dependencies?

 I meant turning off AutoReq on Data-ObjectDriver and fill the deps
 from
 META.yml. But i will try something else instead. I will try to split
 out
 the drivers in subpackages.


Ok I had another thought on that idea and it is propably bad, it will
leave you with a non-complete not working installation. For now i will
simly turn of AutoReeq and fill in the deps from META.yml.


Chris


financial.com AG

Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | 
Germany
Frankfurt branch office/Niederlassung Frankfurt: Messeturm | 
Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany
Management board/Vorstand: Dr. Steffen Boehnert (CEO/Vorsitzender) | Dr. Alexis 
Eisenhofer | Dr. Yann Samson | Matthias Wiederwach
Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender)
Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID 
number/St.Nr.: DE205 370 553
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-28 Thread Steve Huff


On Jul 27, 2009, at 6:36 AM, Chris Eveleigh wrote:

anyway, when there is a requirement of the form at least one of  
these alternates i've heard about virtual provides where each of  
the possible provider packages adds a generic provide - e.g.  
Provides: perlDBdriver - so that the dependency can be satisfied  
by any of the available packages and yum/rpm/whatever will only  
complain if the user attempts to remove the last of those packages.


for example, the bugzilla package depends on webserver which can  
be satisfied by httpd or lighttpd or whatever.  i think there's  
another one for mailserver.



for another example of this procedure, look at rpmforge's perl-JSON- 
Any.  using the -alternative syntax might be a good way of making it  
obvious that one is looking at a virtual provide.


-steve

--
If this were played upon a stage now, I could condemn it as an  
improbable fiction. - Fabian, Twelfth Night, III,v

http://five.sentenc.es



PGP.sig
Description: This is a digitally signed message part
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-27 Thread Chris Eveleigh
hello,

just thought it might be worth mentioning that we hit these problems
when we updated the bugzilla package in the fedora repo to 3.2.2.  i
proposed switching off perl auto-deps and manually specifying them based
on bugzilla release notes but in the end the maintainer went with
adjusting the existing filter - which was sensible.  We also updated the
package description to mention the database requirement.

i'd love for there to be a real solution to optional dependencies (or
per-use-case dependencies perhaps?) but since currently there's no way
to tell the rpm system exactly how you're using the software i guess
that's not possible.

maybe one could split all optional dependencies into separate packages
as if they were plugins - the packages would contain no files, just the
relevant dependencies.  e.g. a new package bugzilla-mail-queue which
depends on perl(TheSchwartz) and perl(Daemon::Generic)?

anyway, when there is a requirement of the form at least one of these
alternates i've heard about virtual provides where each of the
possible provider packages adds a generic provide - e.g. Provides:
perlDBdriver - so that the dependency can be satisfied by any of the
available packages and yum/rpm/whatever will only complain if the user
attempts to remove the last of those packages.

for example, the bugzilla package depends on webserver which can be
satisfied by httpd or lighttpd or whatever.  i think there's another one
for mailserver.

obviously that still doesn't solve the use-case problem.  if i've
installed httpd and lighttpd and i'm running bugzilla on httpd the
system will still allow me to uninstall httpd.

hope that all makes a bit of sense and is of some use.

chris

On Sat, 2009-07-25 at 19:51 +0100, Dave Cross wrote:

 On 25/07/09 12:31, Christoph Maser wrote:
  Am Samstag, den 25.07.2009, 12:39 +0200 schrieb Dave Cross:
 
  If there's something I can do to help fix up the CPAN-rpm toolchain
  then please let me know. It's something I have an interest in (see
  http://rpm.mag-sol.com/)
 
  Well creating spec files from CPAN is fairly simple (for me, after
  spending 1 month on learning CPAN internals). What is hard is proper
  updating spec files. I would need a proper Parse::RPM::Spec which can
  really parse the (Build)Requires entries which allow multiple formats.
  Given that one can simply compare the spec entries to what META.yml
  lists.
 
 I'm happy to make whatever fixes you want to Parse::RPM::Spec. Feel free 
 to raise bugs (with failing test examples is best) on RT[1].
 
 I see that Chris Weyl has also been working in this area. I haven't had 
 time to look his module[2] yet, so I don't know what the differences are 
 between his module and mine.
 
 Cheers,
 
 Dave...
 
 [1] http://rt.cpan.org/Public/Dist/Display.html?Name=Parse-RPM-Spec
 [2] http://search.cpan.org/dist/RPM-Spec/
 ___
 suggest mailing list
 suggest@lists.rpmforge.net
 http://lists.rpmforge.net/mailman/listinfo/suggest
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-25 Thread Dave Cross

On 25/07/09 02:15, Max Kanat-Alexander wrote:

Dag Wieers wrote:

I just packaged them, however perl-TheSchwartz requires
perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
something we cannot deliver right now.


However this works out, Data::ObjectDriver *must* not require
DBD::Oracle, or this is going to create a tremendous support load on us
at the Bugzilla Project. (Because every Bugzilla administrator will
attempt to install it, and 99.9% of them will not be able to install
DBD::Oracle.) It would be better for the module to not be provided by
rpmforge at all than for it to require DBD::Oracle.

It would be ideal if it did not require any DBD:: driver.


I agree completely. Any system that makes the DBD:: modules mandatory 
requirements from Data::ObjectDriver is fundamentally flawed.


Where are these requirements coming from? They aren't in the 
Makefile.PL, Build.PL or META.yml.


Dave...
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-25 Thread Dave Cross

On 25/07/09 10:14, Christoph Maser wrote:

Am Samstag, den 25.07.2009, 08:44 +0200 schrieb Dave Cross:

On 25/07/09 02:15, Max Kanat-Alexander wrote:

Dag Wieers wrote:

I just packaged them, however perl-TheSchwartz requires
perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
something we cannot deliver right now.

However this works out, Data::ObjectDriver *must* not require
DBD::Oracle, or this is going to create a tremendous support load on us
at the Bugzilla Project. (Because every Bugzilla administrator will
attempt to install it, and 99.9% of them will not be able to install
DBD::Oracle.) It would be better for the module to not be provided by
rpmforge at all than for it to require DBD::Oracle.

It would be ideal if it did not require any DBD:: driver.

I agree completely. Any system that makes the DBD:: modules mandatory
requirements from Data::ObjectDriver is fundamentally flawed.

Where are these requirements coming from? They aren't in the
Makefile.PL, Build.PL or META.yml.


They are optional dependencies.


I'm not sure that optional dependency is a very useful phrase. You 
either depend on something or you don't :-)


Data::ObjectDriver doesn't depend on any of these modules.


Data-ObjectDriver-0.06 ships optional Oracle, Pg, Sqlite, and mysql
drivers.


Right. And any individual installation of Data::ObjectDriver is likely 
to use one or two of these drivers. Insisting that a user installs 
Oracle, Pg and SQLite so that they can use Data::ObjectDriver with MySQL 
is obviously a rather silly idea.



The automatic dependency detection from source finds use DBD::Oracle
qw(:ora_types); in Data::ObjectDriver::Driver::DBD::Oracle and
derives a dependency to DBD::Oracle from that.


What tool is doing this automatic dependency detection? That seems like 
a really flawed approach to me. CPAN modules should list their 
dependencies in Makefile.PL, Build.PL or META.yml. Those are surely the 
only places the Fedora packagers should be looking for dependencies.


In cases where genuine dependencies are missing from META.yml, etc., 
then we should be reporting a bug against the CPAN distribution.


Or am I missing something obvious here?


I will fix that.


Is that the unnecessary dependencies in Data-ObjectDriver, or the tool 
that is adding these incorrect dependencies?


If there's something I can do to help fix up the CPAN-rpm toolchain 
then please let me know. It's something I have an interest in (see 
http://rpm.mag-sol.com/).


Cheers,

Dave...
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-25 Thread Dave Cross

On 25/07/09 12:31, Christoph Maser wrote:

Am Samstag, den 25.07.2009, 12:39 +0200 schrieb Dave Cross:



If there's something I can do to help fix up the CPAN-rpm toolchain
then please let me know. It's something I have an interest in (see
http://rpm.mag-sol.com/)


Well creating spec files from CPAN is fairly simple (for me, after
spending 1 month on learning CPAN internals). What is hard is proper
updating spec files. I would need a proper Parse::RPM::Spec which can
really parse the (Build)Requires entries which allow multiple formats.
Given that one can simply compare the spec entries to what META.yml
lists.


I'm happy to make whatever fixes you want to Parse::RPM::Spec. Feel free 
to raise bugs (with failing test examples is best) on RT[1].


I see that Chris Weyl has also been working in this area. I haven't had 
time to look his module[2] yet, so I don't know what the differences are 
between his module and mine.


Cheers,

Dave...

[1] http://rt.cpan.org/Public/Dist/Display.html?Name=Parse-RPM-Spec
[2] http://search.cpan.org/dist/RPM-Spec/
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-24 Thread Max Kanat-Alexander

Max Kanat-Alexander wrote:

Template-Toolkit 2.22 (not out yet, but will be soon).


This is out now.

-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-24 Thread Max Kanat-Alexander

Dag Wieers wrote:
I just packaged them, however perl-TheSchwartz requires 
perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires 
something we cannot deliver right now.


	However this works out, Data::ObjectDriver *must* not require 
DBD::Oracle, or this is going to create a tremendous support load on us 
at the Bugzilla Project. (Because every Bugzilla administrator will 
attempt to install it, and 99.9% of them will not be able to install 
DBD::Oracle.) It would be better for the module to not be provided by 
rpmforge at all than for it to require DBD::Oracle.


It would be ideal if it did not require any DBD:: driver.

-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-21 Thread Christoph Maser
Am Dienstag, den 21.07.2009, 00:54 +0200 schrieb Dag Wieers:

 The auto requirements are not that bad


Sory but i really think they are totally broken in any non-trivial case.


financial.com AG

Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | 
Germany
Frankfurt branch office/Niederlassung Frankfurt: Messeturm | 
Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany
Management board/Vorstand: Dr. Steffen Boehnert (CEO/Vorsitzender) | Dr. Alexis 
Eisenhofer | Dr. Yann Samson | Matthias Wiederwach
Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender)
Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID 
number/St.Nr.: DE205 370 553
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-21 Thread Dries Verachtert
On Sun, Jul 19, 2009 at 7:18 PM, Dag Wieersd...@wieers.com wrote:
 On Sun, 19 Jul 2009, Dave Cross wrote:

 On 19/07/09 17:40, Dag Wieers wrote:

  On Fri, 17 Jul 2009, Max Kanat-Alexander wrote:

   Bugzilla 3.4 will be coming out soon, and it uses the following Perl
   packages as requirements or optionally:
    Template-Toolkit 2.22 (not out yet, but will be soon).
   TheSchwartz
   Daemon-Generic
    Could we get packages for these in rpmforge? (Particularly the last
   two would be nice, because they have a lot of prereqs.)

  I just packaged them, however perl-TheSchwartz requires
  perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
  something we cannot deliver right now.

 Data::ObjectDriver doesn't require DBD::Oracle. That's just one of the
 optional back-ends for it. It shouldn't be a mandatory requirement.

 Right, but it is pulled in with the auto requirements :-/

 Time to implement that filter-macro and maybe commit it upstream so it
 becomes a standard ?

A possible other solution: we could add a subpackage which contains
the following files:

/usr/lib/perl5/vendor_perl/5.10.0/Data/ObjectDriver/Driver/DBD/Oracle.pm
/usr/lib/perl5/vendor_perl/5.10.0/Data/ObjectDriver/SQL/Oracle.pm
/usr/share/man/man3/Data::ObjectDriver::SQL::Oracle.3pm.gz

Only the subpackage will require oracle libraries in this case. Let me
know what you think, i can add the subpackage if needed.

Dries
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-20 Thread Dag Wieers

On Mon, 20 Jul 2009, Dave Cross wrote:


On 19/07/09 18:18, Dag Wieers wrote:

 On Sun, 19 Jul 2009, Dave Cross wrote:

  On 19/07/09 17:40, Dag Wieers wrote:
   On Fri, 17 Jul 2009, Max Kanat-Alexander wrote:
  
Bugzilla 3.4 will be coming out soon, and it uses the following Perl

packages as requirements or optionally:
 Template-Toolkit 2.22 (not out yet, but will be soon).
TheSchwartz
Daemon-Generic
 Could we get packages for these in rpmforge? (Particularly the 
 last

two would be nice, because they have a lot of prereqs.)
  
   I just packaged them, however perl-TheSchwartz requires

   perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
   something we cannot deliver right now.
 
  Data::ObjectDriver doesn't require DBD::Oracle. That's just one of the

  optional back-ends for it. It shouldn't be a mandatory requirement.

 Right, but it is pulled in with the auto requirements :-/


The META.yml for the distribution[1] doesn't require any of the specific DBD 
modules (presumably deliberately). Any system that generates requirements 
using anything other than the modules listed in META.yml is broken.


Talk to Red Hat ;-) Our scripts only add those requirements (and the ones 
we manually add ourselves afterwards).


But in their defence, META.yml didn't exist 15 years ago so their current 
practices back then made a lot of sense. And on top of that, there are 
still lots of packages that do not ship a (proper) META.yml.


--
--   dag wieers,  d...@wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-20 Thread Dag Wieers

On Mon, 20 Jul 2009, Christoph Maser wrote:


Am Montag, den 20.07.2009, 10:20 +0200 schrieb Dag Wieers:


Talk to Red Hat ;-) Our scripts only add those requirements (and the ones
we manually add ourselves afterwards).

But in their defence, META.yml didn't exist 15 years ago so their current
practices back then made a lot of sense. And on top of that, there are
still lots of packages that do not ship a (proper) META.yml.


As i said before the perl-auto-requires is seriously not working. You
have to check the resulting requires on each rpm. If necessary you have
to use AutoReq: no and set the requiremenst manually. That goes
specially for anything involving DBD, and i'd say its nothing new. I
think this problem came the very moment automatic dependency checking
was introduced.


I don't think it is a good idea to set AutoReq: no and set the 
requirements manually. Because any new updates would have to be verified 
manually again, possibly diffing the source.


The auto requirements are not that bad, especially if it was easier to 
filter out some of the requirements and provides manually. At least if new 
stuff is detected it would be added by default.


--
--   dag wieers,  d...@wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-19 Thread Dave Cross

On 19/07/09 17:40, Dag Wieers wrote:

On Fri, 17 Jul 2009, Max Kanat-Alexander wrote:


Bugzilla 3.4 will be coming out soon, and it uses the following Perl
packages as requirements or optionally:

Template-Toolkit 2.22 (not out yet, but will be soon).
TheSchwartz
Daemon-Generic

Could we get packages for these in rpmforge? (Particularly the last
two would be nice, because they have a lot of prereqs.)


I just packaged them, however perl-TheSchwartz requires
perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
something we cannot deliver right now.


Data::ObjectDriver doesn't require DBD::Oracle. That's just one of the 
optional back-ends for it. It shouldn't be a mandatory requirement.


Dave...
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest


Re: [suggest] Request: Required Perl Packages for Bugzilla 3.4

2009-07-19 Thread Dag Wieers

On Sun, 19 Jul 2009, Dave Cross wrote:


On 19/07/09 17:40, Dag Wieers wrote:

 On Fri, 17 Jul 2009, Max Kanat-Alexander wrote:

  Bugzilla 3.4 will be coming out soon, and it uses the following Perl
  packages as requirements or optionally:
 
  Template-Toolkit 2.22 (not out yet, but will be soon).

  TheSchwartz
  Daemon-Generic
 
  Could we get packages for these in rpmforge? (Particularly the last

  two would be nice, because they have a lot of prereqs.)

 I just packaged them, however perl-TheSchwartz requires
 perl-Data-ObjectDriver, which requires perl-DBD-Oracle, which requires
 something we cannot deliver right now.


Data::ObjectDriver doesn't require DBD::Oracle. That's just one of the 
optional back-ends for it. It shouldn't be a mandatory requirement.


Right, but it is pulled in with the auto requirements :-/

Time to implement that filter-macro and maybe commit it upstream so it 
becomes a standard ?


--
--   dag wieers,  d...@wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]
___
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest