* Andrey Rahmatullin w...@wrar.name, 2014-02-18, 02:02:
I have a daemon (#738927) that exits with non-zero status on some
systems, so its initscript fails there too. Should the initscript be
fixed or only the postinst which runs that initscript? In any case,
what exactly should be done?
The copyright exception is in the upstream readme, in the source
tarball under share/doc. The readme is where xchat mentions the
OpenSSL exception, as well. This is one of the first things I
discussed with #debian-mentors when I started this process and a
couple people said it was fine to have the
Hallo Darius,
Am Montag, den 17.02.2014, 20:52 +0100 schrieb Dariusz Dwornikowski:
I am trying to work on an orphaned package maradns. It uses quite a
lot of patches managed with quilt. I created a repo on alioth [1] to
manage different versions. I imported all the versions (debsnap and
On wto, lut 18, 2014 at 07:46:53 +0100, Tobias Frost wrote:
Hallo Darius,
Am Montag, den 17.02.2014, 20:52 +0100 schrieb Dariusz Dwornikowski:
I am trying to work on an orphaned package maradns. It uses quite a
lot of patches managed with quilt. I created a repo on alioth [1] to
ACK. (Reading the upstreams' homepage, you should definitly go for the
latest version. The latest upstream fixes a local DoS.
As a side, please add all CVE-# which closes the new version into the
changelog, please follow the procedure as in [1]))
Thank you, I will do it.
Ok the
Am Dienstag, den 18.02.2014, 21:12 +0100 schrieb Dariusz Dwornikowski:
ACK. (Reading the upstreams' homepage, you should definitly go for the
latest version. The latest upstream fixes a local DoS.
As a side, please add all CVE-# which closes the new version into the
changelog,
Tobias Frost t...@frost.de writes:
Never had a CVE myself, but I think this is the way to go:
technically you don't need a debian bug, you could just write (random
example here [1])
maradns (version-1) unstable; urgency=high
* new upstream release
- fixes CVE--,
Your message dated Tue, 18 Feb 2014 22:11:47 +0100
with message-id 20140218211147.ge16...@ramacher.at
and subject line Re: Bug#738458: RFS: libebur128/1.0.1-1 [ITP] --
implementation of the EBU R128 loudness standard
has caused the Debian Bug report #738458,
regarding RFS: libebur128/1.0.1-1
On wto, lut 18, 2014 at 01:29:06 -0800, Russ Allbery wrote:
Tobias Frost t...@frost.de writes:
Never had a CVE myself, but I think this is the way to go:
technically you don't need a debian bug, you could just write (random
example here [1])
maradns (version-1) unstable; urgency=high
Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl writes:
On wto, lut 18, 2014 at 01:29:06 -0800, Russ Allbery wrote:
I think you were also saying this, but just to be very clear: please
also include the CVE numbers directly in debian/changelog in the entry
for whatever release they
Hi Vincent,
Here's the rest:
1) Recommends line moved back to where it should be
2) There is no doxygen-built documentation distributed with this
package; I discussed it with #debian-mentors and they seemed to think
that the Doxyfile in the upstream tarball is only there for
development
Your message dated Wed, 19 Feb 2014 04:26:28 +
with message-id e1wfyjs-0002ce...@quantz.debian.org
and subject line closing RFS: niceshaper/1.0.0-3 [ITP]
has caused the Debian Bug report #717360,
regarding RFS: niceshaper/1.0.0-3 [ITP]
to be marked as done.
This means that you claim that the
Your message dated Tue, 18 Feb 2014 21:27:24 -0800
with message-id
caczd_tabzm8o-neeea0psanz-kq-xaxen8v+frapo4-cfuv...@mail.gmail.com
and subject line Re: Bug#738683: RFS: hexchat/2.9.6.1-1 [ITP]
has caused the Debian Bug report #738683,
regarding RFS: hexchat/2.9.6.1-1 [ITP]
to be marked as
13 matches
Mail list logo
