Description of problem: Backporting trac to mga9 (I have it working with local build and would like to make installation more standard, pending mga10.
Status: NEW => ASSIGNEDKeywords: (none) => Backport
Écrit : /users/bruno/prj/mageia/9/backports/trac/SRPMS/trac-1.6-1.mga9.src.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-postgresql-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-wsgi-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-cgi-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-sqlite-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-svn-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-standalone-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-mod_python-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-mysql-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-fcgi-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/drakwizard-trac-1.6-1.mga9.noarch.rpm Écrit : /users/bruno/prj/mageia/9/backports/trac/RPMS/noarch/trac-1.6-1.mga9.noarch.rpm
Packages uploaded to core/backports_testing
Has been working for me since more than 6 months now.
Assignee: bruno => qa-bugs
(In reply to Bruno Cornec from comment #3) > Has been working for me since more than 6 months now. @Thomas I propose give OK in base Bruno's test
CC: (none) => andrewsfarm
In cases like this, I always like to try to do at least an install on something other than the developer's hardware. That's just to look for a dependency that might have been overlooked by the developer because it was already installed on his or her machine. (It's happened before.) I installed all of the trac packages, and the dependencies they drew in, in a relatively pristine VirtualBox MGA9-64 Plasma guest. There were no installation errors. With that, and Bruno's test, I'm giving it an OK, and validating.
CC: (none) => sysadmin-bugsKeywords: (none) => validated_backportWhiteboard: (none) => MGA9-64-OK
RH x86_64 LC_ALL=C urpmi /home/katnatek/qa-testing/x86_64/*.rpm Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. Use of uninitialized value in numeric ne (!=) at /usr/lib64/perl5/vendor_perl/URPM/Resolve.pm line 384. To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release (distrib1)") apache-mod_fcgid 2.3.9 9.mga9 x86_64 python3-html5lib 1.1 4.mga9 noarch python3-mysql 1.4.6 6.mga9 x86_64 python3-psycopg2 2.9.3 2.mga9 x86_64 python3-regex 2022.9.13 1.mga9 x86_64 python3-simplejson 3.17.6 2.mga9 x86_64 python3-svn 1.14.2 2.mga9 x86_64 python3-textile 4.0.2 2.mga9 noarch python3-webencodings 0.5.1 8.mga9 noarch (medium "Core Updates (distrib3)") lib64pq5 15.8 1.mga9 x86_64 (command line) drakwizard-trac 1.6 1.mga9 noarch trac 1.6 1.mga9 noarch trac-cgi 1.6 1.mga9 noarch trac-fcgi 1.6 1.mga9 noarch trac-mod_python 1.6 1.mga9 noarch trac-mysql 1.6 1.mga9 noarch trac-postgresql 1.6 1.mga9 noarch trac-sqlite 1.6 1.mga9 noarch trac-standalone 1.6 1.mga9 noarch trac-svn 1.6 1.mga9 noarch trac-wsgi 1.6 1.mga9 noarch 22MB of additional disk space will be used. 4.5MB of packages will be retrieved. Proceed with the installation of the 21 packages? (Y/n) y https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-psycopg2-2.9.3-2.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-webencodings-0.5.1-8.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-textile-4.0.2-2.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-svn-1.14.2-2.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-simplejson-3.17.6-2.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-mysql-1.4.6-6.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-regex-2022.9.13-1.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/apache-mod_fcgid-2.3.9-9.mga9.x86_64.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/python3-html5lib-1.1-4.mga9.noarch.rpm https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/updates/lib64pq5-15.8-1.mga9.x86_64.rpm installing /home/katnatek/qa-testing/x86_64/trac-fcgi-1.6-1.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-wsgi-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/python3-psycopg2-2.9.3-2.mga9.x86_64.rpm /var/cache/urpmi/rpms/python3-webencodings-0.5.1-8.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-cgi-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/python3-simplejson-3.17.6-2.mga9.x86_64.rpm /var/cache/urpmi/rpms/python3-textile-4.0.2-2.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-sqlite-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/python3-mysql-1.4.6-6.mga9.x86_64.rpm /home/katnatek/qa-testing/x86_64/trac-svn-1.6-1.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-standalone-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/apache-mod_fcgid-2.3.9-9.mga9.x86_64.rpm /var/cache/urpmi/rpms/python3-regex-2022.9.13-1.mga9.x86_64.rpm /home/katnatek/qa-testing/x86_64/trac-postgresql-1.6-1.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/python3-svn-1.14.2-2.mga9.x86_64.rpm /home/katnatek/qa-testing/x86_64/drakwizard-trac-1.6-1.mga9.noarch.rpm /var/cache/urpmi/rpms/lib64pq5-15.8-1.mga9.x86_64.rpm /var/cache/urpmi/rpms/python3-html5lib-1.1-4.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-mod_python-1.6-1.mga9.noarch.rpm /home/katnatek/qa-testing/x86_64/trac-mysql-1.6-1.mga9.noarch.rpm Preparing... ################################################################################################## 1/21: lib64pq5 ################################################################################################## 2/21: python3-psycopg2 ################################################################################################## 3/21: python3-svn ################################################################################################## 4/21: python3-regex ################################################################################################## 5/21: apache-mod_fcgid ################################################################################################## 6/21: python3-mysql ################################################################################################## 7/21: python3-simplejson ################################################################################################## 8/21: python3-webencodings ################################################################################################## 9/21: python3-html5lib ################################################################################################## 10/21: python3-textile ################################################################################################## 11/21: trac-sqlite ################################################################################################## 12/21: trac-svn ################################################################################################## 13/21: trac ################################################################################################## 14/21: trac-fcgi ################################################################################################## 15/21: trac-wsgi ################################################################################################## 16/21: trac-cgi ################################################################################################## 17/21: trac-standalone ################################################################################################## 18/21: trac-postgresql ################################################################################################## 19/21: trac-mod_python ################################################################################################## 20/21: trac-mysql ################################################################################################## 21/21: drakwizard-trac ################################################################################################## Bruno I not see the wizard in the MCC
Remove validation until answer to comment#6
CC: sysadmin-bugs => (none)Keywords: validated_backport => feedback
Component: RPM Packages => Backports
(In reply to katnatek from comment #6) > 21/21: drakwizard-trac > ############################################################################# > ##################### > > Bruno I not see the wizard in the MCC Well, as this is a server apps, I never used drakwizard on the machine where I installed it. So I'll have to see why this isn't working as expected for you. (and I have no knowledge of drakwizard either :-))
Have you tried using drakwizard rather than mcc (while I'm searchin how it should appear in mcc) ?
Well looking at that, I think drakwizard is a completely different helper that is not seen in MCC. You can configure server services with it, which you can't with mcc. So I think the behaviour you've seen, is just normal in fact.
I'm not arguing the point at all, but with a name like "drakwizard" it certainly sounds like it *ought* to be associated with MCC...
Well, maybe but it's not ! It's another command allowing you to setup services, outside of MCC, and options that MCC doesn't provide. I wasn't even aware it existed before the above remark ;-) Now please test it, launch the drakwizard command and see that Trac is indeed integrated with it as it should. You can also see that you can configure sshd e.g., which you can't from MCC either. That's coherent.
OK I see trac in drakwizard but Part of description of drakwizard-trac This package provides a wizard to create trac multiple project repository using tracd. You can access it with drakwizard or with Mageia control center. That is why I expect to see it as part of MCC and in drakwizard I see configuration of other services like ssh & apache Look like need to remove the text after drakwizard or consult with other devs how to get this module visible in MCC As the text is not accurate, I think we can't validate, @Thomas you have last word.
(In reply to katnatek from comment #13) > OK I see trac in drakwizard but > > Part of description of drakwizard-trac > This package provides a wizard to create trac multiple project > repository using tracd. > You can access it with drakwizard or with Mageia control center. > > That is why I expect to see it as part of MCC and in drakwizard I see > configuration of other services like ssh & apache > > Look like need to remove the text after drakwizard or consult with other > devs how to get this module visible in MCC > > As the text is not accurate, I think we can't validate, @Thomas you have > last word. I must agree. Drakwizard is separate from MCC, and the description for drakwizard-trac that shows in drakrpm shouldn't reference MCC. Now is the time to correct that description. If we let it go now, without fixing it, it may never happen. Besides, leaving it alone now, when we know about it, is sloppy. We should strive to avoid being sloppy whenever possible.
Interesting. Neither I knew what drakwizard is. I see it is referenced in MCC documentation, so OK, and also in wiki https://wiki.mageia.org/en/Server_Wizards (In reply to Bruno Cornec from comment #10) > I think drakwizard is a completely different helper > that is not seen in MCC. Drakwizard can be started alone (also in text mode) in which case it present a menu on what wizard to run - but it also add two categories to MCC. So IMO trac should appear there in MCC, when drakwizard is installed. Does that not work currently?
CC: (none) => fri
BTW, it seems trac and some other wizards are missing entries in https://doc.mageia.org/mcc/9/en/content ?
(In reply to Morgan Leijström from comment #16) > BTW, it seems trac and some other wizards are missing entries in > https://doc.mageia.org/mcc/9/en/content ? As trac is a new one is normal that is missing, perhaps a thing to add for mga10
Whiteboard: MGA9-64-OK => (none)
(In reply to katnatek from comment #17) > (In reply to Morgan Leijström from comment #16) > > BTW, it seems trac and some other wizards are missing entries in > > https://doc.mageia.org/mcc/9/en/content ? > > As trac is a new one is normal that is missing, perhaps a thing to add for > mga10 CC:ing docteam for that, and check that all wizards of drakwizard are at least mentioned with short description so users see what is available.
CC: (none) => doc-bugs
(In reply to katnatek from comment #13) > You can access it with drakwizard or with Mageia control center. > > That is why I expect to see it as part of MCC and in drakwizard I see > configuration of other services like ssh & apache Indeed, so I removed that text to avoid confusion. Will push a new version with that modification.
(In reply to Bruno Cornec from comment #19) > (In reply to katnatek from comment #13) > > You can access it with drakwizard or with Mageia control center. > > > > That is why I expect to see it as part of MCC and in drakwizard I see > > configuration of other services like ssh & apache > > Indeed, so I removed that text to avoid confusion. > > Will push a new version with that modification. Well based on what Margan said, I checked that indeed relaunching mcc once drakwizard is installed show me the wizzards to configure the services, ... except trac is not there. So there is still some magic missing :-(
While drakwizard-trac adds a perl module under /usr/share/perl5/vendor_perl/MDK/Wizard/, it doesn't provide anything under /usr/share/wizards/ which other wizards have. So I guess I need to add stuff there, even if I have still no clue what should be done :-(
Analyzing further, it seems that the list of wizard displayed in MCC is hard-coded in drakwizard The hash %all_wizards declares what will be usable. If you launch drakwizard proftpd e.g. then you'll directly arrive at the configuration of proftpd. Same for squid. However as trac is not part of that list, doing drakwizard trac doesn't work. Which is how MCC seem to be launching the wizards, thanks to a .desktop file. And even adding the .desktop file isn't sufficient :-( Modify drakwizard to add: trac => [ 'Trac', N("Trac server") ], to %all_wizards makes drakwizard trac work, but it still doesn't appear in MCC, so more needs to be done (I have a .desktop file added as well)
/usr/libexec/drakconf also has a static list of wizards: N("Network Services"), 'network-services-mdk', 'mcc-network', [ { title => N("Network Services"), list => [ (wizard_format( # [ id, wizard file name, icon, description ] [ "DHCP wizard", "dhcp", 'dhcp_server-mdk', N("Configure DHCP"), N("Set up a DHCP server"), 'Dhcp.pm', ], [ "DNS wizard", "bind", 'dns_server-mdk', N("Configure DNS"), N("Set up a DNS server (network name resolution)"), 'Bind.pm', ], [ "Squid wizard", "squid", 'drakproxy-mdk', N("Configure proxy"), N("Configure a web caching proxy server"), 'Squid.pm', ], [ "Time wizard", "ntp", 'ntp_server-mdk', N("Configure time"), N("Set the time of the server to be synchronized with an external time server"), 'Ntp.pm', ], [ "SSHD wizard", "sshd", 'wizard-sshd', N("OpenSSH daemon configuration"), N("OpenSSH daemon configuration"), 'Sshd.pm', ], ), ), ] }, ] So that's why Trac doesn't appear here. So a patch to drakconf is needed to be able to see Trac conf appearing in mcc.
I can confirm that adding an entry on this list allows trac to be seen. Now, that could be a way to solve that particular issue. It's not really a way to dynamically detect wizards added and manage them transparently. Let me know if you want I provide patches to drakconf and drakwizard-base in order to have that solved for trac at least.
(In reply to Bruno Cornec from comment #23) > /usr/libexec/drakconf also has a static list of wizards: > > N("Network Services"), 'network-services-mdk', 'mcc-network', > [ > { > title => N("Network Services"), > list => [ > (wizard_format( # [ id, wizard file name, icon, > description ] > [ "DHCP wizard", "dhcp", 'dhcp_server-mdk', > N("Configure DHCP"), > N("Set up a DHCP server"), 'Dhcp.pm', > ], > [ "DNS wizard", "bind", 'dns_server-mdk', > N("Configure DNS"), > N("Set up a DNS server (network name > resolution)"), 'Bind.pm', > ], > [ "Squid wizard", "squid", 'drakproxy-mdk', > N("Configure proxy"), > N("Configure a web caching proxy server"), > 'Squid.pm', > ], > [ "Time wizard", "ntp", 'ntp_server-mdk', > N("Configure time"), > N("Set the time of the server to be synchronized > with an external time server"), 'Ntp.pm', > ], > [ "SSHD wizard", "sshd", 'wizard-sshd', > N("OpenSSH daemon configuration"), > N("OpenSSH daemon configuration"), 'Sshd.pm', > ], > ), > ), > ] > }, > ] > > > So that's why Trac doesn't appear here. > > So a patch to drakconf is needed to be able to see Trac conf appearing in > mcc. Thank you for the investigation that should be a report for fix in mageia 10/cauldron, just correct what you can for mga 9, like the description will be fine for this backport
(In reply to Bruno Cornec from comment #24) > I can confirm that adding an entry on this list allows trac to be seen. > > Now, that could be a way to solve that particular issue. It's not really a > way to dynamically detect wizards added and manage them transparently. > > Let me know if you want I provide patches to drakconf and drakwizard-base in > order to have that solved for trac at least. Add to mageiatools
CC: (none) => mageiatools
Packages on their way to updates_testing: RPMS/noarch/drakwizard-trac-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-cgi-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-fcgi-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-mod_python-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-mysql-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-postgresql-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-sqlite-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-standalone-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-svn-1.6-1.1.mga9.noarch.rpm RPMS/noarch/trac-wsgi-1.6-1.1.mga9.noarch.rpm SRPMS/trac-1.6-1.1.mga9.src.rpm
Getting with other updates installing //home/katnatek/qa-testing/x86_64/trac-svn-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-cgi-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-mod_python-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-sqlite-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-fcgi-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/drakwizard-trac-1.6-1.1.mga9.noarch.rpm /var/cache/urpmi/rpms/compat-golang-github-sirupsen-logrus-devel-1.9.0-1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-postgresql-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-wsgi-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-mysql-1.6-1.1.mga9.noarch.rpm /var/cache/urpmi/rpms/compat-golang-github-nats-io-devel-1.10.0-5.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-1.6-1.1.mga9.noarch.rpm //home/katnatek/qa-testing/x86_64/trac-standalone-1.6-1.1.mga9.noarch.rpm Preparing... ################################################################################################## 1/13: trac-cgi ################################################################################################## 2/13: trac-sqlite ################################################################################################## 3/13: trac ################################################################################################## 4/13: trac-svn ################################################################################################## 5/13: trac-mod_python ################################################################################################## 6/13: trac-fcgi ################################################################################################## 7/13: trac-postgresql ################################################################################################## 8/13: trac-wsgi ################################################################################################## 9/13: trac-mysql ################################################################################################## 10/13: trac-standalone ################################################################################################## 11/13: compat-golang-github-nats-io-devel ################################################################################################## 12/13: compat-golang-github-sirupsen-logrus-devel ################################################################################################## 13/13: drakwizard-trac ################################################################################################## 1/11: removing trac-standalone-1.6-1.mga9.noarch ################################################################################################## 2/11: removing trac-mysql-1.6-1.mga9.noarch ################################################################################################## 3/11: removing trac-wsgi-1.6-1.mga9.noarch ################################################################################################## 4/11: removing trac-postgresql-1.6-1.mga9.noarch ################################################################################################## 5/11: removing trac-fcgi-1.6-1.mga9.noarch ################################################################################################## 6/11: removing trac-mod_python-1.6-1.mga9.noarch ################################################################################################## 7/11: removing trac-sqlite-1.6-1.mga9.noarch ################################################################################################## 8/11: removing trac-cgi-1.6-1.mga9.noarch ################################################################################################## 9/11: removing trac-1.6-1.mga9.noarch ################################################################################################## 10/11: removing trac-svn-1.6-1.mga9.noarch ################################################################################################## 11/11: removing drakwizard-trac-1.6-1.mga9.noarch ################################################################################################## ---------------------------------------------------------------------- More information on package trac-1.6-1.1.mga9.noarch Trac changed the format of the database in the 0.10 release. If you are upgrading from a pre-0.10 version, please see the file UPGRADE, in /usr/share/doc/trac-1.6/. Remember you will need to run: trac-admin <env-path> upgrade and trac-admin <env-path> wiki upgrade to ensure your installation is up to date (remember to backup first!) In order to ease the installation, and provides more modularity, trac package have been split in four frontends. You can choose trac-standalone for a version with tracd, or trac-cgi, trac-fcgi or trac-mod_python for integration with a webserver (e.g. apache). ---------------------------------------------------------------------- urpmq -pi /home/katnatek/qa-testing/x86_64/drakwizard-trac-1.6-1.1.mga9.noarch.rpm Name : drakwizard-trac Version : 1.6 Release : 1.1.mga9 Group : System/Configuration Size : 7485 Architecture: noarch Source RPM : trac-1.6-1.1.mga9.src.rpm Build Host: localhost Packager : bcornec <bcornec> URL : https://trac.edgewall.org/ Summary : Trac Integrated SCM & Project manager - project creation wizard Description : Trac is a minimalistic web-based software project management and bug/issue tracking system. It provides an interface to revision control systems (Subversion), an integrated Wiki and convenient report facilities. This package provides a wizard to create trac multiple project repository using tracd. You can access it with drakwizard but not with Mageia control center yet. trac is in drakwizard and start the configuration I not go beyond that and cancel the configuration, look good enough now
Keywords: feedback => (none)Whiteboard: (none) => MGA9-64-OK
Even if we change description here to omit that part it say it shows up in MCC, other references (like our wiki) still say drakwizard components show up in MCC... IMO we should not change text, but instead open a bug to change MCC/drakwizard whatever to follow and make trac visible.
(In reply to Morgan Leijström from comment #29) > Even if we change description here to omit that part it say it shows up in > MCC, other references (like our wiki) still say drakwizard components show > up in MCC... > > IMO we should not change text, but instead open a bug to change > MCC/drakwizard whatever to follow and make trac visible. Hello, There is no reference to trac in our wiki. I don't remember that our documentation has a mention of trac. Even if this could be an advantage to have it managed by our MCC, there is nothing that can stop it to be published as backport. Our documentation has sections for the drakwizard tools. https://doc.mageia.org/mcc/9/en/content/mcc-networkservices.html It is stated that they have to be installed to be present in MCC.
CC: (none) => yvesbrungard
(In reply to papoteur from comment #30) > (In reply to Morgan Leijström from comment #29) > > Even if we change description here to omit that part it say it shows up in > > MCC, other references (like our wiki) still say drakwizard components show > > up in MCC... > > > > IMO we should not change text, but instead open a bug to change > > MCC/drakwizard whatever to follow and make trac visible. > > Hello, > There is no reference to trac in our wiki. > I don't remember that our documentation has a mention of trac. No but we are saying generally that drakwizards shows up in MCC. > Even if this could be an advantage to have it managed by our MCC, there is > nothing that can stop it to be published as backport. I agree. I did not until now realise that trac is in backport. > Our documentation has sections for the drakwizard tools. > https://doc.mageia.org/mcc/9/en/content/mcc-networkservices.html > It is stated that they have to be installed to be present in MCC. Yes, they should normally be visible in MCC when installed. But as trac is in backport in mga9, lets forgive it not displaying. Users who installs from backport apparently is aware trac exists. I suggest we ship this, and for mga10 open bug about making trac visible in MCC, and reinstate the about that in package description (if it was removed for mga10)
(In reply to Morgan Leijström from comment #31) > > Yes, they should normally be visible in MCC when installed. > But as trac is in backport in mga9, lets forgive it not displaying. > Users who installs from backport apparently is aware trac exists. > > > I suggest we ship this, and for mga10 open bug about making trac visible in > MCC, and reinstate the about that in package description (if it was removed > for mga10) I'd agree to this. But... (In reply to Bruno Cornec from comment #24) > I can confirm that adding an entry on this list allows trac to be seen. > > Now, that could be a way to solve that particular issue. It's not really a > way to dynamically detect wizards added and manage them transparently. > It seems to me that the very best solution for MGA10 and beyond would be, if possible, to add that dynamic detection capability, not just for trac, but for other wizards that may come along.
If there are no more objections, we can restore the validation.
Keywords: (none) => validated_backportCC: (none) => sysadmin-bugs
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33817
trac-1.6-1.1.mga9.src.rpm has been moved to backports.
CC: (none) => dan
(In reply to Thomas Andrews from comment #32) > (In reply to Bruno Cornec from comment #24) > > I can confirm that adding an entry on this list allows trac to be seen. > > > > Now, that could be a way to solve that particular issue. It's not really a > > way to dynamically detect wizards added and manage them transparently. > > > > It seems to me that the very best solution for MGA10 and beyond would be, if > possible, to add that dynamic detection capability, not just for trac, but > for other wizards that may come along. Yep, currently both in MCC and drakwizard the analysis of existing wizard is completely static (variables containing the existing ones) and duplication of information wrt description, names... A better approach would be to look for say the .desktop files and if one is present, then suppose the wizard is available and propose it in the list, and use the content of the .desktop file to display the description, name, ... Clearly for mga10 or later... But Iwasn't even knowing we had these features of configuring services through it, so would be great also to promote it we can solve these issues.
(In reply to Dan Fandrich from comment #34) > trac-1.6-1.1.mga9.src.rpm has been moved to backports. Thx Dan !
Mail send to backports-announce
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED