Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #242760 > unrolled thread

question about a .deb file

Back to article view | Back to linux.debian.user

Contents

  question about a .deb file Piper H <potthua@gmail.com> - 2021-12-08 09:30 +0100
    Re: question about a .deb file Stanislav Vlasov <stanislav.v.v@gmail.com> - 2021-12-08 09:40 +0100
      Re: question about a .deb file Piper H <potthua@gmail.com> - 2021-12-08 10:20 +0100
        Re: question about a .deb file john doe <johndoe65534@mail.com> - 2021-12-08 10:30 +0100
          Re: question about a .deb file Tim Woodall <debianuser@woodall.me.uk> - 2021-12-09 09:00 +0100
            Re: question about a .deb file john doe <johndoe65534@mail.com> - 2021-12-10 05:50 +0100
              Re: question about a .deb file David Wright <deblis@lionunicorn.co.uk> - 2021-12-10 06:10 +0100
              Re: question about a .deb file Cindy Sue Causey <butterflybytes@gmail.com> - 2021-12-10 06:50 +0100
                Re: question about a .deb file David Wright <deblis@lionunicorn.co.uk> - 2021-12-10 07:10 +0100
    Re: question about a .deb file David <bouncingcats@gmail.com> - 2021-12-08 11:30 +0100
      Re: question about a .deb file Piper H <potthua@gmail.com> - 2021-12-08 11:50 +0100

#242760 — question about a .deb file

[Multipart message — attachments visible in raw view] — view raw

Hello again,

Sorry for this silly question.
I downloaded the JDBC drive from mysql website:
https://dev.mysql.com/downloads/connector/j/

And got a file name:
(mysql-connector-java_8.0.27-1debian10_all.deb)
Then I run:
sudo dpkg -i mysql-connector-java_8.0.27-1debian10_all.deb

And what's the next step?
I expect to get a *.jar file which will be used as the Mysql JDBC drive.
Until now I don't know where to get this jar file from the .deb file above.

Thanks.
Piper

[toc] | [next] | [standalone]

#242761

2021-12-08 13:21 GMT+05:00, Piper H <potthua@gmail.com>:
> I downloaded the JDBC drive from mysql website:
> https://dev.mysql.com/downloads/connector/j/
>
> And got a file name:
> (mysql-connector-java_8.0.27-1debian10_all.deb)
> Then I run:
> sudo dpkg -i mysql-connector-java_8.0.27-1debian10_all.deb
>
> And what's the next step?
> I expect to get a *.jar file which will be used as the Mysql JDBC drive.
> Until now I don't know where to get this jar file from the .deb file above.

You can see content of installed package by command:

dpkg -L mysql-connector-java

And i recommend you do not install packages by hand before searching in repo.
May be this package for you: https://packages.debian.org/buster/libmariadb-java

-- 
Stanislav

[toc] | [prev] | [next] | [standalone]

#242762

[Multipart message — attachments visible in raw view] — view raw

Thanks, I'll check them out. :)

On Wed, Dec 8, 2021 at 4:35 PM Stanislav Vlasov <stanislav.v.v@gmail.com>
wrote:

> 2021-12-08 13:21 GMT+05:00, Piper H <potthua@gmail.com>:
> > I downloaded the JDBC drive from mysql website:
> > https://dev.mysql.com/downloads/connector/j/
> >
> > And got a file name:
> > (mysql-connector-java_8.0.27-1debian10_all.deb)
> > Then I run:
> > sudo dpkg -i mysql-connector-java_8.0.27-1debian10_all.deb
> >
> > And what's the next step?
> > I expect to get a *.jar file which will be used as the Mysql JDBC drive.
> > Until now I don't know where to get this jar file from the .deb file
> above.
>
> You can see content of installed package by command:
>
> dpkg -L mysql-connector-java
>
> And i recommend you do not install packages by hand before searching in
> repo.
> May be this package for you:
> https://packages.debian.org/buster/libmariadb-java
>
> --
> Stanislav
>

[toc] | [prev] | [next] | [standalone]

#242763

On 12/8/2021 10:16 AM, Piper H wrote:
> Thanks, I'll check them out. :)
>

My suggestion would be to do the following commands:
$ apt-get --autoremove purge mysql-connector-java
$ apt-get update && apt-get install libmariadb-java

Add 'sudo' if you need it.

--
John Doe

[toc] | [prev] | [next] | [standalone]

#242794

On Wed, 8 Dec 2021, john doe wrote:

> On 12/8/2021 10:16 AM, Piper H wrote:
>> Thanks, I'll check them out. :)
>> 
>
> My suggestion would be to do the following commands:
> $ apt-get --autoremove purge mysql-connector-java

Does that work or is it a typo? I've always used:

apt-get autoremove --purge



Tim.

[toc] | [prev] | [next] | [standalone]

#242867

On 12/9/2021 8:55 AM, Tim Woodall wrote:
> On Wed, 8 Dec 2021, john doe wrote:
>
>> On 12/8/2021 10:16 AM, Piper H wrote:
>>> Thanks, I'll check them out. :)
>>>
>>
>> My suggestion would be to do the following commands:
>> $ apt-get --autoremove purge mysql-connector-java
>
> Does that work or is it a typo? I've always used:
>
> apt-get autoremove --purge
>

$ apt-get autoremove --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
[snip]
0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
After this operation, 1018 MB disk space will be freed.
Do you want to continue? [Y/n]
$ apt-get purge --autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
[snip]
0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
After this operation, 1018 MB disk space will be freed.
Do you want to continue? [Y/n] ^C
$ apt-get --autoremove purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
[snip]
0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
After this operation, 1018 MB disk space will be freed.
Do you want to continue? [Y/n]
$ apt-get --help
apt 2.3.13 (amd64)
Usage: apt-get [options] command
        apt-get [options] install|remove pkg1 [pkg2 ...]
        apt-get [options] source pkg1 [pkg2 ...]
[snip]


Specifying options before the command looks to be more man page compliant...

--
John Doe

[toc] | [prev] | [next] | [standalone]

#242869

On Fri 10 Dec 2021 at 05:49:06 (+0100), john doe wrote:
> On 12/9/2021 8:55 AM, Tim Woodall wrote:
> > On Wed, 8 Dec 2021, john doe wrote:
> > > On 12/8/2021 10:16 AM, Piper H wrote:
> > > > Thanks, I'll check them out. :)
> > > 
> > > My suggestion would be to do the following commands:
> > > $ apt-get --autoremove purge mysql-connector-java
> > 
> > Does that work or is it a typo? I've always used:
> > 
> > apt-get autoremove --purge
> 
> $ apt-get autoremove --purge
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be REMOVED:
> [snip]
> 0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> After this operation, 1018 MB disk space will be freed.
> Do you want to continue? [Y/n]
> $ apt-get purge --autoremove
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be REMOVED:
> [snip]
> 0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> After this operation, 1018 MB disk space will be freed.
> Do you want to continue? [Y/n] ^C
> $ apt-get --autoremove purge
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be REMOVED:
> [snip]
> 0 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> After this operation, 1018 MB disk space will be freed.
> Do you want to continue? [Y/n]
> $ apt-get --help
> apt 2.3.13 (amd64)
> Usage: apt-get [options] command
>        apt-get [options] install|remove pkg1 [pkg2 ...]
>        apt-get [options] source pkg1 [pkg2 ...]
> [snip]
> 
> 
> Specifying options before the command looks to be more man page compliant...

… and the man page also shows that purge and autoremove
happen to be both commands and options (as is reinstall).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#242870

On 12/9/21, john doe <johndoe65534@mail.com> wrote:
> On 12/9/2021 8:55 AM, Tim Woodall wrote:
>> Does that work or is it a typo? I've always used:
>>
>> apt-get autoremove --purge
>>
> $ apt-get --help
> apt 2.3.13 (amd64)
> Usage: apt-get [options] command
>         apt-get [options] install|remove pkg1 [pkg2 ...]
>         apt-get [options] source pkg1 [pkg2 ...]
> [snip]
>
> Specifying options before the command looks to be more man page
> compliant...


I've seen one rare occasion where [positioning] overall really
matters, but it wasn't apt-get. It was about mount'ing of ISO or img
files or maybe even a third file type.

My apologies that I can't remember what flag I was using. More than
one flag was involved because of the more unusual mount I was
attempting. One flag was expressed in front of declaring the mount
point, and the other was typed in afterward.

It would mount fine in one instance with one particular flag at the
end (because that's how it had been advised somewhere online). That
same format did NOT work for one now forgotten file type. It all had
to be stated before the file and mount point declaration.

It makes sense. There should be some kind of universal uniformity to
best guarantee predictability of outcome across the widest range of
user setups possible. For mounting, that would be to say do all these
things stated here in this beginning lump to this file being mounted
at this point as declared here at the end of this entire [statement].
It reminds me of "subject and predicate" sentence structuring in
grammar.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#242871

On Fri 10 Dec 2021 at 00:41:29 (-0500), Cindy Sue Causey wrote:
> On 12/9/21, john doe <johndoe65534@mail.com> wrote:
> > On 12/9/2021 8:55 AM, Tim Woodall wrote:
> >> Does that work or is it a typo? I've always used:
> >>
> >> apt-get autoremove --purge
> >>
> > $ apt-get --help
> > apt 2.3.13 (amd64)
> > Usage: apt-get [options] command
> >         apt-get [options] install|remove pkg1 [pkg2 ...]
> >         apt-get [options] source pkg1 [pkg2 ...]
> > [snip]
> >
> > Specifying options before the command looks to be more man page
> > compliant...
> 
> 
> I've seen one rare occasion where [positioning] overall really
> matters, but it wasn't apt-get. It was about mount'ing of ISO or img
> files or maybe even a third file type.
> 
> My apologies that I can't remember what flag I was using. More than
> one flag was involved because of the more unusual mount I was
> attempting. One flag was expressed in front of declaring the mount
> point, and the other was typed in afterward.
> 
> It would mount fine in one instance with one particular flag at the
> end (because that's how it had been advised somewhere online). That
> same format did NOT work for one now forgotten file type. It all had
> to be stated before the file and mount point declaration.
> 
> It makes sense. There should be some kind of universal uniformity to
> best guarantee predictability of outcome across the widest range of
> user setups possible. For mounting, that would be to say do all these
> things stated here in this beginning lump to this file being mounted
> at this point as declared here at the end of this entire [statement].
> It reminds me of "subject and predicate" sentence structuring in
> grammar.

It's not rare for placement of options and subcommands to matter.
You can't have the sort of uniformity you want, because many commands
read their options and subcommands in L-R order, and effectively act
upon them as they read them. APT is very forgiving with the above,
because they obviously mean the same thing. And stick a --simulate at
the end of the line and you get a harmless dry-run.

But don't try that with dpkg: it will happily destroy your system
and then say "Oh, didn't you really mean that? Sorry" when it
encounters --simulate at the end of the commandline.

Similarly, get a --delete in the wrong place after a find command,
and you can lose half your filesystem.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#242764

[Multipart message — attachments visible in raw view] — view raw

On Wed, 8 Dec 2021 at 19:21, Piper H <potthua@gmail.com> wrote:

> Hello again,
>
> Sorry for this silly question.
> I downloaded the JDBC drive from mysql website:
> https://dev.mysql.com/downloads/connector/j/
>

Hi.

Just for your information, because you might not realise:

Debian is a huge project that attempts to ensure the
compatibility of every piece of software on your machine.

If you download software from other sources, like you
did from mysql.com above, then you will break Debian's
methods for managing software compatibility on your
machine.

If you get a .deb package from somewhere that is not
Debian, then that package is NOT part of Debian.
It uses Debian packaging methods to create the .deb
file, but it has NOT been integrated by Debian for compatibility
with a Debian release.

This incompatibility can cause your installation to become
unusable, immediately, or later.

Plus, folks from Debian won't be interested in helping you
to fix those issues. Because from their perspective, they
will see that you broke your Debian system by installing a
foreign package.

So for a problem-free experience with Debian, the
ideal approach is to only install packages provided
by Debian through one of its official repositories.

More information on this topic is provided here:
  https://wiki.debian.org/DontBreakDebian

Please do read that. Ask here if you have any questions.

It is important to understand that Debian is intended to
be used by people for whom this restriction is not a problem.
Not only that, but it is the philosophy of the Debian project
and the reason why Debian is what it is. There are dozens
of different Linux distributions, several different package
management systems, and each comes with a different
approach to solving the software compatibility problem.

I hope this information helps you.

[toc] | [prev] | [next] | [standalone]

#242765

[Multipart message — attachments visible in raw view] — view raw

Hi David

Thanks for the info you provided.
The original purpose I asked the question is that I did need that jar file
for Mysql connector for Spark.
As you see the operations below:

$ pyspark --jars mysql-connector-java-8.0.27.jar
Python 3.6.9 (default, Jan 26 2021, 15:33:00)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
...
Spark context available as 'sc' (master = local[*], app id =
local-1638960026416).
SparkSession available as 'spark'.
>>>

In the command line I specify the jar name which must be put in Spark's
library dir.
So I was looking where the file is located in the system.

best regards,
Piper



On Wed, Dec 8, 2021 at 6:27 PM David <bouncingcats@gmail.com> wrote:

> On Wed, 8 Dec 2021 at 19:21, Piper H <potthua@gmail.com> wrote:
>
>> Hello again,
>>
>> Sorry for this silly question.
>> I downloaded the JDBC drive from mysql website:
>> https://dev.mysql.com/downloads/connector/j/
>>
>
> Hi.
>
> Just for your information, because you might not realise:
>
> Debian is a huge project that attempts to ensure the
> compatibility of every piece of software on your machine.
>
> If you download software from other sources, like you
> did from mysql.com above, then you will break Debian's
> methods for managing software compatibility on your
> machine.
>
> If you get a .deb package from somewhere that is not
> Debian, then that package is NOT part of Debian.
> It uses Debian packaging methods to create the .deb
> file, but it has NOT been integrated by Debian for compatibility
> with a Debian release.
>
> This incompatibility can cause your installation to become
> unusable, immediately, or later.
>
> Plus, folks from Debian won't be interested in helping you
> to fix those issues. Because from their perspective, they
> will see that you broke your Debian system by installing a
> foreign package.
>
> So for a problem-free experience with Debian, the
> ideal approach is to only install packages provided
> by Debian through one of its official repositories.
>
> More information on this topic is provided here:
>   https://wiki.debian.org/DontBreakDebian
>
> Please do read that. Ask here if you have any questions.
>
> It is important to understand that Debian is intended to
> be used by people for whom this restriction is not a problem.
> Not only that, but it is the philosophy of the Debian project
> and the reason why Debian is what it is. There are dozens
> of different Linux distributions, several different package
> management systems, and each comes with a different
> approach to solving the software compatibility problem.
>
> I hope this information helps you.
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web