Felix Miata wrote:
On 2007/04/09 14:18 (GMT+0200) Carlos E. R. apparently typed:
2007-04-08 at 20:47 -0400, Felix Miata wrote:
I then tried to mount and chroot to it
in order to run grub-install. Grub-install failed due to the non-existent
target device.
It could be because the /mnt/dev t
On 2007/04/09 14:18 (GMT+0200) Carlos E. R. apparently typed:
> 2007-04-08 at 20:47 -0400, Felix Miata wrote:
>> I then tried to mount and chroot to it
>> in order to run grub-install. Grub-install failed due to the non-existent
>> target device.
> It could be because the /mnt/dev tree is not p
Am Mittwoch 16 Januar 2008 schrieb Günther J. Niederwimmer:
> Hello,
>
> my factory tree is deleted :(.
>
> I have the factory on my local system and update it with drpmsync (cron).
> last night all files from factory are deleted :(.
>
> Now is starting a new download ...
Well, another fallout fro
Hello,
my factory tree is deleted :(.
I have the factory on my local system and update it with drpmsync (cron). last
night all files from factory are deleted :(.
Now is starting a new download ...
--
mit freundlichen Grüßen / best Regards
Günther J. Niederwimmer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cristian Rodríguez schreef:
> M9. escribió:
>
>> But now new deps are troublesome: nfs-client, needs libevent-1.3b.so.1()
>
> Probably not all pakcages have synced out yet, factory provides
> libevent-1.3e atm.
>
>
thnx...
- --
Have a nice day
Cristian Rodríguez wrote:
M9. escribió:
But now new deps are troublesome: nfs-client, needs libevent-1.3b.so.1()
Probably not all pakcages have synced out yet, factory provides
libevent-1.3e atm.
No complaints after upgrading to libevent-1.3e-3.
# rpm -q nfs-client
nfs-client-1.1.0-11
Reg
M9. escribió:
> But now new deps are troublesome: nfs-client, needs libevent-1.3b.so.1()
Probably not all pakcages have synced out yet, factory provides
libevent-1.3e atm.
--
"The only thing that interferes with my learning is my education." -
Albert Einstein
Cristian Rodríguez R.
Platform/Op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
M9. schreef:
>
>
> JP Rosevear schreef:
>> On Thu, 2008-01-03 at 14:01 +0100, Dirk Mueller wrote:
>>> On Sunday 30 December 2007, M9. wrote:
>>>
Many pkgs depend on this.
The most annoying is that not installing totem would be the right
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JP Rosevear schreef:
> On Thu, 2008-01-03 at 14:01 +0100, Dirk Mueller wrote:
>> On Sunday 30 December 2007, M9. wrote:
>>
>>> Many pkgs depend on this.
>>> The most annoying is that not installing totem would be the right
>>> solution, but it is imp
JP Rosevear wrote:
On Thu, 2008-01-03 at 14:01 +0100, Dirk Mueller wrote:
On Sunday 30 December 2007, M9. wrote:
Many pkgs depend on this.
The most annoying is that not installing totem would be the right
solution, but it is impossible to apply that proposel...
Please post error messages, do
On Thu, 2008-01-03 at 14:01 +0100, Dirk Mueller wrote:
> On Sunday 30 December 2007, M9. wrote:
>
> > Many pkgs depend on this.
> > The most annoying is that not installing totem would be the right
> > solution, but it is impossible to apply that proposel...
>
> Please post error messages, do no
On Sunday 30 December 2007, M9. wrote:
> Many pkgs depend on this.
> The most annoying is that not installing totem would be the right
> solution, but it is impossible to apply that proposel...
Please post error messages, do not interpret them. I was able to do a factory
update just fine.
Gree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Many pkgs depend on this.
The most annoying is that not installing totem would be the right
solution, but it is impossible to apply that proposel...
Yast solver does not apply: not install gnomekeyring.
- --
Have a nice day,
M9.
On Mon, Dec 24, 2007 at 09:33:34AM +0100, Stephan Kulow wrote:
> Am Montag 24 Dezember 2007 schrieb Greg KH:
>
> > - File /var/cache/zypp/raw/factoryYGzNXo/content.key doesn't contain
> > public key data - Valid metadata not found at specified URL(s)
> > Please, check if the URLs defined
Am Montag 24 Dezember 2007 schrieb Greg KH:
>- File /var/cache/zypp/raw/factoryYGzNXo/content.key doesn't contain
> public key data - Valid metadata not found at specified URL(s)
> Please, check if the URLs defined for this repository are pointing to a
> valid repository. Skipping re
I'm getting the following when trying to refresh with zypper:
# zypper -v ref factory
Verbosity: 1
Non-option program arguments: 'factory'
Initializing Target
Checking whether to refresh metadata for factory
Downloading: content
* Downloading
Hi,
http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/
kernel-default-2.6.24_rc5_git2-2.i586.rpm
used in factory installation in VirtualBox (latest) can start only with
acpi=off, but then system timer runs very fast. Old kernel is, as usually,
removed.
Booting in r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Updating gets tyresome with the network bug: incompatible
sender/receiver protocols, resultingi update-server time-out errors, and
reinserting the commands.
Now showing the extreme use for the command memory in the navigation
keys :-), (briljant s
Hello,
I have a new problem with drpmsync
d inst-source/suse/noarch/glest-data-3.0.0-3.noarch.rpm
chmod
/data2/SUSE/opensuse/distribution/SL-OSS-factory/drpmsync/wip/glest-data-3.0.0-3.noarch.rpm:
No such file or directory
Please make a sync.
--
mit freundlichen Grüßen / best Regards
Günt
Just a comment from Mr. LWN
> Said grumpy editor has actively looked for an opensuse development
> distribution a few times, with no luck. The folks who create
> opensuse.org don't make the factory distribution easy to find - the
> "latest development version" link does not go anywhere near it. I
Stephan Kulow wrote:
Am Donnerstag 01 November 2007 schrieb Sid Boyce:
Sid Boyce wrote:
lrwxrwxrwx1 rootroot 26 Oct 27 00:22
/usr/lib64/libgda-report-3.0.so -> libgda-report-3.0.so.3.0.0
# rpm -qf /usr/lib64/libgda-report-3.0.so.3.0.0
error: file /usr/lib64/libgda-report-3
Am Donnerstag 01 November 2007 schrieb Sid Boyce:
> Sid Boyce wrote:
> > lrwxrwxrwx1 rootroot 26 Oct 27 00:22
> > /usr/lib64/libgda-report-3.0.so -> libgda-report-3.0.so.3.0.0
> > # rpm -qf /usr/lib64/libgda-report-3.0.so.3.0.0
> > error: file /usr/lib64/libgda-report-3.0.so.3
Sid Boyce wrote:
lrwxrwxrwx1 rootroot 26 Oct 27 00:22
/usr/lib64/libgda-report-3.0.so -> libgda-report-3.0.so.3.0.0
# rpm -qf /usr/lib64/libgda-report-3.0.so.3.0.0
error: file /usr/lib64/libgda-report-3.0.so.3.0.0: No such file or
directory
That's right, it does not exis
lrwxrwxrwx1 rootroot 26 Oct 27 00:22
/usr/lib64/libgda-report-3.0.so -> libgda-report-3.0.so.3.0.0
# rpm -qf /usr/lib64/libgda-report-3.0.so.3.0.0
error: file /usr/lib64/libgda-report-3.0.so.3.0.0: No such file or directory
That's right, it does not exist.
I have seen this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan Kulow schreef:
> Hi!
>
> Just so you know: RC2 is not yet done, we're still waiting for more fixes
> to be verified before we can do give it officially to QA.
>
> But Factory has been synced out again, so if you do a
> zypper update -t packa
Hi!
Just so you know: RC2 is not yet done, we're still waiting for more fixes
to be verified before we can do give it officially to QA.
But Factory has been synced out again, so if you do a
zypper update -t package it should pull in RC2 Candidate and you can
test the latest fixes of the system.
Hi!
We made sure yesterday that Factory gets synced out, so
you see what we're testing.
Note that you will see a missing dependency from desktop-file-utils
to /etc/profile.d/xdg-enviroment.sh (sic!), which was fixed after the
rebuild you see synced out. Just ignore that and keep testing with it
No, it all worked well enough for long enough that I assumed it was a
valid alternative repo URL. The fact that zypper identifies the type
(rpm-md) and includes it in the sl output suggests it has been usable
at some point.
I think I started using those repo definitions when the yast level URLs
w
>>> On 13-08-2007 at 17:30, Klaus Kaempf <[EMAIL PROTECTED]> wrote:
> * Stephan Kulow <[EMAIL PROTECTED]> [Aug 13. 2007 16:13]:
>> Am Montag 13 August 2007 schrieb Jason Boissiere:
>> > Using the inst-source level URL to define the sources appears to have
>> > resolved my problems. Is that expected
* Stephan Kulow <[EMAIL PROTECTED]> [Aug 13. 2007 16:13]:
> Am Montag 13 August 2007 schrieb Jason Boissiere:
> > Using the inst-source level URL to define the sources appears to have
> > resolved my problems. Is that expected behaviour?
> >
> I wonder where you found a hint to use the suse/ subdir
Am Montag 13 August 2007 schrieb Jason Boissiere:
> Using the inst-source level URL to define the sources appears to have
> resolved my problems. Is that expected behaviour?
>
I wonder where you found a hint to use the suse/ subdir
Greetings, Stephan
--
SUSE LINUX Products GmbH, GF: Markus Rex,
Using the inst-source level URL to define the sources appears to have
resolved my problems. Is that expected behaviour?
Jason
On Mon, 2007-08-13 at 14:36 +0200, Stephan Kulow wrote:
> Am Montag 13 August 2007 schrieb Jason Boissiere:
>
> > --+-+-+++--
Am Montag 13 August 2007 schrieb Jason Boissiere:
> --+-+-+++--
>- 1
> | Yes | Yes | rpm-md | opensuse_non_oss |
>
> http://ftp.opensuse.org/pub
I've not been able to update factory for a while now. I expected it to
return to a sane state once beta1 was available, but I'm still getting
nowhere. Is it still inconsistent, or am I hitting a bug I've missed
while looking through bugzilla? Relevant excerpt from a zypper update;
Markus Koßmann wrote:
Am Sonntag, 5. August 2007 schrieb Stephan Kulow:
Am Sunday 05 August 2007 schrieb Markus Koßmann:
which seems to be a known problem IIRC.
Does zypper refresh help?
Yes, that seems to fix the problem.
-
Am Sonntag, 5. August 2007 schrieb Stephan Kulow:
> Am Sunday 05 August 2007 schrieb Markus Koßmann:
> > which seems to be a known problem IIRC.
>
> Does zypper refresh help?
>
Yes, that seems to fix the problem.
-
To unsubscribe,
Filled bug #297627
--
Regards, Nikolay Derkach
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Am Sunday 05 August 2007 schrieb Markus Koßmann:
>
> which seems to be a known problem IIRC.
Does zypper refresh help?
>
> But it's not nice that you need -vv to get an usable error message and
> that the problem is not clearly marked as error in the logfile. So I filed
> bug 297626.
Yes, I agre
Am Samstag, 4. August 2007 schrieb Stephan Kulow:
> Am Saturday 04 August 2007 schrieb Markus Koßmann:
> > Is factory x86_64 still known to be broken ?
>
> No, not known.
>
> > Unfortunately searching for "error" or "warn" in /var/log/zypper.log
> > shows nothing usable.
> >
> > zypper is zypper-0
Hi,
On Sun, 5 Aug 2007, Nikolay Derkach wrote:
> > Same here.
>
> Well, actually it doesn't happen with download.opensuse.org
> Maybe this issue is gwdg specific.
Impossible.
Viele Grüße
Eberhard Mönkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED])
> Same here.
Well, actually it doesn't happen with download.opensuse.org
Maybe this issue is gwdg specific.
--
Regards, Nikolay Derkach
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
В сообщении от Saturday 04 August 2007 21:32:23 Stephan Kulow написал(а):
> Am Saturday 04 August 2007 schrieb Markus Koßmann:
> > Is factory x86_64 still known to be broken ?
>
> No, not known.
>
> > Unfortunately searching for "error" or "warn" in /var/log/zypper.log
> > shows nothing usable.
> >
Am Saturday 04 August 2007 schrieb Markus Koßmann:
> Is factory x86_64 still known to be broken ?
No, not known.
>
> Unfortunately searching for "error" or "warn" in /var/log/zypper.log shows
> nothing usable.
>
> zypper is zypper-0.8.5-3, libzypp is libzypp-3.12.1-2 which seem to be the
> curren
Is factory x86_64 still known to be broken ?
When running "zypper up" I get :
linux-n04x:~ # zypper up
* Building repository 'inst_source' cache
Problem loading data from 'inst_source'
Resolvables from 'inst_source' not loaded because of error.
* Reading installed packages [100%]
with every mi
Donn Washburn wrote:
Stephan Kulow wrote:
Am Dienstag 24 Juli 2007 schrieb Silviu Marin-Caea:
I have just performed an update to latest factory, and there must be
something broken with resmgr.
/dev/null is not accessible by my user, I get /dev/null permission denied
when I log in the console,
Stephan Kulow wrote:
Am Dienstag 24 Juli 2007 schrieb Silviu Marin-Caea:
I have just performed an update to latest factory, and there must be
something broken with resmgr.
/dev/null is not accessible by my user, I get /dev/null permission denied
when I log in the console, and KDE does not start
On Tuesday 24 July 2007 04:07:28 pm Stephan Kulow wrote:
> Am Dienstag 24 Juli 2007 schrieb Silviu Marin-Caea:
> > I have just performed an update to latest factory, and there must be
> > something broken with resmgr.
> >
> > /dev/null is not accessible by my user, I get /dev/null permission denied
Am Dienstag 24 Juli 2007 schrieb Silviu Marin-Caea:
> I have just performed an update to latest factory, and there must be
> something broken with resmgr.
>
> /dev/null is not accessible by my user, I get /dev/null permission denied
> when I log in the console, and KDE does not start at all.
>
> I
Silviu Marin-Caea escribió:
> I have just performed an update to latest factory, and there must be
> something
> broken with resmgr.
>
> /dev/null is not accessible by my user, I get /dev/null permission denied
> when
> I log in the console, and KDE does not start at all.
>
> I have stopped t
Silviu Marin-Caea wrote:
> I have just performed an update to latest factory, and there must be
> something broken with resmgr.
>
> /dev/null is not accessible by my user, I get /dev/null permission denied
> when I log in the console, and KDE does not start at all.
>
> I have stopped the resmgr s
I have just performed an update to latest factory, and there must be something
broken with resmgr.
/dev/null is not accessible by my user, I get /dev/null permission denied when
I log in the console, and KDE does not start at all.
I have stopped the resmgr service and then chmod a+rw /dev/null,
Peter Czanik <[EMAIL PROTECTED]> writes:
> Hello,
> When will we see the next factory update? In its current form PPC can't
> be installed :-(
> I guess, all the developers are now happy about finishing SP1 and gone
> to holiday? ;-)
Once everything is build through again, we'll sync out again.
Hello,
When will we see the next factory update? In its current form PPC can't
be installed :-(
I guess, all the developers are now happy about finishing SP1 and gone
to holiday? ;-)
Bye,
CzP
-
To unsubscribe, e-mail: [EMAIL PROTEC
Hi,
I experiance some strange things lately with updating (using
zen-updater and rug).
Whenever I select a package from the NON-OSS repo, it fails with the
error,
Can not provide /var/cache/./suse/i586/foo.rpm
(containing the whole path representing where from it came on the
server).
I conf
On 1/20/07, Hans Witvliet <[EMAIL PROTECTED]> wrote:
On Fri, 2007-01-19 at 21:14 +0100, Claes Bäckström wrote:
> Is there some problems with the sync to factory?
>
> Been a lot of commits to the commit mailinglist but nothing new at the
> mirrors since 15 Jan.
>
You mean "brand-new" or "new-upgra
On Fri, 2007-01-19 at 21:14 +0100, Claes Bäckström wrote:
> Is there some problems with the sync to factory?
>
> Been a lot of commits to the commit mailinglist but nothing new at the
> mirrors since 15 Jan.
>
> Warm Regards,
> Claes Backstrom
You mean "brand-new" or "new-upgrades"?
yesterday (1
Is there some problems with the sync to factory?
Been a lot of commits to the commit mailinglist but nothing new at the
mirrors since 15 Jan.
Warm Regards,
Claes Backstrom
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Hi,
Factory is open for upstream development again.
However, we will not sync out Factory in the next week, to have the bandwidth
for pushing 10.2 to all reachable mirrors.
10.2 is open for security fix and critical bugfixes as usual.
bye
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH,
Hello,
Am Donnerstag, 19. Oktober 2006 22:50 schrieb Terje J. Hanssen:
[...]
> I downloaded the alpha5 i386 mini.iso, burned and booted the CD.
> On the first boot screen I entered F4, HTTP and
> "download.opensuse.org/distribution/SL-OSS-factory/inst-source" in
> the server field, which become au
Andreas Hanke wrote:
> Terje J. Hanssen schrieb:
>> But what is the correct ftp address to enter according to
>> # 4. Point the YaST installer to the installation repository (by
>> pressing F3 and then F4)
>
> [...]
>
> => The repository URL is:
>
> http://download.opensuse.org/distribution/SL-OSS-
Hi,
Many of the mirrors do not carry the openSUSE factory. Those that do
appear to have mirrored a problem. To wit:
http://linux.nssl.noaa.gov/opensuse/distribution/SL-OSS-factory/inst-source
Can't provide /suse/setup/descr/packages.sk from
http://linux.nssl.noaa.gov/opensuse/distribution/SL-OSS
On Tuesday 17 October 2006 06:50, Felix Miata wrote:
> On 06/10/16 23:05 (GMT-0700) Randall R Schulz apparently typed:
> > On Monday 16 October 2006 22:11, Rajko M wrote:
> >> Is this what you meant:
> >> http://en.opensuse.org/Installation_without_CD
> >>
> >> title
> >> #Installing_from_data_save
On 06/10/16 23:05 (GMT-0700) Randall R Schulz apparently typed:
> On Monday 16 October 2006 22:11, Rajko M wrote:
>> Is this what you meant:
>> http://en.opensuse.org/Installation_without_CD
>> title
>> #Installing_from_data_saved_on_your_local_machine
> That and #Grub, I guess.
> But I think
Rajko,
On Monday 16 October 2006 22:11, Rajko M wrote:
> On Monday 16 October 2006 20:11, Randall R Schulz wrote:
> > Felix,
> >
> > On Monday 16 October 2006 17:13, Felix Miata wrote:
> > > ...
> > >
> > > Note that you need not download even the mini iso if your
> > > installation target already
On Monday 16 October 2006 20:11, Randall R Schulz wrote:
> Felix,
>
> On Monday 16 October 2006 17:13, Felix Miata wrote:
> > ...
> >
> > Note that you need not download even the mini iso if your
> > installation target already has a working grub. All you need is the
> > linux and initrd from the a
On 06/10/16 18:11 (GMT-0700) Randall R Schulz apparently typed:
> On Monday 16 October 2006 17:13, Felix Miata wrote:
>> Note that you need not download even the mini iso if your
>> installation target already has a working grub. All you need is the
>> linux and initrd from the appropriate boot/*
Felix,
On Monday 16 October 2006 17:13, Felix Miata wrote:
> ...
>
> Note that you need not download even the mini iso if your
> installation target already has a working grub. All you need is the
> linux and initrd from the appropriate boot/*/loader directory placed
> where a grub stanza can find
On 06/10/17 01:50 (GMT+0200) Terje J. Hanssen apparently typed:
> Normally I've used to download the non-OSS dvd iso and burn the DVD for
> installation.
> Now I though to try the Internet installation according to
> http://en.opensuse.org/Development_Version#Internet_Installation
> First I downlo
Terje J. Hanssen schrieb:
> But what is the correct ftp address to enter according to
> # 4. Point the YaST installer to the installation repository (by
> pressing F3 and then F4)
[...]
> (the rpm location didn't look to work
> http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
Hi,
On Tue, 17 Oct 2006, Terje J. Hanssen wrote:
Normally I've used to download the non-OSS dvd iso and burn the DVD for
installation.
Now I though to try the Internet installation according to
http://en.opensuse.org/Development_Version#Internet_Installation
First I downloaded and burned the DV
Normally I've used to download the non-OSS dvd iso and burn the DVD for
installation.
Now I though to try the Internet installation according to
http://en.opensuse.org/Development_Version#Internet_Installation
First I downloaded and burned the DVD-i386-mini.iso on a CDR.
But what is the correct ft
No problem, if you have a local server runing and willing to download
the isos.
If both premises can be fullfilled, ask back..
Pete
Hi Pete,
I didn't see any response from the OP (I may have missed it though :( ),
but I'm keen to try again for a network install. I have a number of
machines
Am Montag, 7. August 2006 15:04 schrieb Joerg Mayer:
> On Mon, Aug 07, 2006 at 01:23:29PM +0200, Andreas Jaeger wrote:
> >
> > For now I advise to use the Alpha2 tree,
>
> How do I do a network install of the Alpha2 tree? It looks like there
> are only isos available.
No problem, if you have a loc
Joerg Mayer <[EMAIL PROTECTED]> writes:
> On Mon, Aug 07, 2006 at 01:23:29PM +0200, Andreas Jaeger wrote:
>> Joerg Mayer <[EMAIL PROTECTED]> writes:
>>
>> > I just downloaded the factory miniiso. After I booted it I selected
>> > netinstall
>> > http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS
On Mon, Aug 07, 2006 at 01:23:29PM +0200, Andreas Jaeger wrote:
> Joerg Mayer <[EMAIL PROTECTED]> writes:
>
> > I just downloaded the factory miniiso. After I booted it I selected
> > netinstall
> > http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/
>
> The installation repo
Joerg Mayer <[EMAIL PROTECTED]> writes:
> I just downloaded the factory miniiso. After I booted it I selected
> netinstall
> http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/
The installation repository in factory is broken right now, we're
working on fixing it.
For now I
On Mon, Aug 07, 2006 at 12:46:39PM +0200, Joerg Mayer wrote:
> I just downloaded the factory miniiso. After I booted it I selected
> netinstall
> http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/
>
> After the image is downloaded things look like this (on vt3):
>
>
I just downloaded the factory miniiso. After I booted it I selected
netinstall
http://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/
After the image is downloaded things look like this (on vt3):
===
dns: ftp.gwdgf.de is 134.76.11.100
Loading image
"/
Peter Czanik <[EMAIL PROTECTED]> writes:
> Hello,
> 10.2 Alpha2 is just around the corner, it's synced out to mirrors. If I
> sync my home factory mirror now, will it be the same as Alpha2? Or it's
> older/newer or any other way different? Bye,
Alpha2 and factory are in sync right now,
Andreas
-
Hello,
10.2 Alpha2 is just around the corner, it's synced out to mirrors. If I
sync my home factory mirror now, will it be the same as Alpha2? Or it's
older/newer or any other way different? Bye,
CzP
-
To unsubscribe, e-mail: [EMA
Christian Boltz wrote:
As long as no new critical bugs are introduced, this isn't very
surprising ;-)
:-( so you (and others) are never stopping work :-)
nice. I add a phrase to get this more sure in the Factory page.
Just one more info, as of the testers debugging.
What is the most interes
Hello,
Am Montag, 12. Juni 2006 18:35 schrieb jdd:
[...]
> ==To be sure.==
> how is the passage between 10.1 and 10.2 made?
>
> is there a progressive transition through Factory (for
> example, does factory had the test zen updates?) or is there
> at some date a massive change?
It's freezed some
On Mon, Jun 12, 2006 at 06:35:12PM +0200, jdd wrote:
> http://lists.opensuse.org/archive/opensuse-announce/2006-Mar/0001.html
>
> said
>
> "Our current plan for these snapshots is:
^
> Fri, Jun 16 SUSE Linux 10.2 Alpha1 (Jun 15 is a holiday for
> us) "
>
>
On Monday, 12. June 2006 18:35, jdd wrote:
> so I was thinking dev for 10.2 started really only then.
Wrong.
> is there a progressive transition through Factory
Yes.
> (for example, does factory had the test zen updates?)
Sure, it has newer zen packages all the time.
> how/when are importa
Robert Schiele wrote:
On Mon, Jun 12, 2006 at 04:50:05PM +0200, jdd wrote:
no. I wanted to note that there is no factory distribution
for now (release is sheduled june 16?), the factory
repository should be identical to 10.1 one.
Huh? What did you smoke? Sure there is a current factory di
On Mon, Jun 12, 2006 at 04:50:05PM +0200, jdd wrote:
> no. I wanted to note that there is no factory distribution
> for now (release is sheduled june 16?), the factory
> repository should be identical to 10.1 one.
Huh? What did you smoke? Sure there is a current factory distribution (which
is
Stephan Binner wrote:
On Friday, 9. June 2006 18:53, jdd wrote:
I know Factory is not really available right now, but in the
The mini boot ISOs are back if you refer to that...
no. I wanted to note that there is no factory distribution
for now (release is sheduled june 16?), the factory
On Friday, 9. June 2006 18:53, jdd wrote:
> I know Factory is not really available right now, but in the
The mini boot ISOs are back if you refer to that...
Bye,
Steve
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
I'm rewrtiting
http://en.opensuse.org/Factory
that was evidently very outdated.
For that purpose, I need an info.
Factory is a frequently changing repo. what is approximately
the frequency of it's updates, in term of _minimum_ time
between two updates.
is it possible to have two updates in
I know Factory is not really available right now, but in the
way of translating this page I find:
http://fr.opensuse.org/Factory_Distribution#Where_can_I_find_it_.3F
with difference between YaST and YUM repositories.
is this distinction still usefull? I was understanding the
latter should be
Kastus <[EMAIL PROTECTED]> writes:
> On Sun, Apr 30, 2006 at 08:12:51AM +0200, Andreas Jaeger wrote:
>>
>> Check the inst-source/content file whether it's correct as explained
>> in my message,
>
> I checked inst-source/content on mirrors.kernel.org and it looks good.
> Thank you for the hint.
>
On Sun, Apr 30, 2006 at 08:12:51AM +0200, Andreas Jaeger wrote:
>
> Check the inst-source/content file whether it's correct as explained
> in my message,
I checked inst-source/content on mirrors.kernel.org and it looks good.
Thank you for the hint.
When I try network install from mirrors.kernel.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Juan Erbes escribió:
> In what package are the description of the version and product?
> Because I can't register it, and if I execute:
> /usr/lib/suseRegister/bin # ./suse_release -a
> Product:
> Version:
> Vendor:
> Dist:
> Distproduct:
> Distversion
2006/4/29, Andreas Jaeger <[EMAIL PROTECTED]>:
Factory is updated on our server again - and is synced out to the
mirrors. We've seen a number of reports of about segmentation faults
in YaST with the factory tree. There were two problems:
* bad error handling in YaST
* Wrong release in distvers
Kastus <[EMAIL PROTECTED]> writes:
> On Sat, Apr 29, 2006 at 11:05:19PM +0200, Andreas Jaeger wrote:
>>
>> Therefore I advise to check that factory is updated before using the
>> tree before installation.
>
> Please excuse me if it is an FAQ, but how do I verify that factory is
> updated? I was t
On Sat, Apr 29, 2006 at 11:05:19PM +0200, Andreas Jaeger wrote:
>
> Therefore I advise to check that factory is updated before using the
> tree before installation.
Please excuse me if it is an FAQ, but how do I verify that factory is
updated? I was trying to run net install from factory which wa
Factory is updated on our server again - and is synced out to the
mirrors. We've seen a number of reports of about segmentation faults
in YaST with the factory tree. There were two problems:
* bad error handling in YaST
* Wrong release in distversion in the content file
The inst-source/content
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdd wrote:
> I really don't like the delta iso process, even if I
> understand the necessity.
> but I beg the net install is still possible, with factory
> as source?
How to use smart to upgrade packages with Factory:
http://dev-loki.blogspot.com/20
jdd wrote:
> I really don't like the delta iso process, even if I
> understand the necessity.
I wasn't quite sure either, but it works just fine. I retrieved the
deltas last night, started the applydeltaiso, then went to bed.
/Per Jessen, Zürich
-
Andreas Jaeger wrote:
> Yes, it should be possible with factory as source,
nice, thanks
jdd
--
http://www.dodin.net
http://dodin.org/galerie_photo_web/expo/index.html
http://lucien.dodin.net
http://fr.susewiki.org/index.php?title=Gérer_ses_photos
---
1 - 100 of 124 matches
Mail list logo
