Bug#1061954: frog: NMU diff for 64-bit time_t transition

[Joost van Baal-Ilić]

Hi,

[sorry for yet another one, i clicked sent too early...]

On Fri, Feb 02, 2024 at 03:01:04PM +0100, Joost van Baal-Ilić wrote:
> On Fri, Feb 02, 2024 at 02:22:20PM +0100, Maarten van Gompel wrote:
> > 
> > On second thought, I read https://wiki.debian.org/ReleaseGoals/64bit-time 
> > and
> > checked the updated Frog sources, there is no time_t exposed at all anymore
> > in the new version I'm packaging.
> 
> That's nice.
> 
> > So if I understand things correctly, the new
> > libfrog3 library does not need the t64 transition and I can revert
> > https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f
> >  ?
> 
> 
> > > Afaik the plan is to keep the binary packages named libt64 (reading
> > > https://wiki.debian.org/ReleaseGoals/64bit-time ); this helps executing 
> > > the
> > > transition.
> > 
> > I'll rebase so the libfrog2t64 patch is included, but it'll be
> > immediately superseded by libfrog3.
> 
> Upcoming stable release could likely ship both frog2 and frog3.  E.g. if
> testing around release-time ships binaries build-depending upon frog2, this
> will happen.

Wow, having just read Message-Id:  to
debian-science, we might indeed succeed in shipping upcoming Debian stable
without frog2.

Bye,

Joost

Bug#1061954: frog: NMU diff for 64-bit time_t transition

[Joost van Baal-Ilić]

Hi,

On Fri, Feb 02, 2024 at 02:22:20PM +0100, Maarten van Gompel wrote:
> 
> On second thought, I read https://wiki.debian.org/ReleaseGoals/64bit-time and
> checked the updated Frog sources, there is no time_t exposed at all anymore
> in the new version I'm packaging.

That's nice.

> So if I understand things correctly, the new
> libfrog3 library does not need the t64 transition and I can revert
> https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f
>  ?


> > Afaik the plan is to keep the binary packages named libt64 (reading
> > https://wiki.debian.org/ReleaseGoals/64bit-time ); this helps executing the
> > transition.
> 
> I'll rebase so the libfrog2t64 patch is included, but it'll be
> immediately superseded by libfrog3.

Upcoming stable release could likely ship both frog2 and frog3.  E.g. if
testing around release-time ships binaries build-depending upon frog2, this
will happen.

Bye,

Joost

Bug#1061954: frog: NMU diff for 64-bit time_t transition

[Joost van Baal-Ilić]

Hi Maarten e.a.,

On Thu, Feb 01, 2024 at 06:29:20PM +0100, Maarten van Gompel wrote:
> On Tue Jan 30, 2024 at 2:31 PM CET, Lukas Märdian wrote:
> > As part of the 64-bit time_t transition required to support 32-bit
> > architectures in 2038 and beyond
> > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified

> 
> Thanks for your patch. I am currently in the progress of upgrading these
> packages to the new upstream sources after a long hiatus. This would
> involve a library transition anyway (libfrog2 -> libfrog3). Is it
> sufficient if I include  'Provides: ${t64:Provides}' for the new
> libfrog3 package to accomodate this transition? I just did this in
> commit 2bbda8d92d40b96a216e8d8db972a9589f8df02f:
>   
>   
> https://salsa.debian.org/science-team/frog/-/commit/2bbda8d92d40b96a216e8d8db972a9589f8df02f
> 
> Perhaps that also removes the need for the oddly named frog2t64 package?
> If not, I'll apply your patch and rebase my changes on top of it.

Afaik the plan is to keep the binary packages named libt64 (reading
https://wiki.debian.org/ReleaseGoals/64bit-time ); this helps executing the
transition.

HTH, Bye,

Joost

Bug#1062555: liboprf: NMU diff for 64-bit time_t transition

[Joost van Baal-Ilić]

Hi,

I've had a look at the diff, lgtm.  I'd appreciate the upload to unstable in
due time.  Thanks a lot for your work, much appreciated!

Bye,

Joost


On Thu, Feb 01, 2024 at 10:57:49PM +, Steve Langasek wrote:
> Source: liboprf
> Version: 0.1+git20231001.0da3e2b-1
> Severity: serious
> Tags: patch pending
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
> 
> NOTICE: these changes must not be uploaded to unstable yet!
> 
> Dear maintainer,
> 
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> liboprf as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we assume is affected).
> 
> To ensure that inconsistent combinations of libraries with their
> reverse-dependencies are never installed together, it is necessary to
> have a library transition, which is most easily done by renaming the
> runtime library package.
> 
> Since turning on 64-bit time_t is being handled centrally through a change
> to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
> important that libraries affected by this ABI change all be uploaded close
> together in time.  Therefore I have prepared a 0-day NMU for liboprf
> which will initially be uploaded to experimental if possible, then to
> unstable after packages have cleared binary NEW.
> 
> Please find the patch for this NMU attached.
> 
> If you have any concerns about this patch, please reach out ASAP.  Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes available that your package should not be included in the transition,
> there is time for us to amend the planned uploads.
> 
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)

> diff -Nru liboprf-0.1+git20231001.0da3e2b/debian/changelog 
> liboprf-0.1+git20231001.0da3e2b/debian/changelog
> --- liboprf-0.1+git20231001.0da3e2b/debian/changelog  2023-10-04 
> 14:07:26.0 +
> +++ liboprf-0.1+git20231001.0da3e2b/debian/changelog  2024-02-01 
> 17:51:25.0 +
> @@ -1,3 +1,10 @@
> +liboprf (0.1+git20231001.0da3e2b-1.1) experimental; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Rename libraries for 64-bit time_t transition.
> +
> + -- Steve Langasek   Thu, 01 Feb 2024 17:51:25 +
> +
>  liboprf (0.1+git20231001.0da3e2b-1) unstable; urgency=low
>  
>* New upstream git snapshot (thanks again Thorsten Alteholz for
> diff -Nru liboprf-0.1+git20231001.0da3e2b/debian/control 
> liboprf-0.1+git20231001.0da3e2b/debian/control
> --- liboprf-0.1+git20231001.0da3e2b/debian/control2023-10-04 
> 14:07:26.0 +
> +++ liboprf-0.1+git20231001.0da3e2b/debian/control2024-02-01 
> 17:51:25.0 +
> @@ -10,7 +10,10 @@
>  Vcs-Browser: https://salsa.debian.org/debian/liboprf
>  Vcs-Git: https://salsa.debian.org/debian/liboprf.git
>  
> -Package: liboprf0
> +Package: liboprf0t64
> +Provides: ${t64:Provides}
> +Replaces: liboprf0
> +Breaks: liboprf0 (<< ${source:Version})
>  Section: libs
>  Architecture: any
>  Multi-Arch: same
> diff -Nru liboprf-0.1+git20231001.0da3e2b/debian/liboprf0.install 
> liboprf-0.1+git20231001.0da3e2b/debian/liboprf0.install
> --- liboprf-0.1+git20231001.0da3e2b/debian/liboprf0.install   2023-10-04 
> 14:07:26.0 +
> +++ liboprf-0.1+git20231001.0da3e2b/debian/liboprf0.install   1970-01-01 
> 00:00:00.0 +
> @@ -1,2 +0,0 @@
> -#!/usr/bin/dh-exec
> -usr/lib/liboprf.so.0 => usr/lib/${DEB_HOST_MULTIARCH}/liboprf.so.0
> diff -Nru liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.install 
> liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.install
> --- liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.install
> 1970-01-01 00:00:00.0 +
> +++ liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.install
> 2023-10-04 14:07:26.0 +
> @@ -0,0 +1,2 @@
> +#!/usr/bin/dh-exec
> +usr/lib/liboprf.so.0 => usr/lib/${DEB_HOST_MULTIARCH}/liboprf.so.0
> diff -Nru 
> liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.lintian-overrides 
> liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.lintian-overrides
> --- liboprf-0.1+git20231001.0da3e2b/debian/liboprf0t64.lintian-overrides  
> 1970-01-01 00:00:00.0 +
> +++ 

Bug#1034348: at: autopkgtest regression on arm64

[Joost van Baal-Ilić]

Hi,

Another happy at user here.

Jose M Calhariz  wrote:
> Hi, I believe my last update fixed the problem can someone double check?

That was at 3.2.5-2, right?  Closing this bug: afaik nobody has been able to
reproduce the issue.  Therefore better to close and see what happens next.

Please reopen if you feel this is not appropriate.

Thanks!  Bye,

Joost

Bug#1035289: merecat: diff for NMU version 2.31+git20220513+ds-4.1

[Joost van Baal-Ilić]

Hi gregor,

Awesome, thanks a lot!  (And no need to delay longer.)

Bye,

Joost


On Thu, May 11, 2023 at 08:54:27PM +0200, gregor herrmann wrote:
> Control: tags 1035289 + patch
> Control: tags 1035289 + pending
> 
> 
> Dear maintainer,
> 
> I've prepared an NMU for merecat (versioned as 2.31+git20220513+ds-4.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> 
> 
> -- 
>  .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
>  `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
>`-   

> diff -Nru merecat-2.31+git20220513+ds/debian/changelog 
> merecat-2.31+git20220513+ds/debian/changelog
> --- merecat-2.31+git20220513+ds/debian/changelog  2023-02-23 
> 07:09:58.0 +0100
> +++ merecat-2.31+git20220513+ds/debian/changelog  2023-05-11 
> 20:47:24.0 +0200
> @@ -1,3 +1,13 @@
> +merecat (2.31+git20220513+ds-4.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix "postinst uses /usr/share/doc content (Policy 12.3):
> +/usr/share/doc/merecat/examples/merecat.conf":
> +Install example config files to /usr/share/merecat and symlink them from
> +/usr/share/doc/merecat/examples. (Closes: #1035289)
> +
> + -- gregor herrmann   Thu, 11 May 2023 20:47:24 +0200
> +
>  merecat (2.31+git20220513+ds-4) unstable; urgency=medium
>  
>* Upload to unstable.
> diff -Nru merecat-2.31+git20220513+ds/debian/install 
> merecat-2.31+git20220513+ds/debian/install
> --- merecat-2.31+git20220513+ds/debian/install2023-02-17 
> 09:47:41.0 +0100
> +++ merecat-2.31+git20220513+ds/debian/install2023-05-11 
> 20:47:24.0 +0200
> @@ -1 +1,3 @@
>  merecat.service lib/systemd/system
> +throttle.conf   usr/share/merecat
> +merecat.confusr/share/merecat
> diff -Nru merecat-2.31+git20220513+ds/debian/merecat.examples 
> merecat-2.31+git20220513+ds/debian/merecat.examples
> --- merecat-2.31+git20220513+ds/debian/merecat.examples   2022-05-05 
> 09:52:36.0 +0200
> +++ merecat-2.31+git20220513+ds/debian/merecat.examples   1970-01-01 
> 01:00:00.0 +0100
> @@ -1,2 +0,0 @@
> -throttle.conf
> -merecat.conf
> diff -Nru merecat-2.31+git20220513+ds/debian/merecat.links 
> merecat-2.31+git20220513+ds/debian/merecat.links
> --- merecat-2.31+git20220513+ds/debian/merecat.links  1970-01-01 
> 01:00:00.0 +0100
> +++ merecat-2.31+git20220513+ds/debian/merecat.links  2023-05-11 
> 19:58:06.0 +0200
> @@ -0,0 +1,2 @@
> +usr/share/merecat/throttle.conf usr/share/doc/merecat/examples/throttle.conf
> +usr/share/merecat/merecat.conf  usr/share/doc/merecat/examples/merecat.conf

Bug#1031513: clamav: new upstream security release, CVE-2023-20032

[Joost van Baal-Ilić]

Package: clamav
Severity: grave

Hi,

As you'll likely know there is
https://security-tracker.debian.org/tracker/CVE-2023-20032 and
https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html

"CVE-2023-20032: Fixed a possible remote code execution vulnerability in the
HFS+ file parser. The issue affects versions 1.0.0 and earlier, 0.105.1 and
earlier, and 0.103.7 and earlier. Thank you to Simon Scannell for reporting
this issue."

Upstream released fixed tarballs for all their supported branches.  I've
managed to build 0.103.8+dfsg-0+deb10u1~uvt0 for Debian 10/buster from that,
it's available from https://non-gnu.uvt.nl/debian/buster/clamav/ (including
sources).

We are now running this build on the Tilburg University mail infrastructure,
it might work for others too.

Anybody working on a proper Debian supplied fix: feel free to contact me (via
IRC, e.g.)

HTH, Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: PGP signature

Bug#1030530: pyenv / Re: Python 3.10 in bookworm

[Joost van Baal-Ilić]

Hi karthek e.a.,

Op Tue, Feb 07, 2023 at 10:50:07PM +0530 schreef karthek:
> Sorry for spamming…
> Resending the same message, I just remembered debian.org ignores mails
> from mail@* addresses.
> 
> On Tue, Feb 07, 2023 at 02:24:08PM +, Stefano Rivera wrote:
> > > See "ITP pyenv" @ http://bugs.debian.org/978149 .
> > 
> > I think the Python development community would be very happy to see
> > this. Debian's selected Python releases don't meet all the needs of
> > Python developers, who typically want access to all supported Python 3
> > versions (and possibly the next alpha), at all times.
> > 
> 
> Indeed.
> 
> > I'd be happy to review and sponsor uploads.
> > 
> 
> Thanks Stefano, I packaged it almost 2 years ago while working on
> Android Open-source project (AOSP). While I got response from upstream,
> I Haven't got any response from debian community back then apart from
> interest in it from Julian a year ago.
> 
> Since then I also didn't find any DD nearyby my city to sign my key.
> 
> I'm happy to work on the packaging…
> 

I've just found some work of you @ https://salsa.debian.org/karthek/pyenv .
Nice!

I see you've published just one branch ("master") and did not copy upstream
sources to salsa.  You might want to consider converting it to make use of the
gbp style packaging, as used by https://salsa.debian.org/python-team .

BTW: unfortunately I don't have any more time to invest in this... :(

Happy Hacking!

Bye,

Joost

-- 
“For if I am mistaken, I am. For one who does not exist cannot be mistaken
either.”– St. Augustine of Hippo, De Civitate Dei,
book XI, 26, early 5th century AD.

Bug#1030530: Python 3.10 in bookworm

[Joost van Baal-Ilić]

Op Tue, Feb 07, 2023 at 05:52:21AM + schreef Danial Behzadi دانیال بهزادی:
> Does it worth trying to package pyenv for Debian? Ain't it against any rules?

See "ITP pyenv" @ http://bugs.debian.org/978149 .

Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands

Bug#1028129: #1028129: securestring FTBFS: fatal error: Python.h: No such file or directory

[Joost van Baal-Ilić]

On Tue, Jan 10, 2023 at 06:26:54PM +0800, Bo YU wrote:
> On Mon, Jan 9, 2023 at 10:35 PM Joost van Baal-Ilić
>  wrote:
> >
> > Bo YU: thanks a lot for your recent work on securestring!  Do you plan
> > to upload it, or would you prefer me to handle that?  (I have time
> > to take care of it this week.)
> 
> Yeah, I need your help to upload it as usual(I do not have permission
> to upload package now).
> But before I reply to you, bage has helped to upload it already.
> 
> Anyway, thanks to all here.:)

Excellent, thanks!

Bye,

Joost

Bug#1028129: #1028129: securestring FTBFS: fatal error: Python.h: No such file or directory

[Joost van Baal-Ilić]

Hi,

Bo YU: thanks a lot for your recent work on securestring!  Do you plan
to upload it, or would you prefer me to handle that?  (I have time
to take care of it this week.)

Bye,

Joost

Bug#1024239: libequihash: baseline violation on i386 and FTBFS on !x86

[Joost van Baal-Ilić]

reopen 1024239
thanks

Hi Adrian,

On Mon, Jan 09, 2023 at 02:16:28AM +0200, Adrian Bunk wrote:
> 
> sorry for the late reply.
> 
> On Thu, Dec 29, 2022 at 03:43:18PM +0100, Joost van Baal-Ilić wrote:
> > 
> > 
> > Thanks, after consulting with upstream this should be fixed in new upstream
> > https://github.com/stef/equihash/archive/refs/tags/v1.0.3.tar.gz which has
> > https://github.com/stef/equihash/commit/0806afadf99837519469449c55dc425763e8eef7
> > .  I'll upload a new package soonishlish.
> 
> a second baseline violation I missed in my original bug report is
> -march=native, which FTBFS on some architectures and where it builds
> the package would only run on hardware compatible with whatever buildd
> did build the package (on amd64 this also means either on AMD or on 
> Intel hardware).
> 
> Regarding the binary-any FTBFS, this can be reproduced in a chroot
> with "dpkg-buildpackage -B".
> 
> sbuild has a --no-arch-all option that might do the same (untested).
> 
> python3-equihash is the binary-all package, what seems to fail is 
> debian/rules trying to build it in binary-any-only builds.

Thanks for detailed explanation.  I saw my latest upload FTBFS again, indeed.
Upstream helpfully released yet another version, I'll investigate later this
week.

Bye,

Joost

Bug#1024239: reopen / Re: Bug#1024239: marked as done (libequihash: baseline violation on i386 and FTBFS on !x86)

[Joost van Baal-Ilić]

reopen 1024239
thanks

https://buildd.debian.org/status/fetch.php?pkg=libequihash=amd64=1.0.4-1=1672405470=0

shows build on amd64 still fails.



On Fri, Dec 30, 2022 at 12:51:19PM +, Debian Bug Tracking System wrote:
> Your message dated Fri, 30 Dec 2022 12:49:19 +
> with message-id 
> and subject line Bug#1024239: fixed in libequihash 1.0.4-1
> has caused the Debian Bug report #1024239,
> regarding libequihash: baseline violation on i386 and FTBFS on !x86
> to be marked as done.

Bug#1024239: libequihash: baseline violation on i386 and FTBFS on !x86

[Joost van Baal-Ilić]

Thanks, after consulting with upstream this should be fixed in new upstream
https://github.com/stef/equihash/archive/refs/tags/v1.0.3.tar.gz which has
https://github.com/stef/equihash/commit/0806afadf99837519469449c55dc425763e8eef7
.  I'll upload a new package soonishlish.

Bye,

Joost


On Wed, Nov 16, 2022 at 11:37:01AM +0200, Adrian Bunk wrote:
> Source: libequihash
> Version: 1.0.2-3
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=libequihash=arm64=1.0.2-3=1668331092=0
> 
> ...
> make[1]: Entering directory '/<>'
> g++ -c -Wall -g -O3 -std=c++17 -fstack-protector-strong -D_FORTIFY_SOURCE=2 
> -fasynchronous-unwind-tables -fpic -Werror=format-security -Wl,-z,defs 
> -Wl,-z,relro -ftrapv -Wl,-z,noexecstack -march=native 
> -fstack-clash-protection -fcf-protection=full -o equihash.o equihash.cc
> cc1plus: error: ‘-fcf-protection=full’ is not supported for this target
> make[1]: *** [Makefile:16: equihash.o] Error 1
> 
> 
> -fcf-protection=full is an x86-only option not supported on
> other architectures.
> 
> -fcf-protection=full violates the i386 baseline,
> please use it only on amd64.

Bug#1002249: debian-faq: FTBFS: grep: nullfont.log: No such file or directory

[Joost van Baal-Ilić]

On Tue, Dec 21, 2021 at 05:32:16PM +0100, Lucas Nussbaum wrote:
> Source: debian-faq
> Version: 10.1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211220 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.


> > This is METAFONT, Version 2.71828182 (TeX Live 2022/dev/Debian) (preloaded 
> > base=mf)
> > 
> > kpathsea: Running mktexmf nullfont
> > 
> > ! I can't find file `nullfont'.
> > <*> ...four; mag:=1; ; nonstopmode; input nullfont
> >   
> > Please type another input file name
> > ! Emergency stop.
> > <*> ...four; mag:=1; ; nonstopmode; input nullfont
> >   
> > Transcript written on mfput.log.
> > grep: nullfont.log: No such file or directory
> > mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; ; nonstopmode; 
> > input nullfont' failed to make nullfont.tfm.
> > kpathsea: Appending font creation commands to missfont.log.
> > xelatex failed
> > stdin.tex:24: Package fontspec Error: The font "CharisSIL-R" cannot be 
> > found.

> > stdin.tex:538: Font TU/CharisSIL-R.ttf(0)/b/n/12=[CharisSIL-B.ttf]/OT at 
> > 12.0pt not loadable: Metric (TFM) file or installed font not found.
> > stdin.tex:538: leading text:  T
> > .:1787: Font TU/CharisSIL-R.ttf(0)/b/n/8=[CharisSIL-B.ttf]/OT at 8.0pt not 
> > loadable: Metric (TFM) file or installed font not found.
> > .:1787: leading text: }
> > Unexpected error occured
> > Error: list index out of range
> > make[2]: *** [Makefile:169: en/debian-faq.en.pdf] Error 1
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2021/12/20/debian-faq_10.1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
> 
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.

Thank you for reporting this, and thank you for your massive rebuild efforts:
much appreciated.  I'll look into this issue soonishlish.

Bye,

Joost

Bug#978907: #978907: timbl: ftbfs with autoconf 2.70

[Joost van Baal-Ilić]

tag 978907 +pending
thanks

thanks to Ko van der Sloot: fixed upstream in
https://github.com/LanguageMachines/timbl/commit/63740b

Bye,

Joost

Bug#971713: Bug arrived in Testing?

[Joost van Baal-Ilić]

Hi Dirk,

On Thu, Mar 04, 2021 at 10:35:42AM +, dirk.j...@telekom.de wrote:
> Hi guys,
> it seems the bug from insserv now arrived in testing with the tons of 
> repeated messages. Any chance for a fix?
> Very often repeated:
> insserv: Script sysstat has overlapping Default-Start and Default-Stop 
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
> insserv: Script sysstat has overlapping Default-Start and Default-Stop 
> runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.

This will likely get fixed automatically within 5 days from now:
https://tracker.debian.org/pkg/insserv says:

 Migration status for insserv (1.21.0-1 to 1.21.0-1.1)
 Too young, only 5 of 10 days old
 Updating insserv fixes old bugs: #971713

Bye,

Joost

Bug#958016: zoem: ftbfs with GCC-10

[Joost van Baal-Ilić]

Hi Matthias,

Thanks for this detailed report.  FWIW, upstream has been made aware and
acknowledged the problem.

Bye,

Joost

Bug#944107: simplesamlphp: CVE 2019-3465

[Joost van Baal-Ilić]

Package: simplesamlphp
Severity: grave
Tags: upstream, security

On mon nov 4 2019, 11:35 Jaime Pérez wrote @
https://groups.google.com/forum/#!msg/simplesamlphp-announce/2odMqz63z7k/6zQQeM91EwAJ
:
> We have been made aware of a security issue affecting all SimpleSAMLphp
> instances deployed as a service provider (basically, using SimpleSAMLphp to
> protect access to your application). This issue has been deemed critical, and
> will therefore need an urgent update. We will be releasing SimpleSAMLphp 
> 1.17.7
> during next Wednesday the 6th of November, at a time yet to be determined. We
> urge all SimpleSAMLphp users to make sure they are running the current stable
> version, so that upgrading to the new release doesn’t have any side effects,
> and to be prepared to upgrade their deployments as soon as the new stable
> release is published.
> 
> The details of the issue are embargoed for the time being, but will be made
> public after the bugfix release has been published. CVE 2019-3465 has been
> assigned to this issue.
> 
> --·
> Jaime Pérez
> Uninett / Feide·

We ship:

 jessie (oldoldstable) 1.13.1-2+deb8u2 [security]
 stretch (oldstable)   1.14.11-1+deb9u1
 buster (stable)   1.16.3-1
 bullseye (testing)1.17.6-1


Bye,

Joost

Bug#871105: Status of debian-faq

[Joost van Baal-Ilić]

Hi,

On Thu, Feb 14, 2019 at 02:13:14PM +0100, Dr. Tobias Quathamer wrote:
> 
> the package "debian-faq" has been uploaded three months ago and contains
> various important fixes. It's currently stuck in BYHAND.
> 
> Is there any chance that we can get this package into buster?

and feb 15 it got accepted in unstable, i expect it to enter buster/testing at
about feb 25th: in time for 2019-03-12 - Full-freeze.

Tobias: thanks a lot!

Bye,

Joost

Bug#917700: RM: dimbl -- ROM; ROM, abandoned upstream (was: Re: Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev)

[Joost van Baal-Ilić]

user debian-rele...@lists.debian.org
usertag 917700 + bsp-2019-01-nl-venlo
thanks

Hi Balint,

Since Maarten "proycon" van Gompel--a collegue of your dimbl comaintainer Ko
van der Sloot--told me he expects no new upstream release of dimbl, I feel it's
best to ask for dimbl's removal from testing and unstable.  Is that OK with
you?

Thanks, Bye,

Joost



Subject: RM: dimbl -- ROM; ROM, abandoned upstream
Package: ftp.debian.org
Severity: normal

Hi,

Please remove dimbl from both testing and unstable: no new upstream release
is expected.  Debian's users are better served without dimbl in the upcoming
stable release.  See also https://bugs.debian.org/917700 "FTBFS:
build-dependency not installable: libtimbl4-dev" for some discussion.

Bye,

Joost

PS:
[11:31] [joostvb(+i)] [5:uvt/#lst(+nt)] [Act: 17,21,25], jan 2019:
> нед 13 11:27 < joostvb> proycon: uit debian verwijderen bedoel je?
> нед 13 11:30 < proycon> ja
> нед 13 11:37 < joostvb> proycon: o, en uh: je verwacht geen nieuwe
>   upstream release?
> нед 13 11:46 < proycon> nope
> нед 13 11:46 < proycon> geen releases, geen gebruikers




On Fri, Jan 11, 2019 at 05:32:11AM +0100, Joost van Baal-Ilić wrote:
> Hi Maarten (upstream),
> 
> Is there no new upstream release expected?  If so, I guess indeed it would be
> best to drop it from Debian.
> 
> Thanks, Bye,
> 
> Joost
> 
> 
> On Thu, Jan 10, 2019 at 08:35:15PM +0100, Maarten van Gompel wrote:
> > Hi Lucas,
> > 
> > We're going to let this package get autoremoved, it's hardly used anyway
> > and not worth the effort to maintain.
> > 
> > Regards,
> > 
> > --
> > 
> > Maarten van Gompel
> > Language Machines research group
> > Centre for Language and Speech Technology
> > Radboud Universiteit Nijmegen
> > 
> > proy...@anaproy.nl
> > https://proycon.anaproy.nl
> > https://github.com/proycon
> > 
> > GnuPG key:  0x39FE11201A31555C
> > XMPP:   proy...@anaproy.nl   Matrix: @proycon:matrix.org
> > Telegram:   proycon  IRC: proycon (freenode)
> > Discord:proycon#8272
> > Mastodon:   https://mastodon.social/@proycon   (@proycon@mastodon.social)
> > Twitter:https://twitter.com/proycon
> > ORCID:  https://orcid.org/-0002-1046-0006
> > Keybase:https://keybase.io/proycon
> > Bitcoin:1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd
> 


signature.asc
Description: Digital signature

Bug#871105: Status of debian-faq

[Joost van Baal-Ilić]

Hi Tobias,

On Thu, Jan 10, 2019 at 11:18:41PM +0100, Dr. Tobias Quathamer wrote:
> Am 10.01.2019 um 06:46 schrieb Joost van Baal-Ilić:
> > Saw you've uploaded "byhand: 9.0" on november 17, great!  Upload is now
> > displayed at https://ftp-master.debian.org/new.html.
> > 
> > I'll keep an eye on the progress of the NEW queue handling and plan to work
> > on the SGML-XML conversion.
> 
> yes, the upload has been stuck in NEW for almost two months now. I'm not
> sure why.

I guess ftp-masters are busy, and handling a 'by-hand' request is more work
than a regular upload.

> Is there anything else that needs to be done to get it into
> unstable?

The only thing _we_ could do is kindly remind/ask ftp masters to process the
request.  I believe there still is some time before the freeze, so I would not
ask them now yet.

> > I feel we should try to get your 9.0 in Buster, if not a newer XML-ized
> > upload.
> 
> Hm, wouldn't Buster need the version 10.0 in order to match the version
> of the Buster release itself? Just wondering ...

Yes, ideally it should...

Bye,

Joost

Bug#917700: dimbl: FTBFS: build-dependency not installable: libtimbl4-dev

[Joost van Baal-Ilić]

Hi Maarten (upstream),

Is there no new upstream release expected?  If so, I guess indeed it would be
best to drop it from Debian.

Thanks, Bye,

Joost


On Thu, Jan 10, 2019 at 08:35:15PM +0100, Maarten van Gompel wrote:
> Hi Lucas,
> 
> We're going to let this package get autoremoved, it's hardly used anyway
> and not worth the effort to maintain.
> 
> Regards,
> 
> --
> 
> Maarten van Gompel
> Language Machines research group
> Centre for Language and Speech Technology
> Radboud Universiteit Nijmegen
> 
> proy...@anaproy.nl
> https://proycon.anaproy.nl
> https://github.com/proycon
> 
> GnuPG key:  0x39FE11201A31555C
> XMPP:   proy...@anaproy.nl   Matrix: @proycon:matrix.org
> Telegram:   proycon  IRC: proycon (freenode)
> Discord:proycon#8272
> Mastodon:   https://mastodon.social/@proycon   (@proycon@mastodon.social)
> Twitter:https://twitter.com/proycon
> ORCID:  https://orcid.org/-0002-1046-0006
> Keybase:https://keybase.io/proycon
> Bitcoin:1BRptZsKQtqRGSZ5qKbX2azbfiygHxJPsd

Bug#859784: Bug #859784: validns: Please migrate to openssl1.1 in Buster

[Joost van Baal-Ilić]

Hi Moritz,

On Thu, Jan 10, 2019 at 08:33:05PM +0100, Moritz Mühlenhoff wrote:
> On Mon, Nov 05, 2018 at 03:13:08PM +0100, Joost van Baal-Ilić wrote:
> > 
> > FWIW, this work:
> > 
> > > validns (0.8+git20170804-1) unstable; urgency=medium
> 
> [..]
> 
> > is available from
> > https://non-gnu.uvt.nl/debian/stretch/validns/validns_0.8+git20170804-1.dsc 
> > .
> > I _*might*_ have time to merge this back with what's in the Debian archive,
> > before the freeze.
> 
> What's the status?

Thanks for your interest.  Haven't done any work on it yet.

I'll visit https://wiki.debian.org/BSP/2019/01/nl/Venlo and might get to doing
some work on it, this weekend.  However, if _you're_ interested in working on
it: don't wait for me; go for it.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#871105: Status of debian-faq

[Joost van Baal-Ilić]

Hi again Tobias,

On Sun, Nov 18, 2018 at 09:53:30AM +0100, Joost van Baal-Ilić wrote:
> On Sat, Nov 17, 2018 at 11:57:03PM +0100, Dr. Tobias Quathamer wrote:
> > Am 17.11.2018 um 09:04 schrieb Joost van Baal-Ilić:
> > > I plan to work on the Debian FAQ at
> > > https://wiki.debian.org/BSP/2019/01/nl/Venlo .

That'll happen 3 days from now.

> > > However, IIRC currently
> > > the FAQ is next to ready for upload.  I will likely _not_ work on it
> > > before the BSP.  So: any action from your side is very welcome now.
> > 
> > great to hear, thanks! I did go ahead and fixed another (not reported)
> > FTBFS bug in the package, due to the switch of Chinese from sgml
> > translations to po4a translations.
> > 
> > I also did some minor cleanups and then prepared a new release. I hope I
> > did not mess up, but I thought that fixing the FTBFS bugs now would be a
> > good idea, because the freeze is not too far away.
> 
> Just had a very quick look at your work, it looks good, thanks.
> 
> > > One big issue we'd need to fix is: https://bugs.debian.org/612993 :
> > > convert from SGML to DocBook XML.  As I wrote there, that can wait till
> > > after upload.  But _not_ till the buster freeze, I'd say...
> > 
> > Well, that's probably quite a bit of work. If you don't mind, I could
> > look after some of the easier to fix bugs in the Debian BTS and try to
> > close them before the conversion.
> 
> Sure, go ahead.  An upload by you would be appreciated too.  :)

Saw you've uploaded "byhand: 9.0" on november 17, great!  Upload is now
displayed at https://ftp-master.debian.org/new.html.

I'll keep an eye on the progress of the NEW queue handling and plan to work on
the SGML-XML conversion.

I feel we should try to get your 9.0 in Buster, if not a newer XML-ized upload.

Bye,

Joost


PS/note to self: Upload commit at
https://salsa.debian.org/ddp-team/debian-faq/commit/d3836d052e9309bf5fbf51ac60d15d637ac78952
.

If we want to have an XMLized FAQ in Buster, we likely should do that work and
upload before the Soft-freeze at february 12th.

(* 2019-01-12 - Transition freeze (day after tomorrow)
 * 2019-02-12 - Soft-freeze
 * 2019-03-12 - Full-freeze
https://release.debian.org/buster/freeze_policy.html )


signature.asc
Description: Digital signature

Bug#871105: Status of debian-faq

[Joost van Baal-Ilić]

Hi Tobias,

On Sat, Nov 17, 2018 at 11:57:03PM +0100, Dr. Tobias Quathamer wrote:
> Am 17.11.2018 um 09:04 schrieb Joost van Baal-Ilić:
> >> I plan to work on the Debian FAQ at
> > https://wiki.debian.org/BSP/2019/01/nl/Venlo .  However, IIRC currently the 
> > FAQ
> > is next to ready for upload.  I will likely _not_ work on it before the BSP.
> > So: any action from your side is very welcome now.
> 
> great to hear, thanks! I did go ahead and fixed another (not reported)
> FTBFS bug in the package, due to the switch of Chinese from sgml
> translations to po4a translations.
> 
> I also did some minor cleanups and then prepared a new release. I hope I
> did not mess up, but I thought that fixing the FTBFS bugs now would be a
> good idea, because the freeze is not too far away.

Just had a very quick look at your work, it looks good, thanks.

> > One big issue we'd need to fix is: https://bugs.debian.org/612993 : convert
> > from SGML to DocBook XML.  As I wrote there, that can wait till after 
> > upload.
> > But _not_ till the buster freeze, I'd say...
> 
> Well, that's probably quite a bit of work. If you don't mind, I could
> look after some of the easier to fix bugs in the Debian BTS and try to
> close them before the conversion.

Sure, go ahead.  An upload by you would be appreciated too.  :)

Thanks, Bye,

Joost



signature.asc
Description: Digital signature

Bug#871105: Status of debian-faq

[Joost van Baal-Ilić]

Hi Tobias,

On Fri, Nov 16, 2018 at 10:53:43PM +0100, Dr. Tobias Quathamer wrote:
> 
> are you still planning to do an upload of debian-faq? Or are any other
> members of the maintaining team planning an upload?

I plan to work on the Debian FAQ at
https://wiki.debian.org/BSP/2019/01/nl/Venlo .  However, IIRC currently the FAQ
is next to ready for upload.  I will likely _not_ work on it before the BSP.
So: any action from your side is very welcome now.

One big issue we'd need to fix is: https://bugs.debian.org/612993 : convert
from SGML to DocBook XML.  As I wrote there, that can wait till after upload.
But _not_ till the buster freeze, I'd say...

Thanks for your interest!

Bye,

Joost

Bug#859784: Bug #859784: validns: Please migrate to openssl1.1 in Buster

[Joost van Baal-Ilić]

Hi,

FWIW, this work:

> validns (0.8+git20170804-1) unstable; urgency=medium
> 
>   * Upstream fix for https://github.com/tobez/validns/issues/66 RSIG(CAA).
> 
>  -- Casper Gielen Fri, 04 Aug 2017 10:52:03 +0200
> 
> validns (0.8+git20170801-2) unstable; urgency=medium
> 
>   * Switch to openssl1.1, patch by Sebastian Andrzej Siewior (Closes: 859784).
> 
>  -- Casper Gielen   Wed, 02 Aug 2017 17:46:03 +0200
> 
> validns (0.8+git20170801-1) unstable; urgency=medium
> 
>   * New upstream with support for AAC, CDS, CDNSKEY, SMIMEA resource records.
>   * debian/control Allow both ssl1.0 and ssl1.1 for backwards compatibiltiy.
>   * debian/control Upgrade to Standards-Version 4.0.0 (no changes).
> 
>  -- Casper Gielen   Tue, 01 Aug 2017 16:52:23 +0200
> 
> validns (0.8+git20160720-3) unstable; urgency=medium
> 
>   * debian/copyright Add License: statement.
>   * debian/control Upgrade to Standards-Version 3.9.8 (no changes).
> 
>  -- Casper Gielen   Wed, 14 Dec 2016 16:01:55 +0100
> 
> validns (0.8+git20160720-2) unstable; urgency=medium
> 
>   * Depend on OpenSSL 1.0 (Closes: #828591)
> 
>  -- Casper Gielen   Thu, 01 Dec 2016 14:51:30 +0100
> 
> validns (0.8+git20160720-1) stable; urgency=medium
> 
>   * New upstream with support for INCLUDE.
> 
>  -- Casper Gielen   Wed, 20 Jul 2016 11:27:36 +0200

is available from
https://non-gnu.uvt.nl/debian/stretch/validns/validns_0.8+git20170804-1.dsc .
I _*might*_ have time to merge this back with what's in the Debian archive,
before the freeze.

HTH, Bye,

Joost

Bug#867277: systraq: dpkg hook fails after package removal

[Joost van Baal-Ilić]

awesome, thanks a lot!

Bye, Joost

On Sat, Oct 20, 2018 at 10:12:34PM +0200, Andreas Beckmann wrote:
> Followup-For: Bug #867277
> 
> I just filed a stretch-pu request to finally fix this issue in stretch,
> too: https://bugs.debian.org/911494
> I'll take care of the upload.
> 
> 
> Andreas

> diff -Nru systraq-20160803/debian/20systraq systraq-20160803/debian/20systraq
> --- systraq-20160803/debian/20systraq 2016-03-10 20:03:02.0 +0100
> +++ systraq-20160803/debian/20systraq 2018-10-20 21:27:59.0 +0200
> @@ -1,2 +1,2 @@
>  # /etc/apt/apt.conf.d/20systraq - update systraq's list of monitored files
> -DPkg::Post-Invoke { "test -f /etc/systraq/Makefile && command -v make 
> >/dev/null && su -s /bin/sh -c 'make -s -C /etc/systraq' debian-systraq"; };
> +DPkg::Post-Invoke { "test ! -f /etc/systraq/Makefile || ! command -v make 
> >/dev/null || su -s /bin/sh -c 'make -s -C /etc/systraq' debian-systraq"; };
> diff -Nru systraq-20160803/debian/changelog systraq-20160803/debian/changelog
> --- systraq-20160803/debian/changelog 2016-08-03 19:45:54.0 +0200
> +++ systraq-20160803/debian/changelog 2018-10-20 21:27:59.0 +0200
> @@ -1,3 +1,11 @@
> +systraq (20160803-1+deb9u1) stretch; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/20systraq: Invert logic in order to exit successfully in case
> + /e/s/Makefile is missing.  (Closes: #867277)
> +
> + -- Andreas Beckmann   Sat, 20 Oct 2018 21:27:59 +0200
> +
>  systraq (20160803-1) unstable; urgency=medium
>  
>* New upstream release: The Pidjiguiti Release.

Bug#896317: Bug#896404: python-django-casclient: diff for NMU version 1.2.0-2.1

[Joost van Baal-Ilić]

On Sat, Sep 22, 2018 at 12:09:49PM +0300, Adrian Bunk wrote:
> 
> I've prepared an NMU for python-django-casclient (versioned as 
> 1.2.0-2.1) and uploaded it to DELAYED/15. Please feel free to
> tell me if I should cancel it.

Thanks for your work, much appreciated.  Please do go ahead.

Bye,

Joost

Bug#871105: debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).

[Joost van Baal-Ilić]

tags 871105 pending
thanks

Could reproduce it, after applying patch by Baptiste Jammet (see #851414)
no longer reproducable.  Therefore, closing in upcoming upload.

Thanks!

On Thu, Nov 30, 2017 at 07:00:18AM +0100, Joost van Baal-Ilić wrote:
> Yes, this is indeed buggy.  I'll work on it.  More details below.

Bug#871105: debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).

[Joost van Baal-Ilić]

Yes, this is indeed buggy.  I'll work on it.  More details below.

On Thu, Nov 30, 2017 at 06:43:03AM +0100, Joost van Baal-Ilić wrote:
> On Sun, Aug 06, 2017 at 05:46:58PM -0400, Lucas Nussbaum wrote:
> > 
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> > 
> > Relevant part (hopefully):
> > > make[1]: Entering directory '/<>'
> > > echo "" > faqdynamic.ent
> > > if [ -f debian/changelog ]; then \
> > >   echo " > > grep '^Version: ' | sed 's/^Version: *//'`\">" >> faqdynamic.ent; \
> > > else \
> > >   echo "" >> faqdynamic.ent; \
> > > fi
> > > PERL_PERTURB_KEYS=0 PERL_HASH_SEED=0 po4a --keep 0 --previous 
> > > --rm-backups po4a/po4a.cfg # --localized-charset UTF-8
> > > Negative repeat count does nothing at 
> > > /usr/share/perl5/Locale/Po4a/Sgml.pm line 1103,  line 8143.
> > > Negative repeat count does nothing at 
> > > /usr/share/perl5/Locale/Po4a/Sgml.pm line 1103,  line 8143.
> > > No candidate position for the addendum po4a/add_fr/commentaires.add.
> > > Addendum po4a/add_fr/commentaires.add does NOT apply to 
> > > fr/debian-faq.sgml (translation discarded).
> > > Makefile:53: recipe for target 'po4a-translate' failed
> > > make[1]: *** [po4a-translate] Error 255
> > 
> > The full build log is available from:
> >http://aws-logs.debian.net/2017/08/05/debian-faq_8.1_unstable.log
> > 
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> > 
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> > 
> 
> Thanks a lot for this rebuilding effort!
> 
> FWIW: On a Debian GNU/Linux 9.1 (stretch) system running 'make pdf langs="fr"'
> from current debian-faq svn works just fine.
> 
> Will investigate more soonish.

And on today's Debian sid I can manually build just fine.  Just generated a
fine fr/debian-faq.pdf .

However, running

 touch faqdynamic.ent
 make po4a-translate

indeed shows

 PERL_PERTURB_KEYS=0 PERL_HASH_SEED=0 po4a --keep 0 --previous --rm-backups 
po4a/po4a.cfg # --localized-charset UTF-8
 Negative repeat count does nothing at /usr/share/perl5/Locale/Po4a/Sgml.pm 
line 1106,  line 8222.
 No candidate position for the addendum po4a/add_fr/commentaires.add.
 Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml 
(translation discarded).
 Makefile:53: recipe for target 'po4a-translate' failed
 make: *** [po4a-translate] Error 255

.  (And running 'make' afterwards just happily completes (!).) So our
Makefile is buggy, too.

I did not build the complete .deb yet; it could be some needed build
dependency is missing too...

Bye,

Joost

Bug#871105: debian-faq: FTBFS: Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml (translation discarded).

[Joost van Baal-Ilić]

Hi,

On Sun, Aug 06, 2017 at 05:46:58PM -0400, Lucas Nussbaum wrote:
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > echo "" > faqdynamic.ent
> > if [ -f debian/changelog ]; then \
> >   echo " > '^Version: ' | sed 's/^Version: *//'`\">" >> faqdynamic.ent; \
> > else \
> >   echo "" >> faqdynamic.ent; \
> > fi
> > PERL_PERTURB_KEYS=0 PERL_HASH_SEED=0 po4a --keep 0 --previous --rm-backups 
> > po4a/po4a.cfg # --localized-charset UTF-8
> > Negative repeat count does nothing at /usr/share/perl5/Locale/Po4a/Sgml.pm 
> > line 1103,  line 8143.
> > Negative repeat count does nothing at /usr/share/perl5/Locale/Po4a/Sgml.pm 
> > line 1103,  line 8143.
> > No candidate position for the addendum po4a/add_fr/commentaires.add.
> > Addendum po4a/add_fr/commentaires.add does NOT apply to fr/debian-faq.sgml 
> > (translation discarded).
> > Makefile:53: recipe for target 'po4a-translate' failed
> > make[1]: *** [po4a-translate] Error 255
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/08/05/debian-faq_8.1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 

Thanks a lot for this rebuilding effort!

FWIW: On a Debian GNU/Linux 9.1 (stretch) system running 'make pdf langs="fr"'
from current debian-faq svn works just fine.

Will investigate more soonish.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#853613: pinfo: #853613: gcc-7 with -Os: undefined references to inline functions

[Joost van Baal-Ilić]

Control: tag -1 + fixed-upstream

On 2017-08-07 Bas Zoetekouw commited
https://github.com/baszoetekouw/pinfo/commit/c38522340979c92b7e9ed3fbfbd156dba5344f75
 :
>>  * src/filehandling_functions.c, src/initializelinks.c, src/utils.c: 
>> Get rid of inlined functions, which break buildling with gcc7
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81734
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853613

Bye,

Joost



signature.asc
Description: Digital signature

Bug#853613: pinfo: #853613: gcc-7 with -Os: undefined references to inline functions

[Joost van Baal-Ilić]

Have verified package builds succesfully with gcc-7 in current sid chroot.
Made another house-keeping change, updated debdiff attached.  (If I have more
time I'll upload later.)

Bye,

Joost


diff -Nru pinfo-0.6.9/debian/changelog pinfo-0.6.9/debian/changelog
--- pinfo-0.6.9/debian/changelog2017-10-04 05:39:34.0 +0200
+++ pinfo-0.6.9/debian/changelog2017-10-04 05:38:11.0 +0200
@@ -1,3 +1,18 @@
+pinfo (0.6.9-5.2) unstable; urgency=low
+
+  * NMU
+  * Get rid of undefined references to inline functions when compiling
+with gcc-7 using -Os by first declaring these 3 functions without
+using the inline keyword.  Thanks Matthias Klose for reporting,
+Adrian Bunk for writing a test case and Jakub Jelinek for pointing
+the way to a fix in
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81734#c3.
+(Closes: #853613) [06_gcc_7_Os_inline_functions.dpatch]
+  * Use source format '3.0 (quilt)' [debian/source/format], no longer
+build-depend upon deprecated package dpatch.
+
+ -- Joost van Baal-Ilić <joos...@debian.org>  Wed, 04 Oct 2017 05:38:11 +0200
+
 pinfo (0.6.9-5.1) unstable; urgency=low
 
   * NMU
diff -Nru pinfo-0.6.9/debian/control pinfo-0.6.9/debian/control
--- pinfo-0.6.9/debian/control  2017-10-04 05:39:34.0 +0200
+++ pinfo-0.6.9/debian/control  2017-10-04 05:36:03.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Bas Zoetekouw <b...@debian.org>
 Standards-Version: 3.8.3
-Build-Depends: debhelper (>=5), dpatch, bzip2, gettext, libreadline-dev, 
libncursesw5-dev, texinfo, install-info, autotools-dev
+Build-Depends: debhelper (>=5), bzip2, gettext, libreadline-dev, 
libncursesw5-dev, texinfo, install-info, autotools-dev
 Homepage: http://pinfo.alioth.debian.org/
 
 Package: pinfo
diff -Nru pinfo-0.6.9/debian/patches/00list pinfo-0.6.9/debian/patches/00list
--- pinfo-0.6.9/debian/patches/00list   2017-10-04 05:39:34.0 +0200
+++ pinfo-0.6.9/debian/patches/00list   2017-10-04 04:56:25.0 +0200
@@ -3,3 +3,4 @@
 03_typos.dpatch
 04_link_order.dpatch
 05_term.h.dpatch
+06_gcc_7_Os_inline_functions.dpatch
diff -Nru pinfo-0.6.9/debian/patches/06_gcc_7_Os_inline_functions.dpatch 
pinfo-0.6.9/debian/patches/06_gcc_7_Os_inline_functions.dpatch
--- pinfo-0.6.9/debian/patches/06_gcc_7_Os_inline_functions.dpatch  
1970-01-01 01:00:00.0 +0100
+++ pinfo-0.6.9/debian/patches/06_gcc_7_Os_inline_functions.dpatch  
2017-10-04 04:56:10.0 +0200
@@ -0,0 +1,40 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 06_gcc_7_Os_inline_functions.dpatch by Joost van Baal-Ilić 
<joos...@debian.org>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Get rid of undefined references to inline functions when compiling
+## DP: with gcc-7 using -Os by first declaring these 3 functions without
+## DP: using the inline keyword.
+## DP: Thanks Matthias Klose for reporting, Adrian Bunk for writing a test
+## DP: case and Jakub Jelinek for pointing the way to a fix.
+
+@DPATCH@
+
+--- pinfo-0.6.9/src/initializelinks.c  2006-03-15 22:54:56.0 +0100
 pinfo-0.6.9/src/initializelinks.c  2017-10-04 04:37:18.782964086 +0200
+@@ -75,6 +75,7 @@
+  * checks if an item belongs to tag table. returns 1 on success and 0 on
+  * failure.  It should be optimised...
+  */
++extern int exists_in_tag_table(char *item);
+ inline int
+ exists_in_tag_table(char *item)
+ {
+--- pinfo-0.6.9/src/filehandling_functions.c   2006-03-16 16:15:02.0 
+0100
 pinfo-0.6.9/src/filehandling_functions.c   2017-10-04 04:37:59.519976805 
+0200
+@@ -551,6 +551,7 @@
+   return 1;
+ }
+ 
++extern void buildcommand(char *dest, char *command, char *filename, const 
char *tmpfilename);
+ inline void
+ buildcommand(char *dest, char *command, char *filename, const char 
*tmpfilename)
+ {
+@@ -561,6 +562,7 @@
+   strcat(dest, tmpfilename);
+ }
+ 
++extern void builddircommand(char *dest, char *command, char *filename, const 
char *tmpfilename);
+ inline void
+ builddircommand(char *dest, char *command, char *filename, const char 
*tmpfilename)
+ {
diff -Nru pinfo-0.6.9/debian/source/format pinfo-0.6.9/debian/source/format
--- pinfo-0.6.9/debian/source/format1970-01-01 01:00:00.0 +0100
+++ pinfo-0.6.9/debian/source/format2017-10-04 05:35:40.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)


signature.asc
Description: Digital signature

Bug#853613: pinfo: #853613: gcc-7 with -Os: undefined references to inline functions

[Joost van Baal-Ilić]

Control: tags -1 + patch

On Wed, Oct 04, 2017 at 03:58:59AM +0200, Joost van Baal-Ilić wrote:
> 
> I'm investing some time in working on this issue now.

debdiff attached. _untested_ !  more later.

Bye,

Joost

PS/BTW: This bug did cause https://tracker.debian.org/news/866084: removal from
testing/buster.

pinfo upstream is maintained by Bas Zoutekouw at
g...@github.com:baszoetekouw/pinfo.git ; Debian packaging seems not to be
maintained in any VCS.  (I've checked github,
https://anonscm.debian.org/viewvc/pinfo/ , didn't check sourceforge.)

debian/watch is obsolete: still points at sf.net

diff -u pinfo-0.6.9/debian/changelog pinfo-0.6.9/debian/changelog
--- pinfo-0.6.9/debian/changelog
+++ pinfo-0.6.9/debian/changelog
@@ -1,3 +1,16 @@
+pinfo (0.6.9-5.2) unstable; urgency=low
+
+  * NMU
+  * Get rid of undefined references to inline functions when compiling
+with gcc-7 using -Os by first declaring these 3 functions without
+using the inline keyword.  Thanks Matthias Klose for reporting,
+Adrian Bunk for writing a test case and Jakub Jelinek for pointing
+the way to a fix in
+https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81734#c3.
+(Closes: #853613) [06_gcc_7_Os_inline_functions.dpatch]
+
+ -- Joost van Baal-Ilić <joos...@debian.org>  Wed, 04 Oct 2017 05:03:34 +0200
+
 pinfo (0.6.9-5.1) unstable; urgency=low
 
   * NMU
diff -u pinfo-0.6.9/debian/patches/00list pinfo-0.6.9/debian/patches/00list
--- pinfo-0.6.9/debian/patches/00list
+++ pinfo-0.6.9/debian/patches/00list
@@ -5,0 +6 @@
+06_gcc_7_Os_inline_functions.dpatch
only in patch2:
unchanged:
--- pinfo-0.6.9.orig/debian/patches/06_gcc_7_Os_inline_functions.dpatch
+++ pinfo-0.6.9/debian/patches/06_gcc_7_Os_inline_functions.dpatch
@@ -0,0 +1,40 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 06_gcc_7_Os_inline_functions.dpatch by Joost van Baal-Ilić 
<joos...@debian.org>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Get rid of undefined references to inline functions when compiling
+## DP: with gcc-7 using -Os by first declaring these 3 functions without
+## DP: using the inline keyword.
+## DP: Thanks Matthias Klose for reporting, Adrian Bunk for writing a test
+## DP: case and Jakub Jelinek for pointing the way to a fix.
+
+@DPATCH@
+
+--- pinfo-0.6.9/src/initializelinks.c  2006-03-15 22:54:56.0 +0100
 pinfo-0.6.9/src/initializelinks.c  2017-10-04 04:37:18.782964086 +0200
+@@ -75,6 +75,7 @@
+  * checks if an item belongs to tag table. returns 1 on success and 0 on
+  * failure.  It should be optimised...
+  */
++extern int exists_in_tag_table(char *item);
+ inline int
+ exists_in_tag_table(char *item)
+ {
+--- pinfo-0.6.9/src/filehandling_functions.c   2006-03-16 16:15:02.0 
+0100
 pinfo-0.6.9/src/filehandling_functions.c   2017-10-04 04:37:59.519976805 
+0200
+@@ -551,6 +551,7 @@
+   return 1;
+ }
+ 
++extern void buildcommand(char *dest, char *command, char *filename, const 
char *tmpfilename);
+ inline void
+ buildcommand(char *dest, char *command, char *filename, const char 
*tmpfilename)
+ {
+@@ -561,6 +562,7 @@
+   strcat(dest, tmpfilename);
+ }
+ 
++extern void builddircommand(char *dest, char *command, char *filename, const 
char *tmpfilename);
+ inline void
+ builddircommand(char *dest, char *command, char *filename, const char 
*tmpfilename)
+ {


signature.asc
Description: Digital signature

Bug#853613: pinfo: #853613: gcc-7 with -Os: undefined references to inline functions

[Joost van Baal-Ilić]

For the record:

At https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81734#c3 Jakub Jelinek wrote on
2017-08-07 07:37:55 UTC:
>> The C99/C11 inlining semantics in this case is that if it is possible and
>> desirable to inline the function, then it is inlined, but the out-of-line
>> copy of the inlined function has to be emitted in some other TU.
>> 
>> (In reply to Matthias Klose from comment #2)
>> > but shouldn't these the same with different optimization levels?
>> 
>> Of course not.  Whether it is desirable to inline something is an
>> optimization decision, at -O0 we don't inline anything (unless it has
>> always_inline attribute), at -Os we inline if the heuristics determines that
>> inlining will likely make the code smaller, at -O2 etc. if it determines
>> that inlining will likely make the code faster.
>> 
>> So, for the broken pinfo package, you need to decide what you want.  Either
>> you want it to be inlined always, no matter what, then it needs
>> always_inline attribute, or if it is not desirable to inline, you want a
>> static copy of the out of line function in every TU that needs it, then it
>> should be static inline, or you want out of line copy in one TU and not the
>> others, then you use what you have above in all but one TU, and in that last
>> TU add extern void builddircommand(void);, or you want the GNU inline
>> semantics, then you add gnu_inline attribute and again read the rules for
>> it.  See https://gcc.gnu.org/onlinedocs/gcc-7.1.0/gcc/Inline.html and the C
>> standard for more details.

I'm investing some time in working on this issue now.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#867277: systraq: dpkg hook fails after package removal

[Joost van Baal-Ilić]

Hi Andreas,

Thanks for reporting.  I expect to be able to upload a fixed package
within a couple of days.

Greetings from DebConf17,

Joost

On Wed, Jul 05, 2017 at 02:15:46PM +0200, Andreas Beckmann wrote:
> Package: systraq
> Version: 20160803-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to remove.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Removing systraq (20160803-1) ...
> [...]
>   Removing make (4.1-9.1) ...
> [...]
>   Processing triggers for libc-bin (2.24-12) ...
>   E: Problem executing scripts DPkg::Post-Invoke 'test -f 
> /etc/systraq/Makefile && command -v make >/dev/null && su -s /bin/sh -c 'make 
> -s -C /etc/systraq' debian-systraq'
>   E: Sub-process returned an error code
> 
> 
> cheers,
> 
> Andreas




signature.asc
Description: Digital signature

Bug#807317: again: future of Moodle in Debian: ship with Debian 10 Buster in 2019?

[Joost van Baal-Ilić]

Hi,

Is any DD interested in working on shipping Moodle with upcoming upcoming
Debian 10 Buster release?  This would mean the package should be in good shape
early 2019; and there should be commitment to keep maintaining the package for
some more years.

"Moodle is a learning platform designed to provide educators, administrators
and learners with a single robust, secure and integrated system to create
personalised learning environments."  It's like the Free Software alternative
for Blackboard.

It's a huge PHP web application, it needs a database backend (MySQL, e.g.)  It
comes with bundled PHP modules from other upstreams.  Upstream ships a .tgz; I
believe one needs a javascript enabled webbrowser to be able to download from
https://download.moodle.org/releases/security/ (so crafting a watch-file is not
trivial).  The upstream team (hi Dan and Marina) is helpful and responsive.

Thanks to the work of Isaac Clerencia, Tomasz Muras, Didier Raboud, Thijs
Kinkhorst and others, Moodle has been shipped with Debian in some form since
2003 (moodle 1.1.1), see
http://metadata.ftp-master.debian.org/changelogs/main/m/moodle/moodle_2.7.18+dfsg-1_changelog
.

Currently, it's in unstable only, see https://bugs.debian.org/807317 and
https://bugs.debian.org/747084 : I am the only person working on this package
and due to time constrains can't commit to helping with security support in
upcoming Debian 9 stable/stretch.  However, there _is_ an unofficial backport
to current stable/jessie, available from "deb http://non-gnu.uvt.nl/debian
jessie uvt", see https://non-gnu.uvt.nl/debian/jessie/moodle/ .

The Debian Moodle packaging "team" uses git on Alioth, see
https://alioth.debian.org/projects/pkg-moodle/ .  There's also
pkg-moodle-maintain...@lists.alioth.debian.org .  (That one however is not very
suitable for development discussions since its archive is not publically
accessible.)

In april 2016, Nishanth Aravamudan and Steve Langasek worked on moodle
(3.0.3+dfsg-0ubuntu1) which is shipped with Ubuntu xenial (16.04LTS) and
yakkety (16.10).

It would be really cool if Debian would continue to ship moodle in some form.
And it would be very sad if we'd fail to continue shipping it...  I am willing
to spend _some_ time on making this happen.  However, if nobody steps up
soonish to help, I'm afaid moodle support in Debian will stop.  I'll upload
upcoming 2.7.19+dfsg-1 in a couple of days; if nothing changes that would be my
last moodle upload to Debian...  :(

Anybody interested in working on getting e.g. something based upon Nishanth's
and Steve's moodle 3.0.* in Debian Buster?  I offer to help.

Bye,

Joost



Op Wed, Feb 04, 2015 at 09:54:41AM +0100 schreef Joost van Baal-Ilić:
> 
[...]
> At Tilburg University we are running moodle on some Debian systems; we have
> an interest in keeping it working for us.  I basically took over the work
> from Thijs.
> 
> Op Thu, Jan 22, 2015 at 07:47:17AM + schreef Dan Poltawski:
> > 
> > 'Upstream' here.
[...]
> > Thank you very much for trying to get in touch with us.
> > 
> > I've been cc'd on the Moodle debian bugs for quite some time and i'm
> > afraid that this is a bit of a cycle with the package. Quite some time
> > ago I was part of a team to keep up with keeping the package in order,
> > but eventually could not keep on top of it - then others like Tomasz
> > Muras and Thijs Kinkhorst have valiantly tried to get it in order. See
> > #494642 #647489 #747084 etc.
[...]
> Yes, it is quite a lot of work; Thijs managed to keep the package in shape,
> I'm convinced I can do it too.  However, I don't think it's wise to offer
> moodle in Debian stable


-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: Digital signature

Bug#851986: [request-tracker-maintainers] Bug#851986: rt-extension-sla: Obsolete with RT 4.4

[Joost van Baal-Ilić]

On Fri, Jan 20, 2017 at 03:38:31PM +, Dominic Hargreaves wrote:
> Source: rt-extension-sla
> Version: 1.04-2
> Severity: serious
> Justification: obsolete, uninstallable
> 
> With the upload of RT 4.4 to unstable, this separate package is
> obsoleted - RT 4.4 includes the SLA functionality out of the box. As
> such, rt-extension-sla should not be released with stretch.

Thanks for reporting this; you are right.

FWIW; rt-extension-sla has been packaged to be useful for people running
jessie/stable.  I am running it on jessie production systems.

I am wondering if it would be usefull to have rt-extension-sla in unstable for
the next couple of months...  Unfortunately, as long as it is not in testing,
it can't be in backports either; due to the backports policy :( .

Bye,

Joost

Bug#833905: dimbl will get removed from Debian (was: Re: Bug#833905: dimbl: FTBFS: include/dimbl/DimProcs.h:37:29: error: expected ')' before '&' token)

[Joost van Baal-Ilić]

See also Bug#843328: O: dimbl .

Chris and Adrian: thanks a lot for your investigations!

Bye,

Joost



signature.asc
Description: Digital signature

Bug#836070: #836070 r-cran-sem: FTBFS: ERROR: dependencies 'MASS', 'boot' are not available for package 'sem'

[Joost van Baal-Ilić]

Hi Chris e.a.,

Thanks for this report, I expect to be able to fix it this month.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#817453: taking over maintainership (was: Re: Bug#817453: #817453: filetraq: Removal of debhelper compat 4 (was: Re: systraq is marked for autoremoval from testing))

[Joost van Baal-Ilić]

Hi Sergio,

On Sun, Jul 03, 2016 at 12:27:34PM +0200, Sergio Talens-Oliag wrote:
> El Sat, Jul 02, 2016 at 09:01:49AM +0200, Joost van Baal-Ilić va escriure:
> > 
> > Attached is the debdiff of this NMU.  Sergio: if you'd prefer me to _not_
> > upload, please let me now soonish.  I am willing to take over mainainership
> > of filetraq, btw.
> 
> Feel free to take it, lately I have near to zero time for packages, I'll try
> to catch up but if you are interested it's ok for me.

Great, thanks for this reply.  I'll upload soonish; and take over 
maintainership.

Bye,

Joost


> > On Mon, Jun 20, 2016 at 10:57:23PM +0200, Joost van Baal-Ilić wrote:
> > > 
> > > In order to solve the problem quoted below; I've prepared an NMU for
> > > filetraq, fixing #817453 (and some other maintenance / bitrot-coping
> > > thingies).  Package is available now from http://mdcc.cx/tmp/filetraq/
> > > (filetraq_0.2-14.1_all.deb , filetraq_0.2-14.1.dsc e.a.) .  I plan to
> > > upload in a couple of days.

> -- 
> Sergio Talens-Oliag <s...@mixinet.net>  <http://mixinet.net/stoblog/>
> Key fingerprint = FA90 8E47 1AD3 7D7F 2363  D78F 821A EE0F D167 FBDF

Bug#817453: #817453: filetraq: Removal of debhelper compat 4 (was: Re: systraq is marked for autoremoval from testing)

[Joost van Baal-Ilić]

Hi,

Attached is the debdiff of this NMU.  Sergio: if you'd prefer me to _not_ 
upload,
please let me now soonish.  I am willing to take over mainainership of filetraq,
btw.

Thanks, Bye,

Joost



On Mon, Jun 20, 2016 at 10:57:23PM +0200, Joost van Baal-Ilić wrote:
> tags 817453 +pending
> thanks
> 
> Hi,
> 
> In order to solve the problem quoted below; I've prepared an NMU for filetraq,
> fixing #817453 (and some other maintenance / bitrot-coping thingies).  Package
> is available now from http://mdcc.cx/tmp/filetraq/ (filetraq_0.2-14.1_all.deb 
> ,
> filetraq_0.2-14.1.dsc e.a.) .  I plan to upload in a couple of days.
> 
> Sergio: what do you think?
> 
> Thanks, Bye,
> 
> Joost
> 
> 
> 
> On Mon, Jun 20, 2016 at 04:39:35AM +, Debian testing autoremoval watch 
> wrote:
> > systraq 20160316-1 is marked for autoremoval from testing on 2016-07-19
> > 
> > It (build-)depends on packages with these RC bugs:
> > 817453: filetraq: Removal of debhelper compat 4
> > 


diff -u filetraq-0.2/debian/control filetraq-0.2/debian/control
--- filetraq-0.2/debian/control
+++ filetraq-0.2/debian/control
@@ -2,11 +2,12 @@
 Section: admin
 Priority: optional
 Maintainer: Sergio Talens-Oliag <s...@debian.org>
-Build-Depends-Indep: cdbs, debhelper (>= 4.2)
+Build-Depends: cdbs, debhelper (>= 9)
 Standards-Version: 3.6.2.1
 
 Package: filetraq
 Architecture: all
+Depends: ${misc:Depends}
 Description: Small utility to keep track of changes in config files
  FileTraq is just a shell script that reads a list of files to watch, runs
  diff against each file and its backup, and reports any discrepancies, along
diff -u filetraq-0.2/debian/compat filetraq-0.2/debian/compat
--- filetraq-0.2/debian/compat
+++ filetraq-0.2/debian/compat
@@ -1 +1 @@
-4
+9
diff -u filetraq-0.2/debian/changelog filetraq-0.2/debian/changelog
--- filetraq-0.2/debian/changelog
+++ filetraq-0.2/debian/changelog
@@ -1,3 +1,17 @@
+filetraq (0.2-14.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/compat: bump from debhelper 4 to 9; thanks Niels Thykier (Closes:
+Bug#817453).
+  * debian/control: update debhelper from >= 4.2 to >= 9.
+  * debian/control: change Build-Depends-Indep to Build-Depends (cdbs,
+debhelper): these are required to run the clean target.  Thanks lintian.
+  * debian/control: add Depends: ${misc:Depends} to satisfy debhelper. Thanks
+lintian.
+  * debian/copyright: completed.  Thanks lintian.
+
+ -- Joost van Baal-Ilić <joos...@debian.org>  Mon, 20 Jun 2016 22:16:10 +0200
+
 filetraq (0.2-14) unstable; urgency=low
 
   * Install script on /usr/sbin instead of /usr/bin (Closes: Bug#355669).
diff -u filetraq-0.2/debian/copyright filetraq-0.2/debian/copyright
--- filetraq-0.2/debian/copyright
+++ filetraq-0.2/debian/copyright
@@ -8,3 +8,18 @@
-Copyright:
+Copyright (c) 2000 Jeremy Weatherford
 
-GPL, on debian systems look in '/usr/share/common-licenses/GPL'.
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+02110-1301, USA.
+
+On Debian systems look in '/usr/share/common-licenses/GPL-2'.


signature.asc
Description: Digital signature

Bug#817453: #817453: filetraq: Removal of debhelper compat 4 (was: Re: systraq is marked for autoremoval from testing)

[Joost van Baal-Ilić]

tags 817453 +pending
thanks

Hi,

In order to solve the problem quoted below; I've prepared an NMU for filetraq,
fixing #817453 (and some other maintenance / bitrot-coping thingies).  Package
is available now from http://mdcc.cx/tmp/filetraq/ (filetraq_0.2-14.1_all.deb ,
filetraq_0.2-14.1.dsc e.a.) .  I plan to upload in a couple of days.

Sergio: what do you think?

Thanks, Bye,

Joost



On Mon, Jun 20, 2016 at 04:39:35AM +, Debian testing autoremoval watch 
wrote:
> systraq 20160316-1 is marked for autoremoval from testing on 2016-07-19
> 
> It (build-)depends on packages with these RC bugs:
> 817453: filetraq: Removal of debhelper compat 4
> 


signature.asc
Description: Digital signature

Bug#821534: [moodle-packaging] Bug#821534: Bumping severity of PHP 7.0 transition bugs to serious

[Joost van Baal-Ilić]

Hi,

Op Thu, May 05, 2016 at 10:20:56AM +0200 schreef Ondřej Surý:
> 
> I am bumping the severity of this bug to serious, as we are going to
> remove src:php5 from Debian and your package is blocking the first
> step which is removal of php5 from testing.  Please either update your
> package to support PHP 7.0 or remove the package from Debian unstable
> alltogether.

Thanks, will upload a fixed moodle this month.  Dan Poltawski: thanks for your
comment; appreciated.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#813444: mbtserver: FTBFS with timblserver 1.8

[Joost van Baal-Ilić]

Hi Andreas e.a.,

On Tue, Feb 02, 2016 at 05:00:06AM +0100, Andreas Beckmann wrote:
> Source: mbtserver
> Version: 0.7-3
> Severity: serious
> Tags: sid
> Justification: fails to build from source (but built successfully in the past)
> 
> mbtserver FTBFS with timblserver 1.8 that I just moved from experimental
> to sid:
> 
> /usr/bin/make  all-recursive
> make[2]: Entering directory '/build/mbtserver-0.7'
> Making all in src
> make[3]: Entering directory '/build/mbtserver-0.7/src'
> g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
> -c -o MbtServer.o MbtServer.cxx
> g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
> -c -o MbtServerBase.o MbtServerBase.cxx
> MbtServerBase.cxx:35:40: fatal error: timblserver/TimblServerAPI.h: No such 
> file or directory
> compilation terminated.
> Makefile:308: recipe for target 'MbtServerBase.o' failed
> make[3]: *** [MbtServerBase.o] Error 1
> make[3]: Leaving directory '/build/mbtserver-0.7/src'
> Makefile:323: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> 
> There is a new upstream release 0.10 reported by the watch file and
> a new upstream release v3.2.15 on github.

Thanks for reporting this.

FWIW, all packages as listed on
https://qa.debian.org/developer.php?login=ko.vandersloot%40uvt.nl are somewhat
tightly related.  New upstream releases come in bursts.  Versions of about the
same age build and run fine together.  When versions in Debian get out of sync,
bad things will likely happen.  Same comment applies to Bug#813445: frog:
FTBFS, of course.

Currently, I can't promis to help with this soonish.   Luckily there still is
time before the next freeze...

Bye,

Joost

Bug#807511: cpqarrayd: DNBFS (was: Re: failed ppc64el build of cpqarrayd 2.3-4)

[Joost van Baal-Ilić]

 /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
 from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
 from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
 from /usr/include/signal.h:308,
 from cpqarrayd.c:49:
/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:134:23: 
error: conflicting types for 'blkcnt_t'
 typedef unsigned long blkcnt_t;
   ^
In file included from /usr/include/stdlib.h:314:0,
 from cpqarrayd.c:27:
/usr/include/powerpc64le-linux-gnu/sys/types.h:235:20: note: previous 
declaration of 'blkcnt_t' was here
 typedef __blkcnt_t blkcnt_t;  /* Type to count number of disk blocks.  */
^
In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
 from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
 from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
 from /usr/include/signal.h:308,
 from cpqarrayd.c:49:
/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:154:9: 
error: unknown type name 'u32'
 typedef u32 dma_addr_t;
 ^
/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:164:9: 
error: unknown type name 'u32'
 typedef u32 phys_addr_t;
 ^
/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:216:9: 
error: unknown type name 'u64'
 typedef u64 cycle_t;
 ^
cpqarrayd.c: In function 'main':
cpqarrayd.c:267:5: warning: implicit declaration of function 
'cciss_status_check' [-Wimplicit-function-declaration]
 cciss_status_check(opts);
 ^
Makefile:464: recipe for target 'cpqarrayd.o' failed
make[3]: *** [cpqarrayd.o] Error 1

-- 
Joost van Baal-Ilić <joos...@uvt.nl>   irc://irc.uvt.nl/joostvb
http://abramowitz.uvt.nl/(013-466-)3519
do afwezig  kamer G 236
LIS Unix https://doc.uvt.nl/its-id/its-unix-sm/

Bug#807511: cpqarrayd: DNBFS (was: Re: failed ppc64el build of cpqarrayd 2.3-4)

[Joost van Baal-Ilić]

Op Thu, Dec 10, 2015 at 12:05:42AM +0100 schreef Joost van Baal-Ilić:
> Looking into this.
> 
> Found cpqarrayd for Red Hat: * Jan 12 2012 - 2.3-17.  Unfortunately no new
> patches, I guess this one won't build with linux 4.2 either.
> 
> We succesfully build on i386 and armel with linux 4.1.
> 
> s390x fails with linux 4.1 :
> https://buildd.debian.org/status/fetch.php?pkg=cpqarrayd=s390x=2.3-4=1439019282

amd64 succeeds with linux 4.2: just did build it in sid chroot.

removing debian/linux/linux-source-4.2/include from -I, and making sure 
linux/compiler.h is found (e.g. by
just putting it under cpqarrayd-2.3/ ) yields a succesfull build on amd64 with 
linux 4.2.  This might
also yield succesful build on other platforms.

Reproduce like this:

(sid)joostvb@dijkstra:~/lo.../cpqarrayd/cpqarrayd-2.3% mkdir linux
(sid)joostvb@dijkstra:~/lo.../cpqarrayd/cpqarrayd-2.3% cp 
debian/linux/linux-source-4.2/include/linux/compiler.h linux 

 gcc -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 
-I./debian/linux/linux-source-4.2/drivers/block -g -O2 -fstack-protector-strong 
-O2 -MT cpqarrayd.o -MD -MP -MF .deps/cpqarrayd.Tpo -c -o cpqarrayd.o 
cpqarrayd.c




> Op Wed, Dec 09, 2015 at 10:58:20PM +0100 schreef Joost van Baal-Ilić:
> > Package: cpqarrayd
> > Severity: critical
> > 
> > 
> > Seems like it's our/cpqarrayd's fault:
> > 
> > 
> > Op Wed, Dec 09, 2015 at 06:25:15PM +0100 schreef Debian buildds:
> > >  * Source package: cpqarrayd
> > >  * Version: 2.3-4
> > >  * Architecture: ppc64el
> > >  * State: failed
> > >  * Suite: sid
> > >  * Builder: ppc64el-osuosl-01.debian.org
> > >  * Build log: 
> > > https://buildd.debian.org/status/fetch.php?pkg=cpqarrayd=ppc64el=2.3-4=1449679745=log
> > > 
> > > Please note that these notifications do not necessarily mean bug reports
> > > in your package but could also be caused by other packages, temporary
> > > uninstallabilities and arch-specific breakages.  A look at the build log
> > > despite this disclaimer would be appreciated however.
> > 
> > 
> > make[3]: Leaving directory '/«PKGBUILDDIR»/scripts'
> > make[3]: Entering directory '/«PKGBUILDDIR»'
> > gcc -DHAVE_CONFIG_H -I.   -D_FORTIFY_SOURCE=2 
> > -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/drivers/block 
> > -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include  -g -O2 
> > -fstack-protector-strong -O2 
> > -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/drivers/block 
> > -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include -MT cpqarrayd.o -MD 
> > -MP -MF .deps/cpqarrayd.Tpo -c -o cpqarrayd.o cpqarrayd.c
> > In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
> >  from /usr/include/signal.h:308,
> >  from cpqarrayd.c:49:
> > /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:14:26: 
> > error: conflicting types for 'fd_set'
> >  typedef __kernel_fd_set  fd_set;
> >   ^
> > In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:219:0,
> >  from /usr/include/stdlib.h:314,
> >  from cpqarrayd.c:27:
> > /usr/include/powerpc64le-linux-gnu/sys/select.h:75:5: note: previous 
> > declaration of 'fd_set' was here
> >} fd_set;
> >  ^



> > In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
> >  from /usr/include/signal.h:308,
> >  from cpqarrayd.c:49:
> > /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:15:25: 
> > error: conflicting types for 'dev_t'
> >  typedef __kernel_dev_t  dev_t;
> >  ^
> > In file included from /usr/include/stdlib.h:314:0,
> >  from cpqarrayd.c:27:
> > /usr/include/powerpc64le-linux-gnu/sys/types.h:60:17: note: previous 
> > declaration of 'dev_t' was here
> >  typedef __dev_t dev_t;
> >  ^

> > In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
> >  from 
> > /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
> >

Bug#807511: cpqarrayd: DNBFS (was: Re: failed ppc64el build of cpqarrayd 2.3-4)

[Joost van Baal-Ilić]

Looking into this.

Found cpqarrayd for Red Hat: * Jan 12 2012 - 2.3-17.  Unfortunately no new
patches, I guess this one won't build with linux 4.2 either.

We succesfully build on i386 and armel with linux 4.1.

s390x fails with linux 4.1 :
https://buildd.debian.org/status/fetch.php?pkg=cpqarrayd=s390x=2.3-4=1439019282

Will investigate more...



Op Wed, Dec 09, 2015 at 10:58:20PM +0100 schreef Joost van Baal-Ilić:
> Package: cpqarrayd
> Severity: critical
> 
> 
> Seems like it's our/cpqarrayd's fault:
> 
> 
> Op Wed, Dec 09, 2015 at 06:25:15PM +0100 schreef Debian buildds:
> >  * Source package: cpqarrayd
> >  * Version: 2.3-4
> >  * Architecture: ppc64el
> >  * State: failed
> >  * Suite: sid
> >  * Builder: ppc64el-osuosl-01.debian.org
> >  * Build log: 
> > https://buildd.debian.org/status/fetch.php?pkg=cpqarrayd=ppc64el=2.3-4=1449679745=log
> > 
> > Please note that these notifications do not necessarily mean bug reports
> > in your package but could also be caused by other packages, temporary
> > uninstallabilities and arch-specific breakages.  A look at the build log
> > despite this disclaimer would be appreciated however.
> 
> 
> make[3]: Leaving directory '/«PKGBUILDDIR»/scripts'
> make[3]: Entering directory '/«PKGBUILDDIR»'
> gcc -DHAVE_CONFIG_H -I.   -D_FORTIFY_SOURCE=2 
> -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/drivers/block 
> -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include  -g -O2 
> -fstack-protector-strong -O2 
> -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/drivers/block 
> -I/«PKGBUILDDIR»/debian/linux/linux-source-4.2/include -MT cpqarrayd.o -MD 
> -MP -MF .deps/cpqarrayd.Tpo -c -o cpqarrayd.o cpqarrayd.c
> In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
>  from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
>  from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
>  from /usr/include/signal.h:308,
>  from cpqarrayd.c:49:
> /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:14:26: 
> error: conflicting types for 'fd_set'
>  typedef __kernel_fd_set  fd_set;
>   ^
> In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:219:0,
>  from /usr/include/stdlib.h:314,
>  from cpqarrayd.c:27:
> /usr/include/powerpc64le-linux-gnu/sys/select.h:75:5: note: previous 
> declaration of 'fd_set' was here
>} fd_set;
>  ^
> In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
>  from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
>  from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
>  from /usr/include/signal.h:308,
>  from cpqarrayd.c:49:
> /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:15:25: 
> error: conflicting types for 'dev_t'
>  typedef __kernel_dev_t  dev_t;
>  ^
> In file included from /usr/include/stdlib.h:314:0,
>  from cpqarrayd.c:27:
> /usr/include/powerpc64le-linux-gnu/sys/types.h:60:17: note: previous 
> declaration of 'dev_t' was here
>  typedef __dev_t dev_t;
>  ^
> In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
>  from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
>  from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
>  from /usr/include/signal.h:308,
>  from cpqarrayd.c:49:
> /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:19:17: 
> error: conflicting types for 'nlink_t'
>  typedef __u32   nlink_t;
>  ^
> In file included from /usr/include/stdlib.h:314:0,
>  from cpqarrayd.c:27:
> /usr/include/powerpc64le-linux-gnu/sys/types.h:75:19: note: previous 
> declaration of 'nlink_t' was here
>  typedef __nlink_t nlink_t;
>^
> In file included from /usr/include/powerpc64le-linux-gnu/asm/ptrace.h:27:0,
>  from /usr/include/powerpc64le-linux-gnu/asm/sigcontext.h:11,
>  from /usr/include/powerpc64le-linux-gnu/bits/sigcontext.h:27,
>  from /usr/include/signal.h:308,
>  from cpqarrayd.c:49:
> /«PKGBUILDDIR»/debian/linux/linux-source-4.2/include/linux/types.h:25:26: 
> error: conflicting types for 'timer_t'
>  typedef __kernel_timer_t timer_t;
>   ^
> In file included from /usr/include/powerpc64le-linux-gnu/sys/types.h:132:0,
>  from /usr/include/stdlib.h:314,
>  from cpqarrayd.c:27:
> /usr

Bug#787271: Bug #787271: moodle: dpkg-source fails to extract old-old-stable version of moodle

[Joost van Baal-Ilić]

Hi,

Thanks for reporting this issue.

I am not quite sure how to deal with this bug.

Maybe we should do nothing: Debian ships moodle only in
squeeze/oldoldstable and in sid/unstable.  Moodle is Unsupported in squeeze-lts,
see e.g. https://security-tracker.debian.org/tracker/CVE-2015-5342.  See
https://security-tracker.debian.org/tracker/source-package/moodle for what
would need to be done to support moodle in oldoldstable...

If it is sane to invest time in this; the slightly related fix at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753219#10 might be helpful.

Bye,

Joost




signature.asc
Description: Digital signature

Bug#775850: timblserver: FTBFS in unstable: error: 'class Timbl::GetOptClass' has no member named 'getLogFile'

[Joost van Baal-Ilić]

Hi Andreas e.a.,

On Mon, Nov 09, 2015 at 01:07:44PM +0100, Andreas Beckmann wrote:
> On Mon, 14 Sep 2015 14:11:40 +0200 Joost van =?utf-8?Q?Baal-Ili=C4=87?=
>  wrote:
> > On Mon, Sep 14, 2015 at 12:21:34PM +0100, Peter Green wrote:
> > > >
> > > >  timblserver (1.8-1) experimental; urgency=low
> > > >  .
> > > >* New upstream release.
> > > >  - Fixes "timblserver: FTBFS in unstable: error: 'class 
> > > > Timbl::GetOptClass'
> > > How come this was uploaded to experimental and not unstable?
> > > 
> > 
> > I'm not quite sure if uploading to unstable wouldn't introduce even more RC
> > bugs.  Don't have the time to find out about that now.  I'll likely be able 
> > to
> > allocate more time to it within about one month.
> 
> Did you find some time to look at this issue?

Nope.  Hrm, I guess I can state: if there hasn't been done done any
substantial work on this by february 1, 2016; feel free to remove this stuff
from the archive.  I expect I'll have been able to allocate some time on this
before that date.

> > btw: you're welcome to nmu if you're convinced that will fix bugs.
> 
> In unstable currently the whole reverse-build-deps set of timblserver is
> unbuildable and uninstallable.

Yes...  :(

Thanks for pinging me.

Bye,

Joost

Bug#775850: timblserver: FTBFS in unstable: error: 'class Timbl::GetOptClass' has no member named 'getLogFile'

[Joost van Baal-Ilić]

On Mon, Sep 14, 2015 at 12:21:34PM +0100, Peter Green wrote:
> >
> >  timblserver (1.8-1) experimental; urgency=low
> >  .
> >* New upstream release.
> >  - Fixes "timblserver: FTBFS in unstable: error: 'class 
> > Timbl::GetOptClass'
> How come this was uploaded to experimental and not unstable?
> 

I'm not quite sure if uploading to unstable wouldn't introduce even more RC
bugs.  Don't have the time to find out about that now.  I'll likely be able to
allocate more time to it within about one month.

btw: you're welcome to nmu if you're convinced that will fix bugs.

Bye,

Joost

Bug#791301: ticcutils: diff for NMU version 0.7-2.1

[Joost van Baal-Ilić]

On Tue, Aug 11, 2015 at 10:26:06PM +0100, Jonathan Wiltshire wrote:
 Control: tag -1 patch pending
 
 Dear maintainer,
 
 I've prepared an NMU for ticcutils (versioned as 0.7-2.1)

Great, thanks a lot.

 and
 uploaded it to DELAYED/2. Please feel free to tell me if I
 should delay it longer.

No need to delay, please just go ahead.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#795062: publicfile-installer: insecure use of /tmp

[Joost van Baal-Ilić]

Package: publicfile-installer
Version: 0.10-1
Severity: critical
Tags: security
Justification: root security hole

Hi Justin,

On Sun, Aug 09, 2015 at 12:38:21PM +0100, Justin B Rye wrote:
 
 This contrib installer package downloads the source code for DJB's
 publicfile, builds it, and then puts the output in a predictable
 location in a world-writable directory, using an existing directory of
 that name if it already exists, then (either automatically or by
 telling the admin to run another script) installs whatever happens to
 be in that directory.
 
 This can be exploited by malicious local users to get arbitrary
 installscripts executed as root.
snip

I'll investigate  fix this; thanks for checking the code.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#785591: [moodle-packaging] Bug#785591: moodle: CVE-2015-3174 CVE-2015-3175 CVE-2015-3176 CVE-2015-3177 CVE-2015-3178 CVE-2015-3179 CVE-2015-3180 CVE-2015-3181

[Joost van Baal-Ilić]

Thanks, I'll investigate.  About a week ago a new moodle upsteam was shipped;
likely that one deals with (some of) these CVE's.  I plan to upload within
about a week.

Bye,

Joost

Op Mon, May 18, 2015 at 06:59:03AM +0200 schreef Salvatore Bonaccorso:
 Source: moodle
 Version: 2.7.7+dfsg-1
 Severity: grave
 Tags: security upstream fixed-upstream
 
 Hi,
 
 see http://www.openwall.com/lists/oss-security/2015/05/18/1 for
 details on the assigned CVEs.
 
 Regards,
 Salvatore
 
 ___
 Pkg-moodle-maintainers mailing list
 pkg-moodle-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-moodle-maintainers


signature.asc
Description: Digital signature

Bug#752615: moodle is licensed under the PHP license and is not PHP

[Joost van Baal-Ilić]

Hi,

I am currently investigating this issue.

The file lib/pear/HTML/QuickForm/Renderer/Tableless.php is shipped with
http://pear.php.net/package/HTML_QuickForm_Renderer_Tableless/  License: New
BSD. Current Release: 0.6.2 (2011-07).  Depends upon HTML_QuickForm 3.2.7.

The file lib/pear/HTML/QuickForm/DHTMLRulesTableless.php is shipped with
http://pear.php.net/package/HTML_QuickForm_DHTMLRulesTableless. License: New
BSD. Current Release: 0.3.3 (beta) 2007-10.  Depends upon
HTML_QuickForm_Renderer_Tableless 0.4.0.

I'll have another look at it later.  Thanks for your bugreport!

Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: Digital signature

Bug#782103: libucto2: fails to upgrade from 'sid' - trying to overwrite /etc/ucto/tokconfig-en

[Joost van Baal-Ilić]

On Tue, Apr 07, 2015 at 11:20:12PM +0200, Andreas Beckmann wrote:
 Package: libucto2
 Version: 0.5.5-1
 Severity: serious
 User: debian...@lists.debian.org
 Usertags: piuparts
 
 Hi,
 
 during a test with piuparts I noticed your package fails to upgrade from
 'sid' to 'experimental'.
 It installed fine in 'sid', then the upgrade to 'experimental' fails
 because it tries to overwrite other packages files without declaring a
 Breaks+Replaces relation.
 
 See policy 7.6 at
 https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
 
 From the attached log (scroll to the bottom...):
 
   Preparing to unpack .../libucto2_0.5.5-1_amd64.deb ...
   Unpacking libucto2 (0.5.5-1) over (0.5.3-3.1+b1) ...
   dpkg: error processing archive 
 /var/cache/apt/archives/libucto2_0.5.5-1_amd64.deb (--unpack):
trying to overwrite '/etc/ucto/tokconfig-en', which is also in package 
 ucto 0.5.3-3.1+b1
   Errors were encountered while processing:
/var/cache/apt/archives/libucto2_0.5.5-1_amd64.deb


Thanks, will get to it.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775850: timblserver: FTBFS in unstable: error: 'class Timbl::GetOptClass' has no member named 'getLogFile'

[Joost van Baal-Ilić]

Hi James,

On Tue, Jan 20, 2015 at 05:23:22PM +, James Cowgill wrote:
 Source: timblserver
 Version: 1.7-4
 Severity: serious
 Tags: sid
 
 Hi,
 
 timblserver FTBFS in unstable (but not in testing) on amd64 with the
 following error:
  /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
  -I..  -I../include -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong 
  -Wformat -Werror=format-security -Wall  -I/usr/include/libxml2   -fopenmp   
  -fopenmp -c -o ServerBase.lo ServerBase.cxx
  libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../include 
  -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
  -Werror=format-security -Wall -I/usr/include/libxml2 -fopenmp -fopenmp -c 
  ServerBase.cxx  -fPIC -DPIC -o .libs/ServerBase.o
  ServerBase.cxx: In constructor 
  'TimblServer::IB1_Server::IB1_Server(Timbl::GetOptClass*)':
  ServerBase.cxx:1128:22: error: 'class Timbl::GetOptClass' has no member 
  named 'getLogFile'
 logFile = opt-getLogFile();
snip
^
  ServerBase.cxx:1160:23: error: 'class Timbl::GetOptClass' has no member 
  named 'daemonizeFlag'
 doDaemon = opt-daemonizeFlag();
 ^
  Makefile:413: recipe for target 'ServerBase.lo' failed
  make[3]: *** [ServerBase.lo] Error 1
 
 After playing around with the build dependencies, this seems to be
 caused by the upgrade of timbl from 6.4.4-4 - 6.4.6-1
 
 Full mips64el build log (the arch where I first saw this):
 http://mipsdebian.imgtec.com/debian/logs/t/timblserver/timblserver_1.7-4_mips64el-20150115-0504.build.gz
 

I'll get to this soonish.  It'll get fixed with the upcoming upload of new
upstream 1.9. (Note to self: first convert repo from svn to git.)

Thanks for reporting!

Bye,

Joost

PS: do you happen to know if this endangers timblserver in jessie? I'd guess
not...


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735120: Bug#750853: ITA: postfix-cluebringer -- anti-spam plugin for Postfix

[Joost van Baal-Ilić]

Hi Nigel e.a.,

On Sat, 07 Jun 2014 15:50:41 +, Nigel Kukard wrote:
 I intend to adopt postfix-cluebringer and will make an upload asap.

Excellent!  Did you manage to publish some work, e.g. in some git repo
somewhere?

FWIW, I found out v2.0.14 was released upstream on 2013-10-26.  Furthermore,
Bug #735120 (non-free w3c icons) is fixed upstream in
https://gitlab.devlabs.linuxassist.net/policyd/policyd/commit/925edf8630b83e3f474e47490369b830829a16b6,
at around 2014-05.

So it should not be that hard to get postfix-cluebringer back in Debian...

Bye,

Joost

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: Digital signature

Bug#775842: [moodle-packaging] Bug#775842: moodle: Multiple security issues

[Joost van Baal-Ilić]

Hi,

Op Tue, Jan 20, 2015 at 05:15:13PM +0100 schreef Moritz Muehlenhoff:
 Package: moodle
 Severity: grave
 Tags: security
 Justification: user security hole
 
 The current Moodle package in the archive is affected by multiple security 
 issues:
 
 Cheers,
 Moritz
 
 https://security-tracker.debian.org/tracker/CVE-2015-0218
 https://security-tracker.debian.org/tracker/CVE-2015-0217
 https://security-tracker.debian.org/tracker/CVE-2015-0216
 https://security-tracker.debian.org/tracker/CVE-2015-0215
 https://security-tracker.debian.org/tracker/CVE-2015-0214
 https://security-tracker.debian.org/tracker/CVE-2015-0213
 https://security-tracker.debian.org/tracker/CVE-2015-0212
 https://security-tracker.debian.org/tracker/CVE-2015-0211
 https://security-tracker.debian.org/tracker/CVE-2014-9059
 https://security-tracker.debian.org/tracker/CVE-2014-7848
 https://security-tracker.debian.org/tracker/CVE-2014-7847
 https://security-tracker.debian.org/tracker/CVE-2014-7846
 https://security-tracker.debian.org/tracker/CVE-2014-7845
 https://security-tracker.debian.org/tracker/CVE-2014-7838
 https://security-tracker.debian.org/tracker/CVE-2014-7837
 https://security-tracker.debian.org/tracker/CVE-2014-7836
 https://security-tracker.debian.org/tracker/CVE-2014-7835
 https://security-tracker.debian.org/tracker/CVE-2014-7834
 https://security-tracker.debian.org/tracker/CVE-2014-7833
 https://security-tracker.debian.org/tracker/CVE-2014-7832
 https://security-tracker.debian.org/tracker/CVE-2014-7831
 https://security-tracker.debian.org/tracker/CVE-2014-7830
 https://security-tracker.debian.org/tracker/CVE-2014-4172
 https://security-tracker.debian.org/tracker/CVE-2014-3617
 https://security-tracker.debian.org/tracker/CVE-2014-3553
 https://security-tracker.debian.org/tracker/CVE-2014-3551
 https://security-tracker.debian.org/tracker/CVE-2014-3548
 https://security-tracker.debian.org/tracker/CVE-2014-3547
 https://security-tracker.debian.org/tracker/CVE-2014-3546
 https://security-tracker.debian.org/tracker/CVE-2014-3545
 https://security-tracker.debian.org/tracker/CVE-2014-3544
 https://security-tracker.debian.org/tracker/CVE-2014-3543
 https://security-tracker.debian.org/tracker/CVE-2014-3542
 https://security-tracker.debian.org/tracker/CVE-2014-3541
 https://security-tracker.debian.org/tracker/CVE-2014-2054
 https://security-tracker.debian.org/tracker/CVE-2013-3630

These issues indeed are not listed to be fixed in moodle_2.7.5+dfsg-2 which is
currently in unstable.  I'll upload a new version which explicitly lists the
CVE's fixed in upstream 2.7.5.

For the record, on
https://security-tracker.debian.org/tracker/source-package/moodle, as of today,
only

 CVE-2014-4172
 CVE-2014-2054
 CVE-2013-3630

are still listed as unfixed in 2.7.5+dfsg-2.

Thanks for your time.

Bye,

Joost



signature.asc
Description: Digital signature

Bug#775842: 3 left (was: Re: [moodle-packaging] Bug#775842: Bug#775842: moodle: Multiple security issues)

[Joost van Baal-Ilić]

Hi,

Op Fri, Feb 13, 2015 at 03:21:49PM +0100 schreef Joost van Baal-Ilić:
 Op Tue, Jan 20, 2015 at 05:15:13PM +0100 schreef Moritz Muehlenhoff:
  Package: moodle
  Severity: grave
  Tags: security
  Justification: user security hole
  
  The current Moodle package in the archive is affected by multiple security 
  issues:
  
  Cheers,
  Moritz
  
  https://security-tracker.debian.org/tracker/CVE-2015-0218
snip
  https://security-tracker.debian.org/tracker/CVE-2014-2054
  https://security-tracker.debian.org/tracker/CVE-2013-3630
 
 These issues indeed are not listed to be fixed in moodle_2.7.5+dfsg-2 which is
 currently in unstable.  I'll upload a new version which explicitly lists the
 CVE's fixed in upstream 2.7.5.
 
 For the record, on
 https://security-tracker.debian.org/tracker/source-package/moodle, as of 
 today,
 still listed as unfixed in 2.7.5+dfsg-2 are :

  CVE-2014-4172

php-cas problem, fixed in Debian's php-cas 1.3.3-1 and 1.3.1-4+deb7u1.  Moodle
ships with unchanged phpCAS 1.3.3, see
moodle-2.7.5+dfsg/auth/cas/CAS/moodle_readme.txt Moodle can likely use the
Debian-maintained php-cas package.  I'll try  test that.

  CVE-2014-2054

Security problem in old version of php-excel, which is shipped with moodle.

https://bugs.debian.org/718585 RFP: php-excel -- Read, Write and Create Excel
documents in PHP

Status: hard license problems, will probably never get packaged for Debian.
Popular workaround (as implemented by victims ownCloud and dolibarr): remove
PHPExcel code  functionality from package.  I'll try  test that.

  CVE-2013-3630

https://tracker.moodle.org/browse/MDL-41449

I'll apply for a Jira account later...  :-/

Bye,

Joost

-- 
Ho Mitakuye Oyasin ※ joostvb@{牛在田里,ad1810}.com ※ http://mdcc.cx/


signature.asc
Description: Digital signature

Bug#754565: future of Moodle in Debian stable/unstable (was: Re: [moodle-packaging] Bug#754565: Bug#754565: Bug#754565: Non free icc profile)

[Joost van Baal-Ilić]

Hi Dan e.a.,

Thanks a lot for getting in touch with Debian about this; much appreciated.  I
am currently working on packaging latest moodle  keeping it up to date in
Debian unstable, see https://packages.debian.org/sid/moodle and especially
http://metadata.ftp-master.debian.org/changelogs//main/m/moodle/moodle_2.7.5+dfsg-1_changelog
for what I did.  At Tilburg University we are running moodle on some Debian
systems; we have an interest in keeping it working for us.  I basically took
over the work from Thijs.

Op Thu, Jan 22, 2015 at 07:47:17AM + schreef Dan Poltawski:
 On 22 January 2015 at 06:34, Riley Baird
 bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
  P.S. I tried writing a message on the moodle forums to give them a heads
  up on the situation, but the spam filter stopped me. It told me to send
  my post to he...@moodle.org, so hopefully it will still get through.
 
 'Upstream' here. Apologies that you got hit by a spam filter (I'm
 afraid we were getting hit quite aggressively by first time link
 spammers which is probably the cause of your filtering). Thank you
 very much for trying to get in touch with us.
 
 I've been cc'd on the Moodle debian bugs for quite some time and i'm
 afraid that this is a bit of a cycle with the package. Quite some time
 ago I was part of a team to keep up with keeping the package in order,
 but eventually could not keep on top of it - then others like Tomasz
 Muras and Thijs Kinkhorst have valiantly tried to get it in order. See
 #494642 #647489 #747084 etc.
 
 So much as it saddens me - I think this is the right course of action.
 There is little evidence to suggest that the package is widely used
 which makes it even less motivating for contributors for the
 significant amount of work it takes to keep up with our wide ranging
 upstream security fixes.

Yes, it is quite a lot of work; Thijs managed to keep the package in shape, I'm
convinced I can do it too.  However, I don't think it's wise to offer moodle in
Debian stable: I can't promise to offer a secure moodle with Debian stable.  If
other Debian people stand up and offer a hand, that might change hint hint
:)

Bye,

Joost

-- 
 rorate caeli desuper et nubes pluant justum --Isa 45:8
Tilburg University, The Netherlands * http://abramowitz.uvt.nl/
http://mdcc.cx/  ※   http://ad1810.com/


signature.asc
Description: Digital signature

Bug#754565: [moodle-packaging] Bug#754565: Fwd: future of Moodle in Debian stable/unstable (was: Re: Bug#754565: Bug#754565: Bug#754565: Non free icc profile)

[Joost van Baal-Ilić]

Op Wed, Feb 04, 2015 at 10:22:59AM + schreef Dan Poltawski:
 On Wed, Feb 4, 2015 at 8:54 AM, Joost van Baal-Ilić
 joostvb+moo...@uvt.nl wrote:
  I am currently working on packaging latest moodle  keeping it up to date in
  Debian unstable, see https://packages.debian.org/sid/moodle and especially
  http://metadata.ftp-master.debian.org/changelogs//main/m/moodle/moodle_2.7.5+dfsg-1_changelog
  for what I did.  At Tilburg University we are running moodle on some Debian
  systems; we have an interest in keeping it working for us.  I basically took
  over the work from Thijs.
 
 Thank you! Please feel free to get in touch with me if we can be of help.
 
 ps. Noting Rileys post on moodle.org was eventually posted here:
 https://moodle.org/mod/forum/discuss.php?d=278847

Thanks for that.

As long as moodle will be in Debian sid/unstable only; it will be mildly
usefull.  As soon as it gets more contributors working on the Debian package,
it can enter testing (currently named jessie, will get named stretch in
about a month or so).  It would be awesome if a long-term-maintained moodle
(like the 2.7 branch) get shipped with a stable Debian release like e.g.
stretch.  Sites like Tilburg University rely on a stable security-maintained
moodle.  We're not realy that eager to implement and upgrade to new moodles
with new features every month or so.  We'd rather do such a thing every 2 year
or so.  I'm sure we're not the only one.

BTW, there's http://bugs.debian.org/775842, listing bugs in a previous moodle
version.  Will get to investigate which one of those are no longer present in
https://packages.debian.org/sid/moodle .

HTH, Bye,

Joost

PS: Dan: feel free to quote me on
https://moodle.org/mod/forum/discuss.php?d=278847 .

-- 
5 years from now everyone will be running free GNU on their 200
MIPS, 64M SPARCstation-5 --Andrew S. Tanenbaum, 30 Jan 1992
http://mdcc.cx/  ※   http://ad1810.com/
Tilburg University, The Netherlands * http://abramowitz.uvt.nl/


signature.asc
Description: Digital signature

Bug#775842: #775842 moodle: Multiple security issues

[Joost van Baal-Ilić]

Hi,

Thanks for reporting this.  Likely, some of the issues have been fixed
in moodle_2.7.5+dfsg-1 which just got ACCEPTED in unstable.

I'll investigate the details one of these days.

Bye,

Joost




signature.asc
Description: Digital signature

Bug#754565: moodle removal

[Joost van Baal-Ilić]

Hi,

I don't think removal of moodle right now is a sane thing.  I'll upload
a final 2.7.2 package to unstable within about 5 weeks.

There has been a private discussion between me, Thijs Kinkhorst and Moritz
Mühlenhoff about this.

Thanks, Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754565: moodle removal

[Joost van Baal-Ilić]

On Tue, Jan 27, 2015 at 11:21:22AM +0100, Joost van Baal-Ilić wrote:
 Hi,
 
 I don't think removal of moodle right now is a sane thing.  I'll upload
 a final 2.7.2 package to unstable within about 5 weeks.
 
 There has been a private discussion between me, Thijs Kinkhorst and Moritz
 Mühlenhoff about this.

FWIW, my preliminary work is available from http://mdcc.cx/tmp/moodle/ .

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767193: mbt: 3.2.10-5 must not be in jessie

[Joost van Baal-Ilić]

Package: mbt
Version: 3.2.10-5
Severity: serious

This package of mbt should not be in jessie: a library transition
in the mbt/timbl/dimbl/frog/libfolia/ticcutils/ucto - suite is upcoming.
This transition will take place in unstable; transitioned packages
are targeted for zurg.  There is no time for proper testing before
the freeze of jessie.

Thanks, Bye,

Joost



On Tue, Oct 28, 2014 at 11:04:32PM +, Debian FTP Masters wrote:
 
 Accepted:
 
 Source: mbt
 Binary: mbt libmbt1-dev libmbt1
 Architecture: source amd64
 Version: 3.2.10-5
 Distribution: unstable
 Urgency: low
 Maintainer: Debian Science Team 
 debian-science-maintain...@lists.alioth.debian.org
 Changed-By: Joost van Baal-Ilić joos...@debian.org
 Description:
  libmbt1- memory-based tagger-generator and tagger - runtime
  libmbt1-dev - memory-based tagger-generator and tagger - development
  mbt- memory-based tagger-generator and tagger
 Changes:
  mbt (3.2.10-5) unstable; urgency=low
  .
* debian/control: migrated version control from Subversion to git (still on
  Debian's Alioth).
* debian/*: change version control tags from Subversion to git.
* debian/watch: more strict.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767203: postfix: default install vulnerable for POODLE TLS attack

[Joost van Baal-Ilić]

package: postfix
version: 2.9.6-2
tag: upstream
severity: critical

Hi,

The Postfix Debian package ships with a default list of supported TLS protocols
which makes it vulnerable to the POODLE TLS attack:

 % postconf smtp_tls_mandatory_protocols
 smtp_tls_mandatory_protocols = !SSLv2

This is the upstream default:

 % postconf -d smtp_tls_mandatory_protocols
 smtp_tls_mandatory_protocols = !SSLv2

Other vulnerable daemon settings are:

 lmtp_tls_mandatory_protocols = !SSLv2
 lmtp_tls_protocols = !SSLv2

 smtp_tls_mandatory_protocols = !SSLv2
 smtp_tls_protocols = !SSLv2

 smtpd_tls_mandatory_protocols = !SSLv2

It would be nice if postfix would ship with a /etc/postfix/main.cf which
features

 tls_protocols = !SSLv2, !SSLv3

 smtp_tls_protocols = $tls_protocols
 smtp_tls_mandatory_protocols = $tls_protocols

 lmtp_tls_protocols = $tls_protocols
 lmtp_tls_mandatory_protocols = $tls_protocols

 smtpd_tls_protocols = $tls_protocols
 smtpd_tls_mandatory_protocols = $tls_protocols

 tlsproxy_tls_protocols = $tls_protocols
 tlsproxy_tls_mandatory_protocols = $tls_protocols

This would make the default install no longer vulnerable for POODLE.

Thanks to Wessel Dankers for reporting the problem to me, and suggesting the
mentioned fixes.

Thanks for maintaining the Postfix package, Bye,

Joost

PS: this bug is somewhat related to
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729188#103

PPS  FWIW: on https://blog.surfnet.nl/?p=3290 there's a more elaborate list of
current sane defaults.  Currently,

 tls_ciphers = 
ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA
 lmtp_tls_ciphers = $tls_ciphers
 lmtp_tls_mandatory_ciphers = $tls_ciphers
 smtp_tls_ciphers = $tls_ciphers
 smtp_tls_mandatory_ciphers = $tls_ciphers
 smtpd_tls_ciphers = $tls_ciphers
 smtpd_tls_mandatory_ciphers = $tls_ciphers
 tlsproxy_tls_ciphers = $tls_ciphers
 tlsproxy_tls_mandatory_ciphers = $tls_ciphers

is sane too (but not future-proof).



signature.asc
Description: Digital signature

Bug#725586: debian-faq: FTBFS: make[1]: *** [po4a-translate] Error

[Joost van Baal-Ilić]

On Sun, Sep 28, 2014 at 08:15:32AM +0200, Petter Reinholdtsen wrote:
 
 This RC bug have caused debian-faq to be removed from Jessie, while it
 is also tagged pending.  A new version is waiting in VCS.  Is this
 intentional, or do you plan to upload a fix in time for this package
 to make it into the next stable release?

I've commmited some other changes to VC recently.  It'd be really cool if we
could ship the FAQ with Jessie.  I have this vague plan to upload, but lots of
other stuff to do too.  So: don't hold you breath; NMU's welcome, I'd guess.

Last word is Javier's though, he's listed as maintainer.

Thanks for your interest, Bye,

Joost


-- 
Making the first step toward using free software can be a nerve-wracking 
experience
for even the most experienced of computer users.   
--http://fsf.org
irc:joostvb@oftc,freenode http://mdcc.cx/
http://ad1810.com/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752872: libapr1: file locking is broken, leading to file corruption in e.g. libapache2-mod-auth-cas session files

[Joost van Baal-Ilić]

Package: libapr1
Version: 1.4.6-3+deb7u1
Severity: grave
Tags: patch, upstream

Hi,

libapr1 uses fcntl(F_SETLKW) for locking files, but this is not compatible
with multithreaded programs. fcntl(F_SETLKW) has the strange quirk that if
an open and locked file is opened and then closed a second time in the same
process, the lock is lost. This is something that may happen frequently in
multithreaded programs, such as the apache2 mpm worker.

fd1 = open(foo, O_RDWR|O_CREAT);
fcntl(fd1, F_SETLKW, ...);
/* file is now locked */
fd2 = open(foo, O_RDONLY);
/* file is still locked */
close(fd2);
/* file is no longer locked! */
...

Since file locking in libapr1 is broken^Wviolates the principle of least
surprise, dataloss can very likely happen.

I haven't checked the POSIX specs to see if this is expected behavior but I
was able to reproduce it on both Linux and FreeBSD. A patch is attached
that extends the libapr1 test suite to detect this situation.

While libapr1 defaults to fcntl() locking it also supports flock(), which
does not have the problems outlined above. A patch is attached which makes
libapr1 use flock() even if fcntl() locking is available.

We found this bug when investigating error messages from
libapache2-mod-auth-cas that its session files were getting corrupted:

 [error] [client 127.0.0.1] MOD_AUTH_CAS: Error parsing XML content for 
'01234567890abcdef01234567890abcd' (Internal error), referer: 
https://www.example.com/

Switching to the flock() mechanism solved these problems. In other words,
this bug is causing problems in real life, and is not just theoretical.

This bug was found, reported to me and patched by Wessel Dankers.

Thanks, Bye,

Joost van Baal-Ilić

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
The Netherlands
diff -ur apr-1.4.6,orig/file_io/unix/flock.c apr-1.4.6,fixed/file_io/unix/flock.c
--- apr-1.4.6,orig/file_io/unix/flock.c	2006-08-03 12:55:31.0 +0200
+++ apr-1.4.6,fixed/file_io/unix/flock.c	2014-06-27 10:28:48.721611923 +0200
@@ -27,7 +27,7 @@
 {
 int rc;
 
-#if defined(HAVE_FCNTL_H)
+#if defined(HAVE_FCNTL_H)  0
 {
 struct flock l = { 0 };
 int fc;
diff -ur apr-1.4.6,orig/test/testflock.c apr-1.4.6,test/test/testflock.c
--- apr-1.4.6,orig/test/testflock.c	2010-03-07 16:06:47.0 +0100
+++ apr-1.4.6,test/test/testflock.c	2014-06-27 10:18:59.786062499 +0200
@@ -60,6 +60,7 @@
 static void test_withlock(abts_case *tc, void *data)
 {
 apr_file_t *file;
+apr_file_t *file2;
 apr_status_t rv;
 int code;
 
@@ -71,6 +72,12 @@
 rv = apr_file_lock(file, APR_FLOCK_EXCLUSIVE);
 APR_ASSERT_SUCCESS(tc, Could not lock the file., rv);
 ABTS_PTR_NOTNULL(tc, file);
+
+/* open and close the file another time, to see if that messes with things */
+rv = apr_file_open(file2, TESTFILE, APR_FOPEN_WRITE, APR_OS_DEFAULT, p);
+APR_ASSERT_SUCCESS(tc, Could not open file., rv);
+ABTS_PTR_NOTNULL(tc, file2);
+(void) apr_file_close(file2);
 
 code = launch_reader(tc);
 ABTS_INT_EQUAL(tc, FAILED_READ, code);


signature.asc
Description: Digital signature

Bug#735789: caspar: FTBFS: /«PKGBUILDDIR»/missing: line 81: aclocal-1.14: command not found

[Joost van Baal-Ilić]

tags 735789 +confirmed
thanks

Hi David,

Confirmed, will get to it soonish.

Thanks, Bye,

Joost

On Fri, Jan 17, 2014 at 08:50:12PM +0100, David Suárez wrote:
 Source: caspar
 Version: 20140106-1
 Severity: serious
 Tags: jessie sid
 User: debian...@lists.debian.org
 Usertags: qa-ftbfs-20140114 qa-ftbfs
 Justification: FTBFS on amd64
 
 Hi,
 
 During a rebuild of all packages in sid, your package failed to build on
 amd64.
 
 Relevant part (hopefully):
  make[1]: Entering directory `/«PKGBUILDDIR»'
  CDPATH=${ZSH_VERSION+.}:  cd .  /bin/bash /«PKGBUILDDIR»/missing 
  aclocal-1.14 
  /«PKGBUILDDIR»/missing: line 81: aclocal-1.14: command not found
  WARNING: 'aclocal-1.14' is missing on your system.
   You should only need it if you modified 'acinclude.m4' or
   'configure.ac' or m4 files included by 'configure.ac'.
   The 'aclocal' program is part of the GNU Automake package:
   http://www.gnu.org/software/automake
   It also requires GNU Autoconf, GNU m4 and Perl in order to run:
   http://www.gnu.org/software/autoconf
   http://www.gnu.org/software/m4/
   http://www.perl.org/
  make[1]: *** [aclocal.m4] Error 127
 
 The full build log is available from:

 http://aws-logs.debian.net/ftbfs-logs/2014/01/14/caspar_20140106-1_unstable.log
 
 A list of current common problems and possible solutions is available at
 http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
 
 About the archive rebuild: The rebuild was done on EC2 VM instances from
 Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
 failed build was retried once to eliminate random failures.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#710264: Bug #710264 systraq: postinst uses /usr/share/doc content (Policy 12.3)

[Joost van Baal-Ilić]

Thanks for  reporting this bug.  Have prepared preliminary fixed package, for 
now
available from http://mdcc.cx/tmp/.  WIll upload soonish.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721495: mbtserver: Wrong order of build-depends

[Joost van Baal-Ilić]

reassign: timblserver
tags: +pending
thanks

Hi Kurt,

On Sun, Sep 01, 2013 at 12:42:20PM +0200, Kurt Roeckx wrote:
 Source: mbtserver
 Version: 0.7-2
 Severity: serious
 
 Hi,
 
 You have a build-depends on libtimblserver3-dev | libtimblserver-dev,
 but libtimblserver3-dev doesn't exist.  We will only try to
 install the first alternative so it fails to install the
 build-depends.

Thanks for reporting this.  I'm preparing timblserver (1.7-4)
which has:

  * debian/libtimblserver3-dev.install, debian/libtimblserver-dev.install,
debian/control: rename libtimblserver-dev to libtimblserver3-dev.  Upstream
cannot guarantee strong compatibility yet.  This fixes (part of) mbtserver:
FTBFS: unsatisfiable build-dependencies: libtimblserver3-dev, libmbt1-dev.
Thanks Lucas Nussbaum (Closes: #713119).  It fixes Bug#721495: mbtserver:
Wrong order of build-depends. Thanks Kurt Roeckx (Closes: #721495).

I'll upload this one, and more fixed related ticc software within one week.

Bye,

Joost

PS: Excuse me for abusing build daemon CPU cycles; it won't happen again


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#713119: reassign 713119 to mbt / Re: Bug#713119: mbtserver: FTBFS: unsatisfiable build-dependencies: libtimblserver3-dev, libmbt1-dev

[Joost van Baal-Ilić]

reassign 713119 mbt
thanks



On Sat, Jun 22, 2013 at 01:37:51PM +0200, Lucas Nussbaum wrote:
 Source: mbtserver
 Version: 0.7-2
 Severity: serious
 Tags: jessie sid
 User: debian...@lists.debian.org
 Usertags: qa-ftbfs-20130620 qa-ftbfs
 Justification: FTBFS on amd64
 
 Hi,
 
 During a rebuild of all packages in sid, your package failed to build on
 amd64.
 
 Relevant part:
  ┌──┐
  │ Install mbtserver build dependencies (apt-based resolver) 
 │
  └──┘
  
snip
  
  The following packages have unmet dependencies:
   sbuild-build-depends-mbtserver-dummy : Depends: libtimblserver3-dev but it 
  is not installable
  Depends: libmbt1-dev but it is not 
  installable
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
 
 The full build log is available from:

 http://aws-logs.debian.net/ftbfs-logs/2013/06/20/mbtserver_0.7-2_unstable.log

Thanks for reporting this issue.  It should get fixed in the upload I just did 
of
mbt (3.2.10-4):

   * debian/libmbt1-dev.install, debian/libmbt-dev.install, debian/control:
 rename libmbt-dev to libmblt1-dev.  Upstream cannot guarantee strong
 compatibility yet.

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721140: FTBFS: build-depends on old libticcutils2-dev

[Joost van Baal-Ilić]

Hi Samuel,

Thanks for reporting this bug!

On Wed, Aug 28, 2013 at 02:49:17PM +0200, Samuel Thibault wrote:
 Package: timbl
 Version: 6.4.4-3
 Severity: grave
 Justification: FTBFS
 
 Hello,
 
 timbl currently can't build because it depends on the old libticcutils2-dev, 
 which is now uninstallable:
 
 libticcutils2-dev : Depends: libticcutils2 (= 0.4-3) but it is not going to 
 be installed
 
 Please change the dependency to libticcutils-dev.

timbl (6.4.4-3) has libticcutils2-dev | libticcutils-dev in it's 
Build-Depends, which is
satisfyable.

This source package has succesfully been build on amd64:
https://buildd.debian.org/status/fetch.php?pkg=timblarch=amd64ver=6.4.4-3stamp=1372635651

timbl has been bin-NMU'd: timbl 6.4.4-3+b1.  I believe this is in order
to deal with http://release.debian.org/transitions/html/ticcutils.html .

To my understanding, this binNMU should produce new installable timbl binary
packages.  No changes to the timbl source package are needed.

I guess this bug can get closed.  Do you agree?

Bye,

Joost


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#700389: reopening 700389

[Joost van Baal-Ilić]

reopen 700389
thanks

bug was reported for package timbl, but closed in upload of package frog.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#700389: libtimbl3-dev: Broken dependencies make other packages FTBFS (needs ticcutils/StringOps.h from libticcutils1-dev)

[Joost van Baal-Ilić]

Hi Peter,

On Sun, May 26, 2013 at 03:18:33PM +0100, peter green wrote:
 This bug was filed against libtimbl3-dev and the discussion in this
 bug claims it's an issue in that package but the bug was closed with
 an upload of frog.
 
 Closing a bug in one package with an upload of another leaves the
 bug in a somewhat confusing state. The bug is closed but it's
 still considered to affect the versions of the original package.
 That in turn means that britney is refusing to migrate timbl to
 testing which in turn means that frog is not buildable in testing
 (which is a rc issue in it's own right).
 
 If you belive that fixing this bug in libtimbl3-dev is needed then
 please do so so that timbl can migrate. Otherwise please fixup the
 bug so it's filed against and closed by the same package.

libtimbl3-dev is obsolete, it should get removed from unstable (and possibly
jessie (testing)) soonish.  .  I'll investigate the issue one of these days,
and take needed actions.  Thanks for your bugreport,

Bye,

Joost

-- 
irc:joostvb@{OFTC,freenode} ∙ http://mdcc.cx/ ∙ http://ad1810.com/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#700389: libtimbl3-dev: Broken dependencies make other packages FTBFS (needs ticcutils/StringOps.h from libticcutils1-dev)

[Joost van Baal-Ilić]

tags 700389 +pending
thanks


And this next release will likely happen in march.

Bye,

Joost


On Tue, Feb 12, 2013 at 11:43:58AM +0100, Joost van Baal-Ilić wrote:
 Hi Roland,
 
 Thanks for your bugreport.  Ko van der Sloot and me are working on the issue.
 The issue will get fixed in a next release.
 
 Bye,
 
 Joost
 
 On Tue, Feb 12, 2013 at 11:12:33AM +0100, Roland Stigge wrote:
  Package: timbl
  Version: 6.4.3-1
  Severity: serious
  Tags: sid
  User: debian-powerpc...@breakpoint.cc
  Usertags: powerpcspe
  
  Hi,
  
  trying to build frog[1] on powerpcspe[2], I got this result[3]:
  
  make[3]: Entering directory `/«PKGBUILDDIR»/build/2.6/src'
  g++ -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./src -I..  
  -I/«PKGBUILDDIR»/./include   -g -O2 -fstack-protector 
  --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -pthread 
  -fopenmp -I/usr/include  -I/usr/include/libxml2   -I/usr/include/libxml2   
  -I/usr/include/libxml2   -I/usr/include/libxml2   -I/usr/include/libxml2   
  -I/usr/include/python2.7 -c -o mbma_mod.o /«PKGBUILDDIR»/./src/mbma_mod.cxx
  In file included from /usr/include/timbl/TimblAPI.h:37:0,
   from /«PKGBUILDDIR»/./src/mbma_mod.cxx:34:
  /usr/include/timbl/Types.h:42:33: fatal error: ticcutils/StringOps.h: No 
  such file or directory
  compilation terminated.
  
  Looks like /usr/include/timbl/Types.h in libtimbl3-dev references
  ticcutils/StringOps.h from libticcutils1-dev but doesn't depend on it.
  
  You can reproduce this issue with a simple test program like:
  
  #include timbl/Types.h
  int main() { return 0; }
  
  Just checked that the frog FTBFS issue is also present in amd64.
  
  Adding the libticcutils1-dev fixes this. However, is appears that further, 
  frog
  also uses timbl/LogStream.h which isn't (anymore?) in libtimbl3-dev.
  
  Thanks in advance,
  
  Roland
  
  
  [1] http://packages.qa.debian.org/f/frog.html
  [2] http://wiki.debian.org/PowerPCSPEPort
  [3] http://buildd.debian-ports.org/status/package.php?p=frog
  
  -- System Information:
  Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: i386 (i686)
  
  Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
  Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/bash
  
 


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#700389: libtimbl3-dev: Broken dependencies make other packages FTBFS (needs ticcutils/StringOps.h from libticcutils1-dev)

[Joost van Baal-Ilić]

Hi Roland,

Thanks for your bugreport.  Ko van der Sloot and me are working on the issue.
The issue will get fixed in a next release.

Bye,

Joost

On Tue, Feb 12, 2013 at 11:12:33AM +0100, Roland Stigge wrote:
 Package: timbl
 Version: 6.4.3-1
 Severity: serious
 Tags: sid
 User: debian-powerpc...@breakpoint.cc
 Usertags: powerpcspe
 
 Hi,
 
 trying to build frog[1] on powerpcspe[2], I got this result[3]:
 
 make[3]: Entering directory `/«PKGBUILDDIR»/build/2.6/src'
 g++ -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./src -I..  
 -I/«PKGBUILDDIR»/./include   -g -O2 -fstack-protector 
 --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -pthread 
 -fopenmp -I/usr/include  -I/usr/include/libxml2   -I/usr/include/libxml2   
 -I/usr/include/libxml2   -I/usr/include/libxml2   -I/usr/include/libxml2   
 -I/usr/include/python2.7 -c -o mbma_mod.o /«PKGBUILDDIR»/./src/mbma_mod.cxx
 In file included from /usr/include/timbl/TimblAPI.h:37:0,
  from /«PKGBUILDDIR»/./src/mbma_mod.cxx:34:
 /usr/include/timbl/Types.h:42:33: fatal error: ticcutils/StringOps.h: No such 
 file or directory
 compilation terminated.
 
 Looks like /usr/include/timbl/Types.h in libtimbl3-dev references
 ticcutils/StringOps.h from libticcutils1-dev but doesn't depend on it.
 
 You can reproduce this issue with a simple test program like:
 
 #include timbl/Types.h
 int main() { return 0; }
 
 Just checked that the frog FTBFS issue is also present in amd64.
 
 Adding the libticcutils1-dev fixes this. However, is appears that further, 
 frog
 also uses timbl/LogStream.h which isn't (anymore?) in libtimbl3-dev.
 
 Thanks in advance,
 
 Roland
 
 
 [1] http://packages.qa.debian.org/f/frog.html
 [2] http://wiki.debian.org/PowerPCSPEPort
 [3] http://buildd.debian-ports.org/status/package.php?p=frog
 
 -- System Information:
 Debian Release: 7.0
   APT prefers unstable
   APT policy: (500, 'unstable'), (1, 'experimental')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash
 


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694365: release.debian.org: unblock: aephea/10.008-2

[Joost van Baal-Ilić]

On Mon, Nov 26, 2012 at 09:55:25PM +0100, Joost van Baal-Ilić wrote:
 
 Please unblock package aephea
 This upload fixes RC bug #694365 (file conflict between two packages).

unblock aephea/10.008-2


I just uploaded it to ftp.upload.debian.org:/pub/UploadQueue/ .

Bye,

Joost



 PS: full diff between aephea 10.008-1 (currently in testing/wheezy)
 and the proposed one is:
 
 diff -Nru aephea-10.008/debian/changelog aephea-10.008/debian/changelog
 --- aephea-10.008/debian/changelog  2011-05-12 02:13:25.0 +0200
 +++ aephea-10.008/debian/changelog  2012-11-26 10:14:28.0 +0100
 @@ -1,3 +1,10 @@
 +aephea (10.008-2) testing-proposed-updates; urgency=low
 +
 +  * debian/control: add missing Breaks+Replaces: zoem-doc, to enable upgrades
 +from squeeze to wheezy.  Thanks Andreas Beckmann.  (Closes: #694365)
 +
 + -- Joost van Baal-Ilić joos...@debian.org  Mon, 26 Nov 2012 10:13:51 +0100
 +
  aephea (10.008-1) unstable; urgency=low
  
* First upload (Closes: #620479).
 diff -Nru aephea-10.008/debian/control aephea-10.008/debian/control
 --- aephea-10.008/debian/control2011-04-27 07:40:21.0 +0200
 +++ aephea-10.008/debian/control2012-11-26 10:12:59.0 +0100
 @@ -11,6 +11,8 @@
  Package: aephea
  Architecture: all
  Depends: ${shlibs:Depends}, ${misc:Depends}
 +Breaks: zoem-doc
 +Replaces: zoem-doc
  Recommends: zoem
  Description: text-based authoring tool for HTML
   Aephea is an HTML authoring framework.  It enforces HTML well-formedness


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694365: release.debian.org: unblock: aephea/10.008-2

[Joost van Baal-Ilić]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package aephea

This upload fixes RC bug #694365 (file conflict between two packages).

unblock aephea/10.008-2

Thanks,

Joost



PS: full diff between aephea 10.008-1 (currently in testing/wheezy)
and the proposed one is:

diff -Nru aephea-10.008/debian/changelog aephea-10.008/debian/changelog
--- aephea-10.008/debian/changelog  2011-05-12 02:13:25.0 +0200
+++ aephea-10.008/debian/changelog  2012-11-26 10:14:28.0 +0100
@@ -1,3 +1,10 @@
+aephea (10.008-2) testing-proposed-updates; urgency=low
+
+  * debian/control: add missing Breaks+Replaces: zoem-doc, to enable upgrades
+from squeeze to wheezy.  Thanks Andreas Beckmann.  (Closes: #694365)
+
+ -- Joost van Baal-Ilić joos...@debian.org  Mon, 26 Nov 2012 10:13:51 +0100
+
 aephea (10.008-1) unstable; urgency=low
 
   * First upload (Closes: #620479).
diff -Nru aephea-10.008/debian/control aephea-10.008/debian/control
--- aephea-10.008/debian/control2011-04-27 07:40:21.0 +0200
+++ aephea-10.008/debian/control2012-11-26 10:12:59.0 +0100
@@ -11,6 +11,8 @@
 Package: aephea
 Architecture: all
 Depends: ${shlibs:Depends}, ${misc:Depends}
+Breaks: zoem-doc
+Replaces: zoem-doc
 Recommends: zoem
 Description: text-based authoring tool for HTML
  Aephea is an HTML authoring framework.  It enforces HTML well-formedness


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694365: aephea: missing Breaks+Replaces: zoem-doc

[Joost van Baal-Ilić]

Thanks, I'll get to it soonish.

Bye,

Joost

On Sun, Nov 25, 2012 at 10:06:48PM +0100, Andreas Beckmann wrote:
 Package: aephea
 Version: 10.008-1
 Severity: serious
 User: trei...@debian.org
 Usertags: edos-file-overwrite
 
 Architecture: amd64
 Distribution: squeeze-wheezy (partial) upgrade
 
 Hi,
 
 automatic installation tests of packages that share a file and at the
 same time do not conflict by their package dependency relationships has
 detected the following problem:
 
   Selecting previously deselected package zoem-doc.
   (Reading database ... 6286 files and directories currently installed.)
   Unpacking zoem-doc (from .../zoem-doc_08-248-1_all.deb) ...
   Setting up zoem-doc (08-248-1) ...
 
   Selecting previously deselected package aephea.
   (Reading database ... 6430 files and directories currently installed.)
   Unpacking aephea (from .../aephea_10.008-1_all.deb) ...
   dpkg: error processing /var/cache/apt/archives/aephea_10.008-1_all.deb 
 (--unpack):
trying to overwrite '/usr/share/man/man7/pud.7.gz', which is also in 
 package zoem-doc 08-248-1
 
 
 This is a serious bug as it makes installation/upgrade fail, and
 violates sections 7.6.1 and 10.1 of the policy.
snip


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#688997: youtube-dl: Needs update to newer version to fix youtube downloading

[Joost van Baal-Ilić]

Hi,

On Wed, Oct 10, 2012 at 01:33:03PM -0300, Rogério Brito wrote:
 On Tue, Oct 9, 2012 at 3:40 PM, Julien Cristau jcris...@debian.org wrote:
  On Tue, Oct  9, 2012 at 15:25:44 -0300, Rogério Brito wrote:
  Too many changes? Which ones? Compared to my last upload, there aren't
  really.
 
  Compared to the version currently in wheezy.
 
 I see. Well, those are about 7 months of development (not so active, but...)
 
 But that is, in a sense, the nature of packages/programs that deal
 with web scrapping: all of them are highly subject to drastic changes.
 (Unfortunate, I know). But that affects youtube-dl, clive, cclive,
 get-flash-videos and many, many other packages in a similar vein.
 
 I want to work with you in getting youtube-dl in wheezy and, also, not
 breaking other programs like freevo. What can we do?

Splitting the package in a part containing only data, describing how to parse,
and one containing the actual code.  The data-part will change depending on
developments in youtube webui.  In Debian stable, the code-part will only
change in order to fix security or other really critical bugs.  For keeping
the data-part up to date, users should use debian-volatile. That's where
the data-part shoud get uploaded to.

Bye,

Joost

-- 
Being owned by someone used to be called slavery -- now it's called
commitment.
http://mdcc.cx/   --from the fortune cookies collection


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#683555: release.debian.org: unblock: pear-horde-channel/4

[Joost van Baal-Ilić]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello release team,

Mathieu Parent uploaded a pear-horde-channel source package to unstable.
This builds the pear-horde-channel binary package, which basically consists
of just the file /usr/share/php/.channels/pear.horde.org.reg.  This file
is needed for building

 php-horde-activesync
 php-horde-alarm
 php-horde-argv
 php-horde-auth
 php-horde-autoloader
 php-horde-browser
 php-horde-cache
 [...]
 php-horde-vfs
 php-horde-view
 php-horde-xml-element
 php-horde-xml-wbxml

(see (Bug #683554 RM: horde3 and reverse dependencies) for the complete list).

In current testing, the pear-horde-channel binary package is created from the
horde3 source package, which is scheduled for removal from Debian (Bug#683554:
RM: horde3 and reverse dependencies).

The debdiff of the old and new binary package is available from
http://mdcc.cx/tmp/pear-horde-channel/pear-horde-channel_3.3.12%2bdebian0-2.2_vs_4.debdiff
 .
The files debian/copyright as well as a full diff are available from
http://mdcc.cx/tmp/pear-horde-channel/ .

Unfortunately, the new pear-horde-channel Debian source package lacks
instructions on how to recreate the generated file pear.horde.org.reg.  I've
just filed Bug #690463 reporting this issue.

In the mean time, please allow pear-horde-channel/4 to enter Debian testing.

Thank you for considering.

Joost

unblock: pear-horde-channel/4


PS: See Bug#683628 release-notes: Re: Horde and Kolab removed for even
more background information.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#659987: sqlgrey: impossible to set boolean options to false

[Joost van Baal-Ilić]

Package: sqlgrey
Version: 1.8.0rc2-1
Severity: critical
Tags: patch, upstream

Hi,

Op Wed 15 Feb 2012 om 04:17:57 +0100 schreef Wessel Dankers:
 
 The sqlgrey script contains the following line:
 
   $dflt{$var} = $value || 1;
 
 Which means, “if you try to set this variable to a false value, we'll set
 to it 1 anyway”. The probable intention was to prevent undefined values,
 but this makes it impossible to configure sqlgrey. Suggested patch:

--

--- /usr/sbin/sqlgrey   2010-02-11 09:45:53.0 +0100
+++ /usr/sbin/sqlgrey   2012-02-15 16:01:38.102502020 +0100
@@ -2492,7 +2492,7 @@
 s/\s+$//;   # no trailing white
 next unless length; # anything left ?
 my ($var, $value) = split(/\s*=\s*/, $_, 2);
-$dflt{$var} = $value || 1;
+$dflt{$var} = $value // '';
 }
 close CONF
or die Couldn't close config file $config_file\n;

--


Bye,

Joost - in his role as Wessel's secretary

-- 
Joost van Baal-Ilić   http://abramowitz.uvt.nl/
 Tilburg University
mailto:joostvb.uvt.nl   The Netherlands


signature.asc
Description: Digital signature

Bug#659987: sqlgrey: impossible to set boolean options to false

[Joost van Baal-Ilić]

severity 659987 normal
thanks

Renders package unusable only when combining squeeze with lenny systems



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#621760: frog: FTBFS everywhere: configure: error: Could not link test program to Python

[Joost van Baal-Ilić]

Hi Cyril,

Thanks for your bugreport.  The issue _might_ be fixed in today's upload
http://packages.debian.org/sid/frog (0.12.6-2).

Builds are now waiting for http://ftp-master.debian.org/new/ucto_0.4.9-3.html.
This package can only propagate once
http://ftp-master.debian.org/new/libfolia_0.5-2.html is accepted.

http://ftp-master.debian.org/new/mbt_3.2.7-3.html is also needed.

Once all this is accepted, and build at
https://buildd.debian.org/status/package.php?p=frog _still_ fails, I'll take
another look.  It'll be fixed for sure before wheezy gets frozen :)

BTW: patches / nmu's are very welcome.

Bye,

Joost



signature.asc
Description: Digital signature