Bug#801438: RFS: node-moment/2.10.6+dfsg-1 [ITP bug #759958 ]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-moment" * Package name: node-moment Version : 2.10.6+dfsg-1 Upstream Author : Tim Wood, Iskren Chernev and Moment.js contributors * URL : https://github.com/moment/moment/ * License : Expat Section : web It builds those binary packages: libjs-moment - Work with dates in JavaScript (library) node-moment - Work with dates in JavaScript (Node.js module) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-moment Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-moment/node-moment_2.10.6+dfsg-1.dsc You can also find the package here: Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-moment.git Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-moment.git Notice that I'm not the one who filled the ITP, but the person who did explicitly allowed me to proceed (see bug thread). Thanks, Snark on #debian-js
Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator
Hi Thanks for your feedback. The point of that commit was to add the debugging flags to the compiler command line. if ! "$debug"; then -COMPFLAGS="$COMPFLAGS -DNDEBUG" +COMPFLAGS="$COMPFLAGS -DNDEBUG -O2" +else +COMPFLAGS="$COMPFLAGS -DDEBUG -g -O0" fi yes, but I fail to see why you should override CPPFLAGS anyway :) I recently changed CPPFLAGS to CXXFLAGS which I think is more appropriate (preprocessor flags vs. compiler flags). But frankly, I never fully mastered automake and friends so, not sure if it can be still improved. you can publish the tarball as always, just sign it in a tarball.gpg or whatever detached file. how upstream builds the archive is not a Debian problem :) I mean, use your favourite way, just don't change it too often to avoid debian/watch file broken Now d/watch look like this: version=3 opts=pgpsigurlmangle=s/$/.asc/ http://sf.net/eviacam/eviacam_(.+)\.orig\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) debian uupdate and uscan --debug --force-download dpkg-buildpackage -S -sa works for me I understand that a dbg package is "...useful if program crashes and you want to generate stack trace..." [1]. But not sure who might take advantage if this kind of package. I think that I need more information about this. well, consider a person giving you a bug like "the version X.Y crashes" you might want them to install the dbg package and give you a stack trace with some useful pointers inside. but automatic debug packages are coming soon (TM) in Debian, so you can just avoid it (although it is a nice learning experience) I see. Perhaps we could wait for the automatic debug packages. In the meantime, if someone reports a crash, I could try to provide a debug package. (sorry for the delay, let me know as soon as you have something on mentors, I guess this involves a new upstream minor release or a bunch of debian/patches) Me too. I have been busy lately. I've uploaded a new version (2.0.3) to mentors. Regards, Cesar
Re: unstripped-static-library
02.10.2015 22:18, Herbert Parentes Fortes Neto (hpfn) wrote: > Hi mentors, > > I maintain libgphoto2 and lintian now says > that the package has "unstripped-static-library" > (.a files). We (me and my mentor) believe that > this message can be ignored. BTW, why do you include static library to start with? Thanks, /mjt
Bug#790125: marked as done (RFS: dropbear/2015.68-1 - lightweight SSH2 server and client)
Your message dated Fri, 9 Oct 2015 20:15:00 + (UTC)
with message-id <1798440856.2333560.121700141.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#790125: RFS: dropbear/2015.68-1 - lightweight SSH2
server and client
has caused the Debian Bug report #790125,
regarding RFS: dropbear/2015.68-1 - lightweight SSH2 server and client
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
790125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "dropbear"
* Package name: dropbear
Version : 2015.67-1.1
Upstream Author : Matt Johnston
* URL : http://matt.ucc.asn.au/dropbear/
* License : MIT
Section : net
It builds those binary packages:
dropbear - transitional dummy package for dropbear-{run,initramfs}
dropbear-bin - lightweight SSH2 server and client - command line tools
dropbear-initramfs - lightweight SSH2 server and client - initramfs
integration
dropbear-run - lightweight SSH2 server and client - startup scripts
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/dropbear
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/d/dropbear/dropbear_2015.67-1.1.dsc
More information about dropbear can be obtained from
http://matt.ucc.asn.au/dropbear/ .
The maintainer told me to go ahead a proceed with the NMU [0].
Changes since the last upload:
* Non-maintainer upload.
[ Matt Johnston ]
* New upstream release. (Closes: #775222.)
[ Guilhem Moulin ]
* debian/source/format: 3.0 (quilt)
* debian/compat: 9
* debian/control: bump Standards-Version to 3.9.6 (no changes necessary).
* debian/copyright: add machine-readable file.
* Split up package in dropbear-bin (binaries), dropbear-run (init scripts)
and dropbear-initramfs (initramfs integration). 'dropbear' is now a
transitional dummy package depending on on dropbear-run and
dropbear-initramfs. (Closes: #692932.)
* Refactorize the package using dh_* tools, including dh_autoreconf.
(Closes: #689618, #777324.)
* dropbear-run:
+ Add a status option to the /etc/init.d script.
+ Pass key files with -r not -d in /etc/init.d script. (Closes: #761143.)
+ Post-installation script: Generate missing ECDSA in addition to RSA and
DSS host keys. (Closes: #776976.)
* dropbear-initramfs:
+ Don't mark /usr/share/initramfs-tools/conf-hooks.d/dropbear as a
configuration file, since it violates the Debian Policy Manual section
10.7.2. (Regression from 2014.64-1.)
+ Delete debian/initramfs/premount-devpts, since /dev/pts in mounted by
init since initramfs-tools 0.94. (Closes: #632656.)
+ Auto-generate host keys in the postinstall script, not when runing
update-initramfs. Pass the '-R' option (via $PKGOPTION_dropbear_OPTION)
for the old behavior. Also, print fingerprint and ASCII art for
generated keys (if ssh-keygen is available).
+ Revert ad2fb1c and remove warning about changing host key. Users
shouldn't be encouraged to use the same keys in the encrypted partition
and in the initramfs. The proper fix is to use an alternative port or
UserKnownHostFile.
+ Set ~root to `mktemp -d "$DESTDIR/root-XX"` to avoid collisions with
$rootmnt. (Closes: #558115.)
+ Exit gracefully if $IP is 'none' or 'off'. (Closes: #692932.)
+ Start dropbear with flag -s to explicitly disable password logins.
+ Terminate all children before killing dropbear, to avoid stalled SSH
connections. (Closes: #735203.)
+ Run configure_networking in the foreground. (Closes: #584780, #626181,
#739519.)
+ Bring down interfaces and flush network configuration before existing
the ramdisk, to avoid misconfigured network in the regular kernel.
(Closes: #715048, #720987, #720988.)
+ Add a script '/bin/unlock' to the initramfs to make remote unlocking
easier and possibly as a forced-command restrictions in authorized_keys.
Cheers,
--
Guilhem.
[0] https://lists.debian.org/debian-devel/2015/06/msg00285.html
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi,
Built&Signed&Uploaded on ftp-master/DELAYED/4.
I thought it was a safer option(due to limited time during weekends, and
soonafter I not
Bug#790125: RFS: dropbear/2015.68-1 - lightweight SSH2 server and client
Hi, On Fri, 09 Oct 2015 at 17:19:24 +, Gianfranco Costamagna wrote: > how do you feel about merging the two above Ubuntu deltas in the Debian > packaging? Thanks for pointing that out. I didn't check the Ubuntu uploads, actually. > https://launchpad.net/ubuntu/+source/dropbear/2014.65-1ubuntu1 > + debian/initramfs/premount-devpts, debian/rules: drop the script, this is > handled by initramfs-tools. Done already: + Delete debian/initramfs/premount-devpts, since /dev/pts in mounted by init since initramfs-tools 0.94. (Closes: #632656, #797939.) > + debian/initramfs/dropbear-hook: do not install dropbear in the initramfs > if there's no uncommented line in /etc/crypttab. IMHO this is no longer relevant. The hook now only belongs to the ‘dropbear-initramfs’ binary package, the sole purpose of which is to install dropbear in the initramfs. For backward compatibility it's still possible to disable the hook by setting ‘DROPBEAR=n’, but I don't think we need to make extra checks: if someone doesn't want the hook they can simply uninstall the package. (Furthermore, Ubuntu refuses to install the hook if the crypttab is nonexistant or empty regardless of the value of $DROPBEAR, which is probably a bug. A SSH server in the initrd can have uses beyond remote cryptroot unlocking.) > + debian/initramfs/premout-dropbear: fix so that the network configuration > happens before dropbear takes hold of the network card. I believe it's no longer necessary, with this changelog: + Run configure_networking in the foreground. (Closes: #584780, #626181, #739519.) > https://launchpad.net/ubuntu/+source/dropbear/2014.65-1ubuntu2 > * Enable hmac-sha2-256 and hmac-sha2-512 MAC algorithms (LP: #1409798) Upstream took care of that in the subsequent release: * New upstream release. (Closes: #631858, #775222.) Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#790125: RFS: dropbear/2015.68-1 - lightweight SSH2 server and client
Hi Guilhem, one last more thing. https://launchpad.net/ubuntu/+source/dropbear/2014.65-1ubuntu1 https://launchpad.net/ubuntu/+source/dropbear/2014.65-1ubuntu2 how do you feel about merging the two above Ubuntu deltas in the Debian packaging? I'm going to sponsor soon, it has been a few days and nobody complained yet, and I'm not sure what else to check here. cheers, G. Il Sabato 3 Ottobre 2015 21:12, Guilhem Moulin ha scritto: Hi! On Fri, 02 Oct 2015 at 15:49:18 +, Gianfranco Costamagna wrote: > no problem, just ping me whenever your package becomes ready again. So with Guillem Jover's help on #debian-dpkg I managed to solve the problem of the configuration file in dropbear 2014.65-1's /usr. (Using dpkg-maintscript-helper to move it to /etc upon upgrade.) As a consequence the source package is now lintian-clean and upgrades smoothly from Jessie :-) Moreover, piuparts is now happy \o/ (Ignoring the broken symlink warnings.) Interestingly, piuparts complains when given the .changes file; but giving the .deb by order of dependence makes it happy (I guess one ought to file a bug against dpkg or piuparts): sudo piuparts --schroot=unstable-amd64-sbuild … \ dropbear_2015.68-1_all.deb \ dropbear-bin_2015.68-1_amd64.deb \ dropbear-run_2015.68-1_amd64.deb \ dropbear-initramfs_2015.68-1_amd64.deb I therefore changed the distribution from experimental back to unstable, and uploaded a new version: dget -x http://mentors.debian.net/debian/pool/main/d/dropbear/dropbear_2015.68-1.dsc Cheers, -- Guilhem.
Bug#801295: marked as done (RFS: tightvnc/1.3.9-6.6 [NMU])
Your message dated Fri, 9 Oct 2015 17:13:55 + (UTC) with message-id <1261839112.2265309.110835251.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#801295: RFS: tightvnc/1.3.9-6.6 has caused the Debian Bug report #801295, regarding RFS: tightvnc/1.3.9-6.6 [NMU] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 801295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Version: any Hi, I've prepared a debdiff adding ppc64el support to tightvnc. The patch has been tested, and is already shipping in Ubuntu. As the package is up for adoption, a Debian developer is needed to do the NMU upload. For the history and the debdiff, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788107 - Lauri --- End Message --- --- Begin Message --- Package is on deferred/1 right now, it will be uploaded in 17 hours if nobody cancels it. thanks for your contribution to Debian! cheers, G. Il Giovedì 8 Ottobre 2015 13:39, Lauri Kasanen ha scritto: Control: retitle -1 RFS: tightvnc/1.3.9-6.6 [NMU]--- End Message ---
