EternalTerminal
EternalTerminal copied to clipboard
MisterTea
debian testing package
Installing on debian testing:
The following packages have unmet dependencies:
et : Depends: libprotobuf-lite17 but it is not installable
The lib should now be libprotobuf-lite23.
How are the deb packages produced?
In the deployment branch there's a script and Vagrantfile for making Deb packages.
I tried to get into Debian proper as we are with fedora, but there was pushback.
Debian 11 is now released/stable and the same still applies
so i just snagged and installed http://ftp.us.debian.org/debian/pool/main/p/protobuf/libprotobuf-lite17_3.6.1.3-2_amd64.deb
/shrug
I tried to get into Debian proper as we are with fedora, but there was pushback.
Pushback how and where?
I am only aware of https://bugs.debian.org/861635#8 which I read not as pushback but as "hmm, no activity for more than a year, so let's relax this to either a) get a reaction from the person currently preparing a package, or if not then b) encourage others to step in".
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865881
If you know anyone at Debian who can get this through, please reach out to them. Thanks.
On Wed, Sep 8, 2021, 6:42 AM Jonas Smedegaard @.***> wrote:
I tried to get into Debian proper as we are with fedora, but there was pushback.
Pushback how and where?
I am only aware of https://bugs.debian.org/861635#8 which I read not as pushback but as "hmm, no activity for more than a year, so let's relax this to either a) get a reaction from the person currently preparing a package, or if not then b) encourage others to step in".
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MisterTea/EternalTerminal/issues/437#issuecomment-915161516, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACK5P2WX7OSDUXDA7WMXMLUA5D2DANCNFSM44SIFRPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Debian bugs 865881 and 861635 both track the same issue: a so-called "ITP" i.e. an "intent to package".
If you want to maintain a package while you are not yourself a Debian Maintainer, then you need someone to sponsor it: https://wiki.debian.org/SponsoredMaintainer
Can you sponsor it? Do you know any sponsors who can sponsor it? Can I become a Debian maintainer?
I want to get this package into Debian and am motivated.
On Wed, Sep 8, 2021, 10:30 AM Jonas Smedegaard @.***> wrote:
Debian bugs 865881 and 861635 both track the same issue: a so-called "ITP" i.e. an "intent to package".
If you want to maintain a package while you are not yourself a Debian Maintainer, then you need someone to sponsor it: https://wiki.debian.org/SponsoredMaintainer
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MisterTea/EternalTerminal/issues/437#issuecomment-915342164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACK5PZLXSOFITISDQHTXCTUA56QDANCNFSM44SIFRPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
I won't act as sponsor myself - both because I think Debian is better maintained by direct maintenance than through the proxy of a sponsor, but also because I really have my hands full already (I maintain more than 500 packages).
The link I provided above provides some ways to locate a sponsor, if you want that approach. If you want to join Debian as a Debian Maintainer or Debian Developer (which I think is great if you do), then more information is available at https://www.debian.org/devel/join/
Any updates or workarounds on this? I'm still getting et : Depends: libprotobuf-lite17 but it is not installable on Debian 11 aarch64
@JJGO did you try the workaround at https://github.com/MisterTea/EternalTerminal/issues/437#issuecomment-913566823 ?
Yes, that worked once I change the arch and downloaded the right package. Thanks!
I installed the .deb file (armhf in my case) directly but somehow I am still getting the same issue on Debian Sid:
user@debian-sid /tmp $ sudo dpkg -i libprotobuf-lite17_3.6.1.3-2_armhf.deb
Selecting previously unselected package libprotobuf-lite17:armhf.
(Reading database ... 280175 files and directories currently installed.)
Preparing to unpack libprotobuf-lite17_3.6.1.3-2_armhf.deb ...
Unpacking libprotobuf-lite17:armhf (3.6.1.3-2) ...
Setting up libprotobuf-lite17:armhf (3.6.1.3-2) ...
Processing triggers for libc-bin (2.33-1) ...
user@debian-sid /tmp $ echo "deb https://mistertea.github.io/debian-et/debian-source/ buster main" | sudo tee /etc/apt/sources.list.d/et.list
curl -sS https://mistertea.github.io/debian-et/et.gpg | sudo apt-key add -
sudo apt update
sudo apt install et
deb https://mistertea.github.io/debian-et/debian-source/ buster main
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
Hit:1 http://deb.debian.org/debian sid InRelease
Hit:2 https://mistertea.github.io/debian-et/debian-source buster InRelease
Hit:3 https://www.yoctopuce.com apt/stable/ InRelease
Hit:4 https://repo.nextdns.io/deb stable InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1653 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
et : Depends: libprotobuf-lite17 but it is not installable
E: Unable to correct problems, you have held broken packages.
@Kabouik your log indicates that you don't run Debian but a mixture of Debian and multiple other sources. The problem is that some package (highly likely some not-from-Debian package - probably the one from mistertea) is out of sync with the release of Debian you are mixing it with: You use Debian unstable (a.k.a. sid), yoctopuce and nextdns seems to be some stable release (possibly current stable - a.k.a. bullseye but maybe some older one(s)) and mistertea packages use oldstable (a.k.a. buster).
The solution is that whatever package linking with libprotobuf needs to be rebuilt against the libprotobuf in the Debian system you use.
A possible workaround is to make an even bigger mess by pulling in matching libprotobuf package - as mentioned by xstefen above.
Thanks you very much @jonassmedegaard. I agree that my system is a bit of a mess, this is because I needed to use Sid for other reasons and sadly external repositories such as Yoctopuce, Nextdns and others rarely provide testing variants so I had to use whatever they provided; same with @mistertea's repository ofr et. Another issue is my system is not updated, but it's a LXC container running in another system and keeping those old package versions is a choice.
My understanding from the first post here was that @gregwebs was also trying to install et on Debian testing, and faced the same issue with libprotobuf-lite17 not being installable. I don't understand then how in my case this would be related to those external repos, if @gregwebs gets the same issue without those. Let me clarify that except et, I have no package depending on libprotobuf-lite17, so I can freely remove it without affecting other packages, including those from external repositories.
I did install the package linked by @xstefen above as shown in the logs, but somehow et refuses to link to it. Previously (some weeks/months ago), I think I had et working on the same system by just using the commands on et's installation guide. I guess at that time Debian Sid testing repos provided their own version of libprotobuf-lite17, but the package no longer exists and I did run sudo apt update so it's gone now. It's not clear to me why the .deb linked by @xstefen doesn't work for me though.
@Kabouik its probably outdated now. i'm not running debian currently on any of my systems so i cant know for sure.
I don't understand then how in my case this would be related to those external repos
Possibly those are unrelated.
My point was that your system - Debian sid-as-of-2022-01-03-mixed-with-multiple-unofficial-sources is further from Debian buster than Debian-bullseye-as-of-2021-05-10.
The solution is to build and use a package that matches the system used.
A workaround is to make an even messier system which includes libprotobuf-lite17. It sounds like you are unfamiliar with the administration tasks required for such messy system - e.g. the trick of holding packaging. If you want to go down that route then I recommend that you seek help in the Debian user community.
Can you sponsor it? Do you know any sponsors who can sponsor it? Can I become a Debian maintainer? I want to get this package into Debian and am motivated.
Has there been any progress towards Debian inclusion? It sounds like a lot of people are keen for this.
In the meantime, it could be helpful to put the bullseye version of the install commands on the README.md.
It's a shame - this probably missed the window for bookworm inclusion too.
EDIT> Actually I am dumb and copy-pasted the instructions verbatim without reading them, which configured a buster repo on a bookworm host, sorry for the noise
