Re: [Mageia-dev] Help needed: rpmlint checks not working
On Mon, 14 Jan 2013, nicolas vigier wrote: On Sat, 12 Jan 2013, Colin Guthrie wrote: 'Twas brillig, and nicolas vigier at 12/01/13 15:45 did gyre and gimble: On Sat, 12 Jan 2013, Colin Guthrie wrote: Hi, It seems the rpmlint checks I added to detect (and prevent upload of) files in /var/run and in /etc/udev/rules.d etc. are not working. Can someone see if I've done something wrong? The file distribution.error.list from rpmlint-mageia-policy is not used by the buildsystem to reject uploads. Instead it is using a list of rpmlint errors defined in youri configuration. I added them now : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 Maybe we could change it to use distribution.error.list file instead. Awesome, thanks. Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967
Re: [Mageia-dev] tmpfiles conversion: Thanks! Only 30 pkgs to go!
Today's status update. Feel free to fix anything you fancy. Use https://wiki.mageia.org/en/System_Service_policy as a guide. I should be able to finish them off some night this week. cups:/var/run/cups/certs cyrus-sasl:/var/run/saslauthd freeswitch:/run/freeswitch glusterfs-server:/var/run/glusterfsd gnokii:/var/lock/gnokii hplip:/var/run/hplip jetty:/var/run/jetty kolab-saslauthd:/var/run/kolab-saslauthd kolab-saslauthd:/var/run/saslauthd kolab-server:/var/run/kolabd leafnode:/var/lock/news openldap-servers:/var/run/ldap pacemaker:/var/run/crm php-fpm:/var/run/php-fpm prelude-manager:/var/run/prelude-manager samba-common:/var/run/samba smtp-gated:/run/smtp-gated stompserver:/var/run/stompserver system-config-printer-udev:/var/run/udev-configure-printer system-config-printer-udev:/var/run/udev-configure-printer/usb-uris tomcat:/var/run/tomcat.pid uucp:/var/lock/uucp uuidd:/var/run/uuidd vtun:/var/lock/vtund xen:/run/xend Should be OK to ignore (AL13N checked) xen:/run/xend/boot Should be OK to ignore (AL13N checked) xen:/run/xenstored Should be OK to ignore (AL13N checked) zabbix-agent:/var/run/zabbix zabbix:/var/run/zabbix Also some of the udev things (just need the rules moving from /etc/udev/rules.d to /usr/lib/udev/rules.d (aka %_udevrulesdir)): alsa-tools-firmware:/etc/udev/rules.d/90-alsa-tools-firmware.rules dkms-dahdi:/etc/udev/rules.d/40-dahdi.rules dkms-dahdi:/etc/udev/rules.d/40-xpp.rules drbd-utils:/etc/udev/rules.d/65-drbd.rules em8300:/etc/udev/rules.d/em8300.rules gammu:/etc/udev/rules.d/69-gammu-acl.rules gnome-bluetooth:/etc/udev/rules.d/61-gnome-bluetooth-rfkill.rules gpsd:/etc/udev/rules.d/99-gpsd.rules hplip-model-data:/etc/udev/rules.d/40-hplip.rules hplip-model-data:/etc/udev/rules.d/56-hpmud_add_printer.rules hplip-model-data:/etc/udev/rules.d/56-hpmud_support.rules hplip-model-data:/etc/udev/rules.d/86-hpmud_plugin.rules hso-rezero:/etc/udev/rules.d/49_hso-udev.rules iguanair:/etc/udev/rules.d/iguanaIR.rules indilib:/etc/udev/rules.d/99-gpusb.rules kino:/etc/udev/rules.d/kino.rules libcrystalhd-common:/etc/udev/rules.d/65-crystalhd.rules libdjconsole:/etc/udev/rules.d/45-hpdjconsole.rules libifp:/etc/udev/rules.d/10-libifp.rules libnjb:/etc/udev/rules.d/60-libnjb.rules libunicap:/etc/udev/rules.d/50-euvccam.rules pilot-link-common:/etc/udev/rules.d/60-libpisock.rules razercfg:/etc/udev/rules.d/01-razer-udev.rules sound-scripts:/etc/udev/rules.d/alsa.rules util-linux:/etc/udev/rules.d/60-raw.rules virtualbox:/etc/udev/rules.d/virtualbox.rules virtualbox-guest-additions:/etc/udev/rules.d/vbox-additions.rules zapata:/etc/udev/rules.d/xpp.rules -- 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] Help needed: rpmlint checks not working
'Twas brillig, and nicolas vigier at 15/01/13 10:57 did gyre and gimble: Awesome, thanks. Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Lovely. Thank you :) 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/
[Mageia-dev] autoreconf failures.... (build-aux/test-driver not found)
Hi, This is the second time I've seen this failure now: + autoreconf parallel-tests: error: required file 'build-aux/test-driver' not found parallel-tests: 'automake --add-missing' can install 'test-driver' autoreconf: automake failed with exit status: 1 This was with systemd (http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20130115103253.colin.valstar.9981/log/systemd-195-8.mga3/build.0.20130115103305.log), but I also saw it with network manager yesterday. I found it was easily fixed by changing autoreconf to autoreconf --force --install --verbose (the --verbose isn't needed but likely useful for the log in the event of a failure) HTHs if you have similar issues. 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] proftpd - why was mdv package imported over ours nuking our changes???
Le lundi 14 janvier 2013 00:48:01 Juan Luis Baptiste a écrit : Hi, My mistake too, when Alfonso told me he was going to use the mdv's spec I didn't explicitly told him to merge back any change on mga spec (maybe for me this was something implicit to be done but now I see it isn't for everybody), and just checked his work on the update which was ok. I'll be more careful in the future when reviewing my apprentice's work, I'm sorry for the trouble caused by me and Alfonso. Cheers, What I do usually with my apprentices is not review only the SPEC, but also the diffs from the last commit before they touched it. It allows to see that can of huge changes :) Samuel
Re: [Mageia-dev] Freeze push: gnome-boxes 3.6.3
On Mon, 14 Jan 2013, Olav Vitters wrote: Crasher fix. Already have 3.6.2, seems like non intrusive update. Submitted.
Re: [Mageia-dev] tmpfiles conversion: Thanks! Only 30 pkgs to go!
Colin Guthrie skrev 15.1.2013 12:58: Today's status update. Feel free to fix anything you fancy. Use https://wiki.mageia.org/en/System_Service_policy as a guide. I should be able to finish them off some night this week. uuidd:/var/run/uuidd I'll fix atleast this... Also some of the udev things (just need the rules moving from /etc/udev/rules.d to /usr/lib/udev/rules.d (aka %_udevrulesdir)): drbd-utils:/etc/udev/rules.d/65-drbd.rules util-linux:/etc/udev/rules.d/60-raw.rules virtualbox:/etc/udev/rules.d/virtualbox.rules virtualbox-guest-additions:/etc/udev/rules.d/vbox-additions.rules and theese... -- Thomas
Re: [Mageia-dev] Freeze push: sir 2.5.1
On Mon, 14 Jan 2013, Pierre-Malo Deniélou wrote: Please push sir, which I updated to version 2.5.1. I has some bug fixes and a few new features that we want and that are not too risky to put in for Mageia 3 (since nothing depends on sir). I tested the install and usability. Submitted.
Re: [Mageia-dev] Features
'Twas brillig, and Mustafaa Al-Hamdaani at 15/01/13 12:35 did gyre and gimble: Hi, Are features still accepted for Mageia 3? It's too late for major features. I have these three: 1) Enable vertical two finger scrolling by default, simple but important. This is possible but has to be configured. By default we enable side-swipe scrolling. Unlike on Macs where two finger scrolling is default, a lot of PC laptops (mine included) have graphics on their touchpad indicating the sides can be used for scrolling. Enabling two finger by default would confuse users where side scrolling has both graphics and used to work in the past. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan This would be up to the KDE team to decide, but I suspect it's too late. 3) catalyst-legacy for AMD cards 4xxx and before. Not sure about this one. 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] Features
Le 15/01/2013 13:35, Mustafaa Al-Hamdaani a écrit : Hi, Are features still accepted for Mageia 3? I have these three: List of features has been closed some time ago and we are in version freeze and beta release. Please next time try to propose it in the beginning of the release cycle :) 1) Enable vertical two finger scrolling by default, simple but important. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan 3) catalyst-legacy for AMD cards 4xxx and before. I know there is a policy for features, but I am asking, can I request features now or it's too late? Mustafa Muhammad Hadi -- Anne http://mageia.org
Re: [Mageia-dev] Freeze brea: jgraphx
On Tue, Jan 15, 2013 at 10:43 AM, D.Morgan dmorga...@gmail.com wrote: Hi, Please push jgraphx this is needed by scilab Regards, D. ping
Re: [Mageia-dev] freeze push: jline
On Tue, Jan 15, 2013 at 8:17 AM, D.Morgan dmorga...@gmail.com wrote: hi, please push jline, this is a new version that builds witn maven 3 Regards, D. ping
[Mageia-dev] Freeze push: gnome-menus 3.6.2
Small bugfix and translation updates. -- Regards, Olav ---BeginMessage--- About Menu Library == Library for the Desktop Menu fd.o specification News * 688972 call menu_layout_load() with non_prefixed_name parameter * Translation updates (Arabic, Kannada, Uyghur) ChangeLog = http://download.gnome.org/sources/gnome-menus/3.6/gnome-menus-3.6.2.changes (2.60K) Download http://download.gnome.org/sources/gnome-menus/3.6/gnome-menus-3.6.2.tar.xz (414K) sha256sum: f6cefb25ce3ca2a0e4cb43894089cc6079bf948230e99bc0e244b380fa84bf4f ___ ftp-release-list mailing list ftp-release-l...@gnome.org https://mail.gnome.org/mailman/listinfo/ftp-release-list ---End Message---
[Mageia-dev] Freeze push: scribus
Hello, Could scribus 1.4.2 be pushed? It features a hunspell based spellchecker, which obsoletes aspell checker. Thus, we could finally throw all aspell related pacakges in mga3, as planed. \o/ Regards.
Re: [Mageia-dev] Features
On 01/15/2013 03:42 PM, Thomas Backlund wrote: Mustafaa Al-Hamdaani skrev 15.1.2013 14:35: Hi, Are features still accepted for Mageia 3? I have these three: 1) Enable vertical two finger scrolling by default, simple but important. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan 3) catalyst-legacy for AMD cards 4xxx and before. This one depends on AMD. They have not released any legacy driver since 12.6 last summer, and that is not supporting x11-server 1.13 we use. I know, I just hoped we can ship x11-server 1.12 and 1.13 and only one of them is installed, the power consumption with the open source drivers is just insane, especially for a laptop (and the quality too). I know there is a policy for features, but I am asking, can I request features now or it's too late? Mustafa Muhammad Hadi
Re: [Mageia-dev] Features
On 01/15/2013 03:46 PM, Colin Guthrie wrote: 'Twas brillig, and Mustafaa Al-Hamdaani at 15/01/13 12:35 did gyre and gimble: Hi, Are features still accepted for Mageia 3? It's too late for major features. I have these three: 1) Enable vertical two finger scrolling by default, simple but important. This is possible but has to be configured. By default we enable side-swipe scrolling. Unlike on Macs where two finger scrolling is default, a lot of PC laptops (mine included) have graphics on their touchpad indicating the sides can be used for scrolling. Enabling two finger by default would confuse users where side scrolling has both graphics and used to work in the past. But now it does not work (at least for me), after enabling it I just very much better, so I hoped it enabled by default to enhance the user experience. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan This would be up to the KDE team to decide, but I suspect it's too late. 3) catalyst-legacy for AMD cards 4xxx and before. Not sure about this one. Col
[Mageia-dev] [Freeze push] gis software stack
Sorry for the trouble, but I didn't get to do it in time (and Anne told me on IRC, this would be possible). I updated the gis software stack, because parts of it were quite out of date. Please submit these packages in the following build order: geos (new minor version) gdal (rebuild) postgis (new version, 1.5 was really out of date) grass (rebuild) libspatialite (new package needed by new qgis) libspatialindex (new package needed by new qgis) qgis (somebody already updated it in svn but never built it successfully) mapserver (new version) They all built locally on an up to date cauldron, so it shouldn't make any problems. If it does, just contact me. Thx, Oliver -- Oliver Burger aka obgr_seneca Mageia contributor
Re: [Mageia-dev] Features
On 01/15/2013 03:48 PM, Anne Nicolas wrote: Le 15/01/2013 13:35, Mustafaa Al-Hamdaani a écrit : Hi, Are features still accepted for Mageia 3? I have these three: List of features has been closed some time ago and we are in version freeze and beta release. Please next time try to propose it in the beginning of the release cycle :) I will, thank you. 1) Enable vertical two finger scrolling by default, simple but important. 2) Desktop greeter (like kaptan of pardus or its fork for Chakra, kapudan): http://www.chakra-linux.org/wiki/index.php/Kapudan 3) catalyst-legacy for AMD cards 4xxx and before. I know there is a policy for features, but I am asking, can I request features now or it's too late? Mustafa Muhammad Hadi
Re: [Mageia-dev] Help needed: rpmlint checks not working
On 15 January 2013 11:57, nicolas vigier bo...@mars-attacks.org wrote: Awesome, thanks. Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules?
Re: [Mageia-dev] Help needed: rpmlint checks not working
On Tue, 15 Jan 2013, Thierry Vignaud wrote: On 15 January 2013 11:57, nicolas vigier bo...@mars-attacks.org wrote: Awesome, thanks. Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2.
Re: [Mageia-dev] [changelog] [RPM] cauldron tainted/release mplayer-1.1-9.mga3.tainted
On 8 January 2013 04:35, fwang buildsystem-dae...@mageia.org wrote: + Revision: 341579 - rebuild for ffmpeg 1.1 + luigiwalser luigiwalser - fix building with bundled ffmpeg Not a big deal but here's a warning: Playing foobar.mp4. libavformat version 54.59.106 (external) Mismatching header version 54.6.101
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release python-virtualenv-1.7.1.2-4.mga3
On 13 January 2013 22:41, umeabot buildsystem-dae...@mageia.org wrote: umeabot umeabot 1.7.1.2-4.mga3: + Revision: 379674 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild err, shouldn't we tweak /etc/urpmi/prefer.vendor.list for: # urpmi xen In order to satisfy the 'pythonegg(setuptools)' dependency, one of the following packages is needed: 1- python-virtualenv-1.7.1.2-4.mga3.noarch: Virtual Python Environment builder (to install) 2- python-distribute-0.6.34-2.mga3.noarch: Python Distutils Enhancements (to install) 3- python3-setuptools-0.6.28-2.mga3.noarch: Python Distutils Enhancements (to install) What is your choice? (1-3)
Re: [Mageia-dev] Help needed: rpmlint checks not working
On 15 January 2013 19:00, nicolas vigier bo...@mars-attacks.org wrote: Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. Well no. No as in it may be possible that some updates upload will break due to some error now being detected and rejected. Could we script a pass on all packages with that rpmlint config to catch any such packages and fix them?
Re: [Mageia-dev] Help needed: rpmlint checks not working
'Twas brillig, and nicolas vigier at 15/01/13 18:00 did gyre and gimble: On Tue, 15 Jan 2013, Thierry Vignaud wrote: This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. For packages affected by the rules I added, I use the following commands to get the affected packages (now mercifully small!): urpmf ^(/var)?/(run|lock)/ | sort -u run-lock.txt urpmf ^/etc/udev/rules.d/ | sort -u udev.txt urpmf ^/etc/tmpfiles.d/ | sort -u tmpfiles.txt urpmf ^/etc/systemd/system/ | sort -u units.txt The first two show 21 (ignoring xen) and 19 respectively. The last two commands both show no affected packages \o/ So not too much to fix up :) 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] [changelog] [RPM] cauldron core/release libvirt-1.0.1-6.mga3
On 14 January 2013 21:18, tmb buildsystem-dae...@mageia.org wrote: tmb tmb 1.0.1-6.mga3: + Revision: 388067 - work around broken kernel headers (if_bridge.h not selfcontainted) (P4, upstream) + colin colin - Use kernel-source instead. Headers seems not enough. - Add kernel-headers to build requires - Switch to tmpfiles for [/var]/run dirs + umeabot umeabot - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild Preparing... # 17/23: libvirt-utils ## The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Re: [Mageia-dev] Help needed: rpmlint checks not working
On 15 January 2013 19:15, Colin Guthrie mag...@colin.guthr.ie wrote: http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. For packages affected by the rules I added, I use the following commands to get the affected packages (now mercifully small!): urpmf ^(/var)?/(run|lock)/ | sort -u run-lock.txt urpmf ^/etc/udev/rules.d/ | sort -u udev.txt urpmf ^/etc/tmpfiles.d/ | sort -u tmpfiles.txt urpmf ^/etc/systemd/system/ | sort -u units.txt The first two show 21 (ignoring xen) and 19 respectively. The last two commands both show no affected packages \o/ So not too much to fix up :) err, just look at all the rules that were added (copied from mga2)...
Re: [Mageia-dev] Help needed: rpmlint checks not working
'Twas brillig, and Thierry Vignaud at 15/01/13 18:09 did gyre and gimble: On 15 January 2013 19:00, nicolas vigier bo...@mars-attacks.org wrote: Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. Well no. No as in it may be possible that some updates upload will break due to some error now being detected and rejected. Could we script a pass on all packages with that rpmlint config to catch any such packages and fix them? Well the first commit certainly applied to updates (and I queried as much), but I think the second commit means it only applies to cauldron, not any updates to mga2 etc. 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] Help needed: rpmlint checks not working
On 15 January 2013 19:17, Colin Guthrie mag...@colin.guthr.ie wrote: Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. Well no. No as in it may be possible that some updates upload will break due to some error now being detected and rejected. Could we script a pass on all packages with that rpmlint config to catch any such packages and fix them? Well the first commit certainly applied to updates (and I queried as much), but I think the second commit means it only applies to cauldron, not any updates to mga2 etc. My point is we just added to _CAULDRON_ == mga3 a lot of rules that were missed, just after mass rebuild, and I fear that when we'll try to issue updates to _mga3_, we may see some being rejected, this is why I ask we check current cauldron with upload server rpmlint config...
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release xen-4.2.1-2.mga3
On 13 January 2013 00:58, alien buildsystem-dae...@mageia.org wrote: alien alien 4.2.1-2.mga3: + Revision: 361563 - Fix udev migration - fix /run being tmpfs Just for the fun, I rebooted with kernel-server, see virt-manager failed, systemctl says service succeeded but exited and indeed: # /usr/sbin/xend start xc: error: Could not obtain handle on privileged command interface (2 = No such file or directory): Internal error Traceback (most recent call last): File /usr/sbin/xend, line 36, in module from xen.xend.server import SrvDaemon File /usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py, line 26, in module import relocate File /usr/lib64/python2.7/site-packages/xen/xend/server/relocate.py, line 28, in module from xen.xend import XendDomain File /usr/lib64/python2.7/site-packages/xen/xend/XendDomain.py, line 36, in module from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File /usr/lib64/python2.7/site-packages/xen/xend/XendCheckpoint.py, line 20, in module from xen.xend import balloon, sxp, image File /usr/lib64/python2.7/site-packages/xen/xend/image.py, line 46, in module xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'xc_interface_open failed: No such file or directory')
Re: [Mageia-dev] Missign rebuilds tagged mga1
On Tuesday 15 Jan 2013 00:28:40 JA Magallón wrote:
Hi...
As the mass rebuild seems almost done, I have supposed that
everything in
my box not tagged ad mga3 are leftovers from previous installs, as I
had
not reinstalled my box since mga1. I checked this:
Just for comparison here is a list from mine
I had a long session of removing the --not availables last week so it is
faily clean despite having been updated since mga1.
[root@localhost brian]# rpm -qa --nosignature --qf %{n}-%{v}-%{r}\n
| grep mga1 | sort
dvgrab-3.5-4.mga1
giftrans-1.12.2-23.mga1
jline-0.9.94-4.mga1
kmozillahelper-0.6.3-1.mga1
lib64atlas3-x86_64-3.8.3-7.mga1
lib64opencore-amr0-0.1.2-3.mga1
mpgtx-1.3.1-7.mga1
notification-daemon-engine-nodoka-0.1.0-3.mga1
transfugdrake-1.9.4-1.mga1
[root@localhost brian]# rpm -qa --nosignature --qf %{n}-%{v}-%{r}\n
| grep mga2 | sort
aoss-1.0.25-1.mga2
dcraw-9.12-1.mga2
hsqldb-1.8.1.3-5.mga2
jasper-1.900.1-13.mga2
lcms-1.19-6.mga2
lib64a52dec0-0.7.4-17.mga2
lib64alsa-oss0-1.0.25-1.mga2
lib64gsl0-1.15-1.mga2
lib64jasper1-1.900.1-13.mga2
lib64lcms1-1.19-6.mga2
lib64nut0-0.0.675-2.mga2
lib64nvtvsimple0-0.4.7-20.mga2
lib64vcd0-0.7.24-2.mga2
lib64wpg0.2_2-0.2.1-2.mga2
lib64xavs1-0.1.55-2.mga2
pdf2svg-0.2.1-1.mga2
postgresql-jdbc-9.0.801-1.mga2
vcdimager-0.7.24-2.mga2
x11-driver-input-1.0.0-17.mga2
xli-20061110-7.mga2
[root@localhost brian]# urpme --auto-orphans
No orphans to remove
[root@localhost brian]# urpmq --not-available
projectlibre-1.5.1-1.noarch
[root@localhost brian]#
Projectlibre excepted (which I have installed locally to try it out), theres
not too many.
So it looks like the rebuild bot did a pretty good job. :-)
Re: [Mageia-dev] Help needed: rpmlint checks not working
On Tue, Jan 15, 2013 at 6:21 PM, Thierry Vignaud thierry.vign...@gmail.com wrote: On 15 January 2013 19:17, Colin Guthrie mag...@colin.guthr.ie wrote: Will this affect mga2 builds too? It shouldn't there so hopefully there is no conflict :) Hmm, actually it probably applies to Mageia 2 builds too. I will try to change this. This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 Isn't that commit showing we didn't rejected some packages which should have been due to missing rules? Yes, we didn't reject some packages which should have been. Until this commit : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 But after this one we were rejecting too much on Mageia 2. Now it should be ok on Cauldron and Mageia 2. Well no. No as in it may be possible that some updates upload will break due to some error now being detected and rejected. Could we script a pass on all packages with that rpmlint config to catch any such packages and fix them? Well the first commit certainly applied to updates (and I queried as much), but I think the second commit means it only applies to cauldron, not any updates to mga2 etc. My point is we just added to _CAULDRON_ == mga3 a lot of rules that were missed, just after mass rebuild, and I fear that when we'll try to issue updates to _mga3_, we may see some being rejected, this is why I ask we check current cauldron with upload server rpmlint config... The options used to apply to all versions They were copied to cauldron specific rules and those ones removed from the default rules
Re: [Mageia-dev] proftpd - why was mdv package imported over ours nuking our changes???
Juan Luis Baptiste wrote: Hi, My mistake too, when Alfonso told me he was going to use the mdv's spec I didn't explicitly told him to merge back any change on mga spec (maybe for me this was something implicit to be done but now I see it isn't for everybody), and just checked his work on the update which was ok. I'll be more careful in the future when reviewing my apprentice's work, I'm sorry for the trouble caused by me and Alfonso. Just a heads up for the future, mgarepo sync had also not been run, so all of the old patches were still in SVN. Of course ideally, the patches that were just renamed rediffs would have been svn mv'd.
Re: [Mageia-dev] Freeze push: xterm
nicolas vigier wrote: On Mon, 14 Jan 2013, Damien Lallement wrote: Please push xterm 288. It's a bug fix release. http://www.spinics.net/lists/xorg/msg54908.html It doesn't look like a bugfix release. According to the release announcement on freecode, it is. http://freecode.com/projects/xterm/releases/351244 Also, some of the types of errors found by coverity scanners are possible security issues in general, so this would be good to have.
Re: [Mageia-dev] Freeze push: xterm
David Walser luigiwalser@... writes: On Mon, 14 Jan 2013, Damien Lallement wrote: Please push xterm 288. It's a bug fix release. http://www.spinics.net/lists/xorg/msg54908.html Tested locally on Cauldron, can confirm it works fine.
Re: [Mageia-dev] Freeze push: scribus
On 15.01.2013 15:06, Funda Wang wrote: Hello, Could scribus 1.4.2 be pushed? It features a hunspell based spellchecker, which obsoletes aspell checker. Thus, we could finally throw all aspell related pacakges in mga3, as planed. \o/ Regards. +1 for the push But, I would wait with removing Aspell from distro until Mageia 4. I should double check all packages, dependencies, ask for removal of perl Aspell related software and then patch hunspell-* to obsolete Aspell.
Re: [Mageia-dev] Help needed: rpmlint checks not working
Thierry Vignaud thierry.vign...@gmail.com writes: My point is we just added to _CAULDRON_ == mga3 a lot of rules that were missed, just after mass rebuild, and I fear that when we'll try to issue updates to _mga3_, we may see some being rejected, this is why I ask we check current cauldron with upload server rpmlint config... Right, we need to schedule a new mass rebuild, to check packages against the real rpmlint rules. -- Olivier Blin - blino
Re: [Mageia-dev] Help needed: rpmlint checks not working
nicolas vigier bo...@mars-attacks.org writes: The file distribution.error.list from rpmlint-mageia-policy is not used by the buildsystem to reject uploads. Instead it is using a list of rpmlint errors defined in youri configuration. I added them now : http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2928r2=2963 Maybe we could change it to use distribution.error.list file instead. [...] This should now be fixed. http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/youri/submit-upload.conf?r1=2963r2=2967 This is still an hardcoded list that does not reflect the default Mageia policy from rpmlint-mageia-policy, and this is quite a maintenance burden. Why don't we use rules from these packages directly? If needed, we could maybe have setup per-distro extraction of rpmlint policy on upload of the rpmlint-mageia-policy package. -- Olivier Blin - blino
[Mageia-dev] Freeze push: ibus, ibus-anthy
Hello,Could ibus and ibus-anthy be pushed into core/release? We target at 1.5.x for mga3, and we now have 1.4.9x beta versions.PS, you must remove corresponding packages from core/updates_testing before pushing them.Thanks.
[Mageia-dev] Freeze push: texstudio 2.5.2
Please push texstudio, which I updated to version 2.5.2. Upstream says that it is a bug fix release. -- Malo
[Mageia-dev] [NEED HELP] icewm titlebar missing on certain themes
Hello, We have a problem on icewm that the titlebar will be missing on some themes, including default theme: https://bugs.mageia.org/show_bug.cgi?id=8705 Note that arch user have same problem: https://bbs.archlinux.org/viewtopic.php?id=155162 As icewm is installed along with all Live-CD/DVDs as backup WM, we might need to find a solution for it: - figure out what's wrong in the icewm code and fix it. or - change to another default theme that won't be affected. or - use other light wm (e.g. openbox) for our Live-CD/DVDs Any suggestion is welcomed, Thanks, You-Cheng Hsieh
Re: [Mageia-dev] [NEED HELP] icewm titlebar missing on certain themes
You-Cheng Hsieh wrote: Hello, We have a problem on icewm that the titlebar will be missing on some themes, including default theme: https://bugs.mageia.org/show_bug.cgi?id=8705 Note that arch user have same problem: https://bbs.archlinux.org/viewtopic.php?id=155162 As icewm is installed along with all Live-CD/DVDs as backup WM, we might need to find a solution for it: - figure out what's wrong in the icewm code and fix it. or - change to another default theme that won't be affected. or - use other light wm (e.g. openbox) for our Live-CD/DVDs We shouldn't switch to another light wm when we can just change the theme, but it would be nice if we could find the cause for this, as nothing has changed in the icewm or default theme packages since Mageia 2, which didn't have this issue, so the source of the issue is likely elsewhere, and who knows what else it could affect at some point. What a strange bug :O
