User Tools

Site Tools


debian_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
debian_notes [2021/02/27 18:03] – [bullseye release] rajudebian_notes [2023/03/20 21:37] admin
Line 1: Line 1:
 +===== dummy =====
 +==== when was a package installed ====
 +To find out when I installed the dokuwiki package, I did
 +<code>
 +$ zgrep installed /var/log/dpkg.log* | grep dokuwiki | grep -v "half-installed"
 +/var/log/dpkg.log.2.gz:2022-12-06 17:15:37 status installed dokuwiki:all 0.0.20220731.a-1
 +</code>
 +
 +without the ''grep -v "half-installed"'' at the end, I was getting
 +<code>
 +raju@minion:~$ zgrep installed /var/log/dpkg.log* | grep dokuwiki 
 +/var/log/dpkg.log.2.gz:2022-12-06 17:15:33 status half-installed dokuwiki:all 0.0.20180422.a-2.1
 +/var/log/dpkg.log.2.gz:2022-12-06 17:15:37 status installed dokuwiki:all 0.0.20220731.a-1
 +</code>
 +
 +Got this idea from https://www.cyberciti.biz/faq/debian-ubuntu-linux-find-package-installed-updated-date/
 +
 +==== links in this wiki ====
 +  * [[sources.list]]
 +
 +==== find the dpi of images in a pdf ====
 +<code>
 +$ pdfimages -list deptest.pdf
 +</code>
 +
 +Ref:- https://askubuntu.com/questions/760993/how-to-programmatically-determine-dpi-of-images-in-pdf-file
 +
 +==== combine multiple jpegs into one pdf ====
 +snippet 1:
 +<code>
 +convert *.jpg file.pdf
 +</code>
 +
 +snippet 2:
 +<code>
 + % cat combine_pics.sh
 +#! /usr/bin/env bash
 +
 +script_dir=`dirname "$0"`
 +cd $script_dir/bin
 +convert `ls -v individual_pics/*.jpeg` all_pics_combined.pdf
 +</code>
 +
 +Ref:- https://stackoverflow.com/questions/13618236/merge-multiple-jpg-into-single-pdf-in-linux
 +
 ==== apt-cache search with tags ==== ==== apt-cache search with tags ====
 Use axi-cache instead of apt-cache Use axi-cache instead of apt-cache
Line 15: Line 60:
 </code> </code>
  
-If we are using apt-cache, it would not be possible to "discover" skanlite unless we know the right set of keywords. For example+If we are using apt-cache, it would not be possible to "discover" skanlite unless we know the right set of keywords. For example, searching for 'scanner' and 'kde' would not have told us about skanlite package.
 <code> <code>
  % apt-cache search scanner kde  % apt-cache search scanner kde
Line 28: Line 73:
 ==== bullseye release ==== ==== bullseye release ====
   * https://release.debian.org/bullseye/freeze_policy.html   * https://release.debian.org/bullseye/freeze_policy.html
-  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981424 - blocker to upgrade from buster to bullseye 
  
 ==== status of debian testing ==== ==== status of debian testing ====
Line 49: Line 93:
  
 Ref:- I came across it in https://www.texmacs.org/tmweb/download/linux-repos.en.html#debian Ref:- I came across it in https://www.texmacs.org/tmweb/download/linux-repos.en.html#debian
 +
 +===== packages I came across =====
 +==== python3-full ====
 +  * python3-full package - https://packages.debian.org/stable/python3-full
 +    * This will include python, venv and pip.
 +    * If you just install the https://packages.debian.org/stable/python3 package, it will not have venv.
 +
 +Ref:- https://snarky.ca/how-virtual-environments-work/ -> "Introducing microvenv" section -> first paragraph
  
debian_notes.txt · Last modified: 2023/09/25 21:07 by raju