Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
On Tue, Mar 26, 2013 at 1:44 PM, Pierre-Malo Deniélou pierre-malo.denie...@rhul.ac.uk wrote: Hi all, There will be a packagers meeting tonight at 20h UTC as usual. Only one topic: - Release critical bugs: review and status Please all attend for progress to be made on these bugs. Reminder: https://bugs.mageia.org/buglist.cgi?bug_status=NEWbug_status=UNCONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDbug_status=VERIFIEDpriority=release_blockerproduct=Mageiaquery_format=advancedversion=Cauldronorder=assigned_to%2Cbug_id%20DESCquery_based_on=release_blockerlist_id=2442 Can we also discuss what to do about http://check.mageia.org/cauldron/dependencies.html ? Should a thread be started for each to decide what to do about it? Bugs open? Any of those packages that doesn't get fixed will be dropped (as it can not be installed anyway)
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
On 26/03/13 13:58, Pascal Terjan wrote: On Tue, Mar 26, 2013 at 1:44 PM, Pierre-Malo Deniélou pierre-malo.denie...@rhul.ac.uk wrote: Hi all, There will be a packagers meeting tonight at 20h UTC as usual. Only one topic: - Release critical bugs: review and status Please all attend for progress to be made on these bugs. Reminder: https://bugs.mageia.org/buglist.cgi?bug_status=NEWbug_status=UNCONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDbug_status=VERIFIEDpriority=release_blockerproduct=Mageiaquery_format=advancedversion=Cauldronorder=assigned_to%2Cbug_id%20DESCquery_based_on=release_blockerlist_id=2442 Can we also discuss what to do about http://check.mageia.org/cauldron/dependencies.html ? Should a thread be started for each to decide what to do about it? Bugs open? Good idea. Any of those packages that doesn't get fixed will be dropped (as it can not be installed anyway) We should discuss it. Maybe also we can mention the packages which have not been built recently (failed mass rebuild). Can you post a list? Ok. New list of topics: - Uninstallable packages: http://check.mageia.org/cauldron/dependencies.html - Packages which failed rebuild - Release critical bugs: review and status Cheers, -- Malo
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
'Twas brillig, and Pascal Terjan at 26/03/13 13:58 did gyre and gimble: On Tue, Mar 26, 2013 at 1:44 PM, Pierre-Malo Deniélou pierre-malo.denie...@rhul.ac.uk wrote: Hi all, There will be a packagers meeting tonight at 20h UTC as usual. Only one topic: - Release critical bugs: review and status Please all attend for progress to be made on these bugs. Reminder: https://bugs.mageia.org/buglist.cgi?bug_status=NEWbug_status=UNCONFIRMEDbug_status=ASSIGNEDbug_status=REOPENEDbug_status=VERIFIEDpriority=release_blockerproduct=Mageiaquery_format=advancedversion=Cauldronorder=assigned_to%2Cbug_id%20DESCquery_based_on=release_blockerlist_id=2442 Can we also discuss what to do about http://check.mageia.org/cauldron/dependencies.html ? Should a thread be started for each to decide what to do about it? Bugs open? Any of those packages that doesn't get fixed will be dropped (as it can not be installed anyway) Note, mumble can be build without Ice support (I've submitted a build but for some reason I can't get the build deps right locally to test this seems I cannot install lib64db4.8-devel without it pulling in a whole bunch of i586 stuff - likely something to fix in that package too!) Note, pam_ldap should be nuked AFIUI. Drak tools has been updated to suggest pam_nss_ldap instead. - drakauth: o install nss-pam-ldapd instead of nss_ldap (mga#9375) However it seems pam_ldap remains when it should actually be dropped also... AFAUI, the nss_ldap+pam_ldap should be replced by the nss-pam-ldapd+sssd combo no? If so, then a further couple of tweaks are needed in drakauth methinks. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Colin Guthrie mageia@... writes: Note, pam_ldap should be nuked AFIUI. Drak tools has been updated to suggest pam_nss_ldap instead. - drakauth: o install nss-pam-ldapd instead of nss_ldap (mga#9375) However it seems pam_ldap remains when it should actually be dropped also... AFAUI, the nss_ldap+pam_ldap should be replced by the nss-pam-ldapd+sssd combo no? If so, then a further couple of tweaks are needed in drakauth methinks. I thought you could use one or the other (nss-pam-ldapd/sssd)? Also, something should really obsolete the nss_ldap/pam_ldap packages so they get replaced with something else that works for people that already have them installed. If that's done, pam_ldap will be automatically removed from the mirrors anyway. Probably nss-pam-ldapd is the right place to do this.
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
On 26/03/13 14:03, Pierre-Malo Deniélou wrote: Ok. New list of topics: - Uninstallable packages: http://check.mageia.org/cauldron/dependencies.html - Packages which failed rebuild - Release critical bugs: review and status Cheers, There is also the issue of boost-1.52 and gnuradio. https://bugs.mageia.org/show_bug.cgi?id=8825 https://bugs.mageia.org/show_bug.cgi?id=8789 gnuradio builds against 1.52 but is functionally broken, consequently upstream have blacklisted boost-1.52. gnuradio is OK with boost-1.53, but that does break the build of some other packages. I test built all that require it:- http://mtf.no-ip.co.uk/pub/linux/barjac/boost/boost.txt Options: 1. Update boost to 1.53 and fix the other broken builds 2. Somehow provide boost-1.53 or 1.51 alongside 1.52 3. Nuke gnuradio until boost gets updated.
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Le 26/03/2013 15:30, David Walser a écrit : AFAUI, the nss_ldap+pam_ldap should be replced by the nss-pam-ldapd+sssd combo no? If so, then a further couple of tweaks are needed in drakauth methinks. I thought you could use one or the other (nss-pam-ldapd/sssd)? Exactly. And sssd is much more than just nss-pam-ldapd, it also deals with nss resources caching (as nscd), credentials caching (as pam_ccreds), and multiple user account databases. Also, something should really obsolete the nss_ldap/pam_ldap packages so they get replaced with something else that works for people that already have them installed. If that's done, pam_ldap will be automatically removed from the mirrors anyway. Probably nss-pam-ldapd is the right place to do this. Just installing nss-pam-ldapd won't make it works automagically, so the added value of making it obsoleting pam_ldap and nss_ldap is very discussable, as it will turn something working (with obsolete software) unto something non-working. Also, recurrent argument as 'we should obsoletes X so as to remove it from mirror' is still a non-sense. Removing content on the mirror is an internal administrative issue. The whole issue should rather be documented in release notes, so as to have admins handle the upgrade explicitely, rather than trying to adresse it automagically. -- BOFH excuse #391: We already sent around a notice about that.
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Guillaume Rousse guillomovitch@... writes: Also, recurrent argument as 'we should obsoletes X so as to remove it from mirror' is still a non-sense. Removing content on the mirror is an internal administrative issue. Yes, I still agree with you on this in general. The whole issue should rather be documented in release notes, so as to have admins handle the upgrade explicitely, rather than trying to adresse it automagically. OK, that sounds reasonable then. Thanks.
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
'Twas brillig, and Colin Guthrie at 26/03/13 14:21 did gyre and gimble: Can we also discuss what to do about http://check.mageia.org/cauldron/dependencies.html ? Should a thread be started for each to decide what to do about it? Bugs open? Any of those packages that doesn't get fixed will be dropped (as it can not be installed anyway) Note, mumble can be build without Ice support (I've submitted a build but for some reason I can't get the build deps right locally to test this seems I cannot install lib64db4.8-devel without it pulling in a whole bunch of i586 stuff - likely something to fix in that package too!) Yay, it builds, but I made it worse :D Due to the changed build options, mumble-server-web is no longer generated as a package. This will be removed magically after a while and the dep problem will disappear, but what should we do about installs? Should we Obsolete the package in the mumble-server package if that build option is set? It's not technically obsolete tho'. I guess users will get rpm conflicts and will be asked to remove the old mumble-server-web if they upgade mumble-server so perhaps this is all fine as it is? WDYT? Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Packagers meeting tonight (26/03/3013, 20h UTC)
Minutes of the meeting for people who couldn't attend: http://meetbot.mageia.org/mageia-dev/2013/mageia-dev.2013-03-26-20.03.html -- Malo
