Hi Bastian,
Il giorno mar, 10/12/2024 alle 21.37 +0100, Bastian Germann ha scritto:
> On Tue, 10 Dec 2024 09:28:40 +0100 Emilio Pozuelo Monfort
> wrote:
[...]
> I have uploaded libpaper to unstable with a 10 day delay.
> Giuseppe, if you want me to stop the upload, please just drop me a
> note.
Hello Sebastian,
Il giorno mer, 22/03/2023 alle 21.18 +0100, Sebastian Ramacher ha scritto:
> Control: tags -1 moreinfo
>
> On 2023-03-21 12:03:30 +0100, Giuseppe Sacco wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packa
. See #959403
+ * Update paperconf manual page. See #959404
+ * Update paperconfig manual page. See #959405
+
+ -- Giuseppe Sacco Fri, 17 Mar 2023 14:44:15 +0100
+
libpaper (1.1.28) unstable; urgency=medium
* Completely fixed #927226.
diff -Nru libpaper-1.1.28/debian/control libpaper-1.1.29
7:03.0 +0200
@@ -1,3 +1,10 @@
+libpaper (1.1.27) unstable; urgency=medium
+
+ * Fixed a circular dependency in debian/rules that left libpaper1.config
+not built. See #927226.
+
+ -- Giuseppe Sacco Sun, 23 Jun 2019 21:27:03 +0200
+
libpaper (1.1.26) unstable; urgency=medium
* Check
(3:6.0.6-6) unstable; urgency=medium
+
+ * Don't remove files managed by dpkg when purging package.
+
+ -- Giuseppe Sacco Thu, 04 Dec 2014 22:47:58 +0100
+
Thank you,
Giuseppe
unblock hylafax/3:6.0.6-6
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy
Hi Julien,
Il giorno ven, 01/03/2013 alle 11.31 +0100, Julien Cristau ha scritto:
> On Fri, Mar 1, 2013 at 08:00:27 +0100, Joachim Wiedorn wrote:
[...]
> > The next step is creating hylafax 6.0.6-5 as mentioned by Ivo De Decker.
> > Should I already prepare these updated package of hylafax now?
>
Hi Joachim,
Il 10/03/13 20.03, Joachim Wiedorn ha scritto:
Hello Guiseppe,
[...]
I have already uploaded this package to mentors.d.n for sponsoring. Do
you have time to review and sponsor this upload? If not I can write RFS.
See: https://mentors.debian.net/package/hylafax
I checked your pac
Il giorno ven, 01/03/2013 alle 08.00 +0100, Joachim Wiedorn ha scritto:
[...]
> The next step is creating hylafax 6.0.6-5 as mentioned by Ivo De Decker.
> Should I already prepare these updated package of hylafax now?
I have been waiting for capi4hylafax being accepted, but now I think
I'll packag
@@
+hylafax (3:6.0.6-2~wheezy1) testing-proposed-updates; urgency=high
+
+ * Added restricted deletion flag on tmp directory (Closes: #682824)
+ * Update postinst and postrm scripts for hylafax-client (Closes: #661482)
+
+ -- Giuseppe Sacco Fri, 12 Oct 2012 22:02:09 +
+
hylafax (3:6.0.6-1) unstable
Il giorno lun, 01/10/2012 alle 10.23 +0200, Julien Cristau ha scritto:
[...]
> The BTS thinks #661482 and #682824 are RC bugs affecting the version in
> testing.
You are right, I am going to prepare and updated package during this
weekend.
Thanks,
Giuseppe
--
To UNSUBSCRIBE, email to debian-re
Hi Julien,
could you please explain why you would remove hylafax from wheezy (I am
probably missing something here)? Isn't the package currently in testing
good enough? All RC bugs have been already solved. If you think it is
compulsory to fix these bugs on the wheezy version, than I may prepare
an
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
during last month there were one seriuos and one grave bugs against
hylafax. Both of them have been fixed almost three weeks ago while
upting the package with some changes due to better
Package: release.debian.org
Hi all,
I am requesting to migrate hylafax 2:6.0.5-3 from unstable to testing.
This request follow current freeze guidelines since it fixes two
important bugs #597693 and #514950 and hylafax priority is extra, and
the packages are already sitting in unstable since 12 d
Hi debian-release,
I would like to ask for a freeze exception for latest hylafax Debian
package. The latest package has been uploaded to unstable more than 10
days ago, without showing any new problem.
Main differences between latest (2:6.0.4-10) and testing (2:6.0.4-8)
version are:
1. fixed a ve
Hi release managers,
I would like to ask for an exception to the freeze. I uploaded 10 days
ago version 2:4.4.4-10 of hylafax to unstable. The new package only
change one line of code for fixing bug #497962. There are no other
changes compared to the version already frozen. The line has been
change
Il giorno sab, 10/03/2007 alle 14.43 -0800, Steve Langasek ha scritto:
> Hi Stephen,
>
> Here's the final NMU diff for the NMU which I'm uploading. The NMU will be
> uploaded to incoming shortly.
>
> Release team, please review for etch.
Is there any news on this review?
Bye,
Giuseppe
--
To
Il giorno sab, 10/03/2007 alle 14.43 -0800, Steve Langasek ha scritto:
> Hi Stephen,
>
> Here's the final NMU diff for the NMU which I'm uploading. The NMU will be
> uploaded to incoming shortly.
[...]
Hi Steve,
I prepared a new upload for this package too. It has been ready for one
week now sin
Il giorno mer, 21/02/2007 alle 16.23 -0500, Jamie ffolliott ha scritto:
> Package: libpam-ldap
> Version: 180-1.6
>
> 3rd report - can we please get an acknowledgement from somebody?
>
> The package is still broken in how it handles existing settings upon
> upgrades, and these settings are critic
Il giorno mer, 21/02/2007 alle 09.33 +0100, Martin Schulze ha scritto:
> Steve Langasek wrote:
> > On Tue, Feb 20, 2007 at 02:55:41PM +0100, Giuseppe Sacco wrote:
> > > Hi all,
> > > hylafax 4.3.2 has just been released[1]. This is a minor update but
> > > fi
Il giorno mar, 20/02/2007 alle 23.31 -0800, Steve Langasek ha scritto:
> On Tue, Feb 20, 2007 at 02:55:41PM +0100, Giuseppe Sacco wrote:
[...]
> > I understand this is a new upstream release, so I am asking if I may
> > package and upload this version, instead of backporting (almost
Hi all,
hylafax 4.3.2 has just been released[1]. This is a minor update but
fixes a few bug forwarded upstream and simplify the way Debian package
may be done. The more important fix is that PAM will work again (it is
somewhat broken on 4.3.1).
I understand this is a new upstream release, so I am
Hi release managers,
I would like to have the latest version of hylafax in etch. The new
version, 2:4.3.1-7, does have a few important fixes. Here is a summary
of the difference with the version currently in testing:
1. "faxlock", a new binary, was missing from the package
2. more conversion rules
Hi all,
I received two e-mail from people having problems with the latest
hylafax packages. These problems where related to four shell variables
that select which external programs should be used in order to encode
e-mail body and attachments: uuencode, mimencode, qp-encode.
Moreover I got one new
Hi Release Team,
I just read the announcement of the freeze and I am very glad of that,
but I wish you would allow for hylafax 2:4.3.1-3 to be migrated from
unstable into etch.
This new version is different from the one currently in testing in many
ways:
1. it is a new upstream version that has b
Il giorno dom, 27/11/2005 alle 04.53 -0800, Steve Langasek ha scritto:
[...]
> > > I guess the binary package has changed names from libpostgis1-pg74 to
> > > libpostgis1-pg7.4, and this covers us for the C++ ABI transition?
>
> > The binary package keep the same name since it already included the
Hi Steve,
Il giorno dom, 27/11/2005 alle 00.06 -0800, Steve Langasek ha scritto:
[...]
> The postgis source package has already been removed from testing. In
> addition, the existing postgis source package is already libpostgis1; is
> there a good reason for renaming this source package?
Upstrea
Il giorno mar, 08/11/2005 alle 21.51 -0500, Nathanael Nerode ha scritto:
> This is just a rundown of what little is left, and why.
[...]
> postgis -- Steve Langasek suggested removal
[...]
About postgis, the maintainer and I had a lot of problems in getting a
new version of the package. Moreover w
Il giorno lun, 13-06-2005 alle 13:43 -0700, Thomas Bushnell BSG ha
scritto:
> Giuseppe Sacco <[EMAIL PROTECTED]> writes:
>
> > There are a lot of new large packages that needs a *lot* of testing
> > before being releaseable. I think a one year release is really
> >
Il giorno sab, 11-06-2005 alle 11:26 +0200, Jose Carlos Garcia Sogo ha
scritto:
> El sáb, 11-06-2005 a las 08:15 +0200, Giuseppe Sacco escribió:
[...]
> > There are a lot of new large packages that needs a *lot* of testing
> > before being releaseable. I think a one year re
Il giorno ven, 10-06-2005 alle 18:58 -0700, Thomas Bushnell BSG ha
scritto:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > On Fri, Jun 10, 2005 at 11:14:02PM +0200, martin f krafft wrote:
> >> also sprach Steve Langasek <[EMAIL PROTECTED]> [2005.06.10.2300 +0200]:
> >> > Currently, I am planni
Hi all,
in order to make the sarge announcement translated, I would like to know
if there is already a english draft (on CVS?) that we may start working
on.
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Il giorno mer, 25-05-2005 alle 01:47 +0200, Frans Pop ha scritto:
> Hello translators,
[...]
> Last RevisionLast translator
> Language commitcomment or commit by
> en2005/05/241.43---
[...]
> it2005/02/131.18Luca Brivio
[..
Il giorno gio, 12-05-2005 alle 04:11 -0700, Steve Langasek ha scritto:
> Hi Stefano,
[...]
> I notice that the binary package went from 12MB in size to 772KB. Is this
> expected? (I'm happy to be able to save the space in the archive, as long
> as it doesn't mean something is missing. :)
I am go
Kenshi Muto wrote:
[...]
I built hylafax 1:4.2.1-5 on my arm buildd.
May I upload this if you want to enter -5 to Sarge sooner, Giuseppe?
(http://experimental.ftbfs.de/fetch.php?&pkg=hylafax&ver=1%3A4.2.1-5&arch=arm&stamp=1113137273&file=log&as=raw)
I think hylafax on official arm buildd won't be b
Hi all,
I prepared a new version of hylafax that fixes some really small
problems. They are sometimes "cosmetics", like using invoke-rc.d instead
of calling scripts in /etc/init.d.
The last upload was about 23 days ago and it is still unbuilt for arm
architecture. So I am wondering if I may safely
Hi all,
hylafax in sarge isn't working correctly. A few bugs were submitted
against version 4.2.0-6 and I am preparing a new upload for tomorrow.
May I send it to testing-proposed-update or should I use unstable?
Thanks,
Giuseppe
Il lun, 2004-08-30 alle 12:24, Mark Brown ha scritto:
> On Mon, Aug 30, 2004 at 11:39:46AM +0200, Giuseppe Sacco wrote:
[...]
> > May someone please check it? What's the problem?
>
> After packages have been built by the buildd there is an additional
> manual step where the
Hi,
I am waiting fot hylafax to migrate into testing. The grep-excuses says
that it is not compiled in Alpha, while it has been compiled by buildd 4
days ago.
May someone please check it? What's the problem?
Thank you,
Giuseppe
Steve Langasek wrote:
On Sun, Aug 22, 2004 at 09:32:22AM +0200, Giuseppe Sacco wrote:
[...]
What should I do to make sure that hylafax goes into sarge?
Please upload a fixed package to unstable with urgency=high. If you
believe the best way to fix this problem is with the new upstream
hi all,
the hylafax packages have been blocked in unstable since the arm buildd
is really slow. Moreover hylafax was waiting for the libtiff transition
and has been in unstable for 18 days now.
There are numerous bug fixes in the unstable (4.1.8-16) version and a
new version has already been
40 matches
Mail list logo
