[opensuse] I should have known!

newer
[opensuse] First Moonlight port of...

Chris Arnold

1 Dec 2007 1 Dec '07

02:06

Not to update my system when the gnome:stble "installation sources" was "on"! Using SLED SP1 and performed an online update. Some of the updates were from the gnome:stable repo (like gconf2). Now my system will not login using gdm. Root will not even login. I have the system joined to a 2003 domain nd when trying to login as a domin user, i get "no logon servers". Root can not logon either; get xsession error. How can i find the packages that were updated then back date to those packages that are on the disc? I alt-cntrl-f5 to get the CL and tried to uninstall gconf2 but get a slew of dependency errors. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Carlos E. R.

1 Dec 1 Dec

04:00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-30 at 21:06 -0500, Chris Arnold wrote:

...

How can i find the packages that were updated then back date to those packages that are on the disc? I alt-cntrl-f5 to get the CL and tried to uninstall gconf2 but get a slew of dependency errors.

"rpm -q -a --last | less", for instance. But I prefer this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S To install "older" versions from the DVD you will have to "force" them. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHUNx+tTMYHG2NR9URArvJAJ9fJ1sbDX9vxgk4SKszS8JlqEoxdQCfXGKN WmCmZoWh9x8KUa30CqKkSxc= =FdMT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Bryen

04:22

On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...

rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time? What would put in if I wanted to generate a report that included which repository the packages came from? -- ---Bryen--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Wolfgang Rosenauer

09:36

Bryen schrieb:

...

On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

What would put in if I wanted to generate a report that included which repository the packages came from?

%{DISTRIBUTION} Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

10:55

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...

On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes. I use it as the sort field, being the first one. It could be removed from the ooutput, let me think... here: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | cut --fields="2-" | less -S even better :-) I wrote that before knowing about the --last token. Let's try... rpm -q -a --last --queryformat "%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | less -S but the output is broken! pine-pgp-filters-1.5-1 Sat 01 Dec 2007 02:04:02 AM CET emacs-x11-22.1-40.7 Thu 29 Nov 2007 07:51:39 PM CET emacs-22.1-40.7 Thu 29 Nov 2007 07:50:51 PM CET emacs-info-22.1-40.7 Thu 29 Nov 2007 07:48:14 PM CET MozillaFirefox-2.0.0.10-0.1 Thu 29 Nov 2007 07:47:12 PM CET No, --last doesn't work with --queryformat in any position. No idea why.

...

What would put in if I wanted to generate a report that included which repository the packages came from?

rpm --querytags that lists all the available tags - there are a lot! ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHUT2btTMYHG2NR9URAn9bAJoCCuTP6XGV5GBTdmZdz6P3ABLV0wCfQxcG +HwU80e+vNUGvrP5Otl5M/4= =kyX1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Aaron Kulkis

7 Dec 7 Dec

21:03

Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...
On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes.

Unix Time starts with t=0 seconds at 00:00, between 31 Dec 1969 and 01 Jan 1970, which is also knows as "the epoch." System time is an unsigned 32-bit number representing the number of seconds since "the epoch." 32-bit time will run out sometime in 2038. This gives us 31 years to convert to 64-bit time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

9 Dec 9 Dec

12:47

On Friday 07 December 2007 22:03:40 Aaron Kulkis wrote:

...

Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...
On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes.

Unix Time starts with t=0 seconds at 00:00, between 31 Dec 1969 and 01 Jan 1970, which is also knows as "the epoch."

System time is an unsigned 32-bit number representing the number of seconds since "the epoch."

32-bit time will run out sometime in 2038. This gives us 31 years to convert to 64-bit time.

Actually it's a signed long, which means 2147483647 seconds, or just over 68 years. An unsigned value would be about twice that But since it's typedef:ed to "long", all we have to do is stop buying 32 bit machines, the modern 64 bit systems are already safe until well after the sun explodes in a few billion years' time :) Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

14:18

Anders Johansson wrote:

...

On Friday 07 December 2007 22:03:40 Aaron Kulkis wrote:

...
32-bit time will run out sometime in 2038. This gives us 31 years to convert to 64-bit time.

Actually it's a signed long, which means 2147483647 seconds, or just over 68 years. An unsigned value would be about twice that

But since it's typedef:ed to "long", all we have to do is stop buying 32 bit machines, the modern 64 bit systems are already safe until well after the sun explodes in a few billion years' time :)

Hopefully, I'll have a 128 bit system by then. ;-) -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jerry Feldman

11 Dec 11 Dec

21:57

On Sun, 9 Dec 2007 13:47:50 +0100 Anders Johansson wrote:

...

On Friday 07 December 2007 22:03:40 Aaron Kulkis wrote:

...
Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...
On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes.

Unix Time starts with t=0 seconds at 00:00, between 31 Dec 1969 and 01 Jan 1970, which is also knows as "the epoch."

System time is an unsigned 32-bit number representing the number of seconds since "the epoch."

32-bit time will run out sometime in 2038. This gives us 31 years to convert to 64-bit time.

Actually it's a signed long, which means 2147483647 seconds, or just over 68 years. An unsigned value would be about twice that

Actually you are wrong. The Unix 95 standard required a signed int not a signed long. There was a big todo about converting to 64-bit time in the Unix 98 standard. The problem with many vendors was binary compatibility. I was involved in this for Tru64 Unix as if affected the Utmp/Utmpx libraries since the utmp and wtmp files contain time stamps. We had to be able to provide binary compatibility so applications written for the old way would work. Luckily I was able to get enough data into the release notes so I could get my new utmp library code done in the next release. Making the change is not hard, but making it binary compatible is much more complex. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Anders Johansson

22:18

On Tuesday 11 December 2007 22:57:43 Jerry Feldman wrote:

...

On Sun, 9 Dec 2007 13:47:50 +0100

Anders Johansson wrote:

...
On Friday 07 December 2007 22:03:40 Aaron Kulkis wrote:

...
Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...
On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes.

Unix Time starts with t=0 seconds at 00:00, between 31 Dec 1969 and 01 Jan 1970, which is also knows as "the epoch."

System time is an unsigned 32-bit number representing the number of seconds since "the epoch."

32-bit time will run out sometime in 2038. This gives us 31 years to convert to 64-bit time.

Actually it's a signed long, which means 2147483647 seconds, or just over 68 years. An unsigned value would be about twice that

Actually you are wrong. The Unix 95 standard required a signed int not a signed long.

I was using the present tense. Look around in /usr/include. I dare you to find one single instance of time_t that is not a signed long __kernel_time_t is signed long __time_t is __TIME_T_TYPE, which is __SLONGWORD_TYPE, which is signed long time_t is either of the above depending on which include file you look at, but it doesn't really matter since they are defined the same What I said was "it is a signed long". What you say is "it was a signed int". Sure, it was, and we may have to convert older systems at some point, but that's a whole other story

...

There was a big todo about converting to 64-bit time in the Unix 98 standard. The problem with many vendors was binary compatibility. I was involved in this for Tru64 Unix as if affected the Utmp/Utmpx libraries since the utmp and wtmp files contain time stamps. We had to be able to provide binary compatibility so applications written for the old way would work. Luckily I was able to get enough data into the release notes so I could get my new utmp library code done in the next release. Making the change is not hard, but making it binary compatible is much more complex.

Of course. Any change in the ABI-exposed functions is difficult. Usually vendors take the easy way out and introduce new functions (foo() versus foo64 (), for example) Anders -- Madness takes its toll -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott

9 Dec 9 Dec

14:09

Aaron Kulkis wrote:

...

Carlos E. R. wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Friday 2007-11-30 at 22:22 -0600, Bryen wrote:

...
On Sat, 2007-12-01 at 05:00 +0100, Carlos E. R. wrote:

...
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

That's very cool. What does the first column represent? I'm assuming it is install time based on unix time?

Some internal time representation, I think seconds from certain date which I think is called unix time, yes.

Unix Time starts with t=0 seconds at 00:00, between 31 Dec 1969 and 01 Jan 1970, which is also knows as "the epoch."

System time is an unsigned 32-bit number representing the number of seconds since "the epoch."

32-bit time will run out sometime in 2038.

Oh no!!! What happens when we run out of time??? Will the universe end??? ;-) -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Theo v. Werkhoven

10 Dec 10 Dec

21:32

Sun, 09 Dec 2007, by james.knott@rogers.com:

...

Aaron Kulkis wrote:

...
Carlos E. R. wrote: [..] 32-bit time will run out sometime in 2038.

Oh no!!! What happens when we run out of time??? Will the universe end??? ;-)

Big party at Milliways. Deposit 1 penny now, to pay for all future expenses. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.3 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.22 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Ken Schneider

1 Dec 1 Dec

04:31

Carlos E. R. pecked at the keyboard and wrote:

...

The Friday 2007-11-30 at 21:06 -0500, Chris Arnold wrote:

...
How can i find the packages that were updated then back date to those packages that are on the disc? I alt-cntrl-f5 to get the CL and tried to uninstall gconf2 but get a slew of dependency errors.

"rpm -q -a --last | less", for instance. But I prefer this:

rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE} \ %25{PACKAGER}\n" | sort | less -S

To install "older" versions from the DVD you will have to "force" them.

-- Cheers, Carlos E. R.

Even better is to use --oldpackage instead of force. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

13:39

...

To install "older" versions from the DVD you will have to "force" them. I still get dependency errors when using rpm --force -Uvh <filename>. Is

Carlos E. R. wrote: that syntax correct? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

14:14

Chris Arnold wrote:

...

Carlos E. R. wrote:

...
To install "older" versions from the DVD you will have to "force" them. I still get dependency errors when using rpm --force -Uvh <filename>. Is that syntax correct?

Actually, tht was the wrong syntax. It should look something like this: rpm -i --force <filename> After running the above command and reinstalling gconf2 and gconf2-devel, i am now able to login to the desktop. I do get the attached error and the gnome panel will not start. Any ideas?

Carlos E. R.

16:03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-12-01 at 09:14 -0500, Chris Arnold wrote:

...

Actually, tht was the wrong syntax. It should look something like this: rpm -i --force <filename>

After running the above command and reinstalling gconf2 and gconf2-devel, i am now able to login to the desktop. I do get the attached error and the gnome panel will not start. Any ideas?

Have you checked if you still have "updated" rpms you haven't replaced with the originals yet? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHUYXbtTMYHG2NR9URAnDKAKCFSNE7Ysu602pL+Js/3lR7UxyBQgCfdRPl DsS+mcDe7LAwJYxYYql5eAM= =NQOo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Arnold

2 Dec 2 Dec

12:18

New subject: [opensuse] [SOLVED}I should have known!

Carlos E. R. wrote:

...

Have you checked if you still have "updated" rpms you haven't replaced with the originals yet? Yes and there were 2 packages still installed but removing them did not fix the problem. I ended up installing older gstreamer packages and now i have my SLED install back and all is well! Thanks guys -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5985

Age (days ago)

5995

Last active (days ago)

List overview

Download

16 comments

10 participants

participants (10)

Aaron Kulkis
Anders Johansson
Bryen
Carlos E. R.
Chris Arnold
James Knott
Jerry Feldman
Ken Schneider
Theo v. Werkhoven
Wolfgang Rosenauer