@todd Just run the command I've shown above. Or update with GNOME Software, that should also do the trick.
apt update was actually successful (despite the appearance and exit code), you only need to update your packages with full-upgrade afterwards.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 26 2018
In the error above, I am trying to simply do:
sudo apt update
But get the error. So need to know the work-around to get it updated.
I've already fixed this in Debian days ago and ensured that the issue is resolved in PureOS yesterday.
If you upgrade PureOS fully (apt update ; apt full-upgrade) the issue should be gone.
Done, hashcat 4.2.1-1 is in PureOS now.
2018-08-26 10:28:51 - WARNING: clamav: Target version '0.100.1+dfsg-1pureos1' is newer/equal than source version '0.100.1+dfsg-1'.
This needs a manual dummy upload as described in https://tracker.pureos.net/T99#10198 to reset our package to what Debian ships.
Done.
Done.
This appears to work with the new kernel image and today's (8/26) update.
Aug 25 2018
@vivia.nikolaidou Gentle ping :)
I don't think re-purposing this old bug for a blacklist removal request is a good idea - I was actually a bit confused to me to see seeing the bug appear again with this title...
Done. It's nice that we apparently can get rid of these diversions now :-)
Is this still an issue? Cryptsetup has been upgraded multiple times since this issue was reported...
2018-08-25 19:33:54 - WARNING: xarchiver: Target version '1:0.5.4.13-1pureos1' is newer/equal than source version '1:0.5.4.13-1'.
This needs a manual dummy upload as described in https://tracker.pureos.net/T99#10198 to reset our package to what Debian ships.
WARNING: p7zip: Target version '16.02+dfsg-6pureos1' is newer/equal than source version '16.02+dfsg-6'
This needs a manual upload as described in https://tracker.pureos.net/T99#10198 to reset our package to what Debian ships.
Aug 24 2018
This is resolved in the latest OEM and Live images, please test them! (for the oem image: https://downloads.puri.sm/oem/gnome/2018-08-25/, the live image is currently building)
Since I am quite out of ideas on this one now, I reported the issue with all information that I figured out so far against cryptsetup at Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907201
As weird as it looks, this issue is the same bug as the OEM encryption issue.
Aug 23 2018
Problem solved after upgrading to 4.6.0-2.
Many, many thanks!
A new image was built and I installed it (https://downloads.puri.sm/playground/2018-08-23/pureos-8.0-gnome-oem_20180823-amd64.hybrid.iso) in virt manager. After the install completed, I was prompted to reboot. Right after the reboot, I was prompted to enter the disk encryption password:
This is supposed to be fixed in libvirt >= 4.6.0-2, which PureOS already has.
Can you please ensure the package is up to date and has at least that version, and then try again?
Feel free to reopen the bug in case the issue persists (it should really be gone though).
The archive generally doesn't support downgrades - versions can only ever go up, otherwise our users will not actually get the changes.
So, if we have a version 0.9.3.2-1+pureos1 in PureOS, I can not sync 0.9.3.2-1 from debian, because 0.9.3.2-1 << 0.9.3.2-1+pureos1.
The archive will also *never* override PureOS-specific changes.
So what I did just now make an 0.9.3.2-1+x1 upload[1], because 0.9.3.2-1+x1 >> 0.9.3.2-1+pureos1. Since there is no "pureos" in the version string anymore now, the next time Debian gets a higher version of this package, the archive will just override the package I uploaded and we will be fully in sync again.
Sorry, I don't follow.
Done, but @jonas.smedegaard if the version number in PureOS is *higher* than the one in Debian, I can't sync stuff. In that case, an upload without the "pureos" version suffix has to be made to PureOS, which is a thing you can easily do as well and which doesn't need me.
yagf does not fallback-depend on a non-free package, only a non-existent one.
hashcat does not fallback-depend on a non-free package, only a non-existent one.
Ah: Dropping the fork was done long ago in T330.
audex does not suggest a non-free package, only a non-existent one.
p7zip does not suggest a non-free package, only a non-existent one.
xarchiver does not suggest a non-free package, only a non-existent one.
foo2zjs does not suggest a non-free package, only a non-existent one.
engrampa does not suggest a non-free package, only a non-existent one.
doublecmd does not suggest a non-free package, only a non-existent one.
clamav does not suggest a non-free package, only a non-existent one.
When addressed, this issue should be flaged as "invalid" (not "resolved").
q4wine does not suggest a non-free package, only a non-existent one.
Aug 22 2018
Also working on grpcio module packaging in the Python Modules team.
@vivia.nikolaidou What's the latest on this? Would love to get this settled up either way!
Aug 21 2018
(Feel free to re-use this ticket if there is not already one.)
@mak sorry, you may have told me about making graphics for the installer but I lost track of that.
Aug 20 2018
Chromium is blocked from entering PureOS.