As I was updated my Archlinux - with testing repositories enabled - installation something like an hour ago, I faced a conflict in xorg packages.
After doing some search, I found a bug related to obsolete package removal and a mailing list post.
Bug report: https://bugs.archlinux.org/task/64892
Mailing list post: https://lists.archlinux.org/pipermail/arch-general/2019-December/047247.html
Removed packages (some other packages were rebuilt):
- xf86miscproto yes, in xorgproto package
- libxxf86misc yes
- xf86dgaproto yes, in xorgproto package
- libxxf86dga yes
- libxkbui yes
- libdmx
Donât know if there are used in EndeavourOS installation. Juste wanted to warn everybody.
Edit: on classical installation, libdmx is now an orphaned package.
Missing libdmx package warning.
But removing it breaks screenfetch, so keep libdmx until xorg update is push on stable repositories.
Broken screenfetch install
Upgrading using testing repositories - which I do not tell you to do on real hardware - and everything goes well. No file conflicts after removing libdmx. So Xorg cleanup in testing should work ok.
4 Likes
manuel
December 19, 2019, 10:46pm
#2
Thanks for the warning!
BTW, are you using all Arch testing repos, or just the [testing]?
1 Like
Iâm using all testing repositories. And keeping both libdmx and libxxf86dga (needed by screenfetch?) =
I hope Archlinux maintainer will fix this soon
A workaround to test: uninstall screenfetch, upgrade and install it back again?
manuel
December 19, 2019, 10:56pm
#4
I also had the [testing] repo (only) active on one machine, and it showed the same problem. Lazy as I was, didnât study it but simply disabled the testing repo and downgraded back to normal.
I guess theyâll fix it, or we have a problem coming.
They will fix it They will right?!?
manuel:
I also had the [testing] repo (only) active on one machine, and it showed the same problem. Lazy as I was, didnât study it but simply disabled the testing repo and downgraded back to normal.
I guess theyâll fix it, or we have a problem coming.
Iâll try âremoving screenfetchâ workaround as soon as possible. But I think Archlinux developer will fix issues on xorg cleanup and upgrade. Well, I hope.
They will. I hope
Looking at archlinux bug , rebuilds are being made. Letâs keep fingers crossed
Well, I was like @manuel I reverted back and uncommented the testing repo and Iâm going to wait a few days when that one hits stable.
So⌠donât update until someone on here say it works for sure?
axt
December 20, 2019, 7:12am
#10
The problem still exists. To be able to run other updates, at the moment I have xorgproto set to ignore in â/etc/pacman.confâ:
IgnorePkg = xorgproto
Just look at bug in the first post. It is a work in progress. Some other packages needs to be rebuild, like the ones depending on libxxf86dga (or something like this).
Tweaking IgnorePKG line is a short time answer. I have to do so on my archlinux + testing because of this samba bug: https://bugs.archlinux.org/task/64537
axt
December 20, 2019, 7:37am
#12
Therefore on IgnorePkg. This not only keeps the named package, but also its dependencies.
The alternative would be until the fix:
no updates at all or
picking out updates individually
axt:
Therefore on IgnorePkg. This not only keeps the named package, but also its dependencies.
The alternative would be until the fix:
no updates at all or
picking out updates individually
There is another way to do thing clean:
removing screenfetch
upgrade
reinstall screenfetch
screenfetch dependency xorg-xpdyinfo needs libxxf86dga which will be removed.
First screenshot: removing screenfetch on an EndeavourOS âstableâ.
Screenshot #2: after testing upgrade, installing back screenfetch.
You can see xorg-xpdyinfo move from version 1.3.2-2 to 1.3.2-3
Commit related to 1.3.2-3 version: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/xorg-xdpyinfo&id=63a049668ccb1f38c52dc6fe252d099197eb70c4
So
I also find this interesting bug report related to screenfetch: https://bugs.archlinux.org/task/58279 -> âset âxorg-xdpyinfoâ and âxorg-xpropâ as optdependsâ
2 Likes
manuel
December 20, 2019, 10:01am
#14
âHouston, we have a problem.â
Fortunately not yet, but letâs keep our eyes open.
2 Likes
manuel:
âHouston, we have a problem.â
Fortunately not yet, but letâs keep our eyes open.
And wait for Archlinux developers to finish their work.
It is âHouston, weâve had a problemâ. See https://en.wikipedia.org/wiki/Houston,_we_have_a_problem
2 Likes
This morning i had 31 updates and it wouldnât update. I just didnât update xorgproto and the other updates installed. I then removed the currently installed xorgproto and reinstalled it.
manuel
December 20, 2019, 3:00pm
#17
1 Like
Does this mean i should remove and leave removed the xorgproto package? I reinstalled it after the update.
manuel
December 20, 2019, 3:02pm
#19
Donât know. But Arch just had this on their pages.
FLVAL
December 20, 2019, 3:07pm
#20
Yes, the details from the remove dead Xorg packages here :
https://bugs.archlinux.org/task/64892
xorgproto
remove provides/conflicts/replaces on =(âbigreqsprotoâ âcompositeprotoâ âdamageprotoâ âdmxprotoâ âdri2protoâ âdri3protoâ âfixesprotoâ âfontsprotoâ âglprotoâ âinputprotoâ âkbprotoâ âpresentprotoâ âprintprotoâ ârandrprotoâ ârecordprotoâ ârenderprotoâ âresourceprotoâ âscrnsaverprotoâ âvideoprotoâ âxcmiscprotoâ âxextprotoâ âxf86dgaprotoâ âxf86driprotoâ âxf86miscprotoâ âxf86vidmodeprotoâ âxineramaprotoâ âxprotoâ)
requires fixing/rebuilds:
1 Like