Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd":
* Package name: nsd
Version : 4.3.9-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License :
Control: tags 984460 - moreinfo
Control: retitle 984460 RFS: tlog/12-1 [ITP] -- terminal I/O recording
and playback
Hi Bastian,
Am 26.11.21 um 23:08 schrieb Bastian Germann:
There are a lot of copyright notices that you do not mention in
debian/copyright,
most prominently Red Hat copyrighted
Hi Justin,
Am 02.08.21 um 01:08 schrieb Justin St. Marie:
Have you gained any traction packaging tlog? This package would be very
helpful to me.
Unfortunately not, but that is not really surprising as Debian has been
more or less frozen since March. I would try to find a sponsor again
afte
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd" or a DD who would grant
me the upload rights for my DM key for the "nsd" package.
* Package name: nsd
Version : 4.3.6-1
Upstream Author : nsd-us...@nlnetlabs.nl
* U
Hi,
On Sat, 30 Jan 2021 09:35:53 + u...@net9.ga wrote:
I am not sure a query for a listener shouldn't be done by postinst. I
agree that on package upgrade, I would hope the daemon would bestarted
without the admin intervention. What is the point of starting the daemon
at postinst, after the
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "tlog":
* Package name: tlog
Version : 11-1
Upstream Author : Nikolai Kondrashov
* URL : http://scribery.github.io/tlog/
* License : GPL-2+
* Vcs
Hi,
as there has not been any activity on this in the last two years,
I have taken the liberty to re-assign this bug to myself.
I have started the packaging at:
https://salsa.debian.org/ascii/tlog
An intial package uploaded at mentors:
https://mentors.debian.net/package/tlog/
@Adam:
I know t
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "yadifa":
* Package name: yadifa
Version : 2.4.2-1
Upstream Author : yadifa-us...@mailinglists.yadifa.eu
* URL : https://www.yadifa.eu
* License : BSD-
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd":
* Package name: nsd
Version : 4.3.5-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd":
* Package name: nsd
Version : 4.3.4-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License :
fixed 947030 4.3.3-1
close 947030
thanks
This EDNS size was made default in
https://github.com/NLnetLabs/nsd/pull/123
which was released as NDS 4.3.3
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd":
* Package name: nsd
Version : 4.3.3-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "yadifa":
* Package name: yadifa
Version : 2.3.10-1
Upstream Author : yadifa-us...@mailinglists.yadifa.eu
* URL : https://www.yadifa.eu
* License : EUR
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd":
* Package name: nsd
Version : 4.3.2-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License : B
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "yadifa":
* Package name: yadifa
Version : 2.3.9-1
Upstream Author : yadifa-us...@mailinglists.yadifa.eu
* URL : http://www.yadifa.eu
* License : oth
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd"
* Package name: nsd
Version : 4.3.1-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License : NS
version to 4.5.0
* Correct typo (mount/@mount) in nsd.service SystemCallFilter list
* Add upstream patch to include missing headers file to fix FTBFS
Regards,
--
Markus Schade
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nsd"
* Package name: nsd
Version : 4.2.4-1
Upstream Author : nsd-us...@nlnetlabs.nl
* URL : https://www.nlnetlabs.nl/projects/nsd/about/
* License : NS
Hi Joel,
thanks for the report.
The systemd service file has been in part of the package for 5 years,
with the default ordering of sections (unit, service, install).
The upstream service while was more less recently added (~1 year ago).
Since systemd hardening has been available and recommended,
Hi Alex,
I have been unable to reproduce this error on both a fresh buster
install as well as an upgraded stretch.
According to the release notes[1], the min size has been raised to
2048bit, but not 4k.
Please check if your /etc/ssl/openssl.cnf requires longer keys.
Best regards,
Markus
[1]
ht
Package: intel-microcode
Version: 3.20190312.1
Severity: grave
Tags: security
Dear Maintainer,
Intel has released a new microcode version which includes updates for
most CPU models since Nehalem providing the necessary prerequisites for
the recently disclosed MDS vulnerabilities
Please consider
Hi,
it seems that you are using Ubuntu. While the new release is now
available in Debian unstable, I don't think you will be getting it in
Ubuntu until the 19.04 ('disco') release.
Cheers,
Markus
signature.asc
Description: OpenPGP digital signature
Hi Harald,
I have included your simple fix in git for the next release:
https://salsa.debian.org/dns-team/nsd/commit/ea3dafa968dbc3768184fda5da9cc9c3c3506c83
Thanks!
Best regards,
Markus
Dear Christoph,
as of nsd-4.1.25 is built with support for systemd notify.
It was introduced in 4.1.24, but still had some bugs.
For this reason I am not yet changing the default in Debian, yet.
But if you want to test notify support, you can do so now.
Best regards,
Markus
Hi Christoph,
Yes, this is somewhat annoying.
I don't see how we could change this behavior besides patching this in
source. Which I don't think is really justified.
Best regards,
Markus
Hi Martin,
more recent version no longer carry this misleading notice in nsd.conf
Since it is pretty much as given that nsd.conf would be customized (in
absence of a conf.d), this would regularly trigger the (very annoying)
conflict question on upgrades.
So in my personal experience, I much prefe
This issue is further addressed by:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4
by increasing the memory limit for the mitigation on pretty much all
desktop, mobile and Xeon E3 systems since Nehalem.
Best regards,
M
Package: src:linux
Version: 4.9.110-3+deb9u4
Severity: important
Tags: patch
Dear Maintainer,
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still
vulnerable
is more frequent.
Originally this was reported in OpenSUSE, but I can confirm this is also true
with the latest D
Hi everyone,
apparently Intel has changed its mind and is reverting to the old license:
https://01.org/mcu-path-license-2018
https://wccftech.com/intel-microcode-update-gag-order-benchmarks/
But I guess we have to to wait for the actual MCU download to
incorporate this change. What do you think,
Henrique,
could you please clarify what concerns Debian has with the license?
Other distros seem to have no problems. I see updated packages from
Fedora, OpenSUSE, Gentoo and Archlinux.
Best regards,
Markus
Hi,
Am 18.08.2018 um 13:39 schrieb Moritz Mühlenhoff:
> Do we have also indication whether the 20180703 release also fixed the
> SGX angle?
No sure, if you are asking Henrique or me, but yes, the microcode does
include the mitigation for SGX aka Foreshadow.
It is also explicitly stated by Intel
Am 17.08.2018 um 09:54 schrieb Moritz Mühlenhoff:
> This microcode release happened a week before the disclosure of L1TF and with
> all previous CPU bugs, Intel initially only shipped updates to OEMs and only
> released general microcode updates weeks/months later.
>
> Have you been able to confir
Package: intel-microcode
Version: 3.20180703.1
Severity: grave
Tags: security
Dear Maintainer,
Intel has released a new microcode version which includes updates for
further CPU models providing the necessary code for SSBD as well as the
recently disclosed L1TF vulnerability
https://downloadcente
Package: intel-microcode
Version: 3.20180425.1
Severity: grave
Tags: security
Dear Maintainer,
Intel has released a new microcode version which includes updates for
further CPU models providing the necessary code for SSBD as well as the
recently disclosed L1TF vulnerability
https://downloadcente
Package: intel-microcode
Version: 3.20180425.1
Severity: grave
Tags: security
Dear Maintainer,
Intel has released a new microcode version which includes the prerequisites
for SSBD patches
https://downloadcenter.intel.com/download/27945/Linux-Processor-Microcode-Data-File
Contrary to what the do
NSD does not use debconf templates for some time now.
Hence closing this bug
Package: linux
Version: 3.16.7-ckt11-1+deb8u4
Severity: important
The current jessie kernel lacks proper support for the RTL8168/8111H
onboard NICs
Support for them was added in:
commit 76e1d0b8988188956dac091441c1492a79a342666
commit a3bf5c429eb5f5ec4d364d51dfa8855efcc005f8
Please consider ba
Hi Gianfranco
On 17.08.2015 at 16:41 Gianfranco Costamagna wrote:
> 1)
>
> # upstream does not sign releases
> #yadifa source: debian-watch-may-check-gpg-signature
That is a commented out leftover. I have removed it anyway so other
won't think it is still used like you ;-)
> 2) sbin/yadifad/ins
Hi everyone,
On 16.08.2015 at 22:53 Jakub Wilk wrote:
> * Christian Kastner , 2015-08-16, 19:08:
>> debian/rules:
>> - I believe the "export DH_OPTIONS [...] to make magic work" can be
>> dropped. I think this is a remnant from a time long past; I can't find
>> any reference to this in recent docu
On 03/05/2015 04:32 PM, Paul Wise wrote:
> On Thu, 2015-03-05 at 16:24 +0100, Markus Schade wrote:
>> And I have asked them to do so, of course. Likewise with the other
>> things you mentioned (e.g. signing their releases).
>
> Ah, good. I wasn't sure if you had done t
Package: linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: wishlist
The new Skylake CPUs will come with the new Sunpoint PCH that also
brings a new Intel i219 gigabit network chip.
The current e1000e driver lacks support for these new NICs.
Support for them was added in:
commit 79849ebc0e06d775f53d
Package: haveged
Version: 1.9.1-1
Followup-For: Bug #740349
The bug can be resolved by adding an EnvironmentFile line
to the service file and changing the ExecStart line to use the variable.
[Service]
EnvironmentFile=-/etc/default/haveged
ExecStart=/usr/sbin/haveged --Foreground $DAEMON_ARGS
Re
Package: haveged
Version: 1.9.1-1
Severity: normal
Tags: patch
Dear Maintainer,
haveged exits with code 143 instead of 0 for success. Please add the following
line to the [Service] section of the systemd service file:
SuccessExitStatus=143
-- System Information:
Debian Release: 8.0
APT prefe
On 03/05/2015 04:16 PM, Paul Wise wrote:
> On Thu, Mar 5, 2015 at 10:32 PM, Markus Schade wrote:
> You could forward the code quality issues upstream as suggested by the
> Debian social contract:
>
> https://www.debian.org/social_contract
Yes, I know that. ;-)
And I have asked th
Dear Paul, dear mentors,
Thank you for your extensive review. I won't go into detail for every
item you have mentioned, but I believe that many if not most issues have
been dealt with.
But then again, I am just the packager not the developer. So I can do
little about the code quality.
All of my
Dear mentors,
I am again looking for a sponsor for my package "yadifa".
Now with the new release 2.0.0
YADIFA is a "Yet Another DNS Implementation For All",
a DNS server written by the people of the EURid registry.
The URL of the package is:
http://mentors.debian.net/package/yadifa
The respecti
Hi Ben,
On 04/17/2014 11:21 AM, Debian Bug Tracking System wrote:
> #705959: backport e1000e/igb driver for i354, i210, i217 and i218
>
> It has been closed by Ben Hutchings .
Wow, thanks so much. I am looking forward to testing it once the build
bots are done.
Best regards,
Markus
--
To UNS
retitle 705959 backport e1000e/igb driver for i354, i210, i217 and i218
notfound 705959 3.13
thanks
According to the changelog of 3.2.57⁻1 which Ben uploaded to
proposed-updates/stable-new, there is still no mentioning of a fix.
That means wheezy now lacks support for i210/i211 and i217, and the
fixed 701632 3.2
thanks
Since this is fixed in wheezy, this bug can be closed when squeeze goes EOL.
Best regards,
Markus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 04/09/2014 09:00 PM, Christian Kastner wrote:
> Oh, I missed something here: you are using the substitution variable
> ${Description}, but you are not setting it anywhere, which results in
> half-empty descriptions (see the output in
> debian/libdns*/DEBIAN/control). See deb-substvars(5).
Agai
Hi,
thanks for the review, Christian!
On 04/05/2014 06:16 PM, Christian Kastner wrote:
> AFAIK bind9 only stores run-time data in /var/cache/bind (from dynamic
> DNS updates, etc). bind9's zone files are in /etc/bind/zones.
>
> [...]
>
> I'd either go with /etc/yadifa or /var/lib/yadifa. Check
Dear mentors,
I have made some corrections/improvements and re-uploaded the package
again.
However there is one question, which I am not sure, what is correct.
Upstream uses /var/zones as base for its zone files. My guess was that
this is not the proper location for such files in Debian.
So I cha
Hello,
since Martijn has not followed up on this bug for the last months,
I would like to ask if it is okay to have this bug assigned to me.
I have packaged the current version 1.0.3 and uploaded the package(s)
to mentors.debian.net seeking sponsorship:
http://mentors.debian.net/package/yadifa
Package: linux
Version: 3.2.41-2
Severity: wishlist
in the current wheezy kernel there is no support for the Intel i210 and
the Intel i217 NIC, which will ship on many of the upcoming Haswell
mainboards.
It would be nice, given the pending release of wheezy, to have out of
the box support fo
Hi,
to resolve this issue only 3 very small patches should be added, of
which only the last one is actually required.
6538ee62d597ca09035c33838d7516455f4fd3e1
igb: Alternate MAC Address EEPROM Updates
45b58465acaa9d98354e7fa730e3172c5355da06
igb: Alternate MAC Address Updates for Func2&3
65
Package: linux-2.6
Version: 2.6.32-48
Severity: important
Hi
while the recent point release brought support for Dells PERC H710 raid
controller (great work, thanks!), the driver for the Intel i350 NDC is
(still?) showing duplicate MACs. The backports kernel is not affected.
# uname -a
Linux
Hi Ian,
sorry for answering so late.
On Wed, Jan 4, 2012 at 12:41 PM, Ian Campbell wrote:
> On Wed, 2012-01-04 at 11:20 +0100, Markus Schade wrote:
>> unfortunately this is bug does not apply to Debian only. MSI has changed
>> some
>> ACPI tables as of BIOS Version 8.
Hi,
unfortunately this is bug does not apply to Debian only. MSI has changed some
ACPI tables as of BIOS Version 8.7, which lead to this result.
You can either downgrade to 8.6 or boot the kernel with acpi=ht.
Other common workarounds like 'reboot=b' do not work.
Regards,
Markus
--
To UNS
I have orphaned this package ages ago. It should not even be in squeeze.
Even if I would upload a new package that would add the depedency to
dpatch, I doubt very much that it will built against the squeeze kernel.
So I would tag this as won't fix, even though I would prefer that this
package to
Hi,
> In this kernel version, the e1000e driver is missing support for
> i82567V-4 and i82579 and important bug fixes for i82577, i82578 and
> i82583.
test results of the 82579V on an Asus P8Z68-V Pro.
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network
Connection (rev 05)
Hi,
would it be possible to also include support for the 8168/8111E version?
While the nic is working more or less, there seems to be a bit more
setup necessary.
Commits are 01dc7fec4025f6bb72b6b98ec88b375346b6dbbb and probably also
15ecd039b7182d725f4294e01f2fb12c3a88db17
Best regards,
Marku
On Sat, 16 Aug 2008, Michael Prokop wrote:
I'm not sure about the state of bcm5700 at all. It isn't maintained
by Broadcam for a while AFAICS and the tg3 driver seems to replace it.
Do we need bcm5700 at all?
Basically it is completely unmaintained by upstream, which suggests
using the tg3 dr
Package: wnpp
Severity: normal
I am orphaning the package as I have neither the hardware anymore nor
the time and knowledge to adjust this old and rusty driver to
ever-changing kernel interfaces.
Markus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
I'm curious: What's the point of this package ? Are there devices not
supported by the tg3 driver ?
It's not a support problem, but a stability problem. I have a Dell
server with the 5700 chip,
which will hang predictably after a day or so. Also the TSO support
is not very mature in the in-kern
I send an ITA for this package to wnpp (http://bugs.debian.org/366806).
An updated package with the last and latest bcm driver is available at
https://www.csn.tu-chemnitz.de/~marks/debian/ waiting for upload by a
maintainer.
Regards,
Markus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
A new package ready for upload can be found at:
https://www.csn.tu-chemnitz.de/~marks/debian/
includes new upstream version
Regards,
Markus Schade
--
~~ God does not play dice with the universe. - A.Einstein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubs
66 matches
Mail list logo
