portmaster 2.23, missing ORGIN
in [Ports]
|
From: Jakub Lach on 1 May 2010 08:12 Hello. Since upgrade to 2.23 portmaster is complaining about ORGIN e.g. $ portmaster --check-port-dbdir ===>>> No ORIGIN in /var/db/pkg/pkgdb.db/+CONTENTS Is this expected behaviour? regards, -Jakub Lach -- View this message in context: http://old.nabble.com/portmaster-2.23%2C-missing-ORGIN-tp28420424p28420424.html Sent from the freebsd-ports mailing list archive at Nabble.com. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Peter Jeremy on 1 May 2010 16:25 On 2010-May-01 05:12:13 -0700, Jakub Lach <jakub_lach(a)mailplus.pl> wrote: >Since upgrade to 2.23 portmaster is complaining >about ORGIN e.g. > >$ portmaster --check-port-dbdir > >===>>> No ORIGIN in /var/db/pkg/pkgdb.db/+CONTENTS > >Is this expected behaviour? Have you switched from portupgrade and not deleted the associated metadata files? You should not have a port named pkgdb.db so it is not surprising that /var/db/pkg/pkgdb.db/+CONTENTS would not have an ORIGIN. Do you actually have a /var/db/pkg/pkgdb.db/+CONTENTS? Does the problem exist with any real ports? Does the problem go away if you delete /var/db/pkg/pkgdb.db? I agree that portmaster shouldn't choke on files in /var/db/pkg, but at least there is a fairly easy workaround. -- Peter Jeremy
From: Doug Barton on 1 May 2010 16:29 On 05/01/10 05:12, Jakub Lach wrote: > > Hello. > > Since upgrade to 2.23 portmaster is complaining > about ORGIN e.g. > > > $ portmaster --check-port-dbdir > > ===>>> No ORIGIN in /var/db/pkg/pkgdb.db/+CONTENTS > > Is this expected behaviour? Nope, but the good news is that it's harmless. Previously the origin_from_pdb() function didn't return an error, so the --check-port-dbdir feature didn't need to check if what it was working on is a directory. Now it does, so you can apply the attached patch if that message bothers you. I checked the other places that origin_from_pdb() is called and this seems to be the only place that this would be an issue. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/
From: Jakub Lach on 1 May 2010 16:42 Peter Jeremy-6 wrote: > > > Have you switched from portupgrade and not deleted the associated metadata > files? You should not have a port named pkgdb.db so it is not surprising > that /var/db/pkg/pkgdb.db/+CONTENTS would not have an ORIGIN. > > Thanks for help. Indeed file is from portupgrade and quite stale too. I should check it's content before assuming it's used by portmaster. What fooled me is that earlier portmaster versions didn't complain about this file and I thought portupgrade would delete it's database upon deinstall (which can be preferred behaviour as we see). I should add that this warning didn't stop portmaster from working. best regards, -Jakub Lach -- View this message in context: http://old.nabble.com/portmaster-2.23%2C-missing-ORGIN-tp28420424p28423155.html Sent from the freebsd-ports mailing list archive at Nabble.com. _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Doug Barton on 1 May 2010 18:23 On 05/01/10 13:42, Jakub Lach wrote: > > > > Peter Jeremy-6 wrote: >> >> >> Have you switched from portupgrade and not deleted the associated metadata >> files? You should not have a port named pkgdb.db so it is not surprising >> that /var/db/pkg/pkgdb.db/+CONTENTS would not have an ORIGIN. >> >> > > Thanks for help. > > Indeed file is from portupgrade and quite stale too. I should check it's > content before assuming it's used by portmaster. It is not used by portmaster, it can be safely deleted. Even if you start using portupgrade again, it will have to be rebuilt anyway. There is no reason you cannot have portmaster + some other ports management tool (like portupgrade) installed. The only thing you can't do is run them simultaneously (i.e., at the exact same time). You can easily upgrade one thing with portmaster, then when portmaster exits update something else with another tool. > What fooled me is that earlier portmaster versions didn't complain > about this file I explained that in my previous post, if the explanation isn't clear, let me know. Meanwhile, thanks for bringing this to my attention. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Next
|
Last
Pages: 1 2 Prev: russianukrainiandating.com mailing list memberships reminder Next: new port config in /etc? |