Re: syslog-ng: identified for time_t transition but no ABI in shlibs

question is again, is the rules really changed or we bend the rules just because of one transition? On Fri, 2024-04-05 at 15:15 +0200, Bernd Zeimetz wrote: > Hi Attila, > > On Fri, 2024-04-05 at 09:47 +0100, Attila Szalay wrote: > > Based on https://wiki.debian.org/NonMaintainerUpload, the

Re: syslog-ng: identified for time_t transition but no ABI in shlibs

Hello Steve, I do understand your concern about the time_t structure change and I also admit that there are some room of improvement how the syslog-ng package manage the library versioned dependency, but this is not the solution. Based on https://wiki.debian.org/NonMaintainerUpload, the binNMU

Britney misses builds for architecture not listed in control

Hi, I have a relatively new package (BoxFort). In the beginning, I used the "any" architecture in the control so it was (tried to be) compiled on all architectures. But from the build logs, I realized that currently the package can only be compiled/used in a very few architectures (amd64, arm64,

Re: source only upload with git-buildpackage

That option means that the system will create not only the binary .amd.changes but another changes too which contains only the source packages. And I would like to use this method to be sure the package compiles, to be able to run the lintian against the package and even be able to test it before

source only upload with git-buildpackage

Hi, I'm struggling with it for a while now and I couldn't find the solution. I have a package maintained with git-buildpackage. And now, that I "cannot" upload binary packages I tried to compile the new version with the option to create a source-only changes file too. But for some reason that

Re: ftp master uploads disappearing?

For me, the uploaded package was disappeared when I accidentally used a wrong gpg kez to sign it. It was also mine, just an old, 1024 bit long one. In that case I received nothing back about the upload. And about the source-only upload I found another page where there are some cases, when the

Re: OpenSSL disables TLS 1.0 and 1.1

Hi, My concern is less about https (hello iloms), but other kind of protocols. Ssl vpn, rdp servers, voip, etc. And embedded devices implements this protocols. On Aug 8, 2017 7:35 AM, "Stephan Seitz" wrote: > On Mo, Aug 07, 2017 at 11:18:38 -0500, Michael

buildd failure

Hi All! What can I do with this (from packages.qa.debian.org): # 42 days old (needed 10 days) # out of date on hppa: libzorpll, libzorpll-dev (from 2.0.5.2-1) This is with package libzorpll. -- PGP ID 0x8D143771, /C5 95 43 F8 6F 19 E8 29 53 5E 96 61 05 63 42 D0 GPG ID ABA0E8B2, 45CF B559

Re: buildd failure

Hi All! On 2003 Jun 03, Matt Zimmerman wrote: In any case, debian-devel in general is not likely to know, but the buildd admin will. I only ask what can I do. - Send an email to hppa buildd maintainer - Send an email to debian-hppa mail list - Report a bug - Wait - Other. That's all.