Re: compiled binary file in source package

2018-02-10 Thread David Rabel
On 10.02.2018 00:43, Ben Finney wrote: > David Rabel <david.ra...@noresoft.com> writes: >> On 09.02.2018 00:44, Ben Finney wrote: >>> Is the compiled binary file generated entirely from sources that are >>> all in the upstream source distribution? >> &

Re: compiled binary file in source package

2018-02-09 Thread David Rabel
On 09.02.2018 00:44, Ben Finney wrote: > David Rabel <david.ra...@noresoft.com> writes: > >> I am maintaining jugglinglab. The upstream source package contains a >> compiled binary file. What is the cleanest solution to get rid of it? > > Is the compiled binar

piuparts - installation and purging test

2018-02-08 Thread David Rabel
Hi there, I am maintaining vim-lastplace. A few days ago I saw on my Debian Maintainer Dashboard that piuparts was failing at the installation and purging test. Today I wanted to fix this, but the message was gone. So piuparts now succeeds on piuparts.d.o . But when I run piuparts on my local

compiled binary file in source package

2018-02-08 Thread David Rabel
Hi there, I am maintaining jugglinglab. The upstream source package contains a compiled binary file. What is the cleanest solution to get rid of it? Story behind that: When I started packaging jugglinglab in 2016 I just deleted the file with a patch. This is unclean and for example sbuild

Re: Packaging for Debian with different gpg-keys and emali-addresses

2017-03-01 Thread David Rabel
On 01.03.2017 00:18, Ben Finney wrote: > David Rabel <ra...@b1-systems.de> writes: > >> PS: Please CC me, if you answer to this mail, as I am subscribed to >> Debian mentors anymore. > > To participate, please subscribe so that we don't all have to violate >

Packaging for Debian with different gpg-keys and emali-addresses

2017-02-28 Thread David Rabel
Hi there, is it possible to do Debian packaging with different gpg keys and email addresses? And how would I do it? Yours David PS: Please CC me, if you answer to this mail, as I am subscribed to Debian mentors anymore. -- David Rabel Linux Consultant & Trainer Tel.: +49-1511-5908566

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

2016-08-02 Thread David Rabel
Hi, On 02.08.2016 08:40, Gianfranco Costamagna wrote: > I fully agree here, just a few questions about *where* to put this package. > http://www.vim.org/scripts/ > I think I don't understand. > what about adding it as a patch to the current vim-scripts package? >

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

2016-08-01 Thread David Rabel
Hi, On 01.08.2016 22:35, Gianfranco Costamagna wrote: > it is good, just called "3.0.2-2" > > please use -1 as versioning and dput -f on mentors until it gets accepted. > Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 . > last thing: how do I enable such extension?

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

2016-08-01 Thread David Rabel
Hi Gianfranco, On 01.08.2016 10:38, Gianfranco Costamagna wrote: > 1) please use for debian copyright the same license as upstream if possible > > (this makes easier to forward patches) Done. > > 2) I'm not sure about the directories and installation path > > │ ├── vim-lastplace > │ │

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

2016-07-31 Thread David Rabel
nges since the last upload: * Initial release (Closes: #825665) Regards, David Rabel