Displaying 20 results from an estimated 305 matches for "immin".
Did you mean:
i_min
2007 Sep 18
1
libtheora 1.0 alpha8 released, beta1 imminent
Hello,
it's a great pleasure for me to announce the availability of libtheora
alpha8 and the imminent availability of beta1.
http://downloads.xiph.org/releases/theora/libtheora-1.0alpha8.tar.gz
alpha8 brings a completely new decoder (feature complete, lifted from
derf's theora-exp) and additional control over the encoder (applications
now can specify their own set of quantization parameter...
2007 Sep 18
1
libtheora 1.0 alpha8 released, beta1 imminent
Hello,
it's a great pleasure for me to announce the availability of libtheora
alpha8 and the imminent availability of beta1.
http://downloads.xiph.org/releases/theora/libtheora-1.0alpha8.tar.gz
alpha8 brings a completely new decoder (feature complete, lifted from
derf's theora-exp) and additional control over the encoder (applications
now can specify their own set of quantization parameter...
2001 Apr 19
0
Fwd: Re: 2.2 release imminent.
...e this can be fixed? Even fixing the
check for dn_expand in resolv.so would help ...
Tony
>Date: Tue, 10 Apr 2001 15:29:39 -0700
>To: "jeremy@valinux.com" <jeremy@valinux.com>, samba@samba.org
>From: Anthony Brock <abrock@georgefox.edu>
>Subject: Re: 2.2 release imminent.
>
>Okay,
>
>After hacking around a little, I got it to compile. Basically, Solaris
>requires the resolv.so library be added to the list of libraries for
>dn_expand, and the library libcrypto.a does not exist on my
>system. Instead, I found the library libk5crypto.a, wh...
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make
dist, (on NetBSD 10) and then used that tarball as the source for
pkgsrc, built a package, installed it on machine with a Best Fortress
(NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT
interface code seem fine.
So I see no problems. (Of course, I always like there to be a multiday
interval from rc to
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make
dist, (on NetBSD 10) and then used that tarball as the source for
pkgsrc, built a package, installed it on machine with a Best Fortress
(NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT
interface code seem fine.
So I see no problems. (Of course, I always like there to be a multiday
interval from rc to
2007 Dec 12
0
Last call: 0.24.0 is imminent
I''ve now fixed all of the bugs I''m going to fix for 0.24.0/misspiggy.
Please test that the current ''master'' branch in git works for you.
I''ll probably release tomorrow, or maybe early on Thursday if I don''t
hear of any show-stoppers.
--
I don''t want any yes-men around me. I want everybody to tell me the
truth even if it
2012 Sep 06
1
Xen 4.1.4 release imminent?
Hi,
Just wondering if there''s a release of xen 4.1.4 being planned for the
near future to bundle up the recent XSA''s?
- Nathan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
2007 Aug 01
1
[LLVMdev] Web Server Restart Imminent
All,
Just letting you know that I intend to restart the web server in a few
minutes. Notice was given earlier today.
Reid.
2025 Apr 09
1
NUT testing for v2.8.3 (hopefully imminent)
Sounds great, thanks!
A number of other community members raised a few issues from the RC testing
that finally took off, so I guess there will be an rc3 at least...
There may also be some issues with upssched as discussed in another mailing
list thread and https://github.com/networkupstools/nut/issues/2890 (may be
or not be same problem underneath) but I am not ready to investigate that
deeply.
2025 Apr 09
1
NUT testing for v2.8.3 (hopefully imminent)
Sounds great, thanks!
A number of other community members raised a few issues from the RC testing
that finally took off, so I guess there will be an rc3 at least...
There may also be some issues with upssched as discussed in another mailing
list thread and https://github.com/networkupstools/nut/issues/2890 (may be
or not be same problem underneath) but I am not ready to investigate that
deeply.
2005 Mar 29
1
Rsync 2.6.4pre4 released (2.6.4 imminent!)
I've released rsync 2.6.4pre4. I believe that this version will be what
gets released as 2.6.4, hopefully on Wednesday. Please try this out
and let me know if anything is amiss.
All the changes since 2.6.3 are mentioned here:
http://rsync.samba.org/ftp/rsync/preview/NEWS
You'll also find a preview of the man pages in the same dir (as usual):
2005 Mar 29
1
Rsync 2.6.4pre4 released (2.6.4 imminent!)
I've released rsync 2.6.4pre4. I believe that this version will be what
gets released as 2.6.4, hopefully on Wednesday. Please try this out
and let me know if anything is amiss.
All the changes since 2.6.3 are mentioned here:
http://rsync.samba.org/ftp/rsync/preview/NEWS
You'll also find a preview of the man pages in the same dir (as usual):
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was
supposed to point to the same commit as what I originally hoped was
"v2.8.3"... but did not - instead initially pointed to what would land to
`master` among its fixes for a cleaner release. Hopefully tags are
correctly refined on GitHub repo now, at least.
Jim
On Tue, Apr 8, 2025 at 2:58?PM Greg
2025 Apr 08
2
NUT testing for v2.8.3 (hopefully imminent)
Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was
supposed to point to the same commit as what I originally hoped was
"v2.8.3"... but did not - instead initially pointed to what would land to
`master` among its fixes for a cleaner release. Hopefully tags are
correctly refined on GitHub repo now, at least.
Jim
On Tue, Apr 8, 2025 at 2:58?PM Greg
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing.
There are commits in the rc tag that are not on master:
$ git log --oneline ..v2.8.3-rc1
3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches
4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches
504706d45 Makefile.am: nut-scanner does directly depend on clients after all
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
I'm starting down the path of testing.
There are commits in the rc tag that are not on master:
$ git log --oneline ..v2.8.3-rc1
3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches
4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches
504706d45 Makefile.am: nut-scanner does directly depend on clients after all
2012 Mar 14
2
QA builds for 3.2.6 and 3.3 beta3
Greetings,
There are 2 imminent releases coming soon to a download server near you:
1. GlusterFS 3.2.6 - a maintenance release that fixes some bugs.
2. GlusterFS 3.3 beta 3 - the next iteration of the exciting new hotness that will be 3.3
You can find both of these in the "QA builds" server:
http://bits.gluster.c...
2009 Jan 22
4
SYSLINUX 3.73 release imminent
I intend to release SYSLINUX 3.73-pre7 as SYSLINUX 3.73 as soon as
possible. Please let me know if there are any outstanding bugs with
3.73-pre7 that either haven't been reported or I have forgotten about...
it's been a while.
-hpa
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
So, NUT v2.8.3-rc1 is out.
I first thought it was the release, but some CI runs convinced me
otherwise, so there would be a bit of back and forth on the master branch
as some recipes get fixed. Apparently, some parallel runs stepped onto each
other's toes sometimes, but coinciding the wrong way just once in a few
hundred builds. Hopefully I found why and will re-publish in a few hours.
Jim
2025 Apr 08
1
NUT testing for v2.8.3 (hopefully imminent)
So, NUT v2.8.3-rc1 is out.
I first thought it was the release, but some CI runs convinced me
otherwise, so there would be a bit of back and forth on the master branch
as some recipes get fixed. Apparently, some parallel runs stepped onto each
other's toes sometimes, but coinciding the wrong way just once in a few
hundred builds. Hopefully I found why and will re-publish in a few hours.
Jim