Bug#1059923: marked as done (spread-sheet-widget_0.10-1_s390x-buildd.changes REJECTED)

I disabled that the upstream changelog file is distributed in the debian package. The spread-sheet-widget provides two binary packages libspread-sheet-widget and libspread-sheet-widget-dev and both usually have the same changelog.gz which is derived from ChangeLog in the source directory. I

Bug#1051243: texlive-binaries -8 version fixed the problem

The problem is gone with the -8 release of texlive-binaries. Thanks!!!

Bug#1051243: texlive-binaries needs rebuild due to update of zlib to 1.3

I did a rebuild of texlive-binaries from source. Then I installed the created packages. The build environment contains zlib1g-dev 1.3-dfsg2. Then "apt install texlive-plain-generic“ will work. So texlive needs a rebuild due to the zlib version update as texlive seems to remember which version

Bug#1051243: PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)

The previous error messages showed that the locale was not configured. I configured the locale but the problem persists but now with an additional PANIC: /tmp/fmtutil.kYG8CZ8c No pages of output. Transcript written on pdfetex.log. fmtutil [INFO]: log file copied to:

Bug#1051243: This affects the build of the pspp package

Hi all, i noticed a failure in our CI pipeline for pspp probably due to this bug. The problem occurs when I try to install "apt install texlive-plain-generic“. The install fails with …. Processing triggers for tex-common (6.18) … locale: Cannot set LC_CTYPE to default locale: No such file

Bug#1030827: FTBFS on armhf

Dear Niko, thanks for figuring out the problem! I will disable the perl-module for the moment. Thanks! Friedrich > Am 10.02.2023 um 20:53 schrieb Niko Tyni : > > Control: severity -1 serious > Justification: fails to build from source > > On Tue, Feb 07, 2023 at 03:47:46PM -0500, Sergio

Bug#932951: Updated 1.2.0-4 package in NEW queue

I made a new package version 1.2.0-4 which removes the texlive-generic-recommended dependency. The package is currently in the NEW/unstable queue. Thanks for all your work here. Friedrich

Bug#916902: Taking over pspp into Debian Science team maintenance (Was: pspp: CVE-2018-20230)

> > and added Ben Pfaff to the Debian Science team. Please create a login > on Salsa yourself to enable you becoming a member of the team and thus > getting commit permissions. > > Kind regards > >Andreas. > > On Tue, Apr 23, 2019 at 11:17:23AM +0200,

Bug#916902: Taking over pspp into Debian Science team maintenance (Was: pspp: CVE-2018-20230)

Hi Andreas, thanks for your offer to add the bugfix! You are of course welcome to do so. You can also create a project for the debian parts of pspp in salsa. Regards Friedrich > Am 23.04.2019 um 08:44 schrieb Andreas Tille : > > Hi Friedrich, > > I stumbled upon #916902 in my Buster bug

Bug#909857: fixed upstream

tags 909857 + fixed-upstream thanks This is fixed upstream in https://savannah.gnu.org/bugs/?52072

Bug#850457: pspp 0.10.2-1 FTBS randomly

> Am 03.06.2017 um 14:10 schrieb John Darrington : > > I presume this error is one that has just recently arisen? and so far as I'm > aware, no uploads > of pspp have recently occured in Debian (am I right Frederich?) If so, then > I suggest that recent >

Bug#850457: pspp 0.10.2-1 FTBS randomly

Hi Lucas, I guess the regression failure for postgresql here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863928 and for pspp here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933 which also fails when starting the psql

Bug#850457: PSPP build failure related to PSQL problem?

Hi, maybe the pspp regression failure is related to bug #863928 in PSQL where the regression fails when the database is initialized. This is exactly what we do in the failing test 247 in pspp. Friedrich

Bug#850457: pspp 0.10.2-1 FTBS randomly

Dear Adrian, dear Lucas, thanks for your reports. Maybe you can help me with the analysis as I have problems to reproduce it here locally. As already reported in the bug log https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933 I think the problem is due to locale settings in the