Hi Samo,
On Sat, May 25, 2024 at 07:30:46PM +0200, Samo Pogačnik wrote:
> https://salsa.debian.org/spog/git-subrepo/-/commit/42628d43faa4a05eb3dd3c4b75d9d194ce6bda90
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
On Mon, May 06, 2024 at 02:10:53PM -0300, Lucas Castro wrote:
> >https://salsa.debian.org/debian/lsm
>
> I'm already using gbp, on my own repository server
>
> https://git.gnuabordo.com.br/foolsm.git/, I haven't created the salsa
> account yet.
Ah. You should have put that in the
Hi Lucas,
Hi d-mentors (there's a workflow question below),
On Sun, Mar 24, 2024 at 05:16:54PM -0300, Lucas Castro wrote:
> The source builds the following binary packages:
>
> foolsm - Link connectivity monitor tool
> lsm - Link connectivity monitor tool - transitional package
>
> To
Samo Pogačnik 3w
51d5b * | d/control: Set myself as MaintainerSamo Pogačnik 3w
43a8c * | d/control: Point Vcs to new location (salsa/$ Samo Pogačnik 3w
bf7e8 * | Merge tag '0.4.6' into debian/sid Samo Pogačnik 4w
|\|
On Wed, Apr 24, 2024 at 10:06:49PM +0200, Samo Pogačnik wrote:
> Ok, so i'll prepare merge request in salsa gitlab, after pushing my
> change in my working branch?
So creating a MR is fine but it's not the whole story with gbp. With gbp
you're always dealing with both a debian and an upstream
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 0.4.3-2 release
Commits
Hi Samo,
On Mon, Apr 15, 2024 at 09:13:03PM +0200, Samo Pogačnik wrote:
> Thanks for the review. I followed your suggestions above and recommited
> d/control and
> d/changelog.
>
> > As for the Vcs change: I'd prefer if we put the git repo in the debian/*
> > namespace on Salsa.
> >
>
> Here i
Hi Samo,
On Sun, Mar 31, 2024 at 01:42:48PM +0200, Samo Pogačnik wrote:
> I prepared a new git-subrepo in salsa as a fork of your project (
> https://salsa.debian.org/spog/git-subrepo). Then i updated upstream and
> prepared
debby> a new 'debian/sid' branch. Would you be so kind to take a look
Hi Samo,
wouldn't you know it I've become a DD before I got a response to the
git-subrepo ITP/RFS ;) I also completely forgot about it until I needed it
just now.
Are you still interested in maintaining git-subrepo in Debian?
I'm trying to limit my personal packaging work to stuff I actually
Hi Samo,
On Mon, Apr 01, 2024 at 07:54:09PM +0200, Samo Pogačnik wrote:
> > Workflow wise I don't see why you needed to make a merge commit at
> > d0cc659. Can you explan what you were doing?
>
> Well, after i updated the upstream branch, i wanted to preserve your
> original debian/sid branch, so
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.youtube.
Hi Samo,
On Tue, Mar 19, 2024 at 10:00:44PM +0100, Samo Pogačnik wrote:
> > We can also do a call to figure out where you're at and what info you need
> > because the huge scope of the general packaging related documentation can
> > be a bit overwhelming and confusing, even if what you need to
Hi Lucas,
On Tue, Mar 05, 2024 at 03:29:49PM -0300, Lucas Castro wrote:
> > Are you sure you want to change the source package name? Doing so fractures
> > the history of the package on tracker.d.o and it's not really necessary.
>
> The upstream has changed software name but it's a good point
Hi Lucas,
On Mon, Feb 19, 2024 at 04:50:27PM -0300, Lucas Castro wrote:
> * Package name : foolsm
Are you sure you want to change the source package name? Doing so fractures
the history of the package on tracker.d.o and it's not really necessary.
Quick package review:
- d/postinst: I
Hi Christian,
I'd be happy to sponsor vnstat (as soon as my NM process propagates
through the bueraucracy). In the meantime I've had a look at the
packaging and I have no notes :)
I'll try to remember to upload vnstat but since it might be a while
still until my key is accepted by ftp-master
Hi Frederic,
On Mon, Nov 27, 2023 at 02:30:28PM +0100, PICCA Frederic-Emmanuel wrote:
> Hello, I would like to know if there is command line tool usable from
> bash , which allows to list all the artefacts of a given .changes file.
You can use the dcmd wrapper from devscripts:
$ dcmd echo
Hi Martin,
On Fri, Nov 24, 2023 at 09:54:30PM +0200, Martin-Éric Racine wrote:
> > Looking the last your three dhcpcd revisions I wonder if you shouldn't be
> > debugging these fundamental build issues on a porterbox or in a VM rather
> > than through the buildds?
>
> I don't have access to the
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
> > > .
> > &
Hi Martin,
On Fri, Nov 24, 2023 at 06:55:44PM +0200, Martin-Éric Racine wrote:
> dhcpcd (1:10.0.5-4) unstable; urgency=medium
> .
>* Attempt to fix the GNU/Hurd build.
> + 003_fix_FTBFS_on_Hurd.patch
Does upstream even support hurd? Looking at ./configure:
gnu*) OS=hurd;; # No HURD
Hi Nicholas,
On Sun, Sep 17, 2023 at 02:56:47PM -0400, Nicholas D Steeves wrote:
> Thank you for working on this! One note: where is it documented how
> ipupdown and ipupdown-ng interact?
You just install the ifupdown-ng package and it kicks ifupdown out the door :)
More seriously: ifupdown-ng
.
[ 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 janitor commits
Hi Ryan,
On Wed, Jun 21, 2023 at 03:07:24PM -0500, Ryan Pavlik wrote:
> I'm not sure if uscan can do it,
I did get it working but it's exceedingly cludgy. I have to use mode=git
for the second component since uscan can't just download master.tar.gz
AFACT (it's at a static location not linked
Hi Mentors,
I'm working on packaging prjtrellis[1] which has a git submodule that is
required for building. My plan is to use dpkg-source's multi upstream
tarball support to do this.
[1]: https://github.com/YosysHQ/prjtrellis
I'm wondering if a) this is a good idea and 2) how to get uscan to
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 wonder
Hi Mentors,
my package yosys has a test failure on mips64el that I can't figure out and
consequently got removed from testing. I'm wondering how to deal with this?
From reading the policy it seems I can use the Architecture field to list
all arches except mips64el. Is that the right thing to do
Hi Gavin and Andrey,
On Fri, Apr 01, 2022 at 07:24:55PM +0500, Andrey Rahmatullin wrote:
> This suggests they don't know or don't care about ABI stability.
Yeah, that's my guess too. On the other hand reading through their, pretty
detailed, changelogs does seem to suggest they keep track of
Hi debian-mentors,
I'm working on packaging [vpp] which installs a number of shared libraries
that may want to be used by other Debian packages in the future.
[vpp]: https://github.com/fdio/vpp/
However upstream just uses their release version in SONAME which doesn't
seem very useful. Is it
Hi Ben,
I just had a quick look at your package because I didn't even know makemkv
came in a version that could be considered "oss" :)
I found your debian/watch file a bit peculiar,
version=4
opts="" \
https://www.makemkv.com/forum/viewtopic.php?t=224
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: d...@darkboxed.org
Dear mentors,
I am looking for a sponsor for my package "zsh-histdb":
* Package name: zsh-histdb
Version : 0.0~git20211013.0b63f7c-1
Upstream Author : Tom Hinton
* URL :
Hi,
On Thu, Oct 28, 2021 at 09:02:21PM -0500, Hunter Wittenborn wrote:
> Anything I could try?
I'm not sure this is a path very well travelled, but dpkg does in principle
seem to support a source package format called "3.0 (git)" where the source
tarball is basically a depth limited git-bundle.
Package: sponsorship-requests
Severity: wishlist
Hi mentors,
I am looking for a sponsor for my package "git-autofixup":
* Package name: git-autofixup
Version : 0.003001-1
Upstream Author : Jordan Torbiak
* URL : https://github.com/torbiak/git-autofixup
* License
Hi Samo,
thanks for the quick review!
On Mon, Jan 04, 2021 at 09:01:51PM +0100, Samo Pogačnik wrote:
> Thanks for that. I sincerely hope, that you get through with this useful tool.
I saw you submitted an RFS for git-subrepo a while back. I was wondering
what happened with that. It's not clear
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
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "git-subrepo":
* Package name: git-subrepo
Version : 0.4.3-1
Upstream Author : Ingy döt Net
* URL : https://github.com/ingydotnet/git-subrepo
* License
Hi Thomas,
Thanks for working on this package!
I did a quick review I noticed the Vcs-* fields in debian/control are
pointing at the upstream git repo when they should be pointing to the
debianized one instead, see
36 matches
Mail list logo
