pload.
+ * Add explicit type declarations to fix build error with GCC-14.
+Closes: #1075266
+
+ -- Christoph Biedl Wed, 06 Nov 2024
20:21:52 +0100
+
mgetty (1.2.1-1.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mgetty-1.2.1/debian/patches/90-gcc-14
mgetty-1.2.1/d
Control: tags 1075266 pending
(...)
> cd contrib; /usr/bin/make g3toxwd g3tolj
> make[1]: Entering directory '/<>/contrib'
> cc g3toxwd.c -o g3toxwd
> g3toxwd.c:418:8: error: type defaults to ‘int’ in declaration of ‘hscale’
> [-Wimplicit-int]
> 418 | static hscale = 100;
> |
file
+limits. Closes: 918316
+ * Fix build on (most) 32 bit architectures. Closes: #1069426
+Kudos to Guillem Jover for taking care of that.
+ * Simplify test so it will not time out. Closes: #918316 (again)
+
+ -- Christoph Biedl Sun, 07 Jul 2024
13:44:09 +0200
+
nocache (1.1-1) uns
Guillem Jover wrote...
> I've provided a PR upstream to fix this at:
>
> https://github.com/Feh/nocache/pull/55
Thanks a lot for that.
@Maintainer: As that change is rather huge and relies on other changes
upstream, I'd rather forward to upstream release 1.2[1] and Guillem's
work on top of it
Control: tags 918316 - pending
Christoph Biedl wrote...
> to fix the issues with this package, I've prepared an NMU for nocache
> (versioned as 1.1-1.1), debdiff below.
Not going to upload this, NMU doesn't make sense without fixing #1069426
as well.
Christoph
signature
m. Closes: #918316 (again)
+
+ -- Christoph Biedl Sun, 09 Jun 2024
18:35:07 +0200
+
nocache (1.1-1) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru
nocache-1.1/debian/patches/1546932589.v1.1-2-gb3016b5.cap-the-number-of-fds-nocache-tracks-und-thus-bound-its-memory-usage.patch
n
Christoph Biedl wrote...
> (and why does the BTS¹ not show Étienne's
> message?).
Never mind, just a race condition.
signature.asc
Description: PGP signature
Étienne Mollier wrote...
> If that helps, the symbols strlcat and strlcpy have been added
> to the glibc 2.38, so I believe it should be safe to remove the
> following symbols without soname bump:
Just came here to say the same (and why does the BTS¹ not show Étienne's
message?). There might be
Control: tags 1071335 pending
James Cameron wrote...
> You may be interested in these upstream commits;
>
> b01478d ("Fix some parts of macro expansion are not guarded")
> 0194b80 ("strerror and memset require string.h")
Thanks a lot for having an eye on the Debian packaging. As you'd expect,
v
Source: systemd
Severity: serious
Tags: patch
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de
Greetings,
systemd build-depends on liblz4-tool but that package is no longer build
from src:lz4 (since 1.9.4-2, uploaded about a week ago). Just replacing
the dependency with lz4 seems to fix this problem
Control: tags 1066850 -moreinfo +pending
Matthias Klose wrote...
> On 14.03.24 21:38, Christoph Biedl wrote:
> > Do you have an idea, an existing solution how to do that?
> dep := $(shell dpkg-query '-f${Depends}' -W libmagic-dev | sed
> 's/.*\(libmagic[a-z0-9]*\)
After getting some help in IRC, I guess the problem boils down to:
1. All architectures provide the t64 variant (libmagic1t64).
2. Some architectures no longer provide the old variant (libmagic1), for
example armhf.
3. Therefore, the install dependency of python3-magic must be the t64 variant.
Control: tags 1066850 moreinfo
Matthias Klose wrote...
> Package: src:python-magic
> Version: 2:0.4.27-2
> Severity: serious
> Tags: sid trixie
>
> the package build-depends on libmagic1, and depends on it. The name was
> recently changed to libmagic1t64.
This is not a real problem as libmagic1t
Control: merge 1066134 1065940
Ups, that had already been reported.
signature.asc
Description: PGP signature
Christoph Biedl wrote...
> So, assuming this is the cause here, the fix is pretty simple:
(...)
> +#ifdef INET6
> if (if6_is_up)
> sif6down(0);
> +#endif
This was silently done as part of
commit 80b8744eb42c7493794f3e3fe0bf1ce14f53e6dd
Author: Eivind Næss
Date:
Source: ppp
Version: 2.4.9-1+1.1
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de
Hi Chris,
ppp no longer builds in unstable here, tested in a minimal chroot. A
build in a testi
Axel Beckert wrote...
> Citing from https://buildd.debian.org/status/package.php?p=aptitude:
(...)
> /usr/include/cppunit/TestAssert.h:161:6: note: template argument
> deduction/substitution failed:
> ../../tests/test_misc.cc:187:5: note: deduced conflicting types for
> parameter ‘const T’ (
Control: tags 1065101 pending
Boyuan Yang wrote...
> Package ngircd depends on binary package libident, but this package has
> been renamed to libident0 due to time64 transition. Please fix the binary
> dependency relationship accordingly. You may need to rebuild the package.
The fix for #106570
Source: libident
Severity: serious
Tags: patch
Version: 0.32-2
X-Debbugs-Cc: by...@debian.org, efing...@packages.debian.org,
vor...@debian.org, debian.a...@manchmal.in-ulm.de
Control: block 1065100 by -1
Control: block 1065101 by -1
For libident, the t64 transition was done in a slightly differe
Boyuan Yang wrote...
> Package ngircd depends on binary package libident, but this package has
> been renamed to libident0 due to time64 transition. Please fix the binary
> dependency relationship accordingly. You may need to rebuild the package.
Well, that is broken anyway at the moment:
(...)
Christoph Biedl wrote...
> after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/
> are gone.
It was suggested in IRC this might be the effect of another package's
upgrade. I find that unlikely since no other package should touch
/usr/lib/molly-guard/ - still,
Package: molly-guard
Version: 0.8.1
Severity: grave
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de
Greetings,
after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/
are gone. As this happened on a second machine today, I reckon it's not
a coincidence.
Current state:
# ls -l /
7.3/debian/changelog2022-10-15 12:46:49.0 +0200
+++ smokeping-2.7.3/debian/changelog2023-09-02 11:50:51.0 +0200
@@ -1,3 +1,11 @@
+smokeping (2.7.3-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove recommendation on echoping which is no longer in Debian.
+
g-ng (4.3.1-0.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * New upstream version 4.3.1
+ * Switch to the pcre2 library. Closes: #46
+
+ -- Christoph Biedl Sun, 30 Jul 2023
12:04:27 +0200
+
syslog-ng (3.38.1-5) unstable; urgency=medium
* Build without Criterion support.
d
Michael Biebl wrote...
> If (bookworm-) backports are a concern, you might also use something like
> this
>
> -libblockdev-crypto2,
> +udisks2 (>= 2.10) | libblockdev-crypto2,
Thanks for the suggestion, will adjust the still-not-yet-happened upload.
Christoph
signature.asc
Descrip
Control: Tags 1040924 +pending
Jeremy Bícha wrote...
> Yes, it's a transition. Sorry that it didn't follow the recommended procedure.
Thanks for the clarification. New version is underway, I'd like to do
some thourough testing, though.
Christoph
signature.asc
Description: PGP signature
Control: tags 1040924 moreinfo
Jeremy Bícha wrote...
> clevis-udisks2 depends on libblockdev-crypto2 which is no longer built
> by libblockdev in Unstable. Please update the manual dependency to
> libblockdev-crypto3
I fail to understand what is happening here. Is this supposed to be a
transitio
user debian-rele...@lists.debian.org
usertags 1022180 + bsp-2023-01-ch-stcergue
thank you
@maintainer:
Excuse my bluntness, but is there a reason to *not* just replace "10"
with "12" as shown below, and previously done in commit 334e9afa
("Switch to using gcc-10 rather than gcc-9. Closes: #978521
Control: tags 1005435 pending
Lucas Nussbaum wrote...
> Source: gpr
> Version: 0.15deb-2
> Severity: serious
> Justification: FTBFS
> > configure: error: Must have libppd installed to compile gpr
This was caused by yours truly as a result of updating src:libppd
almost a year ago. Fix is underwa
Control: tags 984057 + patch pending
Christoph Biedl wrote...
> After staring at this for a while I think upstream did some creepy
> things gcc is understandably
un
> happy, but overall this code in sysdep.h
>
> | st
n number.
+Closes: #1021193
+
+ -- Christoph Biedl Sun, 16 Oct 2022
11:02:35 +0200
+
binutils-arm-none-eabi (17) unstable; urgency=medium
* Make --no-warn-rwx-segments the default.
diff -Nru binutils-arm-none-eabi-17/debian/rules
binutils-arm-none-eabi-17+nmu1/debian/rules
--- binutils-
regression in the visual.
+
+ -- Christoph Biedl Sat, 15 Oct 2022
23:32:41 +0200
+
scalable-cyrfonts (4.18) unstable; urgency=medium
* Raise Standards-Version to 4.5.0.
diff -Nru scalable-cyrfonts-4.18/debian/control
scalable-cyrfonts-4.18+num1/debian/control
--- scalable-cyrfonts-4
block 1020205 by bug 1021845
user debian-rele...@lists.debian.org
usertags 1020205 + bsp-2022-10-de-karlsruhe
thank you
Lucas Nussbaum wrote...
> > cp: cannot stat '/usr/share/fonts/type1/gsfonts/s05l.afm': No such file
> > or directory
This file used to be provided by gsfonts which was rep
# ... without rendering it completely unusable to everyone
severity 992592 important
tags 992592 moreinfo unreproducible
user debian-rele...@lists.debian.org
usertags 992592 + bsp-2022-10-de-karlsruhe
thank you
Pavel Sanda wrote...
> updating debian to bullseye killed access to my desktop environ
tags 984057 + patch
user debian-rele...@lists.debian.org
usertags 984057 + bsp-2022-10-de-karlsruhe
thank you
Matthias Klose wrote...
> /<>/include/linux-x86_64/sysdep.h:109:5: error: array subscript
> ‘struct xchg_dummy[0]’ is partly outside array bounds of ‘psmi_spinlock_t[1]’
> {aka ‘ips_ato
11:18:59.0 +0200
+++ quilt-0.66/debian/changelog 2022-10-15 10:12:54.0 +0200
@@ -1,3 +1,10 @@
+quilt (0.66-2.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Cherry-pick "Avoid warnings with grep 3.8". Closes: #1020108
+
+ -- Christoph Biedl Sat, 15 Oct 2022
10:12:54
Control: tags 1020108 patch
Martin Quinson wrote...
> Thanks for any help that could be provided.
Greetings from the Karlsruhe BSP.
As mentioned earlier, the build failure is a result of grep's new
warning messages. Digging closer I realized the current quote_bre()
function can no longer used t
Control: severity 1020840 important
Control: tags 1020840 pending
Taavi Väänänen wrote...
> Hello. A recent update to the Arcanist packaging moved the binary from
> /usr/bin/arc to /usr/bin/arcanist. The binary name change makes the CLI
> fail to function properly:
#919697 has the full story: Th
Guillem Jover wrote...
> On Fri, 2022-09-02 at 12:12:06 +0200, Christoph Biedl wrote:
> > Sylvestre Ledru wrote...
> > > I don't think renaming is the right approach against an MS-DOS
> > > software (and I still think that Debian's policy is too binary for
&g
Sylvestre Ledru wrote...
> I don't think renaming is the right approach against an MS-DOS
> software (and I still think that Debian's policy is too binary for
> this).
As there is a very small chance users would want to install *both*
packages, can't we just resolve this with a Breaks: on both si
Ben Hutchings wrote...
> As a temporary workaround, disabling the Spectre v2 mitigation with the
> kernel parameter "nospectre_v2" should allow this kernel version to run
> on older CPUs without SSE2. We'll fix this properly in a later update.
Thank you, that did the right thing on my very old C
Adam Hupp wrote...
> Would be preferable to use tox to run the tests so it's the same
> configuration as I'm using to test.
Didn't see your message before the upload, but I'll keep that in mind.
Regards,
Christoph
signature.asc
Description: PGP signature
Control: tags 1012449 pending
Gianfranco Costamagna wrote...
> Hello, in the last version .26 the place for the test file changed (...)
Oops. Fix is underway.
Christoph
signature.asc
Description: PGP signature
Control: tag 1003463 confirmed
Roman Lebedev wrote...
> Package: arcanist
> Version: 0~git20200925-2
> Severity: grave
@Sylvestre,
as previously mentioned in IRC (possibly got lost), I am considering
rebasing the src:phabricator package to the latest git commit in the
respective upstream reposi
Control: tags 1009199 confirmed
Paul Gevers wrote...
> The Release Team considers packages that are out-of-sync between testing and
> unstable for more than 60 days as having a Release Critical bug in testing
> [1]. Your package src:tcpreplay has been trying to migrate for 61 days [2].
> Hence, I
Fred Klassen wrote...
> Paul, I am somewhat confused. I have not touched any old versions on
> github, including 4.3.4. Is this something I should concern myself with?
tcpreplay failed to build on armhf and I never managed to take a deeper
look:
https://buildd.debian.org/status/fetch.php?pkg=tcp
ebian/changelog2022-01-10
18:51:57.0 +0100
@@ -1,3 +1,11 @@
+libjavascript-rpc-perl (0.10-2) unstable; urgency=medium
+
+ * Salvaging upload
+ * Take maintainership. Closes: #1001975
+ * Packaging cleanup. Closes: #999265
+
+ -- Christoph Biedl Mon, 10 Jan 2022
18:51:57
10 20:37:21.0 +0100
@@ -1,3 +1,10 @@
+libppd (2:0.10-8) unstable; urgency=medium
+
+ * Take maintainership. Closes: #1001976
+ * Packaging cleanup. Closes: #998954, #912689
+
+ -- Christoph Biedl Mon, 10 Jan 2022
20:37:21 +0100
+
libppd (2:0.10-7.3) unstable; urgency=medium
ibcgi-ssi-parser-perl-0.01/debian/changelog2022-01-08
12:48:43.0 +0100
@@ -1,3 +1,11 @@
+libcgi-ssi-parser-perl (0.01-2) unstable; urgency=medium
+
+ * Salvaging upload
+ * Take maintainership. Closes: #1001973
+ * Packaging cleanup. Closes: #466397, #999223
+
+ -- Christoph
emove external example reference from documentation.
+Closes: #610178
+
+ -- Christoph Biedl Thu, 06 Jan 2022
23:20:53 +0100
+
libdebian-package-html-perl (0.1-2.1) unstable; urgency=medium
* Non-maintainer upload
@@ -16,4 +26,3 @@
* Initial Release (Closes: #379284)
-- Jose Parrella
cc 11. Closes: #984339
+
+ -- Christoph Biedl Tue, 04 Jan 2022
07:02:51 +0100
+
slim (1.3.6-5.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru slim-1.3.6/debian/patches/series slim-1.3.6/debian/patches/series
--- slim-1.3.6/debian/patches/series2017-05-02 15:42:52.0
Slavko wrote...
> i use slim, thus i wonder about its future. The patch proposed by
> Hugo Torres doesn't look as solution for me, but searching lead me
> to gentoo's bug tracker and and it's git, where i found:
>
> + the bugreport with the same problem at https://bugs.gentoo.org/786498
> + patc
Control: reopen 995393
Control: tags 995393 patch
Christoph Biedl wrote...
> As a workaround I propose a tactical __attribute__ to locally disable
> optimization as this issue has been blocking eatmydata for way too long,
> and performance loss should be neglectable.
So as always wi
gency=high
+
+ * Non-maintainer upload
+ * Also wrap the "stat" library call. Closes: #1001961
+ * Work around segfault on ppc64el. Closes: #995393
+
+ -- Christoph Biedl Thu, 23 Dec 2021
08:19:30 +0100
+
fakeroot (1.26-1) unstable; urgency=medium
[ Helmut Grohne ]
diff -Nr
Control: tags 995393 patch
Frédéric Bonnard wrote...
> #ifdef HAVE_OPENAT
> +#if defined(__powerpc__) && defined(__powerpc64__) && __BYTE_ORDER__ ==
> __ORDER_LITTLE_ENDIAN__
> +static int openat(int dir_fd, const char *pathname, int flags, ...)
> +#else
> int openat(int dir_fd, const char *pa
Control: tags 1001961 patch
Christoph Biedl wrote...
> it seems recent changes in libc6 caused the stat() call in C applications
> to be expanded in a different way, a way fakeroot does not properly
> handle, resulting in the real user-id, not 0.
Fix appended (inline, not a patch) f
Package: fakeroot
Version: 1.26-1
Severity: critical
Justification: Breaks unrelated software, possibly affects built packages
Hello,
it seems recent changes in libc6 caused the stat() call in C applications
to be expanded in a different way, a way fakeroot does not properly
handle, resulting in
Control: tags 999323 pending
Lucas Nussbaum wrote...
> Source: libapache-mod-encoding
> Justification: Debian Policy section 4.9
In the past I already did an NMU for this package, will do it again.
Just in the unlikely case somebody wants to adopt the package: Let me
knowt so duplicated work is
Control: tags 999264 pending
Lucas Nussbaum wrote...
> Source: libapache2-mod-encoding
> Justification: Debian Policy section 4.9
In the past I already did an NMU for this package, will do it again.
Just in the unlikely case somebody wants to adopt the package: Let me
knowt so duplicated work i
Control: tags 993578 pending
Raphael Hertzog wrote...
> With the patch in https://salsa.debian.org/debian/gnupg2/-/merge_requests/9
> I no longer have this issue.
Thanks for preparing this.
> But I'm not sure if the patch is fully correct, the manual page is not
> clear whether --check-options
Control: tags 999083 pending
Lucas Nussbaum wrote...
> The severity of this bug will be changed to 'serious' after a month.
In coordination with the maintainer, I will take over and do an
upload to resolve the issue soon.
Christoph
signature.asc
Description: PGP signature
Control: tags 999320 pending
> Your package does not include build-arch and/or build-indep targets in
> debian/rules. This is required by Debian Policy section 4.9, since 2012.
> https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
After a brief exchange with
@@ -1,3 +1,10 @@
+gkrellm-leds (0.8.0-1.4) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Fix startup error, thanks Renzo Davoli. Closes: #995968
+
+ -- Christoph Biedl Mon, 18 Oct 2021
23:33:29 +0200
+
gkrellm-leds (0.8.0-1.3) unstable; urgency=medium
* Non-maintaine
Control: tags 978905 unreproducible moreinfo
Matthias Klose wrote...
> The package fails to build in a test rebuild on at least amd64 with
> autoconf 2.70, but succeeds to build with autoconf 2.69. The
> severity of this report will be raised before the bookworm release,
> so nothing has to be do
@@
+swiftsc (0.5-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Update build dependencies to make package buildable again.
+Closes: #949933, #952353
+
+ -- Christoph Biedl Sat, 16 Jan 2021
14:04:59 +0100
+
swiftsc (0.5-1.1) unstable; urgency=medium
·
* Non-maintainer u
edium
+
+ * Non-maintainer upload.
+ * Fix build with gcc-10. Closes: #957293
+
+ -- Christoph Biedl Mon, 04 Jan 2021
13:22:03 +0100
+
gnupg1 (1.4.23-1) unstable; urgency=medium
* new upstream release
diff -Nru gnupg1-1.4.23/debian/patches/0006-fix-for-gcc10.patch
gnupg1-1.4.23/debian/pa
Control: tags 957293 pending upstream
Matthias Klose wrote...
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for th
Control: tags 977467 pending
Moritz Muehlenhoff wrote...
> https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/
> is for nodejs, but the underlying issue is in http-parser, which Debian's
> nodejs uses. This is already fixed in experimental, if this can't be used
> there's al
Jan Wagner wrote...
> Hi Chirstoph,
>
> thanks for taking care.
You're welcome.
> 1.124.0 is already integrated into VCS
> (https://salsa.debian.org/nagios-team/pkg-nagios-plugins-contrib/-/commit/6827b67108fcaafb5c73de8d7b44d71b2a7e6cf3),
> so you can delay this a bit more. Actually I'm working
12-06
21:20:03.0 +0100
@@ -1,3 +1,10 @@
+nagios-plugins-contrib (27.20200511+1+nmu1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Cherry-pick upstream fix for check_ssl_cert. Closes: #976218
+
+ -- Christoph Biedl Sun, 06 Dec 2020
21:20:03 +0100
+
nagios-plugins-co
Control: tags 976218 fixed-upstream
Paul Gevers wrote...
> So, let's reassign appropriately.
This was fixed¹ in upstream release 1.119.0, and I'll start preparing a
NMU now.
FWIW, upstream is already at version 1.124.0 while Debian unstable is at
1.98.0.
Christoph
¹
https://github.com/ma
Paul Gevers wrote...
> With a recent upload of file the autopkgtest of nagios-plugins-contrib
> fails in testing when that autopkgtest is run with the binary packages
> of file from unstable. It passes when run with only packages from
> testing. In tabular form:
> autopkgtest [14:13:17]: test com
Control: tags 960324 pending
Paul Gevers wrote...
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
Yeah, it's not that easy to get around the autopkgtest world. Noticed
the situation but did not bother to upload a fix im
Control: tag 952240 pending
Lucas Nussbaum wrote...
> Source: clevis
> Version: 11-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200222 ftbfs-bullseye
Packinging for clevis 12 is in the queue and is to happen tonight, I
will take care of tha
James McCoy wrote...
> Autopkgtests already run against packages in experimental, albeit at a
> slower pace than those in unstable. It seems those did catch the issue
> -- https://release.debian.org/britney/pseudo-excuses-experimental.html#file
TIL - now added to the list of things to check befo
Control: tags 948269 tags pending upstream
Sebastian Ramacher wrote...
(...)
> Note the difference in dynamically linked vs statically linked. This
> change breaks dh_shlibdeps causing ${shlibs:Depends} to not be properly
> populated.
That was a change done upstream:
|PR/93: iaeiaeiaeiae: D
Control: tag 945881 pending
Valentin Vidic wrote...
> The program segfaults when started:
>
> $ bgpdump
> Segmentation fault
Ouch. Thanks for reporting - reason was a failed attempt to make
hardening build work, plus another mess which eventually resulted in no
tests being run at all during bui
Package: devscripts
Version: 2.19.7
Severity: serious
Dear Maintainer,
devscripts started failing in the "Run pylint on Python source code" test:
| ==
| FAIL: test_pylint (devscripts.test.test_pylint.PylintTestCase)
| Test: Run
Control: tag 942885 confirmed wontfix
Andreas Beckmann wrote...
> Package: isdnactivecards
> Version: 1:3.12.2007-11-27-1
> Severity: serious
> Tags: sid bullseye ftbfs
Haven't checked, but bullseye /should/ still build. Not for
long, though.
> isdnactivecards cannot be built in sid any longer:
edium
+
+ * Non-maintainer upload
+ * Cherry-pick "Fix a unittest" to fix build error with
+http-parser 2.9 (Closes: #933684)
+
+ -- Christoph Biedl Thu, 01 Aug 2019
21:46:59 +0200
+
python-httptools (0.0.11-1) unstable; urgency=low
* Initial release (Closes: #911498).
d
Control: reopen 932762
Control: severity 932762 important
Control: retitle 932762 Needs a sane solution for running under LD_PRELOAD like
fakeroot
[ Taking Niels into the loop. I'm sorry the first approach didn't work out. ]
With the problem preliminary fixed, the whole story needs some
consider
Control: tags 932762 pending
Helmut Grohne wrote...
> Package: file
> Version: 1:5.37-3
> Severity: serious
> Control: affects -1 + src:unbound
>
> file no longer works under fakeroot. For example:
(...)
> Can we please disable seccomp until a solution for fakeroot is found?
Hm, let's give this
Niels Thykier wrote...
> Can you help me come up with a more reliable regex / handling of file(1)
> output that satisfy your request from #931996 and also avoiding
> regressions like this bug?
Ups, sorry for breaking debhelper the second time in a week. Y'know,
three time's a charm, still it's ca
Niels Thykier wrote...
> Is it possible to patch the code to skip the seccomp support only under
> fakeroot? While we are slowly reducing the number of packages relying
> on fakeroot, it will probably take a decade or more to be completely
> free from it. But I think it would be unfortunate not
Control: tags 931985 pending
So here's the story: The dh_shlibdepends program runs under fakeroot,
and libfakeroot will be loaded be the file binary as well. Nothing new.
Enter seccomp: The version of file in experimental is the first one to
have seccomp support enabled. The syscalls used by libf
Control: tags 931985 confirmed
At first, thanks for reporting, thus avoiding a lot of noise.
Eric Valette wrote...
> I know it is experimental but anyway
That's what experimental is for :) Did you just stumble over it or do
you do build checks incluing experimental on a regular base? In the
Cyril Brulebois wrote...
> Restoring the patch is not sufficient, as the context obviously changed.
> Given there were few changes there, I've tried reverting the upstream
> commit (9c143ce52da11ec3d21a3491c3749841d3dc10f0), restoring
> temp-deb-installer-hack.patch and enabling the relevant confi
Control: tag 924374 pending
Dominik George wrote...
> busybox upstream found out that their ip address show command, with the
> oneline option, includes link layer addresses, which iproute2 normally
> doesn't. They patched that, without realising their ip link show code
> ultimately calls their i
Sebastian Andrzej Siewior wrote...
> > +Build-Depends: debhelper (>= 10~), libeditline-dev, libncurses5-dev,
> > libssl1.0-dev | libssl-dev (<< 1.1.0~), cmake
>
> you need to drop libssl1.0-dev from here and simply depend on
> libssl-dev.
Thanks for checking and the heads-up, noted.
Christ
loses: #912131
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:25:14 +0100
+
netkit-telnet (0.17-41.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru netkit-telnet-0.17/debian/compat netkit-telnet-0.17/debian/compat
--- netkit-telnet-0.17/debian/compat2016-11-05 14:51:10.0
1+0.2/debian/changelog 2019-02-24
14:38:52.0 +0100
@@ -1,3 +1,10 @@
+netkit-telnet-ssl (0.17.41+0.2-3.2) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake to build the package. Closes: #912132
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:38:52 +0100
+
netkit-telne
table; urgency=high
+
+ * Non-maintainer upload
+ * Use cmake as build system. Closes: #912126
+ * Migrate to openssl 1.1, patches by Sebastian Andrzej Siewior.
+Closes: #859224
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:39:23 +0100
+
netkit-ftp-ssl (0.17.34+0.2-4) unstable; urgency=m
iff
-052_no_termcap_linking.diff
060_full_offset_range.diff
070_hash_increments.diff
+use-cmake-as-buildsystem.patch
+use-cmake-as-buildsystem-debian-extras.patch
diff -Nru
netkit-ftp-0.17/debian/patches/use-cmake-as-buildsystem-debian-extras.patch
netkit-ftp-0.17/debian/patches/use-cmake-as
* Use cmake as build system. Closes: #912123
+
+ -- Christoph Biedl Sun, 24 Feb 2019
14:39:30 +0100
+
linux-ftpd-ssl (0.17.36+0.3-2) unstable; urgency=low
* Adaption to libssl of recent version.
diff -Nru linux-ftpd-ssl-0.17.36+0.3/debian/compat
linux-ftpd-ssl-0.17.36+0.3/debian/compat
---
nux-ftpd-0.17/debian/patches/use-cmake-as-buildsystem-debian-extras.patch
2019-02-24 14:28:26.00000 +0100
@@ -0,0 +1,76 @@
+Description: Debian-specific changes to the cmake build system
+Author: Christoph Biedl
+Forwarded: not-needed
+Last-Update: 2019-02-24
+
+--- a/ftpd
Sebastian Andrzej Siewior wrote...
> Do you still plan to address this or should a RM be filled? The window
> for Buster has been closed imho.
Yes, and yes :(
Patches are more or less done but I haven't got the tuits for the last
checks unfortunatly. Unless I'm done within the next 48h, I'll giv
Sebastian Andrzej Siewior wrote...
> On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote:
>
> > Or should we rather remove netkit-ftp-ssl? There are TLS-capable ftp client
> > alternatives in the archive still, e.g. lftp.
>
> I provided a patch after Mats described how bad the new openssl is.
Moritz Mühlenhoff wrote...
> On Sat, Sep 08, 2018 at 03:07:14PM +0800, Paul Wise wrote:
> > Mozilla are still discussing if WebExtensions or NSS extensions are
> > going to be allowed to access and modify TLS validation results:
> >
> > https://bugzilla.mozilla.org/show_bug.cgi?id=1489080
> > htt
Christoph Biedl wrote...
> find attached the NMU ...
Now really attached.
Christoph
diff -Nru biff-0.17.pre2412/comsat/comsat.8
biff-0.17.pre2412/comsat/comsat.8
--- biff-0.17.pre2412/comsat/comsat.8 2018-12-08 10:55:29.0
+0100
+++ biff-0.17.pre2412/com
* Non-maintainer upload
+ * Use cmake as build system. Closes: #873085, #912121
+
+ -- Christoph Biedl Sat, 08 Dec 2018
10:36:30 +0100
+
bsd-finger (0.17-15.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru bsd-finger-0.17/debian/compat bsd-finger-0.17/debian/compat
--- bsd-finger
1 - 100 of 823 matches
Mail list logo
