Dear mentors,
I would like to improve an existing Debian package. Based on the typical
pattern and name convention of a project based on GitHub, entry `Changelog:` in
file `debian/upstream/metadata` currently points to an address normally used
to present individual releases. The anticipated
+Tia, the bug reporter for #989496.
--
Best regards,
Brian T
B.S. Computer Science 2014 (Truman State University)
Minor Stasitics
Minor Chemistry
Minor Mathematics
signature.asc
Description: PGP signature
mplish… could you clarify?
I didn't realize that the error message I essentially got rid of was
intended functionality. I did some rudimentary testing of the change,
and if "no" was selected then any packages with a changelog entry aren't
updated, but everything else is. Still,
nges as
part of it? I am personally not much help than it comes to python, but
Julian might. Mailing list is de...@lists.debian.org and/or you can join
our IRC channel #debian-apt.
I also note that your changelog targets unstable, which might be fine if
you want to fix the mentioned bug and con
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a package I made a fix for,
"apt-listchanges":
* Package name: apt-listchanges
Version : 3.24.1
Upstream Author : Brian Thompson
* URL : https://salsa.debian.org/briant/apt-li
Thanks, Ansgar, Tobias, for the valuable feedback!
JL
of the
> different changelog entries in a forthcoming release to experimental,
> I'm sure you'll be able to quickly solve my doubt.
What is the relation between the different versions?
If they are separate branches (2.1.X in unstable now to be replaced by
2.2.X currently in unstable), i
about what should be the *order* of the
> different changelog entries in a forthcoming release to experimental,
> I'm sure you'll be able to quickly solve my doubt.
>
> Here is the order of events (from [1]):
>
> [2021-01-03] Accepted mrpt 1:2.1.7-1 (source) into unst
Hi dear mentors!
I'm the upstream author and Debian maintainer of a package, and after
uploading a couple of versions to different releases (unstable and
experimental), now I'm unsure about what should be the *order* of the
different changelog entries in a forthcoming release to experim
Your message dated Sun, 23 Aug 2020 09:39:32 +0300
with message-id <20200823063932.GA6253@localhost>
and subject line Re: Bug#963199: RFS: git2cl/1:2.0 git20120920-3 -- Simple tool
to convert git logs to GNU ChangeLog format
has caused the Debian Bug report #963199,
regarding RFS: git2cl
nongnu.org/projects/git2cl
* License : GPL-2+
* Vcs : https://savannah.nongnu.org/cvs/?group=git2cl
Section : utils
It builds those binary packages:
git2cl - Simple tool to convert git logs to GNU ChangeLog format
To access further information about this package, please
On Wed, Dec 18, 2019 at 07:33:17AM -0800, deb...@lewenberg.com wrote:
> > > $ gbp import-orig ../heimdal_7.7.0.orig.tar.gz -u7.7.0
> > > gbp:info: Importing '../heimdal_7.7.0.orig.tar.gz' to branch 'upstream'...
> > > gbp:info: Source package is heimdal
> > > gbp:info: Upstream version is 7.7.0
> >
On 12/17/2019 10:49 PM, Andrey Rahmatullin wrote:
On Tue, Dec 17, 2019 at 12:02:07PM -0800, deb...@lewenberg.com wrote:
$ gbp import-orig ../heimdal_7.7.0.orig.tar.gz -u7.7.0
gbp:info: Importing '../heimdal_7.7.0.orig.tar.gz' to branch 'upstream'...
gbp:info: Source package is heimdal
gbp:inf
On Tue, Dec 17, 2019 at 12:02:07PM -0800, deb...@lewenberg.com wrote:
> $ gbp import-orig ../heimdal_7.7.0.orig.tar.gz -u7.7.0
> gbp:info: Importing '../heimdal_7.7.0.orig.tar.gz' to branch 'upstream'...
> gbp:info: Source package is heimdal
> gbp:info: Upstream version is 7.7.0
> gbp:error: Import
On 12/17/2019 11:00 AM, Andrey Rahmatullin wrote:
On Tue, Dec 17, 2019 at 10:37:27AM -0800, deb...@lewenberg.com wrote:
1. Download the stretch source packages:
wget
http://http.debian.net/debian/pool/main/h/heimdal/heimdal_7.1.0+dfsg-13+deb9u3.dsc
wget
http://http.debian.net/debian/pool/m
On Tue, Dec 17, 2019 at 10:37:27AM -0800, deb...@lewenberg.com wrote:
> 1. Download the stretch source packages:
>
> wget
> http://http.debian.net/debian/pool/main/h/heimdal/heimdal_7.1.0+dfsg-13+deb9u3.dsc
> wget
> http://http.debian.net/debian/pool/main/h/heimdal/heimdal_7.1.0+dfsg.orig.tar.gz
I am trying to build a Debian stretch package using an updated upstream
tarball. However, I am getting the following error:
gbp.deb.changelog.NoChangeLogError: Changelog debian/changelog not found
Here is what I am doing.
1. Download the stretch source packages:
wget
http://http.debian.net
sed, so if I
> run it on changelog.Debian, without even mentioning changelog or
> ChangeLog, these will be compressed. And if I don't add these
> exclusions, all is compressed. So, I don't see really what you mean
> here.
Hmm, indeed. Run it with both -X and explicit file name? :)
/usr/share/doc" (according to the man-page), and you'll have
to use the -X to be able to have some of these not compressed, so if I
run it on changelog.Debian, without even mentioning changelog or
ChangeLog, these will be compressed. And if I don't add these
exclusions, all is compressed.
Hello,
Am 27.07.19 um 18:50 schrieb Andreas Ronnquist:
> On Sat, 27 Jul 2019 20:05:33 +0500,
> Andrey Rahmatullin wrote:
>
>> On Sat, Jul 27, 2019 at 03:30:05PM +0200, Andreas Ronnquist wrote:
>>> I have a package which got a menu item to show the upstream
>>&g
On Sat, Jul 27, 2019 at 06:50:27PM +0200, Andreas Ronnquist wrote:
> >Call dh_compress on changelog.Debian.
> >
>
> Thanks -
>
> However - I'm sorry to say it wasn't that simple - I believe I run into
> #781131 [1]
That report is only about -X so I don't see how is it related to my
suggestion.
I
On Sat, 27 Jul 2019 20:05:33 +0500,
Andrey Rahmatullin wrote:
>On Sat, Jul 27, 2019 at 03:30:05PM +0200, Andreas Ronnquist wrote:
>> I have a package which got a menu item to show the upstream
>> changelog - So I want to avoid compressing this, but still compress
>>
On Sat, Jul 27, 2019 at 03:30:05PM +0200, Andreas Ronnquist wrote:
> I have a package which got a menu item to show the upstream changelog -
> So I want to avoid compressing this, but still compress the Debian
> changelog.
>
> In my attempts I first use override_dh_compress and
Hi
I have a package which got a menu item to show the upstream changelog -
So I want to avoid compressing this, but still compress the Debian
changelog.
In my attempts I first use override_dh_compress and add -Xchangelog
there, with the results that all changelogs are not compressed. (Since
this
Mattia Rizzolo wrote:
> On Mon, Mar 05, 2018 at 10:44:13PM +0100, Sven Hartge wrote:
>> I am co-maintaining bacula with Carsten Leonhardt and this problem
>> now occured several times for me. (Most probably because of misuse by
>> me, but I want to understand what went wrong.)
> …
>> Note how the
On Mon, Mar 05, 2018 at 10:44:13PM +0100, Sven Hartge wrote:
> I am co-maintaining bacula with Carsten Leonhardt and this problem now
> occured several times for me. (Most probably because of misuse by me,
> but I want to understand what went wrong.)
…
> Note how the last entry is unfinished, becau
Hi!
I am co-maintaining bacula with Carsten Leonhardt and this problem now
occured several times for me. (Most probably because of misuse by me,
but I want to understand what went wrong.)
Take the following debian/changelog file for example:
---8
Sorry, I forgot to add the changelog entries for freetype to my original RFS
email.
Changes since the last upload:
* Non-maintainer upload.
* debian/control:
- Mark libfreetype6-dev Multi-Arch: same
(Closes: #642354, #666761, #870618).
- Remove the deprecated Priority: extra marking from
Ross Vandegrift writes:
> On Tue, Oct 17, 2017 at 09:23:57AM +1100, Ben Finney wrote:
> > As someone who went looking for it recently when you didn't know the
> > recommendation: Where exactly would you expect to find this
> > information, which particular section of Policy and/or other guides?
>
Hi Ben - thanks fo the thorough explanation, much appreciated!
On Tue, Oct 17, 2017 at 09:23:57AM +1100, Ben Finney wrote:
> So now that we agree it's not too clear, and may be difficult to find, I
> would welcome a bug report against Policy for clarifying this issue.
>
> As someone who went look
Ross Vandegrift writes:
> On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> > Ross Vandegrift writes:
> > > Good question. I guess I think of a changelog as history - so changes
> > > I made on 1.15 go with 1.15 whether it was released or not.
> &g
On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> Ross Vandegrift writes:
> > Good question. I guess I think of a changelog as history - so changes
> > I made on 1.15 go with 1.15 whether it was released or not.
>
> Thanks for explaining your perspective.
>
>
On Mon, Oct 16, 2017 at 11:54:20AM +1100, Ben Finney wrote:
> Ross Vandegrift writes:
> > On Sun, Oct 15, 2017 at 12:14:59AM +0200, Mattia Rizzolo wrote:
> > > Rather, I have a counter-question for you: why are you keeping
> > > entries for unreleased uploads in d/
Ross Vandegrift writes:
> On Sun, Oct 15, 2017 at 12:14:59AM +0200, Mattia Rizzolo wrote:
> > Rather, I have a counter-question for you: why are you keeping
> > entries for unreleased uploads in d/changelog? I find it rather
> > confusing, mostly useless and with no real
On 10/15/2017 05:36 AM, Ross Vandegrift wrote:
> Good question. I guess I think of a changelog as history - so changes I
> made on 1.15 go with 1.15 whether it was released or not. But if I
> think of the changelog as telling others about changes in a release,
> then it makes sen
yes!
> > there a downside to always starting from the first release?
>
> Yes, you'd always be putting in the .changes all of the changelog, spam
> debian-devel-changes@ with all the changelog all of the time, and trying
> to close all the bugs you closed in the past with ev
nt. dpkg-genchanges(1) says -c requires a version. Is
^
I'll assume this is a typo and you meant -v
> there a downside to always starting from the first release?
Yes, you'd always be putting in the .changes all
On Sat, Oct 14, 2017 at 11:53:25PM +0500, Andrey Rahmatullin wrote:
> It's not BTS, it's dpkg-genchanges. Pass a proper -v to the command you
> use to build the package.
Thanks for the hint. dpkg-genchanges(1) says -c requires a version. Is
there a downside to always starting from the first rele
On Sat, Oct 14, 2017 at 11:53:25PM +0500, Andrey Rahmatullin wrote:
> On Sat, Oct 14, 2017 at 11:33:24AM -0700, Ross Vandegrift wrote:
> > Hi all,
> >
> > My changelog [1] documents versions that weren't released. I like
> > including that info (it's been
On Sat, Oct 14, 2017 at 11:33:24AM -0700, Ross Vandegrift wrote:
> Hi all,
>
> My changelog [1] documents versions that weren't released. I like
> including that info (it's been useful for me). But the BTS doesn't pick
> up on Closes from those - even though lat
Hi all,
My changelog [1] documents versions that weren't released. I like
including that info (it's been useful for me). But the BTS doesn't pick
up on Closes from those - even though later versions have been uploaded.
Is there a way to make the BTS notice these entries -
On Fri, Aug 25, 2017 at 04:17:34PM +0200, Adam Bilbrough wrote:
> Hi,I have updated the entry to be more descriptive:
> * Adds '+' as an argument for specifying a line number (closes: #872848)
> The upload on mentors.debian.net has been updated with this included.
Hi!
I'm afraid that, just like xm
Hi,I have updated the entry to be more descriptive:
* Adds '+' as an argument for specifying a line number (closes: #872848)
The upload on mentors.debian.net has been updated with this included.
~Adam
On Sun, Apr 24, 2016 at 8:02 PM, Nicholas D Steeves wrote:
> If a package's changelog is published on a wiki, is it still necessary
> and/or desirable to ship a changelog with the Debian package?
It could be useful, yes.
> is something like the following the best solution:
* Nicholas D Steeves , 2016-04-24, 08:02:
If a package's changelog is published on a wiki, is it still necessary
and/or desirable to ship a changelog with the Debian package?
It's not strictly necessary, but it is desirable.
If yes, is something like the following the best solut
Hi,
If a package's changelog is published on a wiki, is it still necessary
and/or desirable to ship a changelog with the Debian package? If yes,
is something like the following the best solution:
curl https://btrfs.wiki.kernel.org/index.php/Changelog | html2text |
sed '0,/(announcem
Am Montag, den 15.02.2016, 08:52 -0700 schrieb Sean Whitton:
> Hello,
>
> On Mon, Feb 15, 2016 at 01:31:53PM +0100, Tobias Frost wrote:
> > This would be discouraged, as d/changelog is supposed to document
> > "Changes in the Debian version of the package" (refer
Hello,
On Mon, Feb 15, 2016 at 01:31:53PM +0100, Tobias Frost wrote:
> This would be discouraged, as d/changelog is supposed to document
> "Changes in the Debian version of the package" (refer to Policy 4.4)
> and not changes to upstream (even if you're upstream).
Alt
I package tuptime https://github.com/rfrail3/tuptime/ [1] [1] lintia
>> n
>> warning me about duplicate-changelog-files:
>>
>> tuptime: duplicate-changelog-files
>> usr/share/doc/tuptime/changelog.Debian.gz
>> usr/share/doc/tuptime/changelog.gz
>>
>
Am Montag, den 15.02.2016, 12:48 +0100 schrieb Ricardo F.:
>
>
> Hello,
>
> When I package tuptime https://github.com/rfrail3/tuptime/ [1] lintia
> n
> warning me about duplicate-changelog-files:
>
> tuptime: duplicate-changelog-files
> usr/share/doc/tuptime/c
Hello,
When I package tuptime https://github.com/rfrail3/tuptime/ [1] lintian
warning me about duplicate-changelog-files:
tuptime: duplicate-changelog-files
usr/share/doc/tuptime/changelog.Debian.gz
usr/share/doc/tuptime/changelog.gz
There is a symlink from CHANGELOG to debian/changelog
Oh, and I forgot to mention: The bug you close in d/changelog should be
the ITP, not the RFS. The RFS will be closed automatically once the ITP
is closed.
pgpTpT7nOdACw.pgp
Description: PGP signature
a 'debian'
directory with required files
What I'm struggling with:
- creating a proper changelog
Obviously I can create it manually but the automagic creation sounded
like a much better plan. But the problem I have is that I can't get it
to work.
When I didn't have a ch
a 'debian'
directory with required files
What I'm struggling with:
- creating a proper changelog
Obviously I can create it manually but the automagic creation sounded
like a much better plan. But the problem I have is that I can't get it
to work.
When I didn't have a ch
off|Acked)-by|git-svn-id:
# Use author information from git
git-author = True
# Merge changelog entries by maintainer
multimaint-merge = True
I've attached the whole section for completeness.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
On 6 February 2014 13:05, Joe Healy wrote:
> I use:
>
> git-dch --id-length=7
>
I'm blind.
Thanks.
--
Arturo Borrero González
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://list
On Thu, Feb 6, 2014 at 10:57 PM, Arturo Borrero Gonzalez <
arturo.borrero.g...@gmail.com> wrote:
> Hi there!
>
> I see that some d/changelog uses git commit ids in addition to the
> commit name [0].
> Is a nice trick that I would like to implement in my packages.
>
>
Hi there!
I see that some d/changelog uses git commit ids in addition to the
commit name [0].
Is a nice trick that I would like to implement in my packages.
However, after reading some docs [1] [2] I don't know what to do (i
guess, using git-dch).
Could anyone point me in the right dire
er' is still the
owner of the packages, though.
So now I've asked him to delete all the packages.
I'll upload them anew with a fixed changelog signature.
Thanks,
Dennis
--
D.H. van Dok :: System administrator :: www.nikhef.nl/grid ::
Phone +31 20 592 22 28 :: http://www.nikhef.nl/
On Mon, Jan 20, 2014 at 12:42:26PM +0100, Dennis van Dok wrote:
> Hi,
>
> my colleague has updated some of the packages for which I am the
> maintainer, and he is an uploader. The last changelog entry is by him.
>
> When I tried to upload to mentors, the package was refused
Hi,
my colleague has updated some of the packages for which I am the
maintainer, and he is an uploader. The last changelog entry is by him.
When I tried to upload to mentors, the package was refused and my
colleague got e-mail from mentors stating that the (his) e-mail address
was not found
Le Fri, May 24, 2013 at 02:14:39AM +, T o n g a écrit :
>
> Not complaining, Debian has lot of good documents. Just that they are not
> to my taste. :-) They are written in the reference book style, whereas I
> more prefer a cook book style. :-) Still not complaining -- We've got to
> appr
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote:
> You can try make a test, put your package in mentors.debian.net and send
> us the link, asking for a revision. I and others can help you to
> understand the process.
I really appreciate the mentoring, and understand that each case would be
di
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote:
> You should do what Prach Pongpanich said. And you can see what other
> people done in their packages. A tip: . . .
Thanks Prach & Eriberto for your answers.
I posted my OP, then I thought, since this is the first time I'm posting
here, bett
Hi Tong,
You can try make a test, put your package in mentors.debian.net and
send us the link, asking for a revision. I and others can help you to
understand the process.
You should do what Prach Pongpanich said. And you can see what other
people done in their packages. A tip:
$ find /usr/share/
On Thu, 23 May 2013 04:13:12 +, T o n g wrote:
> What the proper way to update debian/changelog, to increase the least
> significant version # and add my change comment, and my id?
Please bear in mind that you'd be explaining to someone who has never
maintained a debian package
On Thu, May 23, 2013 at 11:13 AM, T o n g wrote:
> Hi,
>
> What the proper way to update debian/changelog, to increase the least
> significant version # and add my change comment, and my id??
>
> should I use the dch before "dpkg-source -x *.dsc" or after, to
>
Hi,
What the proper way to update debian/changelog, to increase the least
significant version # and add my change comment, and my id??
should I use the dch before "dpkg-source -x *.dsc" or after, to
streamline version # updating?
If after, how about the directory already creat
Raphael Hertzog writes:
> Hi,
>
> On Thu, 16 May 2013, Felix Natter wrote:
>> Eric (the previous packager) installed this file as
>> /usr/share/doc/freeplane/history_en.txt.gz, which seems ok. But how
>> should I deal with the no-upstream-changelog lintian warning?
&
Hi,
On Thu, 16 May 2013, Felix Natter wrote:
> Eric (the previous packager) installed this file as
> /usr/share/doc/freeplane/history_en.txt.gz, which seems ok. But how
> should I deal with the no-upstream-changelog lintian warning?
Pass "history_en.txt" to dh_installchangelog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Le 16/05/2013 15:11, Felix Natter a écrit :
> hi,
>
> the package freeplane does not contain an upstream changelog but
> does contain a high-level change history:
>
>
hi,
the package freeplane does not contain an upstream changelog but does
contain a high-level change history:
===
1.2.23
===
Bug fix for dragging of nodes when node tool tip is shown
===
1.2.22
2013/5/14 Emmanuel Bourg :
> Hi all,
>
> I'm updating several Java packages where the source package generates
> two binaries, libfoo-java with the compiled jars and libfoo-java-doc
> with the documentation. Lintian often complains about the missing
> upstream changelog
Hi all,
I'm updating several Java packages where the source package generates
two binaries, libfoo-java with the compiled jars and libfoo-java-doc
with the documentation. Lintian often complains about the missing
upstream changelog (no-upstream-changelog). Should I put the changelog
in
ebian.org/cgi-bin/bugreport.cgi?bug=705385
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705495
>
> So my question is: How would I mark this in the changelog of a new
> upload,
In such cases I write "see: #nn" instead of "closes: #nn", and so far
nobody co
makes
[1] disappear.
Somehow "Closing" the bug doesn't sound right, because the problem is
still persistent. I also set [1] blocked by [2].
So my question is: How would I mark this in the changelog of a new
upload, and in what way should I comment this in the bug report (beyo
On 03/07/2013 11:11 PM, Bas van den Dikkenberg wrote:
Hi.
Is it allowed to remove old changelog entry’s ?
http://wiki.debian.org/DebianMentorsFaq#Is_it_OK_to_edit_old_changelog_entries.3F
Tomek
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of
I found my way, I was hoping to not have to reformat the complete changelog.
-Oorspronkelijk bericht-
Van: paul.is.w...@gmail.com [mailto:paul.is.w...@gmail.com] Namens Paul Wise
Verzonden: vrijdag 8 maart 2013 4:01
Aan: debian-mentors@lists.debian.org
Onderwerp: Re: Remove old Changelog
On Fri, Mar 8, 2013 at 6:11 AM, Bas van den Dikkenberg wrote:
> Is it allowed to remove old changelog entry’s ?
There is usually no reason to do that, could you explain why you want to?
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-mentors-r
Hi,
On 07.03.2013 23:11, Bas van den Dikkenberg wrote:
> Is it allowed to remove old changelog entry's ?
why do you want to do so. Disk space is cheap these days and having them
is beneficial for archiving purposes. Some packages have a long history
of changelogs [1] and that's ve
Hi.
Is it allowed to remove old changelog entry's ?
With kind regards,
Bas van den Dikkenberg
On Sat, Mar 2, 2013 at 6:05 AM, Tony Houghton wrote:
> The thing is there isn't a separate patch in the debian packaging or
> elsewhere in the pending release tarball because I've applied the patch
> to the code upstream. The bug is upstream too, not in Debian. So
> including the URL for the upstr
eam, you can thank the contributor in the upstream
changelog. It is not necessary to repeat the information in the Debian
changelog. If there was a Debian bug associated to the issue, you can mention
its number together with the mention of a "New upstream version".
Have a nice day,
--
Origin: link to patch applied in upstream VCS
> Bug: http://upstream.bugtrackerurl/1275270
>
> > I've applied the patch upstream but don't know the best way to credit
> > the author in debian/changelog. Include his name?
>
> I would either write
>
> * Apply upstream patch
don't know the best way to credit
> the author in debian/changelog. Include his name?
I would either write
* Apply upstream patch fixing frobnicator, 02_fix_frob.diff
(Closes: #245274)
letting people look at the patch header for credits, or
* Apply upstream patch by John Doe f
As both the upstream and Debian maintainer for roxterm I'm unsure what
to do about documenting a patch that was submitted by someone else to
the upstream tracker. I've applied the patch upstream but don't know
the best way to credit the author in debian/changelog. Include his
name
Hello Etienne,
* On Tue, Aug 07, 2012 at 04:48:54PM +0200, Etienne Millon wrote:
> Hi Cédric,
>
> I believe that you should call dh_compress after dh_installchangelogs :
>
That is correct, thanks.
> > binary-arch: build install
> > [...]
> > dh_compress
> > dh_installchangelogs
Hi Cédric,
I believe that you should call dh_compress after dh_installchangelogs :
> binary-arch: build install
> [...]
> dh_compress
> dh_installchangelogs
Also, your debian/rules may be simpler if you use debhelper's
override_* targets, but that's a matter of personal pref
Hello,
Trying to package ohnetlib (ITP: bug #682190 ), I get an error from
lintian
libohnet: changelog-file-not-compressed changelog.Debian
I use dh_installchangelogs in debian/rules which I understand shall
take care of the compression by itself. Am I mistaken here,
or is there anything
On Tue, Jul 17, 2012 at 10:24:07AM +0200, Simon Chopin wrote:
> Quoting Jerome BENOIT (2012-07-17 10:11:16)
> > The upstream source package contains no changelog file,
> > but the library website provides matter to extract one for it.
> >
> > I guess that I may have to
Hi !
On 17/07/12 10:24, Simon Chopin wrote:
Quoting Jerome BENOIT (2012-07-17 10:11:16)
Hello List:
Hi,
I am package a library from scratch.
The upstream source package contains no changelog file,
but the library website provides matter to extract one for it.
I guess that I may have to
Quoting Jerome BENOIT (2012-07-17 10:11:16)
> Hello List:
Hi,
>
> I am package a library from scratch.
> The upstream source package contains no changelog file,
> but the library website provides matter to extract one for it.
>
> I guess that I may have to extract the ch
Hello List:
I am package a library from scratch.
The upstream source package contains no changelog file,
but the library website provides matter to extract one for it.
I guess that I may have to extract the changelog file from the website:
may I forget it ?
is there any tool to do so ?
Any
On 07/15/2012 01:49 PM, Charles Plessy wrote:
> Le Sun, Jul 15, 2012 at 11:25:14AM +, Bart Martens a écrit :
>>
>> I would mention this in debian/changelog :
>>
>> * debian/control: No longer Build-Depends: poppler-utils, asciidoc, lynx.
>>
>> But I d
Le Sun, Jul 15, 2012 at 11:25:14AM +, Bart Martens a écrit :
>
> I would mention this in debian/changelog :
>
> * debian/control: No longer Build-Depends: poppler-utils, asciidoc, lynx.
>
> But I don't know how detailed such information must be for debian-policy.
&
t; Bart Martens
> >
>
> Hi Bart
>
> I just had a look at the changelog, and it mentions "Remove unused
> build-deps".
I see that now too. So actually you did mention it, and I overlooked it.
> Is that not enough?
Maybe this is enough for some sponsors.
Changes since the last upload:
* Add 0002-add-multiarch-support.patch
* Bump compatibility level to 9.
* Bump Standards-Version to 3.9.3 (no changes).
* Add Pre-Depends: ${misc:Pre-Depends} to libx52pro0.
* Set libx52pro0 and libx52pro-dev Multi-Arch: same
* Install the libraries in
Hi,
On Di, 24 Apr 2012, Ben Finney wrote:
> To say it more plainly: Modifying previous changelog entries, while not
> prohibited, does break an implicit user expectation. I think that
> expectation is reasonable to an extent, and breaking it is costly to the
> same extent.
But th
Russ Allbery writes:
> Ben Finney writes:
> > [modifying previous changelog entries] breaks the entirely
> > reasonable expectation: that a changelog only ever accumulates
> > entries for the latest release, and nothing in earlier releases has
> > changed since the l
Tomasz Muras writes:
> On 04/22/2012 02:48 PM, Bernhard R. Link wrote:
>> * Arno Töll [120421 11:51]:
>>> The whole point of a changelog is a time dependent frozen point of view
>>> at your package. Once you released a version of a package, you should
>>
1 - 100 of 560 matches
Mail list logo
