Oke ,
Fixed the isues and uploaded a new version
WIth kind regards,
Bas
-Oorspronkelijk bericht-
Van: Arno Töll [mailto:a...@debian.org]
Verzonden: vrijdag 20 april 2012 23:40
Aan: 669...@bugs.debian.org
CC: Bas van den Dikkenberg
Onderwerp: Bug#669609: sponsorship-requests: NMU
* Do not modify previous changelog entries, especially not in NMUs.
Hi all,
are there concrete problems caused by modifying previous changelog entries ? I
do it from time to time, of course not when the diff has to be carefully
inspected by others as it would be a distraction, and I have not
On 21.04.2012 09:35, Charles Plessy wrote:
are there concrete problems caused by modifying previous changelog entries ?
I
do it from time to time, of course not when the diff has to be carefully
inspected by others as it would be a distraction, and I have not found it
causing breakages.
Hi,
On 21.04.2012 09:22, Bas van den Dikkenberg wrote:
Fixed the isues and uploaded a new version
it looks all fine now. Please file a NMU bug so that I can sponsor your
upload afterwards. You can use the nmudiff tool to assist you filing
such a bug. I would upload to DELAYED/7.
--
with kind
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package libextractor
* Package name: libextractor
Version : 1:0.6.3-4
Upstream Author : Christian Grothoff christ...@grothoff.org
* URL :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package libmicrohttpd
* Package name: libmicrohttpd
Version : 0.9.19-3
Upstream Author : Christian Grothoff christ...@grothoff.org
* URL :
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package reviewboard
* Package name: reviewboard
Version : 1.6.5-1
Upstream Author : Christian Hammond, David Trowbridge
* URL : http://reviewboard.org/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package gnunet
* Package name: gnunet
Version : 0.9.2-1
Upstream Author : Christian Grothoff christ...@grothoff.org
* URL : https://gnunet.org
* License : GPL3
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package gnunet-gtk
* Package name: gnunet-gtk
Version : 0.9.2-1
Upstream Author : Christian Grothoff christ...@grothoff.org
* URL : https://gnunet.org/
* License :
Your message dated Sat, 21 Apr 2012 16:45:01 +0200
with message-id 4f92c7ed.6010...@debian.org
and subject line Re: Bug#669609: sponsorship-requests: NMU mod-gnutls/0.5.10-1.1
has caused the Debian Bug report #669609,
regarding sponsorship-requests: NMU mod-gnutls/0.5.10-1.1
to be marked as done.
Dear all,
thank you for your review of the bibtexconv package!
The updated package version 0.8.15
(http://mentors.debian.net/package/bibtexconv) should fix the problems:
- Files already installed by the build system are not listed in debian/ files
any longer.
- debian/copyright has been fixed
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package ttylog
* Package name: ttylog
Version : 0.1.d-2
Upstream Author : Robert James Clay j...@rocasa.us,
Tibor Koleszar o...@debian.org
* URL :
Charles Plessy ple...@debian.org writes:
are there concrete problems caused by modifying previous changelog
entries ?
Doing that breaks the entirely reasonable expectation: that a changelog
only ever accumulates entries for the latest release, and nothing in
earlier releases has changed since
Le Sun, Apr 22, 2012 at 12:22:43PM +1000, Ben Finney a écrit :
Charles Plessy ple...@debian.org writes:
are there concrete problems caused by modifying previous changelog
entries ?
Doing that breaks the entirely reasonable expectation: that a changelog
only ever accumulates entries for
Are there any best practices when packaging where upstream only has a
git repo? I was thinking of forking it and tagging it, and so on;
does that make sense as a means of maintaining an upstream?
I wish to package gedit-code-assistance, found at
Never mind, I found a real upstream. Turned out the author moved
development from github, but left no pointer :(
Warmest regards,
Michael
On Sun, Apr 22, 2012 at 1:50 PM, Michael van der Kolff
mvanderko...@gmail.com wrote:
Are there any best practices when packaging where upstream only has a
Ben Finney ben+deb...@benfinney.id.au writes:
Charles Plessy ple...@debian.org writes:
are there concrete problems caused by modifying previous changelog
entries ?
Doing that breaks the entirely reasonable expectation: that a changelog
only ever accumulates entries for the latest release,
17 matches
Mail list logo
