Possibly a help2man https://bugs.debian.org/787444 version below
1.47.1 is used on the build server and help2man doesn't support
SOURCE_DATE_EPOCH before this date. (See:
https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal). I'm not
familiar with the debian automated build
On 2015-08-08 22:36, Stefan Fritsch wrote:
Do you know if there is any practical difference between conflicts and
breaks+replaces in this case?
I don't think so. All dependencies on apache-2.2-common should be gone
by now, so removal of that package could happen anytime without
influencing any
On Saturday 08 August 2015 11:38:14, Andreas Beckmann wrote:
during a test with piuparts I noticed your package failed the
piuparts upgrade test because dpkg detected a conffile as being
modified and then prompted the user for an action. As there is no
user input, this fails. But this is not
On Saturday 08 August 2015 09:34:52, Andreas Beckmann wrote:
With apache2.2-common being gone this should be rather easy.
IIRC these conffiles were taken over by the apache2 package, so
all that should be needed are unversioned
Breaks+Replaces: apache2.2-common
in the apache2
Package: lvm2
Version: 2.02.111-2.2
Severity: normal
Dear Maintainer,
During every boot time after a fresh installation of debian jessie, I get
following errors after grub screen passes:
Volume group ert-debian-vg not found.
Skipping volume group ert-debian-vg
Unable to find LVM volume
Package: gksu
Version: 2.0.2-9
Severity: important
After upgrading to Jessie sometimes Gnome got unusable as
/run/user/1000/steink/dconf was suddenly owned by root and not writeable by
steink (Gnome hangs, /var/log/messages grew to some GB etc.).
According to
On 2015-08-08 22:34, Stefan Fritsch wrote:
On Saturday 08 August 2015 11:38:14, Andreas Beckmann wrote:
This was observed while doing a wheezy - jessie - stretch upgrade
test. I did not see such behavior while testing the other apache
packages.
This now shows up on all (or at least a lot of)
Package:steam
Version:1.0.0.50
Severity:important
Dear Maintainer,
When I launch steam, the application say bash: steam : commande
introuvable.
I do an apt-get remove steam, an apt-purge steam and delete the
./steam folder in my home folder before re-installing steam.
$ dpkg --status
Package: linux-image-3.16
Version: 3.16.7
Upgrading to Jessie (kernel 3.16) lost my display. Early in the boot
process, (when the resolution changes) no further output occurs. The
boot process is successful in that I can access via ssh.
Reverting to kernel 3.2 avoids the problem. An
Hi Debian Release Team,
TLTR:
Virtualbox suffers of many security issues in Debian,
specially because Upstream (Oracle) refuses to give
patches for CVEs, and (you can see in the Debian bug
794466 an analysis of the Oracle policy and discussion)
this makes difficult to handle security uploads
Hi,
On 2015-07-01 21:08, Vincent Lefevre wrote:
Package: sensord
Version: 1:3.3.5-2
Severity: grave
Justification: causes non-serious data loss
It seems that sensord uses an inconsistent set of data for its
RRD update, yielding data loss. rrd update no longer updates
the sensord.rrd
Package: mixxx
Version: 1.11.0~dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
Tags: patch
A binNMU of mixxx failed to build from source prior to the transition
from
Hi Frank and Release Team,
Oracle at this moment maintains a 4.0.x 4.1.x 4.2.x 4.3.x 5.0.x
branches where security fixes seems to be addressed all.
(virtualbox-ose from o-o-s still needs some pinpoint fixes)
virtualbox-ose is at version 3.2.10, and the last release from [1]
is 3.2.28, and
Control: severity -1 wishlist
On 08/08/2015 09:25 PM, Thorsten Glaser wrote:
Source: gettext
Version: 0.19.5.1-1
Severity: grave
Justification: renders package unusable
I just noticed we already have libasprintf0v5 in Debian/m68k unstable.
This cannot be, because we haven’t started the
On Sat, Aug 08, 2015 at 09:23:31PM +, Gianfranco Costamagna wrote:
Virtualbox suffers of many security issues in Debian,
specially because Upstream (Oracle) refuses to give
patches for CVEs, and (you can see in the Debian bug
794466 an analysis of the Oracle policy and discussion)
this
Package: nagios3-cgi
Version: 3.5.1.dfsg-2+b1
Severity: wishlist
The main nagios webpage
/usr/share/nagios3/htdocs/index.php
loads
/usr/share/nagios3/htdocs/main.php
which cotains some javascript that loads
/usr/share/nagios3/htdocs/rss-feed.php
/usr/share/nagios3/htdocs/rss-newsfeed.php
Carsten Hey wrote:
[...]
* Please add some additional keybindings, at least for the emacs keymap:
- bind PageUp ${terminfo[kpp]} to history-search-backward
- bind PageDown ${terminfo[knp]} to history-search-forward
- bind BackTabKey ${terminfo[kcbt]} to reverse-menu-complete
I
Hi Debian Security Team,
(Dear Jonathan, thanks for the heads-up, I tried to avoid cross-posting,
and I thought release was a better place then security, so dropping
-release from the mail cc, let me know if I have to readd it)
I would like to ask you whether is possible to have an exception
Matthias Klose dixit:
the package maintainers. Halt the buildds and re-enable them once you have
updated your buildds.
Erm. This is so wrong on several counts.
• What builds gcc-5 if not the buildds?
• There *will* be people later who build packages for other,
e.g. new (think arm64)
Carsten Hey wrote:
Please clear console on logout if the recommended config for new users
is used.
I think this should be doable with a zshexit hook like this:
function debian_clear_upon_exit () {
clear
}
add-zsh-hook zshexit debian_clear_upon_exit
That hook could be
Hello Gianfranco and thank you for your review,
1) d/changelog: please update the changelog to point to unstable suite
(maybe also refresh the timestamp)
Ok.
2) d/changelog might benefit of a \n in the first comment line
(after a full stop it is good to go in a new line)
Ok.
3)
Package: dselect
Version: 1.18.2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since a short time (not sure, since when), dselect refuses to work with
the error mentioned in the subject. Even if I start it to choose an
access method, this error is given.
A downgrade of dpkg
Package: python-cobra
Severity: normal
Control: block -1 by 794511
Packaging of 0.4.0b2 is delayed until cython again becomes installable
in unstable.
--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
On Sat, Aug 08, 2015 at 09:45:33PM +, Thorsten Glaser wrote:
I would like to hear from either of you two how we can fixup the
situation for m68k in the meantime.
In the meantime there is nothing to fix because there is not a *single*
package in debian linked against this library.
This is
Package: gnome-software
Version: 3.16.5-2
Severity: important
gnome-software uses the PackageKit (D-Bus) API, so we should probably
add a dependency on the packagekit package.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200,
On Sat, Aug 08, 2015 at 09:45:33PM +, Thorsten Glaser wrote:
including ports that don’t yet exist.
Hmm. I don't think we should really worry about that case.
Ports that do not even exist yet will definitely need a working gcc-5
if they ever expect to be released architectures some day.
So
Santiago Vila dixit:
In the meantime there is nothing to fix because there is not a *single*
package in debian linked against this library.
Ah, okay then.
Then I agree with the severity downgrade, too.
(Still… building GCC takes about a week, so we could not have
been earlier. Plus it’s about
Hi,
On 2015-08-08 23:30:26 +0200, Aurelien Jarno wrote:
From what I have been able to get the problem is that when using a
single rrd file for all data, the number of columns (ie sensors) is
defined when the file is created. Therefore the upgrade of your kernel
changed the number of sensors,
control: tag -1 moreinfo, unreproducible, -security
control: severity -1 important
On Fri, Aug 7, 2015 at 7:08 PM, reinhard wrote:
Package: bind9-host
Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u4
Severity: serious
File: bind9
Tags: security
Justification: fails to build from source (but built
Hi Antti,
Not changed yet, but inquiry sent to
http://lists.alioth.debian.org/cgi-bin/mailman/private/pkg-qemu-devel/2015-August/006604.html
so if they have good suggestions, then one more upload to mentors
will be needed.
I can't/won't read, but ok, it is good as-is, let me know if you
Santiago Vila dixit:
In the meantime there is nothing to fix because there is not a *single*
package in debian linked against this library.
… wait, what? Why is the package then installed on all systems, even
in the supposedly clean and minimal buildd chroot?
bye,
//mirabilos
--
Why don't you
Package: wnpp
Version: N/A; reported 2015-08-08
Severity: wishlist
* Package name : python-gssapi, python3-gssapi
Version : 1.1.2
Upstream Author : The Python GSSAPI Team
* URL : https://github.com/pythongssapi/python-gssapi/
* License : ISC
Package: rkhunter
Version: 1.4.2-3
Followup-For: Bug #791486
It's not actually the version check, it is how the verison is extracted
by the program. Looking in the logs:
[08:06:10] Info: This version : Binary file /var/lib/rkhunter/db/i18n/zh
matches
control: tag -1 moreinfo, unreproducible
This isn't enough information to debug the problem. Please attach
your ~/.steam/error.log file.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Santiago Vila dixit:
Ports that do not even exist yet will definitely need a working gcc-5
if they ever expect to be released architectures some day.
So the natural thing to do (which I think it is what we have always done,
but I may be wrong) is to use unstable as their starting point, not
Hi Helmut,
On Fri, 31 Jul 2015 at 07:46:26 +0200, Helmut Grohne wrote:
That was quick. Let me answer some of your comments already. I intend
to take another stab at the upload when I find more time, but that
shall not prevent other interested sponsors from uploading it earlier.
Possibly
On Sat, Aug 08, 2015 at 10:21:23PM +, Thorsten Glaser wrote:
Santiago Vila dixit:
In the meantime there is nothing to fix because there is not a *single*
package in debian linked against this library.
… wait, what? Why is the package then installed on all systems, even
in the
control: tag -1 unreproducible, moreinfo
control: severity -1 minor
The current release crashes regularly. For example the following link
reproducibly crashes the browser:
ftp://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/libudev-udev-monitor.html
I'm not able to reproduce this with
* Frank Terbeck [2015-08-08 23:51 +0200]:
Carsten Hey wrote:
Please clear console on logout if the recommended config for new users
is used.
I think this should be doable with a zshexit hook like this:
function debian_clear_upon_exit () {
clear
}
add-zsh-hook
Santiago Vila dixit:
The library was included in gettext-base but it was splitted to its
own package in version 0.18.1.1-6 and a compatibility dependency was
added.
Ah.
We could drop this dependency for stretch, yes, but even in such case
OK.
I don't have an answer for that, but for very slow
Hi!
On Sat, 2015-08-08 at 23:52:38 +0200, Daniel Leidert wrote:
Package: dselect
Version: 1.18.2
Severity: normal
Since a short time (not sure, since when), dselect refuses to work with
the error mentioned in the subject. Even if I start it to choose an
access method, this error is given.
Package: libnet-xmpp-perl
Version: 1.02-4
Severity: wishlist
Dear Maintainer,
after spending literally hours trying to provide a reproducer for
#794963 but all I got was the dreaded ...
| No SASL mechanism found
| at /usr/share/perl5/Authen/SASL.pm line 77.
| at /usr/share/perl5/XML/Stream.pm
Control: reassign -1 samba-common-bin
Control: found -1 2:4.1.17+dfsg-2
On Sat, 06 Jun 2015 14:55:21 +1000 Jason Lingohr ja...@lucid.net.au wrote:
Package: realmd
Version: 0.15.1-1+b2
Severity: important
Dear Maintainer,
Hi, fresh install of jessie. Installed realmd and get:
* Frank Terbeck [2015-08-08 23:46 +0200]:
Carsten Hey wrote:
[...]
* Please add some additional keybindings, at least for the emacs keymap:
- bind PageUp ${terminfo[kpp]} to history-search-backward
- bind PageDown ${terminfo[knp]} to history-search-forward
- bind BackTabKey
Package: alarm-clock
Version: 1.2.5-1.2
Severity: important
Play sound during event is ticked (this is the default), and when
there's an alarm, a Stop the sound button appears, but no sound
is played (ogg123 shows that the sound is working on the machine).
-- System Information:
Debian Release:
* Frank Terbeck [2015-08-08 23:46 +0200]:
Carsten Hey wrote:
[...]
- Maybe F1 could invoke run-help? But then the output of run-help
w/o arguments should be more useful for new users.
- Red Hat maps or mapped space to magic-space, I think Debian should
_not_ do this,
Hi,
This package is apparently not installable on sid now.
1. libcegui-mk2-0.7.6 requires libogre-1.8.0
2. libstdc++6 Breaks libogre-1.8.0 = 1.8.0+dfsg1-7+b1
Updating libogre-1.8.0 is apparently a wontfix:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791222
Can you please prepare a new
tag 794937 moreinfo
thanks
Hi Michael! I have just uploaded a new version, can you check it works for
you? (and yes, you might need to wait for the gcc5 transition to be in a more
advanced state :-/ )
Kinds regards, Lisandro.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
Package: vlc
Version: 2.2.1-2+b2
Architecture: i386
Severity: minor
Somehow (it may have been a transient error caused by C++ ABI upgrades),
I ended up with:
$ ls ~/.config/vlc/
vlc-qt-interface.conf
vlc-qt-interface.conf.lock
vlc-qt-interface.conf.lock.rmlock
Package: gitk
Version: 1:2.5.0+next.20150727-1
Severity: normal
On a high-DPI display, with Xft.dpi set to a large value, gitk scales up
some but not all of its fonts. For instance, the menus and content
fonts seem to be scaled up, but the UI font for Find ... commit
containing and the fonts in
Source: celestia
Severity: normal
On a high-DPI display, with Xft.dpi set to a large value, the fonts used
in the rendering window don't scale up, making them unreadably small.
Please scale the rendering fonts up proportionally to the DPI.
Thanks,
Josh Triplett
-- System Information:
Debian
Package: stellarium
Version: 0.13.3-2
Severity: normal
On a high-DPI display, with Xft.dpi set to a large value, stellarium
does not scale up the fonts in its rendering window to match, making
them unreadably small. Please scale these fonts up based on Xft.dpi.
Thanks,
Josh Triplett
-- System
Hi.
I also confim I get this error. It seems to happen in both Debian Testing, and
Ubuntu Vivid chroots on Kernel 3.19
I get these errors
libtool: install: /usr/bin/install -c .libs/libwayland-server.a
/opt/lib/i386-linux-gnu/libwayland-server.a
libtool: install: chmod 644
Package: mercurial-git
Version: 0.8.1-2
Severity: important
In a repository using hg-git:
$ hg status
*** failed to import extension hgext.git: No module named ignore
** unknown exception encountered, please report by visiting
** http://mercurial.selenic.com/wiki/BugTracker
** Python 2.7.10
This problem still occurs with the 24.5+1-1 package currently in
unstable. Trying to build it on Ubuntu Trusty, I get:
debian/patch-to-news: line 9:
0001-Prefer-usr-share-info-emacs-24-over-usr-share-info.patch: No such
file or directory
debian/patch-to-news: line 9:
Package: node-htmlparser2
Version: 3.7.3-1
Severity: important
Dear Maintainer,
I tried the example in the htmlparser2 readme, and it throws an
error while trying to load the module:
$ cat test.js
var htmlparser = require(htmlparser2);
var parser = new
Hi,
Really sorry for the noise - ERRNOCOFFEE - I had a typo in the key file
names. Once again, sorry.
Celejar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
You are right, Johannes.
I changed the flag name without notice it.
With the change done by Maria (#783475) now we can remove the
--build-date flag (i hope)
Also, now the reproducible build fails due the date in copied files,
(dist_images_DATA in Makefile.am, etc).
Please, give me some days to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu xsdcxx_4.0.0-1 . ALL . unstable . -m Rebuild for new libstdc++6
This is happening because of the libstdc++6 transition.
Technically this is only happening because libstdc++6 declared a
Hi!
On Sat, 2015-08-08 at 10:13:50 +0200, Sven Joachim wrote:
On 2015-08-06 04:16 +0200, Guillem Jover wrote:
Control: tag 794688 pending
Bug #794688 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
Source: mrpt
Version: 1:1.2.2-1.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
This package fails to build with the new libstdc++ ABI (with updated
libassimp3, #794835).
The error has
Package: libsixel
Version: 1.4.2-1
New upstream v1.4.13 is available which includes many bug fixes.
Please package it.
Thanks,
--
Tatsuya Kinoshita
pgp3aNSQJqvAY.pgp
Description: PGP signature
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
The python-sqlalchemy transition was all set to finish today when the
maintainer (zigo) uploaded neutron-vpnaas and so set the whole thing back
by five days (at least, who knows what else he
control: tag -1 patch
Hi,
Here is a trivial patch. Updating the symbols file is a better
solution since neither of the reverse dependencies rely on the changed
symbols. I've tested that doomsday builds fine after this patch.
mrpt does fail to build with g++ 5 (I've submitted bug #794990 about
Package: src:snappy
Version: 1.1.3-1
Severity: serious
Tags: sid stretch patch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11
Control: block 794931 with -1
The short note.
Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not
201 - 265 of 265 matches
Mail list logo
