Does anyone use "APT-LISTBUGS"?
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Does anyone use "APT-LISTBUGS"?
I came across the while reading on the Debian forums.
http://forums.debian.net/viewtopic.php? ... 4f5976b499
and
http://packages.debian.org/wheezy/apt-listbugs
It appears to be a tool that points out "bugs" before a 'apt-get dist-upgrade' (from what i gather)?
------------------------------------------
Its available in synaptic.
Sounds very useful with both "testing" and "SID" (especially SID)
I would be very interested in hearing from anyone who uses it.
(And HOW to use it).
Thanks.
http://forums.debian.net/viewtopic.php? ... 4f5976b499
and
http://packages.debian.org/wheezy/apt-listbugs
It appears to be a tool that points out "bugs" before a 'apt-get dist-upgrade' (from what i gather)?
------------------------------------------
Its available in synaptic.
Sounds very useful with both "testing" and "SID" (especially SID)
I would be very interested in hearing from anyone who uses it.
(And HOW to use it).
Thanks.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Does anyone use "APT-LISTBUGS"?
I had not realized that there was this application, which I think is essential, thanks.
Re: Does anyone use "APT-LISTBUGS"?
Same here!linmint777 wrote:I had not realized that there was this application, which I think is essential, thanks.
I installed it, but am darned if I can figure out how to use it.
Not handy at all with the "terminal" yet.
Perhaps you or someone could help.
This is my output
Code: Select all
gene@zordon ~ $ apt-listbugs
E: You need to specify a command.
Usage: apt-listbugs [options] <command> [arguments]
Options:
-h : Display this help and exit.
-v : Show version number and exit.
-s <severities> : Severities you want to see [critical,grave,serious], or [all].
-T <tags> : Tags you want to see.
-S <stats> : Stats you want to see [forwarded,done,pending,pending-fixed,].
-B <bug#> : Restrict reporting to specified bug#s only.
-D : Show downgraded packages, too.
-H <hostname> : Hostname of Debian Bug Tracking System [bugs.debian.org].
-p <port> : Port number of the server [80].
-P <priority> : Specifies Pin-Priority value [1000].
-E <title> : Specifies the title of rss output.
-q : Don't display progress bar.
-C <apt.conf> : Specify apt.conf.
-y : Assume that you select yes for all questions.
-n : Assume that you select no for all questions.
-d : Debug.
Commands:
apt : Apt mode.
list <pkg...> : List bug reports of the specified packages.
rss <pkg...> : List bug reports of the specified packages in rss.
See the manual page for the long options.
Re: Does anyone use "APT-LISTBUGS"?
Code: Select all
man apt-listbugs
apt-listbugs(1) apt-listbugs(1)
NAME
apt-listbugs - Lists critical bugs before each apt upgrade/installation
SYNOPSIS
apt-listbugs [options] <command> [arguments]
DESCRIPTION
apt-listbugs is a tool which retrieves bug reports from the Debian Bug
Tracking System and lists them. Especially, it is intended to be
invoked before each upgrade by apt, or other similar package managers,
in order to check whether the upgrade/installation is safe.
USAGE
apt-listbugs [-h] [-v] [-s <severities>] [-T <tags>] [-S <stats>] [-B
<bug#>] [-D] [-H <hostname>] [-p <port>] [-P <priority>] [-E <title>]
[-q] [-C <apt.conf>] [-y] [-n] [-d] <command> [arguments]
OPTIONS
· -h | --help Print usage help and exit
· -v | --version Print version number and exit
Manual page apt-listbugs(1) line 1 (press h for help or q to quit)
Re: Does anyone use "APT-LISTBUGS"?
Have been doing a little more searching for info on the use of this package.
It looks to me that you dont actually run the command
It runs when you do an "apt-get"(whatever), and warns of any bugs that are listed.
I found this YOU TUBE tutorial for it.
http://www.youtube.com/watch?v=uwAaELRQxeI
Also another thread.
http://www.linuxquestions.org/questions ... ns-316174/
I just ran an 'sudo apt-get update && sudo apt-get dist-upgrade' on my LMDE SID partition, and saw nothing unusual, but that may just be because there were no "listed" bugs.
It seems to be a good tool, just not sure if I am using it correctly.
If anyone else tries it, and would care to comment. It would be appreciated.
It looks to me that you dont actually run the command
Code: Select all
apt-listbugs
I found this YOU TUBE tutorial for it.
http://www.youtube.com/watch?v=uwAaELRQxeI
Also another thread.
http://www.linuxquestions.org/questions ... ns-316174/
I just ran an 'sudo apt-get update && sudo apt-get dist-upgrade' on my LMDE SID partition, and saw nothing unusual, but that may just be because there were no "listed" bugs.
It seems to be a good tool, just not sure if I am using it correctly.
If anyone else tries it, and would care to comment. It would be appreciated.
Re: Does anyone use "APT-LISTBUGS"?
It runs with Apt-get & Aptitude---A total "must-have"----nice to get the "do you really want to install this?" warning Generally sends me to bug reports to see why, and allows time to think about that upgrade.....You would see it much more if you were running Experimental sources....I see it about 2~3 times a week.....
Re: Does anyone use "APT-LISTBUGS"?
Gene,
I use it routinely before doing upgrades. If you run
it will output Grave, Critical and Serious bugs
If you run
it will output Grave, Critical, Serious, Important, Normal, Minor, and Wishlist bugs. If you only wanted to see the Important and Normal bugs you would enter
To find bugs still present in a particular version
such as apt-listbugs list gdm3/2.30.5-9
I use it routinely before doing upgrades. If you run
Code: Select all
apt-listbugs list <packagename>
If you run
Code: Select all
apt-listbugs list <packagename> -s all
Code: Select all
apt-listbugs list <packagename> -s important,normal
Code: Select all
apt-listbugs list <packagename/versionnumber>
Re: Does anyone use "APT-LISTBUGS"?
Today I check Debian-sid, and see lots of stuff to be removed, even there is no apt-listbug reports.
as I was sensitive about so many 'remove' I am holding.
see how many removal: even gedit is to be removed
87 upgraded, 0 newly installed, 45 to remove and 1 not upgraded.
The following packages will be REMOVED:
alacarte deskbar-applet gdebi gedit gedit-plugins gimp gnome-about
gnome-applets gnome-codec-install gnome-control-center gnome-games gnome-mag
gnome-menus gnome-office gnome-orca gnome-panel gnome-session hamster-applet
python-aptdaemon-gtk python-bugbuddy python-evolution python-gconf
python-glade2 python-gmenu python-gnome2 python-gnomeapplet
python-gnomedesktop python-gnomekeyring python-gtk2 python-gtksourceview2
python-notify python-pyatspi python-vte python-webkit python-wnck rhythmbox
rhythmbox-plugin-cdrecorder rhythmbox-plugins software-center
software-properties-gtk system-config-printer totem-coherence totem-plugins
update-manager-gnome update-notifier
The following packages have been kept back:
seahorse
The following packages will be upgraded:
acpid alsa-base alsa-utils cpp-4.4 cpp-4.5 cups cups-bsd cups-client
cups-common cups-ppdc evolution evolution-common evolution-plugins gcc-4.4
gcc-4.4-base gcc-4.5 gcc-4.5-base gcc-4.6-base gcj-4.4-base gcj-4.4-jre
gcj-4.4-jre-headless gcj-4.4-jre-lib libasound2 libcups2 libcupscgi1
libcupsdriver1 libcupsimage2 libcupsmime1 libcupsppdc1 libdb4.7
libdb4.7-java libdb4.7-java-gcj libdv4 libevolution libgcc1 libgcj10
libgcj10-awt libgfortran3 libgomp1 libgphoto2-2 libgphoto2-l10n
libgphoto2-port0 libimobiledevice1 libpangomm-1.4-1 libquadmath0 libreoffice
libreoffice-base libreoffice-base-core libreoffice-calc libreoffice-common
libreoffice-core libreoffice-draw libreoffice-emailmerge
libreoffice-filter-binfilter libreoffice-filter-mobiledev libreoffice-gcj
libreoffice-gnome libreoffice-gtk libreoffice-help-en-us libreoffice-impress
libreoffice-java-common libreoffice-math libreoffice-report-builder-bin
libreoffice-style-galaxy libreoffice-style-tango libreoffice-writer
libstdc++6 libv4l-0 libva-x11-1 libva1 linux-sound-base python-apt
python-cairo python-debian python-gobject python-gobject-cairo python-mako
python-pyorbit python-twisted-bin python-twisted-core python-twisted-web
python-uno ttf-lyx ttf-opensymbol uno-libs3 ure wpasupplicant
87 upgraded, 0 newly installed, 45 to remove and 1 not upgraded.
Need to get 217 MB of archives.
After this operation, 89.7 MB disk space will be freed.
Do you want to continue [Y/n]?
as I was sensitive about so many 'remove' I am holding.
see how many removal: even gedit is to be removed
87 upgraded, 0 newly installed, 45 to remove and 1 not upgraded.
The following packages will be REMOVED:
alacarte deskbar-applet gdebi gedit gedit-plugins gimp gnome-about
gnome-applets gnome-codec-install gnome-control-center gnome-games gnome-mag
gnome-menus gnome-office gnome-orca gnome-panel gnome-session hamster-applet
python-aptdaemon-gtk python-bugbuddy python-evolution python-gconf
python-glade2 python-gmenu python-gnome2 python-gnomeapplet
python-gnomedesktop python-gnomekeyring python-gtk2 python-gtksourceview2
python-notify python-pyatspi python-vte python-webkit python-wnck rhythmbox
rhythmbox-plugin-cdrecorder rhythmbox-plugins software-center
software-properties-gtk system-config-printer totem-coherence totem-plugins
update-manager-gnome update-notifier
The following packages have been kept back:
seahorse
The following packages will be upgraded:
acpid alsa-base alsa-utils cpp-4.4 cpp-4.5 cups cups-bsd cups-client
cups-common cups-ppdc evolution evolution-common evolution-plugins gcc-4.4
gcc-4.4-base gcc-4.5 gcc-4.5-base gcc-4.6-base gcj-4.4-base gcj-4.4-jre
gcj-4.4-jre-headless gcj-4.4-jre-lib libasound2 libcups2 libcupscgi1
libcupsdriver1 libcupsimage2 libcupsmime1 libcupsppdc1 libdb4.7
libdb4.7-java libdb4.7-java-gcj libdv4 libevolution libgcc1 libgcj10
libgcj10-awt libgfortran3 libgomp1 libgphoto2-2 libgphoto2-l10n
libgphoto2-port0 libimobiledevice1 libpangomm-1.4-1 libquadmath0 libreoffice
libreoffice-base libreoffice-base-core libreoffice-calc libreoffice-common
libreoffice-core libreoffice-draw libreoffice-emailmerge
libreoffice-filter-binfilter libreoffice-filter-mobiledev libreoffice-gcj
libreoffice-gnome libreoffice-gtk libreoffice-help-en-us libreoffice-impress
libreoffice-java-common libreoffice-math libreoffice-report-builder-bin
libreoffice-style-galaxy libreoffice-style-tango libreoffice-writer
libstdc++6 libv4l-0 libva-x11-1 libva1 linux-sound-base python-apt
python-cairo python-debian python-gobject python-gobject-cairo python-mako
python-pyorbit python-twisted-bin python-twisted-core python-twisted-web
python-uno ttf-lyx ttf-opensymbol uno-libs3 ure wpasupplicant
87 upgraded, 0 newly installed, 45 to remove and 1 not upgraded.
Need to get 217 MB of archives.
After this operation, 89.7 MB disk space will be freed.
Do you want to continue [Y/n]?
Re: Does anyone use "APT-LISTBUGS"?
I wouls say that is due to Python...been a bit of trouble with that lately......try a aptitude safe-upgrade & see what it will do.....
Re: Does anyone use "APT-LISTBUGS"?
autocrosser wrote:I wouls say that is due to Python...been a bit of trouble with that lately......try a aptitude safe-upgrade & see what it will do.....
wow, long long list, better hold
Code: Select all
root@debian64net:/home/wayne# aptitude safe-upgrade
Resolving dependencies...
The following packages will be REMOVED:
acl{u} aptdaemon{u} baobab{u} bluez{u} cheese{u} cheese-common{u}
dasher{u} dasher-data{u} dmz-cursor-theme{u} dnsmasq-base{u} ekiga{u}
empathy{u} empathy-common{u} eog{u} epiphany-data{u} espeak{u}
espeak-data{u} evolution{u} evolution-common{u} evolution-exchange{u}
evolution-plugins{u} evolution-webcal{u} file-roller{u}
freedesktop-sound-theme{u} freeglut3{u} gcalctool{u}
gconf-defaults-service{u} gconf-editor{u} gdebi{u} gdebi-core{u} gedit{u}
gedit-common{u} gedit-plugins{u} geoclue{u} geoclue-hostip{u}
geoclue-localnet{u} geoclue-manual{u} geoclue-yahoo{u}
gnome-accessibility-themes{u} gnome-backgrounds{u} gnome-bluetooth{u}
gnome-cards-data{u} gnome-codec-install{u} gnome-disk-utility{u}
gnome-games{u} gnome-games-data{u} gnome-games-extra-data{u} gnome-mag{u}
gnome-nettool{u} gnome-office{u} gnome-orca{u} gnome-screensaver{u}
gnome-screenshot{u} gnome-search-tool{u} gnome-session-canberra{u}
gnome-system-log{u} gnome-system-tools{u} gnome-themes{u}
gnome-themes-extras{u} gnome-themes-more{u} gnome-themes-standard{u}
gnome-user-share{u} gnuchess{u} gnuchess-book{u} gok{u}
gstreamer0.10-nice{u} gstreamer0.10-tools{u} gtk2-engines{u}
gtk2-engines-smooth{u} gucharmap{u} guile-1.8-libs{u} gvfs-bin{u}
hamster-applet{u} hplip-cups{u} hplip-data{u} libapache2-mod-dnssd{u}
libbrlapi0.5{u} libcap-ng0{u} libccid{u} libchamplain-0.4-0{u}
libchamplain-0.8-1{u} libchamplain-gtk-0.4-0{u} libchamplain-gtk-0.8-1{u}
libcheese-gtk18{u} libcolorblind0{u} libcryptui0{u} libdiscid0{u}
libelf1{u} libespeak1{u} libevolution{u} libfreerdp-plugins-standard{u}
libfreerdp0{u} libgail-gnome-module{u} libgcr0{u} libgdu-gtk0{u}
libgeoclue0{u} libgexiv2-0{u} libgirepository1.0-0{u} libglew1.5{u}
libgmp3c2{u} libgnome-bluetooth7{u} libgnome-mag2{u} libgnome-speech7{u}
libgnome2-canvas-perl{u} libgnome2-perl{u} libgnome2-vfs-perl{u}
libgp11-0{u} libgpod-common{u} libgpod4{u} libgsf-1-114{u}
libgsf-1-common{u} libgstfarsight0.10-0{u} libgtkhtml-editor-3.14-0{u}
libgtkhtml-editor-3.14-common{u} libgtkhtml3.14-19{u} libgtkimageview0{u}
libgtksourceview2.0-0{u} libgtksourceview2.0-common{u}
libgupnp-igd-1.0-3{u} libieee1284-3{u} libiptcdata0{u} liblouis-data{u}
liblouis2{u} libmikmod2{u} libmusicbrainz3-6{u} libnet1{u} libnice10{u}
libnl1{u} libnm-glib-vpn1{u} libnm-glib2{u} libnm-util1{u}
libntfs-3g75{u} libopal3.6.8{u} libopenobex1{u} libpango1.0-common{u}
libpcsclite1{u} libportaudio2{u} libppl-c2{u} libppl7{u} libpt2.6.7{u}
libqt4-webkit{u} libqt4-xmlpatterns{u} libqtsensors1{u} librpm1{u}
librpmio1{u} libsane{u} libsane-extras{u} libsane-hpaio{u}
libsdl-mixer1.2{u} libsmpeg0{u} libspeexdsp1{u} libsrtp0{u} libsvga1{u}
libtelepathy-farsight0{u} libxcb-render-util0{u} liferea{u}
liferea-data{u} linux-headers-2.6.37-4.dmz.1-liquorix-amd64{u}
linux-headers-2.6.38-1.dmz.1-liquorix-amd64{u}
linux-headers-2.6.38-2.dmz.1-liquorix-amd64{u}
linux-headers-2.6.38-2.dmz.2-liquorix-amd64{u} media-player-info{u}
mesa-utils{u} mobile-broadband-provider-info{u} modemmanager{u}
mousetweaks{u} nautilus-sendto{u} nautilus-sendto-empathy{u}
network-manager{u} network-manager-gnome{u} obex-data-server{u}
obexd-client{u} pcscd{u} pkg-config{u} ppp{u} python-aptdaemon{u}
python-aptdaemon-gtk{u} python-brlapi{u} python-bugbuddy{u}
python-evolution{u} python-gtkglext1{u} python-gtksourceview2{u}
python-imaging{u} python-louis{u} python-mako{u} python-markupsafe{u}
python-opengl{u} python-pexpect{u} python-pyatspi{u} python-vte{u}
python-webkit{u} qt4-qtconfig{u} remmina{u} remmina-plugin-data{u}
remmina-plugin-rdp{u} remmina-plugin-vnc{u} rhythmbox{u}
rhythmbox-plugin-cdrecorder{u} rhythmbox-plugins{u} rpm-common{u}
rpm2cpio{u} sane-utils{u} seahorse{u} seahorse-plugins{u} shotwell{u}
simple-scan{u} software-center{u} sound-juicer{u} tcl{u} tcl8.5{u}
tcptraceroute{u} telepathy-gabble{u} telepathy-mission-control-5{u}
telepathy-salut{u} transmission-common{u} transmission-gtk{u}
update-manager-core{u} update-manager-gnome{u} update-notifier{u}
update-notifier-common{u} usb-modeswitch{u} usb-modeswitch-data{u}
vino{u} wpasupplicant{u} xdg-user-dirs{u} xdg-user-dirs-gtk{u}
The following packages will be upgraded:
acpid alsa-base alsa-utils cpp-4.4 cpp-4.5 cups cups-bsd cups-client
cups-common cups-ppdc gcc-4.4 gcc-4.4-base gcc-4.5 gcc-4.5-base
gcc-4.6-base gcj-4.4-base gcj-4.4-jre gcj-4.4-jre-headless
gcj-4.4-jre-lib libasound2 libcups2 libcupscgi1 libcupsdriver1
libcupsimage2 libcupsmime1 libcupsppdc1 libdb4.7 libdb4.7-java
libdb4.7-java-gcj libdv4 libgcc1 libgcj10 libgcj10-awt libgfortran3
libgomp1 libgphoto2-2 libgphoto2-l10n libgphoto2-port0 libimobiledevice1
libpangomm-1.4-1 libquadmath0 libreoffice libreoffice-base
libreoffice-base-core libreoffice-calc libreoffice-common
libreoffice-core libreoffice-draw libreoffice-emailmerge
libreoffice-filter-binfilter libreoffice-filter-mobiledev libreoffice-gcj
libreoffice-gnome libreoffice-gtk libreoffice-help-en-us
libreoffice-impress libreoffice-java-common libreoffice-math
libreoffice-report-builder-bin libreoffice-style-galaxy
libreoffice-style-tango libreoffice-writer libstdc++6 libv4l-0
libva-x11-1 libva1 linux-sound-base python-apt python-debian
python-gobject-cairo python-twisted-bin python-twisted-core
python-twisted-web python-uno ttf-lyx ttf-opensymbol uno-libs3 ure
78 packages upgraded, 0 newly installed, 226 to remove and 3 not upgraded.
Need to get 182 MB of archives. After unpacking 809 MB will be freed.
Do you want to continue? [Y/n/?]
Re: Does anyone use "APT-LISTBUGS"?
Yes--looks VERY bad---I'd wait a bit to see what will settle out.........
Re: Does anyone use "APT-LISTBUGS"?
Thanks autocrosser.autocrosser wrote:It runs with Apt-get & Aptitude---A total "must-have"----nice to get the "do you really want to install this?" warning Generally sends me to bug reports to see why, and allows time to think about that upgrade.....You would see it much more if you were running Experimental sources....I see it about 2~3 times a week.....
I did notice that it runs "silently" in the background (unless there is a reported bug), when I did my updates this morning.
For the first time, I noticed the "ckecking for bugs" section. Nothing in testing, but I am sure I will see something in "SID" sometime this week.
----------------------------------
Dawgdocdawgdoc wrote:Gene,
I use it routinely before doing upgrades. If you runit will output Grave, Critical and Serious bugsCode: Select all
apt-listbugs list <packagename>
If you runit will output Grave, Critical, Serious, Important, Normal, Minor, and Wishlist bugs. If you only wanted to see the Important and Normal bugs you would enterCode: Select all
apt-listbugs list <packagename> -s all
To find bugs still present in a particular versionCode: Select all
apt-listbugs list <packagename> -s important,normal
such as apt-listbugs list gdm3/2.30.5-9Code: Select all
apt-listbugs list <packagename/versionnumber>
Thanks for the tips on usage. I will be using those as well.
Very nice addition. Surprised I dont see more mention of it..
Re: Does anyone use "APT-LISTBUGS"?
I use it for quite a long time. It saved my a** once.
Another nice app is debdelta
Another nice app is debdelta
Re: Does anyone use "APT-LISTBUGS"?
yeah, is a great app, i've been using for a long time.Another nice app is debdelta
thanks dawgdoc
Re: Does anyone use "APT-LISTBUGS"?
nice!
apt-listbugs needs to be integrated into synaptic as a tab...
apt-listbugs needs to be integrated into synaptic as a tab...
Re: Does anyone use "APT-LISTBUGS"?
I've been using it for some time and it warned me a couple of days ago about two bugs which I'm "holding" since:
Code: Select all
grave bugs of xserver-xorg-core (2:1.7.7-13 -> 2:1.9.5-1) <forwarded>
#622406 - xorg: crash in drmmode_output_detect() on console switch
grave bugs of udev (166-1 -> 167-1) <marked as done in some version>
#621036 - udev should not assume that /run works just because it exists (Fixed: udev/167-2)
Summary:
udev(1 bug), xserver-xorg-core(1 bug)
Re: Does anyone use "APT-LISTBUGS"?
Definitely a must have if you run sid, apt-listchanges is another useful app.
Of course so is smxi, but it isn't in the repos.
Of course so is smxi, but it isn't in the repos.
Re: Does anyone use "APT-LISTBUGS"?
When I see any Grave, Serious or Critical bugs I will usually wait to install. If these bugs are in the <forwarded> or <marked as done in some version groups I have gotten where I am only waiting a few days to install. I think the <forwared> bugs already apply to the version of the package/app which I am using. I am a little less sure about the <marked as done...> bugs because it does not tell you which version it is that might have the bug fixed.evilgoldy wrote:I've been using it for some time and it warned me a couple of days ago about two bugs which I'm "holding" since:Code: Select all
grave bugs of xserver-xorg-core (2:1.7.7-13 -> 2:1.9.5-1) <forwarded> #622406 - xorg: crash in drmmode_output_detect() on console switch grave bugs of udev (166-1 -> 167-1) <marked as done in some version> #621036 - udev should not assume that /run works just because it exists (Fixed: udev/167-2)
Re: Does anyone use "APT-LISTBUGS"?
Well, after I made the previous I went searching to see if I was working off of correct assumptions. I was not. <forwarded> does not mean what I thought it meant. Which only took a little consideration to figure out, that was the reason I wanted to check my self.
From the Debian Administration site page on Using the Debian bug-tracking system
From the Debian Administration site page on Using the Debian bug-tracking system
The page explains all of the severities and the states, it also tells the proper way to report a bug.Forwarded - The bug has been reported to the upstream maintainer as it requires work on their part.