Re: [Mageia-dev] Bug 4560: WQY fonts
2013/1/27 Joseph Wang joequ...@gmail.com: I just uploaded the missing WQY (zenhei, unibit, bitmap) fonts to the repository. No personal opinion as to whether or not they should go into Mageia 3 or not, but they are there if needed. Hello, Before you import a new package, please search if we already have same one in repo: http://svnweb.mageia.org/packages/cauldron/x11-font-wqy-bitmapfont/ Thanks, You-Cheng Hsieh
Re: [Mageia-dev] [soft-commits] [7213] Check-in debuginfo-install
On 26.01.2013 23:14, Pascal Terjan wrote:
You can run urpmq only once with all the args but as the packages are
installed, I would just use rpmquery
urpmi $(rpmquery --qf %{SOURCERPM}\n $@ | sed 's/-[^-]*-[^-]*$/-debuginfo/')
That should make things faster :)
Yes, this works quicker.
I have pinged the following bug thread and marked it as a
release-blocker https://bugs.mageia.org/show_bug.cgi?id=8555
Regards,
Re: [Mageia-dev] Bug 4560: WQY fonts
'Twas brillig, and You-Cheng Hsieh at 27/01/13 09:28 did gyre and gimble: 2013/1/27 Joseph Wang joequ...@gmail.com: I just uploaded the missing WQY (zenhei, unibit, bitmap) fonts to the repository. No personal opinion as to whether or not they should go into Mageia 3 or not, but they are there if needed. Hello, Before you import a new package, please search if we already have same one in repo: http://svnweb.mageia.org/packages/cauldron/x11-font-wqy-bitmapfont/ As it's already present, can you (Joseph) make sure svn (and any packages submitted if any) is tidied up (svn rm the appropriate package) Cheers 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] Freeze Push: bootsplash
This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. 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] Freeze Push: bootsplash
Colin Guthrie skrev 27.1.2013 12:23: This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. Col Submitted. -- thomas
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On 20/01/13 17:42, Maurice Batey wrote:
On Sun, 20 Jan 2013 14:50:06 +, Barry Jackson wrote:
I repeat - Installing the grub2 package
OK - so you differentiate between installing with GRUB2 and
installing the GRUB2 packge?
I am differentiating between # urpmi grub2 and the use of the
grub2-install command.
Does the former include the latter?
Or do you mean one can install with GRUB Legacy and then go on to
install the GRUB2 *package* (which presumably doesn't do anything but
make itself available for the purposes you described)?
Exactly, except that it does create a menu and builds it's kernel
(core.img) which it places in the /boot/grub2 directory ready for use.
It does no more than this and does not affect the existing MBR or PBR in
any way.
This automatically creates core.img in /boot/grub2/i386-pc/ which
allows
you to boot into it from either grub2 using the multiboot command or from
legacy, using the menu entry shown in the readme.
What/where is the 'multiboot command'?
multiboot is a grub2 command to boot using core.img directly.
Below is my entry for Mga3 in my master grub2 grub.cfg which is in a
small grub partition at the start of sda. My MBR points to this
partition, so all OS's are either chainloaded or multibooted from the
manually created entries in this grub.cfg
menuentry 'Mageia-3' {
search --no-floppy --label --set=root mageia-3
multiboot /boot/grub2/i386-pc/core.img
My limited understanding is that it is similar to chainloading but does
not need embedded code in the PBR. Since grub2 can read the filesystem
(with the appropriate modules loaded) it can navigate to the location of
core.img and launch it.
A useful side effect is that grub legacy may be installed to the PBR and
used if required, using:-
menuentry 'Mageia-3 {
search --no-floppy --label --set=root mageia-3
chainloader +1
}
Did you test it in Mageia as described in the README.Mageia ?
The GRUB2 I tried was from Ubuntu 12.01 and Mint 13, not Mageia.
If you add Mageia (grub2) entry to menu.lst as described and boot into
the Grub2 menu it will have all your legacy systems listed. Do they
not boot? .
Good question. The GRUB2-to-Grub Legacy' boots I attempted via GRUB2
in the MBR all failed.
Next time I get the netbook out I will try booting a GRUB Legacy
install via a GRUB Legacy boot menu entry for booting a GRUB2 install.
(Remember, it has GRUB Legacy in the MBR.)
Yes that's fine
But I expect the result to be the same as booting GRUB legacy from
GRUB2 in the MBR.
:\
If the failure to boot was caused by a faulty GRUB2 component, as has
been suggested, then the test will have to await my installing Mageia-3
with GRUB2, which may not happen very soon.
Have fun ;)
Barry
Re: [Mageia-dev] [council] *ping* Media query: secure boot support
Maybe our developers can answer your question? On 27/01/13 13:31, Trish Fraser wrote: Ping? Begin forwarded message: Date: Sat, 26 Jan 2013 18:48:37 +1100 From: Trish Frasertr...@thefrasers.org To: councilcoun...@ml.mageia.org Subject: [council] Fw: Media query: secure boot support Hi all, Do we have a position on secure boot? NB: Sam has been known to write very scathing articles, so I'd like to respond to him asap. Cheers, Begin forwarded message: Date: Sat, 26 Jan 2013 17:24:26 +1100 From: Sam Vargheses...@gnubies.com To: pr...@mageia.org Subject: Media query: secure boot support G'day I am writing to you on behalf of iTWire, an Australian technology news website. I would like to know what Mageia plans to do about secure boot - when you will have a release that supports booting on hardware on which this feature is enabled. A word in response would be appreciated. Thanks, Sam - (Sam Varghese) FOSS editor iTWire http://www.itwire.com Phone: 0404 489 353 International: +61 404 489 353 My personal blog: http://wildcard.gnubies.com H
[Mageia-dev] Freeze push: gtksourceview 3.6.3
Bugfix release. -- Regards, Olav ---BeginMessage--- About gtksourceview === Source code editing widget News * Fixed classic, tango and kate themes. ChangeLog = http://download.gnome.org/sources/gtksourceview/3.6/gtksourceview-3.6.3.changes (753) Download http://download.gnome.org/sources/gtksourceview/3.6/gtksourceview-3.6.3.tar.xz (1.16M) sha256sum: bb1e016779cf19e3a67d04b1067e8de24d8db6493abf7a43a284850e5ded ___ ftp-release-list mailing list ftp-release-l...@gnome.org https://mail.gnome.org/mailman/listinfo/ftp-release-list ---End Message---
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release python-distribute-0.6.34-3.mga3
On Thu, Jan 24, 2013 at 11:59 AM, Pascal Terjan pter...@gmail.com wrote: On Thu, Jan 24, 2013 at 10:37 AM, Sander Lepik sander.le...@eesti.ee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 12:28, Pascal Terjan kirjutas: On Thu, Jan 24, 2013 at 3:22 AM, Thomas Spuhler tho...@btspuhler.com wrote: I eliminated the package python-pkg-resources and put the two+ files into the basic package python- distribute. The reason is as stated below: Hey! I can see you have imported python-distribute that generates package python-pkg-resources. And now the problem: http://pkgsubmit.mageia.org/uploads/rejected/cauldron/core/release/20130113212011.umeabot.valstar.22055.youri - - python-setuptools generates package with same name. I think you should rename yours to python-pkg-resources-distribute or something like that. The problem is that python-distribute should have then been uploaded just after. python-pkg-resources got cleaned from the mirrors because it was a leftover package built from a src.rpm which no longer existed, and the one from python-distribute had not been uploaded. Not python-distribute but python-setuptools. They both had python-pkg-resources as sub-package. And as python-distribute has bigger version its subpackage was uploaded. That package should come from python-setuptools as it was before Thomas imported python-distribute. Yes sorry, mixed them :) But now we need to fix the problem: python-setuptools can not be uploaded while this package is still here (as the version is lower) or if the package is removed (as chroot creation will fail). I think I will force the upload of python-setuptools BS should be fixed now, tell me if any pbs. Regards, D.
Re: [Mageia-dev] Bug 4560: WQY fonts
I removed fonts-wqy-bitmap and fonts-wqy-unibit from the repository. I added x11-font-wqy-unibit which has the wqy unibit fonts, and I got it to work with the same conventions as x11-font-wqy-bitmapfont
Re: [Mageia-dev] Feedback on Mageia 3 beta1
On Sat, 26 Jan 2013 23:16:26 +, Barry Jackson wrote: I still think that's how it will turn out ;) Hope you're right! :-)) -- /\/\aurice
Re: [Mageia-dev] Grub2 vs. Grub Legacy in M3
On Sun, 27 Jan 2013 12:31:37 +, Barry Jackson wrote: my master grub2 grub.cfg which is in a small grub partition at the start of sda. How does one acquire a 'small grub partition'? (Just get GRUB2 package to install into an empty partition?) My MBR points to this partition, so all OS's are either chainloaded or multibooted from the manually created entries in this grub.cfg Which do you have in the MBR: GRUB2 or Legacy? My limited understanding is that it is similar to chainloading but does not need embedded code in the PBR. Ah,now that's interesting! (I assume you mean 'does not need GRUB2 installed in the PBR') A useful side effect is that grub legacy may be installed to the PBR and used if required, I assume you mean the PBR of the 'small grub partition'. Mamy thanks, Barry, especially w.r.t to the 'bootloader' partition! -- /\/\aurice
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release python-distribute-0.6.34-3.mga3
On Sunday, January 27, 2013 06:11:35 AM D.Morgan wrote: On Thu, Jan 24, 2013 at 11:59 AM, Pascal Terjan pter...@gmail.com wrote: On Thu, Jan 24, 2013 at 10:37 AM, Sander Lepik sander.le...@eesti.ee wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 24.01.2013 12:28, Pascal Terjan kirjutas: On Thu, Jan 24, 2013 at 3:22 AM, Thomas Spuhler tho...@btspuhler.com wrote: I eliminated the package python-pkg-resources and put the two+ files into the basic package python- distribute. The reason is as stated below: Hey! I can see you have imported python-distribute that generates package python-pkg-resources. And now the problem: http://pkgsubmit.mageia.org/uploads/rejected/cauldron/core/release/201 30113212011.umeabot.valstar.22055.youri - - python-setuptools generates package with same name. I think you should rename yours to python-pkg-resources-distribute or something like that. The problem is that python-distribute should have then been uploaded just after. python-pkg-resources got cleaned from the mirrors because it was a leftover package built from a src.rpm which no longer existed, and the one from python-distribute had not been uploaded. Not python-distribute but python-setuptools. They both had python-pkg-resources as sub-package. And as python-distribute has bigger version its subpackage was uploaded. That package should come from python-setuptools as it was before Thomas imported python-distribute. Yes sorry, mixed them :) But now we need to fix the problem: python-setuptools can not be uploaded while this package is still here (as the version is lower) or if the package is removed (as chroot creation will fail). I think I will force the upload of python-setuptools BS should be fixed now, tell me if any pbs. Regards, D. Thanks a lot. I apologize for screwing up. -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
On 24 January 2013 00:44, alien buildsystem-dae...@mageia.org wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for?
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
Op zondag 27 januari 2013 17:05:20 schreef Thierry Vignaud: On 24 January 2013 00:44, alien buildsystem-dae...@mageia.org wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... i donno how to fix this properly. what should i do with revision logs?
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs?
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
On Sun, Jan 27, 2013 at 4:50 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org If you just rebuild it without fixing anything, it will come back next time...
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
On Sun, Jan 27, 2013 at 5:05 PM, Pascal Terjan pter...@gmail.com wrote: On Sun, Jan 27, 2013 at 4:50 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org If you just rebuild it without fixing anything, it will come back next time... Looking at the failure logs: gcc -fPIC -Wall -O3 -Wno-unused-function -shared -o hd44780.so hd44780-hd44780.o libLCD.a hd44780-hd44780-serial.o hd44780-hd44780-lis2.o hd44780-hd44780-usblcd.o hd44780-hd44780-4bit.o hd44780-hd44780-ext8bit.o hd44780-lcd_sem.o hd44780-hd44780-winamp.o hd44780-hd44780-serialLpt.o hd44780-hd44780-bwct-usb.o hd44780-hd44780-lcd2usb.o hd44780-hd44780-uss720.o hd44780-hd44780-usbtiny.o hd44780-hd44780-usb4all.o hd44780-hd44780-ftdi.o hd44780-hd44780-ethlcd.o hd44780-hd44780-i2c.o -lusb -lftdi -lusb libbignum.a -ldl gcc: error: libbignum.a: No such file or directory make[3]: *** [hd44780.so] Error 1 make[3]: Leaving directory `/home/pterjan/rpmbuild/BUILD/lcdproc-0.5.6/server/drivers' So in the Makefile in server/drivers, hd44780.so needs to depend on libbignum.a
Re: [Mageia-dev] nepomukextras / nepomukannotation / kolena
Le dimanche 27 janvier 2013 16:58:01 Pascal Terjan a écrit : I was looking at the packages that have not been built since Magea 1 nepomukextras is one of them, required only by nepomukannotation that nothing requires, they haven't been updated upstream for 2 years They both can't be built because they need libkolena0 which is not installable (requires an old libtesseract_api) and they are the only think using kolena kolena doesn't build: -- Could NOT find KDE4Workspace (missing: KDE4Workspace_CONFIG) -- Could NOT find Tesseract (missing: TESSERACT_LIBRARY) -- Could NOT find TIFF (missing: TIFF_LIBRARY TIFF_INCLUDE_DIR) Should we drop them all? i will take a look
Re: [Mageia-dev] nepomukextras / nepomukannotation / kolena
Le dimanche 27 janvier 2013 16:58:01 Pascal Terjan a écrit : I was looking at the packages that have not been built since Magea 1 nepomukextras is one of them, required only by nepomukannotation that nothing requires, they haven't been updated upstream for 2 years They both can't be built because they need libkolena0 which is not installable (requires an old libtesseract_api) and they are the only think using kolena kolena doesn't build: -- Could NOT find KDE4Workspace (missing: KDE4Workspace_CONFIG) -- Could NOT find Tesseract (missing: TESSERACT_LIBRARY) -- Could NOT find TIFF (missing: TIFF_LIBRARY TIFF_INCLUDE_DIR) Should we drop them all? please remove them if you can
Re: [Mageia-dev] nepomukextras / nepomukannotation / kolena
On Sun, Jan 27, 2013 at 5:30 PM, Nicolas Lécureuil nicolas.lecure...@free.fr wrote: Le dimanche 27 janvier 2013 16:58:01 Pascal Terjan a écrit : I was looking at the packages that have not been built since Magea 1 nepomukextras is one of them, required only by nepomukannotation that nothing requires, they haven't been updated upstream for 2 years They both can't be built because they need libkolena0 which is not installable (requires an old libtesseract_api) and they are the only think using kolena kolena doesn't build: -- Could NOT find KDE4Workspace (missing: KDE4Workspace_CONFIG) -- Could NOT find Tesseract (missing: TESSERACT_LIBRARY) -- Could NOT find TIFF (missing: TIFF_LIBRARY TIFF_INCLUDE_DIR) Should we drop them all? please remove them if you can OK I will, thanks
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
Op zondag 27 januari 2013 17:18:01 schreef Pascal Terjan: On Sun, Jan 27, 2013 at 5:05 PM, Pascal Terjan pter...@gmail.com wrote: On Sun, Jan 27, 2013 at 4:50 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org If you just rebuild it without fixing anything, it will come back next time... Looking at the failure logs: gcc -fPIC -Wall -O3 -Wno-unused-function -shared -o hd44780.so hd44780-hd44780.o libLCD.a hd44780-hd44780-serial.o hd44780-hd44780-lis2.o hd44780-hd44780-usblcd.o hd44780-hd44780-4bit.o hd44780-hd44780-ext8bit.o hd44780-lcd_sem.o hd44780-hd44780-winamp.o hd44780-hd44780-serialLpt.o hd44780-hd44780-bwct-usb.o hd44780-hd44780-lcd2usb.o hd44780-hd44780-uss720.o hd44780-hd44780-usbtiny.o hd44780-hd44780-usb4all.o hd44780-hd44780-ftdi.o hd44780-hd44780-ethlcd.o hd44780-hd44780-i2c.o -lusb -lftdi -lusb libbignum.a -ldl gcc: error: libbignum.a: No such file or directory make[3]: *** [hd44780.so] Error 1 make[3]: Leaving directory `/home/pterjan/rpmbuild/BUILD/lcdproc-0.5.6/server/drivers' So in the Makefile in server/drivers, hd44780.so needs to depend on libbignum.a hd44780_LDADD = libLCD.a @HD44780_DRIVERS@ @LIBUSB_LIBS@ @LIBFTDI_LIBS@ libbignum.a hd44780_DEPENDENCIES = @HD44780_DRIVERS@ so, i should move it to dependencies instead of ldadd in the Makefile.am and use autoreconf -i instead... but... this isn't the only driver, does this mean i'll have to change dependencies for almost all these drivers? /me sighs
Re: [Mageia-dev] Freeze Push: bootsplash
Colin Guthrie wrote: This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. Care to elaborate? Mageia 2 also has 3.3.9.
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
On Sun, Jan 27, 2013 at 7:14 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:18:01 schreef Pascal Terjan: On Sun, Jan 27, 2013 at 5:05 PM, Pascal Terjan pter...@gmail.com wrote: On Sun, Jan 27, 2013 at 4:50 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org If you just rebuild it without fixing anything, it will come back next time... Looking at the failure logs: gcc -fPIC -Wall -O3 -Wno-unused-function -shared -o hd44780.so hd44780-hd44780.o libLCD.a hd44780-hd44780-serial.o hd44780-hd44780-lis2.o hd44780-hd44780-usblcd.o hd44780-hd44780-4bit.o hd44780-hd44780-ext8bit.o hd44780-lcd_sem.o hd44780-hd44780-winamp.o hd44780-hd44780-serialLpt.o hd44780-hd44780-bwct-usb.o hd44780-hd44780-lcd2usb.o hd44780-hd44780-uss720.o hd44780-hd44780-usbtiny.o hd44780-hd44780-usb4all.o hd44780-hd44780-ftdi.o hd44780-hd44780-ethlcd.o hd44780-hd44780-i2c.o -lusb -lftdi -lusb libbignum.a -ldl gcc: error: libbignum.a: No such file or directory make[3]: *** [hd44780.so] Error 1 make[3]: Leaving directory `/home/pterjan/rpmbuild/BUILD/lcdproc-0.5.6/server/drivers' So in the Makefile in server/drivers, hd44780.so needs to depend on libbignum.a hd44780_LDADD = libLCD.a @HD44780_DRIVERS@ @LIBUSB_LIBS@ @LIBFTDI_LIBS@ libbignum.a hd44780_DEPENDENCIES = @HD44780_DRIVERS@ so, i should move it to dependencies instead of ldadd in the Makefile.am and use autoreconf -i instead... but... this isn't the only driver, does this mean i'll have to change dependencies for almost all these drivers? I don't know if they use the lib :)
[Mageia-dev] Freeze push: zim-0.59
Please push Zim 0.59. This release fixes a critical bug in the editor widget that can lead to loss of content for specific combinations of formatting. In addition, week numbers in Journal pages are fixed and Tasklist tag inheritance is improved. (from http://freecode.com/projects/zim) Thanks! Dimitri
[Mageia-dev] Freeze push: fetchyahoo-2.14.9
Hi, Can someone push fetchyahoo? It fixes #8374: https://bugs.mageia.org/show_bug.cgi?id=8374 Thanks :) signature.asc Description: OpenPGP digital signature
[Mageia-dev] Freeze push: gmp 5.1.0
Please push GNU MP 5.1.0. It's bugfix and speedup release, source and binary compatible with 5.0 series: http://gmplib.org/gmp5.1.html Thanks! Dimitri
Re: [Mageia-dev] [changelog] [RPM] cauldron core/release lcdproc-0.5.6-6.mga3
Op zondag 27 januari 2013 20:45:20 schreef Pascal Terjan: On Sun, Jan 27, 2013 at 7:14 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:18:01 schreef Pascal Terjan: On Sun, Jan 27, 2013 at 5:05 PM, Pascal Terjan pter...@gmail.com wrote: On Sun, Jan 27, 2013 at 4:50 PM, AL13N al...@rmail.be wrote: Op zondag 27 januari 2013 17:43:50 schreef Thierry Vignaud: On 27 January 2013 17:32, AL13N al...@rmail.be wrote: alien alien 0.5.6-6.mga3: + Revision: 391755 + rebuild (emptylog) what for? autobuild failed that release, but for some reason i had to bump release anyway... rebuild did succeeded: * Sat Jan 12 2013 umeabot umeabot 0.5.6-2.mga3 + Revision: 356696 - Mass Rebuild - https://wiki.mageia.org/en/Feature:Mageia3MassRebuild and it was rebuild again later. You should have stopped when seeing you'd to bump release as that mean that previous build was successful.. i donno how to fix this properly. what should i do with revision logs? not the mass rebuild, but on of the autobuilds kept showing lcdproc as failed. i had to rebuild it for it to show up properly. it meant i had a personal entry on check.mageia.org If you just rebuild it without fixing anything, it will come back next time... Looking at the failure logs: gcc -fPIC -Wall -O3 -Wno-unused-function -shared -o hd44780.so hd44780-hd44780.o libLCD.a hd44780-hd44780-serial.o hd44780-hd44780-lis2.o hd44780-hd44780-usblcd.o hd44780-hd44780-4bit.o hd44780-hd44780-ext8bit.o hd44780-lcd_sem.o hd44780-hd44780-winamp.o hd44780-hd44780-serialLpt.o hd44780-hd44780-bwct-usb.o hd44780-hd44780-lcd2usb.o hd44780-hd44780-uss720.o hd44780-hd44780-usbtiny.o hd44780-hd44780-usb4all.o hd44780-hd44780-ftdi.o hd44780-hd44780-ethlcd.o hd44780-hd44780-i2c.o -lusb -lftdi -lusb libbignum.a -ldl gcc: error: libbignum.a: No such file or directory make[3]: *** [hd44780.so] Error 1 make[3]: Leaving directory `/home/pterjan/rpmbuild/BUILD/lcdproc-0.5.6/server/drivers' So in the Makefile in server/drivers, hd44780.so needs to depend on libbignum.a hd44780_LDADD = libLCD.a @HD44780_DRIVERS@ @LIBUSB_LIBS@ @LIBFTDI_LIBS@ libbignum.a hd44780_DEPENDENCIES = @HD44780_DRIVERS@ so, i should move it to dependencies instead of ldadd in the Makefile.am and use autoreconf -i instead... but... this isn't the only driver, does this mean i'll have to change dependencies for almost all these drivers? I don't know if they use the lib :) there are at 20ish or more of them that have that exact library in their respective ldadd... i was hoping to have a easier way to make that library built before these drivers...
Re: [Mageia-dev] /run/httpd (maybe others) breaking features
Le 24/01/2013 08:50, Sander Lepik a écrit : Fedora uses d /run/httpd 710 root apache which doesn't help in this case but fixes other problems Why can't we use d /run/httpd 710 apache apache. It's quite possible that apache is trying to create this file as apache not as root. And with current permissions only root can write into that directory. Switching from root to apache user may be eventually needed, but I don't see the point of using any other perm scheme as 755. -- BOFH excuse #186: permission denied
Re: [Mageia-dev] Freeze Push: bootsplash
'Twas brillig, and David Walser at 27/01/13 20:26 did gyre and gimble: Colin Guthrie wrote: This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. Care to elaborate? Mageia 2 also has 3.3.9. I already sent a mail to security@ (as per https://wiki.mageia.org/en/Packagers_Security_Team) to discuss it initially. I've updated the mga2 package in preparation already, but just wanted to discuss the process (i.e. order of certain actions) first. 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] Freeze push: owncloud
hi, please let go owncloud, it fixes securities issues. Security: Fix multiple XSS problems: CVE-2013-0201, CVE-2013-0202, CVE-2013-0203[1] Security: Fix Code execution in external storage: CVE-2013-0204[2] Security: Auth bypass in user_webdavauth and user_ldap (oC-SA-2012-006[3]) Security: XSS vulnerability in bookmarks (oC-SA-2012-007[4]) XSS vulnerability in user_webdavauth (oC-SA-2012-003[5]) Code Execution in /lib/migrate.php (oC-SA-2012-004[6]) Code Execution in /lib/filesystem.php (oC-SA-2012-005[7]) [1] http://owncloud.org/about/security/advisories/oC-SA-2013-001/ [2] http://owncloud.org/about/security/advisories/oc-sa-2013-002/ [3] http://owncloud.org/about/security/advisories/oc-sa-2012-006/ [4] http://owncloud.org/about/security/advisories/oc-sa-2012-007/ [5] http://owncloud.org/about/security/advisories/oc-sa-2012-003/ [6] http://owncloud.org/about/security/advisories/oc-sa-2012-004/ [7] http://owncloud.org/about/security/advisories/oc-sa-2012-005/
Re: [Mageia-dev] Freeze push: owncloud
Le 28/01/2013 00:11, Nicolas Lécureuil a écrit : hi, please let go owncloud, it fixes securities issues. done Security: Fix multiple XSS problems: CVE-2013-0201, CVE-2013-0202, CVE-2013-0203 http://owncloud.org/about/security/advisories/oC-SA-2013-001/ Security: Fix Code execution in external storage: CVE-2013-0204 http://owncloud.org/about/security/advisories/oc-sa-2013-002/ Security: Auth bypass in user_webdavauth and user_ldap (oC-SA-2012-006 http://owncloud.org/about/security/advisories/oc-sa-2012-006/) Security: XSS vulnerability in bookmarks (oC-SA-2012-007 http://owncloud.org/about/security/advisories/oc-sa-2012-007/) XSS vulnerability in user_webdavauth (oC-SA-2012-003 http://owncloud.org/about/security/advisories/oc-sa-2012-003/) Code Execution in /lib/migrate.php (oC-SA-2012-004 http://owncloud.org/about/security/advisories/oc-sa-2012-004/) Code Execution in /lib/filesystem.php (oC-SA-2012-005 http://owncloud.org/about/security/advisories/oc-sa-2012-005/) -- Anne http://mageia.org
Re: [Mageia-dev] Freeze Push: bootsplash
Colin Guthrie wrote: 'Twas brillig, and David Walser at 27/01/13 20:26 did gyre and gimble: Colin Guthrie wrote: This is one of our packages thus semi-exempt from freeze rules. But either way it fixes a potential security issue. Care to elaborate? Mageia 2 also has 3.3.9. I already sent a mail to security@ (as per https://wiki.mageia.org/en/Packagers_Security_Team) to discuss it initially. I've updated the mga2 package in preparation already, but just wanted to discuss the process (i.e. order of certain actions) first. Does anyone get the mails sent to that list?
Re: [Mageia-dev] [changelog] cauldron core/release task-obsolete-3-56.mga3
zezinho wrote: Name: task-obsoleteRelocations: (not relocatable) Version : 3 Vendor: Mageia.Org Release : 56.mga3 Build Date: Sun Jan 27 12:28:18 2013 zezinho zezinho 3-56.mga3: + Revision: 392711 - zsnes removed Why!?? I don't want this removed from my system!
Re: [Mageia-dev] Freeze push: libchewing scim-chewing
2013/1/24 You-Cheng Hsieh yochenhs...@gmail.com: Hello, libchewing scim-chewing dev (quietly) released new versions near the end of last year, and I missed both of them before version freeze.:( For libchewing, 0.3.4 includes more fixes than new features and I highly suggest we should push it for Mageia 3 release: https://github.com/chewing/libchewing/blob/master/NEWS For scim-chewing 0.3.5, only minor changes have been made and scim is still not usable in Cauldron now(?). If you worry about stability issue, this one can be skipped. But I still think it should be OK, though. https://github.com/chewing/scim-chewing/blob/master/NEWS Both of them can be built successfully in my Cauldron VM and I've commit them to svn. Please help submit them. Thanks, You-Cheng Hsieh ping?
Re: [Mageia-dev] Peazip
On 01/27/2013 05:56 PM, Joseph Wang wrote: I got it to compile on my 64-bit machine. It required some code changes which I reported upstream http://code.google.com/p/peazip/issues/detail?id=205 BIG THANK YOU, we've been waiting for too long, thank you very much. I haven't checked in the changes yet because I need to figure out what files need to get installed where to get a working system. It works fine when I run it in the build directory, but it fails when I move outside that directory.
Re: [Mageia-dev] Peazip
On 01/27/2013 06:57 PM, Joseph Wang wrote: I just uploaded to mgarepo a package that fixes peazip. It runs nicely on my 64-bit machine now, I assume that there isn't a problem in uploading since it's not scheduled for Mageia3 and the package that was there before was broken anyway. How can I test it? Now to take a look at mplayer2.
Re: [Mageia-dev] freeze push: libroffice
On Mon, 2013-01-28 at 06:37 +0100, Thierry Vignaud wrote: Hi Please let in freeze push: libroffice-4.0.0.2 This is RC2, we have RC1. When to stop? It's not a difference here between a release candidate and a release... -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/ Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Re: [Mageia-dev] freeze push: libroffice
Le lundi 28 janvier 2013 00:40:53 Liam R E Quin a écrit : On Mon, 2013-01-28 at 06:37 +0100, Thierry Vignaud wrote: Hi Please let in freeze push: libroffice-4.0.0.2 This is RC2, we have RC1. When to stop? It's not a difference here between a release candidate and a release... i don't understand what you mean. I don't think we should release a rc release in mga3 either.
Re: [Mageia-dev] freeze push: libroffice
Le lundi 28 janvier 2013 00:40:53 Liam R E Quin a écrit : On Mon, 2013-01-28 at 06:37 +0100, Thierry Vignaud wrote: Hi Please let in freeze push: libroffice-4.0.0.2 This is RC2, we have RC1. When to stop? It's not a difference here between a release candidate and a release... in the same way we should keep kde 4.10 rc3 ? :) ( joke )
Re: [Mageia-dev] [changelog] cauldron core/release task-obsolete-3-56.mga3
Le 28/01/2013 00:53, David Walser a écrit : zezinho wrote: Name: task-obsoleteRelocations: (not relocatable) Version : 3 Vendor: Mageia.Org Release : 56.mga3 Build Date: Sun Jan 27 12:28:18 2013 zezinhozezinho 3-56.mga3: + Revision: 392711 - zsnes removed Why!?? I don't want this removed from my system! AFAIK, our policy is to obsolete any package that is no more in the distro. You can still install the MGA2 rpm if you remove task-obsolete...
