Re: error when pkg_add'ing

2023-07-02 Thread Marc Espie
On Tue, Jun 27, 2023 at 08:56:41PM +0100, li...@xza.fr wrote:
> > Having A LOTS of problems in pkg_check usually means something in your
> > process is REALLY BAD.
> > 
> > As the guy who wrote (most of) pkg_add/pkg_check, I don't need pkg_check
> > all that often.
> 
> 
> Just wanted to say: thanks for writing pkg_add.
> 
> Don't know if it was by you, but also really appreciated also that 
> semi-recent 
> update to pkg_add which made package updates (pkg_add -u) significantly 
> faster.
> 
> 
Yeah, it was a really fun one to write.

I should talk about the technical details at eurobsdcon in coimbra
next september



Re: error when pkg_add'ing

2023-06-27 Thread lists
> Having A LOTS of problems in pkg_check usually means something in your
> process is REALLY BAD.
> 
> As the guy who wrote (most of) pkg_add/pkg_check, I don't need pkg_check
> all that often.


Just wanted to say: thanks for writing pkg_add.

Don't know if it was by you, but also really appreciated also that semi-recent 
update to pkg_add which made package updates (pkg_add -u) significantly faster.



Re: error when pkg_add'ing

2023-06-26 Thread Stuart Henderson
On 2023-06-24, Pau A.S.  wrote:
> I recently reported what I thought it was a FS corruption because the
> system (-current) was crashing when I was setting a picture or movie on
> full screen. For some reason, the fix is to use xcompmgr in .xsession.

I think you have multiple issues here.

> No pkgname in packing-list for uchardet-0.0.8
> No pkgname in packing-list for grilo-0.3.16
> No pkgname in packing-list for liboauth-1.0.3
> quirks-6.133->6.133: ok
> Can't install python-3.10.12 because of libraries
>|library util.17.0 not found
>| /usr/lib/libutil.so.16.0 (system): bad major

This is "base is too old for the packages you're trying to use".
Running -current, you need to keep on top of updates to both base
and packages, and occasionally there will be times where things
aren't working because something in base has been updated but
there's no new package set available yet (not the case here).

> 75%/usr/local/share/glib-2.0/schemas/org.gnome.totem.enums.xml:1:1  Error
> on line 1 char 1: Document must begin with an element (e.g. ).  This
> entire file has been ignored.
> /usr/local/share/glib-2.0/schemas/org.gnome.online-accounts.gschema.xml:1:1
>  Error on line 1 char 1: Document must begin with an element (e.g.
>).  This entire file has been ignored.

That file seems corrupt

> There seems to be some corruption in that file:
>
> -
> # cat /usr/local/share/applications/org.gnome.Adwaita1.Demo.desktop
> �   recode.mo�WebKitGTK-4.1.mo�eog.mo�vlc.mo
> gimp30-libgimp.mo
> xfce4-panel.mo
> �#

yes that's definitely corrupt

> I have been seeing a lot of crashes of other programs.
[...]
> OpenBSD 7.3-current (GENERIC.MP) #1246: Fri Jun 16 23:57:46 MDT 2023
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
[...]
> cpu0: 12th Gen Intel(R) Core(TM) i7-1255U, 1615.02 MHz, 06-9a-04
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES

This cpu has IBT in the features line. A diff is being tested in
some snapshots to enable this (it's a control-flow protection feature
in the cpu). Some software is not yet compatible with this and the
relevant ports need to be updated to either patch them to make them
compatible, or disable enforcement of control-flow protection when the
binaries from that port are run. Typically you will see "Illegal
instruction" messages in that case.

> What I did then was to copy the contents of /local/usr somewhere else, I
> ran newfs on it by booting as a single user and restored the contents. This
> didn't fix the error, so it is not a FS problem.

err, if the filesystem is corrupt, copying the (already corrupt)
contents elsewhere, and copying them back again, isn't going
to fix things.

> acpicpu11 at acpi0: C3(200@1048 mwait.1@0x60), C2(350@127 mwait.1@0x21),
> C1(1000@1 mwait.1), PSS
> acpicpu12 at acpi0: no cpu matching ACPI ID 12
> acpicpu13 at acpi0: no cpu matching ACPI ID 13
...
> acpicpu62 at acpi0: no cpu matching ACPI ID 62
> acpicpu63 at acpi0: no cpu matching ACPI ID 63

that's "interesting" :)



-- 
Please keep replies on the mailing list.



Re: error when pkg_add'ing

2023-06-25 Thread Marc Espie
On Sat, Jun 24, 2023 at 06:44:11PM +0200, Pau A.S. wrote:
> thanks so much, Marcus; pkg_check helped to identify a LOT of corrupted
> files, which I deleted; after that I ran pkg_add -vu and it looks that one
> file survived:

Having A LOTS of problems in pkg_check usually means something in your
process is REALLY BAD.

As the guy who wrote (most of) pkg_add/pkg_check, I don't need pkg_check
all that often.

And it's mostly because of flakiness in the base system!!!
if you end up fixing A LOT through pkg_check, it means
that SOMETHING ELSE is usually wrong.



Re: error when pkg_add'ing

2023-06-24 Thread Pau A.S.
thanks so much, Marcus; pkg_check helped to identify a LOT of corrupted
files, which I deleted; after that I ran pkg_add -vu and it looks that one
file survived:


usr/local/share/glib-2.0/schemas/org.gnome.totem.enums.xml:1:1  Error on
line 1 char 1: Document must begin with an element (e.g. ).  This
entire file has been ignored.
/usr/local/share/glib-2.0/schemas/org.gnome.online-accounts.gschema.xml:1:1
 Error on line 1 char 1: Document must begin with an element (e.g.
).  This entire file has been ignored.
/usr/local/share/glib-2.0/schemas/org.gnome.totem.gschema.xml:1:1  Error on
line 1 char 1: Document must begin with an element (e.g. ).  This
entire file has been ignored.
/usr/local/share/glib-2.0/schemas/org.gnome.totem.plugins.opensubtitles.gschema.xml:1:1
 Error on line 1 char 1: Document must begin with an element (e.g.
).  This entire file has been ignored.
/usr/local/share/glib-2.0/schemas/org.gnome.totem.plugins.pythonconsole.gschema.xml:1:1
 Error on line 1 char 1: Document must begin with an element (e.g.
).  This entire file has been ignored.


 |100%Could not
parse file "/usr/local/share/applications/org.gnome.Adwaita1.Demo.desktop":
Key file contains line recode.mo??
WebKitGTK-4.1.mo???eog.mo?vlc.mo??
  ??gimp30-libgimp.mo which is not a key-value pair, group,
or comment
Could not parse file
"/usr/local/share/applications/org.gnome.RestDemo.desktop": Key file
contains line
?S7_S2_ZN6Window8MainMenuC1EP7QWidgetN3gsl8not_nullIPNS8_17SessionController3$_8ZNS0_orIS7_S2_NS0_29combine_implementation_helperIJNS_?
which is not a key-value pair, group, or comment
-

I will sysupgrade now and re-run pkg_check and pkg_add -vu

thanks again

Missatge de Marcus MERIGHI  del dia ds., 24 de juny
2023 a les 13:52:

> Hello Pau,
>
> lamarededeusen...@googlemail.com (Pau A.S.), 2023.06.24 (Sat) 12:16
> (CEST):
>
> [...]
>
> > In any case, I noticed that when running pkg_add I was finding some
> strange
> > error messages such as:
> >
> > 
> > # pkg_add -u firefox
> > quirks-6.133 signed on 2023-06-23T22:56:27Z
> > No pkgname in packing-list for totem-pl-parser-3.26.6p1
> > No pkgname in packing-list for gom-0.4p1
> > No pkgname in packing-list for libdmapsharing4-3.9.12p0
> > No pkgname in packing-list for libadwaita-1.3.2p0v0
> > No pkgname in packing-list for gnome-online-accounts-3.48.0p0
> > No pkgname in packing-list for libmediaart-1.9.6p0
> > No pkgname in packing-list for uchardet-0.0.8
> > No pkgname in packing-list for grilo-0.3.16
> > No pkgname in packing-list for liboauth-1.0.3
> > quirks-6.133->6.133: ok
> > Can't install python-3.10.12 because of libraries
> > |library util.17.0 not found
> > | /usr/lib/libutil.so.16.0 (system): bad major
>
> For reference, I have, on a machine upgraded to current -current 12
> hours ago:
>
> $ ls -la /usr/lib/libutil.so.*
> -r--r--r--  1 root  bin  222672 Jun 16 16:11 /usr/lib/libutil.so.16.0
> -r--r--r--  1 root  bin  240048 Jun 23 16:51 /usr/lib/libutil.so.17.0
>
> If I were you I'd do a sysupgrade(8) and retry "pkg_add(1) -u"
> afterwards. I'd run pkg_check(8) too, just to be sure.
>
> Marcus
>


Re: error when pkg_add'ing

2023-06-24 Thread Marcus MERIGHI
Hello Pau, 

lamarededeusen...@googlemail.com (Pau A.S.), 2023.06.24 (Sat) 12:16 (CEST):

[...]

> In any case, I noticed that when running pkg_add I was finding some strange
> error messages such as:
> 
> 
> # pkg_add -u firefox
> quirks-6.133 signed on 2023-06-23T22:56:27Z
> No pkgname in packing-list for totem-pl-parser-3.26.6p1
> No pkgname in packing-list for gom-0.4p1
> No pkgname in packing-list for libdmapsharing4-3.9.12p0
> No pkgname in packing-list for libadwaita-1.3.2p0v0
> No pkgname in packing-list for gnome-online-accounts-3.48.0p0
> No pkgname in packing-list for libmediaart-1.9.6p0
> No pkgname in packing-list for uchardet-0.0.8
> No pkgname in packing-list for grilo-0.3.16
> No pkgname in packing-list for liboauth-1.0.3
> quirks-6.133->6.133: ok
> Can't install python-3.10.12 because of libraries
> |library util.17.0 not found
> | /usr/lib/libutil.so.16.0 (system): bad major

For reference, I have, on a machine upgraded to current -current 12
hours ago:

$ ls -la /usr/lib/libutil.so.*
-r--r--r--  1 root  bin  222672 Jun 16 16:11 /usr/lib/libutil.so.16.0
-r--r--r--  1 root  bin  240048 Jun 23 16:51 /usr/lib/libutil.so.17.0

If I were you I'd do a sysupgrade(8) and retry "pkg_add(1) -u"
afterwards. I'd run pkg_check(8) too, just to be sure.

Marcus