Bug#818113: Info received (I can have)
Actually i get it now. This is the package that supplied the client library for you. All the code is in one file called mosquito with subscribe and publish. I can see that is not available in debian stretch or on available after jessie. https://packages.debian.org/wheezy/all/python-mosquitto/ I will package up the new eclipse clients and submit it to debian. On Thu, Mar 17, 2016 at 10:24 PM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > w...@debian.org > > If you wish to submit further information on this problem, please > send it to 818...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 818113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818113 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > -- Regards Martin Naughton
Bug#818113: I can have
Hey Chris, I can have a look at this and get a package in to debian. Can you just clarify a bit more. I had a look at the python client paho library below. It contains 2 python libraries for publishing and subscribing. https://github.com/eclipse/paho.mqtt.python I could not find these python libraries in previous packages of mosquitto. I can find the c client libraries. When i had a look on the internet for paho client libraries all the tutorials use pip to install the python libraries. Any more information if you have it? What version were they removed and what version were they in last? If i have that information i can make the package and put them in the same place with the package. -- Regards Martin Naughton
Bug#782432:
Where is the upstream code you used to build the package? This website it now an ad farm. www.cronolog.org I would like to take it over since it is a handy tool. Just need some details. thanks. Regards Martin
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Colin, Today i spent the day going through 80% of the bugs in grub2. Find ones that are duplicate and ones that can be closed. I think you need a bit of help closing of bugs that have been solved. Brings down the number and help everyone focus. I have emailed pkg-grub-de...@lists.alioth.debian.org asking them to close a certain amount of bugs since they are answered. Also started investigating a few bugs. Do not know the code base yet but some of the bugs seem like common sense. Wiki might help with how the build works. MIght be able to bring the bugs down from 280 to 240 with some of the work i done today. -- Regards Martin Naughton On Sat, Dec 29, 2012 at 4:03 PM, Martin Naughton wrote: > Hello Colin, > Been looking at the grub2 for debian aswell. Is the help > required with grub 1 or grub 2? i thought grub 1 was being dropped? > > http://packages.qa.debian.org/g/grub2.html > > > -- > Regards > Martin Naughton
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Colin, Been looking at the grub2 for debian aswell. Is the help required with grub 1 or grub 2? i thought grub 1 was being dropped? http://packages.qa.debian.org/g/grub2.html -- Regards Martin Naughton
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Colin, Thanks. Will start looking in to the bugs. Started looking at the grub webpage. Will try out a few bugs fixes. http://packages.qa.debian.org/g/grub.html A wiki would be really handy on how to setup. http://en.wikipedia.org/wiki/GNU_GRUB -- Regards Martin Naughton On Fri, Dec 28, 2012 at 7:10 AM, Colin Watson wrote: > On Wed, Dec 12, 2012 at 11:53:54AM +0000, Martin Naughton wrote: > > Do you still need help. Me and another guy are interested > > in helping. Can you indicate if you still need help. We are not DD yet > but > > we are learning. We can help with the testing of grub and fix bugs while > > you can develop the application. If not help is needed can the ticket be > > closed? > > GRUB package maintenance in Debian still certainly needs help; while > we've generally managed to keep one primary maintainer (I came along > well after this RFH was initially filed, and have been the most active > on the team for the last couple of years), Debian really ought to be > able to manage a team with a higher bus factor for its principal boot > loader. We suffered from that this summer when I had some temporary > motivation problems; if another developer had been sufficiently active > and able to step in it's possible that we'd be shipping wheezy with GRUB > 2.00 rather than 1.99. > > You can certainly help out with testing and fixing individual bugs > without having to ask in advance (as long as you don't actually close > bugs without asking) - just mail the BTS as appropriate. I do think we > need more DDs involved, though. > > Jonathan is right that we need some kind of wiki documentation here. > I'll see if I can carve out some time soon to write up a skeleton of > such a thing ... > > -- > Colin Watson [cjwat...@debian.org] >
Bug#622960: Does this package still need help
Hello Guys, Has this package been adopted? Is there anyone that needs help? Can we close it if not? -- Regards Martin Naughton
Bug#683666: RFH: gradle -- Groovy based build system
Hello Guys, I am interested in helping maintain the gradle package. I am interested in gradle so helping maintain a package would help. what help is needed? Do you need help with packaging and testing on debian? How many people do you need to help? -- Regards Martin Naughton
Bug#248397: Subject: Re: GRUB 2 RFH
Hello Grub, Do you still need help. Me and another guy are interested in helping. Can you indicate if you still need help. We are not DD yet but we are learning. We can help with the testing of grub and fix bugs while you can develop the application. If not help is needed can the ticket be closed? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248397 -- Regards Martin Naughton