- Arch-dev-public - lists.archlinux.org

[arch-dev-public] archboot 2010.07 torrent file, need to be added to archlinux tracker
by Tobias Powalowski 23 Jul '10

23 Jul '10

Hi guys, just created a torrent file of latest archboot release. Can someone with enough rights please add it? filename: archlinux-2010.07-1-archboot.iso.torrent HASH: 88EEA267 4A8A6B73 72BFE004 7E52B7E3 B80BC335 Thanks in advance greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

3 4

[arch-dev-public] gcc 4.5 bug - what to do?
by Firmicus 23 Jul '10

23 Jul '10

Hi guys, Yesterday I had bug report on a segfaulting binary for x86_64 that ships with texlive-bin in testing: http://bugs.archlinux.org/task/20199 I have reported the bug upstream: https://sourceforge.net/tracker/?func=detail&aid=3031498&group_id=145640&at… and as suspected it turned out to be a bug with gcc 4.5: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45008 Now this means I have no means to include a working binary of dvisvgm for x86_64 in texlive-bin until that bug is resolved, since I cannot rely on gcc 4.4.x and no patch is available... What is the procedure you guys follow is such situations? F

5 14

Re: [arch-dev-public] Moving some stuff in for ardour
by Ray Rashif 21 Jul '10

21 Jul '10

On 22 July 2010 06:22, Ray Rashif <schivmeister(a)gmail.com> wrote: > SLV2 and Rubberband are two important but can-do-without dependencies; > the former enabling a particular plug-in subsystem ("LV2"), the latter > replacing an already-existing dependency on SoundTouch because "it can > do more". The reason why I see a reason for this prior notification is > because they bring in two other packages as deps (totalling to four > new packages in extra solely for ardour at this point of time) and > there are no tasks filed for them: > > lv2core - dep of slv2, independent successor to ladspa (upstream > doesn't like to name it simply "lv2" because of certain > technicalities) > vamp-plugin-sdk - dep of rubberband, API stuff > > These are pretty OK software, i.e they rarely break and are safe to > have in the repos. In case it wasn't apparent, they will be moved from > community. If there are no objections, I'll go ahead. Ah crap, this was meant for -public so here's a re-send. Sorry for the traffic jam. -- GPG/PGP ID: B42DDCAD

1 0

Re: [arch-dev-public] Fwd: gcc 4.5 bug - what to do?
by Firmicus 21 Jul '10

21 Jul '10

On 20/07/2010 23:44, Rémy Oudompheng wrote: > ---------- Forwarded message ---------- > From: Rémy Oudompheng<oudomphe(a)phare.normalesup.org> > Date: 2010/7/20 > Subject: Re: [arch-dev-public] gcc 4.5 bug - what to do? > To: Public mailing list for Arch Linux development > <arch-dev-public(a)archlinux.org> > > > On 2010/7/20, Firmicus<Firmicus(a)gmx.net> wrote: >> Hi guys, >> >> Yesterday I had bug report on a segfaulting binary for x86_64 that ships >> with texlive-bin in testing: >> http://bugs.archlinux.org/task/20199 >> I have reported the bug upstream: >> https://sourceforge.net/tracker/?func=detail&aid=3031498&group_id=145640&at… >> and as suspected it turned out to be a bug with gcc 4.5: >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45008 >> >> Now this means I have no means to include a working binary of dvisvgm for >> x86_64 in texlive-bin until that bug is resolved, since I cannot rely on gcc >> 4.4.x and no patch is available... > Can't we use the random patch I posted as a follow-up to the bug > report (until GCC gets fixed...) ? Ah thanks, I'll look at it. (I had not noticed your patch when I wrote the above). But even if it works I'd prefer to ask the dev of dvisvgm first for his expert opinion on this patch. I've already asked him actually. > Another solution would be to use > clang++ ;) Given the complexity and the integrated nature of the texlive build environment, that would probably be hard to achieve locally. A cleaner approach would be to (temporarily) package dvisvgm separately and disable it in the texlive-bin configuration. I'll contact you offlist on this if this becomes a necessity ;) Rémy, thanks for the patch btw ;) F

1 0

[arch-dev-public] [signoff] autoconf-2.66-2 and pkg-config-0.25-2
by Allan McRae 19 Jul '10

19 Jul '10

autoconf-2.66-2 -> patched to fix regressions in 2.66 pkg-config-0.25-2 -> patched to fix issue exposed by autoconf-2.66 Should fix all issues we have seen with the autoconf 2.66 update. Allan

3 3

[arch-dev-public] [signoff] libgcrypt 1.4.6-1
by Andreas Radke 19 Jul '10

19 Jul '10

new upstream release. please signoff. http://lists.gnupg.org/pipermail/gnupg-announce/2010q3/000300.html -Andy

3 3

[arch-dev-public] Anyone using lilo?
by Eric Bélanger 18 Jul '10

18 Jul '10

Hi, Roman has flagged my lilo packages. Lilo developpement is now active and lilo 23.0 was released. Unfortunately, my only system using lilo is no longer working. Is there anyone else using lilo? Ideally, it would be a dev who would take over the package or, at least, a user willing to work with me in testing the new packgae before it hits the testing repo. Thanks, Eric

4 5

[arch-dev-public] Please lock this thread on forum
by Tobias Powalowski 17 Jul '10

17 Jul '10

Hi guys, i need a forum moderator, http://bbs.archlinux.org/viewtopic.php?id=97527 thx greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 2

[arch-dev-public] bbs.archlinux.org is now switched to https only!
by Thomas Bächler 16 Jul '10

16 Jul '10

I just performed the switch to https only on bbs! I also adjusted some internal URLs, so all files will be properly fetched via https directly. http is redirected automatically. Note that the navbar links on Archweb and all other sites still point to http, but that is redirected automatically. There is a catch: 1) Apache configures SSL per-vhost. That means that even though we have a wildcard certificate, the browser must support SNI for name-based vhosts to work. All clients that are not SNI-capable will be redirected to www instead. 2) wget doesn't like wildcard certificates. That means you need to use --no-check-certificate with wget. 3) Our certificate is from CACert. AFAIK, this is not included in many browsers by default. If you use Arch Linux, at least everything that uses the OpenSSL certificate store and all Mozilla browsers are CACert-enabled - on other operating systems, our certificate might show up as untrusted. Let me know if any of the above (especially 1) cause any problems.

3 4

[arch-dev-public] [signoff] autoconf-2.66-1
by Allan McRae 14 Jul '10

14 Jul '10

Upstream update. Mainly bug fixes for regressions introduced in the last couple of releases. Signoff any, Allan

2 4