Bruno Haible via Gnulib discussion list writes:
>> > Should be fixed through this commit:
>>
>> I confirm, everything is working nicely, now, thanks Bruno!
>
> I've reported the bug to Debian, so that they can fix it downstream.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110119
Patric
Chris Hofstaedtler writes:
> * Simon Josefsson [250723 12:11]:
>>Ah, right, although this bug would not necessarily have any activity
>>since the real issue was golang-github-containers-ocicrypt but that is
>>now fixed in testing. And the autoremoval was for 2025-08-22, n
ealized the summer heat caused me to confuse the autoremoval date of
>> 2025-08-22 with 2025-07-22 so there were no real urgency here...
>>
>> /Simon
>>
>> Simon Josefsson writes:
>>
>>> severity 1108992 normal
>>> thanks
>>>
&g
here...
/Simon
Simon Josefsson writes:
> severity 1108992 normal
> thanks
>
> Bastian Germann writes:
>
>> I have already filed bug#1109540 (unblock:
>> golang-github-containers-ocicrypt/1.1.10-3)
>
> It seems the autoremoval is more aggresive than the overri
upload, please don't wait for me.
/Simon
From f54c8aee95597558491fbbbff6fe87d406ff9722 Mon Sep 17 00:00:00 2001
From: Simon Josefsson
Date: Mon, 21 Jul 2025 10:33:31 +0200
Subject: [PATCH] Use Breaks: instead of Conflicts:.
---
debian/control | 8
1 file changed, 4 insertions(
severity 1108992 normal
thanks
Bastian Germann writes:
> I have already filed bug#1109540 (unblock:
> golang-github-containers-ocicrypt/1.1.10-3)
It seems the autoremoval is more aggresive than the override permission,
with autoremoval removing a lot of packages tomorrow that (indirectly)
depe
Oh thank you!
/Simon
> 19 juli 2025 kl. 22:05 skrev Bastian Germann :
>
>
> I have already filed bug#1109540 (unblock:
> golang-github-containers-ocicrypt/1.1.10-3)
Bastian Germann writes:
> All of the reverse dependencies should be okay when #1109389 is fixed.
How do we stop the autoremoval from happening on 2025-08-22? The
migration of golang-github-containers-ocicrypt from unstable to testing
won't happen before then. Is this a situation where we shoul
Mathias Gibbens writes:
> control: tags -1 + confirmed patch
>
> I disagree that this is a policy violation; the cause of error is
> clearly reported. Not sure how the script could be more resilient when
> a remote resource has disappeared:
I tend to agree -- the package is in contrib, which I
Thanks, I have uploaded what was already in Salsa (not sure why I hadn't
uploaded it before), which uses the upstream-tweaked version of my
earlier patch.
The patches are pretty much identical, upstream improved my poor coding
style in the pull request: https://github.com/sigstore/gitsign/pull/664
Paul Gevers writes:
> Hi Noah,
>
> On Thu, 08 May 2025 10:10:06 +0200 Simon Josefsson
> wrote:
>> The testing migration seems a bit unclear to me, can you take a look if
>> this will actually migrate? It is scheduled for autoremoval right now.
>> https://tracker
Noah Meyerhans writes:
> On Thu, May 01, 2025 at 05:04:33PM -0400, Noah Meyerhans wrote:
>> For dovecot in trixie, I'm considering reverting channel binding support
>> altogether. That'll force us to drop SCRAM-SHA-1-PLUS and
>> SCRAM-SHA-256-PLUS support, but I'd rather do that than ship dovecot
Thanks for debugging! Seems okay for a quick fix but a proper fix should work
with both new and old configs. I suspect some GSSAPI flag or parameter may
trigger this, even if it can be fixed in dovecot I would want to review if
gsasl could or should behave differently anyway. I recall some short
/permissions problem or
additional GSSAPI flag check that dovecot didn’t do before.
Alas I am traveling without laptop for the next few days so will have no
ability to debug anything.
/Simon
> 29 apr. 2025 kl. 22:33 skrev Noah Meyerhans :
>
> On Tue, Apr 29, 2025 at 10:22:21PM +02
Thanks for report! Did you confirm that your new dovecot version has working
GSSAPI support, with some other client? Or is this gsasl autopkgtest the only
one that test that functionality? I think the relevant dovecot errors are the
one below, but the error reporting is not that great. Since
Ansgar 🙀 writes:
> No, that is not the core problem. Debian, like most other binary
> distributions, heavily relies on the system library exception in many,
> many places.
I believe that is a fairly new (~5 years?) approach within Debian.
Debian used to treat OpenSSL incompatible with GPLv2 and
Richard Laager writes:
> As I have said before: I think that computer programmers have a
> tendency to treat licenses as if they are self-executing (and precise
> like software).
Agreed, this is often a challenge when technical people discuss legal
matters, and it helps to keep this in mind.
>
Jérémy Lal writes:
>> > 2) However I realized I was wrong in my comment in
>> > https://bugs.debian.org/1100967#10 about which package name is the
>> > "proper" one. Upstream's go.mod namespace is still go.step.sm/crypto
>> > even in latest upstream master:
>> >
>> > https://github.com/smallstep
Control: tag -1 pending
Hello,
Bug #1102402 in golang-github-smallstep-scep reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-github-smal
Jérémy Lal writes:
> To avoid the odd-ness of assigning a RC bug to ftp.debian.org,
> I'd rather create a new Removal Request, then block 1100967 with it ?
Of course, thank you!
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102636
/Simon
signature.asc
Description: PGP signature
Jérémy Lal writes:
>> 1) Now there are no reverse dependencies on golang-step-crypto-dev any
>> more, so I think we could ask for removal of that package from the
>> archive which would resolve https://bugs.debian.org/1100967
>>
>> jas@kaka:~/dpkg/golang-github-smallstep-crypto$ ssh
>> mirror.ftp
Control: tag -1 pending
Hello,
Bug #1102613 in oci-seccomp-bpf-hook reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/oci-seccomp-bpf-hook/-/comm
Source: oci-seccomp-bpf-hook
Version: 1.2.10+ds-2
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
Hi
This package FTBFS with this diff:
-# Dpkg.Copyright.Grant.ByFile
Dpkg::Copyright::Grant::ByFile::_load_fill_blank_data No
Jérémy Lal writes:
>> I had a look at another approach, just upgrading the dependency to
>> golang-github-smallstep-crypto-dev
>> for these two packages:
>> - golang-step-cli-utils: all fine, level1
>> - golang-github-smallstep-certificates: level 2, needs the previous one
>> rebuilt first, and t
Control: tag -1 pending
Hello,
Bug #1101345 in golang-github-xanzy-go-gitlab reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-gitlab-git
fixed 1102241 0.4.0-1
thanks
Santiago Vila writes:
> github.com/openpubkey/opkssh
> # github.com/openpubkey/opkssh
> src/github.com/openpubkey/opkssh/main.go:183:5: not enough arguments in call
> to choosers.NewWebChooser
> have ([]providers.BrowserOpenIdProvider)
> want ([]provider
Control: tag -1 pending
Hello,
Bug #1101904 in litetlog reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/litetlog/-/commit/7919a3eb35b326239eea5
A short-term fix to resolve the RC bug may be to simply add a
'Conflicts: golang-step-crypto-dev' to
golang-github-smallstep-crypto-dev? Or is there a need to be able to
co-install these two packages?
Meanwhile I looked into updating golang-github-smallstep-certificates to
latest version and ran
Hi, and thanks for the report, and sorry for delay in noticing this. Cc
to debian-go since solving this may involve some co-ordination and could
use the attention of someone more knowledgeable.
These two packages have the same upstream! I'm not sure that was known
before.
The golang-github-smal
Hi, and thanks for the report, and sorry for delay in noticing this.
The golang-gitlab-gitlab-org-api-client-go-dev package is a
rename/reupload of golang-github-xanzy-go-gitlab-dev so it is not
surprising these conflict. I've asked for advice on next steps here:
https://lists.debian.org/debian-
A bit more context about the fix: I tried temporarily changing the time
on my machine to 2028-07-01 and built this new upstream release
successfully, so please see if you are still able to reproduce this. It
seems upstream moved tests around and modified them, so chances are they
resolved this som
Control: tag -1 pending
Hello,
Bug #1098553 in golang-github-digitorus-pkcs7 reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-github-dig
Control: tag -1 pending
Hello,
Bug #1100347 in golang-opentelemetry-otel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-opentelemetry-o
Jonathan Wiltshire writes:
> Hi,
>
> New archive signing keys are now needed for trixie, ideally before the soft
> freeze for trixie's update and then they can also be included in 12.11
> before 13.0.
It would be nice to document who generate these keys and how the key
lifecycle is managed inclu
Martina Ferrari writes:
> Hi,
>
> I was looking at this bug only a few minutes ago, because of this
> package threatening prometheus to be removed from testing.
>
> On 07/03/2025 16:34, Simon Josefsson wrote:
>
>> I have uploaded golang-github-smallstep-p
Hi Faidon, (cc'ing debian-go list since this affects several Go packages)
Faidon Liambotis writes:
> Hi Simon,
>
> On Fri, Feb 21, 2025 at 11:27:00PM +, Santiago Vila wrote:
>> During a rebuild of all packages in unstable, your package failed to build:
>>
>>
>>
>> verify_test.go:563: Ve
Jeremy Bícha writes:
> Control: severity -1 serious
>
> On Mon, Feb 17, 2025 at 5:10 PM Simon Josefsson wrote:
>>
>> severity 1061185 important
>> thanks
>>
>> I'm downgrading this due to lack of explanation what is the 'serious'
>>
severity 1061185 important
thanks
I'm downgrading this due to lack of explanation what is the 'serious'
severity level problem.
/Simon
Simon Josefsson writes:
> Hi! You re-opened this ITP bug and changed the title to 'apt-verify:
> unsupportable' and made it a
Package: golang-github-charmbracelet-wish
Severity: serious
X-Debbugs-CC: Anthony Fok , Otto Kekäläinen
Hi
This package golang-github-charmbracelet-wish has no reverse build
dependencies in Debian. The package is version 0.1.1 in Debian but
latest from upstream is 1.4.6.
In the ITP for it -- h
Package: golang-github-jesseduffield-go-git
Severity: serious
Hi
I did an upstream upload of go-git to fix some security vulnerabilities
for trixie:
https://tracker.debian.org/pkg/golang-github-go-git-go-git
However I today realized that we have a old fork of that project that
still have the se
Control: tag -1 pending
Hello,
Bug #1078632 in notary reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/notary/-/commit/60802bcf760fda351106e5e74
Control: tag -1 pending
Hello,
Bug #1091500 in golang-github-github-smimesign reported by you has been fixed
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-github-gi
tore-go.
I got advice on #debian-mentors that led me to upload
golang-github-google-certificate-transparency with a Breaks: sigstore-go
(<= 0.6.2-3~) and I was told the testing migration logic would
understand this and no longer prevent migration. Let's wait and see...
/Simon
Simon Josefss
notfound 1093640 1.3.1-1
reassign 1093640 sigstore-go 0.6.2-2
fixed 1093640 0.6.2-3
thanks
Hi. I'm trying to resolve testing migration, and I hope the above is
the right way to do this. Considerations:
- The FTBFS was actually happneing for sigstore-go 0.6.2-2 when used
with golang-github-goo
Control: tag -1 pending
Hello,
Bug #1093640 in sigstore-go reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/sigstore-go/-/commit/2ec12dceb0d5b9f
Control: tag -1 pending
Hello,
Bug #1093765 in gitsign reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/gitsign/-/commit/99275c17875bbe49588fa7b
Hi! You re-opened this ITP bug and changed the title to 'apt-verify:
unsupportable' and made it a RC bug. It is not clear to me what makes
you believe this is a serious bug in this package, since you gave no
justification. Can you clarify what your actionable concerns are?
/Simon
signature.as
Although shouldn't the FTBFS bug really on 'sigstore-go' rather than
'golang-github-google-certificate-transparency'? The former is what is
failing to build, not the latter. It would have been nice if the
g-g-g-c-t test suite triggered these APIs too. I can see it make sense
to keep 'golang-gith
Mathias Gibbens writes:
> Source: golang-github-google-certificate-transparency
> Version: 1.3.1-1
> Severity: serious
> Justification: FTBFS
> Tags: sid ftbfs
> Affects: sigstore-go
> X-Debbugs-CC: si...@josefsson.org
>
> The recent update of golang-github-google-certificate-transparency is
>
Hi. I have uploaded a new upstream version, and buildd is happy:
https://buildd.debian.org/status/package.php?p=golang-github-safchain-ethtool
Can you re-check if you can reproduce the problem now? If the buildd's
indeed are using unshare now, I am hoping your FTBFS is gone too.
Salsa is able
fre 2025-01-17 klockan 11:32 +0100 skrev Santiago Vila:
> > Loooking at code [1] makes me suspect something rare is happening
> > on
> > your system
>
> Hi. Please try building with sbuild + the unshare backend.
>
> The package might build ok with the traditional file backend,
> but the official
Hi. Thanks for the report. The error message is:
ethtool_test.go:66: Unable to retrieve stats from any interface of this system.
Loooking at code [1] makes me suspect something rare is happening on
your system, what does a 'sudo ip a' display?
I will try latest upstream version and report this
severity 1092527 important
thanks
Hi. FWIW, I can't reproduce this FTBFS locally neither can Salsa:
https://salsa.debian.org/jas/golang-github-containerd-stargz-snapshotter/-/pipelines/798873
So I don't think this is RC, assuming buildds are equally unable to
reproduce it? Looking at your buil
Control: tag -1 pending
Hello,
Bug #1091595 in golang-go-patricia reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-go-patricia/-/commit/e
Antoine Beaupré writes:
> On 2024-12-21 10:25:36, Simon Josefsson wrote:
>> Hi. It seems golang-goptlib changed namespace between upstream
>> releases, and snowflake has to adapt. However, it is possible to solve
>> this with a hack in golang-goptlib, so I did that.
Hi. It seems golang-goptlib changed namespace between upstream
releases, and snowflake has to adapt. However, it is possible to solve
this with a hack in golang-goptlib, so I did that.
/Simon
signature.asc
Description: PGP signature
Hi. I'm uploading !36 now, let's hope it silences this so we can get
back to uploading a new upstream release. I'm happy to review and
sponsor uploads, but I have limited ability to test things beyond
autopkgtest/debci (which would be nice to enhance to cover the important
use cases).
/Simon
s
nding some more discussion
I'm going to stop trying to fix the FTBFS bug on mips64el/riscv64 now.
/Simon
Nilesh Patra writes:
> Hi Simon,
>
> On 14/12/24 3:03 pm, Simon Josefsson wrote:
>> What's the status of Sia in Debian?
>> https://tracker.debian.org/pkg/sia
&g
Package: golang-github-nebulouslabs-ed25519
Severity: serious
Hi. According to upstream
https://github.com/nebulouslabs/ed25519
it is a 9+ year old fork of a another project:
https://github.com/agl/ed25519
And that project has declared itself unmaintained, and say that people
should be using
Package: golang-ed25519-dev
Severity: serious
Hi. According to upstream
https://github.com/agl/ed25519
this project is unmaintained, and people should be using Go's
x/crypto/ed25519 instead. I believe there is harm in having this
package go into the Debian trixie because it may confuse someone
Guillem Jover writes:
> But I guess your plan of just accepting .asc, .pgp, and .gpg, and
> warning to rename to .pgp for other extensions would be the safest
> less disruptive path for now.
The registered MIME file extension for PGP keys is *.asc, see:
https://www.rfc-editor.org/rfc/rfc3156.ht
/de66a2eb7e877023ac8cbf0574d6daf2fc7f8038
Move aliased files from / to /usr (DEP17). (Closes: #1088103)
Signed-off-by: Simon Josefsson
(this message was
Thanks for the report. I was able to reproduce it on amdahl (schroot -b
-c sid_armel-dchroot) but I'm unable to come up with a fix. I've filed
an upstream bug report:
https://bugzilla.samba.org/show_bug.cgi?id=15723
Maybe we should drop support for this package on armhf/armel too.
/Simon
si
Thank you so much for explaining! Going down this path looks like it
involves more work than fixing the real upstream problem. Even a
"solution" to add some ugly patch that hides the problem on armel+armhf
feels attractive now. It feels a bit weird that removing things from
Debian has that prope
severity -1 important
thanks
Chris Hofstaedtler writes:
> On Mon, Sep 23, 2024 at 02:32:20PM +0200, Simon Josefsson wrote:
>> I am in the process of uploading a new upstream version into unstable
>> that disables armel+armhf builds.
>
> You don't need to explicitly dis
I am in the process of uploading a new upstream version into unstable
that disables armel+armhf builds.
While the bug has been discussed upstream, I didn't find a proper bug
report, so I filed this one:
https://bugzilla.samba.org/show_bug.cgi?id=15720
If anyone has time to debug or look into a f
Thanks for caring about this package - feel free to NMU and push changes to
salsa! I think it would be better if this package was team maintained. I no
longer use it, and upstream broke the self tests with some changes in the last
release and wasn’t responsive in fixing them, so the state of th
Ingo writes:
> On Sun, 21 Jul 2024 23:00:48 +0200 Drew Parsons wrote:
>> Just to be clear, I'm not supporting dropping armv7 support.
>> It's only one test that's failing. Skipping the one test (on 32-bit
>> arm) is all that's needed. It's passing the other tests.
>
> Yes, that's what I mean.
Luca Boccassi writes:
> On Mon, 29 Apr 2024 13:03:22 +1200 Andrew Bartlett
> wrote:
>> Just a warning that trying to brute force a fix for this is likely to
>> end badly. A lot of developer time was spent to get to this current
>> delicate situation, which relied on the narrow behaviour that is
Hi.
Most tools from netkit are candidates for migration to GNU InetUtils,
and rwho(d) may be another one -- see email and bug report below.
Cc'ing debian-devel to have broader discussion.
First, I think we need to understand the rationale for doing anything
about 'netkit-rwho': do we want to do s
Source: unicap
Version: 0.9.12+repack20150328.0.git2c600ae-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: si...@josefsson.org
Usertags: ftbfs-trixie
Hi. I have tried to rebuild unicap in sid and it fails:
Making all in po
make[3]: Entering directory '/builds/jas/unicap/deb
tags 1066240 + patch
thanks
A patch to fix this compiler error is available in a pull request and
has been used by Nix:
https://github.com/kjn/lbzip2/pull/33
/Simon
signature.asc
Description: PGP signature
.0.3-2.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Rename libraries for 64-bit time_t transition. Closes: #1062896
> +
> + -- Benjamin Drung Thu, 29 Feb 2024 15:52:14 +
> +
> shishi (1.0.3-2) unstable; urgency=medium
>
>[ Simon Jo
Benjamin Drung writes:
> Source: oath-toolkit
> Dear maintainer,
>
> Please find attached a final version of this patch for the time_t
> transition. This patch is being uploaded to unstable.
>
> Note that this adds a versioned build-dependency on dpkg-dev, to guard
> against accidental backports
Tom Parkin writes:
> Hi folks,
>
> Would someone mind please reviewing and uploading
> golang-github-katalix-go-l2tp 0.1.7-1?
>
> https://salsa.debian.org/go-team/packages/golang-github-katalix-go-l2tp
Looks good, although there were no tag for the previous Debian upload so
diffing changes was a
Sebastian Ramacher writes:
> FAIL: krb5context
> =
>
> ==31890==
> ==31890== Process terminating with default action of signal 11 (SIGSEGV)
> ==31890== Access not within mapped region at address 0xBDB33984
> ==31890==at 0x4856C00: shishi_key_parse (in
> /usr/lib/arm-linux-g
Thank you -- I am uploading a newly built package with your patch.
/Simon
signature.asc
Description: PGP signature
Sam James writes:
> Thanks, I've reported this on the Valgrind bugzilla at
> https://bugs.kde.org/show_bug.cgi?id=478624.
Thank you for reporting this!
Upstream has fixed it:
https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=d35005cef8ad8207542738812705ceabf137d7e0
It would be nice t
Thank you for fixing this! I was just about to fix it. I've merged
your patch into git:
https://salsa.debian.org/xmpp-team/jabberd2/-/commit/aafafbc13ed3d8f06768d6228de6f58cd3d23ff5
For some reason the pkg-xmpp-de...@lists.alioth.debian.org mailing list
doesn't work, or I would have received th
Thank you for fixing this! I'm hoping someone will take over this
package (or that upstream will roll a new releases that passes self-
tests which would allow me to more easily update the package) so I'll
leave this for future package maintainers. Feel free to push fixes to
git on salsa.
/Simon
tags 1024278 help
thanks
Philipp Kern writes:
> Hey Simon,
>
> On Thu, Nov 17, 2022 at 12:46:19PM +0100, Sebastian Ramacher wrote:
>> > I see. If so, it would be good if pkgconf was made consistent with
>> > pkg-config here, if the intention is to replace it.
>>
>> This discussion needs to hap
Thanks, I have reported this to pkgconf upstream:
https://github.com/pkgconf/pkgconf/issues/278
/Simon
signature.asc
Description: PGP signature
tor 2022-11-17 klockan 10:38 +0100 skrev Sebastian Ramacher:
> On 2022-11-17 08:57:12 +0100, Simon Josefsson wrote:
> > ons 2022-11-16 klockan 23:55 +0100 skrev Sebastian Ramacher:
> > > Source: libgssglue
> > > Version: 0.7-1
> > > Severity: serious
>
ons 2022-11-16 klockan 23:55 +0100 skrev Sebastian Ramacher:
> Source: libgssglue
> Version: 0.7-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgssglue/28379714/log.gz
>
> Removing autopkgtest-satdep (0) ...
> autopkgtes
loses: #991448.
+
+ -- Simon Josefsson Wed, 25 Aug 2021 10:23:30 +0200
+
ui-utilcpp (1.10.0-1) unstable; urgency=medium
[ Ondřej Nový ]
diff --git a/debian/control b/debian/control
index 48b4461..3964b68 100644
--- a/debian/control
+++ b/debian/control
@@ -12,6 +12,7 @@ Build-Depends: debh
tis 2021-01-26 klockan 19:25 +0100 skrev Bruno Kleinert:
> On Mon, 23 Nov 2020 20:15:52 +0100 Simon Josefsson <
> si...@josefsson.org> wrote:
> > severity 975030 serious
> > severity 974997 serious
> > severity 974996 serious
> > severity 974995 serious
>
-dev instead of obsolete libidn2-0-dev. Closes:
#974995.
+
+ -- Simon Josefsson Tue, 24 Nov 2020 09:17:37
+0100
+
gnunet (0.13.1-1) unstable; urgency=medium
* Update debian/watch to version 4, add a rule deal with pre and rc
diff -Nru gnunet-0.13.1/debian/control gnunet-0.13.1/debian/con
severity 975030 serious
severity 974997 serious
severity 974996 serious
severity 974995 serious
severity 974994 serious
severity 974993 serious
thanks
It was suggested to me on IRC that the severity of this could be
serious because the build-dependency libidn2-0-dev is going to be
removed from Deb
reassign 938069 ftp.debian.org
retitle 938069 RM: python-pyhsm -- ROM
severity 938069 normal
thanks
Upstream python-pyhsm does not support python3 [1] so I believe it make
sense to remove python-pyhsm from unstable. The only in-debian
reverse dependency appear to be 'yubikey-val' which has been
tags 925709 + upstream moreinfo fixed
thanks
Thanks for the report. I have uploaded 1.8.1-1 that from what I can
tell fixes this, but it would be good if you could confirm that it
builds fine for you too?
/Simon
signature.asc
Description: This is a digitally signed message part
Hi. Just another person to confirm this bug, it took me some time to
track down and then notice it was already reported. I upgraded my mail
server to debian 9 and cyrus imapd always stop working after a couple
of days due to this. Fortunately my mail server is pretty low traffic,
so I'm hoping a
Hi Sergei! We worked on this precisely at the same time! I just
uploaded 2.7.0-1 which incorporates upstream's solution to this
problem. I think it is a cleaner approach than to patch 2.6.1, and we
still have time before the freeze. Sorry for not noticing your push
before doing the upload, but
Done, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906319
/Simon
> 14 aug. 2018 kl. 23:51 skrev Salvatore Bonaccorso :
>
> Hi Simon,
>
>> On Tue, Aug 14, 2018 at 10:35:26PM +0200, Simon Josefsson wrote:
>> Yes, removing the package from testing seems reason
Yes, removing the package from testing seems reasonable to me.
/Simon
> 14 aug. 2018 kl. 20:39 skrev Salvatore Bonaccorso :
>
> Source: libykneomgr
> Version: 0.1.8-1
> Severity: grave
> Tags: security upstream
>
> Hi
>
> See https://www.x41-dsec.de/lab/advisories/x41-2018-004-libykneomgr/
> f
severity -1 normal
tags -1 moreinfo
thanks
Hello Karsten,
> I am sorry to report this, but the users of jabberd2 should now that
> there is no encryption possible with this package. An configuration
> with encryption settings is ignored and an unencrypted connection is
> opened without warnings.
forwarded 834066 https://github.com/Yubico/python-pyhsm/issues/11
thanks
> Hi,
>
> /usr/lib/python2.7/dist-packages/test/__init__.py is a way too generic
> name that shouldn't be used by any python module, since it can easily
> lead to file conflicts between packages (that is how I noticed it).
I would suggest to use gnutls_set_default_priority() instead of
hard-coding a priority string into applications. Your hard coded
priority string will be just as obsolete as the hard coded values you
are replacing in a couple of years.
/Simon
signature.asc
Description: PGP signature
Willem and I are in the process of packaging/uploading the 2.3.3 release
which should take care of this.
/Simon
signature.asc
Description: PGP signature
FWIW, I reinstalled another laptop with jessie rc1, and adding a printer
in GNOME fails due to the same problem. If it matters, the printer is a
HP LaserJet P2055DN.
/Simon
pgpY3UL5QA0o2.pgp
Description: OpenPGP digital signatur
Jonathan Wiltshire writes:
> On Sat, Jan 17, 2015 at 09:21:28PM +, Debian Bug Tracking System wrote:
>> Changes:
>> libykneomgr (0.1.6-2) unstable; urgency=low
>> .
>>* ykneomgr: Depend on pcscd. Closes: #774678.
>
> Unblocked, since I saw it was closed - thanks for the quick upload
T
1 - 100 of 407 matches
Mail list logo
