May I suggest that we promote the rcs dependency to a "Recommends" and
forward the rest (menus grayed out, informative message, etc)
upstream?
--
=Do-
N.AND
2013/11/21 Per Olofsson :
> On Thu, Nov 21, 2013 at 15:41 +0100, Martin Haase wrote:
>> Package: lyx
>> Version: 2.0.6-1+b1
>> Severity: nor
Hi Aide,
I'm working on a version that (hopefully) fixes this bug.
Could you please try the package from mentors:
http://mentors.debian.net/package/acetoneiso
and let me know if it fixes your problem?
Also, thanks for the .desktop suggestion. This change should also be
included in the aforementio
.
Kindest regards,
Nick
--
=Do-
N.AND
2013/6/23 Martin Pitt :
> Hello Nick,
>
> Nick Andrik [2013-05-22 23:09 +0200]:
>> I was refering to the ability to use the unrar backend (already
>> packaged in a separate package), not to build the one shipped with
>> calibre.
>&g
Package: qa.debian.org
Severity: normal
The changelog entry for ffmpeg package [1] is pointing to the wrong location
[2] instead of the correct one [3]
[1] http://packages.qa.debian.org/f/ffmpeg.html
[2] http://ftp-
master.metadata.debian.org/changelogs/updates/main/f/ffmpeg/oldstable_changelog
[
I was refering to the ability to use the unrar backend (already
pacaged in a separate package), not to build the one shipped with
calibre.
In order to do this, I think a "Suggests:" libunrar0 would suffice, no?
--
=Do-
N.AND
2013/5/11 Martin Pitt :
> Nick Andrik [2013-05-02 18:22
BTW, there is also a launchpad bug about this (in the case you would
like to include it in the changelog entry):
https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/390263
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
I cannot seem to find any mention of libunrar in the control file of
0.9.27+dfsg-1
In any case, it should be Suggests: libunrar0, since this is the name
of the required package:
http://packages.debian.org/sid/libunrar0
Best regards,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-d
Hi Adrian,
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 )
which also includes major UI changes.
Could you please check your issue against this version to see if it is
still relevant?
Thanks a lot,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@
Hi Jan,
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 ).
Since your bug was filed 9 years ago and you mention that it is also a
kernel issue, could you please check if it is still relevant against
the latest kismet version?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE,
Is this bug still relevant for 2013.03.R1b-1 ?
I cannot seem to find the flags column. francesco, could you please verify it?
Thanks,
Nikos
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 )
and /etc/kismet_ui.conf seems not to be used any more.
The configuration is taken by ~/.kismet/kismet_ui.conf which has new
configuration options and written automatically by the preferences in
the UI.
Documentation mentions "-
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 ).
Could you please check your issue against this version to see if it is
still there?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 )
and seems that this bug is not an issue any more.
Could you please check your issue against this version to see if it is
still there?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.deb
Hi Marc,
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 ).
Could you please check your issue against this version to see if it is
still there?
In my configuration I get less information printed out when I run with
-s (e.g. INFO messages are not shown)
Thanks,
Nick
--
=Do-
Hi Celejar,
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 ).
Could you please check your issue against this version in order to see
if it is still there?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "
Kismet has been updated to the most upstream version ( 2013.03.R1b-1 ).
Could you please check your issue against this version to see if it is
still there?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
It seems that kismet has updated their gpsd support around beginning of 2010.
Could you please check if the latest ( 2013.03.R1b-1 ) package fixes
this problem?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
> Which versions of the package FTBFS on s390x? There are setools binary
> packages in testing on that architecture, so it obviously built at some
> point; what changed?
I think this is what you are looking for:
https://buildd.debian.org/status/logs.php?pkg=setools&arch=s390x
Not building for s390
> When I manually set the suid bit on /usr/bin/kismet_capture
> kismet works for non-root users too.
Which should be the default behaviour if setcap is not present
> Maybe a required capability is missing?
I will have to check that with upstream and come back with an answer.
The capabilities spe
I already have a packaged version in my PPA:
https://launchpad.net/~andrikos/+archive/ppa/+sourcepub/3022134/+listing-archive-extra
If you want I can build a patch against the tree (we just need to
update a patch and a small thing in debian/rules)
--
=Do-
N.AND
2013/3/17 Per Olofsson :
> 2013-0
I have prepared a new package of lyx with the most recent upstream
which can be found in my PPA in launchpad:
https://launchpad.net/~andrikos/+archive/ppa/+packages
Apart from that, the package needs a bit of cleanup to get rid of all
the filed bugs.
I don't think I will have the time to fully ado
-22 at 00:54:11 +0100, Nick Andrik wrote:
>> 2013/1/22 Martin Meredith :
>> > Why the confersion to cdbs?
>> >
>> > Ca I gets a debdiff?
>>
>> I switched to cdbs because I think (on my experience) it produces way
>> much simpler debian/rules, es
Yes, your new version seems to solve the problem
Thanks!
--
=Do-
N.AND
2013/2/28 Jari Aalto :
> 2013-02-28 17:02 Simon Ruderich :
> | On Thu, Feb 28, 2013 at 12:52:40PM +0100, Nick Andrik wrote:
> |
> | > NONVERBOSE BUILD:C++ Library: stdc++
> | > [1] http
Package: blhc
Version: 0.03+20121004+gite3d197b-1
Severity: normal
Dear Maintainer,
I get a false positive of compiler flags hidden in my logs [1]:
NONVERBOSE BUILD:C++ Library: stdc++
[1] https://buildd.debian.org/~brlink/packages/k/kismet.html
Could you please check it?
Best rega
Package: blhc
Version: 0.03+20121004+gite3d197b-1
Severity: normal
Dear Maintainer,
I get a false positive of compiler flags hidden in my logs [1]:
NONVERBOSE BUILD:C++ Library: stdc++
[1] https://buildd.debian.org/~brlink/packages/k/kismet.html
Could you please check it?
Best rega
Now that I check it again, I see that I get this error when the
address can be resolved, but the machine is not responding (it seems I
cannot ping google from my workstation).
Then, I guess this is a problem on the actual error mesage which
should be something like:
"www.google.com is not respondin
Package: gnome-nettool
Version: 3.2.0-1
Severity: normal
Dear Maintainer,
When attempting to use Ping, having installed iputils-ping, I got the
following message:
An error occurred when try to run 'Ping'
/bin/ping ping -b -c 5 -n www.google.com
It seems that the tool adds an extra word (ping)
Ah ok, didn't check it that much.
Thanks!
--
=Do-
N.AND
2013/2/1 Timo Jyrinki :
> Note that it's already prepared [1] and in NEW queue [2]. There's also
> the associated php5-midgard2 [3] that builds against the new package
> name. So I believe - unless it's not enough to address the rc bug - th
Package: dpkg-dev
Version: 1.16.7ubuntu6
Severity: wishlist
I am packaging a library implemented in C++ .
During my effort to generate sane symbol files for it, I saw that C++ symbols
differ among architectures.
One way to avoid having different symbols files for each architecture is to use
the d
It seems that version 3.3.6 of the package introduced new symbols for
the libraries, but the .symbols files for arm and m68k architectures
were not updated.
The files that are obsolete are (* denotes the architecture):
libapol4.symbols.*
libqpol1.symbols.*
libseaudit4.symbols.*
Also, I notice tha
If nobody is working on this bug, I'm offering to prepare an NMU
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I have prepared an NMU closing 3 bugs included this one.
The updated package can be found on mentors [1]
Martin, I know the package is in lowNMU [2] category, but the the
changes are not trivial (general cleanup, conversion to CDBS, closing
3 bugs).
So, according to the instuctions in the NMU pro
I have prepared an NMU closing 3 bugs included this one.
The updated package can be found on mentors [1]
Martin, I know the package is in lowNMU [2] category, but the the
changes are not trivial (general cleanup, conversion to CDBS, closing
3 bugs).
So, according to the instuctions in the NMU pro
in debian/rules
* Updated debian/copyright in format 1.0
* Bumped standards version to 3.9.4
Regards,
Nick Andrik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Daniel,
I have already prepared an updated version for acetoneiso (solving
also this bug).
I have uploaded it on mentors and I'm waiting for someone to sponsor it:
https://mentors.debian.net/package/acetoneiso
Thanks,
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.or
package kismet
reopen 670176
thanks
The version uploaded to NEW was the wrong one (targetting unstable).
The current version uploaded to NEW targets experimental and is the
same as the one in mentors.
I reopen the bug so that it gets closed appropriately from the
changelog entry when the package
>> I think that the ubuntu situation is orthogonal to the debian one.
>> Since ubuntu takes its packages from unstable, whether or not we
>> remove the package from stable is irrelevant.
>
> The bugs for the kismet package in Ubuntu are irrelevant IFF the package in
> Wheezy doesn't have these SIGS
>> If there are any bugs reported on functionality (which I doubt) then
>> it makes no sense trying to fix the 2008 version.
>
> Ubuntu has several SIGSEGV crashes reported on kismet 2008-05-R1-4.3:
>https://launchpad.net/ubuntu/+source/kismet/+bugs
I think that the ubuntu situation is orthogo
> If you mean "feature requests", then they are not appropriate for
> packages shipped in a stable release, so indeed it does not make
> sense, and then I gather your answer was a "yes".
Then, yes it is :)
> If you mean anything else, please clarify :)
>> If we need to fix anything then I will h
2012/12/12 intrigeri :
> Hi,
>
> Nick Andrik wrote (12 Dec 2012 14:32:35 GMT) :
>> I don't have strong feelings in any case, I don't expect someone to be
>> using this version of the package nowadays.
>> On the other hand, I don't also see the clear bene
>> No. A package which has been removed will always go back through NEW if
>> it is reintroduced. After going through the NEW queue, it can go into
>> either experimental or unstable.
>
> Since the discussion has drifted to full removal from the archive,
> I'd like to point out that a removal from
First of all I also CC the DD that follows my work on packaging the
new version, since I am not an expert on all debian procedures yet.
About removing kismet or not, I don't know what are the arguments for
and against.
I need to know the exact implications in order to give an informed answer.
If
The problem is that I ran dput yesterday but the package dis not
appear in my packages on mentor (I didn't even receive an email).
I guess it got stuck somewhere in the incoming queue.
I read somewhere that it takes 6 hours to get unstuck, but still no
email from yesterdays' upload and I get "Uploa
Is anyone taking care of this?
If noone else is working on this I could try to prepare a package
Best regards,
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello Bart,
Thanks for the review.
I have included a verbatim copy of the MPL-1.1 license (up to the
first half of Exhibit A since the other information is covered in the
debian/copyright file anyway ).
You can find the updated version of the package in the mentors site:
http://mentors.debian.net
pell-el-gr (0.8-2) unstable; urgency=low
* Acknowledge NMU: 0.8-1.1 (Thanks to Agustin Martin Domingo)
* debian/patches/include_changelog :
- Include upstream changelog
* debian/copyright :
- Converted to Version 1.0
* debian/control :
- Bumped standards version to 3.9.4
-- N
I have prepared an update version of the package including the new
upstream version and fixing another bug
It can be found on mentors:
https://mentors.debian.net/package/unrar-nonfree
Martin, could you please take a look
Best regards,
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@l
Hello there,
Do you still need someone to adopt the lyx package?
I could try and help for some time and see if I could possibly adopt
it eventually since it is a package that I use quite much.
If this is OK, I could start by looking on the (quite many) bugs filed
against the package to prepare an
Actually my 4.1.4 package would crash calibre when trying to extract
CBR files but the updated 4.2.4 (most recent upstream) seems to work
just fine.
You can always find both versions on mentors:
http://mentors.debian.net/package/unrar-nonfree
Nick
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
I made a first attempt to also build the shared library of the package.
You can find an updated source package on the mentors site:
https://mentors.debian.net/package/unrar-nonfree
The changes needed is an updated debian/rules file and a patch in
makefile.unix from upstream.
I didn't split the pa
Dear mentors,
I have updated the current (5 years old) kismet version to the most
recent upstream and I also intend to adopt the package.
The new package has updated description (reviewed by the debian
english team) and also closes around 15 bugs.
The new version of the package can be found here:
reopen 670176
Hello Arno,
I just came back after a long period that I wasn't able to take a look
on the package.
I'm trying to address all the things you said.
2012/5/14 Arno Töll :
> Hi Nick,
>
> this is a shallow review of your package. Unfortunately I am lacking
> experience with CDBS package
copyright
+ Extended source copyright
* Package maintenance
- Bumped standars version to 3.9.2 in control
- Added project homepage in control file
Regards,
Nick Andrik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
Package: wnpp
Severity: normal
kismet's current maintainer Francois Gurin seems
to be MIA sincce 2008.
May I propose to orphan the package?
I would also be willing to adopt the package and I have already
prepared an update:
http://mentors.debian.net/package/kismet
What is the official procedure
Package: wnpp
Severity: normal
kismet's current maintainer Francois Gurin seems to be MIA
sincce 2008. May I propose to orphan the package?
I would be also willing to adopt it, I have already prepared an update:
http://mentors.debian.net/package/kismet
What is the official procedure to follow?
+- debian/control.in
+ + Bumped Standards Version to 3.9.3
+
+ -- Nick Andrik Wed, 29 Feb 2012 16:45:16 +0100
+
libart-lgpl (2.3.21-1) unstable; urgency=low
[ Loic Minier ]
diff -Nru libart-lgpl-2.3.21/debian/compat libart-lgpl-2.3.21/debian/compat
--- libart-lgpl-2.3.21/debian/compat 2012
I already have a new package on mentors looking for sponsorship that
also fixes a couple of other issues:
http://mentors.debian.net/package/acetoneiso
I have included also your "unrelated change" :)
Could we arrange for the package to be sponsored?
Thanks,
Nick
--
=Do-
N.AND
--
To UNSUBSCR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luk,
You can find an updated version of the package which includes your patch
and also some other minor fixes on mentors.debian.net:
- - URL: http://mentors.debian.net/debian/pool/main/g/guifications
- - Source repository: deb-src http://mentors.debia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I also have some minor changes for the package, so please give me a
couple of hours to upload the updated package including your changes.
Thanks a lot for your work,
Nick
Στις 20/06/2011 07:03 μμ, ο/η Nick Andrik έγραψε:
> Dear Luk,
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Luk,
- From my side it is fine.
Should I perform a normal upload or we just go on with your NMU?
Nick
Στις 18/06/2011 05:38 μμ, ο/η Luk Claes έγραψε:
> tags 621314 + patch
> tags 621314 + pending
> thanks
>
> Dear maintainer,
>
> I've prepare
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Micheal
I have just tested acetoneiso (the same version you have) with the
debian iso you suggested and it works fine for me.
Could you please check if there is any other problem reported that could
help us debug your issue?
Thanks for your bug r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Luca,
First of all, thanks for your comment.
I will contact the upstream developers ASAP and see if they would like
to make this change themselves (which I believe they'll have no problem)
and pass the changes in the package.
Nick
O/H Luca B
Thanks Sense.
The patch has been applied and the new package is waiting in the
mentors site for a sponsored upload.
I guess in a couple of days it should be ready; then we just need a
merge in ubuntu.
Nick
2010/8/2 Sense Hofstede :
> Tags: patch
>
> Attaching a .debdiff that changes the descripti
Package: ftp.debian.org
Severity: normal
This package cannot be used in kfreebsd-* and hurd-* architectures because its
run-depndency cdrdao is not available in these architectures
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Raphael,
Since I just introduce a new option (fullsourcemangle), the new version
is backwards compatible with the old one. The old watch files still work
exactly the same if they don't have this option.
Of course we would have to update uuscan
00 +0200
@@ -6,6 +6,7 @@
# Originally written by Christoph Lameter (I believe)
# Modified by Julian Gilbey
# HTTP support added by Piotr Roszatycki
+# Full source search support by Nick Andrik
# Rewritten in Perl, Copyright 2002-2006, Julian Gilbey
#
# This program is free software; you
Package: cdrdao
Version: 1:1.2.2-18ubuntu3
Severity: normal
>From the reports of the buildd system it seems that cdrdao cannot be built in
>kfreebsd/hurd OSes, giving this message during the execution of configure:
*** for kfreebsd ***
checking for SIGCPP2... yes
checking for GTKMM2... yes
check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to adopt this package.
I am greek myself, which should help to check any issues which raise in
the actual dictionary files and I have experience in debian packaging.
I would like to update the package using the latest upstream data
(myspe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: wnpp
Severity: normal
This package has been orphaned upstream and from what I understood also
in debian, no activity from the maintainer (in CC) in more than 2 years.
I use this program in a daily basis and I have already done some work to
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that the maintainer has orphaned this package (the last
maintainer upload has been 1.5 year ago).
The version in ubuntu is 1.5.0-0ubuntu3 and has been maintained by
Sebastian Bacher(CC'ed) for the last 6 months.
Sebastian, could you adopt th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Sandro,
First of all thanks for your reply.
O/H Sandro Tosi έγραψε:
> Hello,
>
> 2010/1/24 Nick Andrik :
>> I could try to adopt this package, my only problem is that I don't use
>> it.
>
> so why you want t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: pidgin-skype
Version: 20090920+dfsg-2
Please update pidgin-skype to the latest version.
Also, may I suggest to also add a Replaces/Conflicts: skype4pidgin, for
the case people have installed the package from the original homepage?
- --
=Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Christoph,
I can prepare an updated version of this package to fix all the lintian
warnings and see if I can take a look in the 2 bugs pending. The
upstream version is still the same, so it should not be much work.
If everything goes OK, I coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there still need for help in this package?
I see that the packaged version is 1.5 while the upstream one is 1.51
(they have change their page to http://snes9x.ipherswipsite.com/ as for
the Bug #432922).
I see that the upstream program is not update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Hans,
I could try to get a look in the update of this package and if
everything goes well even adopting it. What do you think?
Regards,
Nick
- --
=Do-
N.AND
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAktbjKs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Joachim,
If there is still need for help in the package I could try to give a
hand. I don't propose an ITA but I can try to see what I can do with the
new version and if everything goes well we can consider its adoption.
What do you think?
- -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Torsten,
I could try to adopt this package, my only problem is that I don't use
it. If you are available for some guidance I would be happy to adopt it
and try to package the latest version (1.0.0).
What do you think?
- --
=Do-
N.AND
-BE
Package: pidgin-guifications
Version: 2.14-3
Severity: wishlist
Guifications team has released the new upstream version 2.16, 19 months
ago. In debian there is still the 2.14 version from 2.5 years ago.
Since this is the last guifications 2.x release (they are working now on
a rewrite for version
Package: wnpp
Severity: wishlist
Owner: Nick Andrik
I have packaged and uploaded the latest version (2.2.1) of acetoneiso on debian
mentors:
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=acetoneiso
Now I am looking for a sponsor to review the package and upload it
I made patch about this bug and submitted it in the official tracker
of the project.
The project seems to be dead though, so you could at least add it as a
patch in the debian package
All info about the patch, here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1945780&group_id=121046&a
80 matches
Mail list logo
