Bug#936086: RFS: vtun/3.0.4-1 [ITA] -- virtual tunnel over TCP/IP networks
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "vtun" * Package name: vtun Version : 3.0.4-1 Upstream Author : Maxim Krasnyansky * URL : http://vtun.sourceforge.net/ * License : GPL-2+ * Vcs : None Section : net It builds those binary packages: vtun - virtual tunnel over TCP/IP networks To access further information about this package, please visit the following URL: https://mentors.debian.net/package/vtun Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/v/vtun/vtun_3.0.4-1.dsc Changes since the last upload: * New upstream release. * New maintainer (Closes: #812758). * debian/rules: use of dpkg-buildflags instead of obsolete finding for noopt in DEB_BUILD_OPTIONS. * No stripping on building package. Patch by Helmut Grohne. (Closes: #883530). Regards, -- Rodrigo Carvalho
Re: Removing binary package from source
On Thu, Aug 29, 2019 at 03:34:10PM +0200, Birger Schacht wrote: > >> Is there a way to uninstall the qt applet when upgrading usbguard? > > Add Breaks on it. > > Mhm, that way libusbguard0 can not be installed unless > usbguard-applet-qt is manually removed, but I guess thats better than to > have a non working applet installed... Would a dist-upgrade > automatically remove the usbguard-applet-qt package in that case? I think it will. -- WBR, wRAR signature.asc Description: PGP signature
Re: Removing binary package from source
Hi, On 8/29/19 2:28 PM, Andrey Rahmatullin wrote: > On Thu, Aug 29, 2019 at 02:04:08PM +0200, Birger Schacht wrote: >> This old version will not work with the newer libusbguard0. > Why? Because libusbguard0 doest not provide a stable ABI and the two versions are not backwards compatible. The package installed the library in /usr/lib//usbguard, to mark it internal, but I forgot to declare a versioned depends for the applet. >> Is there a way to uninstall the qt applet when upgrading usbguard? > Add Breaks on it. Mhm, that way libusbguard0 can not be installed unless usbguard-applet-qt is manually removed, but I guess thats better than to have a non working applet installed... Would a dist-upgrade automatically remove the usbguard-applet-qt package in that case? thanks, Birger
Re: Removing binary package from source
On Thu, Aug 29, 2019 at 02:04:08PM +0200, Birger Schacht wrote: > This old version will not work with the newer libusbguard0. Why? > Is there a way to uninstall the qt applet when upgrading usbguard? Add Breaks on it. -- WBR, wRAR signature.asc Description: PGP signature
Removing binary package from source
Hi, usbguard upstream has decided to move the usbguard QT applet from the usbguard sources to a seperate repository (tba). I removed all traces from the QT applet from the usbguard source package, but there is one little problem: when people upgrade to the new usbguard, the QT applet will not be removed but will stay the old version. This old version will not work with the newer libusbguard0. Is there a way to uninstall the qt applet when upgrading usbguard? Or should I simply add a note to d/NEWS about the applet not working anymore? cheers, Birger
Re: Help with source only upload
Don't break threads please. On Wed, Aug 28, 2019 at 10:28:53PM -0500, Elías Alejandro wrote: > >The command is the same, isn't it? > uhm.. I don't think so. You need to explain why. > I was reading about to source-only > uploads because of[1] however I've uploaded by _mistake_ > with a changes file included binary and source, after > some hours I've noticed that it hasn't been built by buildd[2]. This sounds good. > I'd like to generate a changes file for a new debian > version of the package with only the source. This sounds good too. So what's wrong with the command? > I was reading also that if version ends in -0 or -1 source can be > included but not for the next version, I'm not sure if it's the > explanation. And this doesn't, as this talks about inclusion of orig.tar in the source package, not about things you talked earlier. This is a completely unrelated question but no, you don't need to include orig.tar in the source changes if it waas already uploaded previously. > In other hand, why buildd wasn't be able to built if the > changes file also included the source file? buildds do not build binaries that were uploaded by the uploader. -- WBR, wRAR signature.asc Description: PGP signature
