Re: annoying problems after upgrading to 6.2-RELEASE
Scott Bennett wrote: On Fri, 27 Apr 2007 02:38:31 -0400 quoth Kris Kennaway <[EMAIL PROTECTED]>: Please note that I posted the first two items merely to inform the readership of the existence of the problems. I only hoped for assistance on the third problem. Now, given that you are among the core ports team members, perhaps you would enlighten me as to which indicators pkg_add uses and which indicators pkg_delete uses to decide whether a particular package or port is already installed. With that information in mind, I might be able to fix the problem by hand. Perhaps you could also explain the rationale behind having them both not use the same indicators, too, so that it might not simply appear to me to be a glaring design error. Check into /var/db/pkg if you wish. All of the installed pkg data is kept there. I agree though with Kris. This email chain's a mess.. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: annoying problems after upgrading to 6.2-RELEASE
On Fri, 27 Apr 2007 02:38:31 -0400 quoth Kris Kennaway <[EMAIL PROTECTED]>: >--9jxsPFA5p3P2qPhR >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Thu, Apr 26, 2007 at 11:30:20PM -0500, Scott Bennett wrote: >> On Thu, 26 Apr 2007 23:13:40 -0400 Kris Kennaway <[EMAIL PROTECTED] >g> >> wrote: >>=20 >> >Mime-Version: 1.0 >> >Content-Disposition: inline >> >User-Agent: Mutt/1.4.2.2i >> > >> > >> >--BOKacYhQ+x31HxR3 >> >Content-Type: text/plain; charset=3Dus-ascii >> >Content-Disposition: inline >> >Content-Transfer-Encoding: quoted-printable >> > >> >On Thu, Apr 26, 2007 at 08:51:50PM -0500, Scott Bennett wrote: >> >> I've encountered three annoying problems since doing the upgrade = >from >> >> 6.1-RELEASE to 6.2-RELEASE using the upgrade option when booting from = >the >> >> installation CD. This is on a Dell Inspiron XPS (3.4 GHz P4 w/HTT ena= >bled >> >> and 1 GB of memory). >> >>=3D20 >> >> 1) The ports and packages subsystems are as fragile as ever (no big >> >> surprise). I was able to add packages for less than a day before >> >> it broke. Sometimes I can still add or delete a package, but >> >> in at least one case, I can't because pkg_add says that an earlier >> >> version of the package is already installed, while an attempt to >> >> remove the earlier version using pkg_delete gets a message saying >> >> that no such package is installed. Apparently, pkg_add and >> >> pkg_delete do not refer to the same indicators of whether a >> >> particular package is actually installed. Attempting to build por= >ts >> >> fails while trying to build dependency ports, which was what led >> >> to attempt to remove libtool and then add the newer version. I'll >> >> try to get a PR together and submitted soon. >> > >> >It is recommended to use an upgrade tool like portupgrade instead of >> >trying to use pkg_add/pkg_delete "by hand". It is too easy to misuse >>=20 >> portinstall/portupgrade had failed to install/upgrade certain ports = >or >> packages to satisfy the dependencies in the ports I was trying to install= > or >> upgrade. I really did want to install or upgrade several ports, and so I= > had >> begun attempting to install the required (or later) versions of the >> prerequisites as packages in order to get around the build failures. > >It sounds like you may not have succeeded in first bringing your >system back to a sane state. Anyway, if you have problems please be >more explicit here. Please note that I posted the first two items merely to inform the readership of the existence of the problems. I only hoped for assistance on the third problem. Now, given that you are among the core ports team members, perhaps you would enlighten me as to which indicators pkg_add uses and which indicators pkg_delete uses to decide whether a particular package or port is already installed. With that information in mind, I might be able to fix the problem by hand. Perhaps you could also explain the rationale behind having them both not use the same indicators, too, so that it might not simply appear to me to be a glaring design error. > >> >them and leave your system in an inconsistent state, as yours >> >apparently has become. >>=20 >> That sounds to me like an attempt to skate past my observation that >> "Apparently, pkg_add and pkg_delete do not refer to the same indicators of >> whether a particular package is actually installed." > >Well, they don't...please paste an appropriate transcript if you think >there is a bug. > >> BTW, it is recommended that plain, ASCII text be posted to mailing >> lists, so as not to send lots of garbage to people who may or may not be >> using MIME-oriented mail interfaces or using MIME-oriented mail interfaces >> whose version of MIME is incapatible with that of the sender's mail inter= >face. > >Uh thanks. Read up on "PGP signatures" sometime. Well, it's true that I haven't used PGP for a few years now. However, every version of PGP that I did use was perfectly able to sign a cleartext file by placing a header line at the start of the file and a trailer line at the end of the file, followed by a PGP signature block. IIRC, the options to do that were -sat. It was never necessary to use MIME to send a signed message to a mailing list. I note that your signature block, quoted below, says it was produced by GnuPG, *not* PGP. I haven't used GnuPG and am therefore not familiar with its abilities or deficiencies. In any case, MIME is bad for mailing lists. > >Kris > >--9jxsPFA5p3P2qPhR >Content-Type: application/pgp-signature >Content-Disposition: inline > >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.4.7 (FreeBSD) > >iD8DBQFGMZpnWry0BWjoQKURAvJ3AKCgd4icbHqQDCTALWZiIhyV7i1KRwCdEvHx >hprMUzPT62J6QjsEnpC4PhA= >=IBUj >-END PGP SIGNATURE- > >--9jxsPFA5p3P2qPhR-- > I post only infreque
Re: annoying problems after upgrading to 6.2-RELEASE
On Thu, Apr 26, 2007 at 11:30:20PM -0500, Scott Bennett wrote: > On Thu, 26 Apr 2007 23:13:40 -0400 Kris Kennaway <[EMAIL PROTECTED]> > wrote: > > >Mime-Version: 1.0 > >Content-Disposition: inline > >User-Agent: Mutt/1.4.2.2i > > > > > >--BOKacYhQ+x31HxR3 > >Content-Type: text/plain; charset=us-ascii > >Content-Disposition: inline > >Content-Transfer-Encoding: quoted-printable > > > >On Thu, Apr 26, 2007 at 08:51:50PM -0500, Scott Bennett wrote: > >> I've encountered three annoying problems since doing the upgrade from > >> 6.1-RELEASE to 6.2-RELEASE using the upgrade option when booting from the > >> installation CD. This is on a Dell Inspiron XPS (3.4 GHz P4 w/HTT enabled > >> and 1 GB of memory). > >>=20 > >>1) The ports and packages subsystems are as fragile as ever (no big > >> surprise). I was able to add packages for less than a day before > >> it broke. Sometimes I can still add or delete a package, but > >> in at least one case, I can't because pkg_add says that an earlier > >> version of the package is already installed, while an attempt to > >> remove the earlier version using pkg_delete gets a message saying > >> that no such package is installed. Apparently, pkg_add and > >> pkg_delete do not refer to the same indicators of whether a > >> particular package is actually installed. Attempting to build ports > >> fails while trying to build dependency ports, which was what led > >> to attempt to remove libtool and then add the newer version. I'll > >> try to get a PR together and submitted soon. > > > >It is recommended to use an upgrade tool like portupgrade instead of > >trying to use pkg_add/pkg_delete "by hand". It is too easy to misuse > > portinstall/portupgrade had failed to install/upgrade certain ports or > packages to satisfy the dependencies in the ports I was trying to install or > upgrade. I really did want to install or upgrade several ports, and so I had > begun attempting to install the required (or later) versions of the > prerequisites as packages in order to get around the build failures. It sounds like you may not have succeeded in first bringing your system back to a sane state. Anyway, if you have problems please be more explicit here. > >them and leave your system in an inconsistent state, as yours > >apparently has become. > > That sounds to me like an attempt to skate past my observation that > "Apparently, pkg_add and pkg_delete do not refer to the same indicators of > whether a particular package is actually installed." Well, they don't...please paste an appropriate transcript if you think there is a bug. > BTW, it is recommended that plain, ASCII text be posted to mailing > lists, so as not to send lots of garbage to people who may or may not be > using MIME-oriented mail interfaces or using MIME-oriented mail interfaces > whose version of MIME is incapatible with that of the sender's mail interface. Uh thanks. Read up on "PGP signatures" sometime. Kris pgpVSMboRh1AH.pgp Description: PGP signature
Re: annoying problems after upgrading to 6.2-RELEASE
On Thu, 26 Apr 2007 23:13:40 -0400 Kris Kennaway <[EMAIL PROTECTED]> wrote: >Mime-Version: 1.0 >Content-Disposition: inline >User-Agent: Mutt/1.4.2.2i > > >--BOKacYhQ+x31HxR3 >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Thu, Apr 26, 2007 at 08:51:50PM -0500, Scott Bennett wrote: >> I've encountered three annoying problems since doing the upgrade from >> 6.1-RELEASE to 6.2-RELEASE using the upgrade option when booting from the >> installation CD. This is on a Dell Inspiron XPS (3.4 GHz P4 w/HTT enabled >> and 1 GB of memory). >>=20 >> 1) The ports and packages subsystems are as fragile as ever (no big >> surprise). I was able to add packages for less than a day before >> it broke. Sometimes I can still add or delete a package, but >> in at least one case, I can't because pkg_add says that an earlier >> version of the package is already installed, while an attempt to >> remove the earlier version using pkg_delete gets a message saying >> that no such package is installed. Apparently, pkg_add and >> pkg_delete do not refer to the same indicators of whether a >> particular package is actually installed. Attempting to build ports >> fails while trying to build dependency ports, which was what led >> to attempt to remove libtool and then add the newer version. I'll >> try to get a PR together and submitted soon. > >It is recommended to use an upgrade tool like portupgrade instead of >trying to use pkg_add/pkg_delete "by hand". It is too easy to misuse portinstall/portupgrade had failed to install/upgrade certain ports or packages to satisfy the dependencies in the ports I was trying to install or upgrade. I really did want to install or upgrade several ports, and so I had begun attempting to install the required (or later) versions of the prerequisites as packages in order to get around the build failures. >them and leave your system in an inconsistent state, as yours >apparently has become. That sounds to me like an attempt to skate past my observation that "Apparently, pkg_add and pkg_delete do not refer to the same indicators of whether a particular package is actually installed." BTW, it is recommended that plain, ASCII text be posted to mailing lists, so as not to send lots of garbage to people who may or may not be using MIME-oriented mail interfaces or using MIME-oriented mail interfaces whose version of MIME is incapatible with that of the sender's mail interface. > >Kris >--BOKacYhQ+x31HxR3 >Content-Type: application/pgp-signature >Content-Disposition: inline > >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.4.7 (FreeBSD) > >iD8DBQFGMWpkWry0BWjoQKURAkkVAJ9wvha6XJpjYLVfEL2yv5MhPh/YmwCgxPCg >Uxfqmp633xMmPXCnamZtNZQ= >=rCHk >-END PGP SIGNATURE- > >--BOKacYhQ+x31HxR3-- > Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: annoying problems after upgrading to 6.2-RELEASE
On Thu, Apr 26, 2007 at 08:51:50PM -0500, Scott Bennett wrote: > I've encountered three annoying problems since doing the upgrade from > 6.1-RELEASE to 6.2-RELEASE using the upgrade option when booting from the > installation CD. This is on a Dell Inspiron XPS (3.4 GHz P4 w/HTT enabled > and 1 GB of memory). > > 1) The ports and packages subsystems are as fragile as ever (no big > surprise). I was able to add packages for less than a day before > it broke. Sometimes I can still add or delete a package, but > in at least one case, I can't because pkg_add says that an earlier > version of the package is already installed, while an attempt to > remove the earlier version using pkg_delete gets a message saying > that no such package is installed. Apparently, pkg_add and > pkg_delete do not refer to the same indicators of whether a > particular package is actually installed. Attempting to build ports > fails while trying to build dependency ports, which was what led > to attempt to remove libtool and then add the newer version. I'll > try to get a PR together and submitted soon. It is recommended to use an upgrade tool like portupgrade instead of trying to use pkg_add/pkg_delete "by hand". It is too easy to misuse them and leave your system in an inconsistent state, as yours apparently has become. Kris pgpWpAay2u7Zd.pgp Description: PGP signature
annoying problems after upgrading to 6.2-RELEASE
I've encountered three annoying problems since doing the upgrade from 6.1-RELEASE to 6.2-RELEASE using the upgrade option when booting from the installation CD. This is on a Dell Inspiron XPS (3.4 GHz P4 w/HTT enabled and 1 GB of memory). 1) The ports and packages subsystems are as fragile as ever (no big surprise). I was able to add packages for less than a day before it broke. Sometimes I can still add or delete a package, but in at least one case, I can't because pkg_add says that an earlier version of the package is already installed, while an attempt to remove the earlier version using pkg_delete gets a message saying that no such package is installed. Apparently, pkg_add and pkg_delete do not refer to the same indicators of whether a particular package is actually installed. Attempting to build ports fails while trying to build dependency ports, which was what led to attempt to remove libtool and then add the newer version. I'll try to get a PR together and submitted soon. 2) I had been eagerly awaiting the new version of snd_emu10k1, which is supposed to contain support for the Soundblaster Audigy 2 cards, and I was hoping that my Soundblaster Audigy 2 ZS PCMCIA card might be included in that support. Last night I finally added snd_driver_load="YES" to /boot/loader.conf and rebooted. It looked good until it correctly identifed the card, at which point it hung. After some delay, the machine *powered itself down*. Trying to restart it failed repeatedly before it could complete the hardware initialization prior to booting, and it powered itself down each time, sometimes turning on the battery light briefly as it did so. Eventually, fearing hardware damage, I removed the PCMCIA card, after which I was able to boot the installation CD again in order to remove the line from /boot/loader.conf. Unfortunately, the 6.2-RELEASE installation CD does not allow me to mount the hard drive's root file system onto /mnt in order to change the hard drive's /boot/loader.conf file the way the 6.1-RELEASE CD did. I next tried booting from the hard drive, selecting safe mode-- which may not have mattered anyway--I think the key was removing the sound card, and got to where I could edit the file. Rebooting after that proceeded uneventfully. Because of the computer's thoroughly bizarre response to having the new snd_emu10k1 driver active when the sound card was present, I am reluctant to try this again to document it well enough to submit a PR. I haven't yet tried the $100 sound card again under Windows XP to find out whether it still works. 8-| 3) I use wmaker as a window manager for X. Since the 6.2-RELEASE upgrade, I seem no longer able to cut/copy + paste anything except when doing the operation entirely inside Firefox windows. I can still select the text I want to copy, but I am unable to paste it into other windows (e.g., Putty, xterm) or even into the same window. The first two I don't expect to be able to do anything about, other than maybe submitting a PR for the first one, but perhaps someone can show me a way to fix the third one. Any help would be appreciated. Thanks muchly in advance. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
