7;s fixed upstream and in testing so
I've closed.
Let me know it's prefered to use `fixed` in this case and leave the bug
open even though I don't intend to fix in stable.
Cheers,
Jakub Ružička
On 12/19/24 18:53, Noah Meyerhans wrote:
On Thu, Dec 19, 2024 at 12:06:55AM +0800, Shengqi Chen wrote:
Currently Debian already has bird and bird2. bird3 is now released,
presumably to be packaged separately with previous versions.
Do we need to have all three major release streams indefinitely
Control: merge 1090798 1090783
Ooops, Ondrej was 7 hours faster :)
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: b...@packages.debian.org
Control: affects -1 + src:bird
Legacy BIRD 1.x EOL since 2023, quoting
https://bird.network.cz/pipermail/bird-users/2023-April/016874.html
> Last version of B
Control: owner -1 Jakub Ružička
Hey,
I've already created bird3 Salsa including CI:
https://salsa.debian.org/debian/bird3
and uploaded bird3_3.0.0-1 to Debian experimental,
it's now waiting in NEW queue:
https://ftp-master.debian.org/new/bird3_3.0.0-1.html
Please do test it and r
nly leftover
knot-module-{dnstap,geoip} bins. They aren't supposed to have any
reverse deps.
As explained in
https://lists.debian.org/debian-devel/2024/11/msg00079.html
I just want to finally unblock knot migration to testing.
Cheers,
Jakub Ružička
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: python-json-schema-for-humans
Version : 1.0.3
Upstream Contact: Denis Blanchette
* URL : https://github.com/coveooss/json-schema-for-humans
* License
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: k...@packages.debian.org
Control: affects -1 + src:knot
Please remove 3.3.9-1 bin leftovers as they block knot transition
through #1081191:
knot-module-dnstap| 3.3.9-1
Control: notfound -1 3.3.9
I've fixed this in 3.4.0-3, so why is this still preventing knot
transition?
https://qa.debian.org/excuses.php?package=knot
Control: reassign -1 libgnutls30
I'm hopefully reassigning this to a correct package.
Also CC'ing maintainers for visibility because it's needed in Knot DNS
(knot package).
Cheers,
Jakub Ružička
On Mon, 03 Jun 2024 10:30:41 +0200 Daniel Salzman wrote:
> The GnuTLS library
Control: fixed -1 3.4.0-4
I believe we managed to really fix this with upstream help in 3.4.0-4:
https://buildd.debian.org/status/logs.php?pkg=knot&ver=3.4.0-4&arch=armel
Cheers,
Jakub Ružička
/status/fetch.php?pkg=knot&arch=armel&ver=3.4.0-1&stamp=1725475622&raw=0
This is from 3.4.0-1 which you link here ^
I've attempted to use bug control commands to fix that.
Anyway, 3.4.0-2 will attempt to fix this soon in unstable.
Salsa is moody today.
Cheers,
Jakub Ružička
ather maintain this properly in Debian. It was requested back in 2016.
I'm a part of Debian lua-team and already maintain few other lua packages for
knot-resolver, so I should be able to handle this.
Cheers,
Jakub Ružička
signature.asc
Description: PGP signature
not-resolver eventually
in the future.
There is sadly no upgrade path from v5 to v6, thus the packages must not share
same names. It's not acceptable for a Debian package to break on dist-upgrade.
Cheers,
Jakub Ružička
Hey Daniel,
I did a spring cleaning in upstream debian packaging (distro/pkg/deb),
merging -core and -manager into knot-resolver6, porting most of your
debian/experimental patches, and removing many lintian warnings.
This was done in upstream MRs now merged into `master` branch (which is now
v6,
Yo Santiago (CC'd), could you please drop your opinion on this for extra
reference?
On 4/30/24 18:34, Daniel Baumann wrote:
Hi,
On 4/30/24 18:12, Jakub Ružička wrote:
Secondary reason for that was that there is no upgrade path from 5.x
to 6.x so it's unwanted for knot-resolver 5 p
On 4/29/24 21:13, Daniel Baumann wrote:
On 4/29/24 19:50, Daniel Baumann wrote:
pushing to the repo requires me to be added to the salsa project..
would you mind adding me?
in the meantime, I've pushed to here:
https://git.progress-linux.org/users/daniel.baumann/debian/todo/knot-resolver/log/
On 4/23/24 14:05, Daniel Baumann wrote:
Hi,
On 4/23/24 13:58, Jakub Ružička wrote:
but we've agreed the time has come to get extra testing & feedback
through Debian experimental.
yay, thanks!
[ we use knot-resolver at work for the central resolvers for the
university, and we love
ake some more time to clean the package properly so that it starts
its 6.x life with a clean slate but it's going to hit experimental in
upcoming weeks :)
Thanks for indicating interest, I'll get it done.
Cheers,
Jakub Ružička
On 4/14/24 08:39, Daniel Baumann wrote:
Package: knot-r
ctual lintian
release. Who wants to get blamed for breaking a core tool? :)
Then folks like you and me can help with fixing individual issues and/or
merging MRs.
> Thank you for your time. Please do let me know if you have any
> questions, or if I can do anything else to help.
Thank you for bumping this, we need to get this sorted one way or another.
Cheers,
Jakub Ružička
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: python-nvchecker
Version : 2.12
Upstream Contact: lilydjwg
* URL : https://github.com/lilydjwg/nvchecker
* License : Expat
Programming Lang
eed an extra pair of eyes for review or something, let me know.
Cheers,
Jakub Ružička
On 10/10/23 15:09, Roland Mas wrote:
Hi Jakub,
Is there any progress on the package? A package of mine (dioptas) has
started depending on it, so it would be nice to have in Debian. Can I
help somehow? Is
On 23-08-09 15:08, Colin Watson wrote:
> How will this sort of thing work when a git tree isn't necessarily
> available at binary package build time, since buildds build binary
> packages from a source package rather than directly from git and the
> source package doesn't usually include a git tree
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: python-poetry-dynamic-versioning
Version : 0.25.0
Upstream Contact: Matthew T. Kennerly
* URL : https://github.com/mtkennerly/poetry-dynamic-versioning
gt; Please work together to make these two packages cooperate better.
They cooperated just fine in my testing with current bullseye/bookworm
versions and the above-described patch seems to have addressed exactly this
issue.
Please provide a reproducer with current (bookworm/bullseye) packages
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: dunamai
Version : 1.16.0
Upstream Contact: Matthew T. Kennerly
* URL : https://github.com/mtkennerly/dunamai
* License : MIT
Programming Lang
On 7/1/22 19:57, Adam D. Barratt wrote:
On Fri, 2021-12-03 at 16:59 +0100, Julien Cristau wrote:
Control: tag -1 confirmed
On Mon, Sep 06, 2021 at 04:21:15PM +, Jakub Ružička wrote:
[ Reason ]
Fixing bug #991463 (CVE-2021-40083) - potential DoS.
[...]
Feel free to go ahead and upload
20:00.0
+
@@ -1,3 +1,10 @@
+knot-resolver (5.3.1-1+deb11u1) bullseye; urgency=medium
+
+ * Fix possible assertion failure in NSEC3 edge-case (CVE-2021-40083)
+(Closes: #991463)
+
+ -- Jakub Ružička Tue, 31 Aug 2021 16:20:00 +
+
knot-resolver (5.3.1-1) unstable; urgency=medi
> I've opened transition bug #993027
Got ack from RT, I've uploaded knot-3.1.1-4 into unstable to start the
transition.
Do I need to wait until the new knot built on all archs before uploading
depending knot-resolver-5.4.1-2 or is there a smart mechanism ensuring
build against correct/latest vers
On 8/26/21 10:42 PM, Santiago Ruano Rincón wrote:
> El 26/08/21 a las 14:45, Jakub Ružička escribió:
>>> - Includes fix for CVE-2021-40083 (Closes: #991463)
>> I've used this magic syntax found throughout the changelog and it closed
>> the bug upon experimental upload
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello,
in order to update knot to latest 3.1.1, its only reverse dependency
knot-resolver needs to be updated to >= 5.4 which supports new
knot 3.1 API/ABI.
I've tested this in experime
> - Includes fix for CVE-2021-40083 (Closes: #991463)
I've used this magic syntax found throughout the changelog and it closed
the bug upon experimental upload, which isn't what I expected. Please
reopen as needed, I'm not yet familiar with handling bugs wrt different
Debian branches.
Regardless,
Hello,
thanks for handling the bind9 side of things!
I'm happy to update the knot source package with update-alternatives
functionality as soon as it's implemented in bind9 package which is a
necessary prerequisite to avoid package file conflicts if I understand
correctly.
Cheers,
Jakub
On Wed
I believe this issue is solved and can be closed.
Cheers,
Jakub Ružička
On 11/20/20 10:34 AM, Santiago Ruano Rincón wrote:
> El 19/11/20 a las 22:04, Santiago Ruano Rincón escribió:
>> El 19/11/20 a las 17:56, Santiago Ruano Rincón escribió:
>> Before uploading a wanted to take a look at the debian/watch file.
>> Attached you can find a work-in-progress version. I cann
On 11/17/20 4:41 PM, Santiago Ruano Rincón wrote:
> El 09/11/20 a las 13:31, Jakub Ružička escribió:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Jakub Ružička
>>
>> * Package name: lua-binaryheap
>> Version : 0.4
>>
Package: wnpp
Severity: wishlist
Owner: Jakub Ružička
* Package name: lua-binaryheap
Version : 0.4
Upstream Author : Thijs Schreijer
* URL : https://github.com/Tieske/binaryheap.lua
* License : MIT
Programming Lang: lua
Description : binary heap
Anything including file:/// doesn't work.
For example: http://www.debian.org/Pics/openlogo-50.png
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Adding forgotten
Screen 0 "Screen" 0 0
to ServerLayout solves the problem, but this behaviour(crash on missing option
in config file) is not nice.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
39 matches
Mail list logo
