Guys,
For those that rely on OpenOffice, and for those that prepare the
packages,
it's official, OpenOffice forked as of Sept. 28, 2010. Here is the press
release:
http://www.documentfoundation.org/contact/tdf_release.html
Main Site:
http://www.documentfoundation.org/
Prob
Guys,
Anyone using hylafax should be aware that a bug in ghostscript 8.71
will case
hylafax to send blank pages. The following is the response from the upstream
folks. I'll look for a newer version, test and report back.
David, you using ghostscript 8.71 on that server? That's a known
On 09/28/2010 01:15 PM, Tobias Powalowski wrote:
> Latest kernel is in testing,
> please signoff for both arches.
>
> seems -1 package had wrong headers while packaging
>
>
> greetings
> tpowa
Looks good. Booted 1st time, no usbhid-ups hang, dmraid activated properly.
Fantastic! Thanks Tobias :
Excerpts from Ng Oon-Ee's message of 2010-09-29 00:55:12 +0200:
> On Wed, 2010-09-29 at 00:12 +0200, Philipp Überbacher wrote:
> > Excerpts from Ray Rashif's message of 2010-09-28 23:19:19 +0200:
> > > On 29 September 2010 03:33, Philipp Überbacher
> > > wrote:
> > > > Excerpts from Ng Oon-Ee's m
On Wed, 2010-09-29 at 00:12 +0200, Philipp Überbacher wrote:
> Excerpts from Ray Rashif's message of 2010-09-28 23:19:19 +0200:
> > On 29 September 2010 03:33, Philipp Überbacher
> > wrote:
> > > Excerpts from Ng Oon-Ee's message of 2010-09-28 21:06:57 +0200:
> > >> Or use bauerbill and set mplay
On Tue, 2010-09-28 at 14:44 -0700, John Holbrook wrote:
> Thanks. I just found it in testing. Install fixed my problem. Very
> frustrating though.
Kernel updates always go through [testing] first.
Excerpts from Ray Rashif's message of 2010-09-28 23:19:19 +0200:
> On 29 September 2010 03:33, Philipp Überbacher wrote:
> > Excerpts from Ng Oon-Ee's message of 2010-09-28 21:06:57 +0200:
> >> Or use bauerbill and set mplayer to automatically compile from abs if
> >> there's an update =)
> >
> >
Thanks. I just found it in testing. Install fixed my problem. Very
frustrating though.
On 09/29/2010 12:31 AM, John Holbrook wrote:
Hi,
I'm experiencing the issue as discussed here on the forums:
https://bbs.archlinux.org/viewtopic.php?id=105637
This mentions a bug report at:
https://bugs.archlinux.org/task/20972
The fix mentioned is to run kernel26-headers -2.
I am currently
Hi,
I'm experiencing the issue as discussed here on the forums:
https://bbs.archlinux.org/viewtopic.php?id=105637
This mentions a bug report at:
https://bugs.archlinux.org/task/20972
The fix mentioned is to run kernel26-headers -2.
I am currently running "core/kernel26-headers 2.6.35.6-1 [ins
On 29 September 2010 03:33, Philipp Überbacher wrote:
> Excerpts from Ng Oon-Ee's message of 2010-09-28 21:06:57 +0200:
>> Or use bauerbill and set mplayer to automatically compile from abs if
>> there's an update =)
>
> I'm curious, what can it actually do? Build from ABS, ok, but
> automatically
On 29/09/10 05:27, Heiko Baums wrote:
Am Tue, 28 Sep 2010 21:04:42 +0200
schrieb Andreas Radke:
I'm going to prepare Arch builds for libreoffice in our svn but won't
upload any binary packages until the new way gets more clear.
Why not uploading binary packages? Wouldn't be the worst idea to
On 29 September 2010 03:04, Andreas Radke wrote:
> Anyway go-openoffice is depricated as said in the #go-oo channel topic.
Superseded by libreoffice (or whatever it will finally be called, eg.
if they manage to get the OpenOffice brand, so go-openoffice shouldn't
go anywhere for the moment.
On 2
Excerpts from Ng Oon-Ee's message of 2010-09-28 21:06:57 +0200:
> On Tue, 2010-09-28 at 20:19 +0200, uli.armbrus...@googlemail.com wrote:
> > * Ionuț Bîru [28.09.2010 17:41]:
> > > On 09/28/2010 06:39 PM, Samir wrote:
> > > > I have a question about Best Practices or... a clean way of handeling
>
Am Tue, 28 Sep 2010 21:04:42 +0200
schrieb Andreas Radke :
> I'm going to prepare Arch builds for libreoffice in our svn but won't
> upload any binary packages until the new way gets more clear.
Why not uploading binary packages? Wouldn't be the worst idea to have
both packages in the repo, so th
* Ng Oon-Ee [28.09.2010 21:07]:
> On Tue, 2010-09-28 at 20:19 +0200, uli.armbrus...@googlemail.com wrote:
> > * Ionuț Bîru [28.09.2010 17:41]:
> > > On 09/28/2010 06:39 PM, Samir wrote:
> > > > I have a question about Best Practices or... a clean way of handeling
> > > > these types of scenarios.
On Tue, 2010-09-28 at 20:19 +0200, uli.armbrus...@googlemail.com wrote:
> * Ionuț Bîru [28.09.2010 17:41]:
> > On 09/28/2010 06:39 PM, Samir wrote:
> > > I have a question about Best Practices or... a clean way of handeling
> > > these types of scenarios...
> > >
> > > I've seen this come up with
* Ionuț Bîru [28.09.2010 17:41]:
> On 09/28/2010 06:39 PM, Samir wrote:
> > I have a question about Best Practices or... a clean way of handeling
> > these types of scenarios...
> >
> > I've seen this come up with several packages
> >
> > If I install mplayer and x264 from pacman, but then pul
Latest kernel is in testing,
please signoff for both arches.
seems -1 package had wrong headers while packaging
greetings
tpowa
--
Tobias
Powalowski
Archlinux Developer & Package Maintainer
(tpowa)
http://www.archlinux.org
tp...@archlinux.org
signature.asc
Description: This is a digitally si
On 28.09.2010 18:46, Samir wrote:
> I was trying to think if there's anything, as a packager, that I could
> do to prevent or mitigate dll hell (.so hell? )
>
Some time ago I wrote a patch to add special dependencies to packages so
that issue is being worked on. What's the status Allan?
PS: Ple
Fair enough. I was trying to think if there's a cleaner way of
avoiding breakage.
I found http://aur.archlinux.org/packages.php?ID=15982 which seems to
provide some sanity.
I was trying to think if there's anything, as a packager, that I could
do to prevent or mitigate dll hell (.so hell? )
--
On 28.09.2010 17:39, Samir wrote:
> Now, to be fair.. mplayer probably should have been linked against
> libx264.so rather then libx264.so.104 (-git package provides a
> libx264.so.105).
Normally that number only changes if the libraries aren't compatible
anymore. That means mplayer might break co
On 09/28/2010 06:39 PM, Samir wrote:
I have a question about Best Practices or... a clean way of handeling
these types of scenarios...
I've seen this come up with several packages
If I install mplayer and x264 from pacman, but then pull x264-git from
aur, and install that.
x264 conflicts w
I have a question about Best Practices or... a clean way of handeling
these types of scenarios...
I've seen this come up with several packages
If I install mplayer and x264 from pacman, but then pull x264-git from
aur, and install that.
x264 conflicts with x264-git which makes sense.. but th
24 matches
Mail list logo
