https://apache.org/dist/ignite/deb is down due to the sunset of bintray. I need a deb package of ignite 2.9.0-1 and was hoping there was a mirror somewhere or if there was someway to get the deb off a machine that already has ignite running.
All ignite documentation still points to Bintray
// https://ignite.apache.org/docs/latest/installation/deb
I tried to use ignite's deb package.sh to build my own deb but I'm a little out of my element there and got the following error: [ERROR] RPM for converting to DEB not found
Hoping someone has a mirror.
Apache moved Ignite's repositories here:
https://apache.jfrog.io/artifactory/ignite-deb/
https://apache.jfrog.io/artifactory/ignite-rpm/
Related
When updating your system on archlinux with pacman -Suy, pacman gets package databases from somewhere and then downloads packages from mirrors according to versions specified in these databases.
I know these databases are in /var/lib/pacman/sync/. My question is, where does pacman get them from?
The db files also come from the package mirrors specified in /etc/pacman.d/mirrorlist.
For example in this core repo:
...
core.db 136.6 KiB 2022-Mar-05 12:53
core.db.tar.gz 136.6 KiB 2022-Mar-05 12:53
...
The wiki also mentions what to do if you get an error:
Failed retrieving file 'core.db' from mirror
If you receive this error message with correct mirrors, try setting a different name server.
We've got several flink applications reading from Kafka topics, and they work fine. But recently we've added a new topic to the existing flink job and it started failing immediately on startup with the following root error:
Caused by: org.apache.kafka.common.KafkaException: java.lang.NoClassDefFoundError: net/jpountz/lz4/LZ4Exception
at org.apache.kafka.common.record.CompressionType$4.wrapForInput(CompressionType.java:113)
at org.apache.kafka.common.record.DefaultRecordBatch.compressedIterator(DefaultRecordBatch.java:256)
at org.apache.kafka.common.record.DefaultRecordBatch.streamingIterator(DefaultRecordBatch.java:334)
at org.apache.kafka.clients.consumer.internals.Fetcher$PartitionRecords.nextFetchedRecord(Fetcher.java:1208)
at org.apache.kafka.clients.consumer.internals.Fetcher$PartitionRecords.fetchRecords(Fetcher.java:1245)
... 7 more
I found out that this topic has the lz4 compression and guess that flink for some reason is unable to work with it. Adding lz4 dependencies directly to the app didn't work, and what's weird - it runs fine locally, but fails on the remote cluster.
The flink runtime version is 1.9.1, and we have the same version of all other dependencies in our application:
flink-streaming-java_2.11, flink-connector-kafka_2.11, flink-java and flink-clients_2.11
Could this be happening due to flink not having a dependency to the lz4 lib inside?
Found the solution. No version upgrade was needed, nor the additional dependencies to the application itself. What worked out for us is adding the lz4 library jar directly to the flink libs folder in the Docker image. After that, the error with lz4 compression disappeared.
I want to run Z/IP Gateway on Ubuntu Linux. I have followed all the steps given in the following site:
https://www.silabs.com/support/getting-started/mesh-networking/z-wave/controller-kit
In the "Building the Documentation" section I want to install the 64-Bit Ubuntu but I am receiving the following ERROR("
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lib-dev:i386
I don't understand where to locate the package.
Best Regards,
Raja
It sounds like you're running a 32-bit system. Install libc6-dev and that should resolve the issue.
I git clone the zeppelin from https://github.com/apache/incubator-zeppelin.git, and make the project by running:
mvn clean package -Pspark-1.5 -Dhadoop.version=2.2.0 -Phadoop-2.2 -Ppyspark -DskipTests
but i always get the error:
Most probably, this indicates a dependency version miss-match, in this case Apache Lense.
The best way is to try re-building Apache Zeppelin from latest master, and if the issue persists - file an issue on official project JIRA
I want to start developing Pidgin plugins under Linux Mint 13.
I've read the official tutorial and at the beginning there's said that I should install the development dependencies for pidgin using the command: apt-get build-dep pidgin
But it ends up with the following error message:
E: Unable to find a source package for pidgin
Do I have to add a special repository? Or how can I make Linux Mint to find this package?
Here is the dump of sources.list:
deb http://packages.linuxmint.com/ maya main upstream import
deb http://archive.ubuntu.com/ubuntu/ precise main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ precise-updates main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ precise-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu/ precise partner
deb http://packages.medibuntu.org/ precise free non-free
# deb http://archive.getdeb.net/ubuntu precise-getdeb apps
# deb http://archive.getdeb.net/ubuntu precise-getdeb games
Edit /etc/apt/sources.list, and add deb-src:
deb http://packages.linuxmint.com/ maya main upstream import
deb-src http://packages.linuxmint.com/ maya main upstream import
deb http://archive.ubuntu.com/ubuntu/ precise main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ precise main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ precise-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ precise-updates main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ precise-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu/ precise-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu/ precise partner
deb http://packages.medibuntu.org/ precise free non-free
And try:
apt-get update
apt-get build-dep pidgin
A quick search at http://packages.linuxmint.com/search.php shows that a Pidgin repo exists for both felicia and helena, which is Linux Mint 6 & 8 respecitivly. It is possible the repositories that Mint installed by default did not contain links to those particular repositories.
If you are interested in development for Pidgin I would suggest downloading the files directly from here. This may help you understand the development process not from the perspective of Mint, but from the perspective of distribution independence.