Re: gbp dch --release

[Matt Zagrabelny]

Ping?

Sorry, but the lone reply I received didn't help.

Thanks for anyone's time looking at this.

Cheers,

-m

On Wed, Mar 13, 2024 at 6:21 AM Matt Zagrabelny  wrote:

> Hello Mentors,
>
> It has been a while since I've used gbp and I'm struggling to remember
> how to perform a release.
>
> I've got some software that I'm the upstream for and years ago I
> packaged up for use and installation at $JOB.
>
> I recently updated the software and tagged it for release.
>
> Debian branch: debian
> Upstream branch: master
>
> $ git switch master
> $ git tag v0.21
> $ git switch debian
> $ git merge master
> $ gbp dch --release
>
> ...but gbp chooses a release of 0.20-2 as opposed to 0.21-1.
>
> What am I missing?
>
> Thanks for helping me to get back on the gbp horse!
>
> -m
>
> PS. In case it is helpful, here are the last couple of commits from
> the git repo:
>
> $ git log -p
>
> commit 2b4eaec45156a893cd4c74c7dcde7b9b036bbc44 (HEAD -> debian)
> Merge: 9f4b884 38d08de
> Author: Matt Zagrabelny 
> Date:   Tue Mar 12 13:51:26 2024 -0500
>
> Merge branch 'master' into debian
>
> commit 38d08de5d97d81d3ca0f85226ec4eb88941066c1 (tag: v0.21, master)
> Author: Matt Zagrabelny 
> Date:   Tue Mar 12 13:45:41 2024 -0500
>
> Update changelog for release
>
> diff --git a/changelog b/changelog
> index 8788f2a..20f14b8 100644
> --- a/changelog
> +++ b/changelog
> @@ -47,3 +47,5 @@ undefined warnings.
>  0.19 - Suppress warning about smartmatch
>
>  0.20 - Filter out empty username from demographics source query
> +
> +0.21 - Connect to MariaDB with UTF-8 encoding
>

Re: gbp dch --release

[Matt Zagrabelny]

Hi,

‪On Wed, Mar 13, 2024 at 6:35 AM ‫دانیال بهزادی‬‎
 wrote:‬
>
> Can you try importing new upstream version with gbp too:
>
> gbp import-orig ../package.orig.tar.gz
>
> Or if you use watch file:
>
>gbp import-orig --uscan

Thanks for the reply.

I'm upstream and the upstream code is in the master branch - so I
don't release tar balls.

Sorry for not being clear about that.

-m

gbp dch --release

[Matt Zagrabelny]

Hello Mentors,

It has been a while since I've used gbp and I'm struggling to remember
how to perform a release.

I've got some software that I'm the upstream for and years ago I
packaged up for use and installation at $JOB.

I recently updated the software and tagged it for release.

Debian branch: debian
Upstream branch: master

$ git switch master
$ git tag v0.21
$ git switch debian
$ git merge master
$ gbp dch --release

...but gbp chooses a release of 0.20-2 as opposed to 0.21-1.

What am I missing?

Thanks for helping me to get back on the gbp horse!

-m

PS. In case it is helpful, here are the last couple of commits from
the git repo:

$ git log -p

commit 2b4eaec45156a893cd4c74c7dcde7b9b036bbc44 (HEAD -> debian)
Merge: 9f4b884 38d08de
Author: Matt Zagrabelny 
Date:   Tue Mar 12 13:51:26 2024 -0500

Merge branch 'master' into debian

commit 38d08de5d97d81d3ca0f85226ec4eb88941066c1 (tag: v0.21, master)
Author: Matt Zagrabelny 
Date:   Tue Mar 12 13:45:41 2024 -0500

Update changelog for release

diff --git a/changelog b/changelog
index 8788f2a..20f14b8 100644
--- a/changelog
+++ b/changelog
@@ -47,3 +47,5 @@ undefined warnings.
 0.19 - Suppress warning about smartmatch

 0.20 - Filter out empty username from demographics source query
+
+0.21 - Connect to MariaDB with UTF-8 encoding

Bug#931879: RFS: simple-scan/3.32.2.1-1

[Matt Zagrabelny]

Greetings,

Thanks for packaging software for Debian!

On Thu, Jul 11, 2019 at 2:42 PM Jörg Frings-Fürst  wrote:

> Package: sponsorship-requests
> Severity: normal
>
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "simple-scan"
>
>Package name: simple-scan
>Version : 3.32.2.1-1
>Upstream Author : Robert Ancell 
>URL : https://gitlab.gnome.org/GNOME/simple-scan
>License : GPL-3+
>Section : gnome
>
>  It builds those binary packages:
>
> simple-scan - Simple Scanning Utility
>
>
Please consider using a slightly more informative description. Three words
might be sufficient for the description, but two of those three words are
in the package name and are, unfortunately, generic in nature.

Cheers!

-m

Re: Understanding Git workflow around DEP-14

[Matt Zagrabelny]

Hi Geert!

On Mon, Mar 11, 2019 at 2:12 PM Geert Stappers  wrote:

> On Mon, Mar 11, 2019 at 01:50:49PM -0500, Matt Zagrabelny wrote:
>
>
> > > 2. What should the "master" branch be used for?
>
> Consider the string "master" a label for _your leading branch_
>
>
> > I don't use the master branch with DEP-14. I believe the DEP is stating
> > that you'd use "master" for native packages - which from the sounds of
> it,
> > yours is not. Therefore, I'd not use "master".
>
> But you have your own leading branch
>

When I am packaging someone else's software (upstream/latest) for inclusion
in Debian (debian/master), I don't feel like I have "my own" leading branch.

What am I missing for using (or not using) a "master" branch?


>
> > > 3. When a new upstream tarball is released, where should it be
> imported?
> > >
> >
> > Assuming you have a remote named "github", I suppose you'd do something
> > like:
> >
> > git pull github upstream/latest
>
>
> I think it should be (be warned  _not tested_ )   avoid that your
> current branch gets pollueted.
>

What makes you believe that the current branch would get polluted?

I believe a:

git pull repo refspec

is equivalent to:

git checkout refspec
git pull repo

Am I wrong?

Thanks for the dialog!

-m

Re: Understanding Git workflow around DEP-14

[Matt Zagrabelny]

I'm no expert. I've commented inline with things I've done and how I read
and understand DEP-14.

On Mon, Mar 11, 2019 at 1:30 PM  wrote:

> I am packaging some upstream software for Debian and I am trying to
> understand the workflow around "DEP-14: Recommended layout for Git
> packaging repositories".
>
> Looking at DEP-14 I might have these Git branches:
>
>master
>debian/master
>debian/stretch
>upstream/latest
>
> I understand that the Debian packaging files in debian/ will appear in
> the "debian/*" branch, but my general question is: what is the workflow
> around all these branches? When and how do files get merged from one
> branch to another?
>

git checkout debian/master
git merge upstream/latest

You want to keep the upstream/latest branch free of Debian specific
packaging bits.

You can use tags to mark any upstream releases. Here is an example:

$ git tag
debian/2.4-1
debian/2.4-2
upstream/2.4

More specifically:
>
> 1. Besides the debian/ directory, what is the difference between the
> "debian/master" branch and the "upstream/latest" branch?
>

I don't believe anything.


>
> 2. What should the "master" branch be used for?
>

I don't use the master branch with DEP-14. I believe the DEP is stating
that you'd use "master" for native packages - which from the sounds of it,
yours is not. Therefore, I'd not use "master".


>
> 3. When a new upstream tarball is released, where should it be imported?
>

Assuming you have a remote named "github", I suppose you'd do something
like:

git pull github upstream/latest

Then, you'd do:

git checkout debian/master
git merge upstream/latest

Cheers,

-m

Re: missing email after mentors upload and other problems

[Matt Zagrabelny]

On Mon, Jun 25, 2018 at 1:03 PM, Mattia Rizzolo  wrote:

>
> Problem is that you are not uploading any source.  Binary-only uploads
> are silently discarded.
>

What do folks think about having an autoreply email that states something
like:

"""
You have just uploaded a binary-only package to mentors.d.n.

You need to upload a .changes that includes a source build.

For packages built with dpkg-buildpackage see...

For pbuilder 

For sbuild ...
"""

Just an idea.

Thanks,

-m

Re: missing email after upload and other problems

[Matt Zagrabelny]

Hey Andrey,

On Mon, Jun 25, 2018 at 1:13 PM, Andrey Rahmatullin  wrote:

>
> > Is there a canonical way to upload dsc files to mentors?
> By uploading a .changes that includes it.
>

Good to know.


>
> > Following [0] is how I came to the command:
> >
> > dput mentors *.changes
> >
> >
> >
> > > How did you generate that .changes?
> >
> >
> > gbp buildpackage
> Is that the whole command?
>

For building, yes.


> Are you using sbuild, pbuilder or none?
>

You are two steps ahead of me: I'm using sbuild, but I didn't realize I
needed to instruct sbuild to build the source, too. I (incorrectly) assumed
that a source build would come "for free".

I've rebuilt and my .changes file now references the .dsc and other source
components. Things look better, too:

$ dput -f mentors cdpr_2.4-3_amd64.changes
Checking signature on .changes
gpg: /home/mzagrabe/git/debian/cdpr/build-area/cdpr_2.4-3_amd64.changes:
Valid signature from 07E2BFA842A00942
Checking signature on .dsc
gpg: /home/mzagrabe/git/debian/cdpr/build-area/cdpr_2.4-3.dsc: Valid
signature from 07E2BFA842A00942
Uploading to mentors (via https to mentors.debian.net):
  Uploading cdpr_2.4-3.dsc: done.
  Uploading cdpr_2.4-3.debian.tar.xz: done.
  Uploading cdpr-dbgsym_2.4-3_amd64.deb: done.
  Uploading cdpr_2.4-3_amd64.buildinfo: done.
  Uploading cdpr_2.4-3_amd64.deb: done.
  Uploading cdpr_2.4-3_amd64.changes: done.
Successfully uploaded packages.

Thanks for your help!

-m

Re: missing email after mentors upload and other problems

[Matt Zagrabelny]

Hey Mattia,

On Mon, Jun 25, 2018 at 1:03 PM, Mattia Rizzolo  wrote:

> Thnaks for CCing support@mentors.d.n.
>
> On Mon, Jun 25, 2018 at 07:07:10PM +0200, Geert Stappers wrote:
> > On Mon, Jun 25, 2018 at 11:08:57AM -0500, Matt Zagrabelny wrote:
> > >
> > > $ dput -f mentors cdpr_2.4-3_amd64.changes
> > > Checking signature on .changes
> > > gpg: /home/mzagrabe/git/debian/cdpr/build-area/cdpr_2.4-3_
> amd64.changes:
> > > Valid signature from 07E2BFA842A00942
> > > Uploading to mentors (via https to mentors.debian.net):
> > >   Uploading cdpr-dbgsym_2.4-3_amd64.deb: done.
> > >   Uploading cdpr_2.4-3_amd64.buildinfo: done.
> > >   Uploading cdpr_2.4-3_amd64.deb: done.
> > >   Uploading cdpr_2.4-3_amd64.changes: done.
> > > Successfully uploaded packages.
> > >
> > > According to [0] the upload should be available between 0 and 2 minutes
> > > (HTTPS upload.) It has been over 10 minutes now.
>
> Problem is that you are not uploading any source.  Binary-only uploads
> are silently discarded.
>

Okay. Good to know.


> You are probably using sbuild, which in its default configuration does
> binary-only architecture-dependand builds (i.e. -B).


Correct! Good deducing. :)


> You usually want
> to perform -F builds in your local system.


Located. Super.

Rebuilding right now with ~/.sbuildrc option:

$build_source = 1;

Thanks all!

-m

Re: missing email after upload and other problems

[Matt Zagrabelny]

On Mon, Jun 25, 2018 at 12:39 PM, Andrey Rahmatullin 
wrote:

> On Mon, Jun 25, 2018 at 11:08:57AM -0500, Matt Zagrabelny wrote:
> > $ dput -f mentors cdpr_2.4-3_amd64.changes
> > Checking signature on .changes
> > gpg: /home/mzagrabe/git/debian/cdpr/build-area/cdpr_2.4-3_amd64.changes:
> > Valid signature from 07E2BFA842A00942
> > Uploading to mentors (via https to mentors.debian.net):
> >   Uploading cdpr-dbgsym_2.4-3_amd64.deb: done.
> >   Uploading cdpr_2.4-3_amd64.buildinfo: done.
> >   Uploading cdpr_2.4-3_amd64.deb: done.
> >   Uploading cdpr_2.4-3_amd64.changes: done.
> > Successfully uploaded packages.
> You are not uploading the source package.
>

Sure.

Is there a canonical way to upload dsc files to mentors?

Following [0] is how I came to the command:

dput mentors *.changes



> How did you generate that .changes?


gbp buildpackage

Thanks,

-m

[0] https://mentors.debian.net/intro-maintainers

Re: missing email after upload and other problems

[Matt Zagrabelny]

On Mon, Jun 25, 2018 at 10:51 AM, Matt Zagrabelny 
wrote:

>
>>-f
>>--force
>>   Disable the check for a unique upload.  See VERIFICATION
>> CHECKS, above, for a description of this check.
>>
>>
> I'll give the force option a try and see if the "reupload" fixes anything.
> Fingers crossed!
>

$ dput -f mentors cdpr_2.4-3_amd64.changes
Checking signature on .changes
gpg: /home/mzagrabe/git/debian/cdpr/build-area/cdpr_2.4-3_amd64.changes:
Valid signature from 07E2BFA842A00942
Uploading to mentors (via https to mentors.debian.net):
  Uploading cdpr-dbgsym_2.4-3_amd64.deb: done.
  Uploading cdpr_2.4-3_amd64.buildinfo: done.
  Uploading cdpr_2.4-3_amd64.deb: done.
  Uploading cdpr_2.4-3_amd64.changes: done.
Successfully uploaded packages.

According to [0] the upload should be available between 0 and 2 minutes
(HTTPS upload.) It has been over 10 minutes now.

Similarly to my initial upload, I don't see any packages under my packages
link:

"No packages"

Any suggestions?

Thanks!

-m

[0] https://mentors.debian.net/qa

Re: missing email after upload and other problems

[Matt Zagrabelny]

Hi Gregor,

Thanks for the reply.

On Mon, Jun 25, 2018 at 10:43 AM, gregor herrmann  wrote:

> On Mon, 25 Jun 2018 10:02:33 -0500, Matt Zagrabelny wrote:
>
> > I've uploaded to mentors via:
> >
> > $ dput mentors cdpr_2.4-3_amd64.changes
> > Package has already been uploaded to mentors on mentors.debian.net
> > Nothing more to do for cdpr_2.4-3_amd64.changes
>
> > Any help in:
> > A) Sponsoring this package would be great.
> > B) Figuring out why I don't get an email after a dput upload to mentors.
> > C) Why I don't see my package via the web UI.
> > Would be most appreciated.
>
> B) and C) are easy to answer: Because you didn't upload it, as the
> output of dput quoted above tells you :)
>
>
I know, I know... :)

I didn't save the console output of my initial upload, which did tell me
that I uploaded it - so I just reran the command to demonstrate that I used
dput in a sensible way.



> dput checks if there is already a file called something like
> cdpr_2.4-3_amd64.mentors.upload and then aborts.
> So you can either remove the file or use dput's option:
>
>-f
>--force
>   Disable the check for a unique upload.  See VERIFICATION
> CHECKS, above, for a description of this check.
>
>
I'll give the force option a try and see if the "reupload" fixes anything.
Fingers crossed!

Thanks!

-m

missing email after upload and other problems

[Matt Zagrabelny]

Greetings,

I maintain a network diagnostic tool package: cdpr.

https://tracker.debian.org/pkg/cdpr

It has been a while since an upload. I've fixed some bugs and corrected the
makefile to allow dpkg-buildflags to set hardening options.

I've uploaded to mentors via:

$ dput mentors cdpr_2.4-3_amd64.changes
Package has already been uploaded to mentors on mentors.debian.net
Nothing more to do for cdpr_2.4-3_amd64.changes

$ cat ~/.dput.cf
[mentors]
fqdn   = mentors.debian.net
incoming   = /upload
method = https
allow_unsigned_uploads = 0
progress_indicator = 2
allowed_distributions  = .*

which I performed on Friday, 2018-06-22.

Reading the documentation on mentors.d.n I was expecting an email with a
template to be sent my way so that I could file a RFS bug against
sponsorship-requests. However I haven't received any such email. I do seem
to get general discussion on the mentors mailing list.

Furthermore, I don't see my uploaded package when I login to mentors.d.n
and click the "My packages" link:

"""
Packages uploaded by Matt Zagrabelny
No packages
"""

Any help in:

A) Sponsoring this package would be great.
B) Figuring out why I don't get an email after a dput upload to mentors.
C) Why I don't see my package via the web UI.

Would be most appreciated.

Thanks!

-m

Re: systemd service unit causing lintian init issues

[Matt Zagrabelny]

On Tue, Sep 29, 2015 at 11:20 PM, Andrey Rahmatullin <w...@debian.org> wrote:
> On Tue, Sep 29, 2015 at 03:12:18PM -0500, Matt Zagrabelny wrote:
>> A quick look at the source for dh_installinit doesn't show much about
>> the '-p', nor '--remaining' options. Can you elaborate or point to
>> further docs?
> FWIW those are common debhelper options and so found in debhelper(7).

Thanks! I was guessing that they were common options, but I checked dh(1).

-m

Re: systemd service unit causing lintian init issues

[Matt Zagrabelny]

Hi Tino,

On Tue, Sep 29, 2015 at 3:41 AM, Tino Mettler <tino.kei...@tikei.de> wrote:
> On Wed, Sep 23, 2015 at 16:36:42 -0500, Matt Zagrabelny wrote:
>> Greetings,
>>
>> I'm packaging up a firewall script that ships with a systemd service
>> unit file. lintian is complaining about an init script:
>>
>> % lintian fw-skel_0.06-1_all.deb
>> W: fw-skel: init.d-script-not-marked-as-conffile etc/init.d/fw-skel
>> E: fw-skel: init.d-script-not-included-in-package etc/init.d/fw-skel
>
> Hi,
>
> I had a similar issue in the past. How does your debian/rules file look
> like? I'll try to remember what I did wrong.

I had a minimalistic rules file:

#!/usr/bin/make -f

%:
dh $@

After sending out the initial email to d-mentors, I changed it to:

#!/usr/bin/make -f

%:
dh $@ --with systemd

override_dh_installinit:
dh_installinit --noscripts

With a Build-Depends on dh-systemd. Those tweaks seemed to fix it. I
also submitted a wishlist documentation bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800043

Thanks!

-m

Re: systemd service unit causing lintian init issues

[Matt Zagrabelny]

Hi Niels,

On Tue, Sep 29, 2015 at 2:44 PM, Niels Thykier  wrote:
 [...]
>>
>> With a Build-Depends on dh-systemd. Those tweaks seemed to fix it. I
>> also submitted a wishlist documentation bug:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800043
>>
>> Thanks!
>>
>> -m
>>
>
> Use:
>
> override_dh_installinit:
> dh_installinit -p --noscripts
> dh_installinit --remaining

A quick look at the source for dh_installinit doesn't show much about
the '-p', nor '--remaining' options. Can you elaborate or point to
further docs?

Thanks!

-m

systemd service unit causing lintian init issues

[Matt Zagrabelny]

Greetings,

I'm packaging up a firewall script that ships with a systemd service
unit file. lintian is complaining about an init script:

% lintian fw-skel_0.06-1_all.deb
W: fw-skel: init.d-script-not-marked-as-conffile etc/init.d/fw-skel
E: fw-skel: init.d-script-not-included-in-package etc/init.d/fw-skel
%

There is, of course, no init script:

% dpkg-deb -c fw-skel_0.06-1_all.deb  | grep init
%

The postinst and prerm both reference an absent init script:

% dpkg-deb -e fw-skel_0.06-1_all.deb
% grep init DEBIAN/*
DEBIAN/postinst:# Automatically added by dh_installinit
DEBIAN/postinst:if [ -x "/etc/init.d/fw-skel" ]; then
DEBIAN/postrm:# Automatically added by dh_installinit
DEBIAN/prerm:# Automatically added by dh_installinit
DEBIAN/prerm:if [ -x "/etc/init.d/fw-skel" ]; then
%

It seems that dh-systemd is working in some capacity:

% dpkg-deb -c fw-skel_0.06-1_all.deb| grep systemd
drwxr-xr-x root/root 0 2015-09-23 15:18 ./lib/systemd/
drwxr-xr-x root/root 0 2015-09-23 15:18 ./lib/systemd/system/
-rw-r--r-- root/root   200 2015-09-23 15:18
./lib/systemd/system/fw-skel.service
%

I'm building this using a sid cowbuilder + gbp, FWIW.

Any ideas for keeping SysV init out of the postinst and friends?

Thanks!

-m

Re: Question about title

[Matt Zagrabelny]

On Tue, Aug 25, 2015 at 11:23 AM, J.S.Júnior j.s.jun...@live.com wrote:
 What this  [ITP,PAPT] ?

https://wiki.debian.org/Glossary

Cheers,

-m

Re: watch file help

[Matt Zagrabelny]

On Tue, Mar 18, 2014 at 4:32 AM, Jakub Wilk jw...@debian.org wrote:
 * Matt Zagrabelny mzagr...@d.umn.edu, 2014-03-17, 17:21:

  https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/
 failed: 500 Can't connect to launchpad.net:443


 I believe this is because the ValiCert Class 2 Policy Validation Authority
 certificate, which signs the launchpad.net certificate, has been removed
 from ca-certificates: https://bugs.debian.org/741561#48

 As a temporary work-around, you can disable certificate verification by
 setting the PERL_LWP_SSL_VERIFY_HOSTNAME environment variable to 0.

Thanks for the information, Jakub!

Things look good when run from the command line:

% PERL_LWP_SSL_VERIFY_HOSTNAME=0 uscan --report --verbose
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   https://launchpad.net/ocsinventory-server/
https://launchpad.net/ocsinventory-server/stable-[\d.]+/[\d.]+/\+download/OCSNG_UNIX_SERVER-([\d.]+).tar.gz
-- Found the following matching hrefs:
 
https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-2.1.tar.gz
(2.1)
Newest version on remote site is 2.1, local version is 2.0.5
 = Newer version available from

https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-2.1.tar.gz
-- Scan finished

It is easy enough for me to put the environment variable before the
command, but I am wondering about Debian's automated tools on the
backend.
How do I configure the the source package so that the environment
variable is set for the automated tools that Debian uses?

% cat debian/watch
version=3
https://launchpad.net/ocsinventory-server/
https://launchpad.net/ocsinventory-server/stable-[\d.]+/[\d.]+/\+download/OCSNG_UNIX_SERVER-([\d.]+).tar.gz

Thanks for any help!

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAOLfK3XaH36iXt=jz16iyduo2ity4gqg4eallw71ewz5fjo...@mail.gmail.com

watch file help

[Matt Zagrabelny]

Greetings,

I am attempting to write a watch file, but am hitting some issues. I
thought I would start with a pretty simple regex to grab the static
upstream version:

% cat debian/watch
version=3
https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-(2.1).tar.gz

But I am hitting an issue:

% uscan --report --verbose
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   
https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/OCSNG_UNIX_SERVER-(2.1).tar.gz
uscan warning: In watchfile debian/watch, reading webpage
  https://launchpad.net/ocsinventory-server/stable-2.1/2.1/+download/
failed: 500 Can't connect to launchpad.net:443
-- Scan finished

Not sure if uscan can handle launchpad.net's https.

Any ideas or suggestions?

Thanks!

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caolfk3vnhzkiqu1r092warwzhumgnxebnzwbsxdsytw9bsq...@mail.gmail.com

Re: question about the packaging helpers

[Matt Zagrabelny]

Hi Roelof,

On Wed, Jan 29, 2014 at 12:48 PM, Roelof Wobben rwob...@hotmail.com wrote:

 Now I wonder where detailed information can be found about the packaging
 helpers
 dh and dh7  ?

http://joeyh.name/blog/entry/cdbs_killer___40__design_phase__41__/

http://joeyh.name/talks/debhelper/debhelper-slides.pdf

and some interesting graphs:

http://www.lucas-nussbaum.net/blog/?p=751

HTH,

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3v10tcgwjj9facb8vdfzws_yvsczz3nlgtgujf8bf3...@mail.gmail.com

Re: New to this process, looking for some guidance.

[Matt Zagrabelny]

Hi Dominique,

Welcome.

If you search the archives of debian-mentors, you'll see this question
gets asked every so often and is usually answered with a nice list of
things to read and places to start. So I'd suggest performing a
search.

For a quick hit, Google for WNPP Debian.

Cheers,

-mz

On Mon, Jul 8, 2013 at 10:43 AM, Dominique Ingoglia gogli...@gmail.com wrote:
 Greetings,
I am new to the Debian community but have been using Debian for a while
 now.  I am hoping to get involved but would like to start out very simple.
 I have read through a good deal of information on the website and would like
 to try maintaining a simple package.  Is there someone that might be able to
 get me somewhat on my feet?

 Best


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOLfK3Uveqq-aQg+=wxbm0tamecwyf3-eb7a9lgkopuz4m7...@mail.gmail.com

Bug#707595: RFS: xnoise/0.2.17-1

[Matt Zagrabelny]

lightweight is spelled incorrectly in the descriptions.

On Thu, May 9, 2013 at 11:21 AM, Dominique Lasserre
lasserr...@gmail.com wrote:
 Package: sponsorship-requests
 Severity: wishlist


 Dear mentors,

 I am looking for a sponsor for the package xnoise a lightweight and
 fast GTK+ media player.

  * Package name: xnoise
Version : 0.2.17-1
Upstream Author : Jörn Magens
  * URL : https://bitbucket.org/shuerhaaken/xnoise
  * License : GPL-2+
Section : sound

 It builds those binary packages:

   libxnoise0 - Pretty and leightweight media player for Gtk+ (shared
   library)
   xnoise - Pretty and leightweight media player for Gtk+
   xnoise-dev - Pretty and leightweight media player for Gtk+
  (development)
   xnoise-plugins - Pretty and leightweight media player for Gtk+
  (plugins)


 To access further information about this package, please visit the
 following URL:

   http://mentors.debian.net/package/xnoise


 Alternatively, one can download the package with dget using this command:

 dget -x
 http://mentors.debian.net/debian/pool/main/x/xnoise/xnoise_0.2.17-1.dsc


 The ITP bug can be found here:
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632932


 The libtaginfo library [1] is required so a sponsor should look at both
 packages (see the blocked by bug).
 Currently there are several patches to make this package lintian clean
 and fix the hardening build. All of those patches are already pushed
 upstream and can be dropped with the next xnoise release.


 Thank you for your time and help!


 Regards,
 Dominique Lasserre


 [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707015


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3uxg7lup__xsxhhh-jswpoql479cyrddbrdpbfjcwk...@mail.gmail.com

Bug#707163: RFS: nfsen/1.3.6p1-1

[Matt Zagrabelny]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package nfsen

* Package name: nfsen
  Version : 1.3.6p1-1
  Upstream Author : ph...@sourceforge.net
* URL : http://nfsen.sourceforge.net/
* License : BSD-3-clause
  Section : net

  It builds those binary packages:

nfsen - Netflow Sensor is a graphical web-based front-end for the nfdump 
netflow tools

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/nfsen


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/nfsen/nfsen_1.3.6p1-1.dsc

  Regards,
   Matt Zagrabelny
-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130507202637.9568.3213.report...@achilles.d.umn.edu

Re: tool to create .deb for proprietary software?

[Matt Zagrabelny]

Hi Arno,

Comments inline.

On Thu, Aug 23, 2012 at 4:24 PM, Arno Töll a...@debian.org wrote:
 Hi,

 On 23.08.2012 22:46, Matt Zagrabelny wrote:
 I know I could use ar and tar to get things done, but wasn't sure
 if there was a more elegant approach.

 Depending on your own ambition there are several approaches. The easiest
 and simplest way is to use dpkg-deb -b which does right what you asked
 for.

Hmmm. That looks slick. ;)

 A slightly more advanced way would be to use tools like
 checkinstall(1) which require some Makefile which installs files to the
 file system.

 The cleanest and most formidable solution is to build a regular Debian
 package like we do for Debian archives proper. The New Maintainers'
 Guide [1] has instructions to get started. In your case you can follow
 the usual instructions, just skip the build process (dh_auto_configure,
 dh_auto_build), as your stuff is shipped in binary form already.

Unfortunately I don't have the source code. Just an install .sh that
has a binary blob in the middle of it. I'm not sure if it would be
worth make a regular Debian package for such an infuriating package.

Thanks for the advice, though.

Cheers,

-mz


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3x6wfzvfjospagdtfi1t-v5arrb9aeuqmyxdcnnjfm...@mail.gmail.com

Re: tool to create .deb for proprietary software?

[Matt Zagrabelny]

On Thu, Aug 23, 2012 at 4:46 PM, Andrey Rahmatullin w...@wrar.name wrote:
 On Thu, Aug 23, 2012 at 03:46:08PM -0500, Matt Zagrabelny wrote:
 Is there a tool to create a .deb from a directory of files? I am
 thinking of a Mathematica install I just had to perform and I'd rather
 put a .deb in our local repo and have clients pull it rather than
 manually installing this application on a bunch of computers.
 Please check first that the installer only copies files, not does some
 other things (calling some tools to modify some global configuration for
 example). Otherwise you will need some manual work anyway.

Good point Andrey. Will do.

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3x2h-g_svyayyh-0ca8jjozh8acappdcid04mdby55...@mail.gmail.com

Re: packaging help

[Matt Zagrabelny]

Check /etc/services.

-mz

On Thu, May 3, 2012 at 3:22 PM, Whit Armstrong armstrong.w...@gmail.com wrote:
 This is going really well.  Thanks to all those who have shared advice.

 How does one go about choosing ports for an application?

 Obviously there are well known ports, but is there any doc in debian
 that shows what ports have been 'reserved' by other applications?

 Thanks,
 Whit



 On Tue, Apr 24, 2012 at 12:15 PM, Gergely Nagy alger...@balabit.hu wrote:
 Whit Armstrong armstrong.w...@gmail.com writes:

 I assume it has a main process, which when stopped, would result in the
 workers being killed too. If that is so, I do not think you need to
 store the pids of the workers anywhere.

 Perhaps I'm confusing terminology here.  The main deamon does not
 spawn the workers.  It and the workers are started by the init.d
 script.  The workers and the main daemon should be started and stopped
 together.

 In that case, it seems like I should store the pid's... so I can kill
 them upon stop.

 Have I understood correctly?

 Correct.

 As a suggestion, I'd store the pidfiles under /run/your-program-name/,
 under names like worker:0.pid, and main.pid or somesuch.

 start-stop-daemon can be of great help here, but unfortunately, I don't
 recall any package off the top of my head that would serve as a good
 example, even though I know I've met one or two.. :(

 --
 |8]


 --
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/87aa21umvh.fsf@algernon.balabit



 --
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/camipg43qrd0hfzoyld8yto_zelvhqx2+-htrolx5o9r_...@mail.gmail.com



--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3vsh1ma96jkebnbwesra2ft3lyzymfxswqbhlw2h6w...@mail.gmail.com

Re: packaging help

[Matt Zagrabelny]

On Tue, Apr 24, 2012 at 8:16 AM, Whit Armstrong
armstrong.w...@gmail.com wrote:
 Thanks, Daniel.

 I would be looking for 6-64999, assuming my package eventually
 made it into debian, I suppose it would need to have a 'globally
 allocated' uid.  The idea is simply not to give users executing an R
 script on the machine root access.

 Regarding, reSIProcate, it's cdbs based?  Would the postinst script be
 the same format if I use dh?  Based on Lucas Nussbaum's tutorial
 (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf)
 I thought that dh would be the way to go for new packages.

I've used the postinst script from the puppet package for creating a
user. Here is my version of it:

---{start}---
#!/bin/sh

set -e

if [ $1 = configure ]; then

  # Create the mailregx user
  if ! getent passwd mailregx  /dev/null; then
adduser --quiet --system --group --home /var/run/milter-regex  \
  --no-create-home \
  --gecos milter-regex daemon user \
  mailregx
  fi

  # Create the mailregx group, if it is missing, and set the
  # primary group of the mailregx user to this group.
  if ! getent group mailregx  /dev/null; then
  addgroup --quiet --system mailregx
  usermod -g mailregx mailregx
  fi
fi

#DEBHELPER#
---{end}---

The #DEBHELPER# chunk is a callback or an include. It allows dh to
insert code into the script.

After my package is built, the postinst looks like:

---{start}---
#!/bin/sh

set -e

if [ $1 = configure ]; then

  # Create the mailregx user
  if ! getent passwd mailregx  /dev/null; then
adduser --quiet --system --group --home /var/run/milter-regex  \
  --no-create-home \
  --gecos milter-regex daemon user \
  mailregx
  fi

  # Create the mailregx group, if it is missing, and set the
  # primary group of the mailregx user to this group.
  if ! getent group mailregx  /dev/null; then
  addgroup --quiet --system mailregx
  usermod -g mailregx mailregx
  fi
fi

# Automatically added by dh_installinit
if [ -x /etc/init.d/milter-regex ]; then
update-rc.d milter-regex defaults /dev/null
invoke-rc.d milter-regex start || exit $?
fi
# End automatically added section
---{end}---

You can see the things that dh can put into the various post/pre
scripts in /usr/share/debhelper/autoscripts.

HTH,

-mz


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3u_atyqp7wztfw3yjv28bx-q4udzwfjk1mo-9htj5o...@mail.gmail.com

Re: packaging help

[Matt Zagrabelny]

On Tue, Apr 24, 2012 at 9:20 AM, Whit Armstrong
armstrong.w...@gmail.com wrote:
 Matt, Ansgar, and Gergely,

 Thanks for the tips.

 Can you also help with some advice on the init.d script?

Perhaps.

 The init.d script for deathstar launches a daemon which listens for
 jobs, and one worker per core.

This sounds a little like an apache that forks worker processes.
Perhaps check apache's init script for ideas.

 Can I use the same pid file for all of those processes?

Most Debian init scripts use start-stop-daemon (s-s-d) for controlling
the daemon. How s-s-d interacts with the daemon depends greatly on how
the daemon is written. Start with /etc/init.d/skeleton and tweak as
needed.

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3xczkn7mypjjxc815rvq1-xmr6m1qae-pdgebhp2t_...@mail.gmail.com

Re: Bug#659047: RFS: rpg - Readable Password Generator

[Matt Zagrabelny]

Perhaps taking d-mentors@l.d.o off future replies could be done.

Thanks!

-mz

On Tue, Apr 17, 2012 at 3:17 PM, Timo Juhani Lindfors
timo.lindf...@iki.fi wrote:
 Vladimir Stavrinov vstavri...@gmail.com writes:
 In some degree it is compensated by the fact, that double letters are
 excluded as well as other combinations. This forces to to call $RANDOM
 again and again before pick up a symbol.

 Calling $RANDOM again and again does not help at all. If you run

 for i in $(seq 20); do
    echo $RANDOM
 done

 and tell me the first 10 numbers I can tell you what the rest of the
 numbers are going to be.


 --
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/84obqqi04w@sauna.l.org



--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3xfd2qub1b3t_62r2_obtqijo3dyu7kgt2lcbkmc60...@mail.gmail.com

alternate make file for dh tiny rules

[Matt Zagrabelny]

Greetings,

I am packaging up milter-regex. The upstream source has three makefiles:

Makefile
Makefile.linux
Makefile.solaris

The file, Makefile, is for building in a BSD environment. If I specify

make -f Makefile.linux

things build nicely. Is there an easy way to tell dh that it should
use Makefile.linux instead of Makefile?

Or do I need to perform override_dh_* for all the targets that need to be used?

Thanks for the help!

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3v+2h0euookuza6psxrurj77xv_m2qgqu+knl37wgh...@mail.gmail.com

Re: alternate make file for dh tiny rules

[Matt Zagrabelny]

On Wed, Apr 4, 2012 at 9:49 AM, Matt Zagrabelny mzagr...@d.umn.edu wrote:
 Greetings,

 I am packaging up milter-regex. The upstream source has three makefiles:

 Makefile
 Makefile.linux
 Makefile.solaris

 The file, Makefile, is for building in a BSD environment. If I specify

 make -f Makefile.linux

Hmmm.

I tried the following:

---{debian/rules}---
#!/usr/bin/make -f

export MAKE:= make -f Makefile.linux

%:
dh $@
---{debian/rules}---

And get the following error:

dh build
   dh_testdir
   dh_auto_configure
   dh_auto_build
Can't exec make -f Makefile.linux: No such file or directory at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 215.
dh_auto_build: make -f Makefile.linux -j1 failed to to execute: No
such file or directory
make: *** [build] Error 2


Perhaps I don't understand the MAKE environment variable.

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3xauih15tgpxsbcf+o7rtoaumu75+mtrivibmsud8r...@mail.gmail.com

Re: alternate make file for dh tiny rules

[Matt Zagrabelny]

On Wed, Apr 4, 2012 at 3:47 PM, Gergely Nagy
alger...@madhouse-project.org wrote:
 Matt Zagrabelny mzagr...@d.umn.edu writes:

 On Wed, Apr 4, 2012 at 9:49 AM, Matt Zagrabelny mzagr...@d.umn.edu wrote:
 Greetings,

 I am packaging up milter-regex. The upstream source has three makefiles:

 Makefile
 Makefile.linux
 Makefile.solaris

 The file, Makefile, is for building in a BSD environment. If I specify

 make -f Makefile.linux

 Hmmm.

 I tried the following:

 I suggest reading man dh, in particular, it's EXAMPLES section, where
 this very question has already been answered.

Thanks for the hint, Gergely. Unfortunately the man page, in
particular the EXAMPLES section, does not address my *initial*
question (AFAIK):

---{original question}---
Is there an easy way to tell dh that it should
use Makefile.linux instead of Makefile?

Or do I need to perform override_dh_* for all the targets that need to be used?
---{end}---

And really at this point my original question is making less and less
sense as I think about it.

I am familiar with the override syntax of dh, if that is what you were
referring to when you mentioned the question I asked about being
answered in the dh man page.

I am using the dh_override_* mechanisms now.

 Perhaps I don't understand the MAKE environment variable.

 I'm afraid you don't. The info documentation of make talks about this
 variable in section 5.7.1 How the `MAKE' Variable Works.

Okay. Thanks for the info.

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3xdhzbzo36mtwbgybpkbkfhfpbcooqybolmijajk9p...@mail.gmail.com

Re: RFS: ipset

[Matt Zagrabelny]

On Thu, Jan 19, 2012 at 10:08 AM, Henrique de Moraes Holschuh
h...@debian.org wrote:
 On Thu, 19 Jan 2012, Dmitry Smirnov wrote:
   I reckon you're aware that your package conflicts with
   xtables-addons-common?
 
  At this time, my ipset binary still conflicts as the
  xtables-addons-common also provides the binary in the same path.

 My concern is that overlapping is a big source of problems.
 Imagine one have ipset installed - he/she won't be able to use modules
 provided by xtables-addons without uninstalling ipset first, etc.

 ipset is distributed separately upstream, it has its own life upstream
 (and git tree, etc), and all the functionality it requires is already
 upstream (kernel).  Related functionality (iptables) is also upstream.

 I'd actually ask why should ipset be packaged together with the rest of
 the stuff in xtables-addons, which is composed mostly of stuff that did
 not achieve upstream (as in kernel/iptables) inclusion yet for whatever
 reason?

  IMO, if the next release (1.41) of xtables-addons will not build
  ipset, so, ipset package should set the Conflicts to only for
  xtables-addons-common (= 1.40) then no conflicts any more.

 This may work if we agree not to build ipset in the next xtables-addons
 release and sponsor your package at the same time.

 ...

  Or setup the alternatives which users could select by him/her self.

 I don't like this idea because it is not an alternative but the very same
 thing provided by two different packages. This should not be. :)

 Indeed.  alternatives are not for this kind of use.

  Or ipset source package should build only libipset{2,-dev} and leave
  the ipset utility in xtables-addons as before.

 That's a Bad Idea[tm].  Very bad, in fact.

 I hope you'll excuse me if I stay away from suggestions for some time.
 This discussion needs expertise of someone more experienced than me - a
 someone familiar with resolution of conflicts between packages.
 We need comments from DDs.

 Here is one DD commenting, with his I do use this stuff at work hat on,
 and 10 years experience both as a Debian developer and sysadmin:

 IMO it should be shipped separately, it has a separate life upstream and
 it has been mainlined in the kernel and iptables side so it is now an
 standard feature of an up-to-date Linux-based system.

 Personally I think this decision requires me to thoroughly review your 
 package
 and prepare new xtables-addons. I'm overwhelmed with work for next several
 weeks so I hardly will be able to do so soon.

 I feel we could well wait a few weeks to get this done properly.

 Besides, I think you need to demonstrate the benefits of having separate
 package for ipset. I'm not sure how/why this is better (if it is) or if it's
 worth troubles to do for the marginal benefit, if any.

 To me, a separate ipset package does have advantages:

 1. Ease of backporting.

 2. No need to install stuff not yet ready/accepted on the kernel
   upstream/ipstables upstream to get standard stuff (ipset) to work.
   ipset is the kind of utility you install on routers and firewalls,
   where the less unused stuff, the better.

 3. Reflects the reality upstream.

 It does have an one-time drawback: the work required to remove/disable
 ipset from xtables-addons*.

 What makes you think it worth the effort?

 Well, FWIW, I do think it is worth the effort.  In fact I have a half-done
 ipset package somewhere, which apparently I won't have to finish and take
 care of now that someone else stepped up to do it :-p


Thanks for your comments Henrique, they make sense.

Also, it would be great to have this stuff ironed out for the Wheezy
freeze (perhaps coming in June.)

-Matt Zagrabelny

-- 
This space was intentionally left blank as to not advertise to you
what cellular provider nor what iDevice was used to send you an
email.


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOLfK3UR96CPEuvKfYxAuZqCYuU=vfkzhkpmfjd6ocvffjg...@mail.gmail.com

git-buildpackage and tarballs

[Matt Zagrabelny]

Hi,

For those of you using git-buildpackage (gbp), I have a question I
hope you can answer.

I've got a source tree for which I am the upstream author, it is under
version control using git.

It seems like it should be possible to use gbp to build the package
without having an actual tar ball. However, it appears that it is not.

I'm thinking of some pseudo commands such as the following:

git tag 1.0
git checkout debian
git-buildpackage --using-tag 1.0

I know that gbp does not have the 'using-tag' option, but again, is
there a reason that it cannot exist?

I'd rather not have to create a tarball just to check it in with
pristine-tar just to build the package.

Anyhow, thanks for setting me straight! :)

-mz


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOLfK3VsrXJeCCafvDBHFZ8Pr0L9dEAu1RyW2kio=2-5mvf...@mail.gmail.com

Re: ITP: i-news (2nd request) -- GTK-based highly graphically-configurable RSS Ticker - Bug#638999

[Matt Zagrabelny]

On Thu, Aug 25, 2011 at 5:05 PM, Emmanuel Thomas-Maurin
manutm...@gmail.com wrote:
 On 08/25/2011 09:58 PM, Lucas Nussbaum wrote:
 On 25/08/11 at 21:32 +0200, Emmanuel Thomas-Maurin wrote:
 Dear mentors,

 Sorry if this is a silly question. I previously mentionned the name
 choice was not definitive but must I pick *first* a fully suitable one
 in order to get a chance of getting sponsorded?

 Packages renames are possible but a bit painful, so yes, it's better to
 make sure you won't change the name before getting sponsored.

 Lucas

 Thanks. As I have to decide now, please let me know if I must change the
 package name or not? Sorry, I know this is redundant but I need a final
 answer.

Why did you choose 'i-news'? Isn't the upstream name 'newsrssticker'?

I would go with the upstream name unless there is a name clash, which
it doesn't look like there is.

FWIW, I don't believe you need to file a new ITP, you can just change
the name and close the ITP of 'i-news'.

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3wxvzob4tzgjrgruck-8fkjdz4w4isdb9uvochqn9p...@mail.gmail.com

Re: RFS: ndpmon

[Matt Zagrabelny]

Hi John,

On Thu, Aug 4, 2011 at 9:18 AM, John R. Baskwill jr...@psu.edu wrote:

 Dear mentors,
 I am looking for a sponsor for my package ndpmon,
 * Package name          : ndpmon
   Version               : 1.4.0-2

If your first attempt at getting sponsored and uploaded didn't take,
you'd keep the version of the package at 1.4.0-1.

-mz


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3ua-qnte6htf8pfnhuthv42wvepocupyivnxfosdzk...@mail.gmail.com

Re: RFS: ndpmon

[Matt Zagrabelny]

On Thu, Aug 4, 2011 at 10:08 AM, John R. Baskwill jr...@psu.edu wrote:


 On Thu, Aug 4, 2011 at 10:29 AM, Matt Zagrabelny mzagr...@d.umn.edu wrote:

 Hi John,

 On Thu, Aug 4, 2011 at 9:18 AM, John R. Baskwill jr...@psu.edu wrote:
 
  Dear mentors,
  I am looking for a sponsor for my package ndpmon,
  * Package name          : ndpmon
    Version               : 1.4.0-2

 If your first attempt at getting sponsored and uploaded didn't take,
 you'd keep the version of the package at 1.4.0-1.

 -mz


 Thanks very much for your reply.  This is my first attempt at getting
 sponsored.  The first upload was OK, but based on the reply I received
 from mentors.debian.net, I changed the clean target and uploaded a revised
 package.  Should I have kept it at 1.4.0-1 in that case?

Yep. You only bump versions when there is an upload. Thus, you'll keep
it at that same version while doing all of your (initial) packaging
until it is sponsored and uploaded.

-mz


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caolfk3xftgngqsa5y-7jzovdwtvtx7m+wwgdx1hbktrv16d...@mail.gmail.com

Re: RFS: cdpr (updated package)

[Matt Zagrabelny]

On Thu, May 12, 2011 at 4:19 AM, Sven Hoexter s...@timegate.de wrote:
 On Wed, May 11, 2011 at 10:55:59AM -0500, Matt Zagrabelny wrote:

 Hi,

 I am looking for a sponsor for the new version 2.4-1
 of my package cdpr.

 * Why are you mangling a prior changelog entry when the changes to
  debian/rules did not happen back then?

Good question. I must have eaten some bad mushrooms. I'm not even sure
when that happened, it's been a while since I looked at this package.

 * Will something break with compat level 8? If not, why not switch to
  it directly and while you're at it document it in the changelog.

Not sure about the breakage with compat level 8. This is where I saw
the reference to 7:

http://www.debian.org/doc/manuals/maint-guide/dother.en.html#compat


 * debian/copyright is a bit delicate.
  You list Lance O'Connor while all the file headers list
  MonkeyMental.com. I guess Lance O'Connor is the person behind the domain
  but IMO debian/copyright doesn't reflect the actual copyright holder
  given in the code. Seems wrong to me, I'd mention both. But I'm not sure
  how to correctly reflect this in this fancy new file format for
  debian/copyright which I don't use.
  Regarding this new file format I believe most people reference a revision
  in a subversion repository instead of the wiki page.

Okay. I'll take a look.

  A minor point is that you reference /usr/share/common-licenses/GPL
  which is not necessarily GPL2+ but still not totaly wrong if you make use
  of the '+'. Opinion may vary on that one.

lintian --pedantic complained. I pinged d-devel before and didn't get
a clear answer, IIRC.

 * Regarding the examples you install, I'd recommend to use dh_installexamples
  so they end up in the correct location.

Okay. I'll take a look.

Thanks for the review, Sven!

-matt


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=4H+Cki=HNfFuk=6=8ovg6ntg...@mail.gmail.com

Re: RFS: cdpr (updated package)

[Matt Zagrabelny]

On Thu, May 12, 2011 at 7:25 AM, Sven Hoexter s...@timegate.de wrote:

 http://www.debian.org/doc/manuals/maint-guide/dother.en.html#compat

 That will be almost ever outdated. See man 7 debhelper somewhere near
 the end about the compatiblity level and the changes.

Sure.

   A minor point is that you reference /usr/share/common-licenses/GPL
   which is not necessarily GPL2+ but still not totaly wrong if you make use
   of the '+'. Opinion may vary on that one.

 lintian --pedantic complained. I pinged d-devel before and didn't get
 a clear answer, IIRC.

 I'm not sure if there will ever be a final answer to such questions. I don't
 mind it if you use it this way.

I decided to set it to GPL-2. It gets rid of the lintian message and
is also a bit clearer.

I've made the relevant changes and re-uploaded to mentors

 - URL: http://mentors.debian.net/debian/pool/main/c/cdpr
 - Source repository: deb-src http://mentors.debian.net/debian
unstable main contrib non-free
 - dget http://mentors.debian.net/debian/pool/main/c/cdpr/cdpr_2.4-1.dsc

 and also pushed it to the git repo on alioth.

Thanks again for the review, Sven.

-matt


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinnfqv+kqd0_yxgupjdwsoe9dq...@mail.gmail.com

Re: RFS: cdpr (updated package)

[Matt Zagrabelny]

On Thu, May 12, 2011 at 11:00 AM, Sven Hoexter s...@timegate.de wrote:
 On Thu, May 12, 2011 at 10:29:43AM -0500, Matt Zagrabelny wrote:

 Hi,

 I've made the relevant changes and re-uploaded to mentors

 Uploaded to the archive.

Thanks, Sven!

-matt


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=1qzwlgz_j2ibjtqaz2+jpcxg...@mail.gmail.com

RFS: cdpr (updated package)

[Matt Zagrabelny]

Dear mentors,

I am looking for a sponsor for the new version 2.4-1
of my package cdpr.

It builds these binary packages:
cdpr   - Cisco Discovery Protocol Reporter

The package appears to be lintian clean.

The upload would fix these bugs: 527245, 566983, 570916

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/c/cdpr
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/c/cdpr/cdpr_2.4-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Matt Zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktimtd+ejeufju9iu8rugybdta0y...@mail.gmail.com

Re: Debian Packaging Tutorial

[Matt Zagrabelny]

On Thu, May 5, 2011 at 9:57 AM, Lucas Nussbaum lu...@lucas-nussbaum.net wrote:
 Hi,

 I’ve been working on a Debian packaging tutorial. It is composed of
 about 60 slides providing a throughout overview of Debian packaging.

 It now reached the point where I consider it ready for use, and I am
 looking forward to reviews and comments.
 The document is split into 4 different PDFs:
 * the tutorial itself:
  http://git.debian.org/?p=users/lucas/packaging-tutorial.git;a=blob_plain;f=packaging-tutorial.pdf;hb=refs/heads/pdf
 * a practical session about modifying the ‘grep’ package:
  http://git.debian.org/?p=users/lucas/packaging-tutorial.git;a=blob_plain;f=pract1-grep.pdf;hb=refs/heads/pdf
 * a practical session about packaging the ‘gnujump’ game from scratch:
  http://git.debian.org/?p=users/lucas/packaging-tutorial.git;a=blob_plain;f=pract2-gnujump.pdf;hb=refs/heads/pdf
 * a practical session about packaging a Java library:
  http://git.debian.org/?p=users/lucas/packaging-tutorial.git;a=blob_plain;f=pract3-java.pdf;hb=refs/heads/pdf

 And of course, it can be found on git.debian.org:
 git clone git://git.debian.org/~lucas/packaging-tutorial.git

 Comments very much welcomed!

Hey Lucas,

Thanks for providing this. I've noticed an inconsistency and have
attached a patch.

-matt zagrabelny


 - Lucas


 --
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20110505145738.ga22...@xanadu.blop.info


From 133689f78d3bb1ee9eda44c38567c9dcf1d3b502 Mon Sep 17 00:00:00 2001
From: Matt Zagrabelny mzagr...@d.umn.edu
Date: Thu, 5 May 2011 13:31:55 -0500
Subject: [PATCH] Unmatched parenthesis Remove opening parenthesis from
 Request For Help acronym expansion. This keeps the acronyms
 and their expansion consistent.

---
 packaging-tutorial.tex |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/packaging-tutorial.tex b/packaging-tutorial.tex
index daebbd4..790d2f9 100644
--- a/packaging-tutorial.tex
+++ b/packaging-tutorial.tex
@@ -910,7 +910,7 @@ Vcs-Svn: svn://svn.debian.org/pkg-perl/trunk/libwww-perl
 \item \textbf{ITA}: \textbf{I}ntent \textbf{T}o \textbf{A}dopt\\
   Someone intends to adopt the package\\
   You could propose your help!
-\item \textbf{RFH}: (\textbf{R}equest \textbf{F}or \textbf{H}elp\\
+\item \textbf{RFH}: \textbf{R}equest \textbf{F}or \textbf{H}elp\\
   The maintainer is looking for help
 \end{itemize}
 \hbr
-- 
1.7.4.4

Re: RFS: ripit (updated package, upload to unstable only)

[Matt Zagrabelny]

On Tue, Apr 26, 2011 at 8:33 AM, Sven Hoexter s...@timegate.de wrote:
 On Tue, Apr 26, 2011 at 03:49:30PM +0300, Peter Pentchev wrote:

 Hey Peter,

 -Description: Textbased audio CD ripper
 +Description: textbased audio CD ripper

 this is a rather interesting one. After a short look at various
 packages we seem to have a mixture of upper and lower cases.
 Maybe we should try to go with one variant and advice that in the
 policy (except for proper names of course).

It seems like lowercase would be the way to go. The description is not
a sentence and capitalizing the first letter makes it feel like a
sentence (when it is not one.)
Since it now feels like a sentence, you also begin to wonder where the
ending punctuation is.

my $.02

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=f1x9ejyffastswudovx6_glt...@mail.gmail.com

Re: Init scripts as conffiles

[Matt Zagrabelny]

On Tue, Feb 15, 2011 at 4:06 PM, Don Armstrong d...@debian.org wrote:
 On Tue, 15 Feb 2011, Tony Houghton wrote:
 I don't like about it is that init scripts get left behind when
 uninstalling packages.

 Configuration files are always left behind unless you purge a package.

Sure. That doesn't make it correct, optimal, or the best option, just
how things have always been done.

I understand the difference between remove and purge and the reason to
use both, but removing unmodified conf files seems like a win to me.
Keeps the clutter down.

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikhsv6rztzqjhvzw6qhw1jbydjntekfwlktv...@mail.gmail.com

Re: Init scripts as conffiles

[Matt Zagrabelny]

On Tue, Feb 15, 2011 at 4:39 PM, Joey Hess jo...@debian.org wrote:
 Matt Zagrabelny wrote:
 Sure. That doesn't make it correct, optimal, or the best option, just
 how things have always been done.

 I understand the difference between remove and purge and the reason to
 use both, but removing unmodified conf files seems like a win to me.
 Keeps the clutter down.

 You'll stop thinking this when apt decides to do an upgrade as follows:

 1. remove foo (and its conffiles)
 2. install bar
 3. install foo

 That is one of the reasons for the current behavior, and temporarily
 removing a package is how apt deals with certian dependency issues.
 Renaming a package is another similar reason for the current behavior.

1. would remove the unmodified conf file
3. would install it

Did I miss something?

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTinkogC5+FGtJk=_Oao05S=hq3ufygn9vqauu...@mail.gmail.com

Re: Package Configuration

[Matt Zagrabelny]

On Thu, Aug 19, 2010 at 8:35 AM, Chris Baines cbain...@gmail.com wrote:
 Hello Mentors,

 Sorry for the ambiguous message subject, one of the packages I am
 building creates configuration files in the users home directory.
 However when I purge the package these files do not get deleted.

 Does anyone know where I can find the relevant Debian documentation
 describing how to setup the package so that it behaves as expected? Does
 anyone know of any packages with this kind of setup so I can have an
 example to work off?

Others will correct me if I am wrong, I believe (policy states?) that
the home directory is off limits when purging packages. That is, the
files/directories created aren't config files, per se.

HTH,

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikd16ki3agqnc0tt8gctzsnvpttzvuf=dxyg...@mail.gmail.com

Re: How to Deal with files created dynamically

[Matt Zagrabelny]

On Tue, Jul 27, 2010 at 7:51 PM, Matthew Palmer mpal...@debian.org wrote:
 On Tue, Jul 27, 2010 at 03:47:48PM -0500, Matt Zagrabelny wrote:
 On Tue, Jul 27, 2010 at 3:26 PM, Chris Baines cbain...@gmail.com wrote:
  On Wed, 2010-07-28 at 05:52 +1000, Matthew Palmer wrote:
  On Tue, Jul 27, 2010 at 10:03:42AM -0500, Matt Zagrabelny wrote:
   On Tue, Jul 27, 2010 at 6:53 AM, Chris Baines cbain...@gmail.com 
   wrote:
Hello Mentors,
   
I am looking at creating packages that involve programs that create
caches while running of images or other files. But I am a bit stumped 
at
what to do with the files they create, both where they are meant to go
and with what permissions.
  
   one of these two, I would wager:
  
   /var/cache/
   /var/lib
 
  Scratch /var/lib from that list.  If the data can be recreated from 
  another
  source, then it's cache data and should *not* live in /var/lib.
 
   As for the permissions
  
   root:root 644
 
  If the files are created by root-owned processes, sure.  It kinda smells
  like this is going to be done by a user-run process, which means you won't
  be able to apply that ownership.  You will probably have to revert to
  per-user data stored in the homedir, unless you want to start stuffing
  around with suid wrappers or some such.
 
  Yes, the programs are run with user level permissions. While per user
  data would be a solution I don't want to use it just to make this
  easier. Are there any packages that deal with these problems?

 You could create a group and then do something like:

 addgroup newpackage
 mkdir /var/cache/newpackage
 chown root:newpackage /var/cache/newpackage
 chmod 775 /var/cache/newpackage

 This is only practical if the cache files are not trusted by the
 application; users can directly manipulate the files and their contents.  It
 must be possible to verify that the cache files are correct before using
 them.

 Also, if you're going to go that wild, you may as well just make the
 directory group 'users' or some equally common group.  Also, don't forget
 the g+s and umask 002 to avoid per-user permission nightmares.

 In other words: per-user caching ftw.

Matt,

I understand the 'chmod g+s dir', but in what capacity would you
implement the umask command?

-matt


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktik-a2qrxyzspyeqtrv_nvruyr05ugspdv0g9...@mail.gmail.com

Re: How to Deal with files created dynamically

[Matt Zagrabelny]

On Tue, Jul 27, 2010 at 6:53 AM, Chris Baines cbain...@gmail.com wrote:
 Hello Mentors,

 I am looking at creating packages that involve programs that create
 caches while running of images or other files. But I am a bit stumped at
 what to do with the files they create, both where they are meant to go
 and with what permissions.

one of these two, I would wager:

/var/cache/
/var/lib

As for the permissions

root:root 644

(that was just a guess)

-matt


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=grwqwblnbagady+wuup928daamhkneyjph...@mail.gmail.com

Re: How to Deal with files created dynamically

[Matt Zagrabelny]

On Tue, Jul 27, 2010 at 3:26 PM, Chris Baines cbain...@gmail.com wrote:
 On Wed, 2010-07-28 at 05:52 +1000, Matthew Palmer wrote:
 On Tue, Jul 27, 2010 at 10:03:42AM -0500, Matt Zagrabelny wrote:
  On Tue, Jul 27, 2010 at 6:53 AM, Chris Baines cbain...@gmail.com wrote:
   Hello Mentors,
  
   I am looking at creating packages that involve programs that create
   caches while running of images or other files. But I am a bit stumped at
   what to do with the files they create, both where they are meant to go
   and with what permissions.
 
  one of these two, I would wager:
 
  /var/cache/
  /var/lib

 Scratch /var/lib from that list.  If the data can be recreated from another
 source, then it's cache data and should *not* live in /var/lib.

  As for the permissions
 
  root:root 644

 If the files are created by root-owned processes, sure.  It kinda smells
 like this is going to be done by a user-run process, which means you won't
 be able to apply that ownership.  You will probably have to revert to
 per-user data stored in the homedir, unless you want to start stuffing
 around with suid wrappers or some such.

 - Matt


 Yes, the programs are run with user level permissions. While per user
 data would be a solution I don't want to use it just to make this
 easier. Are there any packages that deal with these problems?

You could create a group and then do something like:

addgroup newpackage
mkdir /var/cache/newpackage
chown root:newpackage /var/cache/newpackage
chmod 775 /var/cache/newpackage

New users who would use this package would need to be added to said group:

adduser joeuser newpackage

HTH,

-matt


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin7ned7dem2kubtorfbdtib4mrbbz0qeufmw...@mail.gmail.com

Re: RFS: tacacs+

[Matt Zagrabelny]

On Wed, 2010-02-03 at 21:54 +0100, Tourneur Henry-Nicolas wrote:

 2° Which version of lintian do you use to get those warnings and errors ? I 
 got an updated sid version of lintian but no messages :( I guess I fixed #2, 
 #3 
 and 4 but it's just based on your description of the problem (thanks for 
 that).

This is what I have been running:

lintian --pedantic package.deb
linitan --pedantic package.dsc

-- 
Matt Zagrabelny - mzagr...@d.umn.edu - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems  Services
PGP key 4096R/42A00942 2009-12-16
Fingerprint: 5814 2CCE 2383 2991 83FF  C899 07E2 BFA8 42A0 0942

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot


signature.asc
Description: This is a digitally signed message part

RFS: cdpr (updated package)

[Matt Zagrabelny]

Dear mentors,

I am looking for a sponsor for the new version 2.3-3
of my package cdpr.

It builds these binary packages:
cdpr   - Cisco Discovery Protocol Reporter

The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/c/cdpr
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/c/cdpr/cdpr_2.3-3.dsc

I would be glad if someone uploaded this package for me.

Kind regards,

-- 
Matt Zagrabelny - mzagr...@d.umn.edu - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems  Services
PGP key 4096R/42A00942 2009-12-16
Fingerprint: 5814 2CCE 2383 2991 83FF  C899 07E2 BFA8 42A0 0942

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot


signature.asc
Description: This is a digitally signed message part

RFS: cdpr - Cisco Discovery Protocol Reporter

[Matt Zagrabelny]

hello,

cdpr - Cisco Discovery Protocol Reporter

cdpr listens on specified network interfaces for Cisco Discovery
Protocol packets. It then decodes  those  packets and outputs the
information, optionally sending the information to a server for
processing.

license: GPL

please download debian package and source files from:

http://www.d.umn.edu/~mzagrabe/debian/cdpr/


thanks for your time.

-matt zagrabelny


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]