Bug#819890: haskell-http2: FTBFS on armel buildds (was: Re: Please give back haskell-http2 on armel)
On Sun, Apr 03, 2016 at 03:11:39PM +0100, Steven Chamberlain wrote: > Wookey wrote: > > +++ Steven Chamberlain [2016-04-01 10:31 +0100]: > > > Currently haskell-http2 FTBFS on only armel: > > > https://buildd.debian.org/status/package.php?p=haskell-http2=unstable > > > delaying the package's testing migration and keeping many reverse-deps > > > BD-Uninstallable on armel. > > > > > > More recently than that it has successfully built: > > > https://tests.reproducible-builds.org/rbuild/unstable/armhf/haskell-http2_1.5.3-2.rbuild.log > > > > > > Therefore, please could it be given back for another build attempt? > > > > > > gb haskell-http2_1.5.3-2 . armel > > > > Seems a reasonable request. > > done > Thanks; it didn't work though. Please could arm porters take a look? > The reproducible-builds log shows the test suite passing, whereas on the > buildds one test failed, on both build attempts. The reproducible-builds is armhf while the failing ones are armel. The regression appears to be a code change in haskell-http2 between 1.0.4 and 1.3.1: https://buildd.debian.org/status/logs.php?pkg=haskell-http2=armel Riku
Bug#815196: ITP: awlsim -- S7 compatible soft-PLC
On Sun, 3 Apr 2016 22:58:12 +0200 Geert Stapperswrote: > After a `git clone`, > I did `dpkg-checkbuilddeps && dpkg-buildpackage -uc -us` and got > > > running build_scripts >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:184: cd > /home/stappers/src/awlsim/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest > discover -v > > -- > Ran 0 tests in 0.000s > > OK > I: pybuild base:184: cd > /home/stappers/src/awlsim/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest > discover -v > awlsim-gui ERROR: Neither PySide nor PyQt found. > PLEASE INSTALL PySide (http://www.pyside.org/) > or PyQt4 with v2 APIs > (http://www.riverbankcomputing.com/software/pyqt/download) > or PyQt5 with v2 APIs > (http://www.riverbankcomputing.com/software/pyqt/download5) > Press enter to exit. > > > What to do to get a "clean build"? > > If I should have build from a .tar.gz ( not from git ), please tell. Using the git tree is fine. pybuild seems to pull in the gui libraries at build time. Funny thing is that it only seems to do this on Python 3. So we probably have to add pyside or pyqt for Python 3 to the build deps. If you install python3-pyside it should build. -- Michael pgpBdb3yAURco.pgp Description: OpenPGP digital signature
Bug#798032: libpgf: diff for NMU version 6.14.12-3.2
Control: tags 798032 + patch Control: tags 798032 + pending Dear maintainer, I've prepared an NMU for libpgf (versioned as 6.14.12-3.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru libpgf-6.14.12/debian/changelog libpgf-6.14.12/debian/changelog --- libpgf-6.14.12/debian/changelog 2015-10-20 04:09:35.0 -0500 +++ libpgf-6.14.12/debian/changelog 2016-04-03 21:58:47.0 -0500 @@ -1,3 +1,12 @@ +libpgf (6.14.12-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * Apply upstream changes 147 & 148 to fix CVE-2015-6673 (Closes: +#798032). New patches 02-fix-CVE-2015-6673-upstream-147.patch and +03-fix-CVE-2015-6673-upstream-148.patch. + + -- Steve M. RobbinsSun, 03 Apr 2016 21:58:47 -0500 + libpgf (6.14.12-3.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libpgf-6.14.12/debian/patches/02-fix-CVE-2015-6673-upstream-147.patch libpgf-6.14.12/debian/patches/02-fix-CVE-2015-6673-upstream-147.patch --- libpgf-6.14.12/debian/patches/02-fix-CVE-2015-6673-upstream-147.patch 1969-12-31 18:00:00.0 -0600 +++ libpgf-6.14.12/debian/patches/02-fix-CVE-2015-6673-upstream-147.patch 2016-04-03 18:45:29.0 -0500 @@ -0,0 +1,97 @@ +--- libpgf-6.14.12.orig/include/PGFimage.h libpgf-6.14.12/include/PGFimage.h +@@ -538,7 +538,7 @@ + ProgressMode m_progressMode; ///< progress mode used in Read and Write; PM_Relative is default mode + + void ComputeLevels(); +- void CompleteHeader(); ++ bool CompleteHeader(); + void RgbToYuv(int pitch, UINT8* rgbBuff, BYTE bpp, int channelMap[], CallbackPtr cb, void *data) THROW_; + void Downsample(int nChannel); + UINT32 UpdatePostHeaderSize() THROW_; +--- libpgf-6.14.12.orig/src/PGFimage.cpp libpgf-6.14.12/src/PGFimage.cpp +@@ -145,7 +145,7 @@ + m_height[0] = m_header.height; + + // complete header +- CompleteHeader(); ++ if (!CompleteHeader()) ReturnWithError(FormatCannotRead); + + // interpret quant parameter + if (m_header.quality > DownsampleThreshold && +@@ -205,7 +205,7 @@ + } + + +-void CPGFImage::CompleteHeader() { ++bool CPGFImage::CompleteHeader() { + if (m_header.mode == ImageModeUnknown) { + // undefined mode + switch(m_header.bpp) { +@@ -261,20 +261,21 @@ + // change mode + m_header.mode = ImageModeRGBA; + } +- ASSERT(m_header.mode != ImageModeBitmap || m_header.bpp == 1); +- ASSERT(m_header.mode != ImageModeIndexedColor || m_header.bpp == 8); +- ASSERT(m_header.mode != ImageModeGrayScale || m_header.bpp == 8); +- ASSERT(m_header.mode != ImageModeGray16 || m_header.bpp == 16); +- ASSERT(m_header.mode != ImageModeGray32 || m_header.bpp == 32); +- ASSERT(m_header.mode != ImageModeRGBColor || m_header.bpp == 24); +- ASSERT(m_header.mode != ImageModeRGBA || m_header.bpp == 32); +- ASSERT(m_header.mode != ImageModeRGB12 || m_header.bpp == 12); +- ASSERT(m_header.mode != ImageModeRGB16 || m_header.bpp == 16); +- ASSERT(m_header.mode != ImageModeRGB48 || m_header.bpp == 48); +- ASSERT(m_header.mode != ImageModeLabColor || m_header.bpp == 24); +- ASSERT(m_header.mode != ImageModeLab48 || m_header.bpp == 48); +- ASSERT(m_header.mode != ImageModeCMYKColor || m_header.bpp == 32); +- ASSERT(m_header.mode != ImageModeCMYK64 || m_header.bpp == 64); ++ ++ if (m_header.mode == ImageModeBitmap && m_header.bpp != 1) return false; ++ if (m_header.mode == ImageModeIndexedColor && m_header.bpp != 8) return false; ++ if (m_header.mode == ImageModeGrayScale && m_header.bpp != 8) return false; ++ if (m_header.mode == ImageModeGray16 && m_header.bpp != 16) return false; ++ if (m_header.mode == ImageModeGray32 && m_header.bpp != 32) return false; ++ if (m_header.mode == ImageModeRGBColor && m_header.bpp != 24) return false; ++ if (m_header.mode == ImageModeRGBA && m_header.bpp != 32) return false; ++ if (m_header.mode == ImageModeRGB12 && m_header.bpp != 12) return false; ++ if (m_header.mode == ImageModeRGB16 && m_header.bpp != 16) return false; ++ if (m_header.mode == ImageModeRGB48 && m_header.bpp != 48) return false; ++ if (m_header.mode == ImageModeLabColor && m_header.bpp != 24) return false; ++ if (m_header.mode == ImageModeLab48 && m_header.bpp != 48) return false; ++ if (m_header.mode == ImageModeCMYKColor && m_header.bpp != 32) return false; ++ if (m_header.mode == ImageModeCMYK64 && m_header.bpp != 64) return false; + + // set number of channels + if (!m_header.channels) { +@@ -300,8 +301,7 @@ + m_header.channels = 4; + break; + default: +- ASSERT(false); +- m_header.channels = 3; ++ return false; + } + } + +@@ -311,6 +311,8 @@ + if (!m_header.usedBitsPerChannel || m_header.usedBitsPerChannel > bpc) { + m_header.usedBitsPerChannel = bpc; + } ++ ++ return true; + } + + // +--- libpgf-6.14.12.orig/src/Decoder.cpp libpgf-6.14.12/src/Decoder.cpp +@@ -158,7
Bug#818023: is orphaning of libindicator (#818023) right?
Hy Adam, feel free to do whatever feels best (incl RoQA if needed). Thanks! Evgeni On April 4, 2016 5:20:33 AM GMT+02:00, Kartik Mistrywrote: >On Mon, Apr 4, 2016 at 8:34 AM, Adam Borowski >wrote: >> I was about to make a QA upload of libindicator fixing a RC bug >(#806470), >> however, when setting the maintainer to the QA team I noticed that >both of >> the listed uploaders seem active: > >Go ahead from me. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Bug#819944: [patch] Backport firejail to Jessie
Package: firejail Version: 0.9.38-1 Severity: wishlist Tags: patch Hi. I just tried to backport firejail to Jessie, and had to apply the following patch as the SYS_* macros were defined to __NR_*, but these __NR_* macros were undefined in the 3.16.7 kernel header packages. Do you have any plans to provide firejail in the Debian backports repo? Index: firejail-0.9.38/src/firejail/seccomp.c === --- firejail-0.9.38.orig/src/firejail/seccomp.c 2016-04-04 06:52:35.0 +0200 +++ firejail-0.9.38/src/firejail/seccomp.c 2016-04-04 07:11:24.785468992 +0200 @@ -420,7 +428,7 @@ #ifdef SYS_init_module filter_add_blacklist(SYS_init_module, 0); #endif -#ifdef SYS_finit_module // introduced in 2013 +#ifdef __NR_finit_module // introduced in 2013 filter_add_blacklist(SYS_finit_module, 0); #endif #ifdef SYS_delete_module @@ -478,7 +486,7 @@ #ifdef SYS_fanotify_init filter_add_blacklist(SYS_fanotify_init, 0); #endif -#ifdef SYS_kcmp +#ifdef __NR_kcmp filter_add_blacklist(SYS_kcmp, 0); #endif -- Happy hacking Petter Reinholdtsen
Bug#658988: ITP: libvirt-sandbox -- API layer which facilitates the creation of application
Btw, I mentioned libvirt-sandbox on #freedombox, and was tipped about firejail, which seem to do a similar task. Are you aware of firejail? Do you know how libvirt-sandbox is different from firejail? Firejail is in unstable and testing already, and was possible to backport with a hack to add some missing kernel call constants. -- Happy hacking Petter Reinholdtsen
Bug#818023: is orphaning of libindicator (#818023) right?
On Mon, Apr 4, 2016 at 8:34 AM, Adam Borowskiwrote: > I was about to make a QA upload of libindicator fixing a RC bug (#806470), > however, when setting the maintainer to the QA team I noticed that both of > the listed uploaders seem active: Go ahead from me. -- Kartik Mistry | IRC: kart_ {0x1f1f, kartikm}.wordpress.com
Bug#818023: is orphaning of libindicator (#818023) right?
Hi! I was about to make a QA upload of libindicator fixing a RC bug (#806470), however, when setting the maintainer to the QA team I noticed that both of the listed uploaders seem active: [~]$ ssh qa.debian.org /srv/qa.debian.org/mia/mia-query evg...@debian.org [...] activity-pgp:[Sun, 03 Apr 2016 16:08:00] [~]$ ssh qa.debian.org /srv/qa.debian.org/mia/mia-query kar...@debian.org [...] activity-pgp:[Mon, 28 Mar 2016 09:50:08] Of course, letting an unanswered FTBFS since November isn't exactly nice, but a more proper action might be pinging or a NMU. Thus, should I complete the orphaning (#818023), disregard it and do a NMU, or let you guys upload on your own? Meow! -- A tit a day keeps the vet away.
Bug#806470: patch
Control: tags -1 +patch --- libindicator-0.5.0.orig/configure.ac +++ libindicator-0.5.0/configure.ac @@ -66,7 +66,7 @@ AS_IF([test "x$with_gtk" = x3], AM_CONDITIONAL(USE_GTK3, [test "x$with_gtk" = x3]) LT_LIB_M -LIBINDICATOR_LIBS+="$LIBM" +LIBINDICATOR_LIBS+=" $LIBM" ## # Custom Junk -- A tit a day keeps the vet away.
Bug#776309: fglrx-driver: Hung PC with black screen and solid white cursor in upper left corner
> Please try again with the 15.12 driver that is now available in > unstable, testing, and jessie-backports. This bug had occurred on my testing/sid machine during a large upgrade. At that point, the Xorg dependencies on my system were in such a state that apt-get successfully installed fglrx-driver despite the xserver-xorg-core version being >=1.18. As noted in bug #811031, the Catalyst drivers do not support that xserver release. For my machine, this bug was merely the effect of unintentionally installing the Catalyst drivers onto a non-supported xserver version. My apologies. Maybe this bug should be closed as irrelevant or marked as directly related to #811031. Thanks!
Bug#819943: really should add an unforbid-version command
Package: aptitude Version: 0.7.8-1 Today I will inspect the how hard it is to just simple reverse the action of # aptitude forbid-version somepackage so we are back to the state before we did it. The man page says To revert the action, "aptitude install " will remove the ban. To remove the forbidden version without installing the candidate version, the current version should be appended: "install =". Well I think you really should an unforbid-version command. With no = then it should clear the forbidden version of that package(s). Also the man page should say if only one version can be forbidden or more. Also one thinks I could just use forbid-version=0 to clear it, but that is not a current version of that package. And # aptitude forbid-version package1 package2 package3 ... package20 will require an enormous amount of work to reverse, digging up each version number... OK, let's try # aptitude install xserver-xorg-video-cirrus=1:1.5.3-1+b1 We will very likely encounter some "The following actions will resolve these dependencies: Remove the following packages:" questions which we will very probably answer "n", never reaching the point where supposedly the forbid-version will be erased without installing the package before quitting! And, when you think about it # aptitude install xserver-xorg-video-cirrus= means the same as # aptitude install xserver-xorg-video-cirrus so if one didn't want to install the package one would answer "n" when asked so never reaching the step where ... anyway one big no-op and the forbid-version stays.
Bug#819942: command line mode war against TERM=dumb
Package: aptitude Version: 0.7.8-1 I am using a emacs shell-mode window. # aptitude install xserver-xorg-video-cirrus=1:1.5.3-1+b1 aptitude cannot run in ncurses mode with terminal type "dumb" So must use: # TERM=linux aptitude install xserver-xorg-video-cirrus=1:1.5.3-1+b1 # TERM= aptitude install xserver-xorg-video-cirrus=1:1.5.3-1+b1 # unset TERM; aptitude install xserver-xorg-video-cirrus=1:1.5.3-1+b1 You don't allow TERM=dumb (bug) but allow no TERM at all (fine). $ TERM= aptitude Error opening terminal: unknown. That is fine. But that is ncurses mode, and what I was doing wasn't.
Bug#819854: [Letsencrypt-devel] Bug#819854: wouldn't Recommends: be better?
On 2016, ഏപ്രിൽ 4 3:55:41 AM IST, Axel Beckertwrote: >> > we can make letsencrypt optional. > >Huh? Now that's a strange request. How is it strange? How is it not different from dbconfig-no-thanks? To me it solves the same problem. dbconfig does database configuration, and letsencrypt does ssl configuration. If you don't want it, just install dbconfig-no-thanks or letsencrypt-no-thanks. If it is just in Recommends, you have to disable recommends for each package that uses letsencrypt. And if you disable recommends for whole system, you lose out on this. I want this as depends but allow people to opt out. dbconfig-no-thanks was a perfect solution and strongly feel, letsencrypt fits the same role. >> I guess you should change Depends: to Recommends: then. > >Definitely. > >Hence reassigning. This is already done in gitlab. If you don't think this is a good idea, you may close this bug.
Bug#598730:
The file /etc/skel/.profile still states that "the default umask is set in /etc/profile". However, the comment in /etc/profile stating that "the default umask is now handled by pam_umask" appears to have been removed, making the comment in the skel file even more confusing. Setting the umask in /etc/profile has no effect.
Bug#819941: gitolite3: Git-annex-shell not working
Package: gitolite3 Version: 3.6.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, on the current stable version (jessie) git-annex is not working due to a bug already fixed on the upstream version 3.6.3 Please, in order to let git-annex works with gitolite, valuate the option to fix it on current branch. PATCH: https://github.com/sitaramc/gitolite/commit/276cf761de0522a19b0312f4466fc497a2a38b5f -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (910, 'stable-updates'), (910, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#819940: dpkg: [INTL:ja] Japanese translation of po file update
Package: dpkg Version: 1.17.26 Severity: wishlist Tags: l10n patch Dear Maintainer, Here's Japanese translation of po (ja.po) file that reviewed by several Japanese Debian developers and users. Please copy the attachment into dselect/po/ja.po. Kind regards. -- Takuma Yamada -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-18+deb8u3 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libselinux1 2.3-2 ii tar 1.27.1-2+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.8.2 -- no debconf information ja.po.gz Description: application/gzip
Bug#819939: dpkg: [INTL:ja] Japanese translation of po file update
Package: dpkg Version: 1.17.26 Severity: wishlist Tags: l10n patch Dear Maintainer, Here's Japanese translation of po (ja.po) file that reviewed by several Japanese Debian developers and users. Please copy the attachment into po/ja.po. Kind regards. -- Takuma Yamada -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-18+deb8u3 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libselinux1 2.3-2 ii tar 1.27.1-2+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.8.2 -- no debconf information ja.po.gz Description: application/gzip
Bug#764541: gsm3: When changing user, the sound is not stopped
tag 764541 + moreinfo thanks On Thu, 09 Oct 2014 00:12:07 +0200 Thibautwrote: Hi, > If a sound is playing on the speaker when a user switch its session to an other > user, the sound is still playing. > When a user as started playing a sound (for example through a youtube video > playing on iceweasel), a user on an other session will not be able to play a > sound. In the sound option menu, the speakers are not visible. Only the > internal audio is accessible. > > To play a sound on the speakers, it is needed to switch back to the first user > that played a sound and close the software (for youtube, closing the tab is > enough). > Can you still reproduce this bug? Just tried again with a mix of debian unstable and experimental and the sound is stopped when switching to an other VT. Cheers, Laurent Bigonville
Bug#816847: ITP: dislocker -- read/write encrypted BitLocker volume
Hi Marco, On 05-03-2016 14:58, Marco d'Itri wrote: > On Mar 05, Giovani Augusto Ferreirawrote: > >> The driver used to only read volumes encrypted under a Windows 7 system but >> is >> now Windows Vista and 8 capable and has the write functionality. > The package description is not the right place to explain the > development history of the package: just list its capabilities, if this > is an information useful to prospective users. > >> The core driver is composed of a library, with multiple binaries using this >> library. Two binaries are of interest when wanting to ecrypt a BitLocker >> encrypted partition: > The package description is not a replacemente for the package > documentation either. > I was really careless with this description, I will improve it now. Thanks for reviewing! cheers, -- Giovani Ferreira http://softwarelivre.org/jova2 GNU/Linux user: 337388 GPG ID: 2375A66C signature.asc Description: OpenPGP digital signature
Bug#819938: apt: [INTL:ja] Japanese translation of po file update
Package: apt Version: 1.0.9.8.2 Severity: wishlist Tags: l10n patch Dear Maintainer, Here's Japanese translation of po (ja.po) file that reviewed by several Japanese Debian developers and users. Please copy the attachment into po/ja.po. Kind regards. -- Takuma Yamada -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt depends on: ii debian-archive-keyring 2014.3 ii gnupg 1.4.18-7 ii libapt-pkg4.12 1.0.9.8.2 ii libc6 2.19-18+deb8u3 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 apt recommends no packages. Versions of packages apt suggests: pn apt-doc ii aptitude0.6.11-1+b1 pn dpkg-dev ii python-apt 0.9.3.12 ii synaptic0.81.2 -- no debconf information ja.po.gz Description: application/gzip
Bug#790511: [INTL:tr] Turkish debconf translation update for gdm3
tag 790511 + moreinfo thanks On Tue, 30 Jun 2015 01:58:15 +0300 Mert Dirikwrote: Hi, > Please find the attached Turkish translation update of gdm3 debconf > messages. I've a remarks concerning the proposed patch to the translation of gdm debconf questions. -"Ekran yöneticisi, X Window Sistemi'ne grafik arayüz ile giriş yapmayı sağlar." +"Ekran yöneticisi, X Pencere Sistemi'ne grafik arayüz ile giriş yapmayı " +"sağlar." I'm not sure that translating "X Window" is a good idea as it's the name of technology. In French it's not translated for example. What do you think? Cheers, Laurent Bigonville
Bug#819703: xscreensaver: please disable "This version of XScreenSaver is very old! Please upgrade!" message
On Fri, 1 Apr 2016 10:10:40 -0700 Jamie Zawinski wrote: > For those of you who can't be bothered to read the code, here's what the comment says. Sounds awfully a lot like this old Gentoo bug https://bugs.gentoo.org/show_bug.cgi?id=35890 And yes, I'm probably going to hell for submitting this into the report... Pete.
Bug#819937: ITP: golang-github-jtacoma-uritemplates -- URI Templates (RFC 6570) implemented in Go
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni* Package name: golang-github-jtacoma-uritemplates Version : 0.0~git20151014.16.802b8e2-1 Upstream Author : Joshua Tacoma * URL : https://github.com/jtacoma/uritemplates * License : MIT Programming Lang: Go Description : URI Templates (RFC 6570) implemented in Go uritemplates -- a level 4 implementation of RFC 6570 This is a dependency of github.com/jingweno/go-sawyer, which is itself a dependency of github.com/octokit/go-octokit, which is (finally) a dependency of github.com/github/hub.
Bug#819936: ITP: golang-github-octokit-go-octokit -- Go wrapper for the GitHub API
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni* Package name: golang-github-octokit-go-octokit Version : 0.3.0+git20160312.364.812e91d-1 Upstream Author : * URL : https://github.com/octokit/go-octokit * License : MIT Programming Lang: Go Description : Simple Go wrapper for the GitHub API Dependency of github.com/github/hub
Bug#819934: ITP: golang-github-inconshreveable-go-update -- Build self-updating Golang programs
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni* Package name: golang-github-inconshreveable-go-update Version : 0.0~git20160112.0.8152e7e-1 Upstream Author : Alan Shreve * URL : https://github.com/inconshreveable/go-update * License : Apache 2.0 Programming Lang: Go Description : Library for building self-updating Golang programs This is a dependency of github.com/github/hub.
Bug#819906: rect can't find its help
On Sun, 2016-04-03 at 11:34 -0700, Josh Triplett wrote: > Package: sgt-puzzles > Version: 20140928.r10274-1 > Severity: normal > File: /usr/games/rect > > In rect, the menu item "Help -> Help on Rectangles" shows an error "Help > file is not installed". However, opening "Help -> Contents" shows help > for all games, which includes "Chapter 8: Rectangles". Interesting - I see an attempt to open a file called "rectangles.html" whereas it's actually "rect.html". This is caused by a Debian patch to deal with Rectangles having inconsistent command and chapter names. I assume it worked originally, but obviously not any more. I've replaced that patch with a special case in man page generation. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#819703: Patch to remove obsolesence checking
On Mon, Apr 04, 2016 at 01:26:17AM +0200, Axel Beckert wrote: > Hi Santiago, > > Santiago Vila wrote: > > Sorry, the not-so-short patch would be like this. > > That edits four files. Yes, I know, but the function says "leave this code intact and this warning in place" :-) In the unlikely case that we wanted to follow that to the letter, we could stop calling the function instead. Doing that would also highlight the places at which the time bomb was intended to be triggered in the code. Of course, we would be honoring the letter but not the "spirit", so I don't really think the not-so-short patch will make the author happy. Thanks.
Bug#819935: ITP: golang-github-jingweno-go-sawyer -- Client library for REST APIs
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni* Package name: golang-github-jingweno-go-sawyer Version : 0.0~git20140729.0.1999ae5-1 Upstream Author : Jingwen Owen Ou * URL : https://github.com/jingweno/go-sawyer * License : MIT Programming Lang: Go Description : Client library for REST APIs This is a dependency of github.com/octokit/go-octokit, which is itself a dependency of github.com/github/hub.
Bug#819933: jessie-pu: package redmine/3.0~20140825-8~deb8u3
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu This fixes an issue when upgrading from 3.0~20140825-5 (original version release with jessie) to any of the later stable updates, when there are multiple redmine instances or when the `default` has been removed. This has been fixed in unstable on 3.2.1-2. The diff for jessie is attached. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Antonio Terceirodiff --git a/debian/changelog b/debian/changelog index c4db2f7..ec0e42a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +redmine (3.0~20140825-8~deb8u3) jessie; urgency=medium + + * gemfile-adjustments.patch: load all database drivers for all Redmine +instances (Closes: #819815) + + -- Antonio Terceiro Sun, 03 Apr 2016 20:47:00 -0300 + redmine (3.0~20140825-8~deb8u2) jessie-security; urgency=high * Security update. Includes fixes for the following vulnerabilities: diff --git a/debian/patches/gemfile-adjustments.patch b/debian/patches/gemfile-adjustments.patch index 3a2f6e1..0db0aa3 100644 --- a/debian/patches/gemfile-adjustments.patch +++ b/debian/patches/gemfile-adjustments.patch @@ -37,24 +37,33 @@ end end -@@ -46,8 +46,11 @@ end +@@ -46,12 +46,16 @@ end # configuration file require 'erb' require 'yaml' -database_file = File.join(File.dirname(__FILE__), "config/database.yml") -if File.exist?(database_file) -+# FIXME duplicating logic in config/application.rb -+ENV['X_DEBIAN_SITEID'] ||= 'default' -+ENV['RAILS_ETC'] = "/etc/redmine/#{ENV['X_DEBIAN_SITEID']}" -+database_file = File.join(ENV['RAILS_ETC'], "database.yml") -+if File.readable?(database_file) ++seen_adapters = {} ++Dir['{config,/etc/redmine/*}/database.yml'].select do |f| ++ File.exists?(f) ++end.each do |database_file| database_config = YAML::load(ERB.new(IO.read(database_file)).result) adapters = database_config.values.map {|c| c['adapter']}.compact.uniq if adapters.any? -@@ -78,21 +81,6 @@ else - warn("Please configure your config/database.yml first") - end - + adapters.each do |adapter| ++ next if seen_adapters[adapter] ++ seen_adapters[adapter] = true + case adapter + when 'mysql2' + gem "mysql2", "~> 0.3.11", :platforms => [:mri, :mingw] +@@ -74,23 +78,6 @@ if File.exist?(database_file) + else + warn("No adapter found in config/database.yml, please configure it first") + end +-else +- warn("Please configure your config/database.yml first") +-end +- -group :development do - gem "rdoc", ">= 2.4.2" - gem "yard" @@ -68,8 +77,6 @@ - # For running UI tests - gem "capybara", "~> 2.1.0" - gem "selenium-webdriver" --end -- + end + local_gemfile = File.join(File.dirname(__FILE__), "Gemfile.local") - if File.exists?(local_gemfile) - eval_gemfile local_gemfile signature.asc Description: PGP signature
Bug#819932: ncdu: counts reflinks multiple times
Package: ncdu Version: 1.11-1 Severity: normal Hi! On filesystems that support copy-on-write, such as btrfs, ocfs2, zfs, ncdu will count shared space multiple times. This is akin to already implemented hardlink detection, although for most filesystems it operates on extent rather than file level: if you reflink a 20GB file (like a VM image) then do 1MB worth of writes to one of the replicas, the total usage will be 20GB+1MB rather than 40GB. On Linux, you can get this information using FIEMAP. Use of "cp --reflink" isn't very widespread, but whole-subvolume snapshots are something most btrfs and zfs users do, so lacking this support in ncdu is quite jarring.
Bug#745027: Fwd: Re: Bug#745027: Missing dependencies
(forgot to CC the Debian bugtracker) --- Begin Message --- On Thu, Mar 31, 2016 at 02:19:48PM +0200, Enrico Zini wrote: > On Tue, Feb 02, 2016 at 06:07:56PM +0100, Markus Unterwaditzer wrote: > > > Sorry to insist, but I'd really like to have a definitive answer on this > > > before > > vdirsyncer is packaged. > > > > I suspect that if vdirsyncer makes its way into stable before 1.0, it > > essentially means I'm forced into long-term support of whichever release is > > in > > stable. However, ideally I'd like to only support the latest release of > > vdirsyncer. > > > > If being in stable would really hinder timely updates, I'd prefer > > vdirsyncer to > > stay in testing/unstable forever. > > I am very happy to see your concerns about support of your software, I > wish more developers cared like you did. I apprechiate your kind response. > > It is possible to keep the package only in unstable, except for versions > that you decided to officially support long-term, if any. There can be a > bug in the Debian BTS with a "serious" severity saying "Not intended to > be included on a stable Debian system". That seems fine. > If you wish, the bug can document that if one is interested in having > vdirsyncer in Debian stable, they can offer to coordinate with you > helping upstream development and doing the work of providing long term > support for specific releases. Not before version 1.0, but the idea is nice. > > Would that be acceptable? > > > Enrico > > -- > GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini--- End Message ---
Bug#806824: libpeas python split
Hi Barry, On Mon, 14 Mar 2016 19:42:37 -0400 Barry Warsawwrote: > On Mar 13, 2016, at 12:29 AM, Michael Biebl wrote: > > >So, if I'm counting correctly, there are only 3 packages remaining that > >use the python2 loader. Somehow I think the best course of action would > >be to get those updated to python3. > > Perhaps, but isn't that an upstream decision? Also, isn't it possible that > third parties might still have Python 2 plugins for applications outside of > the Debian archive? Andreas was suggesting a compromise. Split out the python2 loader but keep the python3 loader within the main libpeas-1.0-0 package. This will reduce the churn quite a but. Both Emilio and myself are ok with that proposal, so we intend to proceed with that plan. This means we can close most of the bugs and and only need to keep the 3 python2 bugs open. We should follow up there and make it clear that they should update to python3. They then can drop the explicit dependency on the python2 loader package again. I intend to work on the libpeas package the next couple of days. One of the modfications I'd like to do, is move the python2 loader package to oldlibs/extra and drop the soname specific part from the package. I hope you can agree with this plan, if not, please shout. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#819931: ITP: golang-github-howeyc-gopass -- getpasswd for Go
Package: wnpp Severity: wishlist Owner: Nicolas Braud-Santoni* Package name: golang-github-howeyc-gopass Version : 0.0~git20160303.0.66487b2-1 Upstream Author : Chris Howey * URL : https://github.com/howeyc/gopass * License : ISC Programming Lang: Go Description : getpasswd for Go getpasswd: Retrieve password from user terminal or piped input without echo. Caution: Multi-byte characters not supported! This is a dependency of [hub], which tianon@ is packaging. [hub]: https://github.com/github/hub
Bug#819868: qtwebkit: Make determineNumberOfCPUs work on kfreebsd
tag 819868 pending thanks On Sunday 03 April 2016 12:15:04 Jon Boden wrote: [snip] > Hi > > Please could you apply this tiny patch? It makes determineNumberOfCPUs work > on kfreebsd. > > Note1: This is more relevant than it seems. I recall seeing some build > system (not sure if qtwebkit itself or something else) spawning an > unlimited offspring of gcc processes (~50) when this routine fails. > > Note2: This is the old version of the patch for qtwebkit 2.3.4. A slightly > different version has already been sent upstream. Patch applied in the repo. Two things to note: - I don't plan to build+upload qtwebkit soon. I would actually prefer to get it removed from the archive, but it's too soon now. - What about Qt5's qtwebkit? Dos it suffer from the same problem? If so, can you provide a patch too? Kinds regards, Lisandro. -- me cago en el gato, es como la tercera vez que me apreta backspace mientras tengo apretados ctrl y alt Visto en #lugfi, irc.freenode.net Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#819703: Patch to remove obsolesence checking
Hello Santiago, On Mon, 4 Apr 2016 01:02:01 +0200 Santiago Vilawrote: > On Sun, Apr 03, 2016 at 05:39:49PM -0400, Michael Greger wrote: > > Here's a patch to remove the obsolensence checking that > > xscreensaver does. > > For an upload to stable-proposed-updates, the release managers > appreciate that diffs are as small and easy to understand as possible, > so the shorter the diff, the better. > > I would apply one of the following patches. This one is better: -- Best regards, Alexander Gerasiov Contacts: e-mail: g...@cs.msu.su Homepage: http://gerasiov.net Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1 diff -rNu xscreensaver-5.30.bak/driver/prefs.c xscreensaver-5.30/driver/prefs.c --- xscreensaver-5.30.bak/driver/prefs.c 2014-08-08 21:57:20.0 +0400 +++ xscreensaver-5.30/driver/prefs.c 2016-04-04 02:27:26.245511238 +0300 @@ -1660,6 +1660,7 @@ } +#if 0 Bool senescent_p (void) { @@ -1738,3 +1739,4 @@ /* h */ return (months > 18); /* p */ } +#endif diff -rNu xscreensaver-5.30.bak/driver/prefs.h xscreensaver-5.30/driver/prefs.h --- xscreensaver-5.30.bak/driver/prefs.h 2014-04-27 08:06:52.0 +0400 +++ xscreensaver-5.30/driver/prefs.h 2016-04-04 02:26:56.973510146 +0300 @@ -20,7 +20,7 @@ saver_preferences *, const char *version_string, Bool verbose_p); const char *init_file_name (void); -extern Bool senescent_p (void); +static inline Bool senescent_p (void) { return 0; } extern screenhack *parse_screenhack (const char *line); extern void free_screenhack (screenhack *);
Bug#819930: dh-make-golang should depend on git-buildpackage and pristine-tar
Package: dh-make-golang Version: 0.0~git20150913.0.1221041-1 Severity: important Dear Maintainer, It seems dh-make-golang has a missing dependency on git-buildpackage: > % dh-make-golang github.com/mattn/go-isatty > 2016/04/04 01:19:05 Downloading "github.com/mattn/go-isatty/..." > 2016/04/04 01:19:06 Determining upstream version number > 2016/04/04 01:19:06 Package version is "0.0~git20151211.0.56b76bd" > 2016/04/04 01:19:06 Determining package type > 2016/04/04 01:19:06 Determining dependencies > 2016/04/04 01:19:06 WARNING: A package called > "golang-github-mattn-go-isatty-dev" is already in Debian! See > https://tracker.debian.org/pkg/golang-github-mattn-go-isatty-dev > 2016/04/04 01:19:06 Could not create git repository: exec: "gbp": executable > file not found in $PATH Moreover, after installing gbp, I encountered the following error: > gbp:error: Couldn't commit to 'pristine-tar' with upstream 'master': > gbp:error: Import of > /home/nbraud/devel/deb/golang-github-howeyc-gopass_0.0~git20160303.0.66487b2.orig.tar.xz > failed: Couldn't commit to 'pristine-tar' with upstream 'master': > 2016/04/04 01:31:53 Could not create git repository: exit status 1 This was solved by installing pristine-tar. Best regards, nicoo -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dh-make-golang depends on: ii git1:2.8.0~rc3-1 ii golang-go 2:1.6-1 ii libc6 2.22-4 Versions of packages dh-make-golang recommends: ii git-buildpackage 0.7.2 ii msmtp-mta [mail-transport-agent] 1.6.4-1 dh-make-golang suggests no packages. -- no debconf information
Bug#819929: RFS: mini-httpd/1.23-1 -- Small HTTP server
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mini-httpd" * Package name: mini-httpd Version : 1.23-1 Upstream Author : Jef Poskanzer* URL : http://www.acme.com/software/mini_httpd * License : BSD-2-clause Section : web It builds those binary packages: mini-httpd - Small HTTP server To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mini-httpd Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.23-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: mini-httpd (1.23-1) unstable; urgency=medium * New upstream release * d/control: - Bump Standard-Version to 3.9.7. * d/upstream.changelog: - Update changes. * d/patches: - Remove patch fix-add_to_response-buffer-overflow fixed for upstream. - Fix support FreeBSD thanks Steven Chamberlain (Closes: #815339) - Add patch fix-autobuilders for a problem with package on 64-bit thanks Steve Langasek (Closes: #819125) * d/rules: - Add hardening - Don`t install htpasswd (LP: #943088) Regards, J.S.Júnior signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#819928: iptraf-ng: curses display is broken
Package: iptraf-ng Version: 1.1.4-2 Severity: important Tags: upstream patch Dear Maintainer, This upstream patch is necessary in order to properly link iptraf-ng https://git.fedorahosted.org/cgit/iptraf-ng.git/commit/?id=1a009a230aacaa87d24fe75a257ffe8d57313116 Without this patch the ncurses display just doesn't work because its trying to use the wide character libncurses with the non-wide char libpanel. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages iptraf-ng depends on: ii libc6 2.22-5 ii libncurses5 6.0+20160319-1 ii libncursesw5 6.0+20160319-1 ii libtinfo5 6.0+20160319-1 iptraf-ng recommends no packages. iptraf-ng suggests no packages. -- no debconf information
Bug#819703:
On Sun, Apr 03, 2016 at 03:44:55PM -0700, Jeff Warnica wrote: > Upstream is adamant that he gets bug reports (and all bug reports are > security bug reports, especially on security software) against the version > included with Debian, which have since been fixed. There are two ways jwz can get such bug reports: * from the BTS -- ie, with an explicit opt-in. If this hurts, "don't do that, then". * via e-mail: in that case, the software shouldn't advertise his address, as name or nick is adequate to show authorship. This doesn't apply for all people -- for example, there are many politicians, film directors, even software developers named "Adam Borowski", but "Jamie Zawinski" seems to be google-unique for as many pages as I checked.[1] Another possible concern is that he doesn't want his name associated with "obsolete" versions. In such case, a rename would work. jwz: could you tell us which of these concerns apply? > Debian applies changed *all the time* to "stable" packages. The alternative > proposal is to apply changes to "stable" software. Only for security and selected RC bugs. > If you do change things, then backport security fixes, however hard that > may be. Which Debian does! It's exactly what a stable release is about. > The laziest possible option is to remove the legitimate warning that the > software is obsolete. The software is not obsolete, it's fully working and at least as secure as the newest shiniest release. It does receive security updates, and the code had more time for bugs to surface. [1]. There's 1082 times as many people named Borowski than Zawi[nń]ski, having a Polish surname but non-Polish first name makes the combination rare, and yeah, jwz having a wee more claims for fame than me might also be a factor. -- A tit a day keeps the vet away.
Bug#819927: RM: json-spirit -- ROM; unused
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi ftpmasters, Please drop json-spirit from unstable: It was intended for use by Bitcoin, but that package has since switched to using a different library (univalue). No other packages in Debian uses json-spirit. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJXAadNAAoJECx8MUbBoAEhBhoQAJ59NtFvxaKFiD5mhsm2+GTE qbWpkNJkfJrUQ6iVtYvHQwAxjCsBxfePXUF+yssSlemrP3ijyuCNmVh/vmOCCq34 vmQrQm71vuXKjvj1QvEsdeRqPugxR1zHegCgBo0S4mJgg6HzdhlFJgvxxg3oeyGS okMOwnm0RRXt1XhZNebPV82iW1ObTtQ6RKMbut626zkfOKgqCKNwuT6n591Sgblz JDzIVYXBNw0hTzxNSXjlms05CajNhDtoHFQd3uUlJJTmhmkaRac1E+Iv7LQeRBRm LLZObl3kf37trdqinyR6ZLLIqaOlyp6loECvUrj8p81MaipDZ8eRWuHU4epfZQUm GZN6cqrve6FPGklvAotRdcyqJ4C4UiMgyne+O0xN2P/3PTE6s7PzHCxgKv7HDXko kCwthK10OLJXW/eNihMsy52tvPxtv865c25EcJYlX/6K2iMXtxNxc74/fdQUDZ+4 rD3wCl6cxWZYG9bZQK6eiy/l+7Sy5Lwb5MTEpPQTNEY1jNfrsOlLJ4pQVMvjyvGc ZAU5e94Q1yv7t/Iq2IsLZjRdOfOBCX9bFxKLXKti700uxtfj5GqkXuxb2+y1zghm slKvcG6mNVDwWb/ZqbeXu/vCho5NM0uWVdR6PE+yXoBaO/Y60Ae9xwx5oRPb41r/ NU9PHuvvRIYl0TwhdPHv =NORo -END PGP SIGNATURE-
Bug#819703: Patch to remove obsolesence checking
Hi Santiago, Santiago Vila wrote: > Sorry, the not-so-short patch would be like this. That edits four files. The patch posted in the initial bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;att=1;filename=patch.txt;bug=819703) only added a single line ("return 0" to senescent_p()) and as far as I can see it should suffice for all places where you removed the call to senescent_p(): diff --git a/driver/prefs.c b/driver/prefs.c index 55bac7b..f9f96c3 100644 --- a/driver/prefs.c +++ b/driver/prefs.c @@ -1663,6 +1663,8 @@ stop_the_insanity (saver_preferences *p) Bool senescent_p (void) { + return 0; + /* If you are in here because you're planning on disabling this warning before redistributing my software, please don't. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#811767: Fwd: Bug#811767: geoip: FTBFS with GCC 6: narrowing conversion
Package: geoip Version: 1.6.9-1 Severity: important User: debian-...@lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-narrowing This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in experimental. To build with GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly. You may be able to find out more about this issue at https://gcc.gnu.org/gcc-6/changes.html sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux ... make[2]: Leaving directory '/<>' # Build the build script. g++ -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -g debian/src/geoip-csv-to-dat.cpp -o debian/tmp/geoip-generator -lGeoIP \ -I /<>/debian/tmp/usr/include/ -L /<>/debian/tmp/usr/lib/x86_64-linux-gnu/ debian/src/geoip-csv-to-dat.cpp: In member function 'void {anonymous}::dat_writer::write_trie({anonymous}::binary_trie&)': debian/src/geoip-csv-to-dat.cpp:658:23: warning: narrowing conversion of '(it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[0] & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[0]) & 0xFF, ~~~^~ debian/src/geoip-csv-to-dat.cpp:659:25: warning: narrowing conversion of '((it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[0] >> 8) & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[0] >> 8) & 0xFF, ~^~ debian/src/geoip-csv-to-dat.cpp:660:25: warning: narrowing conversion of '((it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[0] >> 16) & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[0] >> 16) & 0xFF, ~^~ debian/src/geoip-csv-to-dat.cpp:661:23: warning: narrowing conversion of '(it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[1] & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[1]) & 0xFF, ~~~^~ debian/src/geoip-csv-to-dat.cpp:662:25: warning: narrowing conversion of '((it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[1] >> 8) & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[1] >> 8) & 0xFF, ~^~ debian/src/geoip-csv-to-dat.cpp:663:25: warning: narrowing conversion of '((it.__gnu_cxx::__normal_iterator<_Iterator, _Container>::operator-><{anonymous}::binary_trie::node*, std::vector<{anonymous}::binary_trie::node> >()->{anonymous}::binary_trie::node::edges[1] >> 16) & 255ul)' from '{anonymous}::binary_trie::edge_type {aka long unsigned int}' to 'uint8_t {aka unsigned char}' inside { } [-Wnarrowing] (it->edges[1] >> 16) & 0xFF ~^~ debian/src/geoip-csv-to-dat.cpp: In member function 'virtual void {anonymous}::dat_writer::write_structure_info()': debian/src/geoip-csv-to-dat.cpp:683:67: error: narrowing conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing] const char structure_info[4] = { 0xFF, 0xFF, 0xFF, database_type }; ^ debian/src/geoip-csv-to-dat.cpp:683:67: error: narrowing conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing] debian/src/geoip-csv-to-dat.cpp:683:67: error: narrowing conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing] debian/src/geoip-csv-to-dat.cpp: In member function 'virtual void {anonymous}::city_dat_writer::write_structure_info({anonymous}::binary_trie&)': debian/src/geoip-csv-to-dat.cpp:813:31: error: narrowing conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing] (trie_size >> 16) & 0xFF}; ^ debian/src/geoip-csv-to-dat.cpp:813:31: error: narrowing conversion of '255' from 'int' to 'char' inside { } [-Wnarrowing] debian/src/geoip-csv-to-dat.cpp:813:31:
Bug#772845: freetuxtv: package keeps crushing at startup screen
Hi I confirm that the patch file 02-crash.diff (corresponding to svn commit 750) solves this segfault issue. To fix the compilation issue mentionned by Petter Reinholdtsen above, apparently you also need to apply the commit 747 (patch attached). Best, Pierre L.Index: lib/libvlc-gtk/gtk-libvlc-media-player.c === --- lib/libvlc-gtk/gtk-libvlc-media-player.c (révision 746) +++ lib/libvlc-gtk/gtk-libvlc-media-player.c (révision 747) @@ -1819,7 +1819,7 @@ // Create the media player if not initialized gtk_libvlc_media_player_initialize (self, ); - g_return_if_fail(priv->initialized == TRUE); + g_return_val_if_fail(priv->initialized == TRUE, gtkstate); if(pError == NULL){
Bug#698810: notmuch: Internal error: add_message returned unexpected value: 4 (notmuch-new.c:543)
Paul Wisewrites: > On Tue, 29 Mar 2016 08:24:01 -0300 David Bremner wrote: > >> pabs3 just mentioned the same problem on IRC. > > FTR: > > I got this from notmuch new --quiet, any thoughts? Internal error: > add_message returned unexpected value: 4 (notmuch-new.c:291) > first and only time I got the message yesterday. successful hourly > indexing since then > ... > hmm, different line number. I guess the code has changed a bit > based on that bug, I would guess a race condition between knowing a > directory entry exists, stat()ing it and something else deleting it > >> I don't really know what's going on here, but I wanted to make a note >> somewhere that the error reporting should really be improved here. We >> (upstream) should really catch that specific error code, and at least >> print out the name of the file causing the error. As of upstream commit 0.21-98-g6e6bafe I have added some better error reporting in this case. This will be part of the next upstream, release, in a few weeks. d
Bug#819926: linuxlogo: init script needs to escape backslashes before writing issue.linuxlogo
Package: linuxlogo Version: 5.11-8 Severity: normal Tags: patch Dear Maintainer, when using /etc/issue.linuxlogo or /etc/issue.linuxlogo.ascii with getty as described in /usr/share/doc/linuxlogo/README.Debian, backslashes in the logo don't get escaped and hence get stripped or misinterpreted by getty as escape sequences. This doesn't show up with the default banner or any of the Debian logos, but it does happen with "ubuntu" as well as the "raspi" logo. Both are probably common with Debian derivatives, but since Debian also runs on the Raspberry Pi directly, the "raspi" banner is definitely on-topic for a Debian package and not just a downstream issue. Currently the "raspi" and "ubuntu" logo look like this when shown by getty: .~~. .~~. _____ ___ _ '. ' ' / .' / _ ___ ___ ___ / / ___ ___ ___ _ __ / _ (_) .~ .~~~..~. / , _/ _ `(_- /etc/issue.linuxlogo - "${DAEMON}" -t "Debian Version $(cat /etc/debian_version)" -a -f > /etc/issue.linuxlogo.ascii + "${DAEMON}" -t "Debian Version $(cat /etc/debian_version)" -f | sed -e 's/\\//g' > /etc/issue.linuxlogo + "${DAEMON}" -t "Debian Version $(cat /etc/debian_version)" -a -f | sed -e 's/\\//g' > /etc/issue.linuxlogo.ascii for FILE in /etc/issue.linuxlogo /etc/issue.linuxlogo.ascii do The issue happens with both, systemd as well as sysvrc as init system and the patch works in both cases, at least currently. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 3.18.0-trunk-rpi2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages linuxlogo depends on: ii libc6 2.22-5 ii lsb-base 9.20160110 linuxlogo recommends no packages. linuxlogo suggests no packages. -- Configuration Files: /etc/linux_logo.conf changed: -L raspi -- no debconf information
Bug#819924: uploaders.mk breaks clean target under dh
Am 04.04.2016 um 01:03 schrieb Michael Biebl: > Package: gnome-pkg-tools > Version: 0.19.6 > Severity: important > > We already have quite a few package in pkg-gnome which use dh. > Most of them include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk so > running debian/rules clean updates debian/control from > debian/control.in. > > Unfortunately this breaks the clean target under dh. The only action > that is run in debian/rules clean is the update of debian/control, the > build directory is no longer cleaned up. As it turns out, the proper fix for this seems to be, that packages using dh should use the gnome addon and drop uploaders.mk from debian/rules. Grepping through our pkg-gnome SVN, I found ekiga gcr gfbgraph gnome-builder gnome-calendar gnome-characters gnome-clocks gnome-logs gnome-maps gnome-music gnome-online-miners gnome-photos gnome-software gnome-taquin gsound libproxy libpwquality libsecret polari pygobject which are affected by this. Any takers? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#819925: debmirror: Experimental distribution contents files not downloaded with --getcontents
Package: debmirror Version: 1:2.25 Severity: normal Dear Maintainer, I am trying to mirror the Contents-.gz for experimental (as now required by aptitude) and they do not get downloaded. For other distributions (stable / testing / unstable) they do get downloaded. debmirror should download the Contents-.gz for all distributions being mirrored. -- System Information: Debian Release: stretch/sid APT prefers local APT policy: (500, 'local'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debmirror depends on: ii bzip2 1.0.6-8 pn libdigest-md5-perl ii liblockfile-simple-perl 0.208-1 ii libnet-inet6glue-perl 0.603-2 ii libperl5.22 [libdigest-sha-perl] 5.22.1-9 ii libwww-perl 6.15-1 ii perl 5.22.1-9 ii perl-modules-5.22 [libnet-perl] 5.22.1-9 ii rsync 3.1.1-3 Versions of packages debmirror recommends: pn ed ii gpgv 1.4.20-4 ii patch 2.7.5-1 Versions of packages debmirror suggests: ii gnupg 1.4.20-4 -- no debconf information
Bug#819703: Patch to remove obsolesence checking
Sorry, the not-so-short patch would be like this. --- a/driver/demo-Gtk.c +++ b/driver/demo-Gtk.c @@ -5292,7 +5292,7 @@ main (int argc, char **argv) the_network_is_not_the_computer (s); - if (senescent_p()) + if (0) warning_dialog (s->toplevel_widget, _("Warning:\n\n" "This version of xscreensaver is VERY OLD!\n" --- a/driver/lock.c +++ b/driver/lock.c @@ -487,7 +487,7 @@ make_passwd_window (saver_info *si, * room for the dialog to grow without going off the edge of the screen. */ max_string_width_px *= 0.75; - if (!info_msg && senescent_p()) + if (0) info_msg = ("\n" "This version of XScreenSaver\n" "is very old! Please upgrade!\n"); --- a/driver/splash.c +++ b/driver/splash.c @@ -167,7 +167,7 @@ make_splash_dialog (saver_info *si) Colormap cmap; char *f; - Bool whine = senescent_p (); + Bool whine = 0; if (whine) { --- a/driver/xscreensaver.c +++ b/driver/xscreensaver.c @@ -784,7 +784,7 @@ print_banner (saver_info *si) "\n", blurb()); - if (p->verbose_p && senescent_p ()) + if (0) fprintf (stderr, "\n" "*" "**\n"
Bug#819703: Patch to remove obsolesence checking
On Sun, Apr 03, 2016 at 05:39:49PM -0400, Michael Greger wrote: > Here's a patch to remove the obsolensence checking that xscreensaver does. For an upload to stable-proposed-updates, the release managers appreciate that diffs are as small and easy to understand as possible, so the shorter the diff, the better. I would apply one of the following patches. (The not-so-short version does not even modify the senescent_p() function) Thanks.--- a/driver/demo-Gtk.c +++ b/driver/demo-Gtk.c @@ -5292,7 +5292,7 @@ main (int argc, char **argv) the_network_is_not_the_computer (s); - if (senescent_p()) + if (0) warning_dialog (s->toplevel_widget, _("Warning:\n\n" "This version of xscreensaver is VERY OLD!\n" --- a/driver/lock.c +++ b/driver/lock.c @@ -487,7 +487,7 @@ make_passwd_window (saver_info *si, * room for the dialog to grow without going off the edge of the screen. */ max_string_width_px *= 0.75; - if (!info_msg && senescent_p()) + if (!info_msg) info_msg = ("\n" "This version of XScreenSaver\n" "is very old! Please upgrade!\n"); --- a/driver/splash.c +++ b/driver/splash.c @@ -167,7 +167,7 @@ make_splash_dialog (saver_info *si) Colormap cmap; char *f; - Bool whine = senescent_p (); + Bool whine = 0; if (whine) { --- a/driver/xscreensaver.c +++ b/driver/xscreensaver.c @@ -784,7 +784,7 @@ print_banner (saver_info *si) "\n", blurb()); - if (p->verbose_p && senescent_p ()) + if (p->verbose_p) fprintf (stderr, "\n" "*" "**\n" --- a/driver/prefs.c +++ b/driver/prefs.c @@ -1736,5 +1736,5 @@ senescent_p (void) months = tm->tm_year + 1900) * 12) + tm->tm_mon) - /* h */ (y * 12 + m)); /* h */ /* h */ - return (months > 18);/* p */ + return (0); /* p */ }
Bug#819190:
I was having this problem and I think it's solved now. I was using the current nvidia driver until my graphics card became obsolete, then I installed the legacy driver and uninstalled the current driver. It was left in a broken state after that. I tried to dist-upgrade or remove the nvidia packages but it failed telling me to run "dpkg --configure -a". When I tried to do that the command would hang so I was stuck.. Examining the running processes in another console I could see it was the /usr/lib/nvidia/check-for-mismatching-nvidia-module script that hang. I edited said script putting an exit command at the start of the script so I could resume dpkg execution, then I purged all nvidia packages and installed the legacy package succesfully this time. Questions: - what is your Nvidia card (lspci verbose output please)? 01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce 9800 GT] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce 9800 GT] Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f600 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at f400 (64-bit, non-prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at f700 [disabled] [size=128K] Capabilities: Kernel driver in use: nouveau Kernel modules: nvidia (This is after succesfully removing the nvidia packages, thus the nouveau driver.) - are you on stable, testing or unstable? Testing. - if I understand correctly you have an amd64 installation. Did you add i368 via dpkg --add-architecture? Yes. Had nvidia i386 packages installed. - did you ever have non-legacy-340xx packages installed? Yes. I had them until they become incompatible with my card. - are you installing from a tty or is yours a laptop with an optimus system? It's a desktop system and tried from a gnome terminal and a remote ssh session. I hope this helps someone. Thanks for you support. Best regards. -- Bernat Arlandis
Bug#819844: message should mention that it is possible to restart without asking
> "AJ" == Aurelien Jarnowrites: >> Every upgrade the upgrade stops and the operator must walk over and >> press return to get it started again. >> >> The message shown about restarting services exim4 cron atd should also >> mention how/that one can also restart without asking. AJ> There is already debconf question to avoid getting asked at each AJ> upgrade. If you answer yes, the services are restarted without asking. AJ> I don't really understand what you want more. At the bottom of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819845#10 Colin Watson mentions the problem with it.
Bug#819924: uploaders.mk breaks clean target under dh
Package: gnome-pkg-tools Version: 0.19.6 Severity: important We already have quite a few package in pkg-gnome which use dh. Most of them include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk so running debian/rules clean updates debian/control from debian/control.in. Unfortunately this breaks the clean target under dh. The only action that is run in debian/rules clean is the update of debian/control, the build directory is no longer cleaned up. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-pkg-tools depends on: ii gir1.2-glib-2.0 1.46.0-4 ii perl 5.22.1-9 ii python3 3.5.1-3 ii python3-gi 3.18.2-2+b1 Versions of packages gnome-pkg-tools recommends: ii svn-buildpackage 0.8.5+nmu1 gnome-pkg-tools suggests no packages. -- no debconf information
Bug#819703:
Upstream is adamant that he gets bug reports (and all bug reports are security bug reports, especially on security software) against the version included with Debian, which have since been fixed. Debian applies changed *all the time* to "stable" packages. The alternative proposal is to apply changes to "stable" software. Some ideal universe xscreensaver might maintain an active version and a version for Debian. They don't, and aren't unique in their indifference to the stated policies. If you don't change things, fine, don't change things including the feature warning that the software is obsolete. If you do change things, then backport security fixes, however hard that may be. The laziest possible option is to remove the legitimate warning that the software is obsolete. On Apr 3, 2016 15:21, "Axel Beckert"wrote: > Hi Jeff, > > Jeff Warnica wrote: > > There is the third option of "actually back port fixes and thus honestly > be > > able to remove the obsolete software warning" which should be > investigated. > > Nope, that's _not_ an option for Debian Stable. Please read > https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.1.3 > > > Just selecting a random version and never changing it may quality as > > "stable", > > That's the point. > > > but that isn't "useful". > > It's as useful as on the first day where the Debian Stable release has > been released. New features will very likely introduce bugs and bugs > reduce usability usually more than missing new features. > > Regards, Axel > -- > ,''`. | Axel Beckert , http://people.debian.org/~abe/ > : :' : | Debian Developer, ftp.ch.debian.org Admin > `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 > `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE >
Bug#819923: e2fsprogs: please move filefrag to /usr/bin/
Package: e2fsprogs Version: 1.43~WIP.2016.03.15-2 Severity: wishlist Hi! As "filefrag" seems to work fine for non-root, I think it should be moved from */sbin/ to */bin/. In the past, it used FIBMAP which indeed was root-only but as since kernel 2.6.28 we have FIEMAP, filefrag is useful for ordinary users. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-rc1-x32+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages e2fsprogs depends on: ii e2fslibs1.43~WIP.2016.03.15-2 ii libblkid1 2.27.1-6.0nosystemd1 ii libc6 2.22-5 ii libcomerr2 1.43~WIP.2016.03.15-2 ii libss2 1.43~WIP.2016.03.15-2 ii libuuid12.27.1-6.0nosystemd1 ii util-linux 2.27.1-6.0nosystemd1 e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static pn gpart ii parted 3.2-15 -- no debconf information
Bug#819548: gnome-maps fails to start
Le Sun, 3 Apr 2016 14:41:44 +0200 Andreas Henrikssona écrit: > Hello again! > > mlundblad mentioned to me on IRC that he has identified the culprit > as gjs in testing not being new enough. Please confirm that upgrading > to gjs from unstable fixes the problem for you. > > (This issue has been fixed upstream in gnome-maps at: > https://git.gnome.org/browse/gnome-maps/commit/?id=f735490a47afbf > and I'll add the equivalent dependency to the debian package shortly.) > > Regards, > Andreas Henriksson Hi Andreas, I confirm. I've upgraded to unstable version (1.44.0-1) and it's ok now. Thanks.
Bug#819854: [Letsencrypt-devel] Bug#819854: wouldn't Recommends: be better?
Control: reassign -1 gitlab Control: retitle -1 gitlab: Please downgrade hard dependency on letsencrypt to Recommends Hi, Adam Borowski wrote: > > Please provide a letsencrypt-no-thanks package like dbconfig-no-thanks so > > we can make letsencrypt optional. Huh? Now that's a strange request. > > Currently gitlab depends on letsencrypt but that brings in about 12 python > > packages for those who don't want to use letsencrypt. > > I guess you should change Depends: to Recommends: then. Definitely. Hence reassigning. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#819703:
Hi Jeff, Jeff Warnica wrote: > There is the third option of "actually back port fixes and thus honestly be > able to remove the obsolete software warning" which should be investigated. Nope, that's _not_ an option for Debian Stable. Please read https://www.debian.org/doc/manuals/debian-faq/ch-choosing.en.html#s3.1.3 > Just selecting a random version and never changing it may quality as > "stable", That's the point. > but that isn't "useful". It's as useful as on the first day where the Debian Stable release has been released. New features will very likely introduce bugs and bugs reduce usability usually more than missing new features. Regards, Axel -- ,''`. | Axel Beckert, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#819922: RM: php-sasl -- ROM; no PHP 7 support, dead upstream
Package: ftp.debian.org Severity: normal Hi, please remove php-sasl as there's no PHP 7 support and no sign of it in upstream revision control. We really need to push forward, so we finish the transition to PHP 7 in time. Cheers, Ondrej
Bug#818708: didiwiki regression: fix for CVE-2013-7448 renders many existing pages inaccessible
Thanks Sergio for your review and input. Here is the patch I will be uploading. +if (page_name[0] == '/') +return FALSE; + +if (strncmp(page_name, "../", 3) == 0) +return FALSE; + +if (strstr(page_name, "/../")) +return FALSE; Cheers, Ignace M
Bug#819921: basket: please make the build reproducible (timestamps)
Source: basket Version: 2.10~beta+git20160305.487a115-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, While working on the “reproducible builds” effort [1], we have noticed that 'basket' could not be built reproducibly. The attached patch removes build date from debug info. Once applied, basket can be built reproducibly in our current experimental framework. Regards, Alexis Bienvenüe. [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru basket-2.10~beta+git20160305.487a115/debian/changelog basket-2.10~beta+git20160305.487a115/debian/changelog --- basket-2.10~beta+git20160305.487a115/debian/changelog 2016-03-06 20:38:04.0 +0100 +++ basket-2.10~beta+git20160305.487a115/debian/changelog 2016-04-03 23:41:40.0 +0200 @@ -1,3 +1,9 @@ +basket (2.10~beta+git20160305.487a115-1.0~reproducible1) unstable; urgency=medium + + * Removes build date from debug info, to get a reproducible build. + + -- Alexis BienvenüeSun, 03 Apr 2016 23:41:39 +0200 + basket (2.10~beta+git20160305.487a115-1) unstable; urgency=medium * New git snapshot: diff -Nru basket-2.10~beta+git20160305.487a115/debian/patches/15_remove_build_date_from_debug_info.patch basket-2.10~beta+git20160305.487a115/debian/patches/15_remove_build_date_from_debug_info.patch --- basket-2.10~beta+git20160305.487a115/debian/patches/15_remove_build_date_from_debug_info.patch 1970-01-01 01:00:00.0 +0100 +++ basket-2.10~beta+git20160305.487a115/debian/patches/15_remove_build_date_from_debug_info.patch 2016-04-03 23:40:43.0 +0200 @@ -0,0 +1,14 @@ +Description: Remove build date from debug info + This makes the build reproducible. +Author: Alexis Bienvenüe + +--- basket-2.10~beta+git20160305.487a115.orig/src/crashhandler.cpp basket-2.10~beta+git20160305.487a115/src/crashhandler.cpp +@@ -72,7 +72,6 @@ Crash::crashHandler(int /*signal*/) + + body += " DEBUG INFORMATION ===\n" + "Version:" VERSION "\n" +-"Build date: " __DATE__ "\n" + "CC version: " __VERSION__ "\n" //assuming we're using GCC + "KDElibs:" KDE_VERSION_STRING "\n" + ;//"TagLib: %2.%3.%4\n"; diff -Nru basket-2.10~beta+git20160305.487a115/debian/patches/series basket-2.10~beta+git20160305.487a115/debian/patches/series --- basket-2.10~beta+git20160305.487a115/debian/patches/series 2015-11-29 12:04:35.0 +0100 +++ basket-2.10~beta+git20160305.487a115/debian/patches/series 2016-04-03 23:39:53.0 +0200 @@ -1 +1,2 @@ 14_update_es_po.diff +15_remove_build_date_from_debug_info.patch
Bug#372270: This can be fixed
I think what we need to do here is to have Samba install smbspool_krb5_wrapper somewhere predictable, and have 0700 permissions. If we can cope with that being in /usr/bin then it should just work with older packages with only a fix to the perms, if we want /usr/lib/$MULTIARCH/samba then that is what I'm doing in the 4.4 package as it moved to 'libexec' upstream, and that is where I'm pointing libexec to in my 4.4 package I'm building right now. Then just fix the symlink... Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
Bug#819920: RM: php-mysqlnd-ms -- ROM; no upstream PHP 7 support
Package: ftp.debian.org Severity: normal Hi, please remove /subj, it has no r-deps and no PHP 7 support. Thanks, Ondrej
Bug#819919: openvpn: fails to start
Package: openvpn Version: 2.3.10-1 Severity: important Tags: patch Dear Maintainer, when I tried to start openvpn after updating to testing I got following error lines in the log: Apr 03 21:46:06 wolfsden ovpn-server[6837]: OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jan 21 2016 Apr 03 21:46:06 wolfsden ovpn-server[6837]: library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Apr 03 21:46:06 wolfsden ovpn-server[6837]: daemon() failed or unsupported: Resource temporarily unavailable (errno=11) Apr 03 21:46:06 wolfsden ovpn-server[6837]: Exiting due to fatal error It's caused by this line in /lib/systemd/system/openvpn@.service: LimitNPROC=10 when the line is commented out, it starts fine. (Possibly) relevant info: This is debian system running under OpenVZ. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.6-042stab113.11 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.59 ii init-system-helpers1.29 ii initscripts2.88dsf-59.3 ii iproute2 4.3.0-1+b1 ii libc6 2.22-5 ii liblzo2-2 2.08-1.2 ii libpam0g 1.1.8-3.2 ii libpkcs11-helper1 1.11-5 ii libssl1.0.21.0.2g-1 ii libsystemd0229-3 Versions of packages openvpn recommends: ii easy-rsa 2.2.2-2 Versions of packages openvpn suggests: ii openssl 1.0.2g-1 pn resolvconf -- debconf information: openvpn/create_tun: false --- /lib/systemd/system/openvpn@.service 2016-04-03 21:54:45.208397305 + +++ /lib/systemd/system/openvpn@.service 2016-04-03 21:46:15.722287111 + @@ -17,7 +17,7 @@ WorkingDirectory=/etc/openvpn ProtectSystem=yes CapabilityBoundingSet=CAP_IPC_LOCK CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_SETGID CAP_SETUID CAP_SYS_CHROOT CAP_DAC_READ_SEARCH CAP_AUDIT_WRITE -LimitNPROC=10 DeviceAllow=/dev/null rw DeviceAllow=/dev/net/tun rw
Bug#819918: RM: php-svn -- ROM; no PHP 7 support; almost dead upstream
Package: ftp.debian.org Severity: normal php-svn has no PHP 7 support, upstream is almost dead (there were some commits to support svn 1.9) (and svn should die in peace anyway)... and no r-deps Ondrej
Bug#815567:
Control: tags 815567 patch Control: tags 815567 pending Hi, I uploaded a NMU to 15-day/delay queue. Feel free to cancel this upload if needed. The debian/changelog is: amarok (2.8.0-4.1) unstable; urgency=medium * Non-maintainer upload. * debian/control: - Update to Debian Policy 3.9.7. - Build-Depends-Indep: Change build dependency from mysql-server-core to virtual-mysql-server-core to allow mariadb usage (closes: #815567). I attached a debdiff. Thanks. Samuel Henrique O. P. [samueloph] amarok.debdiff Description: Binary data
Bug#819703: Patch to remove obsolesence checking
Here's a patch to remove the obsolensence checking that xscreensaver does. Currently there's no way for a user to disable or prevent the annoying popups everytime their system starts. Amazingly bad idea. diff -rupN xscreensaver-5.30/driver/demo-Gtk.c xscreensaver-5.30.fixed/driver/demo-Gtk.c --- xscreensaver-5.30/driver/demo-Gtk.c 2014-06-04 05:30:47.0 -0400 +++ xscreensaver-5.30.fixed/driver/demo-Gtk.c 2016-04-03 17:22:08.147755729 -0400 @@ -5291,21 +5291,6 @@ main (int argc, char **argv) if (! s->debug_p) the_network_is_not_the_computer (s); - - if (senescent_p()) -warning_dialog (s->toplevel_widget, - _("Warning:\n\n" -"This version of xscreensaver is VERY OLD!\n" -"Please upgrade!\n" -"\n" -"http://www.jwz.org/xscreensaver/\n; -"\n" -"(If this is the latest version that your distro ships, then\n" -"your distro is doing you a disservice. Build from source.)\n" -), - D_NONE, 7); - - /* Run the Gtk event loop, and not the Xt event loop. This means that if there were Xt timers or fds registered, they would never get serviced, and if there were any Xt widgets, they would never have events delivered. diff -rupN xscreensaver-5.30/driver/lock.c xscreensaver-5.30.fixed/driver/lock.c --- xscreensaver-5.30/driver/lock.c 2014-08-05 02:21:30.0 -0400 +++ xscreensaver-5.30.fixed/driver/lock.c 2016-04-03 17:22:08.283762600 -0400 @@ -487,11 +487,6 @@ make_passwd_window (saver_info *si, * room for the dialog to grow without going off the edge of the screen. */ max_string_width_px *= 0.75; - if (!info_msg && senescent_p()) -info_msg = ("\n" -"This version of XScreenSaver\n" -"is very old! Please upgrade!\n"); - pw->info_label = mlstring_new(info_msg ? info_msg : pw->body_label, pw->label_font, max_string_width_px); diff -rupN xscreensaver-5.30/driver/prefs.c xscreensaver-5.30.fixed/driver/prefs.c --- xscreensaver-5.30/driver/prefs.c 2014-08-08 13:57:20.0 -0400 +++ xscreensaver-5.30.fixed/driver/prefs.c 2016-04-03 17:22:08.359766440 -0400 @@ -1658,83 +1658,3 @@ stop_the_insanity (saver_preferences *p) if (p->auth_warning_slack < 0) p->auth_warning_slack = 0; if (p->auth_warning_slack > 300) p->auth_warning_slack = 300; } - - -Bool -senescent_p (void) -{ - /* If you are in here because you're planning on disabling this warning - before redistributing my software, please don't. - - I sincerely request that you do one of the following: - - 1: leave this code intact and this warning in place, -OR- - - 2: Remove xscreensaver from your distribution. - - I would seriously prefer that you not distribute my software at all - than that you distribute one version and then never update it for - years. - - I am *constantly* getting email from users reporting bugs that have - been fixed for literally years who have no idea that the software - they are running is years out of date. Yes, it would be great if we - lived in the ideal world where people checked that they were running - the latest release before they report a bug, but we don't. To most - people, "running the latest release" is synonymous with "running the - latest release that my distro packages for me." - - When they even bother to tell me what version they're running, I - say, "That version is three years old!", and they say "But this is - the latest version my distro ships". Then I say, "your distro - sucks", and they say "but I don't know how to compile from source, - herp derp I eat paste", and *everybody* goes away unhappy. - - It wastes an enormous amount of my time, and kind of makes me regret - ever having released this software in the first place. - - So seriously. I ask that if you're planning on disabling this - obsolescence warning, that you instead just remove xscreensaver from - your distro entirely. Everybody will be happier that way. Check - out gnome-screensaver instead, I understand it's really nice. - - Of course, my license allows you to ignore me and do whatever the - fuck you want, but as the author, I hope you will have the common - courtesy of complying with my request. - - Thank you! - - jwz, 2014 - */ - time_t now = time ((time_t *) 0);/* N */ - struct tm *tm = localtime ();/* o */ - const char *s = screensaver_id;/* */ - char mon[4], year[5]; /* d */ - int m, y, months; /* o */ - s = strchr (s, ' '); if (!s) abort(); s++; /* n */ - s = strchr (s, '('); if (!s) abort(); s++; /* ' */ - s = strchr (s, '-'); if (!s) abort(); s++; /* t */ - strncpy (mon, s, 3); /* */ - mon[3] = 0; /* d */ - s = strchr (s, '-'); if (!s) abort(); s++; /* o */ - strncpy (year, s, 4); /* */ - year[4] = 0; /* i */ - y = atoi
Bug#819917: RM: uprofiler -- ROM; no PHP 7 support
Package: ftp.debian.org Severity: normal Hi, please remove as there's no upstream support for PHP 7.0 and no upstream activity in an year. Cheers, Ondrej
Bug#819854: wouldn't Recommends: be better?
> Please provide a letsencrypt-no-thanks package like dbconfig-no-thanks so > we can make letsencrypt optional. > > Currently gitlab depends on letsencrypt but that brings in about 12 python > packages for those who don't want to use letsencrypt. I guess you should change Depends: to Recommends: then. -- A tit a day keeps the vet away.
Bug#819916: RFP: netdata -- Netdata is a daemon that collects system data in realtime and presents a web site to view and analyze them
Package: wnpp Severity: wishlist * Package name: netdata Version : 1.0.0 Upstream Author : Costa Tsaousis* URL : https://github.com/firehol/netdata/ * License : (GPLv3) Programming Lang: (C, NodeJs, javascript) Description : Netdata is a daemon that collects system data in realtime and presents a web site to view and analyze them Netdata is a daemon that collects data in realtime (per second) and presents a web site to view and analyze them. The presentation is also real-time and full of interactive charts that precisely render all collected values.
Bug#819703:
There is the third option of "actually back port fixes and thus honestly be able to remove the obsolete software warning" which should be investigated. Just selecting a random version and never changing it may quality as "stable", but that isn't "useful".
Bug#818127: TeX error
retitle 818127 TeX error reassign 818127 texlive-htmlxml close 818127 forcemerge 818127 816584 thanks Not a bug in libraw1394.
Bug#819915: kannel: please make the build reproducible (timestamps)
Source: kannel Version: 1.4.4-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, While working on the “reproducible builds” effort [1], we have noticed that 'kannel' could not be built reproducibly. The attached patch makes sure that a fixed date timestamp is used in the documentation (taken from the last d/changelog entry), so the build date does not appear anywhere in the output. It also removes the build date from the return value of version_report_string. Note than timestamps also appear in postscript files built from FIG and PNG files from the source tree (as CreationDate meta data). However, once transfig and imagemagick (which are used for these conversions) honour the SOURCE_DATE_EPOCH environment variable, these timestamps will also be replaced by a fixed date. Once applied, and once bugs #819911 and #819914 regarding transfig and imagemagick will be resolved in the experimental toolchain, kannel can be built reproducibly in our current experimental framework. Regards, Alexis Bienvenüe. [1]: https://wiki.debian.org/ReproducibleBuilds diff -Nru kannel-1.4.4/debian/changelog kannel-1.4.4/debian/changelog --- kannel-1.4.4/debian/changelog 2015-11-23 11:09:32.0 +0100 +++ kannel-1.4.4/debian/changelog 2016-04-02 14:46:03.0 +0200 @@ -1,3 +1,10 @@ +kannel (1.4.4-2.0~reproducible1) unstable; urgency=medium + + * Reproducible build + * Uses dh-autoreconf, see https://wiki.debian.org/Autoreconf + + -- Alexis BienvenüeSat, 02 Apr 2016 09:38:02 +0200 + kannel (1.4.4-2) unstable; urgency=medium * Fix Vcs-* field URLs. Closes: bug#793981. diff -Nru kannel-1.4.4/debian/control kannel-1.4.4/debian/control --- kannel-1.4.4/debian/control 2015-11-23 11:03:33.0 +0100 +++ kannel-1.4.4/debian/control 2016-04-02 14:46:24.0 +0200 @@ -6,6 +6,7 @@ Paul Dwerryhouse Build-Depends: cdbs, debhelper, + dh-autoreconf, libxml2-dev, libssl-dev, openssl, diff -Nru kannel-1.4.4/debian/patches/35_use_changelog_date_in_doc.patch kannel-1.4.4/debian/patches/35_use_changelog_date_in_doc.patch --- kannel-1.4.4/debian/patches/35_use_changelog_date_in_doc.patch 1970-01-01 01:00:00.0 +0100 +++ kannel-1.4.4/debian/patches/35_use_changelog_date_in_doc.patch 2016-04-02 15:05:46.0 +0200 @@ -0,0 +1,139 @@ +Description: Use debian changelog date in doc + Uses the date from SOURCE_DATE_EPOCH in documentation, + instead of current date. +Author: Alexis Bienvenüe + +--- kannel-1.4.4.orig/Makefile.in kannel-1.4.4/Makefile.in +@@ -60,6 +60,7 @@ PACKAGE = @PACKAGE@ + RANLIB = @RANLIB@ + SHELL = @SHELL@ + VERSION = @VERSION@ ++BUILD_DATE = @BUILD_DATE@ + SUFFIX = @SUFFIX@ + LEX = @LEX@ + PERL = @PERL@ +@@ -179,17 +180,17 @@ figs = $(figsrcs:.fig=.png) $(figsrcs:. + .SUFFIXES: $(SUFFIXES) .xml .html .rtf .ps .fig .png .y .c .i .o .pdf + + .xml.html: +- sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp ++ sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/${BUILD_DATE}/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp + ${JADE} -V nochunks -t sgml -d $(HTML_DSL) $(XML_DCL) $*.tmp > $@ + rm -f $*.tmp + + .xml.rtf: +- sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp ++ sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/${BUILD_DATE}/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp + cd `dirname $<` && $(JADE) -o `basename $*`.rtf -t rtf -d $(TEX_DSL) $(XML_DCL) `basename $*`.tmp + rm -f $*.tmp + + .xml.ps: +- sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp ++ sed "s/#FIGTYPE#/.ps/;s/#VERSION#/${VERSION}/;s/#DATE#/${BUILD_DATE}/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp + $(JADE) -o $*.tex -t tex -d $(TEX_DSL) $(XML_DCL) $*.tmp + rm -f $*.tmp + cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true +@@ -201,7 +202,7 @@ figs = $(figsrcs:.fig=.png) $(figsrcs:. + rm -f $*.dvi $*.tex $*.aux + + .xml.pdf: +- sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/`date +%Y.%m.%d`/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp ++ sed "s/#FIGTYPE#/.png/;s/#VERSION#/${VERSION}/;s/#DATE#/${BUILD_DATE}/;s/#DRAFTS#/${DOCDRAFTS}/" $< > $*.tmp + $(JADE) -o $*.tex -t tex -d $(TEX_DSL) $(XML_DCL) $*.tmp + rm -f $*.tmp + cd `dirname $<` && $(JADETEX) `basename $*`.tex >/dev/null || true +--- kannel-1.4.4.orig/addons/opensmppbox/Makefile.am kannel-1.4.4/addons/opensmppbox/Makefile.am +@@ -6,6 +6,7 @@ rpmtemp = /tmp/opensmppbox-rpm + DOCSTARGET=@DOCSTARGET@ + DOCDRAFTS=@DOCDRAFTS@ + RPMPKG=opensmppbox-@PACKAGE_VERSION@ ++BUILD_DATE=@BUILD_DATE@ + + pssrcs = $(wildcard doc/*.png) + ps = $(pssrcs:.png=.ps) +@@ -14,17 +15,17 @@ figsrcs = $(wildcard doc/*.fig) + figs = $(figsrcs:.fig=.png) $(figsrcs:.fig=.ps)
Bug#805701: clisp on hurd
Control: severity -1 important Control: tag -1 +patch Hi! I'll include that in the next upload for sure .. hopefully this week. Ideally we find a arm solution untill then. Has this patch been sent upstream? Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer
Bug#818078: kannel: FTBFS
retitle 818078 TeX error reassign 818078 texlive-htmlxml close 818078 forcemerge 816584 818078 thanks I finally found the package which was at fault. It's already fixed, but I'm reassigning to tidy up. Thanks.
Bug#819456: libgbm-dev & libgles2-mesa-dev are available on kfreebsd-any / hurd-any
Control: tags -1 +pending Hi Steven, On Sun, Apr 03, 2016 at 12:27:55AM +0100, Steven Chamberlain wrote: > I've tried this on Debian GNU/kFreeBSD and it needs other changes: > > Jon is right that those libraries are available now on kfreebsd, in sid > (but were not available in jessie or before). > > Adding them to Build-Depends, they are still not used/needed, unless > EGLFS is enabled first in debian/rules. > > I tried that, it built EGLFS but did not install it into any package; > some debian/*.install-kfreebsd scripts had to be created also. > > The attached diff has everything needed to make this work. A build log > is attached also; but I don't know how to run-time test this. (What is > an example usage of this? Do any reverse-deps use EGLFS?) Thanks a lot for the investigation! I have now committed your changes to the experimental branch, so they will be in the next Qt 5.6 upload. To test it, one can run a Qt app with QT_QPA_PLATFORM=eglfs, and it should use eglfs directly instead of X11 in this case. > I did not encounter the FTBFS seen on kfreebsd-amd64, which must have > been a random thing on the buildd: > https://buildd.debian.org/status/logs.php?pkg=qtbase-opensource-src=5.5.1%2Bdfsg-16=kfreebsd-amd64 Yes, it's a random thing, perhaps a rebuild will fix it. > EGLFS cannot be built yet on hurd-* (without libgbm-dev), so there is > no point adding libgles2-mesa-dev to Build-Depends there. Ack, that's what I figured out myself too. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#816584: texlive-htmlxml: Missing dependency on texlive-generic-recommended
retitle 816584 texlive-htmlxml: Missing dependency on texlive-generic-recommended thanks Hello. My reading of this bug tells me that this title should be ok. (I'm going to reassign and merge some bugs to this one as you suggest in Bug #816517). Thanks.
Bug#570933: dh-buildinfo: should provide a addon file for dh command (debhelper 7 mode)
I've fixed this now, please see the attached diff. Best, DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/ diff -Nru dh-buildinfo-0.11/buildinfo.pm dh-buildinfo-0.11+nmu1/buildinfo.pm --- dh-buildinfo-0.11/buildinfo.pm 1970-01-01 01:00:00.0 +0100 +++ dh-buildinfo-0.11+nmu1/buildinfo.pm 2016-04-03 22:55:49.0 +0200 @@ -0,0 +1,11 @@ +#!/usr/bin/perl +# debhelper addon script for dh-buildinfo +# written in 2016 by Daniel Stender+ +use warnings; +use strict; +use Debian::Debhelper::Dh_Lib; + +insert_after("dh_installdocs", "dh_buildinfo"); + +1 diff -Nru dh-buildinfo-0.11/debian/changelog dh-buildinfo-0.11+nmu1/debian/changelog --- dh-buildinfo-0.11/debian/changelog 2014-05-17 23:45:40.0 +0200 +++ dh-buildinfo-0.11+nmu1/debian/changelog 2016-04-03 23:00:26.0 +0200 @@ -1,3 +1,10 @@ +dh-buildinfo (0.11+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Added sequencer script buildinfo.pm (Closes: #570933). + + -- Daniel Stender Sun, 03 Apr 2016 23:00:18 +0200 + dh-buildinfo (0.11) unstable; urgency=medium * Avoid dups in "pulled by" lines, and sort contents of those for output diff -Nru dh-buildinfo-0.11/debian/rules dh-buildinfo-0.11+nmu1/debian/rules --- dh-buildinfo-0.11/debian/rules 2014-05-17 23:44:54.0 +0200 +++ dh-buildinfo-0.11+nmu1/debian/rules 2016-04-03 23:01:14.0 +0200 @@ -43,7 +43,9 @@ dh_installdirs $(MAKE) install DESTDIR=$(TMP) - + mkdir -p $(TMP)/usr/share/perl5/Debian/Debhelper/Sequence + mv $(TMP)/usr/share/perl5/buildinfo.pm $(TMP)/usr/share/perl5/Debian/Debhelper/Sequence/ + # not the tip of elegance but I don't know how to install this properly with Module::Build # Build architecture-dependent files here. binary-arch: build install
Bug#819881: radeon_fence_ref BUG: unable to handle kernel NULL pointer dereference
Hi, Today, after updating to Debian 8.4, I had the same problem (see below the extract from syslog). So, I reinstalled the previous package 3.16.7-ckt20-1+deb8u4 and everything back to the way it was before. Syslog extrack Apr 3 22:04:45 hpcore2 kernel: [ 3754.417930] BUG: unable to handle kernel NULL pointer dereference at 0008 Apr 3 22:04:45 hpcore2 kernel: [ 3754.417982] IP: [] radeon_fence_ref+0xd/0x50 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.418053] PGD 0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418067] Oops: 0002 [#1] SMP Apr 3 22:04:45 hpcore2 kernel: [ 3754.418090] Modules linked in: bnep bluetooth 6lowpan_iphc snd_hrtimer snd_seq snd_seq_device cfg80211 rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc usblp radeon ttm drm_kms_helper drm i2c_algo_bit pcspkr serio_raw iTCO_wdt iTCO_vendor_support evdev coretemp i2c_i801 i2c_core snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_timer snd lpc_ich mfd_core shpchp soundcore button acpi_cpufreq processor thermal_sys loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 usb_storage sg sd_mod crc_t10dif crct10dif_generic sr_mod cdrom crct10dif_common ata_generic psmouse ata_piix libata scsi_mod firewire_ohci r8169 firewire_core mii crc_itu_t ehci_pci uhci_hcd ehci_hcd usbcore usb_common Apr 3 22:04:45 hpcore2 kernel: [ 3754.418642] CPU: 0 PID: 697 Comm: Xorg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt25-1 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418677] Hardware name: Hewlett-Packard HP Compaq dx2400 Microtower/2A73, BIOS 5.23 04/21/2008 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418716] task: 88007a9db430 ti: 88007a9ec000 task.ti: 88007a9ec000 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418746] RIP: 0010:[] [] radeon_fence_ref +0xd/0x50 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.418796] RSP: 0018:88007a9efb18 EFLAGS: 00010292 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418820] RAX: RBX: 88007961d5f8 RCX: 88007961cd08 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418849] RDX: 0001 RSI: RDI: Apr 3 22:04:45 hpcore2 kernel: [ 3754.418878] RBP: 88007961d550 R08: 88007961c000 R09: Apr 3 22:04:45 hpcore2 kernel: [ 3754.418907] R10: 0002 R11: ffec R12: 0020 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418936] R13: 88007a9efbe0 R14: 88007a9efbb0 R15: 88007961d5f8 Apr 3 22:04:45 hpcore2 kernel: [ 3754.418966] FS: 7f1092278980() GS:88007fc0() knlGS: Apr 3 22:04:45 hpcore2 kernel: [ 3754.419001] CS: 0010 DS: ES: CR0: 80050033 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419024] CR2: 0008 CR3: 7a993000 CR4: 07f0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419054] Stack: Apr 3 22:04:45 hpcore2 kernel: [ 3754.419064] a046c0bc 002c f100 88007a9efcd0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419106] 88007961c000 88007a9db430 88007a9db430 02e0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419147] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419189] Call Trace: Apr 3 22:04:45 hpcore2 kernel: [ 3754.419217] [] ? radeon_sa_bo_new+0x25c/0x460 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419259] [] ? radeon_ib_get+0x2e/0xd0 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419301] [] ? radeon_cs_ioctl+0x13c/0x730 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419340] [] ? drm_ioctl+0x1c7/0x5b0 [drm] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419371] [] ? __do_page_fault+0x1d1/0x4f0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419407] [] ? radeon_drm_ioctl+0x46/0x80 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419437] [] ? do_vfs_ioctl+0x2cf/0x4b0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419463] [] ? SyS_ioctl+0x81/0xa0 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419487] [] ? page_fault+0x28/0x30 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419513] [] ? system_call_fast_compare_end+0x10/0x15 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419543] Code: e4 48 8b 3b 89 c1 89 ea 48 c7 c6 80 b6 4f a0 31 c0 e8 68 57 f9 e0 eb cb 66 0f 1f 44 00 00 66 66 66 66 90 48 89 f8 ba 01 00 00 00 0f c1 57 08 83 c2 01 83 fa 01 7e 01 c3 80 3d 0e 43 11 00 00 Apr 3 22:04:45 hpcore2 kernel: [ 3754.419839] RIP [] radeon_fence_ref+0xd/0x50 [radeon] Apr 3 22:04:45 hpcore2 kernel: [ 3754.419883] RSP Apr 3 22:04:45 hpcore2 kernel: [ 3754.419898] CR2: 0008 Apr 3 22:04:45 hpcore2 kernel: [ 3754.430323] ---[ end trace 6f078410004efac7 ]--- Regards Patrice
Bug#815196: ITP: awlsim -- S7 compatible soft-PLC
On Fri, Mar 04, 2016 at 10:09:08PM +0100, Michael Büsch wrote: > > As I am currently neither debian developer nor debian maintainer, I > will need sponsoring on this package. > Seen that request a month ago and stole this weekend some time ... After a `git clone`, I did `dpkg-checkbuilddeps && dpkg-buildpackage -uc -us` and got running build_scripts dh_auto_test -O--buildsystem=pybuild I: pybuild base:184: cd /home/stappers/src/awlsim/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover -v -- Ran 0 tests in 0.000s OK I: pybuild base:184: cd /home/stappers/src/awlsim/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v awlsim-gui ERROR: Neither PySide nor PyQt found. PLEASE INSTALL PySide (http://www.pyside.org/) or PyQt4 with v2 APIs (http://www.riverbankcomputing.com/software/pyqt/download) or PyQt5 with v2 APIs (http://www.riverbankcomputing.com/software/pyqt/download5) Press enter to exit. What to do to get a "clean build"? If I should have build from a .tar.gz ( not from git ), please tell. Groeten Geert Stappers DD -- Leven en laten leven signature.asc Description: Digital signature
Bug#819859: sawfish: Sawfish quits immediately after shown up
Hi, I don't understand very well your setup. I think it is a problem with systemd, but will try to reproduce it any way. Kind regards Jose M Calhariz On 03/04/16 08:25, Xiaolin Wang wrote: > Package: sawfish > Version: 1:1.11-2 > Severity: important > > Dear Maintainer, > > In my .bash_profile file, the last line is: > > [[ -z $DISPLAY && $XDG_VTNR -eq 6 ]] && exec startx -- vt6 -keeptty > > In my .xsession file, the last line is: > > [[ $XDG_VTNR -eq 6 ]] && exec /etc/alternatives/x-window-manager > > And my x-window-manager points to sawfish. > > In /etc/systemd/system/getty.target.wants/ I've set up auto login for > all my tty1-6. > > The above configuration works great for years until a few weeks ago I > did an usual 'sudo aptitude upgrade'. > > In these days, after startx brings up X display, I can see the mouse pointer > shows up at the center of the screen. > This means sawfish has been working. But immediately after the mouse cursor > shown up, sawfish quits, the screen > goes back to console tty1. Because I have auto login on tty1-6, startx > works again to bring up X. And immediately after seeing the mouse > cursor, sawfish quits again. And the screen goes back to tty1. This loop > continues until I comments out the last line in my .bash_profile file. > > grep EE ~/.local/share/xorg/Xorg.0.log shows me the following lines: > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 156.708] (EE) Error systemd-logind returned paused fd for > drm node > [ 157.188] (EE) Error systemd-logind returned paused fd for > drm node > > If I 'startx' manually at any tty, I got the following errors: > > (EE) Fatal server error: > (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied) > (EE) > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > (EE) Please also check the log file at > "/home/wx672/.local/share/xorg/Xorg.0.log" for additional > information. > (EE) > (EE) Server terminated with error (1). Closing log file. > xinit: giving up > xinit: unable to connect to X server: Connection refused > xinit: server error > > > Then, I switched to i3 window manager, it works fine. So I guess it > could be a sawfish bug. > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages sawfish depends on: > ii libatk1.0-0 2.18.0-1 > ii libc62.22-5 > ii libcairo21.14.6-1 > ii libfontconfig1 2.11.0-6.4 > ii libfreetype6 2.6.3-3 > ii libgdk-pixbuf2.0-0 2.32.3-1.2 > ii libglib2.0-0 2.48.0-1 > ii libgmp10 2:6.1.0+dfsg-2 > ii libgtk2.0-0 2.24.30-1.1 > ii libice6 2:1.0.9-1+b1 > ii libpango-1.0-0 1.38.1-1 > ii libpangocairo-1.0-0 1.38.1-1 > ii libpangoft2-1.0-01.38.1-1 > ii libpangoxft-1.0-01.38.1-1 > ii librep16 0.92.5-3 > ii libsm6 2:1.2.2-1+b1 > ii libx11-6 2:1.6.3-1 > ii libxext6 2:1.3.3-1 > ii libxft2 2.3.2-1 > ii libxinerama1 2:1.1.3-1+b1 > ii libxrandr2 2:1.5.0-1 > ii libxrender1 1:0.9.9-2 > ii libxtst6 2:1.2.2-1+b1 > ii rep 0.92.5-3 > ii rep-gtk 1:0.90.8.2-3 > ii sawfish-data 1:1.11-2 > ii xterm [x-terminal-emulator] 324-1 > > sawfish recommends no packages. > > Versions of packages sawfish suggests: > pn gnome-control-center > pn menu > pn yelp > > -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#819914: imagemagick: please honour SOURCE_DATE_EPOCH
Source: imagemagick Version: 8:6.8.9.9-7 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: toolchain X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, While working on the “reproducible builds” effort [1], we have noticed that some packages (like kannel) use 'convert' in their building process, resulting in timestamps in postscript files that break reproducibility. To solve this kind of issues, it would be nice to have 'convert' support the SOURCE_DATE_EPOCH environment variable [2]. See the attached patch for a solution to this issue. Regards, Alexis Bienvenüe. [1] https://wiki.debian.org/ReproducibleBuilds [2] https://reproducible-builds.org/specs/source-date-epoch/ diff -Nru imagemagick-6.8.9.9/debian/changelog imagemagick-6.8.9.9/debian/changelog --- imagemagick-6.8.9.9/debian/changelog 2016-01-17 21:45:14.0 +0100 +++ imagemagick-6.8.9.9/debian/changelog 2016-04-01 01:11:37.0 +0200 @@ -1,3 +1,10 @@ +imagemagick (8:6.8.9.9-7.0reproducible1) unstable; urgency=medium + + * Honour the SOURCE_DATE_EPOCH environment variable +when writing to files. + + -- Alexis BienvenüeFri, 01 Apr 2016 01:11:36 +0200 + imagemagick (8:6.8.9.9-7) unstable; urgency=low * Fix various minor security issues diff -Nru imagemagick-6.8.9.9/debian/patches/0076-Honour-SOURCE_DATE_EPOCH-when-writing.patch imagemagick-6.8.9.9/debian/patches/0076-Honour-SOURCE_DATE_EPOCH-when-writing.patch --- imagemagick-6.8.9.9/debian/patches/0076-Honour-SOURCE_DATE_EPOCH-when-writing.patch 1970-01-01 01:00:00.0 +0100 +++ imagemagick-6.8.9.9/debian/patches/0076-Honour-SOURCE_DATE_EPOCH-when-writing.patch 2016-04-03 15:48:56.0 +0200 @@ -0,0 +1,307 @@ +Description: Honour the SOURCE_DATE_EPOCH variable when writing + Honour the SOURCE_DATE_EPOCH environment variable when writing + to some files: PS, PDF, PNG, CIN, DPX, MAT, PDB, setting the timestamp + to the provided value and using GM time instead of local time. +Author: Alexis Bienvenüe + +Index: imagemagick-6.8.9.9/coders/cin.c +=== +--- imagemagick-6.8.9.9.orig/coders/cin.c imagemagick-6.8.9.9/coders/cin.c +@@ -971,14 +971,14 @@ static MagickBooleanType WriteCINImage(c + sizeof(cin.file.filename)); + offset+=WriteBlob(image,sizeof(cin.file.filename),(unsigned char *) + cin.file.filename); +- seconds=time((time_t *) NULL); +-#if defined(MAGICKCORE_HAVE_LOCALTIME_R) +- (void) localtime_r(,_time); +-#else +- (void) memcpy(_time,localtime(),sizeof(local_time)); +-#endif ++ seconds=CurrentTime(); ++ (void) LocalOrGMTime(,_time); + (void) memset(timestamp,0,sizeof(timestamp)); +- (void) strftime(timestamp,MaxTextExtent,"%Y:%m:%d:%H:%M:%S%Z",_time); ++ if(getenv("SOURCE_DATE_EPOCH")) { ++(void) strftime(timestamp,MaxTextExtent,"%Y:%m:%d:%H:%M:%SUTC",_time); ++ } else { ++(void) strftime(timestamp,MaxTextExtent,"%Y:%m:%d:%H:%M:%S%Z",_time); ++ } + (void) memset(cin.file.create_date,0,sizeof(cin.file.create_date)); + (void) CopyMagickString(cin.file.create_date,timestamp,11); + offset+=WriteBlob(image,sizeof(cin.file.create_date),(unsigned char *) +@@ -1074,9 +1074,6 @@ static MagickBooleanType WriteCINImage(c + sizeof(cin.origination.filename)); + offset+=WriteBlob(image,sizeof(cin.origination.filename),(unsigned char *) + cin.origination.filename); +- seconds=time((time_t *) NULL); +- (void) memset(timestamp,0,sizeof(timestamp)); +- (void) strftime(timestamp,MaxTextExtent,"%Y:%m:%d:%H:%M:%S%Z",_time); + (void) memset(cin.origination.create_date,0, + sizeof(cin.origination.create_date)); + (void) CopyMagickString(cin.origination.create_date,timestamp,11); +Index: imagemagick-6.8.9.9/coders/dpx.c +=== +--- imagemagick-6.8.9.9.orig/coders/dpx.c imagemagick-6.8.9.9/coders/dpx.c +@@ -1535,7 +1535,7 @@ static MagickBooleanType WriteDPXImage(c + (void) strncpy(dpx.file.filename,value,sizeof(dpx.file.filename)-1); + offset+=WriteBlob(image,sizeof(dpx.file.filename),(unsigned char *) + dpx.file.filename); +- seconds=time((time_t *) NULL); ++ seconds=CurrentTime(); + (void) FormatMagickTime(seconds,sizeof(dpx.file.timestamp), + dpx.file.timestamp); + offset+=WriteBlob(image,sizeof(dpx.file.timestamp),(unsigned char *) +Index: imagemagick-6.8.9.9/coders/mat.c +=== +--- imagemagick-6.8.9.9.orig/coders/mat.c imagemagick-6.8.9.9/coders/mat.c +@@ -1224,12 +1224,8 @@ static MagickBooleanType WriteMATImage(c + return(MagickFalse); + image->depth=8; + +- current_time=time((time_t *) NULL); +-#if defined(MAGICKCORE_HAVE_LOCALTIME_R) +- (void) localtime_r(_time,_time); +-#else +- (void) memcpy(_time,localtime(_time),sizeof(local_time)); +-#endif ++ current_time=CurrentTime();
Bug#819902: RM: automake-1.14 -- RoQA; superseded by automake-1.15
On Sun, Apr 03, 2016 at 02:11:17PM -0400, Eric Dorland wrote: > It's unclear to me why it wasn't removed automatically when it no > longer had any binary packages in the archive. Is that a bug? TTBOMK, dak never removed anything automatically. Fairly recently it started to automatically remove *some* cruft (NBS and NVIU), but still only binaries, not sources. But to me it's unclear which is the gain of moving from a source package to another with every major version? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#271509: perl fails to warn about incorrect filehandle usage
On Mon, Sep 27, 2004 at 05:49:19PM +1000, Brendan O'Dea wrote: > On Mon, Sep 13, 2004 at 11:54:34PM +1000, Anand Kumria wrote: > >I was mucking about playing with filehandles and discovered that in a.pl > >the output is incorrect whereas perl warns me about bad usage in b.pl > > [a.pl] print $bar, "q\n"; > [b.pl] print BAR, "q\n"; > > >They do, in essence, the same thing. > > The difference is that the syntax in b.pl is unambiguously incorrect, > hence may be (and is) detected at compile-time as an error. By > comparison, the syntax of a.pl is perfectly legal--consider: > > $bar = "hello, world"; > print $bar, "\n"; I'm not sure if this old bug should be kept open as a request for a runtime warning when printing out a stringified file handle, or just closed as a non-bug. Opinions? -- Niko Tyni nt...@debian.org
Bug#819329: [Pkg-xfce-devel] Bug#819329: light-locker: Computer locked by frozen screen after sleep
On Tue, 29 Mar 2016 21:55:23 +0200 Yves-Alexis Perezwrote: The option of 'the graphic stack' might be true. My laptop (Dell Inspiron 1525) contains an Intel GM965/GL960 Integrated Graphics Controller, that seems famous ;-) A frequent warning at that time is shown in the attachment. What log-file could help? Trying to gain remote access to the system is little difficult at the moment, sorry. Regards, Gert > control: tag -1 -d-i moreinfo unreproducible > > On sam., 2016-03-26 at 20:04 +, Gert N wrote: > > I use light-locker with openbox. The computer becomes unreachable after > > sleep > > or hibernate; the screen is frozen and the computer locked. Only a hard > > reboot > > makes the computer available again. > > Remove of light-locker solves the issue. Without light-locker is the > > computer > > waking up well. > > light-locker only shows a locked message on the current vt, and switches to a > login vt. It's quite unlikely to freeze anything, unless you have a problem > with the graphic stack for example. > > There's not much we can do here without more information, so please try to > gain remote access to the system, get logs or anything. > > Regards, > -- > Yves-Alexis > log1 Description: log1
Bug#793818: Pcmanfm crash sometimes at the end of file(s) copy
Thank you very much for the backtrace provided, I'll start from it and let you know when fix is available.
Bug#819913: ITP: imagesize_py -- Getting image size from png/jpeg/jpeg2000/gif file
Package: wnpp Severity: wishlist Owner: Dmitry Shachnev* Package name: imagesize_py Version : 0.7.0 Upstream Author : Yoshiki Shibukawa * URL : https://github.com/shibukawa/imagesize_py * License : MIT Programming Lang: Python Description : Getting image size from png/jpeg/jpeg2000/gif file This small module parses image header and returns width and height of the image. Supported formats are: PNG/JPEG/JPEG2000/GIF. It is needed for the latest Sphinx release, 1.4. This package will be maintained under DPMT umbrella. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#819912: jessie-pu: package postgresql-9.1/9.1.21-0+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hi, I've uploaded postgresql-9.1/9.1.21-0+deb8u1 for inclusion into jessie. As usual, that upload is needed to follow the postgresql-9.1/9.1.21-0+deb7u1 upload in wheezy-pu (see #819805). postgresql-9.1 (9.1.21-0+deb8u1) jessie; urgency=medium * New upstream version, relevant PL/Perl change: + Correctly handle empty arrays in plperl_ref_from_pg_array. -- Christoph BergSat, 02 Apr 2016 16:16:53 +0200 (The good news is that we won't be doing the plperl dance anymore in future releases, tests have shown that PostgreSQL clusters are upgradeable even without plperl.so present. I guess we could even remove postgresql-(plperl-)9.1 from jessie if we adjusted the release notes.) Christoph
Bug#813850: RFS: amanda/3.3.8-1 -- Advanced Maryland Automatic Network Disk Archiver
On 28/03/16 15:21, Mattia Rizzolo wrote: > Is there something blocking on this? > (gentle ping) > Everything sorted out, and the last changes were pushed to the git repo. Kind regards Jose M Calhariz signature.asc Description: OpenPGP digital signature
Bug#819911: transfig: please honour SOURCE_DATE_EPOCH
Source: transfig Version: 1:3.2.5.e-5 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: toolchain X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, While working on the “reproducible builds” effort [1], we have noticed that some packages (like kannel) use fig2dev in their building process, resulting in timestamps in postscript files that break reproducibility. To solve this kind of issues, it would be nice to have transfig support the SOURCE_DATE_EPOCH environment variable [2]. See the attached patch for a solution to this issue. Regards, Alexis Bienvenüe. [1] https://wiki.debian.org/ReproducibleBuilds [2] https://reproducible-builds.org/specs/source-date-epoch/ diff -Nru transfig-3.2.5.e/debian/changelog transfig-3.2.5.e/debian/changelog --- transfig-3.2.5.e/debian/changelog 2016-01-30 11:49:30.0 +0100 +++ transfig-3.2.5.e/debian/changelog 2016-04-03 16:42:27.0 +0200 @@ -1,3 +1,9 @@ +transfig (1:3.2.5.e-5.0~reproducible1) unstable; urgency=medium + + * Honour SOURCE_DATE_EPOCH environment variable + + -- Alexis BienvenüeSun, 03 Apr 2016 16:42:27 +0200 + transfig (1:3.2.5.e-5) unstable; urgency=medium * Upgrade to Standards-Version 3.9.6 (no changes). diff -Nru transfig-3.2.5.e/debian/patches/33_honour_SOURCE_DATE_EPOCH.patch transfig-3.2.5.e/debian/patches/33_honour_SOURCE_DATE_EPOCH.patch --- transfig-3.2.5.e/debian/patches/33_honour_SOURCE_DATE_EPOCH.patch 1970-01-01 01:00:00.0 +0100 +++ transfig-3.2.5.e/debian/patches/33_honour_SOURCE_DATE_EPOCH.patch 2016-04-03 19:11:44.0 +0200 @@ -0,0 +1,147 @@ +Description: Honour SOURCE_DATE_EPOCH variable + Honour SOURCE_DATE_EPOCH environment variable when creating + PS and pictex files. +Author: Alexis Bienvenüe + +Index: transfig-3.2.5.e/fig2dev/dev/genpictex.c +=== +--- transfig-3.2.5.e.orig/fig2dev/dev/genpictex.c transfig-3.2.5.e/fig2dev/dev/genpictex.c +@@ -125,7 +125,6 @@ genpictex_start(objects) + F_compound *objects; + { + char host[256]; +- time_t when; + struct passwd *who; + + texfontsizes[0] = texfontsizes[1] = +@@ -135,12 +134,11 @@ F_compound *objects; + + /* announce filename, version etc */ + +- (void) time(); + fprintf(tfp, "%%Title: %s\n", + (name? name: ((from) ? from : "stdin"))); + fprintf(tfp, "Created by: %s Version %s Patchlevel %s\n", + prog, VERSION, PATCHLEVEL); +- fprintf(tfp, "CreationDate: %s", ctime()); ++ fprintf(tfp, "CreationDate: %s", creation_date()); + if (gethostname(host, sizeof(host)) == -1) + (void)strcpy(host, "unknown-host!?!?"); + if ( !anonymous) { +Index: transfig-3.2.5.e/fig2dev/dev/genps.c +=== +--- transfig-3.2.5.e.orig/fig2dev/dev/genps.c transfig-3.2.5.e/fig2dev/dev/genps.c +@@ -456,7 +456,6 @@ F_compound *objects; + { + char host[256]; + struct passwd *who; +- time_t when; + int itmp, jtmp; + int i; + int cliplx, cliply, clipux, clipuy; +@@ -626,12 +625,11 @@ F_compound *objects; + + if (gethostname(host, sizeof(host)) == -1) + (void)strcpy(host, "unknown-host!?!?"); +- (void) time(); + fprintf(tfp, "Title: %s\n", + (name? name: ((from) ? from : "stdin"))); + fprintf(tfp, "Creator: %s Version %s Patchlevel %s\n", + prog, VERSION, PATCHLEVEL); +- fprintf(tfp, "CreationDate: %s", ctime()); ++ fprintf(tfp, "CreationDate: %s", creation_date()); + if ( !anonymous) { + who = getpwuid(getuid()); + if (who) +Index: transfig-3.2.5.e/fig2dev/dev/readjpg.c +=== +--- transfig-3.2.5.e.orig/fig2dev/dev/readjpg.c transfig-3.2.5.e/fig2dev/dev/readjpg.c +@@ -92,7 +92,6 @@ void + JPEGtoPS(char *jpegfile, FILE *PSfile) { + imagedata *JPEG; + size_t n; +- time_t t; + int i, filtype; + char realname[PATH_MAX]; + +@@ -101,13 +100,11 @@ JPEGtoPS(char *jpegfile, FILE *PSfile) { + /* reopen the file */ + JPEG->fp = open_picfile(jpegfile, , True, realname); + +- time(); +- + /* produce EPS header comments */ + fprintf(PSfile, "%%!PS-Adobe-3.0 EPSF-3.0\n"); + fprintf(PSfile, "Creator: jpeg2ps %s by Thomas Merz\n", VERSION); + fprintf(PSfile, "Title: %s\n", JPEG->filename); +- fprintf(PSfile, "CreationDate: %s", ctime()); ++ fprintf(PSfile, "CreationDate: %s", creation_date()); + fprintf(PSfile, "BoundingBox: %d %d %d %d\n", +0, 0, JPEG->width, JPEG->height); + fprintf(PSfile, "DocumentData: %s\n", +Index: transfig-3.2.5.e/fig2dev/fig2dev.c +=== +--- transfig-3.2.5.e.orig/fig2dev/fig2dev.c transfig-3.2.5.e/fig2dev/fig2dev.c +@@ -31,6 +31,8 @@ + #include "drivers.h" + #include "bound.h" + #include "read.h" ++#include ++#include + + extern int
Bug#819910: Call trace in dmesg with Debian SID
control: reassign -1 src:linux On Sun, Apr 03, 2016 at 09:40:32PM +0200, raccoon wrote: > Package: kernelVersion: 4.4.0-1-amd64 Please don't use HTML in your email to debian, you make the tooling grumpy and they don't parse it, and it requires more manual work for us. Also 1) "kernel" is not the name of a package (there is a linux *source* packages (which requires src: if you want to use it, as I did above) 2) version has to be the version of the debian package, not the one of the ABI. > After fresh install of debian sid (Debian 4.4.6-1 (2016-03-17)), i got > following call trace in dmesg > > http://pastebin.com/wYpFerdH > > I'm using Linux 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) > x86_64 GNU/Linux everybody hates pastebin.com around here, and there is no reason to use it if you use a sane MUA. I'm going to append it at the bottom of my email. With this email, I'm redirecting you misfiled bug report to the attention of linux maintainers. Thanks for taking the time for filing a bug and helping making Debian (and Linux) better. from http://pastebin.com/raw/wYpFerdH : [3.613219] [ cut here ] [3.613239] WARNING: CPU: 3 PID: 730 at /build/linux-dFNWCu/linux-4.4.6/drivers/gpu/drm/drm_atomic_helper.c:1782 __drm_atomic_helper_set_config+0x20a/0x3c0 [drm_kms_helper]() [3.613240] Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic stv6110x intel_rapl lnbp21 iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep stv090x snd_pcm aesni_intel eeepc_wmi snd_timer aes_x86_64 asus_wmi lrw sparse_keymap gf128mul iTCO_wdt i915 glue_helper iTCO_vendor_support rfkill ddbridge ablk_helper snd drm_kms_helper cryptd serio_raw dvb_core pcspkr soundcore sg i2c_i801 drm mei_me i2c_algo_bit mei lpc_ich shpchp mfd_core wmi 8250_fintek battery tpm_infineon video tpm_tis tpm button processor evdev joydev autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid dm_snapshot dm_bufio dm_mod sd_mod xhci_pci [3.613280] ehci_pci xhci_hcd ehci_hcd crc32c_intel ahci libahci libata psmouse scsi_mod r8169 e1000e mii ptp usbcore pps_core usb_common fan thermal fjes [3.613289] CPU: 3 PID: 730 Comm: Xorg Not tainted 4.4.0-1-amd64 #1 Debian 4.4.6-1 [3.613290] Hardware name: ASUS All Series/Q87T, BIOS 0914 12/10/2015 [3.613291] 0286 69d7eacf 812ea865 [3.613293] a04e2940 810774fd 8804081a9b80 88040995ee00 [3.613294] 88040c476d00 88040801ac00 8800d369a000 a04dbdca [3.613296] Call Trace: [3.613304] [] ? dump_stack+0x5c/0x77 [3.613307] [] ? warn_slowpath_common+0x7d/0xb0 [3.613311] [] ? __drm_atomic_helper_set_config+0x20a/0x3c0 [drm_kms_helper] [3.613314] [] ? restore_fbdev_mode+0x215/0x250 [drm_kms_helper] [3.613352] [] ? drm_modeset_lock_all_crtcs+0x87/0xa0 [drm] [3.613357] [] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x70 [drm_kms_helper] [3.613420] [] ? intel_fbdev_restore_mode+0x1e/0x80 [i915] [3.613441] [] ? i915_driver_lastclose+0xa/0x10 [i915] [3.613447] [] ? drm_lastclose+0x29/0x130 [drm] [3.613453] [] ? drm_release+0x2a3/0x480 [drm] [3.613455] [] ? __fput+0xca/0x1d0 [3.613457] [] ? task_work_run+0x71/0x90 [3.613459] [] ? exit_to_usermode_loop+0xba/0xc0 [3.613462] [] ? int_ret_from_sys_call+0x25/0x8f [3.613463] ---[ end trace 8a9bc9ac7e372976 ]--- [3.613468] [ cut here ] [3.613472] WARNING: CPU: 3 PID: 730 at /build/linux-dFNWCu/linux-4.4.6/drivers/gpu/drm/drm_atomic_helper.c:1782 __drm_atomic_helper_set_config+0x20a/0x3c0 [drm_kms_helper]() [3.613473] Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic stv6110x intel_rapl lnbp21 iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep stv090x snd_pcm aesni_intel eeepc_wmi snd_timer aes_x86_64 asus_wmi lrw sparse_keymap gf128mul iTCO_wdt i915 glue_helper iTCO_vendor_support rfkill ddbridge ablk_helper snd drm_kms_helper cryptd serio_raw dvb_core pcspkr soundcore sg i2c_i801 drm mei_me i2c_algo_bit mei lpc_ich shpchp mfd_core wmi 8250_fintek battery tpm_infineon video tpm_tis tpm button processor evdev joydev autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid dm_snapshot dm_bufio dm_mod sd_mod xhci_pci [3.613492] ehci_pci xhci_hcd ehci_hcd crc32c_intel ahci libahci libata psmouse scsi_mod r8169 e1000e mii ptp usbcore pps_core usb_common fan thermal fjes [3.613497] CPU: 3 PID: 730 Comm: Xorg Tainted: GW 4.4.0-1-amd64 #1 Debian 4.4.6-1 [3.613498] Hardware name: ASUS All Series/Q87T,
Bug#819548: gnome-maps fails to start
Sun, 3 Apr 2016 14:41:44 +0200 Andreas Henrikssonécrivait : > Hello again! Hi Andreas, > > mlundblad mentioned to me on IRC that he has identified the culprit > as gjs in testing not being new enough. Please confirm that upgrading > to gjs from unstable fixes the problem for you. I installed gjs 1.44.0-1 and (+ its dependency libgjs0e 1.44.0-1) from unstable and it solved the issue. Gnome Maps start without any problems. > > (This issue has been fixed upstream in gnome-maps at: > https://git.gnome.org/browse/gnome-maps/commit/?id=f735490a47afbf > and I'll add the equivalent dependency to the debian package shortly.) > > Regards, Thank you so much to you and mlundblad on IRC. Kindest regards, > Andreas Henriksson Jean-Marc pgpkD30RBDG0G.pgp Description: PGP signature
Bug#819910: Call trace in dmesg with Debian SID
Package: kernelVersion: 4.4.0-1-amd64 After fresh install of debian sid (Debian 4.4.6-1 (2016-03-17)), i got following call trace in dmesg http://pastebin.com/wYpFerdH I'm using Linux 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 GNU/Linux
Bug#819908: Pending fixes for bugs in the libredis-perl package
tag 819908 + pending thanks Some bugs in the libredis-perl package are closed in revision f9388f75c0ed1ae283a89f77b353c514d47e859a in branch 'master' by Niko Tyni The full diff can be seen at https://anonscm.debian.org/cgit/pkg-perl/packages/libredis-perl.git/commit/?id=f9388f7 Commit message: Add patch from Syohei YOSHIDA fixing locale related build failures. Closes: #819908
Bug#819908: libredis-perl: FTBFS in non-English locales: t/11-timeout.t failure
Package: libredis-perl Version: 2:1.9820-1 Severity: important Tags: upstream patch Forwarded: https://github.com/PerlRedis/perl-redis/issues/111 User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs locale X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org This package fails to build in non-English locales. >From >https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/libredis-perl.html # Failed test 'the code died as expected' # at t/11-timeout.t line 41. # 'Error while reading from Redis server: Resource temporarily unavailable at t/11-timeout.t line 40. # ' # doesn't match '(?^u:Error while reading from Redis server: Connexion termin�e par expiration du d�lai d'attente|Error while reading from Redis server: Ressource temporairement non disponible)' # Looks like you failed 1 test of 2. The test script is calling POSIX::strerror() for two errno values, getting locale dependent strings, and comparing them to the non-locale-dependent return value of Redis->get(). This is https://github.com/PerlRedis/perl-redis/issues/111 and the attached patch is from https://github.com/PerlRedis/perl-redis/pull/112 (not yet merged upstream). -- Niko Tyni nt...@debian.org >From 155f19bd998cb1350dd067ec7b8c06738f9484e3 Mon Sep 17 00:00:00 2001 From: Syohei YOSHIDADate: Tue, 9 Jun 2015 12:26:49 +0900 Subject: [PATCH] Compare error number instead of error message for locale This test may be failed if test platform is not English locale. So we should compare error number rather than error message. --- t/11-timeout.t | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/t/11-timeout.t b/t/11-timeout.t index bc0268b..166bbfa 100644 --- a/t/11-timeout.t +++ b/t/11-timeout.t @@ -25,13 +25,12 @@ subtest "server doesn't replies quickly enough" => sub { my $server = Test::SpawnRedisTimeoutServer::create_server_with_timeout(10); my $redis = Redis->new(server => '127.0.0.1:' . $server->port, read_timeout => 1); ok($redis); -my $msg1 = "Error while reading from Redis server: " . strerror(ETIMEDOUT); -my $msg2 = "Error while reading from Redis server: " . strerror(EWOULDBLOCK); like( exception { $redis->get('foo'); }, - qr/$msg1|$msg2/, + qr/Error while reading from Redis server: /, "the code died as expected", ); +ok($! == ETIMEDOUT || $! == EWOULDBLOCK); }; subtest "server doesn't respond at connection (cnx_timeout)" => sub {
Bug#819844: message should mention that it is possible to restart without asking
On 2016-04-03 07:48, 積丹尼 Dan Jacobson wrote: > Package: libc6 > Version: 2.23-0experimental1 > Severity: wishlist > > Every upgrade the upgrade stops and the operator must walk over and > press return to get it started again. > > The message shown about restarting services exim4 cron atd should also > mention how/that one can also restart without asking. There is already debconf question to avoid getting asked at each upgrade. If you answer yes, the services are restarted without asking. I don't really understand what you want more. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#819907: gitlab: builds fails, /usr/share/gitlab/builds is not writeable
Maybe, it should rather go to logs dir Patch v2 attached, again, untested ;) Libor diff -ur a/debian/gitlab.links b/debian/gitlab.links --- a/debian/gitlab.links 2016-03-13 07:21:05.0 +0100 +++ b/debian/gitlab.links 2016-04-03 20:58:06.683043165 +0200 @@ -1,6 +1,7 @@ var/lib/gitlab/public usr/share/gitlab/public var/lib/gitlab/cache usr/share/gitlab/shared/cache var/log/gitlab usr/share/gitlab/log +var/log/gitlab/builds usr/share/gitlab/builds run/gitlab usr/share/gitlab/tmp etc/gitlab usr/share/gitlab/config usr/share/javascript/jquery-history/jquery.history.min.js usr/share/gitlab/vendor/assets/javascripts/jquery.history.js diff -ur a/debian/postinst b/debian/postinst --- a/debian/postinst 2016-02-18 18:12:11.0 +0100 +++ b/debian/postinst 2016-04-03 21:00:37.922038434 +0200 @@ -39,13 +39,14 @@ # Create gitlab user . /usr/lib/gitlab/scripts/adduser.sh +gitlab_builds_log=${gitlab_log_dir}/builds gitlab_repo_path=${gitlab_data_dir}/repositories gitlab_cache_path=${gitlab_data_dir}/cache gitlab_uploads_path=${gitlab_data_dir}/public/uploads # Create directories and change ownership for i in ${gitlab_repo_path} ${gitlab_cache_path} ${gitlab_uploads_path}\ -${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log}; do +${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log} ${gitlab_builds_log}; do mkdir -p $i chown -R ${gitlab_user}: $i done
Bug#658988: ITP: libvirt-sandbox -- API layer which facilitates the creation of application
[Guido Günther] > This needs a lot more work but I wanted a quick package, so I've pushed > the current state here: > > https://github.com/agx/libvirt-sandbox-debian And the latest news is available from http://honk.sigxcpu.org/con/More_sandboxing.html >. Thank you very much for getting it ready for upload. The system look just what I need for some systems I need to run. I tried building the package in Jessie, but it require newer versions of some dependencies. :( -- Happy hacking Petter Reinholdtsen
Bug#814167: lwjgl: (Build-)Depends on OpenJDK 7
On Sun, Apr 03, 2016 at 08:44:00PM +0200, Markus Koschany wrote: > There are only very few packages left that build-depend or depend on > OpenJDK 7. Yes. >I fixed two of them last week with an NMU and QA upload but > the rest are either candidates for removal or they can be fixed later. > In my opinion we should just remove OpenJDK 7, no need to wait for fixes. Today I asked RM for 2, asked 2 others if their maintainers can go on with RM themselves or I'd do during the week, and poke other 2 (including this) that could (potentially) be fixed. Then we're free to go. Probably if this one is the only one left we can also consider to just break it and leave it broken. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: http://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#819907: gitlab: builds fails, /usr/share/gitlab/builds is not writeable
Package: gitlab Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, builds seems to fail, because it has no dir to write to Errno::EACCES (Permission denied @ dir_s_mkdir - /usr/share/gitlab/builds): /usr/lib/ruby/2.3.0/fileutils.rb:253:in `mkdir' /usr/lib/ruby/2.3.0/fileutils.rb:253:in `fu_mkdir' /usr/lib/ruby/2.3.0/fileutils.rb:227:in `block (2 levels) in mkdir_p' /usr/lib/ruby/2.3.0/fileutils.rb:225:in `reverse_each' /usr/lib/ruby/2.3.0/fileutils.rb:225:in `block in mkdir_p' /usr/lib/ruby/2.3.0/fileutils.rb:211:in `each' /usr/lib/ruby/2.3.0/fileutils.rb:211:in `mkdir_p' /usr/share/gitlab/app/models/ci/build.rb:229:in `trace=' etc... Here is (untested) patch to build system, to create /var/lib/gitlab/builds and create symlink to /usr/share/gitlab/builds Libor - -- System Information: Debian Release: stretch/sid APT prefers experimental APT policy: (700, 'experimental'), (700, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJXAWX+AAoJEPDvjG7Cn0eOUpEQAJeqzWih80/WgbZvVkfSFG3W +7eYJQth/M7vA3tcAGd0mr1Uh8yETILltyW3jB5BoDs0xenHI+WbiL6gfXU+U2aW MDm9+QjPOFJrq/aq9nea5DYxcQkjdEuiyoZU8Q1EJM+iDfqGo1JUtxpXIthBIKxA rg4aH382btXc9xlnOZPijtWi2Ba84O7Lj6gpXPg6ZntCXkLpos3KUmXMVM0wQOJB VNgHf2Eue8Ldp2UC9xjtoHTSxHHg4j/u5ZkqPfvQhcS76dpj9Odal5fKiKMrLdtJ uzS8mmRlNoNIu0xOMmQrTihJO15TPcLQSHdCaGQ1lavR8XGiFRUbv+mafvWfTBqZ tVmAy3veFRp6c6CP60AroTY/qTDp6o2GCOvNkNskXGlJsu0TyNlKlb4AvT/OsnLI 5ZabfPIScSLA25RZ72VTr5896ghm0ndKd7BwQqvCYfLXj8C0Ea22pXmwKXKAHNpD qfqVP/na81dwmCnWPO3IBjgCxUaTxIx9KA6Pjt6Z1Ga3ti4KnuYsQ/SRRa6+KEK0 O7ea/kXc2iSh1J2pjjX+12ZVuvhWDU1l3eVub53ZkznBGnRgxcfNnSTvleLd3xET 6LjbA8uj9mKLvPi7Cf0W1B9yIHr6KlEZnLsMVuVVGW8YS7x6pXI/kBCubGVIZwmy WWXR6AWTwI1AdI1t4hrA =qPhr -END PGP SIGNATURE- diff -ur a/debian/gitlab.links b/debian/gitlab.links --- a/debian/gitlab.links 2016-03-13 07:21:05.0 +0100 +++ b/debian/gitlab.links 2016-04-03 20:46:49.909653752 +0200 @@ -1,3 +1,4 @@ +var/lib/gitlab/builds usr/share/gitlab/builds var/lib/gitlab/public usr/share/gitlab/public var/lib/gitlab/cache usr/share/gitlab/shared/cache var/log/gitlab usr/share/gitlab/log diff -ur a/debian/postinst b/debian/postinst --- a/debian/postinst 2016-02-18 18:12:11.0 +0100 +++ b/debian/postinst 2016-04-03 20:46:29.941259066 +0200 @@ -40,11 +40,12 @@ . /usr/lib/gitlab/scripts/adduser.sh gitlab_repo_path=${gitlab_data_dir}/repositories +gitlab_builds_path=${gitlab_data_dir}/builds gitlab_cache_path=${gitlab_data_dir}/cache gitlab_uploads_path=${gitlab_data_dir}/public/uploads # Create directories and change ownership -for i in ${gitlab_repo_path} ${gitlab_cache_path} ${gitlab_uploads_path}\ +for i in ${gitlab_repo_path} ${gitlab_builds_path} ${gitlab_cache_path} ${gitlab_uploads_path}\ ${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log}; do mkdir -p $i chown -R ${gitlab_user}: $i
Bug#814167: lwjgl: (Build-)Depends on OpenJDK 7
Am 03.04.2016 um 20:31 schrieb Mattia Rizzolo: > On Sat, Mar 12, 2016 at 01:48:27PM -0500, Michael Gilbert wrote: >> On Wed, Mar 9, 2016 at 10:20 AM, Markus Koschany wrote: >>> https://github.com/JetBrains/kotlin >>> >>> This one seems to be the blocker because kotlin build-depends on >>> components of IntelliJ IDEA and all in all that's a lot of stuff for a >>> mere library. >> >> This is the huge dependency stack that I was referring to. >> >>> But perhaps I am missing something and it is much simpler... >> >> Possibly, I only did a quick look at it a while ago, so I don't know >> if it's the only approach. > > Any progress on this? > There are very few rdeps of openjdk-7 left (and today I'm poking them). I will try if I can package the latest version of the 2.x series instead. Perhaps this might fix this bug as well. I don't know when I will get to it though. There are only very few packages left that build-depend or depend on OpenJDK 7. I fixed two of them last week with an NMU and QA upload but the rest are either candidates for removal or they can be fixed later. In my opinion we should just remove OpenJDK 7, no need to wait for fixes. Markus signature.asc Description: OpenPGP digital signature