Package: totem
Version: 3.22.1-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
try to use totem to read a mp4 h264 video:
(totem:15601): Totem-WARNING **: Failed to reset the playback rate
Package: debhelper
Version: 10.6
Severity: grave
If debian/package.install has lines that start with a slash, dh_install
takes those as absolute filenames. I have just tried to build the
giflib package, and dh_install copied whole trees of the /usr directory
into the package build directories
Package: python3-lxml
Version: 3.8.0-1
Severity: important
Despite building on python3-all-dev, only content from the default python3 is
built for python3-lxml. Please build for all supported versions as it
considerably reduces the complexity of transitions.
>From the build log after python3.6
Hi,
On Fr 30 Jun 2017 03:55:51 CEST, Cyril Brulebois wrote:
Control: tag -1 pending
Mike Gabriel (2017-06-28):
the package has just been uploaded (by mfv@d.o).
Flagged for acceptance, thanks.
In hindsight, I should have asked for a more verbose changelog entry.
tag 866546 + pending
thanks
Some bugs in the libjavaewah-java package are closed in revision
18c54855e14c2d1b31b1ab1b94c9eac3dc19d09b in branch 'master' by tony
mancill
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libjavaewah-java.git/commit/?id=18c5485
Commit message:
Package: src:protobuf
Version: 3.0.0-9
Followup-For: Bug #862805
https://buildd.debian.org/status/fetch.php?pkg=protobuf=amd64=3.0.0-9%2Bb1=1498793534=0
==
FAIL: testInvalidTimestamp
Source: uima-addons
Version: 2.3.1-6
Severity: serious
>From my pbuilder build log:
...
[INFO]
[INFO] Building UIMA Addon: SimpleServer 2.3.1
[INFO]
Source: sisu-maven-plugin
Version: 1.1-2
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
On Fri, 30 Jun 2017 at 04:45 Adrian Bunk wrote:
> File "/usr/lib/python3/dist-packages/cffi/api.py", line 56, in __init__
> import _cffi_backend as backend
> ModuleNotFoundError: No module named '_cffi_backend'
>
The cause of this error is that Python 3.6 was just added
tag 866562 + pending
thanks
Some bugs in the maven-invoker package are closed in revision
e2daf9b072072cc0884d131ac2a247aa77cb9cfd in branch 'master' by tony
mancill
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/maven-invoker.git/commit/?id=e2daf9b
Commit message:
Source: openhft-chronicle-queue
Version: 3.6.0-1
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
Source: flask-migrate
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.6
Dear Maintainer,
We updated flask-migrate in Ubuntu got a very strange ftbfs when Python 3.6 was
the default. I figured out what was going on and filed
Source: bind9
Version: 1:9.9.5.dfsg-9
Severity: grave
Tags: patch security upstream
Hi,
the following vulnerabilities were published for bind9.
CVE-2017-3142[0]:
|An error in TSIG authentication can permit unauthorized zone transfers
CVE-2017-3143[1]:
|An error in TSIG authentication can
tag 808584 + pending
thanks
Some bugs in the jsmpp package are closed in revision
bcaa52efa614d85684385f8fb77628e6985c0d81 in branch 'master' by tony
mancill
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jsmpp.git/commit/?id=bcaa52e
Commit message:
Update Vcs URLs
Package: dump
Version: 0.4b44-5
Severity: minor
First line of description "4.4bsd dump and restore for ext2 filesystems".
NAME line from man page, "dump - ext2/3/4 filesystem backup".
The Debian package description should mention it works for ext3 and ext4.
Generally "bsd" is all capital
Source: maven-invoker
Version: 2.2-3
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
Package: libquartz2-java
Followup-For: Bug #864768
Hi Emmanuel,
Unlike 1.8.6, which did automatically perform update checks [1], the
2.2.3 upstream version skips the update check by default [2], i.e. when
the org.quartz.scheduler.skipUpdateCheck property is not set and also
when the
Control: tag -1 pending
Gianfranco Costamagna (2017-06-27):
> uploaded.
Flagged for acceptance, thanks.
(Please use reply-all on the BTS.)
FWIW this might make sense to fix this in jessie as well? If you agree,
feel free to open a jessie-pu bug report to track it.
Package: src:metview
Version: 4.8.0-4
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it has no
Python3 content. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this as
important) [1].
Source: maven-enforcer
Version: 1.4.1-2
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_autoreconf -O--buildsystem=maven
dh_auto_configure
Hi,
Raphael Hertzog (2017-06-29):
> On Tue, 27 Jun 2017, Cyril Brulebois wrote:
> > Personally, I find the systemd part a bit touchy, but I'm happy to ACK
> > the bash-completion fix on its own. Maybe we could handle this in two
> > steps, until the systemd unit situation
Package: apt
Version: 1.5~alpha2
Severity: normal
Hi!
So I'm trying the newest and greatest Dir::Bin::methods::https "http";
and get:
Get:1 http://apt.angband.pl:3142/debian buster InRelease [107 kB]
Ign:2 https://angband.pl/debian sid InRelease
Get:3 http://apt.angband.pl:3142/debian unstable
Source: python-os-api-ref
Version: 0.3.0+dfsg1-3
Severity: serious
Some recent change in unstable makes python-os-api-ref FTBFS:
https://tests.reproducible-builds.org/debian/history/python-os-api-ref.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-os-api-ref.html
Source: libquartz2-java
Version: 2.2.3-1
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven --with javahelper
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
Source: d-feet
Version: 0.3.11-3
Severity: serious
Tags: buster sid
Some recent change in unstable makes d-feet FTBFS:
https://tests.reproducible-builds.org/debian/history/d-feet.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/d-feet.html
...
/usr/bin/make check-TESTS
Hi,
Guido Günther (2017-06-28):
> Great. See new debdiff attached. I've also attached the diff with
> patches applied for the relevant part of the debian.xml.in
> (url-change.diff). For the sake of completeness: I've also changed
> debian/gbp.conf to point to debian/jessie so
Control: reassign -1 debhelper 10.5.1
Control: affects -1 src:libindicate
Works with debhelper 10.2.5, FTBFS with debhelper 10.5.1 and 10.6
On Thu, Jun 29, 2017 at 08:37:52AM -0700, Daniel Schepler wrote:
> Source: libindicate
> Version: 0.6.92-4
> Severity: serious
>
> >From my pbuilder build
Perhaps there should be a caution about filesystems with large numbers
of i-nodes. Notice the numbers provided are just under 330 bytes for
every i-node.
The current `restore` program no longer acts as the traditional 4.4BSD
`restore` did. Instead of restoring a near-exact image of the
Hi,
gregor herrmann (2017-06-28):
> On Wed, 28 Jun 2017 00:51:33 +0200, Cyril Brulebois wrote:
> > I haven't matched this to code changes at first glance. For the sake
> > of clarity: this relates to the Depends → Recommends update, because
> > code was added to
Nik,
At this point there are two blockers:
1. Update the package to the latest release of git-lfs (this should be easy)
2. Split out every go dependency that does not already exist in debian into its
own package. This is the part that has delayed me.
I am hoping to make some forward progress
Package: src:gpgme1.0
Version: 1.8.0-3
Severity: important
This package declares a build-depends on python3-all-dev, but does not build
using other the default python3 version. It it preferable to build for all
supported python3 versions. Alternately, changing the build-dep to
python3-dev would
Hi,
Yao Wei (2017-06-28):
> On Tue, Jun 27, 2017 at 10:59:24PM +0200, Cyril Brulebois wrote:
> > You're fixing this through jessie-pu (short for jessie-proposed-updates),
> > rather than via security; so please use “jessie” as the target codename.
>
> Sorry that the patch was
Hi,
This is my first post so I'll ask for your forbearance. I've read this bug
and experienced the issue with 9.0.0. I've now tried to use 9.0.1 and I am
experiencing similar issues.
However, instead of presenting the CD-ROM error initially, the installation
makes it passed CD-ROM check and then
Control: tag -1 confirmed
Gianfranco Costamagna (2017-06-27):
> >I'm interested in seeing an updated debdiff with a better wording for
> >the xhost issue. The proposed one suggests a syntax error but says
> >nothing about the permission issues which need a fix.
>
> ok,
Control: reopen -1
On Thu, Jun 29, 2017 at 03:24:06PM +, Debian Bug Tracking System wrote:
> Date: Thu, 29 Jun 2017 17:21:34 +0200
> From: Gianfranco Costamagna
> To: 865526-d...@bugs.debian.org
> Subject: Re: libpetsc3.7.5-dev: uninstallable on current sid
>
>
>
Package: wnpp
Severity: wishlist
Owner: Ying-Chun Liu (PaulLiu)
* Package name: node-callback-stream
Version : 1.1.0
Upstream Author : Matteo Collina
* URL : https://github.com/mcollina/callback-stream#readme
* License
Source: python-cryptography
Version: 1.9-1
Severity: serious
https://buildd.debian.org/status/package.php?p=python-cryptography=sid
...
I: pybuild base:184: python3.6 setup.py config
Traceback (most recent call last):
File "setup.py", line 321, in
**keywords_with_side_effects(sys.argv)
Source: translate-toolkit
Version: 2.0.0-1
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.6
Dear Maintainer,
The build fails in very strange ways when multiple Python 3 versions are
supported, e.g. if 3.5 is default and 3.6 is supported you get this when
running the
Source: assertj-core
Version: 2.3.0-3
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
Source: antlr3.2
Version: 3.2-14
Severity: serious
>From my pbuilder build log:
...
debian/rules build
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /build/antlr3.2-3.2/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar':
No such file
Control: tag -1 pending
Markus Koschany (2017-06-29):
> Uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
Raphael Hertzog (2017-06-29):
> Thanks, I updated the changelog in git and I uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
Cyril Brulebois (2017-06-28):
> This looks good to me (also tested locally without then with the patch
> series). Feel free to upload, targetting jessie; thanks.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Source: antlr3
Version: 3.5.2-6
Severity: serious
>From my pbuilder build log:
...
debian/rules build
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /build/antlr3-3.5.2/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar':
No such file
I am encountering the same issue. My configuration in /etc/defaults/opendkim
are ignored, and it’s not clear either if my configuration in
/etc/opendkim.conf is being read. Opendkim is not configurable!
For comparison, in Debian 8 the execute string in the /etc/init.d/opendkim file
reads:
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thank you; uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thanks, uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thank you; uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thank you; uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
Mike Gabriel (2017-06-28):
> the package has just been uploaded (by mfv@d.o).
Flagged for acceptance, thanks.
In hindsight, I should have asked for a more verbose changelog entry.
I've chosen to sum it up like this:
“use proper error handling
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thanks! Uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
Felipe Sateler (2017-06-29):
> Uploaded a couple days ago, I forgot to notify here though.
Thanks for mentioning it; it was on my radar already, just needed some
time to make sure everything was OK.
Flagged for acceptance, thanks.
KiBi.
Control: tag -1 pending
gregor herrmann (2017-06-28):
> Thank you! Uploaded.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Control: tag -1 pending
Aurelien Jarno (2017-06-28):
> Thanks for the review, I have just uploaded it.
Flagged for acceptance, thanks.
KiBi.
signature.asc
Description: Digital signature
Package: src:python-biomaj3
Version: 3.0.20-1
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it has no
arch:any Python3 content. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this
Package: src:python-biomaj3
Version: 3.0.20-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Now FTBFS. See attached log.
: pybuild base:184: python3.6 setup.py clean
Traceback (most recent call last):
File "setup.py", line 18, in
README
Source: libjavaewah-java
Version: 0.6.12-1
Severity: serious
>From my pbuilder build log:
...
debian/rules build
dh build --buildsystem=maven
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configure -O--buildsystem=maven
find:
I'm in the process of updating pycountry to the latest 17.5.14 release in
Ubuntu. I'll attach the diff to the debian directory I used.
diff -Nru pycountry-1.8+ds1/debian/changelog
pycountry-17.5.14+ds1/debian/changelog
--- pycountry-1.8+ds1/debian/changelog 2017-01-29 12:27:30.0 +1300
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "opencryptoki"
Package name: opencryptoki
Version : 3.7.0+dfsg-4
Upstream Author : none
URL : http://opencryptoki.sourceforge.net/
License : CPL
Section : admin
Joel Rosdahl (2017-06-29):
> Oh, right. I'm clearly confused on multiple levels here. (I erroneously
> referenced #829088 above instead of #835460, and I closed #835460
> prematurely. And I mixed up 3.1.12-1 with 3.1.12-2. This might or might not
> be related to my daughter being
On 2017-06-28 11:53, Graham Inggs wrote:
> I've just noticed that CUDA 8.0.61 is now available for download.
>
> I haven't looked at it yet, but will do when I get a chance.
Prepared in svn, packages build, but not tested at all :-)
Andreas
Package: src:xcffib
Version: 0.4.2-2
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it does not use
Python headers. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this as
important)
Package: src:xcffib
Version: 0.4.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
See attached build log
generator/Data/XCB/Python/Parse.hs:292:29: error:
* The constructor `Switch' should have 4 arguments, but has been given 3
* In the
I just uploaded the package to mentors
(https://mentors.debian.net/package/pragha)
This is the second version, because the first had a lintian warning
related the a duplicate changelog file. I fixed it by using the
options "--keep" from dh_installchangelogs.
In this second version, I also
I had the same problem when upgrading from jessie to stretch (systemd
232-25) with a Cinnamon desktop.
Opening a root terminal using "gksu /usr/bin/x-terminal-emulator" (as in
the menu) causes lots of dconf-CRITICAL error messages.
These vanish if I edit the menu item to "gksudo
Package: python3-astlib
Version: 0.9.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From
Package: pidgin-lastfm
Version: 0.4a-2
Severity: important
Tags: patch upstream
Dear Maintainer,
the plugin in question malfunctions because lastfm slightly changed
formatting of their xml responses. It can't figured out the song's artist
anymore.
How to reproduce: enable plugin, set some
Package: nuitka
Version: 0.5.26+ds-1
Severity: serious
Justification: Policy 3.5
Nuitka Recommends: python-qt5. This package doesn't exist. I think you meant
python-pyqt5.
Scott K
Package: src:django-restricted-resource
Version: 2016.8-1
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it has no
arch:any Python3 content. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm
Control: tag -1 - moreinfo + confirmed
gregor herrmann (2017-06-29):
> On Thu, 29 Jun 2017 09:11:43 +0200, Dominique Dumont wrote:
>
> > On Wednesday, 28 June 2017 20:15:01 CEST gregor herrmann wrote:
> > > I suppose yes, in order to make sure that the script waits for
> > >
Package: src:django-testscenarios
Version: 0.9-1.1
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it has no
arch:any Python3 content. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing
Control: tag -1 + patch
On Sun, 18 Jun 2017 23:13:09 +0300, Niko Tyni wrote:
> It looks like the underlying failure reason is that
> at least filter/tv_to_latex and filter/tv_to_text have
>
> use POSIX 'tmpnam';
>
> which was deprecated in Perl 5.24 and removed in 5.26. Unfortunately
> the
Strange, no additional symbols with gcc-7 (7.1.0)
Package: src:jpy
Version: 0.8-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Package FTBFS (just on mips) during binNMU that added python3.6 support:
https://buildd.debian.org/status/fetch.php?pkg=jpy=mips=0.8-5%2Bb1=1498778567=0
Scott K
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
cross-gcc-dev has to be in very close sync with the version of gcc in
order for it's patches to apply. The cross-gcc that made it into
stable was prepared against gcc-6 6.3.0-2
Control: tag -1 + patch
On Tue, 27 Jun 2017 11:49:51 +0100, Dominic Hargreaves wrote:
> Doing so now. Maintainers, the upstream issue at
>
> https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/issues/305
>
> has some useful suggestion about how to modernise Makefile.PL et al
> to resolve
Package: src:ust
Version: 2.9.0-2
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it does not use
Python3 header files. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this as
Package: src:django-hijack
Version: 2.0.7-2
Severity: important
Tags: patch
This package build-depends on python3 dev packages even though it has no
arch:any Python3 content. This is not needed and complicates transition
trackinig for us, the python maintainers, (which is why I'm filing this as
Package: sensord
Version: 1:3.3.5-2
Followup-For: Bug #865042
Hi,
Removing the whole package because one particular use-case has some problems
seems like a bit of an over-reaction, especially when that usage isn't even
mentioned in the package description and the required dependency is only a
On 2017-06-27 11:35, Luca Boccassi wrote:
>> Package: nvidia-legacy-304xx-driver
>> Does not build against current Sid 4.11 kernels, neither regular nor
> Thanks for the report. It's fixed in SVN, pending the next upload.
Uploaded.
Looks like we need a similar fix for 340xx. I forward ported
Control: tag -1 + patch
On Sun, 25 Jun 2017 21:13:02 +0300, Niko Tyni wrote:
> Just a note that while there was a very similar deprecation phase in Perl
> 5.22, this one is new with Perl 5.26. The earlier check was slightly
> buggy and failed to warn in some cases where it should have.
>
> So
On Fri, 12 May 2017 13:40:45 +1200 Michael Hudson-Doyle
wrote:
> Source: khmer
> Version: 2.0+dfsg-10
> Severity: normal
> Tags: patch
>
> Dear Maintainer,
>
> I've applied this patch to get the build working now that Python 3.6 is a
> supported version in Ubuntu. I
Control: tag -1 + patch
On Sat, 24 Jun 2017 20:35:08 +0200, gregor herrmann wrote:
> This is fatal in Perl 5.26 (currently in experimental), making the
> package fail to build from source. Raising the severity accordingly.
I'm attaching a patch to fix this issue.
Cheers,
gregor
--
.''`.
Package: src:python-dictobj
Version: 0.4-1
Severity: important
Tags: patch
This package build-depends on python3 dev packages and the binaries are
arch:any even though it has no arch:any content. This is not needed and
complicates transition trackinig for us, the python maintainers, (which is
Eduardo Moraes wrote...
> I am looking for a sponsor for my package "cid"
The packaging looks sane besides the maintainer scripts, more on that
below. However, the entire package scares me. It seems to fiddle a lot
with several config files that come from other packages (like
/etc/ntp.conf), it
Package: src:python-characteristic
Version: 14.3.0-1
Followup-For: Bug #799635
This is easy enough to fix and it's a nuisance for transition tracking.
Scott K
diff -Nru python-characteristic-14.3.0/debian/changelog python-characteristic-14.3.0/debian/changelog
---
Package: inkscape
Version: 0.92.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Inkscape fails to start with the following error message:
$ inkscape
inkscape: error while loading shared libraries: libgsl.so.0: cannot open shared
object file: No such file or
On Thu, 2017-06-29 at 17:45 +, Ximin Luo wrote:
> Ximin Luo:
> > [..]
> >
> > The segfault occurs on various commands at different frequencies and after
> > differing amounts of time (but all less than a few seconds). The stack
> > traces
> > are all different too. [..]
>
> With some help
On Wed, Jun 28, 2017 at 09:13:05PM +0200, Narcis Garcia wrote:
> >
> > If you are doing an install party, set up a proxy server. That really
> > really helps a lot.
> >
>
> Not only experts should be able to do an install party; some more people
> wants to share small knowledge and
Control: severity -1 important
Control: reassign -1 ifupdown
Am 29.06.2017 um 23:46 schrieb BERTRAND Joël:
> Package: systemd
> Version: 233-9
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I have seen for a long time several issues with systemd. All of
tag 826491 + pending
thanks
Some bugs in the libschedule-cron-perl package are closed in revision
fbadd89ba81cfadd96400c78b6f53c4fa699d072 in branch 'master' by gregor
herrmann
The full diff can be seen at
Am 29.06.2017 um 21:24 schrieb Fabian Greffrath:
> control: tags -1 +patch
>
> Am Donnerstag, den 29.06.2017, 12:04 +0100 schrieb James Cowgill:
>> It looks to me like the game loop has no sleeps or other waiting in
>> it.
>> It has probably always consumed 100% CPU.
>
> Good catch! I have
Le 29/06/2017 à 23:11, Michael Biebl a écrit :
> Picked the wrong line from git blame indeed, this is the correct one
>
> https://github.com/systemd/systemd/commit/5104943722
>
> It's been there since v230 so not a recent change.
Indeed. Looking at my dpkg log on my laptop, the problem started
On Thu, Jun 29, 2017 at 09:13:36PM +0200, Sebastian Ramacher wrote:
> 1.8.3-1 just got accepted. Could you please test if the issue persits with
> that
> version? If it's still there, we should take this upstream.
1.8.3-1 has same issue.
/* Steinar */
--
Homepage: https://www.sesse.net/
> This text is incorrect; KASLR and hibernation have been compatible
> since these changes in Linux 4.8:
[...]
That's great news, but, I'm afraid that's only partly true. As I wrote in
the initial message, my laptop, Lenovo Thinkpad x220i, is unable to wake
up from hibernation unless nokaslr was
tag 749876 + pending
thanks
Some bugs in the libschedule-cron-perl package are closed in revision
6d6d937a37b786f011d61a935a111254872980cd in branch 'master' by gregor
herrmann
The full diff can be seen at
Source: pyrad
Severity: normal
Dear Maintainer,
A new version of pyrad is avilable upstream (2.1)[1]. Please package it.
Thanks,
--Robbie
1: https://github.com/wichert/pyrad/releases/tag/2.1
-- System Information:
Debian Release: 9.0
APT prefers testing-debug
APT policy: (600,
Package: thunar
Version: 1.6.3-2
Severity: normal
Hello,
I recently purged a lot of packages from my system. Now, I am no longer
able to mount removable media in Thunar. They are no longer listed in
the Tree side pane.
I am pretty sure that this is because of a package that I uninstalled,
but
On Tue, 2017-06-13 at 12:59 +0200, Andreas Beckmann wrote:
> On 2017-06-10 13:55, Luca Boccassi wrote:
> > On Fri, 2017-06-09 at 18:33 +0200, Julien Aubin wrote:
> > > Okay thanks. If it were possible in that case to remove the non
> > > gnlvd
> > > it
> > > could be fine
> >
> > Nvidia itself
On Tue, 27 Jun 2017 19:42:51 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
Package: procps
Version: 2:3.3.12-3
Severity: minor
File: /usr/bin/top
It turns out that
$ top
prints trailing blanks all the way to the right edge of the screen.
The problem is gone in -b
1 - 100 of 313 matches
Mail list logo