Bug#999858: pbuilder: debconf template suggest obsolete plain-http URL

Package: pbuilder Version: 0.231 Nowadays only HTTPS entries are in sources.list (maybe that could unblock a fix for #790565 ?), the debconf script seems to fail to detect a mirror as described in that bugreport... and we are shown: Here is a valid mirror example: http://deb.debian.org/debian

Bug#992806: ftjam - ship with bookworm?

> ftjam is the freetype.org improved "jam" (a build tool thats > supposedly better than make). I remember jam being "the hype" a long > time ago. freetype.org themselves have switched away from jam ... a > long time ago, and even switched to meson in the mean time. > > I guess some users of the

Bug#989102: memtest86 - upstream abandonded, still useful?

> Given memtest86 has not received any updates since 2014, one has to > ask if it is still useful. memtest86+ exists, and while it does not > see -regular- updates, it at least gets some. > > Maybe we should remove memtest86 from bookworm? > > Parties interested in keeping memtest86 should speak

Bug#965025: Acknowledgement (gpsshogi-data: data does not seem to be provided in the preferred format for modification)

close 965025 thanks upstream clarification from Daigo: > We (as the upstream) created an opening book file and > evaluation files in a statistical / machine learning > way from a large amount of data with lots of machine > power and tuning parameters. It was not our priority > to develop an

Bug#977532: gscan2pdf: save option not available

>The version of libtiff-tools in testing still outputs to stderr, so I am >inclined to say this is not (yet) a Debian bug, and certainly not important. > >Indeed, your patch will break the version of gscan2pdf in testing. Arguably, this is for this type of problems that we have the ability to

Bug#975545: virtinst: bombs out when virsh missing

Package: virtinst Version: 1:3.1.0-1 virtinst should maybe "Recommends: libvirt-clients" ? $ virt-install --virt-type kvm --name buster-amd64 \ > --location http://deb.debian.org/debian/dists/buster/main/installer-amd64/ \ > --os-variant debian10 \ > --disk size=10 --memory 1000 \ > --graphics

Bug#972941: [DRE-maint] Bug#972941: jekyll: complains about missing kramdown-parser-gfm

> > The real problem is probably https://bugs.debian.org/972702. For > > the > > time being > > please add > > > > gem "kramdown-parser-gfm" > > > > to your Gemfile and eventually remove Gemfile.lock. That should fix > > it. > > Yes that does help, thanks! It is still probably worth

Bug#972941: [DRE-maint] Bug#972941: jekyll: complains about missing kramdown-parser-gfm

- Mail original - > De: "Daniel Leidert" > À: 972...@bugs.debian.org > Cc: 972941-submit...@bugs.debian.org > Envoyé: Lundi 26 Octobre 2020 17:50:13 > Objet: Bug#972941: [DRE-maint] Bug#972941: jekyll: complains about missing > kramdown-parser-gfm > > Am Montag, den 26.10.2020, 13:49

Bug#972941: Acknowledgement (jekyll: complains about missing kramdown-parser-gfm)

Digging further with "strace -e file", I can see that: * other modules are indeed searched for in the kramdown-parser-gfm directory, eg: 187928 stat("/usr/share/rubygems-integration/all/gems/kramdown-parser-gfm-1.1.0/lib/idn", 0x7ffd35c48590) = -1 ENOENT (Aucun fichier ou dossier de ce type)

Bug#972941: jekyll: complains about missing kramdown-parser-gfm

Package: jekyll Version: 3.9.0+dfsg-1 Starting to use a new machine and incrementally installing missing packages, I finally get stuck with this: $ jekyll serve Configuration file: /home/yann/perso/blog/floss-cook/_config.yml Source: /home/yann/perso/blog/floss-cook

Bug#972030: python3-nose: issues warning "No module named 'setuptools.extern.six'"

Package: python3-nose Version: 1.3.7-7 This may be linked to the update from python 3.8.5 to 3.8.6 which just reached testing, at least I did not get that yesterday and that looks like a good culprit: $ cd /tmp/ $ nosetests3 /usr/lib/python3/dist-packages/nose/plugins/manager.py:394:

Bug#970588: accerciser: exception on plugin initialzation

Package: accerciser Version: 3.38.0-1 When starting accerciser (on a recently installed buster upgraded to testing) I get a "plugin errors" tab with a "io.UnsupportedOperation: fileno" title and the following contents. Not sure whose problem it is given the presence of ipython in this stack

Bug#969363: aptitude: goes to 100%CPU and ram usage skyrocketting when handling dependencies

Package: aptitude Version: 0.8.13-2 Starting from a task-desktop-lxde setup, and trying to remove xserver-xorg-video-all and reselecting packages I don't want to go away seems to cause issues to aptitude. I'm keeping an aptitude bundle for initial state, available on request (not sure it makes

Bug#968012: sjaakii: variant "judkins" has incomplete FEN, does not load properly in XBoard

Package: sjaakii Version: 1.4.1-2 Tags: patch X-Debbugs-CC: Evert Glebbeek This change is necessary to avoid undefined behaviour from XBoard (which in this cases ignores the last rook, leading to wrong initial position) --- /tmp/variants.txt 2020-08-06 19:07:29.331235206 +0200 +++

Bug#966378: gazebo: exits with code 255 attempting to create a joint in model

Package: gazebo Version: 11.0.0+dfsg1-4+b3 context: after reading the "beginner:model editor" tutorial while on the move, I tried to reproduce it from memory: creation of links, but manual positionning of wheels and then creation of joints. Then getting back to the tuto I wanted to try the

Bug#965153: gscan2pdf: "fails to open device" for Epson NX100

Package: gscan2pdf Version: 2.8.0-1, 2.8.1-1 Severity: grave Except for a couple of times I've been able to get it to work (without knowing what it was that made it finally work after minutes of battle)... * when I start gscan2pdf it claims it does not see my scanner and offers to rescan or

Bug#965022: ITP: apery -- Strong AI for playing Shogi

> Package: wnpp > Severity: wishlist > Owner: Yann Dirson > > * Package name: apery > Version : WCSC28+git20191114 > Upstream Author : Hiraoka Takuya > * URL : https://github.com/HiraokaTakuya/apery > * License : GPL > Programming Lang: C++ > Description

Bug#964730: ITP: gpsshogi -- Shogi playing program based on OpenShogiLib

Hi Paul, > On Thu, Jul 9, 2020 at 4:18 PM Yann Dirson wrote: > > > This is rather an Intent to Resurrect, as gpsshogi was in Debian > > 2 releases ago. > > Please note the extra steps needed when reintroducing packages, > principally reopening the bugs that were closed by the removal of the >

Bug#964730: ITP: gpsshogi -- Shogi playing program based on OpenShogiLib

> Package: wnpp > Severity: wishlist > Owner: Yann Dirson > > This is rather an Intent to Resurrect, as gpsshogi was in Debian > 2 releases ago. > > * Package name: gpsshogi > Version : 0.7.0 > Upstream Author : Team GPS, feat. Daigo Moriwaki > * URL :

Bug#964414: gnuchess: stdin parsing issues

Package: gnuchess Version: 6.2.5-1 Trying to pinpoint a problem I have driving gnuchess from another program, I stumbled on this: $ printf "xboard\n" | gnuchess -x Chess *** buffer overflow detected ***: gnuchess terminated Aborted (core dumped) $ gdb gnuchess ./core GNU gdb (Debian 9.2-1)

Bug#936023: CVE-2019-15767: fixed in latest upstream ?

Given the comment on the upstream ml, this bug is likely fixed in latest release.

Bug#963983: closed by Gianfranco Costamagna (Re: python3-pyside2.qtsvg: segfault on import)

reopen 963983 thanks The other pyside2 packages (code, gui etc) were still at 5.15.0-1~exp1. If I just update qtsvg to 5.15.0-2 the segfault still happens. Update the rest of pyside2 triggers a huge cascading of upgrades to Qt 5.14 which had not been done when I had installed the exp packages,

Bug#963983: python3-pyside2.qtsvg: segfault on import

Package: python3-pyside2.qtsvg Version: 5.15.0-1 Severity: grave $ gdb python3 ... Reading symbols from python3... Reading symbols from /usr/lib/debug/.build-id/97/0f19629d98e5c631b44f6803fa34a5a07c3806.debug... (gdb) r Starting program: /usr/bin/python3 [Thread debugging using libthread_db

Bug#952645: webext-ublock-origin: any reason we still have a 6-month old version ?

Hi Markus, > There is also little value in filing pointless bug reports against > Debian packages. Sorry, I did not meant any offense in this followup to an old bugreport. It used to be that firefox allowed user to locally install a newer version of a system-wide-installed extension, but this is

Bug#952645: webext-ublock-origin: any reason we still have a 6-month old version ?

IMHO there's little value on having such a plugin packaged, if we cannot follow the releases.

Bug#963011: scalene: please re-upload as source-only

Package: python3-scalene Version: 0.7.5-1 The package has not migrated to testing and https://tracker.debian.org/pkg/scalene shows why: Not built on buildd: arch all binaries uploaded by sergi...@sergiodj.net, a new source-only upload is needed to allow migration

Bug#961593: emacs: help menu entries that require non-free info file should tell what to do

Package: emacs Version: 1:26.3+1-2 Default installation of emacs package does not include the info manual, as they are in emacs-common-non-dfsg. A user selecting help menu entries "read the emacs manual", "how to report a bug" and such are given the info index window, and may miss easily the

Bug#942596: [DRE-maint] Bug#942596: jekyll and required bundles

Hi Daniel, > > I finally understood what confused me at first: even with > > --skip-bundle, > > "jekyll new" creates a Gemfile. And until this Gemfile is removed, > > "jekyll build" will try to go the bundle way all by itself. > > That is not true. As I explained earlier I'm using jekyll

Bug#942596: [DRE-maint] Bug#942596: jekyll and required bundles

Hi Daniel, - Mail original - > 1) Use the Debian package management and don't use bunlder at all > (jekyll new > --skip-bundle). All the Jekyll plugins have been packaged and most of > them can > be found in stable-backports. If you are missing some please let me > know. Just > add the

Bug#795421: version 5.01 freezes on test #7 in SMP mode

There is a rumor of an incoming upstream version including most of the patches that appeared since the last one. I'd rather wait for that one :) - Mail original - > De: "Christoph Anton Mitterer" > À: 795...@bugs.debian.org > Cc: dir...@debian.org > Envoyé: Mercredi 22 Avril 2020

Bug#942596: [DRE-maint] Bug#942596: jekyll and required bundles

Hi Daniel, - Mail original - > De: "Daniel Leidert" > À: ydir...@free.fr, 942...@bugs.debian.org > Envoyé: Lundi 20 Avril 2020 16:19:17 > Objet: Re: [DRE-maint] Bug#942596: jekyll and required bundles > > Am Sonntag, den 19.04.2020, 18:28 +0200 schrieb ydir...@free.fr: > > Trying Jekyll

Bug#942596: jekyll and required bundles

I could finally install the dependencies with the default Gemfile, by downgrading ruby from 2.7 back to 2.5. Looks like eventmachine does not have support for 2.7 yet (hint given by the ruby-eventmachine package in experimental, which still uses 2.5). "bundle exec jekyll build" now works. Good

Bug#942596: jekyll and required bundles

Trying Jekyll for the first time, I get hit by the same issue. Indeed this flag is a good start, but afterwards: 1. we have to gather we should change the Gemfile to use: source "file:///usr/lib/ruby/vendor_ruby" 2. we get hit by missing bundles, that should surely be added as Recommends:

Bug#955588: keepassx: description says "install keepassx instead"

Package: keepassx Version: 2.0.3+git20190121.1682ab9-2.1+b1 The description explain that keepassxc is better than keepassx, but still says "install keepassx instead". It is highly confusing :)

Bug#954660: libsdl2: upstream 2.0.12 released

Package: libsdl2 Version: 2.0.10+dfsg1-2 Severity: wishlist See https://discourse.libsdl.org/t/sdl-2-0-12-released/27318

Bug#953154: lxqt-panel: huge memory leak

Package: lxqt-panel Version: 0.14.1-1+b1 After ~2 month uptime of a single session, resident memory usage is growing unreasonably. A couple of days ago it was 1.5GB already, and today: # top [...] 2548446 yann 20 0 3205080 2.6g 12808 S 0.7 17.0 57:09.15 lxqt-panel

Bug#921220: xchat stops autoconnecting, complaining about "%U" and "host unknown", broken .desktop entry ?

The control email got bounced before unarchiving, here are the details of new findings. - Mail original - > unarchive 921220 > reopen 921220 > retitle 921220 xchat.desktop makes invalid use of %U, breaks at least > lxqt and flwm > affects 921220 + lxqt flwm > severity 921220 grave >

Bug#943752: Needs GCC-6

> A further information I received via IRC is that memtest86+ > _has_ to be compiled with GCC-6 - newer versions have a bug > that break memtest86+. > > I have verified that GCC-6 gives a working result, > while GCC-8 doesn't. Now that is a major issue, as gcc-6 was not even released with

Bug#943752: memtest86+: Please switch source tree

> Upstream memtest86+ is broken - and there are a few patches that > aren't > even included. > > I'd recommend to switch over to > > $ git clone https://review.coreboot.org/memtest86plus > > as that seems maintained, and will even work on my machine > (and not just hang, like upstream). >

Bug#939754: not found in stable

notfound 939754 2.10.8-2 thanks Downgrading to the build currently in buster works around the crash.

Bug#563000: closed by Debian FTP Masters (Bug#935854: Removed package(s) from unstable)

reopen 563000 found 563000 2.2.2-2 thanks Still happens today: Omaha/Holders/.#HexBoard.py:1:0: F0010: error while code parsing: Unable to load file Omaha/Holders/.#HexBoard.py: [Errno 2] No such file or directory: 'Omaha/Holders/.#HexBoard.py' (parse-error) - Mail original - > De:

Bug#695873: memtest86+: Serial console does not work

Hi, Feel free do NMU - thanks much for this :) - Mail original - > De: "Louis-Philippe Véronneau" > À: 695...@bugs.debian.org > Envoyé: Mardi 13 Août 2019 21:44:38 > Objet: Bug#695873: memtest86+: Serial console does not work > > Hello! > > I'd be happy to make an NMU to fix this,

Bug#934265: qtbase5-dev: different archs ship different version of Qt-logo.png

Package: qtbase5-dev Version: 5.11.3+dfsg1-2+b1 Severity: serious Unpacking qtbase5-dev:i386 (5.11.3+dfsg1-2+b1) over (5.11.3+dfsg1-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-01jgzV/14-qtbase5-dev_5.11.3+dfsg1-2+b1_i386.deb (--unpack): trying to overwrite shared

Bug#927010: python3-babeltrace: Event instances all refer to a constantly-overwritten data - unexpected behaviours and segfaults

Package: python3-babeltrace Version: 1.5.6-2 Severity: important While investigating why I was getting a segfault while processing a CTF trace (in which I do a first pass extracting some info, before a second pass plotting the data... while keeping a ref to various events to avoid making copies

Bug#921220: xchat stops autoconnecting, complaining about "%U" and "host unknown", broken .desktop entry ?

Package: xchat Version: 2.8.8-17 xchat when launched from lxqt menu does not autoconnect any more, showing only the following. Python interface loaded Tcl plugin for XChat - Version 1.64 Copyright 2002-2005 Daniel P. Stasinski http://www.scriptkitties.com/tclplugin/ Tcl interface loaded

Bug#916200: script: does not reap signaled children any more, deadlocks until SIGKILL

Package: bsdutils Version: 1:2.32.1-0.1 Severity: important Since upgrade from stretch to buster, script does not terminate any more when the monitored process gets killed. The child is left as a zombie, and when sent SITERM or SIGQUIT script only prints "Session terminated." and does not

Bug#915313: packages-arch-specific: please blacklist cssc on mips

Package: buildd.debian.org Presumably following gcc upgrade, package cssc does not build correctly any more on mips (as well as a couple of non-release archs). Until someone can take the time to dive into this, could you please blacklist it from mips, so that it does not prevent it to be

Bug#915310: developer-reference: broken link to anonscm.debian.org

Package: developer-reference Version: 3.4.18 We have a broken link in current master branch. It also impacts stretch (hence my selection of version). developers-reference (master=)$ git grep anonscm.debian.org

Bug#905674: proper severity

Adam wrote: > Note that parallel's functionality is also provided by moreutils and xargs > -P, thus moving the package out of main would be just an inconvenience (four > packages need to be adjusted: roary last-align freebayes symfony). That may be true of the basic usage of the tool. However, I

Bug#905674: Funding free software

Hello Ole, I do understand that funding Free Software is a problem of its own, but I'm quite surprised to see a program with "GNU" in its name doing things that way. Is it a way of funding that is endorsed by the GNU project ? Best regards, -- Yann

Bug#900399: More good news

severity 900399 normal thanks I suggest you get some advice from the forum[1], and as Dmitry mentionned, bring the issue to Lenovo. [1] http://forum.canardpc.com/forums/73-Memtest86-Official-forum?s=1407c99a4da914ef85e60c32c658ba16 - Mail original - > De: "Сергей Коган" > À:

Bug#902472: sdl2: can deadlock after hiding a window

Package: libsdl2 Version: 2.0.5+dfsg1-3 Tags: stretch patch It can happen that SDL gets stuck waiting for X to accept a grab request, when the window has already been hidden with SDL_HideWindow. This behaviour has been fixed in 2.0.6 with commit 8f0a002 "x11: Don't loop forever if the X server

Bug#891840: gaminggearfxinfo: fails with missing gaminggear_plugins

Hello, That does not fix the init issue, likely 2 different problems: $ gaminggearfxinfo ** (process:21432): WARNING **: Could not initialize fx system $ echo $? 1 - Mail original - > De: "Pierre-Elliott Bécue" > À: 891...@bugs.debian.org, ydir...@free.fr > Envoyé:

Bug#891840: gaminggearfxinfo: fails with missing gaminggear_plugins

Package: gaminggearfxinfo Version: 0.15.1-7 Can't tell if the missing plugin dir is *the* problem. Seems also strange that "Could not initialize fx system" is only reported as a warning and not as a fatal error. $ gaminggearfxinfo ** (process:4089): WARNING **: Error opening directory

Bug#886464: libgaminggear0: uhid line causing errors (with old libkmod ?)

Package: libgaminggear0 Version: 0.15.1-3 This package maybe lacks a versionned dependency, it causes errors when installed on a mostly-stretch install: Preparing to unpack .../linux-image-4.14.0-3-amd64_4.14.12-1_amd64.deb ... /etc/kernel/preinst.d/intel-microcode: libkmod: ERROR

Bug#886128: mini-buildd: answering "never" to auto-setup is not honored

Package: mini-buildd Version: 1.0.32~bpo9+1 yann@buildd:~$ mini-buildd-tool admin@buildd:8066 status [admin@buildd:8066] Password: Saving 'mini-buildd' passwords to 'keyrings.alt.file.EncryptedKeyring' with policy 'Ask': Save password for 'admin@buildd:8066': (Y)es, (N)o, (A)lways, Ne(v)er?

Bug#886126: mini-buildd: using alt.files as keyring backend is highly impractical

Package: mini-buildd Version: 1.0.29 With no external keyring software installed, python-keyring defaults to alt.files, and the impact on scripting (eg. launching auto-setup for a test) is quite high: * have to enter keyring password for each keyring access * a single error in one of those

Bug#886123: python3-keyring: cannot import name 'unicode_str'

Package: python3-keyring Version: 10.5.1-1 After updating just this package on stretch to get the keyring binary: $ keyring get mini-buildd admin Error initializing plugin kwallet = keyrings.alt.kwallet. Traceback (most recent call last): File

Bug#884539: fbxkb: does not explain how to add new keyboards

Package: fbxkb Version: 0.6-2+b1 fbxkb adds a flag matching current layout to my panel, but it is not obvious what one should do to get access to more choices. Left click on flag has no effect, right click only has "about" (curiously labeled "information") and "quit".

Bug#878265: libyami-utils: please build with GLES support

Package: libyami-utils Version: 1.2.0-1 When trying "yamidecode -m 2" or "-m 3" or "-m 4", we get an error message saying "do not support this render mode". Source code shows those are conditionned by GLES support, and rebuilding locally with GLES detected by configure allows me to use modes 2

Bug#876122: spam accumulating in debian-embedded archive

Package: lists.debian.org The last 5 months of debian-embedded archive is essentially spam. At least some of them are rejected by my ISP's MTA with a 500, and that causes reports from the list server that mails to me are bouncing, which is quite uncomfortable :)

Bug#875912: Remove gcompris?

No problem, we can request its removal and go for transition. I'd suggest we wait for new gcompris-qt maintainer to finalize his first upload, and then request removal of old gcompris. - Mail original - > De: "Jeremy Bicha" > À: "submit" >

Bug#873642: weboob-qt: misses dependency on python-pyqt5.qtmultimedia

Package: weboob-qt Version: 1.2-1 Severity: serious without it, qvideoob fails with: $ qvideoob Traceback (most recent call last): File "/usr/bin/qvideoob", line 24, in from weboob.applications.qvideoob import QVideoob File

Bug#861974: libcurl4-openssl-dev multi-architecture incompatibility also affects gnutls version

The same problem happens when trying to install amd64 and i386 versions of the libcurl4-gnutls-dev package.

Bug#872223: tex-common: fails to configure, fmtutils reports errors about missing files

reassign 872223 dpkg severity 872223 grave thanks Well, probably not a missing Conflicts, as downgrading tex-common to the stretch version does not fix the problem. Really a problem with missing files that should not be missing. In fact, despite having the package installed, there is no such

Bug#872223: tex-common: fails to configure, fmtutils reports errors about missing files

Package: tex-common Version: 6.07 I'll spare you the full logs, the end seems to make things quite clear: fmtutil [INFO]: /var/lib/texmf/web2c/luatex/dviluatex.fmt installed. fmtutil [WARNING]: inifile xmltex.ini for xmltex/pdftex not found. fmtutil [WARNING]: inifile jadetex.ini for

Bug#864826: gammaray: 2.8.0 is out

Package: gammaray Version: 2.7.0-1 Severity: wishlist https://github.com/KDAB/GammaRay/releases

Bug#864825: gammaray: crashes target program on attach

Package: gammaray Version: 2.7.0-1 severity: grave When attaching to any Qt5 or Qt4 process, the target process crashes. Here with a freshly-launched kwrite for demonstration: #0 0x7f21b4fd96ad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f21af8429f6 in g_main_context_poll

Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade

Purged laptop-mode-tools, rebooted, no change. network-manager is properly started at boot time, service can be stopped, but not started again afterwards: systemd now has a "(kManager)" child at near-100% CPU. Found the culprit: I have a broken schroot configuration (talk about pending work

Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade

Will test this soon. Oh, just noticed that the fan was indeed noisy... and top reports this: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6019 root

Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade

Here is the relevant journalctl -alb excerpt, sending more details in private mail Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait Online... Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager... Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.5839] caught

Bug#859147: network-manager: restart failure on upgrade

Package: network-manager Version: 1.6.2-3 When upgrading from 1.6.2-2: Setting up network-manager (1.6.2-3) ... Job for NetworkManager.service failed because a timeout was exceeded. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. invoke-rc.d: initscript

Bug#857374: virtualenvwrapper: bash completion lacks testing for availability

Package: virtualenvwrapper Version: 4.3.1-2 When virtualenvwrapper is uninstalled but not purged, we get this each time bash completion is sourced: bash: /usr/share/virtualenvwrapper/virtualenvwrapper_lazy.sh: No such file or directory

Bug#855788: 855788 severity

FWIW, no such problem here. Is that high severity really warranted ?

Bug#776941: dh-kpatches: please help make builds reproducible

Well, the package is orphaned (although I never did an upload removing my name from the maintainer field, it has a proper WNPP bug). For some reason some people seem to be still using it :) - Mail original - > De: "Chris Lamb" > À: 776...@bugs.debian.org > Envoyé:

Bug#833741: Patch updated for 1.8.3

Updated Bob's patch, which was against 1.8.1, to 1.8.3. This fixes both RC bugs, uploading a NMU hoping it's not too late... diff --git a/debian/changelog b/debian/changelog index e94d50a..965efd3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,17 @@ +pepperflashplugin-nonfree

Bug#849856: input-utils: outdated upstream URL, new upstream release

Package: input-utils Version: 1.0-1.1 Contents behind upstream URL in copyright in watch files is apparently a set of CVS snapshot not updated any more. There is a 1.2 release at https://www.kraxel.org/releases/input/ Homepage at https://www.kraxel.org/blog/linux/input/

Bug#849072: lightdm: add-seat badly documented, apparently deprecated

Package: lightdm Version: 1.18.2-2 While "dm-tool add-nested-seat" does work, it is not suitable for all uses, and "dm-tool add-seat" looks like the way to launch a real new X session. However: * manpage mentions the syntax is "dm-tool add-seat TYPE" without giving any clue as to what TYPE

Bug#848668: emacs25: please include .desktop file for emacsclient

Package: emacs25 Severity: wishlist Tags: patch Today eg. firefox proposes to open a text file in emacs, but since it only finds apps through desktop files, it won't propose emacsclient. Attached the one I'm using now, quickly modified from emacs25.desktop emacsclient25.desktop Description:

Bug#847996: edid-decode: wrongly interprets 13-byte strings as non-conforming

Package: edid-decode Version: 0.1~git20140128.afcf2a2e-1 The spec states that only when the "Alphanumeric Data String Descriptor Definition" is less than 13 bytes, should it be followed by 0x0A and further padded with 0x20. Thus, a 13-byte string without a 0x0A is valid, but edid-decode rejects

Bug#844296: libstdc++6-7-dbg: undeclared common file with libstdc++6-6-dbg

Package: libstdc++6-7-dbg Version: 7-20161112-1 Unpacking libstdc++6-7-dbg:amd64 (7-20161112-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-K00oDb/18-libstdc++6-7-dbg_7-20161112-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/debug/libstdc++.a', which is

Bug#833741: patch/nmu ?

tags 833741 + patch thanks Is there any reason not to apply that patch ?

Bug#834790: aptitude hangs at "Loading cache" when unable to download package list

Just hit the same problem after adding a valid sources.list entry without having imported the repo signing key, and I can confirm it'the behaviour is really awkward - and reading suggestions that letting the user lose time until he figures out he has to restarti aptitude would be a valid way out

Bug#841765: enet: new version available

Package: enet Version: 1.3.12+ds-2 1.3.13 was apparently released some time ago. http://enet.bespin.org/download/

Bug#836777: perceptualdiff: does not catch disk-full condition, creates 0-size diffs

Package: perceptualdiff Version: 1.2-2 -output will always create a file, but when the disk is full its size is 0 and we don't get an error message.

Bug#836265: [Aptitude-devel] Bug#836265: aptitude: keeps reselecting sysvinit

- Mail original - > De: "David Kalnischkies" > À: ydir...@free.fr, 836...@bugs.debian.org > Envoyé: Jeudi 1 Septembre 2016 16:20:55 > Objet: Re: [Aptitude-devel] Bug#836265: aptitude: keeps reselecting sysvinit > > On Thu, Sep 01, 2016 at 02:10:14PM +0200,

Bug#836265: aptitude: keeps reselecting sysvinit

- Mail original - > De: "Sven Joachim" > À: ydir...@free.fr > Cc: "Axel Beckert" , 836...@bugs.debian.org > Envoyé: Jeudi 1 Septembre 2016 12:24:59 > Objet: Re: Bug#836265: aptitude: keeps reselecting sysvinit > > On 2016-09-01 11:58 +0200,

Bug#836265: [Aptitude-devel] Bug#836265: aptitude: keeps reselecting sysvinit

- Mail original - > I don't see sysvinit being Essential anymore in unstable: > > → apt-cache show sysvinit | fgrep -i Essential > This package depends on init, which is an essential package that > → > > Any chance that you have stable/jessie in your sources.list, too? Yes: wheezy,

Bug#836068: tightvnc: version 1.3.10

Package: tightvnc Version: 1.3.9-8 Severity: wishlist Although develelopment seems to have stopped in this software, the latest version on http://www.tightvnc.com/download-old.php is more recent than ours.

Bug#835046: apt-listchanges: complains about InfoFD after upgrade

Package: apt-listchanges Version: 3.3 After an upgrade in aptitude, which notified me of changes in the config file, and for which the config file was properly replaced by the new version, I get the following when I request installation of a new package from the same aptitude session:

Bug#831825: clarification request

severity 831825 important tags 831825 + unreproducible moreinfo reassign 831825 gcompris-qt thanks Let's lower the severity as it seems not to impact all users. Trying to reproduce, I'm puzzled by the description, as gcompris does not have a bottom-left menu, although gompris-qt has one. I'm

Bug#833630: scalpel: performance decreases with running time

Another test, more closely monitored, with the same set of 100 1024-bytes patterns, carving a 1TB SATA drive, with defines updated to avoid buffer overflows: +--- scalpel-1.60.orig/scalpel.h scalpel-1.60/scalpel.h +@@ -143,11 +143,10 @@ void setProgramName(char *s); + + + #define

Bug#833649: scalpel: no check for overflow while reading patterns

Package: scalpel Version: 1.60-1 Severity: important Although the buffer used to hold a line is larger than in the original foremost code, it still does not check that the buffer really holds a complete line, and strtok will happily corrupt data outside of the buffer when a line is large enough.

Bug#632689: scalpel: upstream changed

Taking a look at the 2.0 source code from the sleuthkit repo, we can see a small issue with that version: It looks like it uses PASCAL-style prefix-length strings to store patterns, which prevents to use patterns larger than 256 bytes. Why on earth not using a struct to keep the size in an

Bug#833642: foremost: hardcoded limit of 50 patterns is not enforced, segfault

Package: foremost Version: 1.5.7-5 Severity: important main.h: s_spec search_spec[50]; /*ARRAY OF BUILTIN SEARCH TYPES*/ Feeding a config with a large number of entries causes a buffer overflow. It segfaults for my large config, but someone with 51 entries could have funny surprises...

Bug#833639: foremost: cryptic/suspicious error message about config parsing and corrupts memory when lines are longer than 1024 bytes

Package: foremost Version: 1.5.7-5 Severity: important When forging a config file with 100 big (1024-bytes) patterns, I get the message "ERROR: In line 2 of the configuration file." That: * does not tell what the problem is * is suspect because there is no reason why line 1 would have worked and

Bug#833638: foremost: does not completely honor build opts

Package: foremost Version: 1.5.7-5 Tags: patch Only adding flags to the default -O2 will not allow build option "noopt" to work. From faa2c13f600818fc2aac0c293ff55a2935265041 Mon Sep 17 00:00:00 2001 From: Yann Dirson Date: Sun, 7 Aug 2016 13:46:04 +0200 Subject: [PATCH]

Bug#632689: scalpel: upstream changed

Looking for 2.0 source, one rapidly notices that the upstream Homepage is not valid any more. Digging a bit: * Fedora seems to have an upstream tarball at http://pkgs.fedoraproject.org/lookaside/pkgs/scalpel/scalpel-2.0.tar.gz/b0da813bf34941e79209d7fafe86a6e6/ *

Bug#833630: scalpel: performance decreases with running time

Package: scalpel Version: 1.60-1 Severity: important Running scalpel on a 1TB drive with 100 patterns of 1024 bytes each: * ETA some time after starting stabilized around 11h (as I recall it, but this number is superfluous, the next ones talk loud enough) * after 11h run it has done 63% and the

Bug#832797: sgt-puzzles: missing menu entries

Package: sgt-puzzles Version: 20160429.b31155b-1 At least sgt-undead is not in the /usr/share/menu/ declaration - and since for some reason (too many entries?) lxqt does not list all games from desktop files, the only way to launch it from lxqt seems to be from cmdline.

  1   2   >