On Mon, Feb 17, 2025 at 04:50:56PM -0500, Richard Hansen wrote:
> On 2/17/25 13:16, Daniel Gröber wrote:
> > On Mon, Feb 17, 2025 at 12:59:43PM -0500, Richard Hansen wrote:
> > > Looks like it was automatically removed from
> > > <https://mentors.debian.net/pac
ttps://packages.debian.org/sid/ddclient> or
> <https://tracker.debian.org/pkg/ddclient> yet; is it normal to take 8h to
> update?
I couldn't make the upload because of the mentioned discrepancies. Please
re-upload the dsc to mentors or give me a branch with the right ver
Hi Richard,
I was going to sponsor ddclient, but it seems to have dropped out of
mentors and git has no branch for 3.11.2-2. MR!6 is based on debian/latest
but that has a changelog with 4.0.0~rc.3-1 now.
Please resubmit the dsc or cleanup git :-)
Thanks,
--Daniel
On Mon, Feb 17, 2025 at 03:03
Hi Christian,
vnstat's d/watch downloads an .asc file for the upstream tarball, but
doesn't include d/upstream/signing-key.asc to verify it. Please do both or
neither.
Thanks,
--Daniel
On Sun, Feb 16, 2025 at 07:33:10PM +0100, Christian Göttsche wrote:
> Package: sponsorship-reques
r any subsequent uploads of
radsecproxy in the future, feel free to send me the link to the dsc
directly via mail or irc.
Regards,
Daniel
Hi,
On Sun, Nov 10, 2024 at 12:59:11AM +0100, наб wrote:
> On Sat, Nov 09, 2024 at 09:14:48PM +0100, Daniel Gröber wrote:
> > Development documentation nit: I would add a note to d/control on when
> > Package: httpfs2 can be removed (trixie+1 I suppose) and that a Provides:
>
makes it impervious to #986320!
> (if it's ruled as "don't native unless it's Debian infra";
> unlikely, given we have 822 native packages, but).
Eh, I don't see that bug reaching consensus ;) Your call.
On Tue, Nov 05, 2024 at 11:00:11PM +0100, наб wrote:
>
any idea what's going on behind the scenes :D
Thanks for taking the time to explain this David, --with-source is also new
to me and was already super useful for libcurlfs upgrade testing :)
--Daniel
signature.asc
Description: PGP signature
> https://git.sr.ht/~nabijaczleweli/libcurlfs.deb/commit/de6a8f0d58534cd66c81ec63302f6d5e78a8b0b2)
> but the Salsa autopkgtest CI step naturally doesn't have fuse.ko loaded,
> and it can't auto-load from the chroot/container/whatever,
> but it also can't provide isolation-machine so it skips it.
> So I don't really know if it works (or if I need an explicit load step?).
That's a question for the salsa CI team I haven't ventured that deep yet:
https://salsa.debian.org/salsa-ci-team/pipeline#support-for-salsa-ci-use
Feel free to CC me if you end up sending an email.
--Daniel
signature.asc
Description: PGP signature
On 24.09.24 16:41, Shengjing Zhu wrote:
The reason that I propose to use 0.0~gitMMDD is to just track the
latest commit in the mono repo. It just stops caring how the sub
modules are tagged and avoid confusing in the single packaging version
This is what I have done for golang-github-moby-sy
On 21.06.24 23:15, Shengjing Zhu wrote:
I think people are hesitant to sponsor because of the reconstruction
of the upstream repository.
So I propose to create a new package called
golang-github-azure-azure-sdk-for-go-sdk, which contains all the
modules in the /sdk directory. And the package
ea I had was to just to build a httpfs2 pseudopackage that depends on
libcurlfs as part of src:libcurlfs.
Thoughts?
Thanks,
--Daniel
signature.asc
Description: PGP signature
#x27;s always active. Alternatively just remove the
old test repos in the patch :)
Dropping down one layer of abstraction to make sure debuild doesn't do anything
weird:
$ dpkg-buildpackage -uc -us
dpkg-buildpackage: info: source package git-subrepo
dpkg-buildpackage: info: source version 0.4.6-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Samo Pogačnik
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-Removed-hashbangs-from-sourced-only-files.patch
dpkg-source: info: applying
0002-Removed-executable-permission-on-sourced-only-files.patch
dpkg-source: info: applying
0003-Fixed-bash-completion-integration-with-git.patch
dpkg-source: info: applying 0004-Fixed-make-test-for-debian-build.patch
dpkg-source: info: applying 0005-Generate-test-git-repos-foo-bar-init.patch
debian/rules clean
[...]
seems fine.
--Daniel
signature.asc
Description: PGP signature
On Mon, Aug 12, 2024 at 11:37:24PM +1000, Dmitry Smirnov wrote:
> On Sunday, 11 August 2024 8:51:06 PM AEST Daniel Gröber wrote:
> > What remains to discuss is how you want to handle the git repo. Personally
> > I still haven't found a git packaging workflow I'm rea
I'm going to take the following approach out of the three approaches
> Daniel introduced in the previous email.
> 2) Have a select set of people (maint+uploaders) be collectively
> responsible or
> Since Dmitry has already been an uploader, I'll follow this tradition
>
o test cleaning you need an in-tree build.
I do that with `debuild -uc -us; debuild -- clean`, possibly inside a sid
schroot (not necessary for git-subrepo iirc).
--Daniel
signature.asc
Description: PGP signature
On Fri, Aug 09, 2024 at 07:55:22PM +0200, Bastian Germann wrote:
> Am 09.08.24 um 19:42 schrieb Daniel Gröber:
> > On Fri, Aug 09, 2024 at 05:47:50PM +0200, Bastian Germann wrote:
> > > Please see #1072958 for the RM request on markdown.
> > > It should be replaced wi
suggesting letting the RM go through and just re-uploading but
doing it that way seems a waste of ftp-master time. Do you have any other
suggestions?
Thanks,
--Daniel
signature.asc
Description: PGP signature
ted upstream as binary bare git repos, which i really
> do not like. So i prepared a few scripts, which generate the same repos with
> the
> same history upon each test suite startup.
IMO git-subrepo's upstream testsuite made some bad decisions here and I
hope we can convince them this way is better.
I hope you are planning to address admorgan's comments on the upstream PR
since they seem reasonable and the idea when sending patches upstream
really is that we get to drop them on the next release to keep the Debian
package from continuing to diverge.
Thanks,
--Daniel
signature.asc
Description: PGP signature
On Wed, Jul 10, 2024 at 12:57:48PM +0100, Peter B wrote:
> On 04/07/2024 14:44, Daniel Gröber wrote:
> > Sponsors are more likeley to pick up a package if it's personally
> > interesting to them,
>
> Something that might help here, is for the RFS template to include the
On Thu, Jul 04, 2024 at 06:28:17PM +0500, Andrey Rakhmatullin wrote:
> On Thu, Jul 04, 2024 at 03:22:35PM +0200, Daniel Gröber wrote:
> > > I don't think this is necessary or helpful: most RFSes are sponsored
> > > because they are in a good shape and somebody de
t next time you want to have something in Debian and see what
happens.
--Daniel
signature.asc
Description: PGP signature
's easier to just CC the ITP to d-mentors too since that
ought to have the full description.
--Daniel
PS: I was looking at the wrong wnpp bug :D
signature.asc
Description: PGP signature
the ITP in
the RFS is a good idea too. CC'ing a more focused list like d-science in
the ITP/RFS isn't a bad idea either.
tl;dr: more CCs == more better. Just don't go too crazy.
--Daniel
signature.asc
Description: PGP signature
pace where people at a comparable (but
maybe slightly higher) skill level as you hang out. I'm afraid I'm not much
help with specifics here.
--Daniel
signature.asc
Description: PGP signature
explains that
compiled binaries are not allowed. ]
[1]: https://www.debian.org/doc/devel-manuals#packaging-tutorial
--Daniel
signature.asc
Description: PGP signature
ted in taking care of blktrace and have a plan to address
> a different issue, that is #1069862. I appreciate it if you could
> sponsor this upload.
>
> > Firstly, apologies Daichi, if you wish adopt this package and maintain
> > it moving forward, like Daniel, I would b
t a NMU that packages a new upstream
pol> version, it is recommended to use a fake upstream version like
pol> CURRENT+reallyFORMER until one can upload the latest version again.
So I hardly think we can claim this is out of scope for NMUs if policy
deals with the nitty gritty of how to do it
Hi Samo,
On Fri, Jun 14, 2024 at 09:55:31PM +0200, Samo Pogačnik wrote:
> Hi Daniel,
>
> Dne 14.06.2024 (pet) ob 20:50 +0200 je Daniel Gröber napisal(a):
> > Below you're not ACK'ing some of my comments again. With email review you
> > really kind of have to s
onths and is likeley about to
get an NMU, which makes it look like a candidate for salvaging in the near
future to me. So Daichi, you could become it's official maintainer if that
interests you.
[contributors]: https://contributors.debian.org/contributor/bas/
--Daniel
signature.asc
Description: PGP signature
el makes me think git-subtree/subrepo have a good
chance of becoming more popular as we educate upstreams about how to
properly avoid future xz snafu. So you're doing really important work here <3
> Dne 10.06.2024 (pon) ob 22:26 +0200 je Daniel Gröber napisal(a):
> > In general yo
ne 28.05.2024 (tor) ob 19:23 +0200 je Daniel Gröber napisal(a):
> > I'm not super happy with the approach of putting git-subrepo.d inside
> > /usr/share/git-subrepo tbh. I might be able to let it pass but it seems
> > lintian found another issue that needs patching anyway so
---
Makefile| 1 +
debian/rules| 7 ++-
lib/git-subrepo | 22 +-
test/setup | 3 ---
4 files changed, 12 insertions(+), 21 deletions(-)
diff --git a/Makefile b/Makefile
index e7643a7..79898f5 100644
--- a/Makefile
+++ b/Makefile
@@ -62,6 +62,7 @@ $(DOCK
sh-completion-with-hashbang should really be W
severity but the '#!bash' it has is certainly completely wrong. Looks like
you'll have to get over your fear of patching upstream ;)
--Daniel
signature.asc
Description: PGP signature
o's use with something
like
[DEFAULT]
debian-branch = gnuabordo/latest
debian-tag = gnuabordo/%(version)s
and keep that on a separate branch from actual Debian packaging. Thats
obviously more work, so another way to go would be to just not tag your
internal uploads. That what I tend to do when I have something I want to
deply right away and don't feel like waiting on NEW review.
Might just be easier to apply to become DM for lsm and just not have so
much of a need for a local repo ;)
--Daniel
signature.asc
Description: PGP signature
-native packaging. Do you know what's up with that? I
could see why they would include it if they packaged it as a "native"
package but for non-native it just makes no sense. Could you talk to
upstream to figure out what's up with that? Feel free to CC me.
Just FYI: I'd appreciate git commits/patches on top of my repo above
instead of an updated dsc dump.
Thanks,
--Daniel
signature.asc
Description: PGP signature
c9552 * | git-debrebase convert-from-gbp: drop patches$ Samo Pogačnik 2w
873da * | Release 0.4.6-1 Samo Pogačnik 3w
51d5b * | d/control: Set myself as MaintainerSamo Pogačnik 3w
43a
a: man 7
> git-debrebase:
> 'converting an existing package').
Playing with this stuff sure is important to figure out whats going on ;)
--Daniel
PS: I noticed too late that I'd forgotten to start adding BTS to CC. I do
like to keep Debian work public and that includes teaching new
contributors, do you mind if I copy our conversation back to the BTS?
signature.asc
Description: PGP signature
d just edit it. I am starting to think
gbp is more trouble that it's worth now that I'm starting to look at some
of the other workflows...
+git-subrepo (0.4.6-1) unstable; urgency=medium
+
+ [ Daniel Gröber ]
+ * Fix Vcs URLs, s/guest-dxld/dxld-guest/
+ * Update changelog for
rkflow without messing
> with patch-sets (and tarballs), then this is the tool...
There's no escaping tarballs in Debian :3
Except maybe with dgit but even then you need to think about calling
origtargz...
*chanting* In the tarball, part of the tarball, in the tarball, part of the
tarball .
builder-
> based packaging tool: https://salsa.debian.org/spog/debdocker, just to get my
> head around debian ways. You can imagine that the project wasn't accepted very
> well on debian-devel:).
c.f. https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_fence
While sometimes we may need to build to understand others need to see you
understand before they let you build on their land ;-)
--Daniel
signature.asc
Description: PGP signature
ly
needs a once over to check for updates necessary changes tho.
Thanks,
--Daniel
.debian.org/sbuild)
> to create chroot used by sbuild, however sbuild is not run from my old
> ubuntu host directly, but from 'schroot -c debian-sid' prepared
> previously (see:
> https://wiki.debian.org/Packaging/Pre-Requisites#Option_2:_Schroot_and_Sbuild)
I don't see why that would be necessary though? Ubuntu also uses sbuild,
the version in their archive should work just fine for our purposes as long
as you make it use a Debian chroot.
--Daniel
signature.asc
Description: PGP signature
Hi Samo,
On Fri, Mar 15, 2024 at 06:42:54PM +0100, Samo Pogačnik wrote:
> Dne 11.03.2024 (pon) ob 20:18 +0100 je Daniel Gröber napisal(a):
> > Are you still interested in maintaining git-subrepo in Debian?
>
> please excuse me for my late response, but my situation from 2020/21 whe
On Mon, Apr 01, 2024 at 11:07:50PM +0200, Daniel Gröber wrote:
> I wish we could use a rebase workflow with gbp but I haven't found a way to
> do it yet. At least not with gbp import-ref as-is. We could work on a patch
> for it I suppose ;)
Looking at git-debrebase (https://www.you
ildpackage (which has a more extensive manpage) and passess most
options down as-is. git-buildpackage (by default) wraps debuild (or
optionally sbuild if you tell it to). sbuild allows building in chroots and
has a number of fancy options to make that easy.
Aah, it's nice and warm in the jung
Control: tags -1 - moreinfo
Thank you for the review! I've addressed the issues and lintian warnings
mentioned. Let me know if there are more issues.
Best,
Daniel
of distutils (Closes: #1064763)
Thank you for your consideration.
Regards,
Daniel
not doing so in this
case so I think we should clean up behind ourselves and move the config to
the new location.
You should then absoluteley print a message in the log to note this fact,
but perhaps not as conspicuously as you're printing the "configure me"
message. Something
or the new binary package to actually be compatible with the old
one since the config location changed.
- d/foolsm.init: Still has the old $CONFIG path
--Daniel
signature.asc
Description: PGP signature
d by ftp-master feel free to ping if I
forget.
--Daniel
On Mon, Jan 22, 2024 at 03:25:52PM +0100, Christian Göttsche wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "vnstat":
>
> * Package
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "wstroke":
* Package name : wstroke
Version : 2.1-1
Upstream contact : Daniel Kondor
* URL : https://github.com/dkondor/wstroke
hanges
--Daniel
signature.asc
Description: PGP signature
mit your porting changes upstream for review before
even integrating them into Debian though as I expect they'll be substantial
as they amount to supporting a new OS.
I'm following the dhcpcd project so I'll likely review your PR(s) anyway.
Thanks,
--Daniel
signature.asc
Description: PGP signature
On Fri, Nov 24, 2023 at 09:03:37PM +0200, Martin-Éric Racine wrote:
> On Fri, Nov 24, 2023 at 8:59 PM Daniel Gröber wrote:
> > On Fri, Nov 24, 2023 at 06:55:44PM +0200, Martin-Éric Racine wrote:
> > > dhcpcd (1:10.0.5-4) unstable; urgency=medium
> > > .
> > &
;; # No HURD support as yet
doesn't look promising.
--Daniel
signature.asc
Description: PGP signature
Control: tag - moreinfo
Thanks for the review Tobias.
Well, that happens if you put something on the back-burner for some
time. ;)
I do apologise...
All should be fixed now.
Cheers,
Daniel
zope.event (5.0-1) unstable; urgency=medium
.
* New upstream version 5.0
* debian/control:
- Bumped Stanrds-Version to 4.6.2.
* debian/copyright: updated packaging copyright years.
Regards,
--
Daniel Lenharo
Curitiba - Brazil
www.sombra.eti.br
31D8 0509 460E FB31 DF4B
9629
n/h/hello/hello_3.1-4.dsc>
Changes since the last upload:
None - initial upload.
Regards,
Daniel Fancsali
'm just pedantic about
compatibility.
[1]: https://github.com/ifupdown-ng/ifupdown-ng/issues/216
For a high-level overview of the project goals and how it compares to
ifupdown2 etc have a look at Maximilian's DebConf-21 talk:
https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/
--Daniel
ncy=medium
.
[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Set upstream metadata fields: Repository-Browse.
* Update standards version to 4.6.1, no changes needed.
* Set upstream metadata fields: Repository.
.
[ Daniel Gröber ]
* New upstream release
* Fix nonsense janit
an.org/science-team/meshlab/-/blob/master/debian/get-orig-source.sh
I was looking for an API endpoint to get the submodule commit actually,
this way at least I don't have to do a temp clone just to get it. This is
super useful, thanks!
--Daniel
atest berkeley-abc commit and pray it doesn't diverge
from what upstream's release uses too much. This is less than ideal
obviously.
Any input would be appreciated,
--Daniel
Hi Andrey,
On Fri, Jun 17, 2022 at 05:51:36PM +0500, Andrey Rahmatullin wrote:
> On Fri, Jun 17, 2022 at 02:01:42PM +0200, Daniel Gröber wrote:
> > my package yosys has a test failure on mips64el that I can't figure out and
> > consequently got removed from testing. I'm w
hing to do here?
I also wonder if there is a way to specify "everything except mips64el"
instead of listing all arches explicitly?
Thanks,
--Daniel
signature.asc
Description: PGP signature
colleagues in #debian-mentors about
> something similar
Let me know if you find any other good options in this space :)
Thanks,
--Daniel
signature.asc
Description: PGP signature
I'm not sure I fully get all the implications of these
choices.
Thanks,
--Daniel
signature.asc
Description: PGP signature
/download/makemkv-bin-(\d\S+)\.tar\.gz
looking at the linked forum it seems a new post is made for every release,
so the topic ID above is unlikely to stay the same, no?
It seems to me that rather defeats the purpose of a watch file.
--Daniel
On Sun, Jan 16, 2022 at 08:51:04PM -0500, Ben
t using this command:
dget -x
https://mentors.debian.net/debian/pool/main/z/zsh-histdb/zsh-histdb_0.0~git20211013.0b63f7c-1.dsc
Changes for the initial release:
zsh-histdb (0.0~git20211013.0b63f7c-1) unstable; urgency=medium
.
* Initial release (Closes: #998883)
--Daniel
limited git-bundle. See dpkg-source(1) section
"Format: 3.0 (git)".
I just stumbled on this while looking at the dpkg source I haven't actually
used it though.
--Daniel
update the package and reupload soon.
great, let me know and I'm happy to sponsor it.
Regards,
Daniel
why removing the systemd service file on purge? if it's included in
the package (rather than generated at install time, which would be
"unusual" anyway), then, it will automatically be purged by dpkg.
* did you consider using 'wrap-and-sort -bast'?
Regards,
Daniel
-x
https://mentors.debian.net/debian/pool/main/g/git-autofixup/git-autofixup_0.003001-1.dsc
Changes for the initial release:
git-autofixup (0.003001-1) unstable; urgency=medium
.
* Initial Release. (Closes: #987884)
Thanks,
--Daniel
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "gdu":
* Package name : gdu
Version : 4.1.0-1
Upstream Author : Daniel Milde
* URL : https://github.com/dundee/gdu
* License :
More info also here: https://mentors.debian.net/package/gdu/
Regards
Daniel
Package: sponsorship-requests
Severity: normal
Dear developers,
I am looking for a sponsor for my package "gdu":
* Package name : gdu
Version : 2.2.0
Upstream Author : Daniel Milde
* URL : https://github.com/dundee/gdu
* License : MIT
* Vcs : https://github.com/dundee/gdu.g
; probably be dxld-guest).
Ah good catch, fixed in 0.4.3-2.
Side note: I'm not sure if I'm supposed to increment the debian revision
during the mentors process or if should I just keep the initial -1
revision.
Thanks,
--Daniel
PS: You seem to have replied off-list, do you mind if I for
Hi Samo,
On Mon, Jan 04, 2021 at 11:16:04PM +0100, Samo Pogačnik wrote:
> Dne 04.01.2021 (pon) ob 22:11 +0100 je Daniel Gröber napisal(a):
> > I saw you submitted an RFS for git-subrepo a while back. I was wondering
> > what happened with that. It's not clear from what
s: #911397)
Regards,
Daniel
signature.asc
Description: PGP signature
-system-vcs-fields.
--Daniel
On Mon, Aug 17, 2020 at 12:41:10AM +, Thomas wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "ungoogled-chromium":
>
> * Package name : ungoogled-ch
ult Tcl/Tk version
because Tcl/Tk 8.5 is to be removed from Debian
+ Thanks to Sergei Golovan for the patch!.
* debian/compat
+ Switch compat level 8 to 11.
* remove d/secpanel.menu file.
* debian/changelog
+ Remove some whitespaces.
Regards,
Daniel Echeverry
|
libqt4-dev (<< 4.4.0), libqwt5-qt4-dev, libvtk6-dev, libminc-dev,
libqtassistantclient-dev, libpng16-dev, cmake
Dan
--
Daniel J. Sperka, Ph. D.
UC Davis Center for Neuroscience
/changelog
+ Remove trailing whitespaces.
* debian/watch
+ Use HTTPS in url.
Regards
--
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user
Hi Moaz,
the package looks good, but I can't build it in a clean chroot:
Run Build Command:"/usr/bin/make" "cmTC_2ee00/fast"
make[1]: Entering directory
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_2ee00.dir/build.make
CMakeFiles/cmTC_2ee00.dir/build
make[2]:
y extra by optional.
Regards,
--
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user
in Link to copyright format.
+ Change debhelper to 10 in B-D.
* debian/compat
+ Switch compat level 9 to 10.
* debian/copyright
+ Extend debian copyright holder years.
* debian/watch
+ Use secure uri.
Regards,
--
Daniel Echeverry
http://wiki.debian.org/DanielEche
Grohne for the patch!.
* debian/control
+ Bump standard versions 4.0.0 (no changes).
+ Bump debhelper to 10 in B-D.
+ Switch compat level 9 to 10.
* debian/copyright
+ Extend debian copyright holders years.
* debian/rules
+ export hardening flags.
Regards,
--
Daniel Eche
n-list file
Regards,
--
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user
esync/weresync_1.0.7-1.dsc
<https://mentors.debian.net/debian/pool/main/w/weresync/weresync_1.0.6-1.dsc>
Sincerely,
Daniel Manila
signature.asc
Description: OpenPGP digital signature
On 13.07.2017 17:56, Ghislain Vaillant wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for the following package:
>
> * Package name: python-latexcodec
> Version : 1.0.5-1
> Upstream Author : Matthias C. M. Troffaes
> *
retitle 867158 RFS: weresync/1.0.6-1 [ITP]
stop
New version uploaded so changing title to match.
ently released, but has equally little
affect on the function of the package).
You can get the newest package from this link:
https://mentors.debian.net/debian/pool/main/w/weresync/weresync_1.0.6-1.dsc
Thanks for your interest in this package.
Daniel Manila
x-spelling-error.diff
+ Refresh 0006-fix-some-spelling-errors.patch
+ Refresh 0007-fix_security_problems.diff
Regards,
--
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user
Oops, it generated a lintian error, but didn't fail the build. I forgot
exactly what happend.
Daniel
On 07/10/2017 05:21 PM, Andrey Rahmatullin wrote:
> On Mon, Jul 10, 2017 at 05:09:35PM +0600, Daniel Manila wrote:
>> debuild requires a signing key to be added to the package.
his so I could be wrong.
I'll update the various versions ASAP, I was building this under debian
stable, and just learned I should change to sid. I'm upgrading now and
will be posting an update to the package using sid tools in a day or so.
Thanks again!
Sincerely,
Daniel Manila
On 07
Hello,
The upstream package of WereSync was recently updated to version 1.0.5, so I
also updated my package here. You can now download the package with the
following link:
https://mentors.debian.net/debian/pool/main/w/weresync/weresync_1.0.5-1.dsc
Thank you for your help.
Daniel Manila
+ Bump standard versions 4.0.0 (no changes)
+ Change debhelper to 10 in B-D.
* debian/copyright
+ Extend copyright holder years.
* debian/compat
+ Switch compat level 9 to 10.
Regards,
Daniel Echeverry
--
Daniel Echeverry
http://wiki.debian.org/DanielEche
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "weresync"
* Package name: weresync
Version : 1.0.4-1
Upstream Author : Daniel Manila
* URL : https://github.com/DonyorM/weresync
.
Sincerely,
Daniel Manila
On Sat, 01 Jul 2017 23:07:41 +0600 Daniel Manila
wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "weresync"
>
> * Package name : weresync
> Version : 1.
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "weresync"
* Package name: weresync
Version : 1.0-1
Upstream Author : Daniel Manila
* URL : https://github.com/DonyorM/weresync
* License
1 - 100 of 1553 matches
Mail list logo
