Re: Q: Ubuntu PPA induced version ordering mess.

2024-07-02 Thread Milan Kupcevic
On 7/1/24 14:48, Alec Leamas wrote: [...] Hi Alec, opencpn is currently in a beta phase targeting a 5.10.1 release. The beta versions are like "5.9.2-beta2+dfsg-1ubuntu1~bpo2204.1". The upstream policy is to use 5.9.2-beta2, 5.9.3-beta3 so this ordering is, although a bit strange, still

Bug#792751: ITP: e2fslibs1.41-dev -- legacy ext2/ext3/ext4 file system development libraries

2015-07-17 Thread Milan Kupcevic
Package: wnpp Severity: wishlist Owner: Milan Kupcevic Control: affects -1 yaboot * Package name: e2fslibs1.41-dev Version : 1.41.14 Upstream Author : Theodore Y. Ts'o * URL : http://e2fsprogs.sourceforge.net * License : GPL, LGPL, BSD, MIT/X Progra

Re: Proposal: Repository for fast-paced package backports

2018-12-26 Thread Milan Kupcevic
On 12/25/18 3:46 PM, Dominik George wrote: [...] > > Name of the new repository > == > > In the past, the name “volatile” was used for a similar repository, but > with a different scope (limited to data packages for things like virus > scanners). I will thus use the work

Re: Bits from the Release Team: Debian 10 'buster' is frozen; let's get it in shape

2019-03-12 Thread Milan Kupcevic
On 3/12/19 3:53 PM, Paul Gevers wrote: > Just like we announced in our freeze policy [1], the full freeze of > buster started today, some minutes ago. This means that from now on > (well, practically already 10 days ago) all migrations to testing will > require manual approval by the release team.

Re: Consensus Call: Git Packaging Round 1

2019-08-27 Thread Milan Kupcevic
On 8/27/19 1:37 PM, Alf Gaida wrote: > Am Dienstag, den 27.08.2019, 19:18 +0200 schrieb Adam Borowski: >> New stuff is always better. Go Electron! >> > Like it or not - the idea of pull requests (Github) or merge requests (Gitlab) > isn't exactly new. It might surprise you that people outside of d

Re: Git Packaging: Native source formats

2019-08-29 Thread Milan Kupcevic
On 8/28/19 4:00 PM, Sam Hartman wrote: > > Back in the day, one of the big reasons for separating .orig.tar.gz from > .diff.gz was to reuse upstream tarballs for space reasons, both in terms > of space on mirrors when the pool had two Debian revisions with the same > upstream, as well as to reduce

Re: Porter roll call for Debian Stretch

2016-09-30 Thread Milan Kupcevic
On 09/20/2016 05:46 PM, John Paul Adrian Glaubitz wrote: > On 09/20/2016 11:16 PM, Niels Thykier wrote: >>- powerpc: No porter (RM blocker) > > I'd be happy to pick up powerpc to keep it for Stretch. I'm already > maintaining powerpcspe which is very similar to powerpc. > Thank you Adrian f

Bug#874315: ITP: simulide -- real time electronic circuit simulator

2017-09-04 Thread Milan Kupcevic
Package: wnpp Severity: wishlist Owner: Milan Kupcevic * Package name: simulide Version : 0.1.5 Upstream Author : Santiago González * URL : https://sourceforge.net/projects/simulide/ * License : GPL-3 Programming Lang: C++ Description : real time

Bug#874316: ITP: simutron -- AVR simulator IDE

2017-09-04 Thread Milan Kupcevic
Package: wnpp Severity: wishlist Owner: Milan Kupcevic * Package name: simutron Version : 1.0.1 Upstream Author : Santiago González * URL : https://sourceforge.net/projects/simutron/ * License : GPL-3 Programming Lang: C++ Description : AVR simulator

Bug#811905: ITP: esptool -- create and flash firmware files to ESP8266 chip

2016-01-19 Thread Milan Kupcevic
Package: wnpp Severity: wishlist Owner: Milan Kupcevic * Package name: esptool Version : 0.4.6 Upstream Author : Christian Klippel , * URL : https://github.com/igrr/esptool-ck/ * License : GPL-2 Programming Lang: C Description : create and flash

Re: Packaging of static libraries

2016-04-10 Thread Milan Kupcevic
On 04/10/2016 12:15 PM, Clint Adams wrote: > On Mon, Apr 11, 2016 at 12:13:20AM +0800, Paul Wise wrote: >> We should change policy and packaging tools such that static linking >> are not enabled by default and only enabled when there is a good >> reason to do so; when requested by users or when the

Re: Packaging of static libraries

2016-04-10 Thread Milan Kupcevic
On 04/10/2016 06:05 PM, Jakub Wilk wrote: > * Milan Kupcevic , 2016-04-10, 16:51: >>>> We should change policy and packaging tools such that static linking >>>> are not enabled by default and only enabled when there is a good >>>> reason to do so; when r

Bug#825470: ITP: basez -- base 16/32/64 encode/decode data to standard output

2016-05-26 Thread Milan Kupcevic
Package: wnpp Severity: wishlist Owner: Milan Kupcevic * Package name: basez Version : 1.0.1 Upstream Author : Milan Kupcevic * URL : http://www.quarkline.net/basez/ * License : GPL Programming Lang: C Description : base 16/32/64 encode/decode data to

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

2016-06-08 Thread Milan Kupcevic
On 06/08/2016 11:19 AM, Felipe Sateler wrote: [...] > > So, say I want to contribute to a project I don't normally work in. Steps > in alioth: > [...] Well, I would go this route: - git clone - hack - git commit -a -v - git format-patch -1 --to=proj...@lists.alioth.debian.org | mailx -t >

Re: why, nicely explained (Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

2016-06-08 Thread Milan Kupcevic
On 06/08/2016 02:55 PM, Michael Lustfield wrote: > On Wed, 8 Jun 2016 15:47:46 +, Holger Levsen > mailto:hol...@layer-acht.org>> wrote: >>Thanks for this nice summary. It helped me understand things better. > > I'm... actually gonna save this for later because it helps me understand > the alio

Re: Genesis of the git.d.o/gitlab.d.o confusion (Was: Next steps for gitlab.debian)

2016-06-08 Thread Milan Kupcevic
On 06/08/2016 02:08 PM, Milan Kupcevic wrote: > On 06/08/2016 11:19 AM, Felipe Sateler wrote: >> >> So, say I want to contribute to a project I don't normally work in. Steps >> in alioth: >> > > [...] > > Well, I would go this route: > >

Re: New contributor experience

2025-05-30 Thread Milan Kupcevic
On 5/30/25 08:52, Thomas Lange wrote: I saw too many bug reports, that didn't had any reaction from the package maintainer for years. This should be avoided. The said bug reports are often vague and require significant time investment to figure out and are being judged by the maintainer not to