Bug#1066116: libssl3: 3.1.4-2 NEWS entry seems incorrect

2024-03-12 Thread Calum McConnell
Package: libssl3
Version: 3.1.5-1
Severity: minor

The news entry for 3.1.4-2 says, "TLSv1.0, TLSv1.1 and DTLS 1.0 work only at 
security level 0 (it was
  previously allowed at security level 0)"

By my reading, this is saying that 3.1.4-2 changes legacy TLS to work only at 
security level zero,
from the previous state of... them working only at security level zero.  In 
other words, that there
is no change.

I couldn't find the commit that changed this, so I can't say what the 
parenthetical should contain;
please consider either dropping the "it was previously allowed..." section, or 
changing it to
"allowed at security level 2" or whatever the correct answer is.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libssl3 depends on:
ii  libc6  2.37-15

libssl3 recommends no packages.

libssl3 suggests no packages.

-- no debconf information



Bug#1020677: httraqt: Segfault upon mirroring initiation

2022-09-24 Thread Calum McConnell
Package: httraqt
Version: 1.4.9-5
Severity: grave
Justification: renders package unusable

As written: I cannot use the package to complete any mirroring operation.
The program crashes a seccond after you start the mirroring, before any
of the download statistics are displayed (though the locations they will
appear in are)

My first attempt to run it printed out the following messages on STDOUT 
when the mirroring started:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QObject::connect: No such signal QThread::terminated ()
QObject::connect:  (receiver name: 'MainWindow')
Segmentation fault

My second attempt to run (resuming the first download, only adjusting it to a 
debug-level log) printed the following
STDOUT message

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QObject::connect: No such signal QThread::terminated ()
QObject::connect:  (receiver name: 'MainWindow')
Mirror launched on Sun, 25 Sep 2022 00:03:56 by HTTrack Website 
Copier/3.49-2+libhtsjava.so.2 [XR'2014]
mirroring https://tomlehrersongs.com/ +*.bmp +*.tif +*.ico +*.jpeg +*.7z +*.exe 
+*.rar +*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc +*.pdf 
+*.tex +*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob +*.wav 
+*.rm +*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg +*.css 
+*.js +*.mp3 -ad.doubleclick.net/* with the wizard help..
Segmentation faulthrersongs.com/robots.txt (119 bytes) - OK

Attached is the debug-level log file produced on the second run



-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages httraqt depends on:
ii  libc6   2.34-8
ii  libhttrack2 3.49.2-1.1+b1
ii  libqt5core5a5.15.4+dfsg-5
ii  libqt5dbus5 5.15.4+dfsg-5
ii  libqt5gui5  5.15.4+dfsg-5
ii  libqt5widgets5  5.15.4+dfsg-5
ii  libstdc++6  12.2.0-3

httraqt recommends no packages.

httraqt suggests no packages.

-- no debconf information
HTTrack3.49-2+libhtsjava.so.2 launched on Sun, 25 Sep 2022 00:03:56 at 
https://tomlehrersongs.com/ +*.bmp +*.tif +*.ico +*.jpeg +*.7z +*.exe +*.rar 
+*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc +*.pdf +*.tex 
+*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob +*.wav +*.rm 
+*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg +*.css +*.js 
+*.mp3 -ad.doubleclick.net/*
(httraqt -q -%i -i https://tomlehrersongs.com/ -%e0 -C1 -%P -n -x -s2 -Z -%s 
-%u -N0 -p7 -D -a -K0 -m0,0 -c8 -%k -f2 -A0 -F "Mozilla/5.0 (X11; U; Linux 
x86_64; rv:33.0) Gecko/20100101 Firefox/33.0" -%F "" -%l ua,en -O 
"/home/calum/My Web Sites/Tom Lehner/" +*.bmp +*.tif +*.ico +*.jpeg +*.7z 
+*.exe +*.rar +*.gz +*.tgz +*.tar +*.zip +*.ps +*.txt +*.rtf +*.docx +*.doc 
+*.pdf +*.tex +*.odt +*.wmv +*.wma +*.ac3 +*.vid +*.swf +*.qt +*.mkv +*.vob 
+*.wav +*.rm +*.mp2 +*.asf +*.avi +*.mpeg +*.mpg +*.mov +*.png +*.gif +*.jpg 
+*.css +*.js +*.mp3 -ad.doubleclick.net/* )

Information, Warnings and Errors reported for this mirror:
note:   the hts-log.txt file, and hts-cache folder, may contain sensitive 
information,
such as username/password authentication for websites mirrored in this 
project
do not share these files/folders if you want these information to 
remain private

00:03:56Warning:* security warning: maximum bandwidth limited 
to 25 to avoid server overload
00:03:56Debug:  engine: init
00:03:56Debug:  reallocated 256 new link placeholders
00:03:56Debug:  reallocated 32768 new bytes of strings room
00:03:56Debug:  Cache: enabled=1, base=/home/calum/My Web Sites/Tom 
Lehner/hts-cache/, ro=0
00:03:56Debug:  Cache: rename /home/calum/My Web Sites/Tom 
Lehner/hts-cache/new.zip -> /home/calum/My Web Sites/Tom 
Lehner/hts-cache/old.zip (0x7fa61c081974 0x7fa61c07f974)
00:03:56Debug:  Cache: successfully renamed
00:03:56Debug:  Cache: size 0
00:03:56Debug:  Cache: no cache found in /home/calum/My Web Sites/Tom 
Lehner/hts-cache/
00:03:56Info:   engine: start
00:03:56Debug:  Wait get: primary/primary
00:03:56Info:   Warning: could not detect encoding for: primary/primary
00:03:56Info:   engine: check-html: primary/primary
00:03:56Debug:  engine: preprocess-html: primary/primary
00:03:56Debug:  scanning file primary/primary (/home/calum/My Web 
Sites/Tom Lehner/index.html)..
00:03:56Debug:  link detected in html (tag): https://tomlehrersongs.com/
00:03:56Debug:  engine: save-name: 

Bug#799354: gnome-shell segfault libgjs

2021-10-29 Thread Calum McConnell
Package: gnome-shell
Version: 3.38.6-1~deb11u1
Followup-For: Bug #799354
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I can confirm that this still exists in the current version.  

Error messages:
Oct 29 21:56:17 CalumsBeastlyLaptop kernel: show_signal_msg: 81 callbacks 
suppressed
Oct 29 21:56:17 CalumsBeastlyLaptop kernel: gnome-shell[5343]: segfault at 31 
ip 7f26690661c0 sp 7ffdeeeda358 error 4 in libgjs.so.0.0.0[7f26>
Oct 29 21:56:17 CalumsBeastlyLaptop kernel: Code: c0 74 07 48 8b 40 18 c3 66 90 
53 48 89 fb 48 8b 7f 28 e8 e3 06 00 00 48 8b 43 28 5b c3 66 66 2e 0f >

While I don't recall the exact details of what caused this, I can provide more 
of the log if desired

- -- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 
'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  evolution-data-server3.38.3-1
ii  gir1.2-accountsservice-1.0   0.6.55-3
ii  gir1.2-atspi-2.0 2.38.0-4
ii  gir1.2-freedesktop   1.66.1-1+b1
ii  gir1.2-gcr-3 3.38.1-2
ii  gir1.2-gdesktopenums-3.0 3.38.0-2
ii  gir1.2-gdm-1.0   3.38.2.1-1
ii  gir1.2-geoclue-2.0   2.5.7-3
ii  gir1.2-glib-2.0  1.66.1-1+b1
ii  gir1.2-gnomebluetooth-1.03.34.3-2
ii  gir1.2-gnomedesktop-3.0  3.38.5-3
ii  gir1.2-gstreamer-1.0 1.18.4-2.1
ii  gir1.2-gtk-3.0   3.24.24-4
ii  gir1.2-gweather-3.0  3.36.1-3
ii  gir1.2-ibus-1.0  1.5.23-2
ii  gir1.2-mutter-7  3.38.6-2~deb11u1
ii  gir1.2-nm-1.01.30.0-2
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-pango-1.0 1.46.2-3
ii  gir1.2-polkit-1.00.105-31
ii  gir1.2-rsvg-2.0  2.50.3+dfsg-1
ii  gir1.2-soup-2.4  2.72.0-2
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gjs  1.66.2-1
ii  gnome-backgrounds3.38.0-1
ii  gnome-settings-daemon3.38.2-1
ii  gnome-shell-common   3.38.6-1~deb11u1
ii  gsettings-desktop-schemas3.38.0-2
ii  gstreamer1.0-pipewire0.3.19-4
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-13+deb11u2
ii  libcairo21.16.0-5
ii  libecal-2.0-13.38.3-1
ii  libedataserver-1.2-253.38.3-1
ii  libgcr-base-3-1  3.38.1-2
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libgirepository-1.0-11.66.1-1+b1
ii  libgjs0g 1.66.2-1
ii  libgles2 1.3.2-1
ii  libglib2.0-0 2.66.8-1
ii  libglib2.0-bin   2.66.8-1
ii  libgnome-autoar-0-0  0.2.4-3
ii  libgnome-desktop-3-193.38.5-3
ii  libgraphene-1.0-01.10.4+dfsg1-1
ii  libgtk-3-0   3.24.24-4
ii  libical3 3.0.9-2
ii  libjson-glib-1.0-0   1.6.2-1
ii  libmutter-7-03.38.6-2~deb11u1
ii  libnm0   1.30.0-2
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpolkit-agent-1-0  0.105-31
ii  libpolkit-gobject-1-00.105-31
ii  libpulse-mainloop-glib0  14.2-2
ii  libpulse014.2-2
ii  libsecret-1-00.20.4-2
ii  libsystemd0  247.3-6
ii  libwayland-server0   1.18.0-2~exp1.1
ii  libx11-6 2:1.7.2-1
ii  libxfixes3   

Bug#986474: Out of bullseye

2021-07-27 Thread Calum McConnell
Control: severity -1 normal
thanks

Looks like i2p got kicked out of Bullseye for this: oh, well.



Bug#990426: www.debian.org: Clarify status of list of old TC decisions

2021-07-26 Thread Calum McConnell
On Thu, 2021-07-08 at 18:08 -0700, Sean Whitton wrote:
> Hello,
> 
> On Thu 08 Jul 2021 at 09:12AM +02, Raphael Hertzog wrote:
> 
> > Hi,
> > 
> > On Mon, 28 Jun 2021, Sean Whitton wrote:
> > > -NB that decisions from before the 1st of April 2002 are not yet
> > > -recorded here.
> > > +NB that no decisions from before the 1st of April 2002 are yet
> > > recorded
> > > +here yet.
> > 
> > That wording doesn't seem correct for me. Maybe:
> > « Note that no decisions from before the 1st of April 2002 are
> > recorded
> > here. »
> > or
> > « Note that decisions from before the 1st of April 2002 have not been
> > recorded here. »
> 
> There should not be two 'yet's, indeed.  Thanks.
> 
> > >  Formal nontechnical and procedural decisions
> > > 
> > > @@ -337,8 +337,8 @@ recorded here.
> > > 
> > >  
> > > 
> > > -NB that decisions from before the 31st of January 2002 are not
> > > yet
> > > -recorded here.
> > > +NB that no decisions from before the 31st of January 2002 are
> > > recorded here
> > > +yet.
> 
> This one doesn't have the same problem and I think is fine.
> 

I think I understand Raphael's point: the wording felt a bit awkward to me
as well on a first read.  The "no" should go with the verb, not the
subject, and it's a mile away.  Plus, I think there's tense weirdness
going on with the 'yet' as well: 'yet' indicates past actions, and 'are'
indicates the present tense.  

It should probably be:

+NB that all decisions from before the 31st of January 2002 have yet to
be recorded here   

Alternatively, since I think you're trying specifically to remove the "not
yet" in the original, try just getting rid of the 'yet': it doesn't add
much.

+NB that no decisions from before the 31st of January 2002 have been
recorded here 

Or, (and this is the option I personally will be taking), simply ignore
this tiny bit of subjectively awkward english, stop being overly pedantic
about a tiny phrase that doesn't matter, thank the person adding a much
needed note to an out of date page, and take a nap while contemplating the
silliness of language.

Looking forward to his nap,
Calum M


signature.asc
Description: This is a digitally signed message part


Bug#990895: Fwd: Re: Bug#990895: httraqt: Apparently installs entire program in /usr/share/doc/

2021-07-10 Thread Calum McConnell
Resending because I am an idiot who never remembers to reply-all


> On Sat, 2021-07-10 at 21:17 +0200, Anton Gladky wrote:
> > Am Sa., 10. Juli 2021 um 21:11 Uhr schrieb Calum McConnell
> > :
> > > 
> > > I have no idea how else to describe how to reproduce it: the issue
> > > is happening on every run, regardless of what I do, or if I
> > > reinstall.  The CLI httrack package works fine.  The issue manifests
> > > as two error messages popping up, saying the localization files
> > > couldn't be found, followed by a segmentation fault.
> > > 
> > 
> > 
> > If you can create a core-file or run the package through gdb to
> > produce the stack trace, it could help to investigate the issue
> > deeper.  Do not forget to use dbgsym-package for more debug-
> > information.
> 
> I installed the dbgsym packages I could think of: this is the result
> 
> > Thread 1 "httraqt" received signal SIGSEGV, Segmentation fault.
> > QMenu::setTitle (this=0x0001, text=...) at widgets/qmenu.h:65
> > 65 widgets/qmenu.h: No such file or directory.
> > (gdb) bt
> > #0 QMenu::setTitle(QString const&) (this=0x0001, text=...) at
> > widgets/qmenu.h:65
> > #1 0x5558c7bf in HTTraQt::translateActions() ()
> > #2 0x5558e244 in HTTraQt::setLangGUI() ()
> > #3 0x555937c5 in HTTraQt::HTTraQt(QWidget*,
> > QFlags) ()
> > #4 0x5557844b in main ()
> > (gdb) print text
> > $1 = (const QString &) @0x7fffddc8: {static null = { > fields>}, d = 0x5560ff10}
> > (gdb) 
> > 
> 
> > > The AMD64 package version that is currently in both sid and bullseye
> > > is definitely dropping all of it's files into
> > >
> > /usr/share/doc/: https://packages.debian.org/sid/amd64/httraqt/filelist
> > >  shows this.  I'm pretty sure that's the root of the issue.   In
> > > previous versions of the package, those files were not placed in
> > > /usr/share/doc
> > > 
> > 
> > 
> > I do not see any issue there at all. Files are placed in a proper
> > folder.
> 
> /usr/share/doc/ is for documentation.  You package is placing into that
> folder files like /usr/share/doc/httraqt/lang/English.utf.gz , which
> appears to be a list of translation strings for the program itself.
>  This is not a proper folder for that file.  Previous versions of the
> package did not install anything other than documentation in this
> folder, and held that file in /usr/share/httraqt/lang/English.utf.gz ,
> where it belongs.
> 
> Are you running the latest version of httraqt, as it appears in
> Bullseye?
> 



signature.asc
Description: This is a digitally signed message part


Bug#990895: httraqt: Apparently installs entire program in /usr/share/doc/

2021-07-10 Thread Calum McConnell
On Sat, 2021-07-10 at 20:59 +0200, Anton Gladky wrote:
> Control: gravity -1 minor
> Control: tags -1 +moreinfo +unreproducible
> 
> Thanks for the bug report,
> 
> I am not able to reproduce the issue. Please provide more information
> about
> how to reproduce it. It looks like something is broken on your side. Try
> to
> install another similar package.
> 
> Regards
> 
> Anton


I have no idea how else to describe how to reproduce it: the issue is
happening on every run, regardless of what I do, or if I reinstall.  The
CLI httrack package works fine.  The issue manifests as two error messages
popping up, saying the localization files couldn't be found, followed by a
segmentation fault.

The AMD64 package version that is currently in both sid and bullseye is
definitely dropping all of it's files into
/usr/share/doc/: https://packages.debian.org/sid/amd64/httraqt/filelist sh
ows this.  I'm pretty sure that's the root of the issue.   In previous
versions of the package, those files were not placed in /usr/share/doc



signature.asc
Description: This is a digitally signed message part


Bug#990895: httraqt: Apparently installs entire program in /usr/share/doc/

2021-07-10 Thread Calum McConnell
Package: httraqt
Version: 1.4.9-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Any attempt to run this package (on my system) fails: a check through apt-file 
would make it seem that
the whole package (including the localization files that it needs to run) is 
installed to /usr/share/doc.

It doesn't appear to look for the files there, hence the problem.  Also, there 
are some weird double slashes
in the stat() calls: it might be a multi-step issue.


- -- System Information:
Debian Release: 11.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages httraqt depends on:
ii  libc6   2.31-12
ii  libhttrack2 3.49.2-1.1
ii  libqt5core5a5.15.2+dfsg-9
ii  libqt5dbus5 5.15.2+dfsg-9
ii  libqt5gui5  5.15.2+dfsg-9
ii  libqt5widgets5  5.15.2+dfsg-9
ii  libstdc++6  10.2.1-6

httraqt recommends no packages.

httraqt suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAmDp5sAdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzJB7RAApNrG6MnIV4prktVA
fhDDWVG+RyyQ3YDahXRSgjzz6DqS8Mt8qiZ0yHJhwXlosH34RU2WoFsN65IiDqJu
l4wZVPkj9O1o9mmWisF2KBMySho96Ewdso2ieHaQ9sO6VWxAp6hWHbyoplWYnwg6
mSwll9nRIyLG5FqLKnNHTmQLulghnQmUoco2jjV6/SBdS5PStinyIcMoRMCNfV/X
9yVxbBgPxEu9G9UyfTtfJZ9YKD4MbRG3c6XzI3k7BhFovuJnjTtK4sOyJH/mMN9w
6dGuOOBmsHiuwLPJthajMc5V1H4+/YVxlTRpjHna+c3CwyE6RWek0Su+H4sPTpIc
LMT5C5SaMy9y85WTORblbHvAM7+Zi6WmBOzEvTZegDTZzrGz7GJNy76WE8nZQ2Ml
EmrFIKtRQolOIxn/SDZKBKClg2j3vgF0FCr9vNcabKGvKIxqSCsmniho2E/YeOBA
xL3mQkSedW+3Jomp+n2WqrZ9JP2Mbp3x2lFia4714ieU3E+s7J6H9FQ6rYAmGhYM
CSjlK1zarZrk96nnLL29K4qMriq22ma5JfyNs43kiC5mEzttMRw+lrcY/X3TlSMx
WH6FE31b28SOYdjG0rXRbvBXJ14JxboLMVnkrDgmLabwIv1NntHZzGWlsU6WJWIf
6axioF556NZsCW6cDoSOs/dGBFg=
=Ig/8
-END PGP SIGNATURE-



Bug#989156: topydo: Prints "module not found" errors on every nontrivial invokation

2021-05-26 Thread Calum McConnell
Package: topydo
Version: 0.14-4
Severity: important
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Every use of topydo on my system (other than simply stating the name and getting
a task list) results in a ModuleNotFound error being printed.

I am marking this as "Important" because the package is still usable: despite
the error, it is reading my commands just fine.  Spotting the output takes
some more thought, but is still possible.

The issue looks to be a missing dependency: python3-configargparse exists and 
is packaged for Debian, but was not installed on my system.  After installing
it, the issue went away.

Sample broken output:

$ topydo add hi
Traceback (most recent call last):
  File "/usr/bin/todo.txt-base", line 8, in 
from todo_txt_base import entry_points
  File "/usr/share/todo.txt-base/todo_txt_base/entry_points.py", line 13, in 

import todo_txt_base.tdtbackup as tdtbackup
  File "/usr/share/todo.txt-base/todo_txt_base/tdtbackup.py", line 7, in 

import configargparse
ModuleNotFoundError: No module named 'configargparse'
|  2| 2021-05-26 hi
Traceback (most recent call last):
  File "/usr/bin/todo.txt-base", line 8, in 
from todo_txt_base import entry_points
  File "/usr/share/todo.txt-base/todo_txt_base/entry_points.py", line 13, in 

import todo_txt_base.tdtbackup as tdtbackup
  File "/usr/share/todo.txt-base/todo_txt_base/tdtbackup.py", line 7, in 

import configargparse
ModuleNotFoundError: No module named 'configargparse'


- -- System Information:
Debian Release: 11.0
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages topydo depends on:
ii  python33.9.2-3
ii  python3-arrow  0.17.0-1

Versions of packages topydo recommends:
ii  python3-icalendar   4.0.3-4
ii  python3-prompt-toolkit  3.0.14-1
ii  python3-urwid   2.1.2-1
ii  python3-watchdog1.0.2-2
ii  todo.txt-base   2.3

topydo suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAmCvF5QdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzLAPg/9F9zGlTVo1muhwHWf
DapkXKDTffiWfhhBR1sB870KHXIAc0faluaw49FQBtYS4Rq90sLC7u/qI1a5CmS4
NXsRbwZ3Okk5xiohAm6zobMHmYQ6dmaZOQdPgkXlIP+esmTtwpBpg4I/cbV7XQps
RY2+kSxUbacDpGUhY1Tyy49ZMb0ReDIrIPm1ejqglK/78MxwOQSWNl8TqC+XVkp8
TN6PKGxyGjOaRF+l36K5vCF+zQkoZdTPhi53FNGqYE6ew9NuuBsDnsbEq4kpFE0L
YO+Ibhk/RquWcY1pnDjWm8qG+xfbQ38lcCzir8DWlPlmy8D9okvfRqm9kRASI5ev
egRGQxiLETwg1X5g6d1TquxMZm1/xF90rz9CTuwUTtyV6IqRfogcnWwGZvYeYoMX
OxKZKOkK2J4yR5+GDvoUJBErMj0vLy8vjHldXjq1xsJvutPPTAAn88unuGZbjKq2
h6tLgyKf7W1bHPAODzm9cVdwoiWp+LbVYtes/6LZwZAT2ez2JwNXRK2CI3Aqt3F+
dwcMb7V73SenUZCVqHR41Th+UTctVq9cyvz2EO8YYwf1FQlSwNUgTeiclyrjFcdY
+PXOkL8ydAKksai9lD26ZLtd63/dGnqftdaNiL9WsLG+fySfhqhrnX7z4d9Po0P/
UlTqppBND1KS8MS0BVghazCaqAI=
=pXYH
-END PGP SIGNATURE-



Bug#986303: openssh-client: tries to place known_hosts in parent directory when .ssh is a symlink

2021-04-02 Thread Calum McConnell
Package: openssh-client
Version: 1:8.4p1-5
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I try to track all configuration seperately, which means
symlinking dotfiles in $HOME to a seperate folder, that is
a git repositiory.  SSH doesnt yet support the XDG spec for
home folders (AFAIK), which is fine, but it stubbornly
refuses to use the correct known_hosts file.

SSH will instead ignore the $HOME/.ssh/known-hosts file, which
is actually stored at $GIT-REPO-OF-DOTFILES/.ssh/known-hosts.
It tries to use $GIT-REPO/known-hosts instead, creating the file
as needed, and prompting that previously-connected hosts are
unknown.

I solved this issue simply by hard linking the proper file
and the one SSH thinks it needs.  I'd appreciate it if this
could be fixed longer-term, however.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.20.7.1
ii  libc6 2.31-10
ii  libedit2  3.1-20191231-2+b1
ii  libfido2-11.6.0-2
ii  libgssapi-krb5-2  1.18.3-4
ii  libselinux1   3.1-3
ii  libssl1.1 1.1.1k-1
ii  passwd1:4.8.1-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages openssh-client recommends:
ii  xauth  1:1.1-1

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
ii  monkeysphere  0.43-3.1
ii  ssh-askpass   1:1.2.4.1-10+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAmBnUz4dHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzKYyxAA2d+4xly0rt2Ixl/Y
A77cScYWoI2wo8I+XimZb6rm4HaHNGhDL19wNBZCYf8R+F2cZSRQKsPHXhBimiYE
ysTxqrwnPyk6c2USvA8sWJiOqM8Pb74+1WDEfo2WjVbk95xxEAacYk5zIfuAN4q1
7Qf9qIwJKbBNxU5ZKCBVWTlSHQMT3554wjXLixPVFF0WgmNWTGdVOSO1ADmjaXNO
I/vPmPvEkxFpxELIPEgJOc3lXGD4fRrGz+xRMGbWI9zC+fzDMEAZPZ705bwWzPSL
Mx4V/PkZOh4oXm2YuhFU45IAUcumCfOoKXZHdNwApEpyOvGaGjYaQ9cQFTYVPOCW
/mmHf6jPc+sO+2gYAS2IqP1OTzUIZwX7YwNMvJmke95MdDzAYhA/kcx6peJao6vJ
Ya+N6jwSG5kHQu38BhEdynfHq639soFW3v0ZA1xrNdCyObsUIOCIU/Uyj6CEaomI
eYy8MayZO5jEghxsnTXNbFgOZxj09hZ4UJwqzmIosd8ZuPF0mvC53jL56HkJH3Jj
oZ7RKPwYDFUfwEvZ4hdN6KmCbwXSLniR+tEgUmahymMk3oNWC/AsEKJTBRtXdtYN
hKuaPDevqMQK5s20VxzAypRV4t24FDtrxmN6pNBd18anTpXuLoV0JOIViXb9umeC
P1DBfJ9hPmAF2NsI0AJmp8vL1a8=
=z2Ei
-END PGP SIGNATURE-



Bug#985766: closed by Debian FTP Masters (reply to se...@debian.org (Steinar H. Gunderson)) (Bug#985766: fixed in plocate 1.1.6-1)

2021-04-02 Thread Calum McConnell
Thank you!


signature.asc
Description: This is a digitally signed message part


Bug#985766: plocate-updatedb.timer: fires at exactly midnight

2021-03-22 Thread Calum McConnell
Package: plocate
Version: 1.1.5-1
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The current timer shipped by plocate simply fires the
service every day at midnight.  That is bad practice,
since if everyone did it, computers would all hang
at midnight as they get swamped with expiring timers.

Instead, use SystemD's RandomizedDelaySec and
AccuracySec to distribute jobs.  Adding 
RandomizedDelaySec=12h and AccuracySec=20min to the
timer unit file would cause SystemD to run the update
job at some point in the morning, and have the freedom
to align it with other jobs as needed.

Thank you!
Calum


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plocate depends on:
ii  libc6   2.31-9
ii  libgcc-s1   10.2.1-6
ii  libstdc++6  10.2.1-6
ii  liburing1   0.7-3
ii  libzstd11.4.8+dfsg-2.1

plocate recommends no packages.

Versions of packages plocate suggests:
ii  powermgmt-base  1.36
ii  systemd-sysv247.3-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAmBZYOsdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzI2ZA/+LyYskPo/dHnw17Gx
VZXwn3Hl5ZlUQNXVgvz86kgc+ngDauEUtznEZ+enYVtpxUkKNjoWsQ1taqdpq2JT
tsIReZwyeWB/ig3X3/U/VIGxg3OgrNOeMx68AqdHldpUXZav1OVb290yp2XOl4Ep
Yu1/GBmVVLTcTItQQsXg+hYgjgqhl5EfqzlCqxN+EFNvLmrmHoO0vbT0fl0PzobY
GP9Rz8Xddy+Oah8Ovi0FeOVZzkh9o3dTbH6MonTKtMKeGZiweJMiiB13ghZKDUBE
VlWgHavNMt/XiLyBtYPF4ZM1mRLVjx9aZFz9ZqDTDb9FeH+Fhjfe3cxXyINldTui
cSOPTwqhNC8KfS/E8oW+wSWYBKfJjcI003QA3jqTLuWf0a5iSSxZNqNwTguFWz39
7liKfUQPdz9UxwplJ4eYySiO5dgFYZcaXa5WjowlCLhhqNTPuqUyciHA/TxawlQH
5D5x9lS/vy2Zp7iBFFA3mwOvKzlj/kw/GmCGxJrrUxA5c8LMsrnWS/fFKrSYDmvJ
geABRgp67PQjS2aitFStXu0y6Faf48WgvmH1qZ1tecyx9auCAsuWgndrHvfSq2Ue
5sITHHizrATNanK2LXyWGiDdJsR5hSHyBe83PieRdCXFcE+mUBXOF+g8GebdEcnB
qRmu1H2JFeAQg0D1aT4hepnjFFI=
=te/R
-END PGP SIGNATURE-



Bug#985669: RFP: pnpm -- Efficent NPM replacement

2021-03-21 Thread Calum McConnell
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: calumlikesapple...@gmail.com, 
pkg-javascript-de...@lists.alioth.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: pnpm
  Version : 5.18.8
  Upstream Author : Zoltan Kochan 
* URL : https://pnpm.js.org/
* License : MIT
  Programming Lang: Javascript
  Description : Efficent NPM replacement

PNPM is a disk-efficent replacement for the NPM command. It
prevents duplication of package files across projects by hard
linking files to a content-addressed store.  It is a great solution
for developers with limited hard-drive space, or a large number of
projects.

- 

While I would love to package this myself, I do not work with
JavaScript regularally (in part due to ecosystem problems like
NPM's love of duplication).  As such, I am filing this as an RFP,
as opposed to an ITP.



-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAmBXkokdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzI/TxAAsIFoz0j7TLtDJLsi
dN5hbn+SAHg42qDWoWJs5OIkIAWkMOZxT/JIc+KP1dbMM/9nmBYwUHBTAMcK4uwB
DyHEJzRACW4cKsg7oC07O4cq9+7cld25DMpqDyLfOhU1NOO7VT3o94lsCcX17Ntb
Fi5DkdbYEzjVx+/+txM4l6nAMEjF5O3QggnWZwXLpuA8CLiWaLfgcjXSMDNZ37e3
9tNX3gxQd3a7HeLU0ffyhUQ3se1/UfM5jcivGSH6ILn7tV/4ShciVlLPojNYSbIB
vb6GGh2EQFk9CsmEUDZVouDHVDm4A1nNmntnK8x50TIOpUUPJlyCvVUdc+9FYNkb
J3PsD6rwi1wZV9jqpST2gzQi11Q5jFwlc77Gd8cnTQWfwZSSJM309iudHIvoQzeU
mUr6nhKIhWgGih3z/6q2Fvm/dagHE++jm3nhOv7EpXmP9AEXj3CqLGHc0gAXvzyS
zWo6jp+egqqoRlOAPpv6dA6t+egoxQUbgpFgSYRkUdIlttMzywPCI7VFjUT/arp1
D3xNG/O4DeceP0fQhyCWsDxy6fWstiihlw4zj9oP/PHPEqrMv3VQhvJPH7fucgje
vzKV9JztAyps1ppJ4Q2ttVbZMte6HYok+38hSEBOgDYl3tK9L5TjJC4ZDxutP8RZ
AMwHU4KRgQXZWNI8R3MhHok0O7g=
=YNZB
-END PGP SIGNATURE-



Bug#979966: debdelta still contains isAlive()s

2021-01-18 Thread Calum McConnell
On Mon, 2021-01-18 at 14:41 +0100, Steven De Herdt wrote:
> reopen 979966
> thanks
> 
> This report actually concerns 0.65+nmu1: /usr/bin/debdelta is identical
> to the one in 0.65.  Something must have gone wrong in the NMU...
> 
> Thanks for the work on this package!
> -Steven

I can confirm that is true.  It's almost certainly something I screwed up,
and now that A. Mennucc1 is back, the solution will probably be to upload
a new 0.66 rather than a +nmu2.

I'm not sure quite HOW I managed to mess it up, but I have a feeling it is
because I wasn't careful enough in keeping track of what changes I made to
which versions. It's probably the direct result of me using a patch to
copy over the changelog (instead of, you know, just copy-pasting): but as
I prepared the NMU in /tmp, I can't say for sure.  Suffice it to say I am
whacking my head against the wall for not checking one final time whether
there were any more occurences of isAlive().

A. Mennucc, any chance of doing a full upload sometime soon, to hopefully
prevent my mistake from entering Bullseye's final release?

Thanks,
Calum




signature.asc
Description: This is a digitally signed message part


Bug#962203: NMU

2021-01-12 Thread Calum McConnell
Of course I would be willing to help out on package maintenance: I won't
be able to do much this week, but in coming weeks I should be more helpful


signature.asc
Description: This is a digitally signed message part


Bug#962203: NMU

2020-12-28 Thread Calum McConnell
On Tue, 2020-12-29 at 10:36 +0800, Paul Wise wrote:
> On Mon, 14 Dec 2020 17:23:08 -0500 Calum McConnell wrote:
> 
> > I have prepared an NMU for this package.  It is currently at
> > https://mentors.debian.net/package/debdelta/ .  While I need a sponsor
> > to
> > get it into Debian, I am now reaching out to
> > ment...@lists.debian.org to
> > see if I can expedite the process.
> 
> I was looking at sponsoring this, but based on the debdiff it appears
> to have some changes that are not in the patch you posted to the bug.

Yeah, when I tried to build it locally, it failed due to files that are
present in the source package but missing from Git.  I had to manually
generate the PDF docs, and the additional changes were me trying to
automate that process.  However, while the modified commands ran fine on
my testing box and in a testing schroot, they broke spectacularally in the
unstable schroot.  After several hours of adding more build dependencies
to try and make it work, I eventually gave up and just included the PDF I
built locally in the source package.  

If you'd like, I can revert back and generate a more minimal NMU.

> It looks like A Mennucc1 will be working on this issue soon though.

As long as it gets fixed!

Thanks,
Calum


signature.asc
Description: This is a digitally signed message part


Bug#763419: apt ignoring check-valid-until flag

2020-12-17 Thread Calum McConnell
On Fri, 2020-12-18 at 01:15 +, Paul Wise wrote:
> On Thu, Dec 17, 2020 at 10:03 AM Ansgar wrote:
> 
> >     (Bonus points if this keeps the original signature if possible.)
> 
> Two separate signatures is possible for Release+Release.gpg, just
> rename the latter to .old, but what can you do for InRelease? Is it
> possible to have multiple signatures in one blob of signing data? Is
> it possible to take an existing signature and add a second one to it?
> Can the same thing be done for Release.gpg? Do apt, gpg and gpgv cope
> with this sort of thing?
> 

Okay, so maybe my deep dive into old Debian versions was worth it.

If you look at Etch, you will see a Release.gpg with two signatures.  Per
the Etch-era Debian Wiki page on this[1], that's because it was decided
that Etch should be signed with both the 2005 and the 2006, to keep an
upgrade path in place.  Now, due to a bug in apt (fixed in 0.6.43.1), the
systems began to expect both keys to be present, but assuming that there
hasn't been any regressions in that, I believe Apt will work as intended
if we add new signatures by appending them onto the release.gpg.   Apt was
totally fine processing the Etch release file when I tested it: it
complained separately about each key being expired, implying that it would
work of a third, unexpired key was in that list.

Calum

[1]: https://wiki.debian.org/SecureApt#Debian_archive_key_expiry


signature.asc
Description: This is a digitally signed message part


Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails

2020-12-15 Thread Calum McConnell
Package: mariadb-server-10.5
Version: 1:10.5.8-3
Followup-For: Bug #976147
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I can confirm that the bug existed on my install as well.  I encountered it 
while upgrading my Testing installation.

I solved it by using Aptitude's installer instead. 

Below is the resulting history.term entry.  If you need any more information, I 
can provide it.

Start-Date: 2020-12-15  18:11:40
Install: python3-systemd:amd64 (234-3+b4), mariadb-server-core-10.5:amd64 
(1:10.5.8-3, automatic), mariadb-server-10.5:amd64 (1:10.5.8-3, automatic), 
galera-4:amd64 (26.4.6-1+b1, automatic), mariadb-client-10.5:amd64 (1:10.5.8-3, 
automatic), mariadb-client-core-10.5:amd64 (1:10.5.8-3, automatic), 
netcat-openbsd:amd64 (1.217-2)
Upgrade: default-mysql-server:amd64 (1.0.5, 1.0.6), default-mysql-client:amd64 
(1.0.5, 1.0.6)
Remove: mariadb-server-core-10.3:amd64 (1:10.3.24-2), mariadb-server-10.3:amd64 
(1:10.3.24-2), libplymouth4:amd64 (0.9.4-3), galera-3:amd64 (25.3.31-2+b1), 
mariadb-client-10.3:amd64 (1:10.3.24-2), mariadb-client-core-10.3:amd64 
(1:10.3.24-2), libgeos-3.8.1:amd64 (3.8.1-1)
End-Date: 2020-12-15  18:12:38


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server-10.5 depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.74
ii  galera-4  26.4.6-1+b1
ii  gawk  1:5.0.1+dfsg-1
ii  iproute2  5.9.0-1
ii  libc6 2.31-5
ii  libdbi-perl   1.643-3+b1
ii  libpam0g  1.3.1-5
ii  libssl1.1 1.1.1h-1
ii  libstdc++610.2.1-1
ii  lsb-base  11.1.0
ii  lsof  4.93.2+dfsg-1.1
ii  mariadb-client-10.5   1:10.5.8-3
ii  mariadb-common1:10.5.8-3
ii  mariadb-server-core-10.5  1:10.5.8-3
ii  passwd1:4.8.1-1
ii  perl  5.32.0-5
ii  procps2:3.3.16-5
ii  psmisc23.3-1
ii  rsync 3.2.3-2
ii  socat 1.7.3.4-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages mariadb-server-10.5 recommends:
ii  libhtml-template-perl  2.97-1

Versions of packages mariadb-server-10.5 suggests:
ii  mailutils [mailx]  1:3.10-3+b1
pn  mariadb-test   
ii  netcat-openbsd 1.217-2

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/ZXxgdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzKe2g/8CEhJnSVgblGThBuR
BvMZwdXfPh8urmXSE0Gm7SIGvrHom9YoYkgZSnqegxxpUt+07DG8+ApMmyPK88tI
d4deGFNLM8uUFS6xRYACpaps5pLmZ/R4qz3lNAWDEjhEH+Rn8Xqz+sbIztEhryNz
BCQ+ukKOcKFpo7wLiKsyAiyHQNZQxAoNDtMsjVq90MnPdT8jxMOdi+V5jVIqLQb5
71sb1AZ5f/hFd/wserrN8RgZ7f/GkJHeBc+2qJCoDcvjlJuFhZzKR3dHLgOzH8bO
ifEE/hbV419dVYW5fIun9/q9nfr4DmJ4BwoC5VJT8aTx5tucb0CIU5BgLOK0LaFy
aePplNsbbyiWpx0ijpf7ACky/N6a5J7tBjmAnPy+mnUFrGOXvoWyoSkj8Fplkv3G
DNzn6hOhQZlCr3VGxxnupkrN72qID/YAxMB1uS3ou9RnGDYEwh7/2Lz20hB6v8N3
oUFkrs2boZ7Chaps+fVG2j7CHExpTJq5r7ziKFZgRoHesnx6NFrWlitE+kuMoWA4
qbS2JaoDMtCXBwhpX3AJOHkWnzsUau5RxBsqrJuJJVuEej26KsxAkkmJfo6A0vdT
Ht9NynkgQRhiVeEbOLSHHqCc2cU0U9V4J8W3gdwOZt8anIgEk8ok5OuhuME64HkC
2isnyoDM95/vOR7oOFey6HUFEps=
=RFvE
-END PGP SIGNATURE-



Bug#962203: NMU

2020-12-14 Thread Calum McConnell
I have prepared an NMU for this package.  It is currently at
https://mentors.debian.net/package/debdelta/ .  While I need a sponsor to
get it into Debian, I am now reaching out to ment...@lists.debian.org to
see if I can expedite the process.


signature.asc
Description: This is a digitally signed message part


Bug#956836: Can't be packaged without many Javascipt dependencies

2020-12-11 Thread Calum McConnell
Control: retitle -1 RFP: bitwarden -- fully open-source, cross-platform
password manager

Without packaging a massive number of javascript dependencies, from
angular (which might already be in Debian) to keytar, this can't be
packaged.

A person more skilled at javascript than I could probably cut down on
that, but I just can't.  And there is no way I can maintain 6+ new
packages just as dependencies.

Thanks to whoever winds up working on this,
Calum



signature.asc
Description: This is a digitally signed message part


Bug#977121: RFS: debdelta/0.65+nmu1 [NMU] [RC] -- diff and patch utilities which work with Debian packages

2020-12-10 Thread Calum McConnell
Package: sponsorship-requests
Severity: important
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "debdelta":

 * Package name: debdelta
   Version : 0.65+nmu1
 * URL : http://debdelta.debian.net
 * License : GPL-2, Apache-2.0
 * Vcs : https://salsa.debian.org/CalumMcConnell-guest/debdelta
   Section : devel

It builds those binary packages:

  debdelta-doc - diff and patch utilities which work with Debian packages
  debdelta - diff and patch utilities which work with Debian packages

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/debdelta/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/debdelta/debdelta_0.65+nmu1.dsc

Changes since the last upload:

 debdelta (0.65+nmu1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Port to python3.9: Closes: #962203, #954420
   * Attempt to build docs on debian infrastructure: fails in unstable, not 
testing

Additional notes:

With the python 3.9 transition, debdelta is completly unusable, until a 
bog-simple patch is applied.

While working on doing a rebuild for upload to mentors.debian.org, I realized 
that the package, as a whole, needs work in a lot of areas, especially its 
documentation.  The docs weren't built as part of debian/rules, and while I can 
build them on my testing machine and within bullseye chroots, the pdf cannot be 
created in the sid chroot needed for upload to mentors.  After many attempts at 
debugging, I decided to leave it (mostly) alone for now: I left the changes I 
made to get the build onto Debian infrastrucure, however, I executed the 
makefile locally, as the maintainer seems to have done.

I would be happy to take over maintenance of the package, however, it isn't 
officially abandoned yet.


Regards,
- --
  Calum McConnell


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/S/X8dHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzIH3A//SbGmP88KC2qjPWGi
nDRWRKUNzriGtPoCtewSaa//FUcGHkZLXu5Srs98bj/YWtZuevTqAMvjZxnfiluh
u46c54vLabHd094B8nU8c2R/AuPUixMvD9nM7VE60bSQlaIFMVJwhMPL6nP/RUmD
FRowAbpmSm4Gu6ynDC9EpGiOj8wZ0DPQ7Q9SQVpR16csZ+BaCIA7Yagdid5Fc0WB
tjh0oyPgSWhcBV79O4WdSRyU7kWjdEpKJPIeY/7kFDPY5OstwMaCSGTUF049z8Wi
um8eFLZqzvY580Wk4S7Z+GW1O6uePn3SUdz/rXpnsM9XTNVDqM+Lk7MgwyY5ndwB
sbg0y8I96q8e7ojIlsjSjwAWt83WAYlkqeWyF3e0hdsmAERK5cyuCT+0D54+ua4t
cKSx5t8KUMmH2RuQDccb8dNpvvNMPwgFmsjRarLjze9IMHXUhoit+vcY7T437Zce
QBfTOnstdKhLmZGstZ+O+U+sxFEXaI/GtxIZuGEvb8yL2CsCXLPf8AaKfgPOlpoz
0YnI16f2rUNUlLdp/mTn6SuIsUiLo974rxAmf7h2rdVS/CqR+brw8N1NT98EvXqy
DNr5v5e85ftGcHHAV51DJMkhaQarvig7FkYEgxAQzuhg4ovUVAdsgrTt5YZQI4Nj
uRi875tD2Ml+1VkRET+/hpUsd68=
=KpHN
-END PGP SIGNATURE-



Bug#962203: DeprecationWarning: isAlive() is deprecated, use is_alive() instead

2020-12-06 Thread Calum McConnell
Package: debdelta
Version: 0.65
Followup-For: Bug #962203
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have created an attached a patch.  It is also availible as merge request !2 
in the salsa repository.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debdelta depends on:
ii  binutils  2.35.1-3
ii  bzip2 1.0.8-4
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-4
ii  python3   3.8.6-1
ii  python3-requests  2.24.0+dfsg-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages debdelta recommends:
ii  bsdiff   4.3-21+b1
ii  gnupg-agent  2.2.20-1
ii  gnupg2   2.2.20-1
ii  gpg-agent [gnupg-agent]  2.2.20-1
ii  python3-apt  2.1.6
ii  python3-debian   0.1.38
ii  xdelta   1.1.3-9.3
ii  xdelta3  3.0.11-dfsg-1+b1
ii  xz-utils [lzma]  5.2.4-1+b1

Versions of packages debdelta suggests:
ii  debdelta-doc  0.65

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/NHNgdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzK5rA//S3+ySeshMWhTEp38
KOrKKWvR/vGOb2MjPILXU6VJfAcw7tIf/IbzvGkj3QM08f1eF3RElP4UwC4NCpj6
oTEYgq88lE0YTqYrdRJopM70pmcDArzvFpysudonUHJ8k2sUwr/5R18S8BooiGDw
iOs7BaAv3vJNyKfeYSJlIdMLiq1u52z6xooSg92Rb6b/rBC3il5frkpUsy4L/Jid
AHEGDhTAtyvwof/zdyjwVnMQvxoS5lsm5hkc7RNFpndkvRONTWNNOa0raYucbQ3K
vitJ+7BuNZ3GF/yi86+L1krOGpv5E5lbdlmhtqUMd1RcYw1VZpEcJ+3D45dDOxSg
wbIFV+ud+ATXC7yVYMQhDv/S3GSb/sKx7OrLJZX/67BrQZqMM3eB4BXarJe1o9gV
56znmh+hzGoGkzaZJmKHRNdhYK97rWXYts/4pUAnpICDkhMBbQ/D4OgVgA18dRR6
h4CsU+ynf0Z6Xb0bW9tPmkbj0a91mOvqNRvO1E9kwnSolsAjqJQ7HmQp0GLnDQfy
nxdCMGTIQOIWepdF8bi2WiGaSwvK2f2Q1LyxqEMsBf68uH3+IcCxsPKCrZ55w+gy
7NxRvlLwYilTFN20aZSTtFt7ntDPzLy6J9BulukLNjgD1AoW00Y/mlG+Af/hxMhc
fNhgaK9EUfEhOQeqOyoorBwEjok=
=4QZH
-END PGP SIGNATURE-
>From 4821b3f1fdb9118ba3c80b8077af63b5006d6ddb Mon Sep 17 00:00:00 2001
From: Calum McConnell 
Date: Sun, 6 Dec 2020 12:53:52 -0500
Subject: [PATCH] Fix isAlive -> is_alive

---
 debdelta/debdelta | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/debdelta/debdelta b/debdelta/debdelta
index b4a79c1..b7f258c 100755
--- a/debdelta/debdelta
+++ b/debdelta/debdelta
@@ -5460,9 +5460,9 @@ def delta_upgrade_(args):
   #do something useful in the meantime
   debs_down_size=0
   debs_down_time=0
-  if patching_thread.isAlive() and no_delta and VERBOSE > 1 :
+  if patching_thread.is_alive() and no_delta and VERBOSE > 1 :
 logger.info('  Downloading deltas done, downloading debs while waiting for 
patching thread.')
-  while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
+  while patching_thread.is_alive() or ('a' in DEB_POLICY and no_delta):
 if no_delta:
   uri, newdeb  = no_delta.pop()
   thread_returns['downloaduri']=os.path.basename(uri)
@@ -5481,12 +5481,12 @@ def delta_upgrade_(args):
 if http_conns[i] != None :
   http_conns[i].close()
   
-  while patching_thread.isAlive():
+  while patching_thread.is_alive():
 time.sleep(0.1)
 
   #terminate progress report
   thread_returns['STOP']=True
-  while progress_thread != None and progress_thread.isAlive():
+  while progress_thread != None and progress_thread.is_alive():
 time.sleep(0.1)
   
   if DO_PROGRESS:
-- 
2.29.2



Bug#962203: DeprecationWarning: isAlive() is deprecated, use is_alive() instead

2020-12-06 Thread Calum McConnell
Package: debdelta
Version: 0.65
Followup-For: Bug #962203
X-Debbugs-Cc: calumlikesapple...@gmail.com
Control: severity -1 grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The function is removed in Python 3.9, which is now the debian default.
Debdelta-upgrade will now simply crash.  This is not good.

Patching is as easy as a find/replace. Please fix this issue!



- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debdelta depends on:
ii  binutils  2.35.1-3
ii  bzip2 1.0.8-4
ii  libbz2-1.01.0.8-4
ii  libc6 2.31-4
ii  python3   3.8.6-1
ii  python3-requests  2.24.0+dfsg-1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages debdelta recommends:
ii  bsdiff   4.3-21+b1
ii  gnupg-agent  2.2.20-1
ii  gnupg2   2.2.20-1
ii  gpg-agent [gnupg-agent]  2.2.20-1
ii  python3-apt  2.1.6
ii  python3-debian   0.1.38
ii  xdelta   1.1.3-9.3
ii  xdelta3  3.0.11-dfsg-1+b1
ii  xz-utils [lzma]  5.2.4-1+b1

Versions of packages debdelta suggests:
ii  debdelta-doc  0.65

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/NFbAdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzLdMg//RU1jpB2htAenj5tx
e7t1MBIdorjTWUFES2KSJLCFvfOSrLhXpf72xPAu0+kXSEs6VdcmaWZEqIEAjXje
crGFezOx3zKPeV3Yzk3aKWOcftLrlmuDVV5Pgku0KwBtd0Qftgu6t+DemKhUs9Ym
HSlbwlKCsAkikdbNhD+JJ/eIkzERdIUtE3KUM4YHa9LyQEipnE3kdnExrCjn9BZi
7rKQIv6GPpHH9AhwLnbkUuIdoNNeZRhBDcUB9BVJhnrrFhgkB5FF4/22L/DHV6xu
z/ztSf+LiruUmUsR5nK7IH+xwQi8zqk/O1/tChYDWI4EXagMmMhN/rFzrlXmnlJI
oeSxXhGnarKB2fjPqztS53Vd77pjXGWkqQWNQMO9AtmIbHNQ891vr8Hm0Zdd/cGV
KB6uXtySybtHFAJsH2l6IZZgc3ouW+Vhqpn0n8/XcdtQBx7OQFpid/HbYup818fc
9pJOhGEFpq9mtTlje2TUtkKXasl6AbwSPg1+oqmPmmNVlwMT59MMMz2XJeQgLsH/
dUAOd0x3DfsEUq4Nlrcgnyeomk5Jc0mvhJ369CylXJnw9bI71bFiC32kzedz7v+C
dET/HhOWus8IZcEZh4nJj3fhZO/kg2jcyx4wt5vKpzU8Fl6YtkPq3hAWkPgaPolr
PseTA+roHeNtCwowHtdNrSCjmw8=
=0hVv
-END PGP SIGNATURE-



Bug#832958: "the -bit_depth N option is longer functional."

2020-12-02 Thread Calum McConnell
Package: pngcrush
Version: 1.8.13-0.1
Followup-For: Bug #832958
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Update: it no longer gives that warning, and now simply refuses to recognize
the option.  Can the manpage please be edited to reflect that?

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pngcrush depends on:
ii  libc62.31-4
ii  libpng16-16  1.6.37-3
ii  zlib1g   1:1.2.11.dfsg-2

pngcrush recommends no packages.

pngcrush suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl/IZ8UdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzIVqQ/+MlfNdrOZzxwhhtyL
CDZA24EB44ZhHTcHgMJ4GuIpZYnc5mduBQSxrE4FVnJu7lYcQmZNam74HTUk7ivc
t0CAwNFV2js5LwnZ48aEuyRoSQW3M/2rE6wyoXdo7BVNo5nEFenJjdkokK47mrhp
sOJc1q99usSzaWr+zzN0a6TwBok4Xzp5nHM5f7W7zve6EqZAnhyMc3Is0wGG7998
wMpf0NC/p/Ck/aO/84EhnSRrBkWRLu9GiIEA4AxXYl9DAK1pbm5n4GHBNoGhTT4j
PFqksTSmMPpTCqG3cSzG/ry6bbtMeQtwEO3CBhTUEA5P+cDhdjv8N2ucERe2DgE1
VN/nfsyGvMH0efI6MJjG9PVN7s/QB//9QuJgEbdReDzAuPfqjmUiqqLpL0RuyhqR
KjSGfuFNjhPf9xogz6gPw+seOjuiE+RlSmFMNDfLsimOcrvMtz2/9vavo9MrWfEM
r+01R242m2RxMlkLyVWIBifu2qiiRhYI23LGu8BdSUbgZwgPNXGa243gZ8VjMb6V
SjjwmwHzDwOMUKx67MVh9GObS4NEmUHv8pM/KlsNWhxBz7+TZhkC7otWVH0d+syi
OaFg5bT1Th7azv/Yu6JS3quBO2MKRjAo+dJKA1jDZ+UzZnAiriQvGRdA0U7izxxm
NW/mPNqEaJaCcUOWktqDhrQo+s8=
=C873
-END PGP SIGNATURE-



Bug#975657: [Pkg-rust-maintainers] Bug#975657: debcargo: Debcargo, cargo, and other Rust packaging tools are NOT in testing

2020-11-24 Thread Calum McConnell
On Tue, 2020-11-24 at 20:04 +0100, Sylvestre Ledru wrote:
> 
> Hello,
> Le 24/11/2020 à 19:06, Calum McConnell a écrit :
> > Package: debcargo
> > Severity: important
> > X-Debbugs-Cc: calumlikesapple...@gmail.com
> >
> 
> > As the freeze approaches, it becomes more important to make sure that
> > every package desired for the next release is actually
> > present in Debian.  Many of the important rust packages have not been
> > in testing for several months, and must be fixed and updated soon.
> > 
> 
> Do you have a list of packages you have in mind?
> 
> Cargo is in testing (version 0.43.1)
Whoops, yeah.  Rust-cargo isn't, however, which was what I meant (I
thought they were the same: like python3-pip)

But for the most part,  I was only thinking about those core, package
maintenance tools.  I really don't have a list, but I assume all the ones
I am intrested in are connected, and their blocked for mostly the same
reason.
> 



signature.asc
Description: This is a digitally signed message part


Bug#975657: debcargo: Debcargo, cargo, and other Rust packaging tools are NOT in testing

2020-11-24 Thread Calum McConnell
Package: debcargo
Severity: important
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As the freeze approaches, it becomes more important to make sure that every 
package desired for the next release is actually
present in Debian.  Many of the important rust packages have not been in 
testing for several months, and must be fixed and updated soon.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+9S6YdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzKfsA/9FOtEq7p8nsGfR6w/
W4WWAJWJ1KWSNuRpWQsCzngdwQhzDY+XIRW1GZjrpe2+JWyvWDyJgxklBJxUyN4y
TTew6mTDiXOTLNiH3lfQiGabD4uEgR/lvTjktLdmvLnLRu2e8zIF8w/cSi3/lJMw
o5izJlGs6GqSZYCGn4yrZxXWgWGf60cQUXnZLeZokn5LweMTwNva9PivOmiwdd2D
y8EaQjE4VhybzLn+19o4Py3zhyLrBXk1Zuu7xjf0Lthrbw/WuuRxOv7lr3fpwH5v
2hs82f/f1uzK8TqBqcwFYAC1ZMZnIk76xC7Ez07bwtCDySb1CtcOzPElxqPaS62R
ib2bcbZGAgsjWB4Mwz9EF5mpQZsMyBbT5JY1znaZlejoQ4mK1TMKGbbK9LSPobAL
P4/g4+U/1P3PvMuva7MmkLik92WMmDk2Zlzv8L4XMg89UC/VetyPcciAdNY1p6jt
tS12y3AHIVMDb9PH0Hg79fUUkIshciCwLxk/hQEb0HFmUk4NVMFRiiuglQ2EP75q
tCHGKLqcsfzhnGUBfDn7AvvqLRFd5aivCCLza1FmmLnEpo3efb8hgc52+YXfU4Ko
3KP+j7WxrMtzYOaePVCUgulHy894RMMIXEL8X7EZblhlmgvOkTj2tQhxSSlq3DGA
qrvJ9VbfaNKzcTKlgWMhwKp8ASM=
=9vOh
-END PGP SIGNATURE-



Bug#971408: Whoops

2020-11-21 Thread Calum McConnell
Control: reopen -1

I accidentally wrote this bug number, 971408, as the ITP bug that my new
package was closing, number 971407.  As a result, the above message was
sent, and this bug was closed.

I'm sorry for the mistake,
Calum


signature.asc
Description: This is a digitally signed message part


Bug#974013: myrepos: mr list fails to actually list the repositories

2020-11-08 Thread Calum McConnell
On Mon, 2020-11-09 at 10:01 +0800, Paul Wise wrote:
> On Sun, 08 Nov 2020 20:40:50 -0500 Calum McConnell wrote:
> 
> > Just as it says: I get the ending message, saying that all repos were
> > checked,
> > and a set of blank lines where I would expect to see the list of
> > repositories.
> 
> `mr list` works for me.

*sigh* why can't these ever be EASY?

> Is there anything special about your myrepos config?

I attached a (somewhat trimmed and heavily commented) version.  I don't
think there is anything special with it.

> Could you create a new user on your system, check out a single repo,
> register it with myrepos, test `mr list` and report the ~/.mrconfig and
> the results of the test?

It works perfectly (though with a blank space between each entry for some
reason).  .mrconfig is exactly as you'd expect: I attached it as mrconfig-
testuser

Thanks,
Calum

[myrepos.branchable.com]
checkout = git clone 'git://myrepos.branchable.com/' 'myrepos.branchable.com'

[debian]
checkout = git clone 'https://repo.or.cz/r/git/debian.git/' 'debian'
[DEFAULT]
jobs = 6
# Issue still occurs with above line commented out

[GitGud/progit2]
checkout = git clone 'g...@github.com:progit/progit2.git' 'progit2'

[GitGud/packages/whitakers-words]
checkout = git clone 
'g...@salsa.debian.org:CalumMcConnell-guest/whitakers-words.git' 
'whitakers-words'

[GitGud/packages/apt]
checkout = git clone 'https://salsa.debian.org/apt-team/apt.git' 'apt'

[GitGud/school/physics_with_smc]
checkout = git clone 'g...@github.com:zimmermant/physics_with_smc.git' 
'physics_with_smc'


#Only non-standard entry: upstream posts a constantly moving tag, which Git 
hates.
[GitGud/packages/endless-sky]
pre_fetch = git tag -d continuous
checkout = git clone 'g...@github.com:endless-sky/endless-sky.git' 'endless-sky'


# More packages go down here, all following the same, vanilla pattern
# Issue occurs regardless of which subfolder I call mr from
# There is a symling in GitGud, but it's a local repository, not registered 
with mr

# And yes, I am storing (almost) every git repo on my machine in a directory 
that
# tells the user to 'git gud'


signature.asc
Description: This is a digitally signed message part


Bug#974013: myrepos: mr list fails to actually list the repositories

2020-11-08 Thread Calum McConnell
Package: myrepos
Version: 1.20180726
Severity: normal
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Just as it says: I get the ending message, saying that all repos were checked,
and a set of blank lines where I would expect to see the list of repositories.

As a side note, the other, seperatly reported bugs, describe how command-line
options don't override the config file options, which is an annoyance.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages myrepos depends on:
ii  perl  5.30.3-4

Versions of packages myrepos recommends:
ii  libfile-homedir-perl  1.006-1
ii  libhtml-parser-perl   3.75-1
ii  libio-pty-easy-perl   0.10-1
ii  libwww-perl   6.49-1

Versions of packages myrepos suggests:
pn  ack | ack-grep
ii  brz [bzr] 3.1.0-5
ii  bzr   2.7.0+bzr6622+brz
ii  curl  7.72.0-1
pn  cvs   
pn  darcs 
ii  dgit  9.12
pn  fossil
ii  git [git-core]1:2.28.0-1
pn  git-annex 
pn  git-big-picture   
pn  git-svn   
ii  gitk  1:2.28.0-1
pn  kdesdk-scripts
ii  liburi-perl   5.05-1
pn  mercurial 
ii  perl-doc  5.30.3-4
pn  stow  
ii  subversion1.14.0-3
pn  subversion-tools  
pn  unison
pn  vcsh  
ii  xdg-utils 1.1.3-2

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+oniIdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzItmA//YLnonEOPAephPab9
Coj7l8wKHpCaXtA74xcMnalSmCl3HbD11IQSExqEq4PwT6XfXiVpmbdcFqVmV5dn
7GFTcLJ1vNuaHPDOh9Zo4hL0cPkhofYK0p+4j+k8eDRRHPPBynsyFo4G3PPdCmgI
I3H39olJkbr5pL2ikSLl09HJm+k81V6M5vIvtXUkibJBjj8rs7pOPL1tXYO6i8bV
nLcYFcFOMuLa3rLMD/n2gqWhXQ7LX4MT1MA+BtmLr/9241XIhGT+TNqqXmSzAWZT
vFYErcsOUaqI4Ypw/iHKSOyNREKTQKdpE8gpPJCwui1vgRiyp0hdiHg07mJ1/dxC
DIneOvfpHo8mAMIqP9JDvskqKUkAKg/XXAhpsAtLXOOmPNGa30C0vz/4qgH9DkXK
bQIRcKpNez9TYu+lorj5BqiDGXMcJAHRhO0qYGYZDejQDacU7qdFGsIaWCRGuR28
jnquDRPCSB6lvnHTygKNGfQall1s0xG6djdEDmq5xj85AOrvJcW9j4CenV9/Yh1Q
j5rxLMBWlSAcKwIZWXSqSeJx49Hhr90LUP/LyyCHSPRF+NUuD7Gv3SSdKb2w2v+P
YuWiwRDbq+o1bdr6YpJ6JphCfuTG6mnA018h59DoMia2789O86M6nH1crL/ROgsp
JrX05Ss706GQUg41clFIHnBMQc8=
=5SWK
-END PGP SIGNATURE-



Bug#973831: gnome-shell: Login hangs after system suspend

2020-11-05 Thread Calum McConnell
Package: gnome-shell
Version: 3.38.1-1
Severity: important
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After a suspend, my laptop will present me with the username/password
prompt, at which point I can login and return to work.  However,
in many cases, after entering the password and pressing "enter",
the login simply hangs, triggering only some disk activity.  If I
leave it alone for a few minnutes, it eventually presents me with a
screen containing the system time, at which point I can once again
provide input, returning to the login screen and signing in.

I have been frequently experiencing this issue on this laptop,
which has been running Bullseye since June.  It triggers whenever
the laptop suspends without a lid close, and I think it has triggered when
the laptop suspended with a lid-close.

I recently installed laptop-mode-tools, and did other power-saving
efforts, but the issue was present before then.

Lastly, I have found several other related threads about this issue,
but none seem to present a solution.  This includes gdm issue
618, and askUbuntu question 1140365.  I am not sure if this
is the same issue, but neither has received any attention, so I am filing this 
bug.

Attached is what I belive to be the relevant section of my syslog.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  evolution-data-server3.36.4-1
ii  gir1.2-accountsservice-1.0   0.6.55-3
ii  gir1.2-atspi-2.0 2.38.0-2
ii  gir1.2-freedesktop   1.66.1-1
ii  gir1.2-gcr-3 3.38.0-1
ii  gir1.2-gdesktopenums-3.0 3.38.0-2
ii  gir1.2-gdm-1.0   3.38.1-2
ii  gir1.2-geoclue-2.0   2.5.6-1
ii  gir1.2-glib-2.0  1.66.1-1
ii  gir1.2-gnomebluetooth-1.03.34.3-2
ii  gir1.2-gnomedesktop-3.0  3.38.0-2
ii  gir1.2-gtk-3.0   3.24.23-2
ii  gir1.2-gweather-3.0  3.36.1-1
ii  gir1.2-ibus-1.0  1.5.23-1
ii  gir1.2-mutter-7  3.38.1-2
ii  gir1.2-nm-1.01.27.91-1
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-pango-1.0 1.46.2-1
ii  gir1.2-polkit-1.00.105-29
ii  gir1.2-rsvg-2.0  2.50.1+dfsg-1
ii  gir1.2-soup-2.4  2.72.0-2
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gjs  1.66.1-1
ii  gnome-backgrounds3.38.0-1
ii  gnome-settings-daemon3.38.0-2
ii  gnome-shell-common   3.38.1-1
ii  gsettings-desktop-schemas3.38.0-2
ii  gstreamer1.0-pipewire0.3.12-1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-4
ii  libcairo21.16.0-4
ii  libecal-2.0-13.36.4-1
ii  libedataserver-1.2-243.36.4-1
ii  libgcr-base-3-1  3.38.0-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libgirepository-1.0-11.66.1-1
ii  libgjs0g 1.66.1-1
ii  libgles2 1.3.2-1
ii  libglib2.0-0 2.66.1-2
ii  libglib2.0-bin   2.66.1-2
ii  libgnome-autoar-0-0  0.2.4-2
ii  libgnome-desktop-3-193.38.0-2
ii  libgraphene-1.0-01.10.2-1
ii  libgtk-3-0   3.24.23-2
ii  libical3 3.0.8-2
ii  libjson-glib-1.0-0   1.6.0-1
ii  libmutter-7-03.38.1-2
ii  libnm0   1.27.91-1
ii  libpango-1.0-0   1.46.2-1
ii  libpangocairo-1.0-0  1.46.2-1
ii  libpolkit-agent-1-0  0.105-29
ii  libpolkit-gobject-1-00.105-29
ii  libpulse-mainloop-glib0   

Bug#973557: afl++: Long decription implies this package is deprecated

2020-11-01 Thread Calum McConnell
Package: afl++
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The long description finishes with this ambiguous (grammatically incorrect) 
line:

"This package is a fork of the afl package that is no longer maintained"

It seems to say that "this package... is no longer maintained", meaning
that somebody forked AFL, made some changes, and then stop maintaining their
fork, while AFL continued on.  This is obviously untrue, given that AFL
is now a transitional package in oldlibs.

The issue is because"that" refers to the subject, which is "this package", 
not the object ("the afl package")

An alternate phrasing would be:

"This package is a fork of the unmaintained afl package"

It sounds pendantic, but I was genuinly confused for a little bit!
Thanks,
Calum

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages afl++ depends on:
ii  build-essential  12.8
ii  libc62.31-4
ii  libpython3.8 3.8.6-1

Versions of packages afl++ recommends:
pn  afl++-clang  
pn  afl++-doc

Versions of packages afl++ suggests:
ii  gnuplot-x11 [gnuplot]  5.4.0+dfsg1-1

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+fFqgdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzK1+A/+NI5WAzl0Si6O9l4Z
+rFVS79FHXOhHGQSIPF3igMxbRggE6GzSId5V0ENtfJm2McMTxXtFsQSPK+RCWlj
3Wvx0a2JUvpoQgkGr/k9NR5B2wAAqEHXADUicDYnZCK/iq3/m0yWPkjfff2mWwCr
Y/eDGspu7yDJQJ7IEq+4JJ/T5GoVfw2Hxb+ug34lqbpMxicXc61ynTM1Tjj/a/G5
yOVSL/QxbDeXaiX+n61dKfKUbQIE7gqGVGIFqa7c95n03l4Ncs5BmFWqZHzqCUqH
oKngUP5VtJ/FyS2ueVA270XtHrMCEGMbZAPvqjOsMGJRtCJj5zhtQrwMEWS7PwE5
T5WKBJ0dyR8/EifibbOE+1hvQItZ312T5x6sQVyzfrp9v+bwvLIuWkpFfU0ewi4T
4D1ogZnTbE9HRKVBorI6wgfgMQE1aAVts05V+rPtXlxIYsVo7BVfRYHANbskPV83
0FfEAM982FxPm13xXirThaoylL5SELEH6/ND7YKwFHMdNcdCJdlbH5idDPJU2Xw4
Pzd88a9DjST+c0pCEzK99Ci7qpxF8JneyVFnCbhon+G1yhOnZSx0jkFpYL/sspn+
c7jQbZw9vaYdX+ac7lyH+1qlp086+dsNTqTKk+LSS53WE/pJOrnibVyATIzs5Qea
FXAkq7nuhavBKsTcsd+LVhDD0ZI=
=IgJp
-END PGP SIGNATURE-



Bug#973315: dwww doesnt decompress documentation files

2020-10-28 Thread Calum McConnell
Package: dwww
Version: 1.13.5
Severity: wishlist
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Many packages gzip their README files, and even (often) their examples.  It 
saves
space, and it quite useful to me as a user, since I can (usually) just open it 
normally
(I have lesspipe installed).

However, DWWW wanted to download the Gziped readme.md I pointed it to.  Is there
any way that can be changed, so that it gets decompressed and then served?

For that matter, I would be intrested in seeing more flexibility in serving 
files.
For instance, .gz extensions could be decompressed, .md fed through kramdown (if
its installed), ect.  Even if there was just a way to define filters (if the 
following
files are accessed, send them through these programs first), usability would 
improve immensly.

Thanks!
Calum

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dwww depends on:
ii  apache2 [httpd-cgi]2.4.46-1
ii  debconf [debconf-2.0]  1.5.74
ii  debianutils4.11.2
ii  doc-base   0.10.9
ii  file   1:5.38-5
ii  libc6  2.31-4
ii  libfile-ncopy-perl 0.36-2
ii  libmime-types-perl 2.17-1
ii  man-db 2.9.3-2
ii  mime-support   3.64
ii  perl   5.30.3-4
ii  sensible-utils 0.0.12+nmu1
ii  ucf3.0043

Versions of packages dwww recommends:
ii  apache2 [httpd]  2.4.46-1
ii  apt  2.1.10
ii  dlocate  1.07+nmu1
ii  info2www 1.2.2.9-24
ii  swish++  6.1.5-5

Versions of packages dwww suggests:
ii  chromium [www-browser] 83.0.4103.116-3.1
ii  doc-debian 6.4
ii  dpkg-www   2.60
ii  firefox-esr [www-browser]  78.3.0esr-2
ii  lynx [www-browser] 2.9.0dev.6-1
ii  w3m [www-browser]  0.5.3-38+b1

- -- debconf information:
  dwww/badport:
  dwww/cgiuser: www-data
  dwww/serverport: 80
  dwww/index_docs: false
  dwww/nosuchuser:
  dwww/cgidir: /usr/lib/cgi-bin
  dwww/nosuchdir:
  dwww/docrootdir: /var/www
  dwww/servername: CalumsBeastlyLaptop.computercalum.com

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+ZrecdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzIyKxAAgGsJRU+v6zu3oMiY
q2aLYVkvWuRtRXksrOLew6LFbL+bZMoOhYq4J4BWEy+7EPsnHsooi7HStfDF3eEb
SoJYcr3mM/g7GOiBEemxMgQeleoH+v1WQD6TtEFBNgClg30Kchwq66AzisoZ3m9R
ZB+irSaT/VZgYvTFYHikPw6qOcsXvS5FN13e5LTI+2FeghcplF6uD69BHm1cjI07
eb1l7iPxRRvmnh7YDl42EuMy+2TFVSOQZ54nYqbwrqIqturSS5tXlSEitlTPEX5p
0o9635UCHYkimw967nimK4uNOYB0/MMfpA8vYoNVji/u3u0Qt5iGLhvFasFm6VYZ
PpWRXXV370RjyolJBUeYRWFXUAU6r8X5wMOZaE2I+JpXYtyWUqr8+MRVm0GC0ql0
QYvc+r2Ifoz9760bwt2ljtkXtO24huukYcuLGwJRONpX4x0RN8puaosRHsF6DXxe
zPAbLbA4WcQnKMhnlg4jGU5DENflvV7C1HoxyIMXS4dL3rNJEdkpyhQEL9RR5U62
oA/BC85esTAqR381Rh/YXvpHP/AR5SyBkwAxRvdcpZM0XTHDtl9ArqsViP/D9na0
uzOsuRhzbnverNvfuNLT4TRfwvj3HfPTqfmeXhFzRxcK8eE0rUaAIjD2JoTuQbrL
bRK5EcrBjVyRqukCUK2QS2+RS8o=
=xGLe
-END PGP SIGNATURE-



Bug#973301: scons: Scons-doc is not reccomended by scons

2020-10-28 Thread Calum McConnell
Package: scons
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

It is my understanding that documentation pacakges are typically linked
to
the packages they document by a Suggests: or a Reccomends:, however,
that is not the case for scons-doc.  Thus, a potential user would'nt
be informed about the existence of such a package unless they went out
of 
their way to find it.

I think scons-doc should be reccomended by scons, because it is a build
system, and so which most users would probably want to consult the 
documentation on it eventually.

Thanks for your time!

-Calum

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages scons depends on:
ii  python3  3.8.2-3

scons recommends no packages.

scons suggests no packages.


signature.asc
Description: This is a digitally signed message part


Bug#972904: git-debrebase: provide bash-completions

2020-10-25 Thread Calum McConnell
Package: git-debrebase
Version: 9.12
Severity: wishlist
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It would be really neat if there were bash-completions for the git-debrebase
command.  I could put them together, but I am currently a bit busy, so I
figure I should file a bug, and work on it later.

It would really be quite straightforward, I think, since you could reuse a
lot of the code from git's autocompletions.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages git-debrebase depends on:
ii  devscripts  2.20.4
ii  git [git-core]  1:2.28.0-1
ii  libdpkg-perl1.20.5
ii  libfile-fnmatch-perl0.02-2+b7
ii  liblocale-gettext-perl  1.07-4
ii  perl5.30.3-4

Versions of packages git-debrebase recommends:
ii  dgit  9.12
ii  git-buildpackage  0.9.20

git-debrebase suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+WVmIdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzKvBBAA4FUmJlm6NOI1enF4
zVhQk+Rb9DwIupBaHQLlh6VzGi/N5J1voeVrdZ9oHySONmTxfpBdC4UsViAnVXe1
vT8Zt1911XaTfNMqlw0eDIJn52r1MPVzVh9YnFtGbD1oag7SdeCr80f05MSRluxz
hJTrwG3oohps3CNkaGvqr+x6tZ23va9pgU7i7L99D59KCZtnwj6nX5Iv3ZTbDJnD
5FtOzIlZPPQ7oAkrzJVNlX9ZRo9LkkxvrFzDTL8kdz0og4713dfuW3df0ohEJ/Hr
caiGx1rzejyh2JJKoqDew0Bv71FxThJiB229MiOzM7om7YHeJcRv+XbvaPzCLhLv
fzY2Au5IebgD1kp951ksxz5MNQ7eqKXa468t7wgzWoH/YvFUIWv/xjOqF+rCy0FI
rjkfYLnwzDCRJAw5Hs+yVdOxjcuC27nCZ7zb5Gle+M2jHQQodxxlHumzJhBlNUQQ
Q6Si7cZLlkZa7fVJtdOTwS7BtzyEPuY8YsVuoToGDG/VgD0O9jhByQ+aa9r6bVij
F5rP3RzPGz1jXh+xPRaHCU7y8vRJrazEyetNuvNVbEmkcChQS+nCAAKsG0Qhib/9
LIoy9Ka9uyrkFo3viRkM46M2GipafSlFNzrXdkdWgfaU6po1pYDJcL+AexjN9r+R
SwpJtdnQ1LPNeRzoccYtWD0PmM0=
=Qb9a
-END PGP SIGNATURE-



Bug#972605: jekyll: Please update to new 4.x branch

2020-10-20 Thread Calum McConnell
Package: jekyll
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Jekyll upstream has been concentrating on a new 4.x release branch for the past 
year.  It provides a significant set of new features that I use, and it would 
be great if it could be included in debian.

I assume you know all of that already, since 3.9 released after 4.0, but I was 
wondering what the rationale was for sticking with the 3.x branch.

Thanks!

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages jekyll depends on:
ii  ruby1:2.7+1
pn  ruby-addressable
ii  ruby-bundler2.1.4-2
pn  ruby-classifier-reborn  
pn  ruby-coderay
ii  ruby-colorator  1.1.0-3
pn  ruby-em-websocket   
pn  ruby-i18n   
pn  ruby-jekyll-sass-converter  
pn  ruby-jekyll-watch   
pn  ruby-kramdown   
pn  ruby-kramdown-parser-gfm
pn  ruby-liquid 
pn  ruby-mercenary  
pn  ruby-mime-types 
pn  ruby-pathutil   
pn  ruby-pygments.rb
pn  ruby-rdiscount  
pn  ruby-redcarpet  
pn  ruby-rouge  
pn  ruby-safe-yaml  
pn  ruby-tomlrb 
pn  ruby-yajl   
ii  xdg-utils   1.1.3-2

jekyll recommends no packages.

Versions of packages jekyll suggests:
pn  jekyll-theme-minima 
pn  ruby-jekyll-avatar  
pn  ruby-jekyll-coffeescript
pn  ruby-jekyll-compose 
pn  ruby-jekyll-feed
pn  ruby-jekyll-gist
pn  ruby-jekyll-last-modified-at
pn  ruby-jekyll-mentions
pn  ruby-jekyll-paginate | ruby-jekyll-paginate-v2  
pn  ruby-jekyll-redirect-from   
pn  ruby-jekyll-remote-theme
pn  ruby-jekyll-seo-tag 
pn  ruby-jekyll-sitemap 

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+Pq/AdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzItIA/+KZO6m0SPfb3V9ben
g/MgKDRH1ooEoWpQoHfX+/fRKo1rOmF/GsmhA2S02Ce8saLZXwXoGRqqCemdINcA
5D3cyvJjoBf6rERLUPXyawrJ8aVIstLR7VBZEn4NFBNv7KvLeXrMXyR6xem9i77C
fR6E0ar6jz8WVek2ulIZvsnKsVjnOxFx+LEL2tGWLL3Vf3G0Scoydr59uVSPhURH
XoxtL7JXmJBrvY1Phv4PG83T5PPBphs22HMCVAQXjpDkX4H3yE9RAMK7I/18dtqf
8CkfPxQszmHHBth64Pq4vsC6znJvI3yAofmy2maxF29vK5nNQja5oJNPig7K3J31
sufw9d2aoMPY0YhBo3MGkUla22eTxqI8eVIwinl3+iUEyYbgyBIn9PId4COYe4P9
R1ZhmT7xKwGqPY0X7iQeTeEGF/5wdXmmiOMkPymMLrjXcaSLcbCH3x0uQ28zt86u
W4suvYIWwu8yZr91K92oLTq+jwKRTKsWNGyFJKE4D4+0BnwqnBiCjNSwp5E3fT/g
iv95ST6YXUnqfq6nKL0aTCYstxMOGLf8sVO6JfrKFAqlEfErGGdG90yARB9NLJ6e
Gtkf6HIOjW3mC0X1c1CuD2jwsaLuz+7z5DUrkc1ucdXFxGFhpO2kE8PMjXfxq7Z2
cb0Tj5ykxULdJkHj+k9msevEWec=
=gxzn
-END PGP SIGNATURE-



Bug#972543: apt-file: Apt-update downloads full Contents file, not pdiffs

2020-10-19 Thread Calum McConnell
Package: apt-file
Version: 3.2.2
Severity: normal
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Basically, on every call to apt-update that isn't completely trivial (ie, at 
least
1 package changed), my computer downloads the full 60 Mb of Contents files.  
This
is irritating, for while I am often on a fast internet, I frequently find 
myself on
a very slow connection.  

I know my config file enables pdiffs (and I attached it so you can know, too).
The Readme talks a lot about pdiffs, and why I should enable them, but except 
for
one sentence, it doesn't mention anything about apt update.  (The sentence in 
question *could* be interpreted to mean that apt update will never download
Pdiffs, but that is unlikely, given its context).

I don't know what's the cause.  If you need me to get a log file, I can, but
Apt doesnt include these files in its final output: only while it is
drawing progress bars.

Thank you!
Calum

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-file depends on:
ii  apt  2.1.10
ii  libapt-pkg-perl  0.1.36+b3
ii  liblist-moreutils-perl   0.416-1+b5
ii  libregexp-assemble-perl  0.36-1
ii  perl 5.30.3-4

apt-file recommends no packages.

apt-file suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl+ObBsdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzKbuQ//SXtp2pvjIgjQa2As
eWwtieJpvjlxG+qsKKJSfeHxLuCdGKoTs2a7/e4/BVbaQhPvNHdsDOPA6tY+QcdU
+iPU48L9fkA8B4YxeQqB6AzUyZM2bNdiaYNMJSyLu+o1WBDbk/an/QclkD23wQGL
E+Yyo9vIzVtmIA8S/NTWT6u9gW0mov4zH4ORHavacR3z/c4Yx17yNhHc5OlFbqmk
4nAuAedgirkj4OTbjwh+xofFkX7iP5P9X1rkz59UUJmKBOti9ZQs4GZYpHd8YLOG
FKJlOjumHbTB4kz16TfLAYvP/w0BIYkqPMTfZMjZxpFfyYllYx31K6j/w5qXaFTi
GYyBUnqB6+zk6doNzZwV0cBTwaO7tW0snptIHwLtM0iU1LyYkTh5M62IcLeqrozL
eNX9WZOk/OSqiwlJqg2mqB7R2ZRYtJaYf4qGmdQzQ2xMft16Vm+1q9WB0RY+RIJ7
RexE8fo+UrewdKkyuzMw6aMjpFm6iSakagx7Szc02RN9LnL9r63AsIbl0nDIxCQh
a933Oto7D2WbF+tl3OO+I0m2+xGt941VWUD+3yp/RBQcjnSieYIRSfwINlXiNVc+
6/+u3W0NhigH/qS88XH0gc3jQY0DixcGROvrtkVe4+1fwQEwGMrjtjG9aH3E2bif
HfPVdM8L2mhoKuUV7lg4rFLXPEk=
=+avA
-END PGP SIGNATURE-
## This file is provided by apt-file(1) to download Contents
## files, which is used by apt-file for searching.

Acquire::IndexTargets {
deb::Contents-deb  {
MetaKey "$(COMPONENT)/Contents-$(ARCHITECTURE)";
ShortDescription "Contents-$(ARCHITECTURE)";
Description "$(RELEASE)/$(COMPONENT) $(ARCHITECTURE) Contents (deb)";

flatMetaKey "Contents-$(ARCHITECTURE)";
flatDescription "$(RELEASE) Contents (deb)";
PDiffs "true";
KeepCompressed "true";
};

# Download Contents for source files if there is a deb-src
# line
deb-src::Contents-dsc  {
MetaKey "$(COMPONENT)/Contents-source";
ShortDescription "Contents-source";
Description "$(RELEASE)/$(COMPONENT) source Contents (dsc)";

flatMetaKey "Contents-source";
flatDescription "$(RELEASE) Contents (dsc)";
PDiffs "true";
KeepCompressed "true";
DefaultEnabled "false";
};

# Configuration for downloading Contents files for
# debian-installer packages (udebs).
deb::Contents-udeb  {
MetaKey "$(COMPONENT)/Contents-udeb-$(ARCHITECTURE)";
ShortDescription "Contents-udeb-$(ARCHITECTURE)";
Description "$(RELEASE)/$(COMPONENT) $(ARCHITECTURE) Contents (udeb)";

flatMetaKey "Contents-udeb-$(ARCHITECTURE)";
flatDescription "$(RELEASE) Contents (udeb)";
KeepCompressed "true";
PDiffs "true";
DefaultEnabled "false";
};
### FALLBACKS
deb::Contents-deb-legacy {
MetaKey "Contents-$(ARCHITECTURE)";
ShortDescription "Contents-$(ARCHITECTURE)";
Description "$(RELEASE) $(ARCHITECTURE) Contents (deb)";

PDiffs "true";
KeepCompressed "true";
Fallback-Of "Contents-deb";
Identifier "Contents-deb";
};
};
Dir::Etc::apt-file-main "apt-file.conf";
# Default for -I/--index-names (comma-separated)
apt-file::Index-Names "deb";
# Set to true, if you are working with Contents files generated by
# older versions of dak or reprepro (<< 5.2.0-1~) that includes a
# descriptive header.
apt-file::Parser::Check-For-Description-Header "false";


Bug#971407: ITP: whitakers-words -- latin parser and translation aid

2020-09-29 Thread Calum McConnell
Package: wnpp
Severity: wishlist
Owner: Calum McConnell 
X-Debbugs-Cc: debian-de...@lists.debian.org, calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: whitakers-words
  Version : 0~20.6.7
  Upstream Author : Martin Keegan 
* URL : http://mk270.github.io/whitakers-words/index.html
* License : Public Domain
  Programming Lang: Ada
  Description : latin parser and translation aid

Whittakers Words is a program that takes in words in latin,
and analyzes them to determine the stems, case, form,  and any
possible  translations.  It can also provide latin words with
a given translation, going from latin to english.  It is
an invaluble tool for latin users, be they experts or
new learners.

Words was created by Willam Whitaker (1936-2010) as a
curiosity that demonstrated his new programming language,
Ada.  It was since improved and iterated on, ported away
from is DOS roots, and given an online access point. 

- 

This package, as mentioned above, is increadibly useful for
working with latin texts.  As such, most latin teachers
and students will use it often: I certainly have.  I
am not aware with any other packaged program with the
same functionality, and while there do exist other, similar
programs, they are comparativly inaccurate and weak.  

I plan on maintaining it mostly on my own, with aid from
upstream.  I *will* need a sponsor to upload it, and if
anyone is intrested in co-maintaing I would be happy for
the help.  A mentor would probably also be needed,
as I have never actually made a package from scratch
before.

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl9zwDodHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzJAZxAAv+5wkUJ4VPgrui1g
r7UGjKPBtkYqLw/aH/IXqPvdqhnPdl37GZWFeMpaA01WwmDFEq55aul/L3HFzyfD
XVbESeh6XUQ4y9zHmkyb5SGffTK0/htG4xbrCtOIBuo24jwwl/+L4SI0M/rmtis7
hu9gMr63hJS7Gf3nDf1yHCvezMv9KVDry2/RhUpQo5QFJmYoOXFiFU4dxIddaesj
VVtiv0yJhLNBBGmh409yhM4gMAKjW5xow02tu8yX8rq4M9eOH7/B67ffX9/0FEB0
e7i24jMQ50J90qAy0wrOme4Szlo3gJxXt73ankpZS1uc4RNYdhdkhIorZX8hCoSr
uQsjZ0hJIfv3RzPmSuF5P8JkLH5WdS3tPn4P/F/MfE/ssn5xmfXrYlXVZZ0baRhR
LQ08q44v7ZtxK158N+GUoQx6LQ+LZDxgEXABQPDl+9Ozr2wzUxQIbP6lYWKVzBmw
V6XdIX3rcsbMGa1BAfFiWP/YsbzXvpqbai1Lci/z5Xlje9yIrvoJn/xFxTZIt5Ne
jOY6kI68P2Sbh7mYczyn6wsEMzpt92MZ35Z+sj6YtZWuRWaxF1XGBTVy+ZfczoFH
Auo3UXqjhIiT6yhsjLx7dUzrBZp/dMAWr14OzmpoFTRIE7usDemPzkVqDxA+VFg0
imqfgp4qhbvAR9FxW9um11ybmPQ=
=5EAO
-END PGP SIGNATURE-



Bug#970748: pulseeffects: Numerous desktop files without a common categories

2020-09-22 Thread Calum McConnell
Package: pulseeffects
Version: 4.8.0-1
Severity: minor
X-Debbugs-Cc: calumlikesapple...@gmail.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package creates a huge number of .desktop files, but
doesn't put them in a common cateogory.  That means that
it's hard to put them in a GNOME app-folder without manually
naming every one of them.  If you added a Categories: line, that
would not be the case: it would be possible to quickly add
every one into a lsb-plugins folder.  That way, it is easy to
manage the huge number of applications created, while
still letting them be used.

Ideally, the line would contain the basic cateogories.
as well as an X-lsb-plugin line.  That makes it easy
for users to modify GSettings to hide all the entries
into folders.  This could be done with a bash script.

I can write said script if you would like.  
Thanks!
Calum M.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseeffects depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  gir1.2-gst-plugins-bad-1.0   1.18.0-2
ii  gstreamer1.0-adapter-pulseeffects4.8.0-1
ii  gstreamer1.0-plugins-bad 1.18.0-2
ii  gstreamer1.0-plugins-good1.18.0-1
ii  gstreamer1.0-pulseaudio  1.18.0-1
ii  libatkmm-1.6-1v5 2.28.0-2
ii  libboost-filesystem1.71.01.71.0-6+b2
ii  libc62.31-3
ii  libcairomm-1.0-1v5   1.12.2-4
ii  libgcc-s110.2.0-9
ii  libglib2.0-0 2.66.0-2
ii  libglibmm-2.4-1v52.64.2-2
ii  libgstreamer-plugins-base1.0-0   1.18.0-2
ii  libgstreamer1.0-01.18.0-3
ii  libgtk-3-0   3.24.23-1
ii  libgtkmm-3.0-1v5 3.24.2-1
ii  libpangomm-1.4-1v5   2.42.1-1
ii  libpulse013.0-5
ii  libsigc++-2.0-0v52.10.2-1
ii  libsndfile1  1.0.28-8
ii  libstdc++6   10.2.0-9
ii  pulseaudio   13.0-5

Versions of packages pulseeffects recommends:
ii  calf-plugins   0.90.3-1+b1
ii  gstreamer1.0-autogain-pulseeffects 4.8.0-1
ii  gstreamer1.0-convolver-pulseeffects4.8.0-1
ii  gstreamer1.0-crystalizer-pulseeffects  4.8.0-1
ii  liblilv-0-00.24.8~dfsg0-1
ii  lsp-plugins-lv21.1.26-1
ii  rubberband-ladspa  1.9.0-1
ii  zam-plugins3.9~repack3-1+b1

pulseeffects suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJRBAEBCgA7FiEE/vC/PEGxsMPJ5u5w7/Xh1+DNmzIFAl9qPuQdHGNhbHVtbGlr
ZXNhcHBsZXBpZUBnbWFpbC5jb20ACgkQ7/Xh1+DNmzLp5A//SL2GZ50v4BPLmxM+
OltNdbcam51kbgRiVU14P9zOkNww1+m2vnWT8B0NloKnqjXPl0TjUx4qm+miZe6M
BEzu1sy9L6JYewR8nASZpxVSezoOVawtNx8YwJSdAPdXhEoDuJojOrh3tJvW9XBJ
LXencJlZyylg+yGV1faj5NHYQ1/kQhDYXwxg7s+Y0hubRAU/7olfTpITdn3tu2Dr
CgR1CL43B2c/ArXlxwxQ0SL2vuIV7VQrJEhwROM6wpCPCmA9/w6+pTEtyP0pYS0W
xFMfbmkmvIq46cxjTpBjXasTIY6Wh+Ko5i4fnV5Oz4e3WO8YwmfZ4N12MJtlqrTY
wqY7Mif5ijcnopYB+LvgE3+xuEqlFytJGcbxtJmuYpEXuf1nLK6fyZk8+aovTkDI
bQf8uKA0hoarkKXnuHTIar99viSjQDOaqznBjjzwnMtFSV66OfjrjNchZSGpERbT
x5MiHcqaQwZ5gG8FpRBUk6df+n8gZVllMxahvOgNcEEKOryamvdc31L0SGZL1KfK
9lrO0HmmBarqJPe3DNi79qDJ+Du1atYdHZliSz5TUhu0h0UKgk3p/WiykhUbArWL
jOPuotb5aoes/yHH/fynECy3ah73MpwldwoeQkiMPDCbsC0eEeU1MX4sjIdbec0I
2r8RY313J9YmRkCb1uJRbB+uof8=
=Fo9+
-END PGP SIGNATURE-



Bug#970702: bpython: "help" display doesnt clear existing terminal data

2020-09-21 Thread Calum McConnell
Package: bpython
Version: 0.19-1
Severity: normal
X-Debbugs-Cc: calumlikesapple...@gmail.com

I ran some commands in my shell (bash, piped through a plain tty).
I then called bpython, and hit F1, hoping for a help display.  It
just printed over the existing shell output, rather than paging it 
up or deleting it.  Instead, it printed the characters over top of
the existing output: lines would start with the 'help' data, then
switch to the output of 'ls'.  If I wasnt using a colorized
terminal, it would have been impossible to spot: as it was, it
still was completly unreadable

Given this is the help menu, I think this is a significant
issue.

Thanks!
-Calum

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bpython depends on:
ii  less   551-2
ii  python33.8.2-3
ii  python3-curtsies   0.3.4-1
ii  python3-greenlet   0.4.15-4.2
ii  python3-pkg-resources  46.1.3-1
ii  python3-pygments   2.3.1+dfsg-4
ii  python3-requests   2.23.0+dfsg-2
ii  python3-six1.15.0-1

Versions of packages bpython recommends:
ii  python3-watchdog  0.9.0-3

Versions of packages bpython suggests:
ii  python3-jedi  0.17.0-1

-- no debconf information



Bug#970667: bpython: Documentation not shipped

2020-09-20 Thread Calum McConnell
Package: bpython
Version: 0.19-1
Severity: normal
X-Debbugs-Cc: calumlikesapple...@gmail.com

Bpython includes detailed sphinx documentation, but that doesnt appear to
be being shipped along with the package.  I often work offline, and would
appreciate having access to the documentaion files when offline.  If you
could ship them, either in the package itself or as a bpython-doc
package, that would be much appreciated.

I can attempt this if needed, but I am not a debian maintainer, and
have never made a package before.

Thanks!
Calum

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bpython depends on:
ii  less   551-2
ii  python33.8.2-3
ii  python3-curtsies   0.3.4-1
ii  python3-greenlet   0.4.15-4.2
ii  python3-pkg-resources  46.1.3-1
ii  python3-pygments   2.3.1+dfsg-4
ii  python3-requests   2.23.0+dfsg-2
ii  python3-six1.15.0-1

Versions of packages bpython recommends:
ii  python3-watchdog  0.9.0-3

Versions of packages bpython suggests:
ii  python3-jedi  0.17.0-1

-- no debconf information



Bug#970639: grub-pc: Zswap disabled by default

2020-09-20 Thread Calum McConnell
Package: grub-pc
Version: 2.04-8
Severity: wishlist
X-Debbugs-Cc: calumlikesapple...@gmail.com

Simply put, I think a lot of people would benefit from zswap being enabled by 
default.  Except on
very low-preformance machines, it is always an improvment.  Even on those very 
limited machines, 
zswap would only be a significant limitation if memory is being pushed close, 
but not past, it's
limits, and Disk IO is very fast-- neither of which are likely true for 
computers with sufficently
weak CPU's.

>From what I can tell, enabling it should be a simple matter of changing the 
>default grub config file.

I know zswap is a kernel parameter, but every guide I have seen says to enable 
it in grub config.
As such, I appologize if you think this report is better directed elsewhere, or 
if it has been
implemented already and my config files are out of date.

Thanks for your time!
Calum

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/sda1 / ext4 rw,relatime,errors=remount-ro 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
2c7929e7-825d-453d-a064-53da2115a7a2
else
  search --no-floppy --fs-uuid --set=root 2c7929e7-825d-453d-a064-53da2115a7a2
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
2c7929e7-825d-453d-a064-53da2115a7a2
else
  search --no-floppy --fs-uuid --set=root 2c7929e7-825d-453d-a064-53da2115a7a2
fi
insmod png
if background_image 
/usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-2c7929e7-825d-453d-a064-53da2115a7a2' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  
2c7929e7-825d-453d-a064-53da2115a7a2
else
  search --no-floppy --fs-uuid --set=root 
2c7929e7-825d-453d-a064-53da2115a7a2
fi
echo'Loading Linux 5.8.0-1-amd64 ...'
linux   /boot/vmlinuz-5.8.0-1-amd64 
root=UUID=2c7929e7-825d-453d-a064-53da2115a7a2 ro  quiet
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-5.8.0-1-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-2c7929e7-825d-453d-a064-53da2115a7a2' {
menuentry 

Bug#779736: Note on manpage

2020-07-03 Thread Calum McConnell
If you could add a note about this to the manpage, I'd appreciate that
Thanks!
-Calum



Bug#964061: apt: bash-completions doesn't complete 'apt info'

2020-06-30 Thread Calum McConnell
Package: apt
Version: 2.1.6
Severity: minor
Tags: patch

Hey, so "apt info" is a perfectly valid use of apt AFAIK, but
bash doesnt autoclomplete package names if you use it.  I attached
a patch to fix this (at least I think I did: I might have screwed up
my reportbug usage)
It's minor, but a bit of a bother: for whatever reason, I like using
"apt info" rather than "apt show": it just makes more sense to me.

Thanks!
Calum


-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-.*-4\.19\.0-9-amd64$";
APT::NeverAutoRemove:: "^linux-.*-5\.6\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-.*-4\.19\.0-9-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-.*-5\.6\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-.*-4\.19\.0-9-amd64$";
APT::NeverAutoRemove:: "^gnumach-.*-5\.6\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-9-amd64$";
APT::NeverAutoRemove:: "^.*-modules-5\.6\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-9-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-5\.6\.0-2-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null || true; 
fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
APT::Compressor::lzma::Name "lzma";
APT::Compressor::lzma::Extension ".lzma";
APT::Compressor::lzma::Binary "xz";
APT::Compressor::lzma::Cost "400";
APT::Compressor::lzma::CompressArg "";
APT::Compressor::lzma::CompressArg:: "--format=lzma";

Bug#963784: qxw: New upstream release

2020-06-26 Thread Calum McConnell
Package: qxw
Version: 20140331-1.1
Severity: normal
Tags: a11y l10n

There has been a new upstream release of qxw, which adds a host of new features,
including unicode support and hex grids.  Please update the package to provide 
it!

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qxw depends on:
ii  libc6 2.30-8
ii  libcairo2 1.16.0-4
ii  libglib2.0-0  2.64.3-1
ii  libgtk2.0-0   2.24.32-4
ii  libpcre3  2:8.39-13

Versions of packages qxw recommends:
ii  wamerican [wordlist]  2019.10.06-1

qxw suggests no packages.

-- no debconf information



Bug#958734: npm2deb: Man-pages don't document subcommands

2020-04-24 Thread Calum McConnell
Package: npm2deb
Version: 0.3.0-3
Severity: important

I am trying to use npm2deb to package bitwarden, and I cant find the 
documentation
for the subcommands.  'man npm2deb' yields the manpage for npm, which states the
subcommands (ie, create, itp, license), but doesnt give the flags they take.
I can tell the subcommands take flags, but I can't find any manpages on
what those flags do.  Calls to 'man npm2deb create' tell me that no manpage
exists for create: 'man -aw npm2deb' shows only one manpage, the (rather
short) one for npm2deb.

If you need someone to transfer the docs from another location to manpage
format, I can do that: just point me to where it is documented and I'll form
a patch.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages npm2deb depends on:
ii  devscripts2.20.2
ii  node-github-url-from-git  1.5.0-1
ii  npm   6.14.4+ds-1
ii  python3   3.8.2-3
ii  python3-apt   2.1.2
ii  python3-dateutil  2.8.1-4

npm2deb recommends no packages.

npm2deb suggests no packages.

-- no debconf information



Bug#956836: ITP: bitwarden -- fully open-source, cross-platform password manager

2020-04-15 Thread Calum McConnell
Package: wnpp
Severity: wishlist
Owner: Calum McConnell 

* Package name: bitwarden
  Version : 1.17.2
* URL : http://www.bitwarden.com/
* License : GPL-3
  Programming Lang: Typescript
  Description : fully open-source, cross-platform password manager

== Long description ==
Bitwarden is an open-source password manager that syncs securly between devices.
The full stack is libre software, including the server, meaning one can host
their own passwords instead of storing them for free on bitwarden.com's service.

Passwords are stored encrypted on the server and on the client using an 
encryption
key derived from the master password by PKBDF2 SHA-256, and encrypted using 
AES-256.
Passwords are encrypted by the client before being sent to the cloud server: it 
is
not possible to determine the unencrypted passwords from the cloud server, 
unless
an attacker already knows the user's master password.

Bitwarden also supports saving of other data within the vault.  However,
saving large files on the bitwarden.com servers requires a premium subscription.

This package contains the bitwarden client, which connects to a bitwarden 
server.

== Justifications/Plans ==

Note: New to the world of packaging

I think this package is very useful and relevant, because password managers are
a must in order to remain secure using online accounts, and this is the only
cross-platform, FOSS manager of which I am aware.  I, for one, use it: I do
have the premium subscription, but only to support the authors.

This is my first Debian package, and as such I would appreciate support.
I will need a sponsor: I do plan on finding one thru  debian-mentors.  I am 
not aware of any teams which would maintain this: it is a Node.js+electron 
application, though they also distribute a C# port for mobile devices.  I would 
be happy to work with a team on this package, for I have little javascript 
experiance and no Electron experience.

I plan on using Git and Git-buildpackage to maintain this, because I have
grown used to having a full revision history, and I quite like working
on several devices.

Salsa link is here: https://salsa.debian.org/CalumMcConnell-guest/bitwarden.
The branch structure is that recommended by gbp documentation: master
is upstream, debian/sid is the contents of the up-to-date debian packaging.
I plan on using debmake to make the debian/ files.



Bug#955267: gnome-calendar: Also appears on month view

2020-04-08 Thread Calum McConnell
Package: gnome-calendar
Version: 3.36.0-1
Followup-For: Bug #955267

I am experiancing the exact same issue on month view, with this calendar
imported:
http://calendar.google.com/calendar/ical/cheshire.k12.ct.us_5dpc4689dsv5p21e2ie9nvqknc%40group.calendar.google.com/public/basic.ics
In this calendar, every weekday has a day name: 'a' 'b' 'c' 'd', which is
represented by an all-day event.  The 'd' day events ONLY appear as a single
continuous all-day event accross the entire month, in addition to the normal
event.  Intrestingly, the date given for the continuous event in april is the
1st of may, which is a D day but is not displayed on the april month view.

Investigation of other calenders led me to the conclusion that all-day events
that occur on the first of the following month (eg, Feb. 1: First day of
Black History Month) are displayed throughout the previous month (Jan) as
all-day, every-day events. 

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-calendar depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gsettings-desktop-schemas3.36.0-1
ii  libc62.30-4
ii  libcairo21.16.0-4
ii  libdazzle-1.0-0  3.36.0-1
ii  libecal-2.0-13.36.1-1
ii  libedataserver-1.2-243.36.1-1
ii  libedataserverui-1.2-2   3.36.1-1
ii  libgeoclue-2-0   2.5.6-1
ii  libglib2.0-0 2.64.1-1
ii  libgoa-1.0-0b3.36.0-1
ii  libgtk-3-0   3.24.17-2
ii  libgweather-3-16 3.36.0-1
ii  libhandy-0.0-0   0.0.13-2
ii  libical3 3.0.8-1
ii  libpango-1.0-0   1.44.7-3
ii  libpangocairo-1.0-0  1.44.7-3
ii  libsoup2.4-1 2.70.0-1

Versions of packages gnome-calendar recommends:
ii  evolution-data-server  3.36.1-1

gnome-calendar suggests no packages.

-- no debconf information



Bug#915458: multibootusb builds multi-boot live-usb's, but it bundles compiled free software

2020-03-31 Thread Calum McConnell
I cracked open the package, and it seems almost straightforward, except
for two complications: it bundles a compiled version of GRUB for i386
and amd64, as well as some other compiled tools.  I think any working
package would need to rewrite that to use a version of GRUB installed
already on the machine: but I don't know enough about Debian packaging
or boot systems to comfortably rework this for full policy
compatability (ie, being able to build and use the arch-appropriate
GRUB version).

Some possibilities would be to (somehow) download the Grub package for
the appropriate arch, and use the compiled files from there during
runtime.  AFAIK, the software needs to download from the internet
anyways for its core functionality.

Guidance would be much appreciated.  Salsa link is:
https://salsa.debian.org/CalumMcConnell-guest/multibootusb


signature.asc
Description: This is a digitally signed message part


Bug#636977: Interest in packaging Boot-Repair

2020-03-31 Thread Calum McConnell
Hi! I have interest in packaging boot-repair, as it helped to save my
own dual-boot.  I started to repackage it, but I became unsure about
whether I should.  It is a maintained PPA, and so it already has a
functional control file.  I wasn't sure what I should put as (for
instance) the "maintainer".

This is my first package for debian, so guidance would be appreciated.


signature.asc
Description: This is a digitally signed message part


Bug#954865: ruby: Ruby update to 2.7 broke all native extensions, including ones needed for gem pristine

2020-03-26 Thread Calum McConnell
* Calum McConnell  [200324 16:30]:
> [..]
> > /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in
> > `require': libruby-2.5.so.2.5: cannot open shared object file: No
> > such file or directory -
> > /home/calum/gems/gems/psych-3.1.0/lib/psych.so (LoadError)
>   
> 
> [..]
> > Further, I shouldnt need to reinstall ruby: rebuilding native
> > extensions should
> > be done by the upgrade script.
> 
> Rebuilding gems/extensions that are located in your home directory
> or other random places is not something that is allowed to be be done
> by the upgrade process. It also wouldn't work in multi-machine setups
> and many other cases.

Okay, fair enough.

> Please rebuild the gems in your home directory yourself, possibly by
> deleting them first. I would also recommend using versioned
> directories in your gem path to avoid breaking gem itself on such
> occasions.

Thanks for the solution!  My gem directories were auto-generated by
Bundler, and given how rarely I use ruby, I don't think its worth the
time to try and mess with the defaults.  I'm perfectly willing to rm
-rf ~/gems once yearly instead.  You may want to mention the gem-
breaking in the news file, though: many people (okay, at least this
person) don't remember that native-extensions are version dependent and
require rebuilds.

Thanks for the quick assistance,
Calum
(you can close this bug, if you havent already)


signature.asc
Description: This is a digitally signed message part


Bug#954865: ruby: Ruby update to 2.7 broke all native extensions, including ones needed for gem pristine

2020-03-24 Thread Calum McConnell
Package: ruby
Version: 1:2.7
Severity: important

I ran apt update recently, and got ruby 2.7, but now gem seems to have been 
broken.  
Ruby itself continues to work: however, all gems using native extensions seem to
have been broken.
Intrestingly, bundle install fetched and succsessfully installed several gems,
untill it reached one with native extensions, at which point it died 
dramatically.

Any call to 'gem', regardless of subcommands or options, returns this:

calum@CalumsDebianSupreme:~$ gem
Ignoring bigdecimal-2.0.0 because its extensions are not built. Try: gem 
pristine bigdecimal --version 2.0.0
Ignoring bigdecimal-1.4.4 because its extensions are not built. Try: gem 
pristine bigdecimal --version 1.4.4
Ignoring commonmarker-0.21.0 because its extensions are not built. Try: gem 
pristine commonmarker --version 0.21.0
Ignoring commonmarker-0.17.13 because its extensions are not built. Try: gem 
pristine commonmarker --version 0.17.13
Ignoring date-3.0.0 because its extensions are not built. Try: gem pristine 
date --version 3.0.0
Ignoring etc-1.1.0 because its extensions are not built. Try: gem pristine etc 
--version 1.1.0
Ignoring eventmachine-1.2.7 because its extensions are not built. Try: gem 
pristine eventmachine --version 1.2.7
Ignoring ffi-1.12.2 because its extensions are not built. Try: gem pristine ffi 
--version 1.12.2
Ignoring ffi-1.12.1 because its extensions are not built. Try: gem pristine ffi 
--version 1.12.1
Ignoring ffi-1.11.3 because its extensions are not built. Try: gem pristine ffi 
--version 1.11.3
Ignoring ffi-1.11.1 because its extensions are not built. Try: gem pristine ffi 
--version 1.11.1
Ignoring ffi-1.9.18 because its extensions are not built. Try: gem pristine ffi 
--version 1.9.18
Ignoring http_parser.rb-0.6.0 because its extensions are not built. Try: gem 
pristine http_parser.rb --version 0.6.0
Ignoring io-console-0.5.6 because its extensions are not built. Try: gem 
pristine io-console --version 0.5.6
Ignoring io-console-0.5.5 because its extensions are not built. Try: gem 
pristine io-console --version 0.5.5
Ignoring io-console-0.5.2 because its extensions are not built. Try: gem 
pristine io-console --version 0.5.2
Ignoring json-2.3.0 because its extensions are not built. Try: gem pristine 
json --version 2.3.0
Ignoring nokogiri-1.10.9 because its extensions are not built. Try: gem 
pristine nokogiri --version 1.10.9
Ignoring nokogiri-1.10.7 because its extensions are not built. Try: gem 
pristine nokogiri --version 1.10.7
Ignoring nokogiri-1.8.0 because its extensions are not built. Try: gem pristine 
nokogiri --version 1.8.0
Ignoring nokogumbo-2.0.2 because its extensions are not built. Try: gem 
pristine nokogumbo --version 2.0.2
Ignoring psych-3.1.0 because its extensions are not built. Try: gem pristine 
psych --version 3.1.0
Ignoring sassc-2.2.1 because its extensions are not built. Try: gem pristine 
sassc --version 2.2.1
Ignoring stringio-0.1.0 because its extensions are not built. Try: gem pristine 
stringio --version 0.1.0
Ignoring strscan-1.0.3 because its extensions are not built. Try: gem pristine 
strscan --version 1.0.3
Ignoring unicode-0.4.4.4 because its extensions are not built. Try: gem 
pristine unicode --version 0.4.4.4
Ignoring zlib-1.1.0 because its extensions are not built. Try: gem pristine 
zlib --version 1.1.0
/usr/lib/ruby/2.7.0/yaml.rb:3: warning: It seems your ruby installation is 
missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.
Traceback (most recent call last):
14: from /usr/bin/gem:21:in `'
13: from /usr/lib/ruby/2.7.0/rubygems/gem_runner.rb:44:in `run'
12: from /usr/lib/ruby/2.7.0/rubygems/gem_runner.rb:79:in 
`do_configuration'
11: from /usr/lib/ruby/2.7.0/rubygems/gem_runner.rb:79:in `new'
10: from /usr/lib/ruby/2.7.0/rubygems/config_file.rb:182:in `initialize'
 9: from /usr/lib/ruby/2.7.0/rubygems/config_file.rb:332:in `load_file'
 8: from /usr/lib/ruby/2.7.0/rubygems.rb:710:in `load_yaml'
 7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
`require'
 6: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
`require'
 5: from /usr/lib/ruby/2.7.0/yaml.rb:4:in `'
 4: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
`require'
 3: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
`require'
 2: from /home/calum/gems/gems/psych-3.1.0/lib/psych.rb:14:in `'
 1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in 
`require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot 
load such file -- 2.7/psych.so (LoadError)
15: from /usr/bin/gem:21:in `'
14: from /usr/lib/ruby/2.7.0/rubygems/gem_runner.rb:44:in `run'
13: from /usr/lib/ruby/2.7.0/rubygems/gem_runner.rb:79:in 
`do_configuration'
12: from 

Bug#954859: apt-listbugs: listbugs prompt will only accept a package name for pinning

2020-03-24 Thread Calum McConnell
Package: apt-listbugs
Version: 0.1.31
Severity: wishlist

When it comes time to upgrade or not, or pin packages, the 'p' menu requires 
the user to enter the full package name
of whatever package they want to stop the upgrade of.  This is undesireable for 
obvious reasons, since many packages
have lengthy names.
A more concise approach would be to also accept a bug number, like other menu 
items.  To prevent collision
between actual packages and bugs, the syntax could be #, as # 
cannot appear in any valid package names.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listbugs depends on:
ii  apt 2.0.0
ii  ruby1:2.7
ii  ruby-debian 0.3.10+b3
ii  ruby-gettext3.3.3-2
ii  ruby-soap4r 2.0.5-4
ii  ruby-unicode0.4.4-2+b11
ii  ruby-xmlparser  0.7.3-3+b4

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.8.3-2
ii  s6   2.9.0.1-2

Versions of packages apt-listbugs suggests:
iu  chromium [www-browser] 80.0.3987.149-1
ii  firefox-esr [www-browser]  68.6.0esr-1
ii  lynx [www-browser] 2.9.0dev.5-1
ii  reportbug  7.6.0
ii  sensible-utils 0.0.12+nmu1
ii  w3m [www-browser]  0.5.3-37+b1
ii  xdg-utils  1.1.3-2

-- Configuration Files:
/etc/apt/apt.conf.d/10apt-listbugs changed:
// Before installing packages, check whether they have release-critical bugs.
// If you don't like it, comment it out.
DPkg::Pre-Install-Pkgs {"/usr/bin/apt-listbugs apt";};
DPkg::Tools::Options::/usr/bin/apt-listbugs "";
DPkg::Tools::Options::/usr/bin/apt-listbugs::Version "3";
DPkg::Tools::Options::/usr/bin/apt-listbugs::InfoFD "20";
AptListbugs::Severities "all";
// AptListbugs::IgnoreRegexp "FTBFS";


-- no debconf information



Bug#948697: apt-listbugs: Listbugs-spawned QueryBTS can't find Firefox

2020-01-20 Thread Calum McConnell
Below is the email I accidentally sent directly to the maintainer,
instead of pressing reply-all

> > Sorry about taking so long to get back to you: I have been really
> > busy
> > recently.
> 
> No problem, I got ill immediately afterwards!  :-/

That sucks, hope you're doing better!

> But now, I finally found some time to spend on investigating this
> bug.
> I have mixed news for you.
> 
> [...]
> > > First of all: it seems to me that you have firefox-esr unpacked,
> > > but
> > > not configured. In other words, firefox-esr does not seem to be
> > > properly installed on your system:
> > > 
> > > [from System Information in your bug report...]
> > > > iu  firefox-esr [www-browser]  68.4.1esr-1
> > > [...]
> > > 
> > > This could be responsible for a number of errors you encounter,
> > > when
> > > trying to start firefox...
> > 
> > Okay.  I did test a bit, and firefox is definatly working: so if
> > its
> > not unpacked, then somthing weird is going on...
> 
> Did you fix the installation status of firefox-esr?
> What's the output of the command
> 
>   $ dpkg -l | grep firefox
> 
> on your system, now?

I put it below: I did some re-wrapping of lines, because I couldnt
quickly figure out how to make evolution stop wrapping the selection.

$ dpkg -l | grep firefox
ii  firefox-esr   
68.4.1esr-1  amd64
Mozilla Firefox web browser - Extended Support Release (ESR)

> As explained below, this is not the cause of your errors, but
> something
> to be fixed anyway...
> 
> > > I guess xdg-open (internally used by querybts to find a browser)
> > > eventually selected a text browser, such as lynx or w3m:
> > 
> > It did.  I think the errors made that more clear: I'm setting up a
> > controlled test to capture a few.
> [...]
> 
> Now I managed to reproduce the issue, at least with a bunch of
> similar
> errors from firefox (including dialog windows to click into).
> The key point is that you are using "sudo" to become root, while I
> use
> "su -", thus missing one subtle difference.
> 
> Your controlled test was useful in clarifying what you experienced.
> Thanks for taking the time to transcript it (and comment it!).
No problem

> So, without further ado, what happened?
> 
>  • regular user calls sudo to run apt as root
>  • apt calls apt-listbugs
>  • apt-listbugs invokes s6-setuidgid to drop root privileges and run
>querybts as the original regular user
>  • querybts wants to invoke a browser and calls xdg-open on the URL
> 
> [...]
> 
> OK, I think I shared enough of my headache!   ;-)

Thanks for the explaination: it's all making sence now.

> [...]
> 
> Of course, I could completely drop these features, so that apt-
> listbugs
> will no longer be able to invoke querybts or to launch a browser.
> After all, there are other, more comfortable, ways to read bug logs.
> Usually, if you are already in a graphical session, you can start
> your
> favorite browser and copy and paste the bug numbers there. This can
> perhaps be possible even when switching between text consoles...
> 
> But I think there are situations where these strategies are not
> available. Maybe you are stuck in a single text console, and no other
> means to access the web...
> As a consequence, I would like to keep these features, although I
> should probably document that they should be regarded as "last
> resort" approaches...

There is also the fact that it is somtimes handy to be able to get a
full view of the bug quicky: so while copy-paste replicates the
functionality, it also drops the convinience of being able to get more
info about bugs with minimal effort.

> I could drop the s6-setuidgid trick (which will be replaced by
> setpriv in the next version of apt-listbugs, which is however
> equivalent). But running querybts or a browser as root is not a good
> idea, security-wise, and should hence be avoided, wherever possible.
> So, no, I would like to keep the root privilege dropping mechanism,
> to the maximum possible extent.
> 
> Maybe apt-listbugs could drop the DISPLAY enviroment variable before
> invoking querybts or any browser.
> The equivalent of 
> 
>   $ sudo env -u DISPLAY -u XAUTHORITY s6-setuidgid MYREGULARUSER xdg-
> open http://bugs.debian.org/948697
> 
> which directly chooses a text browser, which many less needs than
> firefox!
> I acknowledge that this is not a perfect workaround, but, at least,
> it
> seems to reduce to the more minimalist situations, where the features
> are really needed...
> 
> Let me think about it some more (and feel free to express your
> thoughts!).

That definatly would work for me.  The importance of apt-listbugs, to
me, is being able to take a look at what might break, weigh its
importance, and making a decision on whether or not I should upgrade. 
I can't really think of a reason why reading the bug info in a text
browser would fail to accomplish that goal just as well as a full-
fledged web browser: and if there is some 

Bug#948697: apt-listbugs: Listbugs-spawned QueryBTS can't find Firefox

2020-01-16 Thread Calum McConnell



Bug#948697: apt-listbugs: Listbugs-spawned QueryBTS can't find Firefox

2020-01-14 Thread Calum McConnell
Sorry about taking so long to get back to you: I have been really busy
recently.

> Hello Calum,
> thanks for using apt-listbugs and for caring about reporting the
> issue
> you experienced.

Thank you for your quick responce!  Besides, what is the point of
running sid if not to find bugs and make someone else fix them?

> OK, this launches querybts from package reportbug, which you have on
> your system:

Sounds good...

> OK, please note that this is a menu of the querybts user interface...

I got that far

> First of all: it seems to me that you have firefox-esr unpacked, but
> not configured. In other words, firefox-esr does not seem to be
> properly installed on your system:
> 
> [from System Information in your bug report...]
> > iu  firefox-esr [www-browser]  68.4.1esr-1
> [...]
> 
> This could be responsible for a number of errors you encounter, when
> trying to start firefox...

Okay.  I did test a bit, and firefox is definatly working: so if its
not unpacked, then somthing weird is going on...

> I guess xdg-open (internally used by querybts to find a browser)
> eventually selected a text browser, such as lynx or w3m:

It did.  I think the errors made that more clear: I'm setting up a
controlled test to capture a few.

> I tried to reproduce the issue, but I was not successful: querybts
> started w3m in my case, without any firefox-related errors.

So much for this being a nice, open-and-shut case.

> But the selected browser heavily depends on the system configuration,
> on installed packages, and so forth...
> I am not sure I will be able to investigate this for your system:
> I'll
> have to look deeper, in order to understand which are the key
> questions
> I should ask to you...

Ask away

> How did you start the root session where you were upgrading you
> system?
> Were you inside a desktop session?
> Did you open a terminal?
> Did you use
> 
>   $ su -
> 
> to become root and then start apt or aptitude?
> Or were you using sudo?

So, I was in the GNOME desktop, and to get to apt I opened GNOME shell
(as a normal user) and used sudo apt update, followed by sudo apt
upgrade.  See the reproduced log I attached: basically, just a typical
go-to-the-menu-and-click-on-terminal type operation.

> Since you have s6 installed, apt-listbugs may have launched querybts
> as
> your regular (non-root) user, through s6-setuidgid. However, this
> does
> not correspond to a "full-featured" user session, hence access to
> your
> "normal" user environment is partially unachievable...
> It's complicated (and it will slightly change in the next version of
> apt-listbugs!): I will try to give more details on this, after I
> receive more info from you...

Okay: good to know.

> I should look into querybts and reportbug code more deeply, to be
> sure,
> but maybe in that case querybts ran a text browser as root, thus
> introducing fewer indirectness levels...

> Please provide the requested additional info and let's see whether we
> can shed more light on the issue.

Okay.  I also ran a more controlled test: attached is the text file of
my logs.  I annotated them with a few comments as well, because why
not?

Thanks again: I kind of rely on listbugs to be sure my system isn't
going to go nuclear on me.

> Awkward configuration: you seem to be worried about minor bugs, but
> not
> about normal bugs...

You know how it is: everyone tells you to not sweat the little things,
but you still sweat them enough that you miss the "normal" bugs

Thanks for the catch: I was trying to list all, but without wishlist
bugs: I guess I forgot about the normies.  I switched to using just
"all" lol.
//So, to be sure to trigger the problem, I decided to try and install a known-bad
//package. McComix happened to be at the top of the list when I used the BTS
//web interface to find critical bugs.  I'll try to note down all the things
//not included in the log directly.
//yes, all lines beginning with the c-style comments are me, after the fact.
//(the reason I am in apt.conf.d is to make the fix I meantioned to listbugs)

calum@CalumsDebianSupreme:/etc/apt/apt.conf.d$ sudo apt install mcomix
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  unrar | libunrar mupdf-tools
The following NEW packages will be installed:
  mcomix
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,637 kB of archives.
After this operation, 3,972 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian unstable/main amd64 mcomix all 1.2.1mcomix3+git20191129-1 [2,637 kB]
Fetched 2,637 kB in 1s (1,954 kB/s) 
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of mcomix (→ 1.2.1mcomix3+git20191129-1) 
 b1 - #947508 - mcomix: Upgrade to Python 3 fork deletes user bookmarks
important bugs of mcomix (→ 1.2.1mcomix3+git20191129-1) 
 b2 - #945493 - mcomix: Library shows not all Thumbnails
normal bugs of mcomix (→ 

Bug#948697: apt-listbugs: Listbugs-spawned QueryBTS can't find Firefox

2020-01-11 Thread Calum McConnell
Subject: apt-listbugs: Listbugs-spawned QueryBTS can't find Firefox
Package: apt-listbugs
Version: 0.1.31
Severity: normal

I triggered an update, and apt-listbugs found some bugs.  I used the
b1/b2/b3 notation to query the BTS about said bugs, and read thru the
briefs on screen.  I then tried to use the 'b' menu option to open
firefox, however, I got a rapid fire series of errors instead, along
with
window popups about how the firefox profile was not found.  After I hit
'okay' to each window, it eventually gave me a reasonable text view of
the
bugs.
I would have reproduced the errors below, however, a few other packages
are
having bugs that cause them to spam the terminal with useless,
identical errors,
so the errors from query-bts all got buried (ie, they are above the
viewable
terminal window.)
As a guess, I would say that the root user doesnt have a firefox
profile,
When I ran querybts as a normal user, it was able to open a firefox
page:
sudo querybts wound up opening a text page, and printing about how it
failed to find various browsers, but had no popups about firefox
profiles,
and the error messages were less aggressive.
Thanks for taking the time to review this!
-Calum

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt-listbugs depends on:
ii  apt 1.8.4
ii  ruby1:2.5.2
ii  ruby-debian 0.3.10
ii  ruby-gettext3.2.9-1
ii  ruby-soap4r 2.0.5-4
ii  ruby-unicode0.4.4-2+b9
ii  ruby-xmlparser  0.7.3-3+b2

Versions of packages apt-listbugs recommends:
ii  ruby-httpclient  2.8.3-2
ii  s6   2.9.0.1-2

Versions of packages apt-listbugs suggests:
iu  firefox-esr [www-browser]  68.4.1esr-1
ii  lynx [www-browser] 2.9.0dev.4-1
ii  reportbug  7.6.0
ii  sensible-utils 0.0.12+nmu1
ii  w3m [www-browser]  0.5.3-37+b1
ii  xdg-utils  1.1.3-1

-- Configuration Files:
/etc/apt/apt.conf.d/10apt-listbugs changed:
// Before installing packages, check whether they have release-critical 
bugs.
// If you don't like it, comment it out.
DPkg::Pre-Install-Pkgs {"/usr/bin/apt-listbugs apt";};
DPkg::Tools::Options::/usr/bin/apt-listbugs "";
DPkg::Tools::Options::/usr/bin/apt-listbugs::Version "3";
DPkg::Tools::Options::/usr/bin/apt-listbugs::InfoFD "20";
AptListbugs::Severities "critical,grave,serious,important,minor";
// AptListbugs::IgnoreRegexp "FTBFS";


-- no debconf information



Bug#947907: trying to overwrite '/usr/share/java/juh.jar', which is also in package libjuh-java

2020-01-03 Thread Calum McConnell
I was unfortunate enough to have the oppoiste order of installs: the
four packages, and then URE.  That meant URE's install failed, and I
was left with apt complaining about a broken system.  To get out of it,
I used dpkg -r to get rid of the offending four packages, and then
installed ure.  Of course, then apt began moaning that libreoffice-
java-common was broken, but I removed that and the packages I had
depending on it.

Obviously I would like them back, but libreoffice is working just fine
without them.  

Just wanted to put my workarround up here in case anybody else had the
same bad luck as me.